Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)

You do not see the port group on vCenter Server or the following message is displayed:

The connection to vCenter server is down.

1. Verify that the connection to vCenter Server is Enabled and Connected.

show svs connections

2. Reconnect to vCenter server.

For detailed instructions, see the Connecting to vCenter Server procedure in the Cisco Nexus 1000V System Management Configuration Guide.

The domain configuration was not successfully pushed to vCenter server.

1. Verify that the domain configuration was successfully pushed to vCenter Server.

show svs domain

2. Fix any problems with the domain configuration.

For information about configuring the domain, see the Cisco Nexus 1000V System Management Configuration Guide.

The port profile is configured incorrectly.

1. Verify that the vmware port-group is configured for the port profile and that the port profile is enabled.

show port profile name name

2. Fix the port profile using the procedures in the Cisco Nexus 1000V Port Profile Configuration Guide.

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:

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:

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

After modifying a port profile, an assigned offline interface is quarantined.

A system message similar to the following is logged:

The interface has been removed from the DVS.

To bring the interface back online, see the “Recovering a Quarantined Offline Interface” section.

A module and all associated interfaces are offline.

A system message similar to the following is logged:

The interface carrying system VLANs for the module has gone down for one of the following reasons:

• System interfaces were removed from the DVS on vCenter Server.
• The module was powered down.
• There is a general loss of connectivity to the module.

Follow VEM troubleshooting guidelines to bring the module back online

To bring the interface back online, see the “Recovering a Quarantined Offline Interface” section.

show port-profile

Displays the port profile configuration.

See Example 10-1 on page 10-6 .

show port-profile name name

Displays the configuration for a named port profile.

See Example 10-2 on page 10-7 .

show port-profile brief

Displays a tabular view of all configured port profiles.

See Example 10-3 on page 10-7 .

show port-profile expand-interface

Displays all configured port profiles expanded to include the interfaces assigned to them.

See Example 10-4 on page 10-7 .

show port-profile expand-interface name name

Displays a named port profile expanded to include the interfaces assigned to it.

See Example 10-5 on page 10-8 .

show port-profile-role [ name port-profile-role-name ]

Displays the port profile role configuration, including role names, descriptions, assigned users, and assigned groups.

See Example 10-7 on page 10-8 .

show running-config port-profile [ profile-name ]

Displays the port profile configuration.

See Example 10-6 on page 10-8 .

show port-profile-role

Displays the port profile role configuration.

See Example 10-7 on page 10-8 .

show port-profile-role users

Displays the available users and groups.

See Example 10-8 on page 10-9 .

show port-profile sync-status [ interface if-name ]

Displays the interfaces that are not synchronized with the port profile.

See Example 10-9 on page 10-9 .

show port-profile virtual usage [ name profile-name ]

Displays the port profile usage by interface.

See Example 10-10 on page 10-9 .

show msp internal info

Displays the port profile mappings on vCenter server and configured roles.

See Example 10-11 on page 10-9 .

show system internal port-profile profile-fsm

Displays the port profile activity on the Cisco Nexus 1000V, including transitions such as inherits and configurations. If the following displays, then all inherits are processed:

Curr state: [PPM_PROFILE_ST_SIDLE]

See Example 10-12 on page 10-13 .

show system internal port-profile event-history msgs

Displays the messages logged about port profile events within the Cisco Nexus 1000V.

See Example 10-13 on page 10-14 .