RADIUS Triggered Dynamic Data Services In This Section Topics in this section include: • Introduction to RADIUS Triggered Dynamic Data Services Introduction to RADIUS Triggered Dynamic Data Services RADIUS triggered Dynamic Data Services enables a zero touch, single ended provisioning model for business services. Triggered by the authentication of a single or dual stack PPPoE session or single stack IPv4 host as business CPE control channel, parameters are passed in a RADIUS Access Accept or CoA message to setup a Layer 2 or Layer 3 data service. Dynamic Data Services supported in this release include local Epipe VLL services, Epipe VLL services with dynamic MS-PWs (FEC 129), vpls services with BGP-AD pseudowire, IES and VPRN services. Dynamic Data Service SAPs have to be located on dot1q or qinq encapsulated Ethernet ports and can be part of a LAG. A Python script interface adds a flexible abstraction layer reducing the OSS integration cost: only the business user specific service parameters (service type, IP address, QoS, and filter parameters) are required from RADIUS and then used in a CLI template to setup the target service. Both XML and RADIUS accounting to up to two different RADIUS destinations can be activated on a dynamic data service SAP.
