Bug ID 646768: VCMP Guest CM device name not set to hostname when deployed

Last Modified: Sep 24, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,

Opened: Feb 22, 2017
Severity: 4-Minor
Related AskF5 Article:


When you access the vCMP guest instance after you deploy the system, the instance uses the hostname bigip1.


The vCMP guest does not use the configured hostname.


This issue occurs when all of the following conditions are met: -- The BIG-IP system is running v11.6.0 or earlier. -- You configure a vCMP guest instance that is running BIG-IP v11.6.0 or later. -- You have configured the vCMP guest instance with a hostname other than bigip1. -- You deploy the vCMP guest instance.


-- In tmsh, run the following commands, in sequence: mv cm device bigip1 HOSTNAME save sys config -- Rename the device name in the GUI.

Fix Information


Behavior Change