ProLiant Deployment and Provisioning
1833776 Members
2422 Online
110063 Solutions
New Discussion

hponcfg Utility.

 
Jean Paul Gatt
New Member

hponcfg Utility.

I have a number of BL35p Blades that were recently replaced. Given the rush to put them back into working condition, the serial numbers have not been set up yet. I wonder, is it possible to configure the serial number through the hponcfg utility ? Is there something similar? Or do I have to do this through the BIOS as I usually do?

I really would like to avoid to have to reboot the systems one by one ....
4 REPLIES 4
Gordon Leonard
Honored Contributor

Re: hponcfg Utility.

You sould not change the serial number unless you mean you changed the system board in the BL35p. If the system boad was changed the service tech *should have* entered the serial number to match the replaced board.

Ok...here is your loaded gun. You could end up changing ALL your servers to the same serial number. So aim this CAFEFULLY!

You can set the SN of any server using conrep In the INI file you simply put something like:

Version 2.62
OS_Major 5
OS_Minor 6
System_Serial_Number M009MKV13H


Jean Paul Gatt
New Member

Re: hponcfg Utility.

The mainboards were all changed, that is why the serial numbers all changed.

I am very familiar with the procedure, but given the number of blades being changed, and the production environment necessities, it was replace and bring back on ASAP.. worry about serial numbers later.

Now it is later! I'll try your method ..
Jean Paul Gatt
New Member

Re: hponcfg Utility.

I need some further clarification.

I managed to find the scripting tools from HP. Now ..

1) What should the ini file be name ?
2) Does it require a restart (main idea is to avoid a restart)?
3) conrep.xml does not define a system serial number field anywhere ... only the option to enable CPU serial number.

Thanks.
Gordon Leonard
Honored Contributor

Re: hponcfg Utility.

Current versions of RDP uses Win and Linux tools thus use XML files. You should be able to use the CONREP in RDP.

Try the *attached* (edit the file with Notepad and enter a serial number) and test it on a TEST server.

I'm not sure how the SN is read into the system. Try going to the SNMP service and *restart* it. It should also restart the agents.