Changes between Version 9 and Version 10 of ConnectivityGuidelines
- Timestamp:
- 06/24/10 11:34:52 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ConnectivityGuidelines
v9 v10 3 3 4 4 = Summary = 5 This 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 viewof connectivity approaches. See ConnectivityOptions for a matrix of potential options that various campuses support.5 This wiki outlines the steps required to aquire various types of connections between two campuses. before following these guidelines it's recommended to review ConnectivityOverview for a high-level summary of connectivity approaches. See ConnectivityOptions for a matrix of potential options that various campuses support. 6 6 7 7 = Overview = 8 Every campus's situation is unique. This is a general commoncase guideline. Your campus's particular paths and goals may deviate from this outline.8 Every campus's situation is unique. This page is a general common-case guideline. Your campus's particular paths and goals may deviate from this outline. 9 9 10 10 In 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. 11 11 12 First, 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.12 First, 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. 13 13 14 14 Note that it's assumed that all of this VLAN provisioning is discussing 801.q tagged (aka trunked) VLANs. … … 16 16 = Layer 2 Connections = 17 17 == Backbone Options == 18 This is a high-level summary page, see the corresponding Backbone's GENI wiki page for more information including L Inks to webpages, instructions for creating accounts and provisioning VLANs.18 This 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. 19 19 20 * [ SiteNlr National LambdaRail]20 * [wiki:SiteNlr National LambdaRail] 21 21 * [wiki:SiteInternet2 Internet 2] 22 22 … … 25 25 == Once Per Backbone == 26 26 27 1. Join the Backbone service (contracts, negotiations, bartering, etc).27 1. Join the backbone service (contracts, negotiations, bartering, etc). 28 28 29 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's endpoint. … … 31 31 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. 32 32 33 3. Determine the name of yourendpoint.33 3. Determine the name of your backbone endpoint. 34 34 35 35 == Once Per Campus == … … 37 37 38 38 == Once per Connection == 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 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. 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 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. You may also wish to discuss [#Testing IP address assignments for testing] at this time. 40 40 41 41 === Regional Provisioning === 42 Your 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.42 Your campus will need to request your regional provider to provision the VLAN from your campus's site edge to your backbone 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. 43 43 44 44 === Campus Provisioning === … … 51 51 52 52 == Notes and Gotchas == 53 * NLR's web provisioning service (Sherpa), by default, doesprovide VLAN translation; your campus, your partner campus, and all regional networks will need to provision ''the same VLAN ID'' to establish a connection.53 * [SiteNlr NLR]'s web provisioning service ([SiteNlr#SherpaAccount Sherpa]), by default, does ''not'' provide VLAN translation; your campus, your partner campus, and all regional networks will need to provision ''the same VLAN ID'' to establish a connection. 54 54 55 55 == Two campuses - One Regional == 56 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. 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.56 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]. 57 57 58 58 == Testing == 59 59 Typically both campuses will assign IP addresses to various hosts to allow common IP-based programs to quickly verify Layer-2 connectivity. 60 60 61 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 share a list of IP addresses, as well as MAC addresses, that each campus will use.61 You'll talk with your 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. 62 62 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.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. 64 64 65 65 == VLAN ID conflicts == 66 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. 66 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. 67 68 === Renegotiate === 69 Quite often there's another range of VLANs that are available hich may work within your network. VLAN negotiations are typically an iterative process. 67 70 68 71 === QinQ === 69 QinQ 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. 72 QinQ 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, you provisioned VLAN 1234 within [SiteNlr 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 [SiteNlr NLR] with your VLAN ID intact. Depending on the situation, your regional may do this transparently or your campus may need to be involved. 73 74 ''Your campus and your partner campus would likely be using the same VLAN ID in this scenario''. 70 75 71 76 === VLAN Translation === 72 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 campus's VLAN ID, and vice versa, to establish the connection. 77 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 provisiong. 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. 78 79 ''Your Campus and your partner campus would likely be using different VLAN IDs in this scenario.'' 73 80 74 '''VLAN Translation Options '''::81 '''VLAN Translation Options in Backbone Networks''':: 75 82 * For [wiki:SiteInternet2#VLANTranslation Internet 2] 76 83 * For [wiki:SiteNlr#VLANTranslation NLR] … … 78 85 79 86 = Layer 3 Connections = 80 81 87 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 tunneling. 82 88 83 89 == Connections == 84 90 '''Backbone''':: 85 Your campus may have access to a backbone Layer 3 connection such as NLR's !PackeNet.91 Your campus may have access to a backbone Layer 3 connection such as [SiteNlr#PacketNet NLR's !PackeNet]. 86 92 87 93 '''Commodity Internet''':: … … 92 98 http://en.wikipedia.org/wiki/Generic_Routing_Encapsulation 93 99 Software Encapsulation:: 94 There are several software solutions available. OpenFlow Switches can usesthe Encapsulator package available at http://www.openflowswitch.org/wk/index.php/Capsulator100 There are several software solutions available. OpenFlow switches can use the Encapsulator package available at http://www.openflowswitch.org/wk/index.php/Capsulator 95 101 96 102 Mutli-Path Label Switching (MPLS)::
