Returns a string which indicates the restore/verify status
associated with either the current, or last, restore/verify
operation performed.
NOTE: This status does NOT reflect the current status of the
mirror. This is simply a historical log of the last
restore or verify command which started execution on
the associated VP device. For example, this status
may report a successfully executed restore operation
but the mirror may have lost synchronization in the
time period since the execution of the restore.
The possible strings that can be returned are:
restore/verify not run since reboot
The restore/verify status is not persistent over
kernel reboots. This status is returned whenever
the restore or verify commands have not been issued
since the last reboot.
restore successful
The last command issued to this VP was a restore
which was successful.
verify successful
The last command issued to this VP was a verify
which was successful.
restore cleared read errors
The restore cleared the VP's read error counters.
A physical restore operation was not performed.
restore operation active
A restore operation is currently active on this VP.
verify operation active
A verify operation is currently active on this VP.
restore was canceled
A restore operation was started but the canceled
at the user's request.
verify was canceled
A verify operation was started but the canceled
at the user's request.
mirror needs repair
A restore operation was attempted on a mirror that
need to be repaired.
memory allocation failure
Buffer allocation necessary to perform a restore or
verify operation were not available.
cannot verify a 'forced' mirror
A verify operation was attempted on a mirror that
was created using the 'force' option. Since the
mirror was never synchronized on a block-by-block
basis, the verify operation is expected to fail.
synchronization was lost during verify
The verify operation was aborted due to a loss of
synchronization. The error causing the loss of
synchronization was not associated with the verify
operation (an external event caused the loss).
error reading primary device
A restore or verify command aborted due to a read
error on the primary device during the operation.
error writing primary device
A restore command aborted due to a write error on
the primary device during the restore operation.
error reading secondary device
A restore or verify command aborted due to a read
error on the secondary device during the operation.
error writing secondary device
A restore command aborted due to a write error on
the secondary device during the restore operation.
error accessing tertiary device
A restore or verify command aborted due to failure
either communicating with a Loop B client system or
because of a read or write error on the tertiary
device.
verify error
A verify error occured between the primary and secondary
mirrored device.
tertiary device verify error
A verify error occured between the primary and tertiary
mirrored device.
status unavailable
The restore status returned was invalid.
Parsed from file MEDIAHAWK-MIB.mib
Module: MEDIAHAWK-MIB
Vendor: CyberGuard CorporationDavid Rhein
Module: MEDIAHAWK-MIB
[Automatically extracted from oidview.com]
mhPartitionRestoreStatus OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION " Returns a string which indicates the restore/verify status associated with either the current, or last, restore/verify operation performed. NOTE: This status does NOT reflect the current status of the mirror. This is simply a historical log of the last restore or verify command which started execution on the associated VP device. For example, this status may report a successfully executed restore operation but the mirror may have lost synchronization in the time period since the execution of the restore. The possible strings that can be returned are: restore/verify not run since reboot The restore/verify status is not persistent over kernel reboots. This status is returned whenever the restore or verify commands have not been issued since the last reboot. restore successful The last command issued to this VP was a restore which was successful. verify successful The last command issued to this VP was a verify which was successful. restore cleared read errors The restore cleared the VP's read error counters. A physical restore operation was not performed. restore operation active A restore operation is currently active on this VP. verify operation active A verify operation is currently active on this VP. restore was canceled A restore operation was started but the canceled at the user's request. verify was canceled A verify operation was started but the canceled at the user's request. mirror needs repair A restore operation was attempted on a mirror that need to be repaired. memory allocation failure Buffer allocation necessary to perform a restore or verify operation were not available. cannot verify a 'forced' mirror A verify operation was attempted on a mirror that was created using the 'force' option. Since the mirror was never synchronized on a block-by-block basis, the verify operation is expected to fail. synchronization was lost during verify The verify operation was aborted due to a loss of synchronization. The error causing the loss of synchronization was not associated with the verify operation (an external event caused the loss). error reading primary device A restore or verify command aborted due to a read error on the primary device during the operation. error writing primary device A restore command aborted due to a write error on the primary device during the restore operation. error reading secondary device A restore or verify command aborted due to a read error on the secondary device during the operation. error writing secondary device A restore command aborted due to a write error on the secondary device during the restore operation. error accessing tertiary device A restore or verify command aborted due to failure either communicating with a Loop B client system or because of a read or write error on the tertiary device. verify error A verify error occured between the primary and secondary mirrored device. tertiary device verify error A verify error occured between the primary and tertiary mirrored device. status unavailable The restore status returned was invalid." ::= { mhPartitionsEntry 19 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.1457.1.4.4.1.1 | mhPartitionName | 0 | 0 | Returns the path name of the raw device associated with VP unit 'N'. Examples: mhPartitionName.0 Returns '/dev/rdsk/vp0' mhPartiti… |
1.3.6.1.4.1.1457.1.4.4.1.2 | mhPartitionType | 0 | 0 | Returns current configuration of VP unit 'N'. Legal values are: 'unconfigured' partition has not been configured 'mirror' configu… |
1.3.6.1.4.1.1457.1.4.4.1.3 | mhPartitionState | 0 | 0 | Returns the current state of VP unit 'N'. Legal values are: 'unconfigured' partition has not been configured 'striped' configured… |
1.3.6.1.4.1.1457.1.4.4.1.4 | mhPartitionActiveReadCount | 0 | 0 | Returns the current number of outstanding read requests on VP unit 'N'. |
1.3.6.1.4.1.1457.1.4.4.1.5 | mhPartitionActiveWriteCount | 0 | 0 | Returns the current number of outstanding write requests on VP unit 'N'. |
1.3.6.1.4.1.1457.1.4.4.1.6 | mhPartitionTotalErrors | 0 | 0 | The total number of I/O errors on VP unit 'N' since system initialization. |
1.3.6.1.4.1.1457.1.4.4.1.7 | mhPartitionSliceSize | 0 | 0 | If mhPartitionType='stripe', this is the stripe size as defined by vpinit(1m). Otherwise, a 0 is returned. |
1.3.6.1.4.1.1457.1.4.4.1.8 | mhPartitionSizeKbytes | 0 | 0 | The size, in kilobytes, of this VP is returned. |
1.3.6.1.4.1.1457.1.4.4.1.9 | mhPartitionReaderMode | 0 | 0 | none The VP is not a mirror. primary When this mirror is synchronized, all read requests will be scheduled exclusively to the prim… |
1.3.6.1.4.1.1457.1.4.4.1.10 | mhPartitionWriterMode | 0 | 0 | -1 The VP is not a mirror. 0 When this mirror is synchronized, the first write to this device will result in the on-disk state o… |
1.3.6.1.4.1.1457.1.4.4.1.11 | mhPartitionRestoreThrottle | 0 | 0 | During a mirrored restore or verify operation, an artificial delay may be performed between each read/write (restore) or read/re… |
1.3.6.1.4.1.1457.1.4.4.1.12 | mhPartitionProgressMeter | 0 | 0 | During a mirrored restore or verify operation, this value indicates the completion percentage. This value is always between '0.0… |
1.3.6.1.4.1.1457.1.4.4.1.13 | mhPartitionMemberCount | 0 | 0 | Returns the number of sub-devices which comprise this VP unit. Unconfigured VPs return 0, mirror VPs return 2, and striped VP ret… |
1.3.6.1.4.1.1457.1.4.4.1.14 | mhPartitionMemberDevices | 0 | 0 | Returns the names of the sub-devices which comprise this VP unit. Normally, the named devices are the same as found in /dev/dsk.… |
1.3.6.1.4.1.1457.1.4.4.1.15 | mhPartitionStartRestore | 0 | 0 | Returns a 1 if a restore or verify operation is currently in progress, or a 0 if not. This option can be used to initiate a repai… |
1.3.6.1.4.1.1457.1.4.4.1.16 | mhPartitionCancelRestore | 0 | 0 | When read, returns a 0. When set to a value of 1, the currently executing restore or verify operation is terminated. This operat… |
1.3.6.1.4.1.1457.1.4.4.1.17 | mpPartitionErrorMask | 0 | 0 | Returns an integer value [0..7] which represents a bitmask of member devices which have reported an I/O error. This value is a l… |
1.3.6.1.4.1.1457.1.4.4.1.18 | mhPartitionHealth | 0 | 0 | Returns a string which indicates the overall health of the VP subsystem: none This device is not a mirror. red A double… |
1.3.6.1.4.1.1457.1.4.4.1.20 | mhPartitionRestoreDate | 0 | 0 | Returns the date and time of the last partition restore, in DateAndTime format of 11 octets. |
1.3.6.1.4.1.1457.1.4.4.1.21 | mhPartitionMountPoint | 0 | 0 | Returns a string denoting the mount-point name if this partition is the mount point for any file system. A null string is return… |
1.3.6.1.4.1.1457.1.4.4.1.22 | mhPartitionFreeSpace | 0 | 0 | Applicable only if previous entry (mount point) returns a non-null string. Returns an integer from 0 to 99 indicating the percent… |