VIPTELA-TRAPS :: viptelaVpnVpnId

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › VIPTELA-TRAPS › viptelaVpnVpnId

viptelaVpnVpnId

Module: VIPTELA-TRAPS

OID (symbolic): VIPTELA-TRAPS::viptelaVpnVpnId

OID (numeric): 1.3.6.1.4.1.41916.100.1.67

Node type: OBJECT-TYPE

Type: VpnId

Access: read-only

What is viptelaVpnVpnId?

Identifies which VPN (Viptela's segment/VRF identifier) a VPN-related trap refers to, and is reused across most viptela-vpn traps such as BGP peer state change, interface state change, and DHCP events, so an admin knows which routing segment is affected. This object has an empty DESCRIPTION in the source MIB, so the explanation is inferred from its name and the trap that carries it.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.41916.100.1.67
snmpwalk -v2c -c public <target> VIPTELA-TRAPS::viptelaVpnVpnId

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.41916.100.1.67.1
snmpget -v2c -c public <target> VIPTELA-TRAPS::viptelaVpnVpnId.1

Start monitoring Viptela/Cisco SD-WAN vEdge router, Cisco SD-WAN controller (BFD-failure/reboot-reason notification status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VIPTELA-TRAPS::viptelaVpnVpnId OID value, configure state conditions and alerts, and monitor any Viptela/Cisco SD-WAN vEdge router, Cisco SD-WAN controller (BFD-failure/reboot-reason notification status) from a single console.

OID Breakdown

Upper-level ancestors (7 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.41916viptelaVIPTELA-GLOBAL
Numeric OIDNameModule
1.3.6.1.4.1.41916.100viptela_trapsVIPTELA-TRAPS
1.3.6.1.4.1.41916.100.1fieldsVIPTELA-TRAPS
1.3.6.1.4.1.41916.100.1.67viptelaVpnVpnIdVIPTELA-TRAPS