CISCO-ROUTE-POLICIES-MIB
The CISCO-ROUTE-POLICIES-MIB defines the OID namespace for Cisco routing policies, enabling the differentiation of multiple routing table entries that share identical destination prefixes and next-hops but utilize distinct egress interfaces. This module provides the necessary policy identifiers for standardizing route selection logic within the IP-FORWARD-MIB and MPLS-L3VPN-STD-MIB, specifically supporting scenarios where multiple paths exist to the same destination via different interfaces or zones.
Imported Objects
Objects
6 total| Object Name |
|---|
ciscoRoutePoliciesMIBThis module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This module defines only this 'policy' OID
space and doesn't define any other object.
As an example, these OIDs are required by at least the
following MIB objects: inetCidrRoutePolicy
( IP-FORWARD-MIB, RFC4292 ) and
mplsL3VpnVrfRteInetCidrPolicy ( MPLS-L3VPN-STD-MIB
RCS4382). Both of these objects are defined as OBJECT
IDENTIFIERs without any defined semantics, to
differentiate between multiple entries to the same
destination in the tables inetCidrRoutePolicyTable and
mplsL3VpnVrfRteInetCidrTable. These two objects
utilise a generalised notion of 'policy' defined in
this module.
The table inetCidrRouteTable of IP-FORWARD-MIB may list
multiple paths pointing out of (either):
* different interfaces with the same next-hop
ipv6 route 2003::/64 interface gig0/0 2222::1
ipv6 route 2003::/64 interface gig0/1 2222::1
* different interfaces with no next-hop
ipv6 route 2003::/64 interface gig0/0
ipv6 route 2003::/64 interface gig0/1
2003::/64 and 2222::1 represent an IPv6 route-prefix
and IPv6 next-hop respectively.
If these interfaces were in different zones, then the
'InetAddressIPv6z' type next-hop could distinguish
them. If they are in the same zone, then the two
interfaces refer to the same link.
The indices of inetCidrRouteTable are:
inetCidrRouteDestType
inetCidrRouteDest
inetCidrRoutePfxLen
inetCidrRoutePolicy
inetCidrRouteNextHopType
inetCidrRouteNextHop
The inetCidrRoutePolicy object, when instantiated with a
value from crpPolicyIfIndex, allows us to distinguish
the routing table entries mentioned in the examples
above.
REFERENCE
[1] IP-FORWARD-MIB (RFC4292)
[2] MPLS-L3VPN-STD-MIB (RFC4382)
[3] ifIndex, IF-MIB
[4] RFC 4291 IP Version 6 Addressing Architecture,
Section 2.2, Text Representation of Addresses. MODULE-IDENTITY .1.3.6.1.4.1.9.9.578 |
ciscoRoutePoliciesMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.578.0 |
ciscoRoutePoliciesMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.578.1 |
crpPoliciesA subtree to define OIDs so that various routing
policies used by Cisco routers can be expressed.
Such OIDs may serve as additional indices, e.g., as the
values of inetCidrRoutePolicy in inetCidrRouteTable,
to delineate between multiple routes to the same
destination. OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.578.1.1 |
crpPolicyIfIndexThis OID specifies a set of policies, one for each
ifIndex value. Specifically, the OID value of
crpPolicyIfIndex.i is defined such that each
inetCidrRouteTable entry for which the instance of
inetCidrRoutePolicy has this value, is associated with
ifIndex=i, and thereby is distinct for any
inetCidrRouteTable entry associated with
ifIndex=j. Note that the value of inetCidrRoutePolicy
for the latter would be crpPolicyIfIndex.j.
This set of policies is appropriate only if an ifIndex
value is sufficient to distinguish between routes. OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.578.1.1.1 |
ciscoRoutePoliciesMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.578.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.