Skip to main content
NetApp Knowledge Base

All nodes detects cpeer.unavailable:alert due to mgwd restart in the peered cluster

  1. Last updated
  2. Save as PDF
Views:
1,186
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

ONTAP 9.3
 

Issue

  • All nodes detect cpeer.unavailable:alert at almost same time.

[＜NODE＞: mgwd: cpeer.unavailable:alert]: Peer cluster ＜CLUSTER_NAME＞ is no longer available.

  • The mgwd process in one or more nodes in the peered cluster has restarted due to error.

Example:

[＜NODE＞: mgwd: ucore.panicString:error]: 'mgwd: Received SIGSEGV (Signal 11) at RIP 0x80fe217ca accessing address 0x40 (pid 2261, uid 0, timestamp 1588431655)'
[＜NODE＞: spmd: spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 2261 exited as a result of signal normal exit (0). The subsystem will attempt to restart.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.