RFC1289-phivMIB :: phivAreaMaxHops

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RFC1289-phivMIB › phivAreaMaxHops

phivAreaMaxHops

Module: RFC1289-phivMIB

OID (symbolic): RFC1289-phivMIB::phivAreaMaxHops

OID (numeric): 1.3.6.1.2.1.18.15.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This value represents the maximum number of routing hops allowable from the executor to any other level 2 routing node. This parameter is only applicable if the executor node is of type AREA.

What is phivAreaMaxHops?

This sets the maximum routing hops allowed from this node to any other level-2 (area) routing node; it only applies if this node is itself an AREA-type router. Admins raise it as the number of inter-area hops in the network grows.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.18.15.3
snmpwalk -v2c -c public <target> RFC1289-phivMIB::phivAreaMaxHops

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.18.15.3.1
snmpget -v2c -c public <target> RFC1289-phivMIB::phivAreaMaxHops.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.18.15.3.1 i <value>

Start monitoring DECnet Phase IV network nodes with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1289-phivMIB::phivAreaMaxHops OID value, configure state conditions and alerts, and monitor any DECnet Phase IV network nodes from a single console.

OID Breakdown

Upper-level ancestors (8 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.18phivDECnet-iv
1.3.6.1.2.1.18.15areaDECnet-iv
Numeric OIDNameModule
1.3.6.1.2.1.18.15.3phivAreaMaxHopsRFC1289-phivMIB