CdxQosCtrlUpEntry |
|
SEQUENCE |
|
|
|
|
cdxQosCtrlUpAdmissionCtrl |
TruthValue |
|
|
cdxQosCtrlUpMaxRsvdBWPercent |
Integer32 |
|
|
cdxQosCtrlUpAdmissionRejects |
Counter32 |
|
|
cdxQosCtrlUpReservedBW |
Integer32 |
|
|
cdxQosCtrlUpMaxVirtualBW |
Integer32 |
|
CdxQosIfRateLimitEntry |
|
SEQUENCE |
|
|
|
|
cdxQosIfRateLimitAlgm |
INTEGER |
|
|
cdxQosIfRateLimitExpWt |
Integer32 |
|
|
cdxQosIfRateLimitShpMaxDelay |
INTEGER |
|
|
cdxQosIfRateLimitShpGranularity |
INTEGER |
|
CdxCmtsServiceExtEntry |
|
SEQUENCE |
|
|
|
|
cdxIfCmtsServiceOutOctets |
Counter32 |
|
|
cdxIfCmtsServiceOutPackets |
Counter32 |
|
|
cdxQosMaxUpBWExcessRequests |
Counter32 |
|
|
cdxQosMaxDownBWExcessPackets |
Counter32 |
|
|
cdxIfCmtsServiceHCInOctets |
Counter64 |
|
|
cdxIfCmtsServiceHCInPackets |
Counter64 |
|
|
cdxIfCmtsServiceHCOutOctets |
Counter64 |
|
|
cdxIfCmtsServiceHCOutPackets |
Counter64 |
|
CdxUpInfoElemStatsEntry |
|
SEQUENCE |
|
|
|
|
cdxUpInfoElemStatsNameCode |
INTEGER |
|
|
cdxUpInfoElemStatsIEType |
Integer32 |
|
CdxBWQueueEntry |
|
SEQUENCE |
|
|
|
|
cdxBWQueueNameCode |
INTEGER |
|
|
cdxBWQueueOrder |
Integer32 |
|
|
cdxBWQueueNumServedBeforeYield |
Integer32 |
|
|
cdxBWQueueType |
INTEGER |
|
|
cdxBWQueueMaxDepth |
Integer32 |
|
|
cdxBWQueueDepth |
Integer32 |
|
|
cdxBWQueueDiscards |
Counter32 |
|
CdxCmtsCmStatusExtEntry |
|
SEQUENCE |
|
|
|
|
cdxCmtsCmStatusValue |
INTEGER |
|
|
cdxIfCmtsCmStatusOnlineTimes |
Counter32 |
|
|
cdxIfCmtsCmStatusPercentOnline |
Integer32 |
|
|
cdxIfCmtsCmStatusMinOnlineTime |
TimeInterval |
|
|
cdxIfCmtsCmStatusAvgOnlineTime |
TimeInterval |
|
|
cdxIfCmtsCmStatusMaxOnlineTime |
TimeInterval |
|
|
cdxIfCmtsCmStatusMinOfflineTime |
TimeInterval |
|
|
cdxIfCmtsCmStatusAvgOfflineTime |
TimeInterval |
|
|
cdxIfCmtsCmStatusMaxOfflineTime |
TimeInterval |
|
|
cdxIfCmtsCmStatusDynSidCount |
Integer32 |
|
|
cdxIfCmtsCmStatusAddlInfo |
BITS |
|
|
cdxIfCmtsCmStatusOnlineTimesNum |
CdxResettableCounter32 |
|
|
cdxIfCmtsCmStatusLastResetTime |
TimeStamp |
|
CdxCmtsMacExtEntry |
|
SEQUENCE |
|
|
|
|
cdxCmtsCmOnOffTrapEnable |
TruthValue |
|
|
cdxCmtsCmOnOffTrapInterval |
Integer32 |
|
|
cdxCmtsCmDefaultMaxCpes |
Integer32 |
|
|
cdxCmtsCmTotal |
Integer32 |
|
|
cdxCmtsCmActive |
Integer32 |
|
|
cdxCmtsCmRegistered |
Integer32 |
|
|
cdxCmtsCmDMICMode |
INTEGER |
|
|
cdxCmtsCmDMICLockQos |
Integer32 |
|
CdxCmtsCmChOverEntry |
|
SEQUENCE |
|
|
|
|
cdxCmtsCmChOverSerialNumber |
Integer32 |
|
|
cdxCmtsCmChOverMacAddress |
MacAddress |
|
|
cdxCmtsCmChOverDownFrequency |
Integer32 |
|
|
cdxCmtsCmChOverUpChannelId |
Integer32 |
|
|
cdxCmtsCmChOverTrapOnCompletion |
TruthValue |
|
|
cdxCmtsCmChOverOpInitiatedTime |
TimeStamp |
|
|
cdxCmtsCmChOverState |
INTEGER |
|
|
cdxCmtsCmChOverRowStatus |
RowStatus |
|
CdxCmtsCmStatusDMICEntry |
|
SEQUENCE |
|
|
|
|
cdxCmtsCmStatusDMICMode |
INTEGER |
|
|
cdxCmtsCmStatusDMICUnLock |
TruthValue |
|
CdxCmToCpeEntry |
|
SEQUENCE |
|
|
|
|
cdxCmToCpeCmMacAddress |
MacAddress |
|
|
cdxCmToCpeInetAddressType |
InetAddressType |
|
|
cdxCmToCpeInetAddress |
InetAddress |
|
CdxCpeToCmEntry |
|
SEQUENCE |
|
|
|
|
cdxCpeToCmCpeMacAddress |
MacAddress |
|
|
cdxCpeToCmMacAddress |
MacAddress |
|
|
cdxCpeToCmInetAddressType |
InetAddressType |
|
|
cdxCpeToCmInetAddress |
InetAddress |
|
|
cdxCpeToCmStatusIndex |
Integer32 |
|
CdxCpeIpPrefixEntry |
|
SEQUENCE |
|
|
|
|
cdxCpeIpPrefixCmMacAddress |
MacAddress |
|
|
cdxCpeIpPrefixType |
InetAddressType |
|
|
cdxCpeIpPrefixAddress |
InetAddress |
|
|
cdxCpeIpPrefixLen |
InetAddressPrefixLength |
|
|
cdxCpeIpPrefixCpeMacAddress |
MacAddress |
|
|
cdxCpeIpPrefixCpeType |
SnmpAdminString |
|
CdxIfUpstreamChannelExtEntry |
|
SEQUENCE |
|
|
|
|
cdxIfUpChannelWidth |
Integer32 |
|
|
cdxIfUpChannelModulationProfile |
Unsigned32 |
|
|
cdxIfUpChannelCmTotal |
Integer32 |
|
|
cdxIfUpChannelCmActive |
Integer32 |
|
|
cdxIfUpChannelCmRegistered |
Integer32 |
|
|
cdxIfUpChannelInputPowerLevel |
TenthdBmV |
|
|
cdxIfUpChannelAvgUtil |
Integer32 |
|
|
cdxIfUpChannelAvgContSlots |
Integer32 |
|
|
cdxIfUpChannelRangeSlots |
Integer32 |
|
|
cdxIfUpChannelNumActiveUGS |
Unsigned32 |
|
|
cdxIfUpChannelMaxUGSLastOneHour |
Unsigned32 |
|
|
cdxIfUpChannelMinUGSLastOneHour |
Unsigned32 |
|
|
cdxIfUpChannelAvgUGSLastOneHour |
Unsigned32 |
|
|
cdxIfUpChannelMaxUGSLastFiveMins |
Unsigned32 |
|
|
cdxIfUpChannelMinUGSLastFiveMins |
Unsigned32 |
|
|
cdxIfUpChannelAvgUGSLastFiveMins |
Unsigned32 |
|
CdxCmtsMtcCmEntry |
|
SEQUENCE |
|
|
|
|
cdxCmtsMtcTcsId |
ChSetId |
|
|
cdxCmtsMtcCmTotal |
Unsigned32 |
|
|
cdxCMtsMtcCmOperational |
Unsigned32 |
|
|
cdxCmtsMtcCmRegistered |
Unsigned32 |
|
|
cdxCmtsMtcCmUnregistered |
Unsigned32 |
|
|
cdxCmtsMtcCmOffline |
Unsigned32 |
|
|
cdxCmtsMtcCmWideband |
Unsigned32 |
|
|
cdxCmtsMtcUpstreamBondGrp |
CdxUpstreamBondGrpList |
|
cdxQosCtrlUpEntry |
1.3.6.1.4.1.9.9.116.1.1.1.1 |
A list of attributes for each upstream MAC scheduler
that supports Quality of Service. Entries in this table
exist for each ifEntry with ifType of
docsCableUpstream(129). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxQosCtrlUpEntry |
|
|
cdxQosCtrlUpMaxRsvdBWPercent |
1.3.6.1.4.1.9.9.116.1.1.1.1.2 |
The percentage of upstream maximum reserved bandwidth to the
raw bandwidth if the admission control is enabled on this
upstream.
For example, if the upstream interface has raw bandwidth
1,600,000 bits/second and cdxQosCtrlUpMaxRsvdBWPercent is 200
percent, then this upstream scheduler will set the maximum of
virtual reserved bandwidth capacity to 3,200,000 bits/second
(1,600,000 * 2) to serve cable modems with minimum guaranteed
upstream bandwidth.
The default value is 100 percent (that is, maximum reserved
bandwidth is the raw bandwidth.) Whenever the admission
control is changed (on to off, off to on), this value will
be reset to the default value 100.
If the admission control is disabled, the value will be reset
to 100 (the default value). |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
10..1000 |
|
cdxQosIfRateLimitEntry |
1.3.6.1.4.1.9.9.116.1.1.2.1 |
List of the rate limiting attributes for cable upstream and
downstream interfaces schedulers that support Quality of
Service. Entries in this table exist for each ifEntry with
ifType of docsCableUpstream(129) and
docsCableDownstream(128). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxQosIfRateLimitEntry |
|
|
cdxQosIfRateLimitAlgm |
1.3.6.1.4.1.9.9.116.1.1.2.1.1 |
To ensure fairness, the CMTS will throttle the rate for
bandwidth request (upstream)/packet sent (downstream) at
which CMTS issues grants(upstream) or allow packet to be
send(downstream) such that the flow never gets more than
its provisioned peak rate in bps.
There are two directions for every Service Id (Sid) traffic:
downstream and upstream. Each direction is called a service
flow here and assigned one token bucket with chosen
algorithm.
The enumerations for the rate limiting algorithm are:
noRateLimit(1): The rate limiting is disabled. No rate
limiting.
oneSecBurst(2): Bursty 1 second token bucket algorithm.
carLike(3) : Average token usage (CAR-like) algorithm
wtExPacketDiscard(4) : Weighted excess packet discard
algorithm.
shaping(5): token bucket algorithm with shaping
Upstream supports the following:
No rate limiting (1),
Bursty 1 second token bucket algorithm(2),
Average token usage (CAR-like) algorithm(3),
Token bucket algorithm with shaping(5).
Downstream supports the following:
No rate limiting (1),
Bursty 1 second token bucket algorithm(2),
Average token usage (CAR-like) algorithm(3),
Weighted excess packet discard algorithm(4), and
Token bucket algorithm with shaping(5).
Token bucket algorithm with shaping is the
default algorithm for upstream if CMTS is in DOCSIS 1.0 mode
or DOCSIS 1.1 mode.
Bursty 1 second token bucket algorithm is the
default algorithm for downstream if the CMTS is in
DOCSIS 1.0 mode. If it is in DOCSIS 1.1 mode the default
algorithm for downstream is Token bucket algorithm with
shaping .
Each algorithm is described as below:
No rate limiting:
The rate limiting process is disabled and no checking
against the maximum bandwidth allowed.
Bursty 1 second token bucket rate limiting algorithm:
In this algorithm, at the start of every 1 second
interval, a service flow's token usage is reset to 0,
and every time the modem for that service flow sends a
request (upstream) / packet (downstream) the
upstream/downstream bandwidth token usage is incremented
by the size of the request/packet sent. As long as the
service flow's bandwidth token usage is less than the
maximum bandwidth in bits per second (peak rate limit)
its QoS service class allows, the request/packets will
not be restricted.
Once the service flow has sent more than its peak rate
in the one second interval, it is prevented from sending
more data by rejecting request (upstream) or dropping
packets (downstream). This is expected to slow down
the higher layer sources. The token usage counter gets
reset to 0 after the 1 second interval has elapsed. The
modem for that service flow is free to send more data
up to the peak rate limit in the new 1 second interval
that follows.
Average token usage (Cisco CAR like) algorithm:
This algorithm maintains a continuous average of the
burst token usage of a service flow. There is no sudden
refilling of tokens every 1 second interval. Every time
a request/packet is to be handled, the scheduler tries
to see how much time has elapsed since last transmission
, and computes the number of tokens accumulated by this
service flow at its QoS class peak rate. If burst usage
of the service flow is less than tokens accumulated,
the burst usage is reset to 0 and request/packet is
forwarded. If the service flow has accumulated fewer
tokens than its burst usage, the burst usage shows an
outstanding balance usage after decrementing by the
tokens accumulated. In such cases, the request/packet
is still forwarded, provided the service flow's
outstanding usage does not exceed peak rate limit of its
QoS class. If outstanding burst usage exceeds the peak
rate of the class, the service flow is given some token
credit up to a certain maximum credit limit and the
request/packet is forwarded. The request/packet is
dropped when outstanding usage exceeds peak rate and
maximum credit has been used up by this service flow.
This algorithm tracks long term average bandwidth usage
of the service flow and controls this average usage at
the peak rate limit.
Weighted excess packet discard algorithm:
This rate limiting algorithm is only available as an
option for downstream rate limiting. The algorithm is
to maintain an weighted exponential moving average of
the loss rate of a service flow over time. The loss
rate, expressed in packets, represents the number of
packets that can be sent from this service flow in a
one second interval before a packet will be dropped.
At every one second interval, the loss rate gets
updated using the ratio between the flow peak rate (in
bps) in its QoS profile and the service flow actual
usage (in bps). If the service flow begins to send more
than its peak rate continuously, the number of packets
it can send in an one second interval before
experiencing a drop will slowly keep reducing until
cable modem for that service flow slows down as
indicated by actual usage less or equal to the peak
rate.
Token bucket algorithm with shaping:
If there is no QoS class peak rate limit, forward the
request/packet without delay. If there is a QoS peak
rate limit, every time a request/packet is to be
handled, the scheduler determines the number of
bandwidth tokens that this service flow has
accumulated over the elapsed time at its QoS class peak
rate and increments the tokens counter of the service
flow accordingly. The scheduler limits the token
count to the maximum transmit burst (token bucket
depth). If token count is greater than the number of
tokens required to handle current request/packet,
decrement token count by size of request/packet and
forwards the request/packet without delay. If token
count is less than the size of request/packet, compute
the shaping delay time after which the deficit number
of tokens would be available. If shaping delay time is
less than the maximum shaping delay, decrement tokens
count by size of request/packet and forward this
request/packet with the shaping delay in the shaping
delay queue. When the delay time expires, the
request/packet is forwarded. If shaping delay time is
greater than the maximum shaping delay that the
subsequent shaper can handle, the request/packet is
dropped. Users can use cdxQosIfRateLimitShpMaxDelay to
configure the the maximum shaping delay and
cdxQosIfRateLimitShpGranularity to configure the
shaping granularity. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
noRateLimit(1), oneSecBurst(2), carLike(3), wtExPacketDiscard(4), shaping(5) |
|
cdxQosIfRateLimitShpMaxDelay |
1.3.6.1.4.1.9.9.116.1.1.2.1.3 |
The maximum shaping delay in milliseconds. That is, the
maximum amount time of buffering the CMTS will allow for
any rate exceeded flow. If the max buffering delay is
large, the grants/packets of the flow will be buffered for
a longer period of time even though the flow is rate
exceeded. This means fewer chances of drops for such rate
exceeded flow. However, too large a max shaping delay
can result is quick drainage of packet buffers at the CMTS,
since several packets will be in the shaping (delay) queue
waiting for their proper transmission time. Another
important point to be noted is that delaying a flows packets
(especially TCP flows) for extended periods of time is
useless, since the higher protocol layers may assume a
packet loss after a certain amount of time.
The maximum shaping delay is only applied to rate limit
algorithm:
Token bucket algorithm with shaping. If the rate limit
algorithm is not Token bucket algorithm with shaping, the
value is always na(1) which is not applicable.
If the token count is less than the size of request/packet,
CMTS computes the shaping delay time after which the deficit
number of tokens would be available. If the shaping delay
time is greater than the maximum shaping delay, the
request/packet will be dropped.
The enumerations for maximum shaping delay are:
na(1): maximum shaping delay is not applied to the current
rate limit algorithm
msec128(2): maximum shaping delay is 128 milliseconds
msec256(3): maximum shaping delay is 256 milliseconds
msec512(4): maximum shaping delay is 512 milliseconds
msec1024(5): maximum shaping delay is 1024 milliseconds
The downstream maximum shaping delay is configurable and the
default value is msec128(2). Whenever the downstream rate
limit algorithm is changed to Token bucket algorithm with
shaping from other rate limit algorithm, the value will
be reset to the default value.
The upstream maximum shaping delay is not configurable and
it is read-only value. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
na(1), msec128(2), msec256(3), msec512(4), msec1024(5) |
|
cdxQosIfRateLimitShpGranularity |
1.3.6.1.4.1.9.9.116.1.1.2.1.4 |
The width in milliseconds of each element in shaping
delay queue, that is, the shaping granularity.
The shaping granularity is only applied to rate limit
algorithm: Token bucket algorithm with shaping. It
controls how accurately the algorithm quantizes the shaping
delay for a rate exceeded flow. If granularity is large,
several shaping delay values will all be quantized to the
same element in the queue resulting in less accurate rate
shaping for the flows in bits/sec. On the other hand,
choosing too small granularity causes more memory to be used
for the shaper block, and also can cost a bit more in
runtime overhead.
If the rate limit algorithm is not Token bucket algorithm
with shaping, the value is always na(1) which is not
applicable.
The enumerations for shaping granularity are:
na(1): shaping granularity is not applied to the current
rate limit algorithm
msec1(2): shaping granularity in 1 milliseconds
msec2(3): shaping granularity in 2 milliseconds
msec4(4): shaping granularity in 4 milliseconds
msec8(5): shaping granularity in 8 milliseconds
msec16(6): shaping granularity in 16 milliseconds
The downstream shaping granularity is configurable and the
default value is msec4(4). Whenever the downstream rate
limit algorithm is changed to Token bucket algorithm with
shaping from other rate limit algorithm, the value will be
reset to the default value.
The upstream shaping granularity is not configurable and
it is read-only value. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
na(1), msec1(2), msec2(3), msec4(4), msec8(5), msec16(6) |
|
cdxCmtsServiceExtEntry |
1.3.6.1.4.1.9.9.116.1.1.3.1 |
Additional objects for docsIfCmtsServiceTable entry including
downstream traffic statistics and excess counts against the
Quality of Service limits for each Service ID.
From DOCSIS 1.1 onwards statistics are maintained for each
Service Flow(instead of the Service ID) in the DOCS-QOS-MIB
in docsQosServiceFlowStatsTable objects. For Cable modems
not running in DOCSIS 1.0 mode, the objects
cdxIfCmtsServiceOutOctets and cdxIfCmtsServiceOutPackets
will only support primary service flow. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsServiceExtEntry |
|
|
cdxUpInfoElemStatsEntry |
1.3.6.1.4.1.9.9.116.1.1.4.1 |
The list of statistics for a type of Information
Element (IE) which defines the allowed usage for a range
of upstream mini slots. One entry exists for each
Information Element (IE) in a upstream which ifType is
docsCableUpstream (12). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxUpInfoElemStatsEntry |
|
|
cdxUpInfoElemStatsNameCode |
1.3.6.1.4.1.9.9.116.1.1.4.1.1 |
This entry describes the Information Element (IE) type.
Enumerations are :
reqIE(1) : Request Information Element,
The request Information Element
provides an upstream interval in which
a CM can request the CMTS for bandwidth
on the upstream channel.
reqOrDataIE(2) : Request/Data Information Element,
The Request/data Information Element
provides an upstream interval in which
request may be made by the CM to the
CMTS for bandwidth or short data
packets may be transmitted on the
upstream channel.
initMtnIE(3) : Initial Maintenance Information Element
, The Initial Maintenance Information
Element provides an interval in which
new stations may join the network.
stnMtnIE(4) : Station Maintenance Information Element
, The Station Maintenance Information
Element provides an interval in which
stations are expected to perform some
aspect of routine network maintenance,
such as ranging or power adjustment.
shortGrantIE(5) : Short Data Grant Information Element,
Short data grant Information Element
provides the CM an opportunity to
transmit one or more upstream PDU's.
Short data grants are used with
intervals equal to or less than the
maximum burst size for the usage
specified in the Upstream Channel
Descriptor.
longGrantIE(6) : Long Data Grant Information Element,
The long data grant Information Element
also provides the CM an opportunity to
transmit one or more upstream PDU's.
All long data grant Information
Elements
must have a larger number of mini-slots
than that defined for a short data
grant Information Element profile
defined in the Upstream Channel
Descriptor. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
INTEGER |
reqIE(1), reqOrDataIE(2), initMtnIE(3), stnMtnIE(4), shortGrantIE(5), longGrantIE(6) |
|
cdxBWQueueEntry |
1.3.6.1.4.1.9.9.116.1.2.1.1 |
The list of queue attributes in cable upstream and
downstream interfaces schedulers that supports Quality of
Service. Entries in this table exist for each ifEntry with
ifType of docsCableUpstream(129) and
docsCableDownstream(128). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxBWQueueEntry |
|
|
cdxBWQueueNameCode |
1.3.6.1.4.1.9.9.116.1.2.1.1.1 |
The name code for the queue.
cirQ :CIR queue. The queue is for Committed Information
Rate (CIR) type of service which serves Service IDs
which have minimum guaranteed rate in its QoS
profile. It is applicable if CMTS is running is
either of DOCSIS 1.0 or 1.1 modes. For DOCSIS 1.1 it
has priority 8.
tbeQ :TBE Queue. The queue is for TIERED BEST EFFORT type
service which serves Service IDs which does not have
minimum guaranteed rate in its QoS profile. It is
only applicable if CMTS is running in DOCSIS 1.0
mode.
p0BEGrantQ-p7BEGrantQ : BEST EFFORT Queue
The queues p0BEGrantQ to P7BEGrantQ are for TIERED
BEST EFFORT type service which serves Service IDs
which do not have minimum guaranteed rate specified
in the QoS parameters. P0 has lowest priority and P7
has highest. Best Effort type is purely handled with
prioritization in FIFO's and hence demands more
number of queues. These queues are applicable only if
CMTS is running under mode DOCSIS 1.1.
rngPollQ : RngPoll queue.
The queue is for the ranging SID's. It has the
highest priority. This queue information is only
provided if CMTS is running under mode DOCSIS 1.1. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
INTEGER |
cirQ(1), tbeQ(2), p0BEGrantQ(3), p1BEGrantQ(4), p2BEGrantQ(5), p3BEGrantQ(6), p4BEGrantQ(7), p5BEGrantQ(8), p6BEGrantQ(9), p7BEGrantQ(10), rngPollQ(11) |
|
cdxCmCpeEntry |
1.3.6.1.4.1.9.9.116.1.3.1.1 |
The list contains information for a cable modem (CM) or a
Customer Premises Equipment (CPE). An entry exist for
each cable modem supported by CMTS and each Customer
Premises Equipment connected to a cable modem supported by
CMTS. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmCpeEntry |
|
|
cdxCmtsCmStatusExtEntry |
1.3.6.1.4.1.9.9.116.1.3.2.1 |
Additional objects for docsIfCmtsCmStatusTable entry. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsCmStatusExtEntry |
|
|
cdxCmtsCmStatusValue |
1.3.6.1.4.1.9.9.116.1.3.2.1.1 |
Current Cable Modem connectivity state. The object extends
states in docsIfCmtsCmStatusValue in more details.
The enumerations are:
offline(1) : modem considered offline.
others(2) : states is in
docsIfCmtsCmStatusValue.
initRangingRcvd(3) : modem sent initial ranging.
initDhcpReqRcvd(4) : dhcp request received.
onlineNetAccessDisabled(5): modem registered, but network
access for the CM is disabled.
onlineKekAssigned(6) : modem registered, BPI enabled
and KEK assigned.
onlineTekAssigned(7) : modem registered, BPI enabled
and TEK assigned.
rejectBadMic(8) : modem did attempt to register
but registration was refused
due to bad mic.
rejectBadCos(9) : modem did attempt to register
but registration was refused
due to bad COS.
kekRejected(10) : KEK modem key assignment
rejected.
tekRejected(11) : TEK modem key assignment
rejected.
online(12) : modem registered, enabled for
data.
initTftpPacketRcvd(13) : tftp packet received and option
file transfer started.
initTodRquestRcvd(14) : Time of the Day (TOD) request
received.
reset(15) : modem is resetting.
rangingInProgress(16) : initial ranging is in progress.
-- deprecated value
-- rangingCompleted(17) : initial ranging is completed.
dhcpGotIpAddr(18) : modem has got an IP address
from the DHCP server.
rejStaleConfig(19) : modem did attempt to register
but registration was refused
due to stale Config.
rejIpSpoof(20) : modem did attempt to register
but registration was refused
due to IP Spoof.
rejClassFail(21) : modem did attempt to register
but registration was refused
due to Class failure.
rejRegNack(22) : modem did attempt to register
but no acknowledgement was
received.
bpiKekExpired(23) : KEK modem key assignment
expired.
bpiTekExpired(24) : TEK modem key assignment
expired.
shutdown(25) : modem is in shutdown state.
channelChgInitRangingRcvd(26) : modem sent initial ranging
during channel change.
channelChgRangingInProgress(27) : initial ranging is in
progress during channel
change.
This cdxCmtsCmStatusValue could return initRangingRcvd(3)
or rangingInProgress(16) when the docsIfCmtsCmStatusValue
is ranging(2).
This cdxCmtsCmStatusValue will return others(2) when the
docsIfCmtsCmStatusValue states is either
rangingAborted(3), rangingComplete(4), and
ipComplete(5).
This cdxCmtsCmStatusValue could return online(12), or
onlineNetAccessDisabled(5) for CM with BPI disabled, or
onlineNetAccessDisabled(5) or onlineTekAssigned(7) for
CM with BPI enabled, when the docsIfCmtsCmStatusValue
is registrationComplete(6).
This cdxCmtsCmStatusValue could return either
rejectBadMic(8), rejectBadCos(9) rejStaleConfig(19) or
rejRegNack(22) when the docsIfCmtsCmStatusValue
is accessDenied(7) for possible reasons of cable modem
registration abort.
This cdxCmtsCmStatusValue could return either
onlineKekAssigned(6), kekRejected(10), tekRejected(11),
or online(12) for the CM with BPI enabled when the
docsIfCmtsCmStatusValue is registeredBPIInitializing(9).
The state rejectBadCos(9) is not applicable for DOCSIS1.1
modems.
The CMTS only reports states it is able to detect. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
offline(1), others(2), initRangingRcvd(3), initDhcpReqRcvd(4), onlineNetAccessDisabled(5), onlineKekAssigned(6), onlineTekAssigned(7), rejectBadMic(8), rejectBadCos(9), kekRejected(10), tekRejected(11), online(12), initTftpPacketRcvd(13), initTodRequestRcvd(14), reset(15), rangingInProgress(16), rangingCompleted(17), dhcpGotIpAddr(18), rejStaleConfig(19), rejIpSpoof(20), rejClassFail(21), rejRegNack(22), bpiKekExpired(23), bpiTekExpired(24), shutdown(25), channelChgInitRangingRcvd(26), channelChgRangingInProgress(27) |
|
cdxCmtsMacExtEntry |
1.3.6.1.4.1.9.9.116.1.3.3.1 |
Additional objects for docsIfCmtsMacTable entry including
the cable modem notification enable/disable and the
interval of cable modem notification sent by the CMTS for a
cable modem that the Mac interface supports. An entry in
this table exists for each ifEntry with an ifType of
docsCableMaclayer(127). Additional objects added to
determine the number of active/registered/total cable
modems on this cable mac interface since boot. Also, it
contains the object to set the Dynamic Message Integrity
Check (DMIC) which users can configure how cable modems are
handled if CMs fail the DMIC. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsMacExtEntry |
|
|
cdxCmtsCmDMICMode |
1.3.6.1.4.1.9.9.116.1.3.3.1.7 |
The Dynamic Shared Secret feature can operate in three
different modes, depending on what action should be taken
for cable modems that fail the CMTS MIC verification check:
notConfigured(1): It indicates that the DMIC is not
configured for this cable interface.
mark(2): By default, the Dynamic Shared Secret feature
is enabled on all cable interfaces using the
mark option. In this mode, the CMTS allows
cable modems to come online even if they fail
the CMTS MIC validity check. However, for
this modem cdxCmtsCmStatusDMICMode will
be labeled as marked.
lock(3): When the lock option is used, the CMTS assigns
a restrictive QoS configuration to CMs that
fail the MIC validity check twice in a row. A
particular QoS profile to be used for locked
cable modems can be specified by setting
cdxCmtsCmDMICLockQos.
If a customer resets their CM, the CM will
reregister but still uses the restricted QoS
profile. A locked CM continues with the
restricted QoS profile until it goes offline
and remains offline for at least 24 hours, at
which point it is allowed to reregister with a
valid DOCSIS configuration file. A system
operator can manually clear the lock on a CM by
setting cdxCmtsCmStatusDMICUnLock object.
reject(4): In the reject mode, the CMTS refuses to allow
CMs to come online if they fail the CMTS MIC
validity check. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
notConfigured(1), mark(2), lock(3), reject(4) |
|
cdxCmtsCmChOverEntry |
1.3.6.1.4.1.9.9.116.1.3.5.1 |
A CMTS operation entry to instruct a cable modem to move to
a new downstream and/or upstream channel.
A CMTS operator can use this to initiate an operation
in CMTS to instruct a cable modem to move to a new
downstream, or upstream channel or both.
Each entry consists of the mac address of the cable modem
to be moved, a new downstream frequency, a new upstream
channel id etc.. More than one entries could have for a
cable modem, so there is a time stamp for each entry to
show the time when this operation is initiated.
A management station wishing to create an entry should
first generate a pseudo-random serial number to be used
as the index to this sparse table. The station should
then create the associated instance of the row status
object. It must also, either in the same or in successive
PDUs, create the associated instance of the command and
parameter objects. It should also modify the default values
for any of the parameter objects if the defaults are not
appropriate.
Once the appropriate instances of all the command
objects have been created, either by an explicit SNMP
set request or by default, the row status should be set
to active to initiate the operation. Note that this entire
procedure may be initiated via a single set request which
specifies a row status of createAndGo as well as specifies
valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be stopped.
That is, it will run until either the CMTS has generated
downstream frequency and/or upstream channel override
fields in the RNG-RSP message sent to a cable modem or time
out. In either case, the operation is completed.
Once the operation is completed, the real result of the
operation to the cable modem cannot be known from this
table. The result of the cable modem's downstream frequency
and the upstream channel id can be checked from other MIB
tables. For example, docsIfCmtsServiceTable from
DOCS-IF-MIB can be used to check whether the cable modem's
downstream frequency and upstream channel id are changed.
Please note that even the CMTS has generated downstream
frequency and/or upstream channel override fields in the
RNG-RSP message sent to a cable modems, if the cable modem
cannot lock the instructed downstream frequency or no
upstream channel id could be used, it may reconnect back to
the original downstream frequency and upstream channel id.
Once the operation completes, the management station should
retrieve the values of the cdxCmtsCmChOverState
objects of interest, and should then delete the entry.
In order to prevent old entries from clogging the table,
entries will be aged out, but an entry will never be
deleted within 15 minutes of completing. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsCmChOverEntry |
|
|
cdxCmtsCmEntry |
1.3.6.1.4.1.9.9.116.1.3.6.1 |
The list contains a cable modem's attributes or
configurable parameters from a CMTS. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsCmEntry |
|
|
cdxCmtsCmStatusDMICEntry |
1.3.6.1.4.1.9.9.116.1.3.7.1 |
Additional DMIC objects for docsIfCmtsCmStatusTable
entry. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsCmStatusDMICEntry |
|
|
cdxCmToCpeEntry |
1.3.6.1.4.1.9.9.116.1.3.8.1 |
Represents an entry in the table. Each entry is created if
there is CPE connects to a cable modem.
The indices uniquely identify a CPE. It is never the intent
for an application to perform a SNMP Get operation against
a table of this nature, rather it is the intent to merely
enumberate mappings.
An application would determine the CPEs behind all cable
modems by performing a SNMP GetNext starting with the
variable bindings:
- cdxCmToCpeInetAddressType.0
- cdxCmToCpeInetAddress.0
It will return the IP address type and value tuple
corresponding to the CPE with lowest IP address behind the
cable modem with the lowest MAC address. An application can
perform a SNMP GetNext operation with the following variable
bindings:
- cdxCmToCpeInetAddressType.x.y.z
- cdxCmToCpeInetAddress.x.y.z
where x is MAC address of cable modem, and y.z is IP address
type and value tuple of the reported CPE.
An application can repeat this process until it has
traversed the entire table.
If the application only wants to know the CPEs behind a
given cable modem, it can perform a SNMP GetNext opertaion
with the following:
- cdxCmToCpeInetAddressType.x
- cdxCmToCpeInetAddress.x
where x is MAC address of cable modem. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmToCpeEntry |
|
|
cdxCpeToCmEntry |
1.3.6.1.4.1.9.9.116.1.3.9.1 |
An entry in cdxCpeToCmTable. Each entry contains information
on the MAC address, IP Address, and status index for the
cable modem with a specific CPE connects to. Each entry is
created if there is any cable modem with CPE connects to.
Entries are ordered by cdxCpeToCmCpeMacAddress. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCpeToCmEntry |
|
|
cdxCpeIpPrefixEntry |
1.3.6.1.4.1.9.9.116.1.3.10.1 |
An entry contains information of CM's MAC,
CPE's IP prefix type, CPE's IP prefix address,
CPE's IP prefix length and CPE's MAC address.
An entry is created if CPE is associated with a prefix. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCpeIpPrefixEntry |
|
|
cdxIfUpstreamChannelExtEntry |
1.3.6.1.4.1.9.9.116.1.4.1.1 |
Additional objects for docsIfUpstreamChannelEntry,
including the secondary upstream channel modulation
profile, the lower bound for the channel width and the
number of active, registered and total number of cable
modems on this upstream channel. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxIfUpstreamChannelExtEntry |
|
|
cdxRFtoPrimaryChannelMappingEntry |
1.3.6.1.4.1.9.9.116.1.6.1.1 |
An Entry provides the association between the physical
RF channels and the primary RF Channels. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxRFtoPrimaryChannelMappingEntry |
|
|
cdxPrimaryChanneltoRFMappingEntry |
1.3.6.1.4.1.9.9.116.1.6.2.1 |
An Entry provides the association between the primary
RF channels and the physical RF Channels. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxPrimaryChanneltoRFMappingEntry |
|
|
cdxCmtsMtcCmEntry |
1.3.6.1.4.1.9.9.116.1.7.1.1 |
An entry provides the CM statistics and management
information of a specific TCS. The interface populated in this
table is of ifType = docsCableMaclayer(127). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsMtcCmEntry |
|
|
cdxCmtsUscbSflowEntry |
1.3.6.1.4.1.9.9.116.1.7.2.1 |
A entry contains the Service Flow statistics for a specific
Upstream Channel Bonding group. The interface populated in this
table is of ifType = docsCableMaclayer(127). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CdxCmtsUscbSflowEntry |
|
|