What version of code is running on the switch. You might be hitting CSCee10005. The workaround is to use a default-gateway on the same subnet, but on a different device (i.e. not an interface on the 6509).
I'm running 12.2(18)SXF9. It's not possible for me to use a default-gateway on a different device. The 6509 is the VTP server and the devices on the other end are clients. I'll just have to schedule downtime to upgrade. Thanks.
If you are hitting this bug, CSCee10005, then you need to be running a fixed version of code, then you need to configure the command:
fabric switching-mode force bus-mode
This will force the NAM to use bus-mode switching instead of fabric switching, and should resolve the connectivity problems. The workaround is configure an external default gateway on the NAM (i.e. not the switch in which the NAM is located).
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...