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.

    2. Configure enhanced IP network services.

  2. Enable enhanced subscriber management.
    1. Specify that you want to configure global services for the router.

    2. Enable enhanced subscriber management.

  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. An appropriate database size enables subscriber management to operate and scale optimally. In some circumstances, you must configure a maximum size to increase the amount of shared memory available to subscriber management. In other circumstances, we recommend that you allow the router to determine the appropriate size and that you do not configure a maximum.

    • For MX5, MX10, MX40, MX80, and MX104 routers, you must always configure the maximum size to be no more than 100MB, regardless of the which Junos OS release is running and regardless of Routing Engine RAM.

    • For MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003 routers, the decision whether to explicitly configure a maximum size and what that size is, depends on the Junos OS release and the amount of RAM in the Routing Engines. Table 1 lists conditions and the corresponding recommendations.

      Table 1: Configuration Database Size for MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003 Routers

      Junos OS Release

      Routing Engine RAM

      Recommendation

      Release 17.4R1 and earlier releases

      Release 18.1R1

      Any

      Configure maximum size to no more than 300MB.

      Release 17.4R2 and higher 17.4x releases

      Release 18.1R2 and higher releases

      Routing Engines have at least 32GB each

      Allow the router to determine the appropriate size. Do not configure a maximum size.

      Release 17.4R2 and higher 17.4x releases

      Release 18.1R2 and higher releases

      Routing Engines have less than 32GB each

      Configure maximum size to no more than 300MB.

  4. (Optional) Enable traffic-accounting and rate-monitoring for the given interface:
  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.

      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).

      Note

      To enable graceful restart:

    3. Configure commit operations to automatically synchronize the configuration between the master Routing Engine and the standby Routing Engine.

  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.

    2. Reboot the software.

Example

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

Note

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

Release History Table
Release
Description
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.