Defines the criteria that trigger a change in
frequency hopping, modulation or channel width.
Depending on the type of linecards, the criteria
are slightly different:
For the linecards that have no Hardware
Based Spectrum Management capability like
the uBR-MC1xC, change in modulation or frequency
occurs in the following criteria:
1) Change from modulation profile 1 to
modulation profile 2 would occur when CMTS
detects the SNR that goes below the
threshold and either corr FEC or uncorr FEC
is above the threshold. In this case,
snrBelowThres and either corrFecAboveThres or
uncorrFecAboveThres bits will get set.
2) Change from modulation profile 2 to
modulation profile 1 would occur when CMTS
detects the SNR goes above the threshold+3
and both corr FEC and uncorr FEC are
below the threshold. In this case,
snrAboveThres and corrFecBelowThres
and uncorrFecBelowThres bits will get set.
3) Change in frequency or frequency hopping would
occur when CMTS detects no active modem on the link.
In this case, noActiveModem bit will get
set accordingly.
For the linecards that have the Hardware Based
Spectrum Management capability, change in
frequency, modulation or channel width occurs
in the following criteria:
1) when CMTS detects the SNR or CNR goes below the
threshold and either corr FEC or uncorr FEC is
above the threshold. In this case,
either snrBelowThres or cnrBelowThres and
either corrFecAboveThres or uncorrFecAboveThres
bits will get set.
2) when CMTS detects the SNR or CNR goes above the
threshold + 3 and both corr FEC and uncorr FEC are
below the threshold. In this case,
either snrAboveThres or cnrAboveThres and both
corrFecBelowThres and uncorrFecBelowThres bits
will get set.
3) when CMTS detects no active modem on the link or
uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2.
In this case noActiveModem or
uncorrFecAboveSecondThres bit will get set
accordingly.
Note: The order of frequency, modulation or channel
width changes for the advanced spectrum management
linecards will be determined based on the selection of
the ccsUpSpecMgmtHopPriority.
Parsed from file CISCO-CABLE-SPECTRUM-MIB.mib
Module: CISCO-CABLE-SPECTRUM-MIB
Defines the criteria that trigger a change in
frequency hopping, modulation or channel width.
Depending on the type of linecards, the criteria
are slightly different:
For the linecards that have no Hardware
Based Spectrum Management capability like
the uBR-MC1xC, change in modulation or frequency
occurs in the following criteria:
1) Change from modulation profile 1 to
modulation profile 2 would occur when CMTS
detects the SNR that goes below the
threshold and either corr FEC or uncorr FEC
is above the threshold. In this case,
snrBelowThres and either corrFecAboveThres or
uncorrFecAboveThres bits will get set.
2) Change from modulation profile 2 to
modulation profile 1 would occur when CMTS
detects the SNR goes above the threshold+3
and both corr FEC and uncorr FEC are
below the threshold. In this case,
snrAboveThres and corrFecBelowThres
and uncorrFecBelowThres bits will get set.
3) Change in frequency or frequency hopping would
occur when CMTS detects no active modem on the link.
In this case, noActiveModem bit will get
set accordingly.
For the linecards that have the Hardware Based
Spectrum Management capability, change in
frequency, modulation or channel width occurs
in the following criteria:
1) when CMTS detects the SNR or CNR goes below the
threshold and either corr FEC or uncorr FEC is
above the threshold. In this case,
either snrBelowThres or cnrBelowThres and
either corrFecAboveThres or uncorrFecAboveThres
bits will get set.
2) when CMTS detects the SNR or CNR goes above the
threshold + 3 and both corr FEC and uncorr FEC are
below the threshold. In this case,
either snrAboveThres or cnrAboveThres and both
corrFecBelowThres and uncorrFecBelowThres bits
will get set.
3) when CMTS detects no active modem on the link or
uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2.
In this case noActiveModem or
uncorrFecAboveSecondThres bit will get set
accordingly.
Note: The order of frequency, modulation or channel
width changes for the advanced spectrum management
linecards will be determined based on the selection of
the ccsUpSpecMgmtHopPriority.
Defines the criteria that trigger a change in
frequency hopping, modulation or channel width.
Depending on the type of linecards, the criteria
are slightly different:
For the linecards that have no Hardware
Based Spectrum Management capability like
the uBR-MC1xC, change in modulation or frequency
occurs in the following criteria:
1) Change from modulation profile 1 to
modulation profile 2 would occur when CMTS
detects the SNR that goes below the
threshold and either corr FEC or uncorr FEC
is above the threshold. In this case,
snrBelowThres and either corrFecAboveThres or
uncorrFecAboveThres bits will get set.
2) Change from modulation profile 2 to
modulation profile 1 would occur when CMTS
detects the SNR goes above the threshold+3
and both corr FEC and uncorr FEC are
below the threshold. In this case,
snrAboveThres and corrFecBelowThres
and uncorrFecBelowThres bits will get set.
3) Change in frequency or frequency hopping would
occur when CMTS detects no active modem on the link.
In this case, noActiveModem bit will get
set accordingly.
For the linecards that have the Hardware Based
Spectrum Management capability, change in
frequency, modulation or channel width occurs
in the following criteria:
1) when CMTS detects the SNR or CNR goes below the
threshold and either corr FEC or uncorr FEC is
above the threshold. In this case,
either snrBelowThres or cnrBelowThres and
either corrFecAboveThres or uncorrFecAboveThres
bits will get set.
2) when CMTS detects the SNR or CNR goes above the
threshold + 3 and both corr FEC and uncorr FEC are
below the threshold. In this case,
either snrAboveThres or cnrAboveThres and both
corrFecBelowThres and uncorrFecBelowThres bits
will get set.
3) when CMTS detects no active modem on the link or
uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2.
In this case noActiveModem or
uncorrFecAboveSecondThres bit will get set
accordingly.
Note: The order of frequency, modulation or channel
width changes for the advanced spectrum management
linecards will be determined based on the selection of
the ccsUpSpecMgmtHopPriority.
Parsed from file CISCO-CABLE-SPECTRUM-MIB.my.txt
Company: None
Module: CISCO-CABLE-SPECTRUM-MIB
Defines the criteria that trigger a change in
frequency hopping, modulation or channel width.
Depending on the type of linecards, the criteria
are slightly different:
For the linecards that have no Hardware
Based Spectrum Management capability like
the uBR-MC1xC, change in modulation or frequency
occurs in the following criteria:
1) Change from modulation profile 1 to
modulation profile 2 would occur when CMTS
detects the SNR that goes below the
threshold and either corr FEC or uncorr FEC
is above the threshold. In this case,
snrBelowThres and either corrFecAboveThres or
uncorrFecAboveThres bits will get set.
2) Change from modulation profile 2 to
modulation profile 1 would occur when CMTS
detects the SNR goes above the threshold+3
and both corr FEC and uncorr FEC are
below the threshold. In this case,
snrAboveThres and corrFecBelowThres
and uncorrFecBelowThres bits will get set.
3) Change in frequency or frequency hopping would
occur when CMTS detects no active modem on the link.
In this case, noActiveModem bit will get
set accordingly.
For the linecards that have the Hardware Based
Spectrum Management capability, change in
frequency, modulation or channel width occurs
in the following criteria:
1) when CMTS detects the SNR or CNR goes below the
threshold and either corr FEC or uncorr FEC is
above the threshold. In this case,
either snrBelowThres or cnrBelowThres and
either corrFecAboveThres or uncorrFecAboveThres
bits will get set.
2) when CMTS detects the SNR or CNR goes above the
threshold + 3 and both corr FEC and uncorr FEC are
below the threshold. In this case,
either snrAboveThres or cnrAboveThres and both
corrFecBelowThres and uncorrFecBelowThres bits
will get set.
3) when CMTS detects no active modem on the link or
uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2.
In this case noActiveModem or
uncorrFecAboveSecondThres bit will get set
accordingly.
Note: The order of frequency, modulation or channel
width changes for the advanced spectrum management
linecards will be determined based on the selection of
the ccsUpSpecMgmtHopPriority.
ccsUpSpecMgmtCriteria OBJECT-TYPE SYNTAX BITS { snrBelowThres(0), cnrBelowThres(1), corrFecAboveThres(2), uncorrFecAboveThres(3), snrAboveThres(4), cnrAboveThres(5), corrFecBelowThres(6), uncorrFecBelowThres(7), noActiveModem(8), uncorrFecAboveSecondThres(9), others(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "Defines the criteria that trigger a change in frequency hopping, modulation or channel width. Depending on the type of linecards, the criteria are slightly different: For the linecards that have no Hardware Based Spectrum Management capability like the uBR-MC1xC, change in modulation or frequency occurs in the following criteria: 1) Change from modulation profile 1 to modulation profile 2 would occur when CMTS detects the SNR that goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, snrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) Change from modulation profile 2 to modulation profile 1 would occur when CMTS detects the SNR goes above the threshold+3 and both corr FEC and uncorr FEC are below the threshold. In this case, snrAboveThres and corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) Change in frequency or frequency hopping would occur when CMTS detects no active modem on the link. In this case, noActiveModem bit will get set accordingly. For the linecards that have the Hardware Based Spectrum Management capability, change in frequency, modulation or channel width occurs in the following criteria: 1) when CMTS detects the SNR or CNR goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, either snrBelowThres or cnrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) when CMTS detects the SNR or CNR goes above the threshold + 3 and both corr FEC and uncorr FEC are below the threshold. In this case, either snrAboveThres or cnrAboveThres and both corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) when CMTS detects no active modem on the link or uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2. In this case noActiveModem or uncorrFecAboveSecondThres bit will get set accordingly. Note: The order of frequency, modulation or channel width changes for the advanced spectrum management linecards will be determined based on the selection of the ccsUpSpecMgmtHopPriority." ::= { ccsUpSpecMgmtEntry 23 }
ccsUpSpecMgmtCriteria OBJECT-TYPE SYNTAX OCTET STRING(SIZE(1..2)) ACCESS read-only STATUS mandatory DESCRIPTION "Defines the criteria that trigger a change in frequency hopping, modulation or channel width. Depending on the type of linecards, the criteria are slightly different: For the linecards that have no Hardware Based Spectrum Management capability like the uBR-MC1xC, change in modulation or frequency occurs in the following criteria: 1) Change from modulation profile 1 to modulation profile 2 would occur when CMTS detects the SNR that goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, snrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) Change from modulation profile 2 to modulation profile 1 would occur when CMTS detects the SNR goes above the threshold+3 and both corr FEC and uncorr FEC are below the threshold. In this case, snrAboveThres and corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) Change in frequency or frequency hopping would occur when CMTS detects no active modem on the link. In this case, noActiveModem bit will get set accordingly. For the linecards that have the Hardware Based Spectrum Management capability, change in frequency, modulation or channel width occurs in the following criteria: 1) when CMTS detects the SNR or CNR goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, either snrBelowThres or cnrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) when CMTS detects the SNR or CNR goes above the threshold + 3 and both corr FEC and uncorr FEC are below the threshold. In this case, either snrAboveThres or cnrAboveThres and both corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) when CMTS detects no active modem on the link or uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2. In this case noActiveModem or uncorrFecAboveSecondThres bit will get set accordingly. Note: The order of frequency, modulation or channel width changes for the advanced spectrum management linecards will be determined based on the selection of the ccsUpSpecMgmtHopPriority." ::= { ccsUpSpecMgmtEntry 23 }
Vendor: Cisco
Module: CISCO-CABLE-SPECTRUM-MIB
[Automatically extracted from oidview.com]
ccsUpSpecMgmtCriteria OBJECT-TYPE SYNTAX BITS { snrBelowThres(0), cnrBelowThres(1), corrFecAboveThres(2), uncorrFecAboveThres(3), snrAboveThres(4), cnrAboveThres(5), corrFecBelowThres(6), uncorrFecBelowThres(7), noActiveModem(8), uncorrFecAboveSecondThres(9), others(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "Defines the criteria that trigger a change in frequency hopping, modulation or channel width. Depending on the type of linecards, the criteria are slightly different: For the linecards that have no Hardware Based Spectrum Management capability like the uBR-MC1xC, change in modulation or frequency occurs in the following criteria: 1) Change from modulation profile 1 to modulation profile 2 would occur when CMTS detects the SNR that goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, snrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) Change from modulation profile 2 to modulation profile 1 would occur when CMTS detects the SNR goes above the threshold+3 and both corr FEC and uncorr FEC are below the threshold. In this case, snrAboveThres and corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) Change in frequency or frequency hopping would occur when CMTS detects no active modem on the link. In this case, noActiveModem bit will get set accordingly. For the linecards that have the Hardware Based Spectrum Management capability, change in frequency, modulation or channel width occurs in the following criteria: 1) when CMTS detects the SNR or CNR goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, either snrBelowThres or cnrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) when CMTS detects the SNR or CNR goes above the threshold + 3 and both corr FEC and uncorr FEC are below the threshold. In this case, either snrAboveThres or cnrAboveThres and both corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) when CMTS detects no active modem on the link or uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2. In this case noActiveModem or uncorrFecAboveSecondThres bit will get set accordingly. Note: The order of frequency, modulation or channel width changes for the advanced spectrum management linecards will be determined based on the selection of the ccsUpSpecMgmtHopPriority." ::= { ccsUpSpecMgmtEntry 23 }
ccsUpSpecMgmtCriteria OBJECT-TYPE SYNTAX BITS { snrBelowThres(0), cnrBelowThres(1), corrFecAboveThres(2), uncorrFecAboveThres(3), snrAboveThres(4), cnrAboveThres(5), corrFecBelowThres(6), uncorrFecBelowThres(7), noActiveModem(8), uncorrFecAboveSecondThres(9), others(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "Defines the criteria that trigger a change in frequency hopping, modulation or channel width. Depending on the type of linecards, the criteria are slightly different: For the linecards that have no Hardware Based Spectrum Management capability like the uBR-MC1xC, change in modulation or frequency occurs in the following criteria: 1) Change from modulation profile 1 to modulation profile 2 would occur when CMTS detects the SNR that goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, snrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) Change from modulation profile 2 to modulation profile 1 would occur when CMTS detects the SNR goes above the threshold+3 and both corr FEC and uncorr FEC are below the threshold. In this case, snrAboveThres and corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) Change in frequency or frequency hopping would occur when CMTS detects no active modem on the link. In this case, noActiveModem bit will get set accordingly. For the linecards that have the Hardware Based Spectrum Management capability, change in frequency, modulation or channel width occurs in the following criteria: 1) when CMTS detects the SNR or CNR goes below the threshold and either corr FEC or uncorr FEC is above the threshold. In this case, either snrBelowThres or cnrBelowThres and either corrFecAboveThres or uncorrFecAboveThres bits will get set. 2) when CMTS detects the SNR or CNR goes above the threshold + 3 and both corr FEC and uncorr FEC are below the threshold. In this case, either snrAboveThres or cnrAboveThres and both corrFecBelowThres and uncorrFecBelowThres bits will get set. 3) when CMTS detects no active modem on the link or uncorr FEC is above ccsUpSpecMgmtFecUnCorrectThres2. In this case noActiveModem or uncorrFecAboveSecondThres bit will get set accordingly. Note: The order of frequency, modulation or channel width changes for the advanced spectrum management linecards will be determined based on the selection of the ccsUpSpecMgmtHopPriority." ::= { ccsUpSpecMgmtEntry 23 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.114.1.3.1.1.1 | ccsUpSpecMgmtHopPriority | 0 | 0 | A preference priority for changing the frequency, modulation, or channel width supporting the automatic switching of the modulati… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.2 | ccsUpSpecMgmtSnrThres1 | 0 | 0 | The Signal to Noise (SNR) threshold. This object is applicable for modulation profile 1. When the CMTS detects that the SNR goes… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.3 | ccsUpSpecMgmtSnrThres2 | 0 | 0 | The Signal to Noise (SNR) threshold. This object is applicable for modulation profile 2. Refer to ccsUpSpecMgmtCriteria on how cc… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.4 | ccsUpSpecMgmtFecCorrectThres1 | 0 | 0 | The Forward Error Correction (FEC) correctable count threshold. This object is applicable for profile 1. A value 0 indicates to … |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.5 | ccsUpSpecMgmtFecCorrectThres2 | 0 | 0 | The FEC correctable count threshold. This object is applicable for profile 2. When CMTS detects that FEC correctable count goes … |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.6 | ccsUpSpecMgmtFecUnCorrectThres1 | 0 | 0 | The FEC uncorrectable count threshold. This object is applicable for modulation profile 1. A value 0 indicates to bypass the thr… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.7 | ccsUpSpecMgmtFecUnCorrectThres2 | 0 | 0 | The FEC uncorrectable count threshold. This object is applicable for modulation profile 2. A value 0 indicates to bypass the thr… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.8 | ccsUpSpecMgmtSnrPollPeriod | 0 | 0 | A period between SNR pollings. The SNR is collected from the Fast Fourier Transform (FFT) measurement over the in-use band when t… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.9 | ccsUpSpecMgmtHopCondition | 0 | 0 | A condition that triggers hopping. The SNR condition occurs when SNR does not meet the ccsUpSpecMgmtSnrThres1 or ccsUpSpecMgmtSnr… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.10 | ccsUpSpecMgmtFromCenterFreq | 0 | 0 | Center frequency before hopping occurs. A value 0 indicates that the interface has no frequency assigned. |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.11 | ccsUpSpecMgmtToCenterFreq | 0 | 0 | Current center frequency. A value 0 indicates that the interface has no frequency assigned. |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.12 | ccsUpSpecMgmtFromBandWidth | 0 | 0 | Bandwidth before hopping occurs. |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.13 | ccsUpSpecMgmtToBandWidth | 0 | 0 | Current bandwidth. |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.14 | ccsUpSpecMgmtFromModProfile | 0 | 0 | Modulation profile index before hopping occurs. It is the index identical to the docsIfModIndex in the docsIfCmtsModulationTable.… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.15 | ccsUpSpecMgmtToModProfile | 0 | 0 | The current modulation profile index. It is the index identical to the docsIfModIndex in the docsIfCmtsModulationTable. For the de… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.16 | ccsUpSpecMgmtSNR | 0 | 0 | Current SNR. A value -99 indicates the system detected no modem on line, and a value of -100 indicates the system was unable to re… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.17 | ccsUpSpecMgmtUpperBoundFreq | 0 | 0 | Upper bound frequency that the upstream supports. |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.18 | ccsUpSpecMgmtCnrThres1 | 0 | 0 | The Carrier to Noise (CNR) threshold. This object is applicable for modulation profile 1. When the CMTS detects that the CNR goe… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.19 | ccsUpSpecMgmtCnrThres2 | 0 | 0 | The Carrier to Noise (CNR) threshold. This object is applicable for modulation profile 2. Refer to ccsUpSpecMgmtCriteria on how c… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.20 | ccsUpSpecMgmtCNR | 0 | 0 | Current CNR. A value -99 indicates the system detected no modem on line, and a value of -100 indicates the system was unable to re… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.21 | ccsUpSpecMgmtMissedMaintMsgThres | 0 | 0 | The missed maintenance message threshold in percentage. A value 0 indicates that the interface has no spectrum group assigned. i.… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.22 | ccsUpSpecMgmtHopPeriod | 0 | 0 | The minimum time between frequency hops in seconds. A value 0 indicates that the interface has no spectrum group assigned. i.e. c… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.24 | ccsUpSpecMgmtSpecGroup | 0 | 0 | The spectrum group assigned to the upstream. The value of 0 for the object indicates that the upstream has no spectrum group assi… |
| 1.3.6.1.4.1.9.9.114.1.3.1.1.25 | ccsUpSpecMgmtSharedSpectrum | 0 | 0 | The fiber-node assigned to the upstreams. Upstreams having same fiber-node number indicates that they physically combine together… |