For general restrictions for HSQ, see the HSQ Restrictions section in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide
Deploy ESM on HSQ with the following considerations:
An on-line subscriber profile change (using CoA, RAR, re-authentication, or the tools perform command) for subscribers is allowed only for subscriber profiles with the same hs-sla-modes. In other words, an on-line change of the SLA mode for a subscriber on HSQ is not supported.
Change of a SLA mode within the subscriber profile is allowed only for subscriber profiles that are not associated with subscribers.
An on-line change of a SLA profile for a subscriber in single SLA mode with host-shared filters is not supported.
An on-line change of a SLA profile for subscribers in single SLA mode with more than one non-session based hosts or more than one session, is not supported. When a single subscriber session with multiple hosts within the session where SLA change is allowed, all the hosts within the session are associated with the new SLA.
An on-line change of an SLA profile for subscribers in single SLA mode with any static/l2 host is not supported.
A single SLA mode supports a single SPI and a single SAP. Any attempt to create an additional SPI, or to add an SPI with a different SAP for the subscriber is rejected.
Shared queueing on HSQ ingress is not supported and consequently the default shared-queuing setting in MSAP policy must be explicitly disabled.
To achieve maximum scaling on ingress, it is recommended that policing is deployed on ingress. This implies that all FCs on ingress are explicitly mapped to ingress policers within the QoS policy and that profiled-traffic-only command in the sap>sub-sla-mgmt or msap>sub-sla-mgmt context under is enabled.