HA partner errors seen during cluster setup
This knowledge base was generated through a script and may contain formatting issues. For the accurate content, please refer to the WIP editor. WIP editor.
Applies to
- ONTAP 9
- FAS/AFF systems
Issue
- During Cluster setup, Below errors's are seen
Aug 02 19:00:25 [localhost:fmmb.disk.notAccsble:notice]: All Local mailbox disks are inaccessible.
Aug 02 19:00:25 [localhost:cf.fm.notkoverClusterDisable:error]: Failover monitor: takeover disabled (restart)
boot_from_disk:last_booted_OS:9.13.1P8
Aug 02 19:00:25 [localhost:cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of partner disabled (Controller Failover takeover disabled).
Aug 02 19:00:25 [localhost:kern.syslog.msg:notice]: domain xing mode: off, domain xing interrupt: false
Aug 02 19:00:25 [localhost:clam.invalid.config:error]: Local node (name=unknown, id=0) is in an invalid configuration for providing CLAM functionality. CLAM cannot determine the identity of the HA partner.
Architectural Performance Monitoring Information for CPU type 6, Model 85:
Version: 3
Counters: 8, Width: 48, Event Mask: 0x0000007f
Fixed Counters: 3, Width: 48
wrote key file "/tmp/rndc.key"
Aug 02 19:01:00 [localhost:monitor.globalStatus.critical:EMERGENCY]: Controller failover partner unknown. Controller failover not possible.
- Followed by Cluster setup wizard
Welcome to the cluster setup wizard.
You can enter the following commands at any time:
"help" or "?" - if you want to have a question clarified,
"back" - if you want to change previously answered questions, and
"exit" or "quit" - if you want to quit the cluster setup wizard.
Any changes you made before quitting will be saved.
You can return to cluster setup at any time by typing "cluster setup".
To accept a default or omit a question, do not enter a value.