as far as i know, you cannot do cross switch teaming on these standalone switches. Check the server if it is set to active/active in teaming configuration then you do have network loop/ spanning tree issue.
try changing to your server team as active/standby and that may help.
You may need to disconnect one of the teamed nic from the switch as your switches are seeing same mac address on 2 different switches.
For teaming to work as active/active, You have to use Chassis and plug each server nic into different blade slots, or you can use 3750 switches if they are stacked.
There are no issues with any clients running any OS when connected to any network appliance. If the you have observed that the switch is undergoing high CPU utilization, you should consider investigating where this issue is coming from. Do you have a loop issue? Have you tried moving the servers somewhere else? Are there any line errors on the switch ports?
The 3500XL's weakness is the lack of auto-negotiation capabilities. So speed/duplex can be a trial-and-error. Have you checked that end?
[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...