Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Subscriber Management and Services

  • Support for Wireless CUPS (MX10008)—Starting in Junos OS Release 23.2R1, we support wireless Control and User Plane Separation (CUPS) features on LC480 line cards in use on MX10008 platforms. This includes GRES and Anchor Packet Forwarding Engine redundancy support for 4G and 5G use cases.

    [See Multi-Access User Plane Overview.]

  • Support for Wireless CUPS User Plane Function (MX Series)—Starting in Junos OS Release 23.2R1, we support User Plane Function (UPF) features on MPC10 and LC9600 line cards for MX Series devices.

    [See Multi-Access User Plane Overview.]

  • Support for DHCP groups across dynamic VLANs on a physical interface (MX960 and MX10003 routers)—Starting in Junos OS Release 23.2R1, we introduce the interface-tag statement. The interface-tag statement supports mapping auto-configured dynamic VLAN subsets to different DHCP groups. Before this release, you could only map one DHCP group on a physical interface (IFD) that is supporting dynamic VLANs.

    For example, subscribers that connect to a broadband network gateway (BNG) have different DHCP requirements than subscribers that connect to the Access Gateway Function (AGF). By grouping BNG and AGF subscribers on different VLAN ranges, you can use the interface-tag statement to migrate subscribers from the BNG to the AGF.

    To use the interface-tag statement to map a group of dynamic VLANs to a DHCP group:

    • Configure the interface-tag in the dynamic profile on a VLAN demux interface.

      • set dynamic-profiles profile-name interfaces demux0 unit $junos-interface-unit interface-tag interface-tag-name

    • Configure the auto-sensed VLANs on the physical interface on the physical interface. Specify the dynamic profile and the VLAN range subset. The router determines the DHCP group from the VLAN range and dynamic profile.

    • Map the dynamic profile to the associated DHCP group by specifying the same interface-tag name.

      DHCP Relay

      • set forwarding-options dhcp-relay group name interface-tag interface-tag-name

      • set forwarding-options dhcp-relay dhcpv6 group name interface-tag interface-tag-name

      DHCP Local Server

      • set system services dhcp-local-server group sgroup interface-tag interface-tag-name

      • set system services dhcp-local-server dhcpv6 group sgroup interface-tag interface-tag-name

    [Seefiveqi-map Configuring Group-Specific DHCP Local Server Options, Configuring Group-Specific DHCP Relay Options, and Migrate Subscribers from BNG to AGF.]

  • Support to configure QoS parameters in the 5QI table (MX204, MX240, MX480, MX960, and MX10003 routers)—Starting in Junos OS Release 23.2R1, you can configure the Quality of Service (QoS) attributes for a 5G QoS identifier (5QI) value in the 5QI table. The Access and Mobility Function (AMF) sends N2 messages to the Access Gateway Function containing the 5QI value. The 5QI value corresponds to Junos CoS parameters. AGF inspects the N2 and N1 messages for 5QI and QoS Flow ID (QFI) values and matches those values to parameters in the 5QI table. AGF can then update data packets with an updated differentiated services code point (DSCP) in the payload to match the derived QoS parameters.

    You can set the following QoS attributes for a 5QI value in the 5QI table:

    • Differentiated Services code point (DSCP) value

    • DSCP value for the N3 interface

    • Forwarding class

    • Loss Priority

    To set the QoS attributes, use the set services agf fiveqi-map identifier upstream-rewrite statement.

    [See , upstream-rewrite, and CoS for Subscriber Access Overview.]

  • PCEF diameter enhancements for MX480 that include:

    • Support for PFE specific filter entries for protocols like ARP, BGP, ICMP pre-installed based on requirement.

    • Support for customization of Subscription-Id-Data in CCR, sourced from RADIUS server. External Subscription ID is activated by default.

    • Support for customization of Calling-Station-Id in RADIUS requests. To customize Calling-Station-Id in RADIUS requests, use the command set remote-circuit-id-format (postpend | prepend) under [edit access profile <profile-name> radius options] mode.

    • Usage monitoring through 3rd Generation Partnership Project (3GPP) attribute-value pairs (AVPs) defined as Gx for subscriber services using dynamic-profile configuration.

  • Subscriber management functionality on MX304—Starting in Junos OS Release 23.2R1, we provide the following support:

    • Basic and advanced class of service (CoS) and filters (IPv4 or dual stack) support for:

      • Dynamic Virtual Local Area Networks (DVLANs) with DHCP (Dynamic Host Configuration Protocol) subscribers

      • DVLAN with Point-to-Point Protocol (PPP) subscribers

      • DVLAN and Agent Circuit Identifier (ACI) with DHCP subscribers

      • DVLAN and ACI with PPP subscribers

      • Stacked DVLAN with DHCP subscribers

      • Stacked DVLAN with PPP subscribers

      • Pseudowire DVLAN with DHCP subscribers

      • Pseudowire DVLAN with PPP subscribers

    • DVLAN with L2TP Access Concentrator (LAC) (IPv4) basic and advanced CoS and filters

    • DVLAN with L2TP Network Server (LNS) (IPv4 and dual stack) basic CoS and filters

    • Advanced CoS and filters (IPv4 or dual stack) support for:

      • DHCP subscribers

      • PPP subscribers

    • L2TP tunnels

    • Subscriber services (customer solutions test scripts) processing

    • Scaling and performance for the following features:

      • DHCP subscribers with authenticated dynamic VLAN

      • DHCP subscribers with authenticated dynamic S-VLAN (Service-Virtual Local Area Network)

      • LNS subscribers

      • LAC subscribers

      • CoS service

      • Firewall service

    [See Features Supported on MX304.]