Changes between Version 21 and Version 22 of ConnectivityGuidelines

Timestamp:

07/07/10 17:55:02 (14 years ago)

Author:

jwilliams@bbn.com

Comment:

added hints about using various routerproxy URLs

ConnectivityGuidelines

@@ -72 +72 @@
   * Check to see if your edge switch see's your partner sites MAC address in the appropriate VLAN. 
 
-If this is not as expected escalate to your regional networks to see how far each MAC is getting. Finally, you can do escalate to the the backbone.
+ If you used a backbone network you can use a service to inspect whether various back bone switches are seeing the MAC address in question.
 
-Sometimes regional will attach a node for you to ping to confirm that you can reach a particular point in their Network. Also, sometimes there are spanning tree issues.
+ NLR::
+   httpe://routerproxy.grnoc.iu.edu/nlr/
+   1. Select FrameNet Core Switch that you want to inspect (start with your endpoint).
+   2. select the `show mac-address-table` and specify the vlan you wish to inspect (e.g. type "vlan 3705" in the text box).
+   3. run the command, and look for your mac address.
+Internet2::
+   http://routerproxy.grnoc.iu.edu/internet2/
+ Note that currently this service doesn't offer Layer 32 debugging facilities.
+
+ 1. Select the switch that you want to inspect.
+ 2 run the various command. 
+
+If your MAC is shown in your endpoint switch, but not on your partner's endpoint switch, then the issue may be within the backbone.  
+
+I the MAC is not making it to the campus endpoint, it may be a regional network issue. sometimes regionals will attach a node with an IP address for you to ping to confirm that you can reach a particular point in their Network. 
+
+Note, sometimes there are spanning tree issues.
+