Cisco Cisco Packet Data Interworking Function (PDIF)
Exec Mode Commands (D-S)
▀ logging trace
▄ Command Line Interface Reference, StarOS Release 17
4096
logging trace
Enables or disables the logging of trace information for specific calls, mobiles, or network addresses.
Product
All
Privilege
Security Administrator, Administrator, Operator
Mode
Exec
The following prompt is displayed in the Exec mode:
[local]host_name#
Syntax
[ no ] logging trace { callid call_id | ipaddr ip_address | msid ms_id | username
user_name }
user_name }
no
Indicates the logging of trace information is to be disabled.
callid
call_id | ipaddr
ip_address | msid
ms_id | username
user_name
callid
call_id
: Specifies the exact call instance ID which is to have trace data logged.as a 4-byte
hexadecimal number.
ipaddr
ip_address
: Specifies the IP address in IPv4 dotted-decimal notation for which trace information
is to be logged.
msid
ms_id
: Specifies the mobile subscriber ID for which trace information is to be logged as 7 to 16 digits
of an IMSI, MIN, or RMI.
username
user_name
: Specifies a previously configured user who is to have trace information logged.
Usage
A trace log is useful in troubleshooting subscriber problems as well as for system verification by using a test
subscriber. The
subscriber. The
no
keyword is used to stop the logging of trace information.
Important:
A maximum of 50,000 events may be stored in each log. Enabling more events for logging may
cause the log to be filled in a much shorter time period. This may reduce the effectiveness of the log data as a shorter
time period of event data may make troubleshooting more difficult.
time period of event data may make troubleshooting more difficult.
Important:
Once a log has reached the 50,000 event limit the oldest events will be discarded as new log entries
are created.
Caution:
Issuing this command could negatively impact system performance depending on the number of
subscribers connected and the amount of data being passed.