Skip to main content
NetApp Knowledge Base

TieBreaker 1.6 - MCC Validation failed. Reason : Authentication failed for host

  1. Last updated
  2. Save as PDF
Views:
347
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • TieBreaker 1.6

Issue

  • Adding new MetroCluster shown as successful
    Successfully added monitor to NetApp MetroCluster Tiebreaker software.
  • monitor show-status reporting authentication issues
    :> monitor show -status
    MetroCluster: MetroCluster1
    Disaster: false
    Monitor State: MCC Validation failed. Reason : Authentication failed for host and Authentication failed for host

  • TieBreaker log showing authentication issues2024-01-01 10:00:00,153 INFO [Thread-2] [MCCInfo] Invoking GET https://1.1.1.1/api/cluster/metrocluster/?return_timeout=20
    2024-01-01 10:00:00,203 INFO [Thread-2] [DataBaseProperties] Loading KeyStore
    2024-01-01 10:00:00,274 INFO [Timer-0] [RestClient] Invoking postEMS
    2024-01-01 10:00:00,349 INFO [Timer-0] [DataBaseProperties] Loading KeyStore
    2024-01-01 10:00:00,409 ERROR [Thread-2] [RestClient] Response code : 401
    2024-01-01 10:00:00,410 ERROR [Thread-2] [MCCDiscovery] Discover of cluster MetroCluster1 failed. Reason : Authentication failed for host.

 

 

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.