This attribute determines the metric usage for this RIP instance.
This flag is used to determine the way metrics are incremented.
RFC1058 way :
Sending Update: This is to use the metric for the route from the routing
table as the advertised metric to be sent for that route. Nothing is ever
added to this value from the sending side. The only special case
handling is that if the route being advertised is the network route of a
directly connectednetwork, the metric in the routing table will be zero.
Then the RipIf interface metric for the interface being advertised is used
as the advertise metric. If the interface being advertised is not a Rip
interface, then metric value of 1 is used.
Receiving Update: Add receiving interface's RIP metric to the metric for
the route in the received advertisement and install the result in the
receiver's routing table as the metric for that route.
Older way:
Sending Updates: Add the out going interfaces rip metric to the metric
for a route in the routing table to form the metric to be advertised for
that route.
Receiving Updates: The metric received in the advertisement for a route
is put directly in the routing table as the metric for that route.
Note: It is recommended that, all the routers in this autonomous system
should be following the rfc1058 metric system.
Setting this flag to disabled will have the effect of running the RIP with
old metric incrementing system.
Parsed from file nortelPP-ipV1_BG00S4C.mib.txt
Company: None
Module: Nortel-Magellan-Passport-IpMIB
This attribute determines the metric usage for this RIP instance.
This flag is used to determine the way metrics are incremented.
RFC1058 way :
Sending Update: This is to use the metric for the route from the routing
table as the advertised metric to be sent for that route. Nothing is ever
added to this value from the sending side. The only special case
handling is that if the route being advertised is the network route of a
directly connectednetwork, the metric in the routing table will be zero.
Then the RipIf interface metric for the interface being advertised is used
as the advertise metric. If the interface being advertised is not a Rip
interface, then metric value of 1 is used.
Receiving Update: Add receiving interface's RIP metric to the metric for
the route in the received advertisement and install the result in the
receiver's routing table as the metric for that route.
Older way:
Sending Updates: Add the out going interfaces rip metric to the metric
for a route in the routing table to form the metric to be advertised for
that route.
Receiving Updates: The metric received in the advertisement for a route
is put directly in the routing table as the metric for that route.
Note: It is recommended that, all the routers in this autonomous system
should be following the rfc1058 metric system.
Setting this flag to disabled will have the effect of running the RIP with
old metric incrementing system.
Parsed from file Nortel-Magellan-Passport-IpMIB.mib
Module: Nortel-Magellan-Passport-IpMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-Magellan-Passport-IpMIB
[Automatically extracted from oidview.com]
vrIpRipRfc1058MetricUsage OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute determines the metric usage for this RIP instance. This flag is used to determine the way metrics are incremented. RFC1058 way : Sending Update: This is to use the metric for the route from the routing table as the advertised metric to be sent for that route. Nothing is ever added to this value from the sending side. The only special case handling is that if the route being advertised is the network route of a directly connectednetwork, the metric in the routing table will be zero. Then the RipIf interface metric for the interface being advertised is used as the advertise metric. If the interface being advertised is not a Rip interface, then metric value of 1 is used. Receiving Update: Add receiving interface's RIP metric to the metric for the route in the received advertisement and install the result in the receiver's routing table as the metric for that route. Older way: Sending Updates: Add the out going interfaces rip metric to the metric for a route in the routing table to form the metric to be advertised for that route. Receiving Updates: The metric received in the advertisement for a route is put directly in the routing table as the metric for that route. Note: It is recommended that, all the routers in this autonomous system should be following the rfc1058 metric system. Setting this flag to disabled will have the effect of running the RIP with old metric incrementing system." DEFVAL { enabled } ::= { vrIpRipProvEntry 3 }
vrIpRipRfc1058MetricUsage OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute determines the metric usage for this RIP instance. This flag is used to determine the way metrics are incremented. RFC1058 way : Sending Update: This is to use the metric for the route from the routing table as the advertised metric to be sent for that route. Nothing is ever added to this value from the sending side. The only special case handling is that if the route being advertised is the network route of a directly connectednetwork, the metric in the routing table will be zero. Then the RipIf interface metric for the interface being advertised is used as the advertise metric. If the interface being advertised is not a Rip interface, then metric value of 1 is used. Receiving Update: Add receiving interface's RIP metric to the metric for the route in the received advertisement and install the result in the receiver's routing table as the metric for that route. Older way: Sending Updates: Add the out going interfaces rip metric to the metric for a route in the routing table to form the metric to be advertised for that route. Receiving Updates: The metric received in the advertisement for a route is put directly in the routing table as the metric for that route. Note: It is recommended that, all the routers in this autonomous system should be following the rfc1058 metric system. Setting this flag to disabled will have the effect of running the RIP with old metric incrementing system." DEFVAL { enabled } ::= { vrIpRipProvEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.2.4.1.100.6.8.10.1.2 | vrIpRipMigrateRip | 0 | 0 | This attribute sets the preference level of OSPF-internal routes to be less preferred than RIP. Note: This parameter should only b… |
| 1.3.6.1.4.1.562.2.4.1.100.6.8.10.1.4 | vrIpRipGenerateDiscardRoute | 0 | 0 | This attribute when set to yes will add network disacrd routes to the routing and forwarding table for the subnetted interfaces … |
| 1.3.6.1.4.1.562.2.4.1.100.6.8.10.1.5 | vrIpRipRipUpdate | 0 | 0 | This attribute sets the interval for sending updates bewteen RIP neighbours. Set this attribute with a value less than that of t… |
| 1.3.6.1.4.1.562.2.4.1.100.6.8.10.1.6 | vrIpRipRipTimeout | 0 | 0 | This attribute sets the RIP timeout interval. If this timer expires, the route is no longer valid. The ripTimeout timer starts w… |
| 1.3.6.1.4.1.562.2.4.1.100.6.8.10.1.7 | vrIpRipGarbageCollectTimer | 0 | 0 | This attribute sets the interval between a route's timeout expiring and the deletion of that route's information from the routin… |