| | 1 | [[PageOutline(1-2)]] |
| | 2 | |
| | 3 | = CHK-005: GENI Network Connectivity OpenFlow Checks = |
| | 4 | |
| | 5 | Connectivity through the GENI network is continuously monitored via sets of pings between resources on many GENI aggregates. |
| | 6 | These resources have been allocated in the same way experimenters would allocated resources. OpenFlow controllers are also used as part of this monitoring experiment to direct the ping traffic flow across the network. |
| | 7 | The GENI Network Connectivity OpenFlow Checks procedure defines the steps to make sure that connectivity is achieved throughout the network. |
| | 8 | |
| | 9 | = 1.0 GENI Network Connectivity OpenFlow Check = |
| | 10 | |
| | 11 | == 1.1 Goals of Network Connectivity OpenFlow Check == |
| | 12 | |
| | 13 | The goal of this check is to ensure that the GENI network is performing as expected. |
| | 14 | |
| | 15 | == 1.2 Steps for Network Connectivity OpenFlow Check == |
| | 16 | |
| | 17 | 1. Log onto the [http://alerts.gpolab.bbn.com/nagios3/ alerting system]. |
| | 18 | 1. Select Service Group / Summary in the left pane. [[BR]][[Image(Nagios-Service Groups Summary.png)]] |
| | 19 | 1. In the "GENI data plane connectivity checks" group row, check for the presence of CRITICAL or PENDING service under the "Service Status Summary" column. |
| | 20 | 1. Click on the OK link under the "Service Status Summary" column, which will bring you to the "Service Status Details" for all the services in OK state. [[Image(Nagios-Connectivity Service Groups Details OK.png)]] |
| | 21 | 1. Sort the service with the "Last Check" columns values (click on the up (ascending) orange arrow). Make sure that the time stamps are all within the last 15 minutes or so. |
| | 22 | |
| | 23 | == 1.3 Network Connectivity OpenFlow Check - Pass Criteria == |
| | 24 | |
| | 25 | This check passes if there are no CRITICAL or PENDING services on step 3 of the Steps above, |
| | 26 | |
| | 27 | AND |
| | 28 | |
| | 29 | if the time stamps of the OK services are recent on step 5 of the Steps above. |
| | 30 | |
| | 31 | == 1.4 Network Connectivity OpenFlow Check - Fail Criteria and Escalation == |
| | 32 | |
| | 33 | If there are CRITICAL services in step 3 above: |
| | 34 | 1. click on the CRITICAL link under the "Service Status Summary" column, which will bring you to the "Service Status Details" for all the services in CRITICAL state. [[Image(Nagios-Connectivity Service Groups Details CRITICAL.png)]] |
| | 35 | 1. Sort the service with the "Last Check" columns values (click on the up (ascending) orange arrow). Make sure that the time stamps are all within the last 15 minutes or so. |
| | 36 | |
| | 37 | If the time stamps are within the accepted range, the services are indeed in CRITICAL states. |
| | 38 | If the time stamps are not within the accepted range, something is amiss in the monitoring system and is preventing timely status updates. |
| | 39 | |
| | 40 | If there are PENDING services in step 3 above: |
| | 41 | 1. click on the PENDING link under the "Service Status Summary" column, which will bring you to the "Service Status Details" for all the services in PENDING state. |
| | 42 | |
| | 43 | A PENDING state, means that the monitoring system has never reported on the availability status of a particular aggregate. |
| | 44 | |
| | 45 | '''__Escalation:__''' If there are availability services in CRITICAL states: Report to ??? GMOC team - gmoc@grnoc.iu.edu [[BR]] |
| | 46 | '''__Escalation:__''' If there are availability services in PENDING states: Report to UKY team - ??? [[BR]] |
| | 47 | '''__Escalation:__''' If there are availability services with stale time stamps: Report to UKY team - ??? [[BR]] |
| | 48 | |
