Ha-config

Yesterday we booted up a new 7-mode cluster and saw a couple things:

• The systems were rebooting rather than going to the setup prompt.
• The systems’ NVRAM cards’ LED’s weren’t lit up correctly.
• And an error message:

Cannot determine whether configuration should be stand-alone or HA. Chassis is in default configuration, controller is in default configuration, and the non-volatile memory is dirty. Boot into Maintenance mode and run the 'ha-config modify' command to set the controller and chassis configuration to stand-alone or HA, as appropriate. Setting the wrong configuration might lead to data loss. If you need assistance, contact support.

Mar 07 04:01:46 [localhost:haosc.config.unknown.nv:ALERT]: Cannot determine whether configuration should be stand-alone or HA. Chassis is in default configuration, controller is in default configuration, and the nonvolatile memory is dirty.

This is what we did to fix it.

• Boot to special boot menu.
• Choose 5 to get to maintenance mode.
• Set these:
• ha-config modify chassis ha
• ha-config modify controller ha
• Reboot to setup prompt
• Configure initial setup
• Cf enable
• Verify via sysconfig that the systems knew their partner’s hostname and sysid now
• Cf disable
• Halt to loader prompt
• Printenv
• Verify psm-cc-config is true
• Verify partner-sysid was properly set
• Boot up and cf enable