We upgraded our UCS infrastructure from 2.1 (1f) -> 2.1 (3c). Ever since we've started receiving linkstate down/up alerts from vCenter whenever a VM is vMotion'ed. We're not doing high performance / DirectPath I/O.
I understand with the nature of dynamic vNIC's, these linkstate changes are normal with a vMotion. What I don't understand is why we only started receiving alerts after the upgrade. I've had a case open with Cisco TAC for more than 2 months, they can't reproduce the behavior - though their test environment is running 2.2 and they don't want to downgrade.
Does anyone know how to suppress these messages? Either from the UCS or ESXi side of things? We get a couple dozen emails each day due to this from vCOPS, and unfortunately vCOPS notifications aren't flexible enough to weed them out. I've been told vCOPS v6 contains a complete retooling of the notification system, but the beta isn't due until the end of the year.
VMware ESXi 5.1u1
vem status -v
Package vssnet-esxmn-next-release Version 5.1-188.8.131.52 Build 1 Date Mon Sep 24 11:51:42 PDT 2012
Number of PassThru NICs are 48 VEM modules are loaded
DVS Name Num Ports Used Ports Configured Ports MTU Uplinks VM-FEX 256 73 256 1500 vmnic12,vmnic10 DVS Name Num Ports Used Ports Configured Ports MTU Uplinks Management 256 7 256 1500 vmnic1,vmnic0 DVS Name Num Ports Used Ports Configured Ports MTU Uplinks NAS 256 6 256 9000 vmnic4,vmnic2 DVS Name Num Ports Used Ports Configured Ports MTU Uplinks vMotion 256 6 256 9000 vmnic8,vmnic6
Number of PassThru NICs are 48 VEM Agent (vemdpa) is running
hostd.log:2014-08-07T15:13:31.002Z [45C82B90 info 'Vimsvc.ha-eventmgr'] Event 38445 : Physical NIC vf_vmnic7 linkstate is down.
vmkernel.log:2014-08-07T15:13:30.047Z cpu14:8243)<6>enic 0000:17:00.0: vf_vmnic7: Link DOWN vmkernel.log:2014-08-07T15:13:30.502Z cpu11:8714)hardPts: hard_niv_port_update:4912: Unclaimed VF<vf_vmnic7/0x2000008/Idx:8> vmkernel.log:2014-08-07T15:13:30.502Z cpu11:8714)hardPts: hard_niv_process_link_event_vf:916: Got a Link DOWN on VF vf_vmnic7 in state: Connected Unclaimed, Ignoring
vobd.log:2014-08-07T15:13:30.503Z: [netCorrelator] 6561411644570us: [vob.net.vmnic.linkstate.down] vmnic vf_vmnic7 linkstate down vobd.log:2014-08-07T15:13:31.000Z: [netCorrelator] 6561695768710us: [esx.problem.net.vmnic.linkstate.down] Physical NIC vf_vmnic7 linkstate is down
Hi I have this primary configuration on the primary CSR Router in the HA
mode in same AZ but I am not seeing failover to secondary CSR I am
seeing on the backup router that the API call was successful. 10 10 Actv
success Thu Jun 9 18:13:50 2016 syslog app...
In today’s modern networks the interaction between applications and
network infrastructures is increasingly important for service providers,
content providers and enterprise businesses. The more network operators
can interact with the network the more opt...