
7-8
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 7 VSM and VEM Modules
Problems with the VSM
Verifying the System Port Profile Configuration
You can verify the port profile configuration.
BEFORE YOU BEGIN
•
Log in to the CLI in EXEC mode.
•
Verify that the output of the
show port-profile name
command indicates the following:
–
The control and packet VLANs are assigned.
–
The port profile is enabled.
–
If you have configured a non-default system MTU setting, check that it is the correct size.
Step 1
On the VSM, verify the system port profile configuration.
show port-profile name
system-port-profile-name
Example:
switch#
show port-profile
name SystemUplink
port-profile SystemUplink
description:
type: ethernet
status: enabled
capability l3control: no
pinning control-vlan: -
pinning packet-vlan: -
system vlans: 114,115
port-group: SystemUplink
max ports: 32
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan all
system mtu 1500
no shutdown
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
assigned interfaces:
Verifying the Control and Packet VLAN Configuration
You can verify that the control and packet VLANs are configured on the VSM.
Note
The procedure documented is for troubleshooting VSM and VEM connectivity with Layer 2 mode.
BEFORE YOU BEGIN
•
Log in to the CLI in EXEC mode.
•
Check that the output of the
show running-config
command shows control and packet VLAN ID
numbers among the VLANs configured,