iLO Amplifier Pack - network settings not committing/saved after reboot

[Agg-HQ]

Hi,

we are trying to deploy iLO Amplifier Pack in a Hyper-v environment but when we go throught the first installation wizard and reboot add the end none of the network settings are saved. We also tried to configure the settings through cli but this doesn't seem to help either. Only the admin password seems to be saved.

Has anyone have an idea what is causing this? I also tried to deploy v 2.12. We do use SCVMM if that makes any difference.

thanks in advance!

[support_s]

System recommended content:

1. Advisory: HPE Integrated Lights-Out 5 (iLO 5) - iLO Amplifier Pack Appliance Deployed on VMware ESXi 6.x/7.x Host Configured with iLO 5 Shared Network Port Fails to Access or Discover iLO 5 IP Address

2. Advisory: iLO Amplifier Pack 1.30 - Servers Are Not Discovered with HPE Integrated Lights-Out 5 (iLO 5) Firmware v1.40 When the Anonymous Data Is Disabled in iLO Amplifier Pack

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Agg-HQ]

Hi,

i'm not sure about the article you posted but it seems it's more related to adding iLO servers/interfaces to the amplifier after the installation.

The problem we are having is that we cannot even access the amplifier dashboard after deployment because of the network settings are not being saved to the appliance.

issue:

 At the end of the initial setup we reboot as required by the appliance:

after the reboot we receive that the network config is not completed. 

We also have tried to configure it through cli but the result is the same.

not sure if this might be relevant but we do see during the boot the following message very shortly

thanks in advance

[AmRa]

Please refer iLO Amplifier Pack User Guide (page 22) and verify if you are following the same procedure for the initial setup of the iLO Amplifier Pack.

https://support.hpe.com/hpesc/public/docDisplay?docId=a00100271en_us

[Agg-HQ]

Thanks but I have followed the documentation to the letter but still no network configuration after the reboot. Even when we put the vm in a dhcp vlan and we start the vm with dhcp enabled it doesn't receive any ip.

Also, if we try to assign both NIC1 and NIC2 on DHCP we receive the following error:

HpeCommon.1.4.PropertyValueIncompatible

[AmRa]

We would suggest please raise a support ticket with HPE tech support for further assistance.

So that we can take remote session and assist you further.

[Roger62]

Was this ever solved? We have the exact same issue when installing 2.20 (since upgrade from 1..95 isn't supported, we have to create a new install).
How can we get HPE Support for Amplifier Pack, as there isn't a product or license number attached?

Thanks for any hints!

[Sunitha_Mod]

Hello @Roger62,

Thank you for posting! Since you have posted in an old topic and there is no response yet, I would recommend you to create a new topic using the create "New Discussion" button, so the expert can check and guide you further. 

[Agg-HQ]

Hi Roger,

As far I know there is no available support that can be seperately purchased for the Amp pack. Maybe this will become available in the future.

As for the issue, I got it sorted out by deploying it on a standalone host first. This way my settings and config on the vm stayed after a reboot. I migrated the vm afterwards to our failover cluster and now it keeps my settings even after a reboot. So i'm still not sure if this is a Microsoft or HPE issue.

[Roger62]

Thank you for your hint. Tried it now on standalone and even on a local Win10.

No luck so far, same result as before. 

[SeaoSam]

I have exactly the same issue as you. tried on three different hosts with both legacy network cards and none.

The machine doesnt recieve a DHCP address and if a static address is specified it ignores that as well 

[SeaoSam]

ok SO i managed to get it to work 

after the boot screen completed and the error was on screen. I went into the CLI by pressing Escape

I then typed in 

SET systemconfig factoryreset all

after about 20 seconds it auto rebooted it self. Then i went through the initial setup wizard yet again but this time it actually managed to gt a dhcp address on both network cards,

[Jabiros]

I found the solution, if anyone is still looking for it. 

This is a deployment I did on Hyper-v. So not sure if it's the same on VMware. Initially, when I was deploying the VM it only had 1 NIC. But in the configuration, it was asking to configure 2. Never understood why. 

When I added a second NIC to the VM the settings were saved. I did not have to configure the second NIC, it just had to be present. 

[MarcoLuvisi]

On Hyper-V deploy with a second NIC added to VM, setup end correctly with save network configuration.