Changes between Version 44 and Version 45 of GENIMonitoring/HowTo

Timestamp:

04/08/15 13:44:47 (9 years ago)

Author:

hdempsey@bbn.com

Comment:

minor cleanups

GENIMonitoring/HowTo

@@ -20 +20 @@
  ![6] Enter a term to search for in all monitoring data, regardless of display area.[[BR]]
 
-== Monitoring Data by User Type ==
+== Monitoring Data by User Account Type ==
 
 The data available to you is based on the user type associated with your account.  The following user types are available:
 
  - Admin - User has all administrative functions and can see all data 
- - Operator - Has privileges over monitoring data, but no administrative access.
- - Experimenter - User can only see their own data, and has no access to other user data.
+ - Operator - User can access all monitoring data, but has not adminstrative access.
+ - Experimenter - User can access all data except for user email data.  No adminstrative access.
 
 Following is a table that highlight which function are available by user type:
@@ -49 +49 @@
 == Finding an Experimenter Slice ==
 
-To find a slices simply select the ''' ''Dashboard->Slices'' ''' icon or from the "Main Navigation" choose ''' ''GENI Objects->Slices'' '''.  Both result in the "Main Panel" listing all active slices, you may further narrow down your search by typing the project or slice name in the search box at the top right hand corner of the main panel.
+To find a slices, simply select the ''' ''Dashboard->Slices'' ''' icon or from the "Main Navigation" area, or choose ''' ''GENI Objects->Slices'' '''.  Both result in the "Main Panel" listing all active slices. You may further narrow down your search by typing the project or slice name in the search box at the top right hand corner of the main panel.
 
 == Traffic Statistics ==
 
-If you are interested in traffic statistic for you slice there are two ways to get to statistics for your experiment: you can start with the Slice or start with a VLAN.
+If you are interested in traffic statistics for you slice, there are two ways to get to statistics for your experiment: you can start with the Slice or start with a VLAN.
 
 === Starting with Slice ===
 
-Select "Slices" and find your slice. Once your slice is select you can see the "Information" window which looks as follows:
+Select "Slices" and find your slice. Once your slice is select you can see the "Information" window which looks like this screen capture:
 
 [[Image(slice-info.jpg, 60%)]]
@@ -67 +67 @@
  - "Slivers" - Show the list of slice slivers being monitored for the slice.
 
-To get traffic statistics select the "Slivers" tab and click on the Sliver ID:
+To get traffic statistics, select the "Slivers" tab and click on the Sliver ID:
 
 [[Image(sliver-tab.jpg,60%)]]
 
-This will results in a list of links associates with the sliver. Select a link to see the associated (interface:VLAN) endpoints.  Here are example endpoints:
+This will result in a list of links associates with the sliver. Select a link to see the associated (interface:VLAN) endpoints.  Here are example endpoints:
 
 [[Image(endpoints.jpg,80%)]]
 
-Once of your slice end-points is the AL2S Router (sd-sn.losa.net.internet.edu) and its interface  eth5/1 has a VLAN 1565.  Selecting the Endpoint ID will results in statistics being shown:
+One of the slice endpoints shown above is the AL2S Router (sd-sn.losa.net.internet.edu), and its eth5/1 interface is configured for VLAN 1565.  Selecting the Endpoint ID will result in statistics being shown:
 
 [[Image(report-stats.jpg,80%)]]
@@ -89 +89 @@
 Note: Information returned at this time does not combine the view of the AL2S Network Aggregate and the Compute Resource aggregates.
 
-If we select the sd-sn.losa.net.internet.edu:eth5/1:1565 we will see same information found in the previous sections which started with the slice name.
+If we select the sd-sn.losa.net.internet.edu:eth5/1:1565 entry, we will see same information found in the previous section that started with the slice name.
 
 == GENI External Checks ==
 
-The [http://genimon.uky.edu/ GENI Monitoring] integrates status information collected from checker applications running in other locations. Once example is the '' ''' GENI Objects->Checks''' ''.  This checker runs at the GPO and is intended to eventually capture Campus Status for OpenFlow connections between all GENI sites.  This is being worked on and the current check is run from the University of Washington IG to several remotes. Here is the list of OpenFlow Campus Checks for AL2S sites:
+The [http://genimon.uky.edu/ GENI Monitoring] site also integrates status information collected from checker applications running in other locations. Once example is the '' ''' GENI Objects->Checks''' ''.  This checker runs at the GPO and is intended to eventually capture Campus Status for OpenFlow connections between all GENI sites.  The current check, which is still being improved, checks OpenFlow dataplane availability from the University of Washington InstaGENI rack to several remote sites.  This is the current list of OpenFlow Campus Checks for AL2S sites:
 
 [[Image(checks.jpg,70%)]]