Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Subscriber Management and Services

  • Advanced services support for static subscribers (MX240, MX480, and MX960 with MS-MPCs)—Starting in Junos OS Release 21.2R1, you can configure the static-subscriber-application statement at the [edit services service-set-name service-set-options] hierarchy level to attach advanced services, such as deep packet inspection (DPI), to the static subscriber. [See Configuring Subscriber-Aware and Application-Aware Traffic Treatment Overview and service-set (Subscriber-Aware).]

  • Support for Broadband Edge subscriber management and services (MX10008 and MX10016 with MX10K-LC2101 and MX10K-LC480)—Starting in Junos OS Release 21.2R1, we support subscriber management and services. The line cards also support subscriber access, subscriber authentication, service activation, and deactivation.

    [See Subscriber Management Overview.]

  • Junos Multi-Access User Plane support for 5G user plane function (MX204, MX240, MX480, MX960, and MX10003)—Starting in Junos OS Release 21.2R1, Junos Multi-Access User Plane supports routers functioning as user plane functions (UPFs) in accordance with 3GPP Release 15 CUPS architecture. This provides high-throughput 5G fixed and mobile wireless service in non-standalone (NSA) mode. This includes support for the following:

    • N3, N4, N6, and N9 interface support
    • Roaming through the N9 interface
    • GPRS tunneling protocol, user plane (GTP-U) tunneling to the control plane
    • QoS Flow ID (QFI) support for 5G QoS flows

    [See Junos Multi-Access User Plane Overview.]

  • Support for PWHT with VC type 11 (MX Series routers with MPC7E, MPC10E, MPC9E, or MPC11E line cards)—Starting in Junos OS Release 21.2R1, you can configure a pseudowire headend termination (PWHT) interface on a service PE router with ethernet-tcc encapsulation on the interface. With this feature, the service PE router does not have to support TDM/SONET/SDH-encapsulated traffic coming from access-side customers. The IP-based point-to-point pseudowire—which is an LDP-signaled FEC 128 (virtual circuit (VC) type 11)—connects the service PE router to the access device that is connected to the access CE router.

    You configure the pseudowire to terminate into a Layer 3 VPN instance or a global IP table. The service PE router uses ARP mediation to resolve Layer 2 addresses when different resolution protocols are used on either end of a circuit.

    The feature supports IPv4 and IPv6 payloads, and unicast and multicast traffic.

    [See Configuring a PWHT with VC 11 Type Support.]