cisco 3845 router is restarting again and again

Shaikh Aman Uddin · ‎06-09-2011

Hi,

I am facing a issue on Cisco 3845 router, IOS is :c3845-adventerprisek9-mz.124-22.YB8.bin

I have changed the IOS as well as the Hardware but again the router is restarting. I have put the show tech-support and crash-info in Output interpreter, result is below:

Kindly advise:

============================================================================================================

ERROR MESSAGE NOTIFICATIONS (if any)

  %PAR-1-FATAL (x): [chars]

Explanation: A parity error has occurred. The problem might be caused either
by a motherboard that  has failed or motherboard settings that are incorrectly
set.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Also perform a search of the
Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still
require assistance, open a case  with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical
support  representative and provide the representative with the gathered information.
Attach the following to  your case in non-zipped, plain-text (.txt) format: the
output of the show logging and show  tech-support commands and your pertinent troubleshooting
logs.    PARSER Messages   The following are parser messages. %PAR-1-FATAL (x0): [chars]

Explanation: A parity error has occurred. The problem might be caused either
by a motherboard that  has failed or motherboard settings that are incorrectly
set.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Also perform a search of the
Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still
require assistance, open a case  with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical
support  representative and provide the representative with the gathered information.
Attach the following to  your case in non-zipped, plain-text (.txt) format: the
output of the show logging and show  tech-support commands and your pertinent troubleshooting
logs.    PARSER Messages   The following are parser messages. %CSM-1-NO_CHANNEL (x): [chars]

Explanation: No Signalling channels are available; all the channels are allocated

Recommended Action: This is a notification message. If the modems are not functional
or this message  appears frequently, copy the message exactly as it appears on
the console or in the system log.  Research and attempt to resolve the issue using
the tools and utilities provided at http://www.cisco.com/tac. With some messages,
these tools and utilities will supply clarifying  information. Search for resolved
software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%CSM-1-NO_CHANNEL (x0): [chars]

Explanation: No Signalling channels are available; all the channels are allocated

Recommended Action: This is a notification message. If the modems are not functional
or this message  appears frequently, copy the message exactly as it appears on
the console or in the system log.  Research and attempt to resolve the issue using
the tools and utilities provided at http://www.cisco.com/tac. With some messages,
these tools and utilities will supply clarifying  information. Search for resolved
software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%ALIGN-1-FATAL (x2): [chars]

Explanation: An alignment error has occurred. Alignment errors are caused by
misaligned reads and  writes. For example, a two-byte read of a memory address
that is not a multiple of two bytes is an  alignment error. Alignment errors are
caused by internal software failures. The system will be  reloaded, often with
a bus error.

Recommended Action: This message is caused by a software failure. To take advantage
of recent fixes,  upgrade your system to the latest Cisco  IOS software release
in your release train. If this message  recurs, copy the error message text exactly
as it appears on the console or in the system log, enter  the show log, show alignment
and show tech-support commands, contact your Cisco technical  support representative,
and provide the representative with the gathered information.%ALIGN-1-FATAL (x0): Illegal access to a low address

Explanation: An alignment error has occurred. Alignment errors are caused by
misaligned reads and writes. For example, a two-byte read of a memory address that
is not a multiple of two bytes is an alignment error. Alignment errors are c aused
by internal software failures. The system will be reloaded, often with a bus error.

Recommended Action: This message is caused by a software failure. To take advantage
of recent fixes, upgrade your system to the latest Cisco IOS software release in
your release train. If this message recurs, copy the error message text exactly
as it appears on the console or in the system log, enter the show log, show alignment
and show tech-support commands, contact your Cisco technical support representative,
and provide the representative with the gathered information.%ALIGN-1-FATAL (x0): [chars]

Explanation: An alignment error has occurred. Alignment errors are caused by
misaligned reads and writes. For example, a two-byte read of a memory address that
is not a multiple of two bytes is an alignment error. Alignment errors are caused
by internal software failures. The system will be reloaded, often with a bus error.

