When the SR OS receives an Alc-Sub-Serv-Internal VSA [26-6527-155] in an Access-Accept or CoA message as a result of the Python script sub_svc.commit_service() function, the corresponding subscriber services are activated or deactivated. Optionally, an accounting session can be started for each subscriber service instance.
The following is an example of the show service sub-services command.
# show service sub-services
===============================================================================
Subscriber service table
===============================================================================
Username : cpe2@domain1.com
Subscriber : cpe2@domain1.com Type : PPP
SAP : 1/1/4:1201.5 Service : 1000
MAC Address : 00:51:00:00:01:01 PPPoE-SID: 114
IP : 10.1.1.3
Interface-ID : 02:51:00:FF:FE:00:01:01
-------------------------------------------------------------------------------
Service instance : rate-limit;5120;30720
up time : 0d 00:01:06
type : rate-limit
acct sess id : 144DFF00000A2556B757DA
multi sess id : 144DFF00000A1156B71E44
acct type : volume-time
acct ivl : 1d 00:00:00
input octets : 0
input packets : 0
output octets : 0
output packets : 0
actions :
QoS-override
ingress arbiter "root" rate 5120
QoS-override
egress aggregate rate limit 30720
-------------------------------------------------------------------------------
number of subscriber services found: 1
===============================================================================
The following rules apply for a subscriber service instance.
A subscriber service instance can be activated on a:
single-stack or dual-stack PPPoE session
single-stack or dual-stack IPoE session
single-stack IPoEv4 host
A subscriber service instance is uniquely identified by its name. To deactivate a subscriber service instance, the subscriber service name must be referenced.
A subscriber service cannot be modified. To update a subscriber service instance, the old subscriber service must be deactivated and a new one activated.
Multiple subscriber services can be activated or deactivated in a single Access-Accept or CoA message. Tagged subscriber service-specific VSAs are available for this purpose.
A single subscriber service instance can have multiple actions, such as multiple QoS overrides or multiple PCC rules.
The conflict action determines the behavior when multiple subscriber services of the same type are activated for the same PPPoE or IPoE session:
Conflict action = none
Multiple instances of the same type can be activated.
Conflict action = keep new
Only a single subscriber service instance of the same type is allowed.
When a new subscriber service instance of the same type is activated on a single PPPoE or IPoE session, the old instance is deactivated, and the new subscriber service instance is activated.
Conflict action = keep old
Only a single subscriber service instance of the same type is allowed.
When a subscriber service instance of the same type is activated on a single PPPoE or IPoE session, the new subscriber service instance is rejected.
Multi-Chassis Synchronization (MCS) is not supported for subscriber services.