Not Possible To Define QoS Constraints Despite Having QoS License

Asset ID:	1-72-1983416.1
Update Date:	2017-05-10
Keywords:

Solution Type Problem Resolution Sure

Solution 1983416.1 : Not Possible To Define QoS Constraints Despite Having QoS License

Applies to:

Acme Packet 3820 - Version S-Cx6.2.x and later
Acme Packet 4500 - Version S-Cx6.2.x and later
Information in this document applies to any platform.

Symptoms

Administrator finds it is not possible to define QoS Constraints configuration for use in realms as SBC is complaining that it is not licensed, disagreeing with output of 'show features' command.

SBC(qos-constraints)# name Major65Critical0NoCLR
SBC(qos-constraints)# state enabled
SBC(qos-constraints)# critical-rfactor 0
SBC(qos-constraints)# major-rfactor 6500
SBC(qos-constraints)# call-load-reduction 0
SBC(qos-constraints)# done
% Error 603 saving configuration QoSConstraints
Object not licensed

show features
Total session capacity: 2000
Enabled features:
2000 sessions, SIP, QOS, ACP, Load Balancing, Accounting,
High Availability, Software TLS, DoS, IDS

Cause

QoS and Routing licenses are required.

It is mandatory to have the Routing feature license enabled / imported if the Administrator wishes to use the QoS Based Routing feature, even if just for generating SNMP traps for RFactor threshold breaches. That's how the feature was developed.

The Routing (sometimes referred to as Advanced Routing) feature license unlocks the "local-policy" -> "policy-attribute" sub-menu and configuration parameters. This is what a local-policy looks like without the Routing license:

local-policy
from-address *
to-address *
source-realm peer-1
description
activate-time
deactivate-time
state enabled
policy-priority none
next-hop 192.168.2.31
realm core-1
action none
terminate-recursion disabled
app-protocol SIP
methods
lookup single
next-key

This is what the same local-policy looks like with the Routing license:

local-policy
from-address *
to-address *
source-realm peer-1
description
activate-time
deactivate-time
state enabled
policy-priority none
policy-attribute
next-hop 192.168.2.31
realm core-1
action none
terminate-recursion disabled
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
state enabled
app-protocol SIP
methods
media-profiles
lookup single
next-key
eloc-str-lkup disabled
eloc-str-match

So, the Routing feature unlocks the "carrier", "start-time", "end-time" "days-of-week", "cost", "state", "media-profiles", "eloc-string-lkup" and "eloc-str-match" parameters and allows you to define more than one "policy-attribute" per "local-policy". The Routing feature also unlocks the ENUM and (LRT) Local Routing Table features. As above, it's also a requirement for configuring the QoS Based Routing feature.

Accounting provides functionality to create CDRs in CSV, Radius or Diameter format, QoS allows Quality of Service data to be added to those CDRs. QoS and Routing also allow use of the QoS Based Routing feature. QoS (without Routing and Accounting) additionally allows reporting of average and maximum RFactor values in the ACLI "show sipd realms" output and also via SNMP polling and HDR (please see attached example file, columns U & V).

# show sipd realms M00
16:19:19-47
Realm M00() [In Service]
-- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Inbound Sessions 58 59 66 66 64 59
Rate Exceeded - - 0 0 0 -
[removed for brevity]
Latency=0.000; max=0.000
QoS R-Factor Avg=1.99; max=1.99
Early Sessions - - 49 49 48 -
Successful Sessions - - 43 43 42 -

Solution

Ensure both QoS and Routing licenses are also installed.

Cause and Solution supplied by Carl Binns

References

<BUG:20205974> - SR 3-9885235961 -- ERROR 603 SAVING ... QOSCONSTRAINTS OBJECT NOT LICENSED

Attachments

This solution has no attachment