Recommended Action: This message is caused by a software failure. To take advantage
of recent fixes, upgrade your system to the latest Cisco IOS software release in
your release train. If this message recurs, copy the error message text exactly
as it appears on the console or in the system log, enter the show log, show alignment
and show tech-support commands, contact your Cisco technical support representative,
and provide the representative with the gathered information.  %XCPA-3-OUTHUNG (x): [chars] - output stuck - [chars]

Explanation: The channnel port adapter's transmit queue(s) contained packets
that have been queued  for an excessive period of time. A command will be sent
to the port adapter requesting dump  information. After that, the port adapter
will be reset.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-OUTHUNG (x0): [chars] - output stuck - [chars]

Explanation: The channnel port adapter's transmit queue(s) contained packets
that have been queued  for an excessive period of time. A command will be sent
to the port adapter requesting dump  information. After that, the port adapter
will be reset.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-RXQ (x): [chars] - consistency error - [chars] ([hex],[dec])

Explanation: Consistency check failed receiving packets from the channel port
adapter. The packet is  being dropped.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-RXQ (x0): [chars] - consistency error - [chars] ([hex],[dec])

Explanation: Consistency check failed receiving packets from the channel port
adapter. The packet is  being dropped.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-UCODEHDR (x): bay [[dec]] skip=[hex] hdr_ver=[hex] fw_rev=[hex]  req_hw_ver=[hex]
hw_type=[hex] description = [chars]

Explanation: The header information in the downloadable microcode file contains
incorrect  information. Other messages in the log specify what information is incorrect.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-UCODEHDR (x0): bay [[dec]] skip=[hex] hdr_ver=[hex] fw_rev=[hex]  req_hw_ver=[hex]
hw_type=[hex] description = [chars]

Explanation: The header information in the downloadable microcode file contains
incorrect  information. Other messages in the log specify what information is incorrect.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-UCODESEC (x): bay [[dec]] wcs=[hex] addr=[hex] len=[hex] ep=[hex] compr=[hex]
 sec_type=[hex] ver=[hex]

Explanation: The header information in a section of the downloadable microcode
file contains  incorrect information. Other messages in the log specify what information
is incorrect.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-UCODESEC (x0): bay [[dec]] wcs=[hex] addr=[hex] len=[hex] ep=[hex] compr=[hex]
 sec_type=[hex] ver=[hex]

Explanation: The header information in a section of the downloadable microcode
file contains  incorrect information. Other messages in the log specify what information
is incorrect.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-UNEXPECTEDINT (x): cause_lo=[hex], cause_hi=[hex], mask=[hex],  addr_dec_err=[hex],
bus_err=[hex], ch0_ctrl=[hex]

Explanation: An unexpected interrupt occurred.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-UNEXPECTEDINT (x0): cause_lo=[hex], cause_hi=[hex], mask=[hex],  addr_dec_err=[hex],
bus_err=[hex], ch0_ctrl=[hex]

Explanation: An unexpected interrupt occurred.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%XCPA-3-XCPADRIVERKILL (x): Unexpected request to terminate: XCPA driver process
 ([chars])

Explanation: Unexpected termination of the xcpa driver process.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     XDR Messages %XCPA-3-XCPADRIVERKILL (x0): Unexpected request to terminate: XCPA driver process
 ([chars])

Explanation: Unexpected termination of the xcpa driver process.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     XDR Messages %FPGA_GE-3-RBD_ERROR (x): Interface [chars]: FPGA_GE unexpected RBD error

Explanation: The FPGA GE driver did not encounter EOF flag in Rx buffer descriptor
(RBD) ring.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at  http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FPGA_GE-3-RBD_ERROR (x0): Interface [chars]: FPGA_GE unexpected RBD error

Explanation: The FPGA GE driver did not encounter EOF flag in Rx buffer descriptor
(RBD) ring.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at  http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FPGA_GE-3-RX_INIT_FAIL (x): Interface [chars]: FPGA_GE Rx Init Failure error:
[chars]

Explanation: The FPGA GE driver could not complete the RX init successfully.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at  http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     FPM Messages   The following are the Flexible Packet
Matching (FPM) messages. %FPGA_GE-3-RX_INIT_FAIL (x0): Interface [chars]: FPGA_GE Rx Init Failure error:
[chars]

Explanation: The FPGA GE driver could not complete the RX init successfully.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at  http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     FPM Messages   The following are the Flexible Packet
Matching (FPM) messages. %CSM-3-TGRM_UPDATE_FAILURE (x): The trunk group resource manager failed to update
 channel status to [chars] for channel [chars]:[dec]:[dec]

Explanation: The Trunk Group Resource Management subsystem reported an internal
software error  after a channel status update was sent to it by CSM.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.    CSM_TGRM Messages   The following are Call Switching
ModuleTGRM messages. %CSM-3-TGRM_UPDATE_FAILURE (x0): The trunk group resource manager failed to update
channel status to [chars] for channel [chars]:[dec]:[dec]

Explanation: The Trunk Group Resource Management subsystem reported an internal
software error  after a channel status update was sent to it by CSM.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.    CSM_TGRM Messages   The following are Call Switching
ModuleTGRM messages. %CSM-3-TGRM_UPDATE_FAILURE (x0): The trunk group resource manager failed to update
 channel status to [chars] for channel [chars]:[dec]:[dec]

Explanation: The Trunk Group Resource Management subsystem reported an internal
software error  after a channel status update was sent to it by CSM.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.    CSM_TGRM Messages   The following are Call Switching
ModuleTGRM messages. %CSM-3-TGRM_UPDATE_FAILURE (x0): The trunk group resource manager failed to update
channel status to [chars] for channel [chars]:[dec]:[dec]

Explanation: The Trunk Group Resource Management subsystem reported an internal
software error  after a channel status update was sent to it by CSM.

Recommended Action: If this message recurs, copy the message exactly as it appears
on the console  or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided  at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying  information. Search
for resolved software issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.    CSM_TGRM Messages   The following are Call Switching
ModuleTGRM messages. %CSM_TGRM-3-UNEXPEVT (x): An Unexpected event was reported by the CSM-TGRM Interface
 service

Explanation: The system detected an internal software error. The interface service
between the Call  Switching Modules and Trunk group Resource Manager received an
event that is not valid.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     CSM_TRUNK_MGR Messages   The following are Call Switching
Module Trunk Manager messages. %CSM_TGRM-3-UNEXPEVT (x0): An Unexpected event was reported by the CSM-TGRM Interface
service

Explanation: The system detected an internal software error. The interface service
between the Call  Switching Modules and Trunk group Resource Manager received an
event that is not valid.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     CSM_TRUNK_MGR Messages   The following are Call Switching
Module Trunk Manager messages. %CSM_TGRM-3-UNEXPEVT (x0): An Unexpected event was reported by the CSM-TGRM Interface
 service

Explanation: The system detected an internal software error. The interface service
between the Call  Switching Modules and Trunk group Resource Manager received an
event that is not valid.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     CSM_TRUNK_MGR Messages   The following are Call Switching
Module Trunk Manager messages. %CSM_TGRM-3-UNEXPEVT (x0): An Unexpected event was reported by the CSM-TGRM Interface
service

Explanation: The system detected an internal software error. The interface service
between the Call  Switching Modules and Trunk group Resource Manager received an
event that is not valid.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     CSM_TRUNK_MGR Messages   The following are Call Switching
Module Trunk Manager messages. %PXF_QOS-3-WS_QOS_L2C_TOO_MANY_L2_LKP_TBLS (x): Too many possible PXF QoS layer
2  lookup tables. (reached [int] tables). Can not add more. PXF QoS layer 2  classification
will not function correctly.

Explanation: The PXF QoS Layer 2 Classification does not function correctly because
the number of  PXF QoS Layer 2 lookup tables that result from the classification
exceeds the system limitation.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Also perform a search of the
Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still
require assistance, open a case  with the Technical Assistance Center via the Internet
at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical
support  representative and provide the representative with the gathered information.%CSM_TRUNK_MGR-3-TRUNK_VALIDITY_FAILURE (x): [chars]

Explanation: A trunk validity failure has occurred. This generally indicates
a memory corruption or  uninitialisation issue.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     CSM_VOICE Messages   The following are Call Switching
ModuleVoice call messages. %CSM_TRUNK_MGR-3-TRUNK_VALIDITY_FAILURE (x0): [chars]

Explanation: A trunk validity failure has occurred. This generally indicates
a memory corruption or  uninitialisation issue.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.     CSM_VOICE Messages   The following are Call Switching
ModuleVoice call messages. %FREDDO_E1T1-3-CHANNEL_GROUP (x): [chars]

Explanation: Channel group configuration specific error.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FREDDO_E1T1-3-CHANNEL_GROUP (x0): [chars]

Explanation: Channel group configuration specific error.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FREDDO_E1T1-3-CLOCK_MODE (x): At least one [chars] was configured already for
 [chars]. Please remove it before changing timing mode.

Explanation: If ds0-group or pri-group are already configured, timing mode cannot
be changed  without removing them.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FREDDO_E1T1-3-CLOCK_MODE (x0): At least one [chars] was configured already for
 [chars]. Please remove it before changing timing mode.

Explanation: If ds0-group or pri-group are already configured, timing mode cannot
be changed  without removing them.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FREDDO_E1T1-3-CNTR_TYPE_CHG (x): You need to reload the router for this configuration
 change to be effective.

Explanation: If the controller type is set to T1 or E1 and if the opposite controller
is put on freddo  system, the system needs to be rebooted to change the controller
type.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%FREDDO_E1T1-3-CNTR_TYPE_CHG (x0): You need to reload the router for this configuration
 change to be effective.

Explanation: If the controller type is set to T1 or E1 and if the opposite controller
is put on freddo  system, the system needs to be rebooted to change the controller
type.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at  http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%CSM-4-HWIDB_ALREADY_IN_USE (x): hwidb is already in use by another call

Explanation: A call is already using this HWIDB. This new call will be rejected.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.%CSM-4-HWIDB_ALREADY_IN_USE (x0): hwidb is already in use by another call

Explanation: A call is already using this HWIDB. This new call will be rejected.

Recommended Action: Copy the message exactly as it appears on the console or
in the system log.  Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools
and utilities will supply clarifying  information. Search for resolved software
issues using the Bug Toolkit at  http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance,  open a case with the Technical Assistance Center
via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact
your Cisco technical support  representative and provide the representative with
the gathered information.  %OSPF-5-ADJCHG (x5): Process [dec], Nbr [IP_address] on [chars] from [chars]
to [chars], [chars]

Explanation: An OSPF neighbor has changed state. The message describes the change
and the reason  for it. This message appears only if the log-adjacency-changes
command is configured for the  OSPF process.

Recommended Action: No action is required.%OSPF-5-ADJCHG (x0): Process %d, Nbr %i on %s from %s to %s, %s

Explanation: An OSPF neighbor has changed state. The message describes the change
and the reason  for it. This message appears only if the log-adjacency-changes
command is configured for the  OSPF process.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGNP (x223): list [chars] [chars] [dec] [IP_address] [chars]->
[IP_address], [dec] packet[chars]

Explanation: A packet matching the log criteria for the given access list has
been detected.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGNP (x0): list [chars] [chars] [dec] [IP_address] [chars]->
 [IP_address], [dec] packet[chars] [chars]

Explanation: A packet matching the log criteria for the given access list was
detected.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGNP (x0): list [chars] [chars] [dec] [IP_address] [chars]->
 [IP_address], [dec] packet[chars] [chars] [chars]

Explanation: A packet matching the log criteria for the given access list was
detected.

Recommended Action: Informational message only. No action is required.%SEC-6-IPACCESSLOGP (x7): list [chars] [chars] [chars] [IP_address]([dec]) [chars]->
[IP_address]([dec]), [dec] packet[chars]

Explanation: A packet matching the log criteria for the given access list has
been detected.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGP (x0): list [chars] [chars] [chars] [IP_address]([dec]) [chars]->
 [IP_address]([dec]), [dec] packet[chars] [chars]

Explanation: A packet matching the log criteria for the given access list was
detected.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGP (x0): list [chars] [chars] [chars] [IP_address]([dec]) [chars]->
 [IP_address]([dec]), [dec] packet[chars] [chars] [chars]

Explanation: A packet matching the log criteria for the given access list was
detected.

