Packet-buffer Error Detected On
Contents |
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Parity Errors Troubleshooting Guide Download Print Available what is parity error Languages Download Options PDF (259.4 KB) View with Adobe Reader
Parity Error Cisco
on a variety of devices Updated:Jul 15, 2013 Document ID:116135 Document ID: 116135 Updated: Jul 15, parity error fix 2013 Contributed by Shawn Wargo, Cisco Engineering. Download PDF Print Feedback Related ProductsCisco Catalyst 6500 Series Switches ContentsIntroductionBackgroundSoft ErrorsHard ErrorsCommon Error MessagesProcessorRAMASICLatest AdvancementsProcessorRAMASICSoftwareMSFC
System Returned To Rom By Processor Memory Parity Error At Pc
IBC Reset6700 Series 'Single-Bit Parity Error' ResetRecommendationsSoft Errors (SEU)Environmental AuditLatest Firmware (Rommon)Thumb ScrewsHard Errors (Malfunction)Hardware (MTBF and EOL) AuditHardware DiagnosticsRelated Cisco Support Community DiscussionsIntroductionThis document describes soft and hard parity errors, explains common error messages, and recommends methods that help you avoid or minimize parity errors. Recent improvements in hardware and parity error detected in vram software design reduce parity problems as well. BackgroundWhat is a processor or memory parity error?Parity checking is the storage of an extra binary digit (bit) in order to represent the parity (odd or even) of a small amount of computer data (typically one byte) while that data is stored in memory. The parity value calculated from the stored data is then compared to the final parity value. If these two values differ, this indicates a data error, and at least one bit must have been changed due to data corruption.Within a computer system, electrical or magnetic interference from internal or external causes can cause a single bit of memory to spontaneously flip to the opposite state. This event makes the original data bits invalid and is known as a parity error.Such memory errors, if undetected, may have undetectable and inconsequential results or may cause permanent corruption of stored data or a
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, 3000W power supplies, sup 1-A's. A couple months
Imprecise Data Parity Error
ago we had a bank of 12 ports fail in slot 5. The
High Correctable Ecc Error Rate Detected Cisco
switch was still under warranty from the used hardware reseller, so the blade was replaced. Thought it was a a parity error checking bad refurb. Now again, a blade in slot 7 just had a bank of 12 ports fail. Just like before, the interfaces show (err-disabled). You can do a shut/no shut and it http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116135-trouble-6500-parity-00.html 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. 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 http://www.gossamer-threads.com/lists/cisco/nsp/44677 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, may be privileged and should be read and retained only by the intended recipient without further distribution. If you received this transmission in error, please notify the sender and delete it from your system immediately. _______________________________________________ cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ds at
Dynamic Port VLAN Membershippage 570................................................................................................................................................................ Troubleshooting the ASLB Configurationpage 1381................................................................................................................................................................ Print This PagePrint ShareShare Url of this page: HTML Link: Bookmark Manuals Brands Cisco Manuals Network Router WS-C6506 Software manual Cisco WS-C6506 Software Manual: Configuring Packet-buffer Error Handling; Configuring Etherchannel/link Error Handling Software guide. Hide thumbs Also See for WS-C6506 Manual - 110 pagesInstallation manual - 336 pages 109 http://www.manualslib.com/manual/455877/Cisco-Ws-C6506.html?page=600 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 https://puck.nether.net/pipermail/cisco-nsp/2010-August/072753.html 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 parity error 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 packet-buffer error detected 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 5
] [ 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