CISCO-IPSEC-MIB :: cipsNumTEDProbesReceived

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-IPSEC-MIB › cipsNumTEDProbesReceived

cipsNumTEDProbesReceived

Module: CISCO-IPSEC-MIB

OID (symbolic): CISCO-IPSEC-MIB::cipsNumTEDProbesReceived

OID (numeric): 1.3.6.1.4.1.9.10.62.1.2.2.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of TED probes that were received by this managed entity since bootup. Not affected by any CLI operation.

What is cipsNumTEDProbesReceived?

This counts the number of Tunnel Endpoint Discovery (TED) probes received by this managed entity since bootup, per its description, and explicitly notes it is not affected by any CLI operation. TED lets a router dynamically discover a remote IPsec peer's address rather than requiring it to be statically configured, so this counter reflects how often other routers are trying to discover this one as a potential VPN endpoint. A steadily climbing count on a hub router in a dynamic-mesh VPN design is expected and healthy, showing spokes successfully probing for it.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.62.1.2.2.1
snmpwalk -v2c -c public <target> CISCO-IPSEC-MIB::cipsNumTEDProbesReceived

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.62.1.2.2.1.1
snmpget -v2c -c public <target> CISCO-IPSEC-MIB::cipsNumTEDProbesReceived.1

Start monitoring Cisco routers and VPN gateways implementing IPsec with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-IPSEC-MIB::cipsNumTEDProbesReceived OID value, configure state conditions and alerts, and monitor any Cisco routers and VPN gateways implementing IPsec from a single console.

How to Use in IPNetwork Monitor

Select a Cisco router or VPN gateway implementing IPsec 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 cipsNumTEDProbesReceived into the Find box to locate it in the OID tree, then select it and click OK. The number of TED probes that were received by this managed entity since bootup. 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 Integral Units), 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 (8 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.62ciscoIPsecMIBCISCO-IPSEC-MIB
1.3.6.1.4.1.9.10.62.1ciscoIPsecMIBObjectsCISCO-IPSEC-MIB
1.3.6.1.4.1.9.10.62.1.2cipsIPsecGroupCISCO-IPSEC-MIB
1.3.6.1.4.1.9.10.62.1.2.2cipsIPsecStatisticsCISCO-IPSEC-MIB
1.3.6.1.4.1.9.10.62.1.2.2.1cipsNumTEDProbesReceivedCISCO-IPSEC-MIB