| | 1 | = GENI Monitoring Tips = |
| | 2 | |
| | 3 | This page highlights how to use GENI Monitoring features to investigate GENI Operations issues. All procedures assume that GENI Monitoring user is logged into the [http://genimon.uky.edu/ GENI Monitoring System]. |
| | 4 | |
| | 5 | == Determine a Slice Topology and Usage at each Aggregate == |
| | 6 | |
| | 7 | In a scenario where the slice name is known, it is possible to determine its topology (nodes and links) and bandwidth usage for each site. In this sections we will show how to determine the topology for a slice named "triangle" and then show usage for one of the sites in this experiment. |
| | 8 | |
| | 9 | 1. In the left-hand navigation bar, type `"triangle"` in `Search` box. This will show matching any item in monitoring containing the string `"triangle"` in the main panel. |
| | 10 | |
| | 11 | 2. In the `Slices` listing select the slice ID `"ch.geni.net_ln-test_slice_triangle"`. This will show all slice details in the main panel including: |
| | 12 | - Map tab - A resource allocation map, not the actual topology of the slice. |
| | 13 | - Active Members tab - The project owner of the the slice |
| | 14 | - Slivers tab - The list of compute resource slivers and network slivers associated with the slice. |
| | 15 | |
| | 16 | 3. For our triangle slice, the `Slivers` tab will include a lists of 4 slivers (1 from AL2S and 3 from Rack Aggregates). From this list you can see that te slice has 3 nodes (1 at each site) and 3 links at AL2S, as shown below: |
| | 17 | |
| | 18 | [[Image(triangle-sliver-details.jpg, 80%)]] |
| | 19 | |
| | 20 | 4. You can select the each of the site slivers to determine which VM server or raw device the compute resource is allocated on. For example, selecting: |
| | 21 | - `"geni.uchicago.edu_sliver_5003"` shows that compute resource is on `"geni.uchicago.edu_node_pcvm3-1"` |
| | 22 | - `"instageni.cenic.net_sliver_1266"` shows that compute resource is on `"instageni.cenic.net_node_pcvm2-2"` |
| | 23 | - `"instageni.nysernet.org_sliver_24968"` shows that compute resource is on `"instageni.nysernet.org_node_pcvm3-4"` |
| | 24 | |
| | 25 | 5. You can determine the slice topology and the site usage statistics by using the VLANs IDs allocated to the slice. VLANs can be determined from the AL2S sliver details: |
| | 26 | - Selected the AL2S sliver `"urn:publicid:IDN+ch.geni.net:ln-test+slice+triangle:1bc9e85e-146c-4991-a4e9-96c5f3a5dee9"` for the list of slivers for this slice. |
| | 27 | - Select each of the links that are part of the sliver to find VLANs allocated: |
| | 28 | * I2-LOSA-NEWY32AOA-VLAN-51145 includes `sdn-sw.losa.net.internet2.edu:eth5/1:1550` and `sdn-sw.newy32aoa.net.internet2.edu:eth7/2:1714` |
| | 29 | * I2-LOSA-STAR-VLAN-51146 includes `sdn-sw.losa.net.internet2.edu:eth5/1:1565` and `sdn-sw.star.net.internet2.edu:eth7/1:3092` |
| | 30 | * I2-NEWY32AOA-STAR-VLAN-51144 includes `sdn-sw.newy32aoa.net.internet2.edu:eth7/2:1715` and `sdn-sw.star.net.internet2.edu:eth7/1:3076` |
| | 31 | |
| | 32 | NOTE: Steps 3, 4 and 5 provide information to determine the topology for the slice. Following is a diagram of the details reported from step 3, 4 and 5: |
| | 33 | [[Image(Triangle-details.jpg,60%)]] |
| | 34 | |
| | 35 | 6. Assuming we are interested in the bandwidth usage for the NYSERNet connections (sdn-sw.newy32aoa.net.internet2.edu), you can see from the previous step that there are two VLANs associated with the site (1714 and 1715). |
| | 36 | |
| | 37 | 7. Select '''Dashborad->VLANs''', this will show the full list of VLAN in use in GENI. In the resulting VLAN listing type the VLAN ID `1715` in the panel search to narrow the results to you sliver: |
| | 38 | [[Image(nysernet-1715.jpg)]] |
| | 39 | |
| | 40 | 8. Select the ID `instageni.nysernet.org_interface_pc3:eth1:1715` to see usage statistics: |
| | 41 | [[Image(nysernet-1715-usage.jpg, 80%)]] |
