close

keyboard_arrow_left

Table of Contents Expand all

play_arrow AAA for Subscriber Management
play_arrow DHCP and DHCPv6 for Subscriber Management
- play_arrow DHCP for Subscriber Management
play_arrow IPv6 for Subscriber Management
- play_arrow IPv6 for Subscriber Management
play_arrow DHCPv6 for Subscriber Management
play_arrow Packet Triggered Subscriber Services
- play_arrow Packet Triggered Subscriber Services
  - IP Demultiplexing Interfaces on Packet-Triggered Subscriber Services
play_arrow Address-Assignment Pools for Subscriber Management
- play_arrow Address-Assignment Pools for Subscriber Management
  - Address-Assignment Pools for Subscriber Management
play_arrow DNS Addresses for Subscriber Management
- play_arrow DNS Addresses for Subscriber Management
  - DNS Name Server Addresses for Subscriber Management
play_arrow M:N Subscriber Redundancy
- play_arrow M:N Subscriber Redundancy
play_arrow Access Node Control Protocol and the ANCP Agent for Subscriber Services
- play_arrow Access Node Control Protocol and the ANCP Agent for Subscriber Services
play_arrow Diameter Base Protocol and its Applications
- play_arrow Diameter Base Protocol and its Applications
play_arrow Configuration Statements and Operational Commands

list Table of Contents

English

IP Demultiplexing Interfaces on Packet-Triggered Subscriber Services

date_range 23-Dec-24

arrow_backward

arrow_forward

Read this topic to know about the packet triggered subscribers feature available in Junos and how to configure it. Packet triggered subscribers feature creates IP demultiplexing interfaces (IP demux IFL) on receiving a data packet from clients with preassigned IP address.

IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview

Packet triggered subscribers feature creates IP demultiplexing interfaces (IP demux IFL) on receiving a data packet from clients with preassigned IP address. On receiving the first packet, the control plane checks the IP address. If the source IP address matches one of the configured IP address ranges, the subscriber is authenticated with authenticating server. On successful authentication, the IP demux IFL is created using the dynamic profile specified in the CLI. The IP demux IFL adds the framed route and demux source for subscriber using the mask passed by the authenticating server. If the mask is not sent by the authenticating server, access and demux routes are installed using the mask specified in the CLI.

For residential IPv4 subscribers, all traffic from single household typically has same source IPv4 address. Hence, for every household only one IP demux IFL with a single IPv4 address is created. For business IPv4 subscribers, multiple IPv4 addresses may be assigned using framed-routes, resulting in one IP demux IFL representing multiple IPv4 addresses. For IPv6, the source address of traffic coming from same household or business is different as each device has a separate IPv6 address. The most optimal representation of a household or business in this case consists of one IP demux IFL with an IPv6 prefix, representing all IPv6 addresses in the household/business.

Note:

During IP demux IFL creation if the authentication fails, the IP demux IFL is still created but such IP demux IFL cannot forward any traffic. Any received traffic for the associated subscriber is dropped. All such rejected IP demux IFLs remains in configured state and is referred as configured subscribers. Creating IP demux IFL even if the authentication fails will avoid thrashing as subsequent packets will be dropped on the PFE and will not be punted to the RE. All subscribers in ‘Configured’ state will be periodically removed. Once these subscribers are removed any new packets received from the same source will get punted to the RE.

Note:

Packet-Triggered Subscriber support requires that the MAC address of the connected device remain unchanged for the duration of the subscriber session. If the MAC address changes for a packet-triggered subscriber after the subscriber has logged in and the session is up, the subscriber will not be able to connect from the new device with the same IP address. You can avoid this by setting a period during which the session is monitored for subscriber activity. Use the client-idle-timeout option at the [edit access profile profile-name session-options ] hierarchy level. When the timeout expires, the subscriber is gracefully logged out. The subscriber can then successfully log in from the second device. See Configure Subscriber Session Timeout Options.

Benefits of IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services

