create notification

This command creates a new notification rule.

Synopsis

• Create a new notification rule:

  create notification notification destination destination topic topic type type [description description]

Parameters

• description – A description for the notification rule.

• destination – Where to send the notification. This value must match the specified type. Valid values are:

  • email-addresses – One or more email addresses separated by commas.

  • script – A fully qualified path to a custom Bourne shell script used to manage the notification. The script must be executable by the root user.

  • snmp-host[:port] – An SNMP host. snmp-host is a valid SNMP host name and port is a valid port on the host.

• notification – A name for the notification rule.

• topic – The type of event to trigger the notification. Valid values are:

  • Action.Logical.FirmwareCreate – firmware created

  • Action.Logical.FirmwareDelete – firmware deleted

  • Action.Logical.JobCompleted – job completed

  • Action.Logical.JobStarted – job started

  • Action.Logical.JobTimedOut – job timed out

  • Action.Logical.ProfileCreate – OS profile created

  • Action.Logical.ProfileDelete – OS profile deleted

  • Action.Logical.OSDeployComplete – OS deployment completed

  • Action.Logical.OSDeployStart – OS deployment started

  • Action.Physical.AddCoreJobSuccess – base management feature added

  • Action.Physical.AgentIPJobSuccess – management feature configuration modified

  • Action.Physical.AlreadyKnown – server discovery already known

  • Action.Physical.Discovered – server discovered

  • Action.Physical.DriverNotFound – server discovery driver not found

  • Action.Physical.FWNotCompatible – firmware level is not compatible or supported

  • Action.Physical.InitialAddOsmJobSuccess – OS monitoring and base management feature added

  • Action.Physical.IPUnreachable – server discovery IP address unreachable

  • Action.Physical.LoadUpdateSuccess – OS update deployment succeeded

  • Action.Physical.LoadUpdateFailure – OS update deployment failed

  • Action.Physical.LoadUpdateCanceled – OS update deployment canceled

  • Action.Physical.MultipleAuths – server discovery multiple authorizations

  • Action.Physical.MultipleIPs – server discovery multiple IP addresses

  • Action.Physical.RemoteCmdFailure – remote command failed

  • Action.Physical.RemoteCmdSuccess – remote command succeeded

  • Action.Physical.RemoteCmdTimedOut – remote command timed out

  • Action.Physical.RemoteCmdUnauthorized – remote command unauthorized

  • Action.Physical.RemoveOsmJobSuccess – OS monitoring feature removed

  • Action.Physical.ServerDelete – server deleted

  • Action.Physical.ServerStateChange – server changed

  • Action.Physical.Unauthorized – server discovery unauthorized

  • Action.Physical.UnloadUpdateSuccess – OS update unload succeeded

  • Action.Physical.UnloadUpdateFailure – OS update unload failed

  • Action.Physical.UnloadUpdateCanceled – OS update unload canceled

  • EReport.Logical.ThresholdExceeded – OS resource threshold exceeded

  • EReport.Physical.DomainException – domain exception

  • EReport.Physical.Exception – remote command exception

  • EReport.Physical.FWMgmtException – firmware update exception

  • EReport.Physical.IOException – IO exception

  • EReport.Physical.OpGrpException – server discovery operation group exception

  • EReport.Physical.RemoteCmdUnknownOS – remote command unknown OS

  • EReport.Physical.RemoteCmdUnknownServer – remote command unknown server

  • EReport.Physical.ThresholdExceeded – hardware health threshold exceeded

  • Lifecycle.Logical.AddServer – server added to group

  • Lifecycle.Logical.ChangeSessionRole – session role changed

  • Lifecycle.Logical.CreateGroup – group created

  • Lifecycle.Logical.CreateUpdate – OS update created

  • Lifecycle.Logical.DeleteGroup – group deleted

  • Lifecycle.Logical.DeleteUpdate – OS update deleted

  • Lifecycle.Logical.RemoveServer – server removed from group

  • Lifecycle.Physical.DBUpdateFailed – firmware update database update failed

  • Lifecycle.Physical.InvalidState – firmware update invalid device state

  • Lifecycle.Physical.ObjectJobNotFound – server not found for operation

  • Lifecycle.Physical.UpdateSucceeded – firmware updated

• type – How to send the notification. Valid values are email (send to email address), script (send to custom script), or snmp (send to SNMP host).