Server Management - Remote Server Management
cancel
Showing results for 
Search instead for 
Did you mean: 

HP iLO Cmdlet Set-PersistentBootOrder

lzinga
Occasional Visitor

HP iLO Cmdlet Set-PersistentBootOrder

I am having an issue using the HP iLO powershell command ""Set-PersistentBootOrder". When I execute the Get-PersistentBootOrder for the server it comes back with.

DEVICE         : {Boot000D, Boot0009, Boot000A, Boot0010...}

Which is fine, as long as those values are consistent across servers, I can determine which one is Network PXE (IPv4) and use which ever Boot code. However they are not consistent, in one server it will be Boot000A while in another it will be Boot000D. Which makes absolutely no sense to me, I have tried many different variations, things like "Network" and  "Network Device 1" and nothing works.

If anyone could help me with this that would be great.

For those interested I also opened an issue here incase it gets answered over there but not here. - https://github.com/HewlettPackard/PowerShell-ProLiant-SDK/issues/3

1 REPLY
GokulKS
Valued Contributor

Re: HP iLO Cmdlet Set-PersistentBootOrder

Hi,

Yes seems to be a bug in our cmdlet. The information of the device is available in Gen8 but not in Gen9 where RIBCL xml the device information is coming as "Bootxyz" with description whihc is missing in the cmdlet output object.

I have created a quix for iLOCmdlet 1.5 release to track.

Meanwhile this issue is fixed in our new release iLO cmdlets 2.0 which is coming in Gen 10 snap2 release timeline around April CY18.

Answering to your device name consistency question across servers i think that's the iLO server issue as server is sending all the device names and as cmdlets we don't have any control over it.

Currently you can use below command to know the device informatin of the boot order and later in the Set cmdlet you provide the same device name not floppy or cdrom for gen9 onwards.

$out = Get-HPiLOPersistentBootOrder -Server 192.168.10.19 -Username admin -Password admin123 -DisableCertificateAuthentication -Verbose -OutputType RIBCL

PS C:\Windows\system32> $out
<?xml version="1.0"?>
<RIBCL VERSION="2.23">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>
<?xml version="1.0"?>
<RIBCL VERSION="2.23">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>
<?xml version="1.0"?>
<RIBCL VERSION="2.23">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>
<?xml version="1.0"?>
<RIBCL VERSION="2.23">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
<PERSISTENT_BOOT>
<DEVICE value="Boot0008" DESCRIPTION="Generic USB Boot"/>
<DEVICE value="Boot000D" DESCRIPTION="Embedded FlexibleLOM 1 Port 1 : HP FlexFabric 10Gb 2-port 536FLB Adapter - NIC (PXE IPv6) "/>
<DEVICE value="Boot000C" DESCRIPTION="Embedded FlexibleLOM 1 Port 1 : HP FlexFabric 10Gb 2-port 536FLB Adapter - NIC (PXE IPv4) "/>
<DEVICE value="Boot0009" DESCRIPTION="Embedded RAID 1 : Smart Array P246br Controller - 931.48 GiB, RAID 1 Logical Drive(Target:0, Lun:0)"/>
<DEVICE value="Boot000A" DESCRIPTION="Embedded FlexibleLOM 2 Port 1 : HP FlexFabric 10Gb 2-port 536FLB Adapter - NIC (PXE IPv4) "/>
<DEVICE value="Boot000B" DESCRIPTION="Embedded FlexibleLOM 2 Port 1 : HP FlexFabric 10Gb 2-port 536FLB Adapter - NIC (PXE IPv6) "/>
</PERSISTENT_BOOT>
</RIBCL>
<?xml version="1.0"?>
<RIBCL VERSION="2.23">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>
<?xml version="1.0"?>
<RIBCL VERSION="2.23">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>

$out17 = Set-HPiLOPersistentBootOrder -Server 192.168.10.17 -Username admin -Password admin123 -DisableCertificateAuthentication -BootOrder @("Boot0008,Boot000D,Boot000C") -Verbose

Hope this is helpful.

Thanks,

Gokul

Don't forget to give kudos if you got your answer !

Don't forget to give Kudos if the problem got resolved or like suggestion.