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

Information About Ports
Port Diagnostic Checklist
Problems with Ports
Port Troubleshooting Commands

Ports

This chapter describes how to identify and resolve problems with ports and includes the following sections:

Information About Ports

This section includes the following topics:

Information About Interface Characteristics

Before a switch can relay frames from one data link to another, you must define the characteristics of the interfaces through which the frames are received and sent. The configured interfaces can be Ethernet (physical) interfaces, virtual Ethernet interfaces, and the management interface.

Each interface has the following:

Administrative Configuration

The administrative configuration does not change unless you modify it. This configuration has attributes that you can configure in administrative mode.

Operational state

The operational state of a specified attribute, such as the interface speed. This state cannot be changed and is read-only. Some values might not be valid when the interface is down (such as the operation speed).

For a complete description of port modes, administrative states, and operational states, see the Cisco Nexus 1000V Interface Configuration Guide.

Information About Interface Counters

Port counters are used to identify synchronization problems. Counters can show a significant disparity between received and transmitted frames. To display interface counters, use the following command:

show interface ethernet slot number counters

See Example 9-11 on page 9-14 .

Values stored in counters can be meaningless for a port that has been active for an extended period. Clearing the counters provides a better idea of the actual link behavior at the present time. Create a baseline first by clearing the counters.

clear counters interface ethernet slot-number

Information About Link Flapping

When a port continually goes up and down, it is said to be flapping, or link flapping. When a port is flapping, it cycles through the following states, in this order, and then starts over again:

1. Initializing—The link is initializing.

2. Offline—The port is offline.

3. Link failure or not connected—The physical layer is not operational and there is no active device connection.

To troubleshoot link flapping, see the “Information About Link Flapping” section.

Information About Port Security

The port security feature allows you to secure a port by limiting and identifying the MAC addresses that can access the port. Secure MAC addresses can be manually configured or dynamically learned.

For detailed information about port security, see the Cisco Nexus 1000V Security Configuration Guide.

Type of Port	Is Port Security Supported?
vEthernet access	Yes
vEthernet trunk	Yes
vEthernet SPAN destination	No
Standalone Ethernet interfaces	No
Port channel members	No

To troubleshoot problems with port security, see the following:

Port Diagnostic Checklist

Use the following checklist to diagnose port interface activity.

For more information about port states, see the Cisco Nexus 1000V Interface Configuration Guide.

Table 9-1 Port Diagnostic Checklist
Checklist	Example
Verify that the module is active. show module	See Example 9-1 on page 9-11 .
Verify that the VSM is connected to vCenter Server. show svs connections	See Example 9-3 on page 9-12 .
On vSphere Client connected to vCenter Server, verify that the required port profiles are assigned to the physical NICs and the virtual NICs.
Verify that the ports have been created. show interface brief	See Example 9-8 on page 9-13 .
Verify the state of the interface. show interface ethernet	See Example 9-10 on page 9-13 .

Problems with Ports

This section includes possible causes and solutions for the following symptoms:

Cannot Enable an Interface

Possible Cause	Solution
A Layer 2 port is not associated with an access VLAN or the VLAN is suspended.	1. Verify that the interface is configured in a VLAN. show interface brief 2. If not already, associate the interface with an access VLAN. 3. Determine the VLAN status. show vlan brief 4. If not already active, configure the VLAN as active. config t vlan vlan-id state active

Possible Cause

Solution

A Layer 2 port is not associated with an access VLAN or the VLAN is suspended.

1. Verify that the interface is configured in a VLAN.
show interface brief

2. If not already, associate the interface with an access VLAN.

3. Determine the VLAN status.
show vlan brief

4. If not already active, configure the VLAN as active.
config t
vlan vlan-id
state active

Port Link Failure or Port Not Connected

Possible Cause	Solution
The port connection is bad.	1. Verify the port state. show system internal ethpm info 2. Disable and then enable the port. shut no shut 3. Move the connection to a different port on the same module or a different module. 4. Collect the ESX-side NIC configuration. vss-support
The link is stuck in initialization state or the link is in a point-to-point state.	1. Check for a link failure system message. Link Failure, Not Connected show logging 2. Disable and then enable the port. shut no shut 3. Move the connection to a different port on the same module or a different module. 4. Collect the ESX-side NIC configuration. vss-support

