I was able to get this to work. One main thing to do while the guest is still up is login to the cli and run
f5mku -K
to get the current Master Key. It seemed to change so it couldn't read the config after I performed the steps below. I made sure all of my guests were disabled and offline(Your Guests will be restarted when you restart vcmpd below if they are running). I then edited
bigip.conf
and changed the
guest name, hostname, and the virtual disk name
. I then went into
/shared/vmdisks
to change the virtual disk name using
mv old_name.img new_name.img
. Then I did
tmsh load sys config
tmsh save sys config
bigstart restart vcmpd
. I noticed in the Viprion GUI the old virtual disk was still listed with the old name but a size of 0 so I deleted that. The new renamed image will also be there. Don't delete the new one. Once I deployed the renamed guest it will come up into an INOPERATIVE state and the gui will not load. I connected via SSH to the CLI and restored the Master Key using
f5mku -r key
using the key you got above. Then a final
tmsh load sys config
on the LTM CLI and I was back in business with everything using the new name. You will probably have to do some other steps like updating the LTM Device SSL Certificate to match the new hostname. You also need to go to Device Management > Devices > device_name > Click
Change Device Name