topic Re: iLO Amplifier Pack - network settings not commiting in Server Management - Remote Server Management

iLO Amplifier Pack - network settings not commiting

Roger62 — Wed, 24 May 2023 11:38:01 GMT

We're setting up iLO Amplifier 2.20 on a Hyper-V VM, following the product's installation guide. Admin password gets persisted, but not the network settings. Also not settable via CLI.

Same issue as in this thread, which doesn't show a resolution unfortunately.

Don't know how to create a support ticket for Amplifier with HPE, there's no product name or such we could attach this to.

Thanks for any hints!

Query: iLO Amplifier Pack - network settings not commiting

support_s — Tue, 23 May 2023 13:45:01 GMT

System recommended content:

1. HPE Integrated Lights Out (iLO 4) - Troubleshooting Multiple Issues

2. HPE iLO 4 2.81 User Guide | iLO features that support IPv6

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

Thank you for being a HPE valuable community member.

Re: iLO Amplifier Pack - network settings not commiting

Suman_1978 — Wed, 24 May 2023 11:32:50 GMT

Hi,

I am sure you have already referred to the User Guide to configure Network settings.
You can also check the FAQ document for Network settings.

Here are some more manuals and guides for this product.

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics

Re: iLO Amplifier Pack - network settings not commiting

Vinky_99 — Thu, 25 May 2023 06:23:07 GMT

@Roger62

You may give a try to below stuff:

* Firstly double-check the network settings you have entered to ensure they are correct. Pay attention to details such as IP address, subnet mask, gateway, and DNS settings.

* Make sure you are logged in with administrative privileges or an account with sufficient privileges to modify network settings.

* Restart the iLO Amplifier service. Restart the service and check if the network settings persist after the restart.

* Ensure that the necessary ports for iLO Amplifier are open in your firewall settings. Refer to the iLO Amplifier documentation or installation guide for the required ports.

* Verify if there are any updates available for iLO Amplifier Pack. It's possible that a software update may address the issue you are encountering.

As far as creating a support ticket with HPE for iLO Amplifier, you can visit the HPE Support website (https://support.hpe.com/) and look for the "Contact HPE" or "Create a Case" option. You can explain the issue you are facing and provide relevant details, such as the version of iLO Amplifier, the steps you followed, and any error messages received. HPE support should be able to assist you further with troubleshooting and resolving the issue.

When submitting the support ticket, provide as much information as possible to help them understand the problem. Even if there is no specific product name mentioned for iLO Amplifier, you can describe it as an HPE product and provide details about the version and the issue you are encountering.

Hope it might help you!

Re: iLO Amplifier Pack - network settings not commiting

Roger62 — Mon, 29 May 2023 18:54:12 GMT

No luck so far, tried with 2.22 now, same issue.

Re: iLO Amplifier Pack - network settings not commiting

kutthroat — Wed, 31 May 2023 20:06:46 GMT

had the same issue, booted the server to a kali,iso, mounted the file system to a mount point on Kali, like /mnt/mountpoint

cd' <mountpoint>/etc/network and fixed the interface file manually, that brought up the vm on the next reboot. There was garbage in that configuration that seemed to be gumming up the works, this is probably a bug with the network wrappers that auto create this file when the server is configured static. .

Also in the mix the server is an E1000 driver on vmware, i put this as vmxnet3, the difference between a 1g and a 10G speed, ditched ipv6. hopefully all goes well from here.

Re: iLO Amplifier Pack - network settings not commiting

Roger62 — Thu, 01 Jun 2023 21:31:21 GMT

Thank you, kutthroat, this did the trick!

I had tried that approach with WSL on Windows first but couldn't get into the right partition (seems that WSL2 works too for this).