Contents

Introduction

Commands

monitor subscriber (mon sub)

logging monitor

logging trace

monitor protocol

active or runtime logging

Subscriber commands

show subscribers full

show subscribers (hsgw-only | pgw-only | ggsn-only | mme-only | sgw-only | sgsn-only) full

show active-charging sessions full

show active-charging firewall statistics

show subscribers data-rate [high/low]

show subscribers debug-info

show subscribers aaa-configuration

show subscribers activity

show active-charging flows ip-address

show subscribers policy

show [mipfa | mipha] full

show [mipfa |mipha] counters

show ppp [full]

show rp full

show l2tp sessions full

show rsvp counters

show ims-authorization sessions full

Non-Subscriber specific commands

Related Cisco Support Community Discussions

Introduction

This article focuses on CLIs applicable to troubleshooting specific subscriber(s) issues. Whether there is just a known single or group of subscribers experiencing an issue, or an unknown (at first) group of subscribers, there are a number of CLIs that can help pinpoint the issue. Use them in combination with (non-subscriber specific) statistics CLIs in the troubleshooting process. Obviously not all of these commands would apply to every situation since some of them are protocol specific, while others are generic enough to apply to all subscribers. Some apply to user-plane (passing of data back and forth between subscriber and network) while others apply to call control plane (setting up of the call), while some could apply to both.

Example snippets are provided in a number of places to help make points clear. All IP addresses and identifying information have been changed.

Commands

monitor subscriber (mon sub)

This is probably one of the most well known commands on the platform and the most amount of time is spent here documenting and explaining its usage. Depending on the settings chosen, it has the potential to display all of a particular subscriber’s control/signaling and payload data for all interfaces, services, protocols, etc. Some considerations in running the command and interpreting output include the following:

- Based on investigation up to a point in time, if a problem is suspected but a particular subscriber having an issue is not yet known, then attempting capture by “next-call”, possibly trying many times, may result in capturing a failure if the issue is frequent enough. If the problem is rare, this approach may not be feasible.

- For known call types (Closed RP, Open RP, Evolution Data Optimized (EVDO), 1X-EVDO, Layer 2 Tunnelling Protocol (L2TP), Home Agent (HA), Long Term Evolution (LTE), etc.), especially those that are a low percentage of the overall volume, or those where the peer Packet Control Function (PCF) or peer L2TP Access Concentrator (LAC) is where the problem is suspected to be, then the monitor subscriber menu option allows qualifying the next call by such criteria, which will increase hit rate significantly. If all calls on the node are of the same type, then this approach adds no value (except for the peer address versions just mentioned) since doing so doesn't narrow down the possibilities.

- There are various levels of verbosity 1 to 5. Do not turn on higher levels of verbosity if not needed, as it makes reading the trace (quickly) more difficult. Usually increasing to verbosity 2 (default = 1) is sufficient.

- By default, most, but not all, of the protocols that would be interesting to view are turned ON by default

- Besides the actual packet data, sometimes special CONTROL messages are displayed that may explain what action is being taken under the covers – this information is often useful. This includes the call statistics displayed at the end of a call. Here is an example control message:

***CONTROL*** 00:25:27:054 Eventid:11813

No LMA address available for APN <apn2> in subscriber profile, PDN connection  failed

- If Enhanced Charging Service (ECS) is configured on the gateway nodes, then turning on option 34 (CSS Data) allows for viewing all packets being sent to and from the ECS module, which can be helpful for troubleshooting packet drops and Network Address Translation (NAT). For example here is a subscriber Internet Control Message Protocol (ICMP) packet that is NAT'd by ECS from private IP 10.251.88.68 to public IP 209.165.201.1

<<<<OUTBOUND  23:57:08:943 Eventid:77000(9)

CSS Uplink Output PDU to ACS- slot:2 cpu:17 inst:4369

10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84)

***CONTROL*** 23:57:08:943 Eventid:77202

Rule matched : icmp-pkts for uplink packet of subscriber MSID :

INBOUND>>>>>  23:57:08:943 Eventid:77001(9)

CSS Uplink Input PDU from ACS- slot:3 cpu:34 inst:8738

209.165.201.1 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84)

- If it is not obvious from the trace why the ASR is exhibiting a particular behavior, then viewing the internal processing for the subscriber might have value (interpreting such output which includes state machine info and the like is difficult but can be done by engineering), and so logging monitor or logging trace commands may be considered (discussed later).

- The timestamps displayed are fairly accurate, but, because various facilities are all writing to the screen real-time, it cannot be authoritatively concluded that the order of packets displayed is the actual order that the packets are being processed in, but it will be close.

- On the ingress side for Packet Data Switching Network (PDSN) or High Rate Packet Data Serving Gateway (HSGW) nodes, in order to view all of the A11 messaging (if that is important to view in the troubleshooting scenario, maybe it is not), monitor by Mobile Station Identification (MSID) instead of username, because the username is not yet known (has not yet been presented) at the beginning of the call and so cannot be displayed. If the MSID is not known, then take an initial trace which reveals it, then start over again monitoring by that MSID.

Here is an example where monitoring by MSID captures closer to the start of the call (A11 Response) versus at the point of the Mobile IP (MIP) Registration Request or even Radius Authentication when monitoring by username. In the username case, the call is caught at the FA service point, whereas in the MSID monitor it is caught earlier at the PDSN service point.

[local]PDSN> mon sub msid 111119782577072

----------------------------------------------------------------------

(Switching Trace) - New Incoming Call:

----------------------------------------------------------------------

MSID/IMSI   : 111119782577072             Callid      : 454a2432

IMEI        : n/a                         MSISDN      : n/a

Username    : n/a                         SessionType : unknown(0x00000000)

Status      : Dormant                     Service Name: ORP-1x

Src Context : source

----------------------------------------------------------------------

Wednesday June 17 2015

<<<<OUTBOUND  16:47:57:310 Eventid:29001(3)

A11 Tx PDU, from 10.208.144.30:699 to 10.211.17.206:699 (75)

Message Type: 0x03 (Registration Reply)

Code: 0x00 (Accepted)

Lifetime: 0x0708

[local]PDSN> mon sub user 9782577072@cisco.com

----------------------------------------------------------------------

Incoming Call:

----------------------------------------------------------------------

MSID/IMSI   : 111119782577072             Callid      : 110b36ad

IMEI        : n/a                         MSISDN      : n/a

Username    : 9782577072@cisco.com        SessionType : unknown(0x00000010)

Status      : Dormant                     Service Name: FA_service-1

Src Context : destination

----------------------------------------------------------------------

Wednesday June 17 2015

<<<<OUTBOUND  17:11:53:987 Eventid:23901(6)

RADIUS AUTHENTICATION Tx PDU, from 10.208.148.133:24912 to 198.51.100.1:1645 (401) PDU-dict=custom9

Code: 1 (Access-Request)

Id: 81

Length: 401

Authenticator: CB 94 F3 4B 04 77 9F 4A 7A 44 FA 13 C9 7A 60 3C

Calling-Station-Id = 111119782577072

- Turning on User L3 (19) in many scenarios will not yield more information than would otherwise be captured, but rather it results in duplicates of many packets.

- Turning on certain protocols will result in duplicate packets, for example for Mobile IP, MIP packets display twice, as both Point-to-Point Protocol (PPP) and as MIP.

- The output reads much better with a non-proportional font such as courier because the columns line up perfectly, so do analysis using such a font.

- The output that passes through a particular interface should line up with a packet capture on that interface, the difference being that the monitor subscriber output would be a subset because not every single field in an IP packet will be displayed, as it is not necessarily relevant in troubleshooting the protocol in question. For example, most fields from IP headers are not displayed. If those fields are needed, then turn on HEX/ASCII option.

- A lot of the output will be interpreted according to the standard, so instead of displaying an actual integer value, the system prints a textual representation of the value. Turn on verbosity 3 and/or the hex/ascii dump to see the raw data.

Here is example output of verbosity 3 vs. 2, followed by HEX/ASCII for an entire A11 packet:

Application Sub Type: 0x01 (Radius)

Radius Attr: Attribute Type: 26 (Vendor-Specific)

Length: 12

Vendor Id: 5535 (ThreeGPP2)

Vendor Type: 40 (3GPP2-Airlink-Record-Type)

Vendor Length: 6

Value: 00 00 00 02             ....

(Active-Start)

Application Sub Type: 0x01 (Radius)

Radius Attr: 3GPP2-Airlink-Record-Type = Active-Start

0x0000   010a 0708 0000 0000 0ad0 901e 0ad0 9158        ...............X

0x0010   d92c 509a 0265 af7e 2715 8881 ecba aed8        .,P..e.~'.......

0x0020   0000 0001 0006 0811 1111 4290 4988 6126        ..........B.I.a&

0x0030   0000 d800 0015 9f01 011a 0c00 0015 9f28        ...............(

0x0040   0600 0000 021a 0c00 0015 9f29 06ec baae        ...........)....

0x0050   d81a 0c00 0015 9f2a 0600 0000 011a 1600        .......*........

0x0060   0015 9f74 1041 3030 3030 3034 4444 3045        ...t.A000004DD0E

0x0070   4535 331a 1400 0015 9f0a 0e30 3031 3230        E53........00120

0x0080   3030 3330 3131 341a 0c00 0015 9f0b 0600        0030114.........

0x0090   0000 001a 0c00 0015 9f0c 0600 0000 001a        ................

0x00a0   0c00 0015 9f0d 0600 0000 001a 0c00 0015        ................

0x00b0   9f10 0600 0000 211a 0c00 0015 9f11 0600        ......!.........

0x00c0   0000 001a 0c00 0015 9f12 0600 0000 001a        ................

0x00d0   0c00 0015 9f13 0600 0000 001a 0c00 0015        ................

0x00e0   9f14 0600 0000 001a 0c00 0015 9f15 0600        ................

0x00f0   0000 001a 0c00 0015 9f32 0600 0000 001a        .........2......

0x0100   0c00 0015 9f27 0600 0000 0020 1400 0001        .....'..........

0x0110   00b3 c5f0 257e 8e93 c719 1b79 3ef9 30be        ....%~.....y>.0.

0x0120   07

- Not all fragmented packets are displayed because the Network Processor Unit (NPU) combines fragments received from the wire before giving them to sessmgr process that handles calls and where the monitor subscriber output it generated. Similarly for the outbound direction, fragmenting done by the NPU is not displayed.

- On a Combo Foreign Agent (FA) / HA chassis, the output from only one of the user sessions is displayed. For example, if radius authentication on the FA is seen, it does not display on the HA part of the call. Use monitor protocol in these situations, if feesible, for the specific protocols to be captured.

- When troubleshooting issues between nodes (i.e. FA and HA), take a trace on both chassis if the problem spans across them or if doing so could help eliminate some possibilities.

For example here is the same packet sent from the FA to the HA:

PDSN/FA:

<<<<OUTBOUND  23:57:08:941 Eventid:27001(0)

MIP-TUNNEL (IPv4-IPv4) Tx PDU

203.0.113.1 > 203.0.113.2: 10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84) (ttl 255, id 0, len 104)

HA:

INBOUND>>>>>  23:57:08:943 Eventid:27000(0)

MIP-TUNNEL (IPv4-IPv4) Rx PDU

203.0.113.1 > 203.0.113.2: 10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84) (ttl 251, id 0, len 104)

- Packets sent out and received from the egress interface of the Packet Data Network (PDN) (this does not include the egress of an FA for example, because the egress is an FA-HA IP tunnel), are NOT displayed per the architecture of the system of NOT displaying packets on untunneled interfaces. If a packet comes in the ingress and then a response is sent out the ingress, then that implies that the packet made it to its destination and back (including if the destination was the chassis itself). But if no response is sent out the ingress and it was expected, then it needs to be determined if it did get sent out the egress to eliminate the ASR as a culprit, and if so, was a response ever received on the egress? This applies to both directions actually. Packet sniffers on the respective ingress or egress interfaces and other points in the transport network, including logging at various points in the transport including the termination points (User equipment or network/internet server), may be helpful in pinpointing the cause of non-response.

Here is an ICMP request and response on an FA and HA where the packet is only shown on the ingress (FA-HA tunnel) side of the HA, but on both the ingress and egress sides of the FA, since both interfaces are tunneled. Note the only field that changes between the FA and HA is the Time to Live (TTL) value as it traverses network nodes:

INBOUND>>>>>  23:57:08:941 Eventid:25000(0)

PPP Rx PDU (85)

IP 85: 10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 63, id 13840, len 84)

<<<<OUTBOUND  23:57:08:941 Eventid:27001(0)

MIP-TUNNEL (IPv4-IPv4) Tx PDU

203.0.113.1 > 203.0.113.2: 10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84) (ttl 255, id 0, len 104)

INBOUND>>>>>  23:57:08:943 Eventid:27000(0)

MIP-TUNNEL (IPv4-IPv4) Rx PDU

203.0.113.1 > 203.0.113.2: 10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84) (ttl 251, id 0, len 104)

<<<<OUTBOUND  23:57:09:029 Eventid:27001(0)

MIP-TUNNEL (IPv4-IPv4) Tx PDU

