All MIBs › RAISECOM-L2CP-MIB
Organization: Raisecom, Inc.
Last Updated: 2013-11-21
Category: Raisecom Networks
Description: Manages Layer 2 Control Protocol tunneling for transparent bridging of control frames.
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 RAISECOM-L2CP-MIB?
RAISECOM-L2CP-MIB is a Raisecom enterprise MIB (under the iscomSwitch subtree) that manages Layer 2 Control Protocol (L2CP) tunneling — the mechanism that transparently tunnels or peers control-plane frames like STP, LACP, CDP, VTP, PVST, OAM, and LLDP across a provider network instead of dropping or terminating them locally. It defines rcL2cpProfileBaseTable (tunnel profiles keyed by rcL2cpProfileBaseIndex, specifying rcL2cpProfileBaseTunnelVlan/TunnelEgressPort/TunnelType and RowStatus lifecycle), rcL2cpProfileProtocolTable (per-protocol action: tunnel/peer/drop), rcL2cpProfileMacTable (custom destination-MAC-based tunneling rules), rcL2cpPortTable (applies a profile to a port via rcPortIndex), and rcL2cpStatTable (per-port, per-protocol counters rcL2cpStatsEncap/DeEncap/Drop). Polling rcL2cpStatTable reveals whether tunneled control PDUs are actually being encapsulated/de-encapsulated as configured, and a climbing rcL2cpStatsDrop counter signals control-plane frames being discarded. It depends on the vendor's SWITCH-SYSTEM-MIB (rcPortIndex) and SWITCH-TC/RAISECOM-BASE-MIB definitions, and is deployed on Raisecom Ethernet access/aggregation switches used for L2 control-plane transparency; the RAISECOM-L2CP-MIB download provides the exact object definitions for building such polling scripts.
IPNetwork Monitor allows you to monitor SNMP objects defined in RAISECOM-L2CP-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
- Raisecom Ethernet access/aggregation switches (iSCOM series)
Monitoring Examples
An operator polls rcL2cpStatTable (indexed by rcPortIndex and rcL2cpStatsProtocolIndex) to check rcL2cpStatsEncap and rcL2cpStatsDeEncap counts for the stp(1) protocol on an access port configured with rcL2cpProfileProtocolAction set to tunnel; a nonzero and growing rcL2cpStatsDrop counter for that protocol would indicate STP BPDUs are being dropped instead of tunneled, breaking spanning-tree consistency across the provider network.
What Can Be Monitored
- L2CP tunnel profile configuration
- per-protocol tunnel/peer/drop action assignment
- MAC-based tunneling rule entries
- port-to-profile binding
- encapsulation/de-encapsulation/drop PDU counters
Imported Objects
From RAISECOM-BASE-MIB
| iscomSwitch | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| MacAddress | |
| RowStatus | |
| TruthValue |
From SWITCH-SYSTEM-MIB
| rcPortIndex | OBJECT-TYPE |
From SWITCH-TC
| ObjName |
How to Use in IPNetwork Monitor
Example using rcL2cpStatsEncap OID:
OIDs
RFC description
Controls Layer 2 Control Protocol (L2CP) functionality for Raisecom switches including destination MAC addresses and tunneling.
Start monitoring Raisecom Ethernet access/aggregation switches, iSCOM series (Layer 2 Control Protocol tunneling) 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.