Guest

Preview Tool

Cisco Bug: CSCus74712 - Stingray1:Addhost:Block in UI, if vmknic's vlans not in uplink PP

Last Modified

Jul 08, 2015

Products (1)

  • Cisco Virtual Application Cloud Segmentation (VACS) Services

Known Affected Releases

5.2STV1.1

Description (partial)

Symptom:
Add-host fails with VSUM error 'VLANS_NOT_BACKED'

Conditions:
When the exiting vmknics on vswitch is migrated, and the uplink port-profile selected for the pnics does not carry the vmknics VLANs.

Eg: 
Uplink port-profile has vlans 1-10 and is mapped to pnic vmnic0. 
Now in the kernel NIC migration screen, if the vmknic is of vlan 11, then the vmknic is shown with vlan 11 in the vmknic table, but when you proceed and submit the UI, the add-host fails with the above error.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.