Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show unified-edge tdf statistics

 

Syntax

Release Information

Statement introduced in Junos OS Release 17.1.

Description

Display statistics for one or more TDF gateways. If a TDF gateway is not specified, then statistics for all TDF gateways are displayed.

Options

noneDisplay statistics for all TDF gateways.
domain domain-name(Optional) Display statistics for the specified TDF domain.

The output of the show unified-edge tdf statistics command with the domain domain-name option is the same as the output of the show unified-edge tdf domain statistics command.

gateway gateway(Optional) Display statistics for the specified TDF gateway.

Required Privilege Level

view

List of Sample Output

show unified-edge tdf statistics

Output Fields

Table 1 lists the output fields for the show unified-edge tdf statistics command. Output fields are listed in the approximate order in which they appear.

Table 1: show unified-edge tdf statistics Output Fields

Field Name

Field Description

Gateway

Name of the TDF gateway.

Control Plane Statistics

Subscriber attach attempts

Number of attempted session establishments and number of successful session establishments for IP-based subscribers (Success).

Peer initiated subscriber update attempts

Number of RADIUS client attempts to update the subscriber context of an IP-based subscriber.

TDF Time of day initiated update attempts

Number of attempted activations, deactivations, and revalidations of PCC rules and revalidations of the PCEF session for the time-of-day feature, and number of successful attempts (Success).

TDF initiated update attempts

Number of TDF gateway attempts to update an IFL-based subscriber context as a result of access interfaces going up or down, or as a result of access interfaces being added to or deleted from the subscriber configuration.

TDF initiated subscriber detach attempts

Number of attempted subscriber session detachments initiated by the TDF gateway.

Policy Server initiated subscriber detach attempts

Number of attempted subscriber session detachments initiated by the policy server.

Peer initiated subscriber detach attempts

Number of attempted IP-based subscriber session detachments initiated by the RADIUS client. For IFL-based subscribers, 0 is displayed.

Subscriber attach failures by cause

Number of session establishments that failed:

  • System failure

  • No resources

  • Service denied

  • Policy denied

  • Service PIC NACK

  • Others

Rejects due to early CAC

Number of rejects on the TDF gateway caused by early CAC.

Subscriber detach by cause

Number of subscriber detachments for the following cause:

  • service PIC NACK

Policy statistics

Subscriber session activation attempts

Number of subscriber session activations attempted.

In addition, the number of successful subscriber session establishments (Success) is displayed.

TDF initiated modification attempts

Number of session modifications initiated by TDF gateway.

In addition, the number of session modifications that were successful (Success) is displayed.

Policy Server initiated modification attempts

Number of session modifications initiated by the policy server.

In addition, the number of modifications that were successful (Success) is displayed.

TDF initiated session deactivations

Number of subscriber session deactivations initiated by the TDF gateway.

Policy Server initiated session deactivations

Number of subscriber session deactivations initiated by the policy server.

Modification event reason

Number of Gx modifications for each event reason:

  • Application Start

  • Application Stop

  • Revalidation—PCEF re-requested PCC rules from the PCRF.

Failure Statistics

  • Session terminations due to unreachable policy server—Number of sessions terminated because the policy server was unreachable.

  • Session terminations due to PCRF restart—Number of sessions terminated because the PCRF was restarted.

  • Rule Validation Failures—Number of sessions terminated because the validation of rules failed.

PCC Rule Statistics

  • Dynamic rule activations—Number of dynamic rule activations and deactivations (Deactivations).

  • Static rules activations—Number of static rule activations and deactivations (Deactivations).

  • Dynamic rule modifications—Number of dynamic rule modifications.

PCC Rule Failure Statistics

  • Rule update failure—Number of rules that cannot be updated.

ePCC/ADC Rule Statistics

  • Dynamic rule activations—Number of dynamic rule activations and deactivations (Deactivations).

  • Static rules activations—Number of static rule activations and deactivations (Deactivations).

  • Dynamic rule modifications—Number of dynamic rule modifications.

ePCC/ADC Rule Failure Statistics

  • Rule update failure—Number of rules that cannot be updated.

Usage Monitoring Statistics

UMI AVP validation failures

Number of times that decoding fails for any of the grouped AVPs that belong to the Usage Monitoring Information, such as the Monitoring key, Monitoring Level, and Granted Service Unit AVPs.

