Skip to main content
NetApp Knowledge Base

FabricPool unavailable after node reboot or network maintenance

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

Applies to

  • ONTAP 9
  • FabricPool

Issue

  • A node is rebooted due to maintenance such as ONTAP upgrade
  • The object store is noted as unavailable, cold tiered off data is inaccessible, and warm performance tier data access works normally
  • Errors logged in EMS log state the object store becomes unavailable on boot up after giveback
Sat Nov 21 14:41:56 -0600 [cluster1: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: ERROR: BUG in matching parameters (reason) to definition params: {'node_uuid': '9a842a8a-fbfa-11ea-a5c4-00a0987f363a', 'configname': 'stl_fabricpool'}
  • Prior to the node rebooting, errors were logged stating that TLS connection is failing to the object store and these are on-going
Sat Nov 21 12:05:01 CST [cluster1: mgwd: ktls.failed:notice]: "The TLS connections have failed several times with remote host '162.132.35.10' in IPspace '1', for which the latest reason given is: Errno: Connection reset by peer."
Sat Nov 21 12:15:16 CST [cluster1: mgwd: ktls.failed:notice]: "The TLS connections have failed several times with remote host '162.132.35.10' in IPspace '1', for which the latest reason given is: TLS: Handshake timed out."
  • TLS is enabled as per best practices

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?