I haven’t done this on a VXLAN deployment but I did a packet capture on a Grizzly GRE environment to see exactly what it looks like on the wire and the results are below (although the color coding will probably be lost.) What we have with GRE is 802.1q inside the encapsulated payload so if the 4096 limit is a concern then this doesn’t alleviate it.
What I’m not sure of is whether the VLAN ID inside of the GRE payload is globally unique or whether different compute nodes can reuse the same VLAN ID for different Neutron networks. If somebody has a VXLAN environment up and running I would love to see a packet capture similar to the one below (hint, hint :-)) Frame 1: 136 bytes on wire (1088 bits), 136 bytes captured (1088 bits) Ethernet II, Src: e8:9a:8f:23:41:8f (e8:9a:8f:23:41:8f), Dst: e8:9a:8f:23:42:8d (e8:9a:8f:23:42:8d) Internet Protocol Version 4, Src: 192.168.160.13 (192.168.160.13), Dst: 192.168.160.21 (192.168.160.21) Generic Routing Encapsulation (Transparent Ethernet bridging) Ethernet II, Src: fa:16:3e:69:42:0d (fa:16:3e:69:42:0d), Dst: fa:16:3e:0c:bc:fa (fa:16:3e:0c:bc:fa) 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 1 Internet Protocol Version 4, Src: 192.168.20.3 (192.168.20.3), Dst: 12.129.192.149 (12.129.192.149) User Datagram Protocol, Src Port: 123 (123), Dst Port: 123 (123) Network Time Protocol (NTP Version 4, client) Frame 2: 88 bytes on wire (704 bits), 88 bytes captured (704 bits) Ethernet II, Src: e8:9a:8f:23:41:8f (e8:9a:8f:23:41:8f), Dst: e8:9a:8f:23:41:f1 (e8:9a:8f:23:41:f1) Internet Protocol Version 4, Src: 192.168.160.13 (192.168.160.13), Dst: 192.168.160.14 (192.168.160.14) Generic Routing Encapsulation (Transparent Ethernet bridging) Ethernet II, Src: fa:16:3e:35:e3:4f (fa:16:3e:35:e3:4f), Dst: Broadcast (ff:ff:ff:ff:ff:ff) 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 1 Address Resolution Protocol (request) Frame 3: 88 bytes on wire (704 bits), 88 bytes captured (704 bits) Ethernet II, Src: e8:9a:8f:23:41:8f (e8:9a:8f:23:41:8f), Dst: e8:9a:8f:23:42:8d (e8:9a:8f:23:42:8d) Internet Protocol Version 4, Src: 192.168.160.13 (192.168.160.13), Dst: 192.168.160.21 (192.168.160.21) Generic Routing Encapsulation (Transparent Ethernet bridging) Ethernet II, Src: fa:16:3e:35:e3:4f (fa:16:3e:35:e3:4f), Dst: Broadcast (ff:ff:ff:ff:ff:ff) 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 1 Address Resolution Protocol (request) Frame 4: 88 bytes on wire (704 bits), 88 bytes captured (704 bits) Ethernet II, Src: e8:9a:8f:23:42:8d (e8:9a:8f:23:42:8d), Dst: e8:9a:8f:23:41:8f (e8:9a:8f:23:41:8f) Internet Protocol Version 4, Src: 192.168.160.21 (192.168.160.21), Dst: 192.168.160.13 (192.168.160.13) Generic Routing Encapsulation (Transparent Ethernet bridging) Ethernet II, Src: fa:16:3e:b5:19:db (fa:16:3e:b5:19:db), Dst: fa:16:3e:35:e3:4f (fa:16:3e:35:e3:4f) 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 5 Address Resolution Protocol (reply) Frame 5: 388 bytes on wire (3104 bits), 388 bytes captured (3104 bits) Ethernet II, Src: e8:9a:8f:23:41:8f (e8:9a:8f:23:41:8f), Dst: e8:9a:8f:23:42:8d (e8:9a:8f:23:42:8d) Internet Protocol Version 4, Src: 192.168.160.13 (192.168.160.13), Dst: 192.168.160.21 (192.168.160.21) Generic Routing Encapsulation (Transparent Ethernet bridging) Ethernet II, Src: fa:16:3e:35:e3:4f (fa:16:3e:35:e3:4f), Dst: fa:16:3e:b5:19:db (fa:16:3e:b5:19:db) 802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 1 Internet Protocol Version 4, Src: 192.168.20.10 (192.168.20.10), Dst: 192.168.20.2 (192.168.20.2) User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67) Bootstrap Protocol (Request)
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
