All MIBs › VERTICAL-std-MIB
Category: Vertical Networks Enterprise
Description: Provides standard object definitions and SMI base structure for Vertical Networks products.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is VERTICAL-std-MIB?
VERTICAL-std-MIB is the root SMI (Structure of Management Information) module for Vertical Networks, a vendor of integrated voice/data communication systems and small-business telephony gateways. Rather than exposing runtime data itself, it defines the top-level enterprise OID branch ("vertical") under which all other Vertical Networks MIB modules register their object identifiers. As such it exposes no monitorable counters or status objects of its own; it is purely a namespace/registration module used to organize the vendor's MIB tree. Because every other Vertical Networks MIB (such as its IP telephony gateway MIBs) depends on this module for its OID root, it functions as a foundational dependency for the vendor's entire SNMP instrumentation. It is typically loaded as a prerequisite MIB by SNMP management stations before any device-specific Vertical Networks MIB, rather than polled directly for monitoring. Network engineers evaluating or troubleshooting this functionality can download the VERTICAL-std-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in VERTICAL-std-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Vertical Networks voice/data gateways
- Vertical Networks telephony systems
Monitoring Examples
This module contains only the "vertical" enterprise OID node and defines no tables, scalars, or traps, so it has no runtime data of its own to poll. It exists purely so that other Vertical Networks MIBs can subordinate their object identifiers under a common enterprise branch. An admin would never poll this MIB directly; instead it must simply be compiled/loaded alongside the vendor's functional MIBs (e.g., the IP telephony gateway MIB) so their OIDs resolve correctly.
This MIB depends on
Related MIBs
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC-1215
| TRAP-TYPE |
From RFC1155-SMI
| Gauge | |
| enterprises |
From RFC1213-MIB
| DisplayString |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| INT compEnabled | 1.3.6.1.4.1.2338.8.2.1.1.6 | INTEGER | read-only | Determines whether this component is enabled or disabled. Valid values: enabled = 100, disabled = 1 |
| INT compIndex | 1.3.6.1.4.1.2338.8.2.1.1.1 | INTEGER | read-only | The index of the component |
| INT compInstallStatus | 1.3.6.1.4.1.2338.8.2.1.1.4 | INTEGER | read-only | Describes the installation status of this component. The following the valid values: uninstalled = 100, installed = 1 |
| STR compLastStart | 1.3.6.1.4.1.2338.8.2.1.1.7 | DisplayString | read-only | The date-time stamp when this component was last restarted. |
| STR compName | 1.3.6.1.4.1.2338.8.2.1.1.2 | DisplayString | read-only | The name of the component |
| INT compOperStatus | 1.3.6.1.4.1.2338.8.2.1.1.5 | INTEGER | read-only | The operational status of this component. The following the valid values: stopped =1, start-pending =2, stop-pending =3, running =4 (the normal operational state), continue-pending =5, pause-pending =6, paused =7, unknown =8, disabled =1025 |
| INT compType | 1.3.6.1.4.1.2338.8.2.1.1.3 | INTEGER | read-only | The Component type - defines whether this component is a driver, service or an executable. The following the valid values: type-driver = 1, type-service = 16, type-executable = 2000, type-non-vni-driver = 2001, type-non-vni-service = 2002, type-non-vni-executable = 2003 |
| selfTestDaemon | 1.3.6.1.4.1.2338.8 | |||
| NTF stdBadCABFile | 1.3.6.1.4.1.2338.0.51 | This notification is sent when an upgrade attempt is aborted because of a bad CAB file. | ||
| NTF stdCompAttemptRestart | 1.3.6.1.4.1.2338.0.27 | This notification is sent when the Self Test Daemon attempts to restart a component. | ||
| NTF stdCompFailedToReStart | 1.3.6.1.4.1.2338.0.28 | This notification is sent when an attempt to restart a component failed. | ||
| NTF stdCompFailedToStart | 1.3.6.1.4.1.2338.0.26 | This notification is sent when a component fails to start during initial start-up. | ||
| stdComponentEntry | 1.3.6.1.4.1.2338.8.2.1.1 | not-accessible | An entry in the Component table. | |
| stdComponentGroup | 1.3.6.1.4.1.2338.8.2 | |||
| stdComponentTable | 1.3.6.1.4.1.2338.8.2.1 | not-accessible | Table of status information about all Instant Office components (executables, services and drivers). There are as many entries as there are components in the system. | |
| NTF stdCompRestartComplete | 1.3.6.1.4.1.2338.0.29 | This notification is sent when a component is successfully restarted | ||
| NTF stdInvalidConfiguration | 1.3.6.1.4.1.2338.0.72 | You are running an invalid configuration. 1600-Router card will be disabled since there are more than 2 Station Cards present. | ||
| NTF stdIoNotOperational | 1.3.6.1.4.1.2338.0.63 | This notification is sent under any of the following conditions: - Before attempting to start the components, FBS checks to ensure the minimum configuration is present in the box, currently this means an RSC card in Slot_05. If this check fails, FBS will not attempt to start any of the components and needs to send a trap out to the world! - When FBS attempts to start all components and a critical component fails to start and hence InstantOffice is not operational, FBS needs to send the trap. - After an upgrade is performed and deemed unsuccessful, FBS will attempt to restore to the previous working version. In case this process fails, FBS needs to send the trap. | ||
| NTF stdIOUptoDate | 1.3.6.1.4.1.2338.0.50 | This notification is sent when an upgrade attempt is aborted because the current version of Instant Office is later than the upgrade version. | ||
| NTF stdNotEnoughDiskSpace | 1.3.6.1.4.1.2338.0.52 | This notification is sent when an upgrade attempt is aborted because there is not enough disk space on the machine. | ||
| NTF stdPLDFailed | 1.3.6.1.4.1.2338.0.70 | Resource Card Firmware upgrade failed. Return code=nnnn | ||
| NTF stdPrerequisiteMissing | 1.3.6.1.4.1.2338.0.67 | This notification is sent when an upgrade attempt is done on an Instant Office that does not contain the pre-requisite software version for that upgrade. | ||
| NTF stdRebootingMachine | 1.3.6.1.4.1.2338.0.41 | This notification is sent before an Instant Office reboot is done, typically due to an upgrade/restore request. 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 | ||
| NTF stdRestoreComplete | 1.3.6.1.4.1.2338.0.39 | This notification is sent when a previous version of Instant Office is restored successfully. A restore operation is typically carried out after a failed upgrade attempt. 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 | ||
| NTF stdRestoreError | 1.3.6.1.4.1.2338.0.40 | This notification is sent when an Instant Office restore attemp fails. 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 | ||
| NTF stdRestoreInProgress | 1.3.6.1.4.1.2338.0.38 | This notification is sent when a previous version of Instant Office is restored successfully. A restore operation is typically carried out after a failed upgrade attempt. 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 | ||
| NTF stdRestoreStarted | 1.3.6.1.4.1.2338.0.37 | This notification is sent when a previous version of Instant Office is about to be restored. A restore operation is typically carried out after a failed upgrade attempt. 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 | ||
| stdSystemGroup | 1.3.6.1.4.1.2338.8.1 | |||
| NTF stdUnpackingComplete | 1.3.6.1.4.1.2338.0.32 | This notification is sent when unpacking of the upgraded CAB file is complete. 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 | ||
| NTF stdUnpackingFiles | 1.3.6.1.4.1.2338.0.31 | This notification is sent when unpacking of the upgraded CAB file starts. 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 | ||
| NTF stdUnsupportedConfiguration | 1.3.6.1.4.1.2338.0.71 | You are running an unsupported configuration. 1600-Router card requires a newer version of the Resource Switch Card. | ||
| NTF stdUpgradeBeingApplied | 1.3.6.1.4.1.2338.0.33 | 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 | ||
| NTF stdUpgradeComplete | 1.3.6.1.4.1.2338.0.35 | This notification is sent when an Instant Office upgrade is successfully completed. 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 | ||
| NTF stdUpgradeError | 1.3.6.1.4.1.2338.0.36 | This notification is sent when an Instant Office upgrade attempt fails. A Restore operation would be done immediately. 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 | ||
| NTF stdUpgradeInProgress | 1.3.6.1.4.1.2338.0.34 | This notification is sent when an Instant Office upgrade process is under way. 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 | ||
| NTF stdUpgradeStarted | 1.3.6.1.4.1.2338.0.30 | This notification is sent when an Instant Office upgrade is started. 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 | ||
| NTF stdVerifyingSystem | 1.3.6.1.4.1.2338.0.42 | This notification is sent when the System is brought up (all componenets are started) after an Upgrade or a restore process. 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 | ||
| STR sysCurrentVersion | 1.3.6.1.4.1.2338.8.1.2 | DisplayString | read-only | Specifies the current Instant Office version on this system. |
| INT sysOperStatus | 1.3.6.1.4.1.2338.8.1.1 | INTEGER | read-only | Specifies the current operational status of the Instant Office system. Valid values are: running (1) -> The normal operational status, all components are up and running. startUpInProgress (2) -> The ST Deamon is starting up the system. upgradeInProgress (3) -> The ST Daemon is attempting to upgrade the system. restoreInProgress (4) -> The ST Daemon is attemping to restore the system from a previous installation, after an upgrade attemp failed. error (5) -> An error condition. One or more components failed to start. More information can be found from the Component Table |
| vertical | 1.3.6.1.4.1.2338 |
RFC description
Monitors status of Vertical Instant Office components including services, drivers, and executables.
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. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.