[c-nsp] Buffer Header Checksum Error

[Murphy, Jay, DOH]

A large amount of traffic may cause the bus ASIC to be flow-controlled. This situation improperly triggers a patch that causes the out-of-sync behavior. Bad port... is the port LED flashing an orange color, if an active link is present? If so, sounds like the port. Also a solid orange color can represent an over temperature condition has occurred, port fry. Use the show interface command for Cisco IOS to look for errdisable, disable or shutdown status. When you moved your cable, it may have proven out the port. Then use sh run interface fa or gi mod/port to check for shutdown.. 

 

 

~Jay Murphy 

IP Network Specialist

NM State Government

 

IT Services Division

PSB – IP Network Management Center

Santa Fé, New México 87505 

 

"We move the information that moves your world." 

“Good engineering demands that we understand what we’re doing and why, keep an open mind, and learn from experience.”

“Engineering is about finding the sweet spot between what's solvable and what isn't."

               Radia Perlman

 Please consider the environment before printing e-mail

 

 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Rick Kunkel
Sent: Thursday, June 10, 2010 10:53 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Buffer Header Checksum Error

 

Heya folks.... I've got a 3524 and 6509 connected, and all was looking 

good until we started running traffic between them...  Now I get this 

flapping thing going on, with a "Buffer Header Checksum Error" thing 

happening.  I can't find ANY references to this on Google or newsgroups, 

so I figured I'd ask here.

 

Here are the log entries.

 

Jun 10 09:35:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface 

FastEthernet3/2, changed state to down

 

Jun 10 09:35:04: %PM_SCP-SP-2-LCP_FW_ERR_INFORM: Module 3 is experiencing 

the following error: Port #2 Buffer Header Checksum Error

 

Jun 10 09:35:04: %LINK-3-UPDOWN: Interface FastEthernet3/2, changed state 

to down

 

Jun 10 09:35:04: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface 

FastEthernet3/2, changed state to down

 

Jun 10 09:35:04: %LINK-SP-3-UPDOWN: Interface FastEthernet3/2, changed 

state to down

 

Jun 10 09:35:06: %LINK-3-UPDOWN: Interface FastEthernet3/2, changed state 

to up

 

Jun 10 09:35:06: %LINK-SP-3-UPDOWN: Interface FastEthernet3/2, changed 

state to up

 

Jun 10 09:35:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface 

FastEthernet3/2, changed state to up

 

Jun 10 09:35:06: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface 

FastEthernet3/2, changed state to up

 

 

One minute later, the whole process starts again.

 

The OSs on the gear are as follows:

 

3524

c3500XL-c3h2s-mz-120.5.2-XU.bin

 

6509

s72033-ipservices_wan-mz.122-18.SXF11.bin

 

 

Any ideas?

 

Thanks much!

 

Rick

_______________________________________________

cisco-nsp mailing list  cisco-nsp at puck.nether.net

https://puck.nether.net/mailman/listinfo/cisco-nsp

archive at http://puck.nether.net/pipermail/cisco-nsp/

Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.