Changes between Version 3 and Version 4 of Internal/OpenFlow/SandBoxSetup
- Timestamp:
- Jun 27, 2009, 5:34:22 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/SandBoxSetup
v3 v4 1 1 = Building Sandbox 9 = 2 This page describes any important-like things that happen in setting up the Sandbox 9. Eventually, !OpenFlow will be used with SB9. 2 3 This page describes any important-like things that happen in setting up the Sandbox 9. Sandbox 9 will first be networked using legacy switching and static VLANs. Once the controller is deployed, virtual switches will be used. 3 4 4 5 == Overview == … … 9 10 10 11 11 = = Preliminary setup based on ORBIT Network Infrastructure ==12 As of now (6/26/09), we still have not began work on a controller. Without the controller, the virtual switches are nonfunctional, so we first begin by trying to build Sandbox 9 using static VLANs and legacy firmware. 12 = Preliminary setup based on ORBIT Network Infrastructure = 13 As of now (6/26/09), we still have not began work on a controller. Without the controller, the virtual switches are nonfunctional, so we first begin by trying to build Sandbox 9 using static VLANs and legacy firmware. 13 14 14 On the NEC switch, 3 VLANS and a trunk are assigned in the following manner: 15 == Conventions used == 16 3 types of VLANs are used on the ORBIT testbed: CM, Control, and Data. While the CM VLAN spans across all 10 testbeds (Grid + 9 Sandboxes), each testbed has its own Control and Data VLANs. 15 17 16 * port 1-4 : CM (VLAN 3) 17 * port 5-8 : Control (VLAN 27) 18 * port 9-12 : Data (VLAN 28) 19 * port 55-58 : trunk 18 On the NEC switch, the 3 VLANS and a trunk are assigned in the following manner, according to conventions used for networking the Sandboxes: 20 19 21 == DHCP Relay Agents == 22 No IP relay agents are needed for DHCP because these are only required when the dhcp server lives on one vlan, and hosts on another vlan need its service. In the case of this switch, dhcp comes from beyond the firewall, and comes in from the trunk. 20 ||Usage||Ports||VLAN ID|| 21 ||CM||1-4||3|| 22 ||Control||5-8||27|| 23 ||Data||9-12||28|| 24 ||Trunk||55-58||-|| 25 26 == DHCP == 27 DHCP relay agents are only needed when the DHCP server and host are on separate VLANs. You don't need to configure the relay agent since the DHCP server is on the trunk connection and beyond the ASA. The ASA behaves as a router between the VLANs, and handles the relaying and VLAN tags. 23 28 29 24 30 == Static VLAN Configuration == 25 31 The steps assume you are already logged in and in privileged mode on the switch. Configuration of the CM VLAN (VLAN 3) is shown here. … … 32 38 }}} 33 39 34 2. Assign ports to VLAN. Unfortunately, you have to configure one port at a time. Luckily, you can pull back old commands by using the up arrow key.40 2. Assign CM VLAN 3 to the desired ports. Unfortunately, you have to configure one port at a time. Luckily, you can use the up arrow key to go through previous commands to make things faster. 35 41 {{{ 36 42 !(config)# interface gi 0/1 … … 68 74 69 75 == Setup == 70 A host is connected to a Control VLAN port (0/7), and the dhcp comes from trunk port 0/48. It will be able to bind to an address from Control, but not from any other VLAN. 76 A host is connected to a Control VLAN port (0/7), and the dhcp comes from trunk port 0/48. It will be able to bind to an address from Control, but not from any other VLAN. 71 77 78 79 80 81 [wiki:Documentation/OpenFlow/ go back to OpenFlow index]
