Cisco Bug: CSCuq42918 - VSM port profiles created through PNSC GUI are not deployed in VSM CLI
Oct 01, 2014
- Cisco Virtual Network Management Center
Known Affected Releases
Symptom: Port profile and service path configuration from the Prime Network Services Controller GUI is not pushed to the Nexus 1000V. Conditions: This situation can occur in either of the following scenarios: Scenario 1 You associate the 'svcAutomationDefault' service path with a port profile. This service path is only complete when Prime Network Services Controller is deployed in Orchestrator mode and the 'Auto-ComputeFirewall' is deployed. Orchestrator mode is not supported in this release. Scenario 2 You delete a service logical device that is being referred to by a service node policy. If the service node is active, the bug is triggered immediately. If the service node is not active in any port profile, then the issue would arise if you associate a service path with this service node to a port profile.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases