Cisco Cisco ASR 5500 故障排查指南
the performance of the system will not be affected.
Commands
These commands can be used in order to troubleshoot issues:
#
show support details
#
show crash list
#
show logs
#
show snmp trap history verbose
#
show session recovery status verbose
#
show task resources facility sessmgr instance <>
#
show task resources facility sessmgr all
Corefiles are generated after a crash. Usually operators store them in an external server. The corefile name
usually looks like crash-<Cardnum>-<CPU Num>-<Hex timestamp>-coree.gcrash-09-00-5593a1b8-core.
usually looks like crash-<Cardnum>-<CPU Num>-<Hex timestamp>-coree.gcrash-09-00-5593a1b8-core.
Whenever a crash occurs, this crash information is stored:
The event record is stored in /flash/crashlog2 file (the crash log).
•
The associated minicore, NPU, or kernel dump file is stored in the /flash/crsh2 directory.
•
Summary
All of the ASR5x00 software is designed to handle both foreseen conditions/events and unforeseen
conditions/events. While Cisco strives to have perfect software, inevitably mistakes will exist and crashes will
be possible. That is why the session recovery feature is so important. Cisco's strive for perfection will
minimize the occurrences of crashes, and session recovery will allow the sessions to continue after a crash.
Nonetheless, it is important that Cisco continues to strive to achieve perfect software. Fewer crashes will
reduce the likelihood of multiple crashes that happen simultaneously. While session recovery seamlessly heals
a single crash, the recovery from multiple simultaneous crashes is designed a bit differently. Operators should
rarely (or never) experience multiple simultaneous crashes, but if such were to occur, the ASR5x00 is
designed to recover system integrity as the highest priority, possibly at the sacrifice of some subscriber
sessions.
conditions/events. While Cisco strives to have perfect software, inevitably mistakes will exist and crashes will
be possible. That is why the session recovery feature is so important. Cisco's strive for perfection will
minimize the occurrences of crashes, and session recovery will allow the sessions to continue after a crash.
Nonetheless, it is important that Cisco continues to strive to achieve perfect software. Fewer crashes will
reduce the likelihood of multiple crashes that happen simultaneously. While session recovery seamlessly heals
a single crash, the recovery from multiple simultaneous crashes is designed a bit differently. Operators should
rarely (or never) experience multiple simultaneous crashes, but if such were to occur, the ASR5x00 is
designed to recover system integrity as the highest priority, possibly at the sacrifice of some subscriber
sessions.
Updated: Aug 25, 2015
Document ID: 119224