Building Ether-channel with failover and load-balancing using HP-NIC Teaming and a Cisco 3750 switch.

[NJB] 18-07-2011
1. THE HP SERVER (NIC-TEAMING) SIDE First Congure Teaming on your source-server. In this example we congure teaming with four adapters and two teams. Using two adapters per team.

On the Teaming Controls set Switch-assisted Load Balancing with Fault Tolerance (SLB)

2. THE CISCO (CATALYST 3750 SWITCH) SIDE In this example we create two port-channels (port-channel 47 and port-channel 48) one for each team. Because we dene just one default vlan per port-channel, trunking is nog necessary. Use spanning-tree portfast (for fast port initialisation) ! interface Port-channel47 description *** Connection to Teaming Server VLAN 10** switchport access vlan 10 switchport trunk encapsulation dot1q switchport mode access spanning-tree portfast ! interface Port-channel48 description *** Connection to Teaming Server VLAN 200*** switchport access vlan 200 switchport trunk encapsulation dot1q switchport mode access spanning-tree portfast ! Congure system wide load-balancing for port channels. ! congure terminal port-channel load-balance src-dst-ip

! Explanation: (source: http://www.rstdigest.com/2010/08/cisco-port-channel-load-balancing-explanation/)

src-dst-ip Loads distribution on the source transfer or XOR-destination IP address. What this method does is to pair source and destination IP address and send all the traffic that match this rule over one physical port in port-channel. The advantage of this method over the above one is granularity. With the above method the traffic to one destination, was sent over one physical port in port-channel without taking into consideration the source. With this method, the packets to the same destination can be forwarded over different interfaces in port-channel if they are coming from different IP source.

Now congure the interfaces on the cisco switch for teaming. IMPORTANT: Congure the channel-group mode using the option (ON) to create a static etherchannel, do not use LACP the load balancing is handled by the teaming software even though you are using switched assisted load-balancing and failover. ! interface GigabitEthernet1/0/10 description *** Connection to Teaming Server NIC 1 *** switchport access vlan 10 switchport trunk encapsulation dot1q switchport mode access speed 1000 duplex full spanning-tree portfast channel-group 47 mode on ! ! interface GigabitEthernet2/0/10 description *** Connection to Teaming Server NIC 2 *** switchport access vlan 10 switchport trunk encapsulation dot1q switchport mode access speed 1000 duplex full spanning-tree portfast channel-group 47 mode on !

! interface GigabitEthernet1/0/11 description *** Connection to Teaming Server NIC 3 *** switchport access vlan 200 switchport trunk encapsulation dot1q switchport mode access speed 1000 duplex full spanning-tree portfast channel-group 48 mode on ! ! interface GigabitEthernet1/0/11 description *** Connection to Teaming Server NIC 4 *** switchport access vlan 200 switchport trunk encapsulation dot1q switchport mode access speed 1000 duplex full spanning-tree portfast channel-group 48 mode on ! check your port-channel using: sh ip int brief Correctly congured interfaces should look like this: GigabitEthernet1/0/10 unassigned YES unset up GigabitEthernet1/0/11 unassigned YES unset up GigabitEthernet2/0/10 unassigned YES unset up GigabitEthernet2/0/11 unassigned YES unset up Port-channel47 unassigned YES unset up Port-channel48 unassigned YES unset up up up up up up up

3. TROUBLESHOOTING When the interfaces are up and on the teaming-side everything seems ne, but the link speed isn't doubled and the ether-channels are registering as down. Check your switch-logging. You are probably presented with MACFLAP messages. This is caused by LACP being congured on the port-channel members. *Mar 5 01:14:28.668 CET: %SYS-5-CONFIG_I: Congured from console by Admin on vty0 (10.10.10.228) *Mar 5 01:14:39.263 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35aa in vlan 200 is apping between port Gi1/0/11 and port Gi2/0/11 *Mar 5 01:14:45.705 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35a8 in vlan 10 is apping between port Gi2/0/10 and port Gi1/0/10

*Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

5 01:14:54.312 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35aa in vlan 200 is apping between port Gi2/0/11 and port Gi1/0/11 5 01:15:01.484 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35a8 in vlan 10 is apping between port Gi2/0/10 and port Gi1/0/10 5 01:15:05.461 CET: %SYS-5-CONFIG_I: Congured from console by Admin on vty0 (10.10.10.228) 5 01:15:09.403 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35aa in vlan 200 is apping between port Gi1/0/11 and port Gi2/0/11 5 01:15:14.478 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35a8 in vlan 10 is apping between port Gi2/0/10 and port Gi1/0/10 5 01:15:21.919 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35aa in vlan 200 is apping between port Gi2/0/11 and port Gi1/0/11 5 01:15:28.026 CET: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8e.991b.35a8 in vlan 10 is apping between port Gi2/0/10 and port Po47 5 01:15:28.168 CET: %SYS-5-CONFIG_I: Congured from console by Admin on vty0 (10.10.10.228)

Make sure the interfaces who are member of the port-channel are running in channel-group mode (on). active Enable LACP unconditionally auto Enable PAgP only if a PAgP device is detected desirable Enable PAgP unconditionally on Enable Etherchannel only passive Enable LACP only if a LACP device is detected

Important online sources that helped creating the above tutorial: (HP Virtual Connect for the Cisco Network Administrator) http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf (Cisco Conguring Etherchannels) http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/conguration/guide/cli_rel_4_0_1a/EtherChannel.pdf