New Policing Command Support QoS Aggregate-Policer (Doc ID 1152554.1)

Last updated on AUGUST 13, 2013

Applies to:

Oracle Communications IP Service Activator - Version: 5.2.4 and later   [Release: 5.2 and later ]
Information in this document applies to any platform.

Goal

With older versions of IPSA, only two variations of aggregate policers can be configured using the boolean option "cartridge.cisco.qos.policerAggregateSyntax.isSupported":

"true" - policer aggregate <policer name> <rate> bc <burst> exceed-action {transmit | drop | policed-dscp-transmit}

"false" - mls qos aggregate-policer <policer name> <rate> <burst> exceed-action {transmit | drop | policed-dscp-transmit}

False is the default value

With this enhancement, the user can configure the third variant of the aggregate policer i.e:

qos aggregate-policer <policer name> <rate> <burst> exceed-action {transmit | drop | policed-dscp-transmit}

A new string option is introduced to handle the two existing variants and also the new variant  "cartridge.cisco.qos.aggregatePolicer.commandSyntax". This option takes three values:

"mls_qos_aggregate" - Same as setting the older option to "false"

"policer_aggregate" - Same as setting the older option to "true"

"qos_aggregate" - Supports new command variant i.e, "qos aggregate-policer <policer name> <rate> <burst> exceed-action {transmit | drop | policed-dscp-transmit}"

Note: Though the new option is introduced, existing option will also be available with IPSA to provide backward compatibility. Always, new string option will override the setting of the older boolean option.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms