DC-RTM-MIB
The MIB module for management of the DC-RTM product.
Main OID:
rtmMib.1.2.826.0.1.1578918.5.61.1
241
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
241 total| Object Name |
|---|
rtmMibThe MIB module for management of the DC-RTM product. MODULE-IDENTITY .1.2.826.0.1.1578918.5.61.1 |
rtmObjects OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.1 |
rtmEntityTableThe table of DC-RTM entities. SEQUENCE OF RtmEntityEntry .1.2.826.0.1.1578918.5.61.1.1.1 |
rtmEntityEntryEach entry represents an instance of the DC-RTM entity. RtmEntityEntry .1.2.826.0.1.1578918.5.61.1.1.1.1 |
rtmEntityFteIndexThe index of this rtmEntityEntry. This is the HAF entity index passed on the entity create parameters. FteIndex .1.2.826.0.1.1578918.5.61.1.1.1.1.1 |
rtmEntityRowStatusUsed to create and delete a DC-RTM fault tolerant entity.rw RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.2 |
rtmEntityAdminStatThe desired administrative state of the DC-RTM entity.rw AdminStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.3 |
rtmEntityOperStatusThe current operational state of the DC-RTM entity.ro OperStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.4 |
rtmEntityDsConnctdThe administrative distance used for directly connected routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.5 |
rtmEntityDsStatDfThe default administrative distance used for statically defined routes in the static routes MIB table. It can be overridden for individual static routes. The lower the distance for a given route, the more likely that route is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.6 |
rtmEntityDsOspfIntThe administrative distance used for OSPF internal routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.7 |
rtmEntityDsOspfExtThe administrative distance used for OSPF Autonomous System external routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.8 |
rtmEntityDsIntBgpThe administrative distance used for internal and VPN BGP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.9 |
rtmEntityDsExtBgpThe administrative distance used for external BGP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.10 |
rtmEntityDsIsisInt1The administrative distance used for IS-IS level 1 internal routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.11 |
rtmEntityDsIsisInt2The administrative distance used for IS-IS level 2 internal routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.12 |
rtmEntityDsIsisExt1The administrative distance used for IS-IS level 1 external routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.13 |
rtmEntityDsIsisExt2The administrative distance used for IS-IS level 2 external routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.14 |
rtmEntityDsRipThe administrative distance used for RIP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.15 |
rtmEntityDsEgpThe administrative distance used for Exterior Gateway Protocol routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.16 |
rtmEntityDsPdThe administrative distance used for routes injected using DHCPv6 prefix delegation protocol. The lower the distance for a given type of route, the more likely a route of this type is to be used by RTM as the active route for the given destination.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.17 |
rtmEntityDsHelloThe administrative distance used for FuzzBall HelloSpeak routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.18 |
rtmEntityDsEsisThe administrative distance used for ISO 9542 routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.19 |
rtmEntityDsBbnspfigpThe administrative distance used for BBN SPF IGP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.20 |
rtmEntityDsIdprThe administrative distance used for InterDomain Policy Routing routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.21 |
rtmEntityDsIgrpThe administrative distance used for IGRP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.22 |
rtmEntityDsEigrpSmmThe administrative distance used for enhanced IGRP summary routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.23 |
rtmEntityDsIntEigrpThe administrative distance used for internal enhanced IGRP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.24 |
rtmEntityDsEigrpExtThe administrative distance used for enhanced IGRP external routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.25 |
rtmEntityDsUnknownThe administrative distance used for routes which come from an unrecognized routing protocol. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.26 |
rtmEntityEqlCostOptHow to select which equal cost routes to give to an active routing information consumer, if there is more than one route to a given destination with the lowest administrative distance. This parameter is used in building responses to ATG_QCAR_GET_ROUTES and ATG_QCAR_QUERY_ROUTE signals, and also in building ATG_QCAR_ROUTE_UPDATE and ATG_QCAR_ROUTE_IND signals for consumers that require them. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE and the admin status is AMB_ADMIN_STATUS_UP. If you want to use IGP shortcuts for any routes then this field must be set to 'equalCostAll'.rw EqualCostRouteOpts .1.2.826.0.1.1578918.5.61.1.1.1.1.27 |
rtmEntityDelDeadRteWhether to delete routes from a Routing Protocol Manager (RPM) whose join to DC-RTM goes down. If this is set to TRUE then the routes are deleted after the time specified in the 'dead RPM timer' parameter. If the join between an RPM and DC-RTM goes down, typically because the RPM is no longer running, then the routes received from that RPM gradually become out of date. This parameter allows DC-RTM to continue to use these routes regardless of whether the RPM ever restarts, or to stop using them after a period of time. This period of time should represent the maximum amount of time for which the RPM would be down if this were only a temporary state of affairs. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE and the admin status is AMB_ADMIN_STATUS_UP.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.28 |
rtmEntityDeadRpmTmrOnly used if the option is set to TRUE to delete routes from an RPM which DC-RTM can no longer see. This field defines the period of time that the join to an RPM can be down before its routes are deleted. This period of time should represent the maximum amount of time for which the RPM would be down if this were only a temporary state of affairs. The units for this field are minutes by default. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE and the admin status is AMB_ADMIN_STATUS_UP.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.1.1.29 |
rtmEntityRouteNumberThe number of destination prefixes to which DC-RTM currently has a route. This is the same as the number of rows in the rtmRouteTable if the following are both true. - Either rtmEntityEqlCostOpt is set to 'one', or DC-RTM knows of at most one route to each destination prefix. This means that there is at most one route in rtmRouteTable for each destination prefix included in rtmEntityRouteNumber. - None of the routes which DC-RTM has learned about are loose next hops that cannot be resolved. This means that there is at least one route in rtmRouteTable per destination prefix included in rtmEntityRouteNumber.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.1.1.30 |
rtmEntityAddressFamilyThe address family that this instance of DC-RTM supports. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE and the admin status is AMB_ADMIN_STATUS_UP.rw InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.1.1.31 |
rtmEntityDsDvmrpThe administrative distance used for DVMRP routes. The lower the distance for a given type of route, the more likely a route of this type is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.32 |
rtmEntityI3IndexThe entity index of the instance of the I3 stub to which this instance of DC-RTM should join. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE and the admin status is AMB_ADMIN_STATUS_UP.rw FteIndex .1.2.826.0.1.1578918.5.61.1.1.1.1.33 |
rtmEntityI3JoinStatusThe status of the I3 master join.ro RtmMjStatus .1.2.826.0.1.1578918.5.61.1.1.1.1.34 |
rtmEntityPartnerWaitTimeThe period that DC-RTM waits for joins from Routing Protocol Managers (RPMs) to be reestablished when DC-RTM is activated. DC-RTM checks for routing table convergence by waiting for a complete set of routes from all joins from RPMs that are established within this period. The partner wait timer duration effectively acts as the minimum restart interval. The value should be set to zero if the forwarding table does not maintain routing state when DC-RTM restarts.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.1.1.35 |
rtmEntityStartupTimeThis is the startup timer duration that is used when DC-RTM is activated and no routing state has been retained by the forwarding table as part of graceful restart procedures. This timer duration is used when rtmEntityFtStateRetained is 'false'. It determines the maximum length of time before DC-RTM deems that routing table convergence is complete and hence the maximum length of time before DC-RTM sends routing updates to the forwarding table. This is typically set to a small value to ensure that the forwarding table is populated in a timely manner. Time is in milisecondsrw Integer32 .1.2.826.0.1.1578918.5.61.1.1.1.1.36 |
rtmEntityRestartTimeThis is the startup timer duration that is used when DC-RTM is activated and routing state has been retained by the forwarding table as part of graceful restart procedures. This timer duration is used when rtmEntityFtStateRetained is 'true'. It determines the maximum length of time before DC-RTM deems that routing table convergence is complete and hence the maximum length of time before DC-RTM sends routing updates to the forwarding table. This is typically set to a value greater than the restart timer duration of each routing protocol, so that the routing table can converge before the forwarding table is updated.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.1.1.37 |
rtmEntityFtStateRetainedWhether state has been maintained by the forwarding table during a restart of DC-RTM. This indicates which startup timer duration DC-RTM should uses. Setting this to 'true' causes DC-RTM to use the value of rtmEntityRestartTime as the startup timer duration. Setting this to 'false' causes DC-RTM to use the value of rtmEntityStartupTime as the startup timer duration.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.38 |
rtmEntityUseUnidirectionalLinksAre unidirectional links usable for the FIB maintained by this instance of DC-RTM? If set to 'false' then unidirectional interfaces reported over the I3 and IGP shortcuts reported over the RPI are discarded. If set to 'true' then unidirectional interfaces can be used for next hops reported over the Active Routes Interface. Note in particular that IGP shortcuts through TE-tunnel next hops are reported over the Active Routes Interface in addition to native adjacency next hops. If the active route consumers of this FIB cannot use unidirectional links then this field should be set to 'false'. An example of such an active route consumer is DC-PIM. Because DC-PIM uses paths for Reverse Path Forwarding, it cannot use unidirectional links. If this field is changed while DC-RTM is active, DC-RTM deactivates and then reactivates in order to refresh all routing information.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.39 |
rtmEntityBfdIndexThe entity index of the instance of the BFD stub to which this instance of DC-RTM should join. A value of zero indicates that no BFD join is required. If a non-zero value is specified then DC-RTM can only be active if the corresponding BFD stub is active.rw NumericIndexOrZero (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.40 |
rtmEntityBfdJoinStatusThe status of the BFD master join.ro RtmMjStatus .1.2.826.0.1.1578918.5.61.1.1.1.1.41 |
rtmEntityEnableTrapSupportSet this object to 'true' to enable trap support in DC-RTM. When this field is set to 'true', DC-RTM will generate the rtmOperStateChange, rtmStaticRouteChange and rtmPathActivityChange traps.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.1.1.42 |
rtmRedistTableThe table of DC-RTM redistribution information entries. This table is used to determine how routing information is redistributed to routing protocol managers (RPMs) using DC-RTM's Routing Protocol Input interface. The RPM to which the information may be redistributed is called the destination RPM. Routing information is received from RPMs and from the MIB (for static routes); these are referred to as the routing information source. In general, DC-RTM will not redistribute a route from an RPM back to the same RPM. The one exception to this is if it is explicitly configured to do so - in other words, if it is configured with a redistribution rule where the source and destination filters both indicate the same RPM instance. One example use for this is to inform an instance of BGP which of its routes are active - see the definition of bgpRmAfiSafiAdvertiseInactive in the BGP MIB for more details. SEQUENCE OF RtmRedistEntry .1.2.826.0.1.1578918.5.61.1.1.2 |
rtmRedistEntryInformation defining how routing information is redistributed to routing protocol managers (RPMs)by DC-RTM on its Routing Protocol Input interface. There are two key aspects to an entry in this table. Firstly, it contains a set of filters which determine whether or not the entry applies to a given pairing of a given set of routing information and a given destination RPM. There is a filter priority to determine which entry to use if there are multiple entries whose filters match a given pairing. Secondly, it contains parameters to use when redistributing the routing information to the destination RPM, including a flag which determines whether or not to redistribute at all. RtmRedistEntry .1.2.826.0.1.1578918.5.61.1.1.2.1 |
rtmRedistFteIndexThe HAF entity index identifying the instance of DC-RTM to which this redistribution table entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.2.1.1 |
rtmRedistEntryIdThe index of this DC-RTM redistribution table entry within the DC-RTM entity. This is an arbitrarily selected identifier. Unsigned32 .1.2.826.0.1.1578918.5.61.1.1.2.1.2 |
rtmRedistRowStatusUsed to create and delete a DC-RTM redistribution table entry.rw RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.3 |
rtmRedistAdminStatThe administrative state of the redistribution table entry. The row status by itself does not indicate whether the redistribution is currently active. The row must be defined and the administrative status must be up. This enables a MIB agent to turn off a particular redistribution without deleting it from the table altogether.rw AdminStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.4 |
rtmRedistPriorityThe priority assigned to this table entry. The lower this value takes, the higher the priority of the entry. The priority takes effect when there is more than one entry in the table whose filters match a pairing of routing information and destination RPM.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.2.1.5 |
rtmRedistInfoSrcThe source of the routing information. This is one of: - an RPM, joined to DC-RTM on the Routing Protocol Input interface - 'static' for statically defined routes, defined in the static routes table with path type ATG_QC_PATH_STATIC - 'connected' for routes to local IP addresses and directly connected IP addresses and subnets, learned via the I3 interface, or defined in the static route table with path type ATG_QC_PATH_CONNECTED - 'all', meaning that this entry applies to routes from all RPMs and static routes, but not routes learnt via the I3 interface - 'all-incl-connected', meaning that this entry applies to routes from all RPMs, static routes, and routes learnt via the I3 interface.rw InfoSourceDest .1.2.826.0.1.1578918.5.61.1.1.2.1.6 |
rtmRedistSrcInstFltSpecifies whether or not a source instance filter is in use. If it is not in use then this entry applies to all instances of the source RPM. The purpose of this filter is to allow an entry to apply to only one instance of the source RPM if more than one instance is active. The filter must always be off if the routing information source is set to 'all' or 'all-incl-connected'.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.7 |
rtmRedistSrcInstValue of the source instance filter, if in use. If the filter is in use then do not match the source routing information to this entry if this filter value does not match the fault tolerant entity index of the RPM instance specified as the routing information source.rw FteIndex .1.2.826.0.1.1578918.5.61.1.1.2.1.8 |
rtmRedistInfoDestThe destination of the routing information. This is usually an RPM, joined to DC-RTM on the Routing Protocol Input interface. It can also be set to 'all' or 'all-incl-connected', meaning that this entry applies to all routing information destinations.rw InfoSourceDest .1.2.826.0.1.1578918.5.61.1.1.2.1.9 |
rtmRedistDestInstFltSpecifies whether or not a destination instance filter is in use. If it is not in use then this entry applies to all instances of the destination RPM. The purpose of this filter is to allow an entry to apply to only one instance of the destination RPM if more than one instance is active. The filter must always be off if the routing information destination is 'all' or 'all-incl-connected'.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.10 |
rtmRedistDestInstValue of the destination instance filter, if in use. If the filter is in use then do not redistribute this routing information to a given instance of an RPM if this filter value does not match the fault tolerant entity index of the RPM instance.rw FteIndex .1.2.826.0.1.1578918.5.61.1.1.2.1.11 |
rtmRedistAddrFilterTypeThe type of the address used as the destination address filter. This object must be set to the same value as rtmEntityAddressFamily, and this is its default value.rw InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.2.1.12 |
rtmRedistAddrFilterDestination IP address filter. Do not match the source routing information to this entry if one of these fails: - the destination IP address in the source routing information, with the IP address filter prefix length applied, matches the IP address filter with the IP address filter prefix length applied - the destination IP address prefix length is greater than or equal to the IP address filter prefix length. The IP address filter prefix length is given by the rtmRedistAddrFltLen object. Applying the prefix length to an address means taking the first rtmRedistAddrFltLen bits of the address. To avoid having any destination IP address filtering, set the IP address filter to all zeroes and the IP address filter prefix length to zero. The length of this IP address must be the address length for the family given by rtmEntityAddressFamily.rw InetAddress .1.2.826.0.1.1578918.5.61.1.1.2.1.13 |
rtmRedistAddrFltLenDestination IP address filter prefix length (in bits). Do not match the source routing information to this entry if one of these fails: - the destination IP address in the source routing information, with the IP address filter prefix length applied, matches the IP address filter with the IP address filter prefix length applied - the destination IP address prefix length is greater than or equal to the IP address filter prefix length. If the IP address filter prefix length is L, then applying the length to an address means taking the first L bits of the address. To avoid having any destination IP address filtering, set the IP address filter to all zeroes and the IP address filter prefix length to zero.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.2.1.14 |
rtmRedistHopFltValTypeThe type of the address used as the next hop address filter. This object must be set to the same value as rtmEntityAddressFamily, and this is its default value.rw InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.2.1.15 |
rtmRedistHopFltValValue of next hop filter. Do not match the source routing information to this entry if none of the next hop values in the source routing information, with the next hop filter prefix length applied, matches the next hop filter value with the next hop filter prefix length applied. The next hop filter prefix length is given by the rtmRedistHopFltLen object. Applying the prefix length to an address means taking the first rtmRedistHopFltLen bits of the address. To avoid having any next hop filtering, set the next hop filter to all zeroes and the next hop filter prefix length to zero. The length of this next hop filter must be the address length for the family given by rtmEntityAddressFamily.rw InetAddress .1.2.826.0.1.1578918.5.61.1.1.2.1.16 |
rtmRedistHopFltLenNext hop filter prefix length. Do not match the source routing information to this entry if none of the next hop values in the source routing information, with the next hop filter prefix length applied, matches the next hop filter value with the next hop filter prefix length applied. If the next hop filter prefix length is L, then applying the length to an address means taking the first L bits of the address. To avoid having any next hop filtering, set the next hop filter to all zeroes and the next hop filter prefix length to zero.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.2.1.17 |
rtmRedistIfIndexFltSpecifies whether or not an output network interface index filter is in use.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.18 |
rtmRedistIfIndexValue of output network interface index filter, if in use. If the filter is in use then do not match the source routing information to this entry if none of the output network interface indexes in the source routing information matches this filter value.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.2.1.19 |
rtmRedistPathTypeFltSpecifies whether or not a path type filter is in use. If it is not in use then this entry applies to all path type values. A path type filter can only be used if the routing information source filter _info_src_ is not set to 'all' or 'all-incl-connected'. The value of the path type filter, if used, must be one of the path types which matches the routing information source. For example, a path type filter of 'OSPF external type 1' can only be used if the routing information source filter is set to OSPF.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.20 |
rtmRedistPathTypeValue of path type filter, if in use. If the filter is in use then do not match the source routing information to this entry if the path type in the source routing information does not match this filter value. A path type filter can only be used if the routing information source filter _info_src_ is not set to 'all' or 'all-incl-connected'. The value of the path type filter, if used, must be one of the path types which matches the routing information source. For example, a path type filter of 'OSPF external type 1' can only be used if the routing information source filter is set to OSPF.rw PathType (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.21 |
rtmRedistOspfAreaFltSpecifies whether or not an OSPF area filter is in use. The filter can only be on if the routing information source field is OSPF.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.22 |
rtmRedistOspfAreaValue of OSPF area filter, if in use. If the filter is in use then do not match the source routing information to this entry if the OSPF area ID in the information does not match this area ID.rw IpAddress .1.2.826.0.1.1578918.5.61.1.1.2.1.23 |
rtmRedistOspfTagFltSpecifies whether or not an OSPF tag filter is in use. The filter can only be on if the routing information source field is OSPF.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.24 |
rtmRedistOspfTagValue of OSPF tag filter, if in use. If the filter is in use then do not match the source routing information to this entry if the tag in the information does not match this tag.rw OspfTag .1.2.826.0.1.1578918.5.61.1.1.2.1.25 |
rtmRedistCommunityFltSpecifies whether or not a BGP community number filter is in use. The filter can only be on if the routing information source field is BGP.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.26 |
rtmRedistCommunityValue of BGP community number filter, if in use. If the filter is in use then do not match the source routing information to this entry if there is no match between one of the community numbers in the source routing information and the value of this filter.rw BgpCommunity .1.2.826.0.1.1578918.5.61.1.1.2.1.27 |
rtmRedistExtCommFltSpecifies whether or not a BGP extended community number filter is in use. The filter can only be on if the routing information source field is BGP.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.28 |
rtmRedistExtCommValue of BGP extended community number filter, if in use. If the filter is in use then do not match the source routing information to this entry if there is no match between one of the extended community numbers in the source routing information and the value of this filter.rw BgpExtendedCommunity .1.2.826.0.1.1578918.5.61.1.1.2.1.29 |
rtmRedistRedistFlagFlag determining whether or not DC-RTM redistributes routing information from the given source to the given destination.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.30 |
rtmRedistMetricConvHow to act on the value of the metric in the routing information received from the source to create a value for the metric in the routing information sent to the destination. This field is only used if the redistribution flag is TRUE.rw MetricConversion .1.2.826.0.1.1578918.5.61.1.1.2.1.31 |
rtmRedistMetricValueNumerical parameter to use when creating a value for the metric in the routing information sent to the destination based on the supplied metric in the routing information received from the source. This field is only used if the redistribution flag is TRUE and the metric conversion field is set to 'constant', 'scale up', 'scale down' or 'truncate'. If the metric conversion field is 'constant' then the new metric value is just the value of the numerical parameter. If the metric conversion field is 'scale up' then the new metric value is the supplied metric multiplied by the value of the numerical parameter (or 0xffffffff if this is smaller). If the metric conversion method is 'scale down' then the new metric value is the supplied metric divided by the value of the numerical parameter (rounded down to the next integer). The numerical parameter cannot be zero in this case. If the metric conversion field is 'truncate' then the new metric value is the lower value of the supplied metric value and the numerical parameter.rw Unsigned32 .1.2.826.0.1.1578918.5.61.1.1.2.1.32 |
rtmRedistNwPathTypeType of path to set in routing information sent to destination. This field is only used if the redistribution flag is TRUE. If the information destination filter _info_dest_ is set to 'all' or 'all-incl-connected', the new path type must be set to 'none'. Otherwise it must be set either to 'none' or to a path type which matches the routing information destination filter. For example, a new path type of 'OSPF external type 1' can only be used if the routing information destination filter is set to OSPF.rw PathType (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.33 |
rtmRedistNwOspfTagValue of OSPF tag to set in routing information sent to destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is OSPF or 'all' or 'all-incl-connected'.rw OspfTag .1.2.826.0.1.1578918.5.61.1.1.2.1.34 |
rtmRedistOspfPropagateValue of OSPF propagate flag to set in routing information sent to destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is OSPF or 'all' or 'all-incl-connected'.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.35 |
rtmRedistAddCommunityFlag determining whether or not DC-RTM adds a BGP community value in routing information sent to the destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rwobsolete TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.36 |
rtmRedistNwCommunityValue to use for BGP community number in routing information sent to the destination if the add community flag is TRUE. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rwobsolete BgpCommunity .1.2.826.0.1.1578918.5.61.1.1.2.1.37 |
rtmRedistAddExtCommFlag determining whether or not DC-RTM adds a BGP extended community value in routing information sent to the destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rwobsolete TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.38 |
rtmRedistNwExtCommValue to use for BGP extended community number in routing information sent to destination if the add extended community flag is TRUE. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rwobsolete BgpExtendedCommunity .1.2.826.0.1.1578918.5.61.1.1.2.1.39 |
rtmRedistNwOriginValue to use for the BGP origin code in the routing information sent to the destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw BgpOriginCode .1.2.826.0.1.1578918.5.61.1.1.2.1.40 |
rtmRedistAddMedFlag determining whether or not DC-RTM adds a BGP Multi-Exit Discriminator value in routing information sent to the destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.41 |
rtmRedistNwMedValue to use for the BGP Multi-Exit Discriminator in the routing information sent to the destination of the add MED flag is TRUE. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.2.1.42 |
rtmRedistAddLocalPrefFlag determining whether or not DC-RTM adds a BGP Local Preference value in routing information sent to the destination. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.43 |
rtmRedistNwLocalPrefValue to use for the BGP Local Preference in the routing information sent to the destination if the add local pref flag is TRUE. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.2.1.44 |
rtmRedistSetListIdList identifier for the list of set actions to apply. The list of set actions are defined in the rtmRdstSetFieldTable, and are the group of entries in that table with the rtmRdstSetFieldListId field equal to the list identifier specified here. This field is only used if the redistribution flag is TRUE. A value of 0 indicates no list is specified.rw Unsigned32 .1.2.826.0.1.1578918.5.61.1.1.2.1.45 |
rtmRedistAddAsLimUpperFlag determining whether or not DC-RTM adds a BGP AS_PATHLIMIT attribute upper bound value to routing information sent to the destination. The destination will automatically add the AS number part of the attribute. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.46 |
rtmRedistNwAsLimUpperValue to use for the BGP AS_PATHLIMIT upper bound in the routing information sent to the destination if the rtmRedistAddAsLimUpper flag is TRUE. This field is only used if the redistribution flag is TRUE and the destination for the routing information is BGP or 'all' or 'all-incl-connected'.rw Unsigned32 .1.2.826.0.1.1578918.5.61.1.1.2.1.47 |
rtmRedistOspfVpnPeCeSupportFlag determining whether or not DC-RTM translates between OSPF routes and BGP routes in order to facilitate use of OSPF between provider edge (PE) routers and customer edge (CE) routers in a BGP/MPLS IP VPN. Setting this field to true enables translation between OSPF routes and BGP routes as described in RFC 4577 and draft-ietf-l3vpn-ospfv3-pece-07. This function should only be enabled for OSPF instances for customer VPNs on PE routers. It should be disabled for CE routers, and on PE routers it should be disabled for any OSPF instances for the provider backbone network. The translation between OSPF routes and BGP routes can be overridden by other fields in the redistribution table entry, including rtmRedistNwPathType, rtmRedistMetricConv, rtmRedistMetricValue, rtmRedistAddMed and rtmRedistNwMed. The translation between OSPF routes and BGP routes also depends on route translation performed by OSPF according to the OSPF Domain ID configuration. This field is only used if the redistribution flag is TRUE and the source or destination for the routing information include OSPF and BGP.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.2.1.48 |
rtmStaticRtTableThe table of DC-RTM static routes. SEQUENCE OF RtmStaticRtEntry .1.2.826.0.1.1578918.5.61.1.1.3 |
rtmStaticRtEntryInformation about static routes, containing next hop information or instruction to discard/reject matching packets. RtmStaticRtEntry .1.2.826.0.1.1578918.5.61.1.1.3.1 |
rtmStaticRtFteIndexThe HAF entity index identifying the instance of DC-RTM to which this static route entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.3.1.1 |
rtmStaticRtDestAddrTypeThe type of the address used as the destination internetwork address or subnet address. This object must be set to the same value as rtmEntityAddressFamily. InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.3.1.2 |
rtmStaticRtDestAddrDestination internetwork address or subnet address. The destination prefix length is applied to this value, and to a particular destination address, to determine whether the route applies to the particular address. If the prefix length is L, then applying the length to an address means taking the first L bits of the address. InetAddress .1.2.826.0.1.1578918.5.61.1.1.3.1.3 |
rtmStaticRtDestLenPrefix length (in bits) to apply to the destination internetwork address or subnet address, to obtain the set of addresses to which this route applies. If the prefix length is L, then applying the length to an address means taking the first L bits of the address. Integer32 .1.2.826.0.1.1578918.5.61.1.1.3.1.4 |
rtmStaticRtNextHopTypeThe type of the address used as the next-hop address for this route. This object must be set to the same value as rtmEntityAddressFamily, even if the rtmStaticRtNextHop object is set to all zeroes. InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.3.1.5 |
rtmStaticRtNextHopThe next-hop IP address, if any. If rtmStaticRtAction is 'forward', there may or may not be a next-hop IP address. A next-hop IP address is not required if an output interface index is specified (in other words, if rtmStaticRtIfIndex is non-zero). It is possible to supply a next-hop IP address, but to set the output interface index (rtmStaticRtIfIndex) to zero. In this case - the next hop is referred to as a loose next hop - the next-hop address does not need to be on a directly connected device - if DC-RTM cannot find a route to the specified next-hop address, it does not return the static route on the rtmRouteTable, it does not redistribute the static route to routing protocol managers, and it does not program the static route to a forwarding table (unless the forwarding table has registered to receive loose next hops) or to a partner that is querying route information (such as BGP or PIM). If rtmStaticRtAction is not 'forward', there is no next-hop IP address. If there is no next-hop IP address, the rtmStaticRtNextHop object is set to all zeroes. InetAddress .1.2.826.0.1.1578918.5.61.1.1.3.1.6 |
rtmStaticRtIfIndexThis field contains the network interface index of the interface configured to reach the next hop. If 0, then the rtmStaticRtOutIfIndex is determined by a subnet match of the configured next hop IP address. Otherwise, the rtmStaticRtOutIfIndex is equal to this value. Integer32 .1.2.826.0.1.1578918.5.61.1.1.3.1.7 |
rtmStaticRtOutIfIndexIf the action to perform is to forward the packet, this field contains the network interface index of the output network interface used to reach the next hop. It is not defined for other action values.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.3.1.8 |
rtmStaticRtRowStatusUsed to create and delete a DC-RTM static route.rw RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.9 |
rtmStaticRtAdminStatThe administrative state of the static route. The row status by itself does not indicate whether the static route definition is currently active. The row must be defined and the administrative status must be up. This enables a MIB agent to turn off a particular static route without deleting it from the table altogether.rw AdminStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.10 |
rtmStaticRtOverrideThe administrative distance for this route is by default taken to be the administrative distance configured in the DC-RTM entity table associated with the route's path type (rtmStaticRtPathType). If rtmStaticRtOverride is set to AMB_TRUE, this admin distance is overridden and we use the rtmStaticRtAdminDist instead. The lower the administrative distance for a given route, the more likely that route is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.11 |
rtmStaticRtAdminDistAdministrative distance for static route, if overriding the default administrative distance for this route given in the DC-RTM entity table. This field is not defined if overriding is not being performed. The lower the administrative distance for a given route, the more likely that route is to be used by DC-RTM as the active route for the given destination. See the DC-RTM Architecture Guide for more information about the use of administrative distances.rw AdminDistance (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.12 |
rtmStaticRtActionThe action to perform on receipt of a packet to the specified destination. If the action type is 'forward', one or both of the rtmStaticRtNextHop and rtmStaticRtIfIndex objects must be set to a non-zero value. If the action type is not 'forward', the rtmStaticRtNextHop and rtmStaticRtIfIndex objects must both be set to zero. The action type cannot be set to 'tunnel' for a static route. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE.rw RouteAction (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.13 |
rtmStaticRtFwdAddrTypeThe type of the address used as the forwarding address for this route. This object must be set to the same value as rtmEntityAddressFamily.rw InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.3.1.14 |
rtmStaticRtForwardingAddrForwarding address to advertise for this route. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE.rw InetAddress .1.2.826.0.1.1578918.5.61.1.1.3.1.15 |
rtmStaticRtPathTypeType of path associated with this route. PathType (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.16 |
rtmStaticRtUsePathCostUsed to enable/disable the usage of the path cost metric for this routerw TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.17 |
rtmStaticRtPathCostPath cost for this static route, if overriding the default setting. This field is not used if rtmStaticRtUsePathCost is set to AMB_FALSE. When deciding which path for a given route should be marked as active, the administrative distance is considered first. If multiple paths have the same administrative distance, the path with the lowest path cost is chosen as the active path. If multiple paths have the same path cost, one or more paths may be marked as active depending on the value of rtmEntityEqlCostOpt.rw Integer32 .1.2.826.0.1.1578918.5.61.1.1.3.1.18 |
rtmStaticRtUserDataUser data for this static route. This user data is passed to the QCRT_USER_STATIC_RT_EVENT user exit.rw OCTET STRING .1.2.826.0.1.1578918.5.61.1.1.3.1.19 |
rtmStaticRtLooseNextHopThis object indicates whether this static route contains a loose next hop (see rtmStaticRtNextHop for details).ro TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.20 |
rtmStaticRtBfdSupportThis object indicates whether DC-RTM should use BFD to check IP reachability to the static route's next hop. DC-RTM will only attempt to use BFD if rtmEntityBfdIndex is non-zero and the static route has rtmStaticRtAction set to 'forward' and rtmStaticRtNextHop set to a non-null IP address. This object should be set as follows. - Set to 'none' if BFD is not required for this static route. - Set to 'desired' if it is not known whether the next hop router supports BFD. DC-RTM will use BFD for reachability checking if BFD is able to contact the next hop router. If the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. - Set to 'required' if it is known that the next hop router supports BFD. DC-RTM will use BFD to check reachability of the next hop. If BFD is unable to contact the next hop router or if the BFD session fails, the static route will be removed from the forwarding table and will not be used for redistribution. The current state of the BFD session is indicated by rtmStaticRtBfdStatus.rw RtmBfdSupport .1.2.826.0.1.1578918.5.61.1.1.3.1.21 |
rtmStaticRtBfdStatusThe current BFD session state for this static route.ro BfdSessionStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.3.1.22 |
rtmMjTableThis table controls which entities DC-RTM should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row. SEQUENCE OF RtmMjEntry .1.2.826.0.1.1578918.5.61.1.1.4 |
rtmMjEntryRepresents a join for which DC-RTM is master. RtmMjEntry .1.2.826.0.1.1578918.5.61.1.1.4.1 |
rtmMjRtmFteIndexThe HAF entity index identifying the instance of DC-RTM to which this master join table entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.4.1.1 |
rtmMjSlaveFteIdThe HAF entity index identifying the instance of the slave entity to which this master join table entry applies. This index is used in the join user data, to enable FTI-specific code within System Manager to select a suitable slave entity instance. FteIndex .1.2.826.0.1.1578918.5.61.1.1.4.1.2 |
rtmMjIfTypeIdentifies the interface type for this master join.ro InterfaceType .1.2.826.0.1.1578918.5.61.1.1.4.1.3 |
rtmMjRowStatusThe row status for this DC-RTM master join table entry, used to create and destroy table entries.rw RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.4.1.4 |
rtmMjAdminStatusThe administrative status of this master join, used to start and stop the join.rw AdminStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.4.1.5 |
rtmMjOperStatusThe current operational status of this master join.ro OperStatus (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.4.1.6 |
rtmMjJoinStatusThe status of the master join.ro RtmMjStatus .1.2.826.0.1.1578918.5.61.1.1.4.1.7 |
rtmMjSlaveTypeThe type of entity which the slave side of this join should be. This value is used in the join user data, to enable FTI-specific code within System Manager to select a suitable slave entity instance. AriPrtnrType .1.2.826.0.1.1578918.5.61.1.1.4.1.8 |
rtmMjSafiSub-address family indicating the type of routes that can be queried on the join. This field is only relevant for joins to BGP or PIM. Allowed values are none, unicast and multicast. An example use is where unicast and multicast topologies are different. In this scenario the system requires separate RTM instances to hold the unicast and multicast routing tables. In this case, ARI queries from PIM relate to the multicast routing table, but ARI queries from BGP could be either for the unicast or multicast routing table. If only a single sub-address family need be supported then this can be left with the default value of none. The value of this field must not be changed while the row status of this MIB is AMB_ROW_STATUS_ACTIVE and the admin status is AMB_ADMIN_STATUS_UP.rw InetSubAddressType (DC-MASTER-TC) .1.2.826.0.1.1578918.5.61.1.1.4.1.9 |
rtmSjTableThis table contains information on joins for which DC-RTM entities are acting as slaves. Each row in this table represents one slave join in a particular DC-RTM entity. SEQUENCE OF RtmSjEntry .1.2.826.0.1.1578918.5.61.1.1.5 |
rtmSjEntryRepresents a join for which DC-RTM is slave. RtmSjEntry .1.2.826.0.1.1578918.5.61.1.1.5.1 |
rtmSjRtmFteIndexThe HAF entity index identifying the instance of DC-RTM to which this slave join table entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.5.1.1 |
rtmSjRtmRpmIndexInternal index used by DC-RTM for this RPM. Integer32 .1.2.826.0.1.1578918.5.61.1.1.5.1.2 |
rtmSjIfTypeIdentifies the interface type for this master join.ro InterfaceType .1.2.826.0.1.1578918.5.61.1.1.5.1.3 |
rtmSjMastFteTypeAdditional information about the type of master entity which created the join, where this is not uniquely defined by the interface type. For joins to Routing Protocol Managers using the Routing Protocol Input interface, this field contains the routing protocol type.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.5.1.4 |
rtmSjMastFteIdThe HAF entity index identifying the instance of the master entity to which this slave join table entry applies.ro FteIndex .1.2.826.0.1.1578918.5.61.1.1.5.1.5 |
rtmSjJoinStatusThe status of the slave join.ro RtmSjStatus .1.2.826.0.1.1578918.5.61.1.1.5.1.6 |
rtmRouteTableThis entity's IP Routing table. A route is present in this table if and only if it has been programmed to an Active Routes Interface consumer. This may be a consumer that asks for all route updates (such as a forwarding table), or it may be a consumer that queries information about specific routes (such as BGP or PIM). SEQUENCE OF RtmRouteEntry .1.2.826.0.1.1578918.5.61.1.1.6 |
rtmRouteEntryA particular route to a particular destina- tion, under a particular policy. RtmRouteEntry .1.2.826.0.1.1578918.5.61.1.1.6.1 |
rtmRouteFteIndexThe HAF entity index identifying the instance of DC-RTM to which this static route entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.6.1.1 |
rtmRouteStatusThe row status variable, used according to row installation and removal conventions.ro RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.6.1.2 |
rtmRouteDestTypeThe type of the address used as the destination IP address for this route. InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.6.1.3 |
rtmRouteDestDestination internetwork address or subnet address. The destination prefix length is applied to this value, and to a particular destination address, to determine whether the route applies to the particular address. If the prefix length is L, then applying the length to an address means taking the first L bits of the address. InetAddress .1.2.826.0.1.1578918.5.61.1.1.6.1.4 |
rtmRouteDestLenPrefix length (in bits) to apply to the rtmRouteDest object, to obtain the set of addresses to which this route applies. If the prefix length is L, then applying the length to an address means taking the first L bits of the address. Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.5 |
rtmRouteTosThe policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. +=====+=====+=====+=====+=====+=====+=====+=====+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +=====+=====+=====+=====+=====+=====+=====+=====+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30 RTM always returns a default value of 0 for this field. Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.6 |
rtmRouteNextHopTypeThe type of the address used as the next-hop address for this route. InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.6.1.7 |
rtmRouteNextHopOn remote routes, the address of the next system en route; Otherwise, zero. InetAddress .1.2.826.0.1.1578918.5.61.1.1.6.1.8 |
rtmRouteIfIndexThe ifIndex value which identifies the local interface through which the next hop of this route should be reached. Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.9 |
rtmRouteTypeThe type of route. local(3) refers to a route for which the destination is a local IP address or for which the next hop is the final destination. This includes routes to local IP addresses and routes to directly connected IP addresses or subnets. remote(4) refers to a route for which the next hop is not the final destination. reject (2) refers to a route which, if matched, discards the message as unreachable. This is used in some protocols as a means of correctly aggregating routes.ro RouteType .1.2.826.0.1.1578918.5.61.1.1.6.1.10 |
rtmRouteProtoThe routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.ro IANAipRouteProtocol (IANA-RTPROTO-MIB) .1.2.826.0.1.1578918.5.61.1.1.6.1.11 |
rtmRouteAgeThe number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of 'too old' can be implied except through knowledge of the routing protocol by which the route was learned. This age is only accurate for entries which are less that 49 days old.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.12 |
rtmRouteInfoA reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's rtmRouteProto value. RTM returns the following. - For OSPF, an integer representation of the OID which is required by RFC 2096. - For ISIS, an integer representation of the types of route to IP reachable addresses.ro RouteInfo .1.2.826.0.1.1578918.5.61.1.1.6.1.13 |
rtmRouteNextHopASThe Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing-protocol specified in the route's rtmRouteProto value. When this object is unknown or not relevant its value should be set to zero.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.14 |
rtmRouteMetric1The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRouteProto value. If this metric is not used, its value should be set to -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.15 |
rtmRouteMetric2An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRouteProto value. If this metric is not used, its value should be set to -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.16 |
rtmRouteMetric3An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRouteProto value. If this metric is not used, its value should be set to -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.17 |
rtmRouteMetric4An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRouteProto value. If this metric is not used, its value should be set to -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.18 |
rtmRouteMetric5An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRouteProto value. If this metric is not used, its value should be set to -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.19 |
rtmRouteConnectedIndicates whether the route destination is directly connected. A directly connected route can be reached without going through any IP routers. Route destinations that are local IP addresses are not considered to be directly connected. This field can only be true if rtmRouteType is set to 'local'.ro TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.6.1.20 |
rtmRouteXCIndexIndex into mplsXCTable that identifies which cross- connect entry is associated with this route entry by containing the mplsXCIndex of that cross-connect entry. This field is only valid for a VPN BGP route where rtmRouteType is remote and rtmRouteProto is bgp. Where valid, a zero value for this field indicates that a label stack is not associated with this route entry. This can be the case because the label bindings have not yet been established, or because some change in the agent has removed them.ro MplsIndexType .1.2.826.0.1.1578918.5.61.1.1.6.1.21 |
rtmRouteLocalDestIfIndexIf the route destination is a local IP address then this is the interface index that the local IP address is assigned to. Otherwise this field is zero.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.6.1.22 |
rtmRibTableRead-only copy of this entity's Routing Information Base. This is the complete set of routes known by DC-RTM and is a superset of the routes accessible through the rtmRouteTable (which accesses only the active routes from the Forwarding Information Base). SEQUENCE OF RtmRibEntry .1.2.826.0.1.1578918.5.61.1.1.7 |
rtmRibEntryA particular entry in the Routing Information Base. RtmRibEntry .1.2.826.0.1.1578918.5.61.1.1.7.1 |
rtmRibFteIndexThe HAF entity index identifying the instance of DC-RTM to which this RIB entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.7.1.1 |
rtmRibStatusThe row status variable, used according to row installation and removal conventions.ro RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.7.1.2 |
rtmRibDestTypeThe type of the address used as the destination IP address for this route. InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.7.1.3 |
rtmRibDestDestination internetwork address or subnet address. The destination prefix length is applied to this value, and to a particular destination address, to determine whether the route applies to the particular address. If the prefix length is L, then applying the length to an address means taking the first L bits of the address. InetAddress .1.2.826.0.1.1578918.5.61.1.1.7.1.4 |
rtmRibDestLenPrefix length (in bits) to apply to the rtmRibDest object, to obtain the set of addresses to which this route applies. If the prefix length is L, then applying the length to an address means taking the first L bits of the address. Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.5 |
rtmRibTosThe policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. +=====+=====+=====+=====+=====+=====+=====+=====+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +=====+=====+=====+=====+=====+=====+=====+=====+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30 RTM always returns a default value of 0 for this field. Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.6 |
rtmRibNextHopTypeThe type of the address used as the next-hop address for this route. InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.1.7.1.7 |
rtmRibNextHopOn remote routes, the address of the next system en route; Otherwise, zero. InetAddress .1.2.826.0.1.1578918.5.61.1.1.7.1.8 |
rtmRibIfIndexThe ifIndex value which identifies the local interface through which the next hop of this route should be reached. Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.9 |
rtmRibTypeThe type of route. local(3) refers to a route for which the destination is a local IP address or for which the next hop is the final destination. This includes routes to local IP addresses and routes to directly connected IP addresses or subnets. remote(4) refers to a route for which the next hop is not the final destination. reject (2) refers to a route which, if matched, discards the message as unreachable. This is used in some protocols as a means of correctly aggregating routes.ro RouteType .1.2.826.0.1.1578918.5.61.1.1.7.1.10 |
rtmRibProtoThe routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols. IANAipRouteProtocol (IANA-RTPROTO-MIB) .1.2.826.0.1.1578918.5.61.1.1.7.1.11 |
rtmRibAgeThe number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of 'too old' can be implied except through knowledge of the routing protocol by which the route was learned. This age is only accurate for entries which are less that 49 days old.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.12 |
rtmRibInfoA reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's rtmRibProto value. RTM returns the following. - For OSPF, an integer representation of the OID which is required by RFC 2096. - For ISIS, an integer representation of the types of route to IP reachable addresses.ro RouteInfo .1.2.826.0.1.1578918.5.61.1.1.7.1.13 |
rtmRibNextHopASThe Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing-protocol specified in the route's rtmRibProto value. When this object is unknown or not relevant its value is returned as zero.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.14 |
rtmRibMetric1The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRibProto value. If this metric is not used, its value is returned as -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.15 |
rtmRibMetric2An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRibProto value. If this metric is not used, its value is returned as -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.16 |
rtmRibMetric3An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRibProto value. If this metric is not used, its value is returned as -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.17 |
rtmRibMetric4An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRibProto value. If this metric is not used, its value is returned as -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.18 |
rtmRibMetric5An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's rtmRibProto value. If this metric is not used, its value is returned as -1.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.19 |
rtmRibFibRouteFlag indicating whether or not this route has been programmed either to a forwarding table, or to a partner that queries route information (such as BGP or PIM). If there is no forwarding table and no partners are querying route information then this object is set to 'false' for every route. If this route has rtmRibLooseNextHop set to 'true', it is possible that RTM knows of more than one explicit next hop to the loose next hop address. If so, RTM programs these explicit next hops separately to a forwarding table (unless the forwarding table registers to receive loose next hops) and to a partner that queries route information; in this case the rtmRibFibRoute flag is set to 'true' if and only if one or more of these explicit next hops has been programmed.ro TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.7.1.20 |
rtmRibRpmIndexThe HAF entity index for the RPM that supplied this route, or zero for static routes or automatically configured routes. This is used to distinguish routes in the system where multiple copies of a given protocol (for example BGP) are providing routes to DC-RTM. Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.21 |
rtmRibConnectedIndicates whether the route destination is directly connected. A directly connected route can be reached without going through any IP routers. Route destinations that are local IP addresses are not considered to be directly connected. This field can only be true if rtmRibType is set to 'local'.ro TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.7.1.22 |
rtmRibLooseNextHopThis flag indicates whether DC-RTM considers that the next-hop address for this route is a loose next hop. If DC-RTM sets this object to 'true' then - it must also have set rtmRibType to 'remote' - the next-hop address (rtmRibNextHop) may not be on a directly connected device - if DC-RTM cannot find a route to the next-hop address, it does not return the route on the rtmRouteTable, it does not redistribute the route to routing protocol managers, and it does not program the route to a forwarding table (unless the forwarding table has registered to receive loose next hops) or to a partner that is querying route information (such as BGP or PIM).ro TruthValue (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.7.1.23 |
rtmRibLocalDestIfIndexIf the route destination is a local IP address then this is the interface index that the local IP address is assigned to. Otherwise this field is zero.ro Integer32 .1.2.826.0.1.1578918.5.61.1.1.7.1.24 |
rtmRdstSetFieldTableThis table defines route attributes which are to be set by redistribution filters. A list of set actions is made up of one or more entries in this table with the same list_id. Actions in a list are applied in increasing set_number order. Each list may be referenced by 0, 1 or more redistribution entries. Only actions which are active at the point where the redistribution entry is being evaluated (i.e. at the point where the route is actually being redistributed) are applied. Also, only those set actions which are relevant to the route being redistributed are applied, so BGP attributes will not be set for a route being redistributed to OSPF. SEQUENCE OF RtmRdstSetFieldEntry .1.2.826.0.1.1578918.5.61.1.1.8 |
rtmRdstSetFieldEntryA particular entry in the Redistribution Set Field table. RtmRdstSetFieldEntry .1.2.826.0.1.1578918.5.61.1.1.8.1 |
rtmRdstSetFieldFteIndexThe HAF entity index identifying the instance of DC-RTM to which this set field entry applies. FteIndex .1.2.826.0.1.1578918.5.61.1.1.8.1.1 |
rtmRdstSetFieldListIdThe index of the list of set actions which this action belongs to. It is this identifier which is referenced by the redistribution table entry. A value of 0 is not permitted. Unsigned32 .1.2.826.0.1.1578918.5.61.1.1.8.1.2 |
rtmRdstSetFieldNumberIdentifies this set field entry's position in the list of set field entries with the same list identifier. Unsigned32 .1.2.826.0.1.1578918.5.61.1.1.8.1.3 |
rtmRdstSetFieldRowStatusUsed to create and delete a DC-RTM set field table entry.rw RowStatus (SNMPv2-TC) .1.2.826.0.1.1578918.5.61.1.1.8.1.4 |
rtmRdstSetFieldTypeThe type of field set by this set field entry.rw RdstSetFieldType .1.2.826.0.1.1578918.5.61.1.1.8.1.5 |
rtmRdstSetFieldValueThe value set by this set field entry.rw OCTET STRING .1.2.826.0.1.1578918.5.61.1.1.8.1.6 |
rtmTrap OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.2 |
rtmTraps OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.2.0 |
rtmOperStateChangeDC-RTM generates this trap when the operational state of RTM enters 'up', 'down' or 'act_failed' state. NOTIFICATION-TYPE .1.2.826.0.1.1578918.5.61.1.2.0.1 |
rtmStaticRouteChangeDC-RTM generates this trap when a static route becomes eligible or ineligible for installation in the FIB. NOTIFICATION-TYPE .1.2.826.0.1.1578918.5.61.1.2.0.2 |
rtmPathActivityChangeDC-RTM generates this trap when a path becomes active or inactive. NOTIFICATION-TYPE .1.2.826.0.1.1578918.5.61.1.2.0.3 |
rtmTrapControl OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.2.1 |
rtmStaticRtTrapReasonEvent that caused the trap to be made. Used by the rtmStaticRouteChange trap.ro Enumeration .1.2.826.0.1.1578918.5.61.1.2.1.1 |
rtmPathTrapReasonEvent that caused the trap to be made. Used by the rtmPathActivityChange trap.ro Enumeration .1.2.826.0.1.1578918.5.61.1.2.1.2 |
rtmTrapEntityFteIndexVersion of rtmEntityFteIndex used for traps.ro FteIndex .1.2.826.0.1.1578918.5.61.1.2.1.3 |
rtmTrapStaticRtDestAddrTypeVersion of rtmStaticRtDestAddrType used for traps.ro InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.2.1.4 |
rtmTrapStaticRtDestAddrVersion of rtmStaticRtDestAddr used for traps.ro InetAddress .1.2.826.0.1.1578918.5.61.1.2.1.5 |
rtmTrapStaticRtDestLenVersion of rtmStaticRtDestLen used for traps.ro Integer32 .1.2.826.0.1.1578918.5.61.1.2.1.6 |
rtmTrapStaticRtNextHopTypeVersion of rtmStaticRtNextHopType used for traps.ro InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.2.1.7 |
rtmTrapStaticRtNextHopVersion of rtmStaticRtNextHop used for traps.ro InetAddress .1.2.826.0.1.1578918.5.61.1.2.1.8 |
rtmTrapStaticRtIfIndexVersion of rtmStaticRtIfIndex used for traps.ro Integer32 .1.2.826.0.1.1578918.5.61.1.2.1.9 |
rtmTrapRibDestTypeVersion of rtmRibDestType used for traps.ro InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.2.1.10 |
rtmTrapRibDestVersion of rtmRibDest used for traps.ro InetAddress .1.2.826.0.1.1578918.5.61.1.2.1.11 |
rtmTrapRibDestLenVersion of rtmRibDestLen used for traps.ro Integer32 .1.2.826.0.1.1578918.5.61.1.2.1.12 |
rtmTrapRibTosVersion of rtmRibTos used for traps.ro Integer32 .1.2.826.0.1.1578918.5.61.1.2.1.13 |
rtmTrapRibNextHopTypeVersion of rtmRibNextHopType used for traps.ro InetAddressType (INET-ADDRESS-MIB) .1.2.826.0.1.1578918.5.61.1.2.1.14 |
rtmTrapRibNextHopVersion of rtmRibNextHop used for traps.ro InetAddress .1.2.826.0.1.1578918.5.61.1.2.1.15 |
rtmTrapRibIfIndexVersion of rtmRibIfIndex used for traps.ro Integer32 .1.2.826.0.1.1578918.5.61.1.2.1.16 |
rtmTrapRibProtoVersion of rtmRibProto used for traps.ro IANAipRouteProtocol (IANA-RTPROTO-MIB) .1.2.826.0.1.1578918.5.61.1.2.1.17 |
rtmTrapRibRpmIndexVersion of rtmRibRpmIndex used for traps.ro Integer32 .1.2.826.0.1.1578918.5.61.1.2.1.18 |
rtmConformance OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.3 |
rtmCompliances OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.3.1 |
rtmComplianceThe compliance statement for the DC-RTM module. Unknown .1.2.826.0.1.1578918.5.61.1.3.1.1 |
rtmGroups OBJECT IDENTIFIER .1.2.826.0.1.1578918.5.61.1.3.2 |
rtmEntityMandatoryGroupMandatory objects for the rtmEntityTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.1 |
rtmEntityGroupOptional objects for rtmEntityTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.2 |
rtmRedistMandatoryGroupMandatory objects for rtmRedistTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.3 |
rtmRedistGroupOptional objects for rtmRedistTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.4 |
rtmStaticRtMandatoryGroupMandatory objects for rtmStaticRtTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.5 |
rtmStaticRtGroupOptional objects for rtmStaticRtTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.6 |
rtmMjMandatoryGroupMandatory objects for rtmMjTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.7 |
rtmMjGroupOptional objects for rtmMjTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.8 |
rtmSjMandatoryGroupMandatory objects for rtmSjTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.9 |
rtmSjGroupOptional objects for rtmSjTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.10 |
rtmRouteGroupOptional objects for rtmRouteTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.11 |
rtmRibGroupOptional objects for rtmRibTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.12 |
rtmObsoleteGroupThis group contains obsolete objects.obsolete Unknown .1.2.826.0.1.1578918.5.61.1.3.2.13 |
rtmRdstSetFieldMandatoryGroupMandatory objects for rtmRdstSetFieldTable. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.14 |
rtmNotificationObjectGroupThe objects used to record notification parameters. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.15 |
rtmNotificationEventGroupA grouping of RTM trap events, as specified in NOTIFICATION-TYPE constructs. Unknown .1.2.826.0.1.1578918.5.61.1.3.2.16 |