Manuals

Event	Event's Message Type
Controller failure	AdapterFailure
Enclosure fan failure	Enclosure Fan Failure
Enclosure power supply failure	Enclosure Power Supply Failure
Abnormal enclosure temperature	Enclosure Abnormal Temperature
Enclosure temperature over threshold	Enclosure Temperature above threshold
Failed mirror failover	NoMirror
No space for mirror failover	MirrorNoSpace
Unmirror failure	NoUnMirror
Mirror failover started	FailoverStarted
No controller memory for mirror create	MirrorNoCreate
No failover assigned	MirrorNoFailover
Mirror drive failure	MirrorDriveFailure
RAID-5 drive failure	R5DriveFailure
No controller memory for RAID-5 rebuild	R5NoRebuild
No controller memory for RAID-5 scrub	R5NoScrub
No failover assigned	R5NoFailover
No space on RAID-5 container or failover containers	R5NoSpace

Syntax

mail set message

[/computer{=string}]

[/domain{=string}]

[/all{=boolean}]

[/container{=boolean}]

[/fatal{=boolean}]

[/smart{=boolean}]

[/battery{=boolean}]

[/battery_dead{=boolean}]

[/battery_low_improving{=boolean}]

[/battery_low_degrading{=boolean}]

[/battery_good{=boolean}]

[/battery_recondition_start{=boolean}]

[/battery_dead_finished_recondition{=boolean}]

[/battery_low_finished_recondition{=boolean}]

[/battery_good_finished_recondition{=boolean}]

[/config_change{=boolean}]

[/adapter_failure{=boolean}]

[/container_change{=boolean}]

[/drive_letter{=boolean}]

[/file_system{=boolean}]

[/pause{=boolean}]

[/resumed{=boolean}]

[/failover_change{=boolean}]

[/enclosure_fan{=boolean}]

[/enclosure_fan_change{=boolean}]

[/enclosure_power{=boolean}]

[/enclosure_power_change{=boolean}]

[/enclosure_temp_abnormal{=boolean}]

[/enclosure_temp_over{=boolean}]

[/not_mirror{=boolean}]

[/mirror_no_space{=boolean}]

[/no_unmirror{=boolean}]

[/mirror_failover{=boolean}]

[/mirror_no_create{=boolean}]

[/mirror_no_failover{=boolean}]

[/mirror_drive_failure{=boolean}]

[/r5_rebuild_start{=boolean}]

[/r5_rebuild_restart{=boolean}]

[/r5_drive_failure{=boolean}]

[/r5_no_rebuild{=boolean}]

[/r5_no_scrub{=boolean}]

[/r5_no_failover{=boolean}]

[/r5_no_space{=boolean}]

[/r5_rebuild_done{=boolean}]

[/smart_fpt_exceeded{=boolean}]

[/smart_warning{=boolean}]

[/smart_warning_temp{=boolean}]

[/smart_warning_degraded{=boolean}]

{string} {string}

Parameters

{string}

Specifies the e-mail address of the recipient to whom you want to send the e-mail message.

{string}

Specifies a string that appears in the Subject: line of the e-mail message. For example, if you enable (set) e-mail messages related to disk failure events, you might specify "Disk Error Message" for this parameter. If you enable e-mail messages related to all events, you might specify "Errors for All Events Message" for this parameter.

Switches

/computer{=string}

Specifies the computer name that contains a controller from which you want to enable (set) e-mail message reporting for one or more events. If you do not specify a computer name, the command enables e-mail message reporting for events on the local computer.

This switch is supported only on Windows NT.

/domain{=string}

Specifies the domain in which the specified computer resides.

If you do not specify this switch, the command assumes the local domain.

This switch is supported only on Windows NT.

/all{=boolean}

Specifies whether to enable (set) e-mail message reporting for all events. If you set this switch to TRUE, the command enables e-mail message reporting for all events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for all events.

This switch is supported only on Windows NT.

/container{=boolean}

Specifies whether to enable (set) e-mail message reporting for container-related (ContainerChange event type) events. If you set this switch to TRUE, the command enables e-mail message reporting for container-related events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for container-related events.

This switch is supported only on Windows NT.

The following shows an example of a ContainerChange event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 One or more containers have changed their state on controller : 
"afa0".
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/fatal{=boolean}

