What the router sends on this interface.
ripVersion1 implies sending RIP updates compliant
with RFC 1058. 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.
Parsed from file NS-VR-RIP.mib.txt
Company: None
Module: NETSCREEN-VR-RIPv2-MIB
What the router sends on this interface.
ripVersion1 implies sending RIP updates compliant
with RFC 1058. 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.
Parsed from file NETSCREEN-VR-RIPv2-MIB.mib
Module: NETSCREEN-VR-RIPv2-MIB
Vendor: NetScreen Technologies, Inc.
Module: NETSCREEN-VR-RIPv2-MIB
[Automatically extracted from oidview.com]
nsVrRip2IfConfSend OBJECT-TYPE SYNTAX INTEGER { doNotSend (1), ripVersion1 (2), rip1Compatible (3), ripVersion2 (4), ripV1Demand (5), ripV2Demand (6) } MAX-ACCESS read-create STATUS current DESCRIPTION "What the router sends on this interface. ripVersion1 implies sending RIP updates compliant with RFC 1058. 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." DEFVAL { rip1Compatible } ::= { nsVrRip2IfConfEntry 5 }
nsVrRip2IfConfSend OBJECT-TYPE SYNTAX INTEGER { doNotSend (1), ripVersion1 (2), rip1Compatible (3), ripVersion2 (4), ripV1Demand (5), ripV2Demand (6) } MAX-ACCESS read-create STATUS current DESCRIPTION "What the router sends on this interface. ripVersion1 implies sending RIP updates compliant with RFC 1058. 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." DEFVAL { rip1Compatible } ::= { nsVrRip2IfConfEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3224.18.7.3.1.1 | nsVrRip2IfConfAddress | 0 | 0 | The IP Address of this system on the indicated subnet. For unnumbered interfaces, the value 0.0.0.N, where the least significant… |
| 1.3.6.1.4.1.3224.18.7.3.1.2 | nsVrRip2IfConfDomain | 0 | 0 | Value inserted into the Routing Domain field of all RIP packets sent on this interface. |
| 1.3.6.1.4.1.3224.18.7.3.1.3 | nsVrRip2IfConfAuthType | 0 | 0 | nsVrRip2IfConfAuthtype |
| 1.3.6.1.4.1.3224.18.7.3.1.4 | nsVrRip2IfConfAuthKey | 0 | 0 | The value to be used as the Authentication Key whenever the corresponding instance of nsVrRip2IfConfAuthType has a value other th… |
| 1.3.6.1.4.1.3224.18.7.3.1.6 | nsVrRip2IfConfReceive | 0 | 0 | This indicates which version of RIP updates are to be accepted. Note that rip2 and rip1OrRip2 implies reception of multicast pack… |
| 1.3.6.1.4.1.3224.18.7.3.1.7 | nsVrRip2IfConfDefaultMetric | 0 | 0 | This variable indicates the metric that is to be used for the default route entry in RIP updates originated on this interface. A… |
| 1.3.6.1.4.1.3224.18.7.3.1.8 | nsVrRip2IfConfStatus | 0 | 0 | Writing invalid has the effect of deleting this interface. |
| 1.3.6.1.4.1.3224.18.7.3.1.9 | nsVrRip2IfConfSrcAddress | 0 | 0 | The IP Address this system will use as a source address on this interface. If it is a numbered interface, this MUST be the same … |
| 1.3.6.1.4.1.3224.18.7.3.1.10 | nsVrRip2IfConfVRID | 0 | 0 | Virtual Router ID. VRID range for system created VRs: [1-1024] and for user created VRs: [1025-2048] |