Cluster Issues.

[Singh007]

We are currently testing HPE VME and encountering an issue during deployment. Below are the details of our environment:

Hosts:

• HPE-01: 10.0.205.75
• HPE-02: 10.0.205.180
• HPE-03: 10.0.205.181

HPE-01 and HPE-02 have identical hardware configurations, while HPE-03 has a different processor. The cluster is configured using the Skylake server baseline with EVC mode enabled.

Network Configuration:

• HPE-01 and HPE-02:
• 4 × 10 Gbps NICs
• 2 NICs used for Management and Compute
• 2 NICs dedicated to iSCSI connectivity
• HPE-03:
• 1 × 1 Gbps NIC used for Management and Compute
• 2 × 10 Gbps NICs used for iSCSI connectivity

During hypervisor installation, a bonded network interface was configured with VLAN ID 205, which created the network.205 interface. The IP addresses listed above were assigned accordingly.

We were able to successfully create a cluster using HPE-01 and HPE-02. However, when attempting to add HPE-03 to the cluster, the process fails during the post-provisioning step.

Run-Script Pacemaker Configuration failed

Error: Operation timed Out

Error: Unable to communicate with HPE-03

Password:

We would appreciate your assistance in identifying the cause of this issue and guidance on how to resolve it.

Thank you.

I am ping each other on 10.0.205 subnet without any issue. 

Please let us know the next step to fix this issue. 

[controles]

ood afternoon,

It is important that the network card speeds are identical. If you are using 10 Gb cards, all hosts should use the same, regardless of hardware differences. This can cause latency issues and packet loss. It is also important to understand that the first network created is the management network. With this review, we will have a clearer idea of what might be happening.

Please let me know what type of network cards you are using on host 3. Best regards