CISCO-CABLE-SPECTRUM-MIB
AI MIB Summary
The CISCO-CABLE-SPECTRUM-MIB enables DOCSIS-compliant Cisco CMTS devices to monitor upstream and downstream RF plant impairments, modem flap events, and transmission errors for automated noise mitigation and fault isolation. This module provides specific metrics on spectrum conditions and modem state transitions to facilitate troubleshooting of cable network noise events without introducing additional packet overhead or latency.
This is the MIB Module for Cable Spectrum Management for DOCSIS-compliant Cable Modem Termination Systems (CMTS).
Spectrum management is a software/hardware feature provided in the CMTS so that the CMTS may sense both downstream and upstream plant impairments, report them to a management entity, and automatically mitigate them where possible.
The CMTS directly senses upstream transmission errors.It may also indirectly monitor the condition of the plant by keeping a record of modem state changes. It is desireable to perform these functions without reducing throughput or latency and without creating additional packet overhead on the RF plant.
The purpose of cable Spectrum Management is to prevent long term service interruptions caused by upstream noise events in the cable plant. It is also used for fault management and trouble shooting the cable network. When modems are detected to go on-line and off-line by flap detectors, the cable operators can look at the flap list and spectrum tables to determine the possible causes.
98
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
98 total| Object Name |
|---|
ciscoCableSpectrumMIB OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114 |
RFC1155-SMI Unknown .1.3.6.1.4.1.9.9.114 |
ciscoCableSpectrumMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.1 |
ccsFlapObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.1.1 |
ccsFlapListMaxSizeThe maximum number of modems that a flap list can support.
This number controls the size of the flap list. For each
MAC domain or downstream,the maximum number of cable modems
that can be supported is 8191.The user may want to increase
or decrease the Flap List size according to the number of
downstreams and the number of modem line cards in the CMTS.
When the number of modems exceeds the max flap list size,
the additional modems are ignored. The flap detector is an
information filter to avoid inundating a management agent
with data which is less meaningful as a function of size.rw INTEGER .1.3.6.1.4.1.9.9.114.1.1.1 |
ccsFlapListCurrentSizeThe current number of modems in the flap list. Its value
will be less than or equal to ccsFlapListMaxSize.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.2 |
ccsFlapAgingThe flap entry aging threshold. Periodically, the
aging process scans through the flap list and removes the
cable modems that have not flapped for that many minutes.rw INTEGER .1.3.6.1.4.1.9.9.114.1.1.3 |
ccsFlapInsertionTimeThe insertion-time is an empirically derived, worst-case
number of seconds which the cable modem requires to
complete registration. The time taken by cable modems to
complete their registration is measured by the cable
operators and this information helps to determine the
insertion time. If the cable modem has not completed the
registration stage within this insertion-time setting, the
cable modem will be inserted into the flap-list.rw INTEGER .1.3.6.1.4.1.9.9.114.1.1.4 |
ccsFlapTableThis table keeps the records of modem state changes.
It can be used to identify the problematic cable modems.
An entry can be deleted from the table but can not be
added to the table. SEQUENCE OF CcsFlapEntry .1.3.6.1.4.1.9.9.114.1.1.5 |
ccsFlapEntryList of attributes for an entry in the ccsFlapTable.
An entry in this table exists for each cable modem that
triggered one of our flap detectors. CcsFlapEntry .1.3.6.1.4.1.9.9.114.1.1.5.1 |
ccsFlapMacAddrMAC address of the Cable Modem's Cable interface.
Identifies a flap-list entry for a flapping Cable Modem. MacAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.1.5.1.1 |
ccsFlapUpstreamIfIndexThe ifIndex of the Cable upstream interface whose ifType is
docsCableUpstream(129). The CMTS detects a flapping Cable
Modem from its Cable upstream interface.ro InterfaceIndex -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.1.5.1.2 |
ccsFlapDownstreamIfIndexThe ifIndex of the Cable downstream interface whose ifType
is docsCableDownstream(128).ro InterfaceIndex -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.1.5.1.3 |
ccsFlapInsertionFailsThe number of times a Cable Modem registered
more frequently than expected. Excessive registration
is defined as the presence of a time span between
two successive registration cycles which is less than
a threshold span (ccsFlapInsertionTime).
A Cable Modem may fail the ranging or registration process
due to not being able to get an IP address.When the Cable
Modem can not finish registeration within the insertion
time,it retries the process and sends the Initial
Maintenance packet again.
CMTS will receive the Initial Maintenance
packet from the Cable Modem sooner than expected and the
Cable Modem is considered a flapping modem.
This count may indicate:
Intermittent downstream sync loss, or
DHCP or modem registration problems.
The Flap Count (ccsFlapTotal) will be incremented when this
counter is incremented.
Discontinuites in the value of this counter can occur if
this entry is removed from the table and then re-added, and
are indicated by a change in the value of
ccsFlapCreateTime.rodeprecated Counter .1.3.6.1.4.1.9.9.114.1.1.5.1.4 |
ccsFlapHitsThe number of times the CMTS receives the Ranging request
from the Cable Modem.
The CMTS issues a Station Maintenance transmit opportunity
at a typical rate of once every 10 seconds and waits for
a Ranging request from the Cable Modem.If the CMTS receives
a Ranging request then the Hit count will be increased by 1
If the FlapTotal count is high,both Hits and Misses counts
are high, and other counters are relatively low then the
flapping is probably caused by the modem going up and down.
The Hits and Misses counts are keep-alive polling
statistics.
The Hits count should be much greater than the Misses count
Discontinuites in the value of this counter can occur if
this entry is removed from the table and then re-added, and
are indicated by a change in the value of
ccsFlapCreateTime.rodeprecated Counter .1.3.6.1.4.1.9.9.114.1.1.5.1.5 |
ccsFlapMissesThe number of times the CMTS misses the Ranging request
from the Cable Modem.
The CMTS issues a Station Maintenance packet every 10
seconds and waits for a Ranging request from the Cable
Modem.
If the CMTS misses a Ranging request within 25 msec then
the Misses count will be incremented.
If ccsFlapTotal is high, Hits and Misses are high but
ccsFlapPowerAdjustments and ccsFlapInsertionFails are
low then the flapping is probably caused by the modem
going up and down.
Miss counts can indicate:
Intermittent upstream,
Laser clipping, or
Noise bursts.
Laser clipping can happen if the signal power is too high
when the upstream electrical signal is converted to an
optical signal.When it happens the more input produces less
output, until finally there is no more increase in output.
This phenomena is called laser clipping.
Discontinuites in the value of this counter can occur if
this entry is removed from the table and then re-added, and
are indicated by a change in the value of
ccsFlapCreateTime.rodeprecated Counter .1.3.6.1.4.1.9.9.114.1.1.5.1.6 |
ccsFlapCrcErrorsThe number of times the CMTS upstream receiver flagged
a packet with a CRC error.
If ccsFlapCrcErrors is high, it indicates the cable
upstream may have high noise level. The modem may not be
flapping yet but it may be a potential problem.
This count can indicate:
Intermittent upstream,
Laser clipping, or
Noise bursts.
Laser clipping can happen if the signal power is too high
when the upstream electrical signal is converted to an
optical signal.When it happens the more input produces less
output, until finally there is no more increase in output.
This phenomena is called laser clipping.
Discontinuites in the value of this counter can occur if
this entry is removed from the table and then re-added, and
are indicated by a change in the value of
ccsFlapCreateTime.rodeprecated Counter .1.3.6.1.4.1.9.9.114.1.1.5.1.7 |
ccsFlapPowerAdjustmentsThe number of times the Cable Modem upstream
transmit power is adjusted during station
maintenance. When the adjustment is greater than the
power adjustment threshold the counter will be incremented.
The power adjustment threshold is chosen in an
implementation-dependant manner.
The Flap Count (ccsFlapTotal) will be incremented when this
counter is incremented.
If ccsFlapTotal is high, ccsFlapPowerAdjustments is high
but the Hits and Misses are low and ccsFlapInsertionFails
are low then the flapping is probably caused by an improper
transmit power level setting at the modem end.
This count can indicate:
Amplifier degradation,
Poor connections, or
Wind, moisture, or temperature sensitivity.
Discontinuites in the value of this counter can occur if
this entry is removed from the table and then re-added, and
are indicated by a change in the value of
ccsFlapCreateTime.rodeprecated Counter .1.3.6.1.4.1.9.9.114.1.1.5.1.8 |
ccsFlapTotalWhenever the Cable Modem passes flap detection,
then the flap counter is increased.
There are 3 flap detectors defined:
(1) When ccsFlapInsertionFails is increased the Flap count
will be increased.
(2) When the CMTS receives a Miss followed by a Hit
then the Flap count will be increased.
(3) When ccsFlapPowerAdjustments is increased the Flap
count will be increased.
Discontinuites in the value of this counter can occur if
this entry is removed from the table and then re-added, and
are indicated by a change in the value of
ccsFlapCreateTime.rodeprecated Counter .1.3.6.1.4.1.9.9.114.1.1.5.1.9 |
ccsFlapLastFlapTimeThe flap time is set whenever the Cable Modem triggers a
flap detector.ro DateAndTime -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.1.5.1.10 |
ccsFlapCreateTimeThe time that this entry was added to the table. If an
entry is removed and then later re-added, there may be a
discontinuity in the counters associated with this entry.
This timestamp can be used to detect those discontinuites.ro DateAndTime -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.1.5.1.11 |
ccsFlapRowStatusControls and reflects the status of rows in this table.
When a cable modem triggers a flap detector,if an entry
does not already exist for this cable modem, and
ccsFlapListCurrentSize is less than ccsFlapListMaxSize,
then an entry will be created in this table. The new instance
of this object will be set to active(1). All flapping
modems have the status of active(1).
Active entries are removed from the table after they have
not triggered any additional flap detectors for the period
of time defined in ccsFlapAging. Alternatively, setting
this instance to destroy(6) will remove the entry
immediately.
createAndGo(4) and createAndWait(5) are not supported.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.9.9.114.1.1.5.1.12 |
ccsFlapInsertionFailNumThe number of times a Cable Modem registered more frequently
than expected. Excessive registration is defined as the
presence of a time span between two successive registration
cycles which is less than a threshold span
(ccsFlapInsertionTime).
A Cable Modem may fail the ranging or registration process
due to not being able to get an IP address.When the Cable
Modem can not finish registeration within the insertion
time,it retries the process and sends the Initial
Maintenance packet again. CMTS will receive the Initial
Maintenance packet from the Cable Modem sooner than expected
and the Cable Modem is considered a flapping modem.
This object may indicate:
Intermittent downstream sync loss, or
DHCP or modem registration problems.
The Flap number (ccsFlapTotalNum) will be incremented when
this object is incremented.
This object is going to replace the object
ccsFlapInsertionFails and the value of this object can be
reset to zero if this entry is removed from the table and then
re-added, or if a user resets all the statistical objects for
this entry. The value of the object ccsFlapLastResetTime
indicates the last reset time.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.5.1.13 |
ccsFlapHitNumThe number of times the CMTS receives the Ranging request
from the Cable Modem.
The CMTS issues a Station Maintenance transmit opportunity
at a typical rate of once every 10 seconds and waits for
a Ranging request from the Cable Modem. If the CMTS receives
a Ranging request then the Hit number will be increased by 1
If the FlapTotal object is high, both Hit and Miss objects are
high, and other statistical objects are relatively low then
the flapping is probably caused by the modem going up and down.
The Hit and Miss objects keep-alive polling statistics. The
Hit object should be much greater than the Misses count.
This object is going to replace the object ccsFlapHits and the
value of this object can be reset to zero if this entry is
removed from the table and then re-added, or if an user resets
all the statistical objects for this entry. The value of the
object ccsFlapLastResetTime indicates the last reset time.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.5.1.14 |
ccsFlapMissNumThe number of times the CMTS misses the Ranging request
from the Cable Modem.
The CMTS issues a Station Maintenance packet every 10 seconds
and waits for a Ranging request from the Cable Modem. If the
CMTS misses a Ranging request within 25 msec then the Miss
Object will be incremented.
If ccsFlapTotalNum is high, Hit and Miss are high but
ccsFlapPowerAdjustmentNum and ccsFlapInsertionFailNum are low
then the flapping is probably caused by the modem going up and
down.
Miss object can indicate:
Intermittent upstream,
Laser clipping, or
Noise bursts.
Laser clipping can happen if the signal power is too high
when the upstream electrical signal is converted to an
optical signal.When it happens the more input produces less
output, until finally there is no more increase in output.
This phenomena is called laser clipping.
This object is going to replace the object ccsFlapMisses and
the value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if an user
resets all the statistical objects for this entry. The value
of the object ccsFlapLastResetTime indicates the last reset
time.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.5.1.15 |
ccsFlapCrcErrorNumThe number of times the CMTS upstream receiver flagged
a packet with a CRC error.
If ccsFlapCrcErrorNum is high, it indicates the cable
upstream may have high noise level. The modem may not be
flapping yet but it may be a potential problem.
This object can indicate:
Intermittent upstream,
Laser clipping, or
Noise bursts.
Laser clipping can happen if the signal power is too high
when the upstream electrical signal is converted to an
optical signal.When it happens the more input produces less
output, until finally there is no more increase in output.
This phenomena is called laser clipping.
This object is going to replace the object ccsFlapCrcErrors
and the value of this object can be reset to zero if this
entry is removed from the table and then re-added, or if a
user resets all the statistical objects for this entry. The
value of the object ccsFlapLastResetTime indicates the last
reset time.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.5.1.16 |
ccsFlapPowerAdjustmentNumThe number of times the Cable Modem upstream transmit power
is adjusted during station maintenance. When the adjustment is
greater than the power adjustment threshold the number will be
incremented. The power adjustment threshold is chosen in an
implementation-dependant manner
The Flap number (ccsFlapTotalNum) will be incremented when
this object is incremented.
If ccsFlapTotalNum is high, ccsFlapPowerAdjustmentNum is high
but the Hit and Miss are low and ccsFlapInsertionFailNum are
low then the flapping is probably caused by an improper
transmit power level setting at the modem end.
This object can indicate:
Amplifier degradation,
Poor connections, or
Wind, moisture, or temperature sensitivity.
This object is going to replace the object
ccsFlapPowerAdjustments and the value of this object can be
reset to zero if this entry is removed from the table and
then re-added, or if a user resets all the statistical objects
for this entry. The value of the object ccsFlapLastResetTime
indicates the last reset time.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.5.1.17 |
ccsFlapTotalNumWhenever the Cable Modem passes flap detection, then the flap
number is increased.
There are 3 flap detectors defined:
(1) When ccsFlapInsertionFailNum is increased the Flap number
will be increased.
(2) When the CMTS receives a Miss followed by a Hit
then the Flap number will be increased.
(3) When ccsFlapPowerAdjustmentNum is increased the Flap
number will be increased.
This object is going to replace the object ccsFlapTotal and
the value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if an user
resets all the statistical objects for this entry. The value
of the object ccsFlapLastResetTime indicates the last reset
time.ro Gauge .1.3.6.1.4.1.9.9.114.1.1.5.1.18 |
ccsFlapResetNowSetting this object to true(1) will set the following objects
of this entry to 0: ccsFlapInsertionFailsNum, ccsFlapHitsNum,
ccsFlapMissesNum, ccsFlapCrcErrorsNum, ccsFlapPowerAdjustmentsNum
and ccsFlapTotalNum. Setting this object to true does not destroy
the entry, so the ccsFlapCreateTime will be unchanged. Reading
this object always returns false(2).rw TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- } .1.3.6.1.4.1.9.9.114.1.1.5.1.19 |
ccsFlapLastResetTimeThe last time that all the statistical objects of this entry
are started from zero. There are several ways to restart the
the statistical objects from zero. Setting the object
ccsFlapResetNow or ccsFlapResetAll to true via SNMP is one
way and and the other way is via command Line Interface. This
timestamp can be used to know the last time the statistical
objects are started from zero. The special value of all '00'Hs
indicates that these statistical objects of this entry in the
ccsFlapTable have never been resetro DateAndTime -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.1.5.1.20 |
ccsFlapPowerAdjustThresholdThe power adjust threshold. When the power of the modem is
adjusted beyond this threshold, the modem will be inserted
into the flap-list.rw INTEGER .1.3.6.1.4.1.9.9.114.1.1.6 |
ccsFlapMissThresholdPer modem miss threshold which triggers polling flap detector.
When the number of times a cable modem does not acknowledge a
MAC-layer keepalive message from a cable modem card exceeds the
miss threshold, the cable modem is placed in the flap list.rw Gauge .1.3.6.1.4.1.9.9.114.1.1.7 |
ccsFlapResetAllSetting this object to true(1) causes ccsFlapInsertionFailNum,
ccsFlapHitNum, ccsFlapMissNum, ccsFlapCrcErrorNum,
ccsFlapPowerAdjustmentNum and ccsFlapTotalNum objects of each
entry in ccsFlapTable to be started from zero. Reading this
object always returns false(2).rw TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- } .1.3.6.1.4.1.9.9.114.1.1.8 |
ccsFlapClearAllSetting this object to true(1) removes all cable modems from
flap-list and all the entries in the ccsFlapTable are
destroyed. If a modem keeps flapping, the modem will be added
again into the flap list and a new entry in the ccsFlapTable
will be created. The newly created entry for that modem will
have new value of ccsFlapCreateTime and all the statistical
objects will be started from zero. Reading this object always
returns false(2).rw TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- } .1.3.6.1.4.1.9.9.114.1.1.9 |
ccsFlapLastClearTimeThe last time that all the entries in the ccsFlapTable are
destroyed. There are several ways to destroy all the entries
in the ccsFlapTable. Setting the object ccsFlapClearAll to
true is one way, and the other way is through Command Line
Interface. This timestamp can be used to know when all the
entries in the ccsFlapTable are destroyed. The special value
of all '00'Hs indicates that the entries in the ccsFlapTable
have never been destroyedro DateAndTime -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.1.10 |
ccsSpectrumObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.1.2 |
ccsSpectrumRequestTableThis table contains the spectrum data requests.
There are two types of request: background noise and SNR.
Refer to ccsSpectrumRequestIfIndex and ccsSpectrumRequestMacAddr
DESCRIPTIONS on how the type of request is determined. SEQUENCE OF CcsSpectrumRequestEntry .1.3.6.1.4.1.9.9.114.1.2.1 |
ccsSpectrumRequestEntryInformation about a spectrum data request. The management
system uses ccsSpectrumRequestStatus to control entry
modification, creation, and deletion.
Setting ccsSpectrumRequestEntry to 'destroy' causes entry
and its associated data (example: ccsSpectrumDataEntry)
to be cleaned up properly. It is suggested the entry
to be set to 'destroy' when the row is no longer in use. CcsSpectrumRequestEntry .1.3.6.1.4.1.9.9.114.1.2.1.1 |
ccsSpectrumRequestIndexAn arbitrary integer to uniquely identify the entry. INTEGER .1.3.6.1.4.1.9.9.114.1.2.1.1.1 |
ccsSpectrumRequestIfIndexThe ifIndex of a docsCableUpstream(129) interface.
The background noise measurement is requested when
ccsSpectrumRequestIfIndex is specified.
The receiving power measurement is requested when
ccsSpectrumRequestMacAddr is specified; In this case,
ccsSpectrumRequestIfIndex is the ifIndex of the
remote CM's upstream.rw InterfaceIndexOrZero -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.2.1.1.2 |
ccsSpectrumRequestMacAddrA MAC address that identifies a remote CM.
The default value of 0000.0000.0000 indicates that
the background noise will be measured for the
upstream. In this case, ccsSpectrumRequestIfIndex
must be specified.
Other values indicate that the receiving power test
is requested for the ccsSpectrumRequestMacAddr
with CM signals.rw MacAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.2.1.1.3 |
ccsSpectrumRequestLowFreqStart of frequency range.
The ccsSpectrumRequestLowFreq is adjusted slightly to
accurately represent the actual starting point
of the frequency range.
The adjustment is done as follows:
aFactor = (center frequency - ccsSpectrumRequestLowFreq)/12K
ccsSpectrumRequestLowFreq = center frequency - (aFactor * 12K)
where 12K is the FFT's bin size.rw CCSFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.2.1.1.4 |
ccsSpectrumRequestUpperFreqEnd of frequency range.
With the adjustment done to the ccsSpectrumRequestLowFreq,
ccsSpectrumRequestUpperFreq will also be adjusted to the
last frequency within the specified range divisible by the
bin size.
Refer to the ccsSpectrumRequestLowFreq DESCRIPTION for
the adjustment calculation.rw CCSFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.2.1.1.5 |
ccsSpectrumRequestResolutionA span between two frequencies.
ccsSpectrumRequestResolution dictates the amount of
receiving power data to be returned in ccsSpectrumDataTable.
The finer the resolution, the more data returned.
ccsSpectrumRequestResolution is adjusted to a value which
is divisible by FFT's 12KHz bin size.rw INTEGER .1.3.6.1.4.1.9.9.114.1.2.1.1.6 |
ccsSpectrumRequestOperationThe control that allows 'start' or 'abort' of
the test.
Since there is only 1 FFT engine running on the CMTS,
'start' changes ccsSpectrumRequestOperState to 'pending'
state if the FFT is busy; Otherwise, it changes
ccsSpectrumRequestOperState to 'running'.
'abort' changes ccsSpectrumRequestOperState to 'aborted'
state. 'abort' is only allowed when ccsSpectrumRequestOperState
is in 'pending' state.
Only 'start' when request is to be started and 'abort' when
request is to be aborted can be set by the user. It is set to
'none' only on completion of the request by the FFT engine.
Note: The SNMP SET is rejected if ccsSpectrumRequestStatus
is not 'active'.rw CCSRequestOperation -- Rsyntax INTEGER { -- ?? enum value of zero may cause problems -- none(0), -- start(1), -- abort(2) -- } .1.3.6.1.4.1.9.9.114.1.2.1.1.7 |
ccsSpectrumRequestOperStateThe operational state of the test.
ccsSpectrumRequestIfIndex, ccsSpectrumRequestMacAddr,
ccsSpectrumRequestUpperFreq, ccsSpectrumRequestLowFreq
and ccsSpectrumRequestResolution cannot be changed when
CCSRequestOperState is in the 'running' state.
For a detailed description, see the CCSRequestOperState
DESCRIPTION.ro CCSRequestOperState -- Rsyntax INTEGER { -- ?? enum value of zero may cause problems -- idle(0), -- pending(1), -- running(2), -- noError(3), -- aborted(4), -- notOnLine(5), -- invalidMac(6), -- timeOut(7), -- fftBusy(8), -- fftFailed(9), -- others(10) -- } .1.3.6.1.4.1.9.9.114.1.2.1.1.8 |
ccsSpectrumRequestStartTimeThe value of sysUpTime when the spectrum measurement
operation starts.ro TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.9.114.1.2.1.1.9 |
ccsSpectrumRequestStoppedTimeThe value of sysUpTime when the spectrum measurement
operation stops.ro TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.9.114.1.2.1.1.10 |
ccsSpectrumRequestStatusThe control that allows modification, creation, and
deletion of entries. For detailed rules, see the
ccsSpectrumRequestEntry DESCRIPTION.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.9.9.114.1.2.1.1.11 |
ccsSpectrumDataTableThis table contains the receiving power or background
noise measurement based on the criteria that is set in
the ccsSpectrumRequestEntry. SEQUENCE OF CcsSpectrumDataEntry .1.3.6.1.4.1.9.9.114.1.2.2 |
ccsSpectrumDataEntryInformation about the receiving power or background noise
measured at a particular frequency for the
ccsSpectrumRequestEntry. CcsSpectrumDataEntry .1.3.6.1.4.1.9.9.114.1.2.2.1 |
ccsSpectrumDataFreqccsSpectrumDataPower measurement frequency.
Due to the adjustment calculation the starting
frequency range for the actual measured frequency
if off comparing to the configured frequency.
Refer to ccsSpectrumRequestLowFreq DESCRIPTIONS
for the adjustment calculation.ro CCSMeasuredFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.2.2.1.1 |
ccsSpectrumDataPowerThe receiving power measured at the
ccsSpectrumDataFreq.ro INTEGER(-50..50) -- Units -- dBmV .1.3.6.1.4.1.9.9.114.1.2.2.1.2 |
ccsSNRRequestTableA table of SNR requests. SEQUENCE OF CcsSNRRequestEntry .1.3.6.1.4.1.9.9.114.1.2.3 |
ccsSNRRequestEntryInformation about an SNR request. The management
system uses ccsSNRRequestStatus to control entry
modification, creation, and deletion. CcsSNRRequestEntry .1.3.6.1.4.1.9.9.114.1.2.3.1 |
ccsSNRRequestIndexAn arbitrary integer to uniquely identify this entry. INTEGER .1.3.6.1.4.1.9.9.114.1.2.3.1.1 |
ccsSNRRequestMacAddrA MAC address that identifies the remote online CM
that the SNR measurement operation is being
performed on.rw MacAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.114.1.2.3.1.2 |
ccsSNRRequestSNRA snap shot of the SNR value that is measured over
the in-use band frequency. The ccsSNRRequestSNR is set
to 0 when ccsSNRRequestOperState is in the 'running' state.ro INTEGER(-100..100) -- Units -- dB .1.3.6.1.4.1.9.9.114.1.2.3.1.3 |
ccsSNRRequestOperationThe control that allows start or abort of the test.
Since there is only 1 FFT engine running on the CMTS,
'start' changes ccsSNRRequestOperState to 'pending'
state if the FFT is busy; Otherwise, it changes
ccsSNRRequestOperState to 'running'.
'abort' changes ccsSNRRequestOperState to 'aborted'
state.
Only 'start' when request is to be started and 'abort' when
request is to be aborted can be set by the user. It is set to
'none' only on completion of the request by the FFT engine.rw CCSRequestOperation -- Rsyntax INTEGER { -- ?? enum value of zero may cause problems -- none(0), -- start(1), -- abort(2) -- } .1.3.6.1.4.1.9.9.114.1.2.3.1.4 |
ccsSNRRequestOperStateThe operational state of the test.
ccsSNRRequestMacAddr, cannot be changed when the
ccsSNRRequestOperState is in the 'running' state.ro CCSRequestOperState -- Rsyntax INTEGER { -- ?? enum value of zero may cause problems -- idle(0), -- pending(1), -- running(2), -- noError(3), -- aborted(4), -- notOnLine(5), -- invalidMac(6), -- timeOut(7), -- fftBusy(8), -- fftFailed(9), -- others(10) -- } .1.3.6.1.4.1.9.9.114.1.2.3.1.5 |
ccsSNRRequestStartTimeThe value of sysUpTime when the SNR measurement
operation starts.ro TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.9.114.1.2.3.1.6 |
ccsSNRRequestStoppedTimeThe value of sysUpTime when the SNR measurement
operation stops.ro TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.9.9.114.1.2.3.1.7 |
ccsSNRRequestStatusThe control that allows modification, creation, and
deletion of entries. For detailed rules see the
ccsSpectrumRequestEntry DESCRIPTION.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.9.9.114.1.2.3.1.8 |
ccsConfigObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.1.3 |
ccsUpSpecMgmtTableThis table contains the attributes of the cable
upstream interfaces, ifType of docsCableUpstream(129),
to be used for improving performance and proactive
hopping.
Proactive hopping is achieved by setting the SNR
polling period over the in-use band without CM
signals. SEQUENCE OF CcsUpSpecMgmtEntry .1.3.6.1.4.1.9.9.114.1.3.1 |
ccsUpSpecMgmtEntryUpstream interface's spectrum management information. CcsUpSpecMgmtEntry .1.3.6.1.4.1.9.9.114.1.3.1.1 |
ccsUpSpecMgmtHopPriorityA preference priority for changing the frequency,
modulation, or channel width supporting the automatic
switching of the modulation scheme when the channel
becomes noisy.
The default priority is frequency, modulation, and
channel width. With the default preference, the
frequency is changed if there is a clean band
available. If there's no clean band available,
the modulation is changed. And if the
clean band is still not available, the bandwidth is
reduced until an acceptable band is found or a minimum
bandwidth of 200KHz.rw Enumeration .1.3.6.1.4.1.9.9.114.1.3.1.1.1 |
ccsUpSpecMgmtSnrThres1The upper Signal to Noise (SNR) threshold. This object
is applicable for modulation profile 1.
When the CMTS detects that the SNR goes lower than
ccsUpSpecMgmtSnrThres1, it switches to profile 2.
Therefore, ccsUpSpecMgmtSnrThres1 should be larger than
ccsUpSpecMgmtSnrThres2.rw INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.2 |
ccsUpSpecMgmtSnrThres2The upper Signal to Noise (SNR) threshold. This object
is applicable for modulation profile 2.
When CMTS detects that the SNR goes lower than
ccsUpSpecMgmtSnrThres2, hopping can possibly occur,
depending on the type of ccsUpSpecMgmtHopPriority.
Note: The SNMP SET is rejected if ccsUpSpecMgmtSnrThres2
is higher than ccsUpSpecMgmtSnrThres1.rw INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.3 |
ccsUpSpecMgmtFecCorrectThres1The Forward Error Correction (FEC) correctable count
threshold. This object is applicable for profile 1.
When CMTS detects that FEC correctable count goes
higher than ccsUpSpecMgmtFecCorrectThres1, it
switch to Profile 2. Therefore,
ccsUpSpecMgmtFecCorrectThres1 should be smaller
than ccsUpSpecMgmtFecCorrectThres2.rw INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.4 |
ccsUpSpecMgmtFecCorrectThres2The FEC correctable count threshold. This object
is applicable for profile 2.
When CMTS detects that FEC correctable count goes higher
than ccsUpSpecMgmtFecCorrectThres2, modulation change can
occur, depeding on the type of ccsUpSpecMgmtHopPriority.
Note: SNMP SET will be rejected if ccsUpSpecMgmtFecCorrectThres2
is lower than ccsUpSpecMgmtFecCorrectThres1.rw INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.5 |
ccsUpSpecMgmtFecUnCorrectThres1The FEC uncorrectable count threshold. This object
is applicable for modulation profile 1.
When CMTS detects that FEC uncorrectable count goes higher than
ccsUpSpecMgmtFecUnCorrectThres1, it switches to Profile 2.
Therefore, ccsUpSpecMgmtFecUnCorrectThres1 should be smaller
than ccsUpSpecMgmtUnFecCorrectThres2.rw INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.6 |
ccsUpSpecMgmtFecUnCorrectThres2The FEC uncorrectable count threshold. This object
is applicable for modulation profile 2.
When CMTS detects that FEC uncorrectable count goes higher
than ccsUpSpecMgmtFecUnCorrectThres2, modulation change can
occur, depeding on the type of ccsUpSpecMgmtHopPriority.
Note: SNMP SET is rejected if ccsUpSpecMgmtFecUnCorrectThres2
is lower than ccsUpSpecMgmtFecUnCorrectThres1.rw INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.7 |
ccsUpSpecMgmtSnrPollPeriodA period between SNR pollings.
The SNR is collected from the Fast Fourier Transform
(FFT) measurement over the in-use band when there is
no CM signals. When the CMTS detects that SNR doesn't
meet ccsUpSpecMgmtSnrThres1 or ccsUpSpecMgmtSnrThres2,
a possible hopping occurs, depending on the type of
ccsUpSpecMgmtHopPriority.rwdeprecated INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.8 |
ccsUpSpecMgmtHopConditionA condition that triggers hopping.
The SNR condition occurs when SNR does not meet
the ccsUpSpecMgmtSnrThres1 or ccsUpSpecMgmtSnrThres2.
The stationMaintainenceMiss condition occurs when the
percentage of offline CMs is reached.ro Enumeration .1.3.6.1.4.1.9.9.114.1.3.1.1.9 |
ccsUpSpecMgmtFromCenterFreqCenter frequency before hopping occurs.ro CCSFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.10 |
ccsUpSpecMgmtToCenterFreqCurrent center frequency.ro CCSFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.11 |
ccsUpSpecMgmtFromBandWidthBandwidth before hopping occurs.ro CCSFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.12 |
ccsUpSpecMgmtToBandWidthCurrent bandwidth.ro CCSFrequency -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.13 |
ccsUpSpecMgmtFromModProfileModulation profile index before hopping occurs.
It is the index identical to the docsIfModIndex
in the docsIfCmtsModulationTable.
For the detailed descriptions, see the
docsIfCmtsModulationTable and docsIfCmtsModIndex
DESCRIPTIONS.ro INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.14 |
ccsUpSpecMgmtToModProfileThe current modulation profile index.
It is the index identical to the docsIfModIndex
in the docsIfCmtsModulationTable.
For the detailed descriptions, see the
docsIfCmtsModulationTable and docsIfCmtsModIndex
DESCRIPTIONS.ro INTEGER .1.3.6.1.4.1.9.9.114.1.3.1.1.15 |
ccsUpSpecMgmtSNRCurrent SNR.ro INTEGER(-100..100) -- Units -- dB .1.3.6.1.4.1.9.9.114.1.3.1.1.16 |
ciscoCableSpectrumMIBNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.2 |
ccsMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.2.0 |
ccsHoppingNotificationA notification is sent when there's a change in
frequency (hopping), modulation, or profile.
In the case of frequency hopping,
ccsUpSpecMgmtHopCondition would indicate whether
SNR or modemOffline that caused the hopping. TRAP-TYPE .1.3.6.1.4.1.9.9.114.2.0.1 |
ciscoCableSpectrumMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3 |
ciscoCableSpectrumMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.1 |
ccsCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.1.1 |
ccsCompliance2 OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.1.2 |
ccsCompliance3 OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.1.3 |
ccsCompliance4 OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.1.4 |
ciscoCableSpectrumMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2 |
ccsFlapGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2.1 |
ccsSpectrumGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2.2 |
ccsUpSpecMgmtGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2.3 |
ccsNotificationGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2.4 |
ccsFlapGroupRev1 OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2.5 |
ccsUpSpecMgmtGroupRev1 OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.114.3.2.6 |