Advanced Network Training VERDE VDI Advanced Network Training

Agenda Switching Link Aggregation Control Protocol (LACP) VLAN Access Mode Trunk Mode Link Aggregation Control Protocol (LACP) “Bonded VLAN” Switch Implementation LACP Ubuntu 12.04 HOST example: bond + vlan + bridge IP Addressing Details: Cisco Training CCNA IP Addressing - Part 1 of 5 http://www.youtube.com/watch?v=UXN5XrmsaV8

Switching VLAN Access Mode Trunk Mode (802.1q) A virtual network that creates a distinct broadcast domain. Defined using a managed switch or router. Access Mode Switch port that is statically assigned to a VLAN. Port behaves like a consumer-grade switch with no capability of establishing trunks. Trunk Mode (802.1q) http://www.youtube.com/watch?v=Wi48h6UFhlo Switch port that is assigned to multiple VLAN’s. Requires a managed switch with 802.1q support as well as a either a compute node running an OS with 802.1q support or another switch with 802.1q support. Packets are tagged with corresponding VLAN network for routing in managed switch. VLAN tags are stripped from packet header when they arrive to the destination VLAN. There are proprietary tagging protocols provided by vendors such as Cisco. VERDE only supports 802.1q. Used on a VERDE server to bridge to multiple VLAN’s without requiring dedicated access mode interfaces per VLAN.

Link Aggregation Control Protocol (LACP) A method to combine multiple network connections in parallel to increase throughput, and to provide redundancy in case one of the links fails. Defined by 802.3ad/802.1ax. Requires a managed switch with LACP support as well as a compute node running an OS with LACP support or another switch with LACP support. Individual ports (called member ports) are placed into an LACP group on the switch. A host is connected to the member ports of the LACP group and operate as a single logical interface. Packets bound for target LACP interface flow through all member interfaces increasing throughput. The health of member interfaces is monitored by LACP protocol. Unhealthy member interfaces will be shutdown automatically. Also known as “bonded interfaces”, “teamed NICs”, “bond mode 4”, etc. bond mode 2 does not aggregate interfaces for throughput. It is simply a mechanism for redundancy.

“Bonded VLAN” VLAN support and LACP are completely independent concepts! For example: You can have a single interface connected to a VLAN enabled port. You can configure an LACP group (eg: bond) in access mode. A “Bonded VLAN” is simply a combination of the two concepts meaning an LACP group (eg: bond) that is configured in trunk mode to access multiple VLAN’s

Switch Implementation – VLAN Definition (1/3) VLAN database with VLAN tags and routing definitions

Switch Implementation – VLAN Definition (2/3) VLAN interface definitions

Switch Implementation – VLAN Definition (3/3) VLAN interface definitions (note VLAN 192 is not routed)

Switch Implementation – Access Mode Port Port 1/g16 is configured in access mode to vlan 192 (along with jumbo frames and spanning tree) Ports 1/g17 – 1/g18 are configured in access mode to vlan 200

Switch Implementation – Trunk Mode Port Port 1/g29 is configured in trunk mode (called “general” in Dell speak) to VLAN 60, 100

Switch Implementation – LACP (1/2) Ports 1/g33 – 1/g34 are configured as member interfaces to LACP group 8 (called “channel-group” in Dell speak)

Switch Implementation – LACP (2/2) port-channel 8 forms an LACP group that is trunked to vlan 150, 192, 200, 250. The LACP group could also be configured in access mode.

Only using vlan 70 in this example Ubuntu 12.04 Example Two ports on our L3 switch configured in trunk mode (“general” in Dellspeak) to vlan 70 and100 Only using vlan 70 in this example All Ubuntu network configuration is done in /etc/network/interfaces. The following additional packages must be installed for this configuration apt-get install bridge-utils ifenslave vlan

Example /etc/network/interfaces (1/2) # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # Activate network interfaces eth0 and eth1 # Identify bond master as bond0 (arbitrary name) auto eth0 iface eth0 inet manual bond-master bond0 bond-primary eth0 auto eth1 iface eth1 inet manual # Activate the bond interface auto bond0 iface bond0 inet manual bond-slaves none bond-mode active-backup bond-miimon 100

Example /etc/network/interfaces (2/2) # Add VLAN 70 to our bond, default naming is <interface>.<vlan tag> # Alternately may be arbitrary name ex. "vlan70" with explicit vlan-raw-device <interface> auto bond0.70 iface bond0.70 inet manual # optional explicit interface reference vlan-raw-device bond0 # Create a bridge and assign public IP address auto bridge.bond0.70 iface bridge.bond0.70 inet static address 172.16.70.3 netmask 255.255.255.0 gateway 172.16.70.1 bridge_ports bond0.70 bridge_maxwait 0 bridge_fd 1 bridge_stp off