I have a network consisting of a 4006 SupeII w/ L3 Module in the Core, connected to Cat 3548-XLs via 2-Gbps Etherchannel Trunk at aggregation points which then connect to a mix of 2950s and 3500-XLs gigastacks connecting via 200-Mbps etherchannel. I have two gigastacks of 2950s and two gigastacks of 3548s at the access layer.
Each floor in the building is on its own VLAN (total of four), with the servers isolated on their own VLAN and attached to the 4006.
Recently, the users have been complaining of network slowness. Specifically, opening word documents off of the server take longer than expected for a reasonable file size or applications hang for a period of time and come back. Everytime I try to capture the problem on a Sniffer, the end-user is not able to recreate the problem - so the problem is sporadic but significant enough for users to complain.
The complaints seem to have begun around the time I began introducing the 2950s or when I upgraded the 2950s to 12.1.9.EA1d.
I wonder if anyone else has had any issues mixing the 2950s and 3500s in their network? I generally like to keep everything standardized, but with Cisco issuing an EOS on the 3548s, I immediately moved to the 2950-48s as a replacement.
I unfortunately don't have an answer for your question. However, I do have a similar problem. I have mostly 3Com hubs and I am gradually moving over to Cisco switches. I have put in a 2950T switch and as soon as I move anyone to that switch their network connection seems to just crawl. I move their connection back and it works just fine. I look at the web admin interface for the switch and there are absolutely no errors on the switch or on the port the person is connected to. I really can't figure out what is going on here. Please let me know if you have any solution to your problem with the 2950.
[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...