Subscriber QoS overrides enable per-subscriber and per-SLA Profile Instance QoS parameter customization to reduce the amount of sub-profiles and sla-profiles that must be configured on the router to cover all needed service level combinations.
Subscriber QoS overrides can be installed at subscriber host or session creation:
with an Alc-Subscriber-QoS-Override VSA in a RADIUS Access-Accept message
with a Charging-Rule-Install/Charging-Rule-Definition/QoS-Information AVP in a DIAMETER Gx CCA message
To use the APN-Aggregate-Max-Bitrate-DL and APN-Aggregate-Max-Bitrate-UL AVPs for QoS overrides, a corresponding 3gpp-qos-mapping must be configured in the DIAMETER Gx application policy:
>config>subscr-mgmt>diam-appl-plcy>gx>3gpp-qos-mapping>
[no] apn-ambr-dl - Configure the APN-AMBR mapping for the downlink
[no] apn-ambr-ul - Configure the APN-AMBR mapping for the uplink
Subscriber QoS overrides can be installed, updated or removed in a mid-session change with a RADIUS CoA, a DIAMETER Gx RAR or a DIAMETER Gx CCA message using the same attributes as for a subscriber host or session creation.
Subscriber QoS overrides can also be activated using subscriber services. See QoS override-based subscriber service for details.
The format of the [26.6527.126] Alc-Subscriber-QoS-Override VSA is described in the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.
The format of QoS Overrides AVP's in the 3GPP-1016 QoS-Information AVP are described in the 7750 SR and VSR Gx AVPs Reference Guide.
The following SLA profile instance QoS parameters can be overridden:
ingress and egress queue: pir, cir, mbs, cbs
ingress and egress policer: pir, cir, mbs, cbs
egress queue class weight (applies to HSQ card only)
egress queue wrr weight (applies to HSQ card only)
egress aggregate rate (applies to HSQ card only)
egress wrr group: rate, class weight (applies to HSQ card only)
The following subscriber QoS parameters can be overridden:
egress aggregate rate
ingress and egress root arbiter rate
ingress and egress intermediate arbiter rate
ingress and egress user scheduler: rate, cir
The ingress and egress user scheduler overrides through DIAMETER Gx can only be performed using APN-Aggregate-Max-Bitrate-UL and APN-Aggregate-Max-Bitrate-DL AVPs and requires the following 3gpp-qos-mapping in the DIAMETER Gx Application policy
>config>subscr-mgmt>diam-appl-plcy>gx>
3gpp-qos-mapping
apn-ambr-dl scheduler <scheduler-name>
apn-ambr-ul scheduler <scheduler-name>
exit
The operational value of some of the QoS parameters can be derived from different sources.
For queue and policer QoS parameters, the following hierarchy applies (highest priority is listed first):
Credit Control overrides
Subscriber Services QoS overrides
Subscriber QoS overrides (RADIUS, DIAMETER)
Overrides configured at sla-profile level
Queue parameters set in QoS policy level
For scheduler and arbiter overrides, the following hierarchy applies:
ANCP overrides
Subscriber Services QoS overrides
Subscriber QoS overrides (RADIUS, DIAMETER)
Overrides configured at sub-profile level
Scheduler/arbiter parameters as configured in scheduling/policer-control-policy
Up to 18 QoS overrides can be installed per subscriber host or session. A new set of QoS overrides received using a mid-session change replaces the previous set of QoS overrides.
QoS overrides are always stored as part of the subscriber host or session data but are only applied when the override is valid in the active QoS configuration. For example:
An egress queue 5 PIR rate override is stored with the subscriber session but not applied when the sap-egress QoS policy has no queue 5 defined
RADIUS or DIAMETER Gx initiated QoS overrides can be displayed with the following show commands:
show service id service-id | name ipoe session detail
show service id service-id | name ppp session detail
show service id service-id | name dhcp lease-state detail
show service id service-id | name dhcp6 lease-state detail
show service id service-id | name arp-host detail
show service id service-id | name slaac-host detail
Subscriber services initiated QoS overrides can be displayed with:
show service sub-services
The active QoS overrides per-subscriber and per-SLA Profile Instance can be displayed with:
show service active-subscribers detail
The number of allocated and free Subscriber SLA Profile Instance QoS overrides, QoS Intermediate Arbiter Overrides and QoS User Scheduler Overrides per-line card can be monitored with the tools dump resource-usage card CLI command.
Subscriber QoS overrides are synchronized through MCS in a dual-homing environment. QoS overrides are not stored in the subscriber-mgmt application persistence file.