Allows subscriber management and dynamic subscriber interface configuration in cases where devices in the home or business already have IPv4/IPv6 addresses assigned via other means, for example, statically assigned, or via a Cable Modem Termination System (CMTS).
Supports packet triggered subscribers using authentication and service selection by RADIUS server and allows a maximum of 16 IPv4 and 16 IPv6 address ranges per underlying IFL.
Allows the authenticating server to pass in the dynamic-profile to use. When the authenticating server passes these values, they take precedence over values configured through CLI.
Provides throttling mechanism to mitigate DoS-like attack and limit the rate of exception packets sent to RE for IP demux authentication and creation. The throttling mechanism uses the existing DDoS mechanism.
See Demultiplexing Interface Overview

Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles

You can configure the packet triggered subscribers for demux interfaces for both IPv4 and IPv6 addresses. The packet triggered subscribers feature creates IP demux IFL on receiving a data packet from clients with preassigned IP address. Once the IP demux IFL is created framed route and demux source are added for subscriber using the mask passed by the authenticating server.

To enable the packet triggered subscribers feature, configure the demux options in a dynamic profile. Dynamic profiles enable you to dynamically apply configured values to the dynamic interfaces, making them easier to manage.

Before you begin:

Configure the dynamic profile.

See Configuring a Basic Dynamic Profile.

After you configure the dynamic profile, configure the packet triggered subscribers interfaces beginning with the demux interface:

Specify that you want to configure the demux interface.

content_copy zoom_out_map
[edit interfaces interface-name  unit unit-number]
user@host#  edit demux 

Configure the family for the demux interfaces.
1. Specify that you want to configure the family.
  For IPv4:
  [edit interfaces interface-name unit unit-number demux] user@host# edit inet
  For IPv6:
  [edit interfaces interface-name unit unit-number] user@host# edit inet6
  Note:
  The remaining steps all show family inet, but are the same for either family.

Specify the demux address type to be based on the source address.

content_copy zoom_out_map
[edit interfaces interface-name  unit unit-number inet]
user@host# set address source

Configure the auto-configure details for the family.

content_copy zoom_out_map
[edit interfaces interface-name  unit unit-number inet]
user@host# edit auto-configure

Begin the specific packet-triggered subscriber configuration.

[edit interfaces interface-name  unit unit-number inet address-source]
user@host# edit  address-ranges

Under address range configure the following:
1. Dynamic profile includes the details for network address, and the range for the demux interface for the family.
  [edit interfaces interface-name unit unit-number inet address-source address-range] user@host# edit dynamic-profile
2. Authentication includes the details for password to be included and the username profiles such as, delimiter, domain name, interface name, authentication server, source address and user prefix for the demux interface for the family.
  [edit interfaces interface-name unit unit-number inet address-source address-range] user@host# edit authentication
  Packet Triggered Recovery Support for Static VLAN Subscribers (MX240, MX304, MX480, MX960, MX2010, MX2020, MX10004 and MX10008)
  
  Support for packet triggered functionality based on the following line cards on MX series devices:
  - MX304 and other MX series devices with MPC10 line card (ZT ASIC)
  - MX10K-LC9600 line card (YT ASIC)
  The packet triggered feature supports static IP assigned subscribers, that includes support for:
  - Subscribers with and without VLANs.
  - Subscribers with IPv4 and IPv6 packets.
  - One IP Demux connection per IPv4 or IPv6 address.
  - Packet triggered subscribers using authentication and service selection by RADIUS server and SRC.
  - Support 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.
  To enable subscriber management service for packet triggered configuration on an underlying interface, use the enable force command under [edit system services hierarchy] or use the set system services subscriber-management enable force command.
  [edit system services] subscriber-management { enable { force; } }

arrow_backward PREVIOUS DHCPv6 Monitoring and Management

NEXT arrow_forward Address-Assignment Pools for Subscriber Management

Broadband Subscriber Sessions User Guide

ON THIS PAGE

IP Demultiplexing Interfaces on Packet-Triggered Subscriber Services

IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview

Benefits of IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services

Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles

Packet Triggered Recovery Support for Static VLAN Subscribers (MX240, MX304, MX480, MX960, MX2010, MX2020, MX10004 and MX10008)

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry