General Troubleshooting Information
This section provides the following general information for troubleshooting the Cisco WebEx Node SPA:
Interpreting Console Error and System Messages
Refer to Cisco IOS XE System Messages document.
System error messages are organized in the documentation according to the particular system facility that produces the messages. The SIP and SPA error messages use the following facility names:
-
Cisco ASR 1000 Series SIP:
- ASR1000_SIP
- ASR1000_SIP_SPA
-
Cisco WebEx Node SPA:
- SPA_SE1
- SPA_WMA
-
Cisco WebEx Node SPA Service Engine:
- SPA_SRVCS_ENGINE
- SPA_SRVCS_IF
- SPA Online Insertion and Removal—SPA_OIR
Using show Commands
There are several show commands, used in privileged EXEC mode, that you can use to monitor and troubleshoot the Cisco WebEx Node SPA on Cisco ASR 1000 Series Routers. For more information on these commands, refer to the Cisco IOS command references and see also the Performing Basic Troubleshooting, and the “Verifying the Service Engine Configuration” section of the Configuring the Cisco WebEx Node for the ASR 1000 Series Aggregation Services Routerschapter in this guide.
show Commands to Display Cisco WebEx Node SPA Status
- show platform —Displays the status of all modules installed in the Cisco ASR 1000 Series Router chassis. This command is not useful for out-of-service issues.
- show hw-module subslot all oir —Displays the OIR status of each Cisco WebEx Node SPA in the chassis. This command is useful for displaying out-of-service issues.
- show hw-module subslot oir —Displays the OIR status for a specified Cisco WebEx Node SPA.
- show hw-module subslot service-engine status —Displays the application and operational status and configuration of a specified Cisco WebEx Node SPA.
show Commands to Display Cisco WebEx Node SPA IDPROM
- show diag subslot eeprom —Displays main fields of the Cisco WebEx Node SPA IDPROM.
- show diag subslot detail —Display all the fields of the Cisco WebEx Node SPA IDPROM.
- show diag subslot dump —Dumps the content of the Cisco WebEx Node SPA IDPROM in hexadecimal format.
show Command to Display Cisco WebEx Node SPA Service Engine Status
The show hw-module subslot service-engine status command displays the operational status and configuration of the Cisco WebEx Node SPA. For successful configuration of the service-engine interface, the application status should be “Online.” You can also confirm the provisioned operation mode for the CiscoWebEx Node, which is “Web Conferencing” in the following example:
Router# show hw-module subslot 0/0 service-engine status
Service Engine is Cisco SPA-WMA-K9
Service Engine state: Steady (0x300)
Service Engine OS Version: 1.0.0, Application Version: 1.0.0
Application: WebEx Node (Web Conferencing)
Application Status: Online
Configuration:
Int ip address: 10.200.72.18 , mask: 255.255.255.252
GW ip address: 10.200.72.17
Nameserver 1: 10.100.4.10 , Nameserver 2: 10.100.4.20
Hostname: spawma1, Domain name: cisco.com
WMA URL - https://wmabts.webex.com/wmams
WMA Token - 45484b3e-8ea5-41e5-b050-49409006d14e
WMA Passcode Name - cisco_test, key:0552055C271A4B5C4D5D424A5B5E007Fshow Command to Display Cisco WebEx Node SPA FPD version
The show hw-module all fpd command displays the FPD version of each Cisco WebEx Node SPA in the Cisco ASR 1000 Series Router. The following example shows some sample output:
Router# show hw-module all fpd
==== ====================== ====== =============================================
H/W Field Programmable Current Min. Required
Slot Card Type Ver. Device: "ID-Name" Version Version
==== ====================== ====== ================== =========== ==============
0/0 SPA-WMA-K9 0.169 4-ADM1066 0.5 0.5
5-CPLD 1.2 1.2
1-Appl I/O FPGA 1.2 1.2
2-ROMMON 1.1 1.1
---- ---------------------- ------ ------------------ ----------- --------------
0/1 SPA-5X1GE-V2 1.2 1-GE I/O FPGA 1.10 1.10
---- ---------------------- ------ ------------------ ----------- --------------
0/3 SPA-2X1GE-V2 0.22 1-2xGE V2 I/O FPGA 1.1 1.1
---- ---------------------- ------ ------------------ ----------- --------------
1/0 SPA-WMA-K9 0.133 4-ADM1066 0.5 0.5
5-CPLD 1.2 1.2
1-Appl I/O FPGA 1.2 1.2
2-ROMMON 1.1 1.1
---- ---------------------- ------ ------------------ ----------- --------------
1/1 SPA-WMA-K9 0.165 4-ADM1066 0.5 0.5
5-CPLD 1.2 1.2
1-Appl I/O FPGA 1.2 1.2
2-ROMMON 1.1 1.1show Command to Display Cisco WebEx Node SPA Error Messages on the RP Console
The show logging command displays the logged messages that have appeared on the RP console. The following is an example of a software error message that might appear when you run the show logging command:
Router# show logging
*May 22 17:11:58.712: %SPA_SRVCS_ENGINE-3-APP_MSG_ERR: SIP0/0: SPA-WMA-K9[0/0]: Connect CWNMS server failed, check network availability to CWNMS server.Accessing the SIP and SPA Consoles for Troubleshooting
Some troubleshooting for the Cisco WebEx Node SPA requires that you access the SIP or SPA consoles and run some commands to gather debug information or take other action. Under normal operation there is no need to access these consoles. However, sometimes it can be necessary to troubleshoot more complex problems and gather certain debug information.
Accessing the SIP Console
Use the request platform software console attach command to access the SIP console through the Cisco ASR 1000 Series Router RP console. The SIP console is used to collect debug information about the Cisco IOS code that is running on the SIP.
The following example shows how to access the SIP console and enter enable mode:
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#
To exit the SIP console, enter Control-C .
Accessing the Cisco WebEx Node SPA Console
Use the hw-module subslot service-engine session command to access the Cisco WebEx Node SPA console through the Cisco ASR 1000 Series Router RP console. You will see a VEGAS Shell prompt and have access to the console commands.
Prerequisites
Before you can open a console session on a Cisco WebEx Node SPA, the SPA must first be configured with a minimum of the following commands and be in the “up” state:
- ip address
- service-engine ip address
- service-engine default-gateway
The service-engine ip address command must be configured before the service-engine default-gateway command.
Opening the Cisco WebEx Node SPA Console
The following example shows how to open the SPA console:
 Note |