Possible Cause

Solution

The port connection is bad.

1. Verify the port state.

show system internal ethpm info

2. Disable and then enable the port.

shut
no shut

3. Move the connection to a different port on the same module or a different module.

4. Collect the ESX-side NIC configuration.

vss-support

The link is stuck in initialization state or the link is in a point-to-point state.

1. Check for a link failure system message.
Link Failure, Not Connected

show logging

2. Disable and then enable the port.

shut
no shut

3. Move the connection to a different port on the same module or a different module.

4. Collect the ESX-side NIC configuration.

vss-support

Link Flapping

When you are troubleshooting unexpected link flapping, it is important to have the following information:

Who initiated the link flap.
The actual reason for the link being down.
For a definition of link flapping, see the “Link Flapping” section.

Possible Cause	Solution
The bit rate exceeds the threshold and puts the port into an error-disabled state.	Disable and then enable the port. shut no shut The port should return to the normal state.
A hardware failure or intermittent hardware error causes a packet drop in the switch. A software error causes a packet drop. A control frame is erroneously sent to the device.	An external device might choose to initialize the link again when encountering the error. If so, the exact method of link initialization varies by device. 1. Determine the reason for the link flap as indicated by the MAC driver. 2. Use the debug facilities on the end device to troubleshoot the problem.
ESX errors, or link flapping, occurs on the upstream switch.	Use the troubleshooting guidelines in the documentation for your ESX or upstream switch.

Possible Cause

Solution

The bit rate exceeds the threshold and puts the port into an error-disabled state.

Disable and then enable the port.

shut
no shut

The port should return to the normal state.

A hardware failure or intermittent hardware error causes a packet drop in the switch.

A software error causes a packet drop.

A control frame is erroneously sent to the device.

An external device might choose to initialize the link again when encountering the error. If so, the exact method of link initialization varies by device.

1. Determine the reason for the link flap as indicated by the MAC driver.

2. Use the debug facilities on the end device to troubleshoot the problem.

ESX errors, or link flapping, occurs on the upstream switch.

Use the troubleshooting guidelines in the documentation for your ESX or upstream switch.

Port ErrDisabled

Possible Cause	Solution
The cable is defective or damaged.	1. Verify the physical cabling. 2. Replace or repair defective cables. 3. Reenable the port. shut no shut
You attempted to add a port to a port channel that was not configured identically, and the port is then errdisabled.	1. Display the switch log file and identify the exact configuration error in the list of port state changes. show logging logfile 2. Correct the error in the configuration and add the port to the port channel. 3. Re-enable the port. shut no shut
A VSM application error has occurred.	1. Identify the component that had an error while you were bringing up the port. show logging logfile \| grep interface_number See Example 9-7 on page 9-13 . 2. Identify the error transition. show system internal ethpm event-history interface interface_number 3. Open a support case and submit the output of the above commands. For more information see the “Contacting Cisco or VMware Customer Support” section.

Possible Cause

Solution

The cable is defective or damaged.

1. Verify the physical cabling.

2. Replace or repair defective cables.

3. Reenable the port.

shut
no shut

You attempted to add a port to a port channel that was not configured identically, and the port is then errdisabled.

1. Display the switch log file and identify the exact configuration error in the list of port state changes.

show logging logfile

2. Correct the error in the configuration and add the port to the port channel.

3. Re-enable the port.

shut
no shut

A VSM application error has occurred.

1. Identify the component that had an error while you were bringing up the port.

show logging logfile | grep interface_number

See Example 9-7 on page 9-13 .

2. Identify the error transition.

show system internal ethpm event-history interface interface_number

3. Open a support case and submit the output of the above commands.

For more information see the “Contacting Cisco or VMware Customer Support” section.

VM Cannot Ping a Secured Port

