All MIBs › VIPTELA-TRAPS › viptelaVpnTrafficDirection
viptelaVpnTrafficDirection
Module: VIPTELA-TRAPS
OID (symbolic): VIPTELA-TRAPS::viptelaVpnTrafficDirection
OID (numeric): 1.3.6.1.4.1.41916.100.1.135
Node type: OBJECT-TYPE
Type: TrafficDirectionEnum
Access: read-only
What is viptelaVpnTrafficDirection?
Indicates whether the bandwidth event reported in viptelaVpnInterfaceBw concerns downstream or upstream traffic on the interface. The source MIB leaves this field's DESCRIPTION empty, so this reading is inferred from the object name and the notification it is bound to.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.41916.100.1.135 snmpwalk -v2c -c public <target> VIPTELA-TRAPS::viptelaVpnTrafficDirection
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.41916.100.1.135.1 snmpget -v2c -c public <target> VIPTELA-TRAPS::viptelaVpnTrafficDirection.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::viptelaVpnTrafficDirection 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.41916 | viptela | VIPTELA-GLOBAL |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.41916.100 | viptela_traps | VIPTELA-TRAPS |
| 1.3.6.1.4.1.41916.100.1 | fields | VIPTELA-TRAPS |
| 1.3.6.1.4.1.41916.100.1.135 | viptelaVpnTrafficDirection | VIPTELA-TRAPS |