VERTICAL-std-MIB: View SNMP OID List / Download MIB

VENDOR: VERTICAL NETWORKS


 Home MIB: VERTICAL-std-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 vertical 1.3.6.1.4.1.2338
           selfTestDaemon 1.3.6.1.4.1.2338.8
               stdSystemGroup 1.3.6.1.4.1.2338.8.1
                   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 Enumeration: 'running': 1, 'restoreInProgress': 4, 'upgradeInProgress': 3, 'startUpInProgress': 2, 'error': 5.
                   sysCurrentVersion 1.3.6.1.4.1.2338.8.1.2 displaystring read-only
Specifies the current Instant Office version on this system.
               stdComponentGroup 1.3.6.1.4.1.2338.8.2
                   stdComponentTable 1.3.6.1.4.1.2338.8.2.1 no-access
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.
                       stdComponentEntry 1.3.6.1.4.1.2338.8.2.1.1 no-access
An entry in the Component table.
                           compIndex 1.3.6.1.4.1.2338.8.2.1.1.1 integer read-only
The index of the component
                           compName 1.3.6.1.4.1.2338.8.2.1.1.2 displaystring read-only
The name of the component
                           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 Enumeration: 'type-driver': 1, 'type-service': 16, 'type-executable': 2000, 'type-non-vni-service': 2002, 'type-non-vni-driver': 2001, 'type-non-vni-executable': 2003.
                           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 Enumeration: 'uninstalled': 100, 'installed': 1.
                           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 Enumeration: 'pause-pending': 6, 'continue-pending': 5, 'unknown': 8, 'disabled': 1025, 'paused': 7, 'running': 4, 'stopped': 1, 'stop-pending': 3, 'start-pending': 2.
                           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 Enumeration: 'disabled': 1, 'enabled': 100.
                           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.
             stdCompFailedToStart 1.3.6.1.4.1.23380.26
This notification is sent when a component fails to start during initial start-up.
             stdCompAttemptRestart 1.3.6.1.4.1.23380.27
This notification is sent when the Self Test Daemon attempts to restart a component.
             stdCompFailedToReStart 1.3.6.1.4.1.23380.28
This notification is sent when an attempt to restart a component failed.
             stdCompRestartComplete 1.3.6.1.4.1.23380.29
This notification is sent when a component is successfully restarted
             stdUpgradeStarted 1.3.6.1.4.1.23380.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
             stdUnpackingFiles 1.3.6.1.4.1.23380.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
             stdUnpackingComplete 1.3.6.1.4.1.23380.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
             stdUpgradeBeingApplied 1.3.6.1.4.1.23380.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
             stdUpgradeInProgress 1.3.6.1.4.1.23380.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
             stdUpgradeComplete 1.3.6.1.4.1.23380.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
             stdUpgradeError 1.3.6.1.4.1.23380.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
             stdRestoreStarted 1.3.6.1.4.1.23380.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
             stdRestoreInProgress 1.3.6.1.4.1.23380.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
             stdRestoreComplete 1.3.6.1.4.1.23380.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
             stdRestoreError 1.3.6.1.4.1.23380.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
             stdRebootingMachine 1.3.6.1.4.1.23380.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
             stdVerifyingSystem 1.3.6.1.4.1.23380.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
             stdIOUptoDate 1.3.6.1.4.1.23380.50
This notification is sent when an upgrade attempt is aborted because the current version of Instant Office is later than the upgrade version.
             stdBadCABFile 1.3.6.1.4.1.23380.51
This notification is sent when an upgrade attempt is aborted because of a bad CAB file.
             stdNotEnoughDiskSpace 1.3.6.1.4.1.23380.52
This notification is sent when an upgrade attempt is aborted because there is not enough disk space on the machine.
             stdIoNotOperational 1.3.6.1.4.1.23380.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.
             stdPrerequisiteMissing 1.3.6.1.4.1.23380.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.
             stdPLDFailed 1.3.6.1.4.1.23380.70
Resource Card Firmware upgrade failed. Return code=nnnn
             stdUnsupportedConfiguration 1.3.6.1.4.1.23380.71
You are running an unsupported configuration. 1600-Router card requires a newer version of the Resource Switch Card.
             stdInvalidConfiguration 1.3.6.1.4.1.23380.72
You are running an invalid configuration. 1600-Router card will be disabled since there are more than 2 Station Cards present.