Previous | Table of Contents | Next |
DS1 and E1 objects are designated by {transmission 18}, with OID {1.3.6.2.1.10.18}, as shown in Figure 3-11. This MIB module consists of three groups: the DS1 Near End group, the DS1 Far End group, and the Fractional Table. The DS1 Near End group consists of four tables that contain configuration information and statistics about the DS1 interface at the near end of the communications link. This group contains four tables: the DS1 Configuration Table, which specifies the line coding, circuit identifier, line status, and other configuration details; the DS1 Current Table, which contains statistics collected over the current 15-minute interval; the DS1 Interval Table, which contains statistics collected over the previous 24 hours, broken into 96 complete 15-minute intervals; and the DS1 Far End Total Table, which contains the cumulative sum of various statistics for the 24 hours preceding the current interval.
Figure 3-11. DS1/E1 managed objects
The Fractional Table contains information regarding channels derived from subdividing DS1, such as a 64 Kbps channel used for voice traffic, or a 384 Kbps channel used for data traffic.
RFC 1406 [3-8] discusses details of the DS1/E1 MIB, as well as DS1 error events, performance defects, performance parameters, and failure states.
DS3 and E3 objects are designated by {transmission 30}, with OID {1.3.6.1.2.1.10.30}, as shown in Figure 3-12. This MIB module is similar in structure to the DS1 module discussed in the section above. It places DS3 objects in three groups: the DS3/E3 Near End Group, the DS3 Far End Group, or the DS3 Fractional Group. The tables and objects within those groups are similar to those for DS1/E1.
Figure 3-12. DS3/E3 Managed objects
RFC 1407 [3-9] discusses details of the DS3/E3 MIBas well as explanation of the DS3 error events, performance parameters, and perfomance defects.
The SONET and SDH objects are designated by {transmission 39}, with OID {1.3.6.1.2.10.39}, as shown in Figure 3-13. This MIB module contains eight groups.
Figure 3-13. SONET managed objects
The SONET/SDH Medium Group contains configuration information for optical and electrical SONET/SDH interfaces. The SONET/SDH Section group contains two tables that pertain to the SONET/SDH Section Layer: the SONET Section Current Table, with current statistics collected over a 15-minute interval; and the SONET/SDH Section Interval Table, with statistics collected over the previous 24 hours. The SONET/SDH Line group contains interval and current tables that pertain to the SONET/SDH Line layer. The SONET/SDH Far End Line group is implemented for systems that provide for FEBE information at the SONET/SDH Line layer; it contains both current and interval tables. The SONET/SDH Path and SONET/SDH Far End Path groups contain current interval information regarding the SONET/SDH Path layer. Finally, the SONET/SDH Virtual Tributary (VT) and SONET/SDH Far End VT groups contain current and interval information regarding the SONET/SDH VT Layer.
Details of the SONET/SDH are discussed in RFC 1595 [3-10], which is considered a companion document to the DS1/E1 and DS3/E3 MIBs. The SONET/SDH MIB also includes a listing of applicable terms and error conditions.
Frame relay DTE objects are designated by {transmission 32}, with OID {1.3.6.1.2.1.10.32}, as shown in Figure 3-14. This module contains three principle groups: the Data Link Connection Management Interface (DLCMI) group, the Circuits group, and the Errors group.
Figure 3-14. Frame relay DTE managed objects
The DLCMI group contains variables that configure the DLCMI, such as the Address field length, the interval between T1.617 Annex D STATUS ENQUIRY messages, the maximum number of virtual circuits on this interface, and so on. The Circuit group contains one table with information regarding specific DLCIs and their corresponding virtual circuits. The Error group contains one table that describes errors that have occurred on that frame relay interface. A fourth group, Frame-Relay-Globals, contains trap information. Details of the Frame Relay DTE MIB are discussed in RFC 1315 [3-11].
Frame relay network service objects are designated by {transmission 44}, with OID {1.3.6.1.2.1.10.44} (as shown in Figure 3-15). This MIB is intended for CNM of a frame relay network service and lets customers obtain details of the performance, faults, and configuration about their frame relay network service. The networks SNMP proxy agent obtains those details. A PVC between that agent and the customer constitutes the logical transmission path.
Figure 3-15. Frame relay network service managed objects
This MIB module consists of seven groups. The Frame Relay Logical Port group is an addendum to the ifTable found in MIB-II (RFC 1213). The Frame Relay Management VC Signaling group contains objects that relate to the T1.617 Annex D signaling channel. The PVC End-Point group identifies traffic parameters and provides statistics for a PVC segment end-point. The Frame Relay PVC Connection group models PVC information flows and connections. The PVC Connection Table contains connection information. The PVC Accounting on a Frame Relay Logical Port basis group contains additional accounting information. Two additional groups define traps and conformance information. Details of the Frame Relay Service MIB are discussed in RFC 1604 [3-12]. This MIB also includes a listing of applicable frame relay terms and parameters.
SIP objects are designated by {transmission 31} with OID {1.3.6.1.2.1.10.31}, as shown in Figure 3-16. This MIB module consists of six groups. The SIP Level 3 group contains SIP L3 parameters and state variables. The SIP Level 2 group contains SIP L2 parameters and state variables. The SIP PLCP group contains tables with both DS1 and DS3 PLCP parameters and state variables. The SMDS Applications group is used with IP over SMDS (from RFC 1209). The SMDS Carrier Selection group is a place holder for carrier-selection objects. The SIP Error Log group is a table that contains SIP L3 PDU errors. RFC 1694 [3-13] provides details of the SIP Interface MIB.
Figure 3-16. SIP managed objects
Previous | Table of Contents | Next |