Dynamic data services enables a zero-touch, single-ended provisioning model for business services. Two deployment models are available:
With control channel
Triggered by the authentication of a single or dual-stack PPPoE or IPoE session as a business CPE control channel, parameters are passed in a RADIUS Access-Accept or CoA message to set up a Layer 2 or Layer 3 data service.
Without control channel
RADIUS or local authentication of a dynamic data service data trigger provides the required parameters to set up a Layer 2 or Layer 3 data service.
Dynamic Data Services support includes:
Epipe VLL services
Epipe VLL services with dynamic MS-PWs (FEC 129) or spoke SDP
EVPN based Epipe service
VPLS services
VPLS services with BGP-AD pseudowire
VPLS service with spoke SDP or mesh SDP
EVPN based VPLS service
IES and VPRN services
MVPN services
Routing policy, filter, operational groups and OAM-PM provisioning
The full list of supported configuration commands can be displayed with the tools dump service dynamic-services command-list CLI command. Dynamic data service SAPs must be located on dot1q- or qinq-encapsulated Ethernet, anchoring or satellite ports and can be part of a LAG.
A Python script interface adds a flexible abstraction layer that reduces the OSS integration cost; only the business user specific service parameters, such as service type, IP address, QoS, and filter parameters, are required from RADIUS or local authentication. These parameters are then used in the Python script to generate a CLI template to set up the target Dynamic Data Service.
Dynamic data services configuration can be updated via a RADIUS CoA message.
Both XML accounting and RADIUS accounting for up to two different RADIUS destinations can be activated on a dynamic data service SAP.