RC-VRF-MIB
The MIB module is the definition of the managed objects for the Virtual Router.
Main OID:
rcVrfMib.1.3.6.1.4.1.2272.1.203.1
41
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
41 total| Object Name |
|---|
rcVrfMibThe MIB module is the definition of the managed
objects for the Virtual Router. MODULE-IDENTITY .1.3.6.1.4.1.2272.1.203.1 |
rcVrfNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.0 |
rcVrfObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.1 |
rcVrfConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.1.1 |
rcVrfConfigScalars OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.1.1.1 |
rcVrfConfigNextAvailableVrfIdThe 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.ro VrfIdentifier .1.3.6.1.4.1.2272.1.203.1.1.1.1.1 |
rcVrfConfigTableThis table is for creating the new Virtual Routers. SEQUENCE OF RcVrfConfigEntry .1.3.6.1.4.1.2272.1.203.1.1.1.2 |
rcVrfConfigEntryThe entries in this table can be added/deleted
using the rcVrfRowStatus. RcVrfConfigEntry .1.3.6.1.4.1.2272.1.203.1.1.1.2.1 |
rcVrfIdThe 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. VrfIdentifier .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.1 |
rcVrfRowStatusThe 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.2 |
rcVrfNameThe Name of the Virtual Router.rw DisplayString .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.3 |
rcVrfContextNameThe SNMPv2 Community String or SNMPv3 contextName
denotes the VRF 'context' and is used to logically
separate the MIB module management.rw SnmpAdminString .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.4 |
rcVrfTrapEnableThis objects is used to enable the generation
of the VrfUp and VrfDown traps.
true(1) - VRF Traps Enabled
false(2) - VRF Traps Disabledrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.5 |
rcVrfMaxRoutesThis object specifies the maximum number of routes that
this VRF can support. The default value is 10000.rw Unsigned32 .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.6 |
rcVrfAdminStatusThe administrative state of the Virtual Router.rw Enumeration .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.7 |
rcVrfVpnIdThe Virtual Private Network Identifier of the Virtual
Router.rw VPNId .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.8 |
rcVrfRpTriggerThis 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.rw VrfRpTriggerBitCode .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.9 |
rcVrfMaxRoutesTrapEnableThis 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 Disabledrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2272.1.203.1.1.1.2.1.10 |
rcVrfStat OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.1.2 |
rcVrfStatScalars OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.1.2.1 |
rcVrfConfiguredVRFsThe number of VRFs configured on this network element.ro Unsigned32 .1.3.6.1.4.1.2272.1.203.1.1.2.1.1 |
rcVrfActiveVRFsThe number of VRFs that are active on the network element.
These are VRFs for which the
rcVrfStatOperStatus = up(1)ro Unsigned32 .1.3.6.1.4.1.2272.1.203.1.1.2.1.2 |
rcVrfStatTableThis table contains statistics for the Virtual Router. SEQUENCE OF RcVrfStatEntry .1.3.6.1.4.1.2272.1.203.1.1.2.2 |
rcVrfStatEntryEntries in this table are per rcVrfId. RcVrfStatEntry .1.3.6.1.4.1.2272.1.203.1.1.2.2.1 |
rcVrfStatRouteEntriesTotal number of routes for this VRF.ro Unsigned32 .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.1 |
rcVrfStatFIBEntriesTotal number of FIB Entries for this VRF.ro Unsigned32 .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.2 |
rcVrfStatUpTimeThe time in (in hundredths of a second) since
this VRF entry has been operational.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.3 |
rcVrfOperStatusThe operational status of the Virtual Router.ro Enumeration .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.4 |
rcVrfRpStatusThis 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.ro VrfRpTriggerBitCode .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.5 |
rcVrfRouterAddressTypeRouter Address Type of this VRF.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.6 |
rcVrfRouterAddressRouter 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.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.2272.1.203.1.1.2.2.1.7 |
rcVrfIpVpnTableSizeSize of Vrf IpVpn Tablero Integer32 .1.3.6.1.4.1.2272.1.203.1.1.3 |
rcVrfIpVpnTableTable required to configure vpn under ip. SEQUENCE OF RcVrfIpVpnTableEntry .1.3.6.1.4.1.2272.1.203.1.1.4 |
rcVrfIpVpnTableEntryEntries in this table are per rcVrfId. RcVrfIpVpnTableEntry .1.3.6.1.4.1.2272.1.203.1.1.4.1 |
rcVrfIpVpnVrfIdThe 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. VrfIdentifier .1.3.6.1.4.1.2272.1.203.1.1.4.1.1 |
rcVrfIpVpnStatusThe status of IpVpn.rw EnableValue (RAPID-CITY) .1.3.6.1.4.1.2272.1.203.1.1.4.1.2 |
rcVrfIpVpnImportRTListThe Import RT list is a list of all the route-targets
attached to a particular vrf behaving in the import mode.rw IdList (RAPID-CITY) .1.3.6.1.4.1.2272.1.203.1.1.4.1.3 |
rcVrfIpVpnExportRTListThe Export RT list is a list of all the route-targets
attached to a particular vrf in the export mode.rw IdList (RAPID-CITY) .1.3.6.1.4.1.2272.1.203.1.1.4.1.4 |
rcVrfIpVpnSvcLblAllocOptThe service label allocation option for the ipvpnrw Enumeration .1.3.6.1.4.1.2272.1.203.1.1.4.1.5 |
rcVrfIpVpnRowStatusRowStatus for the Vpn Entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2272.1.203.1.1.4.1.6 |
rcVrfNotificationObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2272.1.203.1.2 |
More MIBs from Rapidcity
Browse all RapidcityMIBs →RAPID-CITY
The RAPID-CITY MIB module facilitates SNMP-based monitoring and management of Accelar product family hardware, specifically tracking performance metrics such as throughput, connection states, and resource utilization for traffic acceleration appliances.
6502 objects→
RAPID-CITY-VSP
The RAPID-CITY-VSP MIB provides enterprise-level monitoring and management capabilities for the Accelar product family, enabling the collection of performance metrics, interface statistics, and system health data for Accelar network appliances. This module facilitates the tracking of device availability, traffic throughput, and operational states specific to Accelar's hardware and software implementations.
5404 objects→
RC-CFM-MIB
The RC-CFM-MIB module enables monitoring of Ethernet Connectivity Fault Management (CFM) state variables, including Maintenance Domain, Maintenance Association, and Maintenance Endpoint operational statuses, to detect and isolate Layer 2 network faults. It provides specific counters and gauges for CFM message transmission, reception, and error conditions to facilitate rapid diagnosis of link integrity and service continuity issues.
572 objects→
SWL2MGMT-MIB
SNMP MIB module
286 objects→
RC-IP-POLICY-MIB
The RC-IP-POLICY-MIB module provides SNMP access to configure and monitor IP traffic filtering rules, policy routing decisions, and associated session statistics on Accelar network appliances. It enables administrators to track policy hit counts, match conditions, and enforcement states for granular control over packet forwarding and security policies.
220 objects→
RC-2K-MIB
SNMP MIB module
218 objects→