Subscriber Management and Services

Session scale configurations for wireless CUPS (MX Series)—Starting in Junos OS Release 23.4R1, you can select the session scaling profile for your specific configuration. The session scaling profile determines how much memory is allocated for your user sessions in wireless control and user plane separation (CUPS). If you don't select a session scale, Junos OS uses the maximum available scale size for your device.

When the number of sessions reaches 80%, 90%, and 100% of the active scaling profile, Junos OS sends telemetry and ERRMSG notifications to you. At 100% usage, Junos OS rejects new sessions..

[See Session Maintenance and Optimization].

Session maintenance support for wireless CUPS (MX Series)—Starting in Junos OS Release 23.4R1, you can view session entries from the internal table with the transient-sessions filter. This filter enables you to view all sessions and session IDs that are in a transient state. If a session stays in a transient state for a longer duration of several minutes, you can consider it a potentially stuck session.

You can view session summaries in both 5-minute and hourly increments.

You can also manually clear sessions by the session IDs. This action enables you to remove any subscriber sessions that get stuck in any state.

Junos OS deletes exact routes when the last session using that route is deleted. Junos OS will not advertise the deleted routes, and the routes aren't visible to other devices and Junos OS users.

[See Session Maintenance and Optimization].

Peer group routing instance support for wireless CUPS—Starting in Junos OS Release 23.4R1, you must designate a routing instance in Junos OS for each peer group on the same user plane function (UPF). Doing this isolates control traffic when more than one subscriber management function (SMF) terminates on the same UPF.

[See Session Maintenance and Optimization].

• Customization of Subscription-Id-Data attribute-value pair (AVP) in Credit-Control Request (CCR), sourced from the RADIUS server. The external subscription ID is activated by default.

• Customization of Calling-Station-Id in RADIUS requests. To customize Calling-Station-Id in RADIUS requests, configure the command remote-circuit-id-format (postpend | prepend) under [edit access profile <profile-name> radius options]hierarchy level.

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

  [See Understanding Junos Subscriber Aware Policy and Charging Enforcement Function (PCEF) and Configuring Diameter AVPs for Gx Applications.]

Support for one-to-many SCTP associations (MX204, MX240, MX480, MX960, and MX10003)—Starting in Junos OS Release 23.4R1, Junos OS supports a one-to-many style SCTP endpoint on the Access Gateway Function (AGF).

[See SCTP.]

Broadband edge static framed-route for subscriber management (MX Series)—Starting in Junos OS Release 23.4R1, you can now set up static subscriber IP addresses for multiple hosts on a site as follows:

• Enable, disable, add, update, or delete static framed routes when subscribers are not up and attach the configured static framed route when a subscriber logs in. Static framed routes are supported for IPv4 only.
• Use the set routing-instances routing-instance routing-options access route ip command to configure and commit routes to the routing table. The routes are hidden, until the configured subscriber IP comes up.
• Use the static-framed-route command at [edit system services subscriber-management] hierarchy level to configure the static framed-route on the Broadband Network Gateway (BNG) towards a specific subscriber. You can now use the RADIUS server only for authentication purposes.

[See static-framed-route, access (Static Framed Routes), RADIUS-Initiated Subscriber Secure Policy Overview, and Example: Configuring HTTP Redirect Services Using a Next-Hop Method and Attaching It to a Static Interface.]