I have several 3548's connected via FEC to my 6509. All these ports are trunking and all setup as channels and configured properly on the 6509 and each 3548. Just yesterday 1 user complained about having issues staying connected to a server. I started to do a continious ping to his system and noticed many time outs. On the switch 3548 that his is connected to, I removed the port group command on the 3548 and the 6509 and this fixed the issue. Could there be a possible loop somewhere on one of the 3548 ports? Need some troubleshooting guidance. Thank you
Etherchannel can definitely be the source of loops if it's misconfigured. You can get 2 ports channeling on 1 side, and 1 on the other, creating a virtual unidirectional link. For this reason, if you must use Etherchannel, use the desirable mode on both sides. Consider utilizing 802.1w instead of Etherchannel if you are looking for redundancy instead of bandwidth, the failover and restore times are roughly 2 seconds.
I don't think it is misconfigured, I have several other 3548's connected to my 6509 configured exactly the same, and I am not having any issues with these switches. The config is exactly the same on all 3548's, as well as the other ports on the 6509. I do have ports on both sides set as trunk ports set to dot1q. I will into 802.1w. I am using these links more as bandwidth than redundancy. Do you have any links for configuring 802.1w? Thanks.
I totally missed the fact that you are running with 3548s. Unfortunately the 3500XLs don't support PAgP, which is what desirable mode requires. You have to use the "on" mode which is unconditional port channeling, which leads to a large number of misconfigured loops.
Make sure your ports and interfaces are configured identically. Even a difference in QoS configs can bring one port out of the channel on one end.
I'd also suggest enabling UDLD to ensure there are no unidirectional links.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...