A3COM-IPEXTNS-R5-MIB :: a3IPextMode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsA3COM-IPEXTNS-R5-MIBa3IPextMode

a3IPextMode

Module: A3COM-IPEXTNS-R5-MIB

OID (symbolic): A3COM-IPEXTNS-R5-MIB::a3IPextMode

OID (numeric): 1.3.6.1.4.1.43.2.6.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object determines the mode the IP protocol layer operates in. When in multipleNet mode, the system will accept different network addresses for each of its interfaces. Routing may be disabled (via ipForwarding), but the system will still be in routing mode, i.e., it will keep all of its assigned addresses and it may still participate in routing update protocols (if configured). When in singleNet mode, the IP address assigned to interfaces 1 is applied to all interfaces. ipForwarding can only be disabled, and all RIP parameters, other than those related to listening, will be ignored. Note, when the value of this object is changed, the new IP address must also be set in the same PDU. This is required to ensure connectivity remains.

When this object transitions from multipleNet mode to singleNet mode, 1) ipForwarding is automatically set to not-forwarding,

2) all RIP-IP parameters will be ignored except those related to listening on interface 1. These parameters will be applied to all interfaces.

3) an IP address must be configured, in the same request, for interface 1.

the agent removes all other IP addresses, and the IP address assigned to interface 1 will apply to all interfaces.

When this object transitions back to multipleNet mode,

1) an IP address must be assigned, in the same request, to one of the ports,

that IP address will apply only to that port to which it is assigned.

The IP address for interface 1 will no longer apply to all interfaces.

2) ipForwarding will stay at not-forwarding, and

3) all previously ignored RIP-IP parameters will take effect. In order to actively route packets, ipForwarding will need to be set to forwarding.

During this transition, there is the danger that no IP address will have been configured for the interface that receives the SNMP requests, in which case, the device will no longer be manageable. For this reason, it is suggested that the IP addresses for the interface that receives the SNMP requests be set in the same PDU that sets this object.

What is a3IPextMode?

This read-write INTEGER controls whether the IP layer operates in single-network or multi-network mode, affecting how the system handles multiple interface addresses. Operators use this to configure whether the device acts as a single-homed host or supports distributed network configurations with independent addressing per interface. Setting this to multipleNet mode (vs. single-instance) determines routing behavior even when forwarding is disabled.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.2.6.1
snmpwalk -v2c -c public <target> A3COM-IPEXTNS-R5-MIB::a3IPextMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.43.2.6.1.1
snmpget -v2c -c public <target> A3COM-IPEXTNS-R5-MIB::a3IPextMode.1

Set instance 1 (SNMPv2c):

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

Start monitoring Legacy 3Com routers (R5) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the A3COM-IPEXTNS-R5-MIB::a3IPextMode OID value, configure state conditions and alerts, and monitor any Legacy 3Com routers (R5) 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.43a3ComA3COM-BRIDGE-R3-MIB
1.3.6.1.4.1.43.2brouterMIBA3COM-BRIDGE-R3-MIB
Numeric OIDNameModule
1.3.6.1.4.1.43.2.6a3ComIPextnsA3COM-IPEXTNS-R5-MIB
1.3.6.1.4.1.43.2.6.1a3IPextModeA3COM-IPEXTNS-R5-MIB