RAISECOM-L2CP-MIB :: rcL2cpStatsEncap

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RAISECOM-L2CP-MIB › rcL2cpStatsEncap

rcL2cpStatsEncap

Module: RAISECOM-L2CP-MIB

OID (symbolic): RAISECOM-L2CP-MIB::rcL2cpStatsEncap

OID (numeric): 1.3.6.1.4.1.8886.6.1.65.2.5.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The tunneled PDU encapsulation statistics of an interface. These statistics cover the number of tunneled ingress PDUs.

What is rcL2cpStatsEncap?

This counter tracks the number of ingress PDUs that have been encapsulated for tunneling for a given protocol on this port. Admins monitor it to confirm that expected control-protocol traffic (like STP or LACP) is actually being tunneled rather than dropped or peered locally. A steady increase confirms tunneled PDUs are being encapsulated as configured.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8886.6.1.65.2.5.1.2
snmpwalk -v2c -c public <target> RAISECOM-L2CP-MIB::rcL2cpStatsEncap

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.8886.6.1.65.2.5.1.2.1
snmpget -v2c -c public <target> RAISECOM-L2CP-MIB::rcL2cpStatsEncap.1

Start monitoring Raisecom Ethernet access/aggregation switches, iSCOM series (Layer 2 Control Protocol tunneling) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RAISECOM-L2CP-MIB::rcL2cpStatsEncap OID value, configure state conditions and alerts, and monitor any Raisecom Ethernet access/aggregation switches, iSCOM series (Layer 2 Control Protocol tunneling) from a single console.

How to Use in IPNetwork Monitor

Select a Raisecom Ethernet access/aggregation switch, iSCOM series (Layer 2 Control Protocol tunneling) 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 rcL2cpStatsEncap into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The tunneled PDU encapsulation statistics of an interface. 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 encapsulated PDUs), 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.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.8886raisecomRAISECOM-BASE-MIB
1.3.6.1.4.1.8886.6iscomSeriesRAISECOM-BASE-MIB
1.3.6.1.4.1.8886.6.1iscomSwitchRAISECOM-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.8886.6.1.65rcL2cpRAISECOM-L2CP-MIB
1.3.6.1.4.1.8886.6.1.65.2rcL2cpConfigTableGroupRAISECOM-L2CP-MIB
1.3.6.1.4.1.8886.6.1.65.2.5rcL2cpStatTableRAISECOM-L2CP-MIB
1.3.6.1.4.1.8886.6.1.65.2.5.1rcL2cpStatEntryRAISECOM-L2CP-MIB
1.3.6.1.4.1.8886.6.1.65.2.5.1.2rcL2cpStatsEncapRAISECOM-L2CP-MIB