Query: HP380 Gen11 - Configure HPe iLO IP address using powershell not working

[udalsem]

I'm trying to configure the IP address of the iLO dedicated network card using the HPe iLO powershell module but it doesnt work

$IPStatic = 10.0.100.125

$Subnet = "255.255.254.0"
$Gateway = "10.0.100.1"
$DNSServers = ,@("10.150.5.15", "10.150.5.16", "0.0.0.0")
$DNSServerTypes = ,@("Primary", "Secondary", "Tertiary")

$Hostname = "ILO-SERVER01

$Connection | Set-HPEiLOIPv4NetworkSetting -InterfaceType Dedicated -DHCPv4Enabled No -IPv4Address $IPStatic -IPv4Gateway $Gateway -IPv4SubnetMask $Subnet -DNSName $Hostname -DomainName $DomainName -NICEnabled Yes -DNSServerType $DNSServerTypes -DNSServer $DNSServers -RegisterDDNSServer Disabled -RegisterWINSServer Disabled

I get this error:

Set-HPEiLOIPv4NetworkSetting : [10.0.101.161]: Input string was not in a correct format.
At line:1 char:15
+ ... onnection | Set-HPEiLOIPv4NetworkSetting -InterfaceType Dedicated -DH ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [Set-HPEiLOIPv4NetworkSetting], Exception
+ FullyQualifiedErrorId : HPE.iLO.Cmdlet.SetHPEiLOIPv4NetworkSetting

Even when i only run: $Connection | Set-HPEiLOIPv4NetworkSetting -InterfaceType Dedicated -DHCPv4Enabled No -IPv4Address $IPStatic -IPv4Gateway $Gateway -IPv4SubnetMask $Subnet

I get the same error.

Is this a bug?

[support_s]

System recommended content:

1. HPE iLO 5 User Guide | iLO IP address acquisition

2. HPE iLO 6 User Guide | iLO IP address acquisition

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

Thank you for being a HPE valuable community member.

[udalsem]

Sorry, you are posting an answer that have has nothing to do with this problem.

[shiva_jr]

Hi @udalsem ,
      Will this syntax of the command help you ? DHCP might not disabled before assigning the static IP, otherwise, it won't work for assigning static IP to gateway.

Set-HPEiLOIPv4NetworkSetting -Credential $cred -Server $iLODHCPIP -DHCPEnable No -DHCPSNTP No -DNSName $iLODNSName -Domain $Zone -IPAddress $iLOIPAddress -GatewayIP $iLOGateway -PingGateway Yes -PrimDNSServer $iLOPrimaryDNS -RegDDNSServer Yes -RegWINSServer No -SecDNSServer $iloSecondaryDNS -SNTPServer1 $iLOPrimaryDNS -SNTPServer2 $iloSecondaryDNS -SubnetMask 255.255.248.0 -Timezone $TimeZone
Start-Sleep -s 30

Regards,
Shiva_jr 

[udalsem]

Thank you for the reply.

In you powershell command line are options that dont excist in my powershell module version of HPe iLO. I think you are using a realy old one. i marked them below in bold.

Set-HPEiLOIPv4NetworkSetting -Credential $cred -Server $iLODHCPIP -DHCPEnable No -DHCPSNTP No -DNSName $iLODNSName -Domain $Zone -IPAddress $iLOIPAddress -GatewayIP $iLOGateway -PingGateway Yes -PrimDNSServer $iLOPrimaryDNS -RegDDNSServer Yes -RegWINSServer No -SecDNSServer $iloSecondaryDNS -SNTPServer1 $iLOPrimaryDNS -SNTPServer2 $iloSecondaryDNS -SubnetMask 255.255.248.0 -Timezone $TimeZone

Every combination i make i get the same error,  at line:1, character 15.

[jashaw · Accepted solution]

I'm pretty sure this is a bug in 4.4.0.0.  I was having the same issue until I rolled back to 4.3.0.0.  This looks like a REST issue to me.

[udalsem]

Thank you so much, now it works again with the version 4.3..0..0..

Let's hope HP updates the script soon.

[Sunitha_Mod]

Hello @udalsem,

That's Excellent! 

We are extremely glad to know the issue has been resolved. 

[jgmke]

Thank you for sharing this.  I'm in the middle of a deployment and the code I've been using for years didn't work.  I igured it was a Gen11 difference, but it's not!

[Erikssonp_65]

Is this issue solved in HPEilocmdlet 5.0 ? Or is there any workaround to set a static ILO ip ?

[udalsem]

I have not tried 5.0.0 version yet because i have no servers to enroll yet.

In the new release they only say it fixed:
9. Fixes
 Enable-HPEiLOComputeOpsManagement - "ActivationKey" updated as mandatory parameter.

[uhlhpe]

Still not fixed. I tried it with version 5.0.0 

iLO6 - Set-HPEiLOIPv4NetworkSetting - Pv4Address - The input string was not in a correct format. · Issue #93 · HewlettPackard/PowerShell-ProLiant-SDK