Preview Tool

Cisco Bug: CSCvh93166 - Unable to add portgroups to the vcenter domain after renaming an uplink from the vcenter

Last Modified

Sep 14, 2019

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases

3.1(1i) 3.1(2m)

Description (partial)

After changing uplinks names in the VDS from the vCenter, changes in the ACI regarding the associated domain were no longer possible. 
Unable to push/modify portgroupsin the VDS after renaming an uplink from the vCenter.
This was working previously in 2.3 version, from 3.1x the defect was observed.
Fault F606347 is raised on the APIC.

Fault delegate: [FSM:FAILED]: Addition or Deletion of Port Group for: (uni/tn-JJ/ap-test/epg-testportgroup2) Tenant: JJ associated with either EPG:(Ap: test Epg: testportgroup2) or Services:(LDevInst: EPpInfo: ) on VM Controller: test VM Domain: TEST VM Provider: VMware, failed with error: A specified parameter was not correct: spec.uplinkTeamingPolicy.uplinkPortOrder.activeUplinkPort(TASK:ifc:vmmmgr:CompEpPDAddorDelExtPol)

6135||18-02-09 18:44:45.737+01:00||ifc_vmmmgr||INFO||fn=[getTaskInfo]||TEST: test: 0x564f45046a10:  : Error :A specified parameter was not correct: spec.uplinkTeamingPolicy.uplinkPortOrder.activeUplinkPort||../svc/vmmmgr/src/gen/ifc/app/./imp/vmm/vmware/||770
6135||18-02-09 18:44:45.737+01:00||ifc_vmmmgr||INFO||fn=[vcTaskHandler]||TEST: test: 0x564f45046a10: JJ|test|testportgroup2: Task failed - Error Code: 286||../svc/vmmmgr/src/gen/ifc/app/./imp/vmm/vmware/||10357

The vcenter reports error 
A specified parameter was not correct: spec.uplinkTeamingPolicy.uplinkPortOrder.activeUplinkPort?

There are three condition could trigger this problem:
1) uplink portgroup name is changed
2) The uplink name of dvs is change(this can be check follow dvs->setting->edit settings->edit uplink names)
3) number of uplink is changed from default 8.

Related Community Discussions

<key>CSCvh93166</key> - Unable to add portgroups to the vcenter domain after renaming an uplink from the vcenter
I have same issue this Bug in version 3.1(2m).
Latest activity: Apr 11, 2018
Bug details contain sensitive information and therefore require a 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.