MIB Viewer

secure-disk-unlock

OBJECT-TYPE
1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.20
Access
write-only
Status
optional
Sub-identifiers
0
This object can be used to reinitialize the secure hard disk. If the value is eTrue the secure disk will be crypto erased, the NVRAM <<hidden>> will be cleared and the Auotlock mode will be set to TRUE , else otherwise. This Object is writable when FILE-SYSTEM-SECURITY-ACCESS-<<hidden>> is the empty string or when a write to FILE-SYSTEM-SECURITY-ACCESS-<<hidden>> with the current <<hidden>> has preceeded the write to the object. FILE-SYSTEM-SECURITY-ACCESS-<<hidden>> must then be written to again with the current <<hidden>> in order to make another write operation on the object possible. A write to this Object without a preceeding write with current <<hidden>> to FILE-SYSTEM-SECURITY-ACCESS-<<hidden>>,when the latter is set will return <genErr>. Additional information: This object can be used to reinitialize the secure hard disk . If the value is eTrue the secure disk will be crypto erased , the NVRAM <<hidden>> will be cleared and the Auotlock mode will be set to TRUE , else otherwise Successful execution of this PML object cause reboot. This Object is writable when FILE-SYSTEM-SECURITY-ACCESS-<<hidden>> is the empty string or when a write to FILE-SYSTEM-SECURITY- ACCESS-<<hidden>> with the current <<hidden>> has preceeded the write to the object. FILE-SYSTEM-SECURITY-ACCESS-<<hidden>> must then be written to again with the current <<hidden>> in order to make another write operation on the object possible. A write to this Object without a preceeding write with current <<hidden>> to FILE-SYSTEM-SECURITY-ACCESS-<<hidden>>,when the latter is set will return <genErr>.If the secure disk is in the SecureDiskLocked<<hidden>>Correct and SecureDiskUnLocked<<hidden>>Null state Unlock operation is going to work like normal diskwipe ,That means the Crypto erase is going to happen after the reboot .
INTEGER { eFalse(1), eTrue(2) }