AIQUM occur Event: Storage Failover Node Status Down

Applies to

Issue

• AIQUM generate multiple false alerts for Storage Failover Node Status Down.Reason: up.

The following items are included:

⚠️Event: Storage Failover Node Status Down

(Last Seen:YYYY/MM/DD MM:SS)

The status of the node <node name> is down. Reason: up.

EVENT TRIGGER TIME

YYYY/MM/DD MM:SS

STATE

Obsolete

OBSOLETED CAUSE

The issue is fixed and the event is obsolete.

SEVERITY

Errror

IMPACT LEVEL

Risk

IMPACT AREA

Availability

ALERT SETTINGS

all_event_alert

LAST NOTIFICATION SENT

<customer mail address at YYYY/MM/DD MM:SS>

SEND BY

Email

SOURCE

<node name>

SOURCE TYPE

Node

ON CLUSTER

<cluster name>

• If you choose to SEND BY via email, the same content as AIQUM will be sent to the recipient via email.
• ONTAP mgwd.log: 

[kern_mgwd:info:3168] ZSM: KSMF REQ FAILED: sf-status - Timeout: Operation "ksmfRawZapi_iterator::get_imp()" took longer than 20 seconds to complete [from mgwd on node "<node_name>" (VSID: -3) to kernel at 127.0.0.1] [TO=20s TRT=20.000s =>127.0.0.1:951 CN=135804659/1] {ksmf_invoke:369}

[kern_mgwd:info:3168] ZAPI sf-status failed. Host: 127.0.0.1, Status: 1, Reason: ZSM - failed, status code = 571, extra = Timeout: Operation "ksmfRawZapi_iterator::get_imp()" took longer than 20 seconds to complete [from mgwd on node "<Node_Name>" (VSID: -3) to kernel at 127.0.0.1], took 20.000s, max 20s [127.0.0.1:951], Error: 13057

[kern_mgwd:info:3168] ZSM: KSMF REQ FAILED: file-usage-get - Timeout: Operation "ksmfRawZapi_iterator::get_imp()" took longer than 110 seconds to complete [from mgwd on node "<Node_name>" (VSID: 3) to kernel at 127.0.0.1] [TO=110s TRT=109.994s =>169.254.234.50:951 CN=135191001/1] {ksmf_invoke:369}