- play_arrow Overview
- play_arrow Use Juniper BNG CUPS
- Use Juniper BNG CUPS with Multiple Geographical Redundancy
- Use Dynamic Address Pools in Juniper BNG CUPS
- Juniper BNG CUPS High Availability
- Use Juniper BNG CUPS Subscriber Groups
- Use BNG User Plane Maintenance
- Use Juniper BNG CUPS Smart Session Load Balancing
- Use Juniper BNG CUPS for Subscriber Steering
- Use Juniper BNG CUPS Multicast
- Use Juniper BNG CUPS Lawful Intercept
- Use Juniper BNG CUPS Captive Portal and Content Delivery Services
- Configure Agent Circuit Identifier and IFL Sets in Juniper BNG CUPS
- Understanding DVLAN (Single/Dual tag) for Subscriber Services Scaling (Junos Evolved for ACX7100-48L, ACX7332, and ACX7348 Devices)
- How to Use the Juniper BNG CUPS Controller Utility Commands
- Troubleshooting and Monitoring Juniper BNG CUPS
- play_arrow Juniper BNG CUPS Controller CLI Configuration Statements
- play_arrow Juniper BNG CUPS Controller CLI Operational Statements
- play_arrow Juniper BNG User Plane CLI Configuration Statements
- Juniper BNG User Plane CLI Configuration Statements
- auto-configure
- captive-portal-content-delivery-profile (Services)
- dynamic-profile (Stacked VLAN)
- flexible-vlan-tagging (Interfaces)
- hierarchical-scheduler
- ranges (Dynamic Stacked VLAN)
- service-set (Dynamic Service Sets)
- service-set-options
- services (Captive Portal Content Delivery)
- stacked-vlan-tagging
show system subscriber-management summary
Output Fields
Table 1 lists the output fields for the show system subscriber-management summary command. Output fields are listed in the approximate order in which they appear.
Field Name | Field Description |
|---|---|
| State of graceful Routing Engine switchover (GRES):
(Enhanced subscriber management for MX Series routers) The name of this field is |
| State of the Routing Engine:
|
| State of the subscriber management database:
|
| (Enhanced subscriber management for MX Series routers) State of the standby Routing Engine:
|
| Reason why both Routing Engines are disconnected when there is a DRAM mismatch.
|
| State of unified ISSU chassis daemon:
|
| State of unified ISSU aggregate daemon:
|
| Amount of time, in seconds, requested by a daemon to perform cleanup. If multiple daemons request time, the displayed value is the highest wait time requested by a daemon. |
Sample Output
- show system subscriber-management summary
- show system subscriber-management summary (Enhanced Subscriber Management)
- show system subscriber-management summary (DRAM Size Mismatch Error)
show system subscriber-management summary
user@host> show system subscriber-management summary
General:
Graceful Restart Enabled
Mastership Master
Database Available
Chassisd ISSU State DAEMON_ISSU_PREPARE
ISSU State PREPARE
ISSU Wait 198
show system subscriber-management summary (Enhanced Subscriber Management)
user@host> show system subscriber-management summary
General:
Graceful Switchover Enabled
Mastership Master
Database Available
Standby Resync (75%)
Chassisd ISSU State IDLE
ISSU State IDLE
ISSU Wait 0
show system subscriber-management summary (DRAM Size Mismatch Error)
user@host> show system subscriber-management summary
General:
Graceful Restart Enabled
Mastership Master
Database Available
Standby Disconnected
<emphasis> Disconnection Reason Master/Standy RE DRAM Size Mismatch</emphasis
>
Chassisd ISSU State IDLE
ISSU State IDLE
ISSU Wait 0