- play_arrow Subscriber-Aware and Application-Aware Traffic Treatment Overview
- play_arrow Subscriber-Aware and Application-Aware Traffic Treatment Overview
-
- play_arrow Configuring Reporting for Subscriber-Aware Data Sessions
- play_arrow Configuring Reporting
-
- play_arrow Modifying Subscriber-Aware Configuration
- play_arrow Modifying Subscriber-Aware Configuration in Maintenance Mode
- Maintenance Mode Overview for Subscriber Aware Policy Enforcement
- Changing Address Attributes in the Address Pool
- Deleting an Address Pool
- Changing AMS Interface Parameters on a TDF Gateway
- Modifying a TDF Domain
- Modifying the TDF Interface of a TDF Domain
- Deleting a TDF Domain
- Changing a TDF Interface
- Deleting a TDF Interface
- Changing TDF Gateway Parameters with Maintenance Mode
- Changing PCEF Profiles, PCC Rules, PCC Rulebases, Diameter Profiles, Flow Descriptions, and PCC Action Profiles
- Deleting a PCEF Profile
- Changing Static Time-of-Day Settings for PCC Rules
- Deleting a Services PIC
- Deleting a Session PIC
-
- play_arrow Monitoring and Troubleshooting
- play_arrow Monitoring and Troubleshooting
-
- play_arrow Configuration Statements and Operational Commands
Understanding IFL-Based Subscriber Setup
You use the CLI to configure an IFL-based subscriber for a particular interface or set of access interfaces. All user traffic that uses these interfaces belongs to the same subscriber session. The IFL-based subscriber session becomes active when at least one of its access interfaces is up.
You can specify the following types of interfaces:
Physical Layer 3 Ethernet interface
Layer 3 Aggregated Ethernet interface
Integrated routing and bridging (IRB) interface
IRB that contains Ether-channel and physical interface members
Logical Tunnel interface
You specify how an IFL-based subscriber’s traffic is processed by configuring the properties of the TDF domain in which the IFL-based subscriber is configured, which includes a pointer to the PCEF profile to assign to the subscriber.
When an IFL-based subscriber session is created, it is anchored on a session PIC based on a round-robin selection process. If a stand-alone session PIC goes down and any IFL-based subscribers are anchored on that PIC, Junos OS re-anchors a subscriber onto another session PIC.
An IFL-based subscriber session is deleted in the following situations:
All of the subscriber’s access interfaces are down. When at least one interface comes back up, the subscriber session is restored.
Subscriber is removed from the configuration with the CLI.
Subscriber is set to deactivate with the CLI.
Subscriber is cleared with the CLI. You can later restore the subscriber by using the revert option with the clear command. (See clear unified-edge tdf subscribers.)
