topic configurare ILO shared su ML30 GEN10 in ProLiant Servers (ML,DL,SL)

configurare ILO shared su ML30 GEN10

mvaltolina — Fri, 05 Jan 2024 14:03:01 GMT

Buongiorno a Tutti

dovrei configurare la porta ILO su un server ML30 GEN 10 Windows 2016. Questo server non ha una porta ilo dedicata ma 2 porte di rete. E' possibile creare un NIC fra le due porte e gestire anche la ILO ?

Da DHCP mi viene assegnato un IP ma non è raggiungibile.

Al momento la ILO è cos configurata :Shared network port ENABLED, Snp Port : PORT 1 Vlan DISABLED

Qualche idea/aiuto ? Grazie in anticipo

Google Translated:

configure ILO shared on ML30 GEN10
Good morning everyone

I should configure the ILO port on a ML30 GEN 10 Windows 2016 server. This server does not have a dedicated ilo port but 2 network ports. Is it possible to create a NIC between the two ports and also manage the ILO?

By DHCP I am assigned an IP but it is not reachable.

At the moment the ILO is configured as follows: Shared network port ENABLED, Snp Port: PORT 1 Vlan DISABLED

Any ideas/help? Thanks in advance

Re: configurare ILO shared su ML30 GEN10

thutchings — Fri, 05 Jan 2024 13:59:20 GMT

Hello,

One of the issues you may run into when using the Shared Network Port (SNP) is that the NIC available in the OS that is being used for SNP cannot "talk with itself". This means that if you are in Windows on the server and attempt to use the same port to communicate with the iLO, then the communications will not work. Using a DHCP assigned address for the SNP should work fine and it should be accessible from other devices on your network.

Regarding NIC teaming and the use of the SNP...

I would review the following limitations in the iLO user guide related to this:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00105236en_us&page=GUID-51B2317D-535C-4ED5-940F-1A3BD1970039.html

Regards

Re: configurare ILO shared su ML30 GEN10

mvaltolina — Fri, 05 Jan 2024 14:02:55 GMT

thank you very much

Re: configurare ILO shared su ML30 GEN10

Sunitha_Mod — Mon, 08 Jan 2024 06:13:29 GMT

Hello @mvaltolina,

That's awesome!

We are extremely glad to know your concern has been addressed.