Changes between Version 10 and Version 11 of ConnectivityGuidelines

Timestamp:

06/24/10 16:35:41 (14 years ago)

Author:

jwilliams@bbn.com

Comment:

--

ConnectivityGuidelines

@@ -1 @@
-'''This page is a pre-draft. The content here will change significantly'''
+'''NOTE:  This information is subject to change, but is actively maintained.  Please email us (see footer) with updates and corrections.'''
 [[PageOutline]]
 
@@ -63 +63 @@
 '''TIP''' If you're the first person to start IP negotiations specify what IP address you want to use. Such as "I plan on using 10.37.45.12 -  what do you plan on using". This may help prevent the case where both campuses use the same IP address.
 
+ * `ping` your partner site's IP address.
+ * `traceroute` your partner site's IP address.
+ * `arp` your partner site's IP Address. this will display your partner's MAC address.
+
+=== When Things Go Wrong ===
+Talk to your partner campus. Each Site should:
+  * Check to see if your edge switch see's your MAC address in the appropriate VLAN. 
+  * 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.
+
+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.
+
+
 == VLAN ID conflicts ==
 Given the limited number of VLAN IDs, it's conceivable to run into a conflict when provisioning a common VLAN between two end points. Here are a few common options to resolve the conflict.