The SPA console default prompt is “service-spa.” This prompt can be changed by configuring the service-engine hostname command. |
Router# hw-module subslot 0/0 service-engine session
MontaVista(R) Linux(R) Carrier Grade Edition 5.0 (custom)
Linux/mips64 2.6.21_mvlcge500-octeon-mips64_octeon_v2_be
Vegas Shell -- CGE 5.0 Version
Copyright (c) 1985-2008 by Cisco Systems, Inc.
All rights reserved.
service-spa#Listing the Available Cisco WebEx SPA Console Commands
The Cisco WebEx SPA console supports a similar help function as the RP console. You can enter ? at the console to obtain a list of the available commands as shown in the following example:
service-spa# ?
Exec commands:
clean Clean commands
copy Copy files from src to destination
delete Remove files
dir Directory listing for files
exit Exit from the EXEC
format Format a device with ext3/fat16/dummy file system
fsck Perform file system check operation
less Shows content of file
load Load plug-in image
mkdir Create new directory
move Move files
ping Send echo messages
rmdir Remove existing directory
show Show system information
terminal Set terminal line parameters
traceroute Trace route to destination
webex Webex Application Commands
Some of the most useful commands include:
- show eventlog —Dumps the content of the /var/log/messages file.
- show disk partitions —Displays the partitions available on the hard disk drive (HDD).
- show disk smart —Displays S.M.A.R.T. output of the HDD.
- show tech-support —Gathers information for troubleshooting.
- ping —Sends echo messages.
- copy tftp: disk0: —Copies files from a TFTP server to the HDD first partition.
- load —Loads a plug-in image.
- exit —Exits from the Cisco WebEx Node SPA console.
Exiting the Cisco WebEx Node SPA Console
To exit the SPA console, use the exit command as shown in the following example:
service-spa# exit
Router#Handling TraceBack and Core Dump Files on the Cisco WebEx Node SPA
This section describes how to gather traceback and core dump file information for troubleshooting by Cisco technical support.
Collecting Core Dump Files for the Cisco WebEx Node SPA
Linux utilities on the Cisco WebEx Node SPA and the WebEx application software can create core dump files when errors occur. When this happens an error message is logged on the RP console as shown in the following example:
*May 22 17:12:02.210:%SPA_SRVCS_ENGINE-2-APP_MSG_CRIT: SIP1/0: SPA-WMA-K9[1/0]: Core dump generated for 'smartd' (corefile:smartd-626-11-1242970631.core.gz). If the problem persists, contact your technical support representative for assistance.
The core file is saved on the hard disk on the Cisco WebEx Node SPA. Using commands from the Cisco WebEx Node SPA console, you can copy the file from the SPA to an external TFTP server. This file should be given to Cisco technical support as necessary for analysis of the problem.
To access the core dump file and copy it to a TFTP server, complete the following steps:
SUMMARY STEPS
- From the RP console, access the Cisco WebEx Node SPA console as shown in the following example:
- From the Cisco WebEx Node SPA console, run the dir core: command to display the smartd file as shown in the following example:
- Copy the core dump file from the SPA to a TFTP server as shown in the following example:
DETAILED STEPS
| Step 1 |
From the RP console, access the Cisco WebEx Node SPA console as shown in the following example: Example: |
||
| Step 2 |
From the Cisco WebEx Node SPA console, run the dir core: command to display the smartd file as shown in the following example:
Example: |
||
| Step 3 |
Copy the core dump file from the SPA to a TFTP server as shown in the following example:
Example: |
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:
SUMMARY STEPS
- From the RP console, access the SIP console and enter enable mode as shown in the following example:
- 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:
DETAILED STEPS
| Step 1 |
From the RP console, access the SIP console and enter enable mode as shown in the following example: Example: |
||
| 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: Example: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:
Example: |
Feedback