Alcatel-Lucent 7750 SR - Page 683

Virtual Private LAN Services
7750 SR OS Services Guide Page 683
service
Syntax [no] service service-id
Context config>service>vpls>sap>msap-defaults
Description This command sets default service for all subscribers created based on trigger packets received on the
given capture SAP in case the corresponding VSA is not included in RADIUS authentication
response. This command is applicable to capture SAP only.
Default no service.
policy
Syntax policy msap-policy-name
no policy
Context config>service>vpls>sap>msap-defaults
Description This command sets default msap-policy for all subscribers created based on trigger packets received
on the given capture-sap in case the corresponding VSA is not included in the RADIUS
authentication response. This command is applicable to capture SAP only.
Default no policy
multi-service-site
Syntax multi-service-site customer-site-name
no multi-service-site
Context config>service>vpls>sap
Description This command associates the SAP with a customer-site-name. If the specified customer-site-name
does not exist in the context of the service customer ID an error occurs and the command will not
execute. If customer-site-name exists, the current and future defined queues on the SAP (ingress and
egress) will attempt to use the scheduler hierarchies created within customer-site-name as parent
schedulers.
This command is mutually exclusive with the SAP ingress and egress scheduler-policy commands. If
a scheduler-policy has been applied to either the ingress or egress nodes on the SAP, the multi-
service-site command will fail without executing. The locally applied scheduler policies must be
removed prior to executing the multi-service-site command.
The no form of the command removes the SAP from any multi-service customer site the SAP belongs
to. Removing the site can cause existing or future queues to enter an orphaned state.
Default None
customer-site-name — The customer-site-name must exist in the context of the customer-id defined
as the service owner. If customer-site-name exists and local scheduler policies have not been
applied to the SAP, the current and future queues defined on the SAP will look for their parent
schedulers within the scheduler hierarchies defined on customer-site-name.