Possible Cause	Solution
The vEthernet interface is not up.	1. Verify the state of the vEthernet interface. show interface vethernet number 2. If the interface is down, enable it. shut no shut
Drop on Source Miss (DSM) is set. New MAC addresses cannot be learned by this port.	1. Verify the port security configuration. module vem 3 execute vemcmd show portsec stats 2. If DSM is set, clear the DSM bit on the VSM. no port-security stop learning
The packet VLAN is not allowed on the port.	1. Identify the packet VLAN ID. show svs domain 2. Verify that the packet VLAN is allowed on VEM uplink ports. show port-profile na uplink-all 3. If the packet VLAN is not allowed on the uplink port profile, add it to the allowed VLAN list.
The packet VLAN is not allowed on the upstream switch port.	1. Identify the upstream neighbors connected to the interface. show cdp neighbors 2. Log in to the upstream switch and verify that the packet VLAN is allowed on the port. show running-config interface gigabitEthernet slot/port 3. If the packet VLAN is not allowed on the port, add it to the allowed VLAN list.

Port Security Violations

For detailed information about port security, see the Cisco Nexus 1000V Security Configuration Guide.

Possible Cause	Solution
The configured maximum number of secured addresses on the port is exceeded.	1. Display the secure addresses. show port -security address vethernet number show port-security address interface vethernet number 2. Identify ports with a security violation. show logging \| inc "PORT-SECURITY-2-ETH_PORT_SEC_SECURITY_VIOLATION_MAX_MAC_VLAN" 3. Correct the security violation. 4. Enable the interface. shut no shut

Possible Cause

Solution

The configured maximum number of secured addresses on the port is exceeded.

1. Display the secure addresses.

show port -security address vethernet number
show port-security address interface vethernet number

2. Identify ports with a security violation.

show logging | inc "PORT-SECURITY-2-ETH_PORT_SEC_SECURITY_VIOLATION_MAX_MAC_VLAN"

3. Correct the security violation.

4. Enable the interface.

shut
no shut

Port State is Blocked on a VEM

Possible Cause	Solution
The VLAN is not created on the VSM.	1. Verify the status and of the vEthernet interface. It should be up and not inactive. show interface vethernet number 2. Verify that the VLAN on the VSM is created. show vlan vlan-id On the VEM module, do the following: 1. Verify that the VLAN is programmed. vemcmd show vlan vlan-id 2. Verify that the VLAN is allowed on the ports. vemcmd show port vlan 3. Create the VLAN on the VSM. vlan vlan-id
The VEM modules are unlicensed.	1. Verify that all the modules are in licensed state. show module 2. Verify the status of the vEthernet interface. It should be up and not "VEM Unlicensed.” show interface vethernet number 3. Verify the license status of VEM modules. show module vem license-info On the VEM module, do the following: 1. Verify that card details show Licensed: Yes. vemcmd show card 2. Install the necessary licenses or move the switch to essential mode. svs switch edition essential

Possible Cause

Solution

The VLAN is not created on the VSM.

1. Verify the status and of the vEthernet interface. It should be up and not inactive.

show interface vethernet number

2. Verify that the VLAN on the VSM is created.

show vlan vlan-id

On the VEM module, do the following:

1. Verify that the VLAN is programmed.

vemcmd show vlan vlan-id

2. Verify that the VLAN is allowed on the ports.

vemcmd show port vlan

3. Create the VLAN on the VSM.

vlan vlan-id

The VEM modules are unlicensed.

1. Verify that all the modules are in licensed state.

show module

2. Verify the status of the vEthernet interface. It should be up and not "VEM Unlicensed.”

show interface vethernet number

3. Verify the license status of VEM modules.

show module vem license-info

On the VEM module, do the following:

1. Verify that card details show Licensed: Yes.

vemcmd show card

2. Install the necessary licenses or move the switch to essential mode.

svs switch edition essential

Port Troubleshooting Commands

You can use the commands in this section to troubleshoot problems related to ports.

