ccqmCmtsEnfRuleSecondPeakTime

CISCO-CABLE-QOS-MONITOR-MIB · .1.3.6.1.4.1.9.9.341.1.1.1.1.19

Object

column r/w Unsigned32
The user can define two peak times in a day. The second 
peak is defined using ccqmCmtsEnfRuleSecondPeakTime, 
ccqmCmtsEnfRuleSecondDuration and 
ccqmCmtsEnfRuleSecondThreshold objects while the first 
peak is defined using ccqmCmtsEnfRuleFirstPeakTime, 
ccqmCmtsEnfRuleFirstDuration and 
ccqmCmtsEnfRuleFirstDuration. For the remaining hours in 
the day, the off-peak monitoring would happen if
both  ccqmCmtsEnfRuleOffPeakDuration and
ccqmCmtsEnfRuleOffPeakThreshold are defined. 
Defining the first peak is mandatory, though
defining the second peak and offpeak is not mandatory.
Both these peak times should be defined such that they 
don't overlap and the first peak time has to be an earlier
time than the second peak time. 
ccqmCmtsEnfRuleSecondDuration can be set to 0 to 
indicate that the second peak monitoring no longer
needs to be performed. The first peak has to be
defined before defining the second peak time. 
User would need to use 24 hour clock for setting this.
This object cannot be changed when 
ccqmCmtsEnfRuleRowStatus is active(1).

Context

MIB
CISCO-CABLE-QOS-MONITOR-MIB
OID
.1.3.6.1.4.1.9.9.341.1.1.1.1.19
Type
column
Access
readwrite
Status
current
Parent
ccqmCmtsEnforceRuleEntry
Table
ccqmCmtsEnforceRuleTable
Siblings
22

Syntax

Unsigned32

Values & Constraints

Object Constraints
range: 0-23

Related Objects

Sibling Objects