Changes between Version 4 and Version 5 of NetworkCore
- Timestamp:
- 01/17/11 09:09:16 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetworkCore
v4 v5 5 5 There are currently two standing VLANs (3715 and 3716) carried on the ten switches in the core, which are located in the nine cities shown on the maps below. Each VLAN in each provider is topologically a broken ring (to help prevent accidental loops), with the two rings in each VLAN linked in Atlanta. The gap in each VLAN is between two different links, to provide either a longer or shorter path through the core between two switches. The two VLANs are not interconnected in the core, and should not be interconnected in regionals or at GENI sites either. Sites may connect to both VLANs as long as the site keeps them separated at layer 2. 6 6 7 = = VLAN 3715 ==7 = VLAN 3715 = 8 8 9 9 [[Image(geni-core-vlan-3715.png)]] 10 10 11 = = VLAN 3716 ==11 = VLAN 3716 = 12 12 13 13 [[Image(geni-core-vlan-3716.png)]] 14 15 = Testing / monitoring = 16 17 We're in the process of setting up a process for testing the OpenFlow core from end to end, including out to campuses. Between the two VLANs, each with two end points and on two providers, we have a total of eight endpoints, which we intend to connect to these campuses: 18 19 || 3715 NEWY I2 || Rutgers || 20 || 3715 LOSA I2 || BBN || 21 || 3716 LOSA I2 || BBN || 22 || 3716 HOUS I2 || BBN || 23 || 3715 SEAT NLR || Washington || 24 || 3715 SUNN NLR || Stanford || 25 || 3716 CHIC NLR || Indiana || 26 || 3716 DENV NLR || BBN || 27 28 We don't have an OpenFlow campus naturally close to Denver, Houston, or Los Angeles, so we're planning to use VLAN translation to link hosts in the GPO lab at BBN to each of those endpoints.