A3COM-RIP-IPEXTNS-R4-MIB: View SNMP OID List / Download MIB

This parameter specifies the time interval, in seconds, within which RIP-IP sends update packets. This parameter also determines the length of time a route learned through RIP-IP stays in the IP routing table. For example, once a route is in the routing table, the router must receive a RIP update packet indicating the reachability of this route every 6 * a3RipIpUpdateTime. If no updates are received in that time interval, the entry is removed from the routing table.

This table contains parameters that affect the operation of RIP for IP.

Each entry contains parameters specific to each network port on this system.

This provides the port index to which the RIP-IP parameters in this table entry apply.

If talk (1) is specified, RIP-IP sends update and request packets on the specified port. If noTalk (2) is specified, no updates or requests are sent over this port. If talk(1) is specified, 3RipIpDynNbrCtl has been set to dynamicNbr, and the -PORT owner has been set to FR/X.25, the -RIP Neighbor list is built from the ARP table. Enumeration: 'noTalk': 2, 'talk': 1.

If listen (1) is selected, RIP-IP receives and processes incoming update and request packets. If a3RipIpTalkCtl is set to noTalk (2), this system does not send any response packets for the request packets it receives. Enumeration: 'noListen': 2, 'listen': 1.

This object controls how the list of trusted neighbors in a3RipIpTrustedNbrTable is to be interpreted. If this is set to include (1), RIP-IP will accept routing packets from the set of addresses in a3RipIpTrustedNbrTable. If this is set to exclude (2), RIP-IP will accept routing packets from all addresses except those listed in that table for this port. Note, if a3RipIpTrustedNbrTable is empty, RIP-IP will accept routing updates from all neighbors, regardless of the value of this object. Enumeration: 'exclude': 2, 'include': 1.

This parameter determines how split horizon is performed. To achieve split horizon, RIP-IP refrains from advertising a route to a port if the gateway for this route can be reached on the same port. If poison (1) is selected, RIP-IP advertises the route but it uses infinity (16) for the metric. If noPoison (2) is selected, the route is not advertised. Enumeration: 'noPoison': 2, 'poison': 1.

This parameter determines if RIP-IP sends trigger update packets. Trigger update packets are sent when a route's metric has changed. By sending these update packets, RIP does not need to wait for the update interval, allowing earlier notification that a route's metric has changed. Enumeration: 'noTrigger': 2, 'trigger': 1.

This parameter specifies whether RIP-IP advertises the default route. The default route is the network with internet address 0.0.0.0 and is reported with a metric equal to the value of this parameter. If this is set to 0, the default route is advertised only if it was learned and if that default route is allowed by the corresponding policies.

This parameter controls which routes learned by the Exterior Gateway Protocol (EGP) are reported by RIP-IP. If this is set to all (1), all routes learned from EGP or BGP are reported, provided those routes are allowed to be reported by the Network Policy (see a3RipIpNetPolCtl). The metric that will be reported by RIP for all routes learned via EGP or BGP is specified by a3RipIpExtPolAllMet. If this is set to none (2), none of the routes learned from EGP or BGP are reported. If this is set to include (3), routes to destinations listed in a3RipIpExtPolTable are reported. If no routes are listed in a3RipIpExtPolTable, all routes are reported. This applies to the other policy tables as well. If this is set to exclude (4), all routes are reported except those listed in a3RipIpExtPolTable. If no routes are listed in a3RipIpExtPolTable, no routes are reported. This applies to the other policy tables as well. The metric reported for routes learned via EGP or BGP in this case is calculated using the formula specified in a3RipIpImpMetTable (for egp or bgp). (note, in all these cases, Network Policy must be passed before this policy is applied). If this objects gets changed from include to exclude, or from exclude to include, all existing entries will be flushed from the table. Enumeration: 'exclude': 4, 'all': 1, 'include': 3, 'none': 2.

