Juniper-HDLC-MIB
The HDLC MIB for the Juniper Networks enterprise. This MIB provides a means for configuring HDLC interfaces on top of various types of interfaces, such as packet over SONET (POS) and high speed serial interfaces (HSSI). Management objects are provided to query for an available interface index, and to create/delete interfaces of this type. Creating/deleting this interface type using this MIB has the side effect of creating/deleting corresponding entries in the IF-MIB.ifTable, the IF-MIB.ifXTable, and the Juniper-UNI-IF-MIB.juniIfTable.
Main OID:
juniHdlcMIB.1.3.6.1.4.1.4874.2.2.9
27
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
juniHdlcMIBThe HDLC MIB for the Juniper Networks enterprise. This MIB provides a means for configuring HDLC interfaces on top of various types of interfaces, such as packet over SONET (POS) and high speed serial interfaces (HSSI). Management objects are provided to query for an available interface index, and to create/delete interfaces of this type. Creating/deleting this interface type using this MIB has the side effect of creating/deleting corresponding entries in the IF-MIB.ifTable, the IF-MIB.ifXTable, and the Juniper-UNI-IF-MIB.juniIfTable. MODULE-IDENTITY .1.3.6.1.4.1.4874.2.2.9 |
juniHdlcObjects OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.9.1 |
juniHdlcNextIfIndexCoordinate ifIndex value allocation for entries in juniHdlcIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.ro JuniNextIfIndex (Juniper-TC) .1.3.6.1.4.1.4874.2.2.9.1.1 |
juniHdlcIfTableThis table contains entries for HDLC interfaces present in the system. SEQUENCE OF JuniHdlcIfEntry .1.3.6.1.4.1.4874.2.2.9.1.2 |
juniHdlcIfEntryEach entry describes the characteristics of an HDLC interface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable. JuniHdlcIfEntry .1.3.6.1.4.1.4874.2.2.9.1.2.1 |
juniHdlcIfIndexThe ifIndex of the HDLC interface. When creating entries in this table, suitable values for this object are determined by reading juniHdlcNextIfIndex. InterfaceIndex (IF-MIB) .1.3.6.1.4.1.4874.2.2.9.1.2.1.1 |
juniHdlcIfRowStatusControls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniHdlcIfRowStatus juniHdlcIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for juniHdlcIfIndex must have been determined previously, by reading juniHdlcNextIfIndex. The interface identified by juniHdlcIfLowerIfIndex must exist. A corresponding entry in ifTable/ifXTable/juniIfTable is created/ destroyed as a result of creating/destroying an entry in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.9.1.2.1.2 |
juniHdlcIfLowerIfIndexThe ifIndex of an interface over which this HDLC interface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.4874.2.2.9.1.2.1.3 |
juniHdlcIfMtuThe Maximum Transmission Unit (MTU) this interface is permitted to transmit. At creation, if a value for this object is not specified, a default will be chosen that is suitable for the type of lower interface on which this interface is stacked. This setting plus 2 bytes for HDLC address/control plus the length in bytes of the HDLC CRC cannot exceed 65535. The maximum value for this object reflects the largest possible value when no CRC is used; technology constraints of a particular implementation may further limit the upper bound value.rw Integer32 .1.3.6.1.4.1.4874.2.2.9.1.2.1.4 |
juniHdlcIfMruThe Maximum Receive Unit (MRU) this interface is permitted to receive. At creation, if a value for this object is not specified, a default will be chosen that is suitable for the type of lower interface on which this interface is stacked. This setting plus 2 bytes for HDLC address/control plus the length in bytes of the HDLC CRC cannot exceed 65535. The maximum value for this object reflects the largest possible value when no CRC is used; technology constraints of a particular implementation may further limit the upper bound value.rw Integer32 .1.3.6.1.4.1.4874.2.2.9.1.2.1.5 |
juniHdlcIfCrcSizeSelects the CRC size: none, 16 bits, or 32 bits.rw Enumeration .1.3.6.1.4.1.4874.2.2.9.1.2.1.6 |
juniHdlcIfDataPolarityPolarity of data transmitted on this HDLC interface. Inverted data is used for certain line coding configurations to ensure sufficient one's density for timing recovery by the remote end.rw Enumeration .1.3.6.1.4.1.4874.2.2.9.1.2.1.7 |
juniHdlcIfClockModeThe clock mode setting for this HDLC interface. This object is only applicable to HDLC interfaces directly over a high speed serial interface (HSSI). At creation, if a value for this object is not specified, a default will be chosen that is suitable for the type of lower interface on which this interface is stacked. If the lower interface is not HSSI, then the default value will be hdlcClockUnsupported(0); if the lower interface is HSSI then the default value will be hdlcClockLine(2).rw Enumeration .1.3.6.1.4.1.4874.2.2.9.1.2.1.8 |
juniHdlcIfClockRateThe clock rate setting for this HDLC interface. This object is only applicable to HDLC interfaces directly over a high speed serial interface (HSSI). At creation, if a value for this object is not specified, a default will be chosen that is suitable for the type of lower interface on which this interface is stacked. If the lower interface is not HSSI, then the default value will be hdlcClockRateUnsupported(0); if the lower interface is HSSI then the default value will be hdlcClockRate44At736Mhz(2).rw Enumeration .1.3.6.1.4.1.4874.2.2.9.1.2.1.9 |
juniHdlcIfForceDteAckThe force DTE acknowledge setting. This object is only applicable to HDLC interfaces directly over a high speed serial interface (HSSI). This is set to force Cisco compatibility mode, and is only valid when the lower interface is configured for internal (DTE) clocking. At creation, if a value for this object is not specified, a default will be chosen that is suitable for the type of lower interface on which this interface is stacked. If the lower interface is not HSSI, then the default value will be forceDteAckUnsupported(0); if the lower interface is HSSI then the default value will be forceDteAckNormal(1).rw Enumeration .1.3.6.1.4.1.4874.2.2.9.1.2.1.10 |
juniHdlcIfIdleCharacterThe HDLC idle character has two possible settings. The value can be set to idleCharacterFlags which translates to 0x7E or it can be set to idleCharacterMarks which translates to 0xFF. At creation, if a value for this object is not specified, the default value of idleCharacterFlags will be assigned.rw Enumeration .1.3.6.1.4.1.4874.2.2.9.1.2.1.11 |
juniHdlcConformance OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.9.4 |
juniHdlcCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.9.4.1 |
juniHdlcComplianceObsolete compliance statement for entities that implement the Juniper HDLC MIB. This compliance statement became obsolete when juniHdlcIfDataPolarity was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.9.4.1.1 |
juniHdlcCompliance2The compliance statement for entities that implement the Juniper HDLC MIB. This compliance statement became obsolete when juniHdlcIfClockMode, juniHdlcIfClockRate, and juniHdlcIfForceDteAck were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.9.4.1.2 |
juniHdlcCompliance3Obsolete compliance statement for entities that implement the Juniper HDLC MIB. This compliance statement became obsolete when juniHdlcIfIdleCharacter was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.9.4.1.3 |
juniHdlcCompliance4The compliance statement for entities that implement the Juniper HDLC MIB. Unknown .1.3.6.1.4.1.4874.2.2.9.4.1.4 |
juniHdlcGroups OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.9.4.2 |
juniHdlcGroupObsolete collection of objects providing management of HDLC interfaces in a Juniper product. This group became obsolete when juniHdlcIfDataPolarity was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.9.4.2.1 |
juniHdlcGroup2Obsolete collection of objects providing management of HDLC interfaces in a Juniper product. This group became obsolete when juniHdlcIfClockMode, juniHdlcIfClockRate, and juniHdlcIfForceDteAck were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.9.4.2.2 |
juniHdlcGroup3Obsolete collection of objects providing management of HDLC interfaces in a Juniper product. This group became obsolete when juniHdlcIfIdleCharacter was added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.9.4.2.3 |
juniHdlcGroup4A collection of objects providing management of HDLC interfaces in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.9.4.2.4 |
More MIBs from Unisphere
Browse all UnisphereMIBs →Juniper-BGP-MIB
SNMP MIB module
673 objects→
Unisphere-Data-BGP-MIB
The Unisphere-Data-BGP-MIB enables monitoring and management of Border Gateway Protocol (BGP) session states, routing table statistics, and neighbor relationships on Dell EMC Unisphere for Data storage systems. It provides access to standard BGP MIB objects for tracking peer connectivity, route advertisements, and protocol error counters within the storage network infrastructure.
466 objects→
Juniper-RADIUS-CLIENT-MIB
The Juniper-RADIUS-CLIENT-MIB enables monitoring of RADIUS client authentication sessions, accounting records, and server reachability states on Juniper network devices. It provides specific counters and gauges for tracking authentication failures, successful logins, and RADIUS server response times to validate access control infrastructure health.
397 objects→
Juniper-UNI-ATM-MIB
The Juniper-UNI-ATM-MIB module provides SNMP management capabilities for Juniper devices configured with Asynchronous Transfer Mode (ATM) user-network interfaces, enabling the monitoring of ATM-specific performance counters, interface states, and VPI/VCI traffic statistics.
380 objects→
Juniper-AAA-MIB
The Juniper-AAA-MIB enables monitoring of authentication, authorization, and accounting events on Juniper Networks devices, specifically tracking user session states, login success/failure counts, and accounting record generation for RADIUS and TACACS+ protocols.
362 objects→
Juniper-POLICY-MIB
SNMP MIB module
348 objects→