Skip to main content

Requesting notification of issues encountered in nondisruptive upgrades

If you do not plan to monitor the progress of the upgrade process, it is a good practice to request EMS notifications of errors that might require manual intervention. Alternatively, you can configure an AutoSupport message to send to your internal support organization.

Before you begin

You must be a cluster administrator to perform this task.

About this task

It is useful to set up notifications such that they are sent in case of a problem during the upgrade process. In particular, the callhome.andu.pausederr message contains useful troubleshooting information.

Note
If your cluster is not configured to send AutoSupport messages, a copy of the notification is saved locally.
  1. Required: Request notification of issues encountered in nondisruptive upgrade.

    EMS express configuration

  2. Before initiating a nondisruptive upgrade, if AutoSupport is enabled on this cluster, suppress automatic case creation by invoking an AutoSupport message. If AutoSupport is not enabled on this cluster, then ignore this step: system node autosupport invoke -node * -type all -message MAINT=xh

    x is the duration of the maintenance window in hours.
    Note
    The message will notify technical support of this maintenance task so that automatic case creation is suppressed during the maintenance window.

    Example

    This command suppresses automatic case creation for two hours:

    cluster::*> system node autosupport invoke -node * -type all -message MAINT=2h
  3. After the nondisruptive upgrade, reenable automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=END

    Example

    The command reenables automatic case creation:

    cluster::*> system node autosupport invoke -node * -type all -message MAINT=END