Unisphere-Data-L2TP-MIB :: usdL2tpSysStatusTotalDestinations

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Unisphere-Data-L2TP-MIB › usdL2tpSysStatusTotalDestinations

usdL2tpSysStatusTotalDestinations

Module: Unisphere-Data-L2TP-MIB

OID (symbolic): Unisphere-Data-L2TP-MIB::usdL2tpSysStatusTotalDestinations

OID (numeric): 1.3.6.1.4.1.4874.2.2.35.1.1.2.4

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of destination creations attempted.

What is usdL2tpSysStatusTotalDestinations?

Running count of L2TP destination creations attempted since the counter last reset; compare against Failed Destinations to gauge how often destination setup is failing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.35.1.1.2.4
snmpwalk -v2c -c public <target> Unisphere-Data-L2TP-MIB::usdL2tpSysStatusTotalDestinations

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.35.1.1.2.4.1
snmpget -v2c -c public <target> Unisphere-Data-L2TP-MIB::usdL2tpSysStatusTotalDestinations.1

Start monitoring Juniper/Unisphere ERX edge routing switch, LAC/LNS (L2TP tunnel/destination-count status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-L2TP-MIB::usdL2tpSysStatusTotalDestinations OID value, configure state conditions and alerts, and monitor any Juniper/Unisphere ERX edge routing switch, LAC/LNS (L2TP tunnel/destination-count status) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper/Unisphere ERX edge routing switch, LAC/LN (L2TP tunnel/destination-count status) 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 usdL2tpSysStatusTotalDestinations into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of destination creations attempted. 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 (13 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.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.35juniL2tpMIBJuniper-L2TP-MIB
1.3.6.1.4.1.4874.2.2.35.1juniL2tpObjectsJuniper-L2TP-MIB
1.3.6.1.4.1.4874.2.2.35.1.1juniL2tpSystemJuniper-L2TP-MIB
1.3.6.1.4.1.4874.2.2.35.1.1.2juniL2tpSystemStatusJuniper-L2TP-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.35.1.1.2.4usdL2tpSysStatusTotalDestinationsUnisphere-Data-L2TP-MIB