This parameter determines which routes learned by an Interior Gateway Protocol (IGP) are reported by RIP-IP. If this is set to all (1), all routes learned from an IGP are reported, provided those routes are allowed to be reported by the Network Policy (see a3RipIpNetPolCtl) The metric that will be reported by RIP for all routes learned via an IGP (other than RIP) is specified by a3RipIpIntPolAllMet. If this is set to none (2), none of the routes learned from the IGP are reported. If this is set to include (3) routes to destinations listed in a3RipIpIntPolTable are reported. If this is set to exclude (4), all routes are reported except those listed in a3RipIpIntPolTable. If no routes are listed, no routes will be reported. The metric reported for routes learned via an IGP (other than RIP) in this case is calculated using the formula specified in a3RipIpImpMetTable (for ospf or iisis). (note, in all these cases, Network Policy must be passed before this policy is applied). If this objects gets changed from include to exclude, or from exclude to include, all existing entries will be flushed from the table. Enumeration: 'exclude': 4, 'all': 1, 'include': 3, 'none': 2.

This parameter determines which routes are reported by RIP-IP. The policies defined by this object and a3RipIpNetPolTable overrides the policies defined in a3RipIpIntPolCtl/Table, a3RipIpExtPolCtl/Table, and a3RipIpStaPolCtl/Table in deciding whether a route is to be reported. If this is set to all (1), all routes are reported, provided they are allowed by either the interior policy or exterior policy. The metric that will be reported by RIP for all routes is specified by a3RipIpNetPolAllMet. If this is set to none (2), none of the routes are reported. If this is set to include (3), routes to destinations listed in a3RipIpNetPolTable are reported. If this is set to exclude (4), all routes are reported except those listed in a3RipIpNetPolTable. If no routes are listed, no routes will be reported. The metric reported for routes learned via RIP in this case is taken directly from the routing table or from the results of applying one of the other policies. (note, in all these cases, the Interior Policy or Exterior Policy must be passed after this policy is applied. Only those routes that pass both sets of policies will be advertised). If this objects gets changed from include to exclude, or from exclude to include, all existing entries will be flushed from the table. Enumeration: 'exclude': 4, 'all': 1, 'include': 3, 'none': 2.

This parameter is used to filter routing updates from trusted neighbors. It allows control over which RIP routes are received and stored in the routing table. If this is set to all (1), all routes reported by trusted neighbors are received and stored in the routing table. The metric that will be stored in the routing table in this case is specified by a3RipIpRcvPolAllMet. If this is set to none (2), none of the routes are received or stored in the routing table. If this is set to include (3), routes to destinations listed in a3RipIpRcvPolTable are received and stored. If this is set to exclude (4), all routes are received and stored except those listed in a3RipIpRcvPolTable. If this objects gets changed from include to exclude, or from exclude to include, all existing entries will be flushed from the table. Enumeration: 'exclude': 4, 'all': 1, 'include': 3, 'none': 2.

This parameter is used to filter the reporting of static routes. It allows control over which static RIP routes are reported. If this is set to all (1), all static routes are reported, provided those routes are allowed to be reported by a3RipIpNetPolCtl/Table. The metric that will be stored in the routing table in this case is specified by a3RipIpStaPolAllMet. If this is set to none (2), none of the static routes are reported. If this is set to include (3), static routes to destinations listed in a3RipIpStaPolTable are reported. If this is set to exclude (4), all routes are reported except those listed in a3RipIpStaPolTable. (note, in all these cases, Network Policy must be passed before this policy is applied). If this objects gets changed from include to exclude, or from exclude to include, all existing entries will be flushed from the table. Enumeration: 'exclude': 4, 'all': 1, 'include': 3, 'none': 2.

This parameter specifies which routes are reported by RIP updates sent over an unnumbered link. If this object is set to subnetAdvUnn (1), RIP explicitly reports each subnetted route the system knows about. If this object is set to netAdvUnn (2), RIP reports only the IP network rather than each subnet. Enumeration: 'subnetAdvUnn': 1, 'netAdvUnn': 2.

This object specifies the destination IP address to which RIP updates are sent over this port. If this object is set to subnetBcast(1), the RIP advertisement is sent using a directed broadcast IP address as its destination (e.g., 129.213.255.255). If this object has the value all1sBcast, the RIP advertisement is sent using a limited broadcast IP address as its destination (i.e., 255.255.255.255). Enumeration: 'subnetBcast': 1, 'all1sBcast': 2.

When a3RipIpExtPolCtl is set to all, this object specifies the metric used in RIP updates of routes learned via EGP or BGP. If this object is set to zero, the metric is calculated from the metric learned from EGP or BGP according to the formula defined in the a3RipIpImpMetTable (ie, the entry corresponding to egp or bgp).