Specifies whether to enable (set) e-mail message reporting for fatal events. If you set this switch to TRUE, the command enables e-mail message reporting for fatal events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for fatal events.

This switch is supported only on Windows NT.

/smart{=boolean}

Specifies whether to enable (set) e-mail message reporting for SMART events. If you set this switch to TRUE, the command enables e-mail message reporting for SMART events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for SMART events.

This switch is supported only on Windows NT.

/battery{=boolean}

Specifies whether to enable (set) e-mail message reporting for all battery-related events. If you set this switch to TRUE, the command enables e-mail message reporting for all battery-related events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for all battery-related events.

This switch is supported only on Windows NT and only on controllers that support a battery.

/battery_dead{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state to dead (Battery Dead event type) event. This event occurs when a previously good or low battery changes to the dead state. If you set this switch to TRUE, the command enables e-mail message reporting for a battery changes state to dead event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state to dead events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a Battery Dead event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The state of the battery on controller : "afa0" is now dead.
 Computer : BULLDOG
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/battery_low_improving{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state from dead to low improving (Battery Low, Improving event type) event. This event occurs when a previously dead battery changes to the low improving state. If you set this switch to TRUE, the command enables e-mail message reporting for a battery changes state from dead to low improving event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state from dead to low improving events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a Battery Low, Improving event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The state of the battery on controller: "afa0" has improved to low.
 Computer : BULLDOG
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/battery_low_degrading{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state from good to low degrading (Battery Low, Degrading event type) event. This event occurs when a previously good battery changes to the low degrading state. If you set this switch to TRUE, the command enables e-mail message reporting for a battery changes state from good to low degrading event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state from good to low degrading events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a Battery Low, Degrading event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The state of the battery on controller : "afa0" has degraded to low.
 Computer : BULLDOG
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/battery_good{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state from dead or low to good (Battery good event type) event. This event occurs when a previously dead or low battery changes to the good state. If you set this switch to TRUE, the command enables e-mail message reporting for a battery changes state from dead or low to good event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state from dead or low to good events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a Battery good event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The state of the battery on controller : "afa0" is now good.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/battery_recondition_start{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state to a recondition start (BatteryReconditioning event type) event. This event occurs when you start a battery recondition operation with the controller battery_recondition command. If you set this switch to TRUE, the command enables e-mail message reporting for battery changes state to recondition start events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state to recondition start events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a BatteryReconditioning event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The battery on controller "afa0" has begun reconditioning.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/battery_dead_finished_recondition{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state from recondition completion to a battery is now dead (BatteryReconditionDead event type) event. This event occurs when a battery recondition operation with the controller battery_recondition command completes and the battery is now dead. If you set this switch to TRUE, the command enables e-mail message reporting for battery changes state from recondition completion to battery is now dead events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state from recondition completion to battery is now dead events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a BatteryReconditionDead event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The battery on controller "afa0" has finished reconditioning and 
is now dead.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Monday 13 April 1998 (Local Time)

 
/battery_low_finished_recondition{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state from recondition completion to a battery is now low (BatteryReconditionLow event type) event. This event occurs when a battery recondition operation with the controller battery_recondition command completes and the battery is now low. If you set this switch to TRUE, the command disables e-mail message reporting for battery changes state from recondition completion to battery is now low events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state from recondition completion to battery is now low events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a BatteryReconditionLow event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The battery on controller "afa0" has finished reconditioning and 
is now low.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Monday 17 November 1997 (Local Time)

 
/battery_good_finished_recondition{=boolean}

Specifies whether to enable (set) e-mail message reporting for a battery changes state from recondition completion to a battery is now good (BatteryReconditionGood event type) event. This event occurs when a battery recondition operation with the controller battery_recondition command completes and the battery is now good. If you set this switch to TRUE, the command enables e-mail message reporting for battery changes state from recondition completion to battery is now good events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for battery changes state from recondition completion to battery is now good events.

This switch is supported only on Windows NT and only on controllers that support a battery.

The following shows an example of a BatteryReconditionGood event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The battery on controller "afa0" has finished reconditioning and 
is now good.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Tuesday 19 May 1998 (Local Time)

 
/config_change{=boolean}

Specifies whether to enable (set) e-mail message reporting for a configuration change (ConfigChange event type) event. If you set this switch to TRUE, the command enables e-mail message reporting for a configuration change event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for a configuration change event.

This switch is supported only on Windows NT.

The following shows an example of a ConfigChange event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 A Configuration Change occured on adapter : "afa0".
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/adapter_failure{=boolean}

Specifies whether to enable (set) e-mail message reporting for a controller failure (AdapterFailure event type) event. A controller failure event occurs when the controller fails. If you set this switch to TRUE, the command enables e-mail message reporting for controller failure events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for controller failure events.

This switch is supported only on Windows NT.

The following shows an example of an AdapterFailure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 The controller "afa0" sent the following text message.
 [Text of message from the controller goes here.]
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/container_change{=boolean}

Specifies whether to enable (set) e-mail message reporting for a container change (ContainerChange event type) event. A container change event occurs any time a container changes its type. If you set this switch to TRUE, the command enables e-mail message reporting for container change events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for container change events.

This switch is supported only on Windows NT.

The following shows an example of a ContainerChange event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 One or more containers have changed their state adapter : 
"afa0".
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/drive_letter{=boolean}

Specifies whether to enable (set) e-mail message reporting for a drive letter change (DriveLetterChange event type) event. A drive letter change event occurs when you use the container assign drive_letter command to assign a drive letter to a container or the container remove drive_letter command to remove a drive letter from a container. If you set this switch to TRUE, the command enables e-mail message reporting for drive letter change events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for drive letter change events.

This switch is supported only on Windows NT.

The following shows an example of a ContainerChange event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 A drive letter change occured on container (0).
 Controller : "afa0"
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/file_system{=boolean}

Specifies whether to enable (set) e-mail message reporting for a file system change (FileSystemChange event type) event. A file system change event occurs when you use the container format command to create a file system on a container or the container remove command to remove a file system from a container. If you set this switch to TRUE, the command enables e-mail message reporting for file system change events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for file system change events.

This switch is supported only on Windows NT.

The following shows an example of a FileSystemChange event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 A file system change occured on container (0).
 Controller : "afa0"
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/pause{=boolean}

Specifies whether to enable (set) e-mail message reporting for a controller pause (Paused event type) event. A controller pause event occurs when you use the controller pause_io command to pause all I/O activity on the open controller. If you set this switch to TRUE, the command enables e-mail message reporting for controller pause events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for controller pause events.

This switch is supported only on Windows NT.

The following shows an example of a Paused event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 The controller "afa0" was paused.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/resumed{=boolean}

Specifies whether to enable (set) e-mail message reporting for a controller resume (Resumed event type) event. A controller resume event occurs when you use the controller resume_io command to resume all I/O activity on the open controller. If you set this switch to TRUE, the command enables e-mail message reporting for controller resume events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for controller resume events.

This switch is supported only on Windows NT.

The following shows an example of a Resumed event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 The controller "afa0" was resumed.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/failover_change{=boolean}

Specifies whether to enable (set) e-mail message reporting for a failover change (FailoverChange event type) event. A failover change event occurs when you use the container set failover command to assign one or more failover disks to a container or the container remove failover command to remove one or more failover disks from a container. If you set this switch to TRUE, the command enables e-mail message reporting for failover change events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for failover change events.

This switch is supported only on Windows NT.

The following shows an example of a FailoverChange event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 A Failover Change occured on "afa0".
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/enclosure_fan{=boolean}

Specifies whether to enable (set) e-mail message reporting for an enclosure fan failure (Enclosure Fan Failure event type) event. An enclosure fan failure event occurs when a fan in a SAF-TE enclosure management device fails. If you set this switch to TRUE, the command enables e-mail message reporting for enclosure fan failure events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for enclosure fan failure events.

This switch is supported only on Windows NT.

The following shows an example of an Enclosure Fan Failure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Fan 1 failed in enclosure 0.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/enclosure_fan_change{=boolean}

Specifies whether to enable (set) e-mail message reporting for an enclosure fan staus change (Enclosure fan status change event type) event. An enclosure fan status change event occurs when a fan in a SAF-TE enclosure management device changes speed. Fans typically run at full speed, 1/4 the full speed, 1/2 the full speed, or 3/4 the full speed. You can set a fan's speed by using the enclosure set fan command. If you set this switch to TRUE, the command enables e-mail message reporting for enclosure fan status change events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for enclosure fan status change events.

This switch is supported only on Windows NT.

The following shows an example of an Enclosure fan status change event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Fan 1 changed in enclosure 0.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/enclosure_power{=boolean}

Specifies whether to enable (set) e-mail message reporting for an enclosure power supply failure (Enclosure Power Supply Failure event type) event. An enclosure power supply failure event occurs when a power supply in a SAF-TE enclosure management device fails. If you set this switch to TRUE, the command enables e-mail message reporting for enclosure power supply failure events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for enclosure power supply failure events.

This switch is supported only on Windows NT.

The following shows an example of an Enclosure Power Supply Failure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Power Supply 1 failed in enclosure 0.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/enclosure_power_change{=boolean}

Specifies whether to enable (set) e-mail message reporting for an enclosure power supply change (Enclosure power supply change event type) event. An enclosure power supply change event occurs when one of the power supplies in a SAF-TE enclosure management device is turned on or off. You can turn a power supply on or off by using the enclosure set power command. If you set this switch to TRUE, the command enables e-mail message reporting for enclosure power supply change events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for enclosure power supply change events.

This switch is supported only on Windows NT.

The following shows an example of an Enclosure Power Supply Failure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Power Supply 1 failed in enclosure 0.
 Power Supply 1 changed in enclosure 0.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)

 
/enclosure_temp_abnormal{=boolean}

Specifies whether to enable (set) e-mail message reporting for an abnormal enclosure temperature (Enclosure Abnormal Temperature event type) event. An abnormal enclosure temperature event occurs when a SAF-TE enclosure management device reports a high temperature. If you set this switch to TRUE, the command enables e-mail message reporting for abnormal enclosure temperature events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for abnormal enclosure temperature events.

This switch is supported only on Windows NT.

The following shows an example of an Enclosure Abnormal Temperature Failure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 The enclosure 0 reported an abnormal temperature for sensor 2.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Sunday 13 April 1997 (Local Time)

 
/enclosure_temp_over{=boolean}

Specifies whether to enable (set) e-mail message reporting for an enclosure temperature over threshold (Enclosure Temperature above threshold event type) event. An enclosure temperature over threshold event occurs when a SAF-TE enclosure management device reports that a temperature is above a user set threshold. If you set this switch to TRUE, the command enables e-mail message reporting for enclosure temperature over threshold events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for enclosure temperature over threshold events.

This switch is supported only on Windows NT.

The following shows an example of an Enclosure Temperature above threshold event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 The enclosure 0 reported a temperature reading above the 
threashold for sensor 1.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Sunday 13 April 1997 (Local Time)

 
/not_mirror{=boolean}

Specifies whether to enable (set) e-mail message reporting for a failed mirror failover (NoMirror event type) event. A failed mirror failover event occurs when a mirror is not in the mirroring state (that is, the mirror is broken). If you set this switch to TRUE, the command enables e-mail message reporting for failed mirror failover events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for failed mirror failover events.

This switch is supported only on Windows NT.

The following shows an example of a NoMirror event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 The container (0) on controller "afa0" is not mirroring.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Sunday 13 April 1997 (Local Time)

 
/mirror_no_space{=boolean}

Specifies whether to enable (set) e-mail message reporting for a no space for mirror failover (MirrorNoSpace event type) event. A no space for failover event occurs when a failover operation fails to occur because there is no space on any failover drives. If you set this switch to TRUE, the command enables e-mail message reporting for no space for mirror failover events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for no space for mirror failover events.

This switch is supported only on Windows NT.

The following shows an example of a MirrorNoSpace event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Failover was not started on container (1) on controller "afa0" 
because no space was found on the failover devices.
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Sunday 13 April 1997 (Local Time)

 
/no_unmirror{=boolean}

Specifies whether to enable (set) e-mail message reporting for an unmirror failure (NoUnMirror event type) event. An unmirror failure event occurs when you use the container unmirror command to unmirror a mirror set and the operation fails. If you set this switch to TRUE, the command enables e-mail message reporting for unmirror failure events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for unmirror failure events.

This switch is supported only on Windows NT.

The following shows an example of a NoUnMirror event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Failover was not started because the mirror set could not be 
unmirrored.
 Container : (1)
 Controller : "afa0"
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Sunday 13 April 1997 (Local Time)

 
/mirror_failover{=boolean}

Specifies whether to enable (set) e-mail message reporting for a mirror failover (FailoverStarted event type) event. A mirror failover event occurs when a failover occurs on a mirror set. If you set this switch to TRUE, the command enables e-mail message reporting for mirror failover events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for mirror failover events.

This switch is supported only on Windows NT.

The following shows an example of a FailoverStarted event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 Failover has started on container (1) on controller "afa0".
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Sunday 13 April 1997 (Local Time)

 
/mirror_no_create{=boolean}

Specifies whether to disable (clear) e-mail message reporting for not enough memory to create a mirror container (MirrorNoCreate event type) event. A not enough memory to create a mirror container event occurs when a mirror set creation operation failed because there was not enough memory on the controller. If you set this switch to TRUE, the command disables e-mail message reporting for not enough memory to create mirror container events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for not enough memory to create mirror container events.

This switch is supported only on Windows NT.

The following shows an example of a MirrorNoCreate event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 A mirror create failure occured. There was not enough adapter 
memory to complete the operation.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Sunday 13 April 1997 (Local Time)

 
/mirror_no_failover{=boolean}

Specifies whether to disable (clear) e-mail message reporting for a no failover assign (MirrorNoFailover event type) event. A no failover assign event occurs when a disk in a mirror set failed and failover could not be started because no other failover disks were assigned. If you set this switch to TRUE, the command disables e-mail message reporting for no failover assign events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for no failover assign events.

This switch is supported only on Windows NT.

The following shows an example of a MirrorNoFailover event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 There was no failover space assigned to a failed mirror 
container.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Sunday 13 April 1997 (Local Time)

 
/mirror_drive_failure{=boolean}

Specifies whether to enable (set) e-mail message reporting for a mirror drive failure (MirrorDriveFailure event type)event. A mirror drive failure event occurs when a disk in a mirror set failed. If you set this switch to TRUE, the command enables e-mail message reporting for mirror drive failure events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for mirror drive failure events.

This switch is supported only on Windows NT.

The following shows an example of a MirrorDriveFailure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:James Bond
 Cc:
 Subject:afa0 controller message
 A drive in a mirror set failed.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Sunday 13 April 1997 (Local Time)

 
/r5_rebuild_start{=boolean}

Specifies whether to enable (set) e-mail message reporting for a RAID-5 rebuild start (R5RebuildStart event type) event. A rebuild start event occurs when a rebuild operation starts on a RAID-5 container. If you set this switch to TRUE, the command enables e-mail message reporting for RAID-5 rebuild start events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for RAID-5 rebuild start events.

This switch is supported only on Windows NT.

The following shows an example of a R5RebuildStart event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 RAID5 failover and rebuild started.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_rebuild_restart{=boolean}

Specifies whether to enable (set) e-mail message reporting for a RAID-5 rebuild restart (R5RebuildRestart event type) event. A RAID-5 rebuild restart event occurs when a previously interrupted rebuild of a RAID-5 container restarts the build operation. If you set this switch to TRUE, the command enables e-mail message reporting for RAID-5 rebuild restart events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for RAID-5 rebuild restart events.

This switch is supported only on Windows NT.

The following shows an example of a R5RebuildRestart event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 RAID5 rebuild restarted.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_drive_failure{=boolean}

Specifies whether to enable (set) e-mail message reporting for a RAID-5 drive failure (R5DriveFailure event type) event. A RAID-5 drive failure event occurs when a drive in a RAID-5 set fails. If you set this switch to TRUE, the command enables e-mail message reporting for RAID-5 drive failure events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for RAID-5 drive failure events.

This switch is supported only on Windows NT.

The following shows an example of a R5DriveFailure event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 A storage device in a RAID5 set failed.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_no_rebuild{=boolean}

Specifies whether to enable (set) e-mail message reporting for a no controller memory for a RAID-5 rebuild (R5NoRebuild event type) event. A no controller memory for a RAID-5 rebuild event occurs when a RAID-5 rebuild operation fails because there is not enough controller memory. If you set this switch to TRUE, the command enables e-mail message reporting for no controller memory for RAID-5 rebuild events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for RAID-5 rebuild events.

This switch is supported only on Windows NT.

The following shows an example of a R5NoRebuild event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 A RAID5 rebuild start failure occured. There was not enough 
adapter memory to complete the operation.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_no_scrub{=boolean}

Specifies whether to enable (set) e-mail message reporting for a not enough memory for RAID-5 scrub (R5NoScrub event type) event. A not enough memory for a RAID-5 scrub event occurs when a RAID-5 scrub operation fails because there is not enough controller memory. If you set this switch to TRUE, the command enables e-mail message reporting for not enough memory for RAID-5 scrub events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for not enough memory for RAID-5 scrub events.

This switch is supported only on Windows NT.

The following shows an example of a R5NoScrub event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 A RAID5 scrub start failure occured. There was not enough 
adapter memory to complete the operation.
 Container : (0)
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_no_failover{=boolean}

Specifies whether to enable (set) e-mail message reporting for a no failover assigned (R5NoFailover event type) event. A no failover assigned event occurs when a RAID-5 failover operation fails because there are no failover devices assigned to the RAID-5 container. If you set this switch to TRUE, the command enables e-mail message reporting for no failover assigned events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for no failover assigned events.

This switch is supported only on Windows NT.

The following shows an example of a R5NoFailover event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 There was no failover space assigned to the RAID5 container 
(0).
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_no_space{=boolean}

Specifies whether to enable (set) e-mail message reporting for a no space on a RAID-5 failover disk (R5NoSpace event type) event. A no space on a RAID-5 failover disk event occurs when a failover operation fails on a RAID-5 set because there was not enough space on a failover disk. If you set this switch to TRUE, the command enables e-mail message reporting for no space on a RAID-5 failover disk event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for no space on a RAID-5 failover disk event.

This switch is supported only on Windows NT.

The following shows an example of a R5NoSpace event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 There was no space found on the failover devices assigned to 
the RAID5 container (0).
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/r5_rebuild_done{=boolean}

Specifies whether to enable (set) e-mail message reporting for a RAID-5 rebuild completion (R5RebuildDone event type) event. A RAID-5 rebuild completion event occurs when a RAID-5 rebuild operation completes. If you set this switch to TRUE, the command enables e-mail message reporting for RAID-5 rebuild completion events.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for RAID-5 rebuild completion events.

This switch is supported only on Windows NT.

The following shows an example of a R5RebuildDone event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 The rebuild for the RAID5 container (0) completed.
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/smart_fpt_exceeded{=boolean}

Specifies whether to enable (set) e-mail message reporting for a disk exceeds its failure prediction threshold (Smart fpt exceeded event type) event. This event occurs when the number of recoverable disk errors reported exceeds the maximum that the disk can report. If you set this switch to TRUE, the command enables e-mail message reporting for a disk exceeds its failure prediction threshold event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for a disk exceeds its failure prediction threshold event.

This switch is supported only on Windows NT.

The following shows an example of a Smart fpt exceeded event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 The disk (1,2,0) on controller afa0 has exceeded its threshold 
for SMART errors.
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Monday 17 November 1997 (Local Time)

 
/smart_warning{=boolean}

Specifies whether to enable (set) e-mail message reporting for a disk reporting a SMART degraded warning (Smart Warning event type) event. This event occurs whenever the system reports a SMART degraded warning. If you set this switch to TRUE, the command enables e-mail message reporting for a disk reporting a SMART degraded warning event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for a disk reporting a SMART degraded warning event.

This switch is supported only on Windows NT.

The following shows an example of a Smart Warning event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 The disk (1,2,0) on controller afa0 reports a SMART error.
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Sunday 13 April 1997 (Local Time)

 
/smart_warning_temp{=boolean}

Specifies whether to enable (set) e-mail message reporting for a disk reporting a SMART temperature warning (Temperature warning event type) event. This event occurs whenever the system reports a SMART temperature range exceeds a specific temperature. If you set this switch to TRUE, the command enables e-mail message reporting for a disk reporting a SMART temperature warning event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for a disk reporting a SMART temperature warning event.

This switch is supported only on Windows NT.

The following shows an example of a Temperature warning event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 The disk (1,2,0) on controller afa0 reports temperature has 
exceeded limit.
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Sunday 13 April 1997 (Local Time)

 
/smart_warning_degraded{=boolean}

Specifies whether to enable (set) e-mail message reporting for a disk reporting a SMART degraded warning (Degraded Warning event type) event. This event occurs whenever the system reports a SMART degraded warning. If you set this switch to TRUE, the command enables e-mail message reporting for a disk reporting a SMART degraded warning event.

This switch defaults to FALSE, which means that the command does not enable e-mail message reporting for a disk reporting a SMART degraded warning event.

This switch is supported only on Windows NT.

The following shows an example of a Degraded Warning event type e-mail message:

 From:afa0@mrhyde.ntc.dell.com
 To:Sam Spade
 Cc:
 Subject:afa0 controller message
 The disk (1,2,0) on controller afa0 reports a SMART error.
 Controller : "afa0"
 Host MRHYDE
 Time 17:44:36 (Local Time)
 Date Sunday 13 April 1997 (Local Time)

Examples

The following example shows how to enable (set) the following event types:

• Configuration change events
• Drive letter change events
• File system change events

   AFA0> mail set message /config_change /drive_letter /file_system 
  "stemplar@dell.com" "afa0 controller message"
   Executing: mail set message /config_change=TRUE /drive_letter=TRUE 
  /file_system=TRUE "stemplar@dell.com" "afa0 controller message"
  

The following examples show sample e-mail messages related to the previously listed events:

 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 Subject:afa0 controller message
 A configuration change occured on controller "afa0".
 Computer : MRHYDE
 TIME : 17:44:36 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)
 
 
 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 A drive letter change occured on container (0).
 Controller : "afa0"
 Computer : MRHYDE
 TIME : 17:44:34 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)
 
 
 From:afa0@mrhyde.ntc.dell.com
 To:Simon Templar
 Cc:
 A file system change occured on container (0).
 Controller : "afa0"
 Computer : MRHYDE
 TIME : 17:43:35 (Local Time)
 DATE : Wednesday 06 August 1997 (Local Time)
 

Related Information

mail Commands:

• mail clear message (mail clear message)
• mail show message (mail show message)

mail set server

To set the computer that processes e-mail messages for controller events, use the mail set server command.

Command Availability

This command is supported only on Windows NT.

Syntax

mail set server [/computer{=string}] [/domain{=string}] {string}

Parameters

{string}

Specifies the name of the computer that will process e-mail messages for controller events. The computer that functions as a mail server must support the Simple Mail Transport Protocol (SMTP).

Switches

/computer{=string}

Specifies the name of the computer whose associated mail server you want to set. If you do not specify a computer name, the command assumes the local computer.

This switch is supported only on Windows NT.

/domain{=string}

Specifies the domain in which the specified computer resides.

If you do not specify this switch, the command assumes the local domain.

This switch is supported only on Windows NT.

Examples

The following example shows that ELEMENTLAD is the name of the server handling e-mail messages for controller events:

AFA0> mail set server "elementlad"

Executing: mail set server "elementlad"

Related Information

mail Commands:

• mail show server (mail show server)

mail show message

To display e-mail message format information for one event type, several or more event types, or all event types, use the mail show message command. You must have previously enabled the message with the mail set message command to display the message format information.

This command provides a switch for each event type, so that you can specifically indicate which events for which you want to display e-mail message information.

Command Availability

This command is supported only on Windows NT.

Notes

If you issue a mail show message command without using any of the switches, the command displays all e-mail message formats for those events that you previously set with the mail set message command.

The following switches allow you to display e-mail message format information for many events:

• /all (all events)
• /container (container-related events)
• /fatal (fatal events)

Events Displayed with the /all Switch

Table 9 lists all of the events for which the command displays e-mail message format information when you use the /all switch. The table also lists each event's associated message type. This message type appears in the Message: line of the e-mail message.

 From: drjekyll@bulldog.dell.com  Sent:Wed 8/6/97 1:55 PM
 To: Simon Templar
 Cc:
 Subject: A test message.
 This is a test mail message.