This feature enables individual attributes/values to be set against an AA subscriber complementary to using app-profiles. The AA subscriber types supported that can have ASO overrides by CLI/SNMP are provisioned business AA SAPs and spoke SDPs, and statically-provisioned transit AA subs. ESM and transit-aa AA subscribers can have ASO overrides applied by RADIUS override VSAs.
Application profile assignment is still used to obtain the following information:
the application-assurance group (and partition) to which the AA subscriber is being assigned to
whether the traffic should be diverted
capacity-cost (for load balancing to a multi-isa group)
The information configured in the app-profile is also used, but ASO characteristics and values (these are from the policy defined in the group and partition) can be overridden.
The overrides are specific to a single AA subscriber. An ASO override does affect any other AA subscriber or the app-profile config itself.
Typically the ASO characteristics in the app-profile would not be specified, therefore leaving all characteristics at their default values. This is not mandatory though and the app-profile could specify any ASO characteristic and non-default value.
The AQP has entries that can refer to ASO characteristics (attributes) and values in their match criteria. In the absence of any individual attribute/value override, an AA subscriber continues to work as before - using the ASO characteristics/values defined inside the app-profile assigned to them. With overrides, the AA subscriber attributes used in AQP lookups are the combination of the following:
the characteristics/values from the app-profile
any specific characteristics and values overridden for that AA subscriber
Show command output display the combined set of attributes that apply to the AA subscriber.
The override commands can only be used if there is already an app-profile assigned to the AA subscriber, otherwise, the overrides are rejected.
The app-profile attribute override is assigned to a specific AA subscriber (SAP, spoke SDP) within the AA Group:partition with where the subscriber exists. While subscriber names are unique, the Group:partition policy context where apps, app-profiles and ASO characteristics are defined is relevant to the override context. Override for ESM subscribers can be triggered via DIAMETER or RADIUS.