Skip to main content
NetApp Knowledge Base

Cluster port didn't revert to its home port after port attributes modification even with auto-revert enabled

Views:
238
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9

Issue

  • After autonegotiate-admin status of cluster port was modified to true, LIF on the port didn't auto-reverted even with auto-revert enabled:

Thu Jun 23 2022 16:59:57 +09:00 [kern_audit:info:2243]  :: Cluster:console :: Cluster:admin :: network port modify -node Nodename1 -port e0c -mtu 9000 -autonegotiate-admin true -duplex-admin auto -speed-admin auto :: Pending

  • EMS shows lif03 was moved to its failover target port e0d:

Thu Jun 23 17:01:30 +0900 [Nodename01: vifmgr: vifmgr.lifmoved.linkdown:notice]: LIF Nodename01-lif02 (on virtual server 4294967293), IP address 169.254.xx.xx, is being moved to node Nodename01, port e0d.
Thu Jun 23 17:01:31 +0900 [Nodename01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF Nodename01-lif02 (on virtual server 4294967293), IP address 169.254.xx.xx, is now hosted on node Nodename01, port e0d.

  • NETWORK-INTERFACE.XML shows lif03 not in home:

Cluster port

 

 

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.