| ccsFlapMacAddr |
.1.3.6.1.4.1.9.9.114.1.1.5.1.1 |
|
MAC address of the Cable Modem's Cable interface
which identifies a flap-list entry for a flapping
Cable Modem.
|
| ccsFlapUpstreamIfIndex |
.1.3.6.1.4.1.9.9.114.1.1.5.1.2 |
|
The ifIndex of the Cable upstream interface whose ifType is
docsCableUpstream(129). The CMTS detects a flapping Cable
Modem from its Cable upstream interface.
|
| ccsFlapDownstreamIfIndex |
.1.3.6.1.4.1.9.9.114.1.1.5.1.3 |
|
The ifIndex of the Cable downstream interface whose ifType
is docsCableDownstream(128).
|
| ccsFlapInsertionFails |
.1.3.6.1.4.1.9.9.114.1.1.5.1.4 |
|
The 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 registration 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.
|
| ccsFlapHits |
.1.3.6.1.4.1.9.9.114.1.1.5.1.5 |
|
The 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.
|
| ccsFlapMisses |
.1.3.6.1.4.1.9.9.114.1.1.5.1.6 |
|
The 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.
|
| ccsFlapCrcErrors |
.1.3.6.1.4.1.9.9.114.1.1.5.1.7 |
|
The 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.
|
| ccsFlapPowerAdjustments |
.1.3.6.1.4.1.9.9.114.1.1.5.1.8 |
|
The 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-dependent 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.
|
| ccsFlapTotal |
.1.3.6.1.4.1.9.9.114.1.1.5.1.9 |
|
Whenever 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.
|
| ccsFlapLastFlapTime |
.1.3.6.1.4.1.9.9.114.1.1.5.1.10 |
|
The flap time is set whenever the Cable Modem triggers a
flap detector.
|
| ccsFlapCreateTime |
.1.3.6.1.4.1.9.9.114.1.1.5.1.11 |
|
The 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
discontinuities.
|
| ccsFlapRowStatus |
.1.3.6.1.4.1.9.9.114.1.1.5.1.12 |
|
Controls 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.
|
| ccsFlapInsertionFailNum |
.1.3.6.1.4.1.9.9.114.1.1.5.1.13 |
|
The 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 registration 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.
|
| ccsFlapHitNum |
.1.3.6.1.4.1.9.9.114.1.1.5.1.14 |
|
The 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.
|
| ccsFlapMissNum |
.1.3.6.1.4.1.9.9.114.1.1.5.1.15 |
|
The 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.
|
| ccsFlapCrcErrorNum |
.1.3.6.1.4.1.9.9.114.1.1.5.1.16 |
|
The 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.
|
| ccsFlapPowerAdjustmentNum |
.1.3.6.1.4.1.9.9.114.1.1.5.1.17 |
|
The 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-dependent 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.
|
| ccsFlapTotalNum |
.1.3.6.1.4.1.9.9.114.1.1.5.1.18 |
|
Whenever 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.
|
| ccsFlapResetNow |
.1.3.6.1.4.1.9.9.114.1.1.5.1.19 |
|
Setting 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).
|
| ccsFlapLastResetTime |
.1.3.6.1.4.1.9.9.114.1.1.5.1.20 |
|
The 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 reset
|
| ccsCmFlapDownstreamIfIndex |
.1.3.6.1.4.1.9.9.114.1.1.11.1.1 |
|
The ifIndex of the Cable downstream interface whose ifType
is docsCableDownstream(128).
|
| ccsCmFlapUpstreamIfIndex |
.1.3.6.1.4.1.9.9.114.1.1.11.1.2 |
|
The ifIndex of the Cable upstream interface whose ifType is
docsCableUpstream(129). The CMTS detects a flapping Cable
Modem from its Cable upstream interface.
|
| ccsCmFlapMacAddr |
.1.3.6.1.4.1.9.9.114.1.1.11.1.3 |
|
MAC address of the Cable Modem's Cable interface which
identifies a flapping Cable Modem.
|
| ccsCmFlapLastFlapTime |
.1.3.6.1.4.1.9.9.114.1.1.11.1.4 |
|
The flap time is set whenever the Cable Modem triggers a
flap detector.
|
| ccsCmFlapCreateTime |
.1.3.6.1.4.1.9.9.114.1.1.11.1.5 |
|
The 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
discontinuities.
|
| ccsCmFlapInsertionFailNum |
.1.3.6.1.4.1.9.9.114.1.1.11.1.6 |
|
The 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 registration 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 (ccsCmFlapTotalNum) will be incremented when
this object is incremented.
The value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if the
ccsCmFlapResetNow object was set to true(1). The value of the
object ccsCmFlapLastResetTime indicates the last reset time.
|
| ccsCmFlapHitNum |
.1.3.6.1.4.1.9.9.114.1.1.11.1.7 |
|
The 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.
The value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if the
ccsCmFlapResetNow object was set to true(1). The value of the
object ccsCmFlapLastResetTime indicates the last reset time.
|
| ccsCmFlapMissNum |
.1.3.6.1.4.1.9.9.114.1.1.11.1.8 |
|
The 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 ccsCmFlapTotalNum is high, Hit and Miss are high but
ccsCmFlapPowerAdjustmentNum and ccsCmFlapInsertionFailNum
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.
The value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if the
ccsCmFlapResetNow object was set to true(1). The value of the
object ccsCmFlapLastResetTime indicates the last reset time.
|
| ccsCmFlapCrcErrorNum |
.1.3.6.1.4.1.9.9.114.1.1.11.1.9 |
|
The number of times the CMTS upstream receiver flagged
a packet with a CRC error.
If ccsCmFlapCrcErrorNum 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.
The value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if the
ccsCmFlapResetNow object was set to true(1). The value of the
object ccsCmFlapLastResetTime indicates the last reset time.
|
| ccsCmFlapPowerAdjustmentNum |
.1.3.6.1.4.1.9.9.114.1.1.11.1.10 |
|
The 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-dependent manner
The Flap number (ccsCmFlapTotalNum) will be incremented when
this object is incremented.
If ccsCmFlapTotalNum is high, ccsCmFlapPowerAdjustmentNum is
high but the Hit and Miss are low and
ccsCmFlapInsertionFailNum 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.
The value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if the
ccsCmFlapResetNow object was set to true(1). The value of the
object ccsCmFlapLastResetTime indicates the last reset time.
|
| ccsCmFlapTotalNum |
.1.3.6.1.4.1.9.9.114.1.1.11.1.11 |
|
Whenever the Cable Modem passes flap detection, then the flap
number is increased.
There are 3 flap detectors defined:
(1) When ccsCmFlapInsertionFailNum 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 ccsCmFlapPowerAdjustmentNum is increased the Flap
number will be increased.
The value of this object can be reset to zero if this entry
is removed from the table and then re-added, or if the
ccsCmFlapResetNow object was set to true(1). The value of the
object ccsCmFlapLastResetTime indicates the last reset time.
|
| ccsCmFlapResetNow |
.1.3.6.1.4.1.9.9.114.1.1.11.1.12 |
|
Setting this object to true(1) will set the value of
certain objects in this table to 0 and does not
destroy the entry, so the ccsCmFlapCreateTime will be
unchanged. Reading this object always returns false(2).
|
| ccsCmFlapLastResetTime |
.1.3.6.1.4.1.9.9.114.1.1.11.1.13 |
|
The 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
ccsCmFlapResetNow or ccsCmFlapResetAll 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
ccsCmFlapTable have never been reset
|
| ccsCmFlapRowStatus |
.1.3.6.1.4.1.9.9.114.1.1.11.1.14 |
|
Controls 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,
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.
|
| ccsSpectrumRequestIndex |
.1.3.6.1.4.1.9.9.114.1.2.1.1.1 |
|
An arbitrary integer to uniquely identify the entry.
|
| ccsSpectrumRequestIfIndex |
.1.3.6.1.4.1.9.9.114.1.2.1.1.2 |
|
The 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.
|
| ccsSpectrumRequestMacAddr |
.1.3.6.1.4.1.9.9.114.1.2.1.1.3 |
|
A 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.
|
| ccsSpectrumRequestLowFreq |
.1.3.6.1.4.1.9.9.114.1.2.1.1.4 |
|
Start 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.
|
| ccsSpectrumRequestUpperFreq |
.1.3.6.1.4.1.9.9.114.1.2.1.1.5 |
|
End 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.
|
| ccsSpectrumRequestResolution |
.1.3.6.1.4.1.9.9.114.1.2.1.1.6 |
|
A 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.
|
| ccsSpectrumRequestOperation |
.1.3.6.1.4.1.9.9.114.1.2.1.1.7 |
|
The 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'.
|
| ccsSpectrumRequestOperState |
.1.3.6.1.4.1.9.9.114.1.2.1.1.8 |
|
The 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.
|
| ccsSpectrumRequestStartTime |
.1.3.6.1.4.1.9.9.114.1.2.1.1.9 |
|
The value of sysUpTime when the spectrum measurement
operation starts.
|
| ccsSpectrumRequestStoppedTime |
.1.3.6.1.4.1.9.9.114.1.2.1.1.10 |
|
The value of sysUpTime when the spectrum measurement
operation stops.
|
| ccsSpectrumRequestStatus |
.1.3.6.1.4.1.9.9.114.1.2.1.1.11 |
|
The control that allows modification, creation, and
deletion of entries. For detailed rules, see the
ccsSpectrumRequestEntry DESCRIPTION.
|
| ccsSpectrumDataFreq |
.1.3.6.1.4.1.9.9.114.1.2.2.1.1 |
|
ccsSpectrumDataPower 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.
|
| ccsSpectrumDataPower |
.1.3.6.1.4.1.9.9.114.1.2.2.1.2 |
|
The receiving power measured at the
ccsSpectrumDataFreq.
|
| ccsSNRRequestIndex |
.1.3.6.1.4.1.9.9.114.1.2.3.1.1 |
|
An arbitrary integer to uniquely identify this entry.
|
| ccsSNRRequestMacAddr |
.1.3.6.1.4.1.9.9.114.1.2.3.1.2 |
|
A MAC address that identifies the remote online CM
that the CNR measurement operation is being
performed on.
|
| ccsSNRRequestSNR |
.1.3.6.1.4.1.9.9.114.1.2.3.1.3 |
|
A snap shot of the CNR value that is measured over
the in-use band frequency. The ccsSNRRequestSNR is set
to 0 when ccsSNRRequestOperState is in the 'running' state.
|
| ccsSNRRequestOperation |
.1.3.6.1.4.1.9.9.114.1.2.3.1.4 |
|
The 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.
|
| ccsSNRRequestOperState |
.1.3.6.1.4.1.9.9.114.1.2.3.1.5 |
|
The operational state of the test.
ccsSNRRequestMacAddr, cannot be changed when the
ccsSNRRequestOperState is in the 'running' state.
|
| ccsSNRRequestStartTime |
.1.3.6.1.4.1.9.9.114.1.2.3.1.6 |
|
The value of sysUpTime when the CNR measurement
operation starts.
|
| ccsSNRRequestStoppedTime |
.1.3.6.1.4.1.9.9.114.1.2.3.1.7 |
|
The value of sysUpTime when the CNR measurement
operation stops.
|
| ccsSNRRequestStatus |
.1.3.6.1.4.1.9.9.114.1.2.3.1.8 |
|
The control that allows modification, creation, and
deletion of entries. For detailed rules see the
ccsSpectrumRequestEntry DESCRIPTION.
|
| ccsUpSpecMgmtHopPriority |
.1.3.6.1.4.1.9.9.114.1.3.1.1.1 |
|
A 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.
|
| ccsUpSpecMgmtSnrThres1 |
.1.3.6.1.4.1.9.9.114.1.3.1.1.2 |
|
The 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.
|
| ccsUpSpecMgmtSnrThres2 |
.1.3.6.1.4.1.9.9.114.1.3.1.1.3 |
|
The 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.
|
| ccsUpSpecMgmtFecCorrectThres1 |
.1.3.6.1.4.1.9.9.114.1.3.1.1.4 |
|
The 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.
|
| ccsUpSpecMgmtFecCorrectThres2 |
.1.3.6.1.4.1.9.9.114.1.3.1.1.5 |
|
The 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, depending on the type of ccsUpSpecMgmtHopPriority.
Note: SNMP SET will be rejected if
ccsUpSpecMgmtFecCorrectThres2 is lower than
ccsUpSpecMgmtFecCorrectThres1.
|
| ccsUpSpecMgmtFecUnCorrectThres1 |
.1.3.6.1.4.1.9.9.114.1.3.1.1.6 |
|
The 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.
|
| ccsUpSpecMgmtFecUnCorrectThres2 |
.1.3.6.1.4.1.9.9.114.1.3.1.1.7 |
|
The 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.
|
| ccsUpSpecMgmtSnrPollPeriod |
.1.3.6.1.4.1.9.9.114.1.3.1.1.8 |
|
A 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.
|
| ccsUpSpecMgmtHopCondition |
.1.3.6.1.4.1.9.9.114.1.3.1.1.9 |
|
A 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.
|
| ccsUpSpecMgmtFromCenterFreq |
.1.3.6.1.4.1.9.9.114.1.3.1.1.10 |
|
Center frequency before hopping occurs.
|
| ccsUpSpecMgmtToCenterFreq |
.1.3.6.1.4.1.9.9.114.1.3.1.1.11 |
|
Current center frequency.
|
| ccsUpSpecMgmtFromBandWidth |
.1.3.6.1.4.1.9.9.114.1.3.1.1.12 |
|
Bandwidth before hopping occurs.
|
| ccsUpSpecMgmtToBandWidth |
.1.3.6.1.4.1.9.9.114.1.3.1.1.13 |
|
Current bandwidth.
|
| ccsUpSpecMgmtFromModProfile |
.1.3.6.1.4.1.9.9.114.1.3.1.1.14 |
|
Modulation 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.
|
| ccsUpSpecMgmtToModProfile |
.1.3.6.1.4.1.9.9.114.1.3.1.1.15 |
|
The 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.
|
| ccsUpSpecMgmtSNR |
.1.3.6.1.4.1.9.9.114.1.3.1.1.16 |
|
Current SNR/CNR.
|
| ccsUpSpecMgmtUpperBoundFreq |
.1.3.6.1.4.1.9.9.114.1.3.1.1.17 |
|
Upper bound frequency that the upstream supports.
|