203.0.113.2 > 203.0.113.1: 192.0.2.1 > 10.251.88.68: icmp: echo reply (ttl 42, id 27830, len 84) (ttl 255, id 0, len 104)

Monday May 18 2015

INBOUND>>>>>  23:57:09:030 Eventid:27000(0)

MIP-TUNNEL (IPv4-IPv4) Rx PDU

203.0.113.2 > 203.0.113.1: 192.0.2.1 > 10.251.88.68: icmp: echo reply (ttl 42, id 27830, len 84) (ttl 251, id 0, len 104)

Monday May 18 2015

<<<<OUTBOUND  23:57:09:030 Eventid:25001(0)

PPP Tx PDU (88)

IP 88: 192.0.2.1 > 10.251.88.68: icmp: echo reply (ttl 41, id 27830, len 84)

* There is no built-in packet sniffer on the ASR interfaces that customers can access, but TAC has some capability in this area depending on the protocol (user data cannot be captured nomatter what)

When analyzing the mon sub output, consider the following:

- are there packets missing that are expected to be seen (i.e. responses from outside the chassis or requests from the chassis or forwarded packets from the chassis)

- can packets be seen going in the opposite direction than is being troubleshot (to confirm at least one direction is working)

- are packets being sent/received at expected intervals realtime and/or according to specification/configured timer values

- are packets being sent/received in expected order per the protocol (see caveat earlier about ordering)

- are the various fields in packets containing the correct/expected values (port numbers, ip addresses, etc.)

- for TCP/IP, is the connection properly setup and torn down. Identification of TCP flags used by mon sub includes S (SYN), . followed by Ack on line (Acknowledgement), S followed by Ack later on line (SYN Ack), P (Push), R (Reset), F (FIN)

- is the problem consistently happening or randomly

- is there any pattern with respect to subscriber call control type, subscriber id (username, msid, imsi, etc.), Private or NAT IP pool or address range, UDP/TCP port numbers, network server (endpoint) address, type of user traffic (HTTP, SMS, FTP, UDP, etc.), peer call control node addresses (Ex: FA, HA, PCF, Policy & Charging Rules Function (PCRF), Serving Gateway (SGW), Diameter server, etc.), etc. Leave no stone unturned.

- familiarity with rules and custom protocol behaviors the service provider has put into place that may or may not be published/revealed - ask questions!!!

logging monitor

This is actually a global config command versus a runtime executive command used to monitor specific users. There are two advantages to using this command:

- there is no need to keep a CLI session open because all output is saved to logs

- it automatically saves debug level logs for all facilities for the subscriber, including the output that normally would appear with monitor subscriber. Though debug is a lot more than may be needed, no information is missed, and it is not intrusive to the system as turning on logging or monitor protocol would be for various facilities (since doing so would pull information for all subscribers using the monitored facilities).

- output may not be as easy/quick to read as that generated by monitor subscriber.  Typically TAC and/or engineering would need to interpret the output.

- in order to capture the details of protocol messages as would be captured by monitor subscriber (logging monitor only saves the first few lines of any protocol message), either run a monitor subscriber session simultaneously and later reference the output as needed when analyzing the logging monitor output, OR, turn on full event verbosity for logging (global config command "logging display event-verbosity full"). The latter approach does not require any additional work later because all of the output is already contiguous and complete.

logging trace

As opposed to logging monitor, this approach uses exec mode level access, but at the same time also requires the device to be already connected. This is useful to troubleshoot user data (and/or further call control events after the point of running the command) as opposed to call setup because the call needs to be already setup in order for this to work (otherwise is reports "No calls match the specified criteria" and achieves nothing). Similar to logging monitor, "show logs" displays all captured data.

monitor protocol

This command monitors all protocol exchange on a chassis for the specified protocol(s) (call control, data-plane) and the output is a similar style as monitor subscriber

- This should only be a last resort on a production chassis because of the potential load exerted, dependent on the protocol and packet volume for the protocol.

- Requires Administrator CLI access to run

- To get the output for a specific subscriber, it would need to be filtered by identifying type of information, such as username/MSID, callid, etc..

active or runtime logging

This captures output for specified facilities at specified level (range from error to debug)

- This has the same issues as with monitor protocol with regards to system load and filtering subscriber output

- Likely requires running/configuring a syslog server depending on the desire of facilities, debug level, and timeframe to go back, or else data could be overwritten by the time it is attempted to be retrieved on the chassis.

Subscriber commands

For all of the below subscriber commands, not only is the information for a particular subscriber available, but the hit list can be narrowed to a group of subscribers by any number of criteria, such as call control service they are attached to (PDSN, FA, HA, LAC, L2TP Network Server (LNS), ECS, LTE etc.) or entity that are communicating (peered) with (PCF, FA, HA, LAC, LNS, SGW, etc.), Packet Switching Card (PSC) attached to, connected or idle time left or session time left (greater/less than), amount of data received or sent (greater/less than), associated IP pool name, dormant/active, etc., or even various combinations of these and many other parameters. Using the online help to list out the possibilities and then to experiment with them is a great way to learn.

As mentioned earlier, it is not required to always know the specific subscriber to track. Rather knowing the category that the subscribers falls into leads to being able to obtain a list of the subscribers in the category, from which one can further narrow/analyze and choose particular subscribers to analyze. See the CLI auto-complete help for “show subscribers”.

When it does come time to choose a particular subscriber, qualification with one of the keywords such as username, International Mobile Subscriber Identitiy (IMSI), MSID, Mobile Station ISDN (MSISDN), etc. will be necessary.

show subscribers full

This is probably the number one subscriber command that exists and should be captured for every subscriber issue. It includes a TON of information for the specified subscriber and can be very useful for troubleshooting subscriber issues. While it is not feasible to discuss every field here, some fields obviously are commonly checked and referenced more than others, though each scenario is different depending on what is being troubleshot. Some things to keep in mind are:

- Some fields are not relevant depending on the call technology. For instance:- the Domain Named Server (DNS) address on an HA is not relevant because the DNS is given out from the PDSN/FA.

- Dormancy only has meaning on the access node and is always set to active on the gateway

- Some fields could be listed more than once

- Some fields may indicate one value but in fact another value ends up getting used. For instance, the RADIUS server that gets used may change if there are connectivity issues to the primary one

- For LTE and others, one output for each connected bearer per subscriber is displayed. So for example, if a subscriber is connected with three Application Point Names (APNs) where one APN has two bearers, then there would be four separate outputs one after the other.

- The various fields should be able to be correlated to the output of other CLIs including the configuration as necessary.

Interesting fields for PDSN/FA (Access node(s)) and HA (HA is a gateway type of node) node types, also applicable mostly to all the call types, include:

- Status - Dormant or Active.

- Access Type/Tech - technology on the ingress side of the call

- Network Type - technology on the egress side of the call

- Username, MSID, ip address, NAT ip address - ways to identify the subscriber.

Note: msid is not always msid. For example on a PGW it is IMSI.

- Callid - 8 hex digit ID used to track all activity for every session. A unique Callid exists for each APN on a Packet Data Network Gateway (PGW) or Multimedia Management Entity (MME)

- Sessmgr Instance - sessmgr instance handling the session (show task resources will list the sessmgrs)

- Card/Cpu - PSC or Data Processing Card (DPC) on which the sessmgr resides

- PCF, HA, FA, DNS addresses, etc. - self explanatory

- connected time - when the call connected

- call duration - how long the call has been connected.

Note: May be different between FA and HA if subscriber has roamed, since the new FA node would not know the total life the original call has been up for

- idle time - how long user data (control packets are not counted) has not been exchanged

- session time left - how much longer the session can last before being terminated (controlled by hard-coded configuration, returned in authentication, and/or negotiated amongst nodes)

- MIP FA / MIP HA - various values for the MIP session

- Input Pkts/Bytes - # of user Packets/Bytes received from the subscriber via the ingress side

- Output Pkts/Bytes - # of user Packets/Bytes sent towards the subscriber via the ingress side.

Notes:

- These counters apply to the ingress side. There are no counters on the egress side!!

- There should be a close correlation of these counts and the packets sent to/from ECS but there might not be an exact match

