Packet-buffer Error Detected Cisco
Contents |
Cisco Bug: CSCsh02049 - Linkdown traps not generated when ports go to err-disabled state Last Modified Sep 18, 2015 Product Cisco Catalyst 6000 Series what is parity error Switches Known Affected Releases 12.2(18)SXF2 Description (partial) None Symptom: linkDown traps not parity error cisco generated when ports on a WS-X6148-RJ-45 module go to err-disabled state. Conditions: A transient parity error on a WS-X6148-RJ-45
Parity Error Fix
module in a catalyst 6500 running 12.2(18)SXF2, may cause packet buffer errors on all ports on the module, putting them in err-disabled state. No linkDown traps are issued when this
System Returned To Rom By Processor Memory Parity Error At Pc
occurs. %EARL_L3_ASIC-SP-STDBY-3-INTR_WARN: EARL L3 ASIC: Non-fatal interrupt Packet Parser block interrupt %PM-SP-STDBY-4-ERR_DISABLE: packet-buffer error detected on Fa7/1, putting Fa7/1 in err-disable state View Bug Details in Bug Search Tool Why Is Login Required? Bug details contain sensitive information and therefore require a Cisco.com account to be viewed. Bug Details Include Full Description (including symptoms, conditions and workarounds) Status Severity Known Fixed parity error detected in vram Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials and Mining Public Sector Retail Smart+Connected Communities Sports and Entertainment Transportation Workspace Transformation Marketplace Contacts Contact Cisco Meet our Partners Find a Reseller News & Alerts Newsroom Blogs Field Notices Security Advisories Technology Trends Cloud Internet of Things (IoT) Software Defined Networking (SDN) Support Downloads Documentation Communities DevNet Learning Network Support Community Video Portal Certifications Events Industries Inside Cisco Products Service Provider Services Technology Trends TechWiseTV About Cisco Investor Relations Corporate Social Responsibility Environmental Sustainability Trust and Transparency Center The Next Wave of The Internet Our People Careers Search Jobs Life at Cisco Programs Cisco Designated VIP Program Cisco Powered Financing Options Contacts Feedback Help Site Map Terms & Conditions PrivacyPrivacy Statement CookiesCookie Policy Trademarks
Post #1 of 3 (5312 views) Permalink WS-X6348-RJ45V ports failing We have a 6509 with 4 - WS-X6348-RJ45V PoE 10/100 blades,
High Correctable Ecc Error Rate Detected Cisco
3000W power supplies, sup 1-A's. A couple months ago we had a imprecise data parity error bank of 12 ports fail in slot 5. The switch was still under warranty from the used parity error checking hardware reseller, so the blade was replaced. Thought it was a a bad refurb. Now again, a blade in slot 7 just had a bank of 12 ports fail. https://quickview.cloudapps.cisco.com/quickview/bug/CSCsh02049 Just like before, the interfaces show (err-disabled). You can do a shut/no shut and it will work for a minute or so, then the led indicators go orange. Cisco 7940 IP phones run off this switch. IOS Version 12.1(26)E4, RELEASE SOFTWARE (fc1). Anyone seen this before? Have we just run into a bad batch of refurbished equipment? Thanks. http://www.gossamer-threads.com/lists/cisco/nsp/44677 FastEthernet7/15 is up, line protocol is down (err-disabled) Hardware is C6k 100Mb 802.3, address is 0001.9757.a5ae (bia 0001.9757.a5ae) MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Full-duplex, 100Mb/s input flow-control is off, output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 08:45:21, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 4533321 packets input, 981795181 bytes, 0 no buffer Received 162285 broadcasts (152148 multicast) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 36272200 packets output, 4303887531 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets John Kienzle CONFIDENTIALITY NOTICE: This e-mail transmission, along with any attachment, is confidential, m
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help https://www.experts-exchange.com/questions/27978011/Cisco-6509-err-disabled.html Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Cisco 6509 err-disabled Want to Advertise Here? Solved Cisco 6509 err-disabled https://puck.nether.net/pipermail/cisco-nsp/2010-August/072753.html Posted on 2012-12-26 Network Operations Networking Hardware-Other Switches / Hubs 1 Verified Solution 8 Comments 1,577 Views Last Modified: 2013-01-03 we have recently had issues with our 6509 were about 12 ports in our blade went parity error in to err-disabled mode. for some reason the syslog didn't give me much info. I have to give an explaination on how this happened. I figured it has to deal with excessive collisions on the back plane, that why all the ports went in to err-disabled mode at the same time? but i have no proof of this. I brought the ports down and back up and it brought them out of packet-buffer error detected err-disabled mode. but im hessitent to plug any servers in to those ports. the chaise is around 8 years so they are defiantly dated.. any theories and thoughts are always welcome 0 Question by:mattlast Facebook Twitter LinkedIn Google LVL 20 Best Solution byrauenpc Bummer on the timestamps. I've seen these before, and we ended up getting the module replaced via TAC RMA. We had dozens of the same line cards in our data center that ended up getting replaced for this Go to Solution 8 Comments LVL 24 Overall: Level 24 Switches / Hubs 11 Networking Hardware-Other 7 Network Operations 6 Message Active 3 days ago Expert Comment by:Ken Boone CCIE #46492012-12-26 Well don't know why, but if you plug something into those ports and those ports go err-disabled, it will show a log message as to why the port went err-disabled. So unless you plug something in to those ports and watch the logs you probably won't know why they went err-disabled. 0 LVL 10 Overall: Level 10 Network Operations 2 Switches / Hubs 1 Networking Hardware-Other 1 Message Expert Comment by:akhalighi2012-12-26 do you have port security enabled ? this usually happens if port security is configured and triggered . any recent acclivity that could change MAC addresses ? ( e.
] [ subject ] [ author ] hi Arie we made the hard reset and the logs still appear so TAC informed us that the module is faulty and we ordered a new one Thanks a lot for your help Regards, Mohammad Khalil > Subject: RE: [c-nsp] Cisco CISCO7606-S Module > Date: Sun, 22 Aug 2010 15:37:16 +0200 > From: avayner at cisco.com > To: eng_mssk at hotmail.com; cisco-nsp at puck.nether.net > > Mohammad, > > This could be (after a very quick query) related to CSCef46923 "Group of > 4 ports on WS-X6516-xx modules may stop forwarding traffic" > > These are the release notes: > PROBLEM/SYMPTOMS > ================ > Under very rare conditions, a group of ports on the same port-ASIC may > experience connectivity issue. This issue can occur on any module which > uses the same port-ASIC as WS-X6516-GE-TX. > > The following syslog messages might also be seen, but is not required to > observe the issue. > > %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 4 is experiencing the following > error: > Pinnacle #0, Frames with Bad Packet CRC Error (PI_CI_S_PKTCRC_ERR - > 0xC7) = > 110 > > > Syslog Messages update (3/14/05) > ========================================== > > Examples of Syslog message from IOS: > ______________________________________________________________ > %PM_SCP-SP-2-LCP_FW_ERR_INFORM: Module 5 is experiencing the following > error: > PINNACLE Pb transient parity error detected : ports - 1 3 5 7 > > %PM_SCP-SP-2-LCP_FW_ERR_INFORM: Module 5 is experiencing the following > error: > Bus Asic #1 transient Pb error. Recovered. (0x1234, 0x5678) > > > Examples of Syslog message from CatOS: > ______________________________________________________________ > > %SYS-3-PKTBUFFERFAIL_ERRDIS:Packet buffer failure detected. > Err-disabling > port 5/5. > > %SYS-3-PKTBUFFERFAIL_PWRCYCLE:Packet buffer failure detected. Power > cycling > module 5. > > ______________________________________________________________ > > Condition > ========= > The problem usually happens to a group of ports that are connected > through the same ASIC. > > WORKAROUND > ========== > The problem will usually recover after hard-reset the module. If the > problem > keeps happening on the same module, please contact TAC. > > > > > > > So, I would suggest you contact TAC for this... > Arie > > -----Original Message----- > From: cisco-nsp-bounces at puck.nether.net > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Mohammad Khalil > Sent: Sunday, August 22, 2010 10:26 > To: cisco-nsp at puck.nether.net > Subject: [c-nsp] Cisco CISCO7606-S Module