Troubleshooting guide

10-11
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 10 Troubleshooting the Cisco BTS 10200 Softswitch
Troubleshooting
The call processing logic in the Cisco BTS 10200 Softswitch is based on the IN Capability Set 2 (CS2)
half call model. The interface between the basic call module (BCM), which provides the core call
processing logic, and the signaling interface adapters (SIA) is protocol independent.
To verify the current status of the Cisco BTS 10200 Softswitch you can enter commands using the
command line interface (CLI). Logging into a CLI session is a Secure Shell (SSH) function, not a UNIX
function. You must use SSH to connect to the EMS using your user name and password, which invokes
a CLI shell. After you log in only the CLI command prompt appears on the screen. To enter commands
using the CLI, enter the command with all its required parameters (tokens) and any optional parameters
you wish.
To log in from the client-side, perform the following steps:
Step 1 Enter ssh -l username IPaddress
On the first SSH login from the client-side, expect a message similar to this:
The authenticity of host [hostname] can't be established.
Key fingerprint is 1024 5f:a0:0b:65:d3:82:df:ab:42:62:6d:98:9c:fe:e9:52.
Are you sure you want to continue connecting (yes/no)?
Step 2
Enter “y” or “yes.”
The password prompt appears. From this point on, all communications are encrypted. Subsequent SSH
logins will prompt only for a password.
Verify Alarm Status
To verify the current alarm status of the Cisco BTS 10200 Softswitch, perform the following steps:
Step 1 Start a CLI session by using a valid login id.
Step 2 Enter the command CLI> rtrv-alms::CONT
This command retrieves the alarm status of the system. Look for alarms with "FAIL", "UNAVAIL" and
"OOS" descriptions.
For example,
"nlink525a:npath525,LID=0:OOS" is a major alarm stating that an NAS IP path has
failed.
Look for a recommended action under the alarms section of the Cisco BTS 10200 Operations Guide.
Verify Media Gateways
This section describes diagnostic tests that can be performed on media gateways. Media gateways must
be in the MAINT state for testing.
To verify the current status of the media gateways, perform the following steps:
Step 1 Use the following control command to force a media gateway into the MAINT state for testing:
control mgw id=c2421.65; mode=forced; target-state=maint;