Troubleshooting guide

6-157
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Tracing
Where:
The filename (yyyymmddhhmmss) is a time stamp that is formatted as follows:
– yyyy—Four-digit designation for the year, such as 2000, 2001, or 2002.
– mm—Two-digit designation for the month (01 through 12).
– dd—Two-digit designation for the day of the month (01 through 31).
– hh—Two-digit designation for the hour of the day (00 through 23).
– mm—Two-digit designation for the minutes of an hour (00 through 59).
– ss—Two-digit designation for the seconds of a minute (00 through 59).
• n—Duration for which call trace information is collected, in seconds. At the expiration of this
period, the system discontinues PDU collection on the signaling path and closes the log file. In the
absence of this parameter, the default period is set to 1800 seconds (30 minutes), after which the
system stops the trace automatically.
• confirm—An option that is required to confirm a sig_path level trace or a trkgrp level trace
command. This option is required because of the large volume of data that the system can generate
and the potential performance impact of generating a large trace file. If you do not specify the
confirm option, the system rejects the command and displays a message about the potential
performance impact of this command.
• span—Span ID, an integer value denoting the traffic channel for the sig_path (NFAS only).
• rng—Range. When used with “span=x,” y is an optional range of spans beginning with span x and
continuing for y spans. When used with “tc=z,” y is an optional range of traffic channels beginning
with z and continuing for y traffic channels. When used with “trk=w,” y is an optional range of
contiguous trunks that you want to trace starting with trunk w and ending with trunk y.
• tc—Traffic channel that is associated with the trace, in integer form.
• trk—Trunk that is associated with the trace, integer form.
The following paragraphs present examples of the five possible command variations:
• Signaling path level trace traces all calls occurring on the signaling path. Use this format if you do
not know the specific signaling path level.
sta-sc-trc: sig_path :log=” filenameprefix ”, prd=600, confirm
In this form of the command, the confirm parameter is required.
• Signaling path span-level trace traces calls at the span level. Use this format to reduce the amount
of trace information if you know the span on which the call is placed.
sta-sc-trc: sig_path :span= x
The confirm parameter is not needed in this form of the command because the volume of the trace
file should not be an issue, nor should system performance.
• Signaling path span-traffic-channel level trace traces calls at the TC or CIC level. Use this format if
the traffic channel on which the call is placed is known.
sta-sc-trc: sig_path :span=x,tc=y
• Trunk group level trace traces all calls at a trunk group level. Use this format if the trunk group on
which the call is placed is known.
sta-sc-trc: trkgrp :confirm
This form of the command requires the confirm parameter.