Data-triggered subscriber management

Prerequisites

This feature allows the creation of ESM subscribers and hosts based on the receipt of upstream data packets.

Data-triggered host creation does not rely on protocol triggers (DHCP, PPPoE) or management triggers (static hosts) to create each host, and is especially useful in the following cases:

BNG manages subscribers under Layer 3 nodes (BRAS, CMTS, GGSN/PGW, and so on) and is not on the DHCP message path.
BNG needs to manage large numbers of static hosts and bulk provisioning is required.

BNG authenticates, creates, and deletes subscriber hosts as follows:

Procedure

The subscriber SAP, including MSAP, receives a user packet that does not match existing anti-spoof table entries.
BNG instantiates an IPoE session if there is no existing session with the same session key, and performs authentication using LUDB and RADIUS.

Note: Data-triggered ESM is supported only with IPoE sessions.
A subscriber host is created with the ESM strings provided during authentication.
The subscriber host is deleted when session-timeout or idle-timeout expires, CoA triggers a disconnect, SHCV check failure, or management (CLI, SNMP, and so on) triggers a host deletion.

Note: There are no automatic triggers to delete a host if session-timeout or idle-timeout and SHCV are not configured.