The value of this object indicates the conformance of
the implementation to important regional cable standards.
annexA : Annex A from ITU-T J.83 is used.
(equivalent to EN 300 429)
annexB : Annex B from ITU-T J.83 is used.
annexC : Annex C from ITU-T J.83 is used.
Parsed from file DOCS-IF-MIB.mib
Module: DOCS-IF-MIB
The value of this object indicates the conformance of
the implementation to important regional cable standards.
annexA : Annex A from ITU-T J.83 is used.
(equivalent to EN 300 429)
annexB : Annex B from ITU-T J.83 is used.
annexC : Annex C from ITU-T J.83 is used.
docsIfDownChannelAnnex OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
other(2),
annexA(3),
annexB(4),
annexC(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object indicates the conformance of
the implementation to important regional cable standards.
annexA : Annex A from ITU-J83 is used.
annexB : Annex B from ITU-J83 is used.
annexC : Annex C from ITU-J83 is used.
AnnexB is used for DOCSIS implementations"
REFERENCE
"Document [28] from References, Section 2.2"
View at oid-info.com
The value of this object indicates the conformance of
the implementation to important regional cable standards.
annexA : Annex A from ITU-T J.83 is used.
(equivalent to EN 300 429)
annexB : Annex B from ITU-T J.83 is used.
annexC : Annex C from ITU-T J.83 is used.
Parsed from file DOCS-IF-MIB.txt
Company: None
Module: DOCS-IF-MIB
The value of this object indicates the conformance of
the implementation to important regional cable standards.
annexA : Annex A from ITU-T J.83 is used.
(equivalent to EN 300 429)
annexB : Annex B from ITU-T J.83 is used.
annexC : Annex C from ITU-T J.83 is used.
docsIfDownChannelAnnex OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), annexA(3), annexB(4), annexC(5) } ACCESS read-only STATUS mandatory DESCRIPTION "The value of this object indicates the conformance of the implementation to important regional cable standards. annexA : Annex A from ITU-T J.83 is used. (equivalent to EN 300 429) annexB : Annex B from ITU-T J.83 is used. annexC : Annex C from ITU-T J.83 is used." REFERENCE "Data-Over-Cable Service Interface Specifications: Radio Frequency Interface Specification SP-RFIv2.0-I10-051209, Sections 6.3.1, and H.3.1." ::= { docsIfDownstreamChannelEntry 7 }
docsIfDownChannelAnnex OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), annexA(3), annexB(4), annexC(5) } ACCESS read-only STATUS mandatory DESCRIPTION "The value of this object indicates the conformance of the implementation to important regional cable standards. annexA : Annex A from ITU-T J.83 is used. (equivalent to EN 300 429) annexB : Annex B from ITU-T J.83 is used. annexC : Annex C from ITU-T J.83 is used." REFERENCE "Data-Over-Cable Service Interface Specifications: Radio Frequency Interface Specification SP-RFIv2.0-I10-051209, Sections 6.3.1, and H.3.1." ::= { docsIfDownstreamChannelEntry 7 }
Automatically extracted from Cisco "SNMP v2 MIBs".
docsIfDownChannelAnnex OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), annexA(3), annexB(4), annexC(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the conformance of the implementation to important regional cable standards. annexA : Annex A from ITU-T J.83 is used. (equivalent to EN 300 429) annexB : Annex B from ITU-T J.83 is used. annexC : Annex C from ITU-T J.83 is used." REFERENCE "Data-Over-Cable Service Interface Specifications: Radio Frequency Interface Specification SP-RFIv2.0-I10-051209, Sections 6.3.1, and H.3.1." ::= { docsIfDownstreamChannelEntry 7 }
docsIfDownChannelAnnex OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), annexA(3), annexB(4), annexC(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the conformance of the implementation to important regional cable standards. annexA : Annex A from ITU-T J.83 is used. (equivalent to EN 300 429) annexB : Annex B from ITU-T J.83 is used. annexC : Annex C from ITU-T J.83 is used." REFERENCE "Data-Over-Cable Service Interface Specifications: Radio Frequency Interface Specification SP-RFIv2.0-I10-051209, Sections 6.3.1, and H.3.1." ::= { docsIfDownstreamChannelEntry 7 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.127.1.1.1.1.1 | docsIfDownChannelId | 0 | 0 | The Cable Modem Termination System identification of the downstream channel within this particular MAC interface. if the interfac… |
| 1.3.6.1.2.1.10.127.1.1.1.1.2 | docsIfDownChannelFrequency | 0 | 0 | The center of the downstream frequency associated with this channel. This object will return the current tuner frequency. If a … |
| 1.3.6.1.2.1.10.127.1.1.1.1.3 | docsIfDownChannelWidth | 0 | 0 | The bandwidth of this downstream channel. Most implementations are expected to support a channel width of 6 MHz (North America) a… |
| 1.3.6.1.2.1.10.127.1.1.1.1.4 | docsIfDownChannelModulation | 0 | 0 | The modulation type associated with this downstream channel. If the interface is down, this object either returns the configured … |
| 1.3.6.1.2.1.10.127.1.1.1.1.5 | docsIfDownChannelInterleave | 0 | 0 | The Forward Error Correction (FEC) interleaving used for this downstream channel. Values are defined as follows: taps8Increment16(… |
| 1.3.6.1.2.1.10.127.1.1.1.1.6 | docsIfDownChannelPower | 0 | 0 | At the CMTS, the operational transmit power. At the CM, the received power level. If the interface is down, this object either r… |
| 1.3.6.1.2.1.10.127.1.1.1.1.8 | docsIfDownChannelStorageType | 0 | 0 | The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-w… |