We have appox 100 VMware images running Windows 2008 R2 and registered in the SA Console. Once a week the servers are restarted and rebuilt from a gold PXE image.
When trying to re-install the agent on any of these server, the install runs but returns the error:
"INFO: Initially registering hardware and operating system information... Chassis ID: VMware-42 00 16 c2 cd 66 c3 e5-ca 05 70 75 9a ed 5b 31 UUID: 420016c2-cd66-c3e5-ca05-70759aed5b31 TRACE: Connecting to 'https://spin:1004/spinrpc.py'... [FATAL] The agent has been unable to initially register hardware with server at 'https://spin:1004/spinrpc.py'. More error information regarding this failure may follow. INFO: Encountered Fatal registration error, see errors above for possible cause TRACE: Rolling back any mid/crypto file changes ERROR: spin.permissions - The agent installer detected an existing device record 'Server ID 133710001 (server.domain)' in the core that has the same chassis ID; the installer attempted to reclaim this device record but failed to because the device record is not configured to accept a request to issue a certificate.
To gain access to most of the HPSA components individual UI's, such as spin, you need to present a cert when accessing the URL.
The cert created when your HPSA core was deployed is located here: '/var/opt/opsware/crypto/spin/spin-developer.p12' the password can be found in your response file. Look for the value under '%decrypt_passwd'.
The spin calls can be launched from any browser with access to that URL. The DNS name doesn't matter as long as it is pointing to the IP of your Spin server.
I think you should be fully removing any reference to the servers before re-registering by deactivating and deleting. If not I think you will end up with lots of unreachable agents with duplicate names using up object IDs. This can be done through a script in OGSH using the 'decommission' and 'remove' methods:
When the server is not registered on the server, we have to uninstall the agent after boot, as its part of the PXE boot image.
I have then written a script that runs the initial install, once the install of the HPSA agent is complete and registered against the core, it will copy the following files to a safe area that isn’t cleared on restart of the server:
On subsequent reboots, the HPSA agent is set not to start on boot up, a script then copies the above files from the safe area to the correct areas in the HPSA file structure replacing the files already there. The agent then starts, and due to it using the files from a successful install and registration the agent connects correctly
Bit of a long winded way of resolving the issue but it works.
Thanks for all the suggestions, it did point me in the right direction.