So the first question I tend to address with customers is how do they want their hosts networking to look. which is equally relevant whatever platform is used and I’m sure you are familiar with. Ok, Thats narrowed us down but still a lengthy topic, so I’ll concentrate on the Cisco UCS specific aspects and not so much on the standard VMware config, I/O control etc. Lets take the most common implementation I tend to do which is vSphere using standard vSwitches. whether using Standard vSwitches / vDS, Nexus 1000V or VM-FEX. Thanks for the great question, and one (as you might expect) with potentially several answers depending on the implementation, i.e. Supported hashing options for load balancing: 802.3ad LACP (only supported on C-Series (P81E)) Currently.
Active-Active (outbound load balancing only).Active-Backup (with or without failback).
HOW WOULD I MONITOR INTERNET UPTIME MAC DRIVER
The Windows teaming driver supports the below:
HOW WOULD I MONITOR INTERNET UPTIME MAC INSTALL
With regards to a bare metal install there is now a M81KR (Palo) NIC teaming driver for W2K8R2 available, which I have found works really well. I think the issue arises when you use a per packet / flow algorithm as the upstream LAN will see the host on Fabric A one minute then fabric B the next and the host will “flap” between the two. Again the answer is it depends, if you are using a Hyper-Visor like VMware you can select the hash algorithm to use and if you would like to active/active load balance as you suggest you would need to specify Port-Group based load balancing, this will ensure that each VM gets consistently mapped to the same UCS vNIC so VM 1 may go fabric A and VM 2 may go out Fabric B.
0 kommentar(er)
