I've recently deployed a pair of Nexus 3064s in a VPC for core routing/switching. Since I've deployed these switches, we've experienced intermittent packet loss on our ESX devices. I suspect some kind of oddity on the ESX servers but I'm curious to know what is the correct configuration for the ESX hosts from a Load Balancing perspective?
Should our server team have them configured in Redundancy mode a.k.a Active/Passive links or should they configure as port-channel on their servers?
To drawn this picture out, the ESX servers are attached to a single 4948 within a rack but have multiple links on this switch. The 4948 is multihomed to the 3064s via a single port-channel with VPC enabled.
Redundancy mode vs port-channel is really dependent upon what the hosts support but in general port-channels provide you with additional bandwidth. I believe with ESX you may need to use mode on.
In regards to the intermittent packet loss, I would start with the basic: sho int count, check spanning tree, cpu, log, qos etc. Might have to do sniffer traces. Intermittent issues are the toughest ones to troubleshoot.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...