Skip to main content

Configure NIC teaming for V Switch


Two or more NIC cards are required to use NIC teaming in  ESX server.



Step 1 : Create a new vSwitch and give it a network label like "VM Network” . Add the required NICs to the switch. Procedure on how to add nic to a virtual switch is described below



Select the vSwitch from the Configuration -> networking . Select Network adapters and click on add


In the Add Adapter Wizard select the nic card which needs to be added to the switch and click on next. If the nic card is already attached to another virtual switch, it will be removed from it and added to the new one.. Go to next screen


In the failover order, we can configure the active and standby adapters if required. Click next and finish the configuration

Step 2: Configure teaming

Configuring teaming in Esx server will implement load balancing for outbound traffic only. For implementing the same for inbound traffic the required configurations need to be done on the physical switch to which the NICs are actually connected
Switch configuration steps

Suppose two nics vnic0 and vnic1 are added to a virtual switch vswitch0. vnic0 and vnic1 are physical adapters connected to switch ports gi0/23 and gi0/24

1) Create a port channel in the switch for the ports.

Commands used for the same in Cisco Catalyst IOS-based physical switches are given below:

s3(config)#int port-channel1
s3(config-if)#description NIC team for ESX server
s3(config-if)#int gi0/23
s3(config-if)#channel-group 1 mode on
s3(config-if)#int gi0/24
s3(config-if)#channel-group 1 mode on


This creates port-channel1  and assigns GigabitEthernet0/23 and GigabitEthernet0/24 into team

2) Ensure that the load balancing mechanism that is used by both the switch and ESX Server matches. To find out the switch’s current load balancing mechanism, use this command in enable mode:

show etherchannel load-balance

This will report the current load balancing algorithm in use by the switch. We can either use IP- based load balancing or MAC-based load balancing . IP-based option gives  better utilization across the members of the NIC team than some of the other options

3) Set the switch load-balancing algorithm using one of the following commands in global configuration mode:

port-channel load-balance src-dst-ip (to enable IP-based load balancing)
port-channel load-balance src-mac (to enable MAC-based load balancing)
Labels:

Comments

Post a Comment

Popular posts from this blog

Install nested KVM in VMware ESXi 5.1

In this blog, I will explain the steps required to run a nested KVM hypervisor on  Vmware ESXi. The installation of KVM is done on Ubuntu 13.10(64 bit). Note: It is assumed that you have already installed your Ubuntu 13.10 VM in ESXi, and hence we will not look into the Ubuntu installation part. 1) Upgrade VM Hardware version to 9. In my ESXi server, the default VM hardware version was 8. So I had to shutdown my VM and upgrade the Hardware version to 9 to get the KVM hypervisor working. You can right click the VM and select the Upgrade hardware option to do this. 2)In the ESXi host In /etc/vmware edit the 'config' file and add the following setting vhv.enable = "TRUE" 3)Edit the VM settings and go to VM settings > Options  > CPU/MMU Virtualization . Select the Intel EPT option 4) Go to Options->CPUID mask> Advanced-> Level 1, add the following CPU mask level ECX  ---- ---- ---- ---- ---- ---- --H- ---- 5) Open the vmx...
5 comments
Read more

Virtual fibre channel in Hyper V

Virtual fibre channel option in Hyper V allows the connection to pass through from physical  fibre channel HBA to virtual fibre channel HBA, and still have the flexibilities like live migration. Pre-requisites: VM should be running Windows Server 2008, 2008 R2 or Windows Server 2012 Supported physical HBA with N_Port Virtualization(NPIV) enabled in the HBA. This can be enabled using any management utility provided by the SAN manufacturer. If you need to enable live migration, each host should be having two physical HBAs and each HBA should have two World Wide Names(WWN). WWN is used to established connectivity to FC storage.When you perform migration, the second node can use the second WWN to connect to the storage and then the first node can release its connection. Thereby the storage connectivity is maintained during live migration Configuring virtual fibre channel is a two step process Step 1: Create a Virtual SAN in the Hyper-V host First you need to click on Vir...
2 comments
Read more

The Cloud Migration Gotchas..

All leading cloud providers have a well defined Cloud Adoption Framework that will help you shape up your cloud migration strategy. Customers would eventually end up with one of the 5 'R's of rationalization - Rehost(Lift&shift) , Refactor, Rearchitect, Rebuild or Replace.  Once you have identified the approach , next steps would be planning and execution. However the best  plans laid out by  a professional services team can be driven off the track by  customer specific environment challenges. If you are helping customers with cloud migration, here are few things that you might want to think through again and prepare for before you go all in . 1.Start with stakeholder buy in The first step called out in Azure Cloud Adoption Framework is Strategy  or rather the motivation of the organization to move to cloud. Though this would usually be done in the presales phase and might have the buy in of the C-Suite, it is very important that this acceptance trickles do...
23 comments
Read more