Recommended Action: Informational message only. No action is required.%SEC-6-IPACCESSLOGRP (x12): list [chars] [chars] [chars] [IP_address] [chars]->
[IP_address], [dec] packet[chars]

Explanation: A packet matching the log criteria for the given access list has
been detected.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGRP (x0): list [chars] [chars] [chars] [IP_address] [chars]->
 [IP_address], [dec] packet[chars] [chars]

Explanation: A packet matching the log criteria for the given access list was
detected.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGRP (x0): list [chars] [chars] [chars] [IP_address] [chars]->
 [IP_address], [dec] packet[chars] [chars] [chars]

Explanation: A packet matching the log criteria for the given access list was
detected.

Recommended Action: Informational message only. No action is required.%SEC-6-IPACCESSLOGRL (x5): access-list logging rate-limited or missed [dec] packet[chars]

Explanation: Some packet-matching logs were missed because the access list log
messages were rate  limited, or no access list log buffers were available.

Recommended Action: No action is required.%SEC-6-IPACCESSLOGRL (x0): access-list logging rate-limited or missed [dec] 
packet[chars] [chars]

Explanation: Some packet matching logs were missed because the access list log
messages were  rate-limited or no access list log buffers were available.

Recommended Action: No action is required.%ENTITY_ALARM-6-INFO (x): [chars] [chars] [chars] [chars] [chars]

Explanation: Alarm assertion or deassertion information.

Recommended Action: No action is required.     ENVM Messages   The following
are Environmental Monitor messages. %ENTITY_ALARM-6-INFO (x0): [chars] [chars] [chars] [chars] [chars]

Explanation: Alarm assertion or deassertion information.

