Message "platform.typeId: Expected Controller ID: 3, Controller ID: 3, Partner ID: 7." observed in both nodes of Metrocluster
Applies to
- AFF/FAS platforms
- 2 node MetroCluster configuration
Issue
-
ONTAP Event Messages, in both nodes of a 2 nodes MetroCluster. Example:
CLUSTER01::*> event log show -event *Controller*
Time Node Severity Event
------------------- ------------ -------- ---------------------------
9/21/2023 17:40:58 CLUSTER01-01 DEBUG platform.typeId: Expected Controller ID: 3, Controller ID: 3, Partner ID: 7.
CLUSTER02::*> event log show -event *Controller*
Time Node Severity Event
------------------- ------------ -------- ---------------------------
9/21/2023 17:19:00 CLUSTER02-01 DEBUG platform.typeId: Expected Controller ID: 3, Controller ID: 3, Partner ID:7.
- Messages received from both nodes in the MetroCluster configuration, but with different headers. Example:
[CLUSTER02-01: monitor: platform.typeId:debug]: Expected Controller ID: 3, Controller ID: 3, Partner ID: 7.
[CLUSTER01-01: svc_queue_thread: platform.typeId:debug]: Expected Controller ID: 3, Controller ID: 3, Partner ID: 7.
[CLUSTER01-01: api_dpool_13: platform.typeId:debug]: Expected Controller ID: 3, Controller ID: 3, Partner ID: 7.
- No other alerts present related to the communications between the nodes.