Juniper-UNI-IF-MIB

All MIBs › Juniper-UNI-IF-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2005-10-11

Category: Network Interfaces, Vendor: Juniper

Description: Juniper Networks MIB for managing UNI (User-Network Interface) interface configurations on Juniper E-series edge routers.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is Juniper-UNI-IF-MIB?

Juniper-UNI-IF-MIB is a Juniper Networks enterprise "Generic Interfaces" MIB for JUNOSe E-series platforms, providing an interface table, interface stacking/layering relationships, and per-interface-type counts. It exposes inventory-style data: interface type, stack status between logical/physical layers, and aggregate counts of interfaces by type. Its monitoring value is mainly software/inventory health: juniIfCountTable and juniIfCountNumberOfInterfaces track how many interfaces of a given type exist, letting an admin detect an unexpected drop after a line-card reset or software fault, while juniIfInvStackTable/juniIfInvStackStatus confirms that layered interfaces (e.g., ATM sub-interfaces over physical ports) remain properly stacked. It complements the standard IF-MIB and its ifStackTable, adding Juniper-specific per-type counting. It is typically deployed on Juniper E-series edge routers with complex multi-layer interface stacks (ATM/PPP/VLAN over physical ports). Engineers can download the Juniper-UNI-IF-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-UNI-IF-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Juniper E-series router (JUNOSe)

Monitoring Examples

An admin can poll juniIfCountTable (juniIfCountIfType, juniIfCountNumberOfInterfaces) to track interface counts by type and catch an unexpected drop after a line-card event, then check juniIfInvStackTable/juniIfInvStackStatus to confirm dependent logical interfaces are still correctly layered on their parent. juniIfTable/juniIfType supplies the base inventory used to cross-reference against standard ifTable entries.

What Can Be Monitored

interface count by type
interface stacking/layering status
interface type inventory
interface index-to-type mapping

Imported Objects

From IF-MIB

ifEntry	OBJECT-TYPE
ifStackHigherLayer	OBJECT-TYPE
ifStackLowerLayer	OBJECT-TYPE

From Juniper-MIBs

juniMibs

MODULE-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
juniIfMIB	1.3.6.1.4.1.4874.2.2.3			The Generic Interfaces MIB for the Juniper Networks enterprise.
juniInterfaces	1.3.6.1.4.1.4874.2.2.3.1
juniIf	1.3.6.1.4.1.4874.2.2.3.1.1
juniIfObjects	1.3.6.1.4.1.4874.2.2.3.1.1.1
juniIfTable	1.3.6.1.4.1.4874.2.2.3.1.1.1.1		not-accessible	This table contains a corresponding entry for each entry found in the standard Generic Interfaces MIB ifTable/ifXTable. The entries in this table contain supplementary generic interface characteristics. Entries in ifTable/ifXTable and in this table are created/deleted as a consequence of hardware detection, or of management configuration via standard or enterprise type-specific interface MIBs.
juniIfEntry	1.3.6.1.4.1.4874.2.2.3.1.1.1.1.1		not-accessible	An entry representing an interface's enterprise-defined generic interface characteristics.
JUN juniIfType	1.3.6.1.4.1.4874.2.2.3.1.1.1.1.1.1	JuniIfType	read-only	Identifies the type of this interface.
juniIfInvStackTable	1.3.6.1.4.1.4874.2.2.3.1.1.1.2		not-accessible	A table containing information on the relationships between the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'underneath' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs underneath the sub-layer with ifIndex value y, then this table contains: juniIfInvStackStatus.x.y = active For each ifIndex value, I, which identifies an active interface, there are always at least two instantiated rows in this table associated with I. For one of these rows, I is the value of ifStackHigherLayer; for the other, I is the value of ifStackLowerLayer. (If I is not involved in multiplexing, then these are the only two rows associated with I.) For example, two rows exist even for an interface which has no others stacked on top or below it: ifStackStatus.x.0 = active ifStackStatus.0.x = active This table contains exactly the same number of rows as the ifStackTable, but the rows appear in a different order.
juniIfInvStackEntry	1.3.6.1.4.1.4874.2.2.3.1.1.1.2.1		not-accessible	Information on a particular relationship between two sub-layers, specifying that one sub-layer runs underneath the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable.
ROW juniIfInvStackStatus	1.3.6.1.4.1.4874.2.2.3.1.1.1.2.1.1	RowStatus	read-only	The status of the relationship between two sub-layers. An instance of this object exists for each instance of the ifStackStatus object, and vice versa. For example, if the variable ifStackStatus.H.L exists, then the variable juniIfInvStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value. However, unlike ifStackStatus, the juniIfInvStackStatus object is NOT write-able. A network management application wishing to change a relationship between sub-layers H and L cannot do so by modifying the value of juniIfInvStackStatus.L.H, but must instead modify the value of ifStackStatus.H.L. After the ifStackTable is modified, the change will be reflected in this table.
juniIfCountTable	1.3.6.1.4.1.4874.2.2.3.1.1.1.3		not-accessible	This table contains entries for each interface type's system wide interfaces counts.
juniIfCountEntry	1.3.6.1.4.1.4874.2.2.3.1.1.1.3.1		not-accessible	An entry represents system wide total number of interfaces configured for the particular interface type.
JUN juniIfCountIfType	1.3.6.1.4.1.4874.2.2.3.1.1.1.3.1.1	JuniIfType	not-accessible	Identifies the type of this interface.
U32 juniIfCountNumberOfInterfaces	1.3.6.1.4.1.4874.2.2.3.1.1.1.3.1.2	Unsigned32	read-only	Represents system wide total number of interfaces configured for the particular interface type.
juniIfConformance	1.3.6.1.4.1.4874.2.2.3.1.1.4
juniIfCompliances	1.3.6.1.4.1.4874.2.2.3.1.1.4.1
juniIfCompliance	1.3.6.1.4.1.4874.2.2.3.1.1.4.1.1			Obsolete compliance statement for entities which implement the Juniper Generic Interfaces MIB.
juniIfCompliance1	1.3.6.1.4.1.4874.2.2.3.1.1.4.1.2			The compliance statement for entities which implement the Juniper Generic Interfaces MIB.
juniIfGroups	1.3.6.1.4.1.4874.2.2.3.1.1.4.2
juniIfGroup	1.3.6.1.4.1.4874.2.2.3.1.1.4.2.1			A collection of objects for managing generic interfaces in a Juniper product.
juniIfInvStackGroup	1.3.6.1.4.1.4874.2.2.3.1.1.4.2.2			A collection of objects providing inverted information on the layering of MIB-II interfaces.
juniIfCountGroup	1.3.6.1.4.1.4874.2.2.3.1.1.4.2.3			A collection of objects providing interface information on the system wide count of number of interfaces per interface type.

RFC description

Defines generic interface types and stacking relationships for Juniper enterprise devices.

Start monitoring Juniper E-series router, JUNOSe (generic interfaces/stacking/inventory) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download Juniper-UNI-IF-MIB

What Is Juniper-UNI-IF-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description