We have a setup based on a blade center with 8 blade servers running vmware esxi 4.1 - we are using ms win2k3 terminalsers which is load-balanced with NLB - as long as we keep the VM's on the same ESXi host the NLB works fine in unicast mode as long as we are using VMWare's native vswitch - but if we replace the VMWare switch with Cisco's NX 1000V we can only address one server and I can see that the clusers mac is found in the cam in one of the veth's.
we have also tried the multicast setup but it is not useable.
Has some out there got a running setup with MS NLB under VMWare & Cisco NX 1000?
Are you running this under the Cisco 1000V or the VMWare switch?
When you are running in multicast mode are you then using SessionDirectory also ? - if so do you then also observe a short disconnect when logging where the Session Directory redirects you to another server ?
hmm - strange - try to take a look here - wireshark dump - here in packet #1094 is the last packet seen from the cluster-address and the next packet is a reconnect on the primary lan-addresse - do you observe something similary? I cannot find some documentation on this behavior in multicast mode..
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...