Changes between Version 2 and Version 3 of ConnectivityGuidelines


Ignore:
Timestamp:
06/22/10 16:57:57 (9 years ago)
Author:
jwilliams@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ConnectivityGuidelines

    v2 v3  
    22[[PageOutline]]
    33= Summary =
    4 In order for two sites to communicate they need some help from every service provider along the network path between the sites. The service providers involved may include: campus IT, regional providers, national research backbones.
    54
    6 Decide which methods your campus can use to connect with other campuses.  View what various Campuses have to offer (FIXME - campus index) here.  While your establishing connectivity for your campus if you regard the info on your campuses page then other campuses can also see what you are available.
     5This wiki outlines the steps required to aquire various types of connections between two campuses. before following these guidelines it's recommended review ConnectivityOverview for a high-level view of connectivity approaches. See ConnectivityOptions for a matrix of potential options that various campuses support.
    76
    8 See CampusConnectivityOverview for more information on various options. See GeniConnectivity for a matrix of potential options that various campuses support. This will involve determining what types of support you Once you know which connection method you'd like to use
     7= Overview =
    98
    109Every campus's situation is unique. This is a general common case guideline. Your campus's particular paths and goals may deviate from this outline.
    1110
    12 Note that it's assumed that all of this VLAN provisioning is discussing 801.q tagged (aka trunked) VLANs. This is typically the case.
     11In order for two sites to establish a connection they need some help from every service provider along the network path between the sites. The service providers involved may include: campus IT, regional providers, national research backbones.
    1312
    14 = Layer 2 connections =
     13First, you must decide which method(s) your campus can use to connect with other campuses.  See ConnectivityOptions for a matrix of which options are supported by  which [wiki:SiteIndex campuses].  While your establishing connectivity you should also update your info on your campus's site page. this will allow for other campuses to find the necessary information to connect with you in the future.
     14
     15
     16Note that it's assumed that all of this VLAN provisioning is discussing 801.q tagged (aka trunked) VLANs.
     17
     18= Layer 2 Connections =
    1519==  Backbone Options ==
    16 This is a high-level summary page, see the corresponding Backbone page for more information.
    17 If you and your partner campus have accessibility to the same backbone network you have several choices.
     20This is a high-level summary page, see the corresponding Backbone's GENI wiki page for more information including LInks to webpages, instructions for creating accounts and provisioning VLANs.
     21
     22 * [SiteNlr National Lambda Rail]
     23 * [SiteIon Internet 2]
    1824
    1925This section lays out the general procedure for establishing an end-to-end connection over a backbone network.
    2026
    21 == Backbones ==
    22 NLR-LINK FIXME
    23 I2-LINK. FIXME
    24 
    25 == Once per backbone ==
     27== Once Per Backbone ==
    2628
    2729 1. Join the Backbone service (contracts, negotiations, bartering, etc).
    2830
    29  If this is your campus's first time connecting to a backbone you'll need to establish a relationship with your backbone and establish a backbone endpoint.  There may already be arrangements for your Regional Provider to share/provide access to a Backbone.
     31If this is your campus's first time connecting to a backbone you'll need to establish a relationship with your backbone and establish a backbone endpoint.  There may already be arrangements for your Regional Provider to share/provide access to a backbone's endpoint.
    3032
    3133 2. Obtain an account for provisioning connections in the backbone network. Strictly speaking this isn't always necessary if your partner campus has access - they can provision the VLAN.
     
    33353. Determine the name of your endpoint.
    3436
    35 == Once per campus ==
    36 You may be required to grant permissions to your partner campus to connect to your backbone endpoint This is the case For NLR (FIXME - link to NLR)
     37== Once Per Campus ==
     38You may be required to grant permissions to your partner campus to connect to your backbone endpoint This is the case For [wiki:SiteNlr NLR]
    3739
    38 == Once per path ==
    39 These section outlines the steps necessary for your campus to get connectivity to your backbone endpoint. Your partner campus will also need to do these steps, though they may have established extra connections that are available. Note that you'll need a unique VLAN per unique connection you want to establish. If you wish to connect to multiple campuses, you'll need to provision multiple VLANs. 
     40== Once per Connection ==
     41These section outlines the steps necessary for your campus to get connectivity to your backbone endpoint. Your partner campus will also need to do these steps, though they may allocated extra paths at a previous point. Note that you'll need a unique VLAN per unique connection that you want to establish. If you wish to connect to multiple campuses, you'll need to provision multiple VLANs. 
    4042
    41 === Regional provisioning ===
    42  Your campus will need to request your regional to provision quest VLANs from your retie reach from your campus's site endpoint (FIX NAME). If you plan on connecting to multiple campuses, or have multiple unique connections to a campus,  you may want to request multiple VLANs.
     43=== Regional Provisioning ===
     44Your campus will need to request your regional provider to provision the VLAN from your from your campus's site edge to your bacnbone endpoint. If you plan on connecting to multiple campuses, or have multiple unique connections to a campus,  you may want to request multiple VLANs at this time.
    4345
    44 === your campus ===
    45 Now that you know which VLAN(s) are available in the regional network to reach your campus's backbone endpoint,  you'll need to provision the same VLAN IDs from your campus's regional endpoint to the particular network gear that you wish to share.
     46=== Campus Provisioning ===
     47Now that you know which VLAN(s) are available in the regional network to reach your campus's backbone endpoint,  You'll need to provision the same VLAN IDs from your campus's site edge to the particular network gear that you wish to share.
    4648
    47 Your partner campus will need to provision VLAN(s) to their endpoint as well.
     49Your partner campus will need to provision VLAN(s) to their campus's edge as well.
    4850
    49 === backbone ===
    50 Now that both your campus and your partner campus have VLANs provisioned to your corresponding endpoints, you can, finally, provision the VLAN in the backbone to connect the endpoints into one network. You, or your partner campus, can perform this action via the backbone's web provisoning service.
    51 
     51=== Backbone Provisioning ===
     52Now that both your campus and your partner campus have VLANs provisioned to your corresponding endpoints, you can, finally, provision the VLAN in the backbone to connect the endpoints into one network. You, or your partner campus, can perform this action via the backbone's web provisioning service.
    5253
    5354== Notes and Gotchas ==
    54  * NLR's web provisioning service (Sherpa) does provide VLAN translation; your campus, your partner campus, and all regionals will need to provision ''the same VLAN ID'' to establish a connection. NLR may be able to provide translation on a case-by-case basis. If this is required you will need to connect NLR directly. (FIXME - add link to VLAN translation)
     55 * NLR's web provisioning service (Sherpa), by default, does provide VLAN translation; your campus, your partner campus, and all regional networks will need to provision ''the same VLAN ID'' to establish a connection.
    5556
    56 == Simular regional ==
    57 Sometimes campuses share the same regional. 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.  You campus and your regional campus can then provision a VLAN within the campus and regional network as outlined above. IN FIXME. You'll need to discuss with your regional whether your campus and your partner campus need to negotiate the same VLAN ID.
     57== Two campuses - One Regional ==
     58Sometimes 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.  You campus and your regional campus can then provision a VLAN within the campus and regional network 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 can support VLAN translation.
    5859
    5960== Testing ==
    6061Typically both campuses will assign IP addresses to various hosts to allow common IP-based programs to quickly verify Layer-2 connectivity.
    6162 
    62 You'll talk with you partner campus to decide on a IP subnet that can be used on both campuses. You'll then want to provide you're partner campus.
     63You'll talk with you partner campus to decide on a IP subnet that can be used on both campuses. You'll then want to share a list of IP addresses, as well as MAC addresses, that each campus will use.
    6364
    64 ''''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.
     65''''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.
    6566
    6667== VLAN ID conflicts ==
    67 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.
     68Given 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.
    6869
    6970=== QinQ ===
    7071
    71 QinQ is a tunneling option which "wraps" your frames from marked with your VLAN ID within another VLAN ID. For example, your can provision VLAN 1234 within NLR and your network, but your regional is already using this VLAN iD. YOur regional can assign you another VLAN ID say 2345, for this connection and tunnel VLAN ID 1234 through this connection so that you can Reach NLR with your VLAN iD intact.
     72QinQ is a tunneling option which "wraps" your frames (marked with your VLAN ID) within another VLAN ID that is available within the regional network. For example, your can provision VLAN 1234 within NLR and your network, but your regional is already using this VLAN ID. Your regional can assign you another VLAN ID say 2345, for this connection and tunnel VLAN ID 1234 through this connection so that you can Reach NLR with your VLAN iD intact. Depending on the situation, your reginonal may do this transparently or your campus may need to be involved.
    7273 
    73 === VLAN translation ===
    74  VLAN translation translates one VLAN ID to another allowing two separate VLAN ID's to coexist as if it was one VLAN topology. Internet2's ION interface allows for translation. This means that your campus only needs to provision a VLAN ID trough your campus and regional network to your ION endpoint. Your partner campus does the same without the requirement to use the same VLAN ID as your campus. once both campuses can reach there ION endpoints ION will translate your campus VLAN ID to your partner campuses ID, and vice versa, to establish the connection.
    75 
    76 = Layer 3 connections =
    77 
    78 If your campus doesn't have layer 2 connectivity (no backbones, must go through a router, etc) then layer 3 connectivity may be an option. For GENI experiments this requires tunnel
     74=== VLAN Translation ===
     75 VLAN translation translates one VLAN ID to another allowing two separate VLAN ID's to coexist as if it was one VLAN topology.   This means that your campus only needs to provision a VLAN ID trough your campus and regional network to your ION endpoint. Your partner campus does the same without the requirement to use the same VLAN ID as your campus. once both campuses can reach there ION endpoints ION will translate your campus VLAN ID to your partner campuses ID, and vice versa, to establish the connection.
     76 
     77 VLAN translation option's::
     78   * For [wiki:Site:ION#VLANTranslation ION]
     79   * For [wiki:SiteNlr#VLANTranslation NLR]
    7980
    8081
    81 == connections ==
     82= Layer 3 Connections =
     83
     84If your campus doesn't have layer 2 connectivity (no backbones, must go through a router, etc) then layer 3 connectivity may be an option. For GENI experiments this requires tunneling.
     85
     86== Connections ==
    8287 backbone::
    83    Your campus may have access to a backbone Layer3 connection such as !PackeNet.
     88   Your campus may have access to a backbone Layer 3 connection such as NLR's !PackeNet.
    8489
    8590 commodity internet::
    86   You use the normal "commodity" internet path's through your ISP(s).
     91   You use the normal "commodity" internet path's through your ISP(s).
    8792
    88 == tunneling options ==
    89  GRE::
    90    FIXME describe GRE here.
     93== Tunneling Options ==
     94 Generic Route Encapsulation (GRE)::
     95   http://en.wikipedia.org/wiki/Generic_Routing_Encapsulation
    9196 Software Encapsulation::
    92    FIXME mention Capsulator.
    93  MPLS::
    94    FIXME describe MPLS Here
     97   There are several software solutions available. OpenFlow uses the Encapsulator package available at
     98 Mutli=Path Label Switching (MPLS)::
     99   http://en.wikipedia.org/wiki/MPLS
    95100
    96101{{{
     
    103108{{{
    104109#!html
    105 <a href="mailto:help@geni.net?subject=[GENI site] ConnectivityGuidelines question">Email us</a> with questions and feedback on this page!
     110<a href="mailto:jwilliams@geni.net?subject=[GENI site] ConnectivityGuidelines question">Email us</a> with questions and feedback on this page!
    106111}}}
    107112