When a3RipIpIntPolCtl is set to all, this object specifies the metric used in RIP updates of routes learned via OSPF or IISIS. If this object is set to zero, the metric is calculated from the metric learned from OSPF or IISIS according to the formula defined in the a3RipIpImpMetTable (ie, the entry corresponding to ospf or iisis).

When a3RipIpNetPolCtl is set to all, this object specifies the metric used in RIP updates of routes learned via RIP. If this object is set to zero, the metric is taken directly from the routing table.

When a3RipIpRcvPolCtl is set to all, this object specifies the metric stored in the routing table when routing updates are received via RIP (from trusted neighbors).

When a3RipIpStaPolCtl is set to all, this object specifies the metric used in RIP updates of static routes (ie, those routes entered by a user). If this object is set to zero, the metric is calculated from the metric specified by the static entry according to the formula defined in the a3RipIpImpMetTable (ie, the entry corresponding to static).

When a3RipIpDynNbrCtl is set to dynamicNbr over FR or X.25, and -RIP CONTrol is set to TALK, the neighbor list is learnt dynamically as InArp learn the IP addresses of the dlcis or as addresses are added to the ARP table. The user need not configure the -RIP Neighbor parameter manually. The dynamicNbr|NoDynamicNbr has no significance for non-FR and non-X.25 media. When a3RipIpDynNbrCtl is set to NodynamicNbr, any neighbor in the neighbor list is deleted and the -RIP neighbor list from the config file is restored onto the neighbor list. When the -PORT owner parameter is changed from a non-FR and non-X.25 owner to FR or X.25, the -RIP Neighbor list was empty, and the -RIP CONTrol had the value TALK for this port, the code automatically sets this object to DynamicNbr, and fills up the neighbor list with the appropriate IP addresses in the ARP table. Note: only those neighbors of the same IP address network number for this port is being copied from the ARP table to this port's neighbor list. If the -PORT owner parameter is changed from a FR/X.25 to a non-FR and non-X25 media, and this object had the value DynamicNbr, the code automatically changes this object value to NoDynamicNbr and restores the statically configured neighbors from the config file into the -RIP neighbor list. If a3RipIpDynNbrCtl has been set to dynamicNbr and the -PORT owner is FR/X.25, no -RIP neighbor can be statically added. Enumeration: 'noDynamicNbr': 2, 'dynamicNbr': 1.

This parameter determines if RIP-IP aggregates subnetworks with variable-length subnet masks into one network. Enumeration: 'aggregate': 1, 'noAggregate': 2.

This parameter determines if RIP-IP de-aggregate a network into many subnetted network. Enumeration: 'noDeAggregate': 2, 'deAggregate': 1.

This parameter determines if the underlying NBMA network is full-mesh or non-mesh. Partial-mesh is treated as non-mesh. When this object is set to fullMesh(1), RIP-IP advertises routes based on regular split-horizon. If nonMesh(2), RIP-Ip advertises routes based on next-hop split-horizon. This object is only meaningful when the underlying interface is NBMA, (i.e. Frame Relay or X.25) Enumeration: 'fullMesh': 1, 'nonMesh': 2.

The table contains a list of addresses learned via EGP that are to be included or excluded from RIP reports.

Each entry contains a single IP destination address. This destination is either included or excluded from RIP reports about routes learned via EGP. Each entry also contains a metric to be used in the reports.

This defines the port to which this entry applies.

This specifies a route destination learned via EGP that is to be included or excluded (based on a3RipIpExtPolCtl) from RIP reports.

The metric that is to be used in RIP reports of this route. If a metric value in the range of 1 to 15 is specified, the route, together with the specified metric, is reported. If the metric 0 is specified, the routing table metric is calculated according to the formula defined in a3RipIpImpMetTable (for either EGP or BGP). (all fractions are rounded down to the next integer)

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

The table contains a list of addresses learned via an IGP other than RIP that are to be included or excluded from RIP reports.

Each entry contains a single IP destination address. This destination is either included or excluded from RIP reports. Each entry also contains a metric to be used in the reports.

This defines the port to which this entry applies.

This specifies a route destination learned via an IGP that is to be included or excluded (based on a3RipIpIntPolCtl) from RIP reports.

