We've had problems with VMs on the Nexus 1000v not being able to communicate at times, when we move them to the standard switch, the problem disappears. We've stumbled upon some lines in the vmkernel.log on the ESXi host with the problem that might give us a hint, but we can't understand what they mean:
2013-12-03T06:45:27.675Z cpu62:8254)<3>nx_nic[vmnic3]: Bad Rcv descriptor ring
2013-12-03T06:45:27.763Z cpu62:8254)<3>nx_nic[vmnic3]: Bad Rcv descriptor ring
2013-12-03T06:45:27.783Z cpu62:8254)<3>nx_nic[vmnic3]: Bad Rcv descriptor ring
2013-12-03T06:45:27.951Z cpu63:8255)<3>nx_nic[vmnic3]: Bad Rcv descriptor ring
2013-12-03T06:45:27.988Z cpu58:8250)<3>nx_nic[vmnic3]: Got a buffer index:11f for Jumbo desc type. Max is 80
2013-12-03T06:45:27.991Z cpu58:8250)<3>nx_nic[vmnic3]: Got a buffer index:117 for Jumbo desc type. Max is 80
2013-12-04T12:29:56.114Z cpu44:8287)sf_netif_port_unreserve: DEBUG port 33554454-2000016 clientName is SRV7WWWMID002 ethernet0, unlicensed/headless VEM
2013-12-05T08:43:44.725Z cpu26:5272602)sf_netif_port_connect: Cannot set uplink tree capabilities, error returned was Not found
2013-12-06T08:59:58.554Z cpu5:8285)sf_netif_port_unreserve: DEBUG port 33554449-2000011 clientName is AV01_Prod.eth0, unlicensed/headless VEM
2013-12-06T09:02:10.196Z cpu56:8287)sf_netif_port_unreserve: DEBUG port 33554458-200001a clientName is SRV9DMZAPP002 ethernet0, unlicensed/headless VEM
The log errors didn't relate to the problem we had. We had a Cisco technician look through our setup and logs and he didn't find anything. He suspects that we're running a too old version of VSM/VEM for the ESXi build we're running. Either that or a hardware driver failure. We're updating everything and then we'll see how it goes.
He recommended getting these logs if we experience the error again:
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...