Recommended Action: No action is required.     ENVM Messages   The following
are Environmental Monitor messages.  
No information on error code 034777
No information on error code 034823
No information on error code 034808
No information on error code 034739
No information on error code 034700
No information on error code 034681
No information on error code 034792
No information on error code 034610
No information on error code 034707
No information on error code 034674
No information on error code 034668
No information on error code 034624
No information on error code 034740
No information on error code 034727
No information on error code 034787
No information on error code 034759
No information on error code 034614
No information on error code 034705
No information on error code 034651
No information on error code 034671
No information on error code 034646
No information on error code 034812
No information on error code 034619
No information on error code 034781
No information on error code 034835
No information on error code 034749
No information on error code 034780
No information on error code 034719
No information on error code 034609
No information on error code 034733
No information on error code 034664
No information on error code 034620
No information on error code 034678
No information on error code 034635
No information on error code 034776
No information on error code 034737
No information on error code 034726
No information on error code 034587
No information on error code 034638
No information on error code 034771
No information on error code 034744
No information on error code 034650
No information on error code 034657
No information on error code 034768
No information on error code 034687
No information on error code 034813
No information on error code 034691
No information on error code 034793
No information on error code 034804
No information on error code 034819
No information on error code 034704
No information on error code 034752
No information on error code 034706
No information on error code 034588
No information on error code 034765
No information on error code 034730
No information on error code 034630
No information on error code 034829
No information on error code 034615
No information on error code 034720
No information on error code 034834
No information on error code 034592
No information on error code 034686
No information on error code 034699
No information on error code 034783
No information on error code 034596
No information on error code 034755
No information on error code 034728
No information on error code 034677
No information on error code 034605
No information on error code 034618
No information on error code 034828
No information on error code 034816
No information on error code 034710
No information on error code 034654
No information on error code 034831
No information on error code 034716
No information on error code 034669
No information on error code 034736
No information on error code 034613
No information on error code 034824
No information on error code 034616
No information on error code 034627
No information on error code 034773
No information on error code 034690
No information on error code 034714
No information on error code 034807
No information on error code 034682
No information on error code 034743
No information on error code 034810
No information on error code 034832
No information on error code 034586
No information on error code 034658
No information on error code 034648
No information on error code 034741
No information on error code 034825
No information on error code 034753
No information on error code 034633
No information on error code 034782
No information on error code 034748
No information on error code 034665
No information on error code 034593
No information on error code 034731
No information on error code 034590
No information on error code 034799
No information on error code 034659
No information on error code 034623
No information on error code 034769
No information on error code 034693
No information on error code 034601
No information on error code 034798
No information on error code 034694
No information on error code 034806
No information on error code 034634
No information on error code 034701
No information on error code 034772
No information on error code 034723
No information on error code 034803
No information on error code 034597
No information on error code 034721
No information on error code 034786
No information on error code 034688
No information on error code 034698
No information on error code 034734
No information on error code 034644
No information on error code 034794
No information on error code 034756
No information on error code 034760
No information on error code 034660
No information on error code 034802
No information on error code 034747
No information on error code 034628
No information on error code 034604
No information on error code 034695
No information on error code 034639
No information on error code 034790
No information on error code 034821
No information on error code 034762
No information on error code 034789
No information on error code 034612
No information on error code 034836
No information on error code 034637
No information on error code 034742
No information on error code 034603
No information on error code 034702
No information on error code 034595
No information on error code 034626
No information on error code 034640
No information on error code 034666
No information on error code 034754
No information on error code 034709
No information on error code 034724
No information on error code 034713
No information on error code 034826
No information on error code 034712
No information on error code 034717
No information on error code 034683
No information on error code 034820
No information on error code 034622
No information on error code 034594
No information on error code 034833
No information on error code 034817
No information on error code 034673
No information on error code 034641
No information on error code 034800
No information on error code 034652
No information on error code 034732
No information on error code 034617
No information on error code 034655
No information on error code 034766
No information on error code 034608
No information on error code 034636
No information on error code 034645
No information on error code 034679
No information on error code 034757
No information on error code 034735
No information on error code 034788
No information on error code 034599
No information on error code 034598
No information on error code 034689
No information on error code 034811
No information on error code 034795
No information on error code 034697
No information on error code 034672
No information on error code 034647
No information on error code 034814
No information on error code 034746
No information on error code 034750
No information on error code 034763
No information on error code 034661
No information on error code 034606
No information on error code 034643
No information on error code 034805
No information on error code 034632
No information on error code 034675
No information on error code 034629
No information on error code 034667
No information on error code 034785
No information on error code 034809
No information on error code 034600
No information on error code 034708
No information on error code 034725
No information on error code 034718
No information on error code 034621
No information on error code 034822
No information on error code 034778
No information on error code 034801
No information on error code 034738
No information on error code 034663
No information on error code 034649
No information on error code 034791
No information on error code 034711
No information on error code 034827
No information on error code 034602
No information on error code 034670
No information on error code 034758
No information on error code 034684
No information on error code 034722
No information on error code 034761
No information on error code 034685
No information on error code 034642
No information on error code 034830
No information on error code 034770
No information on error code 034767
No information on error code 034745
No information on error code 034764
No information on error code 034797
No information on error code 034784
No information on error code 034631
No information on error code 034775
No information on error code 034818
No information on error code 034607
No information on error code 034796
No information on error code 034676
No information on error code 034653
No information on error code 034815
No information on error code 034656
No information on error code 034692
No information on error code 034611
No information on error code 034779
No information on error code 034591
No information on error code 034703
No information on error code 034662
No information on error code 034729
No information on error code 034751
No information on error code 034625
No information on error code 034715
No information on error code 034680
No information on error code 034774
No information on error code 034589
No information on error code 034696
  

STACK DECODE NOTIFICATIONS (if any)

  ERROR: This device has recorded 'Spurious Access', which is caused by a Cisco
IOS software bug. A spurious access occurs when a process attempts to read from
the lowest 16 KB region of memory. This portion of memory is reserved, and should
never be accessed. A read operation to this region of memory is usually caused
when a non-existing value is returned to a function in the software, when a null
pointer is passed to a function.
TRY THIS: Upgrade your device to the latest version of Cisco IOS software in your
release train.  Review Bug Toolkit for any potential bugs related to the loaded
image. Paste the "show tech-support" command output into the Output Interpreter
to display the potential issues and fixes. If the issue persists, consider opening
a service request with Cisco using the TAC Service Request Tool. Include the
"show alignment" and "show tech-support" command output for TAC analysis.
  REFERENCE: For more information on spurious access, see Troubleshooting Spurious
