Changes between Version 27 and Version 28 of ConnectivityGuidelines


Ignore:
Timestamp:
04/14/11 14:39:39 (13 years ago)
Author:
jwilliams@bbn.com
Comment:

fixed ION link and Two Campuses' VLAN service Link

Legend:

Unmodified
Added
Removed
Modified

  • ConnectivityGuidelines

    v27 v28  
    5555
    5656== Two campuses - One Regional ==
    57 Sometimes campuses share the same regional provider. It's possible that the regional can provide a direct layer 2 connection between your campus's regional endpoint and your partner campus's regional endpoint.  Your campus, your partner campus, and your shared regional provider can then provision a VLAN as outlined above. You'll need to discuss with your regional whether your campus and your partner campus need to negotiate the same VLAN ID or if the regional offers any [# VLANIDConflicts VLAN services].
     57Sometimes campuses share the same regional provider. It's possible that the regional can provide a direct layer 2 connection between your campus's regional endpoint and your partner campus's regional endpoint.  Your campus, your partner campus, and your shared regional provider can then provision a VLAN as outlined above. You'll need to discuss with your regional whether your campus and your partner campus need to negotiate the same VLAN ID or if the regional offers any [#VLANIDConflicts VLAN services].
    5858
    5959== Testing ==
    … …  
    9797
    9898
    99 == VLAN ID conflicts ==
     99== VLAN ID Conflicts ==
    100100Given 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.
    101101
    … …  
    109109 
    110110=== VLAN Translation ===
    111 VLAN translation translates one VLAN ID to another allowing two separate VLAN ID's to coexist as if it was one VLAN topology.   For example, [wiki:siteInternet2#ION ION] provides VLAN translation. This allows your campus to provision a VLAN ID through your campus and regional network to your ION endpoint without concern for your partner campus's VLAN provisioning. Your partner campus does the same. Once both campuses can reach their ION endpoints, the ION connection can be provisioned to translate your campus's and your partner campus's VLAN ID.
     111VLAN translation translates one VLAN ID to another allowing two separate VLAN ID's to coexist as if it was one VLAN topology.   For example, [wiki:SiteInternet2 Internet2's ION service] provides VLAN translation. This allows your campus to provision a VLAN ID through your campus and regional network to your ION endpoint without concern for your partner campus's VLAN provisioning. Your partner campus does the same. Once both campuses can reach their ION endpoints, the ION connection can be provisioned to translate your campus's and your partner campus's VLAN ID.
    112112
    113113''Your Campus and your partner campus would likely be using different VLAN IDs in this scenario.''