Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Subscriber Management and Services

  • Resiliency support for PPPoE/DHCP/L2TP subscribers on Packet Forwarding Engine-disable (MX960 and MX10004)—Ensure resiliency of subscriber services when a Packet Forwarding Engine is disabled. Currently this feature is supported until MPC7(EA) based line cards. Packet Forwarding Engines may become non-functional due to various errors including Error Correcting Code (ECC) errors, parity errors, or timeout issues, resulting its memory being invalidated.

    When a PFE in a line card is disabled and if at least one aggregated Ethernet link is present on the active PFE:

    • There is no impact to the existing subscriber functionality.

    • New subscriber login is seamless.

    The feature support includes:

    • Subscriber operations for DHCP, PPPoE, and L2TP, remain operational if there is at least one member link of the Aggregated Ethernet present on the active PFE.

    • Traffic redistribution .

    • Session continuity.

    • Subscriber stability.

    • Mode support

    • VLAN compatibility.

    • Redundancy and fault tolerance.

  • Chassis-based DHCP redundancy (MX480)—We support 1:1 redundancy for active lease queries below the limit of quantification (BLQ). This feature enhances reliability by providing redundancy for non-participating underlying subscriber interfaces, regardless of topology discovery. You can exclude interfaces without topology discovery. Use this feature on subscriber stacks and DHCP configurations and BBE and non-BBE DHCP configurations in the following scenarios:
    • Subscriber management "Enabled" and "Disabled" modes.
    • IP Demux and IP Demux Lite.
    • Dual-stack and dual-stack single-session modes.
    • Pseudowire access model PS Interfaces (L2 Circuit, EVPN VPWS, and L2VPN).
    • VRRP access model for gigabit Ethernet, 10Gb Ethernet, and aggregated Ethernet interfaces.
    • Non-default routing instances.
    • DHCP relay and DHCP servers.

    [ See M:N Subscriber Service Redundancy on DHCP Server, active-leasequery (DHCP Server), active-leasequery (DHCP Relay agent), and exclude-interface.]

  • Support for ANCP on AFT line cards (MX304)—

    This feature supports 15 non-Juniper and 14 Juniper-specific vendor-specific attributes (VSAs). Use the new RADIUS VSA for Layer-2 VLAN dynamic profile management. You can use the new Junos OS variable, $junos-inner-vlan-tag-protocol-id, to set VLAN map identifiers through RADIUS server or default configuration values.

    [See VSAs Supported by the AAA Service Framework, Junos OS Predefined Variables That Correspond to RADIUS Attributes and VSAs, access-line (Access-Line Rate Adjustment), and show-ancp-subscriber.]

    We provide support for border network gateway (BNG) for cascading DSLAM deployments including four QoS scheduler levels for residential subscribers. Passive Optical Network (PON) access technologies with broadband internet service models, Copper to the Business (CuTTB), and Fiber to the Business (FTTB).

    [See DSLAM Deployments Over Bonded Channels.]

    MX Series routers configured as L2TP network servers (LNSs) can process detailed subscriber access line information from L2TP access concentrators (LACs), with more accurate CoS shaping. You can detect and autogenerate logical interface sets with expanded traffic rate adjustments for DSL access lines. Use ANCP traffic control and new DSL types for access. [See Layer 2 forwarding when running unified ISSU on AFT-based line cards.]

  • Packet triggered recovery for static VLAN subscribers (MX240, MX304, MX480, MX960, MX2010, MX2020, MX10004, and MX10008)—We support packet triggered functionality based on the line card on the MX304 and other MX Series devices with MPC10 (ZT ASIC) and MX10K-LC9600 (YT ASIC) line cards.

    The packet triggered feature supports static IP assigned subscribers with IPv4 and IPv6 addresses regardless of the VLAN availability. This feature also supports:

    • One IP Demux connection per IPv4 or IPv6 address.
    • Packet triggered subscribers using authentication and service selection by using RADIUS server and Session and Resource Control (SRC) network.
    • CoS at subscriber level.
    • Throttling mechanism to mitigate DOS-like attack.
    • Removal of IP demux interface when no activity is seen for certain configurable duration.

      Enable subscriber management service for packet triggered configuration on an underlying interface by using the enable force command under [edit system services hierarchy] or the set system services subscriber-management enable force command.

      [See BNG Redundancy for DHCP Subscribers Using Packet Triggered Based Recovery and enable (Enhanced Subscriber Management).]

  • IPoE DHCP packet triggered recovery for BNG (MX480, MX960, and MX2020)—Use IPoE DHCP packet-triggered recovery to automatically update IP configurations in DHCP networks. When a data packet from a client with a pre-assigned IP is received, the system creates an IP demultiplexing interface (IP demux IFL).The routing engine authenticates the subscriber with an authentication server, applying requested services such as volume accounting, firewall filters, or CoS. The feature supports failover detection, subscriber creation after failover, static VLAN support for IP demux interfaces (IFL), IPv4 and IPv6 addresses, auto-clear timeout for dynamic IP subscribers, and DHCP recovery after failover. It ensures reliable service for dynamic IP and DHCP subscribers.

    This feature supports stateless border network gateway (BNG) redundancy for LAG (an active backup model) and pseudowire for L2VPN scenario, L2 Circuit based on IP/MPLS PWHT scenario, and EVPN-VPWS access network topologies.

    Use the command auto-configure session-timeout<seconds> under family [inet | inet6] hierarchy to configure the auto clear timeout functionality on the Active Dynamic IP subscriber.

    Remove Dynamic IP subscriber when DHCP renew or re-connect happens from the same subscriber or customer premises equipment (CPE).

    [See BNG Redundancy for DHCP Subscribers Using Packet Triggered Based Recovery and session-timeout.]

  • Load-based throttling for AFT-based line cards (MX10004 and MX10008)— Use this feature enabled by default for the advanced forwarding toolkit (AFT)-based line card MX10K-LC9600 on the MX10004 and the MX10008, to prevent saturation of line card processing capacity, reduce programming delays, and improve efficiency. The Packet Forwarding Engine supports multithreading and guides the Routing Engine to control packet management and load balancing. This feature is supported for integrated and disaggregated border network gateway (BNG) modes, on the following interface types:

    • Gigabit Ethernet/Line Termination interface for a single and multiple AFT cards.

    • Aggregated Ethernet/Remote Link Termination interface on

    • Aggregated Ethernet/Remote Link Termination interface with non-AFT cards.

    Use the no-load-throttle command under [edit] system services resource-monitor hierarchy to disable load-based throttling on AFT-based line cards. [ See Load based throttling for AFT based linecards on MX10004 and MX10008 and no-load-throttle.]

  • Subscriber management redundancy for Packet Forwarding Engine during graceful OIR (MX304-LMIC)—Use subscriber management redundancy on the Packet Forwarding Engine for seamless online insertion and removal (OIR). The system retains the subscribers and flows when an alternate Packet Forwarding Engine provides redundancy. DHCP subscribers remain active even if the Packet Forwarding Engine goes offline, and their functionalities resume when the LMIC is back online. You can cache subscriber accounting statistics during offline periods to ensure accurate values across offline-online transitions. You can clear interface statistics when the Packet Forwarding Engine goes offline.

    [See Subscriber management redundancy for Packet Forwarding Engine during graceful OIR.]