ZHONE-COM-IP-RIPv2-MIB :: zhRip2IfConfAuthKey

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › ZHONE-COM-IP-RIPv2-MIB › zhRip2IfConfAuthKey

zhRip2IfConfAuthKey

Module: ZHONE-COM-IP-RIPv2-MIB

OID (symbolic): ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfAuthKey

OID (numeric): 1.3.6.1.4.1.5504.4.1.2.3.1.3

Node type: OBJECT-TYPE

Type: RipAuthKey

Access: read-write

Description: The value to be used as the Authentication Key whenever the corresponding instance of zhRip2IfConfAuthType has a value other than noAuthentication. A modification of the corresponding instance of zhRip2IfConfAuthType does not modify the zhRip2IfConfAuthKey value. If a string shorter than 16 octets is supplied, it will be left- justified and padded to 16 octets, on the right, with nulls (0x00).

Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.

What is zhRip2IfConfAuthKey?

This read-write RipAuthKey (0..16 bytes), which per its source description always reads back as a zero-length string regardless of what's configured (authentication may not be bypassed by reading it), holds the actual authentication key used when zhRip2IfConfAuthType is set to something other than noAuthentication; shorter strings are left-justified and null-padded to 16 bytes. Admins set this to a shared secret matching what neighboring routers use for RIP authentication, understanding that changing zhRip2IfConfAuthType alone doesn't reset or clear this key value. For example, an admin rotating the RIP authentication key across a network would need to explicitly write a new value here on every participating router, since simply switching AuthType off and back on would not clear the old key.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5504.4.1.2.3.1.3
snmpwalk -v2c -c public <target> ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfAuthKey

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5504.4.1.2.3.1.3.1
snmpget -v2c -c public <target> ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfAuthKey.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.5504.4.1.2.3.1.3.1 s <value>

Start monitoring Zhone access/routing equipment (RIPv2 neighbor-adjacency/authentication status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfAuthKey OID value, configure state conditions and alerts, and monitor any Zhone access/routing equipment (RIPv2 neighbor-adjacency/authentication status) from a single console.

OID Breakdown

Upper-level ancestors (9 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.5504ZhoneBITSTORM-HP-160-MIB
1.3.6.1.4.1.5504.4zhoneCommunicationProtocolsZhone
1.3.6.1.4.1.5504.4.1zhoneIpZhone
Numeric OIDNameModule
1.3.6.1.4.1.5504.4.1.2rip2ZHONE-COM-IP-RIPv2-MIB
1.3.6.1.4.1.5504.4.1.2.3zhRip2IfConfTableZHONE-COM-IP-RIPv2-MIB
1.3.6.1.4.1.5504.4.1.2.3.1zhRip2IfConfEntryZHONE-COM-IP-RIPv2-MIB
1.3.6.1.4.1.5504.4.1.2.3.1.3zhRip2IfConfAuthKeyZHONE-COM-IP-RIPv2-MIB