📄 rfc1232.txt
字号:
RFC 1232 DS1 Interface Objects May 1991 Unavailable Seconds, as defined by ANSI Draft Standard T1M1.3/90 - 027R2[15], encountered by a DS1 CSU in the previous 24 hour interval." ::= { ds1TotalEntry 5 } ds1TotalCSSs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The counter associated with the number of Controlled Slip Seconds, as defined by ANSI Draft Standard T1M1.3/90 - 027R2[15], encountered by a DS1 CSU in the previous 24 hour interval." ::= { ds1TotalEntry 6 } ds1TotalBPVs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The counter associated with the number of Bipolar Violations, as defined by ANSI Draft Standard T1M1.3/90 - 027R2[15], encountered by a DS1 CSU in the previous 24 hour interval." ::= { ds1TotalEntry 7 } ds1TotalCVs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The counter associated with the number of Code Violation Error Events, as defined by ANSI Draft Standard T1M1.3/90 - 027R2[15], encountered by a DS1 CSU in the previous 24 hour interval. Note that D4 and G.704 (section 2.1.3.2) interfaces do not support Code Violation Error Events. Accordingly, such agents may treat this object as having an ACCESS clause value of not- accessible." ::= { ds1TotalEntry 8 } -- the DS1 Fractional group -- Implementation of this group is mandatory for thoseTransmission MIB Working Group [Page 22]RFC 1232 DS1 Interface Objects May 1991 -- systems utilizing a fractional DS1 capability -- The DS1 fractional table contains identifies which DS1 -- channels associated with a CSU are being used to support a -- logical interface, i.e., an entry in the interfaces table -- from the Internet-standard MIB. For Clear Channel -- implementations, exactly one ifTable entry corresponds to -- the CSU being managed. In this very typical case, the -- variable ds1Index indicates the value of ifIndex which -- corresponds to the interface being supported by a -- particular CSU. -- However, for fractional DS1 implementations, the -- correspondent value of ds1Index is 0, and for each DS1 -- channel supporting a logical interface, there is an entry -- in the DS1 fractional table which names a value for -- ifIndex. -- -- For ds1ESF, ds1D4, and ds1ANSI-ESF, there are 24 legal -- channels, numbered 1 through 24. -- -- For G.704, there are 32 legal channels, numbered 1 -- through 32. ds1G704 can carry user data in channels 2 -- through 32, channel 1 being an overhead channel. -- ds1G704-CRC can carry user data in channels 2 through -- 16 and 18 through 32, channels 1 and 17 being overhead -- channels. ds1FracTable OBJECT-TYPE SYNTAX SEQUENCE OF DS1FracEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The DS1 Fractional table." ::= { ds1 5 } ds1FracEntry OBJECT-TYPE SYNTAX DS1FracEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry in the DS1 Fractional table." INDEX { ds1FracIndex, ds1FracNumber } ::= { ds1FracTable 1 } DS1FracEntry ::= SEQUENCE {Transmission MIB Working Group [Page 23]RFC 1232 DS1 Interface Objects May 1991 ds1FracIndex INTEGER, ds1FracNumber INTEGER (1..32), ds1FracIfIndex INTEGER } ds1FracIndex 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." ::= { ds1FracEntry 1 } ds1FracNumber OBJECT-TYPE SYNTAX INTEGER (1..32) ACCESS read-only STATUS mandatory DESCRIPTION "The channel number for this entry." ::= { ds1FracEntry 2 } ds1FracIfIndex 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." ::= { ds1FracEntry 3 } ENDTransmission MIB Working Group [Page 24]RFC 1232 DS1 Interface Objects May 19916. Acknowledgements This document was produced by the SNMP and the Transmission MIB Working Groups: Anne Ambler, Spider Karl Auerbach, Sun Fred Baker, ACC Ken Brinkerhoff Ron Broersma, NOSC Jack Brown, US Army Theodore Brunner, Bellcore Jeffrey Buffum, HP Jeffrey D. Case, UTK Chris Chiptasso, Spartacus Paul Ciarfella, DEC Bob Collet Tracy Cox, Bellcore James R. Davin, MIT-LCS Kurt Dobbins, Cabletron Nadya El-Afandi, Network Systems Gary Ellis, HP Fred Engle Mike Erlinger Richard Fox, Synoptics Karen Frisa, CMU Chris Gunner, DEC Ken Hibbard, Xylogics Ole Jacobsen, Interop Ken Jones Satish Joshi, Synoptics Frank Kastenholz, Racal-Interlan Shimshon Kaufman, Spartacus Jim Kinder, Fibercom Alex Koifman, BBN Christopher Kolb, PSI Cheryl Krupczak, NCR Peter Lin, Vitalink John Lunny, TWG Carl Malamud Keith McCloghrie, HLS Donna McMaster, David Systems Lynn Monsanto, Sun Dave Perkins, 3COM Jim Reinstedler, Ungerman Bass Anil Rijsinghani, DEC Kary Robertson Marshall T. Rose, PSI (chair)Transmission MIB Working Group [Page 25]RFC 1232 DS1 Interface Objects May 1991 L. Michael Sabo, NCSC Jon Saperia, DEC John Seligson Fei Shu, NEC Sam Sjogren, TGV Mark Sleeper, Sparta Lance Sprung Mike St.Johns Bob Stewart, Xyplex Emil Sturniold Kaj Tesink, Bellcore Dean Throop, Data General Bill Townsend, Xylogics Maurice Turcotte Kannan Varadhou Sudhanshu Verma, HP Warren Vik, Interactive Systems David Waitzman, BBN Steve Waldbusser, CMU Dan Wintringhan David Wood Jeff Young, Cray Research7. References [1] Cerf, V., "IAB Recommendations for the Development of Internet Network Management Standards", RFC 1052, NRI, April 1988. [2] Cerf, V., "Report of the Second Ad Hoc Network Management Review Group", RFC 1109, NRI, August 1989. [3] Rose M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [4] McCloghrie K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1156, Hughes LAN Systems, Performance Systems International, May 1990. [5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [6] McCloghrie K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1213, Performance Systems International, March 1991.Transmission MIB Working Group [Page 26]RFC 1232 DS1 Interface Objects May 1991 [7] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987. [8] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987. [9] AT&T Information Systems, AT&T ESF DS1 Channel Service Unit User's Manual, 999-100-305, February 1988. [10] AT&T Technical Reference, Requirements for Interfacing Digital Terminal Equipment to Services Employing the Extended Superframe Format, Publication 54016, May 1988. [11] CCITT Specifications Volume III, Recommendation G.703, Physical/Electrical Characteristics of Hierarchical Digital Interfaces, July 1988. [12] CCITT Specifications Volume III, Recommendation G.704, Synchronous frame structures used at primary and secondary hierarchical levels, July 1988. [13] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. [14] ANSI T1.403-1989 American National Standard for Telecommunications -- Carrier-to-Customer Installation -- DS1 Metallic Interface. [15] ANSI T1M1.3/90 - 027R2 Draft Proposed Standard -- Description of Installation and Maintenance Parameters for Digital Circuits, Facilities, and Networks. [16] Bell System Techical Reference, Publication 62411, High Capacity Digital Service Channel Interface Specification, September 1983. [17] Bell System Technical Reference, Publication 43801, "Digital Channel Bank Requirements and Objectives", November 1982.8. Security Considerations Security issues are not discussed in this memo.Transmission MIB Working Group [Page 27]RFC 1232 DS1 Interface Objects May 19919. Authors' Addresses Fred Baker Advanced Computer Communications, Inc. 720 Santa Barbara Street Santa Barbara, California 93101 Phone: (805) 963 9431 EMail: fbaker@acc.com Christopher P. Kolb Performance Systems International, Inc. Reston International Center 11800 Sunrise Valley Drive Suite 1100 Reston, VA 22091 Phone: (703) 620-6651 EMail: kolb@psi.comTransmission MIB Working Group [Page 28]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -