Monitor Subscriber; Gathering D-Ewag-Related Statistics And Information - Cisco ASR 5000 Administration Manual

DHCP-based Enhanced Wireless Access Gateway Configuration
To view monitor protocol based logging information, in the Exec Mode use the following command:
monitor protocol
For D-eWAG use the following filters:
 12 — RADIUS Authentication
 13 — RADIUS Accounting
 19 — User L3
 20 — USERTCP STACK
 24 — GTPC
 26 — GTPU
 27 — GTPP
 28 — DHCP
 29 — CDR
 31 — RADIUS COA
 34 — CSS Data: In case of Local Traffic Breakout support, shows data packets after NAT is done.
 41 — IPSG RADIUS Signal: Must be used to view the RADIUS accounting messages on the control path for
IPSG session management.
 70 — DNS Client

Monitor Subscriber

The system's 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.
To view monitor subscriber based logging information, in the Exec Mode use the following command:
monitor subscriber
The following filters are available for monitor subscriber based logging in D-eWAG.
Monitor Subscriber for full call flow can be checked with the options next-call, type, and username. Other options like
IMSI, MSISDN, and MSID are not applicable for calls as they are not known to D-eWAG at the initial stage of
authentication (D-eWAG gets this information only after receiving Access-Accept from the AAA server.

Gathering D-eWAG-related Statistics and Information

Table 7. D-eWAG-related Statistics and Information
D-eWAG-related statistics or
information
To view concise D-eWAG service-
level information.
CLI command to use
show ipsg service all
Cisco ASR 5000 Enhanced Wireless Access Gateway Administration Guide ▄
D-eWAG Administration ▀
111