Symptom
When a VSM's policy agent is registered to Prime NSC, the security profile ID (SPID) for VSG security profiles may not be resolved correctly. The output of 'show vservice port brief' will show that the SPID is not resolving correctly:
PortProfile:Tenant-Cisco-VSG-Protected-VMs
Org:root/Cisco
Node:Tenant-Cisco-VSG(192.168.112.11) Profile(Id):E2E-Test(0)#
Veth Mod VM-Name vNIC IP-Address
9 3 vm4-centos-test 1 10.129.0.201
# - PA/VNMC is not connected to VSM yet or Org confer error or PA/VNMC malfunctioning
The output of 'show proc | grep http' on the VSM will also show that the httpd processes are not starting up correctly.
Conditions
This has been seen with the following software combinations (other versions may also be affected):
VSM: 2.2.1
VSM PA: 2.1.1b
NSC: 3.0.1c
Workaround
Rebooting the VSM or forcing a 'system switchover' may resolve the issue.
Further Problem Description
