DECNET-PHIV-MIB :: phivAreaMaxHops

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DECNET-PHIV-MIB › phivAreaMaxHops

phivAreaMaxHops

Module: DECNET-PHIV-MIB

OID (symbolic): DECNET-PHIV-MIB::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?

Sets the maximum number of routing hops allowed from the executor to any other Level 2 routing node; applicable only if this node is an AREA-type router. Must be kept at or above the inter-area network's actual diameter to avoid falsely marking distant areas unreachable.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.18.15.3
snmpwalk -v2c -c public <target> DECNET-PHIV-MIB::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> DECNET-PHIV-MIB::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 Legacy DEC systems/routers (DECnet Phase IV) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DECNET-PHIV-MIB::phivAreaMaxHops OID value, configure state conditions and alerts, and monitor any Legacy DEC systems/routers (DECnet Phase IV) 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.3phivAreaMaxHopsDECNET-PHIV-MIB