Changes between Version 10 and Version 11 of ConnectivityGuidelines


Ignore:
Timestamp:
06/24/10 16:35:41 (9 years ago)
Author:
jwilliams@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ConnectivityGuidelines

    v10 v11  
    1 '''This page is a pre-draft. The content here will change significantly'''
     1'''NOTE:  This information is subject to change, but is actively maintained.  Please email us (see footer) with updates and corrections.'''
    22[[PageOutline]]
    33
     
    6363'''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.
    6464
     65 * `ping` your partner site's IP address.
     66 * `traceroute` your partner site's IP address.
     67 * `arp` your partner site's IP Address. this will display your partner's MAC address.
     68
     69=== When Things Go Wrong ===
     70Talk to your partner campus. Each Site should:
     71  * Check to see if your edge switch see's your MAC address in the appropriate VLAN.
     72  * Check to see if your edge switch see's your partner sites MAC address in the appropriate VLAN.
     73
     74If 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.
     75
     76Sometimes 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.
     77
     78
    6579== VLAN ID conflicts ==
    6680Given 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.