3com switches and memory leaks

[infocus]

I look after a small site of some 40 3com switches. They are spread over some 10 sites the larger being a stack of 19 connected via 2 * 2 gig trunks from the LAN to 2 3900's. The switches are in 2 stacks connected via crossovers, 3 switches connected from 1 3900 at 200mb, with the remainder at 100meg from the same 3900.

The problem is users compalin of slowdowns. Some bright spark has suggested that rebooting the switches resolves the problem, which it does, and blames the switches. - Memory Leaks. Personall I believe it is bandwidth issue which turning off the switch resolves because the traffic what ever it is is stopped and life then returns to normal.

Anyone any ideas

 

[J007ST]

The following came from 3COM's knowlede.3com.com

SolutionID: 2.0.73093632.3227756 Title: SuperStack 3 Switch 4400

- Why does the Switch reset on a network with significant unregistered IP multicast traffic.

Goal Why does the Switch reset on a network with a significant unregistered IP multicast traffic Fact SuperStack 3 Switch 4400 Fact 3C17203 Fact Agent code v1.04

Fact 3C17203

Fact IGMP Fact IGMP snooping is enabled on the switch
Symptom After the switch has been running for a significant period of time the unit resets Symptom Switch resets on a network with significant unregistered IP multicast traffic Cause When a large number of IP multicast packets are received by the switch, its internal memory allocation can be disrupted sufficiently to cause its normal operations to become disrupted. The switch resets under these conditions to recover normal working. The time it takes before a reset occurs under these circumstances depends on the rate at which IP multicasts are received. The problem only occurs if the multicasts have not been registered by an endstation using the IGMP protocol and whan an abnormal level of unregistered IP multicast traffic is present on the network.

Fix If running v1.04 of the agent, disable the IGMP snooping feature. Fix Upgrade to v1.05 of the agent code. This contains a complete fix for the problem. Fact Search group - SuperStack 3 Switches
Fact Last Reviewed: November 2001