ALERT

This message occurs when the specified Vserver initialization was skipped due to a user-initiated abort. Giveback was allowed to succeed—​in a degraded state—​to allow further recovery. LUNs in the Vserver might not be accessible or might not be accessible on all paths.

Resolve the previously identified fault for which the abort was issued, and then restart SAN initialization on the node by using the "debug san node restart-vserver-initialization" command.

Vserver "%s" was not initialized due to a user-initiated abort request. SAN service for this Vserver might be degraded or unavailable on this node.

vserver (STRING): Name of the Vserver.

ALERT

This message occurs when there is a problem initializing the SAN Kernel Agent for one or more Vservers. LUNs in the affected Vserver(s) might not be accessible or might not be accessible via all paths.

Perform a planned takeover of the node with the failure followed by a giveback.

There was a problem initializing the SAN Kernel Agent for one or more Vservers. Vserver: %s. Reason: %s.

vserver (STRING): Name of the Vserver for which the SAN Kernel Agent failed to initialize.
error (STRING): Error encountered while initializing the SAN Kernel Agent for the Vserver.