Using The Protocol Monitor For A Specific Subscriber - Cisco ASR 5500 System Administration Manual

Using the Protocol Monitor

Using the Protocol Monitor for a Specific Subscriber

The protocol monitor can be used to display information for a specific subscriber session that is currently
being processed. Depending on the number of protocols monitored, and the number of sessions in progress,
a significant amount of data is generated. It is highly recommended that logging be enabled on your terminal
client in order to capture all of the information that is generated.
Follow the instructions in this section to invoke and configure the protocol monitoring tool for a specific
subscriber session.
Step 1 To invoke the session-specific protocol monitor from the Exec mode enter the monitor subscriber command.
host_name
[local]
peer-fa | peer-lac | sgsn-address | type | username }
Step 2 Specify the method the monitor should use by entering the appropriate keyword.
Step 3
Select other options and/or enter the appropriate information for the selected keyword.
If no session matching the specified criteria was being processed when the monitor was invoked, a screen of available
monitoring options appears.
Step 4
Configure the amount of information that is displayed by the monitor. To enable or disable options, enter the letter or
2-digit number associated with that option (C, D, E, 11, 12, etc.). To increase or decrease the verbosity, use the plus ( +
) or minus ( - ) keys.
The current state, ON (enabled) or OFF (disabled), is shown to the right of each option.
Option Y for performing multi-call traces is only supported for use with the GGSN.
Step 5 Repeat step 6 as needed to enable or disable multiple protocols.
Step 6 Press Enter to refresh the screen and begin monitoring.
The following displays a portion of a sample of the monitor's output for a subscriber named user2@aaa. The default
protocols were monitored.
---------------------------------------------------------------------------
Incoming Call:
---------------------------------------------------------------------------
MSID: 0000012345 Callid: 002dc6c2
Username: user2@aaa SessionType: unknown
Status: Active Service Name: xxx1
Src Context: source Dest Context:
---------------------------------------------------------------------------
<<<<OUTBOUND 10:02:35:415 Eventid:25001(0)
PPP Tx PDU (9)
PAP 9: Auth-Ack(1), Msg=
<<<<OUTBOUND 10:02:35:416 Eventid:25001(0)
PPP Tx PDU (14)
IPCP 14: Conf-Req(1), IP-Addr=192.168.250.70
<<<<OUTBOUND 10:02:35:416 Eventid:25001(0)
PPP Tx PDU (27)
CCP 27: Conf-Req(1), MPPC, Stac-LZS, Deflate, MVRCA
ASR 5500 System Administration Guide, StarOS Release 21.5
164
monitor subscriber { callid | imei | imsi | ipaddr | ipv6addr | msid | msisdn | next-call | pcf |
#
Troubleshooting