CLI Guide

● managedlogswarn: Specify this option to test receipt of the managed-logs notification that
logs are nearly full and must be transferred to avoid losing older entries. (Event 401)
● managedlogswrap: Specify this option to test receipt of the managed-logs notification that
logs have wrapped and older entries may be lost. (Event 402)
● notification: Specify this option to test receipt of event-notification messages by every
interface that is configured to receive them, such as email, SNMP, and SMI-S. (Event 312)
● snmp: This option behaves the same as the notification option.
region crash1|crash2|crash3|crash4|ecdebug|mc|scdebug
Optional. For use with the managed logs feature, this parameter specifies the log type (debug-data
region) for which to send notifications.
● crash1, crash2, crash3, or crash4: Specify one of these options to send notification for
one of the Storage Controller’s four crash logs.
● ecdebug: Specify this option to send notification for the Expander Controller log.
● mc: Specify this option to send notification for the Management Controller log.
● scdebug: Specify this option to send notification for the Storage Controller log, which includes
the event log.
If this parameter is omitted, the command sends four representative log types: crash1, ecdebug,
scdebug, and mc.
Examples Test receipt of event notifications by every interface that is configured to receive them.
# test notification
Test receipt of the managed-logs notification that the Storage Controller log needs to be transferred.
# test managedlogs region scdebug
See also
set email-parameters
set ntp-parameters
trust
Description
Enables an offline disk group to be brought online for emergency data recovery.
CAUTION: Improper use of trust may cause data corruption or data loss.
NOTE: This command is for use by or with direction from technical support.
This command must be enabled before each use. If used improperly this command can cause unstable
operation and data loss. Before use, carefully read the cautions and procedures below.
The trust command provides an opportunity to recover data from a disk group that has failed due
to disk failure. The command forces a resynchronization of the metadata (as well as time and date
stamps) that unifies members of a disk group, and essentially puts the disk group back into an
accessible state. As long as the failed disks are operable, data can be read from the disks and
restored to another location.
From examining the state of the disks, if the command determines that the trust operation is unsafe
—that it may result in an unstable disk group with data corruption—the command will fail. You
may then seek assistance from technical support or run the command with a special parameter to
acknowledge the risk of proceeding. Otherwise, if the command determines the operation to be safe,
the command will proceed.
When the “trusted” disk group is back online, back up its data and audit the data to make sure that
it is intact. Then delete that disk group, create a new disk group, and restore data from the backup
to the new disk group. Using a trusted disk group is only a disaster-recovery measure. The disk group
has no tolerance for any additional failures.
The following procedure outlines the general steps for performing a trust operation, but the best
procedure to follow for your situation may vary from this procedure. Before starting this procedure,
contact technical support for assistance in determining if the trust operation applies to your situation,
and for assistance to perform it.
Alphabetical list of commands
275