Changes between Version 9 and Version 10 of OpenFlow/CampusTopology
- Timestamp:
- 04/06/11 14:11:30 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/CampusTopology
v9 v10 32 32 33 33 9 a host T 1700 1750 3715 3716 34 10+ another host T 1700 1750 3715 3716 34 10 another host T 1700 1750 3715 3716 35 11 another host T 1700 1750 3715 3716 36 12+ more hosts T 1700 1750 3715 3716 35 37 }}} 36 38 … … 38 40 39 41 Each of the following sections refers to this diagram to explain how the various options are implmented. The precise port numbers aren't actually important, they're just selected for ease of explanation here. 42 43 We also have examples of how to configure the interfaces on NEC and HP switches to implement the above topology. 40 44 41 45 = Uplink = … … 70 74 71 75 Ports 9 and 10 (and so on) are the ports that are connected to the dataplane interfaces on hosts (e.g. MyPLC, ProtoGENI, etc). Their key unusual feature is that they're trunk ports, i.e. they carry multiple tagged VLANs; this requires the hosts that you connect to them to speak 802.1q, aka "VLAN-based subinterfacing". Modern Linux distributions, like Ubuntu and Fedora / Red Hat, do this just fine, with interface names like eth1.1700, eth1.3715, etc. Configuring the hosts' dataplane interfaces with 802.1q, and connecting them as trunk ports, is the key ingredient that allows experimenters to control which VLANs their compute slivers actually connect to. We're working on detailed guidelines for how campus resource operators can enable this on their hosts, and how experimenters can take advantage of it. ''(FIXME: Replace the previous sentence with a link to a page with more information.)'' 76 77 = Example configurations = 78 79 The following configuration, on an NEC switch (running the Product firmware), will implement the topology in the diagram above: 80 81 {{{ 82 interface gigabitethernet 0/1 83 switchport mode trunk 84 switchport trunk allowed vlan 3704,3711,3712,3715,3716 85 86 interface gigabitethernet 0/3 87 switchport mode access 88 switchport access vlan 1750 89 90 interface gigabitethernet 0/4 91 switchport mode access 92 switchport access vlan 3715 93 94 interface gigabitethernet 0/5 95 switchport mode access 96 switchport access vlan 1750 97 98 interface gigabitethernet 0/6 99 switchport mode access 100 switchport access vlan 3716 101 102 interface gigabitethernet 0/7 103 switchport mode trunk 104 switchport trunk allowed vlan 1700,3704,3711,3712,3715,3716 105 106 interface gigabitethernet 0/8 107 switchport mode dot1q-tunnel 108 switchport access vlan 1799 109 110 interface gigabitethernet 0/9 111 switchport mode trunk 112 switchport trunk allowed vlan 1700,1750,3715,3716 113 114 interface gigabitethernet 0/10 115 switchport mode trunk 116 switchport trunk allowed vlan 1700,1750,3715,3716 117 118 interface gigabitethernet 0/11 119 switchport mode trunk 120 switchport trunk allowed vlan 1700,1750,3715,3716 121 122 interface gigabitethernet 0/12 123 switchport mode trunk 124 switchport trunk allowed vlan 1700,1750,3715,3716 125 }}} 126 127 128 The following configuration, on an HP switch, will implement the topology in the diagram above: 129 130 {{{ 131 vlan 1700 132 tagged 7,9-12 133 vlan 1750 134 tagged 9-12 135 untagged 3,4 136 vlan 1799 137 tagged 8 138 vlan 3704 139 tagged 1,7 140 vlan 3711 141 tagged 1,7 142 vlan 3712 143 tagged 1,7 144 vlan 3715 145 tagged 1,7,9-12 146 untagged 4 147 vlan 3716 148 tagged 1,7,9-12 149 untagged 6 150 }}}