RFC4805 日本語訳
4805 Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2Interface Types. O. Nicklass, Ed.. March 2007. (Format: TXT=189927 bytes) (Obsoletes RFC3895) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
英語原文
Network Working Group O. Nicklass, Ed. Request for Comments: 4805 RAD Data Communications, Ltd. Obsoletes: 3895 March 2007 Category: Standards Track
Network Working Group O. Nicklass, Ed. Request for Comments: 4805 RAD Data Communications, Ltd. Obsoletes: 3895 March 2007 Category: Standards Track
Definitions of Managed Objects
for the DS1, J1, E1, DS2, and E2 Interface Types
Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2 Interface Types
Status of This Memo
Status of This Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright Notice
Copyright (C) The IETF Trust (2007).
Copyright (C) The IETF Trust (2007).
Abstract
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, J1, E1, DS2, and E2 interfaces. This document is a companion to the documents that define managed objects for the DS0, DS3/E3, and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Types.
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, J1, E1, DS2, and E2 interfaces. This document is a companion to the documents that define managed objects for the DS0, DS3/E3, and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Types.
This document obsoletes RFC 3895.
This document obsoletes RFC 3895.
Nicklass, Ed. Standards Track [Page 1] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 1] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Table of Contents
Table of Contents
1. The Internet-Standard Management Framework ......................2
2. Conventions Used in This Document ...............................3
3. Overview ........................................................3
3.1. Use of ifTable for DS1 Layer ...............................4
3.2. Usage Guidelines ...........................................5
3.2.1. Usage of ifStackTable for Routers and DSUs ..........5
3.2.2. Usage of ifStackTable for DS1/J1/E1 on DS2/E2 .......7
3.2.3. Usage of Channelization for DS3, DS1, DS0 ...........8
3.2.4. Usage of Channelization for DS3, DS2, DS1 ...........9
3.2.5. Usage of Loopbacks .................................10
3.3. Objectives of This MIB Module .............................10
3.4. DS1 Terminology ...........................................11
3.4.1. Error Events .......................................11
3.4.2. Performance Defects ................................12
3.4.3. Performance Parameters .............................13
3.4.4. Failure States .....................................17
3.4.5. Other Terms ........................................20
4. Object Definitions .............................................20
5. Security Considerations ........................................83
6. Acknowledgments ................................................84
7. References .....................................................84
7.1. Normative References ......................................84
7.2. Informative References ....................................86
Appendix A - Use of dsx1IfIndex and dsx1LineIndex .................88
Appendix B - The Delay Approach to Unavailable Seconds ............90
Appendix C - Changes from Previous Versions .......................92
C.1. Changes from RFC 3895 .....................................92
C.2. Changes from RFC 2495 .....................................92
C.3. Changes from RFC 1406 .....................................92
C.4. Companion Documents .......................................93
1. The Internet-Standard Management Framework ......................2 2. Conventions Used in This Document ...............................3 3. Overview ........................................................3 3.1. Use of ifTable for DS1 Layer ...............................4 3.2. Usage Guidelines ...........................................5 3.2.1. Usage of ifStackTable for Routers and DSUs ..........5 3.2.2. Usage of ifStackTable for DS1/J1/E1 on DS2/E2 .......7 3.2.3. Usage of Channelization for DS3, DS1, DS0 ...........8 3.2.4. Usage of Channelization for DS3, DS2, DS1 ...........9 3.2.5. Usage of Loopbacks .................................10 3.3. Objectives of This MIB Module .............................10 3.4. DS1 Terminology ...........................................11 3.4.1. Error Events .......................................11 3.4.2. Performance Defects ................................12 3.4.3. Performance Parameters .............................13 3.4.4. Failure States .....................................17 3.4.5. Other Terms ........................................20 4. Object Definitions .............................................20 5. Security Considerations ........................................83 6. Acknowledgments ................................................84 7. References .....................................................84 7.1. Normative References ......................................84 7.2. Informative References ....................................86 Appendix A - Use of dsx1IfIndex and dsx1LineIndex .................88 Appendix B - The Delay Approach to Unavailable Seconds ............90 Appendix C - Changes from Previous Versions .......................92 C.1. Changes from RFC 3895 .....................................92 C.2. Changes from RFC 2495 .....................................92 C.3. Changes from RFC 1406 .....................................92 C.4. Companion Documents .......................................93
1. The Internet-Standard Management Framework
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
Nicklass, Ed. Standards Track [Page 2] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 2] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
2. Conventions Used in This Document
2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
3. Overview
3. Overview
These objects are used when the particular media being used to realize an interface is a DS1/J1/E1/DS2/E2 interface. At present, this applies to the following value of the ifType variable in the Internet-standard MIB:
These objects are used when the particular media being used to realize an interface is a DS1/J1/E1/DS2/E2 interface. At present, this applies to the following value of the ifType variable in the Internet-standard MIB:
ds1 (18)
ds1 (18)
The definitions contained herein are based on the AT&T T-1 Superframe (a.k.a. D4) [ANSI-T1.107] and Extended Superframe (ESF) formats [AT&T-UM-305], [AT&T-TR-54016], the latter of which conforms to ANSI specifications [ANSI-T1.403], and the CCITT Recommendations [CCITT-G.703], [ITU-T-G.704], referred to as E1 for the rest of this memo. J1 refers to the definition presented in [JT-G704], [JT-G706], and [JT-I431].
The definitions contained herein are based on the AT&T T-1 Superframe (a.k.a. D4) [ANSI-T1.107] and Extended Superframe (ESF) formats [AT&T-UM-305], [AT&T-TR-54016], the latter of which conforms to ANSI specifications [ANSI-T1.403], and the CCITT Recommendations [CCITT-G.703], [ITU-T-G.704], referred to as E1 for the rest of this memo. J1 refers to the definition presented in [JT-G704], [JT-G706], and [JT-I431].
The various DS1, J1, and E1 line disciplines are similar enough that separate MIBs are unwarranted, although there are some differences. For example, Loss of Frame is defined more rigorously in the ESF specification than in the D4 specification, or Yellow Alarm generation and detection are a bit different between T1 and J1 but in both examples, there is definition in both related lines. Therefore, interface types e1(19) and g703at2mb(67) have been obsoleted and there is also no need for special type for J1.
The various DS1, J1, and E1 line disciplines are similar enough that separate MIBs are unwarranted, although there are some differences. For example, Loss of Frame is defined more rigorously in the ESF specification than in the D4 specification, or Yellow Alarm generation and detection are a bit different between T1 and J1 but in both examples, there is definition in both related lines. Therefore, interface types e1(19) and g703at2mb(67) have been obsoleted and there is also no need for special type for J1.
Where it is necessary to distinguish between the flavors of E1 with and without Cyclic Redundancy Check (CRC), E1-CRC denotes the "with CRC" form (G.704 Table 5B) and E1-noCRC denotes the "without CRC" form (G.704 Table 5A).
Where it is necessary to distinguish between the flavors of E1 with and without Cyclic Redundancy Check (CRC), E1-CRC denotes the "with CRC" form (G.704 Table 5B) and E1-noCRC denotes the "without CRC" form (G.704 Table 5A).
Nicklass, Ed. Standards Track [Page 3] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 3] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
3.1. Use of ifTable for DS1 Layer
3.1. Use of ifTable for DS1 Layer
Only the ifGeneralInformationGroup needs to be supported.
Only the ifGeneralInformationGroup needs to be supported.
ifTable Object Use for DS1 Layer
===================================================================
ifIndex Interface index.
ifTable Object Use for DS1 Layer =================================================================== ifIndex Interface index.
ifDescr See interfaces MIB [RFC2863].
ifDescr See interfaces MIB [RFC2863].
ifType ds1(18)
ifType ds1(18)
ifSpeed Speed of line rate
DS1 - 1544000
J1 - 1544000
E1 - 2048000
DS2 - 6312000
E2 - 8448000
ifSpeed Speed of line rate DS1 - 1544000 J1 - 1544000 E1 - 2048000 DS2 - 6312000 E2 - 8448000
ifPhysAddress The value of the Circuit Identifier.
If no Circuit Identifier has been assigned,
this object should have an octet string
with zero length.
ifPhysAddress The value of the Circuit Identifier. If no Circuit Identifier has been assigned, this object should have an octet string with zero length.
ifAdminStatus See interfaces MIB [RFC2863].
ifAdminStatus See interfaces MIB [RFC2863].
ifOperStatus See interfaces MIB [RFC2863].
ifOperStatus See interfaces MIB [RFC2863].
ifLastChange See interfaces MIB [RFC2863].
ifLastChange See interfaces MIB [RFC2863].
ifName See interfaces MIB [RFC2863].
ifName See interfaces MIB [RFC2863].
ifLinkUpDownTrapEnable Set to enabled(1).
ifLinkUpDownTrapEnable Set to enabled(1).
ifHighSpeed Speed of line in mega-bits per second
(2, 6, or 8).
ifHighSpeed Speed of line in mega-bits per second (2, 6, or 8).
ifConnectorPresent Set to true(1) normally, except for
cases such as DS1/E1 over AAL1/ATM where
false(2) is appropriate.
ifConnectorPresent Set to true(1) normally, except for cases such as DS1/E1 over AAL1/ATM where false(2) is appropriate.
Nicklass, Ed. Standards Track [Page 4] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 4] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
3.2. Usage Guidelines
3.2. Usage Guidelines
3.2.1. Usage of ifStackTable for Routers and DSUs
3.2.1. Usage of ifStackTable for Routers and DSUs
The object dsx1IfIndex has been deprecated. This object previously allowed a very special proxy situation to exist for routers and Channel Service Units (CSUs). This section now describes how to use the ifStackTable to represent this relationship.
The object dsx1IfIndex has been deprecated. This object previously allowed a very special proxy situation to exist for routers and Channel Service Units (CSUs). This section now describes how to use the ifStackTable to represent this relationship.
The paragraphs discussing dsx1IfIndex and dsx1LineIndex have been preserved in Appendix A for informational purposes.
The paragraphs discussing dsx1IfIndex and dsx1LineIndex have been preserved in Appendix A for informational purposes.
The ifStackTable is used in the proxy case to represent the association between pairs of interfaces, i.e., this T1 is attached to that T1. This use is consistent with the use of the ifStackTable to show the association between various sub-layers of an interface. In both cases, entire PDUs are exchanged between the interface pairs -- in the case of a T1, entire T1 frames are exchanged; in the case of PPP and High-Level Data Link Control (HDLC), entire HDLC frames are exchanged. This usage is not meant to suggest the use of the ifStackTable to represent Time Division Multiplexing (TDM) connections in general.
The ifStackTable is used in the proxy case to represent the association between pairs of interfaces, i.e., this T1 is attached to that T1. This use is consistent with the use of the ifStackTable to show the association between various sub-layers of an interface. In both cases, entire PDUs are exchanged between the interface pairs -- in the case of a T1, entire T1 frames are exchanged; in the case of PPP and High-Level Data Link Control (HDLC), entire HDLC frames are exchanged. This usage is not meant to suggest the use of the ifStackTable to represent Time Division Multiplexing (TDM) connections in general.
External and Internal interface scenario: the SNMP agent resides on a host external from the device supporting DS1 interfaces (e.g., a router). The agent represents both the host and the DS1 device.
External and Internal interface scenario: the SNMP agent resides on a host external from the device supporting DS1 interfaces (e.g., a router). The agent represents both the host and the DS1 device.
Nicklass, Ed. Standards Track [Page 5] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 5] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Example:
Example:
A shelf full of CSUs connected to a router. An SNMP agent residing on the router proxies for itself and the CSU. The router has also an Ethernet interface:
A shelf full of CSUs connected to a router. An SNMP agent residing on the router proxies for itself and the CSU. The router has also an Ethernet interface:
+-----+
| | |
| | | +---------------------+
|E | | 1.544 MBPS | Line#A | DS1 Link
|t | R |---------------+ - - - - - - - - - +------>
|h | | | |
|e | O | 1.544 MBPS | Line#B | DS1 Link
|r | |---------------+ - - - - - - - - - - +------>
|n | U | | CSU Shelf |
|e | | 1.544 MBPS | Line#C | DS1 Link
|t | T |---------------+ - - - -- -- - - - - +------>
| | | | |
|-----| E | 1.544 MBPS | Line#D | DS1 Link
| | |---------------+ - - - - -- - - - - +------>
| | R | |_____________________|
| | |
| +-----+
+-----+ | | | | | | +---------------------+ |E | | 1.544 MBPS | Line#A | DS1 Link |t | R |---------------+ - - - - - - - - - +------> |h | | | | |e | O | 1.544 MBPS | Line#B | DS1 Link |r | |---------------+ - - - - - - - - - - +------> |n | U | | CSU Shelf | |e | | 1.544 MBPS | Line#C | DS1 Link |t | T |---------------+ - - - -- -- - - - - +------> | | | | | |-----| E | 1.544 MBPS | Line#D | DS1 Link | | |---------------+ - - - - -- - - - - +------> | | R | |_____________________| | | | | +-----+
The assignment of the index values could, for example, be as follows:
The assignment of the index values could, for example, be as follows:
ifIndex Description
1 Ethernet
2 Line#A Router
3 Line#B Router
4 Line#C Router
5 Line#D Router
6 Line#A CSU Router
7 Line#B CSU Router
8 Line#C CSU Router
9 Line#D CSU Router
10 Line#A CSU Network
11 Line#B CSU Network
12 Line#C CSU Network
13 Line#D CSU Network
ifIndex Description 1 Ethernet 2 Line#A Router 3 Line#B Router 4 Line#C Router 5 Line#D Router 6 Line#A CSU Router 7 Line#B CSU Router 8 Line#C CSU Router 9 Line#D CSU Router 10 Line#A CSU Network 11 Line#B CSU Network 12 Line#C CSU Network 13 Line#D CSU Network
The ifStackTable is then used to show the relationships between the various DS1 interfaces.
The ifStackTable is then used to show the relationships between the various DS1 interfaces.
Nicklass, Ed. Standards Track [Page 6] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 6] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
ifStackTable Entries
ifStackTable Entries
HigherLayer LowerLayer
2 6
3 7
4 8
5 9
6 10
7 11
8 12
9 13
HigherLayer LowerLayer 2 6 3 7 4 8 5 9 6 10 7 11 8 12 9 13
If the CSU shelf is managed by itself by a local SNMP agent, the situation would be identical, except the Ethernet and the four router interfaces are deleted. Interfaces would also be numbered from 1 to 8.
If the CSU shelf is managed by itself by a local SNMP agent, the situation would be identical, except the Ethernet and the four router interfaces are deleted. Interfaces would also be numbered from 1 to 8.
ifIndex Description
1 Line#A CSU Router
2 Line#B CSU Router
3 Line#C CSU Router
4 Line#D CSU Router
5 Line#A CSU Network
6 Line#B CSU Network
7 Line#C CSU Network
8 Line#D CSU Network
ifIndex Description 1 Line#A CSU Router 2 Line#B CSU Router 3 Line#C CSU Router 4 Line#D CSU Router 5 Line#A CSU Network 6 Line#B CSU Network 7 Line#C CSU Network 8 Line#D CSU Network
ifStackTable Entries
ifStackTable Entries
HigherLayer LowerLayer
1 5
2 6
3 7
4 8
HigherLayer LowerLayer 1 5 2 6 3 7 4 8
3.2.2. Usage of ifStackTable for DS1/J1/E1 on DS2/E2
3.2.2. Usage of ifStackTable for DS1/J1/E1 on DS2/E2
An example is given of how DS1/J1/E1 interfaces are stacked on DS2/E2 interfaces. It is not necessary nor is it always desirable to represent DS2 interfaces. If this is required, the following stacking should be used. All ifTypes are ds1. The DS2 is determined by examining ifSpeed or dsx1LineType.
An example is given of how DS1/J1/E1 interfaces are stacked on DS2/E2 interfaces. It is not necessary nor is it always desirable to represent DS2 interfaces. If this is required, the following stacking should be used. All ifTypes are ds1. The DS2 is determined by examining ifSpeed or dsx1LineType.
Nicklass, Ed. Standards Track [Page 7] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 7] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
ifIndex Description
1 DS1 #1
2 DS1 #2
3 DS1 #3
4 DS1 #4
5 DS2
ifIndex Description 1 DS1 #1 2 DS1 #2 3 DS1 #3 4 DS1 #4 5 DS2
ifStackTable Entries
ifStackTable Entries
HigherLayer LowerLayer
1 5
2 5
3 5
4 5
HigherLayer LowerLayer 1 5 2 5 3 5 4 5
3.2.3. Usage of Channelization for DS3, DS1, DS0
3.2.3. Usage of Channelization for DS3, DS1, DS0
An example is given here to explain the channelization objects in the DS3, DS1, and DS0 MIBs to help the implementer use the objects correctly. Treatment of E3 and E1 would be similar, with the number of DS0s being different depending on the framing of the E1.
An example is given here to explain the channelization objects in the DS3, DS1, and DS0 MIBs to help the implementer use the objects correctly. Treatment of E3 and E1 would be similar, with the number of DS0s being different depending on the framing of the E1.
Assume that a DS3 (with ifIndex 1) is channelized into DS1s (without DS2s). The object dsx3Channelization is set to enabledDs1. There will be 28 DS1s in the ifTable. Assume the entries in the ifTable for the DS1s are created in channel order and the ifIndex values are 2 through 29. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each DS1. The entries will be as follows:
Assume that a DS3 (with ifIndex 1) is channelized into DS1s (without DS2s). The object dsx3Channelization is set to enabledDs1. There will be 28 DS1s in the ifTable. Assume the entries in the ifTable for the DS1s are created in channel order and the ifIndex values are 2 through 29. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each DS1. The entries will be as follows:
dsx1ChanMappingTable Entries
dsx1ChanMappingTable Entries
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
1 1 2
1 2 3
......
1 28 29
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 1 1 2 1 2 3 ...... 1 28 29
In addition, the DS1s are channelized into DS0s. The object dsx1Channelization is set to enabledDS0 for each DS1. When this object is set to this value, 24 DS0s are created by the agent. There will be 24 DS0s in the ifTable for each DS1. If the dsx1Channelization is set to disabled, the 24 DS0s are destroyed.
In addition, the DS1s are channelized into DS0s. The object dsx1Channelization is set to enabledDS0 for each DS1. When this object is set to this value, 24 DS0s are created by the agent. There will be 24 DS0s in the ifTable for each DS1. If the dsx1Channelization is set to disabled, the 24 DS0s are destroyed.
Assume the entries in the ifTable are created in channel order and the ifIndex values for the DS0s in the first DS1 are 30 through 53. In the DS0 MIB, there will be an entry in the dsx0ChanMappingTable for each DS0. The entries will be as follows:
Assume the entries in the ifTable are created in channel order and the ifIndex values for the DS0s in the first DS1 are 30 through 53. In the DS0 MIB, there will be an entry in the dsx0ChanMappingTable for each DS0. The entries will be as follows:
Nicklass, Ed. Standards Track [Page 8] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 8] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
dsx0ChanMappingTable Entries
dsx0ChanMappingTable Entries
ifIndex dsx0Ds0ChannelNumber dsx0ChanMappedIfIndex
2 1 30
2 2 31
......
2 24 53
ifIndex dsx0Ds0ChannelNumber dsx0ChanMappedIfIndex 2 1 30 2 2 31 ...... 2 24 53
3.2.4. Usage of Channelization for DS3, DS2, DS1
3.2.4. Usage of Channelization for DS3, DS2, DS1
An example is given here to explain the channelization objects in the DS3 and DS1 MIBs to help the implementer use the objects correctly.
An example is given here to explain the channelization objects in the DS3 and DS1 MIBs to help the implementer use the objects correctly.
Assume that a DS3 (with ifIndex 1) is channelized into DS2s. The object dsx3Channelization [RFC3896] is set to enabledDs2. There will be 7 DS2s (ifType of DS1) in the ifTable. Assume the entries in the ifTable for the DS2s are created in channel order and the ifIndex values are 2 through 8. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each DS2. The entries will be as follows:
Assume that a DS3 (with ifIndex 1) is channelized into DS2s. The object dsx3Channelization [RFC3896] is set to enabledDs2. There will be 7 DS2s (ifType of DS1) in the ifTable. Assume the entries in the ifTable for the DS2s are created in channel order and the ifIndex values are 2 through 8. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each DS2. The entries will be as follows:
dsx1ChanMappingTable Entries
dsx1ChanMappingTable Entries
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
1 1 2
1 2 3
......
1 7 8
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 1 1 2 1 2 3 ...... 1 7 8
In addition, the DS2s are channelized into DS1s. The object dsx1Channelization is set to enabledDS1 for each DS2. There will be 4 DS1s in the ifTable for each DS2. Assume the entries in the ifTable are created in channel order and the ifIndex values for the DS1s in the first DS2 are 9 through 12, then 13 through 16 for the second DS2, and so on. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each DS1. The entries will be as follows:
In addition, the DS2s are channelized into DS1s. The object dsx1Channelization is set to enabledDS1 for each DS2. There will be 4 DS1s in the ifTable for each DS2. Assume the entries in the ifTable are created in channel order and the ifIndex values for the DS1s in the first DS2 are 9 through 12, then 13 through 16 for the second DS2, and so on. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each DS1. The entries will be as follows:
dsx1ChanMappingTable Entries
dsx1ChanMappingTable Entries
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
2 1 9
2 2 10
2 3 11
2 4 12
3 1 13
3 2 14
...
8 4 36
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 2 1 9 2 2 10 2 3 11 2 4 12 3 1 13 3 2 14 ... 8 4 36
Nicklass, Ed. Standards Track [Page 9] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 9] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
3.2.5. Usage of Loopbacks
3.2.5. Usage of Loopbacks
This section discusses the behavior of objects related to loopbacks.
This section discusses the behavior of objects related to loopbacks.
The object dsx1LoopbackConfig represents the desired state of loopbacks on this interface. Using this object, a manager can request
The object dsx1LoopbackConfig represents the desired state of loopbacks on this interface. Using this object, a manager can request
LineLoopback
PayloadLoopback (if ESF framing)
InwardLoopback
DualLoopback (Line + Inward)
NoLoopback
LineLoopback PayloadLoopback (if ESF framing) InwardLoopback DualLoopback (Line + Inward) NoLoopback
The remote end can also request loopbacks either through the Facility Data Link (FDL) channel if ESF or inband if D4. The loopbacks that can be requested this way are
The remote end can also request loopbacks either through the Facility Data Link (FDL) channel if ESF or inband if D4. The loopbacks that can be requested this way are
LineLoopback
PayloadLoopback (if ESF framing)
NoLoopback
LineLoopback PayloadLoopback (if ESF framing) NoLoopback
To model the current state of loopbacks on a DS1 interface, the object dsx1LoopbackStatus defines which loopback is currently applied to an interface. This object, which is a bitmap, will have bits turned on that reflect the currently active loopbacks on the interface as well as the source of those loopbacks.
To model the current state of loopbacks on a DS1 interface, the object dsx1LoopbackStatus defines which loopback is currently applied to an interface. This object, which is a bitmap, will have bits turned on that reflect the currently active loopbacks on the interface as well as the source of those loopbacks.
The following restrictions/rules apply to loopbacks:
The following restrictions/rules apply to loopbacks:
The far end cannot undo loopbacks set by a manager.
The far end cannot undo loopbacks set by a manager.
A manager can undo loopbacks set by the far end.
A manager can undo loopbacks set by the far end.
Both a line loopback and an inward loopback can be set at the same time. Only these two loopbacks can co-exist and either one may be set by the manager or the far end. A LineLoopback request from the far end is incremental to an existing Inward loopback established by a manager. When a NoLoopback is received from the far end in this case, the InwardLoopback remains in place.
Both a line loopback and an inward loopback can be set at the same time. Only these two loopbacks can co-exist and either one may be set by the manager or the far end. A LineLoopback request from the far end is incremental to an existing Inward loopback established by a manager. When a NoLoopback is received from the far end in this case, the InwardLoopback remains in place.
3.3. Objectives of This MIB Module
3.3. Objectives of This MIB Module
There are numerous things that could be included in a MIB for DS1 signals: the management of multiplexers, CSUs, Data Service Units (DSUs), and the like. The intent of this document is to facilitate the common management of all devices with DS1, J1, E1, DS2, or E2 interfaces. As such, a design decision was made up front to very
There are numerous things that could be included in a MIB for DS1 signals: the management of multiplexers, CSUs, Data Service Units (DSUs), and the like. The intent of this document is to facilitate the common management of all devices with DS1, J1, E1, DS2, or E2 interfaces. As such, a design decision was made up front to very
Nicklass, Ed. Standards Track [Page 10] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 10] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
closely align the MIB with the set of objects that can generally be read from these types of devices that are currently deployed.
closely align the MIB with the set of objects that can generally be read from these types of devices that are currently deployed.
J2 interfaces are not supported by this MIB.
J2 interfaces are not supported by this MIB.
3.4. DS1 Terminology
3.4. DS1 Terminology
The terminology used in this document to describe error conditions on a DS1 interface as monitored by a DS1 device are based on the latest ANSI T1.231 standard [ANSI-T1.231]. If the definition in this document does not match the definition in the ANSI T1.231 document, the implementer should follow the definition described in this document.
The terminology used in this document to describe error conditions on a DS1 interface as monitored by a DS1 device are based on the latest ANSI T1.231 standard [ANSI-T1.231]. If the definition in this document does not match the definition in the ANSI T1.231 document, the implementer should follow the definition described in this document.
3.4.1. Error Events
3.4.1. Error Events
Bipolar Violation (BPV) Error Event
A BPV error event for an AMI-coded (AMI stands for Alternate Mark
Inversion) signal is the occurrence of a pulse of the same
polarity as the previous pulse (see T1.231, Section 4.2.1.1.1). A
BPV error event for a B8ZS- or HDB3-coded signal is the occurrence
of a pulse of the same polarity as the previous pulse without
being a part of the zero substitution code.
Bipolar Violation (BPV) Error Event A BPV error event for an AMI-coded (AMI stands for Alternate Mark Inversion) signal is the occurrence of a pulse of the same polarity as the previous pulse (see T1.231, Section 4.2.1.1.1). A BPV error event for a B8ZS- or HDB3-coded signal is the occurrence of a pulse of the same polarity as the previous pulse without being a part of the zero substitution code.
Excessive Zeroes (EXZ) Error Event
An Excessive Zeroes error event for an AMI-coded signal is the
occurrence of more than fifteen contiguous zeroes (see T1.231
Section 4.2.1.1.2). For a B8ZS-coded signal, the defect occurs
when more than seven contiguous zeroes are detected.
Excessive Zeroes (EXZ) Error Event An Excessive Zeroes error event for an AMI-coded signal is the occurrence of more than fifteen contiguous zeroes (see T1.231 Section 4.2.1.1.2). For a B8ZS-coded signal, the defect occurs when more than seven contiguous zeroes are detected.
Line Coding Violation (LCV) Error Event
A Line Coding Violation (LCV) is the occurrence of either a
Bipolar Violation (BPV) or Excessive Zeroes (EXZ) error event.
(Also known as CV-L; see T1.231, Section 4.6.1.1.)
Line Coding Violation (LCV) Error Event A Line Coding Violation (LCV) is the occurrence of either a Bipolar Violation (BPV) or Excessive Zeroes (EXZ) error event. (Also known as CV-L; see T1.231, Section 4.6.1.1.)
Path Coding Violation (PCV) Error Event
A Path Coding Violation error event is a frame synchronization bit
error in the D4 and E1-noCRC formats, or a CRC or frame synch. bit
error in the ESF and E1-CRC formats. (Also known as CV-P; see
T1.231, Section 4.6.2.1.)
Path Coding Violation (PCV) Error Event A Path Coding Violation error event is a frame synchronization bit error in the D4 and E1-noCRC formats, or a CRC or frame synch. bit error in the ESF and E1-CRC formats. (Also known as CV-P; see T1.231, Section 4.6.2.1.)
Controlled Slip (CS) Error Event
A Controlled Slip is the replication or deletion of the payload
bits of a DS1 frame (see T1.231, Section 4.2.1.2.3). A Controlled
Slip may be performed when there is a difference between the
timing of a synchronous receiving terminal and the received
signal. A Controlled Slip does not cause an Out of Frame defect.
Controlled Slip (CS) Error Event A Controlled Slip is the replication or deletion of the payload bits of a DS1 frame (see T1.231, Section 4.2.1.2.3). A Controlled Slip may be performed when there is a difference between the timing of a synchronous receiving terminal and the received signal. A Controlled Slip does not cause an Out of Frame defect.
Nicklass, Ed. Standards Track [Page 11] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 11] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
3.4.2. Performance Defects
3.4.2. Performance Defects
Out of Frame (OOF) Defect
An OOF defect is the occurrence of a particular density of Framing
Error events (see T1.231, Section 4.2.2.2.1).
Out of Frame (OOF) Defect An OOF defect is the occurrence of a particular density of Framing Error events (see T1.231, Section 4.2.2.2.1).
For DS1 links, an Out of Frame defect is declared when the
receiver detects two or more framing errors within a 3-msec period
for ESF signals and 0.75 msec for D4 signals, or two or more
errors out of five or fewer consecutive framing bits.
For DS1 links, an Out of Frame defect is declared when the receiver detects two or more framing errors within a 3-msec period for ESF signals and 0.75 msec for D4 signals, or two or more errors out of five or fewer consecutive framing bits.
For E1 links, an Out of Frame defect is declared when three
consecutive frame alignment signals have been received with an
error (see G.706, Section 4.1 [CCITT-G.706]).
For E1 links, an Out of Frame defect is declared when three consecutive frame alignment signals have been received with an error (see G.706, Section 4.1 [CCITT-G.706]).
For DS2 links, an Out of Frame defect is declared when seven or
more consecutive errored framing patterns (four multiframe) are
received. The OOF is cleared when three or more consecutive
correct framing patterns are received.
For DS2 links, an Out of Frame defect is declared when seven or more consecutive errored framing patterns (four multiframe) are received. The OOF is cleared when three or more consecutive correct framing patterns are received.
Once an Out Of Frame Defect is declared, the framer starts
searching for a correct framing pattern. The Out of Frame defect
ends when the signal is in-frame.
Once an Out Of Frame Defect is declared, the framer starts searching for a correct framing pattern. The Out of Frame defect ends when the signal is in-frame.
In-frame occurs when there are fewer than two frame bit errors
within a 3-msec period for ESF signals and 0.75 msec for D4
signals.
In-frame occurs when there are fewer than two frame bit errors within a 3-msec period for ESF signals and 0.75 msec for D4 signals.
For E1 links, in-frame occurs when a) in frame N the frame
alignment signal is correct and b) in frame N+1 the frame
alignment signal is absent (i.e., bit 2 in TS0 is a one) and c) in
frame N+2 the frame alignment signal is present and correct (see
G.704, Section 4.1).
For E1 links, in-frame occurs when a) in frame N the frame alignment signal is correct and b) in frame N+1 the frame alignment signal is absent (i.e., bit 2 in TS0 is a one) and c) in frame N+2 the frame alignment signal is present and correct (see G.704, Section 4.1).
Alarm Indication Signal (AIS) Defect
For D4 and ESF links, the 'all ones' condition is detected at a
DS1 line interface upon observing an unframed signal with a one's
density of at least 99.9% present for a time equal to or greater
than T, where 3 ms <= T <= 75 ms. The AIS is terminated upon
observing a signal not meeting the one's density or the unframed
signal criteria for a period equal to or greater than T (see
G.775, Section 5.4).
Alarm Indication Signal (AIS) Defect For D4 and ESF links, the 'all ones' condition is detected at a DS1 line interface upon observing an unframed signal with a one's density of at least 99.9% present for a time equal to or greater than T, where 3 ms <= T <= 75 ms. The AIS is terminated upon observing a signal not meeting the one's density or the unframed signal criteria for a period equal to or greater than T (see G.775, Section 5.4).
For E1 links, the 'all-ones' condition is detected at the line
interface as a string of 512 bits containing fewer than three zero
bits (see O.162 [ITU-T-O.162], Section 3.3.2).
For E1 links, the 'all-ones' condition is detected at the line interface as a string of 512 bits containing fewer than three zero bits (see O.162 [ITU-T-O.162], Section 3.3.2).
Nicklass, Ed. Standards Track [Page 12] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 12] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
For DS2 links, the DS2 AIS shall be sent from the NT1 to the user
to indicate a loss of the 6,312-kbps frame capability on the
network side. The DS2 AIS is defined as a bit array of 6,312 kbps
in which all binary bits are set to '1'.
For DS2 links, the DS2 AIS shall be sent from the NT1 to the user to indicate a loss of the 6,312-kbps frame capability on the network side. The DS2 AIS is defined as a bit array of 6,312 kbps in which all binary bits are set to '1'.
The DS2 AIS detection and removal shall be implemented according
to ITU-T Draft Recommendation G.775 [ITU-T-G.775] Section 5.5:
The DS2 AIS detection and removal shall be implemented according to ITU-T Draft Recommendation G.775 [ITU-T-G.775] Section 5.5:
- a DS2 AIS defect is detected when the incoming signal has two
or less zeroes in a sequence of 3156 bits (0.5 ms).
- a DS2 AIS defect is detected when the incoming signal has two or less zeroes in a sequence of 3156 bits (0.5 ms).
- a DS2 AIS defect is cleared when the incoming signal has three
or more zeroes in a sequence of 3156 bits (0.5 ms).
- a DS2 AIS defect is cleared when the incoming signal has three or more zeroes in a sequence of 3156 bits (0.5 ms).
3.4.3. Performance Parameters
3.4.3. Performance Parameters
All performance parameters are accumulated in 15-minute intervals, and up to 96 intervals (24 hours' worth) are kept by an agent. Fewer than 96 intervals of data will be available if the agent has been restarted within the last 24 hours. In addition, there is a rolling 24-hour total of each performance parameter. Performance parameters continue to be collected when the interface is down.
All performance parameters are accumulated in 15-minute intervals, and up to 96 intervals (24 hours' worth) are kept by an agent. Fewer than 96 intervals of data will be available if the agent has been restarted within the last 24 hours. In addition, there is a rolling 24-hour total of each performance parameter. Performance parameters continue to be collected when the interface is down.
There is no requirement for an agent to ensure a fixed relationship between the start of a 15-minute interval and any wall clock; however, some agents may align the 15-minute intervals with quarter hours.
There is no requirement for an agent to ensure a fixed relationship between the start of a 15-minute interval and any wall clock; however, some agents may align the 15-minute intervals with quarter hours.
Performance parameters are of types PerfCurrentCount, PerfIntervalCount, and PerfTotalCount. These textual conventions are all Gauge32, and they are used because it is possible for these objects to decrease. Objects may decrease when Unavailable Seconds occur across a 15-minute interval boundary. See Unavailable Second discussion later in this section.
Performance parameters are of types PerfCurrentCount, PerfIntervalCount, and PerfTotalCount. These textual conventions are all Gauge32, and they are used because it is possible for these objects to decrease. Objects may decrease when Unavailable Seconds occur across a 15-minute interval boundary. See Unavailable Second discussion later in this section.
Line Errored Second (LES)
A Line Errored Second is a second in which one or more Line Coding
Violation error events were detected. (Also known as ES-L; see
T1.231, Section 4.6.1.2.)
Line Errored Second (LES) A Line Errored Second is a second in which one or more Line Coding Violation error events were detected. (Also known as ES-L; see T1.231, Section 4.6.1.2.)
Controlled Slip Second (CSS)
A Controlled Slip Second is a one-second interval containing one
or more controlled slips (see T1.231, Section 4.6.2.9). This is
not incremented during an Unavailable Second.
Controlled Slip Second (CSS) A Controlled Slip Second is a one-second interval containing one or more controlled slips (see T1.231, Section 4.6.2.9). This is not incremented during an Unavailable Second.
Nicklass, Ed. Standards Track [Page 13] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 13] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Errored Second (ES)
For ESF and E1-CRC links, an Errored Second is a second with one
or more Path Coding Violations OR one or more Out of Frame defects
OR one or more Controlled Slip events OR a detected AIS defect.
(See T1.231, Section 4.6.2.2 and G.826 [ITU-T-G.826], Section
B.1).
Errored Second (ES) For ESF and E1-CRC links, an Errored Second is a second with one or more Path Coding Violations OR one or more Out of Frame defects OR one or more Controlled Slip events OR a detected AIS defect. (See T1.231, Section 4.6.2.2 and G.826 [ITU-T-G.826], Section B.1).
For D4 and E1-noCRC links, the presence of Bipolar Violations also
triggers an Errored Second.
For D4 and E1-noCRC links, the presence of Bipolar Violations also triggers an Errored Second.
This is not incremented during an Unavailable Second.
This is not incremented during an Unavailable Second.
Bursty Errored Second (BES)
A Bursty Errored Second (also known as Errored Second type B in
T1.231, Section 4.6.2.4) is a second with fewer than 320 and more
than 1 Path Coding Violation error events, no Severely Errored
Frame defects, and no detected incoming AIS defects. Controlled
Slips are not included in this parameter.
Bursty Errored Second (BES) A Bursty Errored Second (also known as Errored Second type B in T1.231, Section 4.6.2.4) is a second with fewer than 320 and more than 1 Path Coding Violation error events, no Severely Errored Frame defects, and no detected incoming AIS defects. Controlled Slips are not included in this parameter.
This is not incremented during an Unavailable Second. It applies
to ESF signals only.
This is not incremented during an Unavailable Second. It applies to ESF signals only.
Severely Errored Second (SES)
A Severely Errored Second for ESF signals is a second with 320 or
more Path Coding Violation error events OR one or more Out of
Frame defects OR a detected AIS defect (see T1.231, Section
4.6.2.5).
Severely Errored Second (SES) A Severely Errored Second for ESF signals is a second with 320 or more Path Coding Violation error events OR one or more Out of Frame defects OR a detected AIS defect (see T1.231, Section 4.6.2.5).
For E1-CRC signals, a Severely Errored Second is a second with 832
or more Path Coding Violation error events OR one or more Out of
Frame defects.
For E1-CRC signals, a Severely Errored Second is a second with 832 or more Path Coding Violation error events OR one or more Out of Frame defects.
For E1-noCRC signals, a Severely Errored Second is 2048 LCVs or
more.
For E1-noCRC signals, a Severely Errored Second is 2048 LCVs or more.
For D4 signals, a Severely Errored Second is a count of one-second
intervals with Framing Error events, or an OOF defect, or 1544
LCVs or more.
For D4 signals, a Severely Errored Second is a count of one-second intervals with Framing Error events, or an OOF defect, or 1544 LCVs or more.
Controlled Slips are not included in this parameter.
Controlled Slips are not included in this parameter.
This is not incremented during an Unavailable Second.
This is not incremented during an Unavailable Second.
Severely Errored Framing Second (SEFS)
An Severely Errored Framing Second is a second with one or more
Out of Frame defects OR a detected AIS defect. (Also known as
SAS-P (SEF/AIS second); see T1.231, Section 4.6.2.6.)
Severely Errored Framing Second (SEFS) An Severely Errored Framing Second is a second with one or more Out of Frame defects OR a detected AIS defect. (Also known as SAS-P (SEF/AIS second); see T1.231, Section 4.6.2.6.)
Nicklass, Ed. Standards Track [Page 14] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 14] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Degraded Minutes
A Degraded Minute is one in which the estimated error rate exceeds
1E-6 but does not exceed 1E-3 (see G.821 [CCITT-G.821]).
Degraded Minutes A Degraded Minute is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3 (see G.821 [CCITT-G.821]).
Degraded Minutes are determined by collecting all of the Available
Seconds, removing any Severely Errored Seconds, grouping the
result in 60-second long groups, and counting a 60-second long
group (a.k.a. minute) as degraded if the cumulative errors during
the seconds present in the group exceed 1E-6. Available seconds
are merely those seconds that are not Unavailable as described
below.
Degraded Minutes are determined by collecting all of the Available Seconds, removing any Severely Errored Seconds, grouping the result in 60-second long groups, and counting a 60-second long group (a.k.a. minute) as degraded if the cumulative errors during the seconds present in the group exceed 1E-6. Available seconds are merely those seconds that are not Unavailable as described below.
Unavailable Second (UAS)
Unavailable Seconds (UASs) are calculated by counting the number
of seconds that the interface is unavailable. The DS1 interface
is said to be unavailable from the onset of 10 contiguous SESs, or
the onset of the condition leading to a failure (see Failure
States). If the condition leading to the failure was immediately
preceded by one or more contiguous SESs, then the DS1 interface
unavailability starts from the onset of these SESs. Once
unavailable, and if no failure is present, the DS1 interface
becomes available at the onset of 10 contiguous seconds with no
SESs. Once unavailable, and if a failure is present, the DS1
interface becomes available at the onset of 10 contiguous seconds
with no SESs, if the failure clearing time is less than or equal
to 10 seconds. If the failure clearing time is more than 10
seconds, the DS1 interface becomes available at the onset of 10
contiguous seconds with no SESs, or the onset period leading to
the successful clearing condition, whichever occurs later. With
respect to the DS1 error counts, all counters are incremented
while the DS1 interface is deemed available. While the interface
is deemed unavailable, the only count that is incremented is UASs.
Unavailable Second (UAS) Unavailable Seconds (UASs) are calculated by counting the number of seconds that the interface is unavailable. The DS1 interface is said to be unavailable from the onset of 10 contiguous SESs, or the onset of the condition leading to a failure (see Failure States). If the condition leading to the failure was immediately preceded by one or more contiguous SESs, then the DS1 interface unavailability starts from the onset of these SESs. Once unavailable, and if no failure is present, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs. Once unavailable, and if a failure is present, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs, if the failure clearing time is less than or equal to 10 seconds. If the failure clearing time is more than 10 seconds, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs, or the onset period leading to the successful clearing condition, whichever occurs later. With respect to the DS1 error counts, all counters are incremented while the DS1 interface is deemed available. While the interface is deemed unavailable, the only count that is incremented is UASs.
Note that this definition implies that the agent cannot determine
until after a 10-second interval has passed whether a given one-
second interval belongs to available or unavailable time. If the
agent chooses to update the various performance statistics in real
time, then it must be prepared to retroactively reduce the ES,
BES, SES, and SEFS counts by 10 and increase the UAS count by 10
when it determines that available time has been entered. It must
also be prepared to adjust the PCV count and the DM count as
necessary since these parameters are not accumulated during
unavailable time. It must be similarly prepared to retroactively
decrease the UAS count by 10 and increase the ES, BES, and DM
counts as necessary upon entering available time. A special case
exists when the 10-second period leading to available or
unavailable time crosses a 900-second statistics window boundary,
as the foregoing description implies that the ES, BES, SES, SEFS,
Note that this definition implies that the agent cannot determine until after a 10-second interval has passed whether a given one- second interval belongs to available or unavailable time. If the agent chooses to update the various performance statistics in real time, then it must be prepared to retroactively reduce the ES, BES, SES, and SEFS counts by 10 and increase the UAS count by 10 when it determines that available time has been entered. It must also be prepared to adjust the PCV count and the DM count as necessary since these parameters are not accumulated during unavailable time. It must be similarly prepared to retroactively decrease the UAS count by 10 and increase the ES, BES, and DM counts as necessary upon entering available time. A special case exists when the 10-second period leading to available or unavailable time crosses a 900-second statistics window boundary, as the foregoing description implies that the ES, BES, SES, SEFS,
Nicklass, Ed. Standards Track [Page 15] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 15] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
DM, and UAS counts the PREVIOUS interval must be adjusted. In
this case, successive GETs of the affected dsx1IntervalSESs and
dsx1IntervalUASs objects will return differing values if the first
GET occurs during the first few seconds of the window.
DM, and UAS counts the PREVIOUS interval must be adjusted. In this case, successive GETs of the affected dsx1IntervalSESs and dsx1IntervalUASs objects will return differing values if the first GET occurs during the first few seconds of the window.
The agent may instead choose to delay updates to the various
statistics by 10 seconds in order to avoid retroactive adjustments
to the counters. A way to do this is sketched in Appendix B.
The agent may instead choose to delay updates to the various statistics by 10 seconds in order to avoid retroactive adjustments to the counters. A way to do this is sketched in Appendix B.
In any case, a linkDown trap shall be sent only after the agent has determined for certain that the unavailable state has been entered, but the time on the trap will be that of the first UAS (i.e., 10 seconds earlier). A linkUp trap shall be handled similarly.
In any case, a linkDown trap shall be sent only after the agent has determined for certain that the unavailable state has been entered, but the time on the trap will be that of the first UAS (i.e., 10 seconds earlier). A linkUp trap shall be handled similarly.
According to ANSI T1.231, unavailable time begins at the onset of 10 contiguous severely errored seconds -- that is, unavailable time starts with the first of the 10 contiguous SESs. Also, while an interface is deemed unavailable all counters for that interface are frozen except for the UAS count. It follows that an implementation that strictly complies with this standard must not increment any counters other than the UAS count -- even temporarily -- as a result of anything that happens during those 10 seconds. Since changes in the signal state lag the data to which they apply by 10 seconds, an ANSI-compliant implementation must pass the one-second statistics through a 10-second delay line prior to updating any counters. That can be done by performing the following steps at the end of each one-second interval.
According to ANSI T1.231, unavailable time begins at the onset of 10 contiguous severely errored seconds -- that is, unavailable time starts with the first of the 10 contiguous SESs. Also, while an interface is deemed unavailable all counters for that interface are frozen except for the UAS count. It follows that an implementation that strictly complies with this standard must not increment any counters other than the UAS count -- even temporarily -- as a result of anything that happens during those 10 seconds. Since changes in the signal state lag the data to which they apply by 10 seconds, an ANSI-compliant implementation must pass the one-second statistics through a 10-second delay line prior to updating any counters. That can be done by performing the following steps at the end of each one-second interval.
i) Read near/far end CV counter and alarm status flags from the
hardware.
i) Read near/far end CV counter and alarm status flags from the hardware.
ii) Accumulate the CV counts for the preceding second and compare
them to the ES and SES threshold for the layer in question.
Update the signal state and shift the one-second CV counts and
ES/SES flags into the 10-element delay line. Note that far-end
one-second statistics are to be flagged as "absent" during any
second in which there is an incoming defect at the layer in
question or at any lower layer.
ii) Accumulate the CV counts for the preceding second and compare them to the ES and SES threshold for the layer in question. Update the signal state and shift the one-second CV counts and ES/SES flags into the 10-element delay line. Note that far-end one-second statistics are to be flagged as "absent" during any second in which there is an incoming defect at the layer in question or at any lower layer.
iii) Update the current interval statistics using the signal state
from the previous update cycle and the one-second CV counts and
ES/SES flags shifted out of the 10-element delay line.
iii) Update the current interval statistics using the signal state from the previous update cycle and the one-second CV counts and ES/SES flags shifted out of the 10-element delay line.
This approach is further described in Appendix B.
This approach is further described in Appendix B.
Nicklass, Ed. Standards Track [Page 16] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 16] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
3.4.4. Failure States
3.4.4. Failure States
The following failure states are received, or detected failures, that are reported in the dsx1LineStatus object. When a DS1 interface would, if ever, produce the conditions leading to the failure state is described in the appropriate specification.
The following failure states are received, or detected failures, that are reported in the dsx1LineStatus object. When a DS1 interface would, if ever, produce the conditions leading to the failure state is described in the appropriate specification.
Far End Alarm Failure
The Far End Alarm failure is also known as "Yellow Alarm" in the
DS1 and J1 cases, "Distant Alarm" in the E1 case, and "Remote
Alarm" in the DS2 case.
Far End Alarm Failure The Far End Alarm failure is also known as "Yellow Alarm" in the DS1 and J1 cases, "Distant Alarm" in the E1 case, and "Remote Alarm" in the DS2 case.
For D4 links, the Far End Alarm failure is declared when bit 6 of
all channels has been zero for at least 335 ms and is cleared when
bit 6 of at least one channel is non-zero for a period T, where T
is usually less than one second and always less than five seconds.
The Far End Alarm failure is not declared for D4 links when a Loss
of Signal is detected. In J1 the 12th F-bit is set to 1.
For D4 links, the Far End Alarm failure is declared when bit 6 of all channels has been zero for at least 335 ms and is cleared when bit 6 of at least one channel is non-zero for a period T, where T is usually less than one second and always less than five seconds. The Far End Alarm failure is not declared for D4 links when a Loss of Signal is detected. In J1 the 12th F-bit is set to 1.
For ESF links, the Far End Alarm failure is declared if the Yellow
Alarm signal pattern occurs in at least seven out of ten
contiguous 16-bit pattern intervals and is cleared if the Yellow
Alarm signal pattern does not occur in ten contiguous 16-bit
signal pattern intervals. For DS1 the patterns is FF00 and for J1
the pattern is FFFF.
For ESF links, the Far End Alarm failure is declared if the Yellow Alarm signal pattern occurs in at least seven out of ten contiguous 16-bit pattern intervals and is cleared if the Yellow Alarm signal pattern does not occur in ten contiguous 16-bit signal pattern intervals. For DS1 the patterns is FF00 and for J1 the pattern is FFFF.
For E1 links, the Far End Alarm failure is declared when bit 3 of
time-slot zero is received set to one on two consecutive
occasions. The Far End Alarm failure is cleared when bit 3 of
time-slot zero is received set to zero.
For E1 links, the Far End Alarm failure is declared when bit 3 of time-slot zero is received set to one on two consecutive occasions. The Far End Alarm failure is cleared when bit 3 of time-slot zero is received set to zero.
For DS2 links, if a loss of frame alignment (LOF or LOS) and/or
DS2 AIS condition is detected, the RAI signal shall be generated
and transmitted to the remote side.
For DS2 links, if a loss of frame alignment (LOF or LOS) and/or DS2 AIS condition is detected, the RAI signal shall be generated and transmitted to the remote side.
The Remote Alarm Indication (RAI) signal is defined on m-bits as a
repetition of the 16-bit sequence consisting of eight binary '1s'
and eight binary '0s' in m-bits(1111111100000000). When the RAI
signal is not sent (in normal operation), the HDLC flag pattern
(01111110) in the m-bit is sent.
The Remote Alarm Indication (RAI) signal is defined on m-bits as a repetition of the 16-bit sequence consisting of eight binary '1s' and eight binary '0s' in m-bits(1111111100000000). When the RAI signal is not sent (in normal operation), the HDLC flag pattern (01111110) in the m-bit is sent.
The RAI failure is detected when 16 or more consecutive RAI-
patterns (1111111100000000) are received. The RAI failure is
cleared when 4 or more consecutive incorrect-RAI-patterns are
received.
The RAI failure is detected when 16 or more consecutive RAI- patterns (1111111100000000) are received. The RAI failure is cleared when 4 or more consecutive incorrect-RAI-patterns are received.
Nicklass, Ed. Standards Track [Page 17] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 17] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Alarm Indication Signal (AIS) Failure
The Alarm Indication Signal failure is declared when an AIS defect
is detected at the input and the AIS defect still exists after the
Loss of Frame failure (which is caused by the unframed nature of
the 'all-ones' signal) is declared. The AIS failure is cleared
when the Loss of Frame failure is cleared. (See T1.231, Section
4.3.1.2.2).
Alarm Indication Signal (AIS) Failure The Alarm Indication Signal failure is declared when an AIS defect is detected at the input and the AIS defect still exists after the Loss of Frame failure (which is caused by the unframed nature of the 'all-ones' signal) is declared. The AIS failure is cleared when the Loss of Frame failure is cleared. (See T1.231, Section 4.3.1.2.2).
An AIS defect at a 6312-kbit/s (G.704) interface is detected when
the incoming signal has two or less zeroes in a sequence of 3156
bits (0.5ms).
An AIS defect at a 6312-kbit/s (G.704) interface is detected when the incoming signal has two or less zeroes in a sequence of 3156 bits (0.5ms).
The AIS signal defect is cleared when the incoming signal has
three {3} or more zeroes in a sequence of 3156 bits (0.5ms).
The AIS signal defect is cleared when the incoming signal has three {3} or more zeroes in a sequence of 3156 bits (0.5ms).
Loss Of Frame (LOF) Failure
For DS1 links, the Loss of Frame failure is declared when an OOF
or LOS defect has persisted for T seconds, where 2 <= T <= 10.
The Loss of Frame failure is cleared when there have been no OOF
or LOS defects during a period T where 0 <= T <= 20. Many systems
will perform "hit integration" within the period T before
declaring or clearing the failure; e.g., see TR 62411
[AT&T-TR-62411].
Loss Of Frame (LOF) Failure For DS1 links, the Loss of Frame failure is declared when an OOF or LOS defect has persisted for T seconds, where 2 <= T <= 10. The Loss of Frame failure is cleared when there have been no OOF or LOS defects during a period T where 0 <= T <= 20. Many systems will perform "hit integration" within the period T before declaring or clearing the failure; e.g., see TR 62411 [AT&T-TR-62411].
For E1 links, the Loss of Frame failure is declared when an OOF
defect is detected.
For E1 links, the Loss of Frame failure is declared when an OOF defect is detected.
Loss Of Signal (LOS) Failure
For DS1, the Loss of Signal failure is declared upon observing
175 +/- 75 contiguous pulse positions with no pulses of either
positive or negative polarity. The LOS failure is cleared upon
observing an average pulse density of at least 12.5% over a period
of 175 +/- 75 contiguous pulse positions starting with the receipt
of a pulse.
Loss Of Signal (LOS) Failure For DS1, the Loss of Signal failure is declared upon observing 175 +/- 75 contiguous pulse positions with no pulses of either positive or negative polarity. The LOS failure is cleared upon observing an average pulse density of at least 12.5% over a period of 175 +/- 75 contiguous pulse positions starting with the receipt of a pulse.
For E1 links, the Loss of Signal failure is declared when greater
than 10 consecutive zeroes are detected (see O.162, Section
3.4.4).
For E1 links, the Loss of Signal failure is declared when greater than 10 consecutive zeroes are detected (see O.162, Section 3.4.4).
A LOS defect at 6312kbit/s interfaces is detected when the
incoming signal has "no transitions", i.e., when the signal level
is less than or equal to a signal level of 35dB below nominal, for
N consecutive pulse intervals, where 10 <= N <= 255.
A LOS defect at 6312kbit/s interfaces is detected when the incoming signal has "no transitions", i.e., when the signal level is less than or equal to a signal level of 35dB below nominal, for N consecutive pulse intervals, where 10 <= N <= 255.
The LOS defect is cleared when the incoming signal has
"transitions", i.e., when the signal level is greater than or
equal to a signal level of 9dB below nominal, for N consecutive
pulse intervals, where 10 <= N <= 255.
The LOS defect is cleared when the incoming signal has "transitions", i.e., when the signal level is greater than or equal to a signal level of 9dB below nominal, for N consecutive pulse intervals, where 10 <= N <= 255.
Nicklass, Ed. Standards Track [Page 18] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 18] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
A signal with "transitions" corresponds to a G.703-compliant
signal.
A signal with "transitions" corresponds to a G.703-compliant signal.
Loopback Pseudo-Failure
The Loopback Pseudo-Failure is declared when the near-end
equipment has placed a loopback (of any kind) on the DS1. This
allows a management entity to determine from one object whether
the DS1 can be considered to be in service or not (from the point
of view of the near-end equipment).
Loopback Pseudo-Failure The Loopback Pseudo-Failure is declared when the near-end equipment has placed a loopback (of any kind) on the DS1. This allows a management entity to determine from one object whether the DS1 can be considered to be in service or not (from the point of view of the near-end equipment).
TS16 Alarm Indication Signal Failure
For E1 links, the TS16 Alarm Indication Signal failure is declared
when time-slot 16 is received as all ones for all frames of two
consecutive multiframes (see G.732, Section 4.2.6). This
condition is never declared for DS1.
TS16 Alarm Indication Signal Failure For E1 links, the TS16 Alarm Indication Signal failure is declared when time-slot 16 is received as all ones for all frames of two consecutive multiframes (see G.732, Section 4.2.6). This condition is never declared for DS1.
Loss of MultiFrame Failure
The Loss of MultiFrame failure is declared when two consecutive
multiframe alignment signals (bits 4 through 7 of TS16 of frame 0)
have been received with an error. The Loss of Multiframe failure
is cleared when the first correct multiframe alignment signal is
received. The Loss of Multiframe failure can only be declared for
E1 links operating with G.732 [CCITT-G.732] framing (sometimes
called "Channel Associated Signalling" mode).
Loss of MultiFrame Failure The Loss of MultiFrame failure is declared when two consecutive multiframe alignment signals (bits 4 through 7 of TS16 of frame 0) have been received with an error. The Loss of Multiframe failure is cleared when the first correct multiframe alignment signal is received. The Loss of Multiframe failure can only be declared for E1 links operating with G.732 [CCITT-G.732] framing (sometimes called "Channel Associated Signalling" mode).
Far End Loss of Multiframe Failure
The Far End Loss of Multiframe failure is declared when bit 2 of
TS16 of frame 0 is received set to one on two consecutive
occasions. The Far End Loss of Multiframe failure is cleared when
bit 2 of TS16 of frame 0 is received set to zero. The Far End
Loss of Multiframe failure can only be declared for E1 links
operating in "Channel Associated Signalling" mode (see G.732).
Far End Loss of Multiframe Failure The Far End Loss of Multiframe failure is declared when bit 2 of TS16 of frame 0 is received set to one on two consecutive occasions. The Far End Loss of Multiframe failure is cleared when bit 2 of TS16 of frame 0 is received set to zero. The Far End Loss of Multiframe failure can only be declared for E1 links operating in "Channel Associated Signalling" mode (see G.732).
DS2 Payload AIS Failure
The DS2 Payload AIS failure is declared when the incoming signal
of the 6,312-kbps frame payload (time-slots 1 through 96) has two
or less zeroes in a sequence of 3072 bits (0.5ms). The DS2
Payload AIS is cleared when the incoming signal of the 6,312-kbps
frame payload has three or more zeroes in a sequence of 3072 bits
(0.5 ms).
DS2 Payload AIS Failure The DS2 Payload AIS failure is declared when the incoming signal of the 6,312-kbps frame payload (time-slots 1 through 96) has two or less zeroes in a sequence of 3072 bits (0.5ms). The DS2 Payload AIS is cleared when the incoming signal of the 6,312-kbps frame payload has three or more zeroes in a sequence of 3072 bits (0.5 ms).
DS2 Performance Threshold Failure
DS2 Performance Threshold failure monitors equipment performance
and is based on the CRC (Cyclic Redundancy Check) procedure
defined in G.704.
DS2 Performance Threshold Failure DS2 Performance Threshold failure monitors equipment performance and is based on the CRC (Cyclic Redundancy Check) procedure defined in G.704.
The DS2 Performance Threshold failure is declared when the bit
error ratio exceeds 10^-4 (Performance Threshold), and the DS2
The DS2 Performance Threshold failure is declared when the bit error ratio exceeds 10^-4 (Performance Threshold), and the DS2
Nicklass, Ed. Standards Track [Page 19] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 19] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Performance Threshold failure is cleared when the bit error ratio
decreases to less than 10^-6."
Performance Threshold failure is cleared when the bit error ratio decreases to less than 10^-6."
3.4.5. Other Terms
3.4.5. Other Terms
Circuit Identifier
This is a character string specified by the circuit vendor and is
useful when communicating with the vendor during the
troubleshooting process (see M.1400 [ITU-T-M.1400] for additional
information).
Circuit Identifier This is a character string specified by the circuit vendor and is useful when communicating with the vendor during the troubleshooting process (see M.1400 [ITU-T-M.1400] for additional information).
Proxy
In this document, the word proxy is meant to indicate an
application that receives SNMP messages and replies to them on
behalf of the devices that implement the actual DS1/E1 interfaces.
The proxy may have already collected the information about the
DS1/J1/E1 interfaces into its local database and may not
necessarily forward the requests to the actual DS1/J1/E1
interface. It is expected in such an application that there are
periods of time where the proxy is not communicating with the
DS1/J1/E1 interfaces. In these instances, the proxy will not
necessarily have up-to-date configuration information and will
most likely have missed the collection of some statistics data.
Missed statistics data collection will result in invalid data in
the interval table.
Proxy In this document, the word proxy is meant to indicate an application that receives SNMP messages and replies to them on behalf of the devices that implement the actual DS1/E1 interfaces. The proxy may have already collected the information about the DS1/J1/E1 interfaces into its local database and may not necessarily forward the requests to the actual DS1/J1/E1 interface. It is expected in such an application that there are periods of time where the proxy is not communicating with the DS1/J1/E1 interfaces. In these instances, the proxy will not necessarily have up-to-date configuration information and will most likely have missed the collection of some statistics data. Missed statistics data collection will result in invalid data in the interval table.
4. Object Definitions
4. Object Definitions
DS1-MIB DEFINITIONS ::= BEGIN
DS1-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, transmission
FROM SNMPv2-SMI -- [RFC2578]
DisplayString, TimeStamp, TruthValue
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndex, ifIndex
FROM IF-MIB -- [RFC2863]
PerfCurrentCount, PerfIntervalCount,
PerfTotalCount
FROM PerfHist-TC-MIB; -- [RFC3593]
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI -- [RFC2578] DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC -- [RFC2579] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] InterfaceIndex, ifIndex FROM IF-MIB -- [RFC2863] PerfCurrentCount, PerfIntervalCount, PerfTotalCount FROM PerfHist-TC-MIB; -- [RFC3593]
ds1 MODULE-IDENTITY
LAST-UPDATED "200703050000Z"
ORGANIZATION "IETF AToM MIB Working Group"
ds1 MODULE-IDENTITY LAST-UPDATED "200703050000Z" ORGANIZATION "IETF AToM MIB Working Group"
Nicklass, Ed. Standards Track [Page 20] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 20] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/atommib-charter.html
CONTACT-INFO "WG charter: http://www.ietf.org/html.charters/atommib-charter.html
Mailing Lists:
General Discussion: atommib@research.telcordia.com
To Subscribe: atommib-request@research.telcordia.com
Mailing Lists: General Discussion: atommib@research.telcordia.com To Subscribe: atommib-request@research.telcordia.com
Editor: Orly Nicklass
Editor: Orly Nicklass
Postal: RAD Data Communications, Ltd.
Ziv Tower, 24 Roul Walenberg
Tel Aviv, Israel, 69719
Postal: RAD Data Communications, Ltd. Ziv Tower, 24 Roul Walenberg Tel Aviv, Israel, 69719
Tel: +9723 765 9969
E-mail: orly_n@rad.com"
Tel: +9723 765 9969 E-mail: orly_n@rad.com"
DESCRIPTION
"The MIB module to describe DS1, J1, E1, DS2, and
E2 interfaces objects.
DESCRIPTION "The MIB module to describe DS1, J1, E1, DS2, and E2 interfaces objects.
Copyright (c) The IETF Trust (2007). This
version of this MIB module is part of RFC 4805;
see the RFC itself for full legal notices."
REVISION "200703050000Z"
DESCRIPTION
"The following changes were made:
(1) Values were added to dsx1LineType to
support J1 types.
(2) The object dsx1LineImpedance was added.
(3) All DM-related objects were deprecated
following their removal from ITU performance
standards.
The RFC 4805 version of this MIB module."
REVISION "200409090000Z"
DESCRIPTION
"The RFC 3895 version of this MIB module.
The key changes made to this MIB module
since its publication in RFC 2495 are as follows:
(1) The dsx1FracIfIndex SYNTAX matches the description
range.
(2) A value was added to dsx1TransmitClockSource.
(3) Values were added to dsx1LineType.
(4) Two objects were added, dsx1LineMode and
dsx1LineBuildOut, to better express transceiver
mode and LineBuildOut for T1.
(5) Reference was added to Circuit Identifier object.
Copyright (c) The IETF Trust (2007). This version of this MIB module is part of RFC 4805; see the RFC itself for full legal notices." REVISION "200703050000Z" DESCRIPTION "The following changes were made: (1) Values were added to dsx1LineType to support J1 types. (2) The object dsx1LineImpedance was added. (3) All DM-related objects were deprecated following their removal from ITU performance standards. The RFC 4805 version of this MIB module." REVISION "200409090000Z" DESCRIPTION "The RFC 3895 version of this MIB module. The key changes made to this MIB module since its publication in RFC 2495 are as follows: (1) The dsx1FracIfIndex SYNTAX matches the description range. (2) A value was added to dsx1TransmitClockSource. (3) Values were added to dsx1LineType. (4) Two objects were added, dsx1LineMode and dsx1LineBuildOut, to better express transceiver mode and LineBuildOut for T1. (5) Reference was added to Circuit Identifier object.
Nicklass, Ed. Standards Track [Page 21] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 21] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
(6) Align the DESCRIPTION clauses of few statistic
objects with the near-end definition, with the far-end
definition, and with RFC 3593.
(7) Changes in Compliance Statements to include new
objects.
(8) A typographical error in dsx2E2 was fixed; the new name
is dsx1E2."
(6) Align the DESCRIPTION clauses of few statistic objects with the near-end definition, with the far-end definition, and with RFC 3593. (7) Changes in Compliance Statements to include new objects. (8) A typographical error in dsx2E2 was fixed; the new name is dsx1E2."
REVISION "199808011830Z"
DESCRIPTION
"The RFC 2495 version of this MIB module.
The key changes made to this MIB module
since its publication in RFC 1406 are as follows:
(1) The Fractional table has been deprecated.
(2) This document uses SMIv2.
(3) Usage is given for ifTable and ifXTable.
(4) Example usage of ifStackTable is included.
(5) dsx1IfIndex has been deprecated.
(6) Support for DS2 and E2 has been added.
(7) Additional lineTypes for DS2, E2, and unframed E1
were added.
(8) The definition of valid intervals has been clarified
for the case where the agent proxied for other
devices. In particular, the treatment of missing
intervals has been clarified.
(9) An inward loopback has been added.
(10) Additional lineStatus bits have been added for Near
End in Unavailable Signal State, Carrier Equipment
Out of Service, DS2 Payload AIS, and DS2 Performance
Threshold.
(11) A read-write line Length object has been added.
(12) Signal mode of other has been added.
(13) Added a lineStatus last change, trap and enabler.
(14) The e1(19) ifType has been obsoleted, so this MIB
does not list it as a supported ifType.
(15) Textual Conventions for statistics objects have
been used.
(16) A new object, dsx1LoopbackStatus, has been
introduced to reflect the loopbacks established
on a DS1 interface and the source to the requests.
dsx1LoopbackConfig continues to be the desired
loopback state while dsx1LoopbackStatus reflects
the actual state.
(17) A dual loopback has been added to allow the setting
of an inward loopback and a line loopback at the
same time.
(18) An object indicating which channel to use within a
parent object (i.e., DS3) has been added.
REVISION "199808011830Z" DESCRIPTION "The RFC 2495 version of this MIB module. The key changes made to this MIB module since its publication in RFC 1406 are as follows: (1) The Fractional table has been deprecated. (2) This document uses SMIv2. (3) Usage is given for ifTable and ifXTable. (4) Example usage of ifStackTable is included. (5) dsx1IfIndex has been deprecated. (6) Support for DS2 and E2 has been added. (7) Additional lineTypes for DS2, E2, and unframed E1 were added. (8) The definition of valid intervals has been clarified for the case where the agent proxied for other devices. In particular, the treatment of missing intervals has been clarified. (9) An inward loopback has been added. (10) Additional lineStatus bits have been added for Near End in Unavailable Signal State, Carrier Equipment Out of Service, DS2 Payload AIS, and DS2 Performance Threshold. (11) A read-write line Length object has been added. (12) Signal mode of other has been added. (13) Added a lineStatus last change, trap and enabler. (14) The e1(19) ifType has been obsoleted, so this MIB does not list it as a supported ifType. (15) Textual Conventions for statistics objects have been used. (16) A new object, dsx1LoopbackStatus, has been introduced to reflect the loopbacks established on a DS1 interface and the source to the requests. dsx1LoopbackConfig continues to be the desired loopback state while dsx1LoopbackStatus reflects the actual state. (17) A dual loopback has been added to allow the setting of an inward loopback and a line loopback at the same time. (18) An object indicating which channel to use within a parent object (i.e., DS3) has been added.
Nicklass, Ed. Standards Track [Page 22] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 22] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
(19) An object has been added to indicate whether or
not this DS1/E1 is channelized.
(20) Line coding type of B6ZS has been added for DS2."
(19) An object has been added to indicate whether or not this DS1/E1 is channelized. (20) Line coding type of B6ZS has been added for DS2."
REVISION "199301252028Z"
DESCRIPTION
"Initial version, published as RFC 1406."
::= { transmission 18 }
REVISION "199301252028Z" DESCRIPTION "Initial version, published as RFC 1406." ::= { transmission 18 }
-- note that this subsumes cept(19) and g703at2mb(67) -- there is no separate CEPT or G703AT2MB MIB -- The DS1 Near End Group
-- note that this subsumes cept(19) and g703at2mb(67) -- there is no separate CEPT or G703AT2MB MIB -- The DS1 Near End Group
-- The DS1 Near End Group consists of five tables: -- DS1 Configuration -- DS1 Current -- DS1 Interval -- DS1 Total -- DS1 Channel Table
-- The DS1 Near End Group consists of five tables: -- DS1 Configuration -- DS1 Current -- DS1 Interval -- DS1 Total -- DS1 Channel Table
-- The DS1 Configuration Table
-- The DS1 Configuration Table
dsx1ConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1ConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Configuration table."
::= { ds1 6 }
dsx1ConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF Dsx1ConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The DS1 Configuration table." ::= { ds1 6 }
dsx1ConfigEntry OBJECT-TYPE
SYNTAX Dsx1ConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Configuration table."
INDEX { dsx1LineIndex }
::= { dsx1ConfigTable 1 }
「DS1 Configurationのエントリーはテーブルの上に置く」dsx1ConfigEntry OBJECT-TYPE SYNTAX Dsx1ConfigEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1LineIndexに索引をつけてください:、:= dsx1ConfigTable1
Dsx1ConfigEntry ::=
SEQUENCE {
dsx1LineIndex InterfaceIndex,
dsx1IfIndex InterfaceIndex,
dsx1TimeElapsed INTEGER,
dsx1ValidIntervals INTEGER,
dsx1LineType INTEGER,
dsx1LineCoding INTEGER,
dsx1SendCode INTEGER,
Dsx1ConfigEntry:、:= 系列、dsx1LineIndex InterfaceIndex、dsx1IfIndex InterfaceIndex、dsx1TimeElapsed整数、dsx1ValidIntervals整数、dsx1LineType整数、dsx1LineCoding整数、dsx1SendCode整数
Nicklass, Ed. Standards Track [Page 23] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[23ページ]RFC
dsx1CircuitIdentifier DisplayString,
dsx1LoopbackConfig INTEGER,
dsx1LineStatus INTEGER,
dsx1SignalMode INTEGER,
dsx1TransmitClockSource INTEGER,
dsx1Fdl INTEGER,
dsx1InvalidIntervals INTEGER,
dsx1LineLength INTEGER,
dsx1LineStatusLastChange TimeStamp,
dsx1LineStatusChangeTrapEnable INTEGER,
dsx1LoopbackStatus INTEGER,
dsx1Ds1ChannelNumber INTEGER,
dsx1Channelization INTEGER,
dsx1LineMode INTEGER,
dsx1LineBuildOut INTEGER,
dsx1LineImpedance INTEGER
}
dsx1CircuitIdentifier DisplayString、dsx1LoopbackConfig整数、dsx1LineStatus整数、dsx1SignalMode整数、dsx1TransmitClockSource整数、dsx1Fdl整数、dsx1InvalidIntervals整数、dsx1LineLength整数、dsx1LineStatusLastChangeタイムスタンプ、dsx1LineStatusChangeTrapEnable整数、dsx1LoopbackStatus整数、dsx1Ds1ChannelNumber整数、dsx1Channelization整数、dsx1LineMode整数、dsx1LineBuildOut整数、dsx1LineImpedance整数
dsx1LineIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"This object should be made equal to ifIndex. The
next paragraph describes its previous usage.
Making the object equal to ifIndex allows proper
use of the ifStackTable and ds0/ds0bundle MIBs.
dsx1LineIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--SMIv1インデックスSTATUS現在の記述は「ifIndexと等しく作これが反対するされているべきである」。 次のパラグラフは前の用法を説明します。 物をifIndexと等しくすると、ifStackTableとds0/ds0bundle MIBsの適切な使用は許容されます。
Previously, this object was the identifier of a DS1
interface on a managed device. If there is an
ifEntry that is directly associated with this and
only this DS1 interface, it should have the same
value as ifIndex. Otherwise, number the
dsx1LineIndices with a unique identifier
following the rules of choosing a number that is
greater than ifNumber and numbering the inside
interfaces (e.g., equipment side) with even
numbers and outside interfaces (e.g., network
side) with odd numbers."
::= { dsx1ConfigEntry 1 }
以前、この物は管理された装置の上のDS1インタフェースに関する識別子でした。 直接これに関連しているifEntryとこのDS1インタフェースしかなければ、それには、ifIndexと同じ値があるべきです。 「さもなければ、ユニークな識別子がifNumberより大きい数を選んで、内部に付番する規則に従っているdsx1LineIndicesが偶数と外部に連結する(例えば、設備側)数は(例えば、ネットワーク側)を奇数に連結します。」 ::= dsx1ConfigEntry1
dsx1IfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"This value for this object is equal to the value
dsx1IfIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止STATUSが記述を非難した、「この物のためのこの値は値と等しいです」。
Nicklass, Ed. Standards Track [Page 24] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[24ページ]RFC
of ifIndex from the Interfaces table (RFC 2863)."
::= { dsx1ConfigEntry 2 }
「InterfacesからのifIndexでは、(RFC2863)をテーブルの上に置いてください。」 ::= dsx1ConfigEntry2
dsx1TimeElapsed OBJECT-TYPE
SYNTAX INTEGER (0..899)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds that have elapsed since the
beginning of the near-end current error-
measurement period. If, for some reason, such as
an adjustment in the system's time-of-day clock,
the current interval exceeds the maximum value,
the agent will return the maximum value."
::= { dsx1ConfigEntry 3 }
dsx1TimeElapsed OBJECT-TYPE SYNTAX INTEGER(0 .899)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「終わり頃の現在の誤り測定の期間の初め以来経過している秒数。」 「現在の間隔がシステムの時刻時計での調整などの何らかの理由で最大値を超えていると、エージェントは最大値を返すでしょう。」 ::= dsx1ConfigEntry3
dsx1ValidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of previous near-end intervals for
which data was collected. The value will be 96
unless the interface was brought online within the
last 24 hours, in which case the value will be the
number of complete 15-minute near-end intervals
since the interface has been online. In the case
where the agent is a proxy, it is possible that
some intervals are unavailable. In this case,
this interval is the maximum interval number for
which data is available."
::= { dsx1ConfigEntry 4 }
dsx1ValidIntervals OBJECT-TYPE SYNTAX INTEGER(0 .96)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「終わり頃のデータが集められた前の間隔の数。」 インタフェースがオンラインでここ24時間の範囲内に収められなかったなら値が96になる、その場合、インタフェースがオンラインであったので、値は終わり頃の完全な15分の間隔の数になるでしょう。 エージェントがプロキシである場合では、いくつかの間隔が入手できないのは、可能です。 「この場合、この間隔はデータが利用可能である最大の間隔番号です。」 ::= dsx1ConfigEntry4
dsx1LineType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
dsx1ESF(2),
dsx1D4(3),
dsx1E1(4),
dsx1E1CRC(5),
dsx1E1MF(6),
dsx1E1CRCMF(7),
dsx1Unframed(8),
dsx1E1Unframed(9),
dsx1DS2M12(10),
dsx1E2(11),
dsx1E1Q50(12),
dsx1E1Q50CRC(13),
dsx1LineType OBJECT-TYPE SYNTAX INTEGER、他の(1)、dsx1ESF(2)、dsx1D4(3)、dsx1E1(4)、dsx1E1CRC(5)、dsx1E1MF(6)、dsx1E1CRCMF(7)、dsx1Unframed(8)、dsx1E1Unframed(9)、dsx1DS2M12(10)、dsx1E2(11)、dsx1E1Q50(12)、dsx1E1Q50CRC(13)
Nicklass, Ed. Standards Track [Page 25] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[25ページ]RFC
dsx1J1ESF(14),
dsx1J1Unframed(16)
}
MAX-ACCESS read-write
STATUS current
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:
dsx1J1ESF(14)、dsx1J1Unframed(16) マックス-ACCESSは「この変数はこのサーキットを実行するDS1線のバラエティーを示すこと」をSTATUSの現在の記述に読書して書きます。 サーキットのタイプはサーキットが合理的に運ぶことができるbpsの数、および用法と誤り統計の解釈に影響します。 値は連続して以下について説明します。
TITLE: SPECIFICATION:
dsx1ESF Extended SuperFrame DS1
(T1.107)
dsx1D4 AT&T D4 format DS1 (T1.107)
dsx1E1 ITU-T G.704, (Table 5A)
dsx1E1-CRC ITU-T G.704, (Table 5B)
dsxE1-MF G.704 (Table 5A) with TS16
multiframing enabled
dsx1E1-CRC-MF G.704 (Table 5B) with TS16
multiframing enabled
dsx1Unframed DS1 with No Framing
dsx1E1Unframed E1 with No Framing (G.703)
dsx1DS2M12 DS2 frame format (T1.107)
dsx1E2 E2 frame format (G.704)
dsx1E1Q50 TS16 bits 5,7,8 set to 101,
[in all other cases it is set
to 111.] (G.704, table 14)
dsx1E1Q50CRC E1Q50 with CRC
dsx1J1ESF J1 according to (JT-G704,
JT-G706, and JT-I431)
dsx1J1Unframed J1 with No Framing
タイトル: 仕様: dsx1ESF Extended SuperFrame DS1(T1.107)dsx1D4 AT&T D4形式DS1(T1.107)dsx1E1ITU-T G.704、(テーブル5A)dsx1E1-CRC ITU-T G.704、TS16 multiframingと(テーブル5B)dsxE1-MF G.704(テーブル5A)はdsx1E1-CRC-MF G.704を有効にしました。Framing(G.703)dsx1DS2M12 DS2フレーム形式(T1.107)dsx1E2 2Eのフレーム形式(G.704)dsx1E1Q50 TS16ビット5、7、8が全く101にセットしていなくTS16 multiframingがある(テーブル5B)がいいえ、Framing dsx1E1Unframedと共にdsx1Unframed DS1を1E有効にした、[他のすべての場合では、それは111に設定されます] (G.704、テーブル14) 縁どりのない(JT-G704、JT-G706、およびJT-I431)dsx1J1Unframed J1に従ったCRC dsx1J1ESF J1とdsx1E1Q50CRC E1Q50
For clarification, the capacity for each E1 type
is as listed below:
dsx1E1Unframed - E1, no framing = 32 x 64k = 2048k
dsx1E1 or dsx1E1CRC - E1, with framing,
no signalling = 31 x 64k = 1984k
dsx1E1MF or dsx1E1CRCMF - E1, with framing,
signalling = 30 x 64k = 1920k"
REFERENCE
"American National Standard for
telecommunications -
digital hierarchy - formats specification,
ANSI T1.107- 1988.
ITU-T G.703: Physical/Electrical Characteristics
明確化において、1Eのタイプのためのそれぞれの容量は以下に同じくらい記載されています: 「dsx1E1Unframed--32の1E、x64k=2048k dsx1E1または縁どりでない=dsx1E1CRC--1E、縁どりで、合図は31のx64k=1984k dsx1E1MFかdsx1E1CRCMFと等しくはありません--1Eです、縁どりで、合図は30x64k=1920kと等しく」REFERENCE「テレコミュニケーション(デジタル階層構造)形式仕様のための米国標準規格、ANSI T1.107 1988」。 ITU-T G.703: 物理的であるか電気の特性
Nicklass, Ed. Standards Track [Page 26] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[26ページ]RFC
of Hierarchical Digital Interfaces, November
2001.
ITU-T G.704: Synchronous frame structures used at
1544, 6312, 2048, 8488 and 44 736 kbit/s
Hierarchical Levels, July 1995.
JT-G704: Synchronous frame structures used at
Primary and Secondary Hierarchical Levels,2002.
JT-G706. Frame Alignment and Cyclic Redundancy
Check (CRC) Procedures.
JT-I431. ISDN Primary Rate User-Network Interface,
Layer 1 Specifications, 2002 "
::= { dsx1ConfigEntry 5 }
階層的なデジタルインタフェース、2001年11月について。 ITU-T G.704: 同期枠組構造は1544、6312、2048、8488、および44歳のときに736kbit/s Hierarchical Levels、1995年7月を使用しました。 JT-G704: PrimaryとSecondary Hierarchical Levels、2002で使用される同期枠組構造。 JT-G706。 整列と周期冗長検査(CRC)手順を縁どってください。 JT-I431。 ISDNの第一のレートユーザネットワーク・インターフェース、層1の仕様、2002、「:、:、」= dsx1ConfigEntry5
dsx1LineCoding OBJECT-TYPE
SYNTAX INTEGER {
dsx1JBZS(1),
dsx1B8ZS(2),
dsx1HDB3(3),
dsx1ZBTSI(4),
dsx1AMI(5),
other(6),
dsx1B6ZS(7)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable describes the variety of Zero Code
Suppression used on this interface, which in turn
affects a number of its characteristics.
dsx1LineCoding OBJECT-TYPE SYNTAX INTEGER、dsx1JBZS(1)、dsx1B8ZS(2)、dsx1HDB3(3)、dsx1ZBTSI(4)、dsx1AMI(5)、他の(6)、dsx1B6ZS(7)、マックス-ACCESSは「この変数は順番に多くの特性に影響するこのインタフェースで使用されるZero Code Suppressionのバラエティーについて説明すること」をSTATUSの現在の記述に読書して書きます。
dsx1JBZS refers the Jammed Bit Zero Suppression,
in which the AT&T specification of at least one
pulse every 8-bit period is literally implemented
by forcing a pulse in bit 8 of each channel.
Thus, only 7 bits per channel, or 1.344 Mbps,
are available for data.
dsx1JBZSはJammed Bit Zero Suppressionを参照します。そこでは、少なくとも1パルスのAT&T仕様が、いつも8ビットの期間にそれぞれのチャンネルのビット8を1パルス押し込めることによって、文字通り履行されます。 1チャンネルあたり7ビット、または1.344Mbpsだけがデータに有効です。
dsx1B8ZS refers to the use of a specified pattern
of normal bits and bipolar violations that are
used to replace a sequence of 8 zero bits.
ANSI Clear Channels may use dsx1ZBTSI, or Zero
Byte Time Slot Interchange.
dsx1B8ZSは8ゼロ・ビットの系列を置き換えるのに使用される標準のビットとバイポーラ違反の指定されたパターンの使用について言及します。 ANSI Clear Channelsはdsx1ZBTSI、またはZero Byte Time Slot Interchangeを使用するかもしれません。
E1 links, with or without CRC, use dsx1HDB3 or
dsx1AMI.
CRCのあるなしにかかわらず、1Eのリンクがdsx1HDB3かdsx1AMIを使用します。
dsx1AMI refers to a mode wherein no Zero Code
Suppression is present and the line encoding does
dsx1AMIはZero Code Suppressionがないのが存在させているモードとコード化がする線を示します。
Nicklass, Ed. Standards Track [Page 27] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[27ページ]RFC
not solve the problem directly. In this
application, the higher layer must provide data
that meets or exceeds the pulse density
requirements, such as inverting HDLC data.
直接問題を解決してください。 このアプリケーションに、より高い層はパルス密度必要条件を満たすか、または超えているデータを提供しなければなりません、HDLCデータを逆にするのなどように。
dsx1B6ZS refers to the user of a specified pattern
of normal bits and bipolar violations that are
used to replace a sequence of 6 zero bits. Used
for DS2.
For more information about line coding see
[ANSI-T1.102]"
::= { dsx1ConfigEntry 6 }
dsx1B6ZSは6ゼロ・ビットの系列を置き換えるのに使用される標準のビットとバイポーラ違反の指定されたパターンのユーザについて言及します。 DS2において、使用されています。 「ラインコード方式に関する詳しい情報に関して、[ANSI-T1.102]を見てください」:、:= dsx1ConfigEntry6
dsx1SendCode OBJECT-TYPE
SYNTAX INTEGER {
dsx1SendNoCode(1),
dsx1SendLineCode(2),
dsx1SendPayloadCode(3),
dsx1SendResetCode(4),
dsx1SendQRS(5),
dsx1Send511Pattern(6),
dsx1Send3in24Pattern(7),
dsx1SendOtherTestPattern(8)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates what type of code is
being sent across the DS1 interface by the device.
Setting this variable causes the interface to send
the code requested. The values mean the following:
dsx1SendCode OBJECT-TYPE SYNTAX INTEGER、dsx1SendNoCode(1)、dsx1SendLineCode(2)、dsx1SendPayloadCode(3)、dsx1SendResetCode(4)、dsx1SendQRS(5)、dsx1Send511Pattern(6)、dsx1Send3in24Pattern(7)、dsx1SendOtherTestPattern(8)、マックス-ACCESSは「この変数は、どんなタイプのコードがDS1インタフェースの向こう側に装置によって送られるかを示すこと」をSTATUSの現在の記述に読書して書きます。 この変数を設定するのに、インタフェースは要求されたコードを送ります。 値は以下を意味します:
dsx1SendNoCode
sending looped or normal data
dsx1SendNoCodeの送付の輪にされたか正常なデータ
dsx1SendLineCode
sending a request for a line loopback
線ループバックを求める要求を送るdsx1SendLineCode
dsx1SendPayloadCode
sending a request for a payload loopback
ペイロードループバックを求める要求を送るdsx1SendPayloadCode
dsx1SendResetCode
sending a loopback termination request
ループバック終了要求を送るdsx1SendResetCode
dsx1SendQRS
sending a Quasi-Random Signal (QRS) test
pattern
Quasi無作為のSignal(QRS)テストパターンを送るdsx1SendQRS
Nicklass, Ed. Standards Track [Page 28] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[28ページ]RFC
dsx1Send511Pattern
sending a 511-bit fixed test pattern
511ビットの固定テストパターンを送るdsx1Send511Pattern
dsx1Send3in24Pattern
sending a fixed test pattern of 3 bits set
in 24
3ビットの固定テストパターンを送るdsx1Send3in24Patternが24でセットしました。
dsx1SendOtherTestPattern
sending a test pattern other than those
described by this object"
::= { dsx1ConfigEntry 7 }
「この物によって説明されたものを除いて、テストを送るdsx1SendOtherTestPatternが型に基づいて作る」:、:= dsx1ConfigEntry7
dsx1CircuitIdentifier OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable contains the transmission vendor's
circuit identifier, for the purpose of
facilitating troubleshooting."
REFERENCE "ITU-T M.1400"
::= { dsx1ConfigEntry 8 }
dsx1CircuitIdentifier OBJECT-TYPE SYNTAX DisplayString(SIZE(0 .255))マックス-ACCESSは「この変数がトランスミッション業者のサーキット識別子を含んでいます、障害調査するのを容易にする目的のために」STATUSの現在の記述に読書して書きます。 参照「ITU-T M.1400」:、:= dsx1ConfigEntry8
dsx1LoopbackConfig OBJECT-TYPE
SYNTAX INTEGER {
dsx1NoLoop(1),
dsx1PayloadLoop(2),
dsx1LineLoop(3),
dsx1OtherLoop(4),
dsx1InwardLoop(5),
dsx1DualLoop(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable represents the desired loopback
configuration of the DS1 interface. Agents
supporting read/write access should return
inconsistentValue in response to a requested
loopback state that the interface does not
support. The values mean:
dsx1LoopbackConfig OBJECT-TYPE SYNTAX INTEGER、dsx1NoLoop(1)、dsx1PayloadLoop(2)、dsx1LineLoop(3)、dsx1OtherLoop(4)、dsx1InwardLoop(5)、dsx1DualLoop(6)、マックス-ACCESSは「この変数はDS1インタフェースの必要なループバック構成を表すこと」をSTATUSの現在の記述に読書して書きます。 支持がインタフェースが支持しない要求されたループバック状態に対応してinconsistentValueを返すべきであるとアクセスに読み込むか、または書くエージェント。 値は以下を意味します。
dsx1NoLoop
not in the loopback state. A device that is not
capable of performing a loopback on the interface
shall always return this as its value.
ループバック状態でないところのdsx1NoLoop。 インタフェースにループバックを実行できない装置は値としていつもこれを返すものとします。
dsx1PayloadLoop
dsx1PayloadLoop
Nicklass, Ed. Standards Track [Page 29] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[29ページ]RFC
the received signal at this interface is looped
through the device. Typically, the received signal
is looped back for retransmission after it has
passed through the device's framing function.
このインタフェースの受信された信号は装置を通して輪にされます。 装置の縁どり機能を通り抜けた後に通常、受信された信号は「再-トランスミッション」のために輪にされます。
dsx1LineLoop
the received signal at this interface does not go
through the device (minimum penetration) but is
looped back out.
このインタフェースの受信された信号がするdsx1LineLoopは装置(最小の浸透)を通りませんが、輪にされた背中は出ていますか?
dsx1OtherLoop
loopbacks that are not defined here.
ここで定義されないdsx1OtherLoopループバック。
dsx1InwardLoop
the transmitted signal at this interface is
looped back and received by the same interface.
What is transmitted onto the line is product
dependent.
これの伝えられた信号が連結するdsx1InwardLoopを輪にし返して、同じインタフェースは受け取ります。 線に送られることは製品に依存しています。
dsx1DualLoop
both dsx1LineLoop and dsx1InwardLoop will be
active simultaneously."
::= { dsx1ConfigEntry 9 }
「dsx1DualLoop、dsx1LineLoopとdsx1InwardLoopの両方が同時にアクティブになる、」 ::= dsx1ConfigEntry9
dsx1LineStatus OBJECT-TYPE
SYNTAX INTEGER (1..131071)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates the line status of the
interface. It contains loopback, failure,
received alarm and transmitted alarms
information.
dsx1LineStatus OBJECT-TYPE SYNTAX INTEGER(1 .131071)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「この変数はインタフェースの線状態を示します」。 それはループバック、失敗、受信されたアラーム、および伝えられたアラーム情報を含んでいます。
The dsx1LineStatus is a bitmap represented as a
sum; therefore, it can represent multiple failures
(alarms) and a LoopbackState simultaneously.
dsx1LineStatusは合計として表されたビットマップです。 したがって、それは同時に、複数の失敗(アラーム)とLoopbackStateを表すことができます。
dsx1NoAlarm must be set if and only if no other
flag is set.
そして、dsx1NoAlarmが用意ができなければならない、他の旗が全く設定されない場合にだけ。
If the dsx1loopbackState bit is set, the loopback
in effect can be determined from the
dsx1loopbackConfig object. The various bit
positions are as follows:
dsx1loopbackStateビットが設定されるなら、事実上、ループバックはdsx1loopbackConfig物から決定できます。 様々なビット位置は以下の通りです:
1 dsx1NoAlarm No alarm present
2 dsx1RcvFarEndLOF Far end LOF (a.k.a.
1つのdsx1NoAlarmいいえアラーム現在の2dsx1RcvFarEndLOF FarがLOFを終わらせる、(別名
Nicklass, Ed. Standards Track [Page 30] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[30ページ]RFC
Yellow Alarm)
4 dsx1XmtFarEndLOF Near end sending LOF
indication
8 dsx1RcvAIS Far end sending AIS
16 dsx1XmtAIS Near end sending AIS
32 dsx1LossOfFrame Near end LOF (a.k.a.
Red Alarm)
64 dsx1LossOfSignal Near end Loss of Signal
128 dsx1LoopbackState Near end is looped
256 dsx1T16AIS E1 TS16 AIS
512 dsx1RcvFarEndLOMF Far end sending TS16 LOMF
1024 dsx1XmtFarEndLOMF Near end sending TS16 LOMF
2048 dsx1RcvTestCode Near end detects a test code
4096 dsx1OtherFailure Any line status not defined
here
8192 dsx1UnavailSigState Near end in unavailable
signal state
16384 dsx1NetEquipOOS Carrier equipment out of
service
32768 dsx1RcvPayloadAIS DS2 payload AIS
65536 dsx1Ds2PerfThreshold DS2 performance threshold
exceeded"
::= { dsx1ConfigEntry 10 }
黄色いアラーム) 4 dsx1XmtFarEndLOF Near終わりの送付LOF指示8dsx1RcvAIS Far終わりの送付AIS16dsx1XmtAIS Near終わりの送付AIS32dsx1LossOfFrame Near終わりのLOF(通称Red Alarm) 64 dsx1LoopbackState Nearが終わらせるSignal128のdsx1LossOfSignal Near終わりのLossは2048年のTS16 LOMF dsx1RcvTestCode Nearエンドが検出するTS16 LOMF1024dsx1XmtFarEndLOMF Near終わりの発信にテスト・コード4096を送る1EのTS16 AIS512dsx1RcvFarEndLOMF Farが終わらせる256輪にされたdsx1T16AISです; 「dsx1OtherFailure Any線状態はここでAIS65536dsx1Ds2PerfThreshold DS2性能敷居が超えていた入手できない信号州16384のdsx1NetEquipOOS Carrier設備使われなくなっている32768dsx1RcvPayloadAIS DS2ペイロードへの8192年のdsx1UnavailSigState Nearエンドを定義しませんでした」:; := dsx1ConfigEntry10
dsx1SignalMode OBJECT-TYPE
SYNTAX INTEGER {
none(1),
robbedBit(2),
bitOriented(3),
messageOriented(4),
other(5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"'none' indicates that no bits are reserved for
signaling on this channel.
dsx1SignalMode OBJECT-TYPE SYNTAX INTEGER、なにも、(1)、robbedBit(2)、bitOriented(3)、messageOriented(4)、他の(5)、マックス-ACCESSは「'なにも'は、ビットが全くこのチャンネルの上に合図するために予約されないのを示すこと」をSTATUSの現在の記述に読書して書きます。
'robbedBit' indicates that DS1 Robbed Bit Signaling
is in use.
'robbedBit'は、DS1 Robbed Bit Signalingが使用中であることを示します。
'bitOriented' indicates that E1 Channel Associated
Signaling is in use.
'bitOrientedされたこと'は、1EのChannel Associated Signalingが使用中であることを示します。
'messageOriented' indicates that Common Channel
Signaling is in use on either channel 16 of
an E1 link or channel 24 of a DS1."
::= { dsx1ConfigEntry 11 }
「'messageOrientedされたこと'は、Common Channel Signalingが1Eのリンクのチャンネル16かDS1のチャンネル24のどちらかに使用中であることを示します。」 ::= dsx1ConfigEntry11
Nicklass, Ed. Standards Track [Page 31] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[31ページ]RFC
dsx1TransmitClockSource OBJECT-TYPE
SYNTAX INTEGER {
loopTiming(1),
localTiming(2),
throughTiming(3),
adaptive (4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The source of transmit clock.
dsx1TransmitClockSource OBJECT-TYPE SYNTAX INTEGER、loopTiming(1)、localTiming(2)、throughTiming(3)、マックス-ACCESSがSTATUS現在の記述を読書して書く適応型の(4)、「ソース、時計を送ってください、」
'loopTiming' indicates that the recovered
receive clock is used as the transmit clock.
'loopTiming'が、回復が使用される時計を受けるのを示す、時計を送ってください。
'localTiming' indicates that a local clock
source is used or when an external clock is
attached to the box containing the interface.
使用されるか、または外部クロックがインタフェースを含む箱に付属しているとき、'localTiming'は、ローカルの時計ソースがそうであることを示します。
'throughTiming' indicates that recovered
receive clock from another interface is used as
the transmit clock.
'throughTiming'が、回復されたそれがインタフェースが使用される別のものから時計を受けるのを示す、時計を送ってください。
'adaptive' indicates that the clock is recovered
based on the data flow and not based on the
physical layer"
::= { dsx1ConfigEntry 12 }
「'適応型'は時計がデータフローに基づいて回収されて、物理的な層に基づいていないのを示す」:、:= dsx1ConfigEntry12
dsx1Fdl OBJECT-TYPE
SYNTAX INTEGER (1..15)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This bitmap describes the use of the
facilities data link and is the sum of the
capabilities. Set any bits that are appropriate:
dsx1Fdl OBJECT-TYPE SYNTAX INTEGER(1 .15)マックス-ACCESSは「このビットマップは、施設のデータ・リンクの使用について説明して、能力の合計です」をSTATUSの現在の記述に読書して書きます。 あらゆる適切なビットを設定してください:
other(1),
dsx1AnsiT1403(2),
dsx1Att54016(4),
dsx1FdlNone(8)
他の(1)、dsx1AnsiT1403(2)、dsx1Att54016(4)、dsx1FdlNone(8)
'other' indicates that a protocol other than
one of the following is used.
'他'は、以下の1つ以外のプロトコルが使用されているのを示します。
'dsx1AnsiT1403' refers to the FDL exchange
recommended by ANSI.
'dsx1AnsiT1403'はANSIによって推薦されたFDL交換について言及します。
Nicklass, Ed. Standards Track [Page 32] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[32ページ]RFC
'dsx1Att54016' refers to ESF FDL exchanges.
'dsx1Att54016'はESF FDL交換について言及します。
'dsx1FdlNone' indicates that the device does
not use the FDL."
::= { dsx1ConfigEntry 13 }
「'dsx1FdlNone'は、装置がFDLを使用しないのを示します。」 ::= dsx1ConfigEntry13
dsx1InvalidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of intervals in the range from 0 to
dsx1ValidIntervals for which no data is available.
This object will typically be zero except in cases
where the data for some intervals is not
available (e.g., in proxy situations)."
::= { dsx1ConfigEntry 14 }
dsx1InvalidIntervals OBJECT-TYPE SYNTAX INTEGER(0 .96)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「0〜データがないのが利用可能であるdsx1ValidIntervalsまでの範囲の間隔の数。」 「この物はいくつかの間隔の間のデータを得ることができない(例えば、プロキシ状況における)ケース以外の通常ゼロになるでしょう。」 ::= dsx1ConfigEntry14
dsx1LineLength OBJECT-TYPE
SYNTAX INTEGER (0..64000)
UNITS "meters"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The length of the DS1 line in meters. This
object provides information for line build-out
circuitry. This object is only useful if the
interface has configurable line build-out
circuitry."
::= { dsx1ConfigEntry 15 }
dsx1LineLength OBJECT-TYPE SYNTAX INTEGER(0 .64000)UNITS「メーター」マックス-ACCESSは「DS1線の長さは中で計量する」現在の記述をSTATUSに読書して書きます。 この物は線外に建て回路のための情報を提供します。 「インタフェースに構成可能な線外に建て回路がある場合にだけ、この物は役に立ちます。」 ::= dsx1ConfigEntry15
dsx1LineStatusLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of MIB II's sysUpTime object at the
time this DS1 entered its current line status
state. If the current state was entered prior to
the last re-initialization of the proxy-agent,
then this object contains a zero value."
::= { dsx1ConfigEntry 16 }
「このDS1が現在行状態州に入ったとき、MIB IIのsysUpTimeの値は反対させる」dsx1LineStatusLastChange OBJECT-TYPE SYNTAX TimeStampのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「現状がプロキシ兼エージェントの最後の再初期化の前に入られたなら、この物はaゼロ値を含んでいます。」 ::= dsx1ConfigEntry16
dsx1LineStatusChangeTrapEnable OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
dsx1LineStatusChangeTrapEnableオブジェクト・タイプ構文整数(1)、身体障害者(2)を可能にします。
Nicklass, Ed. Standards Track [Page 33] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[33ページ]RFC
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether dsx1LineStatusChange traps
should be generated for this interface."
DEFVAL { disabled }
::= { dsx1ConfigEntry 17 }
マックス-ACCESSは現在の記述が「dsx1LineStatusChange罠がこのインタフェースに発生するべきであるか否かに関係なく、示す」STATUSに読書して書きます。 DEFVAL身体障害者:、:= dsx1ConfigEntry17
dsx1LoopbackStatus OBJECT-TYPE
SYNTAX INTEGER (1..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable represents the current state of the
loopback on the DS1 interface. It contains
information about loopbacks established by a
manager and remotely from the far end.
dsx1LoopbackStatus OBJECT-TYPE SYNTAX INTEGER(1 .127)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「この変数はDS1インタフェースにループバックの現状を表します」。 それはマネージャによって確立されたループバックと離れて遠端からの情報を含んでいます。
The dsx1LoopbackStatus is a bitmap represented as
a sum; therefore, it can represent multiple
loopbacks simultaneously.
dsx1LoopbackStatusは合計として表されたビットマップです。 したがって、それは同時に、複数のループバックを表すことができます。
The various bit positions are as follows:
1 dsx1NoLoopback
2 dsx1NearEndPayloadLoopback
4 dsx1NearEndLineLoopback
8 dsx1NearEndOtherLoopback
16 dsx1NearEndInwardLoopback
32 dsx1FarEndPayloadLoopback
64 dsx1FarEndLineLoopback"
様々なビット位置は以下の通りです: 「1dsx1NoLoopback2のdsx1NearEndPayloadLoopback4dsx1NearEndLineLoopback8dsx1NearEndOtherLoopback16dsx1NearEndInwardLoopback32dsx1FarEndPayloadLoopback64dsx1FarEndLineLoopback」
::= { dsx1ConfigEntry 18 }
::= dsx1ConfigEntry18
dsx1Ds1ChannelNumber OBJECT-TYPE
SYNTAX INTEGER (0..28)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable represents the channel number of
the DS1/E1 on its parent DS2/E2 or DS3/E3. A
value of 0 indicates that this DS1/E1 does not
have a parent DS3/E3."
::= { dsx1ConfigEntry 19 }
dsx1Ds1ChannelNumber OBJECT-TYPE SYNTAX INTEGER(0 .28)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「この変数は親の上に1DS1/Eの論理機番を2DS2/Eか3DS3/ユーロ表します」。 「0の値は、この1DS1/Eには親が3DS3/Eいないのを示します。」 ::= dsx1ConfigEntry19
dsx1Channelization OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabledDs0(2),
dsx1Channelization OBJECT-TYPE SYNTAX INTEGER、身体障害者(1)、enabledDs0(2)
Nicklass, Ed. Standards Track [Page 34] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[34ページ]RFC
enabledDs1(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether this DS1/E1 or DS2 is
channelized or unchannelized.
enabledDs1(3) マックス-ACCESSは現在の記述が「この1DS1/EかDS2がchannelizedされるか、またはunchannelizedされることにかかわらず示す」STATUSに読書して書きます。
The value of enabledDs0(2) indicates that this is a
DS1 channelized into DS0s. Setting this value will
cause the creation, and resetting it to disabled(1)
will cause the deletion of entries in the ifTable
for the DS0s that are within the DS1.
enabledDs0(2)の値は、これがDS0sへのDS1 channelizedであることを示します。 この値を設定すると、創造は引き起こされるでしょう、そして、身体障害者(1)にそれをリセットすると、ifTableでのエントリーの削除はDS1の中にあるDS0sのために引き起こされるでしょう。
The value of enabledDs1(3) indicates that this is a
DS2 channelized into DS1s. Setting this value will
cause the creation, and resetting it to disabled(1)
will cause the deletion of entries in the ifTable
for the DS1s that are within the DS2."
enabledDs1(3)の値は、これがDS1sへのDS2 channelizedであることを示します。 「この値を設定すると、創造は引き起こされるでしょう、そして、身体障害者(1)にそれをリセットすると、ifTableでのエントリーの削除はDS2の中にあるDS1sのために引き起こされるでしょう。」
::= { dsx1ConfigEntry 20 }
::= dsx1ConfigEntry20
dsx1LineMode OBJECT-TYPE
SYNTAX INTEGER {
csu(1),
dsu(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This setting puts the T1 framer into either
long-haul (CSU) mode or short-haul (DSU) mode."
::= { dsx1ConfigEntry 21 }
dsx1LineMode OBJECT-TYPE SYNTAX INTEGER、csu(1)、dsu(2)、マックス-ACCESSは「この設定は長期(CSU)モードか近距離(DSU)モードのどちらかにT1喧嘩早い人を入れること」をSTATUSの現在の記述に読書して書きます。 ::= dsx1ConfigEntry21
dsx1LineBuildOut OBJECT-TYPE
SYNTAX INTEGER {
notApplicable(1),
neg75dB(2),
neg15dB(3),
neg225dB(4),
zerodB(5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Attenuation setting for T1 framer in long haul
(CSU) mode. The optional values are -7.5dB,
-15dB, -22.5dB, and 0dB."
dsx1LineBuildOut OBJECT-TYPE SYNTAX INTEGER、notApplicable(1)、neg75dB(2)、neg15dB(3)、neg225dB(4)、zerodB(5)、マックス-ACCESSは「T1喧嘩早い人のために長期(CSU)モードでセットする減衰」をSTATUSの現在の記述に読書して書きます。 「任意の値は、-7.5dBと、-15dBと、-22.5dBと、0dBです。」
Nicklass, Ed. Standards Track [Page 35] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[35ページ]RFC
::= { dsx1ConfigEntry 22 }
::= dsx1ConfigEntry22
dsx1LineImpedance OBJECT-TYPE
SYNTAX INTEGER {
notApplicable(1),
unbalanced75ohms(2),
balanced100ohms(3),
balanced120ohms(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Nominal line impedance. For T1 and J1 lines, the
value is typically balanced100ohms(3). For E1
lines, the value is typically unbalanced75ohms(2)
and balanced120ohms(4). When this object does not
apply, or when the appropriate value is not known,
the value should be set to notApplicable(1)."
::= { dsx1ConfigEntry 23 }
dsx1LineImpedance OBJECT-TYPE SYNTAX INTEGER、notApplicable(1)、unbalanced75ohms(2)、balanced100ohms(3)、マックス-ACCESSがSTATUSの現在の記述「名目上の線路インピーダンス」を読書して書くbalanced120ohms(4)。 T1とJ1線に、通常、値はbalanced100ohms(3)です。 1Eの線に、値は、通常unbalanced75ohms(2)とbalanced120ohms(4)です。 「この物が適用されないか、または適切な値が知られていないとき、値はnotApplicable(1)に設定されるべきです。」 ::= dsx1ConfigEntry23
-- The DS1 Current Table
dsx1CurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1CurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Current table contains various statistics
being collected for the current 15-minute
interval."
::= { ds1 7 }
-- アクセスしやすくないDS1 Current Table dsx1CurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF Dsx1CurrentEntryマックス-ACCESSのSTATUSの現在の記述、「DS1 Currentテーブルは現在の15分の間隔の間に集められる様々な統計を含んでいます」。 ::= ds1 7
dsx1CurrentEntry OBJECT-TYPE
SYNTAX Dsx1CurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Current table."
INDEX { dsx1CurrentIndex }
::= { dsx1CurrentTable 1 }
「DS1 Currentのエントリーはテーブルの上に置く」dsx1CurrentEntry OBJECT-TYPE SYNTAX Dsx1CurrentEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1CurrentIndexに索引をつけてください:、:= dsx1CurrentTable1
Dsx1CurrentEntry ::=
SEQUENCE {
dsx1CurrentIndex InterfaceIndex,
dsx1CurrentESs PerfCurrentCount,
dsx1CurrentSESs PerfCurrentCount,
dsx1CurrentSEFSs PerfCurrentCount,
dsx1CurrentUASs PerfCurrentCount,
dsx1CurrentCSSs PerfCurrentCount,
Dsx1CurrentEntry:、:= 系列、dsx1CurrentIndex InterfaceIndex、dsx1CurrentESs PerfCurrentCount、dsx1CurrentSESs PerfCurrentCount、dsx1CurrentSEFSs PerfCurrentCount、dsx1CurrentUASs PerfCurrentCount、dsx1CurrentCSSs PerfCurrentCount
Nicklass, Ed. Standards Track [Page 36] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[36ページ]RFC
dsx1CurrentPCVs PerfCurrentCount,
dsx1CurrentLESs PerfCurrentCount,
dsx1CurrentBESs PerfCurrentCount,
dsx1CurrentDMs PerfCurrentCount,
dsx1CurrentLCVs PerfCurrentCount
}
dsx1CurrentPCVs PerfCurrentCount、dsx1CurrentLESs PerfCurrentCount、dsx1CurrentBESs PerfCurrentCount、dsx1CurrentDMs PerfCurrentCount、dsx1CurrentLCVs PerfCurrentCount
dsx1CurrentIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The index value that uniquely identifies the DS1
interface 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 as a dsx1LineIndex object instance."
::= { dsx1CurrentEntry 1 }
SMIv1はSTATUS現在の記述に索引をつけます。dsx1CurrentIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値。」 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndex物の例と同じ値によって特定されるように同じインタフェースです。」 ::= dsx1CurrentEntry1
dsx1CurrentESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Errored Seconds."
::= { dsx1CurrentEntry 2 }
dsx1CurrentESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Errored Secondsの数。」 ::= dsx1CurrentEntry2
dsx1CurrentSESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Seconds."
::= { dsx1CurrentEntry 3 }
dsx1CurrentSESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Severely Errored Secondsの数。」 ::= dsx1CurrentEntry3
dsx1CurrentSEFSs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Framing Seconds."
::= { dsx1CurrentEntry 4 }
dsx1CurrentSEFSs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Severely Errored Framing Secondsの数。」 ::= dsx1CurrentEntry4
dsx1CurrentUASs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
dsx1CurrentUASs OBJECT-TYPE SYNTAX PerfCurrentCountマックス-ACCESS書き込み禁止STATUS海流
Nicklass, Ed. Standards Track [Page 37] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[37ページ]RFC
DESCRIPTION
"The number of Unavailable Seconds."
::= { dsx1CurrentEntry 5 }
記述、「Unavailable Secondsの数。」 ::= dsx1CurrentEntry5
dsx1CurrentCSSs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Controlled Slip Seconds."
::= { dsx1CurrentEntry 6 }
dsx1CurrentCSSs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Controlled Slip Secondsの数。」 ::= dsx1CurrentEntry6
dsx1CurrentPCVs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Path Coding Violations."
::= { dsx1CurrentEntry 7 }
dsx1CurrentPCVs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Path Coding Violationsの数。」 ::= dsx1CurrentEntry7
dsx1CurrentLESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Errored Seconds."
::= { dsx1CurrentEntry 8 }
dsx1CurrentLESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「線Errored Secondsの数。」 ::= dsx1CurrentEntry8
dsx1CurrentBESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds."
::= { dsx1CurrentEntry 9 }
dsx1CurrentBESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Bursty Errored Secondsの数。」 ::= dsx1CurrentEntry9
dsx1CurrentDMs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of Degraded Minutes."
::= { dsx1CurrentEntry 10 }
dsx1CurrentDMs OBJECT-TYPE SYNTAX PerfCurrentCountマックス-ACCESS書き込み禁止STATUSは記述を非難しました。「Degraded Minutesの数。」 ::= dsx1CurrentEntry10
dsx1CurrentLCVs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
dsx1CurrentLCVs OBJECT-TYPE SYNTAX PerfCurrentCountマックス-ACCESS書き込み禁止STATUS海流
Nicklass, Ed. Standards Track [Page 38] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[38ページ]RFC
DESCRIPTION
"The number of Line Coding Violations (LCVs)."
::= { dsx1CurrentEntry 11 }
記述、「線Coding Violations(LCVs)の数。」 ::= dsx1CurrentEntry11
-- The DS1 Interval Table
dsx1IntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1IntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Interval table contains various
statistics collected by each DS1 interface over
the previous 24 hours of operation. The past 24
hours are broken into 96 completed 15-minute
intervals. Each row in this table represents one
such interval (identified by dsx1IntervalNumber)
for one specific instance (identified by
dsx1IntervalIndex)."
::= { ds1 8 }
-- アクセスしやすくないDS1 Interval Table dsx1IntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF Dsx1IntervalEntryマックス-ACCESSのSTATUSの現在の記述、「DS1 IntervalテーブルはそれぞれのDS1インタフェースによって前の24時間の操作の上に集められた様々な統計を含んでいます」。 96回の完成した15分の間隔が過去24時間に細かく分けられます。 「このテーブルの各列は1つの特定の例(dsx1IntervalIndexによって特定される)のために、そのような間隔の1つ(dsx1IntervalNumberによって特定される)を表します。」 ::= ds1 8
dsx1IntervalEntry OBJECT-TYPE
SYNTAX Dsx1IntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Interval table."
INDEX { dsx1IntervalIndex, dsx1IntervalNumber }
::= { dsx1IntervalTable 1 }
「DS1 Intervalのエントリーはテーブルの上に置く」dsx1IntervalEntry OBJECT-TYPE SYNTAX Dsx1IntervalEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1IntervalIndex、dsx1IntervalNumberに索引をつけてください:、:= dsx1IntervalTable1
Dsx1IntervalEntry ::=
SEQUENCE {
dsx1IntervalIndex InterfaceIndex,
dsx1IntervalNumber INTEGER,
dsx1IntervalESs PerfIntervalCount,
dsx1IntervalSESs PerfIntervalCount,
dsx1IntervalSEFSs PerfIntervalCount,
dsx1IntervalUASs PerfIntervalCount,
dsx1IntervalCSSs PerfIntervalCount,
dsx1IntervalPCVs PerfIntervalCount,
dsx1IntervalLESs PerfIntervalCount,
dsx1IntervalBESs PerfIntervalCount,
dsx1IntervalDMs PerfIntervalCount,
dsx1IntervalLCVs PerfIntervalCount,
dsx1IntervalValidData TruthValue
}
Dsx1IntervalEntry:、:= 系列dsx1IntervalIndex InterfaceIndex、dsx1IntervalNumber整数、dsx1IntervalESs PerfIntervalCount、dsx1IntervalSESs PerfIntervalCount、dsx1IntervalSEFSs PerfIntervalCount、dsx1IntervalUASs PerfIntervalCount、dsx1IntervalCSSs PerfIntervalCount、dsx1IntervalPCVs PerfIntervalCount、dsx1IntervalLESs PerfIntervalCount、dsx1IntervalBESs PerfIntervalCount、dsx1IntervalDMs PerfIntervalCount、dsx1IntervalLCVs PerfIntervalCount、dsx1IntervalValidData TruthValue
dsx1IntervalIndex OBJECT-TYPE
SYNTAX InterfaceIndex
dsx1IntervalIndexオブジェクト・タイプ構文InterfaceIndex
Nicklass, Ed. Standards Track [Page 39] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[39ページ]RFC
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The index value that uniquely identifies the DS1
interface 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 as a dsx1LineIndex object instance."
::= { dsx1IntervalEntry 1 }
SMIv1はSTATUS現在の記述に索引をつけます。マックス-ACCESS、書き込み禁止--書き込み禁止、元々、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値。」 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndex物の例と同じ値によって特定されるように同じインタフェースです。」 ::= dsx1IntervalEntry1
dsx1IntervalNumber OBJECT-TYPE
SYNTAX INTEGER (1..96)
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"A number between 1 and 96, where 1 is the most
recently completed 15-minute interval and 96 is
the 15-minute interval completed 23 hours and 45
minutes prior to interval 1."
::= { dsx1IntervalEntry 2 }
dsx1IntervalNumber OBJECT-TYPE SYNTAX INTEGER(1 .96)マックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--SMIv1は「1が最も最近完成した15分の間隔であり、96が15分の間隔である1〜96の数は間隔1の23時間と45分前に完成した」STATUSの現在の記述に索引をつけます。 ::= dsx1IntervalEntry2
dsx1IntervalESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Errored Seconds."
::= { dsx1IntervalEntry 3 }
dsx1IntervalESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Errored Secondsの数。」 ::= dsx1IntervalEntry3
dsx1IntervalSESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Seconds."
::= { dsx1IntervalEntry 4 }
dsx1IntervalSESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Severely Errored Secondsの数。」 ::= dsx1IntervalEntry4
dsx1IntervalSEFSs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Framing Seconds."
::= { dsx1IntervalEntry 5 }
dsx1IntervalSEFSs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Severely Errored Framing Secondsの数。」 ::= dsx1IntervalEntry5
dsx1IntervalUASs OBJECT-TYPE
dsx1IntervalUASsオブジェクト・タイプ
Nicklass, Ed. Standards Track [Page 40] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[40ページ]RFC
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds. This object
may decrease if the occurrence of unavailable
seconds occurs across an interval boundary."
::= { dsx1IntervalEntry 6 }
SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Unavailable Secondsの数。」 「入手できない秒の発生が間隔境界の向こう側に起こるなら、この物は減少するかもしれません。」 ::= dsx1IntervalEntry6
dsx1IntervalCSSs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Controlled Slip Seconds."
::= { dsx1IntervalEntry 7 }
dsx1IntervalCSSs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Controlled Slip Secondsの数。」 ::= dsx1IntervalEntry7
dsx1IntervalPCVs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Path Coding Violations."
::= { dsx1IntervalEntry 8 }
dsx1IntervalPCVs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Path Coding Violationsの数。」 ::= dsx1IntervalEntry8
dsx1IntervalLESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Errored Seconds."
::= { dsx1IntervalEntry 9 }
dsx1IntervalLESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「線Errored Secondsの数。」 ::= dsx1IntervalEntry9
dsx1IntervalBESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds."
::= { dsx1IntervalEntry 10 }
dsx1IntervalBESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Bursty Errored Secondsの数。」 ::= dsx1IntervalEntry10
dsx1IntervalDMs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of Degraded Minutes."
::= { dsx1IntervalEntry 11 }
dsx1IntervalDMs OBJECT-TYPE SYNTAX PerfIntervalCountマックス-ACCESS書き込み禁止STATUSは記述を非難しました。「Degraded Minutesの数。」 ::= dsx1IntervalEntry11
Nicklass, Ed. Standards Track [Page 41] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[41ページ]RFC
dsx1IntervalLCVs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Coding Violations."
::= { dsx1IntervalEntry 12 }
dsx1IntervalLCVs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「線Coding Violationsの数。」 ::= dsx1IntervalEntry12
dsx1IntervalValidData OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates whether the data for this
interval is valid."
::= { dsx1IntervalEntry 13 }
「この間隔の間のデータが有効であるか否かに関係なく、この変数は示す」dsx1IntervalValidData OBJECT-TYPE SYNTAX TruthValueのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 ::= dsx1IntervalEntry13
-- The DS1 Total Table
dsx1TotalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1TotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Total table contains the cumulative sum
of the various statistics for the 24-hour period
preceding the current interval."
::= { ds1 9 }
-- アクセスしやすくないDS1 Total Table dsx1TotalTable OBJECT-TYPE SYNTAX SEQUENCE OF Dsx1TotalEntryマックス-ACCESSのSTATUSの現在の記述、「DS1 Totalテーブルは現在の間隔に先行しながら、24時間の期間のための様々な統計の累積合計を含んでいます」。 ::= ds1 9
dsx1TotalEntry OBJECT-TYPE
SYNTAX Dsx1TotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Total table."
INDEX { dsx1TotalIndex }
::= { dsx1TotalTable 1 }
「DS1 Totalのエントリーはテーブルの上に置く」dsx1TotalEntry OBJECT-TYPE SYNTAX Dsx1TotalEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1TotalIndexに索引をつけてください:、:= dsx1TotalTable1
Dsx1TotalEntry ::=
SEQUENCE {
dsx1TotalIndex InterfaceIndex,
dsx1TotalESs PerfTotalCount,
dsx1TotalSESs PerfTotalCount,
dsx1TotalSEFSs PerfTotalCount,
dsx1TotalUASs PerfTotalCount,
dsx1TotalCSSs PerfTotalCount,
dsx1TotalPCVs PerfTotalCount,
dsx1TotalLESs PerfTotalCount,
dsx1TotalBESs PerfTotalCount,
Dsx1TotalEntry:、:= 系列、dsx1TotalIndex InterfaceIndex、dsx1TotalESs PerfTotalCount、dsx1TotalSESs PerfTotalCount、dsx1TotalSEFSs PerfTotalCount、dsx1TotalUASs PerfTotalCount、dsx1TotalCSSs PerfTotalCount、dsx1TotalPCVs PerfTotalCount、dsx1TotalLESs PerfTotalCount、dsx1TotalBESs PerfTotalCount
Nicklass, Ed. Standards Track [Page 42] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[42ページ]RFC
dsx1TotalDMs PerfTotalCount,
dsx1TotalLCVs PerfTotalCount
}
dsx1TotalDMs PerfTotalCount、dsx1TotalLCVs PerfTotalCount
dsx1TotalIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The index value that uniquely identifies the DS1
interface 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 as a dsx1LineIndex object instance."
::= { dsx1TotalEntry 1 }
SMIv1はSTATUS現在の記述に索引をつけます。dsx1TotalIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値。」 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndex物の例と同じ値によって特定されるように同じインタフェースです。」 ::= dsx1TotalEntry1
dsx1TotalESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Errored Seconds encountered by a DS1
interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1TotalEntry 2 }
「Errored Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry2
dsx1TotalSESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
::= { dsx1TotalEntry 3 }
「Severely Errored Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalSESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry3
dsx1TotalSEFSs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Framing Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
::= { dsx1TotalEntry 4 }
「Severely Errored Framing Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalSEFSs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry4
Nicklass, Ed. Standards Track [Page 43] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[43ページ]RFC
dsx1TotalUASs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered by
a DS1 interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1TotalEntry 5 }
「Unavailable Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalUASs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry5
dsx1TotalCSSs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Controlled Slip Seconds encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
::= { dsx1TotalEntry 6 }
「Controlled Slip Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalCSSs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry6
dsx1TotalPCVs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Path Coding Violations encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
::= { dsx1TotalEntry 7 }
「Path Coding Violationsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalPCVs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry7
dsx1TotalLESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Errored Seconds encountered by
a DS1 interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1TotalEntry 8 }
「線Errored Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalLESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry8
dsx1TotalBESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
dsx1TotalBESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述は「Bursty Errored Secondsの数」です。(BESs)
Nicklass, Ed. Standards Track [Page 44] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[44ページ]RFC
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals count
as 0."
::= { dsx1TotalEntry 9 }
前の24時間の間隔のDS1インタフェースで、遭遇します。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry9
dsx1TotalDMs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of Degraded Minutes (DMs) encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
::= { dsx1TotalEntry 10 }
dsx1TotalDMs OBJECT-TYPE SYNTAX PerfTotalCountマックス-ACCESS書き込み禁止STATUSは「Degraded Minutes(DMs)の数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」記述を非難しました。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry10
dsx1TotalLCVs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Coding Violations (LCVs)
encountered by a DS1 interface in the current
15-minute interval. Invalid 15-minute intervals
count as 0."
::= { dsx1TotalEntry 11 }
「線Coding Violations(LCVs)の数は現在の15分の間隔のDS1インタフェースのそばで遭遇した」dsx1TotalLCVs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1TotalEntry11
-- The DS1 Channel Table
-- DS1チャンネルテーブル
dsx1ChanMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1ChanMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Channel Mapping table. This table maps a
DS1 channel number on a particular DS3 into an
ifIndex. In the presence of DS2s, this table can
be used to map a DS2 channel number on a DS3 into
an ifIndex, or used to map a DS1 channel number on
a DS2 into an ifIndex."
::= { ds1 16 }
「DS1 Channel Mappingはテーブルの上に置く」dsx1ChanMappingTable OBJECT-TYPEのSYNTAX SEQUENCE OF Dsx1ChanMappingEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 このテーブルは特定のDS3でDS1論理機番をifIndexに写像します。 「DS2sの面前で、DS2でDS1論理機番をifIndexに写像するのにこのテーブルをDS3でDS2論理機番をifIndexに写像するのに使用するか、または使用できます。」 ::= ds1 16
dsx1ChanMappingEntry OBJECT-TYPE
SYNTAX Dsx1ChanMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Channel Mapping table. There
「DS1 Channel Mappingのエントリーはテーブルの上に置く」dsx1ChanMappingEntry OBJECT-TYPE SYNTAX Dsx1ChanMappingEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 そこでは
Nicklass, Ed. Standards Track [Page 45] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[45ページ]RFC
is an entry in this table corresponding to each
DS1 ifEntry within any interface that is
channelized to the individual DS1 ifEntry level.
何か個々のDS1 ifEntryレベルにchannelizedされるインタフェースの中に各DS1 ifEntryに対応するこのテーブルのエントリーがありますか?
This table is intended to facilitate mapping from
channelized interface / channel number to DS1
ifEntry (e.g., mapping (DS3 ifIndex, DS1 channel
number) -> ifIndex).
このテーブルが、channelizedインタフェース/論理機番からDS1 ifEntry(例えば、->ifIndexを写像します(DS3 ifIndex、DS1論理機番))まで写像するのを容易にすることを意図します。
While this table provides information that can
also be found in the ifStackTable and
dsx1ConfigTable, it provides this same information
with a single table lookup, rather than by walking
the ifStackTable to find the various constituent
DS1 ifTable entries, and testing various
dsx1ConfigTable entries to check for the entry
with the applicable DS1 channel number."
INDEX { ifIndex, dsx1Ds1ChannelNumber }
::= { dsx1ChanMappingTable 1 }
「このテーブルはまた、ifStackTableとdsx1ConfigTableで見つけることができる情報を提供しますが、様々な構成しているDS1 ifTableエントリーを見つけるためにifStackTableを押して行くことによってというよりむしろただ一つの索表にこの同じ情報を提供して、適切なDS1論理機番でエントリーがないかどうかチェックするテストの様々なdsx1ConfigTableエントリーを提供します。」 ifIndex、dsx1Ds1ChannelNumberに索引をつけてください:、:= dsx1ChanMappingTable1
Dsx1ChanMappingEntry ::=
SEQUENCE {
dsx1ChanMappedIfIndex InterfaceIndex
}
Dsx1ChanMappingEntry:、:= 系列dsx1ChanMappedIfIndex InterfaceIndex
dsx1ChanMappedIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the ifIndex value assigned
by the agent for the individual DS1 ifEntry that
corresponds to the given DS1 channel number
(specified by the INDEX element
dsx1Ds1ChannelNumber) of the given channelized
interface (specified by INDEX element ifIndex)."
::= { dsx1ChanMappingEntry 1 }
「与えられたchannelizedインタフェース(INDEX要素ifIndexによって指定される)の与えられたDS1論理機番(INDEX要素dsx1Ds1ChannelNumberによって指定される)に対応する個々のDS1 ifEntryのためにエージェントによって割り当てられて、評価この物がifIndexを示すす」dsx1ChanMappedIfIndex OBJECT-TYPE SYNTAX InterfaceIndexのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 ::= dsx1ChanMappingEntry1
-- The DS1 Far End Current Table
-- DS1の遠端の現在のテーブル
dsx1FarEndCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FarEndCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Far End Current table contains various
statistics being collected for the current
15-minute interval. The statistics are collected
dsx1FarEndCurrentTable OBJECT-TYPEのSYNTAX SEQUENCE OF Dsx1FarEndCurrentEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「DS1 Far End Currentテーブルは現在の15分の間隔の間に集められる様々な統計を含んでいます」。 統計は集められます。
Nicklass, Ed. Standards Track [Page 46] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[46ページ]RFC
from the far-end messages on the Facilities Data
Link. The definitions are the same as described
for the near-end information."
::= { ds1 10 }
Facilities Data Linkに関する遠端メッセージから。 「定義は終わり頃の情報のために説明されるのと同じです。」 ::= ds1 10
dsx1FarEndCurrentEntry OBJECT-TYPE
SYNTAX Dsx1FarEndCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Far End Current table."
INDEX { dsx1FarEndCurrentIndex }
::= { dsx1FarEndCurrentTable 1 }
「DS1 Far End Currentのエントリーはテーブルの上に置く」dsx1FarEndCurrentEntry OBJECT-TYPE SYNTAX Dsx1FarEndCurrentEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1FarEndCurrentIndexに索引をつけてください:、:= dsx1FarEndCurrentTable1
Dsx1FarEndCurrentEntry ::=
SEQUENCE {
dsx1FarEndCurrentIndex InterfaceIndex,
dsx1FarEndTimeElapsed INTEGER,
dsx1FarEndValidIntervals INTEGER,
dsx1FarEndCurrentESs PerfCurrentCount,
dsx1FarEndCurrentSESs PerfCurrentCount,
dsx1FarEndCurrentSEFSs PerfCurrentCount,
dsx1FarEndCurrentUASs PerfCurrentCount,
dsx1FarEndCurrentCSSs PerfCurrentCount,
dsx1FarEndCurrentLESs PerfCurrentCount,
dsx1FarEndCurrentPCVs PerfCurrentCount,
dsx1FarEndCurrentBESs PerfCurrentCount,
dsx1FarEndCurrentDMs PerfCurrentCount,
dsx1FarEndInvalidIntervals INTEGER
}
Dsx1FarEndCurrentEntry:、:= 系列dsx1FarEndCurrentIndex InterfaceIndex、dsx1FarEndTimeElapsed整数、dsx1FarEndValidIntervals整数、dsx1FarEndCurrentESs PerfCurrentCount、dsx1FarEndCurrentSESs PerfCurrentCount、dsx1FarEndCurrentSEFSs PerfCurrentCount、dsx1FarEndCurrentUASs PerfCurrentCount、dsx1FarEndCurrentCSSs PerfCurrentCount、dsx1FarEndCurrentLESs PerfCurrentCount、dsx1FarEndCurrentPCVs PerfCurrentCount、dsx1FarEndCurrentBESs PerfCurrentCount、dsx1FarEndCurrentDMs PerfCurrentCount、dsx1FarEndInvalidIntervals整数
dsx1FarEndCurrentIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
index is identical to the interface identified by
the same value of dsx1LineIndex."
::= { dsx1FarEndCurrentEntry 1 }
SMIv1はSTATUS現在の記述に索引をつけます。dsx1FarEndCurrentIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値。」 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndexの同じ値によって特定されたインタフェースと同じです。」 ::= dsx1FarEndCurrentEntry1
dsx1FarEndTimeElapsed OBJECT-TYPE
SYNTAX INTEGER (0..899)
MAX-ACCESS read-only
STATUS current
dsx1FarEndTimeElapsed OBJECT-TYPE SYNTAX INTEGER(0 .899)マックス-ACCESS書き込み禁止STATUS海流
Nicklass, Ed. Standards Track [Page 47] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[47ページ]RFC
DESCRIPTION
"The number of seconds that have elapsed since the
beginning of the far-end current error-measurement
period. If, for some reason, such as an adjustment
in the system's time-of-day clock, the current
interval exceeds the maximum value, the agent will
return the maximum value."
::= { dsx1FarEndCurrentEntry 2 }
記述「遠端の始まり以来経過している秒数の現在の誤り測定の期間。」 「現在の間隔がシステムの時刻時計での調整などの何らかの理由で最大値を超えていると、エージェントは最大値を返すでしょう。」 ::= dsx1FarEndCurrentEntry2
dsx1FarEndValidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of previous far-end intervals for
which data was collected. The value will be 96
unless the interface was brought online within the
last 24 hours, in which case the value will be the
number of complete 15-minute far-end intervals
since the interface has been online. In the case
where the agent is a proxy, it is possible that
some intervals are unavailable. In this case,
this interval is the maximum interval number for
which data is available."
::= { dsx1FarEndCurrentEntry 3 }
dsx1FarEndValidIntervals OBJECT-TYPE SYNTAX INTEGER(0 .96)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「データが集められた前の遠端間隔の数。」 インタフェースがオンラインでここ24時間の範囲内に収められなかったなら値が96になる、その場合、インタフェースがオンラインであったので、値は完全な15分の遠端間隔の数になるでしょう。 エージェントがプロキシである場合では、いくつかの間隔が入手できないのは、可能です。 「この場合、この間隔はデータが利用可能である最大の間隔番号です。」 ::= dsx1FarEndCurrentEntry3
dsx1FarEndCurrentESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Errored Seconds."
::= { dsx1FarEndCurrentEntry 4 }
dsx1FarEndCurrentESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Errored Secondsの数。」 ::= dsx1FarEndCurrentEntry4
dsx1FarEndCurrentSESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Seconds."
::= { dsx1FarEndCurrentEntry 5 }
dsx1FarEndCurrentSESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Severely Errored Secondsの数。」 ::= dsx1FarEndCurrentEntry5
dsx1FarEndCurrentSEFSs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Framing
dsx1FarEndCurrentSEFSs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述は「Far End Severely Errored Framingの数」です。
Nicklass, Ed. Standards Track [Page 48] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[48ページ]RFC
Seconds."
::= { dsx1FarEndCurrentEntry 6 }
「秒。」 ::= dsx1FarEndCurrentEntry6
dsx1FarEndCurrentUASs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds."
::= { dsx1FarEndCurrentEntry 7 }
dsx1FarEndCurrentUASs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Unavailable Secondsの数。」 ::= dsx1FarEndCurrentEntry7
dsx1FarEndCurrentCSSs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Controlled Slip Seconds."
::= { dsx1FarEndCurrentEntry 8 }
dsx1FarEndCurrentCSSs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Controlled Slip Secondsの数。」 ::= dsx1FarEndCurrentEntry8
dsx1FarEndCurrentLESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Line Errored Seconds."
::= { dsx1FarEndCurrentEntry 9 }
dsx1FarEndCurrentLESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End線Errored Secondsの数。」 ::= dsx1FarEndCurrentEntry9
dsx1FarEndCurrentPCVs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Path Coding Violations."
::= { dsx1FarEndCurrentEntry 10 }
dsx1FarEndCurrentPCVs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Path Coding Violationsの数。」 ::= dsx1FarEndCurrentEntry10
dsx1FarEndCurrentBESs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Bursty Errored Seconds."
::= { dsx1FarEndCurrentEntry 11 }
dsx1FarEndCurrentBESs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Bursty Errored Secondsの数。」 ::= dsx1FarEndCurrentEntry11
dsx1FarEndCurrentDMs OBJECT-TYPE
SYNTAX PerfCurrentCount
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
dsx1FarEndCurrentDMs OBJECT-TYPE SYNTAX PerfCurrentCountのマックス-ACCESSの書き込み禁止のSTATUSの推奨しない記述
Nicklass, Ed. Standards Track [Page 49] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[49ページ]RFC
"The number of Far End Degraded Minutes."
::= { dsx1FarEndCurrentEntry 12 }
「Far End Degraded Minutesの数。」 ::= dsx1FarEndCurrentEntry12
dsx1FarEndInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of intervals in the range from 0 to
dsx1FarEndValidIntervals for which no data is
available. This object will typically be zero
except in cases where the data for some intervals
is not available (e.g., in proxy situations)."
::= { dsx1FarEndCurrentEntry 13 }
dsx1FarEndInvalidIntervals OBJECT-TYPE SYNTAX INTEGER(0 .96)のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「0〜データがないのが利用可能であるdsx1FarEndValidIntervalsまでの範囲の間隔の数。」 「この物はいくつかの間隔の間のデータを得ることができない(例えば、プロキシ状況における)ケース以外の通常ゼロになるでしょう。」 ::= dsx1FarEndCurrentEntry13
-- The DS1 Far End Interval Table
-- DS1遠端間隔テーブル
dsx1FarEndIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FarEndIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Far End Interval table contains various
statistics collected by each DS1 interface over
the previous 24 hours of operation. The past 24
hours are broken into 96 completed 15-minute
intervals. Each row in this table represents one
such interval (identified by
dsx1FarEndIntervalNumber) for one specific
instance (identified by dsx1FarEndIntervalIndex)."
::= { ds1 11 }
dsx1FarEndIntervalTable OBJECT-TYPEのSYNTAX SEQUENCE OF Dsx1FarEndIntervalEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「DS1 Far End IntervalテーブルはそれぞれのDS1インタフェースによって前の24時間の操作の上に集められた様々な統計を含んでいます」。 96回の完成した15分の間隔が過去24時間に細かく分けられます。 「このテーブルの各列は1つの特定の例(dsx1FarEndIntervalIndexによって特定される)のために、そのような間隔の1つ(dsx1FarEndIntervalNumberによって特定される)を表します。」 ::= ds1 11
dsx1FarEndIntervalEntry OBJECT-TYPE
SYNTAX Dsx1FarEndIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Far End Interval table."
INDEX { dsx1FarEndIntervalIndex,
dsx1FarEndIntervalNumber }
::= { dsx1FarEndIntervalTable 1 }
「DS1 Far End Intervalのエントリーはテーブルの上に置く」dsx1FarEndIntervalEntry OBJECT-TYPE SYNTAX Dsx1FarEndIntervalEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1FarEndIntervalIndex、dsx1FarEndIntervalNumberに索引をつけてください:、:= dsx1FarEndIntervalTable1
Dsx1FarEndIntervalEntry ::=
SEQUENCE {
dsx1FarEndIntervalIndex InterfaceIndex,
dsx1FarEndIntervalNumber INTEGER,
dsx1FarEndIntervalESs PerfIntervalCount,
dsx1FarEndIntervalSESs PerfIntervalCount,
Dsx1FarEndIntervalEntry:、:= 系列、dsx1FarEndIntervalIndex InterfaceIndex、dsx1FarEndIntervalNumber整数、dsx1FarEndIntervalESs PerfIntervalCount、dsx1FarEndIntervalSESs PerfIntervalCount
Nicklass, Ed. Standards Track [Page 50] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[50ページ]RFC
dsx1FarEndIntervalSEFSs PerfIntervalCount,
dsx1FarEndIntervalUASs PerfIntervalCount,
dsx1FarEndIntervalCSSs PerfIntervalCount,
dsx1FarEndIntervalLESs PerfIntervalCount,
dsx1FarEndIntervalPCVs PerfIntervalCount,
dsx1FarEndIntervalBESs PerfIntervalCount,
dsx1FarEndIntervalDMs PerfIntervalCount,
dsx1FarEndIntervalValidData TruthValue
}
dsx1FarEndIntervalSEFSs PerfIntervalCount、dsx1FarEndIntervalUASs PerfIntervalCount、dsx1FarEndIntervalCSSs PerfIntervalCount、dsx1FarEndIntervalLESs PerfIntervalCount、dsx1FarEndIntervalPCVs PerfIntervalCount、dsx1FarEndIntervalBESs PerfIntervalCount、dsx1FarEndIntervalDMs PerfIntervalCount、dsx1FarEndIntervalValidData TruthValue
dsx1FarEndIntervalIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
index is identical to the interface identified by
the same value of dsx1LineIndex."
::= { dsx1FarEndIntervalEntry 1 }
SMIv1はSTATUS現在の記述に索引をつけます。dsx1FarEndIntervalIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値。」 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndexの同じ値によって特定されたインタフェースと同じです。」 ::= dsx1FarEndIntervalEntry1
dsx1FarEndIntervalNumber OBJECT-TYPE
SYNTAX INTEGER (1..96)
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"A number between 1 and 96, where 1 is the most
recently completed 15-minute interval and 96 is
the 15 minutes interval completed 23 hours and 45
minutes prior to interval 1."
::= { dsx1FarEndIntervalEntry 2 }
dsx1FarEndIntervalNumber OBJECT-TYPE SYNTAX INTEGER(1 .96)マックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--SMIv1は「1が最も最近完成した15分の間隔であり、96が15分の間隔である1〜96の数は間隔1の23時間と45分前に完成した」STATUSの現在の記述に索引をつけます。 ::= dsx1FarEndIntervalEntry2
dsx1FarEndIntervalESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Errored Seconds."
::= { dsx1FarEndIntervalEntry 3 }
dsx1FarEndIntervalESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Errored Secondsの数。」 ::= dsx1FarEndIntervalEntry3
dsx1FarEndIntervalSESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
dsx1FarEndIntervalSESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述
Nicklass, Ed. Standards Track [Page 51] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[51ページ]RFC
"The number of Far End Severely Errored Seconds."
::= { dsx1FarEndIntervalEntry 4 }
「Far End Severely Errored Secondsの数。」 ::= dsx1FarEndIntervalEntry4
dsx1FarEndIntervalSEFSs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Framing
Seconds."
::= { dsx1FarEndIntervalEntry 5 }
dsx1FarEndIntervalSEFSs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Severely Errored Framing Secondsの数。」 ::= dsx1FarEndIntervalEntry5
dsx1FarEndIntervalUASs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds."
::= { dsx1FarEndIntervalEntry 6 }
dsx1FarEndIntervalUASs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Unavailable Secondsの数。」 ::= dsx1FarEndIntervalEntry6
dsx1FarEndIntervalCSSs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Controlled Slip Seconds."
::= { dsx1FarEndIntervalEntry 7 }
dsx1FarEndIntervalCSSs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Controlled Slip Secondsの数。」 ::= dsx1FarEndIntervalEntry7
dsx1FarEndIntervalLESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Line Errored Seconds."
::= { dsx1FarEndIntervalEntry 8 }
dsx1FarEndIntervalLESs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End線Errored Secondsの数。」 ::= dsx1FarEndIntervalEntry8
dsx1FarEndIntervalPCVs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Path Coding Violations."
::= { dsx1FarEndIntervalEntry 9 }
dsx1FarEndIntervalPCVs OBJECT-TYPE SYNTAX PerfIntervalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「Far End Path Coding Violationsの数。」 ::= dsx1FarEndIntervalEntry9
dsx1FarEndIntervalBESs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS current
dsx1FarEndIntervalBESs OBJECT-TYPE SYNTAX PerfIntervalCountマックス-ACCESS書き込み禁止STATUS海流
Nicklass, Ed. Standards Track [Page 52] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[52ページ]RFC
DESCRIPTION
"The number of Far End Bursty Errored Seconds."
::= { dsx1FarEndIntervalEntry 10 }
記述、「Far End Bursty Errored Secondsの数。」 ::= dsx1FarEndIntervalEntry10
dsx1FarEndIntervalDMs OBJECT-TYPE
SYNTAX PerfIntervalCount
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of Far End Degraded Minutes."
::= { dsx1FarEndIntervalEntry 11 }
dsx1FarEndIntervalDMs OBJECT-TYPE SYNTAX PerfIntervalCountマックス-ACCESS書き込み禁止STATUSは記述を非難しました。「Far End Degraded Minutesの数。」 ::= dsx1FarEndIntervalEntry11
dsx1FarEndIntervalValidData OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This variable indicates if the data for this
interval is valid."
::= { dsx1FarEndIntervalEntry 12 }
「この間隔の間のデータが有効であるなら、この変数は示す」dsx1FarEndIntervalValidData OBJECT-TYPE SYNTAX TruthValueのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 ::= dsx1FarEndIntervalEntry12
-- The DS1 Far End Total Table
-- DS1遠端合計テーブル
dsx1FarEndTotalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FarEndTotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Far End Total table contains the
cumulative sum of the various statistics for the
24-hour period preceding the current interval."
::= { ds1 12 }
dsx1FarEndTotalTable OBJECT-TYPEのSYNTAX SEQUENCE OF Dsx1FarEndTotalEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「DS1 Far End Totalテーブルは現在の間隔に先行しながら、24時間の期間のための様々な統計の累積合計を含んでいます」。 ::= ds1 12
dsx1FarEndTotalEntry OBJECT-TYPE
SYNTAX Dsx1FarEndTotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Far End Total table."
INDEX { dsx1FarEndTotalIndex }
::= { dsx1FarEndTotalTable 1 }
「DS1 Far End Totalのエントリーはテーブルの上に置く」dsx1FarEndTotalEntry OBJECT-TYPE SYNTAX Dsx1FarEndTotalEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 dsx1FarEndTotalIndexに索引をつけてください:、:= dsx1FarEndTotalTable1
Dsx1FarEndTotalEntry ::=
SEQUENCE {
dsx1FarEndTotalIndex InterfaceIndex,
dsx1FarEndTotalESs PerfTotalCount,
dsx1FarEndTotalSESs PerfTotalCount,
dsx1FarEndTotalSEFSs PerfTotalCount,
Dsx1FarEndTotalEntry:、:= 系列、dsx1FarEndTotalIndex InterfaceIndex、dsx1FarEndTotalESs PerfTotalCount、dsx1FarEndTotalSESs PerfTotalCount、dsx1FarEndTotalSEFSs PerfTotalCount
Nicklass, Ed. Standards Track [Page 53] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[53ページ]RFC
dsx1FarEndTotalUASs PerfTotalCount,
dsx1FarEndTotalCSSs PerfTotalCount,
dsx1FarEndTotalLESs PerfTotalCount,
dsx1FarEndTotalPCVs PerfTotalCount,
dsx1FarEndTotalBESs PerfTotalCount,
dsx1FarEndTotalDMs PerfTotalCount
}
dsx1FarEndTotalUASs PerfTotalCount、dsx1FarEndTotalCSSs PerfTotalCount、dsx1FarEndTotalLESs PerfTotalCount、dsx1FarEndTotalPCVs PerfTotalCount、dsx1FarEndTotalBESs PerfTotalCount、dsx1FarEndTotalDMs PerfTotalCount
dsx1FarEndTotalIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION
"The index value that uniquely identifies the DS1
interface to which this entry is applicable. The
interface identified by a particular value of this
index is identical to the interface identified by
the same value of dsx1LineIndex."
::= { dsx1FarEndTotalEntry 1 }
SMIv1はSTATUS現在の記述に索引をつけます。dsx1FarEndTotalIndex OBJECT-TYPE SYNTAX InterfaceIndexマックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値。」 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndexの同じ値によって特定されたインタフェースと同じです。」 ::= dsx1FarEndTotalEntry1
dsx1FarEndTotalESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Errored Seconds encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
::= { dsx1FarEndTotalEntry 2 }
「Far End Errored Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1FarEndTotalESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry2
dsx1FarEndTotalSESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 3 }
「Far End Severely Errored Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1FarEndTotalSESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry3
dsx1FarEndTotalSEFSs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
dsx1FarEndTotalSEFSs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述
Nicklass, Ed. Standards Track [Page 54] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[54ページ]RFC
"The number of Far End Severely Errored Framing
Seconds encountered by a DS1 interface in the
previous 24-hour interval. Invalid 15-minute
intervals count as 0."
::= { dsx1FarEndTotalEntry 4 }
「前の24時間の間隔のDS1インタフェースで遭遇するFar End Severely Errored Framing Secondsの数。」 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry4
dsx1FarEndTotalUASs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered by
a DS1 interface in the previous 24-hour interval.
Invalid 15-minute intervals count as 0."
::= { dsx1FarEndTotalEntry 5 }
「Unavailable Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1FarEndTotalUASs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry5
dsx1FarEndTotalCSSs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Controlled Slip Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 6 }
「Far End Controlled Slip Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1FarEndTotalCSSs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「15分の無効の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry6
dsx1FarEndTotalLESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Line Errored Seconds
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 7 }
「Far End線Errored Secondsの数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1FarEndTotalLESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry7
dsx1FarEndTotalPCVs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Path Coding Violations
reported via the far end block error count
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
「Far End Path Coding Violationsの数は前の24時間の間隔でDS1インタフェースで遭遇する遠端ブロック誤り件数で報告した」dsx1FarEndTotalPCVs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」
Nicklass, Ed. Standards Track [Page 55] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[55ページ]RFC
::= { dsx1FarEndTotalEntry 8 }
::= dsx1FarEndTotalEntry8
dsx1FarEndTotalBESs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the previous
24-hour interval. Invalid 15-minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 9 }
「Bursty Errored Seconds(BESs)の数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」dsx1FarEndTotalBESs OBJECT-TYPE SYNTAX PerfTotalCountのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry9
dsx1FarEndTotalDMs OBJECT-TYPE
SYNTAX PerfTotalCount
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of Degraded Minutes (DMs) encountered
by a DS1 interface in the previous 24-hour
interval. Invalid 15-minute intervals count as
0."
::= { dsx1FarEndTotalEntry 10 }
dsx1FarEndTotalDMs OBJECT-TYPE SYNTAX PerfTotalCountマックス-ACCESS書き込み禁止STATUSは「Degraded Minutes(DMs)の数は前の24時間の間隔のDS1インタフェースのそばで遭遇した」記述を非難しました。 「無効の15分の間隔は0にみなします。」 ::= dsx1FarEndTotalEntry10
-- The DS1 Fractional Table
-- DS1の断片的なテーブル
dsx1FracTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FracEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"This table is deprecated in favor of using
ifStackTable.
dsx1FracTable OBJECT-TYPE SYNTAX SEQUENCE OF Dsx1FracEntryのマックス-ACCESSのアクセスしやすくないSTATUSは記述を非難しました。「ifStackTableを使用することを支持してこのテーブルは非難されます」。
The table was mandatory for systems dividing a DS1
into channels containing different data streams
that are of local interest. Systems that are
indifferent to data content, such as CSUs, need
not implement it.
テーブルはDS1を地方におもしろい異なったデータ・ストリームを含むチャンネルに分割するシステムに義務的でした。 CSUsなどのデータ内容にありきたりのシステムはそれを実行する必要はありません。
The DS1 Fractional table 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.
DS1 Fractionalテーブルは、CSUに関連づけられたどのDS1チャンネルが論理的なインタフェースを支持するのに使用されているかを特定して、すなわち、インタフェースのエントリーはインターネット標準MIBからのテーブルです。
For example, consider an application managing a
North American ISDN Primary Rate link whose
division is a 384-kbit/s H1 _B_ Channel for video,
例えば、ビデオのために、分割が384-kbit/s H1_B_Channelである北米のISDN Primary Rateリンクを管理するアプリケーションを考えてください。
Nicklass, Ed. Standards Track [Page 56] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[56ページ]RFC
a second H1 for data to a primary routing peer,
and 12 64-kbit/s H0 _B_ Channels. Consider that
some subset of the H0 channels is used for voice
and the remainder are available for dynamic data
calls.
第一のルーティング同輩、および12 64-kbit/s H0_B_Channelsへのデータのための第2のH1。 H0チャンネルの何らかの部分集合が声に使用されて、残りがダイナミックなデータ呼び出しに利用可能であると考えてください。
We count a total of 14 interfaces multiplexed onto
the DS1 interface. Six DS1 channels (for the sake
of the example, channels 1..6) are used for video,
six more (7..11 and 13) are used for data, and the
remaining 12 are in channels 12 and 14..24.
私たちはDS1インタフェースに多重送信された合計14のインタフェースを数えます。 6個のDS1チャンネル(例のためにチャンネル1.6)がビデオに使用されます、そして、もう6(7 .11と13)はデータに使用されます、そして、残っている12がチャンネル12と14であります。24.
Let us further imagine that ifIndex 2 is of type
DS1 and refers to the DS1 interface and that the
interfaces layered onto it are numbered 3..16.
さらに、ifIndex2がタイプDS1にはあって、DS1インタフェースについて言及して、それに層にされたインタフェースが番号付の3であると想像しましょう。16.
We might describe the allocation of channels, in
the dsx1FracTable, as follows:
dsx1FracIfIndex.2. 1 = 3 dsx1FracIfIndex.2.13 = 4
dsx1FracIfIndex.2. 2 = 3 dsx1FracIfIndex.2.14 = 6
dsx1FracIfIndex.2. 3 = 3 dsx1FracIfIndex.2.15 = 7
dsx1FracIfIndex.2. 4 = 3 dsx1FracIfIndex.2.16 = 8
dsx1FracIfIndex.2. 5 = 3 dsx1FracIfIndex.2.17 = 9
dsx1FracIfIndex.2. 6 = 3 dsx1FracIfIndex.2.18 = 10
dsx1FracIfIndex.2. 7 = 4 dsx1FracIfIndex.2.19 = 11
dsx1FracIfIndex.2. 8 = 4 dsx1FracIfIndex.2.20 = 12
dsx1FracIfIndex.2. 9 = 4 dsx1FracIfIndex.2.21 = 13
dsx1FracIfIndex.2.10 = 4 dsx1FracIfIndex.2.22 = 14
dsx1FracIfIndex.2.11 = 4 dsx1FracIfIndex.2.23 = 15
dsx1FracIfIndex.2.12 = 5 dsx1FracIfIndex.2.24 = 16
私たちは以下の通りdsx1FracTableでのチャンネルの配分について説明するかもしれません: dsx1FracIfIndex.2。 1 = 3 dsx1FracIfIndex.2.13は4dsx1FracIfIndex.2と等しいです。 2 = 3 dsx1FracIfIndex.2.14は6dsx1FracIfIndex.2と等しいです。 3 = 3 dsx1FracIfIndex.2.15は7dsx1FracIfIndex.2と等しいです。 4 = 3 dsx1FracIfIndex.2.16は8dsx1FracIfIndex.2と等しいです。 5 = 3 dsx1FracIfIndex.2.17は9dsx1FracIfIndex.2と等しいです。 6 = 3 dsx1FracIfIndex.2.18は10dsx1FracIfIndex.2と等しいです。 7 = 4 dsx1FracIfIndex.2.19は11dsx1FracIfIndex.2と等しいです。 8 = 4 dsx1FracIfIndex.2.20は12dsx1FracIfIndex.2と等しいです。 9 = 4 dsx1FracIfIndex、.2、.21、=13dsx1FracIfIndex、.2、.10、=4dsx1FracIfIndex、.2、.22、=14dsx1FracIfIndex、.2、.11、=4dsx1FracIfIndex、.2、.23、=15dsx1FracIfIndex、.2、.12、=5dsx1FracIfIndex、.2、.24、=16
For North American (DS1) interfaces, there are 24
legal channels, numbered 1 through 24.
北米の(DS1)インタフェースには、1〜24に付番された24の法的手段があります。
For G.704 interfaces, there are 31 legal channels,
numbered 1 through 31. The channels (1..31)
correspond directly to the equivalently numbered
time-slots."
::= { ds1 13 }
G.704インタフェースには、1〜31に付番された31の法的手段があります。 「チャンネル(1 .31)は直接同等に番号付の時間帯に文通しています。」 ::= ds1 13
dsx1FracEntry OBJECT-TYPE
SYNTAX Dsx1FracEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"An entry in the DS1 Fractional table."
INDEX { dsx1FracIndex, dsx1FracNumber }
::= { dsx1FracTable 1 }
dsx1FracEntry OBJECT-TYPE SYNTAX Dsx1FracEntryのマックス-ACCESSのアクセスしやすくないSTATUSは「DS1 Fractionalのエントリーはテーブルの上に置く」記述を非難しました。 dsx1FracIndex、dsx1FracNumberに索引をつけてください:、:= dsx1FracTable1
Nicklass, Ed. Standards Track [Page 57] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[57ページ]RFC
Dsx1FracEntry ::=
SEQUENCE {
dsx1FracIndex INTEGER,
dsx1FracNumber INTEGER,
dsx1FracIfIndex INTEGER
}
Dsx1FracEntry:、:= 系列dsx1FracIndex整数、dsx1FracNumber整数、dsx1FracIfIndex整数
dsx1FracIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS deprecated
DESCRIPTION
"The index value that uniquely identifies the
DS1 interface 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 as a dsx1LineIndex
object instance."
::= { dsx1FracEntry 1 }
SMIv1インデックスSTATUSは記述を非難しました。dsx1FracIndex OBJECT-TYPE SYNTAX INTEGER(1'7fffffff'h)マックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「唯一このエントリーがどれであるかに適切なDS1インタフェースを特定するインデックス値」、' 「このインデックスの特定の値によって特定されたインタフェースはdsx1LineIndex物の例と同じ値によって特定されるように同じインタフェースです。」 ::= dsx1FracEntry1
dsx1FracNumber OBJECT-TYPE
SYNTAX INTEGER (1..31)
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS deprecated
DESCRIPTION
"The channel number for this entry."
::= { dsx1FracEntry 2 }
SMIv1インデックスSTATUSは記述を非難しました。dsx1FracNumber OBJECT-TYPE SYNTAX INTEGER(1 .31)マックス-ACCESS書き込み禁止--、元々以来の書き込み禁止、--、「このエントリーへの論理機番。」 ::= dsx1FracEntry2
dsx1FracIfIndex OBJECT-TYPE
SYNTAX INTEGER (0..'7fffffff'h)
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"An index value that uniquely identifies an
interface. The interface identified by a particular
value of this index is the same interface
as identified by the same value as an ifIndex
object instance. If no interface is currently using
a channel, the value should be zero. If a
single interface occupies more than one time-slot,
that ifIndex value will be found in multiple
time-slots."
::= { dsx1FracEntry 3 }
dsx1FracIfIndex OBJECT-TYPE SYNTAX INTEGER(0'7fffffff'h)マックス-ACCESSが「唯一インタフェースを特定するインデックス値」をSTATUSの推奨しない記述に読書して書く、' このインデックスの特定の値によって特定されたインタフェースはifIndex物の例と同じ値によって特定されるように同じインタフェースです。 どんなインタフェースも現在チャンネルを使用していないなら、値はゼロであるべきです。 「単一のインタフェースが1つ以上の時間帯を占領すると、そのifIndex値は複数の時間帯で見つけられるでしょう。」 ::= dsx1FracEntry3
-- DS1 TRAPS
-- DS1罠
Nicklass, Ed. Standards Track [Page 58] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[58ページ]RFC
ds1Traps OBJECT IDENTIFIER ::= { ds1 15 }
ds1Traps物の識別子:、:= ds1 15
dsx1LineStatusChange NOTIFICATION-TYPE
OBJECTS { dsx1LineStatus,
dsx1LineStatusLastChange }
STATUS current
DESCRIPTION
"A dsx1LineStatusChange trap is sent when the
value of an instance dsx1LineStatus changes. It
can be utilized by an Network Management Station
(NMS) to trigger polls. When the line status
change results from a higher-level line status
change (i.e., DS3), then no traps for the DS1
are sent."
::= { ds1Traps 0 1 }
dsx1LineStatusChange NOTIFICATION-TYPE OBJECTS、dsx1LineStatus、dsx1LineStatusLastChange、「dsx1LineStatusが変える例の値であるときにdsx1LineStatusChange罠を送る」STATUSの現在の記述。 Network Management駅(NMS)は、投票の引き金となるのにそれを利用できます。 「そして、よりハイレベルの線状態からの線状態変化結果が(すなわち、DS3)を変えるとき、DS1のための罠を全く送りません。」 ::= ds1Traps0 1
-- conformance information
-- 順応情報
ds1Conformance OBJECT IDENTIFIER ::= { ds1 14 }
ds1Conformance物の識別子:、:= ds1 14
ds1Groups OBJECT IDENTIFIER ::= { ds1Conformance 1 }
ds1Compliances OBJECT IDENTIFIER ::= { ds1Conformance 2 }
ds1Groups物の識別子:、:= ds1Conformance1ds1Compliances物の識別子:、:= ds1Conformance2
-- compliance statements
-- 承諾声明
ds1Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for T1 and E1
interfaces."
MODULE -- this module
MANDATORY-GROUPS { ds1NearEndConfigGroup,
ds1NearEndStatisticsGroup }
ds1Compliance MODULE-COMPLIANCE STATUSは「T1と1Eの承諾声明は連結する」記述を非難しました。 MODULE--このモジュールMANDATORY-GROUPSds1NearEndConfigGroup、ds1NearEndStatisticsGroup
GROUP ds1FarEndGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 interface."
GROUP ds1FarEndGroup記述、「DS1インタフェースに付くすべてのシステムに、このグループの実現は任意です」。
GROUP ds1NearEndOptionalConfigGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 interface."
GROUP ds1NearEndOptionalConfigGroup記述、「DS1インタフェースに付くすべてのシステムに、このグループの実現は任意です」。
GROUP ds1DS2Group
DESCRIPTION
"Implementation of this group is mandatory for all
systems that attach to a DS2 interface."
GROUP ds1DS2Group記述、「このグループの実現はDS2インタフェースに付くすべてのシステムに義務的です」。
Nicklass, Ed. Standards Track [Page 59] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[59ページ]RFC
GROUP ds1TransStatsGroup
DESCRIPTION
"This group is the set of statistics appropriate
for all systems that attach to a DS1 interface
running transparent or unFramed lineType."
「このグループは、DS1インタフェース走行に透明な状態で付くすべてのシステムに、適切な統計のセットかunFramed lineType GROUP ds1TransStatsGroup記述です」。
GROUP ds1ChanMappingGroup
DESCRIPTION
"This group is the set of objects for mapping a
DS3 Channel (dsx1Ds1ChannelNumber) to ifIndex.
Implementation of this group is mandatory for
systems that support the channelization of DS3s
into DS1s."
GROUP ds1ChanMappingGroup記述、「このグループはDS3 Channel(dsx1Ds1ChannelNumber)をifIndexに写像するための物のセットです」。 「このグループの実現はDS3sのチャネル化をDS1s.に支持するシステムに義務的です」
OBJECT dsx1LineType
SYNTAX INTEGER {
other(1),
dsx1ESF(2),
dsx1D4(3),
dsx1E1(4),
dsx1E1CRC(5),
dsx1E1MF(6),
dsx1E1CRCMF(7),
dsx1Unframed(8),
dsx1E1Unframed(9),
dsx1DS2M12(10),
dsx1E2(11)
}
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line type is not
required."
OBJECT dsx1LineType SYNTAX INTEGER、他の(1)、dsx1ESF(2)、dsx1D4(3)、dsx1E1(4)、dsx1E1CRC(5)、dsx1E1MF(6)、dsx1E1CRCMF(7)、dsx1Unframed(8)、dsx1E1Unframed(9)、dsx1DS2M12(10)、dsx1E2(11)、MIN-ACCESS書き込み禁止記述、「線タイプを設定する能力は必要ではありません」。
OBJECT dsx1LineCoding
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line coding is not
required."
OBJECT dsx1LineCoding MIN-ACCESS書き込み禁止記述、「ラインコード方式を設定する能力は必要ではありません」。
OBJECT dsx1SendCode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the send code is not
required."
OBJECT dsx1SendCode MIN-ACCESS書き込み禁止記述、「セットする能力、発信、コードは必要でない、」
OBJECT dsx1LoopbackConfig
MIN-ACCESS read-only
DESCRIPTION
OBJECT dsx1LoopbackConfig MIN-ACCESS書き込み禁止記述
Nicklass, Ed. Standards Track [Page 60] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[60ページ]RFC
"The ability to set loopbacks is not required."
「ループバックを設定する能力は必要ではありません。」
OBJECT dsx1SignalMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the signal mode is not
required."
OBJECT dsx1SignalMode MIN-ACCESS書き込み禁止記述、「信号モードを設定する能力は必要ではありません」。
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1),
localTiming(2),
throughTiming(3)
}
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the transmit clock source is
not required."
OBJECT dsx1TransmitClockSource SYNTAX INTEGER、loopTiming(1)、localTiming(2)、throughTiming(3)、MIN-ACCESS書き込み禁止記述、「セットする能力、伝える、時計ソースは必要でない、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the FDL is not required."
OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述、「FDLを設定する能力は必要ではありません」。
OBJECT dsx1LineLength
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line length is not
required."
OBJECT dsx1LineLength MIN-ACCESS書き込み禁止記述、「行長を設定する能力は必要ではありません」。
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization is not
required."
::= { ds1Compliances 1 }
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。 ::= ds1Compliances1
ds1MibT1PriCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"Compliance statement for using this MIB for ISDN
Primary Rate interfaces on T1 lines."
MODULE
MANDATORY-GROUPS { ds1NearEndConfigGroup,
ds1NearEndStatisticsGroup }
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1ESF(2) -- Intl Spec would be G704(2)
「ISDN Primary RateにこのMIBを使用するための承諾声明はT1系列で連結する」ds1MibT1PriCompliance MODULE-COMPLIANCE STATUSの推奨しない記述。 MODULE MANDATORY-GROUPS、ds1NearEndConfigGroup、ds1NearEndStatisticsGroup、OBJECT dsx1LineType SYNTAX INTEGER、dsx1ESF(2)、--Intl SpecがG704であるだろう(2)
Nicklass, Ed. Standards Track [Page 61] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[61ページ]RFC
-- or I.431(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for T1 ISDN Primary Rate
interfaces."
-- I.431(4) MIN-ACCESS書き込み禁止記述は「T1 ISDN Primary Rateインタフェースへのタイプを裏打ちします」。
OBJECT dsx1LineCoding
SYNTAX INTEGER {
dsx1B8ZS(2)
}
MIN-ACCESS read-only
DESCRIPTION
"Type of Zero Code Suppression for
T1 ISDN Primary Rate interfaces."
OBJECT dsx1LineCoding SYNTAX INTEGER dsx1B8ZS(2)、MIN-ACCESSの読書唯一の記述「T1 ISDN Primary RateインタフェースへのタイプのZero Code Suppression。」
OBJECT dsx1SignalMode
SYNTAX INTEGER {
none(1), -- if there is no signaling channel
messageOriented(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Possible signaling modes for
T1 ISDN Primary Rate interfaces."
OBJECT dsx1SignalMode SYNTAX INTEGER、なにも、(1)、チャンネルmessageOriented(4)に合図してはいけない、「T1 ISDN Primary Rateのためにモードに合図するのが連結するのが可能な」MIN-ACCESS書き込み禁止記述。
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1)
}
MIN-ACCESS read-only
DESCRIPTION
"The transmit clock is derived from
received clock on ISDN Primary Rate
interfaces."
OBJECT dsx1TransmitClockSource SYNTAX INTEGER loopTiming(1)、MIN-ACCESS書き込み禁止記述、「ISDN Primary Rateインタフェースで容認された時計から派生していた状態で時計を送ってください、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"Facilities Data Link usage on T1 ISDN
Primary Rate interfaces.
Note: Eventually, dsx1Att-54016(4) is to be
used here since the line type is ESF."
「T1 ISDN Primary Rateの上の施設Data Link用法は連結する」OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述。 以下に注意してください。 「結局、dsx1Att-54016(4)は系列タイプがESFであるので、ここで使用されることになっています。」
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述は「チャネル化を設定する能力」です。
Nicklass, Ed. Standards Track [Page 62] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[62ページ]RFC
is not required."
::= { ds1Compliances 2 }
「必要ではありません。」 ::= ds1Compliances2
ds1MibE1PriCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"Compliance statement for using this MIB for ISDN
Primary Rate interfaces on E1 lines."
MODULE
MANDATORY-GROUPS { ds1NearEndConfigGroup,
ds1NearEndStatisticsGroup }
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1E1CRC(5)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for E1 ISDN Primary Rate
interfaces."
「ISDN Primary RateにこのMIBを使用するための承諾声明は1Eの系列で連結する」ds1MibE1PriCompliance MODULE-COMPLIANCE STATUSの推奨しない記述。 MODULE MANDATORY-GROUPS、ds1NearEndConfigGroup、ds1NearEndStatisticsGroup、OBJECT dsx1LineType SYNTAX INTEGER dsx1E1CRC(5)、MIN-ACCESS読書だけ記述は「1EのISDN Primary Rateインタフェースへのタイプを裏打ちします」。
OBJECT dsx1LineCoding
SYNTAX INTEGER {
dsx1HDB3(3)
}
MIN-ACCESS read-only
DESCRIPTION
"Type of Zero Code Suppression for
E1 ISDN Primary Rate interfaces."
OBJECT dsx1LineCoding SYNTAX INTEGER dsx1HDB3(3)、MIN-ACCESSの読書唯一の記述「1EのISDN Primary RateインタフェースへのタイプのZero Code Suppression。」
OBJECT dsx1SignalMode
SYNTAX INTEGER {
messageOriented(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Signaling on E1 ISDN Primary Rate interfaces
is always message oriented."
OBJECT dsx1SignalMode SYNTAX INTEGER messageOriented(4)、MIN-ACCESS書き込み禁止記述、「1EのISDN Primary Rateインタフェースで合図して、いつもメッセージは適応しますか?」
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1)
}
MIN-ACCESS read-only
DESCRIPTION
"The transmit clock is derived from received
clock on ISDN Primary Rate interfaces."
OBJECT dsx1TransmitClockSource SYNTAX INTEGER loopTiming(1)、MIN-ACCESS書き込み禁止記述、「ISDN Primary Rateインタフェースで容認された時計から派生していた状態で時計を送ってください、」
OBJECT dsx1Fdl
オブジェクトdsx1Fdl
Nicklass, Ed. Standards Track [Page 63] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[63ページ]RFC
MIN-ACCESS read-only
DESCRIPTION
"Facilities Data Link usage on E1 ISDN
Primary Rate interfaces.
Note: There is an 'M-Channel' in E1,
using National Bit Sa4 (G.704,
Table 5A). It is used to implement
management features between ET
and NT. This is different from
FDL in T1, which is used to carry
control signals and performance
data. In E1, control and status
signals are carried using National
Bits Sa5, Sa6, and A (RAI Ind.).
This indicates that only the other(1) or
eventually the dsx1Fdl-none(8) bits should
be set in this object for E1 PRI."
「1EのISDN Primary Rateの上の施設Data Link用法は連結する」MIN-ACCESS書き込み禁止記述。 以下に注意してください。 National Bit Sa4(G.704、Table 5A)を使用して、1Eには'Mチャンネル'があります。 それは、管理がETとNTの間の特徴であると実装するのに使用されます。 これはT1でFDLと異なっています。(T1は、制御信号と性能データを運ぶのに使用されます)。 1Eでは、コントロールとステータス信号は、National Bits Sa5、Sa6、およびA(RAIインディアナ州)を使用することで運ばれます。 「これは、他の(1)だけか結局なにもの(8)ビットがそうするべきであるdsx1Fdlがこのオブジェクトで1EのPRIに用意ができているのを示します。」
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization is not
required."
::= { ds1Compliances 3 }
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。 ::= ds1Compliances3
ds1Ds2Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for using this MIB for DS2
interfaces."
MODULE
MANDATORY-GROUPS { ds1DS2Group }
「DS2にこのMIBを使用するための承諾声明は連結する」ds1Ds2Compliance MODULE-COMPLIANCE STATUSの現在の記述。 モジュールの義務的なグループds1DS2Group
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1DS2M12(10),
dsx1E2(11)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for DS2, E2
interfaces."
OBJECT dsx1LineType SYNTAX INTEGER、dsx1DS2M12(10)、dsx1E2(11)、MIN-ACCESS読書だけ記述は「DS2のためのタイプ、2Eのインタフェースを裏打ちします」。
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization is not
required."
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。
Nicklass, Ed. Standards Track [Page 64] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[64ページ]RFC
::= { ds1Compliances 4 }
::= ds1Compliances4
ds1NCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for T1 and E1
interfaces."
MODULE -- this module
MANDATORY-GROUPS { ds1NearEndConfigurationGroup,
ds1NearEndStatisticsGroup }
「T1と1Eの承諾声明は連結する」ds1NCompliance MODULE-COMPLIANCE STATUSの推奨しない記述。 MODULE--このモジュールMANDATORY-GROUPSds1NearEndConfigurationGroup、ds1NearEndStatisticsGroup
GROUP ds1FarEndGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 interface."
GROUP ds1FarEndGroup記述、「DS1インタフェースに付くすべてのシステムに、このグループの実装は任意です」。
GROUP ds1NearEndOptionalTrapGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 interface. If it is
implemented, then ds1NearEndOptionalConfigGroup
should also be implemented."
GROUP ds1NearEndOptionalTrapGroup記述、「DS1インタフェースに付くすべてのシステムに、このグループの実装は任意です」。 「また、それが実装されるなら、ds1NearEndOptionalConfigGroupは実装されるべきです。」
GROUP ds1NearEndOptionalConfigGroup
DESCRIPTION
"Implementation of this group is recommended for
all systems that attach to a DS1 interface and
implement ds1NearEndOptionalTrapGroup."
「このグループの実装はDS1インタフェースに付いて、ds1NearEndOptionalTrapGroupを実装するすべてのシステムのために推薦される」GROUP ds1NearEndOptionalConfigGroup記述。
GROUP ds1DS2Group
DESCRIPTION
"Implementation of this group is mandatory for all
systems that attach to a DS2 interface."
GROUP ds1DS2Group記述、「このグループの実装はDS2インタフェースに付くすべてのシステムに義務的です」。
GROUP ds1TransStatsGroup
DESCRIPTION
"This group is the set of statistics appropriate
for all systems that attach to a DS1 interface
running transparent or unFramed lineType."
「このグループは、DS1インタフェース実行に透明な状態で付くすべてのシステムに、適切な統計のセットかunFramed lineType GROUP ds1TransStatsGroup記述です」。
GROUP ds1ChanMappingGroup
DESCRIPTION
"This group is the set of objects for mapping a
DS3 Channel (dsx1Ds1ChannelNumber) to ifIndex.
Implementation of this group is mandatory for
systems that support the channelization of DS3s
into DS1s."
GROUP ds1ChanMappingGroup記述、「このグループはDS3 Channel(dsx1Ds1ChannelNumber)をifIndexに写像するためのオブジェクトのセットです」。 「このグループの実装はDS3sのチャネル化をDS1s.にサポートするシステムに義務的です」
Nicklass, Ed. Standards Track [Page 65] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[65ページ]RFC
OBJECT dsx1LineType
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line type is not
required."
OBJECT dsx1LineType MIN-ACCESS書き込み禁止記述、「系列タイプを設定する能力は必要ではありません」。
OBJECT dsx1LineCoding
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line coding is not
required."
OBJECT dsx1LineCoding MIN-ACCESS書き込み禁止記述、「ラインコード方式を設定する能力は必要ではありません」。
OBJECT dsx1SendCode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the send code is not
required."
OBJECT dsx1SendCode MIN-ACCESS書き込み禁止記述、「セットする能力、発信、コードは必要でない、」
OBJECT dsx1LoopbackConfig
MIN-ACCESS read-only
DESCRIPTION
"The ability to set loopbacks is not required."
OBJECT dsx1LoopbackConfig MIN-ACCESS書き込み禁止記述、「ループバックを設定する能力は必要ではありません」。
OBJECT dsx1SignalMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the signal mode is not
required."
OBJECT dsx1SignalMode MIN-ACCESS書き込み禁止記述、「信号モードを設定する能力は必要ではありません」。
OBJECT dsx1TransmitClockSource
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the transmit clock source is
not required."
OBJECT dsx1TransmitClockSource MIN-ACCESS書き込み禁止記述、「セットする能力、伝える、時計ソースは必要でない、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the FDL is not required."
OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述、「FDLを設定する能力は必要ではありません」。
OBJECT dsx1LineLength
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line length is not
required."
OBJECT dsx1LineLength MIN-ACCESS書き込み禁止記述、「行長を設定する能力は必要ではありません」。
OBJECT dsx1Channelization
MIN-ACCESS read-only
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止
Nicklass, Ed. Standards Track [Page 66] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[66ページ]RFC
DESCRIPTION
"The ability to set the channelization is not
required."
記述、「チャネル化を設定する能力は必要ではありません」。
OBJECT dsx1LineMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line mode is not
required."
OBJECT dsx1LineMode MIN-ACCESS書き込み禁止記述、「ライン・モードを設定する能力は必要ではありません」。
OBJECT dsx1LineBuildOut
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line build-out is not
required."
::= { ds1Compliances 5 }
OBJECT dsx1LineBuildOut MIN-ACCESS書き込み禁止記述、「外に系列建てるように設定する能力は必要ではありません」。 ::= ds1Compliances5
ds1MibT1PriNCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"Compliance statement for using this MIB for ISDN
Primary Rate interfaces on T1 lines."
MODULE
MANDATORY-GROUPS { ds1NearEndConfigurationGroup,
ds1NearEndStatisticsGroup }
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1ESF(2) -- Intl Spec would be G704(2)
-- or I.431(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for T1 ISDN Primary Rate
interfaces."
「ISDN Primary RateにこのMIBを使用するための承諾声明はT1系列で連結する」ds1MibT1PriNCompliance MODULE-COMPLIANCE STATUSの推奨しない記述。 MODULE MANDATORY-GROUPS、ds1NearEndConfigurationGroup、ds1NearEndStatisticsGroup、OBJECT dsx1LineType SYNTAX INTEGER、Intl SpecがG704(2)であるだろうというdsx1ESF(2)かI.431(4)、MIN-ACCESS読書だけ記述は「T1 ISDN Primary Rateインタフェースへのタイプを裏打ちします」。
OBJECT dsx1LineCoding
SYNTAX INTEGER {
dsx1B8ZS(2)
}
MIN-ACCESS read-only
DESCRIPTION
"Type of Zero Code Suppression for
T1 ISDN Primary Rate interfaces."
OBJECT dsx1LineCoding SYNTAX INTEGER dsx1B8ZS(2)、MIN-ACCESSの読書唯一の記述「T1 ISDN Primary RateインタフェースへのタイプのZero Code Suppression。」
OBJECT dsx1SignalMode
SYNTAX INTEGER {
none(1), -- if there is no signaling channel
messageOriented(4)
OBJECT dsx1SignalMode SYNTAX INTEGER、なにも、(1)、チャンネルmessageOrientedに合図してはいけません。(4)
Nicklass, Ed. Standards Track [Page 67] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[67ページ]RFC
}
MIN-ACCESS read-only
DESCRIPTION
"Possible signaling modes for
T1 ISDN Primary Rate interfaces."
} 「T1 ISDN Primary Rateのためにモードに合図するのが連結するのが可能な」MIN-ACCESS書き込み禁止記述。
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1)
}
MIN-ACCESS read-only
DESCRIPTION
"The transmit clock is derived from
received clock on ISDN Primary Rate
interfaces."
OBJECT dsx1TransmitClockSource SYNTAX INTEGER loopTiming(1)、MIN-ACCESS書き込み禁止記述、「ISDN Primary Rateインタフェースで容認された時計から派生していた状態で時計を送ってください、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"Facilities Data Link usage on T1 ISDN
Primary Rate interfaces.
Note: Eventually, dsx1Att-54016(4) is to be
used here since the line type is ESF."
「T1 ISDN Primary Rateの上の施設Data Link用法は連結する」OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述。 以下に注意してください。 「結局、dsx1Att-54016(4)は系列タイプがESFであるので、ここで使用されることになっています。」
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization
is not required."
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。
OBJECT dsx1LineMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line mode is not
required."
OBJECT dsx1LineMode MIN-ACCESS書き込み禁止記述、「ライン・モードを設定する能力は必要ではありません」。
OBJECT dsx1LineBuildOut
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line build-out
is not required."
::= { ds1Compliances 6 }
OBJECT dsx1LineBuildOut MIN-ACCESS書き込み禁止記述、「外に系列建てるように設定する能力は必要ではありません」。 ::= ds1Compliances6
ds1MibE1PriNCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"Compliance statement for using this MIB for ISDN
Primary Rate interfaces on E1 lines."
「ISDN Primary RateにこのMIBを使用するための承諾声明は1Eの系列で連結する」ds1MibE1PriNCompliance MODULE-COMPLIANCE STATUSの推奨しない記述。
Nicklass, Ed. Standards Track [Page 68] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[68ページ]RFC
MODULE
MANDATORY-GROUPS { ds1NearEndConfigurationGroup,
ds1NearEndStatisticsGroup }
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1E1CRC(5)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for E1 ISDN Primary Rate
interfaces."
MODULE MANDATORY-GROUPS、ds1NearEndConfigurationGroup、ds1NearEndStatisticsGroup、OBJECT dsx1LineType SYNTAX INTEGER dsx1E1CRC(5)、MIN-ACCESS読書だけ記述は「1EのISDN Primary Rateインタフェースへのタイプを裏打ちします」。
OBJECT dsx1LineCoding
SYNTAX INTEGER {
dsx1HDB3(3)
}
MIN-ACCESS read-only
DESCRIPTION
"Type of Zero Code Suppression for
E1 ISDN Primary Rate interfaces."
OBJECT dsx1LineCoding SYNTAX INTEGER dsx1HDB3(3)、MIN-ACCESSの読書唯一の記述「1EのISDN Primary RateインタフェースへのタイプのZero Code Suppression。」
OBJECT dsx1SignalMode
SYNTAX INTEGER {
messageOriented(4)
}
MIN-ACCESS read-only
OBJECT dsx1SignalMode SYNTAX INTEGER messageOriented(4)、MIN-ACCESS書き込み禁止
DESCRIPTION
"Signaling on E1 ISDN Primary Rate interfaces
is always message oriented."
記述、「1EのISDN Primary Rateインタフェースで合図して、いつもメッセージは適応しますか?」
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1)
}
MIN-ACCESS read-only
DESCRIPTION
"The transmit clock is derived from received
clock on ISDN Primary Rate interfaces."
OBJECT dsx1TransmitClockSource SYNTAX INTEGER loopTiming(1)、MIN-ACCESS書き込み禁止記述、「ISDN Primary Rateインタフェースで容認された時計から派生していた状態で時計を送ってください、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"Facilities Data Link usage on E1 ISDN
Primary Rate interfaces.
Note: There is an 'M-Channel' in E1,
using National Bit Sa4 (G704,
Table 5A). It is used to implement
「1EのISDN Primary Rateの上の施設Data Link用法は連結する」OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述。 以下に注意してください。 National Bit Sa4(G704、Table 5A)を使用して、1Eには'Mチャンネル'があります。 それは実装するのにおいて使用されています。
Nicklass, Ed. Standards Track [Page 69] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[69ページ]RFC
management features between ET
and NT. This is different from
FDL in T1, which is used to carry
control signals and performance
data. In E1, control and status
signals are carried using National
Bits Sa5, Sa6, and A (RAI Ind.).
This indicates that only the other(1) or
eventually the dsx1Fdl-none(8) bits should
be set in this object for E1 PRI."
ETとNTの間の管理機能。 これはT1でFDLと異なっています。(T1は、制御信号と性能データを運ぶのに使用されます)。 1Eでは、コントロールとステータス信号は、National Bits Sa5、Sa6、およびA(RAIインディアナ州)を使用することで運ばれます。 「これは、他の(1)だけか結局なにもの(8)ビットがそうするべきであるdsx1Fdlがこのオブジェクトで1EのPRIに用意ができているのを示します。」
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization is not
required."
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。
OBJECT dsx1LineMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line mode is not
required."
OBJECT dsx1LineMode MIN-ACCESS書き込み禁止記述、「ライン・モードを設定する能力は必要ではありません」。
OBJECT dsx1LineBuildOut
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line build-out
is not required."
::= { ds1Compliances 7 }
OBJECT dsx1LineBuildOut MIN-ACCESS書き込み禁止記述、「外に系列建てるように設定する能力は必要ではありません」。 ::= ds1Compliances7
ds1J1Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for T1, J1, and E1
interfaces."
MODULE -- this module
MANDATORY-GROUPS { ds1NearEndCfgGroup,
ds1NearEndStatGroup }
「T1、J1、および1Eの承諾声明は連結する」ds1J1Compliance MODULE-COMPLIANCE STATUSの現在の記述。 MODULE--このモジュールMANDATORY-GROUPSds1NearEndCfgGroup、ds1NearEndStatGroup
GROUP ds1FarEndNGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 interface."
GROUP ds1FarEndNGroup記述、「DS1インタフェースに付くすべてのシステムに、このグループの実装は任意です」。
GROUP ds1NearEndOptionalTrapGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 interface. If it is
GROUP ds1NearEndOptionalTrapGroup記述、「DS1インタフェースに付くすべてのシステムに、このグループの実装は任意です」。 それがそうなら
Nicklass, Ed. Standards Track [Page 70] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[70ページ]RFC
implemented, then ds1NearEndOptionalConfigGroup
should also be implemented."
「実装されて、そして、また、ds1NearEndOptionalConfigGroupは実装されるべきです。」
GROUP ds1NearEndOptionalConfigGroup
DESCRIPTION
"Implementation of this group is recommended for
all systems that attach to a DS1 interface and
implement ds1NearEndOptionalTrapGroup."
「このグループの実装はDS1インタフェースに付いて、ds1NearEndOptionalTrapGroupを実装するすべてのシステムのために推薦される」GROUP ds1NearEndOptionalConfigGroup記述。
GROUP ds1DS2Group
DESCRIPTION
"Implementation of this group is mandatory for all
systems that attach to a DS2 interface."
GROUP ds1DS2Group記述、「このグループの実装はDS2インタフェースに付くすべてのシステムに義務的です」。
GROUP ds1TransStatsGroup
DESCRIPTION
"This group is the set of statistics appropriate
for all systems that attach to a DS1 interface
running transparent or unFramed lineType."
「このグループは、DS1インタフェース実行に透明な状態で付くすべてのシステムに、適切な統計のセットかunFramed lineType GROUP ds1TransStatsGroup記述です」。
GROUP ds1ChanMappingGroup
DESCRIPTION
"This group is the set of objects for mapping a
DS3 Channel (dsx1Ds1ChannelNumber) to ifIndex.
Implementation of this group is mandatory for
systems that support the channelization of DS3s
into DS1s."
GROUP ds1ChanMappingGroup記述、「このグループはDS3 Channel(dsx1Ds1ChannelNumber)をifIndexに写像するためのオブジェクトのセットです」。 「このグループの実装はDS3sのチャネル化をDS1s.にサポートするシステムに義務的です」
OBJECT dsx1LineType
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line type is not
required."
OBJECT dsx1LineType MIN-ACCESS書き込み禁止記述、「系列タイプを設定する能力は必要ではありません」。
OBJECT dsx1LineCoding
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line coding is not
required."
OBJECT dsx1LineCoding MIN-ACCESS書き込み禁止記述、「ラインコード方式を設定する能力は必要ではありません」。
OBJECT dsx1SendCode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the send code is not
required."
OBJECT dsx1SendCode MIN-ACCESS書き込み禁止記述、「セットする能力、発信、コードは必要でない、」
OBJECT dsx1LoopbackConfig
MIN-ACCESS read-only
OBJECT dsx1LoopbackConfig MIN-ACCESS書き込み禁止
Nicklass, Ed. Standards Track [Page 71] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[71ページ]RFC
DESCRIPTION
"The ability to set loopbacks is not required."
記述、「ループバックを設定する能力は必要ではありません」。
OBJECT dsx1SignalMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the signal mode is not
required."
OBJECT dsx1SignalMode MIN-ACCESS書き込み禁止記述、「信号モードを設定する能力は必要ではありません」。
OBJECT dsx1TransmitClockSource
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the transmit clock source is
not required."
OBJECT dsx1TransmitClockSource MIN-ACCESS書き込み禁止記述、「セットする能力、伝える、時計ソースは必要でない、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the FDL is not required."
OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述、「FDLを設定する能力は必要ではありません」。
OBJECT dsx1LineLength
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line length is not
required."
OBJECT dsx1LineLength MIN-ACCESS書き込み禁止記述、「行長を設定する能力は必要ではありません」。
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization is not
required."
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。
OBJECT dsx1LineMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line mode is not
required."
OBJECT dsx1LineMode MIN-ACCESS書き込み禁止記述、「ライン・モードを設定する能力は必要ではありません」。
OBJECT dsx1LineBuildOut
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line build-out is not
required."
OBJECT dsx1LineBuildOut MIN-ACCESS書き込み禁止記述、「外に系列建てるように設定する能力は必要ではありません」。
OBJECT dsx1LineImpedance
MIN-ACCESS read-only
DESCRIPTION
"The ability to set line impedance is not
OBJECT dsx1LineImpedance MIN-ACCESS書き込み禁止記述、「線路インピーダンスを設定する能力はそうではありません」
Nicklass, Ed. Standards Track [Page 72] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[72ページ]RFC
required."
::= { ds1Compliances 8 }
「必要です」。 ::= ds1Compliances8
ds1NMibT1PriNCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for using this MIB for ISDN
Primary Rate interfaces on T1 lines."
MODULE
MANDATORY-GROUPS { ds1NearEndCfgGroup,
ds1NearEndStatGroup }
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1ESF(2) -- Intl Spec would be G704(2)
-- or I.431(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for T1 ISDN Primary Rate
interfaces."
「ISDN Primary RateにこのMIBを使用するための承諾声明はT1系列で連結する」ds1NMibT1PriNCompliance MODULE-COMPLIANCE STATUSの現在の記述。 MODULE MANDATORY-GROUPS、ds1NearEndCfgGroup、ds1NearEndStatGroup、OBJECT dsx1LineType SYNTAX INTEGER、Intl SpecがG704(2)であるだろうというdsx1ESF(2)かI.431(4)、MIN-ACCESS読書だけ記述は「T1 ISDN Primary Rateインタフェースへのタイプを裏打ちします」。
OBJECT dsx1LineCoding
SYNTAX INTEGER {
dsx1B8ZS(2)
}
MIN-ACCESS read-only
DESCRIPTION
"Type of Zero Code Suppression for
T1 ISDN Primary Rate interfaces."
OBJECT dsx1LineCoding SYNTAX INTEGER dsx1B8ZS(2)、MIN-ACCESSの読書唯一の記述「T1 ISDN Primary RateインタフェースへのタイプのZero Code Suppression。」
OBJECT dsx1SignalMode
SYNTAX INTEGER {
none(1), -- if there is no signaling channel
messageOriented(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Possible signaling modes for
T1 ISDN Primary Rate interfaces."
OBJECT dsx1SignalMode SYNTAX INTEGER、なにも、(1)、チャンネルmessageOriented(4)に合図してはいけない、「T1 ISDN Primary Rateのためにモードに合図するのが連結するのが可能な」MIN-ACCESS書き込み禁止記述。
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1)
}
MIN-ACCESS read-only
DESCRIPTION
"The transmit clock is derived from
received clock on ISDN Primary Rate
OBJECT dsx1TransmitClockSource SYNTAX INTEGER loopTiming(1)、MIN-ACCESS書き込み禁止記述、「ISDNの容認された時計から派生している時計Primary Rateを伝えてください、」
Nicklass, Ed. Standards Track [Page 73] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[73ページ]RFC
interfaces."
「インタフェース。」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"Facilities Data Link usage on T1 ISDN
Primary Rate interfaces.
Note: Eventually, dsx1Att-54016(4) is to be
used here since the line type is ESF."
「T1 ISDN Primary Rateの上の施設Data Link用法は連結する」OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述。 以下に注意してください。 「結局、dsx1Att-54016(4)は系列タイプがESFであるので、ここで使用されることになっています。」
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the channelization
is not required."
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述、「チャネル化を設定する能力は必要ではありません」。
OBJECT dsx1LineMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line mode is not
required."
OBJECT dsx1LineMode MIN-ACCESS書き込み禁止記述、「ライン・モードを設定する能力は必要ではありません」。
OBJECT dsx1LineBuildOut
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line build-out
is not required."
::= { ds1Compliances 9 }
OBJECT dsx1LineBuildOut MIN-ACCESS書き込み禁止記述、「外に系列建てるように設定する能力は必要ではありません」。 ::= ds1Compliances9
ds1NMibE1PriNCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for using this MIB for ISDN
Primary Rate interfaces on E1 lines."
MODULE
MANDATORY-GROUPS { ds1NearEndCfgGroup,
ds1NearEndStatGroup }
「ISDN Primary RateにこのMIBを使用するための承諾声明は1Eの系列で連結する」ds1NMibE1PriNCompliance MODULE-COMPLIANCE STATUSの現在の記述。 モジュールの義務的なグループds1NearEndCfgGroup、ds1NearEndStatGroup
OBJECT dsx1LineType
SYNTAX INTEGER {
dsx1E1CRC(5)
}
MIN-ACCESS read-only
DESCRIPTION
"Line type for E1 ISDN Primary Rate
interfaces."
OBJECT dsx1LineType SYNTAX INTEGER dsx1E1CRC(5)、MIN-ACCESS読書だけ記述は「1EのISDN Primary Rateインタフェースへのタイプを裏打ちします」。
OBJECT dsx1LineCoding
オブジェクトdsx1LineCoding
Nicklass, Ed. Standards Track [Page 74] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[74ページ]RFC
SYNTAX INTEGER {
dsx1HDB3(3)
}
MIN-ACCESS read-only
DESCRIPTION
"Type of Zero Code Suppression for
E1 ISDN Primary Rate interfaces."
SYNTAX INTEGER dsx1HDB3(3)、MIN-ACCESSの読書唯一の記述「1EのISDN Primary RateインタフェースへのタイプのZero Code Suppression。」
OBJECT dsx1SignalMode
SYNTAX INTEGER {
messageOriented(4)
}
MIN-ACCESS read-only
DESCRIPTION
"Signaling on E1 ISDN Primary Rate interfaces
is always message oriented."
OBJECT dsx1SignalMode SYNTAX INTEGER messageOriented(4)、MIN-ACCESS書き込み禁止記述、「1EのISDN Primary Rateインタフェースで合図して、いつもメッセージは適応しますか?」
OBJECT dsx1TransmitClockSource
SYNTAX INTEGER {
loopTiming(1)
}
MIN-ACCESS read-only
DESCRIPTION
"The transmit clock is derived from received
clock on ISDN Primary Rate interfaces."
OBJECT dsx1TransmitClockSource SYNTAX INTEGER loopTiming(1)、MIN-ACCESS書き込み禁止記述、「ISDN Primary Rateインタフェースで容認された時計から派生していた状態で時計を送ってください、」
OBJECT dsx1Fdl
MIN-ACCESS read-only
DESCRIPTION
"Facilities Data Link usage on E1 ISDN
Primary Rate interfaces.
Note: There is an 'M-Channel' in E1,
using National Bit Sa4 (G704,
Table 5A). It is used to implement
management features between ET
and NT. This is different from
FDL in T1, which is used to carry
control signals and performance
data. In E1, control and status
signals are carried using National
Bits Sa5, Sa6, and A (RAI Ind.).
This indicates that only the other(1) or
eventually the dsx1Fdl-none(8) bits should
be set in this object for E1 PRI."
「1EのISDN Primary Rateの上の施設Data Link用法は連結する」OBJECT dsx1Fdl MIN-ACCESS書き込み禁止記述。 以下に注意してください。 National Bit Sa4(G704、Table 5A)を使用して、1Eには'Mチャンネル'があります。 それは、管理がETとNTの間の特徴であると実装するのに使用されます。 これはT1でFDLと異なっています。(T1は、制御信号と性能データを運ぶのに使用されます)。 1Eでは、コントロールとステータス信号は、National Bits Sa5、Sa6、およびA(RAIインディアナ州)を使用することで運ばれます。 「これは、他の(1)だけか結局なにもの(8)ビットがそうするべきであるdsx1Fdlがこのオブジェクトで1EのPRIに用意ができているのを示します。」
OBJECT dsx1Channelization
MIN-ACCESS read-only
DESCRIPTION
OBJECT dsx1Channelization MIN-ACCESS書き込み禁止記述
Nicklass, Ed. Standards Track [Page 75] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[75ページ]RFC
"The ability to set the channelization is not
required."
「チャネル化を設定する能力は必要ではありません。」
OBJECT dsx1LineMode
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line mode is not
required."
OBJECT dsx1LineMode MIN-ACCESS書き込み禁止記述、「ライン・モードを設定する能力は必要ではありません」。
OBJECT dsx1LineBuildOut
MIN-ACCESS read-only
DESCRIPTION
"The ability to set the line build-out
is not required."
OBJECT dsx1LineBuildOut MIN-ACCESS書き込み禁止記述、「外に系列建てるように設定する能力は必要ではありません」。
OBJECT dsx1LineImpedance
MIN-ACCESS read-only
DESCRIPTION
"The ability to set line impedance is not
required."
::= { ds1Compliances 10 }
OBJECT dsx1LineImpedance MIN-ACCESS書き込み禁止記述、「線路インピーダンスを設定する能力は必要ではありません」。 ::= ds1Compliances10
-- units of conformance
-- ユニットの順応
ds1NearEndConfigGroup OBJECT-GROUP
OBJECTS { dsx1LineIndex,
dsx1TimeElapsed,
dsx1ValidIntervals,
dsx1LineType,
dsx1LineCoding,
dsx1SendCode,
dsx1CircuitIdentifier,
dsx1LoopbackConfig,
dsx1LineStatus,
dsx1SignalMode,
dsx1TransmitClockSource,
dsx1Fdl,
dsx1InvalidIntervals,
dsx1LineLength,
dsx1LoopbackStatus,
dsx1Ds1ChannelNumber,
dsx1Channelization }
STATUS deprecated
DESCRIPTION
"A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 1 }
ds1NearEndConfigGroup OBJECT-GROUP OBJECTS、dsx1LineIndex、dsx1TimeElapsed、dsx1ValidIntervals、dsx1LineType、dsx1LineCoding、dsx1SendCode、dsx1CircuitIdentifier、dsx1LoopbackConfig、dsx1LineStatus、dsx1SignalMode、dsx1TransmitClockSource、dsx1Fdl、dsx1InvalidIntervals、dsx1LineLength、dsx1LoopbackStatus、dsx1Ds1ChannelNumber、dsx1Channelization、「オブジェクトがすべてのDS1に適切な設定情報を提供する収集は連結する」STATUSの推奨しない記述。 ::= ds1Groups1
Nicklass, Ed. Standards Track [Page 76] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[76ページ]RFC
ds1NearEndStatisticsGroup OBJECT-GROUP
OBJECTS { dsx1CurrentIndex,
dsx1CurrentESs,
dsx1CurrentSESs,
dsx1CurrentSEFSs,
dsx1CurrentUASs,
dsx1CurrentCSSs,
dsx1CurrentPCVs,
dsx1CurrentLESs,
dsx1CurrentBESs,
dsx1CurrentDMs,
dsx1CurrentLCVs,
dsx1IntervalIndex,
dsx1IntervalNumber,
dsx1IntervalESs,
dsx1IntervalSESs,
dsx1IntervalSEFSs,
dsx1IntervalUASs,
dsx1IntervalCSSs,
dsx1IntervalPCVs,
dsx1IntervalLESs,
dsx1IntervalBESs,
dsx1IntervalDMs,
dsx1IntervalLCVs,
dsx1IntervalValidData,
dsx1TotalIndex,
dsx1TotalESs,
dsx1TotalSESs,
dsx1TotalSEFSs,
dsx1TotalUASs,
dsx1TotalCSSs,
dsx1TotalPCVs,
dsx1TotalLESs,
dsx1TotalBESs,
dsx1TotalDMs,
dsx1TotalLCVs }
STATUS deprecated
DESCRIPTION
"A collection of objects providing statistics
information applicable to all DS1 interfaces."
::= { ds1Groups 2 }
ds1NearEndStatisticsGroupオブジェクト群対象; { dsx1CurrentIndex、dsx1CurrentESs、dsx1CurrentSESs、dsx1CurrentSEFSs、dsx1CurrentUASs、dsx1CurrentCSSs、dsx1CurrentPCVs、dsx1CurrentLESs、dsx1CurrentBESs、dsx1CurrentDMs、dsx1CurrentLCVs、dsx1IntervalIndex、dsx1IntervalNumber、dsx1IntervalESs、dsx1IntervalSESs、dsx1IntervalSEFSs、dsx1IntervalUASs; dsx1IntervalCSSs、dsx1IntervalPCVs、dsx1IntervalLESs、dsx1IntervalBESs、dsx1IntervalDMs、dsx1IntervalLCVs、dsx1IntervalValidData、dsx1TotalIndex、dsx1TotalESs、dsx1TotalSESs、dsx1TotalSEFSs、dsx1TotalUASs、dsx1TotalCSSs、dsx1TotalPCVs、dsx1TotalLESs、dsx1TotalBESs、dsx1TotalDMs、dsx1TotalLCVs; } 「オブジェクトがすべてのDS1に適切な統計情報を提供する収集は連結する」STATUSの推奨しない記述。 ::= ds1Groups2
ds1FarEndGroup OBJECT-GROUP
OBJECTS { dsx1FarEndCurrentIndex,
dsx1FarEndTimeElapsed,
dsx1FarEndValidIntervals,
dsx1FarEndCurrentESs,
dsx1FarEndCurrentSESs,
ds1FarEndGroupオブジェクト群対象、dsx1FarEndCurrentIndex、dsx1FarEndTimeElapsed、dsx1FarEndValidIntervals、dsx1FarEndCurrentESs、dsx1FarEndCurrentSESs
Nicklass, Ed. Standards Track [Page 77] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[77ページ]RFC
dsx1FarEndCurrentSEFSs,
dsx1FarEndCurrentUASs,
dsx1FarEndCurrentCSSs,
dsx1FarEndCurrentLESs,
dsx1FarEndCurrentPCVs,
dsx1FarEndCurrentBESs,
dsx1FarEndCurrentDMs,
dsx1FarEndInvalidIntervals,
dsx1FarEndIntervalIndex,
dsx1FarEndIntervalNumber,
dsx1FarEndIntervalESs,
dsx1FarEndIntervalSESs,
dsx1FarEndIntervalSEFSs,
dsx1FarEndIntervalUASs,
dsx1FarEndIntervalCSSs,
dsx1FarEndIntervalLESs,
dsx1FarEndIntervalPCVs,
dsx1FarEndIntervalBESs,
dsx1FarEndIntervalDMs,
dsx1FarEndIntervalValidData,
dsx1FarEndTotalIndex,
dsx1FarEndTotalESs,
dsx1FarEndTotalSESs,
dsx1FarEndTotalSEFSs,
dsx1FarEndTotalUASs,
dsx1FarEndTotalCSSs,
dsx1FarEndTotalLESs,
dsx1FarEndTotalPCVs,
dsx1FarEndTotalBESs,
dsx1FarEndTotalDMs }
STATUS deprecated
DESCRIPTION
"A collection of objects providing remote
configuration and statistics information."
::= { ds1Groups 3 }
dsx1FarEndCurrentSEFSs、dsx1FarEndCurrentUASs、dsx1FarEndCurrentCSSs、dsx1FarEndCurrentLESs、dsx1FarEndCurrentPCVs、dsx1FarEndCurrentBESs、dsx1FarEndCurrentDMs、dsx1FarEndInvalidIntervals、dsx1FarEndIntervalIndex、dsx1FarEndIntervalNumber、dsx1FarEndIntervalESs、dsx1FarEndIntervalSESs、dsx1FarEndIntervalSEFSs、dsx1FarEndIntervalUASs、dsx1FarEndIntervalCSSs; dsx1FarEndIntervalLESs、dsx1FarEndIntervalPCVs、dsx1FarEndIntervalBESs、dsx1FarEndIntervalDMs、dsx1FarEndIntervalValidData、dsx1FarEndTotalIndex、dsx1FarEndTotalESs、dsx1FarEndTotalSESs、dsx1FarEndTotalSEFSs、dsx1FarEndTotalUASs、dsx1FarEndTotalCSSs、dsx1FarEndTotalLESs、dsx1FarEndTotalPCVs、dsx1FarEndTotalBESs、dsx1FarEndTotalDMs STATUSの推奨しない記述、「リモート構成と統計情報を提供するオブジェクトの収集。」 ::= ds1Groups3
ds1DeprecatedGroup OBJECT-GROUP
OBJECTS { dsx1IfIndex,
dsx1FracIndex,
dsx1FracNumber,
dsx1FracIfIndex }
STATUS deprecated
DESCRIPTION
"A collection of obsolete objects that may be
implemented for backwards compatibility."
::= { ds1Groups 4 }
ds1DeprecatedGroup OBJECT-GROUP OBJECTS、dsx1IfIndex、dsx1FracIndex、dsx1FracNumber、dsx1FracIfIndex、STATUSの推奨しない記述、「遅れている互換性のために実装されるかもしれない時代遅れのオブジェクトの収集。」 ::= ds1Groups4
ds1NearEndOptionalConfigGroup OBJECT-GROUP
ds1NearEndOptionalConfigGroupオブジェクトグループ
Nicklass, Ed. Standards Track [Page 78] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[78ページ]RFC
OBJECTS { dsx1LineStatusLastChange,
dsx1LineStatusChangeTrapEnable }
オブジェクトdsx1LineStatusLastChange、dsx1LineStatusChangeTrapEnable
STATUS current
DESCRIPTION
"A collection of objects that may be implemented
on DS1 and DS2 interfaces."
::= { ds1Groups 5 }
「DS1で実装されるかもしれないオブジェクトとDS2の収集は連結する」STATUSの現在の記述。 ::= ds1Groups5
ds1DS2Group OBJECT-GROUP
OBJECTS { dsx1LineIndex,
dsx1LineType,
dsx1LineCoding,
dsx1SendCode,
dsx1LineStatus,
dsx1SignalMode,
dsx1TransmitClockSource,
dsx1Channelization }
STATUS current
DESCRIPTION
"A collection of objects providing information
about DS2 (6,312 kbps) and E2 (8,448 kbps)
systems."
::= { ds1Groups 6 }
ds1DS2Group OBJECT-GROUP OBJECTS、dsx1LineIndex、dsx1LineType、dsx1LineCoding、dsx1SendCode、dsx1LineStatus、dsx1SignalMode、dsx1TransmitClockSource、dsx1Channelization、STATUSの現在の記述、「DS2(6,312キロビット毎秒)と情報のおよそ2E(8,448キロビット毎秒)のシステムを提供するオブジェクトの収集」、:、:= ds1Groups6
ds1TransStatsGroup OBJECT-GROUP
OBJECTS { dsx1CurrentESs,
dsx1CurrentSESs,
dsx1CurrentUASs,
dsx1IntervalESs,
dsx1IntervalSESs,
dsx1IntervalUASs,
dsx1TotalESs,
dsx1TotalSESs,
dsx1TotalUASs }
STATUS current
DESCRIPTION
"A collection of objects that are the
statistics that can be collected from a DS1
interface that is running transparent or unframed
lineType. Statistics not in this list should
return noSuchInstance."
::= { ds1Groups 7 }
ds1TransStatsGroup OBJECT-GROUP OBJECTS、dsx1CurrentESs、dsx1CurrentSESs、dsx1CurrentUASs、dsx1IntervalESs、dsx1IntervalSESs、dsx1IntervalUASs、dsx1TotalESs、dsx1TotalSESs、dsx1TotalUASs、STATUSの現在の記述、「透明な状態で稼働する予定であるDS1インタフェースから集めることができる統計であるオブジェクトかunframed lineTypeの収集。」 「統計はこのリストでnoSuchInstanceを返すべきではありません。」 ::= ds1Groups7
ds1NearEndOptionalTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { dsx1LineStatusChange }
STATUS current
DESCRIPTION
ds1NearEndOptionalTrapGroup NOTIFICATION-GROUP NOTIFICATIONS dsx1LineStatusChange、STATUSの現在の記述
Nicklass, Ed. Standards Track [Page 79] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[79ページ]RFC
"A collection of notifications that may be
implemented on DS1 and DS2 interfaces."
::= { ds1Groups 8 }
「DS1とDS2で実装されるかもしれない通知の収集は連結します。」 ::= ds1Groups8
ds1ChanMappingGroup OBJECT-GROUP
OBJECTS { dsx1ChanMappedIfIndex }
STATUS current
DESCRIPTION
"A collection of objects that give a mapping of
DS3 Channel (dsx1Ds1ChannelNumber) to ifIndex."
::= { ds1Groups 9 }
ds1ChanMappingGroup OBJECT-GROUP OBJECTS dsx1ChanMappedIfIndex、STATUSの現在の記述、「DS3 Channel(dsx1Ds1ChannelNumber)に関するマッピングをifIndexに与えるオブジェクトの収集。」 ::= ds1Groups9
ds1NearEndConfigurationGroup OBJECT-GROUP
OBJECTS { dsx1LineIndex,
dsx1TimeElapsed,
dsx1ValidIntervals,
dsx1LineType,
dsx1LineCoding,
dsx1SendCode,
dsx1CircuitIdentifier,
dsx1LoopbackConfig,
dsx1LineStatus,
dsx1SignalMode,
dsx1TransmitClockSource,
dsx1Fdl,
dsx1InvalidIntervals,
dsx1LineLength,
dsx1LoopbackStatus,
dsx1Ds1ChannelNumber,
dsx1Channelization,
dsx1LineMode,
dsx1LineBuildOut }
STATUS deprecated
DESCRIPTION
"A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 10 }
ds1NearEndConfigurationGroupオブジェクト群対象、dsx1LineIndex、dsx1TimeElapsed、dsx1ValidIntervals、dsx1LineType、dsx1LineCoding、dsx1SendCode、dsx1CircuitIdentifier、dsx1LoopbackConfig、dsx1LineStatus、dsx1SignalMode、dsx1TransmitClockSource、dsx1Fdl、dsx1InvalidIntervals、dsx1LineLength、dsx1LoopbackStatus、dsx1Ds1ChannelNumber、dsx1Channelization、dsx1LineMode、dsx1LineBuildOut; 「オブジェクトがすべてのDS1に適切な設定情報を提供する収集は連結する」STATUSの推奨しない記述。 ::= ds1Groups10
ds1NearEndCfgGroup OBJECT-GROUP
OBJECTS { dsx1LineIndex,
dsx1TimeElapsed,
dsx1ValidIntervals,
dsx1LineType,
dsx1LineCoding,
dsx1SendCode,
dsx1CircuitIdentifier,
dsx1LoopbackConfig,
dsx1LineStatus,
ds1NearEndCfgGroupオブジェクト群対象、dsx1LineIndex、dsx1TimeElapsed、dsx1ValidIntervals、dsx1LineType、dsx1LineCoding、dsx1SendCode、dsx1CircuitIdentifier、dsx1LoopbackConfig、dsx1LineStatus
Nicklass, Ed. Standards Track [Page 80] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[80ページ]RFC
dsx1SignalMode,
dsx1TransmitClockSource,
dsx1Fdl,
dsx1InvalidIntervals,
dsx1LineLength,
dsx1LoopbackStatus,
dsx1Ds1ChannelNumber,
dsx1Channelization,
dsx1LineMode,
dsx1LineBuildOut,
dsx1LineImpedance }
STATUS current
DESCRIPTION
"A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 11 }
dsx1SignalMode、dsx1TransmitClockSource、dsx1Fdl、dsx1InvalidIntervals、dsx1LineLength、dsx1LoopbackStatus、dsx1Ds1ChannelNumber、dsx1Channelization、dsx1LineMode、dsx1LineBuildOut、dsx1LineImpedance 「オブジェクトがすべてのDS1に適切な設定情報を提供する収集は連結する」STATUSの現在の記述。 ::= ds1Groups11
ds1NearEndStatGroup OBJECT-GROUP
OBJECTS { dsx1CurrentIndex,
dsx1CurrentESs,
dsx1CurrentSESs,
dsx1CurrentSEFSs,
dsx1CurrentUASs,
dsx1CurrentCSSs,
dsx1CurrentPCVs,
dsx1CurrentLESs,
dsx1CurrentBESs,
dsx1CurrentLCVs,
dsx1IntervalIndex,
dsx1IntervalNumber,
dsx1IntervalESs,
dsx1IntervalSESs,
dsx1IntervalSEFSs,
dsx1IntervalUASs,
dsx1IntervalCSSs,
dsx1IntervalPCVs,
dsx1IntervalLESs,
dsx1IntervalBESs,
dsx1IntervalLCVs,
dsx1IntervalValidData,
dsx1TotalIndex,
dsx1TotalESs,
dsx1TotalSESs,
dsx1TotalSEFSs,
dsx1TotalUASs,
dsx1TotalCSSs,
dsx1TotalPCVs,
dsx1TotalLESs,
ds1NearEndStatGroupオブジェクト群対象、dsx1CurrentIndex、dsx1CurrentESs、dsx1CurrentSESs、dsx1CurrentSEFSs、dsx1CurrentUASs、dsx1CurrentCSSs、dsx1CurrentPCVs、dsx1CurrentLESs、dsx1CurrentBESs、dsx1CurrentLCVs、dsx1IntervalIndex、dsx1IntervalNumber、dsx1IntervalESs、dsx1IntervalSESs; dsx1IntervalSEFSs、dsx1IntervalUASs、dsx1IntervalCSSs、dsx1IntervalPCVs、dsx1IntervalLESs、dsx1IntervalBESs、dsx1IntervalLCVs、dsx1IntervalValidData、dsx1TotalIndex、dsx1TotalESs、dsx1TotalSESs、dsx1TotalSEFSs、dsx1TotalUASs、dsx1TotalCSSs、dsx1TotalPCVs、dsx1TotalLESs
Nicklass, Ed. Standards Track [Page 81] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[81ページ]RFC
dsx1TotalBESs,
dsx1TotalLCVs }
STATUS current
DESCRIPTION
"A collection of objects providing statistics
information applicable to all DS1 interfaces."
::= { ds1Groups 12 }
dsx1TotalBESs、dsx1TotalLCVs 「オブジェクトがすべてのDS1に適切な統計情報を提供する収集は連結する」STATUSの現在の記述。 ::= ds1Groups12
ds1FarEndNGroup OBJECT-GROUP
OBJECTS { dsx1FarEndCurrentIndex,
dsx1FarEndTimeElapsed,
dsx1FarEndValidIntervals,
dsx1FarEndCurrentESs,
dsx1FarEndCurrentSESs,
dsx1FarEndCurrentSEFSs,
dsx1FarEndCurrentUASs,
dsx1FarEndCurrentCSSs,
dsx1FarEndCurrentLESs,
dsx1FarEndCurrentPCVs,
dsx1FarEndCurrentBESs,
dsx1FarEndInvalidIntervals,
dsx1FarEndIntervalIndex,
dsx1FarEndIntervalNumber,
dsx1FarEndIntervalESs,
dsx1FarEndIntervalSESs,
dsx1FarEndIntervalSEFSs,
dsx1FarEndIntervalUASs,
dsx1FarEndIntervalCSSs,
dsx1FarEndIntervalLESs,
dsx1FarEndIntervalPCVs,
dsx1FarEndIntervalBESs,
dsx1FarEndIntervalValidData,
dsx1FarEndTotalIndex,
dsx1FarEndTotalESs,
dsx1FarEndTotalSESs,
dsx1FarEndTotalSEFSs,
dsx1FarEndTotalUASs,
dsx1FarEndTotalCSSs,
dsx1FarEndTotalLESs,
dsx1FarEndTotalPCVs,
dsx1FarEndTotalBESs}
STATUS current
DESCRIPTION
"A collection of objects providing remote
configuration and statistics information."
::= { ds1Groups 13 }
END
ds1FarEndNGroupオブジェクト群対象; { dsx1FarEndCurrentIndex、dsx1FarEndTimeElapsed、dsx1FarEndValidIntervals、dsx1FarEndCurrentESs、dsx1FarEndCurrentSESs、dsx1FarEndCurrentSEFSs、dsx1FarEndCurrentUASs、dsx1FarEndCurrentCSSs、dsx1FarEndCurrentLESs、dsx1FarEndCurrentPCVs、dsx1FarEndCurrentBESs、dsx1FarEndInvalidIntervals、dsx1FarEndIntervalIndex、dsx1FarEndIntervalNumber、dsx1FarEndIntervalESs、dsx1FarEndIntervalSESs; dsx1FarEndIntervalSEFSs、dsx1FarEndIntervalUASs、dsx1FarEndIntervalCSSs、dsx1FarEndIntervalLESs、dsx1FarEndIntervalPCVs、dsx1FarEndIntervalBESs、dsx1FarEndIntervalValidData、dsx1FarEndTotalIndex、dsx1FarEndTotalESs、dsx1FarEndTotalSESs、dsx1FarEndTotalSEFSs、dsx1FarEndTotalUASs、dsx1FarEndTotalCSSs、dsx1FarEndTotalLESs、dsx1FarEndTotalPCVs、dsx1FarEndTotalBESs; } STATUSの現在の記述、「リモート構成と統計情報を提供するオブジェクトの収集。」 ::= ds1Groups13は終わります。
Nicklass, Ed. Standards Track [Page 82] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[82ページ]RFC
5. Security Considerations
5. セキュリティ問題
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The specific objects and their sensitivities/vulnerabilities are as follows.
読書して書くことのマックス-ACCESS節でこのMIBモジュールで定義された多くの管理オブジェクトがあります。 そのようなオブジェクトはいくつかのネットワーク環境で敏感であるか、または被害を受け易いと考えられるかもしれません。 適切な保護のない非安全な環境におけるSET操作のサポートはネットワーク操作のときにマイナスの影響がある場合があります。 特定のオブジェクトとそれらの敏感さ/脆弱性は以下の通りです。
Setting the following objects to incorrect values may result in traffic interruptions:
不正確な値に以下のオブジェクトを設定すると、トラフィック中断はもたらされるかもしれません:
dsx1LineType
dsx1LineCoding
dsx1SendCode
dsx1LoopbackConfig
dsx1SignalMode
dsx1TransmitClockSource
dsx1Fdl
dsx1LineLength
dsx1Channelization
dsx1LineMode
dsx1LineBuildOut
dsx1LineImpedance
dsx1LineType dsx1LineCoding dsx1SendCode dsx1LoopbackConfig dsx1SignalMode dsx1TransmitClockSource dsx1Fdl dsx1LineLength dsx1Channelization dsx1LineMode dsx1LineBuildOut dsx1LineImpedance
In the case of dsx1LineType, for example, both ends of a DS1/E1 must have the same value in order for traffic to flow. In the case of dsx1SendCode and dsx1LoopbackConfig, for another example, traffic may stop transmitting when particular loopbacks are applied.
dsx1LineTypeの場合では、例えば、1DS1/Eの両端は、トラフィックが流れるように同じ値を持たなければなりません。 dsx1SendCodeに関するケースと別の例のためのdsx1LoopbackConfigでは、トラフィックは、特定のループバックが適用されているとき、伝わるのを止めるかもしれません。
Setting the following object to an incorrect value will not harm the traffic, but it may cause a circuit to be misidentified and thereby create difficulties for service personnel when attempting to troubleshoot a problem:
不正確な値に以下のオブジェクトを設定する場合、トラフィックは害を及ぼさないでしょうが、問題を障害調査するのを試みるとき、回路が誤認されて、その結果、サービスマンのための困難を作成することを引き起こすかもしれません:
dsx1CircuitIdentifier
dsx1CircuitIdentifier
Setting the following object can cause an increase in the number of traps received by the network management station:
以下のオブジェクトを設定すると、ネットワークマネージメントステーションによって受け取られた罠の数の増加は引き起こされる場合があります:
dsx1LineStatusChangeTrapEnable
dsx1LineStatusChangeTrapEnable
The readable objects in this MIB module (i.e., the objects with a MAX-ACCESS other than not-accessible) may be considered sensitive in some environments since, collectively, they provide extensive information about the performance of interfaces in DS1/J1/E1/DS2/E2 equipment or networks and can reveal some aspects of their
このMIBモジュール(すなわち、アクセスしやすくないのを除いたマックス-ACCESSがあるオブジェクト)による読み込み可能なオブジェクトが彼らが以来にまとめて、2 1/DS2/E DS1/J1/Eの設備かネットワークにおける、インタフェースの性能の大規模な情報を提供して、いくつかの局面を明らかにすることができるいくつかの環境で敏感であると考えられるかもしれない、それら
Nicklass, Ed. Standards Track [Page 83] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[83ページ]RFC
configuration. In such environments, it is important to control even GET and NOTIFY access to these objects and possibly to encrypt the values of these objects when sending them over the network via SNMP.
構成。 そのような環境で、SNMPを通してネットワークの上にそれらを送るとき、GETとこれらのオブジェクトへのNOTIFYアクセスさえ制御して、ことによるとこれらのオブジェクトの値を暗号化するのは重要です。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3の前のSNMPバージョンは十分な安全性を含んでいませんでした。 ネットワーク自体が安全であっても(例えば、IPSecを使用するのによる)、その時でさえ、アクセスとGET/SET(読むか、変える、作成する、または削除する)へのオブジェクトが安全なネットワークにこのMIBモジュールでだれに許容されているかに関してコントロールが全くありません。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
implementersがSNMPv3フレームワークで提供するようにセキュリティ機能を考えるのは([RFC3410]を見てください、セクション8)、RECOMMENDEDです、SNMPv3の暗号のメカニズム(認証とプライバシーのための)の全面的な支援を含んでいて。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
さらに、SNMPv3の前のSNMPバージョンの展開はNOT RECOMMENDEDです。 代わりに、それはSNMPv3を配布して、暗号のセキュリティを可能にするRECOMMENDEDです。 そして、このMIBモジュールのインスタンスへのアクセスを与えるSNMP実体が本当にGETに正当な権利を持っている校長(ユーザ)をそれらだけへのオブジェクトへのアクセスに与えるか、または(変えるか、作成する、または削除します)それらをSETに与えるために適切に構成されるのを保証するのは、顧客/オペレータ責任です。
6. Acknowledgments
6. 承認
This document was produced by the AToM MIB Working Group.
このドキュメントはAToM MIB作業部会によって製作されました。
7. References
7. 参照
7.1. Normative References
7.1. 引用規格
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] ブラドナー、S.、「Indicate Requirement LevelsへのRFCsにおける使用のためのキーワード」、BCP14、RFC2119、1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578] McCloghrie、K.、パーキンス、D.、およびJ.Schoenwaelder、「経営情報バージョン2(SMIv2)の構造」、STD58、RFC2578(1999年4月)。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579,
April 1999.
[RFC2579] McCloghrieとK.とパーキンス、D.とJ.Schoenwaelder、「SMIv2"、STD58、RFC2579、1999年4月の原文のコンベンション。」
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2580] McCloghrieとK.とパーキンス、D.とJ.Schoenwaelder、「SMIv2"、STD58、RFC2580、1999年4月のための順応声明。」
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Group MIB", RFC 2863, June 2000.
[RFC2863] McCloghrieとK.とF.Kastenholz、「インタフェースはMIBを分類する」RFC2863、2000年6月。
Nicklass, Ed. Standards Track [Page 84] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[84ページ]RFC
[AT&T-TR-54016] AT&T Technical Reference, Requirements for
Interfacing Digital Terminal Equipment to Services
Employing the Extended Superframe Format, Publication
54016, May 1988.
[AT&T-TR-54016] AT&Tの技術的な参照、拡張Superframe形式を使うサービスにデジタル端末装置を連結するための要件(公表54016)は1988がそうするかもしれません。
[ANSI-T1.403] American National Standard for Telecommunications --
Carrier-to-Customer Installation - DS1 Metallic
Interface, T1.403, February 1989.
テレコミュニケーションのための[ANSI-T1.403]米国標準規格--キャリヤーから顧客へのインストール--DS1の金属インタフェース、T1.403、2月1989日。
[CCITT-G.703] ITU-T G.703, Physical/Electrical Characteristics of
Hierarchical Digital Interfaces, November 2001.
[CCITT-G.703] ITU-T G.703、階層的なデジタルインタフェース、2001年11月の物理的であるか電気の特性。
[ITU-T-G.704] ITU-T G.704: Synchronous frame structures used at
1544, 6312, 2048, 8488 and 44 736 kbit/s Hierarchical
Levels, October 1998.
[ITU-T-G.704] ITU-T G.704: 同期枠組構造は1544、6312、2048、8488、および44歳のときに736kbit/s Hierarchical Levels、1998年10月を使用しました。
[ANSI-T1.231] American National Standard for Telecommunications --
Digital Hierarchy DS1-- Layer 1 In-Service Digital
Transmission Performance Monitoring, T1.231.02,
October 2003.
テレコミュニケーションのための[ANSI-T1.231]米国標準規格(デジタル階層構造DS1)は2003年10月に1の稼働中のデジタルトランスミッションパフォーマンスモニター、T1.231.02を層にします。
[ITU-T-O.162] ITU-T O.162, Equipment To Perform In Service
Monitoring On 2048 kbit/s Signals, October 1992.
[ITU-T-O.162] ITU-T O.162、Equipment To Perform In Service Monitoring On2048kbit/s Signals、1992年10月。
[CCITT-G.821] ITU-T G.821, Error Performance Of An International
Digital Connection Forming Part Of An Integrated
Services Digital Network, December 2002.
[CCITT-G.821] ITU-T G.821、サービス統合ディジタル網、2002年12月の一部を形成する国際デジタル接続に関する誤り実績。
[AT&T-TR-62411] AT&T Technical Reference, Technical Reference 62411,
ACCUNET T1.5 Service Description And Interface
Specification, December 1990.
[AT&T-TR-62411] AT&Tの技術的な参照と技術的な参照62411とACCUNET T1.5サービス記述とインターフェース仕様、1990年12月。
[CCITT-G.706] ITU-T G.706, Frame Alignment and Cyclic Redundancy
Check (CRC) Procedures Relating to Basic Frame
Structures Defined in Recommendation G.704, April
1991.
[CCITT-G.706] ITU-T G.706、基本枠構造に関連するフレーム整列と周期冗長検査(CRC)手順が推薦でG.704(1991年4月)を定義しました。
[CCITT-G.732] ITU-T G.732, Characteristics Of Primary PCM Multiplex
Equipment Operating at 2048 kbit/s, November 1988.
[CCITT-G.732] ITU-T G.732、2048kbit/s、1988年11月のCharacteristics Of Primary PCM Multiplex Equipment Operating。
[ITU-T-G.775] ITU-T G.775: Loss of signal (LOS) and alarm
indication signal (AIS) defect detection and
clearance criteria, October 1998.
[ITU-T-G.775] ITU-T G.775: 信号の損失(LOS)と警報指示は1998年10月に(AIS)欠陥検出とクリアランス評価基準を示します。
[ITU-T-G.826] ITU-T G.826: Error performance parameters and
objectives for international, constant bit rate
digital paths at or above the primary rate, December
2002.
[ITU-T-G.826] ITU-T G.826: 予備選挙における、または、予備選挙を超えた国際的で、一定のビット伝送速度デジタル経路への誤り性能パラメタと目的は2002年12月に評価します。
Nicklass, Ed. Standards Track [Page 85] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
エドNicklass、2007年のMIB行進の2 1/DS2/E4805DS1/J1/Eの標準化過程[85ページ]RFC
[ANSI-T1.107] American National Standard for Telecommunications --
Digital Hierarchy - Format Specifications, T1.107,
January 2002.
テレコミュニケーションのための[ANSI-T1.107]米国標準規格--デジタル階層構造--書式仕様、T1.107、1月2002日。
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules
Using Performance History Based on 15 Minute
Intervals", RFC 3593, September 2003.
[RFC3593]Tesink、K.、「MIBモジュールのための15分の間隔に基づくパフォーマンス歴史を使用する原文のコンベンション」、RFC3593、2003年9月。
[ITU-T-M.1400] ITU-T M.1400: Designation For Interconnections Among
Network Operators, October 2001.
[ITU-T-M.1400] ITU-T M.1400: ネットワーク・オペレータの中のインタコネクトのための2001年10月の名称。
[JT-G704] JT-G.704: Synchronous frame structures used at
Primary and Secondary Hierarchical Levels, 2002.
[JT-G704]JT-G.704: PrimaryとSecondary Hierarchical Levels、2002で使用される同期枠組構造。
[JT-G706] JT-G.706: Frame Alignment and Cyclic Redundancy Check
(CRC) Procedures.
[JT-G706]JT-G.706: 整列と周期冗長検査(CRC)手順を縁どってください。
[JT-I431] JT-I.431: ISDN Primary Rate User-Network
Interface,Layer 1 Specifications, 2002.
[JT-I431]JT-I.431: ISDNのプライマリレートユーザネットワーク・インターフェース、層1の仕様、2002。
7.2. Informative References
7.2. 有益な参照
[RFC1213] McCloghrie, K. and M. Rose, "Management Information
Base for Network Management of TCP/IP-based
internets:MIB-II", STD 17, RFC 1213, March 1991.
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets:MIB-II", STD 17, RFC 1213, March 1991.
[RFC3895] Nicklass, O., "Definitions of Managed Objects for the
DS1, E1, DS2, and E2 Interface Types", RFC 3895,
September 2004.
[RFC3895] Nicklass, O., "Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types", RFC 3895, September 2004.
[RFC2495] Fowler, D., "Definitions of Managed Objects for the
DS1, E1, DS2 and E2 Interface Types", RFC 2495,
January 1999.
[RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types", RFC 2495, January 1999.
[RFC1406] Baker, F. and J. Watt, "Definitions of Managed
Objects for the DS1 and E1 Interface Types", RFC
1406, January 1993.
[RFC1406] Baker, F. and J. Watt, "Definitions of Managed Objects for the DS1 and E1 Interface Types", RFC 1406, January 1993.
[AT&T-UM-305] AT&T Information Systems, AT&T ESF DS1 Channel
Service Unit User's Manual, 999-100-305, February
1988.
[AT&T-UM-305] AT&T Information Systems, AT&T ESF DS1 Channel Service Unit User's Manual, 999-100-305, February 1988.
[RFC3896] Nicklass, O., "Definitions of Managed Objects for the
DS3/E3 Interface Type", RFC 3896, September 2004.
[RFC3896] Nicklass, O., "Definitions of Managed Objects for the DS3/E3 Interface Type", RFC 3896, September 2004.
Nicklass, Ed. Standards Track [Page 86] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 86] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
[RFC3592] Tesink, K., "Definitions of Managed Objects for the
Synchronous Optical Network/Synchronous Digital
Hierarchy (SONET/SDH) Interface Type", RFC 3592,
September 2003.
[RFC3592] Tesink, K., "Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type", RFC 3592, September 2003.
[RFC2494] Fowler, D., "Definitions of Managed Objects for the
DS0 and DS0 Bundle Interface Type", RFC 2494, January
1999.
[RFC2494] Fowler, D., "Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type", RFC 2494, January 1999.
[ANSI-T1.102] American National Standard for Telecommunications --
Digital Hierarchy - Electrical Interfaces, T1.102,
December 1993.
[ANSI-T1.102] American National Standard for Telecommunications -- Digital Hierarchy - Electrical Interfaces, T1.102, December 1993.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
Nicklass, Ed. Standards Track [Page 87] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 87] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Appendix A - Use of dsx1IfIndex and dsx1LineIndex
Appendix A - Use of dsx1IfIndex and dsx1LineIndex
This appendix exists to document the previous use of dsx1IfIndex and dsx1LineIndex and to clarify the relationship of dsx1LineIndex as defined in RFC 1406 with the dsx1LineIndex as defined in this document.
This appendix exists to document the previous use of dsx1IfIndex and dsx1LineIndex and to clarify the relationship of dsx1LineIndex as defined in RFC 1406 with the dsx1LineIndex as defined in this document.
The following shows the old and new definitions and the relationship:
The following shows the old and new definitions and the relationship:
[New Definition]: "This object should be made equal to ifIndex. The next paragraph describes its previous usage. Making the object equal to ifIndex allows proper use of ifStackTable and ds0/ds0bundle mibs.
[New Definition]: "This object should be made equal to ifIndex. The next paragraph describes its previous usage. Making the object equal to ifIndex allows proper use of ifStackTable and ds0/ds0bundle mibs.
[Old Definition]: "This object is the identifier of a DS1 Interface on a managed device. If there is an ifEntry that is directly associated with this and only this DS1 interface, it should have the same value as ifIndex. Otherwise, number the dsx1LineIndices with an unique identifier following the rules of choosing a number that is greater than ifNumber and numbering the inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g., network side) with odd numbers."
[Old Definition]: "This object is the identifier of a DS1 Interface on a managed device. If there is an ifEntry that is directly associated with this and only this DS1 interface, it should have the same value as ifIndex. Otherwise, number the dsx1LineIndices with an unique identifier following the rules of choosing a number that is greater than ifNumber and numbering the inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g., network side) with odd numbers."
When the "Old Definition" was created, it was described this way to allow a manager to treat the value as if it were an ifIndex; i.e., the value would be either: 1) an ifIndex value or 2) a value that was guaranteed to be different from all valid ifIndex values.
When the "Old Definition" was created, it was described this way to allow a manager to treat the value as if it were an ifIndex; i.e., the value would be either: 1) an ifIndex value or 2) a value that was guaranteed to be different from all valid ifIndex values.
The new definition is a subset of that definition; i.e., the value is always an ifIndex value.
The new definition is a subset of that definition; i.e., the value is always an ifIndex value.
The following is Section 3.1 from RFC 1406:
The following is Section 3.1 from RFC 1406:
Different physical configurations for the support of SNMP with DS1
equipment exist. To accommodate these scenarios, two different
indices for DS1 interfaces are introduced in this MIB. These
indices are dsx1IfIndex and dsx1LineIndex.
Different physical configurations for the support of SNMP with DS1 equipment exist. To accommodate these scenarios, two different indices for DS1 interfaces are introduced in this MIB. These indices are dsx1IfIndex and dsx1LineIndex.
External interface scenario: the SNMP Agent represents all managed
DS1 lines as external interfaces (for example, an Agent residing
on the device supporting DS1 interfaces directly):
External interface scenario: the SNMP Agent represents all managed DS1 lines as external interfaces (for example, an Agent residing on the device supporting DS1 interfaces directly):
For this scenario, all interfaces are assigned an integer value
equal to ifIndex, and the following applies:
For this scenario, all interfaces are assigned an integer value equal to ifIndex, and the following applies:
ifIndex=dsx1IfIndex=dsx1LineIndex for all interfaces.
ifIndex=dsx1IfIndex=dsx1LineIndex for all interfaces.
Nicklass, Ed. Standards Track [Page 88] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 88] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
The dsx1IfIndex column of the DS1 Configuration table relates each
DS1 interface to its corresponding interface (ifIndex) in the
Internet-standard MIB (MIB-II STD 17, RFC 1213) [RFC1213].
The dsx1IfIndex column of the DS1 Configuration table relates each DS1 interface to its corresponding interface (ifIndex) in the Internet-standard MIB (MIB-II STD 17, RFC 1213) [RFC1213].
External & Internal interface scenario: the SNMP Agents resides on
a host external from the device supporting DS1 interfaces (e.g., a
router). The Agent represents both the host and the DS1 device.
The index dsx1LineIndex is used to not only represent the DS1
interfaces external from the host/DS1-device combination, but also
the DS1 interfaces connecting the host and the DS1 device. The
index dsx1IfIndex is always equal to ifIndex.
External & Internal interface scenario: the SNMP Agents resides on a host external from the device supporting DS1 interfaces (e.g., a router). The Agent represents both the host and the DS1 device. The index dsx1LineIndex is used to not only represent the DS1 interfaces external from the host/DS1-device combination, but also the DS1 interfaces connecting the host and the DS1 device. The index dsx1IfIndex is always equal to ifIndex.
Example:
Example:
A shelf full of CSUs connected to a router. An SNMP Agent
residing on the router proxies for itself and the CSU. The router
has also an Ethernet interface:
A shelf full of CSUs connected to a router. An SNMP Agent residing on the router proxies for itself and the CSU. The router has also an Ethernet interface:
+-----+
| | |
| | | +---------------------+
|E | | 1.544 MBPS | Line#A | DS1 Link
|t | R |---------------+ - - - - - - - - - +------>
|h | | | |
|e | O | 1.544 MBPS | Line#B | DS1 Link
|r | |---------------+ - - - - - - - - - - +------>
|n | U | | CSU Shelf |
|e | | 1.544 MBPS | Line#C | DS1 Link
|t | T |---------------+ - - - -- -- - - - - +------>
| | | | |
|-----| E | 1.544 MBPS | Line#D | DS1 Link
| | |---------------+ - - - - -- - - - - +------>
| | R | |_____________________|
| | |
| +-----+
+-----+ | | | | | | +---------------------+ |E | | 1.544 MBPS | Line#A | DS1 Link |t | R |---------------+ - - - - - - - - - +------> |h | | | | |e | O | 1.544 MBPS | Line#B | DS1 Link |r | |---------------+ - - - - - - - - - - +------> |n | U | | CSU Shelf | |e | | 1.544 MBPS | Line#C | DS1 Link |t | T |---------------+ - - - -- -- - - - - +------> | | | | | |-----| E | 1.544 MBPS | Line#D | DS1 Link | | |---------------+ - - - - -- - - - - +------> | | R | |_____________________| | | | | +-----+
The assignment of the index values could for example be:
The assignment of the index values could for example be:
ifIndex (= dsx1IfIndex) dsx1LineIndex
1 NA NA (Ethernet)
2 Line#A Router Side 6
2 Line#A Network Side 7
3 Line#B Router Side 8
3 Line#B Network Side 9
4 Line#C Router Side 10
4 Line#C Network Side 11
5 Line#D Router Side 12
5 Line#D Network Side 13
ifIndex (= dsx1IfIndex) dsx1LineIndex 1 NA NA (Ethernet) 2 Line#A Router Side 6 2 Line#A Network Side 7 3 Line#B Router Side 8 3 Line#B Network Side 9 4 Line#C Router Side 10 4 Line#C Network Side 11 5 Line#D Router Side 12 5 Line#D Network Side 13
Nicklass, Ed. Standards Track [Page 89] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 89] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
For this example, ifNumber is equal to 5. Note the following
description of dsx1LineIndex: the dsx1LineIndex identifies a DS1
Interface on a managed device. If there is an ifEntry that is
directly associated with this and only this DS1 interface, it
should have the same value as ifIndex. Otherwise, number the
dsx1LineIndices with an unique identifier following the rules of
choosing a number greater than ifNumber and numbering inside
interfaces (e.g., equipment side) with even numbers and outside
interfaces (e.g., network side) with odd numbers.
For this example, ifNumber is equal to 5. Note the following description of dsx1LineIndex: the dsx1LineIndex identifies a DS1 Interface on a managed device. If there is an ifEntry that is directly associated with this and only this DS1 interface, it should have the same value as ifIndex. Otherwise, number the dsx1LineIndices with an unique identifier following the rules of choosing a number greater than ifNumber and numbering inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g., network side) with odd numbers.
If the CSU shelf is managed by itself by a local SNMP Agent, the
situation would be:
If the CSU shelf is managed by itself by a local SNMP Agent, the situation would be:
ifIndex (= dsx1IfIndex) dsx1LineIndex
1 Line#A Network Side 1
2 Line#A RouterSide 2
3 Line#B Network Side 3
4 Line#B RouterSide 4
5 Line#C Network Side 5
6 Line#C Router Side 6
7 Line#D Network Side 7
8 Line#D Router Side 8
ifIndex (= dsx1IfIndex) dsx1LineIndex 1 Line#A Network Side 1 2 Line#A RouterSide 2 3 Line#B Network Side 3 4 Line#B RouterSide 4 5 Line#C Network Side 5 6 Line#C Router Side 6 7 Line#D Network Side 7 8 Line#D Router Side 8
Appendix B - The Delay Approach to Unavailable Seconds
Appendix B - The Delay Approach to Unavailable Seconds
This procedure is illustrated below for a DS1 ESF interface. Similar rules would apply for other DS1, DS2, and E1 interface variants. The procedure guarantees that the statistical counters are correctly updated at all times, although they lag real time by 10 seconds. At the end of each 15-minute interval, the current interval counts are transferred to the most recent interval entry and each interval is shifted up by one position, with the oldest being discarded if necessary in order to make room. The current interval counts then start over from zero. Note, however, that the signal state calculation does not start afresh at each interval boundary; rather, signal state information is retained across interval boundaries.
This procedure is illustrated below for a DS1 ESF interface. Similar rules would apply for other DS1, DS2, and E1 interface variants. The procedure guarantees that the statistical counters are correctly updated at all times, although they lag real time by 10 seconds. At the end of each 15-minute interval, the current interval counts are transferred to the most recent interval entry and each interval is shifted up by one position, with the oldest being discarded if necessary in order to make room. The current interval counts then start over from zero. Note, however, that the signal state calculation does not start afresh at each interval boundary; rather, signal state information is retained across interval boundaries.
Nicklass, Ed. Standards Track [Page 90] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 90] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
+---------------------------------------------------------------------+
| READ COUNTERS & STATUS INFO FROM HARDWARE |
| |
| BPV EXZ LOS FE CRC CS AIS SEF OOF LOF RAI G1-G6 SE FE LV SL |
+---------------------------------------------------------------------+
| | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | |
V V V V V V V V V V V V V V V V
+---------------------------------------------------------------------+
| ACCUM ONE-SEC STATS, CHK ERR THRESHOLDS, & UPDT SIGNAL STATE |
| |
| |<---------- NEAR END ----------->| |<-------- FAR END ------>| |
| |
| LCV LES PCV ES CSS BES SES SEFS A/U PCV ES CSS BES SES SEFS A/U |
+---------------------------------------------------------------------+
| | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | |
V V V V V V V V | V V V V V V |
+------------------------------+ | +----------------------+ |
| ONE-SEC DELAY | | | ONE-SEC DELAY | |
| (1 OF 10) | | | (1 OF 10) | |
+------------------------------+ | +----------------------+ |
| | | | | | | | | | | | | | | |
/ / / / / / / / / / / / / / / /
| | | | | | | | | | | | | | | |
V V V V V V V V | V V V V V V |
+------------------------------+ | +----------------------+ |
| ONE-SEC DELAY | | | ONE-SEC DELAY | |
| (10 OF 10) | | | (10 OF 10) | |
+------------------------------+ | +----------------------+ |
| | | | | | | | | | | | | | | |
V V V V V V V V V V V V V V V V
+---------------------------------------------------------------------+
| UPDATE STATISTICS COUNTERS |
| |
|<-------------- NEAR END ----------->| |<--------- FAR END --------->|
| |
|LCV LES PCV ES CSS BES SES SEFS UAS DM PCV ES CSS BES SES SEFS UAS DM|
+---------------------------------------------------------------------+
+---------------------------------------------------------------------+ | READ COUNTERS & STATUS INFO FROM HARDWARE | | | | BPV EXZ LOS FE CRC CS AIS SEF OOF LOF RAI G1-G6 SE FE LV SL | +---------------------------------------------------------------------+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | V V V V V V V V V V V V V V V V +---------------------------------------------------------------------+ | ACCUM ONE-SEC STATS, CHK ERR THRESHOLDS, & UPDT SIGNAL STATE | | | | |<---------- NEAR END ----------->| |<-------- FAR END ------>| | | | | LCV LES PCV ES CSS BES SES SEFS A/U PCV ES CSS BES SES SEFS A/U | +---------------------------------------------------------------------+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | V V V V V V V V | V V V V V V | +------------------------------+ | +----------------------+ | | ONE-SEC DELAY | | | ONE-SEC DELAY | | | (1 OF 10) | | | (1 OF 10) | | +------------------------------+ | +----------------------+ | | | | | | | | | | | | | | | | | / / / / / / / / / / / / / / / / | | | | | | | | | | | | | | | | V V V V V V V V | V V V V V V | +------------------------------+ | +----------------------+ | | ONE-SEC DELAY | | | ONE-SEC DELAY | | | (10 OF 10) | | | (10 OF 10) | | +------------------------------+ | +----------------------+ | | | | | | | | | | | | | | | | | V V V V V V V V V V V V V V V V +---------------------------------------------------------------------+ | UPDATE STATISTICS COUNTERS | | | |<-------------- NEAR END ----------->| |<--------- FAR END --------->| | | |LCV LES PCV ES CSS BES SES SEFS UAS DM PCV ES CSS BES SES SEFS UAS DM| +---------------------------------------------------------------------+
Note that if such a procedure is adopted, there is no current interval data for the first 10 seconds after a system comes up. noSuchInstance must be returned if a management station attempts to access the current interval counters during this time.
Note that if such a procedure is adopted, there is no current interval data for the first 10 seconds after a system comes up. noSuchInstance must be returned if a management station attempts to access the current interval counters during this time.
It is an implementation-specific matter whether an agent assumes that the initial state of the interface is available or unavailable.
It is an implementation-specific matter whether an agent assumes that the initial state of the interface is available or unavailable.
Nicklass, Ed. Standards Track [Page 91] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 91] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Appendix C - Changes from Pervious Versions
Appendix C - Changes from Pervious Versions
C.1. Changes from RFC 3895
C.1. Changes from RFC 3895
The changes from RFC 3895 [RFC3895] are the following:
The changes from RFC 3895 [RFC3895] are the following:
(1) Values were added to dsx1LineType to support J1 types.
(2) The object dsx1LineImpedance was added.
(3) All DM-related objects were deprecated following their
removal from ITU performance standards.
(4) Relevant text and reference section were updated.
(5) Changes in Compliance Statements to include new values.
(1) Values were added to dsx1LineType to support J1 types. (2) The object dsx1LineImpedance was added. (3) All DM-related objects were deprecated following their removal from ITU performance standards. (4) Relevant text and reference section were updated. (5) Changes in Compliance Statements to include new values.
C.2. Changes from RFC 2495
C.2. Changes from RFC 2495
The changes from RFC 2495 [RFC2495] are the following:
The changes from RFC 2495 [RFC2495] are the following:
(1) The dsx1FracIfIndex SYNTAX matches the description range.
(2) A value was added to dsx1TransmitClockSource.
(3) Values were added to dsx1LineType.
(4) Two objects were added, dsx1LineMode and dsx1LineBuildOut, to
better express transceiver mode and LineBuildOut for T1.
(5) Reference was added to Circuit Identifier object.
(6) Align the DESCRIPTION clauses of few statistic objects with
the near-end definition, with the far-end definition, and with
[RFC3593].
(7) Changes in Compliance Statements to include new objects.
(8) A typographical error in dsx2E2 was fixed; new name is dsx1E2.
(1) The dsx1FracIfIndex SYNTAX matches the description range. (2) A value was added to dsx1TransmitClockSource. (3) Values were added to dsx1LineType. (4) Two objects were added, dsx1LineMode and dsx1LineBuildOut, to better express transceiver mode and LineBuildOut for T1. (5) Reference was added to Circuit Identifier object. (6) Align the DESCRIPTION clauses of few statistic objects with the near-end definition, with the far-end definition, and with [RFC3593]. (7) Changes in Compliance Statements to include new objects. (8) A typographical error in dsx2E2 was fixed; new name is dsx1E2.
C.3. Changes from RFC 1406
C.3. Changes from RFC 1406
The changes from RFC 1406 [RFC1406] are the following:
The changes from RFC 1406 [RFC1406] are the following:
(1) The Fractional table has been deprecated.
(2) This document uses SMIv2.
(3) Usage is given for ifTable and ifXTable.
(4) Example usage of ifStackTable is included.
(5) dsx1IfIndex has been deprecated.
(6) Support for DS2 and E2 has been added.
(7) Additional lineTypes for DS2, E2, and unframed E1 were added.
(8) The definition of valid intervals has been clarified for the
case where the agent proxied for other devices. In
particular, the treatment of missing intervals has been
clarified.
(9) An inward loopback has been added.
(10) Additional lineStatus bits have been added for Near End in
Unavailable Signal State, Carrier Equipment Out of Service,
DS2 Payload AIS, and DS2 Performance Threshold.
(1) The Fractional table has been deprecated. (2) This document uses SMIv2. (3) Usage is given for ifTable and ifXTable. (4) Example usage of ifStackTable is included. (5) dsx1IfIndex has been deprecated. (6) Support for DS2 and E2 has been added. (7) Additional lineTypes for DS2, E2, and unframed E1 were added. (8) The definition of valid intervals has been clarified for the case where the agent proxied for other devices. In particular, the treatment of missing intervals has been clarified. (9) An inward loopback has been added. (10) Additional lineStatus bits have been added for Near End in Unavailable Signal State, Carrier Equipment Out of Service, DS2 Payload AIS, and DS2 Performance Threshold.
Nicklass, Ed. Standards Track [Page 92] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 92] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
(11) A read-write line Length object has been added.
(12) Signal mode of other has been added.
(13) Added a lineStatus last change, trap and enabler.
(14) The e1(19) ifType has been obsoleted, so this MIB does not
list it as a supported ifType.
(15) Textual Conventions for statistics objects have been used.
(16) A new object, dsx1LoopbackStatus, has been introduced to
reflect the loopbacks established on a DS1 interface and the
source to the requests. dsx1LoopbackConfig continues to be
the desired loopback state while dsx1LoopbackStatus reflects
the actual state.
(17) A dual loopback has been added to allow the setting of an
inward loopback and a line loopback at the same time.
(18) An object indicating which channel to use within a parent
object (i.e., DS3) has been added.
(19) An object has been added to indicate whether or not this
DS1/E1 is channelized.
(20) Line coding type of B6ZS has been added for DS2.
(11) A read-write line Length object has been added. (12) Signal mode of other has been added. (13) Added a lineStatus last change, trap and enabler. (14) The e1(19) ifType has been obsoleted, so this MIB does not list it as a supported ifType. (15) Textual Conventions for statistics objects have been used. (16) A new object, dsx1LoopbackStatus, has been introduced to reflect the loopbacks established on a DS1 interface and the source to the requests. dsx1LoopbackConfig continues to be the desired loopback state while dsx1LoopbackStatus reflects the actual state. (17) A dual loopback has been added to allow the setting of an inward loopback and a line loopback at the same time. (18) An object indicating which channel to use within a parent object (i.e., DS3) has been added. (19) An object has been added to indicate whether or not this DS1/E1 is channelized. (20) Line coding type of B6ZS has been added for DS2.
C.4. Companion Documents
C.4. Companion Documents
This document is a companion to the documents that define managed objects for the DS0 [RFC2494], DS3/E3 [RFC3896], and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) [RFC3592] Interface Types.
This document is a companion to the documents that define managed objects for the DS0 [RFC2494], DS3/E3 [RFC3896], and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) [RFC3592] Interface Types.
Author's Address
Author's Address
Orly Nicklass, Editor RAD Data Communications, Ltd. Ziv Tower, 24 Roul Walenberg Tel Aviv, Israel, 69719
Orly Nicklass, Editor RAD Data Communications, Ltd. Ziv Tower, 24 Roul Walenberg Tel Aviv, Israel, 69719
Phone: 9723-765-9969 EMail: orly_n@rad.com
Phone: 9723-765-9969 EMail: orly_n@rad.com
Nicklass, Ed. Standards Track [Page 93] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Nicklass, Ed. Standards Track [Page 93] RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Full Copyright Statement
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
Intellectual Property
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
Acknowledgement
Acknowledgement
Funding for the RFC Editor function is currently provided by the Internet Society.
Funding for the RFC Editor function is currently provided by the Internet Society.
Nicklass, Ed. Standards Track [Page 94]
Nicklass, Ed. Standards Track [Page 94]
一覧
スポンサーリンク
