Cisco Nexus 1000V - Page 133

10-3
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 10 Port Profiles
Problems with Port Profiles
A port configuration is not applied to
an interface.
Management connectivity between
vCenter server and the VSM has
prevented the port profile
assignment from being sent or
received.
1. Display the port profile usage by interface.
show port-profile virtual usage
2. Verify that the interface level configuration
did not overwrite the port profile
configuration.
show run
show port-profile expand-interface
3. If the show command output is incorrect, on
vCenter server, reassign the port group to
the interface.
An Ethernet interface or vEthernet
interface is administratively down.
A system message similar to the
following is logged:
%VMS-3-DVPG_NICS_MOVED: '1' nics
have been moved from port-group
'Access483' to
'Unused_Or_Quarantine_Veth'.
The interface is inheriting a
quarantined port profile.
A configuration was not saved prior
to rebooting the VSM, the
configuration was lost, and the
interfaces were moved to one of the
following port profiles:
• Unused_Or_Quarantine_Uplink
for ethernet types
• Unused_Or_Quarantine_Veth
for Vethernet types
1. Verify the port profile-to-interface mapping.
show port-profile virtual usage
2. Reassign the VMNIC or PNIC to a
non-quarantined port group to enable the
interface to be up and forwarding traffic.
This requires changing the port group on
vCenter Server.
After applying a port profile, an
online interface is quarantined.
A system message similar to the
following is logged:
%PORT-PROFILE-2-INTERFACE_QUARAN
TINED: Interface Ethernet3/3 has
been quarantined due to Cache
Overrun
The assigned port profile is
incorrectly configured. The
incorrect command fails when the
port profile is applied to an
interface.
Although a specific command fails,
the port profile-to-interface
mapping is created.
1. Identify the command that failed.
show accounting log | grep FAILURE
2. Verify that the interface is quarantined.
show port-profile sync-status
3. Verify the port profile-to-interface mapping.
show port-profile virtual usage
4. Fix the error in the port profile using the
procedures in the Cisco Nexus 1000V Port
Profile Configuration Guide.
5. Bring the interface out of quarantine.
no shutdown
The interface comes back online.
6. Return shutdown control to the port profile.
default shutdown
Symptom Possible Causes Solution