Skip to main content
NetApp Knowledge Base

Running swanctl commands can potentially cause controller disruption

  1. Last updated
  2. Save as PDF
Views:
70
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

ONTAP 9

Issue

  • System crash with ucore due to swanctl command usage.

  • EMS Log reports below swanctl panic events:

    Tue Sep 26 16:17:04 +0100 [NetApp: swanctl: ucore.panicString:error]: 'swanctl: Received SIGSEGV (Signal 11) at RIP 0x80032afea accessing address 0 (pid 58191, uid 0, timestamp 1695741424)'
    Tue Sep 26 16:32:04 +0100 [NetApp: swanctl: ucore.panicString:error]: 'swanctl: Received SIGSEGV (Signal 11) at RIP 0x80032afea accessing address 0 (pid 62497, uid 0, timestamp 1695742324)'

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.