Chapter 37: Service Class Names
STANDARD Revision 1.0
C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1002
Usage is monitored per Service Flow (SF). Only SFs assigned to a SC that is named as a Reference SC by an Enforce Rule
will be monitored by this feature. If any of these four parameters (priority, max-tr-rate, max-tr-burst, peak-tr-rate) of
the SC have been modified (overridden) by the CM’s configuration file, then that SF will be exempt from this feature.
Multicast SFs are exempt from this feature.
It is possible for a SF to have exceeded the usage threshold by so much that even after a penalty period its average
usage will still trigger the penalty, causing that CM to be penalized again.
Guidelines for Service Class Names:
Any configured SCN can be used as a Reference SC
The CLI disallows any attempt to use the same SCN as both the Reference and Enforce SC of a Rule
An SCN can be used as a Reference by only one Enforce Rule. An attempt to define an Enforce Rule having a
Reference SC that has already been used by another Rule will be disallowed.
A given SCN can be used as an Enforce SC by more than one rule.
The Reference SC and Enforce SC must both be defined for the same traffic direction—upstream or downstream.
Only unicast SFs are monitored by ISCA. These SFs can be static (provisioned) or dynamic and must be associated
with a service class. The four parameters monitored by the Enforce SC must not be manually overwritten in the
config file.
The bandwidth or usage allowed by the Enforce SC must be less than that allowed by the Reference SC. This is not
enforced, but ARRIS does not recommend or support Enforce Rules that increase the allowed usage.
Persistence of enforcement count histories:
ISCA count histories are preserved across Control Complex Redundancy (CCR) failovers
Counts are not preserved across system reboots, CAM sparing failovers, or modems going offline
The penalty timers will persist across a CAM sparing event, such that a CM in penalty will serve out the duration of
its penalty period after a CAM failover or failback. They will also persist if Load Balancing moves the penalized CM
to a different channel.
From one to all (any number) of downstream SFs can use the same DS Enforce Rule; any number of upstream SFs can
use the same US Enforce Rule.
It is permitted to use CLI commands to modify the QoS Parameters for a Service Class Name that is being used as the
Enforce Service Class Name within an already existing Enforce Rule.
Resetting a CM will not remove it from being in penalty, unless the "delete" option is used to remove it from the MAC
Db.
