VERTICAL-std-MIB

File: VERTICAL-std-MIB.mib (31923 bytes)

Imported modules

RFC1155-SMI RFC1213-MIB RFC-1212
RFC-1215

Imported symbols

Gauge enterprises DisplayString
OBJECT-TYPE TRAP-TYPE

Defined Types

STDComponentEntry  
SEQUENCE    
  compIndex INTEGER
  compName DisplayString
  compType INTEGER
  compInstallStatus INTEGER
  compOperStatus INTEGER
  compEnabled INTEGER
  compLastStart DisplayString

Defined Values

vertical 1.3.6.1.4.1.2338
OBJECT IDENTIFIER    

selfTestDaemon 1.3.6.1.4.1.2338.8
OBJECT IDENTIFIER    

stdSystemGroup 1.3.6.1.4.1.2338.8.1
OBJECT IDENTIFIER    

sysOperStatus 1.3.6.1.4.1.2338.8.1.1
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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER running(1), startUpInProgress(2), upgradeInProgress(3), restoreInProgress(4), error(5)  

sysCurrentVersion 1.3.6.1.4.1.2338.8.1.2
Specifies the current Instant Office version on this system.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..32)  

stdComponentGroup 1.3.6.1.4.1.2338.8.2
OBJECT IDENTIFIER    

stdComponentTable 1.3.6.1.4.1.2338.8.2.1
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.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    STDComponentEntry

stdComponentEntry 1.3.6.1.4.1.2338.8.2.1.1
An entry in the Component table.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  STDComponentEntry  

compIndex 1.3.6.1.4.1.2338.8.2.1.1.1
The index of the component
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

compName 1.3.6.1.4.1.2338.8.2.1.1.2
The name of the component
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..100)  

compType 1.3.6.1.4.1.2338.8.2.1.1.3
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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER type-driver(1), type-service(16), type-executable(2000), type-non-vni-driver(2001), type-non-vni-service(2002), type-non-vni-executable(2003)  

compInstallStatus 1.3.6.1.4.1.2338.8.2.1.1.4
Describes the installation status of this component. The following the valid values: uninstalled = 100, installed = 1
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER uninstalled(100), installed(1)  

compOperStatus 1.3.6.1.4.1.2338.8.2.1.1.5
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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER stopped(1), start-pending(2), stop-pending(3), running(4), continue-pending(5), pause-pending(6), paused(7), unknown(8), disabled(1025)  

compEnabled 1.3.6.1.4.1.2338.8.2.1.1.6
Determines whether this component is enabled or disabled. Valid values: enabled = 100, disabled = 1
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER enabled(100), disabled(1)  

compLastStart 1.3.6.1.4.1.2338.8.2.1.1.7
The date-time stamp when this component was last restarted.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..32)  

stdCompFailedToStart 26
This notification is sent when a component fails to start during initial start-up.
TRAP-TYPE    

stdCompAttemptRestart 27
This notification is sent when the Self Test Daemon attempts to restart a component.
TRAP-TYPE    

stdCompFailedToReStart 28
This notification is sent when an attempt to restart a component failed.
TRAP-TYPE    

stdCompRestartComplete 29
This notification is sent when a component is successfully restarted
TRAP-TYPE    

stdUpgradeStarted 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
TRAP-TYPE    

stdUnpackingFiles 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
TRAP-TYPE    

stdUnpackingComplete 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
TRAP-TYPE    

stdUpgradeBeingApplied 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
TRAP-TYPE    

stdUpgradeInProgress 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
TRAP-TYPE    

stdUpgradeComplete 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
TRAP-TYPE    

stdUpgradeError 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
TRAP-TYPE    

stdRestoreStarted 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
TRAP-TYPE    

stdRestoreInProgress 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
TRAP-TYPE    

stdRestoreComplete 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
TRAP-TYPE    

stdRestoreError 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
TRAP-TYPE    

stdRebootingMachine 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
TRAP-TYPE    

stdVerifyingSystem 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
TRAP-TYPE    

stdIOUptoDate 50
This notification is sent when an upgrade attempt is aborted because the current version of Instant Office is later than the upgrade version.
TRAP-TYPE    

stdBadCABFile 51
This notification is sent when an upgrade attempt is aborted because of a bad CAB file.
TRAP-TYPE    

stdNotEnoughDiskSpace 52
This notification is sent when an upgrade attempt is aborted because there is not enough disk space on the machine.
TRAP-TYPE    

stdIoNotOperational 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.
TRAP-TYPE    

stdPrerequisiteMissing 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.
TRAP-TYPE    

stdPLDFailed 70
Resource Card Firmware upgrade failed. Return code=nnnn
TRAP-TYPE    

stdUnsupportedConfiguration 71
You are running an unsupported configuration. 1600-Router card requires a newer version of the Resource Switch Card.
TRAP-TYPE    

stdInvalidConfiguration 72
You are running an invalid configuration. 1600-Router card will be disabled since there are more than 2 Station Cards present.
TRAP-TYPE