- input pkts dropped/output pkts dropped - note that packets may actually get dropped outside of ECS, such as multi-cast packets, or dropped by an Access Control List (ACL) in the context (so don't assume all packet drops are in ECS).

Gateway nodes:

- ip pool name - IP pool from which IP addressed are retrieved. Relevant only on call endpoint (gateway) since other nodes (i.e. PDSN) have no way to know the pool name, only the address.

- ECS Rulebase - rulebase in Active Charging Service (ACS) containing rules to apply to subscriber packets

- Nat ip address - publicly routable IP address which NATs the subscribers privately assigned IP address

- NAT Realm - grouping of associated NAT IP pools used in ECS service

- (on-demand) - whether NAT address is permanently or temporarily assigned to the subscriber (per pool configuration)

- (NAT IP pool name) - NAT pool name

- Nexthop ip address - next hop address of IP pool to where packets should be forwarded

- Nat port chunks allocated - number of ports available and used and range of those ports for NATing with NAT IP

- Downlink CSS Information/Uplink CSS Information - Counts for uplink (input) and downlink (output) directions for packets processed by ECS service

The following is an abbreviated output (some "less important" fields removed) for "show sub full" taken at the same time for the same subscriber on both a PDSN and HA, making it easy to correlate the output between the two including the packet counts.

PDSN> show sub full username 9782577072@cisco.com

Monday May 18 23:56:20 UTC 2015

Username: 9782577072@cisco.com       Status: Dormant

Access Type: pdsn-mobile-ip        Network Type: Mobile-IP

Access Tech: CDMA 1xRTT           Access Network Peer ID: n/a

callid: 3ee822d2                   msid: 111119782577072

Card/Cpu: 15/0                     Sessmgr Instance: 212

state: Connected                   PCF address: 10.211.17.207

connect time: Mon May 18 23:45:54 2015 call duration: 00h10m35s

idle time: 00h02m30s               idle time left: 02h02m30s

session time left: 23h44m25s       ip address: 10.251.88.68

Primary DNS Address: 209.165.200.225

Secondary DNS Address: 209.165.200.226

home-agent:  203.0.113.2

fa-service name: FA9  (context destination)

source context: source       destination context: destination

AAA context: source                AAA domain: cisco.com

AAA start count: 1                 AAA stop count: 0

AAA interim count(RADIUS+GTPP): 0  Acct-session-id: 69A9CDEB

AAA RADIUS group: aaa-cisco.com

RADIUS Auth Server IP: 198.51.100.1

RADIUS Acct Server IP: 198.51.100.1

NAS IP Address: 10.208.148.133

MIPFA Session:                  Care-of-Address: 203.0.113.1

Home-Address: 10.251.88.68     HA-Address: 203.0.113.2

Lifetime: 02h00m00s              Remaining Life: 01h49m25s

Revocation Negotiated: yes Revocation I Bit Negotiated: Yes

input pkts: 254                       output pkts: 229

input bytes: 24088                    output bytes: 129012

input pkts dropped: 0                  output pkts dropped: 0

dormancy total: 11                  handoff total: 0

Num Auxiliary A10s:1

PCF Address     SR_ID

10.211.17.207      1

[local]HA> show sub full username 9782577072@cisco.com

Monday May 18 23:56:14 UTC 2015

Username: 9782577072@cisco.com           Status: Online/Active

Access Type: ha-mobile-ip              Network Type: IP

Access Tech: Other                     Access Network Peer ID: n/a

callid: 4a6ae475                       msid: n/a

Card/Cpu: 2/0                          Sessmgr Instance: 329

state: Connected                       FA address: 66.174.112.72

connect time: Mon May 18 23:45:54 2015 call duration: 00h10m28s

idle time: 00h02m23s                idle time left:  n/a

session time left: 23h49m32s

ip address: 10.251.88.68

ip pool name: MIP_Private

ha-service name: HA1

source context: HA                     destination context: XGWout

Acct-session-id: A414F3F6

RADIUS Auth Server IP: 198.51.100.1    RADIUS Acct Server IP: n/a

NAS IP Address: 10.208.148.135         Nexthop IP Address: 209.165.200.230

active input acl: ECS_ACL              active output acl: ECS_ACL

ECS Rulebase: 201                      Firewall-and-Nat Policy: MIP

Nat Realm: MIP_NAT_Int       Nat ip address: 170.200.132.0   (on-demand) (MIP_NAT_Int04)

Nexthop ip address: 209.165.200.230

Nat port chunks allocated[start - end]: (1 chunk) [6464 - 6495]

Max NAT port chunks used: 1

HA binding care-of-addr(s): 203.0.113.1

MIPHA binding 1:  Care-of-Address: 203.0.113.1

FA Address/Port: 203.0.113.1/434

Home-Address: 10.251.88.68           HA-Address: 203.0.113.2

Lifetime: 02h00m00s                  Remaining Life: 01h49m32s

Revocation Negotiated: Yes           Revocation I Bit Negotiated: Yes

MN-HA-Key-Present: TRUE              MN-HA-SPI:300

FA-HA-Key-Present: TRUE              FA-HA-SPI:8832

Proxy DNS Intercept List: ROAMINGDNS

Downlink CSS Information

Service/ACL Names: /ECS_ACL

downlink pkts to svc: 229          downlink pkts from svc: 229

Uplink CSS Information

Service/ACL Names: /ECS_ACL

uplink pkts to svc: 254            uplink pkts from svc: 252

input pkts: 254                                 output pkts: 229

input bytes: 24088                              output bytes: 129012

Based on the following ICMP Request/Response packet exchange between FA and HA nodes (there were actually 4 ICMP exchanges, only one shown here), the ensuing packet/byte counts tracked by "show sub full" are shown:

[local]PDSN> show sub full username 9782577072@cisco.com

Monday May 18 23:56:20 UTC 2015

input pkts: 254                      output pkts: 229

input bytes: 24088                   output bytes: 129012

input pkts dropped: 0                output pkts dropped: 0

[local]PDSN> show sub full username 9782577072@cisco.com

Monday May 18 23:57:25 UTC 2015

input pkts: 258                      output pkts: 233

input bytes: 24424                   output bytes: 129348

INBOUND>>>>>  23:57:08:943 Eventid:27000(0)

MIP-TUNNEL (IPv4-IPv4) Rx PDU

203.0.113.1 > 203.0.113.2: 10.251.88.68 > 192.0.2.1: icmp: echo request (ttl 62, id 13840, len 84) (ttl 251, id 0, len 104)

<<<<OUTBOUND  23:57:09:029 Eventid:27001(0)

MIP-TUNNEL (IPv4-IPv4) Tx PDU

203.0.113.2 > 203.0.113.1: 192.0.2.1 > 10.251.88.68: icmp: echo reply (ttl 42, id 27830, len 84) (ttl 255, id 0, len 104)

[local]HA> show sub full username 9782577072@cisco.com

Monday May 18 23:56:14 UTC 2015

Downlink CSS Information

downlink pkts to svc: 229        downlink pkts from svc: 229

Uplink CSS Information

uplink pkts to svc: 254          uplink pkts from svc: 252

input pkts: 254                  output pkts: 229

input bytes: 24088               output bytes: 129012

[local]HA> show sub full username 9782577072@cisco.com

Monday May 18 23:57:34 UTC 2015

Downlink CSS Information

downlink pkts to svc: 233        downlink pkts from svc: 233

Uplink CSS Information

uplink pkts to svc: 258          uplink pkts from svc: 256

input pkts: 258                   output pkts: 233

input bytes: 24424                output bytes: 129348

The following example snippet is for a Voice over LTE (VoLTE) call. Interpreting can be tricky because there are two subscribers listed and the differentiation is not crystal clear between them.

- The first one listed is the default IP Multimedia System (IMS) bearer and the second is the dedicated (VoLTE) bearer, both part of the same APN

- The Acct-session-id: is a differentiator.

- The input/output pkts/bytes are different between the two bearers, and because the dedicated bearer would be sending many more (voice) packets, one could assume that the subscriber with the higher count would be the dedicated bearer, meanwhile ... packet counts to / from ECS is listed the same for both (the amount used by the default bearer)

- The connect time display for both displays the default bearer connection time even though the dedicated connected later.

- The way to get more useful and accurate, less tricky information for PGW calls is with "show pgw-only full" (discussed later)

[local]PGW> show sub full imsi 300420060496012

Monday September 16 21:50:07 UTC 2013

Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org Status: Online/Active

Access Type: gtp-pdn-type-ipv6         Network Type: IPv6

Access Tech: eUTRAN                    Access Network Peer ID: n/a

callid: 22075719                       msid: 300420060496012

Card/Cpu: 7/1                          Sessmgr Instance: 115

state: Connected                       SGW Address: 203.0.113.3

connect time: Mon Sep 16 21:44:28 2013 call duration: 00h05m42s

idle time: 00h00m00s                   idle time left: 02h05m00s

session time left: 08759h54m

long duration time left:  n/a          long duration action:  n/a

always on: Disabled

ip address: 2001:db8::1

ip pool name: ims61-03

source context: XGWin                  destination context: XGWout

...

AAA context: XGWin                     AAA domain: XGWin

...

Acct-session-id: 42AE2B922619E10F

...

active input acl: n/a                  active output acl: n/a

active input ipv6 acl: ECS_ACL_V6      active output ipv6 acl: ECS_ACL_V6

ECS Rulebase: PGW

...

P-CSCF address :

Primary:  2001:db8::fd

Secondary:  2001:db8::fe

Tertiary:   n/a

...

Downlink CSS Information

Service/ACL Names: /ECS_ACL_V6

(Active Charging Optimized Mode)

downlink pkts to svc: 658          downlink pkts from svc: 658

Uplink CSS Information

Service/ACL Names: /ECS_ACL_V6

(Active Charging Optimized Mode)

uplink pkts to svc: 675            uplink pkts from svc: 675

Collapsed cscf subscribers: none

input pkts: 29                             output pkts: 45

input bytes: 10578                         output bytes: 10763

input bytes dropped: 0                     output bytes dropped: 0

input pkts dropped: 0                      output pkts dropped: 0

...

pk rate from user(bps): 1375               pk rate to user(bps): 1699

ave rate from user(bps): 458               ave rate to user(bps): 566

sust rate from user(bps): 456              sust rate to user(bps): 564

pk rate from user(pps): 0                  pk rate to user(pps): 1

...

CAE Server Address:

Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org Status: Online/Active

Access Type: gtp-pdn-type-ipv6         Network Type: IPv6

Access Tech: eUTRAN                    Access Network Peer ID: n/a

callid: 22075719                       msid: 300420060496012

Card/Cpu: 7/1                          Sessmgr Instance: 115

state: Connected                       SGW Address: 203.0.113.3

connect time: Mon Sep 16 21:44:28 2013 call duration: 00h05m42s

idle time: 00h00m00s                   idle time left: 02h05m00s

session time left: 08759h54m

long duration time left:  n/a          long duration action:  n/a

always on: Disabled

ip address: 2001:db8::1

ip pool name: ims61-03

source context: XGWin                  destination context: XGWout

...

AAA context: XGWin                     AAA domain: XGWin

AAA start count: 0                     AAA stop count: 0

AAA interim count(RADIUS+GTPP): 0

Acct-session-id: 42AE2B922619E18D

...

active input ipv6 acl: ECS_ACL_V6      active output ipv6 acl: ECS_ACL_V6

ECS Rulebase: PGW

P-CSCF address :

Primary:  2001:db8::fd

Secondary:  2001:db8::fe

Tertiary:   n/a

...

Downlink CSS Information

Service/ACL Names: /ECS_ACL_V6

(Active Charging Optimized Mode)

downlink pkts to svc: 658          downlink pkts from svc: 658

Uplink CSS Information

Service/ACL Names: /ECS_ACL_V6

(Active Charging Optimized Mode)

uplink pkts to svc: 675            uplink pkts from svc: 675

Collapsed cscf subscribers: none

input pkts: 643                            output pkts: 617

input bytes: 58421                         output bytes: 55925

...

pk rate from user(bps): 1375               pk rate to user(bps): 1699

ave rate from user(bps): 458               ave rate to user(bps): 566

sust rate from user(bps): 456              sust rate to user(bps): 564

pk rate from user(pps): 0                  pk rate to user(pps): 1

show subscribers (hsgw-only | pgw-only | ggsn-only | mme-only | sgw-only | sgsn-only) full

Some of these have very useful information that is specifically tailored to the call type than just normal show subscriber full (which is more generic where many fields apply to all call types, though some fields still are specific to certain call types)

- In the case of hsgw-only and ggsn-only, there is no difference in output compared to normal "show sub full" except that the qualifier automatically limits the hit list to calls of the specified type.

- MSISDN effectively lists the device phone number

- Field name IMSI is explicitly and correctly listed

- Note that Bearers from the same APN have the same Callid

- Bearer Type and Bearer-ID - distinguish between the various bearers

- QCI - Quality of Service Identifier (ranges from 1 to 9). In this case QCI 1 is for voice and QCI 5 is for IMS control

- c-teid, u-teid - Terminal Endpoint Identifiers for Control and User plane are necessary for identifying what bearer to associate data packets with

- S5/S8/S2b-APN, SGi-APN - The APN of the bearer

- input pkts/output pkts - packet counts are for the bearer itself

- MBR/GBR Uplink/Downlink - Maximum and Guaranteed Bit rates in both directions. Note 38000 bits/sec for VoLTE which is about the bitrate for the VoLTE codecs.

The following example snippet is for the same Voice over LTE (VoLTE) call as shown with "show sub full" above, taken around the same time (see timestamp), so that useful comparisons of output can be made if interested. It also includes the Internet APN that was also connected at the time:

[local]PGW> show sub pgw-only full imsi 300420060496012

Monday September 16 21:50:25 UTC 2013

Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

Subscriber Type : Home

Status          : Online/Active

State           : Connected

Connect Time    : Mon Sep 16 21:44:28 2013

Idle time       : 00h00m00s

MS TimeZone     : +5:00        Daylight Saving Time: +1 hour

Access Type: gtp-pdn-type-ipv6         Network Type: IPv6

Access Tech: eUTRAN                    pgw-service-name: PGW1

Callid: 22075719                       IMSI: 300420060496012

Protocol Username:                     MSISDN: 19126757869

Interface Type: S5S8GTP

Emergency Bearer Type: N/A

S6b Auth Status: Enabled

Acct-session-id (C1): 42AE2B922619E10F

ThreeGPP2-correlation-id (C2): 3939BA30 / h0WKcCZS

Card/Cpu: 7/1                          Sessmgr Instance: 115

Bearer Type: Default                   Bearer-Id: 5

Bearer State: Active

IP allocation type: N/A

IPv6 allocation type: local pool

IP address: 2001:db8::1

Framed Routes: N/A                              Framed Routes Source: N/A

ULI:

TAI-ID:

MCC: 300  MNC: 420

TAC: 0x8504

ECGI-ID:

MCC: 300 MNC: 420

ECI: 0x207b201

Accounting mode: None                  APN Selection Mode: Subscribed

MEI: 9900015028325700                  Serving Nw: MCC=300, MNC=420

Charging id: 639230223                 Charging chars: normal

Source context: XGWin                  Destination context: XGWout

S5/S8/S2b-APN: IMSAPN

SGi-APN:   IMSAPN

APN-OI:    mnc420.mcc300.gprs

IMS Auth Service : IMS-GX

active input ipv4 acl:                 active output ipv4 acl:

active input ipv6 acl: ECS_ACL_V6      active output ipv6 acl: ECS_ACL_V6

ECS Rulebase: PGW

Bearer QoS:

QCI: 5

ARP: 0x069

PCI: 1 (Disabled)

PL : 10

PVI: 1 (Disabled)

MBR Uplink(bps): 0                    MBR Downlink(bps): 0

GBR Uplink(bps): 0                    GBR Downlink(bps): 0

P-CSCF address :

1:  2001:db8::fd

2:  2001:db8::fe

3:   NA

Access Point MAC Address:  N/A

pgw c-teid: [0x8d11c073] 2366750835    pgw u-teid: [0xc20d0073] 3255631987

sgw c-teid: [0x00160880] 1443968       sgw u-teid: [0x00160885] 1443973

ePDG c-teid: N/A                       ePDG u-teid: N/A

pgw c-addr: 203.0.113.4                pgw u-addr: 203.0.113.4

2001:db8::1f

sgw c-addr: 203.0.113.3                sgw u-addr: 203.0.113.3

ePDG c-addr: N/A                       ePDG u-addr: N/A

Downlink APN AMBR:        600 Kbps    Uplink APN AMBR:        600 Kbps

input pkts: 29                         output pkts: 45

input bytes: 10578                     output bytes: 10763

input bytes dropped: 0                 output bytes dropped: 0

input pkts dropped: 0                  output pkts dropped: 0

...

pk rate from user(bps): 27699          pk rate to user(bps): 24879

ave rate from user(bps): 9691          ave rate to user(bps): 8859

sust rate from user(bps): 9720         sust rate to user(bps): 8885

pk rate from user(pps): 37             pk rate to user(pps): 34

ave rate from user(pps): 12            ave rate to user(pps): 11

sust rate from user(pps): 12           sust rate to user(pps): 11

link online/active percent: 100

...

CAE Server Address:

Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

Subscriber Type : Home

Status          : Online/Active

State           : Connected

Connect Time    : Mon Sep 16 21:49:53 2013

Idle time       : 00h00m00s

MS TimeZone     : +5:00        Daylight Saving Time: +1 hour

Access Type: gtp-pdn-type-ipv6         Network Type: IPv6

Access Tech: eUTRAN                    pgw-service-name: PGW1

Callid: 22075719                       IMSI: 300420060496012

Protocol Username:                     MSISDN: 19126757869

Interface Type: S5S8GTP

Emergency Bearer Type: N/A

S6b Auth Status: Enabled

Acct-session-id (C1): 42AE2B922619E18D

ThreeGPP2-correlation-id (C2): 3939BA30 / h0WKcCZS

Card/Cpu: 7/1                          Sessmgr Instance: 115

Bearer Type: Dedicated                 Bearer-Id: 7

Bearer State: Active

IP allocation type: N/A

IPv6 allocation type: local pool

IP address: 2001:db8::1

Framed Routes: N/A                              Framed Routes Source: N/A

ULI:

TAI-ID:

MCC: 300  MNC: 420

TAC: 0x8504

ECGI-ID:

MCC: 300 MNC: 420

ECI: 0x207b201

Accounting mode: None                  APN Selection Mode: Subscribed

MEI: 9900015028325700                  Serving Nw: MCC=300, MNC=420

Charging id: 639230349                 Charging chars: normal

Source context: XGWin                  Destination context: XGWout

S5/S8/S2b-APN: IMSAPN

SGi-APN:   IMSAPN

APN-OI:    mnc420.mcc300.gprs

IMS Auth Service : IMS-GX

active input ipv4 acl:                 active output ipv4 acl:

active input ipv6 acl: ECS_ACL_V6      active output ipv6 acl: ECS_ACL_V6

ECS Rulebase: PGW

Bearer QoS:

QCI: 1

ARP: 0x06d

PCI: 1 (Disabled)

PL : 11

PVI: 1 (Disabled)

MBR Uplink(bps): 38000                MBR Downlink(bps): 38000

GBR Uplink(bps): 38000                GBR Downlink(bps): 38000

P-CSCF address :

1:  2001:db8::fd

2:  2001:db8::fe

3:   NA

Access Point MAC Address:  N/A

pgw c-teid: [0x8d11c073] 2366750835    pgw u-teid: [0xc1f20073] 3253862515

sgw c-teid: [0x00160880] 1443968       sgw u-teid: [0x00160887] 1443975

ePDG c-teid: N/A                       ePDG u-teid: N/A

pgw c-addr: 203.0.113.4                pgw u-addr: 203.0.113.4

2001:db8::1f

sgw c-addr: 203.0.113.3                sgw u-addr: 203.0.113.3

ePDG c-addr: N/A                       ePDG u-addr: N/A

Downlink APN AMBR:        600 Kbps    Uplink APN AMBR:        600 Kbps

input pkts: 1640                          output pkts: 1614

input bytes: 149478                       output bytes: 146930

input bytes dropped: 0                    output bytes dropped: 0

input pkts dropped: 0                     output pkts dropped: 0

...

pk rate from user(bps): 27699             pk rate to user(bps): 24879

ave rate from user(bps): 9691             ave rate to user(bps): 8859

sust rate from user(bps): 9720            sust rate to user(bps): 8885

pk rate from user(pps): 37                pk rate to user(pps): 34

ave rate from user(pps): 12               ave rate to user(pps): 11

sust rate from user(pps): 12              sust rate to user(pps): 11

CAE Server Address:

Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

Subscriber Type : Home

Status          : Online/Active

State           : Connected

Connect Time    : Mon Sep 16 21:44:33 2013

Idle time       : 00h02m04s

MS TimeZone     : +5:00        Daylight Saving Time: +1 hour

Access Type: gtp-pdn-type-ipv4-ipv6    Network Type: IPV4+IPv6

Access Tech: eUTRAN                    pgw-service-name: PGW1

Callid: 2207571f                       IMSI: 300420060496012

Protocol Username:                     MSISDN: 19126757869

Interface Type: S5S8GTP

Emergency Bearer Type: N/A

S6b Auth Status: Enabled

Acct-session-id (C1): 42AE2B922619E115

ThreeGPP2-correlation-id (C2): 3939BA36 / h0WKfBYt

Card/Cpu: 7/1                          Sessmgr Instance: 115

Bearer Type: Default                   Bearer-Id: 6

Bearer State: Active

IP allocation type: local pool

IPv6 allocation type: local pool

IP address: 2001:db8::2, 10.174.230.156

Framed Routes: N/A                              Framed Routes Source: N/A

ULI:

TAI-ID:

MCC: 300 MNC: 420

TAC: 0x8504

ECGI-ID:

MCC: 300 MNC: 420

ECI: 0x207b201

Accounting mode: None                  APN Selection Mode: Subscribed

MEI: 9900015028325700                  Serving Nw: MCC=300, MNC=420

Charging id: 639230229                 Charging chars: normal

Source context: XGWin                  Destination context: XGWout

S5/S8/S2b-APN: INTERNET

SGi-APN:   INTERNET

APN-OI:    mnc420.mcc300.gprs

IMS Auth Service : IMS-GX

active input ipv4 acl: ECS_ACL_V4      active output ipv4 acl: ECS_ACL_V4

active input ipv6 acl: ECS_ACL_V6      active output ipv6 acl: ECS_ACL_V6

ECS Rulebase: OCS

Bearer QoS:

QCI: 9

ARP: 0x069

PCI: 1 (Disabled)

PL : 10

PVI: 1 (Disabled)

MBR Uplink(bps): 0                    MBR Downlink(bps): 0

GBR Uplink(bps): 0                    GBR Downlink(bps): 0

P-CSCF address :

1:   NA

2:   NA

3:   NA

Access Point MAC Address:  N/A

pgw c-teid: [0x8c298073] 2351530099    pgw u-teid: [0xc20b8073] 3255533683

sgw c-teid: [0x31580880] 827852928     sgw u-teid: [0x31580886] 827852934

ePDG c-teid: N/A                       ePDG u-teid: N/A

pgw c-addr: 203.0.113.4                pgw u-addr: 203.0.113.4

2001:db8::1f

sgw c-addr: 203.0.113.3                sgw u-addr: 203.0.113.3

ePDG c-addr: N/A                       ePDG u-addr: N/A

Downlink APN AMBR:      75000 Kbps    Uplink APN AMBR:      75000 Kbps

input pkts: 21                                  output pkts: 23

input bytes: 2687                               output bytes: 6457

input bytes dropped: 0                          output bytes dropped: 0

input pkts dropped: 0                           output pkts dropped: 0

...

CAE Server Address:

Total subscribers matching specified criteria: 3

show active-charging sessions full

This is probably the second most important subscriber command behind "show sub full", even more important on the gateways if troubleshooting ECS-related issues such as packet drops, online charging, IMS (PCRF) authorization.

- Uplink and Downlink Packets and Bytes should match those reportedly sent to/from ECS in "show sub pgw-only"

- Be aware of the various fields that track dropped packets

- Dynamic-Rule-Name entries are rules returned by the PCRF via Gx interaction at initial and ongoing PCRF interaction. The packet counts matching the rule are listed along with their definitions

- For charging rule definitions (in this example it's the dedicated VoLTE bearer), quota, usage, and time are also listed

To be consistent, the following example snippet is for the same Voice over LTE (VoLTE) call as shown with "show sub full" and "show sub pgw-only full" above, taken around the same time (see timestamp), so that useful comparisons of output can be made if interested.

- Additionally shown is the Internet APN which captures online charging data

- rule 0_0 is for the voice (Realtime Transport Protocol (RTP)) data, and 0_1 is for Realtime Control Protocol (RCP) - which is used to communicate the quality of the link and voice over that link over time. No packets have passed over RCP bearer at the time this CLI was run.

[local]PGW> show active-charging sessions full imsi 300420060496012

Monday September 16 21:50:18 UTC 2013

Session-ID:             115:12023212  Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

Callid:                     22075719  IMSI/MSID:          300420060496012

MSISDN:                                                       19126757869

ACSMgr Instance:                 115  ACSMgr Card/Cpu:                7/1

SessMgr Instance:                                                     115

Client-IP:                                                     2001:db8::

NAS-IP:                                                           0.0.0.0

Access-NAS-IP(FA):

NAS-PORT:                         0   NSAPI:                            5

Acct-Session-ID:                                                 393A43B1

NAS-ID:                                                               n/a

Access-NAS-ID(FA):                                                    n/a

3GPP2-BSID:                                                           n/a

Access-Correlation-ID(FA):                                            n/a

3GPP2-Correlation-ID:                                                 n/a

MEID:                                                                 n/a

Carrier-ID:                      n/a  ESN:                            n/a

Uplink Bytes:                  10778  Downlink Bytes:               10411

Uplink Packets:                   32  Downlink Packets:                41

Injected Uplink Bytes:             0  Injected Downlink Bytes:          0

Injected Uplink Packets:           0  Injected Downlink Packets:        0

Buffered Uplink Packets:           0  Buffered Downlink Packets:        0

Buffered Uplink Bytes:             0  Buffered Downlink Bytes:          0

Uplink Packets in Buffer:          0  Uplink Bytes in Buffer:           0

Downlink Packets in Buffer:        0  Downlink Bytes in Buffer:         0

Buff Over-limit Uplink Pkts:       0  Buff Over-limit Uplink Bytes:     0

Buff Over-limit Downlink Pkts:     0  Buff Over-limit Downlink Bytes:   0

Processed Uplink Packets:          0  Processed Downlink Packets:       0

Dropped Uplink Packets:            0  Dropped Downlink Packets:         0

Uplink Out of Order Packets:       0  Downlink Out of Order Packets:    0

Dyn FUI Redirected Flows:          0  Dyn FUI Discarded Pkts:           0

ITC Terminated Flows:              0  ITC Redirected Flows:             0

ITC Dropped Packets:               0  ITC ToS Remarked Packets:         0

ITC Dropped Upl Pkts:              0  ITC Dropped Dnl Pkts:             0

ITC Dropped Upl Bytes:             0  ITC Dropped Dnl Bytes:            0

Flow action Terminated Flows:                                           0

PP Flow action Terminated Flows:                                        0

CC Dropped Uplink Packets:         0  CC Dropped Uplink Bytes:          0

CC Dropped Downlink Packets:       0  CC Dropped Downlink Bytes:        0

NRUPC Req Made:                    1  NRUPC Req Success:                1

NRUPC Req Failed:                  0  NRUPC Req Time Out:               0

Dynamic Rule Limiting: Enabled

Bearer Bandwidth Limiting: Enabled

Uplink MBR (bps):                  0  Downlink MBR (bps):               0

Uplink GBR (bps):                  0  Downlink GBR (bps):               0

Uplink Burst (bytes):              0  Downlink Burst (bytes):           0

Dropped Uplink Pkts:               0  Dropped Downlink Pkts:            0

Dropped Uplink Bytes:              0  Dropped Downlink Bytes:           0

Current Readdressed Sessions:                                           0

Total Readdressed Uplink Pkts:                                          0

Total Readdressed Uplink Bytes:                                         0

Total Readdressed Downlink Pkts:                                        0

Total Readdressed Downlink Bytes:                                       0

Total Readdressing Failure Packets:                                     0

Non Syn Flow:                    0  Duplicate Key:                    0

Dropped Pkts:                    0

Creation Time:                      Monday September 16 21:44:28 GMT 2013

Last Pkt Time:                      Monday September 16 21:50:20 GMT 2013

Duration:                                                     00h:05m:52s

Active Charging Service name:                                         LTE

Rule Base name:                                                       PGW

URL-Redir First-Request-Only:                                         n/a

Bandwidth Policy:                                                     n/a

FW-and-NAT Policy:                                                    n/a

NAT Policy NAT44:                                            Not-required

NAT Policy NAT64:                                            Not-required

TPO Policy:                                                           n/a

CF Policy ID:                                                         n/a

Old CF Policy ID:                                                     n/a

Dynamic Charging:                                                 Enabled

Dynamic Chrg Msg Received:         3  Rule Definitions Received:        3

Installs Received:                 3  Removes Received:                 0

Installs Succeeded:                3  Installs Failed:                  0

Removes Succeeded:                 0  Removes Failed:                   0

Uplink Dynamic Rule Packets:      32  Uplink Dynamic Rule Bytes:    10778

Downlink Dynamic Rule Packets:    41  Downlink Dynamic Rule Bytes:  10411

Dynamic Charging Packet Drop statistics:

PCC Rule BW Limit Upl Pkts:        0  PCC Rule BW Limit Dnl Pkts:       0

PCC Rule BW Limit Upl Bytes:       0  PCC Rule BW Limit Dnl Bytes:      0

PCC Rule Gating Upl Pkts:          0  PCC Rule Gating Dnl Pkts:         0

PCC Rule Gating Upl Bytes:         0  PCC Rule Gating Dnl Bytes:        0

RuleMatch Fail Upl Pkts:           0  RuleMatch Fail Dnl Pkts:          0

RuleMatch Fail Upl Bytes:          0  RuleMatch Fail Dnl Bytes:         0

Credit-Control:                                                       Off

Event-Triggers:

QoS Renegotiate Up:                0  QoS Renegotiate Dn:               0

TCP Proxy Flows Requests:          0  TCP Proxy Flows Request Success:  0

Disable TCP Proxy Flows Requests:  0  Disable TCP Proxy Flows Success:  0

Current TCP Proxy Flows:           0  Total TCP Proxy Flows:            0

TCP-proxy reset for non-SYN flows:                                      0

Current IP Flows:                  0  Current ICMP Flows:               0

Current IPv6 Flows:                2  Current ICMPv6 Flows:             0

Current TCP Flows:                 1  Current UDP Flows:                1

Current HTTP Flows:                0  Current HTTPS Flows:              0

Current FTP Flows:                 0  Current POP3 Flows:               0

Current SMTP Flows:                0  Current SIP Flows:                1

Current RTSP Flows:                0  Current RTP Flows:                0

Current RTCP Flows:                0  Current IMAP Flows:               0

Current WSP-CO Flows:              0  Current WSP-CL Flows:             0

Current MMS Flows:                 0  Current DNS Flows:                0

Current PPTP-GRE Flows:            0  Current PPTP Flows:               0

Current P2P Flows:                 0  Current H323 Flows:               0

Current TFTP Flows:                0

Current UNKNOWN Flows:             1

Max (L3) Flows:                    6

Max Flows Timestamp:                Monday September 16 21:44:39 GMT 2013

CAE-Readdressing:

GET Requests redirected:                                                0

POST Requests redirected:                                               0

Other Requests redirected:                                              0

HTTP Responses redirected:                                              0

Requests having xheader inserted:                                       0

Total Uplink Bytes:                                                     0

Total Uplink Packets:                                                   0

Total Downlink Bytes:                                                   0

Total Downlink Packets:                                                 0

Total request charging action hit:                                      0

Total response charging action hit:                                     0

Total Charging action hit - Req. Readdr.:                               0

Total Charging action hit - Resp. Readdr.:                              0

CAE Readdressing Err. Conditions:

Total connection failed to video server:                                0

Skipped Req. Readdr. - pipelined req:                                   0

Skipped Req. Readdr. - persistent case:                                 0

Skipped Req. Readdr. - zero copied buf:                                 0

Skipped Req. Readdr. - buf limit exceed:                                0

Req. Readdr. - Socket Mig. failed:                                      0

Skipped Flow. - pipelined req.:                                         0

Skipped Resp. Readdr. - pipelined req:                                  0

Skipped Resp. Readdr. - persistent case:                                0

Skipped Resp. Readdr. - partial resp hdr:                               0

Skipped Resp. Readdr. - zero copied buf:                                0

Skipped Resp. Readdr. - buf limit exceed:                               0

Resp. Readdr. - Socket Mig. failed:                                     0

Total load balancer failed:                                             0

Total MVG xheader insertion failed:                                     0

Rulebase configuration missing:                                         0

Transrating:

Total Transrated Video Connections:                                     0

Total GZIP'd Video Connections:                                         0

Total MP4 Video Connections:                                            0

Total FLV Video Connections:                                            0

Transrated Sorenson H263 Connections:                                   0

Transrated H264 Connections:                                            0

Failed Sorenson H263 Connections:                                       0

Failed H264 Connections:                                                0

Failed Video Codec not supported                                        0

Total Input Video Data Bytes:                                           0

SH263 Input Video Data Bytes:                                           0

H264 Input Video Data Bytes:                                            0

GZIP Input Video Data Bytes:                                            0

Total Output Video Data Bytes:                                          0

SH263 Output Video Data Bytes:                                          0

H264 Output Video Data Bytes:                                           0

GZIP Output Video Data Bytes:                                           0

Average Input Video Bit Rate:                                           0

SH263 Input Video Bit Rate:                                             0

H264 Input Video Bit Rate:                                              0

Average Output Video Bit Rate:                                          0

SH263 Output Video Bit Rate:                                            0

H264 Output Video Bit Rate:                                             0

Average Bit Rate Reduction:                                             0

SH263 Bit Rate Reduction:                                               0

H264 Bit Rate Reduction:                                                0

TCP-Proxy Session Stats:                                               n/a

WiMAX Hotlining Status:                                               n/a

Link Monitoring Average Throughput:                0 kbps

Link Monitoring Average RTT:                       0 ms

Charging Updates:                                                     n/a

Dynamic Charging Rule Definition Statistics:

Dynamic-Rule-Name     Pkts-Down Bytes-Down    Pkts-Up   Bytes-Up       Hits

-------------------- ---------- ---------- ---------- ---------- ----------

IMSDefault                   41      10411         32      10778         73

Total Dynamic Rules:             1

Total Predefined Rules:          0

Total Firewall Predefined Rules: 0

Charging-Updates Statistics:         n/a

Dynamic Charging Rule Definition(s) Configured:

Name                 Prior Content-Id Chrg-Type Rule Parameters

-------------------- ----- ---------- --------- ---------------------------

IMSDefault   950        100   Offline Gate Status:      Allow All

QoS Class Identifier:     5

ARP Priority Level:      10

Reporting Level: Rating Grp

Metering Method:   Duration

Uplink MBR:        75000000

Downlink MBR:      75000000

Filter 1:

Direction:           Uplink

Dst Addr  ::/0

Filter 2:

Direction:         Downlink

Src Addr  ::/0

Predefined Rules Enabled List: n/a

Predefined Firewall Rules Enabled List: n/a

Session-ID:             115:12023218  Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

Callid:                     2207571f  IMSI/MSID:          300420060496012

MSISDN:                                                       19126757869

ACSMgr Instance:                 115  ACSMgr Card/Cpu:                7/1

SessMgr Instance:                                                     115

Client-IP:                                      2001:db8::,10.174.230.156

NAS-IP:                                                           0.0.0.0

Access-NAS-IP(FA):

NAS-PORT:                         0   NSAPI:                            6

Acct-Session-ID:                                                 393A43B7

NAS-ID:                                                               n/a

Access-NAS-ID(FA):                                                    n/a

3GPP2-BSID:                                                           n/a

Access-Correlation-ID(FA):                                            n/a

3GPP2-Correlation-ID:                                                 n/a

MEID:                                                                 n/a

Carrier-ID:                      n/a  ESN:                            n/a

Uplink Bytes:                   2887  Downlink Bytes:                6105

Uplink Packets:                   24  Downlink Packets:                19

Injected Uplink Bytes:             0  Injected Downlink Bytes:          0

Injected Uplink Packets:           0  Injected Downlink Packets:        0

Buffered Uplink Packets:           0  Buffered Downlink Packets:        0

Buffered Uplink Bytes:             0  Buffered Downlink Bytes:          0

Uplink Packets in Buffer:          0  Uplink Bytes in Buffer:           0

Downlink Packets in Buffer:        0  Downlink Bytes in Buffer:         0

Buff Over-limit Uplink Pkts:       0  Buff Over-limit Uplink Bytes:     0

Buff Over-limit Downlink Pkts:     0  Buff Over-limit Downlink Bytes:   0

Processed Uplink Packets:          0  Processed Downlink Packets:       0

Dropped Uplink Packets:            0  Dropped Downlink Packets:         0

Uplink Out of Order Packets:       0  Downlink Out of Order Packets:    0

Dyn FUI Redirected Flows:          0  Dyn FUI Discarded Pkts:           0

ITC Terminated Flows:              0  ITC Redirected Flows:             0

ITC Dropped Packets:               0  ITC ToS Remarked Packets:         0

ITC Dropped Upl Pkts:              0  ITC Dropped Dnl Pkts:             0

ITC Dropped Upl Bytes:             0  ITC Dropped Dnl Bytes:            0

Flow action Terminated Flows:                                           0

PP Flow action Terminated Flows:                                        0

CC Dropped Uplink Packets:         0  CC Dropped Uplink Bytes:          0

CC Dropped Downlink Packets:       0  CC Dropped Downlink Bytes:        0

NRUPC Req Made:                    1  NRUPC Req Success:                1

NRUPC Req Failed:                  0  NRUPC Req Time Out:               0

Dynamic Rule Limiting: Enabled

Bearer Bandwidth Limiting: Enabled

Uplink MBR (bps):                  0  Downlink MBR (bps):               0

Uplink GBR (bps):                  0  Downlink GBR (bps):               0

Uplink Burst (bytes):              0  Downlink Burst (bytes):           0

Dropped Uplink Pkts:               0  Dropped Downlink Pkts:            0

Dropped Uplink Bytes:              0  Dropped Downlink Bytes:           0

Current Readdressed Sessions:                                           0

Total Readdressed Uplink Pkts:                                          0

Total Readdressed Uplink Bytes:                                         0

Total Readdressed Downlink Pkts:                                        0

Total Readdressed Downlink Bytes:                                       0

Total Readdressing Failure Packets:                                     0

Non Syn Flow:                    0  Duplicate Key:                    0

Dropped Pkts:                    0

Creation Time:                      Monday September 16 21:44:33 GMT 2013

Last Pkt Time:                      Monday September 16 21:48:33 GMT 2013

Duration:                                                     00h:05m:47s

Active Charging Service name:                                         LTE

Rule Base name:                                                       OCS

URL-Redir First-Request-Only:                                         n/a

Bandwidth Policy:                                                     n/a

FW-and-NAT Policy:                                              NATPOLICY

NAT Policy NAT44:                                                Required

NAT Policy NAT64:                                            Not-required

TPO Policy:                                                           n/a

CF Policy ID:                                                         n/a

Old CF Policy ID:                                                     n/a

Dynamic Charging:                                                 Enabled

Dynamic Chrg Msg Received:         1  Rule Definitions Received:        1

Installs Received:                 3  Removes Received:                 0

Installs Succeeded:                3  Installs Failed:                  0

Removes Succeeded:                 0  Removes Failed:                   0

Uplink Dynamic Rule Packets:      22  Uplink Dynamic Rule Bytes:     2763

Downlink Dynamic Rule Packets:    17  Downlink Dynamic Rule Bytes:   5879

Dynamic Charging Packet Drop statistics:

PCC Rule BW Limit Upl Pkts:        0  PCC Rule BW Limit Dnl Pkts:       0

PCC Rule BW Limit Upl Bytes:       0  PCC Rule BW Limit Dnl Bytes:      0

PCC Rule Gating Upl Pkts:          0  PCC Rule Gating Dnl Pkts:         0

PCC Rule Gating Upl Bytes:         0  PCC Rule Gating Dnl Bytes:        0

RuleMatch Fail Upl Pkts:           0  RuleMatch Fail Dnl Pkts:          0

RuleMatch Fail Upl Bytes:          0  RuleMatch Fail Dnl Bytes:         0

Credit-Control:                                                        On

CC Peer:                                                     PHLARTRMAS03

CC Group:                                                         DCCA-GY

CC Mode:                                                         DIAMETER

CC Failure Handling:                                    Retry & Terminate

CC Session Failover:                                              Enabled

CCR-I Server Unreachable Handling:                               Continue

CCR-U Server Unreachable Handling:                               Continue

Total CCR-U                                                             0

Current Server Unreachable State:                                     n/a

Interim Volume in Bytes (used / allotted):                 na/   na

Interim Time in Seconds (used / allotted):                 na/   na

Server Retries (attempted / configured):                   na/   na

QoS Renegotiate Up:                0  QoS Renegotiate Dn:               0

TCP Proxy Flows Requests:          0  TCP Proxy Flows Request Success:  0

Disable TCP Proxy Flows Requests:  0  Disable TCP Proxy Flows Success:  0

Current TCP Proxy Flows:           0  Total TCP Proxy Flows:            0

TCP-proxy reset for non-SYN flows:                                      0

Current IP Flows:                  0  Current ICMP Flows:               0

Current IPv6 Flows:                1  Current ICMPv6 Flows:             0

Current TCP Flows:                 1  Current UDP Flows:                0

Current HTTP Flows:                0  Current HTTPS Flows:              0

Current FTP Flows:                 0  Current POP3 Flows:               0

Current SMTP Flows:                0  Current SIP Flows:                0

Current RTSP Flows:                0  Current RTP Flows:                0

Current RTCP Flows:                0  Current IMAP Flows:               0

Current WSP-CO Flows:              0  Current WSP-CL Flows:             0

Current MMS Flows:                 0  Current DNS Flows:                0

Current PPTP-GRE Flows:            0  Current PPTP Flows:               0

Current P2P Flows:                 0  Current H323 Flows:               0

Current TFTP Flows:                0

Current UNKNOWN Flows:             1

Max (L3) Flows:                    6

Max Flows Timestamp:                Monday September 16 21:44:40 GMT 2013

...

Charging Updates:                                                     n/a

Rating-Group:                 3300

Service-Identifier:            0

State:                  Charging

Checkpoint State:        Current

Pending Update:               No

Last Answer:            0h05m47s

Validity-Time:             42853

Volume Threshold:      255852544

Quota         Usage   Total Usage

------------------ ------------- ------------- -------------

CC-Time:                       -           347           347

CC-Total-Octets:       524288000          8992          8992

CC-Input-Octets:               -          2887          2887

CC-Output-Octets:              -          6105          6105

CC-Service-Specific-Units:     -            36            36

Quota-Consumption-Time:        -             -

Quota-Hold-Time:               -             -

Quota-Validity-Time:       43200           347

Ruledef Name          Pkts-Down Bytes-Down    Pkts-Up   Bytes-Up       Hits

-------------------- ---------- ---------- ---------- ---------- ----------

HandleDNS3300                 2        226          2        124          4

Firewall-Ruledef Name Pkts-Down Bytes-Down    Pkts-Up   Bytes-Up       Hits

-------------------- ---------- ---------- ---------- ---------- ----------

int_apn_src                   2        226          2        124          4

Dynamic Charging Rule Definition Statistics:

Dynamic-Rule-Name     Pkts-Down Bytes-Down    Pkts-Up   Bytes-Up       Hits

-------------------- ---------- ---------- ---------- ---------- ----------

RTRRule3300                  17       5879         22       2763         36

Total Dynamic Rules:             1

Total Predefined Rules:          2

Total Firewall Predefined Rules: 0

Charging-Updates Statistics:         n/a

Dynamic Charging Rule Definition(s) Configured:

Name                 Prior Content-Id Chrg-Type Rule Parameters

-------------------- ----- ---------- --------- ---------------------------

RTRRule3300   950       3300      Both Gate Status:      Allow All

QoS Class Identifier:     9

ARP Priority Level:      10

Reporting Level: Rating Grp

Metering Method: Durn + Vol

Uplink MBR:        75000000

Downlink MBR:      75000000

Filter 1:

Direction:           Uplink

Dst Addr  0.0.0.0/0

Filter 2:

Direction:         Downlink

Src Addr  0.0.0.0/0

Filter 3:

Direction:           Uplink

Dst Addr  ::/0

Filter 4:

Direction:         Downlink

Src Addr  ::/0

Predefined Rules Enabled List:

HandleTCP3300

HandleDNS3300

Predefined Firewall Rules Enabled List: n/a

Session-ID:             115:12023409  Username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

Callid:                     22075719  IMSI/MSID:          300420060496012

MSISDN:                                                       19126757869

ACSMgr Instance:                 115  ACSMgr Card/Cpu:                7/1

SessMgr Instance:                                                     115

Client-IP:                                                     2001:db8::

NAS-IP:                                                           0.0.0.0

Access-NAS-IP(FA):

NAS-PORT:                         0   NSAPI:                            7

Acct-Session-ID:                                                 393A43B1

NAS-ID:                                                               n/a

Access-NAS-ID(FA):                                                    n/a

3GPP2-BSID:                                                           n/a

Access-Correlation-ID(FA):                                            n/a

3GPP2-Correlation-ID:                                                 n/a

MEID:                                                                 n/a

Carrier-ID:                      n/a  ESN:                            n/a

Uplink Bytes:                  94041  Downlink Bytes:               83406

Uplink Packets:                 1033  Downlink Packets:               922

...

Dynamic Rule Limiting: Enabled

Bearer Bandwidth Limiting: Enabled

Uplink MBR (bps):              38000  Downlink MBR (bps):           38000

Uplink GBR (bps):              38000  Downlink GBR (bps):           38000

Uplink Burst (bytes):           9500  Downlink Burst (bytes):        9500

Dropped Uplink Pkts:               0  Dropped Downlink Pkts:            0

Dropped Uplink Bytes:              0  Dropped Downlink Bytes:           0

Current Readdressed Sessions:                                           0

Total Readdressed Uplink Pkts:                                          0

Total Readdressed Uplink Bytes:                                         0

Total Readdressed Downlink Pkts:                                        0

Total Readdressed Downlink Bytes:                                       0

Total Readdressing Failure Packets:                                     0

Non Syn Flow:                    0  Duplicate Key:                    0

Dropped Pkts:                    0

Creation Time:                      Monday September 16 21:44:28 GMT 2013

Last Pkt Time:                      Monday September 16 21:50:20 GMT 2013

Duration:                                                     00h:05m:52s

Active Charging Service name:                                         LTE

Rule Base name:                                                       PGW

URL-Redir First-Request-Only:                                         n/a

Bandwidth Policy:                                                     n/a

FW-and-NAT Policy:                                                    n/a

NAT Policy NAT44:                                            Not-required

NAT Policy NAT64:                                            Not-required

TPO Policy:                                                           n/a

CF Policy ID:                                                         n/a

Old CF Policy ID:                                                     n/a

Dynamic Charging:                                                 Enabled

Dynamic Chrg Msg Received:         0  Rule Definitions Received:        0

Installs Received:                 0  Removes Received:                 0

Installs Succeeded:                0  Installs Failed:                  0

Removes Succeeded:                 0  Removes Failed:                   0

Uplink Dynamic Rule Packets:    1033  Uplink Dynamic Rule Bytes:    94041

Downlink Dynamic Rule Packets:   922  Downlink Dynamic Rule Bytes:  83406

Dynamic Charging Packet Drop statistics:

PCC Rule BW Limit Upl Pkts:        0  PCC Rule BW Limit Dnl Pkts:       0

PCC Rule BW Limit Upl Bytes:       0  PCC Rule BW Limit Dnl Bytes:      0

PCC Rule Gating Upl Pkts:          0  PCC Rule Gating Dnl Pkts:         0

PCC Rule Gating Upl Bytes:         0  PCC Rule Gating Dnl Bytes:        0

RuleMatch Fail Upl Pkts:           0  RuleMatch Fail Dnl Pkts:          0

RuleMatch Fail Upl Bytes:          0  RuleMatch Fail Dnl Bytes:         0

Credit-Control:                                                       Off

Event-Triggers:

QoS Renegotiate Up:                0  QoS Renegotiate Dn:               0

TCP Proxy Flows Requests:          0  TCP Proxy Flows Request Success:  0

Disable TCP Proxy Flows Requests:  0  Disable TCP Proxy Flows Success:  0

Current TCP Proxy Flows:           0  Total TCP Proxy Flows:            0

TCP-proxy reset for non-SYN flows:                                      0

Current IP Flows:                  0  Current ICMP Flows:               0

Current IPv6 Flows:                1  Current ICMPv6 Flows:             0

Current TCP Flows:                 0  Current UDP Flows:                1

Current HTTP Flows:                0  Current HTTPS Flows:              0

Current FTP Flows:                 0  Current POP3 Flows:               0

Current SMTP Flows:                0  Current SIP Flows:                0

Current RTSP Flows:                0  Current RTP Flows:                0

Current RTCP Flows:                0  Current IMAP Flows:               0

Current WSP-CO Flows:              0  Current WSP-CL Flows:             0

Current MMS Flows:                 0  Current DNS Flows:                0

Current PPTP-GRE Flows:            0  Current PPTP Flows:               0

Current P2P Flows:                 0  Current H323 Flows:               0

Current TFTP Flows:                0

Current UNKNOWN Flows:             1

Max (L3) Flows:                    0

Max Flows Timestamp:                                                  n/a

...

Charging Updates:                                                     n/a

No Charging ruledef(s) match the specified criteria

No Firewall ruledef(s) match the specified criteria

Dynamic Charging Rule Definition Statistics:

Dynamic-Rule-Name     Pkts-Down Bytes-Down    Pkts-Up   Bytes-Up       Hits

-------------------- ---------- ---------- ---------- ---------- ----------

0_0                         922      83406       1033      94041       1955

Total Dynamic Rules:             2

Total Predefined Rules:          0

Total Firewall Predefined Rules: 0

Charging-Updates Statistics:         n/a

Dynamic Charging Rule Definition(s) Configured:

Name                 Prior Content-Id Chrg-Type Rule Parameters

-------------------- ----- ---------- --------- ---------------------------

0_0   400        102   Offline Gate Status:      Allow All

QoS Class Identifier:     1

ARP Priority Level:      11

Reporting Level: Rating Grp

Metering Method:   Duration

Uplink MBR:           38000

Downlink MBR:         38000

Uplink GBR:           38000

Downlink GBR:         38000

Filter 1:

Direction:           Uplink

Protocol:               UDP

Src Addr  2001:db8::12/128

Dst Addr  2001:db8::13/128

Dst Port  59536

Filter 2:

Direction:         Downlink

Protocol:               UDP

Src Addr  2001:db8::13/128

Dst Addr  2001:db8::12/128

Dst Port  53626

0_1   401        102   Offline Gate Status:      Allow All

QoS Class Identifier:     1

ARP Priority Level:      11

Reporting Level: Rating Grp

Metering Method:   Duration

Uplink MBR:               0

Downlink MBR:             0

Uplink GBR:               0

Downlink GBR:             0

Filter 1:

Direction:           Uplink

Protocol:               UDP

Src Addr  2001:db8::12/128

Dst Addr  2001:db8::13/128

Dst Port  59537

Filter 2:

Direction:         Downlink

Protocol:               UDP

Src Addr  2001:db8::13/128

Dst Addr  2001:db8::12/128

Dst Port  53627

Predefined Rules Enabled List: n/a

Predefined Firewall Rules Enabled List: n/a

Total acs sessions matching specified criteria: 3

show active-charging firewall statistics

This is the little sister of "show active-charging sessions full" and could provide more information on the reason for packet drops.

[XGWout]PGW> show active-charging firewall statistics callid 0000513a

Thursday June 18 17:01:20 UTC 2015

Firewall Statistics for Callid 0000513a in Context: XGWout.

Data Stats:

Total Packets Received:                                                     8745

Total Bytes Received:                                                    5296353

Total Packets Sent:                                                         8704

Total Bytes Sent:                                                        5291193

Total Packets (NAT64 Translation):                                             0

Total Bytes Reduced (NAT64 Translation):                                       0

Total Packets Injected:                                                        0

Total Bytes Injected:                                                          0

Uplink Packets Dropped:                                                       37

Uplink Bytes Dropped:                                                       5000

Downlink Packets Dropped:                                                      4

Downlink Bytes Dropped:                                                      160

Total Malformed Packets:                                                       0

Total DOS Attacks:                                                             0

Total Flows Processed by Firewall:                                             0

Total NAT Flows Processed by Firewall:                                       171

Total NAT44 Flows Processed by Firewall:                                     171

Total NAT64 Flows Processed by Firewall:                                       0

Total Bypass-NAT Flows Processed by Firewall:                                  0

Total Bypass-NAT44 Flows Processed by Firewall:                                0

Total Bypass-NAT64 Flows Processed by Firewall:                                0

Current Flows Processed by Firewall:                                           0

Current NAT Flows Processed by Firewall:                                       1

Current NAT44 Flows Processed by Firewall:                                     1

Current NAT64 Flows Processed by Firewall:                                     0

Current Bypass-NAT Flows Processed by Firewall:                                0

Current Bypass-NAT44 Flows Processed by Firewall:                              0

Current Bypass-NAT64 Flows Processed by Firewall:                              0

show subscribers data-rate [high/low]

Captures data rates / throughput for a subscriber or group of subscribers

- This is most useful when applying to a group of subscribers that are suspected to have data issues in either/both directions compared to normal or other groups - i.e. subscribers in a particular IP pool that is having issues

The following output is for the same VoLTE subscriber taken at the same time as the previous commands.

[local]PGW> show sub data-rate high callid 22075719

Monday September 16 21:51:07 UTC 2013

Total Subscribers       : 1

Active                  : 1             Dormant                 : 0

peak rate from user(bps): 27699         peak rate to user(bps)  : 24879

ave rate from user(bps) : 16663         ave rate to user(bps)   : 16433

sust rate from user(bps): 16692         sust rate to user(bps)  : 16459

peak rate from user(pps): 37            peak rate to user(pps)  : 34

ave rate from user(pps) : 22            ave rate to user(pps)   : 22

sust rate from user(pps): 22            sust rate to user(pps)  : 22

show subscribers debug-info

This command has mostly information that could be helpful for TAC or Engineering in their efforts to support the customer, though there is information here that the curious customer might find interesting.

The same VoLTE example is used here:

[local]PGW> show sub debug-info msid 300420060496012

Monday September 16 21:50:51 UTC 2013

username: 0300420060496012@nai.epc.mnc420.mcc300.3gppnetwork.org

callid: 22075719    msid: 300420060496012

Card/Cpu: 7/1

Sessmgr Instance: 115

Primary callline:

Redundancy Status: Original Session

Checkpoints   Attempts    Success    Last-Attempt   Last-Success

Full:             8          6         63300ms        63300ms

Micro:          661        661             0ms            0ms

GR Checkpoints Sent

2 Full Checkpoints,  last 63 seconds before

56 Micro Checkpoints, last 3 seconds before

Invalidate-CRRs: 0         Call Statistics: 1

Current number of NAT flows checkpointed: 0

Current state: SMGR_STATE_CONNECTED

FSM Event trace:

State                            Event                Num Occurances  Time

SMGR_STATE_OPEN               SMGR_EVT_NEWCALL                (1)  2013-09-16:21:44:28

SMGR_STATE_NEWCALL_ARRIVED    SMGR_EVT_IPV6ADDR_ALLOC_SUCCESS (1)  2013-09-16:21:44:29

SMGR_STATE_NEWCALL_ARRIVED    SMGR_EVT_ANSWER_CALL            (1)  2013-09-16:21:44:29

SMGR_STATE_NEWCALL_ANSWERED   SMGR_EVT_LINE_CONNECTED         (1)  2013-09-16:21:44:29

SMGR_STATE_LINE_CONNECTED     SMGR_EVT_LOWER_LAYER_UP         (1)  2013-09-16:21:44:29

CLP State Trace:

State                                              EBI's Associated                  Time

CLI_MAPPED_SGX_EVT_POLICY_STATUS_IND             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SGX_EVT_POLICY_CHANGE_REQ             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SEF_EVT_POLICY_CHANGE_REQ             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SEF_EVT_POLICY_CHANGE_RSP             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SGX_EVT_POLICY_CHANGE_REQ             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SGX_EVT_POLICY_STATUS_IND             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SEF_EVT_SESS_SETUP_RSP                -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:44:29

CLI_MAPPED_SGX_EVT_POLICY_STATUS_IND             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:44:29

SMGR_CLP_EVT_PGW_UPDATE_BEARER_REQ               -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:44:29

CLI_MAPPED_SEF_EVT_BEARER_BINDING_RSP            -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:44:29

SMGR_CLP_EVT_PGW_CREATE_SESSION_RSP              5  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:44:29

CLI_MAPPED_SGX_EVT_POLICY_CHANGE_REQ             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:52

CLI_MAPPED_SEF_EVT_POLICY_CHANGE_REQ             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:52

CLI_MAPPED_SEF_EVT_POLICY_CHANGE_RSP             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:52

CLI_MAPPED_SGX_EVT_POLICY_CHANGE_REQ             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:52

CLI_MAPPED_SGX_EVT_POLICY_STATUS_IND             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:52

SMGR_CLP_EVT_PGW_CREATE_BEARER_REQ               -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:52

CLI_MAPPED_SEF_EVT_BEARER_BINDING_RSP            -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

SMGR_CLP_EVT_PGW_CREATE_BEARER_RSP               -  -  7  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

CLI_MAPPED_SEF_EVT_POLICY_STATUS_IND             -  -  -  -  -  -  -  -  -  -  -    2013-09-16:21:49:53

Sub Session State Trace:

EBI ID                               State                        TimeStamp

5   SMGR_STATE_NEWCALL_ARRIVED        2013-09-16:21:44:28

5   SMGR_STATE_CONNECTED              2013-09-16:21:44:29

7   SMGR_STATE_CONNECTED              2013-09-16:21:49:53

NAT Policy NAT44: Not-required

NAT Policy NAT64: Not-required

Data Reorder statistics

Total timer expiry:       0         Total flush (tmr expiry):  0

Total no buffers:         0         Total flush (no buffers):  0

Total flush (queue full): 0         Total flush (out of range):0

Total flush (svc change): 0         Total out-of-seq pkt drop: 0

Total out-of-seq arrived: 0

IPv4 Reassembly Statistics:

Success:                  0         In Progress:               0

Failure (timeout):        0         Failure (no buffers):      0

Failure (other reasons):  0

Re-addressed Session Entries:

Allowed:                  2000      Current:                   0

Added:                    0         Deleted:                   0

Revoked for use by different subscriber: 0

TCP Proxy DNS Info entries 0

IPv4 ACL applied:

active input acl:                   number of rules: 0

active output acl:                  number of rules: 0

ACL caching statistics:

input packets:            2206      input cache hits:          0

output packets:           2183      output cache hits:         0

IPv6 ACL applied:

active input ipv6 acl:  ECS_ACL_V6       number of rules: 8

active output ipv6 acl: ECS_ACL_V6       number of rules: 8

IPv6 ACL caching statistics:

input cache hits:         1787      output cache hits:         739

Total number of ACL reload:        0

Total number of ACS session deleted on ACL reload:        0

NEMO Mode: N/A ; Peer bond: NO ; Peer Callid: 00000000

sessmgr NPU Flow Details:

Flow Id    Flow Type                 Nat Realm                  VPN Id

8079786    IPV6_FLOW                 n/a                        5

Private IP NPU flow timeout (Seconds) : n/a

ACS PCP Service: n/a

show subscribers aaa-configuration

This is a huge list of all AAA and configuration (even non-AAA related) related information for a subscriber, regardless of whether AAA is even used or was ever accessed or not. It is useful to see what the chassis assigned to the subscriber without having to necessarily analyze AAA authentication packets exchanges, subscriber profiles or make assumptions about the default chassis settings.

show subscribers activity

This graphs activity level of a subscriber

show active-charging flows ip-address

This is a list of all flows by flow id for all sessions connected to the given egress ip address, along with the number of bytes sent in both directions. Monitor subscriber must be used first to see what addresses that a subscriber is trying to access and then confirm whether any packets are received from that address.

- Detailed information about the flow id of interest can be retrieved with show active-charging flows full flow-id, identifying the proper flow by the MS IP field (IP address of the subscriber which is known at this point from mon sub output).

show subscribers policy

This lists the subscriber's current policies assigned

show [mipfa | mipha] full

This lists detailed MIP-related information about a subscriber

[local]PDSN-FA> show mipfa full username 9786045176@cisco.com

Tuesday May 12 16:08:05 UTC 2015

Username: 9786045176@cisco.com          Callid: 1120ff97

MSID:  311289786045176

Num Agent Advt Sent: 1     Num Agent Solicit Rcvd: 0

Home Address #1: 10.235.121.62       NAI: 9786045176@cisco.com

FA Address: 203.0.113.1            HA Address: 203.0.113.2

Lifetime: 02h00m00s                Remaining Lifetime: 01h56m04s

Reverse Tunneling: On              Encapsulation Type: IP-IP

GRE Key: n/a                       IPSec Required: No

IPSec Ctrl Tunnel Estab.: No       IPSec Data Tunnel Estab.: No

MN-AAA Removal: No                 Proxy MIP: Disabled

DMU Auth Failures: 0               Send Terminal Verification: Disabled

Revocation Negotiated: YES         Revocation I Bit Negotiated: YES

MN-HA-Key-Present: FALSE           MN-HA-SPI: n/a

FA-HA-Key-Present: TRUE            FA-HA-SPI: 8832

MN-FA-Key-Present: FALSE           MN-FA-SPI: n/a

HA-RK-KEY-Present: FALSE           HA-RK-SPI: n/a

HA-RK-Lifetime:    n/a             HA-RK-Remaining-Lifetime: n/a

Send Host Config: Disabled

show [mipfa |mipha] counters

This reports on various MIP related counters for a subscriber:

[local]PFDN> show mipfa counters username 9786045176@cisco.com

Tuesday May 12 16:08:12 UTC 2015

MSID: 311289786045176

Username: 9786045176@cisco.com

Callid: 1120ff97

Num Agent Advt Sent: 1   Num Agent Solicit Rcvd: 0

Home Address: 10.235.121.62          NAI: 9786045176@cisco.com

FA Address: 203.0.113.1              HA Address: 203.0.113.2

Registration Request Received:

Total Received Reg:         1            Accepted Reg:           1

Rejected Reg:               0

Denied Reg:               0              Discarded Reg:        0

Relayed Reg:                1            Auth Failed Reg:        0

FA Denied Reg:              0            HA Denied Reg:          0

Rcvd with MIP Key Data&colon;     0

Init RRQ Received:          1            Init RRQ Accepted:      1

Init RRQ Rejected:          0

Init RRQ Denied:          0              Init RRQ Discarded:   0

Init RRQ Relayed:           1            Init RRQ Auth Failed:   0

Init PMIP RRQ Xmit:         0            Init PMIP RRQ Re-Xmit:  0

Init RRQ Denied by FA:      0            Init RRQ Denied by HA:  0

Renew RRQ Received:         0            Renew RRQ Accepted:     0

Renew RRQ Rejected:         0

Renew RRQ Denied:         0              Renew RRQ Discarded:  0

Renew RRQ Relayed:          0            Renew RRQ Auth Failed:  0

Renew PMIP RRQ Xmit:        0            Renew PMIP RRQ Re-Xmit: 0

Renew RRQ Denied by FA:     0            Renew RRQ Denied by HA: 0

Dereg RRQ Received:         0            Dereg RRQ Accepted:     0

Dereg RRQ Rejected:         0

Dereg RRQ Denied:         0              Dereg RRQ Discarded:  0

Dereg RRQ Relayed:          0            Dereg RRQ Auth Failed:  0

Dereg PMIP RRQ Xmit:        0            Dereg PMIP RRQ Re-Xmit: 0

Dereg RRQ Denied by FA:     0            Dereg RRQ Denied by HA: 0

Denied by FA:

Unspecified error:          0            Reg Timeout:            0

Admin Prohibited:           0            No Resources:           0

MN Auth Failure:            0            HA Auth Failure:        0

Lifetime too long:          0            Poorly formed Request:  0

Poorly formed Reply:        0            MN Too Distant:         0

Invalid COA:                0            Missing NAI:            0

Missing Home Agent:         0            Missing Home Addr:      0

Unknown Challenge:          0            Missing Challenge:      0

Stale Challenge:            0

Encap Unavailable:          0            Rev Tunnel Unavailable: 0

Rev Tunnel Mandatory:       0            HA Network Unreachable: 0

Delivery Style Unavailable: 0            HA Host Unreachable:    0

HA Port Unreachable:        0            HA Unreachable:         0

Unknown CVSE Rcvd:          0            MIP Key Request:        0

AAA Authenticator:          0            Public Key Invalid:     0

Discarded by FA:

Invalid Extn:               0            Invalid UDP Checksum:   0

Denied by HA:

FA Auth Failure:            0            Poorly formed Request:  0

Mismatched ID:              0            Simul Bindings Exceeded:0

Unknown HA:                 0            Rev Tunnel Unavailable: 0

MN Auth Failure:            0            No Resources:           0

Admin Prohibited:           0            Rev Tunnel Mandatory:   0

Encap Unavailable:          0            Unspecified Reason:     0

Unknown CVSE Rcvd:          0

Registration Reply Rcvd:

Total:                      1            Relayed:                1

Errors:                     0

Init RRP Rcvd:              1            Init RRP Relayed:       1

Renew RRP Rcvd:             0            Renew RRP Relayed:      0

Dereg RRP Rcvd:             0            Dereg RRP Relayed:      0

RRP with Dyn HA Rcvd:       0            RRP with Dyn HA Denied: 0

Registration Reply Sent:

Total:                      1            Accepted Reg:           1

Accepted DeReg:             0            Denied:                 0

Send Error:                 0

Tunnel Data Received:

Total Packets :             3383

IPIP:                     3383         GRE:                    0

Total Bytes :               3850296

IPIP:                     3850296      GRE:                    0

Errors:

Protocol Type Error:      0            GRE Key Absent:         0

GRE Checksum Error :      0            Invalid Pkt Length:     0

No Session Found   :      0

Tunnel Data Sent:

Total Packets :             2905

IPIP:                     2905         GRE:                    0

Total Bytes :               346228

IPIP:                     346228       GRE:                    0

show ppp [full]

This reports detailed PPP related information about a subscriber.

- The full version is not a superset of the normal version.

[local]PDSN-HSGW> show ppp username 9786045176@cisco.com

Tuesday May 12 16:08:18 UTC 2015

PPP Summary:

1 PPP Sessions In Progress

Layer Info:

1 LCP Up             1 IPCP Up            0 IPv6CP Up     0  CCP Up

Compression:

0 VJ Compressed Sessions (loc to rem)

0 VJ Compressed Sessions (rem to loc)

0 ROHC Compressed Sessions (loc to rem)

0 ROHC Compressed Sessions (rem to loc)

0 Normal PPP Compressed Sessions

0 Stateless PPP Compressed Sessions

1 NONE        0 STAC        0 MPPC        0 DEFLATE (loc to rem)

1 NONE        0 STAC        0 MPPC        0 DEFLATE (rem to loc)

Errors:

0 In errors              0 In discards             0 In unknown proto

0 Out errors             0 Out discards            0 Pkt too long

0 Bad address            0 Bad control             0 Bad FCS

0 Bad Length

0 Echo req rcvd          0 Echo rsp rcvd           0 Echo Req sent

0 Echo rsp sent          0 Invalid magic-number rcvd

0 LCP Vend Ext req sent          0 LCP Vend Ext req resent

0 LCP Vend Ext rsp rcvd          0 LCP Vend Ext protocol rejected

0 LCP Vend Ext req max-retried

0 Decomp errors          0 Comp Reset sent

0 Comp errors            0 Comp expansion          0 Comp Reset rcvd

Data Stats:

294366 In octs(unframed)              2059 In pkts

307 In ctrl octs                      8 In ctrl pkts

0 In comp octs                      0 In comp pkts

0 In uncomp octs

307522 In framed octs

3798297 Out octs(unframed)             3400 Out pkts

139 Out ctrl octs                     6 Out ctrl pkts

0 Out comp octs                     0 Out comp pkts

0 Out uncomp octs

3840820 Out framed octs

[local]PDSN-HSGW> show ppp full username 9786045176@cisco.com

Tuesday May 12 16:08:23 UTC 2015

Username: 9786045176@cisco.com  Callid:1120ff97 Msid: 311289786045176

LCP State: Opened

mtu (Negotiated/Enforced): 1500/1500   mru: 1500

auth algorithm (loc to rem):     none  (rem to loc):     none

PFC  (loc to rem): enabled [ignore]  (rem to loc):  enabled

ACFC (loc to rem): enabled [ignore]  (rem to loc):  enabled

async map (loc to rem): 0x00000000     (rem to loc): 0x00000000

IPCP State: Opened

IP Header comp. (loc to rem): none

(rem to loc): none

Local Address:   203.0.113.1            Remote Address:         0.0.0.0

Primary DNS:  209.165.200.225           Secondary DNS:  209.165.200.226

Primary NBNS:         0.0.0.0           Secondary NBNS:         0.0.0.0

IPV6CP State: Not Opened

CCP State: Not Opened

294701 In octs(unframed)                  2063 In pkts

3798574 Out octs(unframed)                 3404 Out pkts

307 In ctrl octs                          8 In ctrl pkts

139 Out ctrl octs                         6 Out ctrl pkts

307883 In framed octs                  3841113 Out framed octs

291333 In data (unfr/data-cmp) octs    3784675 Out data (unfr/data-cmp) octs

291471 In data (iphdr-cmp) octs        3784843 Out data (iphdr-cmp) octs

0 In data (iphdr-cmp-fail) octs         0 In data (iphdr-cmp-fail) pkts

0 In data (iphdr-rohc) octs             0 Out data (iphdr-rohc) octs

0 In data (iphdr-rohc-fail) octs        0 In data(iphdr-rohc-fail) pkts

0 In discards                           0 In errors

0 Out discards                          0 Out errors

0 Bad address                           0 Bad control

0 Pkt too long                          0 Bad FCS

0 Bad pkt length

0 Echo req rcvd                         0 Echo rsp rcvd

0 Echo req sent                         0 Echo rsp sent

0 LCP Vend Ext req sent                 0 LCP Vend Ext req resent

0 LCP Vend Ext rsp rcvd                 0 LCP Vend Ext protocol rejected

0 LCP Vend Ext req max-retried

0 Invalid magic-number rcvd

Total PPP sessions matching specified criteria: 1

show ppp counters

[local]PDSN-HSGW> show ppp counters username 9786045176@cisco.com

Tuesday May 12 16:08:52 UTC 2015

Username: 9786045176@cisco.com  Callid:1120ff97 Msid: 311289786045176

296894 In octs(unframed)                  2083 In pkts

3800156 Out octs(unframed)                 3412 Out pkts

307 In ctrl octs                          8 In ctrl pkts

139 Out ctrl octs                         6 Out ctrl pkts

310124 In framed octs                  3842736 Out framed octs

293517 In data (unfr/data-cmp) octs    3786225 Out data (unfr/data-cmp) octs

293655 In data (iphdr-cmp) octs        3786393 Out data (iphdr-cmp) octs

0 In data (iphdr-cmp-fail) octs         0 In data (iphdr-cmp-fail) pkts

0 In data (iphdr-rohc) octs             0 Out data (iphdr-rohc) octs

0 In data (iphdr-rohc-fail) octs        0 In data(iphdr-rohc-fail) pkts

0 In discards                           0 In errors

0 Out discards                          0 Out errors

0 Bad address                           0 Bad control

0 Pkt too long                          0 Bad FCS

0 Bad pkt length

0 Echo req rcvd                         0 Echo rsp rcvd

0 Echo req sent                         0 Echo rsp sent

0 LCP Vend Ext req sent                 0 LCP Vend Ext req resent

0 LCP Vend Ext rsp rcvd                 0 LCP Vend Ext protocol rejected

0 LCP Vend Ext req max-retried

0 Invalid magic-number rcvd

Total PPP sessions matching specified criteria: 1

show rp full

This reports detailed A11 (RP interface) related information about a subscriber

- "show rp counters" is a subset of this command

[local]PDSN-HSGW> show rp full username 9786045176@cisco.com

Tuesday May 12 16:07:52 UTC 2015

Username: 9786045176@cisco.com  Callid: 1120ff97 Msid: 311289786045176

A10 Connection #1:(Main)

PCF Address: 10.207.6.67                PDSN Address: 10.211.28.132

MN Sess Ref ID: 1                       GRE Key: 1864769

Service Option: 59

Flow Control State : XON

Lifetime: 00h30m00s                     Remaining Lifetime: 00h28m59s

GRE Receive:

Total Packets Rcvd: 2017                Total Bytes Rcvd: 367426

GRE Send:

Total Packets Sent: 4722                Total Bytes Sent: 3988706

Data Over Signaling Packets: 0          Data Over Signaling Bytes: 0

IP Header compression:

Forward: ROHC not negotiated

Reverse: ROHC not negotiated

GRE Flow Control:

Total Packets Received with XOFF:       0

Total Packets Received with XON:        0

Total XON->XOFF Transitions:            0

Total Output Packets Dropped on XOFF:   0

Total Output Bytes Dropped on XOFF:     0

SPI: 257

Prev System Id: 0                       Current System Id: 0

Prev Network Id: 0                      Current Network Id: 0

Prev Packet Zone Id: 0                  Current Packet Zone Id: 0

BSID: 001C00030015                      GRE Segmentation : Disabled

Registration Request/Reply:

Renew RRQ Accepted: 0                   Discarded: 0

Intra PDSN Active H/O RRQ Accept: 0   Intra PDSN Dormant H/O RRQ Accept: 0

Inter PDSN Handoff RRQ Accepted: 1

Reply Send Error: 0

Registration Update/Ack:

Initial Update Transmitted: 0           Update Retransmitted: 0

Denied: 0                               Not Acknowledged: 0

Reg Ack Received: 0                     Reg Ack Discarded: 0

Update Send Error: 0

Registration Update Send Reason:

Lifetime Expiry:  0                     Upper Layer Initiated: 0

Other Reasons: 0                        Handoff Release: 0

Session Manager Exited: 0

Registration Update Denied:

Reason Unspecified: 0                   Admin Prohibited: 0

PDSN Failed Authentication: 0           Identification Mismatch: 0

Poorly Formed Update: 0

Session Update/Ack:

Initial Update Transmitted: 1           Update Retransmitted: 0

Denied: 0                               Not Acknowledged: 0

Sess Update Ack Received: 1             Sess Update Ack Discarded: 0

Update Send Error: 0

Session Update Send Reason:

Always On:        0                     QoS Info:           1

TFT violation:    0                     Traffic Violation:  0

Traffic Policing: 0                     Operator Triggered: 0

Session Update Denied:

Reason Unspecified: 0                   Insufficient Resources: 0

Admin Prohibited: 0                     Parameter not updated: 0

PDSN Failed Authentication: 0

Identification Mismatch: 0

Poorly Formed Update: 0

Profile Id Not Supported: 0             Handoff In Progress :    0

GRE Receive:

Total Packets Received:   2017          Protocol Type Error:     0

Total Bytes Received:     367426        GRE Key Absent:          0

GRE Checksum Error:      0

Invalid Packet Length:   0

GRE Send:

Total Packets Sent:       4722

Total Bytes Sent:         3988706

Total Packets Sent in SDB:0

Total Bytes Sent in SDB:  0

GRE Segmentation:

Total Packets Received with Segmentation Indication:     0

Total Packets Sent with Segmentation Indication:         0

Total Successful Reassembly:                             0

Total packets processed without proper reassembly:       0

GRE Flow Control:

Total Packets Received with XOFF:       0

Total Packets Received with XON:        0

Total XON->XOFF Transitions:            0

Total Output Packets Dropped on XOFF:   0

Total Output Bytes Dropped on XOFF:     0

Total RP sessions matching specified criteria: 1

show l2tp sessions full

This reports detailed l2tp related information about a subscriber

- note the Rx and Tx data Pkts counts for the LAC side of the call (0s) do not appear correct when compared to the LNS side of the call

[local]PDSN-LAC> show l2tp sessions full user 0020000648@cisco.com

Wednesday June 17 23:34:13 UTC 2015

Username: 0020000648@cisco.com    Callid: 161df87f     Msid: 311280020000648

Peer IP Address: 203.0.113.11       Service Name:   LAC-Service1

Context Name:    destination        Service Type:   LAC

Session State: LAC_ESTABLISHED

Local Tunnel ID:  7             Local Session ID:  2471

Peer Tunnel ID:   88            Peer Session ID:   2471

Call Type:        LAC-INCOMING  Call Serial Num:   371062911

Rx Connect Speed: 57600         Tx Connect Speed:  64000

PPP Proxy-Auth:   CHAP_MD5      Tunnel Key:        n/a

Bearer Type:      DIGITAL       Framing Type:      ASYNC

System ID:        0             Network ID:        0

Cell Number:      0             Service Option:    0

Data Rx Sequence Num Enabled:  DISABLED

Data Tx Sequence Num Enabled:  DISABLED

Data Rx Sequence Num:          0

Data Tx Sequence Num:          0

Rx Data Pkts:          0           Tx Data Pkts:  0

Rx Data Octs:          0           Tx Data Octs:  0

Rx Discard Data Pkts:  0

Handoffs:              0

[local]HA-LNS> show l2tp sessions full username 0020009112@cisco.com

Wednesday June 17 23:33:01 UTC 2015

Username: 0020000648@cisco.com    Callid: 0a30f2ac     Msid: 311280020000648

Peer IP Address: 203.0.113.10       Service Name:   SIP-LNS

Context Name:    LNSINGRESS         Service Type:   LNS

Session State: LNS_ESTABLISHED

Local Tunnel ID:  88            Local Session ID:  2471

Peer Tunnel ID:   7             Peer Session ID:   2471

Call Type:        LNS-INCOMING  Call Serial Num:   371062911

Rx Connect Speed: 57600         Tx Connect Speed:  64000

PPP Proxy-Auth:   CHAP_MD5      Tunnel Key:        n/a

Bearer Type:      DIGITAL       Framing Type:      ASYNC

Data Rx Sequence Num Enabled:  ENABLED

Data Tx Sequence Num Enabled:  DISABLED

Data Rx Sequence Num:          15

Data Tx Sequence Num:          6

Rx Data Pkts:          15          Tx Data Pkts:  6

Rx Data Octs:          953         Tx Data Octs:  424

Rx Discard Data Pkts:  0

show rsvp counters

This lists detailed rsvp counters for a subscriber

show ims-authorization sessions full

This lists detailed information about the PCRF session

This example shows PCRF information for two APNs, APN1 and APN2

- Note the SGSN IP-Address is actually the SGW address

[local]PGW> show ims-authorization sessions full imsi 300420160377232

Wednesday June 17 23:47:00 UTC 2015

CallId: 4d9f33cb            Service Name: IMS-GX

IMSI:  300420160377232

Session ID: 0007-diamproxy.PHLA.Gx.ims.com;1302279115;926061183;55810c5d-17f02

Bearer Type: GTP

SGSN IP-Addr: 203.0.113.3

APN: APN1

Bearer Control Mode: UE/NW

State: Connected

Negotiated Supported Features:

3gpp-r10

Bound PCRF Server: ohcis04mra01.cisco.com

Primary PCRF Server: ohcis04mra01.cisco.com

Secondary PCRF Server: njbbs04mra01.cisco.com

Primary P-CSCF: NA

Secondary P-CSCF: NA

Outstanding CCR-U: 0

UE IP Address:

UE IP Session Type: IPv6

IPv4 Address: NA

IPv6 Prefix: 5555:1000:8010:a9a4::

Auth Decision:

Event Triggers:

QoS-Change

PLMN-Change

RAT-Change

IP_CAN-Change

Usage-Report

Successful-Resource-Alloc

UE-Timezone-Change

Resource-Modification-Request

UE-IP-Address-Allocate

UE-IP-Address-Release

Default-EPS-Bearer-QOS-Change

APN-AMBR-Modification-Failure

Default-EPS-Bearer-QOS-Modification-Failure

Event Report Indication: None

Negotiated QoS:

Default-Bearer-QoS:

QCI: 5

ARP:

PL: 10        PCI: 1

PVI: 1

APN AMBR Uplink(in bps): 600000        APN AMBR Downlink(in bps): 600000

CallId: 4d9f5163            Service Name: IMS-GX

IMSI:  300420160377232

Session ID: 0007-diamproxy.PHLA.Gx.ims.com;1302286691;929479551;55814953-17f02

Bearer Type: GTP

SGSN IP-Addr: 203.0.113.3

APN: APN2

Bearer Control Mode: UE/NW

State: Connected

Negotiated Supported Features:

3gpp-r10

Bound PCRF Server: ohcis04mra01.cisco.com

Primary PCRF Server: ohcis04mra01.cisco.com

Secondary PCRF Server: njbbs04mra01.cisco.com

Primary P-CSCF: NA

Secondary P-CSCF: NA

Outstanding CCR-U: 0

UE IP Address:

UE IP Session Type: IPv4_IPv6

IPv4 Address: 100.107.226.26

IPv6 Prefix: 5555:1000:b029:a82d::

Auth Decision:

Event Triggers:

QoS-Change

PLMN-Change

RAT-Change

IP_CAN-Change

Out-Of-Credit

Reallocation-Of-Credit

Usage-Report

Resource-Modification-Request

UE-IP-Address-Allocate

UE-IP-Address-Release

Default-EPS-Bearer-QOS-Change

APN-AMBR-Modification-Failure

Default-EPS-Bearer-QOS-Modification-Failure

Event Report Indication: None

Negotiated QoS:

Default-Bearer-QoS:

QCI: 8

ARP:

PL: 10        PCI: 1

PVI: 1

APN AMBR Uplink(in bps): 150000000    APN AMBR Downlink(in bps): 150000000

Non-Subscriber specific commands

Although the commands “show port npu counters” and “show port datalink counters” apply to an entire interface, if trying to see if the system is processing data for a particular subscriber out the egress interface (see mention above of limitation of monitor subscriber), and the the subscriber can be controlled, then try to send very large packets through the network, and see if the interface counters increment by the number of packets sent in the short window during which they are

sent. Being able to do this with confidence in the results requires making sure the counters for the packet size chosen are not normally incrementing very frequently before running the test.