All MIBs › VERTICAL-std-MIB › stdUpgradeBeingApplied
stdUpgradeBeingApplied
Module: VERTICAL-std-MIB
OID (symbolic): VERTICAL-std-MIB::stdUpgradeBeingApplied
OID (numeric): 1.3.6.1.4.1.2338.0.33
Node type: NOTIFICATION-TYPE
Description: This notification is sent when an Instant Office upgrade is about to be applied. This is done after the Upgraded CAB file is unpacked and a system reboot is done. The stages of an upgrade and restore are : 1. An Upgrade request comes in: CAB file is pushed - stdUpgradeStarted Trap is sent 2. Unpacking of the CAB file is done - stdUnpackingFiles Trap is sent 3. Multiple stdUpgradeInProgress Traps are sent during this period 4. Unpacking is complete - stdUnpackingComplete Trap is sent 5. A system reboot is done - stdRebootingMachine Trap is sent 6. Upgrade is applied - stdUpgradeBeingApplied Trap is sent. 7. Multiple stdUpgradeInProgress Traps are sent during this period 8. System is rebooted again - stdRebootingMachine Trap is sent. 9. All components are started - stdVerifyingSystem Trap is sent. 10. If success: stdUpgradeComplete Trap is sent : All is well Else ,stdUpgradeError Trap is sent, and a restore operation is attempted 11. Restore is attempted - stdRestoreStarted Trap is sent 12. Multiple stdRestoreInProgress Traps are sent at this point. 13. A system reboot is done : stdRebootingMachine Trap is sent. 14. All components are started - stdVerifyingSystem Trap is sent. 15. If success: stdRestoreComplete Trap is sent, else stdRestoreError Trap is sent. std quits at this point
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> '' VERTICAL-std-MIB::stdUpgradeBeingApplied snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.2338.0.33
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]:58710->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (192166742) 22 days, 5:47:47.42 SNMPv2-MIB::snmpTrapOID.0 = OID: VERTICAL-std-MIB::stdUpgradeBeingApplied
Start monitoring Vertical Networks voice/data gateways, Vertical Networks telephony systems (base enterprise OID registration, no data objects) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VERTICAL-std-MIB::stdUpgradeBeingApplied OID value, configure state conditions and alerts, and monitor any Vertical Networks voice/data gateways, Vertical Networks telephony systems (base enterprise OID registration, no data objects) 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.2338 | vertical | VERTICAL-EVENTLOG-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2338.0.33 | stdUpgradeBeingApplied | VERTICAL-std-MIB |