ON THIS PAGE
request network-access aaa address-assignment domain-profile
request network-access aaa address-assignment subscriber-group
request subscriber-group subscriber-group-name user-plane user-plane-name [enable | disable]
request user-plane maintenance associate serviced-user-plane
request user-plane maintenance disassociate serviced-user-plane
request user-plane maintenance switchover serviced-user-plane
show network-access address-assignment address-pool-manager status
Juniper BNG CUPS Controller CLI Operational Commands
This topic provides an overview of clear, request,
restart, and show commands, including syntax,
option descriptions, and sample output. You use these commands with Juniper BNG CUPS
Controller.
clear user-plane ipv6 router-advertisement
Syntax
clear ipv6 router-advertisement up-name <up-name user-plane-name>
Description
Clear IPv6 router advertisement counters.
Options
| up-name user-plane-name | Clear IPv6 router advertisement counters for the specified BNG User Plane. |
Required Privilege Level
view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear user-plane ipv6 router-advertisement up-name
user@host> clear user-plane ipv6 router-advertisement up-name up1-example
clear user-plane pppoe lockout
Syntax
clear user-plane pppoe lockout <up-name user-plane-name>
Description
Clear the lockout condition for the PPPoE client associated with the specified BNG User Plane.
Options
| up-name user-plane-name | Clear the lockout condition for the PPPoE clients associated with the specified BNG User Plane. |
Required Privilege Level
clear
Sample Output
clear use-plane pppoe lockout up-name
user@host> clear user-plane pppoe lockout up-name up-test-1
clear user-plane pppoe statistics
Syntax
clear user-plane pppoe statistics <up-name user-plane-name>
Description
Reset PPPoE session statistics information.
Options
| up-name user-plane-name | Reset PPPoE statistics for the specified BNG User Plane. |
Required Privilege Level
clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear user-plane pppoe statistics up-name
user@host> clear user-plane pppoe statistics up-name up-test1
clear user-plane statistics
Syntax
clear user-plane statistics <up-name user-plane-name>
Description
Clear subscriber-management statistics.
Options
| up-name user-plane-name | Clear subscriber-management statistics for the specified BNG User Plane. |
Required Privilege Level
view and system
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear user-plane statistics up-name
user@host> clear user-plane statistics up-name up1-example
request network-access aaa address-assignment domain-profile
Syntax
request network-access aaa address-assignment domain-profile profile-name profile-name ri-name routing-instance-name [enable-logins | disable-logins]
Description
Enable or disable logins for existing domains created from the domain profile and to control the creation of new domains from the domain profile.
Options
ri-name routing-instance-name |
Specify the routing instance name. |
profile-name profile-name |
Specify the name of the profile. |
[enable-logins | disable-logins] |
Specify the desired action for enabling logins. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request network-access aaa address-assignment subscriber-group
Syntax
request network-access aaa address-assignment subscriber-group subscriber-group-name [enable-logins | disable-logins]
Description
Enable or disable logins for a particular subscriber group.
Options
subscriber-group-name |
Specify the name of the subscriber group. |
[enable-logins | disable-logins] |
Specify the desired action for enabling logins. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request network-access aaa address-assignment user-plane
Syntax
request network-access aaa address-assignment user-plane user-plane-name [enable-login | disable-login]
Description
Enable or disable logins for subscribers originating from the specified BNG User Plane. When you use this command, you effectively enable or disable logins for existing domains associated with the BNG User Plane. You also control the creation of new domains for the BNG User Plane.
Options
user-plane user-plane-name |
Specify the BNG User Plane name. |
[enable-login | disable-login] |
Specify the desired action. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request subscriber-group subscriber-group-name user-plane user-plane-name [enable | disable]
Syntax
request subscriber-group <subscriber-group-name user-plane user-plane-name [enable | disable]>
Description
Disable or enable the BNG User Plane port for a BNG User Plane managed subscriber group.
Options
subscriber-group-name |
The subscriber group name for which you want to enable or disable the subscriber port. |
user-plane user-plane-name |
The subscriber group's BNG User Plane for which you want to either disable or enable the subscriber port. |
[enable | disable] |
Enable or disable the port for the subscriber group’s BNG User Plane. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
Sample Output
request subscriber-group subscriber-group-nameuser-plane user-plane-name
user@host> request subscriber-group SGRP1 user-plane boston disable
request subscriber-group switchover
Syntax
request subscriber-group switchover subscriber-group-name
Description
Activate or deactivate a subscriber group on a BNG User Plane. You use this command to switch between active and backup BNG User Planes. This command runs on the BNG CUPS Controller.
Options
subscriber-group-name |
Specify the subscriber group name that you want to make the active BNG User Plane. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request user-plane maintenance associate serviced-user-plane
Syntax
request user-plane maintenance associate serviced-user-plane user-plane-name serviced-port port-number backup-user-plane user-plane-name backup-port port-number
Description
Creates a backup of a BNG User Plane. You can run this command multiple times for each logical port active and backup pair.
Options
serviced-user-plane
user-plane-name |
Specify the serviced BNG User Plane name. |
serviced-port port-number |
Specify the serviced port number. |
backup-user-plane
user-plane-name |
Specify the backup BNG User Plane name. |
backup-port port-number |
Specify the backup port number. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request user-plane maintenance complete serviced-user-plane
Syntax
request user-plane maintenance complete serviced-user-plane user-plane-name
Description
Completes the maintenance operation for a BNG User Plane. The command ensures that all resources that were used for the maintenance operation are restored.
Options
serviced-user-plane
user-plane-name |
Specify the BNG User Plane name that was serviced as part of the maintenance operation. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request user-plane maintenance disassociate serviced-user-plane
Syntax
request user-plane maintenance disassociate serviced-user-plane user-plane-name request user-plane maintenance disassociate serviced-user-plane user-plane-name serviced-port port-number backup-user-plane user-plane-name backup-port port-number
Description
Remove the active and backup BNG User Plane association and remove the database synchronization.
Options
serviced-user-plane
user-plane-name |
Specify the serviced BNG User Plane name. |
serviced-port port-number |
Specify the serviced port number. |
backup-user-plane
user-plane-name |
Specify the backup BNG User Plane name. |
backup-port port-number |
Specify the backup port number. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
request user-plane maintenance switchover serviced-user-plane
Syntax
request user-plane maintenance switchover serviced-user-plane user-plane-name
Description
Switch the role of the active and the backup BNG User Planes for the logical port pairing.
Options
serviced-user-plane
user-plane-name |
Specify the serviced BNG User Plane name. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback only if an error occurs.
restart authentication-service
Syntax
restart authentication-service
Description
Restarts the authentication service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart authentication-service
user@host> restart authentication-service General authentication process started, pid 1687717
restart cpm-service
Syntax
restart cpm-service
Description
Restarts the Control Plane Manager daemon.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart cpm-service
user@host> restart cpm-service Control Plane Manager for dBNG started, pid <process-id>
restart dhcp-service
Syntax
restart dhcp-service
Description
Restarts the DHCP service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart dhcp-service
user@host> restart dhcp-service Junos Dynamic Host Configuration Protocol process started, pid 1687787
restart dynamic-flow-capture
Syntax
restart dhcp-service
Description
Restarts the dynamic flow capture service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart dynamic-flow-capture
user@host> restart dynamic-flow-capture Dynamic flow capture service started, pid 1688041
restart gtp-proxy-service
Syntax
restart gtp-proxy-service
Description
Restarts the GPRS tunneling protocol proxy service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart l2tp-service
user@host> restart gtp-proxy-service Control Plane GTP Protocol Proxy started, pid 1688164
restart l2tp-service
Syntax
restart l2tp-service
Description
Restarts the L2TP service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart l2tp-service
user@host> restart l2tp-service Universal edge Layer 2 Tunneling Protocol daemon started, pid 1687917
restart pfcp-proxy-service
Syntax
restart pfcp-proxy-service
Description
Restarts the PFCP proxy service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart pfcp-proxy-service
user@host> restart pfcp-proxy-service Control Plane PFCP Protocol Proxy started, pid 1688195
restart ppp-service
Syntax
restart ppp-service
Description
Restarts the Point-to-Point Protocol (PPP) service.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart ppp-service
user@host> restart ppp-service Universal edge PPP process started, pid 1687840
restart smg-service
Syntax
restart smg-service
Description
Restarts the Enhanced Session Management BNG CUPS Controller process. This command runs on the BNG CUPS Controller.
Options
control-plane-instance
control-plane-instance-name |
Display information for the designated control plane instance. This option is required when your BNG CUPS Controller system has multiple control plane instances. |
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request.
Sample Output
restart smg-service
user@host> restart smg-service Control Plane Manager for dBNG started, pid <process-id>
restart subscriber-statistics-service
Syntax
restart subscriber-statistics-service
Description
Restarts the Enhanced Session Management Statistics daemon.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request. This command runs on the BNG CUPS Controller.
Sample Output
restart subscriber-statistics-service
user@host> restart subscriber-statistics-service Control Plane Manager for dBNG started, pid <process-id>
restart upsf-service
Syntax
restart upsf-service
Description
Restarts the User Plane Selection Function daemon. This command runs on the BNG CUPS Controller.
Required Privilege Level
root
Output Fields
When you enter this command, you receive feedback on the status of your request.
Sample Output
restart upsf-service
user@host> restart upsf-service Control Plane Manager for dBNG started, pid <process-id>
show broadband-device
Syntax
show broadband-device [interface | detail | state | summary]
Description
Displays information for a broadband edge (BBE) device.
Options
interface |
Displays information for a the specified BBE device interface. |
detail |
Displays detailed information for all BBE devices. |
state |
Displays the state for each port on the BBE device. |
summary |
Displays summary information for all BBE devices. |
Required Privilege Level
root
Output Fields
Table 1 lists the
output fields for the show broadband-device command.
|
Field Name |
Field Description |
|---|---|
| Interface | BBE interface. |
|
Name |
BBE device name. |
|
Port |
The fully qualified BNG User Plane port name of the format up:user-plane-name:physical-port-name. |
|
Sessions |
The number of sessions. |
|
SGRP |
The subscriber group that the BBE device belongs to. |
|
User Plane |
The BNG User Planes that belong to the subscriber group. |
|
Redundancy interface name |
The redundancy-interface name containing the member BNG User Plane logical ports. |
|
Subscriber Group |
The subscriber group that the BBE device belongs to. |
|
Session ID |
Session identifier. |
Sample Output
show broadband-device summary
user@host> show broadband-device summary Interface Name Port Sessions Port Sessions SGRP bb0.1 alpha up:NYC:xe-2/0/0 125 up:Jersey:xe-1/0/0 124 NYC-1 bb0.2 beta up:NYC:xe-3/0/0 120 up:Jersey:xe-2/0/0 120 NYC-2
show broadband-device interface
user@host> show broadband-device interface bb0.1 Interface Name Port Sessions Port Sessions SGRP bb0.1 alpha up:NYC:xe-2/0/0 125 up:Jersey:xe-1/0/0 124 NYC-1
user@host> show broadband-device interface bb0.1 detail UP1 port : NYC:xe-2/0/0 (active) (124) UP2 port : Jersey:xe-1/0/0 (backup) (123) Redundancy Interface Name: alpha Subscriber Group: NYC-1 Subscriber Group ID: 26 Session ID UP1 state UP 2 state 200 Installed Installed-Warm 353 Installed Out of resources
show firewall
Syntax
show firewall <filter filter-name> <filter regex regular-expression> <terse>
Description
When running the show firewall command on the BNG CUPS
Controller, the output displays only the filter names and the associated BNG
User Plane. No counters or other information appears. To see the counters or the
log or syslog output, you must run the show firewall command on
the appropriate BNG User Plane.
Options
| filter filter-name |
(Optional) Name of a configured filter. |
| filter regex regular-expression |
(Optional) Regular expression that matches the names of a subset of filters. |
| terse |
(Optional) Display firewall filter names and BNG User Plane names. |
Required Privilege Level
view
Output Fields
Table 2 lists the output fields for the show
firewall command. Output fields are listed in the approximate order
in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of a filter that has been configured with the
|
| User Plane | BNG User Plane name |
Sample Output
show firewall terse
user@host> show firewall terse Filter: finid_UID4003-demux0.3221229982-in User Plane: up-example-2 Filter: dfwda-demux0.3221229982-in User Plane: up-example-2 Filter: finid_UID4003-demux0.3221225473-in User Plane: up-example-1 Filter: dfwda-demux0.3221225473-in User Plane: up-example-1
show health
Syntax
show health <subsystem microservice-name (endpoint endpoint-name)> <subsystem microservice-name (service service-name)> <user-plane user-plane-name (endpoint endpoint-name)>
Description
Displays the health information about the BNG CUPS Controller subsystems or the overall health of the BNG User Planes.
Options
| none |
Displays health information for all BNG CUPS Controller subsystems. |
|
subsystem microservice-name |
You can display health information for the following specified subsystems: |
|
service service-name |
Displays health information for the associated endpoints for the specified service that is part of the microservice. Not all services have associated endpoints. |
user-plane user-plane-name |
Displays BNG User Plane health information. |
endpoint endpoint-name |
Displays health information for the specified endpoint of the BNG User Plane. |
Required Privilege Level
root
Output Fields
Table 3 lists the
output fields for the show health command.
|
Field Name |
Field Description |
|---|---|
|
|
Depending on which show health command output you are viewing, the name field can be one of the following:
|
|
|
The name of the workload cluster on which a subsystem is running. This command applies only to multiple geographical redundancy deployments. |
|
|
The state of the subsystem. Either |
|
|
Health of the BNG CUPS Controller subsystem. Following are the health levels:
|
|
|
The number of unhealthy services. |
|
|
The amount of time the service has been up. |
|
|
The generation number of the subsystem. A subsystem's generation number increments each time it switches the workload clusters. This command applies only to multiple geographical redundancy deployments. |
|
|
The subsystem for which the information is being displayed. |
|
|
The health of the shared memory. |
|
|
Displays whether the initial state recovery succeeded. |
|
|
List of services for the subsystem. |
|
|
Current status of the service. Either |
|
|
The number of times the service restarted. |
|
|
The health of the endpoint for the service. |
|
|
The number of unhealthy endpoints for the service. |
|
|
List of key endpoints. |
|
|
State of the key endpoint. |
|
|
The number of times the key endpoint flapped. |
|
|
Memory usage of the service. |
|
|
The percentage of CPU being used by the service. |
|
|
Health of the BNG User Plane. Following are the health levels:
|
|
|
BNG User Plane IP address. |
|
|
The number of active and backup subscriber sessions served by the BNG User Plane. |
|
|
The state of the BNG User Plane. The state can be one of the following:
|
|
|
The BNG User Plane for which the information is being reported. |
|
|
The control plane instance that handling the BNG User Plane. |
|
|
The number of active subscriber sessions served by the BNG User Plane. |
|
|
The number of backup subscriber sessions served by the BNG User Plane. |
Sample Output
- show health
- show health subsystem
- show health subsystem bngd
- show health subsystem scache
- show health subsystem mgmt
- show health subsystem <microservice-name> service
- show health subsystem <microservice-name> endpoint
- show health user-plane
- show health user-plane
- show health user-plane <user-plane-name> endpoint
show health
user@host show health Name Cluster Subsystem-State Health Unhealthy-services Uptime Generation cpi-groton wlc001 active healthy 0 14d 02:22:19 1 cpi-westford wlc001 active healthy 0 18d 07:00:03 1 cpi-chelmsford wlc001 active healthy 0 18d 07:16:13 1 cpi-littleton wlc001 active healthy 0 18d 05:41:14 1 cpi-acton wlc001 active healthy 0 16d 11:31:58 1 bngd wlc001 active healthy 0 21d 02:24:19 1 mgmt wlc001 active healthy 0 21d 02:22:19 1 scache-1 wlc001 active healthy 0 21d 02:24:01 1 scache-2 wlc002 active healthy 0 21d 02:24:01 1
show health subsystem
user@host> show health subsystem cpi-hardening Subsystem: cpi-hardening Cluster: - Health: healthy Shared-memory: healthy Initial State Recovery: succeeded Services Status UpTime Restarts Endpoint-Health Unhealthy-Endpoints ppp-service up 05:59:04 0 healthy 0 pfcp-proxy-service up 05:59:08 0 healthy 0 smg-service up 05:59:08 0 healthy 0 replication-server-service up 06:08:20 0 healthy 0 replication-client-service up 06:08:20 0 healthy 0 authentication-service up 05:59:09 0 healthy 0 smd-4-service up 05:59:10 0 healthy 0 smd-3-service up 05:59:11 0 healthy 0 smd-2-service up 05:59:11 0 healthy 0 smd-1-service up 05:59:12 0 healthy 0 cpm-service up 06:08:20 0 healthy 0 l2tp-service up 05:59:05 0 healthy 0 dhcp-service up 05:59:06 0 healthy 0 upsf-service up 05:59:07 0 healthy 0 subscriber-statistics-service up 05:59:07 0 healthy 0 gtp-proxy-service up 05:59:09 0 healthy 0 Key-Endpoints State UpTime Flapped Sync cpi-test-Scache-Client reconciled - 0 completed cpi-test-Scache-Server connected 01:45:05 0 continuous Apm connected 01:44:32 1 - BngDirector-cpi-test connected 01:44:38 1 - cpi-test-BngDirector connected 01:44:44 1 - BngDirector-scache connected 01:44:38 1 -
show health subsystem bngd
user@host> show health subsystem bngd Subsystem: bngd Cluster: - Health: healthy Subsystem-State: active Generation: 1 Shared-memory: healthy Services Status UpTime Restarts Endpoint-Health Unhealthy-Endpoints bng-director-service up 11d 04:44:29 0 healthy 0 replication-client-service up 11d 04:44:29 0 healthy 0 replication-server-service up 11d 04:44:29 0 healthy 0 bngd-podmgr-service up 11d 04:44:31 0 healthy 0 Key-Endpoints State UpTime Flapped Sync BngDirector-scache connected 11d 04:44:30 0 - BngDirector-mgmt connected 11d 04:44:30 0 - BngDirector-cpi-xxx connected 09:27:22 0 - BngDirector-cpi-yyy connected 09:27:22 0 - bngd-Scache-Client reconciled - 0 completed bngd-Scache-Server connected 09:27:22 0 continuous
show health subsystem scache
user@host> show health subsystem scache Subsystem: scache Cluster: - Health: healthy Subsystem-State: active Generation: 1 Shared-memory: healthy Services Status UpTime Restarts Endpoint-Health Unhealthy-Endpoints scache-service up 10:51:27 0 healthy 0 replication-server-service up 10:51:27 0 healthy 0 replication-client-service up 10:51:27 0 healthy 0 Key-Endpoints State UpTime Flapped Sync Scache-cpi-xxx-Client connected 09:30:04 1 continuous Scache-cpi-xxx-Server reconciled - 0 completed Scache-cpi-yyy-Client connected 09:30:04 1 continuous Scache-cpi-yyy-Server reconciled - 0 completed Scache-bngd-Client connected 09:30:04 1 continuous Scache-bngd-Server reconciled - 0 completed Scache-mgmt-Client connected 09:30:04 1 continuous Scache-mgmt-Server reconciled - 0 completed scache-BngDirector connected 10:46:20 0 -
show health subsystem mgmt
user@host> show health subsystem mgmt Subsystem: mgmt Cluster: - Health: healthy Shared-memory: healthy Subsystem: mgmt Cluster: - Health: healthy Subsystem-State: active Generation: 1 Shared-memory: healthy Services Status UpTime Restarts Endpoint-Health Unhealthy-Endpoints mgmt-podmgr-service up 10:50:49 0 healthy 0 replication-server-service up 10:51:27 0 healthy 0 replication-client-service up 10:51:27 0 healthy 0 Key-Endpoints State UpTime Flapped Sync mgmt-BngDirector connected 09:27:22 0 - mgmt-Scache-Client reconciled - 0 completed mgmt-Scache-Server connected 09:27:22 0 continuous
show health subsystem <microservice-name> service
user@host> show health subsystem cpi-boston service gtp-proxy-service
Subsystem: cpi-boston
Cluster: -
Service: gtp-proxy-service
Status: up
State: ready
Up-time: 01:45:23
Memory Usage: 21364 kB
CPU% (threads): 0.0% (3)
Restarts: 0
Endpoint-health: healthy
Endpoint:Id Flapped State Up-time
GtpProxySmdLowIpc:1024 0 connected 01:45:10
GtpProxySmdHighIpc:1024 0 connected 01:45:10
GtpProxySmdMedIpc:1024 0 connected 01:45:10
show health subsystem <microservice-name> endpoint
user@host> show health subsystem cpi-boston endpoint apm Subsystem: cpi-boston Cluster: - Endpoint: Apm Status: connected Up-time: 01:45:04
show health user-plane
user@host> show health user-plane Name Address CPi State Health Up-time Active/Backup-sess test1 192.32.6.32 cpi-boston connected unhealthy-minor 2d 03:10:44 31281/10400 test2 156.9.0.41 - connecting unhealthy-major - 0/0 test3 178.3.65.9 cpi-boston misconfig healthy 16d 14:23:07 0/0 test4 77.100.1.19 - disconnected healthy 0d 00:00:00 0/0 test5 187.22.14.37 - disconnecting healthy 0d 00:00:00 0/0
show health user-plane
user@host> show health user-plane test123 User-plane: test123 Address: 192.32.6.32 Id: 1 CPi: cpi-boston State: connected Health: unhealthy-minor Up-time: 2d 03:10:44 Active-sessions: 31281 Backup-sessions: 10400 Endpoints Flapped State Up-time L2tpSmdIpc 0 connected 2d 03:10:44 SmdL2tpIpc 0 connected 2d 03:10:44 PppSmdIpc 0 connected 2d 03:10:44 SmdPppIpc 0 connected 2d 03:10:44 AuthSmdIpc 0 connected 2d 03:10:44 SmdAuthIpc 0 connected 2d 03:10:44 DhcpSmdIpc 0 connected 2d 03:10:44 SmdDhcpIpc 0 connected 2d 03:10:44 RepServerSS 0 connected 2d 03:10:44 Cpri 0 disconnected - Sci 0 connected 2d 03:10:44 PfcpProxySmdIpc 0 connected 2d 03:10:44 PfcpProxyStatsIpc 0 connected 2d 03:10:44 SmdPfcpProxyIpc 0 connected 2d 03:10:44 StatsPfcpProxyIpc 0 connected 2d 03:10:44
show health user-plane <user-plane-name> endpoint
user@host> show health user-plane test123 endpoint Cpri
User-plane: test123
Endpoint: Cpri
Status: Connected
High-priority : Connected
Medium-priority : Connected
Low-priority : Connected
High-Priority
Pkts client rx: 0
Pkts terminated locally: 13242
Pkts aggr rx: 13242
Pkts enqueue rx fail: 0
Client packets cp to up: 0
Aggr packets cp to up: 26512
Aggr packets cp to up fail: 0
Pkts injected locally: 26512
Last local seq num tx: 0
Last local seq num rx: 0
Last remote seq num rx: 13270
Total local echo pkts rx: 0
Total remote echo pkts rx: 13242
Num of echo pkts lost: 13270
Medium Priority:
Pkts client rx: 0
Pkts terminated locally: 13242
Pkts aggr rx: 13242
Pkts enqueue rx fail: 0
Client packets cp to up: 0
Aggr packets cp to up: 26512
Aggr packets cp to up fail: 0
Pkts injected locally: 26512
Last local seq num tx: 0
Last local seq num rx: 0
Last remote seq num rx: 13270
Total local echo pkts rx: 0
Total remote echo pkts rx: 13242
Num of echo pkts lost: 13270
Low Priority:
Pkts client rx: 0
Pkts terminated locally: 13242
Pkts aggr rx: 13242
Pkts enqueue rx fail: 0
Client packets cp to up: 0
Aggr packets cp to up: 26512
Aggr packets cp to up fail: 0
Pkts injected locally: 26512
Last local seq num tx: 0
Last local seq num rx: 0
Last remote seq num rx: 13270
Total local echo pkts rx: 0
Total remote echo pkts rx: 13242
Num of echo pkts lost: 13270
show load-balancing-group
Syntax
show load-balancing-group <group group-name>
Description
Displays information for the load-balancing group.
Options
| Empty |
If you do not enter a load-balancing group name, all load-balancing groups are listed. |
group group-name |
(Optional) Displays information about the listed load-balancing group. |
Required Privilege Level
root
Output Fields
Table 4 lists the
output fields for the show load-balancing-group command.
|
Field Name |
Field Description |
|---|---|
|
|
The name of the load-balancing group. |
|
|
BNG User Plane logical port. |
|
|
The logical port's current load, represented as a percentage. |
|
|
Indicates whether the CPU load has been exceeded. |
|
|
Current computed weight. |
|
|
Configured maximum weight. |
|
CPi |
The BNG CUPS Controller that the loading-balancing groups belong to. |
|
Logical-port-List |
List of BNG User Plane logical ports. |
Sample Output
show load-balancing-group
user@host> show load-balancing-group Name CPi Logical-Port-List cohort cpi-xxx up:cheleb:xe-2/1/18 up:etrigan:xe-2/2/0
show load-balancing-group group load-balancing-group-name
user@host> show load-balancing-group group mygroup
Group Name Logical-Port % Usage CPU Exceeded Computed weight Max weight
mygroup up:UP-example-1:ps0.30 80 Yes 6 10
up:UP-example-3:ps0.25 5 No 3 20
up:UP-example-2:ps0.22 30 No 2 20
up:UP-example-7:ps0.27 7 No 1 20
show network-access address-assignment address-pool-manager status
Syntax
show network-access address-assignment address-pool-manager status
Description
Displays the status of Juniper Address Pool Manager (APM).
Required Privilege Level
root
Output Fields
Table 5 lists the
output fields for the show network-access address-assignment
address-pool-manager status command. Output fields are listed in
alphabetical order.
|
Field Name |
Field Description |
|---|---|
| Address Pool Manager | IP address for APM |
| Status | Connection status of APM |
| Pool Count | Number of pools |
| Connect Timestamp | Time at which APM first connected to BNG CUPS Controller |
| Security | Connection status: secured or not secured |
| Appointment mode | One of the following appointment
modes:
|
Sample Output
show network-access address-assignment address-pool-manager status
user@host> show network-access address-assignment address-pool-manager status Address Pool Manager: 10.9.160.19 Protocol: gRPC Security: clear-text Apportionment mode: Remote
show network-access address-assignment domain
Syntax
show network-access address-assignment domain <name> domain-name <routing-instance> routing-instance-name
Description
Displays the state of each pool domain (dynamic linked address pool) connected to APM and a count of the transmitted alarms for a specified routing instance.
Options
name domain-name |
domain-profile |
(Optional) Displays information depending on which of the following
variables are entered:
|
routing-instance
routing-instance-name |
(Optional) Designate the routing instance to use. If left empty, the default routing instance is used. |
Required Privilege Level
root
Output Fields
Table 6 lists the
output fields for the show network-access address-assignment domain
command. Output fields are listed in alphabetical order.
|
Field Name |
Field Description |
|---|---|
| Abatement (Abate) | The number of abatement alarms. An the
alarm occurs when either of the following conditions changes,
causing APM to disregard the original alarm:
|
|
Active-Tag |
The value of the route tag that is associated with the discard routes installed on the active BNG User Plane. |
| Addresses | Total number of addresses in the pool domain. |
| Apportion (Apport) | The number of apportion alarms. The alarm occurs when the number of free addresses falls below the apportion threshold. |
|
Backup-Tag |
The value of the route tag that is associated with the discard routes installed on the backup BNG User Plane. |
| Domain Name | Name of the pool domain. |
| Free | Number of addresses in the pool domain that are available for allocation. |
| Pool Count | Number of pools. |
| Pool Drain (Drain) | The number of pool drain alarms. The alarm occurs when a pool is completely drained. |
| Pool Name | Name of the pool. |
| Prefix | Subnetwork allocated to the address pool. |
| Programmed |
The state of the pool state (discard routes, dhcp gateway address, and so on) programming to the BNG User Plane. |
| Reclaim | The number of reclaim alarms. The alarm occurs when the number of free addresses for the pool domain on the BNG CUPS Controller rises above the reclaim threshold. |
| State |
State of the pool domain. |
|
Status |
The pool is either active or in drain mode. |
|
Type |
The source of the pool prefix. It can be a local reserve partition or a remote (APM) partition. |
| Used |
The number of addresses being used. |
|
User-Plane |
The BNG User Plane that is the target for the programmed pool state. |
Sample Output
- show network-access address-assignment domain
- show network-access address-assignment domain name (routing instance)
- show network-access address-assignment domain name
- show network-access address-assignment domain name
show network-access address-assignment domain
user@host> show network-access address-assignment domain Domain Name Active-Tag Backup-Tag Pool Count Addresses Free Apport Reclaim Abate Drain v4pool-milan-default 44 55 2 510 268 2 0 0 0 v4pool-milan-foo 33 66 4 1020 137 4 0 0 0
show network-access address-assignment domain name (routing instance)
user@host> show network-access address-assignment domain name test1234 routing-instance default56 Domain Name Pool Count Addresses Free Apportion Reclaim Abatement PoolDrain test1234-default56 1 1024 98 1 1 0 1
show network-access address-assignment domain name
user@host show network-access address-assignment domain name v4pool-default Pool Name Prefix Addresses Used Type Status User-Plane Programmed User-Plane Programmed v4pool-default-00001 10.19.0.0/24 254 24 Local Active milan added rome adding v4pool-default-00002 10.19.2.0/24 254 0 Local Drained milan removed rome removing
show network-access address-assignment domain name
user@host show network-access address-assignment domain name genoa-default Pool Name Prefix Addresses Used Status Mode genoa-default 6.0.0.0/30 4 4 Active Remote genoa-default-0000 6.0.0.4/30 4 0 Active Remote genoa-default-00001 10.0.0.0/30 4 0 Active Local
show network-access address-assignment domain-state
Syntax
show network-access address-assignment domain-state <routing-instance> routing-instance-name
Description
Displays the alarm state (outstanding alarms) for each pool domain.
Options
routing-instance
routing-instance-name |
(Optional) Designate the routing instance to use. If left empty, the default routing instance is used. |
Required Privilege Level
root
Output Fields
Table 7 lists the
output fields for the show network-access address-assignment
domain-state command. Output fields are listed in alphabetical
order.
|
Field Name |
Field Description |
|---|---|
| Domain Name | Name of the pool domain. |
| Alarm | Name of the alarm.
|
| Age | How long an alarm has been outstanding. |
| Logins | Whether logins are enabled. |
| State | State of the pool domain. |
Sample Output
- show network-access address-assignment domain
- show network-access address-assignment domain name (using domain profile)
- show network-access address-assignment domain name
show network-access address-assignment domain
user@host> show network-access address-assignment domain Domain Name Pool Count Addresses Free Apportion Reclaim Abatement PoolDrain 1232-default 3 507 120 1 0 0 0 test-default 2 1535 279 1 0 0 0
show network-access address-assignment domain name (using domain profile)
user@host> show network-access address-assignment domain name test1234 routing-instance default56 Domain Name Pool Count Addresses Free Apportion Reclaim Abatement PoolDrain test1234-default56 1 1024 98 1 1 0 1
show network-access address-assignment domain name
user@host show network-access address-assignment domain name test1234-default56 routing-instance default56 Pool Name Prefix Addresses Used State test1234-default56 192.0.2.1/24 255 253 Active test1234-default56-000 192.0.2.8/24 254 0 Active -
show routing-instances
Syntax
show routing instances <routing-instance-name>
Description
Displays a list of BNG User Planes that are using the listed routing instance.
Options
routing-instance-name |
The routing instance name for which you want the list of BNG User Planes. |
Required Privilege Level
view
Output Fields
Table 24 lists the output fields for the show
routing-instances command. Output fields are listed in the
approximate order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of the BNG User Plane. |
|
|
The routing instance state:
|
Sample Output
show routing-instances
user@host> show routing-instances example-1 Routing Instance: example-1 User Plane Name Routing Instance State test-2 isolated test-3 isolated example-1 connected example-2 connected
show subscriber-group
Syntax
show subscriber-group subscriber-group-name
Description
Displays information for subscriber groups.
Options
subscriber-group subscriber-group-name
|
Subscriber group for which you want to display information. If you do not enter a subscriber-group-name, the command only displays information for subscriber groups that have logical-ports associated with the subscriber group. If you want to see information for a subscriber group that does not have any logical ports associated with it, you must include the subscriber-group-name in the command. |
Required Privilege Level
root
Output Fields
Table 9 lists the
output fields for the show subscriber-group command.
|
Field Name |
Field Description |
|---|---|
|
Name |
Subscriber group name. |
|
ID |
ID number for the subscriber group. |
|
SGRP Mode |
The operational mode of the device, either Control Plane or User Plane |
|
SGRP State |
Health status of the subscriber group. Either healthy or unhealthy. |
|
User Plane |
The BNG User Planes that belong to the subscriber group. |
|
Active UP |
The active BNG User Plane. |
|
Mode |
The operational mode of the device, either Control Plane or User Plane. |
|
BB device |
The Broadband device that is a member of the subscriber group. |
|
Name (Logical port mapping) |
Logical port mapping name. |
|
Logical-port |
BNG User Plane logical port. |
|
Sessions |
The number of subscriber sessions. |
|
Name (Address domains) |
Address Domain name. |
|
Prefixes |
The number of address prefixes assigned to the specified BNG User Plane for the subscriber group. |
|
User-Plane |
The BNG User Plane that the specified subscriber group belongs to. The User-Plane field lists the following information:
|
|
Programmed |
The number of address prefixes programmed on the User Plane for the subscriber group |
|
Name (Routing Instances) |
Routing instances name. |
|
User-Plane (Address domain) |
BNG User Plane name. |
|
CPi |
The BNG CUPS Controller that the subscriber groups belong to. |
Sample Output
- show subscriber-group
- show subscriber-group subscriber-group-name
- show subscriber-group subscriber-group-name
show subscriber-group
user@host> show subscriber-group Name CPi ID SGRP Mode SGRP State User Plane User Plane Active UP SGRP1_CP cpi-xxx 2048 Control Plane healthy r14mx960wf r7mx304wf r14mx960wf r7mx304wf cpi-yyy 1025 Control Plane healthy r7mx304wf --- r7mx304wf
show subscriber-group subscriber-group-name
user@host> show subscriber-group SGRP1 Name: SGRP1 ID: 2048 User-Plane: jersey (active) (hot) (admin-disabled) User-Plane: boston (backup) (hot) Health status: healthy Mode: User Plane VMAC: 0A:0A:0A:0A:0A:0A Logical port mapping: BB device Name Logical-port Sessions Logical-port Sessions bb0.8 beta up:ps0 0 up:boston:ps0 0
show subscriber-group subscriber-group-name
user@host> show subscriber-group example-1 Name: example-1 ID: 1 User-Plane: caelum (active) , (hot) Health status: healthy Mode: Control Plane Logical port mapping: BB device Name Logical-port Sessions Logical-port Sessions bb0.12 bb0.12 up:caelum:xe-2/1/0 13000 --- --- bb0.9 bb0.9 up:caelum:xe-2/0/0 12999 --- --- bb0.8 bb0.8 up:caelum:xe-1/1/0 16000 --- --- bb0.7 bb0.7 up:caelum:xe-1/0/0 16000 --- --- bb0.6 bb0.6 up:caelum:ge-2/3/0 12999 --- --- bb0.5 bb0.5 up:caelum:ge-2/2/0 13000 --- --- Address domains: Name Prefixes User-Plane Programmed User-Plane Programmed v4pool:caelum:default 352 caelum 352 --- ---
show subscribers
Syntax
show subscribers <display (detail | extensive | terse)> <accounting-statistics> <aci-interface-set-name address> <address address> <agent-circuit-identifier agent-circuit-identifier> <agent-remote-identifier agent-remote-identifier> <id> session-id <mac-address mac-address> <user-name user-name>
Description
Display information for active subscribers.
Options
display
(detail | extensive |
terse) |
(Optional) Display the specified level of output. |
accounting-statistics |
(Optional) Display subscriber accounting statistics |
aci-interface-set-name |
(Optional) Display all the dynamic subscriber sessions that use the specified agent circuit identifier (ACI) interface set. You must use the ACI interface set name generated by the router, such as aci-1003-ge-1/0/0.4001, and not the actual ACI value found in the Dynamic Host Configuration Protocol (DHCP) or Point-to-Point Protocol over Ethernet (PPPoE) control packets. |
address |
(Optional) Display subscribers whose IP address matches the specified address. You must specify the IPv4 or IPv6 address prefix without a netmask (for example, 192.0.2.0). If you specify the IP address as a prefix with a netmask (for example, 192.0.2.0/32), the router displays a message that the IP address is invalid, and rejects the command. |
agent-circuit-identifier |
(Optional) Display all dynamic subscriber sessions whose ACI value matches the specified string. You can specify either the complete ACI string or a substring. To specify a substring, you must enter characters that form the beginning of the string, followed by an asterisk (*) as a wildcard to substitute for the remainder of the string. The wildcard can be used only at the end of the specified substring; for example: user@host1> show subscribers agent-circuit-identifier substring* |
agent-remote-identifier |
(Optional) Display all dynamic subscriber sessions whose ARI value matches the specified string. You must specify the complete ACI string; you cannot specify a wildcard. |
id session-id |
(Optional) Display a specific subscriber session whose session ID
matches the specified subscriber ID. You can display subscriber IDs
by using the |
mac-address |
(Optional) Display subscribers whose MAC address matches the specified MAC address. |
user-name |
(Optional) Display subscribers whose username matches the specified subscriber name. |
Because of display limitations, logical system and routing instance output values are truncated when necessary.
Required Privilege Level
view
Output Fields
Table 10 lists the output fields for the show
subscribers command. Output fields are listed in the approximate
order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Interface associated with the subscriber. The router or switch displays subscribers whose interface matches or begins with the specified interface. The * character indicates a continuation of addresses for the same session. |
|
|
Subscriber IP address or VLAN ID associated with the subscriber in the form tpid.vlan-id No IP address or VLAN ID is assigned to an L2TP
tunnel-switched session. For these subscriber sessions the
value is |
|
|
Name of subscriber. |
|
|
Logical system and routing instance associated with the subscriber. |
|
|
Subscriber client type (DHCP, FWA, GRE, L2TP, PPP, PPPoE, STATIC-INTERFACE, VLAN). |
|
|
Subscriber IPv4 address. |
|
|
Subscriber IP netmask. This field displays 255.255.255.255 by default. For tunneled or terminated PPP subscribers only, this field displays the actual value of Framed-IP-Netmask when the SDB_FRAMED_PROTOCOL attribute in the session database is equal to AUTHD_FRAMED_PROTOCOL_PPP. This occurs in the use case where the LNS generates access-internal routes when it receives Framed-IP-Netmask from RADIUS during authorization. When it receives Framed-Pool from RADIUS, the pool mask is ignored and the default /32 mask is used. |
|
|
IP address of primary DNS server. This field is displayed with the |
|
|
IP address of secondary DNS server. This field is displayed with the |
|
|
IPv6 address of primary DNS server. This field is displayed with the |
|
|
IPv6 address of secondary DNS server. This field is displayed with the |
|
|
IP addresses for the DNS server, displayed in order of configuration. This field is displayed with the |
|
|
IPv6 addresses for the DNS server, displayed in order of configuration. This field is displayed with the |
|
|
IP address of primary WINS server. |
|
|
IP address of secondary WINS server. |
|
|
Subscriber IPv6 address, or multiple addresses. |
|
|
Subscriber IPv6 prefix. If you are using DHCPv6 prefix delegation, this is the delegated prefix. |
|
|
IPv6 prefix obtained through NDRA. |
|
|
Subscriber IPv6 address pool. The IPv6 address pool is used to allocate IPv6 prefixes to the DHCPv6 clients. |
|
|
Length of the network portion of the IPv6 address. |
|
|
Length of the subscriber IPv6 prefix. |
|
|
Logical system associated with the subscriber. |
|
|
Routing instance associated with the subscriber. |
|
|
(Enhanced subscriber management for MX Series routers) Name
of the enhanced subscriber management logical interface, in
the form |
|
|
Whether the subscriber interface is |
|
|
Internally generated name of the dynamic ACI or ALI interface set used by the subscriber session. The prefix of the name indicates the string received in DHCP or PPPoE control packets on which the interface set is based. For ALI interface sets, the prefix indicates that the value is configured as a trusted option to identify the subscriber line. The name of the interface set uses one of the following prefixes:
Note:
ACI interface sets are configured with the
Besides dynamic ACI and ALI interface sets, this field can be an interface set based on a substring of the ARI string. This occurs when the dynamic profile includes the predefined variable $junos-pon-id-interface-set-name, and the profile is applied for a passive optical network (PON). The ARI string is inserted by the optical line terminal (OLT). The final substring in the string, unique for the PON, identifies individual subscriber circuits, and is used as the name of the interface set. |
|
|
Interface type of the ACI interface set:
|
|
|
Identifier of the dynamic ACI interface set entry in the session database. |
|
|
Name of the underlying interface for the subscriber session. |
|
|
Dynamic profile used for the subscriber. |
|
|
Version number of the dynamic profile used for the subscriber. |
|
|
MAC address associated with the subscriber. |
|
|
Current state of the subscriber session
( |
|
|
Current state of the L2TP session, |
|
|
Name of the L2TP tunnel switch profile that initiates tunnel switching. |
|
|
IP address of the local gateway (LAC). |
|
|
IP address of the remote peer (LNS). |
|
|
Forwarding flow identifier. |
|
|
VLAN ID associated with the subscriber in the form tpid.vlan-id. |
|
|
Stacked VLAN ID associated with the subscriber in the form tpid.vlan-id. |
|
|
RADIUS accounting ID associated with the subscriber. |
|
|
For the For the |
|
|
For the For the |
|
|
Value of the $junos-aggregation-interface-set-name predefined variable; one of the following:
|
|
|
Actual transmitted subscriber accounting statistics by
session ID or interface. Service accounting statistics are
not included. These statistics do not include overhead bytes
or dropped packets; they are the accurate statistics used by
RADIUS. The statistics are counted when the
|
|
|
IP address used by the DHCP relay agent. |
|
|
Date and time at which the subscriber logged in. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Actual downstream traffic shaping rate for the subscriber, in kilobits per second. |
|
|
Input service set in access dynamic profile. |
|
|
Output service set in access dynamic profile. |
|
|
PCEF profile in access dynamic profile. |
|
|
PCC rule or rulebase used in dynamic profile. |
|
|
Values for variables that are passed into the dynamic profile from RADIUS. |
|
|
Time at which the first family in this service became active. |
|
|
Name of the filter applied by the dynamic profile to IPv4 packets that fail the RPF check. |
|
|
Name of the filter applied by the dynamic profile to IPv6 packets that fail the RPF check. |
|
|
|
|
|
ID number for a subscriber session. |
|
|
For DHCPv6 subscribers on a PPPoE network, displays the session ID of the underlying PPPoE interface. |
|
|
Number of service sessions (that is, a service activated using RADIUS CoA) associated with the subscribers. |
|
|
ID number for a subscriber service session. |
|
|
Service session profile name. |
|
|
Number of seconds of access provided to the subscriber before the session is automatically terminated. |
|
|
Number of seconds subscriber can be idle before the session is automatically terminated. |
|
|
Name of the pool used for DHCPv6 prefix delegation. |
|
|
Length of the prefix configured for the IPv6 delegated address pool. |
|
|
Address assigned by the Framed-Ipv6-Prefix AAA attribute. This field is displayed only when the predefined variable $junos-ipv6-address is used in the dynamic profile. |
|
|
Interface ID assigned by the Framed-Interface-Id AAA attribute. |
|
|
Name assigned to the Ascend-Data-Filter (ADF) interface IPv4 input filter (client or service session). The filter name is followed by the rules (in hexadecimal format) associated with the ADF filter and the decoded rule in Junos OS filter style. |
|
|
Name assigned to the Ascend-Data-Filter (ADF) interface IPv4 output filter (client or service session). The filter name is followed by the rules (in hexadecimal format) associated with the ADF filter and the decoded rule in Junos OS filter style. |
|
|
Name assigned to the Ascend-Data-Filter (ADF) interface IPv6 input filter (client or service session). The filter name is followed by the rules (in hexadecimal format) associated with the ADF filter and the decoded rule in Junos OS filter style. |
|
|
Name assigned to the Ascend-Data-Filter (ADF) interface IPv6 output filter (client or service session). The filter name is followed by the rules (in hexadecimal format) associated with the ADF filter and the decoded rule in Junos OS filter style. |
|
|
Name assigned to the IPv4 input filter (client or service session). |
|
|
Name assigned to the IPv4 output filter (client or service session). |
|
|
Name assigned to the IPv6 input filter (client or service session). |
|
|
Name assigned to the IPv6 output filter (client or service session). |
|
|
Name assigned to the logical interface input filter (client or service session). |
|
|
Name assigned to the logical interface output filter (client or service session). |
|
|
PPPoE subscriber’s access line type reported by the PPPoE
intermediate agent in a PADI or PADO packet in the
Vendor-Specific-Tags TLV in subattribute DSL-Type (0x0091).
The DSL type is one of the following types:
|
|
|
Mode type of the PPPoE subscriber’s access line determined by the PPPoE daemon based on the received subattribute DSL-Type (0x0091):
The value is stored in the subscriber session database. |
|
|
Number of bytes added to or subtracted from the actual downstream cell or frame overhead to account for the technology overhead of the DSL line type. The value is determined by the PPPoE daemon based on the received subattribute DSL-Type (0x0091). The value is stored in the subscriber session database. |
|
|
Unadjusted upstream data rate for the PPPoE subscriber’s access line reported by the PPPoE intermediate agent in a PADI or PADO packet in the Vendor-Specific-Tags TLV in subattribute Actual-Net-Data-Rate-Upstream (0x0081). |
|
|
Unadjusted downstream data rate for the PPPoE subscriber’s access line reported by the PPPoE intermediate agent in a PADI or PADO packet in the Vendor-Specific-Tags TLV in subattribute Actual-Net-Data-Rate-Downstream (0x0082). |
|
|
Adjusted downstream data rate for the PPPoE subscriber’s access line, calculated by the PPPoE daemon and stored in the subscriber session database. |
|
|
Adjusted upstream data rate for the PPPoE subscriber’s access line, calculated by the PPPoE daemon and stored in the subscriber session database. |
|
|
Tunnel endpoint identifier on the BNG for the GTP-U user plane tunnel to the eNodeB. The identifier is allocated by the BNG. A fully qualified local TEID-C consists of this identifier
and the |
|
|
Tunnel endpoint identifier on the BNG for the GTP-C control plane tunnel to the MME. The identifier is allocated by the BNG. A fully qualified local TEID-C consists of this identifier
and the |
|
|
Tunnel endpoint identifier on the eNodeB for the GTP-U user plane tunnel to the BNG. The identifier is allocated by the eNodeB. A fully qualified remote TEID-U consists of this identifier
and the |
|
|
Tunnel endpoint identifier on the MME for the GTP-C control plane tunnel to the BNG. The identifier is allocated by the MME. A fully qualified remote TEID-C consists of this identifier
and the |
|
|
IP address of the S1-U interface on the eNodeB for the GTP-U tunnel endpoint. A fully qualified remote TEID-U consists of this address and
the |
|
|
IP address of the S1-U interface on the BNG for the GTP-U tunnel endpoint. A fully qualified local TEID-U consists of this address and
the |
|
|
IP address of the S11 interface on the MME for the GTP-C tunnel endpoint. A fully qualified remote TEID-C consists of this address and
the |
|
|
IP address of the S11 interface on the BNG for the GTP-C tunnel endpoint. A fully qualified local TEID-C consists of this address and
the |
|
|
Access point name (APN) for the user equipment. The APN corresponds to the connection and service parameters that the subscriber’s mobile device can use for connecting to the carrier’s gateway to the Internet. |
|
|
Name of the tenant system. You can create multiple tenant system administrators for a tenant system with different permission levels based on your requirements. |
User Plane id |
ID number for the BNG User Plane that the subscriber belongs to. |
User Plane
Name |
Name of the BNG User Plane that the subscriber belongs to. |
User-plane:port |
The BNG User Plane that the subscriber belongs to with its port number and whether it is configured as active or backup. |
|
|
Name of the routing instance. When a custom routing instance is created for a tenant system, all the interfaces defined in that tenant system are added to that routing instance. |
|
|
Configured name for a specific variation of a base dynamic profile. IT’s presence indicates that the profile configuration is different from that of the base profile. The value is conveyed to the RADIUS server during authentication in the Client-Profile-Name VSA (26–4874–174). |
|
|
BNG CUPS Controller instance. |
|
|
The subscriber group that the subscriber belongs to. |
|
|
Lists the active BNG User Plane for the SGRP. |
Sample Output
- show subscribers user-name
- show subscribers user-name
- show subscribers detail (DHCP)
- show subscribers accounting-statistics id
- show subscribers client-type (PPPoE)
- show subscribers client-type (DHCP)
- show subscribers detail
- show subscribers agent-circuit-identifier substring detail
show subscribers user-name
user@host> show subscribers user-name user@host.com SID CP-instance SGRP Ports 234096 cpi-boston alk-vest003 alkaid:xe-0/0/1,cora:xe-2/1/1 230077 cpi-boston alk-west001 alkaid:xe-2/1/1,cora:xe-0/2/0
show subscribers user-name
user@host> show subscribers user-name user@host.com display detail <device header for cpi-boston> Type: DHCP User Name: joe@sixpack.com IP Address: 192.168.0.1 IP Netmask: 255.255.255.0 Logical System: default Routing Instance: default Interface: demux0.3221225553 Interface-tag: foobar-tag Interface type: Dynamic Underlying Interface: demux0.3221225547 Dynamic Profile Name: dhcp-demux-prof MAC Address: 00:01:02:03:04:28 Idle Timeout (seconds): 1800 Idle Timeout Ingress Only: FALSE State: Active Radius Accounting ID: 4106 Session ID: 234096 SGRP: alk-vest003 User-plane:port: alkaid:xe-2/1/1 (active) User-plane:port: cora:xe-2/0/1 (backup) PFE Flow ID: 132 Stacked VLAN Id: 210 VLAN Id: 214 Login Time: 2023-04-24 07:44:46 PDT DHCP Options: len 3 35 01 01 DHCP Header: len 44 01 01 06 00 84 76 db 36 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 02 03 04 28 00 00 00 00 00 00 00 00 00 00
show subscribers detail (DHCP)
user@host> show subscribers detail Type: DHCP IP Address: 16.0.0.2 IP Netmask: 255.0.0.0 Logical System: default Routing Instance: default User Plane ID: 1 Interface: up:green-arrow:demux0.3221225474 Interface type: Dynamic Underlying Interface: up:green-arrow:ge-0/3/5.2 Dynamic Profile Name: client-dhcp-demux MAC Address: 00:00:64:03:01:02 State: Active Radius Accounting ID: 8 Session ID: 8 PFE Flow ID: 12 VLAN Id: 10 Login Time: 2022-02-23 22:35:35 UTC DHCP Options: len 3 35 01 01 DHCP Header: len 44 01 01 06 00 dd 7d 5a 46 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 64 03 01 02 00 00 00 00 00 00 00 00 00 00 Type: DHCP IPv6 Address: 1000::3 Logical System: default Routing Instance: default User Plane ID: 1 Interface: up:green-arrow:demux0.3221225475 Interface type: Dynamic Underlying Interface: up:green-arrow:ge-0/3/5.2 Dynamic Profile Name: client-dhcp-demux MAC Address: 00:00:64:03:01:02 State: Active Radius Accounting ID: 9 Session ID: 9 PFE Flow ID: 13 VLAN Id: 10 Login Time: 2022-02-23 22:35:44 UTC DHCPV6 Options: len 42 00 08 00 02 00 00 00 01 00 0a 00 03 00 01 00 00 64 03 01 02 00 06 00 02 00 03 00 03 00 0c 00 00 00 00 00 00 00 00 00 00 00 00 DHCPV6 Header: len 4 01 03 00 00
show subscribers accounting-statistics id
user@host> show subscribers accounting-statistics id 206 Session ID: 206 Interface: pp0.3221225677 Accounting Statistics Input bytes: 0 Input packets: 0 Output bytes: 0 Output packets: 0 IPv6 Input bytes: 0 Input packets: 0 Output bytes: 0 Output packets: 0
show subscribers client-type (PPPoE)
user@host> show subscribers client-type pppoe Interface IP Address/VLAN ID User Name LS:RI up:green-arrow:pp0.3221225473 100.16.0.2 user-example-1 default:default * 1000::2
show subscribers client-type (DHCP)
user@host> show subscribers client-type pppoe Interface IP Address/VLAN ID User Name LS:RI up:green-arrow:demux0.3221225474 16.0.0.2 default:default up:green-arrow:demux0.3221225475 1000::3 default:default
show subscribers detail
user@host> show subscribers detail Type: VLAN Logical System: default Routing Instance: default User Plane ID: 2 SGRP ID: 1 SGRP Refcnt: 1 Interface: demux0.3221225472 Interface type: Dynamic Underlying Interface: bb0 Dynamic Profile Name: ppp-dvlan State: Active Session ID: 469 PFE Flow ID: 419 Stacked VLAN Id: 0x8100.3500 VLAN Id: 0x8100.3500 Login Time: 2023-02-23 16:40:27 UTC Type: VLAN Logical System: default Routing Instance: default User Plane ID: 2 SGRP ID: 1 SGRP Refcnt: 1 Interface: ge-0/0/0 Interface Set: aci-1002-demux0.3221225472 Interface Set Session ID: 0 Underlying Interface: demux0.3221225472 Dynamic Profile Name: ACI-SET-NGN2 State: Active Session ID: 470 Agent Circuit ID: ACI-Household-1 Login Time: 2023-02-23 16:40:27 UTC Type: PPPoE User Name: DEFAULTUSER IP Address: 192.0.101.31 IP Netmask: 255.255.255.255 IPv6 User Prefix: 3000:0:0:119::/64 Logical System: default Routing Instance: default User Plane ID: 2 SGRP ID: 1 Interface: pp0.3221225473 Interface type: Dynamic Interface Set: aci-1002-demux0.3221225472 Interface Set Session ID: 470 Underlying Interface: demux0.3221225472 Dynamic Profile Name: SOHO-NGN2-FTTH MAC Address: 00:03:01:00:00:01 State: Active Radius Accounting ID: 471 Session ID: 471 PFE Flow ID: 419 Stacked VLAN Id: 3500 VLAN Id: 3500 Agent Circuit ID: ACI-Household-1 Login Time: 2023-02-23 16:40:27 UTC
show subscribers agent-circuit-identifier substring detail
user@host> show subscribers agent-circuit-identifier ACI-Household-1 detail Type: VLAN Logical System: default Routing Instance: default User Plane ID: 2 SGRP ID: 1 SGRP Refcnt: 1 Interface: ge-0/0/0 Interface Set: aci-1002-demux0.3221225472 Interface Set Session ID: 0 Underlying Interface: demux0.3221225472 Dynamic Profile Name: ACI-SET-NGN2 State: Active Session ID: 470 Agent Circuit ID: ACI-Household-1 Login Time: 2023-02-23 16:40:27 UTC Type: PPPoE User Name: DEFAULTUSER IP Address: 192.0.101.31 IP Netmask: 255.255.255.255 IPv6 User Prefix: 3000:0:0:119::/64 Logical System: default Routing Instance: default User Plane ID: 2 SGRP ID: 1 Interface: pp0.3221225473 Interface type: Dynamic Interface Set: aci-1002-demux0.3221225472 Interface Set Session ID: 470 Underlying Interface: demux0.3221225472 Dynamic Profile Name: SOHO-NGN2-FTTH MAC Address: 00:03:01:00:00:01 State: Active Radius Accounting ID: 471 Session ID: 471 PFE Flow ID: 419 Stacked VLAN Id: 3500 VLAN Id: 3500 Agent Circuit ID: ACI-Household-1 Login Time: 2023-02-23 16:40:27 UTC
show subscribers subscriber-group
Syntax
show subscribers subscriber-group sgrp-name subscriber-goup-name <client-type client-type> <broadband-device broadband-device-name> <interface interface-name <profile-name profile-name> <routing-instance routing-instance> <stacked-vlan-id stacked-vlan-id> <subscriber-state subscriber-state> <user-name user-name> <vlan-id vlan-id>
Description
Display information for subscribers as part of a subscriber group.
Options
broadband-device-name |
Name of the broadband edge device. |
| client-type |
(Optional) Display subscribers whose client type matches one of the following client types:
|
| interface |
(Optional) Display subscribers whose interface matches the specified interface. |
| profile-name |
(Optional) Display subscribers whose dynamic profile matches the specified profile name. |
| routing-instance |
(Optional) Display subscribers whose routing instance matches the specified routing instance. |
| stacked-vlan-id |
(Optional) Display subscribers whose stacked VLAN ID matches the specified stacked VLAN ID. |
| subscriber-state |
(Optional) Display subscribers whose subscriber state matches the specified subscriber state (ACTIVE, CONFIGURED, INIT, TERMINATED, or TERMINATING). |
| user-name |
(Optional) Display subscribers whose username matches the specified subscriber name. |
| vlan-id |
(Optional) Display subscribers whose VLAN ID matches the specified
VLAN ID, regardless of whether the subscriber uses a single-tagged
or double-tagged VLAN. For subscribers using a double-tagged VLAN,
this option displays subscribers where the inner VLAN tag matches
the specified VLAN ID. To display only subscribers where the
specified value matches only double-tagged VLANs, use the
|
Because of display limitations, routing instance output values are truncated when necessary.
Required Privilege Level
view
Output Fields
Table 11 lists the
output fields for the show subscribers subscriber-group
command. Output fields are listed in the approximate order in which they
appear.
|
Field Name |
Field Description |
|---|---|
|
|
The associated BNG CUPS Controller. |
|
|
The list of broadband edge devices. |
|
|
Subscriber IPv4 address. |
|
|
Name of subscriber. |
|
|
Routing instance associated with the subscriber. |
|
|
ID number for a subscriber session. |
|
|
Lists whether the device is configured as active or backup. |
Sample Output
show subscribers subscriber-group sgrp-name
user@host> show subscribers subscriber-group sgrp-name SGRP2_UP Broadband-device IP Address User Name RI SID Resiliency-state bb0.12 default 6183 - bb0.12 5.0.0.254 user@juniper.com RI_2 6184 -
show subscribers summary
Syntax
show subscribers summary <user-plane user-plane-name> <subscriber-group subscriber-group-name> <control-plane-instance control-plane-instance-name> <port>
Description
Display summary information for subscribers.
Options
user-plane user-plane-name |
Display subscriber information for the designated BNG User Plane. |
subscriber-group
subscriber-group-name |
Display subscriber information for the designated subscriber group. |
control-plane-instance
control-plane-instance-name |
Display subscriber information for the designated control plane instance. |
port |
Display the number of active subscriber sessions for the BNG User Plane ports. |
Required Privilege Level
view
Output Fields
Table 12 lists the output fields for the show subscribers
summary command. Output fields are listed in the approximate order
in which they appear.
|
Field Name |
Field Description |
|---|---|
|
user-plane |
BNG User Plane name. |
|
control-plane-instance |
BNG CUPS Controller name. |
|
subscriber-group |
Subscriber group name. |
|
|
Number of subscribers summarized by state. The summary information includes the following:
|
|
|
Number of subscribers summarized by client type. Client types can include DHCP, GRE, L2TP, PPP, PPPoE, STATIC-INTERFACE, and VLAN. Also displays the total number of subscribers for all client types (Total). |
Sample Output
- show subscribers summary
- show subscribers summary control-plane-instance
- show subscribers summary control-plane-instance control-plane-instance-name
- show subscribers summary user-plane
- show subscribers summary user-plane user-plane-name
- show subscribers summary subscriber-group
- show subscribers summary subscriber-group subscriber-group-name
- show subscribers summary port
show subscribers summary
user@host> show subscribers summary user-plane up-example-1 Subscribers by State Active: 1 Total: 1 Subscribers by Client Type DNCP: 1 Total: 1
show subscribers summary control-plane-instance
user@host> show subscribers summary control-plane-instance Subscriber by State control-plane-instance init configured active terminating terminated total cpi-boston 200 100 38665 610 425 40000 cpi-new-york 0 0 20000 0 0 20000 Subscribers by Client Type control-plane-instance vlan dhcp pppoe l2tp total cpi-boston 10 39990 0 0 40000 cpi-new-york 10 19990 0 0 20000
show subscribers summary control-plane-instance control-plane-instance-name
user@host> show subscribers summary control-plane-instance cpi-boston Subscribers by State Init: 200 Configured: 100 Active: 38665 Terminating: 610 Terminated: 425 Total: 40000 Subscribers by Client Type DHCP: 39990 VLAN: 10 Total: 40000
show subscribers summary user-plane
user@host> show subscribers summary user-plane Subscriber by State user-plane control-plane-instance init configured active terminating terminated total R0mx30401 cpi-boston 0 0 36235 610 425 37270 R0mx3048a cpi-boston 200 100 2430 0 0 2730 R1mx1003a0 cpi-new-york 0 0 20000 0 0 20000 Subscribers by Client Type user-plane control-plane-instance vlan dhcp pppoe l2tp total R0mx30401 cpi-boston 10 37260 0 0 37270 R0mx3048a cpi-boston 20 2410 0 0 2730 R1mx1003a0 cpi-new-york 1000 19000 0 0 20000
show subscribers summary user-plane user-plane-name
user@host> show subscribers summary user-plane up-example1 Subscribers by State Active: 36235 Terminating: 610 Terminated: 425 Total: 37270 Subscribers by Client Type DHCP: 37260 VLAN: 10 Total: 37270 Subscribers by Resiliency State Active: 18630 Backup: 18630 Total: 37270
show subscribers summary subscriber-group
user@host> show subscribers summary subscriber-group Subscriber by State subscriber-group init configured active terminating terminated total mx-default 0 0 36235 610 425 37270 mx-def-nord 0 100 2430 0 0 2730 mx-sud 0 0 20000 0 0 20000 Subscribers by Client Type subscriber-group vlan dhcp pppoe l2tp total mx-default 10 37260 0 0 37270 mx-def-nord 20 2410 0 0 2730 mx-sud 1000 19000 0 0 20000
show subscribers summary subscriber-group subscriber-group-name
user@host> show subscribers summary subscriber-group example-subscriber-group Subscribers by State Active: 36235 Terminating: 610 Terminated: 425 Total: 37270 Subscribers by Client Type DHCP: 37260 VLAN: 10 Total: 37270
show subscribers summary port
user@host> show subscribers summary subscriber-group example-subscriber-group Interface up:acubens-up:et-0/0/0:0 145096 up:acubens-up:et-0/1/1:0 2291 up:cassiopeia-up:et-0/0/0:1 7822
show subscribers user-plane
Syntax
show subscribers user-plane up-name user-plane-name <client-type client-type> <interface interface <physical-interface physical-interface-name> <profile-name profile-name> <routing-instance routing-instance> <stacked-vlan-id stacked-vlan-id> <subscriber-state subscriber-state> <user-name user-name> <vlan-id vlan-id>
Description
Displays information for subscribers associated to a BNG User Plane.
Options
| client-type |
(Optional) Display subscribers whose client type matches one of the following client types:
|
| interface |
(Optional) Display subscribers whose interface matches the specified interface. |
| physical-interface-name |
(Optional) Display subscribers whose physical interface matches the specified physical interface. |
| profile-name |
(Optional) Display subscribers whose dynamic profile matches the specified profile name. |
| routing-instance |
(Optional) Display subscribers whose routing instance matches the specified routing instance. |
| stacked-vlan-id |
(Optional) Display subscribers whose stacked VLAN ID matches the specified stacked VLAN ID. |
| subscriber-state |
(Optional) Display subscribers whose subscriber state matches the specified subscriber state (ACTIVE, CONFIGURED, INIT, TERMINATED, or TERMINATING). |
| user-name |
(Optional) Display subscribers whose username matches the specified subscriber name. |
| vlan-id |
(Optional) Display subscribers whose VLAN ID matches the specified
VLAN ID, regardless of whether the subscriber uses a single-tagged
or double-tagged VLAN. For subscribers using a double-tagged VLAN,
this option displays subscribers where the inner VLAN tag matches
the specified VLAN ID. To display only subscribers where the
specified value matches only double-tagged VLANs, use the
|
Because of display limitations, routing instance output values are truncated when necessary.
Required Privilege Level
view
Output Fields
Table 13 lists the
output fields for the show subscribers user-plane command.
Output fields are listed in the approximate order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
The associated BNG CUPS Controller. |
|
|
The list of broadband edge devices. |
|
|
Subscriber IPv4 address. |
|
|
Name of subscriber. |
|
|
Routing instance associated with the subscriber. |
|
|
ID number for a subscriber session. |
|
|
Lists whether the device is configured as active or backup. |
Sample Output
show subscribers user-plane up-name
user@host> show subscribers user-plane up-name test123 client-type dhcp physical-interface ae1 Control-plane-instance: cpi-test1 Broadband-device IP Address User Name RI SID Resiliency-state bb0.1 192.168.0.0 user@host.com default 1340 Active bb0.1 192.168.0.5 user@host.com default 1897 Active bb0.2 192.168.0.6 user@host.com default 2349 Backup
show user-plane igmp interface
Syntax
show user-plane igmp interface up-name user-plane-name
Description
Displays information about Internet Group Management Protocol (IGMP)-enabled interfaces on BNG User Planes.
Options
| none |
When you run this command on the BNG CUPS Controller, the output displays standard information about all IGMP-enabled interfaces on all BNG User Planes associated to the BNG CUPS Controller. When you run this command on a BNG User Plane, the output displays standard information about all IGMP-enabled interfaces on the BNG User Plane. |
up-name user-plane-name |
(Optional) Displays information about the IGMP-enabled interfaces on the specified BNG User Plane. |
Required Privilege Level
view
Output Fields
Table 14 describes the output fields for the show user-plane
igmp interface command. Output fields are listed in the approximate
order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of the interface. |
|
|
Address of the routing device that has been elected to send membership queries. |
|
|
State of the interface: Up or Down. |
|
Timeout |
How long until the IGMP querier is declared to be unreachable, in seconds. |
|
|
IGMP version being used on the interface: 1 , 2 , or 3. |
|
|
Number of groups on the interface. |
|
|
Configured threshold at which a warning message is generated. This threshold is based on a percentage of groups received on the interface. If the number of groups received reaches the configured threshold, the device generates a warning message. |
|
|
Time (in seconds) between consecutive log messages. |
|
|
The SSM map policy applied to the IGMP interface.. |
|
|
State of the immediate leave option:
|
|
|
State of the promiscuous mode option:
|
|
|
State of IGMP, which, by default, takes place on the Routing Engine for MX Series routers but can be distributed to the Packet Forwarding Engine to provide faster processing of join and leave events.
|
|
|
State of the passive mode option:
The
|
|
|
The group policy applied to the IGMP interface. |
Sample Output
show user-plane igmp interface up-name
user@host> show user-plane igmp interface up-name up-example-1
Interface: up:up-example-1:pp0.3221225481
Querier: 0.0.0.0
State: Up Timeout: None Version: 3
Group threshold: 0
SSM map policy: igmp-ssm-map-policy
Immediate leave: On
Promiscuous mode: On
Passive: Off
Group policy: igmp-group-policy
Distributed: On
Release Information
Statement introduced in Juniper BNG CUPS Release.
show user-plane ipv6 router-advertisement
- Syntax
- Description
- Options
- Additional Information
- Required Privilege Level
- Output Fields
- Sample Output
- Release Information
Syntax
show user-plane ipv6 router-advertisement <interface interface> <prefix prefix/prefix length> <up-name user-plane-name>
Description
Display information about IPv6 router advertisements, including statistics about messages sent and received on interfaces, and information received from advertisements from other routers.
The router advertisement module does not function in the backup Routing Engine as the Routing Engine does not send an acknowledgment message after receiving the packets.
Options
| interface interface |
(Optional) Display IPv6 router advertisement information for the specified interface. |
| prefix prefix/prefix length |
(Optional) Display IPv6 router advertisement information for the specified prefix. |
| up-name user-plane-name |
The BNG User Plane for which you want to view IPv6 router advertisement information. |
Additional Information
The display identifies conflicting information by enclosing the value the router is advertising in brackets.
Required Privilege Level
view
Output Fields
Table 15 describes the output fields for the show user-plane ipv6
router-advertisement command. Output fields are listed in the
approximate order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of the interface. |
|
|
Number of router advertisements sent and the elapsed time since they were sent. |
|
|
Number of solicitation messages received. |
|
|
Number of router advertisements received. |
|
|
Names of interfaces from which router advertisements have been received and the elapsed time since the last one was received. |
|
|
Managed address configuration flag: |
|
|
Other stateful configuration flag: |
|
|
Time that a node identifies a neighbor as reachable after receiving a reachability confirmation, in milliseconds. |
|
|
Default lifetime, in seconds: from 0 seconds to 18.2 hours. A setting of 0 indicates that the router is not a default router. |
|
|
Time between retransmitted Neighbor Solicitation messages, in milliseconds. |
|
|
Configured current hop limit. |
|
|
Name and length of the prefix. |
|
|
How long the prefix remains valid for onlink determination. |
|
|
How long the prefix generated by stateless autoconfiguration remains preferred. |
|
|
Onlink flag: |
|
|
Autonomous address configuration flag: |
|
|
Configured interface as upstream interface for RA proxy |
|
|
Configured interface as downstream interface for RA proxy. |
|
|
Downstream interface for RA proxy. |
|
|
RA receive only mode is enabled. |
|
|
Proxy blackout timer interval is the time interval for which the interface must not be used as a proxy interface. Proxy functionality is disabled on that interface. |
|
|
Preference to select configured or proxied parameters for downstream interface |
|
|
Displays the details of the error. |
Sample Output
show user-plane ipv6 router-advertisement up-name
user@host> show user-plane ipv6 router-advertisement up-name up-test1
Interface: fe-0/1/1.0
Advertisements sent: 0
Solicits received: 0
Advertisements received: 0
Interface: fxp0.0
Advertisements sent: 0
Solicits received: 0
Advertisements received: 1
Advertisement from fe80::2d0:b7ff:fe1e:7b0e, heard 00:00:13 ago
Managed: 0
Other configuration: 0 [1]
Reachable time: 0 ms
Default lifetime: 1800 sec
Retransmit timer: 0 ms
Current hop limit: 64Release Information
show user-plane maintenance
Syntax
show user-plane maintenance up-name user-plane-name
Description
Displays the maintenance state for a BNG User Plane.
Options
user-plane-name |
Display the maintenance status of the specified BNG User Plane. |
Required Privilege Level
view
Output Fields
Table 16
lists the output fields for the show user-plane maintenance
up-name command.
|
Field Name |
Field Description |
|---|---|
|
|
The current maintenance status of the BNG User Plane. |
|
|
The BNG User Plane that is being serviced. |
|
|
The backup BNG User Plane. |
|
|
Broadband device for the logical port pair for the BNG User Plane being serviced and the backup BNG User Plane. |
|
|
Redundancy interface name for the logical port pair for the BNG User Plane being serviced and the backup BNG User Plane. |
|
|
The number of subscriber sessions configured on the BNG User Plane logical port. |
|
|
The number of subscriber sessions configured on the BNG User Plane logical port. |
|
|
Name of the address Domain. |
|
|
The number of address prefixes assigned to the address domain. |
|
|
The BNG User Plane name. |
|
|
One of the following:
|
|
|
Name of the routing instance. |
|
|
The routing tag value used for the active BNG User Plane. |
|
|
The routing tag value used for the backup BNG User Plane. |
Sample Output
show user-plane maintenance up-name
user@host> show user-plane maintenance up-name up-exampl-1
Maintenance Status:- In-progress
Serviced UP: up-exampl-1 – Active/Synchronized
Backup UP: up-examp2-2- Backup/Sync-in-progress
Logical port mapping:
BB device Name Logical-port Sessions Logical-port Sessions
bb0.1 alpha up:NYC:xe-2/0/0 1125 up:Jersey:xe-2/0/0 1120
bb0.2 beta up:NYC:xe-3/0/0 4588 up:Jersey:xe-2/0/0 4588
Address Domains:
Name Prefixes User-Plane Programmed User-Plane Programmed
Domain-foo:NYC:default 125 up-exampl-1 125 Jersey 125
Domain-bar:NYC:bar 255 up-exampl-1 255 Jersey 240
Routing Instances:
Name Tag Backup-Tag User-Plane Programmed User-Plane Programmed
default 55 77 up-exampl-1 added Jersey adding
bar 277 314 up-exampl-1 removing Jersey removed
show user-plane mld interface
Syntax
show user-plane mld interface up-name user-plane-name
Description
Displays information about multipoint Listener Discovery (MLD)-enabled interfaces.
Options
| none |
When you run this command on the BNG CUPS Controller, the output displays standard information about all MLD-enabled interfaces on all BNG User Planes associated to the BNG CUPS Controller. When you run this command on a BNG User Plane, the output displays standard information about all MLD-enabled interfaces on the BNG User Plane. |
| up-name user-plane-name |
(Optional) Displays information about the MLD-enabled interfaces on the specified BNG User Plane. |
Required Privilege Level
view
Output Fields
Table 17 describes the output fields for the show user-plane
mld interface command. Output fields are listed in the approximate
order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of the interface. |
|
|
Address of the router that has been elected to send membership queries. |
|
|
State of the interface: Up or Down. |
|
|
How long until the MLD querier is declared to be unreachable, in seconds. |
|
|
MLD version being used on the interface: 1 or 2. |
|
Groups |
Number of groups on the interface. |
|
Passive |
State of the passive mode option:
The
|
|
Group threshold |
Configured threshold at which a warning message is generated. This threshold is based on a percentage of groups received on the interface. If the number of groups received reaches the configured threshold, the device generates a warning message. |
|
Immediate Leave |
State of the immediate leave option:
|
|
Distributed |
State of MLD, which, by default, takes place on the Routing Engine for MX Series routers but can be distributed to the Packet Forwarding Engine to provide faster processing of join and leave events.
|
|
Promiscuous Mode |
State of the promiscuous mode option:
|
Sample Output
show user-plane mld interface up-name
user@host> show user-plane mld interface up-name up-example-1
IInterface: pp0.3221225473
Querier: ::
State: Up Timeout: None Version: 2
Group threshold: 0
Immediate leave: Off
Promiscuous mode: Off
Passive: Off
Distributed: On
Release Information
Statement introduced in Juniper BNG CUPS Release
show user-plane pppoe interfaces
Syntax
show user-plane pppoe interfaces <brief | detail | extensive> <up-name user-plane-name>
Description
Display session-specific information about PPPoE interfaces.
Options
| none |
Display interface information for all PPPoE interfaces. |
| brief | detail | extensive |
(Optional) Display the specified level of output. |
| up-name user-plane-name |
The BNG User Plane for which you want to view PPPoE interface information. |
Required Privilege Level
view
Output Fields
Table 18 lists the output fields for the show user-plane
pppoe interfaces command. Output fields are listed in the
approximate order in which they appear.
|
Field Name |
Field Description |
Level of Output |
|---|---|---|
| Logical Interface | ||
|
|
Name of the logical interface. |
All levels |
|
|
Index number of the logical interface, which reflects its initialization sequence. |
|
|
|
State of the logical interface: |
All levels |
|
|
Session ID. |
All levels |
|
|
Origin of the logical interface: |
|
|
|
Type of service required (can be used to indicate an ISP name or a class or quality of service). |
|
|
|
Configured access concentrator name. |
|
|
|
Name of the access concentrator. |
|
|
|
MAC address of the remote side of the connection, either the access concentrator or the PPPoE client. |
All levels |
|
|
Length of time the session has been up, in hh:mm:ss. |
|
|
|
Name of the dynamic profile that was used to create this interface. If the interface was statically created, this field is not displayed. |
|
|
|
Interface on which PPPoE is running. |
All levels |
|
|
Agent circuit identifier (ACI) that corresponds to the DSLAM interface that initiated the client service request. An asterisk is interpreted as a wildcard character and can appear at the beginning, the end, or both the beginning and end of the string. If the agent circuit ID is not configured, this field is not displayed. |
|
|
|
Agent remote identifier that corresponds to the subscriber associated with the DSLAM interface that initiated the service request. An asterisk is interpreted as a wildcard character and can appear at the beginning, the end, or both at the beginning and end of the string. If the agent remote ID is not configured, this field is not displayed. |
|
|
|
Internally-generated name of the dynamic ACI interface set, if configured, and the set index number of the ACI entry in the session database. |
|
|
|
Number of packets sent and received during the PPPoE session, categorized by packet type and packet errors:
|
|
Sample Output
show user-plane pppoe interfaces up-name
user@host> show user-plane pppoe interfaces up-name up-test1 up:green-arrow:pp0.3221225473 Index 536870923 State: Session Up, Session ID: 1, Type: Dynamic, Service name: AGILENT, Remote MAC address: 00:00:64:02:01:02, Session AC name: bng-controller, Session uptime: 00:00:19 ago, Dynamic Profile: ppp-dp-pp0, Underlying interface: up:green-arrow:ge-0/3/5.1 Index 3
show user-plane pppoe lockout
Syntax
show user-plane pppoe lockout <underlying-interface-name> <up-name user-plane-name>
Description
Display summary information about PPPoE clients currently undergoing lockout or currently in a lockout grace period on all PPPoE underlying logical interfaces or on a specified PPPoE underlying logical interface, for the specified BNG User Plane. You can configure PPPoE subscriber session lockout, also known as short-cycle protection, for VLAN, VLAN demux, and PPPoE-over-ATM dynamic subscriber interfaces.
Options
| none |
Display information about the lockout condition and the lockout grace period for PPPoE clients on all PPPoE underlying logical interfaces. |
| underlying-interface-name |
(Optional) Name of the PPPoE underlying logical interface. If you do not specify an underlying interface, the router iteratively displays output for all existing clients undergoing lockout per PPPoE underlying logical interface. |
| up-name user-plane-name |
The BNG User Plane for which you want to view PPPoE information. |
Required Privilege Level
view
Output Fields
Table 19 lists the output fields for the show user-plane
pppoe lockout command. Output fields are listed in the approximate
order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of the PPPoE underlying logical interface. |
|
|
Index number of the logical interface, which reflects its initialization sequence. |
|
|
Name of the physical interface or aggregated Ethernet bundle. |
|
|
Stacked VLAN ID, also known as the outer tag. |
|
|
VLAN ID, also know as the inner tag. |
|
|
Virtual path identifier value for the PPPoE client. |
|
|
Virtual circuit identifier value for the PPPoE client. |
|
|
State of PPPoE short-cycle protection, also known as PPPoE subscriber session lockout, on the underlying interface:
Enabling short-cycle protection temporarily prevents (locks out) a failed or short-lived (short-cycle) PPPoE subscriber session from reconnecting to the router for a default or configurable period of time. |
|
|
Displays the PPPoE lockout time range, the number of PPPoE clients in lockout condition, and the number of PPPoE clients in a lockout grace period:
|
|
|
MAC source address or agent circuit idenfiier (ACI) value of the PPPoE client. |
|
|
Current lockout time, in seconds; displays |
|
|
Time elapsed into the lockout period, in seconds; displays
|
|
|
Lockout time, in seconds, that the router uses for the next lockout event; displays a nonzero value if the PPPoE client is currently in a lockout grace period. |
Sample Output
show user-plane pppoe lockout up-name
user@host> show user-plane pppoe lockout at-1.0.0.30 up-name test-up1
at-1/0/0.30 Index 10305
Device: at-1/0/0, VPI: 1, VCI: 30
Short Cycle Protection: circuit-id,
Lockout Time (seconds): Min: 1, Max: 300
Total clients in lockout: 1
Total clients in lockout grace period: 1
Client Address Current Elapsed Next
Relay-identifier atm 3/0:100.33 64 22 128
00:00:5e:00:53:ab
00:00:5e:00:53:21show user-plane pppoe lockout up-name
user@host> show user-plane pppoe lockout demux0.100 up-name test-up1
demux0.100 Index 10305
Device: xe-1/0/0, SVLAN: 100, VLAN: 100,
Short-Cycle Protection: mac-address,
Lockout Time (seconds): Min: 1, Max: 300
Total clients in lockout: 3
Total clients in lockout grace period: 1
Client Address Current Elapsed Next
00:00:5e:00:53:15 16 10 32
00:00:5e:00:53:ab 256 168 300
00:00:5e:00:53:23 0 0 8show user-plane pppoe service-name-tables
Syntax
show user-plane pppoe service-name-tables <table-name> <up-name user-plane-name>
Description
Display configuration information about PPPoE service name tables, for the specified BNG User Plane.
Options
| none |
Display the names of configured PPPoE service name tables. |
| table-name |
(Optional) Name of a configured PPPoE service name table. |
| up-name user-plane-name |
The BNG User Plane for which you want to view PPPoE service name table information. |
Required Privilege Level
view
Output Fields
Table 20 lists the output fields for the show user-plane
pppoe service-name-tables command. Output fields are listed in the
approximate order in which they appear.
|
Field Name |
Field Description |
Level of Output |
|---|---|---|
|
|
Name of the PPPoE service name table. |
none |
|
|
Name of a configured service in the PPPoE service name table:
|
none |
|
|
Action taken when the PPPoE underlying interface interface
receives a PPPoE Active Discovery Initiation (PADI) packet
with the specified named service,
|
none |
|
|
Name of the dynamic profile with which the router creates a
dynamic PPPoE subscriber interface. A dynamic profile can be
assigned to a named service, |
none |
|
|
Name of the routing instance in which to instantiate the
dynamic PPPoE subscriber interface. A routing instance can
be assigned to a named service, |
none |
|
|
Maximum number of active PPPoE sessions that the router can
establish with the specified named service,
|
none |
|
|
Current count of active PPPoE sessions created using the
specified named service, |
none |
|
|
Agent circuit identifier (ACI) that corresponds to the DSLAM
interface that initiated the client service request. An
asterisk is interpreted as a wildcard character and can
appear at the beginning, the end, or both the beginning and
end of the string. An ACI can be configured as part of an
ACI/ARI pair for a named service, |
none |
|
|
Agent remote identifier (ARI) that corresponds to the
subscriber associated with the DSLAM interface that
initiated the service request. An asterisk is interpreted as
a wildcard character and can appear at the beginning, the
end, or both at the beginning and end of the string. An ARI
can be configured as part of an ACI/ARI pair for a named
service, |
none |
|
|
Name of the static PPPoE interface reserved for exclusive use by the PPPoE client with matching ACI/ARI information. A static interface can be configured only for an ACI/ARI pair. |
none |
Sample Output
show user-plane pppoe service-name-tables up-name
user@host> show user-plane pppoe service-name-tables up-name test-up1 Service Name Table: test1 Service Name Table: test2 Service Name Table: test3
show user-plane pppoe service-name-tables up-name
user@host> show user-plane pppoe service-name-tables Table1 up-name test-up1 Service Name Table: Table1 Service Name: <empty> Action: Terminate Dynamic Profile: BasicPppoeProfile Max Sessions: 100 Active Sessions: 3 Service Name: <any> Action: Drop ACI: velorum-ge-2/0/3 ARI: westford Action: Terminate Static Interface: pp0.100 ACI: volantis-ge-5/0/5 ARI: sunnyvale Action: Terminate Static Interface: pp0.101 Service Name: Wholesale Action: Terminate Dynamic Profile: WholesalePppoeProfile Routing Instance: WholesaleRI Max Sessions: 16000 Active Sessions: 4
show user-plane pppoe sessions
Syntax
show user-plane pppoe sessions <aci circuit-id-string> <ari remote-id-string> <service service-name> <up-name user-plane-name>
Description
Display information about all active PPPoE sessions on the router, or about the active PPPoE sessions established for a specified service name, agent circuit identifier (ACI), or agent remote identifier (ARI).
Options
| none |
Display information for all active PPPoE sessions on the router. |
| aci circuit-id-string |
(Optional) Display information only for active PPPoE sessions established with the specified agent circuit identifier. The agent circuit identifier corresponds to the DSLAM interface that initiated the service request. |
| ari remote-id-string |
(Optional) Display information only for active PPPoE sessions established with the specified agent remote identifier. The agent remote identifier corresponds to the subscriber associated with the DSLAM interface that initiated the service request. |
| service service-name |
(Optional) Display information only for active PPPoE sessions
established with the specified service, where
service-name can be |
| up-name user-plane-name |
The BNG User Plane for which you want to view active PPPoE sessions. |
Required Privilege Level
view
Output Fields
Table 21 lists the output fields for the show user-plane
pppoe sessions command. Output fields are listed in the approximate
order in which they appear.
|
Field Name |
Field Description |
Level of Output |
|---|---|---|
|
|
Name of the statically-created or dynamically-created PPPoE interface for the active PPPoE session. |
none |
|
|
Interface on which PPPoE is running. |
none |
|
|
State of the PPPoE session; displays |
none |
|
|
PPPoE session identifier. |
none |
|
|
MAC address of the remote side of the connection, either the access concentrator or the PPPoE client. |
none |
Sample Output
show user-plane pppoe sessions up-name
user@host> show user-plane pppoe sessions up-name test-up1 Interface Underlying State Session Remote interface ID MAC up:green-arrow:pp0.3221225473 up:green-arrow:ge-0/3/5.1 Session Up 1 00:00:64:02:01:02
show user-plane pppoe statistics
Syntax
show user-plane pppoe statistics <logical-interface-name> <up-name user-plane-name>
Description
Display statistics information about PPPoE interfaces.
Options
| none |
Display PPPoE statistics for all interfaces. |
| logical-interface-name |
(Optional) Name of a PPPoE underlying logical interface. |
| up-name user-plane-name |
The BNG User Plane for which you want to view PPPoE statistics. |
Required Privilege Level
view
Output Fields
Table 22 lists the output fields for the show user-plane
pppoe statistics command. Output fields are listed in the
approximate order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Total number of active PPPoE sessions and the number of packets sent and received during the PPPoE session, categorized by packet type and packet errors:
|
|
|
Information about timeouts that occurred during the PPPoE session (not displayed for M120, M320, and MX Series routers):
|
Sample Output
show user-plane pppoe statistics up-name
user@host> show user-plane pppoe statistics up-name test-up1 Active PPPoE sessions: 32000 PacketType Sent Received PADI 0 60216 PADO 60216 0 PADR 0 60216 PADS 60216 0 PADT 0 28178 Service name error 0 0 AC system error 0 0 Generic error 0 0 Malformed packets 0 0 Unknown packets 0 0 Active PPPoE sessions: 53326 PacketType Sent Received PADI 0 244012 PADO 244012 0 PADR 0 244287 PADS 244287 0 PADT 1 187851 Service name error 0 0 AC system error 275 0 Generic error 0 0 Malformed packets 0 0 Unknown packets 0 0 Active PPPoE sessions: 54598 PacketType Sent Received PADI 0 242606 PADO 242606 0 PADR 0 242774 PADS 242774 0 PADT 0 185503 Service name error 0 0 AC system error 168 0 Generic error 0 0 Malformed packets 0 0 Unknown packets 0 0
show user-plane pppoe underlying-interfaces
Syntax
show user-plane pppoe underlying-interfaces <brief | detail | extensive> <lockout> <logical-interface-name> <up-name user-plane-name>
Description
Display information about PPPoE underlying interfaces.
Options
| brief | detail | extensive |
(Optional) Display the specified level of output. |
| lockout |
(Optional) Display summary information about the lockout condition and the lockout grace period for PPPoE clients on the PPPoE underlying interface. |
| logical-interface-name |
(Optional) Name of a PPPoE underlying logical interface. |
| up-name user-plane-name |
The BNG User Plane for which you want to view PPPoE underlying interfaces information. |
Required Privilege Level
view
Output Fields
Table 23 lists the output fields for the show user-plane
pppoe underlying-interfaces command. Output fields are listed in
the approximate order in which they appear.
|
Field Name |
Field Description |
Level of Output |
|---|---|---|
|
Underlying Interface |
Name of the PPPoE underlying logical interface. |
All levels |
|
Service Name Table |
Name of the service name table. |
All levels |
|
Dynamic Profile |
Name of the dynamic profile that was used to create this interface. If the interface was statically created, then the value is none. |
All levels |
|
Index |
Index number of the logical interface, which reflects its initialization sequence. |
|
|
State |
Origin of the logical interface: Static or Dynamic. Indicates whether the interface was statically or dynamically created. |
|
|
Operational States |
Fields in this block are actual operational values rather than simply the configured values. The operational values can be the result of RADIUS-initiated changes. |
|
|
Max Sessions |
Maximum number of PPPoE logical interfaces that can be activated on the underlying interface. When this number of logical interfaces has been established, all subsequent PPPoE Active Discovery Initiation (PADI) packets are dropped and all subsequent PPPoE Active Discovery Request (PADR) packets trigger PPPoE Active Discovery Session (PADS) error responses. |
|
|
Max Sessions VSA Ignore |
Whether the router is configured to ignore (clear) the PPPoE
maximum session value returned by RADIUS in the
Max-Clients-Per-Interface Juniper Networks VSA [26-143] and
restore the PPPoE maximum session value on the underlying
interface to the value configure with the
|
|
|
Active Sessions |
Number of active PPPoE sessions on the underlying interface. If a dynamic profile is listed, then it is the number of active PPPoE sessions on the underlying interface that are using this profile. The Active Sessions value must not exceed the Max Sessions value. |
|
|
Agent Circuit Identifier |
Whether the underlying interface is configured with the
Note:
The Agent Circuit Identifier field is replaced with the
Line Identity field when an ALI interface set is
configured with the |
|
|
|
Whether the underlying interface is configured with the
Note:
The Line Identity field is replaced with the ACI VLAN
field when an ACI interface set is configured with the
|
|
|
Duplicate Protection |
State of PPPoE duplicate protection: On or Off. When duplicate protection is configured for the underlying interface, a dynamic PPPoE logical interface cannot be activated when an existing active logical interface is present for the same PPPoE client. The uniqueness of the PPPoE client is determined by the client's MAC address. |
|
|
Short Cycle Protection |
State of PPPoE short cycle protection: mac-address, circuit-id, or Off. Enabling short cycle protection, also known as PPPoE lockout, on the PPPoE underlying interface temporarily prevents (locks out) a failed or short-lived (short-cycle) PPPoE subscriber session from reconnecting to the router for a default or configurable period of time. PPPoE client sessions are identified by their unique media access control (MAC) source address or agent circuit identifier (ACI) value. |
|
|
Direct Connect |
State of the configuration to ignore DSL Forum VSAs: On or Off. When configured, the router ignores any of these VSAs received from a directly connected CPE device on the interface. |
|
|
AC Name |
Name of the access concentrator. |
|
|
PacketType |
Number of packets sent and received during the PPPoE session, categorized by packet type and packet errors:
|
|
|
Lockout Time (sec) |
The PPPoE lockout time range, the number of PPPoE clients in lockout condition, and the number of PPPoE clients in a lockout grace period if Short Cycle Protection is enabled (On):
|
|
|
Client Address |
MAC source address of the PPPoE client. |
|
|
Current |
Current lockout time, in seconds; displays 0 (zero) if the PPPoE client is not undergoing lockout. |
|
|
Elapsed |
Time elapsed into the lockout period, in seconds; displays
|
|
|
Next |
Lockout time, in seconds, that the router uses for the next lockout event; displays a nonzero value if the PPPoE client is currently in a lockout grace period. |
|
Sample Output
- show user-plane pppoe underlying-interfaces brief up-name
- show user-plane pppoe underlying-interfaces detail up-name
- show user-plane pppoe underlying-interfaces extensive up-name
show user-plane pppoe underlying-interfaces brief up-name
user@host> show use-plane pppoe underlying-interfaces brief up-name test-up1 Underlying Interface Service Name Table Dynamic Profile ge-4/0/3.1 Premium None ge-4/0/3.2 None PppoeProfile
show user-plane pppoe underlying-interfaces detail up-name
user@host> show use-plane pppoe underlying-interfaces detail up-name test-up1ge-4/0/3.1 Index 73 Operational States: State: Static, Dynamic Profile: None, Max Sessions: 4000, Max Sessions VSA Ignore: Off, Active Sessions: 0, Service Name Table: Premium, Direct Connect: Off, AC Name: velorum, Duplicate Protection: On, Short Cycle Protection: Off ge-4/0/3.2 Index 78 Operational States: State: Dynamic, Dynamic Profile: PppoeProfile, Max Sessions: 500, Max Sessions VSA Ignore: Off, Active Sessions: 3, Service Name Table: None, Direct Connect: Off, AC Name: velorum, Duplicate Protection: On, Short Cycle Protection: Off
show user-plane pppoe underlying-interfaces extensive up-name
user@host> show use-plane pppoe underlying-interfaces extensive up-name test-up1 ge-4/0/3.1 Index 73ge-4/0/3.1 Index 73 Operational States: 1053 State: Static, Dynamic Profile: None, Max Sessions: 4000, Max Sessions VSA Ignore Off, Active Sessions: 0, Service Name Table: None, Direct Connect: Off, AC Name: velorum, Duplicate Protection: Off, Short Cycle Protection: Off PacketType Sent Received PADI 0 0 PADO 0 0 PADR 0 0 PADS 0 0 PADT 0 0 Service name error 0 0 AC system error 0 0 Generic error 0 0 Malformed packets 0 0 Unknown packets 0 0 ge-4/0/3.2 Index 78 Operational States: State: Dynamic, Dynamic Profile: PppoeProfile, Max Sessions: 4000, Max Sessions VSA Ignore: Off Active Sessions: 3, Service Name Table: None, Direct Connect: Off, AC Name: velorum, Duplicate Protection: Off, Short Cycle Protection: Off PacketType Sent Received PADI 0 5 PADO 5 0 PADR 0 5 PADS 4 0 PADT 0 1 Service name error 0 0 AC system error 0 0 Generic error 0 0 Malformed packets 0 0 Unknown packets 0 0f
show user-plane route
Syntax
show user-plane route <family family> <incomplete> <level (brief | detail)> <next-hop index> <prefix> <routing-instance name>> <route-type type> <rrt-index index> <summary> user-plane-name <up-name> user-plane-name
Description
Display information about how routes are mapped to specific enhanced subscriber
management interfaces. You can customize the output by including one or more
optional filters in the command. With the exception of the
summary option, all filter options can be combined in a
single command.
This command is only run on BNG User Planes.
Options
family family |
(Optional) Display route mapping information for the specified
protocol family: |
incomplete |
(Optional) Display route mapping information for incomplete routes that are missing elements required to add the routes to the routing table. |
level (brief | detail) |
(Optional) Display the specified level of output:
|
next-hop index |
(Optional) Display the next hop associated with the route entry with the specified next-hop index, in the range 1 through 65535. |
prefix address |
(Optional) Use the same prefix and prefix length as the subscriber host address. Output includes attributes that originate in the Famed-Route record of an upstream RADIUS server (Tag, Metric, Preference). |
route-type type |
(Optional) Display route mapping information for the specified route
type: |
routing-instance name |
(Optional) Display route mapping information for the specified routing-instance |
rrt-index index |
(Optional) Display mapping information for the specified routing
table index, in the range 0 through 65535. An
|
summary user-plane-name |
(Optional) Display summary information about the routes managed by enhanced subscriber management for the specified BNG User Plane. |
up-name user-plane-name |
The BNG User Plane for which to display information about the routes managed by enhanced subscriber management. |
Required Privilege Level
view
Output Fields
Table 24 lists the output fields for the show user-plane
route command. Output fields are listed in the approximate order in
which they appear.
|
Field Name |
Field Description |
Level of Output |
|---|---|---|
|
|
IPv4 or IPv6 address associated with the route entry. |
All levels |
|
|
IPv4 or IPv6 address associated with the route entry. |
All levels |
|
|
One of the following route types:
|
All levels |
|
|
Name of the enhanced subscriber management interface associated with the route entry. |
All levels |
|
|
Next-hop associated with the route entry. |
All levels |
|
|
Reflects the Tag attribute used in the RADIUS Framed-Route type record. |
All levels |
|
|
Reflects the Metric attribute used in the RADIUS Framed-Route type record. |
All levels |
|
|
Reflects the Preference attribute used in the RADIUS Framed-Route type record. |
All levels |
|
|
Value of the routing table index. A value of
|
|
|
|
Value of the interface index for the control plane. |
|
|
|
Value of the route object index. |
|
|
|
Used for internal accounting. |
|
|
Discard route count |
Number of discard routes. |
Summary |
|
Discard route gateway |
Number of gateway routes. |
Summary |
|
|
Used for internal accounting. |
|
|
|
Used for internal accounting. |
|
|
|
One of the following protocol families:
|
|
|
|
Name of the BNG User Plane. |
All levels |
|
|
The kernel routing table ID number. |
Summary |
|
|
The number of local routes. |
Summary |
|
|
The number of access routes. |
Summary |
|
|
The number of access internal routes. |
Summary |
|
|
The number of kernel routes. |
Summary |
|
|
The number of local routes that have not been fully installed. It is always 0 for the active RE for the BNG User Plane. It can be non-zero for the standby RE (representing a transient condition). |
Summary |
|
|
The number of access routes that have not been fully installed. It is always 0 for the active RE for the BNG User Plane. It can be non-zero for the standby RE (representing a transient condition). |
Summary |
|
|
The number of access-internal routes that have not been fully installed. It is always 0 for the active RE for the User Plane. It can be non-zero for the standby RE (representing a transient condition). |
Summary |
|
|
The number of kernel routes that have not been fully installed. It is always 0 for the active RE for the BNG User Plane. It can be non-zero for the standby RE (representing a transient condition). |
Summary |
|
|
The number of inflight routes that have not been fully installed. It is always 0 for the active RE for the BNG User Plane. It can be non-zero for the standby RE (representing a transient condition). |
Summary |
Sample Output
- show user-plane route up-name
- show user-plane route summary up-name up-exampl-1
- show user-plane route summary
- show user-plane route route-type discard
- show user-plane route prefix <address>
- show user-plane route family route-type rtt-index level brief
- show user-plane route family route-type rtt-index level detail
- show user-plane route family route-type rtt-index level brief
show user-plane route up-name
user@host> show user-plane route up-name up-example-1
Route: 193.0.21.0/32
Route Type: Access-internal
Interface: pp0.3221324082
Next-Hop index: 0
Route: 193.0.21.1/32
Route Type: Access-internal
Interface: pp0.3221324088
Next-Hop index: 0
Route: 193.0.21.2/32
Route Type: Access-internal
Interface: pp0.3221324092
Next-Hop index: 0
Route: 193.0.21.3/32
Route Type: Access-internal
Interface: pp0.3221324094
Next-Hop index: 0
show user-plane route summary up-name up-exampl-1
user@host> show user-plane route summary up-name up-example-1
UP Name: up-example-1
Routing-instance: default:default
Kernel rt-table id: 0
Family: AF_INET
Local route count: 1
Access route count: 0
Access internal route count: 31985
Kernel route count: 0
Dirty local route count: 0
Dirty access route count: 0
Dirty access internal route count: 0
Dirty kernel route count: 0
Dirty inflight route count: 0
show user-plane route summary
user@host> show user-plane route summary Routing-instance: default:default Kernel rt-table id: 0 Family: AF_INET Local route count: 0 Access route count: 4 Access internal route count: 604 Kernel route count: 0 Discard route count: 20 Gateway route count: 1 Dirty local route count: 0 Dirty access route count: 0 Dirty access internal route count: 0 Dirty kernel route count: 0 Dirty inflight route count: 0
show user-plane route route-type discard
user@host> show route route-type discard Route: 173.162.0.0/24 Route Type: Discard Tag: 33 Next-Hop index: 0 Route: 173.162.0.0/24 Route Type: Discard Tag: 33 Next-Hop index: 0 Route: 173.162.0.0/24 Route Type: Discard Tag: 33 Next-Hop index:
show user-plane route prefix <address>
rtt-index 0
user@host> show user-plane route prefix 10.10.0.1/32
Route: 10.10.0.1/32
Routing-instance: default:default
Kernel rt-table id : 0
Family: AF_INET
Route Type: Framed
Protocol Type: Unspecified
Interface: pp0.3221225491
Interface index: 26
Internal Interface index: 26
Route index: 20
Next-Hop: 684
Tag: 9999
Metric: 56
Preference: 10
Reference-count: 1
L2 Address: 00:00:5e:00:53:0b
Flags: 0x0
Dirty Flags: 0x0
show user-plane route family route-type rtt-index level brief
The following example displays abbreviated information about IPv6 access
routes in the default routing table (rtt-index 0) managed
by enhanced subscriber management.
user@host> show user-plane route family inet6 route-type access rtt-index 0 level brief
2001:db8::/64
Route Type: Access
Interface: pp0.3221225479, Next-hop:721
2001:db8:0:0:1::/64
Route Type: Access
Interface: pp0.3221225477, Next-hop:721
2001:db8:0:0:2::/64
Route Type: Access
Interface: pp0.3221225478, Next-hop:721
2001:db8:0:0:3::/64
Route Type: Access
Interface: pp0.3221225480, Next-hop:721
2001:db8:0:0:4::/64
Route Type: Access
Interface: pp0.3221225481, Next-hop:721
2001:db8:2002::/84
Route Type: Access
Interface: demux0.3221225492, Next-hop:721
2001:db8:0:0:5::/64
Route Type: Access
Interface: pp0.3221225487, Next-hop:721
2001:db8:0:0:6::/64
Route Type: Access
show user-plane route family route-type rtt-index level detail
The following example displays detailed information about IPv6 access routes
in the default routing table (rtt-index 0) managed by
enhanced subscriber management.
user@host> show user-plane route family inet6 route-type access rtt-index 0 level detail
2001:db8::/64
Route Type: Access
Interface: pp0.3221225479
Next-hop: 721
Rtt-index: 0
Bbe index: 9
Flow id: 1
Reference Count: 1
Dirty Flags: 0
Flags: 0x10082
Family: AF_INET6
2001:db8:0:0:1::/64
Route Type: Access
Interface: pp0.3221225477
Next-hop: 721
Rtt-index: 0
Bbe index: 9
Flow id: 1
Reference Count: 1
Dirty Flags: 0
Flags: 0x10082
Family: AF_INET6
2001:db8:0:0:2::/64
Route Type: Access
Interface: pp0.3221225478
Next-hop: 721
Rtt-index: 0
Bbe index: 9
Flow id: 1
Reference Count: 1
Dirty Flags: 0
Flags: 0x10082
Family: AF_INET6
2001:db8:0:0:3::/64
Route Type: Access
Interface: pp0.3221225480
Next-hop: 721
Rtt-index: 0
Bbe index: 9
Flow id: 1
Reference Count: 1
Dirty Flags: 0
Flags: 0x10082
Family: AF_INET6
show user-plane route family route-type rtt-index level brief
The following example displays abbreviated information about IPv6 access
routes in the default routing table (rtt-index 0) managed
by enhanced subscriber management.
user@host> show user-plane route family inet6 route-type access rtt-index 0 level brief
2001:db8::/64
Route Type: Access
Interface: pp0.3221225479, Next-hop:721
2001:db8:0:0:1::/64
Route Type: Access
Interface: pp0.3221225477, Next-hop:721
2001:db8:0:0:2::/64
Route Type: Access
Interface: pp0.3221225478, Next-hop:721
2001:db8:0:0:3::/64
Route Type: Access
Interface: pp0.3221225480, Next-hop:721
2001:db8:0:0:4::/64
Route Type: Access
Interface: pp0.3221225481, Next-hop:721
2001:db8:2002::/84
Route Type: Access
Interface: demux0.3221225492, Next-hop:721
2001:db8:0:0:5::/64
Route Type: Access
Interface: pp0.3221225487, Next-hop:721
2001:db8:0:0:6::/64
Route Type: Access
show user-plane routing-instances
Syntax
show user-plane routing instances up-name <bng-user-plane-name>
Description
Displays routing instances in use by a particular BNG User Plane.
Options
bng-user-plane |
The BNG User Plane for which you want to know the routing instance that are being used. |
Required Privilege Level
view
Output Fields
Table 24 lists the output fields for the show user-plane
routing-instances command. Output fields are listed in the
approximate order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
Name of the BNG User Plane. |
|
Routing Instance Name |
Name of the routing instance. |
|
|
The routing instance state:
|
Sample Output
show user-plane routing-instances
user@host> show user-plane routing-instances example-1 User-plane: example-1 Routing Instance Name State default connected RETAILER33 connected RETAILER0 connected
show user-plane statistics
Syntax
show user-plane statistics <all> <dhcp> <dvlan> <l2tp> <ppp> <pppoe> <up-name user-plane-name>
Description
Display statistics for the specified BNG User Plane. You can customize the output by including one or more optional filters in the command.
Options
| all |
(Optional) Display packet statistics for all protocols. |
| dhcp |
(Optional) Display DHCP packet statistics. |
| dvlan |
(Optional) Display DVLAN packet statistics. |
| l2tp |
(Optional) Display L2TP packet statistics. |
| ppp |
(Optional) Display PPP packet statistics. |
| pppoe |
(Optional) Display PPPoE packet statistics. |
| up-name user-plane-name |
The BNG User Plane for which you want to view packet statistics. |
Required Privilege Level
view
Output Fields
Table 26 lists the output fields for the show user-plan
statistics command. Output fields are listed in the approximate
order in which they appear.
|
Field Name |
Field Description |
|---|---|
|
|
The BNG User Plane for which the information is being displayed. |
|
|
Statistics for packets received. |
|
|
Statistics for packets sent. |
|
|
Statistics for visibility into packet drops from the queue. |
|
|
Includes connection packets, flow control, and messages and packets sent to and received from the daemon. |
|
|
Event Rate Analyzer discards. For DHCP and PPPoE in advanced subscriber management, ERA packet discard counts are included for Discover, Solicit, and PADI packets . |
|
|
Statistics for Layer 3 packets. |
|
|
PPPoE Active Discovery Initiation (PADI) packets. PADI is the first step in the PPPoE establishment protocol. |
|
|
PPPoE Active Discovery Request packets. |
|
|
Point-to-Point Protocol packets. |
|
|
Number of router solicitations sent or received. Router solicitations are sent to prompt all on-link routers to send it router advertisements. |
|
|
Number of router advertisements sent or received. |
Sample Output
show user-plane statistics up-name
user@host> show user-plane statistics up-name up-example-1
User-plane : up-example-1
I/O Statistics:
Rx Statistics
packets : 3059637
Tx Statistics
packets : 2837485
Layer 3 Statistics
Rx Statistics
packets : 0
Tx Statistics
packets : 0
show user-plane statistics pppoe up-name
user@host> show user-plane statistics pppoe up-name up-example-1
User-plane : up-example-1
I/O Statistics:
Rx Statistics
packets : 3059637
Tx Statistics
packets : 2837485
Layer 3 Statistics
Rx Statistics
packets : 0
Tx Statistics
packets : 0
PPPoE Statistics:
Rx Statistics
packets : 369141
padis : 32027
padrs : 32000
ppp packets : 241057