ECS: OBS: Symptom ID 12024 - Geo test connection failed

Zusammenfassung: This alert is added to show that the Geo test connection failed.

Dieser Artikel gilt für Dieser Artikel gilt nicht für Dieser Artikel ist nicht an ein bestimmtes Produkt gebunden. In diesem Artikel werden nicht alle Produktversionen aufgeführt.

Symptome

Symptom Code Severity Description Condition
12024 ERROR

Test TLS/HTTP connectivity failed during local/remote call. Please resolve remote connection problem for TLS/HTTP connection. The failed connections are:

<node IP> to <node IP>: caused by: <error message>
<node IP> to <node IP>: caused by: <error message>

Geo test connection failed

Ursache

This alert is sent in the following cases:

Case 1: Single VDC switch to HTTPS case

  • Upgraded the system to 4.3
  • User tries to test the connection to see if it can switch Geo connection to HTTPS, but encounters an error.

Case 2: Multiple VDCs switch to HTTPS case

  • Upgraded the system to 4.3
  • User has uploaded Geo TLS CA and Certificates for all the VDCs following the admin guide.
  • User tries to test the connection to see if it can switch Geo connection to HTTPS, but encounters an error.

Case 3: Single or multiple VDC's fallback to HTTP case

  • Upgraded the system to 4.3 and has successfully switch the Geo connections to HTTPS.
  • For some emergency case, the user wants to fallback Geo connection to HTTP.
  • Customer uses provided API to start Geo receiver HTTP server.
  • User tries to test HTTP connection to see if it can fallback Geo connection to HTTP, but encounters an error.

Lösung

For case 1 and 2, switch to the HTTPS case. Use the below API to check again if the test connection is good or not.

// SSH to one node of the cluster
cluster_ip=localhost

// Get authentication token of management API
auth_token=$(curl -s -k -I -u root:ChangeMe https://${cluster_ip}:4443/login | grep X-SDS-AUTH-TOKEN | awk '{print $NF}')

// For switch to HTTPS case, use testConnection API. 
curl -kv -X 'GET'   'https://localhost:4443/rest/v1/geoConnection/testConnection'   -H 'accept: application/json'   -H 'X-SDS-AUTH-TOKEN: '${auth_token}

If it returns 200, the test connection is good. Otherwise, it returns an error message like the following (the error message might be different):

{"description":"Test HTTPS connection failed during remote call. Please resolve remote connection problem for HTTPS connection. The failed connections are:","failure":[{"source_ip":"10.10.10.10","source_node_name":"node01.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.10","target_node_name":"node01.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.10","source_node_name":"node01.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.11","target_node_name":"node02.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.12","source_node_name":"node03.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.12","target_node_name":"node03.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.12","source_node_name":"node03.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.13","target_node_name":"node04.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.14","source_node_name":"node05.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.14","target_node_name":"node05.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.14","source_node_name":"node05.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.15","target_node_name":"node06.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.16","source_node_name":"node07.d* Connection #0 to host localhost left intact
omain.com","source_zone_name":"vdc1","target_ip":"10.10.10.16","target_node_name":"node07.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.16","source_node_name":"node07.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.17","target_node_name":"node08.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"}]}

 

For case 3, fall back to the HTTPS case. Use the below API to check if the test HTTP connection is good or not.

// SSH to one node of the cluster
cluster_ip=localhost

// Get authentication token of management API
auth_token=$(curl -s -k -I -u root:ChangeMe https://${cluster_ip}:4443/login | grep X-SDS-AUTH-TOKEN | awk '{print $NF}')

// For fallback to HTTP case, use testHttpConnection API. 
curl -kv -X 'GET' 'https://localhost:4443/rest/v1/geoConnection/testHttpConnection' -H 'accept: application/json' -H 'X-SDS-AUTH-TOKEN: '${auth_token}

If it returns 200, the test connection is good. Otherwise, it returns an error message like the following (the error message might be different):

{"description":"Test HTTP connection failed during remote call. Please resolve remote connection problem for HTTPS connection. The failed connections are:","failure":[{"source_ip":"10.10.10.10","source_node_name":"node01.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.10","target_node_name":"node01.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.10","source_node_name":"node01.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.11","target_node_name":"node02.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.12","source_node_name":"node03.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.12","target_node_name":"node03.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.12","source_node_name":"node03.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.13","target_node_name":"node04.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.14","source_node_name":"node05.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.14","target_node_name":"node05.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.14","source_node_name":"node05.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.15","target_node_name":"node06.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.16","source_node_name":"node07.d* Connection #0 to host localhost left intact
omain.com","source_zone_name":"vdc1","target_ip":"10.10.10.16","target_node_name":"node07.domain.com","target_zone_name":"vdc1","error_message":"java.net.ConnectException: Connection refused (Connection refused)"},{"source_ip":"10.10.10.16","source_node_name":"node07.domain.com","source_zone_name":"vdc1","target_ip":"10.10.10.17","target_node_name":"node08.domain.com","target_zone_name":"vdc2","error_message":"java.net.ConnectException: Connection refused (Connection refused)"}]}

Contact Dell support if you see error messages like the above.

Artikeleigenschaften
Artikelnummer: 000445543
Artikeltyp: Solution
Zuletzt geändert: 14 Mai 2026
Version:  1
Antworten auf Ihre Fragen erhalten Sie von anderen Dell NutzerInnen
Support Services
Prüfen Sie, ob Ihr Gerät durch Support Services abgedeckt ist.