CISCO-REMOTE-ACCESS-MONITOR-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-REMOTE-ACCESS-MONITOR-MIB

Organization: Cisco Systems

Last Updated: 2008--0-8-

Category: Cisco Devices, VPN and Security

Description: Tracks remote access VPN structures spanning Layer 2 (PPTP, L2TP, L2F), Layer 3 (IPSec), and Layer 4 (SSL) VPNs.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-REMOTE-ACCESS-MONITOR-MIB with a free 30-day trial of IPNetwork Monitor.

What Is CISCO-REMOTE-ACCESS-MONITOR-MIB?

CISCO-REMOTE-ACCESS-MONITOR-MIB is a Cisco-specific SNMP module for monitoring remote-access VPN infrastructure spanning Layer 2 tunneling (PPTP, L2TP, L2F), Layer 3 IPSec, and Layer 4 SSL/WebVPN technologies on Cisco routers and VPN head-end devices. It exposes data organized around remote-access sessions and administrative groups, including per-protocol session counts, group membership, and aggregate connection statistics for the Remote Access Service (RAS) subsystem. Its primary monitoring value is software/service health rather than hardware: it lets an operator confirm the RAS process is up, track how many VPN sessions and groups are currently active, and spot abnormal drops or spikes that indicate a service outage or overload. The module is explicitly built on top of the underlying PPTP, L2TP, L2F, IPSec, and SSL/WebVPN protocol standards and is meant to complement, not duplicate, protocol-specific MIBs and RFCs for those tunnel types. It is typically deployed on Cisco VPN concentrators, ISP remote-access routers, and enterprise VPN head-ends that terminate large numbers of client-initiated remote-access tunnels, where CISCO-REMOTE-ACCESS-MONITOR-MIB SNMP monitoring gives operators visibility into RAS session health.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-REMOTE-ACCESS-MONITOR-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.

Supported Devices

  • Cisco VPN concentrator/router
  • Cisco remote-access router

Monitoring Examples

The MIB source did not expose concrete object or table names in this batch, so no specific OID-level polling scenario can be given without inventing identifiers. In practice a network operations team would poll this module's per-group and per-protocol session counters to see, for example, that IPSec session counts have dropped to zero while SSL VPN sessions remain steady, pointing to an IPSec-specific fault. Because RAS terminology (sessions, groups, RTT-style accounting) is described in the module identity text, any real deployment would use this to distinguish a healthy remote-access service from one silently failing for a subset of VPN technologies.

What Can Be Monitored

  • active VPN session counts
  • remote-access group counts
  • per-protocol tunnel status (PPTP/L2TP/L2F/IPSec/SSL)
  • RAS subsystem availability
Imported Objects

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
zeroDotZero

From SNMPv2-TC

TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using crasNumPrevSessions OID:

Select a Cisco VPN concentrator/remote-access router as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type crasNumPrevSessions into the Find box to locate it in the OID tree, then select it and click OK. The number of remote access sessions which were previously active but which where since terminated. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in Sessions), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Monitors remote access VPN structures across Layer 2 (PPTP, L2TP, L2F), Layer 3 (IPSec), and Layer 4 (SSL) virtual private networks.

Start monitoring Cisco VPN concentrator/remote-access router 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 CISCO-REMOTE-ACCESS-MONITOR-MIB