Session Level

The following information about usage monitoring at the session level is displayed:

  • UM activations—Number of session-level monitoring keys that the TDF gateway has activated.

  • UM update quota attempts—Number of times the PCRF has attempted to update the quota for a session-level monitoring key. The number of reports that the TDF gateway sent as a result of the update quota attempts is shown in Stats report sent.

  • UM implicit deactivations—Number of times that a session-level monitoring key has been implicitly deactivated by the TDF gateway. For example, this happens if a monitoring key does not receive additional quota after a threshold has been reached.

  • UM explicit deactivations—Number of session-level monitoring key deactivations that the TDF gateway has received from the PCRF. The number of reports that the TDF gateway sent as a result of the deactivations is shown in Stats report sent.

  • Usage report request received—Number of requests for session-level usage reports that the TDF gateway has received from the PCRF. The number of reports that the TDF gateway sent as a result of the requests is shown in Stats report sent.

  • UM threshold hit—Number of times that a threshold for a session-level monitoring key has been reached. The number of reports that the TDF gateway sent as a result of the threshold being reached is shown in Stats report sent.

Rule Level

The following information about usage monitoring at the rule level is displayed:

  • UM activations—Number of rule-level monitoring keys that the TDF gateway has activated.

  • UM update quota attempts—Number of times the PCRF has attempted to update the quota for a rule-level monitoring key. The number of reports that the TDF gateway sent as a result of the update quota attempts is shown in Stats report sent.

  • UM implicit deactivations—Number of times that a rule-level monitoring key has been implicitly deactivated by the TDF gateway. For example, this happens if a monitoring key does not receive additional quota after a threshold has been reached.

  • UM explicit deactivations—Number of rule-level monitoring key deactivations that the TDF gateway has received from the PCRF. The number of reports that the TDF gateway sent as a result of the deactivations is shown in Stats report sent.

  • Usage report request received—Number of requests for rule-level usage reports that the TDF gateway has received from the PCRF. The number of reports that the TDF gateway sent as a result of the requests is shown in Stats report sent.

  • UM threshold hit—Number of times that a threshold for a rule-level monitoring key has been reached. The number of reports that the TDF gateway sent as a result of the threshold being reached is shown in Stats report sent.

  • UM with no rule reference—Number of rule-level monitoring keys received by the TDF gateway that had no rule referring to it. These keys are not activated.

Service plane statistics

Subscriber detach attempts (NACK) by cause

Number of service PIC messages to session PIC indicating that subscriber creation or modification failed for the following causes:

  • Memory watermark high threshold hit

  • Memory watermark critical threshold hit

  • Memory alloc failure

  • Subscriber lookup failure

  • Others

Data plane statistics

Subscriber Stats

The following information about packets processed by the data plane for subscribers connected to the TDF domains in the TDF gateway is displayed:

  • Uplink—Statistics for traffic in the uplink direction from the TDF gateway to the PDN (Internet).

  • Downlink—Statistics for traffic in the downlink direction from the PDN (Internet) to the TDF gateway.

  • Packets—Number of packets forwarded in the uplink direction and in the downlink direction.

  • Bytes—Number of bytes forwarded in the uplink direction and in the downlink direction.

  • Dropped Packets—Number of packets dropped in the uplink direction and in the downlink direction.

  • Dropped Bytes—Number of bytes dropped in the uplink direction and in the downlink direction.

Non Subscriber Stats

The following information about packets processed by the data plane for traffic that does not belong to subscribers connected to the TDF domains in the TDF gateway is displayed:

  • Uplink—Statistics for traffic in the uplink direction from the TDF gateway to the PDN (Internet).

  • Downlink—Statistics for traffic in the downlink direction from the PDN (Internet) to the TDF gateway.

  • Packets—Number of packets sent in the uplink direction and in the downlink direction.

  • Bytes—Number of bytes sent in the uplink direction and in the downlink direction.

  • Dropped Packets—Number of packets dropped in the uplink direction and in the downlink direction.

  • Dropped Bytes—Number of bytes dropped in the uplink direction and in the downlink direction.

Sample Output

show unified-edge tdf statistics

user@host> show unified-edge tdf statistics