Forum Discussion

Jana's avatar
Jana
Icon for Altostratus rankAltostratus
Aug 08, 2014

Device name under 'Device Management'

I'm looking for some information as to why there's device name shown as 'bigip1(self)' and also a hostname under 'Device Management > Devices', though the device hostname has been changed.   Also,...
design
ha
TMSH
Stan_Ward's avatar
Stan_Ward
Icon for Altocumulus rankAltocumulus
May 14, 2020

Apparently, all of the cm device commands have been disabled as of v14.1.2.3 (and MV command was already depricated). Changing hostname does not change the device name since v13.1 even if the device is not in a DSC cluster. However, the Ansible bigip_hostname module attempts to change the device name when changing hostname, though this is not documented. It will fail if the device is already in a trust relationship.

 

Even when the device isn't (and never has been) in a device trust relationship, as when a new vCMP guest is created, I've not been able to change the name via TMSH - it always says that the device is referenced by /Common/device_trust_group; actually, that is not found, but it's referenced in trust-domain Root, which cannot be deleted.

 

I always have to do it via the ConfigUI.

 

 

 

 

 

  • seamlessfirework's avatar
    seamlessfirework
    Icon for Cirrus rankCirrus
    Nov 22, 2023

    I feel your pain, too. Currently I am working on a iControl REST framework to push basic configuration to a fresh BIG-IP. I stumbled upon this issue and the "mv" command still works though it has been deprecated years ago by F5. I am working on BIG-IPv16. Don't know whether this still works on BIG-IPv17.