ZHONE-COM-IP-RIPv2-MIB :: zhRip2IfConfPoison

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

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

zhRip2IfConfPoison

Module: ZHONE-COM-IP-RIPv2-MIB

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

OID (numeric): 1.3.6.1.4.1.5504.4.1.2.3.1.9

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This variable specifies whether to send poison reverse updates on this interface. Poison reverse updates are used to prevent larger loops within the network by setting the metric (cost) of neighboring routes to infinity. This will prevent two-hop loops.

By default, RIP uses a technique called split horizon to avoid routing loops and allow smaller update packets. Split horizon specifies that when a RIP update is sent out a particular network interface, it should not include routing information acquired over that same interface. Poison Reverse is a variation of the split horizon technique that specifies that all routes are included in an update out a particular interface, but that the metric is set to infinity for routes acquired over that interface. One drawback is that routing update packet sizes are increased when using poison reverse.

Setting the value of this object to 'disable' prevents poison reverse updates, where 'enable' allows poison updates to be sent on this interface. The default value is 'disabled'.

What is zhRip2IfConfPoison?

This read-write INTEGER (disabled(1)/enabled(2)), defaulting to disabled, controls, per its source description, whether poison reverse updates are sent on this interface, a technique that includes all routes in an outgoing update but sets the metric to infinity for routes learned over that same interface, at the cost of larger update packets, in order to more thoroughly prevent two-hop routing loops than basic split horizon alone. Admins enable this on interfaces prone to routing loops, accepting the larger update packet size, for faster and more reliable loop prevention than split horizon provides by itself. For example, enabling poison reverse on a redundant WAN link susceptible to transient loops would help RIP converge more reliably after a topology change, despite the extra bandwidth used by larger updates.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5504.4.1.2.3.1.9
snmpwalk -v2c -c public <target> ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfPoison

Get a specific instance (index 1):

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

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.5504.4.1.2.3.1.9.1 i <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::zhRip2IfConfPoison 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.9zhRip2IfConfPoisonZHONE-COM-IP-RIPv2-MIB