Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

  1. Kemp Support
  2. Knowledge Base
  3. Fault Tolerance

geocheck: Cluster Cluster <clustername> (IP address) failed

Updated: 

 

Information

 

Summary:

geocheck: Cluster Cluster <clustername> (IP address) failed
Environment:

Product: Loadmaster

Version: Any

Platform: Any

Application: N/A
Question/Problem Description:

Why customer is getting such errors on their logs
Steps to Reproduce:  
Error Message: 
2022-11-24T10:17:01+08:00 LB03 geocheck: Cluster Cluster DC2 (x.x.x.x) failed
2022-11-24T10:17:01+08:00 LB03 geocheck: Mapping vip.hostname. -> y.y.y.y failed

2022-11-24T10:17:13+08:00 LB03 geocheck: Cluster Cluster DC2 (x.x.x.x) back in service
2022-11-24T10:17:13+08:00 LB03 geocheck: Mapping vip.hostname. -> y.y.y.y back in service
Defect Number:  
Enhancement Number:  
Cause: There could be network or firewall maintenance that caused the error messages.
We conclude that likely cause is connectivity loss between HDC1 and HDC2 site. the device looses connectivity. As such, the services fail health checks, as such they are taken out of rotation, as such the service becomes unavailable, Then when connectivity is restored, they come back online.

Impact would be that the 2 sites would be operating independently each responding to DNS requests on their own without knowledge of other site. Until the connection is establish back.
Resolution:

Investigate the network switch or link between the 2 sites why the connection would be interrupted.

Otherwise rare interruptions are nothing to worry about if they recover in such short time.
Workaround:  
Notes:  
Was this article helpful?
0 out of 0 found this helpful

Comments

In this document