Vm Cannot Ping A Secured Port - Cisco Nexus 1000V Troubleshooting Manual

Problems with Ports
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
Table 8-4
Possible Cause
You attempted to add a port
to a port channel that was
not configured identically;
and the port is then
errdisabled.
VSM application error

VM Cannot Ping a Secured Port

Use these troubleshooting guidelines when you cannot ping a secured port from a VM.
Table 8-5
Possible Cause
The vEthernet interface is
not up.
Drop on Source Miss
(DSM) is set.
New MAC addresses
cannot be learned by this
port.
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
8-6
Troubleshooting error disabled ports (continued)
Solution
Display the switch log file and identify the exact configuration error
1.
in the list of port state changes.
show logging logfile
Correct the error in the configuration and add the port to the port
2.
channel.
Re-enable the port.
3.
shut
no shut
Identify the component which errored while bringing up the port.
1.
show logging logfile | grep interface_number
See Example 8-7 on page
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
Support" section on page
Troubleshooting VM Cannot Ping a Secured Port
Solution
Verify the state of the vEthernet interface.
1.
show interface vethernet number
2. If the interface is down, enable it.
shut
no shut
Verify the port security configuration.
1.
module vem 3 execute vemcmd show portsec stats
If DSM is set, clear the DSM bit on the VSM.
2.
no port-security stop learning
8-11.
"Before Contacting Technical
27-1.
Chapter 8 Ports
OL-28795-01