Addition of new NIC to port-channel fails if profile has queueing policy
Symptom: Addition of NIC(s) to port-channel fails if the VEM is added first time to VSM or NIC(s) are added first time to VSM one at a time. Error similar to the following can be seen: %ETHPORT-5-IF_DOWN_PORT_PROFILE_INHERIT_ERR: Interface Ethernet1/2 is down (port-profile inherit error)
Conditions: Failure is seen only when the NIC which was previously not added to VSM by any other port-profile and is added to port-channel port-profile for the first time or multiple NICs are added the first time to VSM one at a time.
1. Remove the queuing policy from the port-profile and add the NIC to the port-channel. Once port joins the bundle, put back queuing policy. Subsequent NIC removal/addition to profile will work fine.
2. Or, bring the NIC up using any other port-profile and then move it to intended port-profile having queuing policy.
We prefer to use option-2, because we want to avoid to make changes at the primary uplink-port-profile what is used by all hosts. When something would go wrong during the change of this profile, our complete vmware environment would be down.
But option-2 doesn't work in our environment. We did the steps described in the workaround:
1. created a new profile without any queing:
port-profile type ethernet Uplink-Test
switchport mode access
switchport access vlan 100
2. Then we moved the failed vmnic11 to this new profile. And we see this error:
2012 Jan 16 12:52:35 BYNX04 %VIM-5-IF_DETACHED: Interface Ethernet5/12 is detached
2012 Jan 16 12:52:35 BYNX04 %VIM-5-IF_ATTACHED: Interface Ethernet5/12 is attached to vmnic11 on module 5
2012 Jan 16 12:52:36 BYNX04 %IPQOSMGR-SLOT5-3-QOSMGR_DPA_MSG: DPA returned error message - QoS Agent: Only one queuing policy instance (per VEM) is sup ported
2012 Jan 16 12:52:36 BYNX04 %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet5/12 has been quarantined due to Cmd Failure 2012 Jan 16 12:52:37 BYNX04 %ETHPORT-5-IF_DOWN_INACTIVE: Interface Ethernet5/12 is down (Inactive)
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...