RCV3

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RCV3

Category: Generic / Unclassified

Description: Defines revision and version control objects for network management module version tracking.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is RCV3?

RCV3 is a RedCreek Communications enterprise MIB (part of the 'redCreek' enterprise OID branch) used for basic version and identity tracking on RedCreek's network/VPN routing products, alongside fundamental interface and IP routing configuration. It exposes boot ROM, firmware, and hardware version/ID objects, a distinguished name/host name for the device, an interface table with per-interface IP address, mask, and MAC address, and an IP routing table. Its main relevance to hardware/software status monitoring is software version tracking -- confirming rc3FirmwareVer/rc3BootRomVer/rc3HardwareVer match the expected release across a fleet of devices -- plus basic interface/route configuration visibility, though it lacks environmental sensors like temperature or fan-speed objects. As a small, self-contained enterprise MIB it has no notable dependency on external standard MIBs, though its interface/route tables parallel concepts in the standard IF-MIB and IP-MIB. It is deployed on RedCreek routing/VPN gateway devices where administrators need to audit firmware/hardware version consistency and basic IP configuration remotely. Network engineers evaluating or troubleshooting this functionality can download the RCV3 file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in RCV3. 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.

Supported Devices

  • RedCreek Communications VPN/routing gateway

Monitoring Examples

An administrator would poll rc3FirmwareVer, rc3BootRomVer, and rc3HardwareVer to audit software/hardware version consistency across a fleet of RedCreek devices before a firmware rollout, and check rc3DistinguishedName/rc3HostName to confirm device identity. rc3InterfaceTable (rc3InterfaceEntry) with rc3InterfaceIp, rc3InterfaceMask, and rc3InterfaceMac would be checked to verify an interface's IP configuration matches expectations, and rc3IpRouteTable would reveal whether expected routes are present, flagging a routing misconfiguration if a critical route is missing.

What Can Be Monitored

  • boot ROM/firmware/hardware version
  • device host name/identity
  • interface IP address, mask, and MAC
  • IP routing table entries
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
IpAddress
enterprises

From RFC1213-MIB

DisplayString
ifIndex
OIDs

RFC description

RedCreek Ravlin VPN appliance management covering system configuration, IPSec, PPPoE, and security parameters.

Start monitoring RedCreek Communications VPN/routing gateway (firmware/hardware version and basic IP/interface config) 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.

Download RCV3