The metric that is to be used in RIP reports of this route. It a metric value in the range of 1 to 15 is specified, the route, together with the specified metric, is reported. If the metric 0 is specified, the routing table metric is calculated according to the formula defined in a3RipIpImpMetTable (for either OSPF or IISIS). (all fractions are rounded down to the next integer)

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

The table contains a list of addresses that are to be included or excluded from RIP reports. Note, Network Policy overrides Static Policy, Interior Policy, and Exterior Policy in deciding whether a route is to be reported.

Each entry contains a single IP destination address. This destination is either included or excluded from RIP reports. Each entry also contains a metric to be used in the reports.

This defines the port to which this entry applies.

This specifies a route destination that is to be included or excluded (based on a3RipIpNetPolCtl) from RIP reports.

The metric that is to be used in RIP reports of this route. If a metric value in the range of 1 to 15 is specified, the route, together with the specified metric, is reported. If the metric 0 is specified, the routing table metric is used.

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

The table contains a list of addresses learned via trusted neighbors that are to be received and stored in the routing table.

Each entry contains a single IP destination address. This destination is either stored or not stored when RIP reports from trusted neighbors are received. Each entry also contains a metric to be used in the routing table entry.

This defines the port to which this entry applies.

This specifies a route destination that is to be stored or not stored (based on a3RipIpRcvPolCtl) when RIP reports from trusted neighbors are received.

The metric that is to be used in the routing table entry for this route. It a metric value in the range of 1 to 15 is specified, the route, together with the specified metric, is stored. If the metric 0 is specified, the routing report metric is used.

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

The table contains a list of static addresses that are to be included or excluded from RIP reports.

Each entry contains a single IP destination address representing a static route. This destination is either included or excluded from RIP reports. Each entry also contains a metric to be used in the reports.

This defines the port to which this entry applies.

This specifies a route destination learned statically that is to be included or excluded (based on a3RipIpStaPolCtl) from RIP reports.

The metric that is to be used in RIP reports of this route. It a metric value in the range of 1 to 15 is specified, the route, together with the specified metric, is reported. If the metric 0 is specified, the routing table metric is calculated according to the formula defined in a3RipIpImpMetTable (for static entries). (all fractions are rounded down to the next integer)

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

This table contains a list of neighbor addresses that RIP-IP uses to determine to which neighbors it should send update packets. RIP-IP neighbors are router that share a common network and participate in the RIP-IP protocol. Each RIP-IP packet can be either broadcast or addressed individually to each neighbor. If no neighbors are configured on the port, RIP broadcasts update packets on the port.

Each entry contains information about a single RIP-IP neighbor. The information include the neighbor's IP address as well as the port from which it can be reached.

This indicates the port from which this neighbor can be reached. The neighbor must be attached to the same network as this port.

This specifies the IP address of the RIP-IP neighbor.

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

This table contains a list of RIP-IP neighbors from which RIP-IP accepts packets. If this table contains no entries for a particular port, RIP-IP will accept all packets from that port.

Each entry identifies a trusted neighbor from which RIP-IP will accept routing packets.

This specifies the port for which this table entry applies.

This identifies the IP address of a trusted neighbor from which RIP-IP will accept (or not, depending on the value of a3RipIpTrustedNbrCtl) routing packets.

This object is used to add and delete entries in this table. See the notes describing RowStatus at the beginning of this MIB.

This table specifies the operations to be performed on metrics imported from other routing update protocols before they are reported by RIP.

Each entry specifies the operations to be performed on the metric imported from a specific routing update protocol before it is reported by RIP.

This object identifies the routing update protocol from which metrics (and routes) are imported. Enumeration: 'bgp': 4, 'iisis': 2, 'static': 5, 'egp': 3, 'ospf': 1.

This specifies the operation to be performed on the native protocol metric before it is reported by RIP. Enumeration: 'multiply': 1, 'divide': 2.

This specifies the operand of the operation specified by the corresponding instance of a3RipIpImpMetOperation. See the comments describing this table for more details. If this object has the value 0, the default formulas are used. These are ... for OSPF: metric in routing table ----------------------- 4096 for IISIS: metric in routing table ----------------------- 64 for EGP: metric in routing table ----------------------- 16 for BGP: metric in routing table ----------------------- 1024 for static: metric in routing table (unchanged)