| | 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. |
| | 3 | |
| | 4 | == Overview == |
| | 5 | This is the strategy regarding this department: |
| | 6 | |
| | 7 | 1. Set up static VLANs based on ORBIT network infrastructure convention. |
| | 8 | |
| | 9 | |
| | 10 | == Preliminary port VLAN assignment based on ORBIT Network Infrastructure == |
| | 11 | 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 | |
| | 13 | On the NEC switch, 3 VLANS and a trunk are assigned in the following manner: |
| | 14 | |
| | 15 | * port 1-4 : CM (VLAN 3) |
| | 16 | * port 5-8 : Control (VLAN 27) |
| | 17 | * port 9-12 : Data (VLAN 28) |
| | 18 | * port 55-58 : trunk |
| | 19 | |
| | 20 | 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. |
| | 21 | |
| | 22 | == Setup == |
| | 23 | 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. |
| | 24 | |
