Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Junos OS Enhanced Subscriber Management

    Junos OS enhanced subscriber management is a next-generation broadband edge software architecture for wireline subscriber management. With enhanced subscriber management, you can take advantage of optimized scaling and performance for configuration and management of dynamic interfaces and services for subscriber management. It must be enabled to use dynamic profiles for creating and managing dynamic subscriber interfaces and services.

    Enhanced subscriber management is supported on all MX Series 3D Universal Edge Routers with Modular Port Concentrators (MPCs) installed. It is not supported for MS-DPCs. If the router has both MPC and MS-DPCs, a conflict between the MS-DPC and Enhanced Subscriber Management services can occur during ISSU that can result in an unscheduled shutdown of the device. To prevent this, do not run ISSU if the system has MS-DPCs installed, or only enable Enhanced Subscriber Management on device where no MS-DPCs are present.

    Before you begin:

    • Download and install Junos OS Release 15.1R3 or later.

      See Migration, Upgrade, and Downgrade Instructions in the Junos OS Release 15.1R3 Release Notes. You must reboot the router after the upgrade is validated and installed.

      Caution: Because unified in-service software upgrade (unified ISSU) is not supported for subscriber management when you upgrade from a release that does not support enhanced subscriber management (Junos OS Release 14.2 or earlier) to a release that does support enhanced subscriber management (15.1R4 and later), all subscriber sessions and subscriber state are lost after the upgrade.

    Note: Starting in Junos OS Release 17.4R1, when enhanced IP network services and enhanced subscriber management are enabled and a Routing Engine in the system has at least 32 GB of RAM, subscriber management daemons on that Routing Engine run in 64-bit mode. For consistent operation, all Routing Engines in the system must have the same amount of memory.

    To configure Junos OS enhanced subscriber management for the first time:

    1. Configure enhanced IP network services on the router.
      1. Specify that you want to configure chassis properties for the router.
        user@host# edit chassis
      2. Configure enhanced IP network services.
        [edit chassis]
        user@host# set network-services enhanced-ip
    2. Enable enhanced subscriber management.
      1. Specify that you want to configure global services for the router.
        user@host# edit system services
      2. Enable enhanced subscriber management.
        [edit system services]
    3. Increase the amount of system shared memory available for enhanced subscriber management by limiting the maximum size of the configuration database.

      JUNOS OS processes map shared memory into their process space. For example, on MX240 through MX10003 routers, processes can map up to 1GB of shared memory. Enhanced subscriber management processes contend for shared memory with the JUNOS OS configuration database. By default, the configuration database tries to reserve 80 percent of the shared memory map, leaving insufficient space for subscriber management to function. The majority of configurations require much less than 300MB of mapped space. To allow subscriber management to operate and scale, adjust the JUNOS OS configuration database shared memory allocation as follows to increase the amount of shared memory available to subscriber management:

      • No more than 300 MB for MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003 routers.
      • No more than 100 MB for MX5, MX10, MX40, MX80, and MX104 routers.
      user@host# set system configuration-database max-db-size 300M
    4. (Optional) Enable traffic-accounting and rate-monitoring for the given interface:
      [edit dynamic-profiles profile-name interfaces unit “$junos-interface-unit”]
      user@host# set actual-transit-statistics
    5. (Optional) Enable graceful Routing Engine switchover (GRES) and nonstop active routing (NSR).

      Note: For MX Series routers using enhanced subscriber management, the new backup Routing Engine (the former master Routing Engine) will reboot when a graceful Routing Engine switchover is performed. This cold restart resynchronizes the backup Routing Engine state with that of the new master Routing Engine, preventing discrepancies in state that might have occurred during the switchover.

      1. Enable GRES.
        [edit chassis redundancy]
        user@host# set graceful-switchover

        Note: When GRES is enabled, you can either configure NSR or graceful restart. If you configure both, then committing the configuration fails.

      2. Enable NSR (recommended if you enable GRES).
        [edit routing-options]
        user@host# set nonstop-routing

        Note: To enable graceful restart:

        [edit routing-options]
        user@host# set graceful-restart
      3. Configure commit operations to automatically synchronize the configuration between the master Routing Engine and the standby Routing Engine.
        [edit system]
        user@host# set commit synchronize
    6. Commit the configuration.

      After you commit the configuration, the software prompts you to initiate a system reboot.

    7. Reboot the router software to enable enhanced subscriber management.
      1. Access operational mode.
        [edit system]
        user@host# exit
      2. Reboot the software.
        user@host> request system reboot


    The following example shows a typical configuration to enable enhanced subscriber management.

    chassis {
    network-services {
    redundancy {
    routing-options {
    system {
    commit synchronize;
    configuration-database {
    max-db-size 300M;
    services {
    subscriber-management {

    Note: If you have configured graceful-restart, then the following statement will be displayed in the example instead of nonstop-routing:

    routing-options {

    Release History Table

    Starting in Junos OS Release 17.4R1, when enhanced IP network services and enhanced subscriber management are enabled and a Routing Engine in the system has at least 32 GB of RAM, subscriber management daemons on that Routing Engine run in 64-bit mode.

    Modified: 2018-03-08