Filter Policies And Dynamic, Policy-Driven Interfaces - Alcatel-Lucent 7450 Configuration Manual

Filter Policy Advanced Topics
Note that the subscriber identification string is available only when used with subscriber
management. Refer to the subscriber management section of the SROS Triple Play Guide and the
SR OS Router Configuration Guide.
Since most web sites are accessed using the domain name the router allows either DNS queries or
responds to DNS with the portal's IP address.

Filter Policies and Dynamic, Policy-Driven Interfaces

In addition to configuration interfaces like CLI/SNMP for example; filter policies can be modified
and/or assigned to by dynamic, policy-driven interfaces. Example of such interfaces include: BGP
flowspec, OpenFlow, Radius.
For BGP flowspec, system may auto-create internal filter policies (if an interface on which BGP
flowspec is enabled does not have a filter policy assigned). Then upon receiving of a flowspec rule,
system will attach flowspec filter rules at the end of the filter policy used on the interface up to the
supported flowspec limit. Please see BGP flowspec for more information.
For Radius, operator can assign filter policies to a subscriber, and populate filter policies used by
subscriber within a pre-configured block reserved for Radius filter entries. See TPSDA guide and
filter RADIUS-related commands for more details.
For OpenFlow, embedded filter infrastructure is used to inject OpenFlow rules into an existing
filter policy. Please see "Hybrid OpenFlow Switch" section for more details.
Policy-controlled auto-created filters are recreated on system reboot. Policy-controlled filter-
entries are lost on system reboot and need to be reprogrammed.
Page 462 7450 ESS Router Configuration Guide