Skip to main content
NetApp Knowledge Base

Object store unavailable due to InterCluster LIF down during node reboot

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

Applies to

  • ONTAP 9
  • FabricPool

Issue

  • After a node reboot, multiple ports on the node show a link up event.
  • During the link up process, the InterCluster LIF shows objstore.interclusterlifDown temporarily.
  • The object.store.unavailable error is logged, indicating the object store is unreachable.
  • Shortly after, the InterCluster LIF recovers, and the object.store.available message is logged.
Example:
Sat Jan 31 12:09:12 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port e3a.
Sat Jan 31 12:09:12 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port e9a.
Sat Jan 31 12:09:12 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port e9b.
Sat Jan 31 12:09:12 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port a0b.
Sat Jan 31 12:09:12 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port a0b-22.
Sat Jan 31 12:09:12 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port e3b.
Sat Jan 31 12:09:13 +0900 [Node1: OscLowPriThreadPool_3: objstore_interclusterlifDown_1:error]: params: {'sysVserverID': 'x', 'nodeUuid': 'xxxx'}
Sat Jan 31 12:09:13 +0900 [Node1: OscLowPriThreadPool_3: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "FabricPool" from node xxxx. Reason: Inter-cluster LIF not configured.
Sat Jan 31 12:09:14 +0900 [Node1: vifmgr: vifmgr.lifbeinghosted:notice]: LIF Node1-intcls1 (on virtual server 4294967295), IP address x.x.x.x, previously marked as down, is now up and serving data on node Node1, port a0b-22.
Sat Jan 31 12:09:14 +0900 [Node1: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF Node1-intcls1 (on virtual server 4294967295), IP address x.x.x.x, is now hosted on node Node1, port a0b-22.
Sat Jan 31 12:09:15 +0900 [Node1: OscLowPriThreadPool_1: object.store.available:notice]: Able to connect to the object store "FabricPool" from node xxxx.
Sat Jan 31 12:09:16 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port a0a.
Sat Jan 31 12:09:16 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port a0a-3.
Sat Jan 31 12:09:16 +0900 [Node1: vifmgr: vifmgr.portup:notice]: A link up event was received on node Node1, port a0a-22.

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.