We have been running into some issues with two of our semi-production environments where in both environments, there are two VSMs running on top of the VEM. Both VSMs loss connectivity at the same time and never came back. In one environment (A), we tried reboot, moving into different host (VEM) but still can't see any modules when we did a "show module". We then shift the VSM over to the standard vSwitch and everything start to talk, and the module is back, SVS connection is back. As soon we move it back to the VEM we will lose the VSM again. However, on day 2, everything started to work again in environment A (now on VEM), but not in B.
Now we are trying everything we could in B, but we could't get the VSM to talk via VEM, of course as soon as you put the VSM on the standard vSwitch, it started to talk.
Has anyone experience this issue before? and under VMware, the System-Uplink port is showing blocked by admin. and We do have the system vlan configured under the System-Uplink port profile. We have rebooted all the ESXi hosts as well as the VSM several times, still no luck.
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...