Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Subscriber Management and Services

  • BNG subscriber redundancy on aggregated Ethernet interfaces with disabled Packet Forwarding Engines (MX304, MX960, and MX10004)—You can enhance network reliability for broadband network gateway (BNG) subscribers by maintaining active sessions over aggregated Ethernet interfaces, ensuring service continuity even if a Packet Forwarding Engine fails. This feature supports DHCP, PPPoE, and L2TP and remains operational as long as one member link is active. It is compatible with the following configurations:
    • Active/Active mode
    • Active/Standby
    • Dynamic VLAN
    • Static VLAN.
    This redundancy improves user experience by minimizing service disruptions and ensuring uninterrupted connectivity. Disabling a Packet Forwarding Engine on a Flexible PIC Concentrator (FPC) does not affect other Packet Forwarding Engines on that FPC or other FPCs.. If you disable a Packet Forwarding Engine with an aggregated Ethernet member link, link aggregation group (LAG) or the aggregated Ethernet infrastructure redistributes the traffic on other member links.

    [See Broadband Network Gateway (BNG) Subscriber Redundancy on Aggregated Ethernet (AE) Interfaces with Disabled PFEs.]

  • Wireless CUPS mobile edge support (MX240, MX304, MX480, and MX960)—You can use the LC4800 and LC9600 line cards for the following non-anchor link configurations in the devices with user plane function (UPF) configuration:

    • N3 mobile-edge: Access-facing side to carry and steer uplink traffic to the UPF anchor card

    • N4 mobile-edge: Exchange tunneled traffic in addition to PFCP control traffic between the CPF and UPF

    • N6 mobile-edge: Core-facing side to carry and steer downlink traffic to the anchor card on the UPF

    • N9 mobile-edge: Uplink or downlink for GPRS tunneling protocol, user plane (GTP-U) tunnel switching between the I-UPF and A-UPF

    [See Junos Multi-Access User Plane Overview and MX Series Router as Junos Multi-Access User Plane.]

  • L2-BSA service on new-generation line cards (MX304-LMIC16 on MX304, MPC10E-10C and MPC10E-15C on MX960, MX10004, MX10008, and MX10016) —Support for Layer-2 Bit Stream Access (L2-BSA) service on advanced forwarding toolkit (AFT)-based line cards, MX304-LMIC16 on MX304, and MPC trio based line cards MPC10E-10C and MPC10E-15C on MX960, MX10004, MX10008, and MX10016. This includes support for:

    • Inline L2-BSA.
    • Out-of-Band L2-BSA
    • Bring up of L2BSA subscribers
    • Bring down of L2BSA subscribers
    • Upstream packet flow
    • Downstream packet flow
    • Service providers can now provide 100-Mbps domain-specific language (DSL) speed VDSL2 with L2-BSA service for network service provider (NSP) partners.

    [See Broadband Subscribers Access Network Overview.]

  • Support for PPPoE subscriber over softGRE tunnels on pseudowire interfaces over RLT(MX240, MX480, and MX960)—You can extend subscriber services over softGRE tunnels to pseudowire subscriber interface over redundant logical tunnel (RLT) interfaces for Wi-Fi access gateway (WAG) deployments in a PPPoE dual-stack network. This feature enhances forwarding-path redundancy and supports active-active or active-backup modes. You can use VLAN-tagged or untagged Ethernet frames. Support is limited to line cards from MPC2 to MPC9.

    [See Wi-Fi Access Gateways.]

  • Load balancing based on tunnel identified in L2TPv3 header (MX204, MX240, MX304 MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—These devices can load-balance packets based on the tunnel they belong to. When Layer 2 Tunneling Protocol version 3 (L2TPv3) packets are encapsulated in IP tunnels, the packet header includes a tunnel ID and a session ID that distinguishes the traffic flow that packet belongs to. The device uses this information in the L2TPv3 packet headers when performing the hash computations for load balancing. This feature enables the device to better manage traffic flows in L2TPv3-over-IP tunnels.

    To enable and disable L2TPv3-header based load balancing, use the l2tp-tunnel-session-identifier statement at the [edit enhanced-hash-key family family] hierarchy, where the family can be inet or inet6.

    [See l2tp-tunnel-session-identifier and Layer 2 Tunneling Protocol (L2TP).]

  • N+1 (DHCP Server and Relay) subscriber redundancy on BNG using Packet Forwarding Engine (MX304, MX480, MX960, MX10004, and MX10008)

    —Optimize resource usage and defer full-service traffic handling until failover occurs, thus supporting higher subscriber density. This feature supports Packet Forwarding Engine over-subscription using pseudowire interfaces (MPLS PWHT and EVPN VPWS PWHT) across multiple chassis for access and DHCP in relay mode with external server addresses and in local server mode with locally assigned IP addresses. The backup Packet Forwarding Engine transitions from basic forwarding to full service during failover. The MPC7 and LC2103 line cards act as secondary line cards.

    Use the service-activation-on-failover mode to enable this feature.

    Use the set system services subscriber-management redundancy group <group-name> interface <interface-name> standby-mode [hot-standby | service-activation-on-failover]; command.

    Enable one secondary device to back up multiple primary devices.

    [See N+1 Redundancy Support for BNG.]

  • Support for creating access-line-identifier (ALI) based dynamic VLANs using unique source MAC Address for PPPoE Subscribers only (MX Series Routers)—Service Provider deployments with multi-service access nodes (MSANs) that do not support agent circuit identifier (ACI) or agent remote identifier (ARI) insertion in PPPoE control packets can create ALI based dynamic VLANs using a single network-wide unique MAC address assigned to each household or access line.

    Use the accept-no-ids mac address option to trigger ALI based dynamic VLAN creation based on source MAC address.

    The following CLI show command outputs are updated:

    show subscribers detail

    show subscribers extensive

    show subscribers aci-interface-set

    show interface interface-set detail

    show pppoe interface-sets

    show interfaces

    show pppoe underlying-interfaces

    show pppoe lockout

    [See Access-Line-Identifier-Based Dynamic VLANs Overview.]

  • Support for static IPv4 subscribers over statically configured soft-GRE tunnels (MX240, MX480, MX960 with MPC5 and MPC7 line cards)—Service Providers using Fixed Wireless LAN (WLAN) to provide network access to subscribers can now provision static IPv4 subscribers wherein IP address of the Customer Premises Equipment (CPE) router is statically configured on both the CPE and the Broadband Network Gateway (BNG) and the data is transmitted over statically configured soft-GRE tunnels. Control plane protocols such as PPPoE or DHCP do not run on the CPE to provision the CPE IP address. The soft-GRE tunnel is brought up by the configuration and will stay up as long as the configuration is present on the router. The static subscriber requires the underlying soft-GRE tunnel to be present before it comes up. The static subscriber can access all BNG services including policers, Class of Service (CoS), accounting and more, based on the configuration. A static tunnel configuration must be defined under the set services soft-gre gre-group hierarchy with a tunnel name and remote address. These subscribers are associated with statically configured demux1 logical interfaces with IPv4 prefixes, defined under the set system services static-subscribers hierarchy.

    [See Static Subscribers Over Statically Configured Soft-GRE Tunnels.]