23-7
Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Software Configuration Guide
OL-14127-08
Chapter 23 Troubleshooting the Cisco WebEx Node for the ASR 1000 Series
General Troubleshooting Information
Collecting Traceback Information for the Cisco WebEx Node SPA
Traceback information is generated during booting of the Cisco WebEx Node SPA and can be used to
troubleshoot problems. You can access the traceback information from the SIP console.
No error messages are logged on the RP to indicate that a traceback event has occurred. These events are
usually associated with other failures whose errors are reported on the RP console such as
SYSINIT_FAILURE messages, as shown in the following example:
*May 1 07:46:32.650: %SPA_SE1-3-SYSINIT_FAILURE: SIP0/0: SPA-WMA-K9[0/0]: System init
failure was detected during bootup - application installation error. SPA will be disabled
because of this failure.
To collect traceback information for the Cisco WebEx Node SPA, complete the following steps:
Step 1 From the RP console, access the SIP console and enter enable mode as shown in the following example:
Router# request platform software console attach 0/0
#
# Connecting to the SPA console on 0/0.
# Enter Control-C to exit the console connection.
#
Router> enable
Router#
Step 2 From the SIP console, enter the show hw-module subslot bay bootlog cpu-prev or show hw-module
subslot bay bootlog cpu-last commands to access the traceback from either the previous SPA boot
(cpu-prev option) or last SPA boot (cpu-last option), as shown in the following examples:
Router# show hw-module subslot 0 bootlog cpu-last
% CPU boog log not available from last SPA-WMA-K9[0/0] bootup.
The following excerpt of a traceback shows a problem with the kernel that eventually causes the Cisco
WebEx Node SPA to timeout. After 5 attempts to reload the Cisco WebEx Node SPA, the SPA enters an
out-of-service state:
Note Some output has been removed to make the example more readable.
Router# show hw-module subslot 0 bootlog cpu-prev
--------- CPU boot log from previous SPA-WMA-K9[0/0] bootup ---------
Checking for the multiply/shift bug... no.
Checking for the daddi bug... no.
Checking for the daddiu bug... no.
CPU 0 Unable to handle kernel paging request at virtual address 0000000000000008,
epc == ffffffff8c029fb4, ra == ffffffff8c02a0bc
Oops[#1]:
Cpu 0
$ 0 : 0000000000000000 ffffffff8c4a3400 ffffffff8c4a5c00 ffffffff8c4a3400
$ 4 : 0000000000000028 0000000000000000 0000000000000000 0000000000000001
$ 8 : a800000414487e60 ffffffffffffffc0 0000000000000000 0000000000000000
$12 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000
$16 : 0000000000000028 0000000000000000 0000000000000010 ffffffff8c4a5c70
$20 : 0000000000000001 0000000000000000 0000000000000000 0000000000000000
$24 : 0000000000000000 0000000000000000
$28 : a800000414484000 a800000414487e60 0000000000000000 ffffffff8c02a0bc
Hi : 0000000000000000
Lo : 0000000000000000
epc : ffffffff8c029fb4 octeon_unmask_ciu_irq+0x24/0x30 Not tainted
ra : ffffffff8c02a0bc octeon_irq_ciu_unmask+0x84/0xc8
Status: 10008ce2 KX SX UX KERNEL EXL