Preview Tool

Cisco Bug: CSCuq61825 - Nexus3500: Packet received on access vPC port w/ vlan id 0 not processed

Last Modified

Nov 27, 2020

Products (2)

  • CiscoPro Workgroup EtherSwitch Software
  • Cisco Nexus 3548 Switch

Known Affected Releases

6.0(2)A3(2.68) 6.0(2)A4(1)

Description (partial)

The Cisco Nexus 3500 does not process the packets received on an access vPC port. This happens only when a dot1q header with VLAN id as 0 is received.

The port is in access port, and part of a vPC.
Issue is seen in 6.0(2)A3 releases.

Related Community Discussions

Unable to ping devices directly connected to Nexus 3548
We have a Nexus 3548 switch that is the top of rack switch for our new flexpod. I'm trying to get our existing network to see the new subnets. I have setup a trunk port on the Nexus 3548 and on our Small business series Cisco switch. The Nexus can ping all of the new and old network including devices directly connected to it. When I try and ping devices on the Nexus (i.e. the NetApp, UCS, etc) I cannot. When I do a tracert form the pc on the old network to the nexus it shows me getting to the Nexus ...
Latest activity: Sep 09, 2014
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.