Changes between Version 11 and Version 12 of GENIOperationsTrial


Ignore:
Timestamp:
06/18/15 08:02:21 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIOperationsTrial

    v11 v12  
    4040||'''Priority'''||'''#'''||'''Event type'''                ||'''Dispatch'''||'''Procedure'''||
    4141|| Critical     || 1     ||Emergency Stop and LLR          || GMOC         || [http://gmoc.grnoc.iu.edu/uploads/7e/39/7e39c5ec9577a5badab80ea15419ece8/GENI-Emergency-Stop-Procedure-and-Workflow.pdf GMOC Emergency Stop procedure] and [https://gmoc.grnoc.iu.edu/uploads/79/f2/79f227a094bd55b11838b994498d525a/GENI-LLR-Procedure-Workflow.pdf GMOC LLR procedure] ||
    42 || Critical     || 2     ||Security Event ''[*]''          || GMOC         || [wiki:LuisaSandbox/GENIOperationsTrial/SecurityEvent OPS-002-A: Security: System Security Events]  ||
     42|| Critical     || 2     ||Security Event ''[*]''          || GMOC         || [wiki:GENIOperationsTrial/SecurityEvent OPS-002-A: Security: System Security Events]  ||
    4343|| Critical     || 3     ||GENI !Clearinghouse/Portal Event        || GMOC         || <<Insert OPS procedure link>> ||
    4444|| Critical     || 4     ||Stitching Computation Service   || GMOC         || GMOC I2 SCS Procedure  exists        ||
    4545|| Critical     || 5     ||AL2S Aggregate Event            || GMOC         || GMOC OESS Procedures exist           ||
    46 || Critical     || 6     ||GENI Stitching Event            || GMOC         || [wiki:LuisaSandbox/GENIOperationsTrial/GENINetworkStitching OPS-003-B: Network Stitching Experiment Debugging Procedure] ||
    47 || High         || 7     ||WiMAX Multipoint VLANs Events   || GMOC         || [wiki:LuisaSandbox/GENIOperationsTrial/WimaxDataplaneebugging OPS-006-B: GENI WiMAX Dataplane Debugging]  ||
     46|| Critical     || 6     ||GENI Stitching Event            || GMOC         || [wiki:GENIOperationsTrial/GENINetworkStitching OPS-003-B: Network Stitching Experiment Debugging Procedure] ||
     47|| High         || 7     ||WiMAX Multipoint VLANs Events   || GMOC         || [wiki:GENIOperationsTrial/WimaxDataplaneebugging OPS-006-B: GENI WiMAX Dataplane Debugging]  ||
    4848|| High         || 8     ||Regional (AM+Switches+links)    || Rack or Site Group || <<Insert OPS procedures links>> ||
    49 || High         || 9     ||Site Events reported by site contact|| GMOC         ||   [wiki:LuisaSandbox/GENIOperationsTrial/SitePowerOutage OPS-004-A: Site Power Outage], [wiki:LuisaSandbox/GENIOperationsTrial/ScheduledMaintenance OPS-005-A: Scheduled Site Maintenance] ||
    50 || High         || 10    ||Site Events(AM+Switches+links reported by experimenters or tools) ''[**]''|| Rack or Site Group || [wiki:LuisaSandbox/GENIOperationsTrial/SitePowerOutage OPS-004-A: Site Power Outage], [wiki:LuisaSandbox/GENIOperationsTrial/ScheduledMaintenance OPS-005-A: Scheduled Site Maintenance], [wiki:LuisaSandbox/GENIOperationsTrial/WimaxDebugging OPS-006-A: GENI WiMAX Base Station Debugging]  ||
     49|| High         || 9     ||Site Events reported by site contact|| GMOC         ||   [wiki:GENIOperationsTrial/SitePowerOutage OPS-004-A: Site Power Outage], [wiki:GENIOperationsTrial/ScheduledMaintenance OPS-005-A: Scheduled Site Maintenance] ||
     50|| High         || 10    ||Site Events(AM+Switches+links reported by experimenters or tools) ''[**]''|| Rack or Site Group || [wiki:GENIOperationsTrial/SitePowerOutage OPS-004-A: Site Power Outage], [wiki:GENIOperationsTrial/ScheduledMaintenance OPS-005-A: Scheduled Site Maintenance], [wiki:GENIOperationsTrial/WimaxDebugging OPS-006-A: GENI WiMAX Base Station Debugging]  ||
    5151|| High         || 11    ||Experimenter Tools Events(Portal, jacks, omni..)|| Tools Contacts ||  ||
    52 || High         || 12    ||Monitoring Infrastructure Events|| UKY Monitoring team ||[wiki:LuisaSandbox/GENIOperationsTrial/MonitoringSystemOutage OPS-001-C: Monitoring: Monitoring System Outage]   ||
    53 || Normal       || 13    ||Monitoring Infrastructure Setup || UKY Monitoring team / GPO ||[wiki:LuisaSandbox/GENIOperationsTrial/CreatingMonitoringAlert OPS-001-A: Monitoring: Creating Monitoring Event Alerts], [wiki:LuisaSandbox/GENIOperationsTrial/MonitoringSitesProcedure OPS-001-B: Monitoring: Adding Monitoring Sites] ||
     52|| High         || 12    ||Monitoring Infrastructure Events|| UKY Monitoring team ||[wiki:GENIOperationsTrial/MonitoringSystemOutage OPS-001-C: Monitoring: Monitoring System Outage]   ||
     53|| Normal       || 13    ||Monitoring Infrastructure Setup || UKY Monitoring team / GPO ||[wiki:GENIOperationsTrial/CreatingMonitoringAlert OPS-001-A: Monitoring: Creating Monitoring Event Alerts], [wiki:GENIOperationsTrial/MonitoringSitesProcedure OPS-001-B: Monitoring: Adding Monitoring Sites] ||
    5454
    5555 ''[*] Security Events start as Critical and may be re-prioritized upon investigation. [[BR]]''
    … …  
    8484||'''Procedure Name '''             || ''' Procedure Description ''' ||
    8585|| [http://groups.geni.net/geni/wiki/GENIMonitoring/Alerts OPS-001-A: Monitoring: Creating Monitoring Event Alerts] || Instructions to how to define `alerts` for operation events.||
    86 || [wiki:LuisaSandbox/GENIOperationsTrial/MonitoringAddingSites OPS-001-B: Monitoring: Adding Monitoring Sites] ||  Defines the required information to request the addition, modification, or removal of a GENI site in monitoring. ||
    87 || [wiki:LuisaSandbox/GENIOperationsTrial/MonitoringSystemOutage OPS-001-C: Monitoring: Monitoring System Outage] || Defines how to report and respond to monitoring system events such as: collector or GUI is down, report non-critical bugs, or incorrect measurements ||
    88 || [wiki:LuisaSandbox/GENIOperationsTrial/SecurityEvent OPS-002-A: Security: System Security Events] || Describes how to report a security event to the GENI Monitoring team, and how to respond to that event. This type of event can also include Emergency Stop events.||
    89 || [wiki:LuisaSandbox/GENIOperationsTrial/DataPlaneDebugging OPS-003-A: GENI Network: Dataplane Debugging] || Defines the processes to be used for detecting and debugging GENI experiment issues with the data plane and control plane in experiments. [1] ||
    90 || [wiki:LuisaSandbox/GENIOperationsTrial/GENINetworkStitching OPS-003-B: GENI Network: Stitching Experiment Debugging] || Defines detecting and debugging GENI Network Stitching experiment issues with the stitching of Layer 2 VLAN for GENI experiments.||
    91 || [wiki:LuisaSandbox/GENIOperationsTrial/SitePowerOutage OPS-004-A: Site Power Outage] || Defines how handle a site power failure and how to verify that the site's aggregate is fully restored upon recovery [1] ||
    92 || [wiki:LuisaSandbox/GENIOperationsTrial/ScheduledMaintenance OPS-005-A: Scheduled Site Maintenance] || Defines schedules one-time or periodic maintenance activities [2] ||
    93 || [wiki:LuisaSandbox/GENIOperationsTrial/WimaxDebugging OPS-006-A: GENI WiMAX Base Station Debugging]  || Defines how to identify and remedy GENI WiMAX base station configuration at a WiMAX site. [3] ||
    94 || [wiki:LuisaSandbox/GENIOperationsTrial/WimaxDataplaneebugging OPS-006-B: GENI WiMAX Dataplane Debugging]  || Defines how to identify and remedy GENI WiMAX multipoint VLAN(s)between sites ||
     86|| [wiki:GENIOperationsTrial/MonitoringAddingSites OPS-001-B: Monitoring: Adding Monitoring Sites] ||  Defines the required information to request the addition, modification, or removal of a GENI site in monitoring. ||
     87|| [wiki:GENIOperationsTrial/MonitoringSystemOutage OPS-001-C: Monitoring: Monitoring System Outage] || Defines how to report and respond to monitoring system events such as: collector or GUI is down, report non-critical bugs, or incorrect measurements ||
     88|| [wiki:GENIOperationsTrial/SecurityEvent OPS-002-A: Security: System Security Events] || Describes how to report a security event to the GENI Monitoring team, and how to respond to that event. This type of event can also include Emergency Stop events.||
     89|| [wiki:GENIOperationsTrial/DataPlaneDebugging OPS-003-A: GENI Network: Dataplane Debugging] || Defines the processes to be used for detecting and debugging GENI experiment issues with the data plane and control plane in experiments. [1] ||
     90|| [wiki:GENIOperationsTrial/GENINetworkStitching OPS-003-B: GENI Network: Stitching Experiment Debugging] || Defines detecting and debugging GENI Network Stitching experiment issues with the stitching of Layer 2 VLAN for GENI experiments.||
     91|| [wiki:GENIOperationsTrial/SitePowerOutage OPS-004-A: Site Power Outage] || Defines how handle a site power failure and how to verify that the site's aggregate is fully restored upon recovery [1] ||
     92|| [wiki:GENIOperationsTrial/ScheduledMaintenance OPS-005-A: Scheduled Site Maintenance] || Defines schedules one-time or periodic maintenance activities [2] ||
     93|| [wiki:GENIOperationsTrial/WimaxDebugging OPS-006-A: GENI WiMAX Base Station Debugging]  || Defines how to identify and remedy GENI WiMAX base station configuration at a WiMAX site. [3] ||
     94|| [wiki:GENIOperationsTrial/WimaxDataplaneebugging OPS-006-B: GENI WiMAX Dataplane Debugging]  || Defines how to identify and remedy GENI WiMAX multipoint VLAN(s)between sites ||
    9595
    96 [1] Before investigating this type of issue, first verify that it is not due to a [wiki:LuisaSandbox/GENIOperationsTrial/ScheduledMaintenance Scheduled Maintenance].[[BR]]
    97 [2] Sites, services or resources outages may be caused by a [wiki:LuisaSandbox/GENIOperationsTrial/ScheduledMaintenance Scheduled Maintenance]. [[BR]]
     96[1] Before investigating this type of issue, first verify that it is not due to a [wiki:GENIOperationsTrial/ScheduledMaintenance Scheduled Maintenance].[[BR]]
     97[2] Sites, services or resources outages may be caused by a [wiki:GENIOperationsTrial/ScheduledMaintenance Scheduled Maintenance]. [[BR]]
    9898[3] A WiMAX issue arises when the frequency or transmit power of a campus WiMAX base station changes. These variables are fixed by site administrators and negotiated via a GENI-Sprint agreement. An event of this type should be very rare, but if monitoring reports a change, handling the event is high priority.
    9999