Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5500G Core with Stacks of 4500/50

Status
Not open for further replies.

tundra9

Technical User
Nov 14, 2006
2
CA
Hi, new to this forum, but hope you can help. I have a core 5500G 26 port switch doing L3 routing. It has an 8Port gig module in back connecting (6) stacks fo 4500/50 switches. I have a couple of problems,

1) a short while ago I lost the ability to see ALL of the learned MAC addresses in my stacks. (all but one). when i use this command i get all of the addresses in switch 1 of the stack and the odd address from the others. I had taken a stack as an example and rebooted it. I saw everything, but within a couple of minutes, I was back to the same result. OS version is the same and up to date on all switches.
2) I am seeing input errors on the fabric interfaces within stacks. no output errors. traffic is relatively light, so not sure why we are seeing this. in some cases the % of errors is quite high. the switches are connected within the stack using SFP modules.

Any insight or thoughts would be appreciated.

Thanks

 
FYI for you, I did get a response from 3Com on the Input errors and wanted to share with you.

here is the offical response....

Problem Giant errors incrementing on XRN uplink ports

Fact Switch 4500

Fact Switch 4500 26-Port

Fact

Switch 4500 50-Port



Fact Switch 5500-SI 28-Port

Fact Switch 5500-SI 52-Port

Fact giant counter incrementing

Fact Jumbo packets incrementing giant counter

Fact input error total

Cause

The giant count will increment for packets larger than 1522 bytes for a
standard LAN port.

If a packet length of 1515 - 1518 bytes must traverse an XRN port, 4
bytes are added for VLAN tag information and 4 bytes for special XRN
processing, exceeding the 1522 packet size, which will increment a giant
counter.

Giants are mistakenly counted in the "input error" total and they
shouldn't be, as they are not errored packets, just ones greater than
the Standard Ethernet maximum.



Fix This is working as designed.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top