Applies to: BLAZE

Summary

This article provides a detailed breakdown of clustering error codes and resolution steps.

Error Codes and Resolutions

• 4070001: Subnet does not match 
  
  Servers must share the same Class C network prefix on OS network settings. 
  
  The IP address used for first clustering must remain consistent for future clustering. 
  
  For example, if a server uses the address 192.168.2.55, additional clustered servers must also use the 192.168.2.xxx network range. 
  
  You can find the IP address used for clustering from the system batch API via Postman. In the batch API response, ipAddressForCluster indicates the clustering IP address.
  
  
   
• 4070002: Version mismatch 
  
  Server versions must match for clustering.
  
  
   
• 4070003: Linked to cloud fail 
  
  The target server is already linked to the cloud. Unlink the server before adding it to a new cluster.
  
  
   
• 4070004: Clustered to another system 
  
  The target server already belongs to another cluster. 
  
  Reset the target server or detach it from the cluster before adding it to a new cluster.
  
  
   
• 4070006: Authenticate fail 
  
  When adding a server with existing system information (initial setup completed), the server requires a clustering password. If the password is incorrect, clustering fails due to an authentication error.
  
  
   
• 4070007: Sync password fail 
  
  When adding a server with existing system information, clustering may fail while syncing passwords between servers, even when the passwords match. A network issue may cause the failure.
   
• 4070008/4070009: System information initialization failure
  
  
   
• 4070008: Failed to retrieve the server’s own system information
   
• 4070009: Failed to create new system information for the target server