All MIBs › JUNIPER-VPN-MIB › jnxVpnPwUp
jnxVpnPwUp
Module: JUNIPER-VPN-MIB
OID (symbolic): JUNIPER-VPN-MIB::jnxVpnPwUp
OID (numeric): 1.3.6.1.4.1.2636.3.26.0.3
Node type: NOTIFICATION-TYPE
Description: A jnxVpnPwUp notification is generated when the Pseudo-Wire with index jnxVpnPwIndex belonging to the VPN named jnxVpnPwVpnName of type jnxVpnPwVpnType transitions out of the 'down' state.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' JUNIPER-VPN-MIB::jnxVpnPwUp snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.2636.3.26.0.3
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:51000->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (385352504) 44 days, 14:25:25.04 SNMPv2-MIB::snmpTrapOID.0 = OID: JUNIPER-VPN-MIB::jnxVpnPwUp
Start monitoring Juniper MX/PE router (L2VPN/L3VPN service instances) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-VPN-MIB::jnxVpnPwUp OID value, configure state conditions and alerts, and monitor any Juniper MX/PE router (L2VPN/L3VPN service instances) from a single console.
OID Breakdown
Upper-level ancestors (8 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.2636 | juniperMIB | JUNIPER-SMI |
| 1.3.6.1.4.1.2636.3 | jnxMibs | JUNIPER-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2636.3.26 | jnxVpnMIB | JUNIPER-VPN-MIB |
| 1.3.6.1.4.1.2636.3.26.0 | jnxVpnMIBNotifications | JUNIPER-VPN-MIB |
| 1.3.6.1.4.1.2636.3.26.0.3 | jnxVpnPwUp | JUNIPER-VPN-MIB |