topic Cluster join failure and storage failover show the status of "Kernel loaded." in ONTAP Discussions

Cluster join failure and storage failover show the status of "Kernel loaded."

chenguanghui — Fri, 11 Oct 2024 14:09:03 GMT

Hi:

I had two very frustrating experiences today and I need some help:

1. Today I performed initial setup on both ends and prepared to create a cluster, but I found that one node would not join in despite my efforts. Just as I was about to give up, it suddenly joined successfully. Why is that? My system version is 9.14.1p16, and my device is a FAS2720.

2.Five minutes after the cluster is successfully created, I check the storage failover show and find that the status of controller A is kernel loaded. Finally, I check that the status of controller A is abnormal. The content of the error is like this:Waiting for giveback...(Press Ctrl-C to abort wait)
Waiting for giveback...(Press Ctrl-C to abort wait)Entering FM state:5 because mbFound:0 local in headswap:0
Entering FM state:5 because mbFound:0 local in headswap:0
Entering FM state:5 because mbFound:0 local in headswap:0

What should I do in this situation?

Thank you !

Wish you a happy life

Re: Cluster join failure and storage failover show the status of "Kernel loaded."

TMACMD — Fri, 11 Oct 2024 14:27:21 GMT

Make sure everything is cabled correctly.

Internal disks all seated correctly?

external drives attached to the correct ports?

BOTH cluster ports connected?

BOTH cluster ports up/active/home?

Re: Cluster join failure and storage failover show the status of "Kernel loaded."

chenguanghui — Sat, 12 Oct 2024 01:21:29 GMT

Hi:

All of this is in place, the ports are plugged in normally, and they are all healthy, but I just don't know why this is happening, which is weird

Re: Cluster join failure and storage failover show the status of "Kernel loaded."

pmidhun — Tue, 29 Oct 2024 10:41:42 GMT

This KB article might help you
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Entering_FM_state_5_because_mbFound_0_Resolution_guide

If issue persists, please open a support case if you have valid entitlements