Command	Purpose
show module module-number	Displays the state of a module. See Example 9-1 on page 9-11 .
show svs domain	Displays the domain configuration. See Example 9-2 on page 9-12 .
show svs connections	Displays the Cisco Nexus 1000V connections. See Example 9-3 on page 9-12 .
show cdp neighbors	Displays the neighbors connected to an interface. See Example 9-4 on page 9-12 .
show port internal event-history interface	Displays information about the internal state transitions of the port. See Example 9-5 on page 9-12 .
show logging logfile	Displays logged system messages. See Example 9-6 on page 9-12 .
show logging logfile \| grep interface_number	Displays logged system messages for a specified interface. See Example 9-7 on page 9-13 .
show interface brief	Displays a table of interface states. See Example 9-8 on page 9-13 .
show interface ethernet	Displays the configuration for a named Ethernet interface, including the following: Administrative state Speed Trunk VLAN status Number of frames sent and received Transmission errors, including discards, errors, CRCs, and invalid frames See Example 9-9 on page 9-13 . See Example 9-10 on page 9-13 .
show interface ethernet counters	Displays port counters for identifying synchronization problems. For information about counters, see the “Information About Interface Counters” section. See Example 9-11 on page 9-14 .
show interface vethernet	Displays the vEthernet interface configuration. See Example 9-12 on page 9-14 .
show interface status	Displays the status of the named interface.
show interface capabilities	Displays a tabular view of all configured port profiles. See Example 9-13 on page 9-14 .
show interface virtual port mapping	Displays the virtual port mapping for all vEthernet interfaces. See Example 9-14 on page 9-16 .
module vem execute vemcmd show portsec status	Displays the port security status of the port. If enabled, the output shows an LTL connected to the VM network adapter. See Example 9-15 on page 9-16 .
show port-security interface veth	Displays secure vEthernet interfaces.
show port -security address interface vethernet	Displays information about secure addresses on an interface. See Example 9-17 on page 9-16 .

For detailed information about show command output, see the Cisco Nexus 1000V Command Reference.

EXAMPLES

Example 9-1 show module Command

switch# show mod 3

Mod Ports Module-Type Model Status

--- ----- -------------------------------- ------------------ ------------

3 248 Virtual Ethernet Module ok

Mod Sw Hw

--- -------------- ------

3 NA 0.0

Mod MAC-Address(es) Serial-Num

--- -------------------------------------- ----------

3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA

Mod Server-IP Server-UUID Server-Name

--- --------------- ------------------------------------ --------------------

3 192.168.48.20 496e48fa-ee6c-d952-af5b-001517136344 frodo

Example 9-2 show svs domain Command

switch# show svs domain

SVS domain config:

Domain id: 559

Control vlan: 3002

Packet vlan: 3003

L2/L3 Aipc mode: L2

L2/L3 Aipc interface: management interface0

Status: Config push to VC successful.

switch#

Example 9-3 show svs connections Command

switch# show svs connections

connection VC:

ip address: 192.168.0.1

protocol: vmware-vim https

certificate: default

datacenter name: Hamilton-DC

DVS uuid: ac 36 07 50 42 88 e9 ab-03 fe 4f dd d1 30 cc 5c

config status: Enabled

operational status: Connected

switch#

Example 9-4 show cdp neighbors Command

switch# show cdp neighbors

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

S - Switch, H - Host, I - IGMP, r - Repeater,

V - VoIP-Phone, D - Remotely-Managed-Device,

s - Supports-STP-Dispute

Device ID Local Intrfce Hldtme Capability Platform Port ID

swordfish-6k-2 Eth3/2 149 R S I WS-C6506-E Gig1/38

switch#

Example 9-5 show port internal event-history interface Command

switch# show port internal event-history interface e1/7

>>>>FSM: <e1/7> has 86 logged transitions<<<<<

1) FSM:<e1/7> Transition at 647054 usecs after Tue Jan 1 22:44..

Previous state: [PI_FSM_ST_IF_NOT_INIT]

Triggered event: [PI_FSM_EV_MODULE_INIT_DONE]

Next state: [PI_FSM_ST_IF_INIT_EVAL]

2) FSM:<e1/7> Transition at 647114 usecs after Tue Jan 1 22:43..

Previous state: [PI_FSM_ST_IF_INIT_EVAL]

Triggered event: [PI_FSM_EV_IE_ERR_DISABLED_CAP_MISMATCH]

Next state: [PI_FSM_ST_IF_DOWN_STATE]

Example 9-6 show logging logfile Command

switch# show logging logfile

...

Jan 4 06:54:04 switch %PORT_CHANNEL-5-CREATED: port-channel 7 created

Jan 4 06:54:24 switch %PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel 7 is down (No operational members)

Jan 4 06:54:40 switch %PORT_CHANNEL-5-PORT_ADDED: e1/8 added to port-channel 7

Jan 4 06:54:56 switch %PORT-5-IF_DOWN_ADMIN_DOWN: Interface e1/7 is down (Admnistratively down)

Jan 4 06:54:59 switch %PORT_CHANNEL-3-COMPAT_CHECK_FAILURE: speed is not compatible

