All MIBs › ZHONE-COM-IP-RIPv2-MIB › zhRip2IfConfSend
zhRip2IfConfSend
Module: ZHONE-COM-IP-RIPv2-MIB
OID (symbolic): ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfSend
OID (numeric): 1.3.6.1.4.1.5504.4.1.2.3.1.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: What the router sends on this interface. If set to 'doNotSend', no RIP updates are sent out on this interface. If set to 'ripVersion1', RIP updates compliant with RFC 1058 are sent. 'rip1Compatible' implies broadcasting RIP-2 updates using RFC 1058 route subsumption rules. 'ripVersion2' implies multicasting RIP-2 updates. 'ripV1Demand' indicates the use of Demand RIP on a WAN interface under RIP Version 1 rules. 'ripV2Demand' indicates the use of Demand RIP on a WAN interface under Version 2 rules. The default is 'rip1Compatible'.
What is zhRip2IfConfSend?
This read-write INTEGER, defaulting to rip1Compatible, specifies, per its source description, what RIP update format this interface transmits: doNotSend (no updates), ripVersion1 (RFC 1058 compliant), rip1Compatible (broadcasts RIP-2 with RFC 1058 route subsumption), ripVersion2 (multicasts RIP-2), or the ripV1Demand/ripV2Demand variants for Demand RIP on WAN interfaces. Admins change this from the RIP-1-compatible default to ripVersion2 in networks with only RIP-2-capable routers, gaining multicast efficiency and full subnet-mask support that RIP-1 lacks. For example, setting this to ripVersion2(4) on an interface facing only modern routers would switch from broadcast to multicast RIP updates, reducing unnecessary processing load on non-RIP hosts on the segment.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5504.4.1.2.3.1.4 snmpwalk -v2c -c public <target> ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfSend
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.5504.4.1.2.3.1.4.1 snmpget -v2c -c public <target> ZHONE-COM-IP-RIPv2-MIB::zhRip2IfConfSend.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.5504.4.1.2.3.1.4.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> zhRip2IfConfSend.1
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::zhRip2IfConfSend 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.5504 | Zhone | BITSTORM-HP-160-MIB |
| 1.3.6.1.4.1.5504.4 | zhoneCommunicationProtocols | Zhone |
| 1.3.6.1.4.1.5504.4.1 | zhoneIp | Zhone |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.5504.4.1.2 | rip2 | ZHONE-COM-IP-RIPv2-MIB |
| 1.3.6.1.4.1.5504.4.1.2.3 | zhRip2IfConfTable | ZHONE-COM-IP-RIPv2-MIB |
| 1.3.6.1.4.1.5504.4.1.2.3.1 | zhRip2IfConfEntry | ZHONE-COM-IP-RIPv2-MIB |
| 1.3.6.1.4.1.5504.4.1.2.3.1.4 | zhRip2IfConfSend | ZHONE-COM-IP-RIPv2-MIB |