H3C-L2TP-MIB :: h3cL2tpStatsTotalTunnels

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › H3C-L2TP-MIB › h3cL2tpStatsTotalTunnels

h3cL2tpStatsTotalTunnels

Module: H3C-L2TP-MIB

OID (symbolic): H3C-L2TP-MIB::h3cL2tpStatsTotalTunnels

OID (numeric): 1.3.6.1.4.1.2011.10.2.139.1.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The total number of tunnels at the time of querying.

What is h3cL2tpStatsTotalTunnels?

This counter reports how many L2TP tunnels currently exist on the device at the moment it's queried. An admin monitors this to track L2TP VPN tunnel load on the device and spot unexpected spikes or drops in the number of active tunnels. A reading of 42 would tell the admin the device currently has 42 active L2TP tunnels established.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.139.1.1.1.1
snmpwalk -v2c -c public <target> H3C-L2TP-MIB::h3cL2tpStatsTotalTunnels

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.139.1.1.1.1.1
snmpget -v2c -c public <target> H3C-L2TP-MIB::h3cL2tpStatsTotalTunnels.1

Start monitoring H3C router/BRAS acting as L2TP LAC or LNS with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the H3C-L2TP-MIB::h3cL2tpStatsTotalTunnels OID value, configure state conditions and alerts, and monitor any H3C router/BRAS acting as L2TP LAC or LNS from a single console.

How to Use in IPNetwork Monitor

Select an H3C router/BRAS acting as L2TP LAC or LNS 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 h3cL2tpStatsTotalTunnels into the Find box to locate it in the OID tree, then select it and click OK. The total number of tunnels at the time of querying. 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, 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.2011huaweiEXPERTV2-MIB
1.3.6.1.4.1.2011.10h3cHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.10.2h3cCommonHUAWEI-3COM-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2011.10.2.139h3cL2tpH3C-L2TP-MIB
1.3.6.1.4.1.2011.10.2.139.1h3cL2tpObjectsH3C-L2TP-MIB
1.3.6.1.4.1.2011.10.2.139.1.1h3cL2tpScalarH3C-L2TP-MIB
1.3.6.1.4.1.2011.10.2.139.1.1.1h3cL2tpStatsH3C-L2TP-MIB
1.3.6.1.4.1.2011.10.2.139.1.1.1.1h3cL2tpStatsTotalTunnelsH3C-L2TP-MIB