Po1 is the root port. G0/16 is an âupâ access port. Po2 is a trunk to another access layer switch at the same level. Po2 spends its time in blocking state on the other switch. This switch prunes most VLANs off Po2.
Now let us look at the trunks:
CC80#show int trunkPort Mode Encapsulation Status Native vlan
Gi0/3 on 802.1q trunking 2
Po1 on 802.1q trunking 12
Po2 on 802.1q trunking 12Port Vlans allowed on trunk
Po2 1-2,5,12,21-26,169Port Vlans allowed and active in management domain
Po2 1-2,5,12,21-26,169Port Vlans in spanning tree forwarding state and not pruned
As expected, most of the VLANs are pruned off Po2 as te other end of Po2 is on STP blocking state. Ignore G0/3; this is a server trunk. The interesting thing is that the switch has pruned VLAN 21 from the root port trunk, Po1. Why? This has effectively cut this switch off from VLAN 21.
VLAN 21 is pruned from both Po1 and Po2, and yet it has an access port on it. Now, that access port, G0/16, is apparently not receiving any MAC traffic from its connected host. There is nothing in the CAM table except the upstream switch. But it is still isolated, so it cannot see any traffic from the remote part of the VLAN, so it does not respond:
CC80#show mac-address-table dyn vlan 21
Mac Address Table
-------------------------------------------Vlan Mac Address Type Ports
---- ----------- -------- -----
21 0016.c73d.a22b DYNAMIC Po1
Total Mac Addresses for this criterion: 1
One last possible clue. We have four VLANs, each with two host connections. Two of them work, two of them don't. The difference is that they take different paths. Two of them are rooted on a 4506 running IOS 12.2(25)EWA2, and they work; they are not pruned anywhere between the two sites. The two that do not work are rooted on a 4003 running CatOS 8.4(5)GLX.
Thanks for looking at the output from the switches. I think I have sorted it out, and I think it is a bug in the root switch for VLAN 21. Unlike our other VLANs, VLAN 21 is rooted in a CatOS switch. Due to various circumstances in our network, it tripped over a bug.
The bug is related to one I found a couple of years ago. I found that in a CatOS switch, if you manually disallow the native VLAN (in my case VLAN 12) from a trunk, then it stops the trunk passing BPDUs for VLAN 1 as well. At the time, that resulted in a 5-minute meltdown of my network.
Here are the notes I have made for this new bug. Sorry about the generalisations ... I do not know the VTP protocol very well yet.
Normally, VTP signalling is carried on the native VLAN of each trunk. By default, the native VLAN is VLAN 1, but you are allowed other values. We use VLAN 12 as native, a VLAN that is unused anywhere on the network. Now, an IOS switch will never prune VLAN 1 from a trunk. Nor will it prune the native VLAN. However, CatOS has a bug: if the (non-1) native VLAN is unused, it will prune it from the trunk regardless of the fact that it is the native. Once the native VLAN is pruned, of course, the VTP signal cannot be propagated to other switches.
It happens that we have one CatOS siwtch in our core loop. That switch is the root for VLANs 21 and 23. (And fortunately only for VLANs 21 and 23.) Because that root switch had pruned the native VLAN from its trunks, it was no longer able to send VTP unprune signals for VLANs 21 and 23 to its neighbors. Its neighbors therefore pruned VLANs 21 and 23 from the trunks to the root. The result was that there was no connectivity in VLANs 21 and 23, and every switch pruned all ports on those VLANs.
I resolved the problem by rolling back the VTP pruning.
I hope this makes sense. If FranÃ§ois Tallet ses this posting, I wonder if you could comment please FranÃ§ois?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...