HPE PCBE deployment 20% Error

[RMO-Sam]

Hi All,

I have an issue with HPE Alletra MP PCBE VM Essential software deployment. 

[DiegoDelgado]

Hello,

are your interfaces properly cabled and the switches configured with the right settings? I've seen issues where the switch ports are administratevly down.

I would also recommend filing a new support case in the top right of the Greenlake Platform

[duru19]

Hello,

Based on the screenshot, the deployment is failing at the 20% Server Validation stage.

The main issue appears to be related to the network interface status of the servers. The validation output shows that the system found 3 servers, but all of them are currently marked as incompatible:

For servers 10.215.226.110 and 10.215.226.112, one or more required network interfaces are in NoLink state. The expected state is LinkUp.
For server 10.215.226.114, the validation reports that there are no valid network interfaces configured.

Because of this, the deployment cannot continue to the next step.

At this stage, I recommend checking the following items on all three servers:

Verify the physical cabling between the servers and the switches.
Confirm that the related switch ports are enabled and showing link up.
Check whether the correct NIC ports are connected for management/compute/storage traffic.
Validate the speed, transceiver/DAC compatibility, and auto-negotiation/FEC settings if applicable.
If bonding/LACP is used, confirm that both the server-side bond configuration and switch-side port-channel configuration are aligned.
On server 10.215.226.114, additionally verify that the NICs are visible at the OS/iLO level and that the required interfaces are properly configured.

The following commands may help to validate the server-side interface status;

ip -br link
ip -br addr
nmcli dev status
ethtool <interface-name>
cat /proc/net/bonding/bond0

Once all required interfaces are in LinkUp state and the network interfaces are correctly configured, please run the validation/deployment retry again.

In summary, this does not currently look like a storage or license-related issue. The deployment is blocked because the required server network interfaces are either down or not properly configured.