Accesses, Alignment Errors, and Spurious Interrupts.
  
  Note: Understanding the 'Fixed In Version' field - Sometimes the fixed-in version
specified may not be available for download from the Software Downloads. This
is because, bug fixes are incorporated into software versions which have not been
regression tested. These builds are called interim images and will have a "."
in the build number found between the parenthesis, for example 12.3(8.1). The bug
fix will be in the next available image, and all later images. So if a bug is fixed
in 12.3(8.1), the bug fix is present in 12.3(9), 12.3(10), and so on.
  REFERENCE: For more information on how IOS images are named, see Cisco IOS Reference
Guide.

 The failure was caused by a software defect.

The stack trace decoded symbols are:
     oce_surrender_fwd_state_handle
     crypto_ceal_post_decrypt_cef
     crypto_ceal_post_decrypt_switch
     crypto_engine_packet_callback
     sfnt_callback
     sfnt_udm_callback
     udm_notify
     udm_isr_common_bottom
     udm_isr
     c3800_sysctlr_interrupt
     c3800_pm_slot0
     scheduler
     oce_surrender_fwd_state_handle
     crypto_ceal_post_decrypt_cef
     crypto_ceal_post_decrypt_switch
     crypto_engine_packet_callback
     sfnt_callback
     sfnt_udm_callback
     udm_notify
     udm_isr_common_bottom
     udm_isr
     c3800_sysctlr_interrupt
     c3800_pm_slot0
     scheduler
     r4k_level_table
     oce_surrender_fwd_state_handle
     oce_surrender_fwd_state_handle

Possible bug matches are listed below. Bugs with a score of .90 or more

are the most likely candidates:

Score	Bugid	Status	Fixed In	Duplicate	Title
0.85	CSCse62295	R	12.4(16.13)PI7a 12.2(32.8.11)SR14 12.2(32.8.99a)SR133 12.4(16.14)T1 12.4(21.14.9)PIC1 12.2(33)SRC	None	Traffic shaping rework to use new CEF infrastructure.
0.85	CSCsk65460	R	12.4(21.3)T 12.2(32.8.11)SR142 12.4(19.18)T5 12.2(32.8.11)SX184 12.2(32.8.20)REC137 12.2(32.0)DPI 12.2(33)SXI 12.2(33)XNC	None	MVPN: mcast-FS fails on decapPE
0.85	CSCsq36269	R	12.4(21.14)T 12.4(21.13)PI9 12.4(21.14.1)PIC1 12.4(21.14.9)PIC1 12.4(15)T8 12.4(22.3.4)PIC1 12.4(20)T2	None	IPSEC on 7200: increments TTL when U turning packets
0.85	CSCsr21842	R	12.4(23.1)T 12.4(23.1)PI10 12.2(32.8.5)REC154 12.2(32.8.2)YCA172.24 12.4(21.14.6)PIC1 12.4(22.3.9)PIX11 12.4(23.5.2)PIX11 15.1(1)SG3.90 15.1(1)SG1.3	None	GRE+ipsec, tunnel inbound ACL, not process switched from cef punt
0.85	CSCsx51103	R	12.4(24.5)T 12.4(23.15)T6 12.4(24.5.2)PIC1 12.4(20)T3 12.2(33.1.8)MCP5 12.2(33.0.9)XND 12.4(22)T2	None	Router crash at OCE function after post-decrypt + %ALIGN-1-FATAL:
0.74	CSCsk29999	V	12.4(19.12)PI8 12.4(15)XZ 12.4(15)XY3 12.4(19.18)T1 12.4(21.14.9)PIC1 12.4(24.5.1)PIX11	None	AIM-IPS-K9:TCP intercept not entering aggressive mode
0.58	CSCtb05176	A		None	IPSEC Performance Degradation observed 12.4(24.6)PI11n vs 12.4(23.5)PI10

  

SHOW MEMORY Partial NOTIFICATIONS (if any)

  INFO: It seems you are trying to interpret 'show memory' command output. Please
paste the complete output of the show command into the Output interpreter tool
for analysis.

============================================================================================================

Thanks,

paolo bevilacqua · ‎06-09-2011

Try replacing memory. If stiull trouble, HW is faulty and must be replaced.