On 04/12/2007, Clinton Work <[EMAIL PROTECTED]> wrote: > > Is the new backup link just a dark fiber connection between the two > boxes? From the error message it looks like the frames are being > seriously corrupted at some point and that is causing the problems. > > The SPANTREE-SP-2-RECV_PVID_ERR error message indicates that the PVST+ > BPDU for vlan 53 was received on vlan 55. Looking at your configuration > I don't see how this is possible. I have seen some strange behavior > with faulty Supervisors, but nothing like this.
It is a copper SFP (cisco branded) in both 6500s. and just a piece of cable between them. And yes, we've tried different cables ;-) @noble.tn 6500-2: Name: Gi1/48 Switchport: Enabled Administrative Mode: trunk Operational Mode: down Administrative Trunking Encapsulation: dot1q Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk private VLANs: none Operational private-vlan: none Trunking VLANs Enabled: 30,48-63,70,80,81 Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Unknown unicast blocked: disabled Unknown multicast blocked: disabled and 6500-1: Name: Gi1/38 Switchport: Enabled Administrative Mode: trunk Operational Mode: down Administrative Trunking Encapsulation: dot1q Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Voice VLAN: none Administrative private-vlan host-association: none Administrative private-vlan mapping: none Administrative private-vlan trunk native VLAN: none Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none Administrative private-vlan trunk private VLANs: none Operational private-vlan: none Trunking VLANs Enabled: 30,48-63,70,80,81 Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL Unknown unicast blocked: disabled Unknown multicast blocked: disabled sh vlan brief doesn't show anything usefull (the same on both of them): 6500-1: VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Gi1/18, Gi1/20, Gi1/22, Gi1/38, Gi1/48 30 Legacy_Filer active 48 vip-int active 49 filter-pub active 50 filter-cust active 51 smtpin active 52 smtpout active 53 smtpoutslow active 54 smtpbounce active 55 smtpreply active 56 smtplist active 57 maildrop active 58 mailbox active 59 webmail active 60 spare60 active 61 ldap active 62 database active 63 dns active 70 EMC_Filer active 80 vip-pub active 81 host-out active 1002 fddi-default act/unsup 1003 token-ring-default act/unsup 1004 fddinet-default act/unsup 1005 trnet-default act/unsup and 6500-2: VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Gi1/18, Gi1/20, Gi1/43, Gi1/46, Gi1/48 30 Legacy_Filer active 48 vip-int active 49 filter-pub active 50 filter-cust active 51 smtpin active 52 smtpout active 53 smtpoutslow active 54 smtpbounce active 55 smtpreply active 56 smtplist active 57 maildrop active 58 mailbox active 59 webmail active 60 spare60 active Gi1/41, Gi1/44 61 ldap active 62 database active 63 dns active 70 EMC_Filer active 80 vip-pub active 81 host-out active 1002 fddi-default act/unsup 1003 token-ring-default act/unsup 1004 fddinet-default act/unsup 1005 trnet-default act/unsup kind regards pshem _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
