⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2670.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 5 页
字号:
docsIfDownChannelFrequency  OBJECT-TYPE        SYNTAX      Integer32 (0..1000000000)        UNITS       "hertz"        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The center of the downstream frequency associated with             this channel. This object will return the current tuner             frequency. If a CMTS provides IF output, this object             will return 0, unless this CMTS is in control of the             final downstream RF frequency.  See the associatedSt. Johns                       Standard                       [Page 20]RFC 2670                DOCSIS RF Interface MIB              August 1999             compliance object for a description of valid frequencies             that may be written to this object."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 4.3.3."        ::= { docsIfDownstreamChannelEntry 2 }docsIfDownChannelWidth  OBJECT-TYPE        SYNTAX      Integer32 (0..16000000)        UNITS       "hertz"        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The bandwidth of this downstream channel. Most             implementations are expected to support a channel width             of 6 MHz (North America) and/or 8 MHz (Europe).  See the             associated compliance object for a description of the             valid channel widths for this object."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Table 4-12 and Table 4-13."        ::= { docsIfDownstreamChannelEntry 3 }docsIfDownChannelModulation OBJECT-TYPE        SYNTAX      INTEGER {            unknown(1),            other(2),            qam64(3),            qam256(4)        }        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The modulation type associated with this downstream             channel. If the interface is down, this object either             returns the configured value (CMTS), the most current             value (CM), or the value of unknown(1).  See the             associated conformance object for write conditions and             limitations. See the reference for specifics on the             modulation profiles implied by qam64 and qam256."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 3.6.2."        ::= { docsIfDownstreamChannelEntry 4 }docsIfDownChannelInterleave OBJECT-TYPE        SYNTAX      INTEGER {            unknown(1),St. Johns                       Standard                       [Page 21]RFC 2670                DOCSIS RF Interface MIB              August 1999            other(2),            taps8Increment16(3),            taps16Increment8(4),            taps32Increment4(5),            taps64Increment2(6),            taps128Increment1(7)        }        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The Forward Error Correction (FEC) interleaving used             for this downstream channel.             Values are defined as follows:             taps8Increment16(3):   protection 5.9/4.1 usec,                                    latency .22/.15 msec             taps16Increment8(4):   protection 12/8.2 usec,                                    latency .48/.33 msec             taps32Increment4(5):   protection 24/16 usec,                                    latency .98/.68 msec             taps64Increment2(6):   protection 47/33 usec,                                    latency 2/1.4 msec             taps128Increment1(7):  protection 95/66 usec,                                    latency 4/2.8 msec             If the interface is down, this object either returns             the configured value (CMTS), the most current value (CM),             or the value of unknown(1).             The value of other(2) is returned if the interleave             is known but not defined in the above list.             See the associated conformance object for write             conditions and limitations. See the reference for the FEC             configuration described by the setting of this object."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 4.3.2."        ::= { docsIfDownstreamChannelEntry 5 }docsIfDownChannelPower OBJECT-TYPE        SYNTAX      TenthdBmV        UNITS       "dBmV"        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "At the CMTS, the operational transmit power. At the CM,             the received power level. May be set to zero at the CM             if power level measurement is not supported.             If the interface is down, this object either returns             the configured value (CMTS), the most current value (CM)             or the value of 0. See the associated conformance objectSt. Johns                       Standard                       [Page 22]RFC 2670                DOCSIS RF Interface MIB              August 1999             for write conditions and limitations. See the reference             for recommended and required power levels."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Table 4-12 and Table 4-13."        ::= { docsIfDownstreamChannelEntry 6 }---- The following table is implemented on both the CM and the CMTS.-- For the CM, only attached channels appear in the table.  For the-- CM, this table is read only as well.--docsIfUpstreamChannelTable OBJECT-TYPE        SYNTAX      SEQUENCE OF DocsIfUpstreamChannelEntry        MAX-ACCESS  not-accessible        STATUS      current        DESCRIPTION            "This table describes the attributes of attached upstream             channels (frequency bands)."        ::= { docsIfBaseObjects 2 }docsIfUpstreamChannelEntry OBJECT-TYPE        SYNTAX      DocsIfUpstreamChannelEntry        MAX-ACCESS  not-accessible        STATUS      current        DESCRIPTION            "List of attributes for a single upstream channel.             An entry in this table exists for each ifEntry with an             ifType of docsCableUpstream(129)."        INDEX { ifIndex }        ::= { docsIfUpstreamChannelTable 1 }DocsIfUpstreamChannelEntry ::= SEQUENCE {            docsIfUpChannelId                     Integer32,            docsIfUpChannelFrequency              Integer32,            docsIfUpChannelWidth                  Integer32,            docsIfUpChannelModulationProfile      Unsigned32,            docsIfUpChannelSlotSize               Unsigned32,            docsIfUpChannelTxTimingOffset         Unsigned32,            docsIfUpChannelRangingBackoffStart    Integer32,            docsIfUpChannelRangingBackoffEnd      Integer32,            docsIfUpChannelTxBackoffStart         Integer32,            docsIfUpChannelTxBackoffEnd           Integer32        }docsIfUpChannelId OBJECT-TYPE        SYNTAX      Integer32 (0..255)St. Johns                       Standard                       [Page 23]RFC 2670                DOCSIS RF Interface MIB              August 1999        MAX-ACCESS  read-only        STATUS      current        DESCRIPTION            "The CMTS identification of the upstream channel."        ::= { docsIfUpstreamChannelEntry 1 }docsIfUpChannelFrequency OBJECT-TYPE        SYNTAX      Integer32 (0..1000000000)        UNITS       "hertz"        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The center of the frequency band associated with this             upstream channel. This object returns 0 if the frequency             is undefined or unknown. Minimum permitted upstream             frequency is 5,000,000 Hz for current technology.  See             the associated conformance object for write conditions             and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Table 2-2."        ::= { docsIfUpstreamChannelEntry 2 }docsIfUpChannelWidth OBJECT-TYPE        SYNTAX      Integer32 (0..20000000)        UNITS       "hertz"        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The bandwidth of this upstream channel. This object             returns 0 if the channel width is undefined or unknown.             Minimum permitted channel width is 200,000 Hz currently.             See the associated conformance object for write conditions             and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Table 4-3."        ::= { docsIfUpstreamChannelEntry 3 }docsIfUpChannelModulationProfile OBJECT-TYPE        SYNTAX      Unsigned32        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "An entry identical to the docsIfModIndex in the             docsIfCmtsModulationTable that describes this channel.             This channel is further instantiated there by a grouping             of interval usage codes which together fully describe theSt. Johns                       Standard                       [Page 24]RFC 2670                DOCSIS RF Interface MIB              August 1999             channel modulation. This object returns 0 if the             docsIfCmtsModulationTable entry does not exist or             docsIfCmtsModulationTable is empty. See             the associated conformance object for write conditions             and limitations."        ::= { docsIfUpstreamChannelEntry 4 }docsIfUpChannelSlotSize OBJECT-TYPE        SYNTAX      Unsigned32        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The number of 6.25 microsecond ticks in each upstream mini-             slot. Returns zero if the value is undefined or unknown.             See the associated conformance object for write             conditions and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 6.1.2.4."        ::= { docsIfUpstreamChannelEntry 5 }docsIfUpChannelTxTimingOffset OBJECT-TYPE        SYNTAX      Unsigned32        MAX-ACCESS  read-only        STATUS      current        DESCRIPTION            "A measure of the current round trip time at the CM, or the             maximum round trip time seen by the CMTS.  Used for timing             of CM upstream transmissions to ensure synchronized             arrivals at the CMTS. Units are in terms of             (6.25 microseconds/64)."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 6.5."        ::= { docsIfUpstreamChannelEntry 6 }docsIfUpChannelRangingBackoffStart OBJECT-TYPE        SYNTAX      Integer32 (0..16)        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The initial random backoff window to use when retrying             Ranging Requests. Expressed as a power of 2. A value of 16             at the CMTS indicates that a proprietary adaptive retry             mechanism is to be used. See the associated conformance             object for write conditions and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,St. Johns                       Standard                       [Page 25]RFC 2670                DOCSIS RF Interface MIB              August 1999             Section 6.4.4."        ::= { docsIfUpstreamChannelEntry 7 }docsIfUpChannelRangingBackoffEnd OBJECT-TYPE        SYNTAX      Integer32 (0..16)        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The final random backoff window to use when retrying             Ranging Requests. Expressed as a power of 2. A value of 16             at the CMTS indicates that a proprietary adaptive retry             mechanism is to be used. See the associated conformance             object for write conditions and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 6.4.4."        ::= { docsIfUpstreamChannelEntry 8 }docsIfUpChannelTxBackoffStart OBJECT-TYPE        SYNTAX      Integer32 (0..16)        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The initial random backoff window to use when retrying             transmissions. Expressed as a power of 2. A value of 16             at the CMTS indicates that a proprietary adaptive retry             mechanism is to be used. See the associated conformance             object for write conditions and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 6.4.4."        ::= { docsIfUpstreamChannelEntry 9 }docsIfUpChannelTxBackoffEnd OBJECT-TYPE        SYNTAX      Integer32 (0..16)        MAX-ACCESS  read-write        STATUS      current        DESCRIPTION            "The final random backoff window to use when retrying             transmissions. Expressed as a power of 2. A value of 16             at the CMTS indicates that a proprietary adaptive retry             mechanism is to be used. See the associated conformance             object for write conditions and limitations."        REFERENCE            "DOCSIS Radio Frequency Interface Specification,             Section 6.4.4."        ::= { docsIfUpstreamChannelEntry 10 }St. Johns                       Standard                       [Page 26]RFC 2670                DOCSIS RF Interface MIB              August 1999-- The following table describes the attributes of each class of-- service.  The entries in this table are referenced from the-- docsIfServiceEntries.  They exist as a separate table in order to-- reduce redundant information in docsIfServiceTable.---- This table is implemented at both the CM and the CMTS.-- The CM need only maintain entries for the classes of service-- referenced by its docsIfServiceTable.--docsIfQosProfileTable OBJECT-TYPE        SYNTAX      SEQUENCE OF DocsIfQosProfileEntry        MAX-ACCESS  not-accessible        STATUS      current

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -