📄 rfc1232.txt
字号:
Transmission MIB Working Group [Page 7]RFC 1232 DS1 Interface Objects May 1991 ds1CircuitIdentifier DisplayString (SIZE (0..255)) } ds1CSUIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The index value which uniquely identifies the CSU to which this entry is applicable." ::= { ds1ConfigEntry 1 } ds1Index OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "An index value that uniquely identifies an interface to a ds1. The interface identified by a particular value of this index is the same interface as identified by the same value an ifIndex object instance." ::= { ds1ConfigEntry 2 } ds1TimeElapsed OBJECT-TYPE SYNTAX INTEGER (1..900) ACCESS read-only STATUS mandatory DESCRIPTION "The number of seconds that have elapsed since the beginning of the current error-measurement period. Any fraction is rounded up." ::= { ds1ConfigEntry 3 } ds1ValidIntervals OBJECT-TYPE SYNTAX INTEGER (0..96) ACCESS read-only STATUS mandatory DESCRIPTION "The number of previous intervals for which valid data was collected. The value will be 96 unless the CSU device was brought online within the last 24 hours, in which case the value will be the number of complete 15 minute intervals the CSU has been online." ::= { ds1ConfigEntry 4 }Transmission MIB Working Group [Page 8]RFC 1232 DS1 Interface Objects May 1991 ds1LineType OBJECT-TYPE SYNTAX INTEGER { other(1), ds1ESF(2), ds1D4(3), ds1ANSI-ESF(4), ds1G704(5), ds1G704-CRC(6) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the variety of DS1 Line implementing this circuit. The type of circuit affects the number of bits per second that the circuit can reasonably carry, as well as the interpretation of the usage and error statistics. The values, in sequence, describe: TITLE: SPECIFICATION: ds1ESF AT&T Extended SuperFrame DS1 [10] ds1D4 AT&T D4 format DS1 [16], [17] ds1ANSI-ESF ANSI Extended SuperFrame format [14] ds1G704 CCITT Recommendation G.704 [12] (section 2.1.3.2) ds1G704-CRC CCITT Recommendation G.704 [12] (section 2.1.3.1) " ::= { ds1ConfigEntry 5 } ds1ZeroCoding OBJECT-TYPE SYNTAX INTEGER { ds1JammedBit(1), ds1B8ZS(2), ds1InvertedHDLC(3), ds1HDB3(4), ds1ZBTSI(5) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable describes the variety of Zero Code Suppression used on the link, which in turn affects a number of its characteristics. ds1JammedBit refers the Jammed bit Zero Encoding, in which the AT&T specification of at least one pulse every 8 bit periods is literally implementedTransmission MIB Working Group [Page 9]RFC 1232 DS1 Interface Objects May 1991 by forcing a pulse in bit 8 of each channel. Thus, only seven bits per channel, or 1.344 Mbps, is available for data. ds1B8ZS refers to the use of a specified pattern of normal bits and bipolar violations which are used to replace a sequence of eight zero bits (see [14]). In this context, all eight bits in a channel are technically available for data, but care must be taken with D4 encoded data to avoid having HDLC Flag streams imitate spurious Yellow Alarm conditions. Typically, one bit per frame is ignored to force flag streams to rotate, thereby avoiding this error type. CCITT Recommendation G.703 [11] may be referred to for further definition of these. ds1InvertedHDLC refers to the practice, common on HDLC encoded DS1 data links, of inverting the data between the serial interface chip and the CSU. Since HDLC guarantees one zero every 6 bits in the worst case, while the standards call for (in effect) at least one pulse every eight, inverted HDLC enjoys 4/24 one's density on the line, which may improve the effective clock stability of a DS1 line. As with B8ZS, all eight bits in a channel are technically available for data, but care must be taken with D4 encoded data to avoid having HDLC Flag streams imitate spurious Yellow Alarm conditions. Typically, one bit per frame is ignored to force flag streams to rotate, thereby avoiding this error type. ANSI Clear Channels may use ds1ZBTSI, or Zero Byte Time Slot Interchange (see [14]). G.704 links, with or without CRC, use ds1HDB3 (see [11]). " ::= { ds1ConfigEntry 6 } ds1Loopback OBJECT-TYPE SYNTAX INTEGER { ds1NoLoop(1), ds1LocalLoopbackLocalSide(2), ds1LocalLoopbackRemoteSide(3), ds1RemoteLoopbackLocalSide(4), ds1RemoteLoopbackRemoteSide(5) }Transmission MIB Working Group [Page 10]RFC 1232 DS1 Interface Objects May 1991 ACCESS read-only STATUS mandatory DESCRIPTION "This variable represents the loopback state of the CSU. Devices supporting read/write access should return badValue in response to a requested loopback state that the CSU does not support. The values mean: ds1NoLoop Not in the loopback state. A device that is not capable of performing a loopback on either interface shall always return this as it's value. ds1LocalLoopbackLocalSide Signal received from the local side of the device is looped back at the local connector (eg, without involving the CSU). ds1LocalLoopbackRemoteSide Signal received from the local side of the device is looped back at the remote connector (eg, through the CSU). ds1RemoteLoopbackLocalSide Signal received from the remote side of the device is looped back at the local connector (eg, through the CSU). ds1RemoteLoopbackRemoteSide Signal received from the remote side of the device is looped back at the remote connector (eg, without involving the CSU)." ::= { ds1ConfigEntry 7 } ds1SendCode OBJECT-TYPE SYNTAX INTEGER { ds1OtherTest(1), ds1SendNoCode(2), ds1SendSetCode(3), ds1SendResetCode(4), ds1SendQRSS(5)Transmission MIB Working Group [Page 11]RFC 1232 DS1 Interface Objects May 1991 } ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates what type of code is being sent across the DS1 circuit by the CSU. The values mean: ds1SendNoCode sending looped or normal data ds1SendSetCode sending a loopback request ds1SendResetCode sending a loopback termination request ds1SendQRSS sending the BERT pattern described in ANSI T1.403-1989 section 5.6 ds1OtherTest sending a different BERT/BLERT pattern, such as all zeroes, all ones, etc." ::= { ds1ConfigEntry 8 } ds1YellowAlarm OBJECT-TYPE SYNTAX INTEGER { ds1NoYellowAlarm (1), ds1YellowAlarm (2) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates if a Yellow Alarm condition exists. Note that G.704 interfaces do not support Yellow Alarms. Accordingly, such agents should return the value ds1NoYellowAlarm." ::= { ds1ConfigEntry 9 } ds1RedAlarm OBJECT-TYPE SYNTAX INTEGER { ds1NoRedAlarm (1), ds1RedAlarm (2) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates if a Red Alarm condition exists. Note that G.704 interfaces do not support Red Alarms. Accordingly, such agents should return the value ds1NoRedAlarm." ::= { ds1ConfigEntry 10 }Transmission MIB Working Group [Page 12]RFC 1232 DS1 Interface Objects May 1991 ds1CircuitIdentifier OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting." ::= { ds1ConfigEntry 11 } -- the DS1 Interval group -- Implementation of this group is mandatory for all systems -- that attach to a ds1. -- It is recognized that some currently deployed CSUs do not -- record the entire set of statistics specified in this -- group. Accordingly, some agents queried for these objects -- may treat these objects as having an ACCESS clause value -- of not-accessible. -- The DS1 Interval Table contains various statistics -- collected by each CSU over the previous 24 hours of -- operation. The past 24 hours are broken into 96 completed -- 15 minute intervals. ds1IntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF DS1IntervalEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The DS1 Interval table." ::= { ds1 2 } ds1IntervalEntry OBJECT-TYPE SYNTAX DS1IntervalEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry in the DS1 Interval table." INDEX { ds1IntervalIndex, ds1IntervalNumber } ::= { ds1IntervalTable 1 } DS1IntervalEntry ::= SEQUENCE { ds1IntervalIndex INTEGER,Transmission MIB Working Group [Page 13]RFC 1232 DS1 Interface Objects May 1991 ds1IntervalNumber INTEGER (1..96), ds1IntervalESs Counter, ds1IntervalSESs Counter, ds1IntervalSEFSs Counter, ds1IntervalUASs Counter, ds1IntervalCSSs Counter, ds1IntervalBPVs Counter, ds1IntervalCVs Counter } ds1IntervalIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The index value which uniquely identifies the CSU to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value an ds1CSUIndex object instance." ::= { ds1IntervalEntry 1 } ds1IntervalNumber OBJECT-TYPE SYNTAX INTEGER (1..96) ACCESS read-only STATUS mandatory DESCRIPTION "A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the least recently completed 15 minute interval (assuming that all 96 intervals are valid)." ::= { ds1IntervalEntry 2 } ds1IntervalESs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The counter associated with the number of Errored Seconds, as defined by ANSI Draft StandardTransmission MIB Working Group [Page 14]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -