RFC-HIPPI-MIB :: hippiInterconnectStatus

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RFC-HIPPI-MIB › hippiInterconnectStatus

hippiInterconnectStatus

Module: RFC-HIPPI-MIB

OID (symbolic): RFC-HIPPI-MIB::hippiInterconnectStatus

OID (numeric): 1.3.6.1.4.1.10.2.2.2.1.2.1.20

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: As defined in HIPPI-PH, HIPPI connections have interconnect signals that are carried to allow endpoints to determine power on and enable. These signals are also useful in determining that cables are established correctly. There are two (2) signals for all connections that are referred to as INTERCONNECT-A. These signals are used to identify a source to destination as well as a destination to source connection. In addition, 64 bit wide connections (1600 MB) have two (2) additional signals that are referred to as INTERCONNECT-B. These are exactly the same as the INTERCONNECT-A signals but are carried on the second set of cables that make up the 64 bit connection.

These signals are encoded into the lowest order four (4) bits of the hippiInterconnectStatus object as follows: 0 0 0 1 INTERCONNECT-A Source to Destination (1) 0 0 1 0 INTERCONNECT-A Destination to Source (2) 0 1 0 0 INTERCONNECT-B Source to Destination (4) 1 0 0 0 INTERCONNECT-B Destination to Source (8)

What is hippiInterconnectStatus?

A read-only 4-bit value (0-0xF) reporting the state of the HIPPI physical interconnect signals used to confirm cabling and power/enable status: bit 1 for INTERCONNECT-A source-to-destination, bit 2 for A destination-to-source, bit 4 for INTERCONNECT-B source-to-destination (64-bit/1600 Mbit links only), and bit 8 for B destination-to-source - useful for diagnosing miswired or unpowered HIPPI cabling.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.10.2.2.2.1.2.1.20
snmpwalk -v2c -c public <target> RFC-HIPPI-MIB::hippiInterconnectStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.10.2.2.2.1.2.1.20.1
snmpget -v2c -c public <target> RFC-HIPPI-MIB::hippiInterconnectStatus.1

Start monitoring vendor-neutral, standards-based MIB, HIPPI-interconnected high-performance computing equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC-HIPPI-MIB::hippiInterconnectStatus OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, HIPPI-interconnected high-performance computing equipment from a single console.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.10nscCMU-MIB
1.3.6.1.4.1.10.2nscMibNSC-MIB
1.3.6.1.4.1.10.2.2nscManagementNSC-MIB
1.3.6.1.4.1.10.2.2.2nscTransmissionNSC-MIB
1.3.6.1.4.1.10.2.2.2.1nscHippiNSC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.10.2.2.2.1.2hippiTableRFC-HIPPI-MIB
1.3.6.1.4.1.10.2.2.2.1.2.1hippiEntryRFC-HIPPI-MIB
1.3.6.1.4.1.10.2.2.2.1.2.1.20hippiInterconnectStatusRFC-HIPPI-MIB