Technical Documentation
New
Specifying QoS Parameter Instances in a Service Definition
You can specify that Service Manager create QoS parameter instances when the subscriber logs in (during service activation) or through RADIUS QoS parameter VSAs.
You can specify up to eight parameter instance commands within a profile. When you activate a service, Service Manager creates or modifies parameter instances for the subscriber interface that matches one of the subscriber-interface types configured in the QoS parameter definition.
Deactivating a service can modify or remove QoS parameter instances.
Using a service definition, you can also configure QoS parameters instances to add value to an existing parameter instance using the add keyword or dynamically create new parameter instances with an initial value using the initial-value keyword.
For more information about configuring QoS parameters, see JunosE Quality of Service Configuration Guide, QoS Parameter Overview.
To specify QoS parameter instances in a service definition, perform the following tasks:
Creating a Parameter Instance in a Profile
To create a QoS parameter instance for Service Manager:
- Configure the QoS parameter definition described in JunosE Quality of Service Configuration Guide, QoS Parameter Overview.
You must configure at least one controlled-interface type and one subscriber-interface type. The range specified in the parameter definition controls the available value of the parameter instance.
- Configure the QoS profile.host1(config)#profile video
- Configure the QoS parameter instance command in the
profile.host1(config-profile)#qos-parameter videoBandwidth1 add 40000
When the service is activated, the parameter instances are created for the subscriber interface.
You can use the add keyword with this command in Profile Configuration mode to add a value to an existing parameter instance.
You can use the initial-value keyword with this command to create a new instance with the specified value.
host1(config-profile)#qos-parameter max-subscriber-bandwidth initial-value 15000Use the no version to remove the QoS parameter instance command in the profile.
Specifying QoS Parameter Instances in a Service Definition
After you configure a QoS parameter instance for Service Manager, you can reference it in a service definition. For example:
When you activate a service, Service Manager creates the parameter instance and overwrites previous parameter instances. For example, activating the qosserviceone service definition creates a profile containing two QoS parameter instances. Service Manager creates the qosParameterName1 parameter instance with the value of bandwidth1, and creates qosParameterName2 with a value of bandwidth2.
If you activate the service definition using qosserviceone(2000000,3000000), Service Manager creates qosParameterName1 with a value of 2000000 and qosParameterName2 instance with a value of 3000000.
You can use the add keyword to add value to an existing parameter instance. For example:
<# endtmpl #>
When you specify parameter instances using the add keyword, you can also use the initial-value keyword to specify an initial value. For example:
When you activate the service, Service Manager locates the existing QoS parameter instance in the interface column. If Service Manager does not find a parameter instance, it creates one with a value specified in the initial-value keyword (in this case, 100000). The value in the command is then added to the initial value. If an existing parameter instance is found, Service Manager adds the value to the existing interface.
For example, when you activate qosServiceOne as qosServiceOne(2000000,3000000), Service Manager attempts to locate the parameter instance qosParameterName4 for the subscriber's interface. If it finds a parameter instance, it adds bandwidth2 (3,000,000) to the current value. If Service Manager does not find a parameter instance, it creates one with an initial value of 1,000,000 and adds 3,000,000. The final parameter instance value is 4,000,000.
When deactivating the service, Service Manager locates the QoS parameter instance and subtracts the value in the command from the existing instance value. If the parameter is no longer referenced, the parameter instance is removed.
