i'm trying to find the cause of my 4500 reloading - the crashdump shows:
Nov 28 11:29:19: %C4K_SWITCHINGENGINEMAN-3-PPECELLDUPDETECTED: Free cell duplicate(s) detected 5343. System will be reset
however when i try and use the output interpretor for the stack decode i get an error msg:
ERROR: Traceback information was not found.
In order to decode the Traceback information, the Stack Decoder requires the platform
and version information to be present in the output and precede any Tracebacks
or Stack Traces.
TRY THIS: Collect the output of the 'show version' command, and the Traceback or
Stack Trace information and submit it to the Output Interpreter.
Here is an example of a Traceback output with version information:
Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-PV-M), Version 12.0(19)S2, EARLY DEPLOYMENT RELEASE
TAC Support: http:www.cisco.comtac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sat 02-Feb-02 21:27 by dchih
Image text-base: 0x60010968, data-base: 0x60DAE000
Traceback= 0x60251F84 0x60254820 0x60250A58 0x602549F0 0x60257E0C
0x601E6B8C 0x601E6C38 0x6015332C 0x60153500 0x601CC454 0x601CC440
NOTE: Stack Trace information or Alignment Data can be substituted for the Traceback
"C4K_SWITCHINGENGINEMAN-3-PPECELLDUPDETECTED" prior to switch reboot
indicates software has detected duplicate packet cell in PPE freelist
The PPE freelist tracks all free and available packet cells whose buffers
can be used for incoming packets. Software detects cell duplication and
resets the box to avoid corruption in the packet cell freelist.
The decision to have the switch reset is done because duplicate cells on the
freelist causes further freelist corruption resulting in weird packet
processing behaviors, packet errors and packet buffer leaks which can
eventually lead to stoppage of all packet switching through the box.
For the ASIC on this SUP, duplicate cells can sometimes appear on the
freelist as a result of a parity error in this memory. This has generally
been found to be a very rare occurrence and was not found by development to
occur more than once on any SUP.
Thus, it is recommended that the switch be left running in a monitoring
status. If the problem is seen further, it is likely the SUP is becoming
faulty and would require replacement.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...