13-2
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 13 VLANs
Initial Troubleshooting Checklist
•
A private VLAN host or promiscuous port cannot be a SPAN destination port. If you configure a
SPAN destination port as a private VLAN port, the port becomes inactive.
•
A destination SPAN port cannot be an isolated port. (However, a source SPAN port can be an
isolated port.)
•
SPAN could be configured to span both primary and secondary VLANs or to span either one if the
you are is interested only in ingress or egress traffic.
•
A MAC address learned in a secondary VLAN is placed in the shared table of the primary VLAN.
When the secondary VLAN is associated to the primary VLAN, their MAC address tables are
merged into one, shared MAC table.
Initial Troubleshooting Checklist
Troubleshooting a VLAN problem involves gathering information about the configuration and
connectivity of individual devices and the entire network. In the case of VLANs, begin your
troubleshooting activity as follows:
The following CLI commands are used to display VLAN information:
•
show system internal private-vlan info
•
show system internal private-vlan event-history errors
•
show system internal private-vlan event-history traces
•
show vlan id
vlan-id
•
show vlan private-vlan
•
show vlan all-ports
•
show vlan private-vlan type
•
show vlan internal bd-info vlan-to-bd 1
•
show vlan internal errors
•
show vlan internal info
•
show vlan internal event-history errors
Checklist
Verify the physical connectivity for any problem ports or VLANs.
Verify that both end devices are in the same VLAN.