All MIBs › RC-VRF-MIB
Organization: Nortel Networks
Last Updated: 2008-09-09
Category: Nortel Enterprise Data
Description:
Manages VRF instance configuration, interface assignment, and routing table separation on Nortel Ethernet Routing Switch.
Imported Objects
From IF-MIB
| InterfaceIndex |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From RAPID-CITY
| EnableValue | |
| IdList | |
| rcVrf | OBJECT-IDENTITY |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| TimeTicks | |
| Unsigned32 | |
| mib-2 |
From SNMPv2-TC
| DisplayString | |
| RowStatus | |
| TEXTUAL-CONVENTION | |
| TruthValue |
What Is RC-VRF-MIB?
RC-VRF-MIB is a Nortel (Ethernet Routing Switch / Passport 'Rapid City' family) MIB for managing Virtual Router and VRF (Virtual Routing and Forwarding) instances, including VRF/VPN table sizing, interface assignment, and route separation. It exposes configuration objects for VRF creation and identification, import/export route target lists for VPN route leaking, and service label allocation options, along with notification objects for VRF-related events. Its monitoring value is centered on VPN/VRF configuration integrity and capacity: administrators track rcVrfIpVpnTableSize against the number of configured VRFs to watch for capacity exhaustion, and monitor rcVrfIpVpnStatus/rcVrfIpVpnRowStatus to confirm a VRF is active and correctly provisioned. It complements standard IP routing and MPLS VPN MIBs since VRFs are used to segregate routing tables for multi-tenant or MPLS L3VPN services. It is deployed on Nortel/Avaya Ethernet Routing Switches acting as provider-edge or virtual-router-capable devices in segmented enterprise or carrier networks, and administrators typically load RC-VRF-MIB into a MIB Browser to review VRF table sizing and route target configuration before compiling it into their NMS.
IPNetwork Monitor allows you to monitor SNMP objects defined in RC-VRF-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
What Can Be Monitored
- configured VRF count vs table size limit
- VRF operational/row status
- import/export route target lists
- service label allocation option
- VRF-related notifications
Supported Devices
- Nortel/Avaya Ethernet Routing Switch, Passport/Rapid-City family (VRF/virtual-router configuration)
Monitoring Examples
An operator would compare rcVrfIpVpnTableSize against the count of rows in rcVrfIpVpnTable to see how close the switch is to its maximum supported VRF count. Checking rcVrfIpVpnStatus and rcVrfIpVpnRowStatus per entry confirms whether a given VRF (indexed by rcVrfIpVpnVrfId) is active, and inspecting rcVrfIpVpnImportRTList/rcVrfIpVpnExportRTList reveals which route targets are being imported or exported, useful for diagnosing why routes aren't leaking between VRFs as expected. rcVrfNotifications would alert an operator to VRF state changes without needing to poll continuously.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| rcVrfMib | 1.3.6.1.4.1.2272.1.203.1 | The MIB module is the definition of the managed objects for the Virtual Router. | ||
| rcVrfNotifications | 1.3.6.1.4.1.2272.1.203.1.0 | |||
| rcVrfObjects | 1.3.6.1.4.1.2272.1.203.1.1 | |||
| rcVrfConfig | 1.3.6.1.4.1.2272.1.203.1.1.1 | |||
| rcVrfConfigScalars | 1.3.6.1.4.1.2272.1.203.1.1.1.1 | |||
| OID rcVrfConfigNextAvailableVrfId | 1.3.6.1.4.1.2272.1.203.1.1.1.1.1 | VrfIdentifier | read-only | The next available Virtual Router Id (index). This object provides a hint for the rcVrfId value to use when administratively creating a new rcVrfConfigEntry. A GET of this object returns the next available rcVrfId value to be used to create an entry in the associated rcVrfConfigTable; or zero, if no valid rcVrfId value is available. A value of zero(0) indicates that it is not possible to create a new rcVrfConfigEntry. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously. Unless specified otherwise by its MAX-ACCESS and DESCRIPTION clauses, an object of this type is read-only, and a SET of such an object returns a notWritable error. |
| rcVrfConfigTable | 1.3.6.1.4.1.2272.1.203.1.1.1.2 | not-accessible | This table is for creating the new Virtual Routers. | |
| rcVrfConfigEntry | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1 | not-accessible | The entries in this table can be added/deleted using the rcVrfRowStatus. | |
| OID rcVrfId | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.1 | VrfIdentifier | not-accessible | The unique id of this virtual router instance. A Virtual Router cannot not be created with rcVrfId = 0. VRFID 0 is reserved for the Administrative VRF. |
| ROW rcVrfRowStatus | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.2 | RowStatus | read-create | The status column has three defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. |
| STR rcVrfName | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.3 | DisplayString | read-write | The Name of the Virtual Router. |
| STR rcVrfContextName | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.4 | SnmpAdminString | read-create | The SNMPv2 Community String or SNMPv3 contextName denotes the VRF 'context' and is used to logically separate the MIB module management. |
| T/F rcVrfTrapEnable | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.5 | TruthValue | read-create | This objects is used to enable the generation of the VrfUp and VrfDown traps. true(1) - VRF Traps Enabled false(2) - VRF Traps Disabled |
| U32 rcVrfMaxRoutes | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.6 | Unsigned32 | read-create | This object specifies the maximum number of routes that this VRF can support. The default value is 10000. |
| INT rcVrfAdminStatus | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.7 | INTEGER | read-create | The administrative state of the Virtual Router. |
| VPN rcVrfVpnId | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.8 | VPNId | read-create | The Virtual Private Network Identifier of the Virtual Router. |
| VRF rcVrfRpTrigger | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.9 | VrfRpTriggerBitCode | read-create | This object represents Routing Protocol (RP) Triggers on a Virtual Router and it meant to be used to initiate or shutdown routing protocols on a VRF. Multiple RPs can be acted on simultaneously. Also, individual RPs can be brought up in steps, which should not affect the RPs that were running. The BITS represent an Action-code that specifies what action is to be performed for the RPs. The actions are: initiate(1) or shutdown(0). The running status of an RP shall be available in the VRF stats table's rcVrfRpStatus, which has a similar format, but represents the status. Bits 0-3 may be specified in any combination. Individual routing protocols may be enabled and disabled independently. Protocols are enabled by setting the respective BIT and are disabled by resetting the BIT. So, for example, to enable RIP and BGP protocols the rcVrfRpTrigger bits 0 and 2 need to be set, and as encoded as 10100000. All zeros should be interpreted as all protocols disable. |
| T/F rcVrfMaxRoutesTrapEnable | 1.3.6.1.4.1.2272.1.203.1.1.1.2.1.10 | TruthValue | read-create | This objects is used to enable the generation of the VRF Max Routes Exceeded traps. true(1) - VRF Max Routes Exceeded Traps Enabled false(2) - VRF Max Routes Exceeded Traps Disabled |
| rcVrfStat | 1.3.6.1.4.1.2272.1.203.1.1.2 | |||
| rcVrfStatScalars | 1.3.6.1.4.1.2272.1.203.1.1.2.1 | |||
| U32 rcVrfConfiguredVRFs | 1.3.6.1.4.1.2272.1.203.1.1.2.1.1 | Unsigned32 | read-only | The number of VRFs configured on this network element. |
| U32 rcVrfActiveVRFs | 1.3.6.1.4.1.2272.1.203.1.1.2.1.2 | Unsigned32 | read-only | The number of VRFs that are active on the network element. These are VRFs for which the rcVrfStatOperStatus = up(1) |
| rcVrfStatTable | 1.3.6.1.4.1.2272.1.203.1.1.2.2 | not-accessible | This table contains statistics for the Virtual Router. | |
| rcVrfStatEntry | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1 | not-accessible | Entries in this table are per rcVrfId. | |
| U32 rcVrfStatRouteEntries | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.1 | Unsigned32 | read-only | Total number of routes for this VRF. |
| U32 rcVrfStatFIBEntries | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.2 | Unsigned32 | read-only | Total number of FIB Entries for this VRF. |
| TIK rcVrfStatUpTime | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.3 | TimeTicks | read-only | The time in (in hundredths of a second) since this VRF entry has been operational. |
| INT rcVrfOperStatus | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.4 | INTEGER | read-only | The operational status of the Virtual Router. |
| VRF rcVrfRpStatus | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.5 | VrfRpTriggerBitCode | read-only | This object represents the status of Routing Protocols on this VRF corresponding to the list of RP specified in rcVrfRpTrigger. The BITS represent an Action-code that specifies the status of the RPs. The status are: initiated (1) or shutdown (0). Initiated status is indicated when the respective BIT value is 1 and indicates shutdown when the respective BIT value is 0. Bits 0-3 may appear in any combination to indicate that RPs may be enabled and disabled independently or that multiple RP are acted on simultaneously. |
| IPt rcVrfRouterAddressType | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.6 | InetAddressType | read-only | Router Address Type of this VRF. |
| IP rcVrfRouterAddress | 1.3.6.1.4.1.2272.1.203.1.1.2.2.1.7 | InetAddress | read-only | Router Address of this VRF. It is derived from one of the interfaces. If loopback interface is present, the loopback interface address can be used. However, loopback interface is optional. |
| I32 rcVrfIpVpnTableSize | 1.3.6.1.4.1.2272.1.203.1.1.3 | Integer32 | read-only | Size of Vrf IpVpn Table |
| rcVrfIpVpnTable | 1.3.6.1.4.1.2272.1.203.1.1.4 | not-accessible | Table required to configure vpn under ip. | |
| rcVrfIpVpnTableEntry | 1.3.6.1.4.1.2272.1.203.1.1.4.1 | not-accessible | Entries in this table are per rcVrfId. | |
| OID rcVrfIpVpnVrfId | 1.3.6.1.4.1.2272.1.203.1.1.4.1.1 | VrfIdentifier | not-accessible | The VrfId serves as the Index for the rcIpVpnVrfTable and also for the rcIpVpnRouteDistinguisherTable. It allows to connect to the vrf table to obtain other attributes like the vrf name, rcVrfMaxRoutesTrapEnable etc. |
| ENA rcVrfIpVpnStatus | 1.3.6.1.4.1.2272.1.203.1.1.4.1.2 | EnableValue | read-create | The status of IpVpn. |
| IDL rcVrfIpVpnImportRTList | 1.3.6.1.4.1.2272.1.203.1.1.4.1.3 | IdList | read-create | The Import RT list is a list of all the route-targets attached to a particular vrf behaving in the import mode. |
| IDL rcVrfIpVpnExportRTList | 1.3.6.1.4.1.2272.1.203.1.1.4.1.4 | IdList | read-create | The Export RT list is a list of all the route-targets attached to a particular vrf in the export mode. |
| INT rcVrfIpVpnSvcLblAllocOpt | 1.3.6.1.4.1.2272.1.203.1.1.4.1.5 | INTEGER | read-create | The service label allocation option for the ipvpn |
| ROW rcVrfIpVpnRowStatus | 1.3.6.1.4.1.2272.1.203.1.1.4.1.6 | RowStatus | read-create | RowStatus for the Vpn Entry. |
| rcVrfNotificationObjects | 1.3.6.1.4.1.2272.1.203.1.2 |
RFC description
Virtual Routing and Forwarding (VRF) MIB; manages VRF configuration, routing tables, and forwarding instances.
Start monitoring Nortel/Avaya Ethernet Routing Switch, Passport/Rapid-City family (VRF/virtual-router configuration) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.