Jan 4 06:55:56 switch%PORT_CHANNEL-5-PORT_ADDED: e1/7 added to port-channel 7

switch#

Example 9-7 show logging logfile | grep Command

switch# show logging logfile | grep Vethernet3626

2011 Mar 25 10:56:03 n1k-bl %VIM-5-IF_ATTACHED: Interface Vethernet3626

is attached to Network Adapter 8 of gentoo-pxe-520 on port 193 of module

13 with dvport id 6899

2011 Mar 25 11:10:06 n1k-bl %ETHPORT-2-IF_SEQ_ERROR: Error ("Client data

inconsistency") while communicating with component MTS_SAP_ACLMGR for

opcode MTS_OPC_ETHPM_PORT_PRE_CFG (RID_PORT: Vethernet3626)

2011 Mar 25 11:10:06 n1k-bl %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface

Vethernet3626 is down (Error disabled. Reason:Client data inconsistency)

Example 9-8 show interface brief Command

switch# show int brief

--------------------------------------------------------------------------------

Port VRF Status IP Address Speed MTU

--------------------------------------------------------------------------------

management interface0 -- up 172.23.232.141 1000 1500

--------------------------------------------------------------------------------

Ethernet VLAN Type Mode Status Reason Speed Port

Interface Ch #

--------------------------------------------------------------------------------

Eth3/2 1 eth trunk up none 1000(D) --

Eth3/3 1 eth access up none 1000(D) --

switch#

Example 9-9 show interface ethernet Command

switch# show interface e1/14

e1/7 is down (errDisabled)

Example 9-10 show interface ethernet Command

switch# show interface eth3/2

Ethernet3/2 is up

Hardware: Ethernet, address: 0050.5653.6345 (bia 0050.5653.6345)

MTU 1500 bytes, BW -598629368 Kbit, DLY 10 usec,

reliability 0/255, txload 0/255, rxload 0/255

Encapsulation ARPA

Port mode is trunk

full-duplex, 1000 Mb/s

Beacon is turned off

Auto-Negotiation is turned off

Input flow-control is off, output flow-control is off

Auto-mdix is turned on

Switchport monitor is off

18775 Input Packets 10910 Unicast Packets

862 Multicast Packets 7003 Broadcast Packets

2165184 Bytes

6411 Output Packets 6188 Unicast Packets

216 Multicast Packets 7 Broadcast Packets 58 Flood Packets

1081277 Bytes

1000 Input Packet Drops 0 Output Packet Drops

1 interface resets

switch#

Example 9-11 show interface ethernet counters Command

switch# show interface eth3/2 counters

--------------------------------------------------------------------------------

Port InOctets InUcastPkts InMcastPkts InBcastPkts

--------------------------------------------------------------------------------

Eth3/2 2224326 11226 885 7191

--------------------------------------------------------------------------------

Port OutOctets OutUcastPkts OutMcastPkts OutBcastPkts

--------------------------------------------------------------------------------

Eth3/2 1112171 6368 220 7

Example 9-12 show interface vEthernet Command

switch# show interface veth1

Vethernet1 is up

Port description is gentoo1, Network Adapter 1

Hardware is Virtual, address is 0050.56bd.42f6

Owner is VM "gentoo1", adapter is Network Adapter 1

Active on module 33

VMware DVS port 100

Port-Profile is vlan48

Port mode is access

491242 Input Packets 491180 Unicast Packets

7 Multicast Packets 55 Broadcast Packets

29488527 Bytes

504958 Output Packets 491181 Unicast Packets

1 Multicast Packets 13776 Broadcast Packets 941 Flood Packets

714925076 Bytes

11 Input Packet Drops 0 Output Packet Drops

switch#

Example 9-13 show interface capabilities Command

switch# show interface capabilities

management interface0

Model: --

Type: --

Speed: 10,100,1000,auto

Duplex: half/full/auto

Trunk encap. type: 802.1Q

Channel: no

Broadcast suppression: none

Flowcontrol: rx-(none),tx-(none)

Rate mode: none

QOS scheduling: rx-(none),tx-(none)

CoS rewrite: yes

ToS rewrite: yes

SPAN: yes

UDLD: yes

Link Debounce: no

Link Debounce Time: no

MDIX: no

Port Group Members: none

port-channel1

Model: unavailable

Type: unknown

Speed: 10,100,1000,10000,auto

Duplex: half/full/auto

Trunk encap. type: 802.1Q

Channel: yes

Broadcast suppression: percentage(0-100)

Flowcontrol: rx-(off/on/desired),tx-(off/on/desired)

Rate mode: none

QOS scheduling: rx-(none),tx-(none)

CoS rewrite: yes

ToS rewrite: yes

SPAN: yes

UDLD: no

Link Debounce: no

Link Debounce Time: no

MDIX: no

Port Group Members: none

port-channel2

Model: unavailable

Type: unknown

Speed: 10,100,1000,10000,auto

Duplex: half/full/auto

Trunk encap. type: 802.1Q

Channel: yes

Broadcast suppression: percentage(0-100)

Flowcontrol: rx-(off/on/desired),tx-(off/on/desired)

Rate mode: none

QOS scheduling: rx-(none),tx-(none)

CoS rewrite: yes

ToS rewrite: yes

SPAN: yes

UDLD: no

Link Debounce: no

Link Debounce Time: no

MDIX: no

Port Group Members: none

port-channel12

Model: unavailable

Type: unknown

Speed: 10,100,1000,10000,auto

Duplex: half/full/auto

Trunk encap. type: 802.1Q

Channel: yes

Broadcast suppression: percentage(0-100)

Flowcontrol: rx-(off/on/desired),tx-(off/on/desired)

Rate mode: none

QOS scheduling: rx-(none),tx-(none)

CoS rewrite: yes

ToS rewrite: yes

SPAN: yes

UDLD: no

Link Debounce: no

Link Debounce Time: no

MDIX: no

Port Group Members: none

control0

Model: --

Type: --

Speed: 10,100,1000,auto

Duplex: half/full/auto

Trunk encap. type: 802.1Q

Channel: no

Broadcast suppression: none

Flowcontrol: rx-(none),tx-(none)

Rate mode: none

QOS scheduling: rx-(none),tx-(none)

CoS rewrite: yes

ToS rewrite: yes

SPAN: yes

UDLD: yes

Link Debounce: no

Link Debounce Time: no

MDIX: no

Port Group Members: none

switch#

Example 9-14 show interface virtual port-mapping Command

switch# show interface virtual port-mapping

-------------------------------------------------------------------------------

Port Hypervisor Port Binding Type Status Reason

-------------------------------------------------------------------------------

Veth1 DVPort5747 static up none

Veth2 DVPort3361 static up none

switch#

Example 9-15 module vem execute vemcmd show portsec status Command

cyp1-switch# module vem 3 execute vemcmd show portsec status

LTL if_index Max Aging Aging DSM Sticky VM

Secure Time Type Bit Enabled Name

Addresses

56 1c0000a0 5 0 Absolute Clr No Ostinato-Upgrade-VM1.eth1

Example 9-16 show port-security Command

switch# show port-security

Total Secured Mac Addresses in System (excluding one mac per port) : 0

Max Addresses limit in System (excluding one mac per port) : 8192

----------------------------------------------------------------------------

Secure Port MaxSecureAddr CurrentAddr SecurityViolation Security Action

(Count) (Count) (Count)

----------------------------------------------------------------------------

Vethernet1 1 0 0 Shutdown

==========================================================================

Example 9-17 show port-security address interface vethernet Command

switch# show port-security address interface vethernet 11

Secure Mac Address Table

----------------------------------------------------------------------

Vlan/Vxlan Mac Address Type Ports Configured Age

(mins)

---------- ----------- ------ ----- ---------------

50 0050.56a4.38ec STATIC Vethernet11 0

50 0000.0000.0011 DYNAMIC Vethernet11

Bias-Free Language

Results

Chapter: Ports

Ports

Information About Ports

Information About Interface Characteristics

Information About Interface Counters

Information About Link Flapping

Information About Port Security

Port Diagnostic Checklist

Problems with Ports

Cannot Enable an Interface

Port Link Failure or Port Not Connected

Link Flapping

Port ErrDisabled

VM Cannot Ping a Secured Port

Port Security Violations

Port State is Blocked on a VEM

Port Troubleshooting Commands

EXAMPLES

Was this Document Helpful?

Contact Cisco