For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Sajan_Mania_381's avatar
Sajan_Mania_381
Icon for Altostratus rankAltostratus
Mar 04, 2019
Solved

How do I to rename a Virtual Server/Pool name on a F5 LTM ?

How do I rename a Virtual Server/Pool name on a F5 LTM ?   Can you please help me with commands with example .   BIG-IP version details : Sys::Version   Main Package   Product BIG-...
application delivery
LTM
TMSH
  • Dylan_375544's avatar
    Dylan_375544
    Mar 04, 2019

    HERE is a link explaining that in order to rename VIPS through CLI, you must enable the MV (move) command. I just tested this on Ver 13, and it works the same with Pools. That link references THIS one, which is an official F5 doc and has some good info too.

    Do that by running the command in TMSH

    modify /sys db mcpd.mvenabled value true

    You can then "rename" your VIP by MOVING it to another name

    mv ltm virtual

    Or rename your pool in the same manner

    mv ltm pool

    Then disable the MV command so no mistakes are made later by running

    modify /sys db mcpd.mvenabled value false

    Hope that helps! If it does, please up-vote and select this answer, it would be greatly appreciated!

    -Dylan

    NOTE There is a chance that TMM will restart after that change is made, so be aware of that.

Dylan_375544's avatar
Dylan_375544
Icon for Cirrocumulus rankCirrocumulus
Mar 04, 2019

HERE is a link explaining that in order to rename VIPS through CLI, you must enable the MV (move) command. I just tested this on Ver 13, and it works the same with Pools. That link references THIS one, which is an official F5 doc and has some good info too.

Do that by running the command in TMSH

modify /sys db mcpd.mvenabled value true

You can then "rename" your VIP by MOVING it to another name

mv ltm virtual

Or rename your pool in the same manner

mv ltm pool

Then disable the MV command so no mistakes are made later by running

modify /sys db mcpd.mvenabled value false

Hope that helps! If it does, please up-vote and select this answer, it would be greatly appreciated!

-Dylan

NOTE There is a chance that TMM will restart after that change is made, so be aware of that.

Michael_Saleem1's avatar
Michael_Saleem1
Icon for Cirrus rankCirrus
Mar 05, 2019

The mv command is supported from v11.5.4 (so v11.6.2 will be supported)

From past experience, enabling the 

mcpd.mvenabled
variable is fine. However, when I renamed an object using the 
mv
command, it caused a failover. As such, I would be cautious about using it in a Production environment

https://support.f5.com/csp/article/K08689048

Impact

The BIG-IP system may temporarily stop processing traffic while the TMM service restarts. Systems configured as part of a high availability (HA) pair may fail over to a peer device.

Important: Currently, the ability to move certain BIG-IP objects to other folders and to rename those objects is an experimental feature. F5 recommends that you disable this feature after you have moved or renamed any BIG-IP objects. Also, use of this feature could result in a loss of statistics and a disruption in BIG-IP GTM service. If you plan to move or rename a virtual server, please contact your BIG-IP GTM administrator before doing so.

Symptoms As a result of this issue, you may encounter one or more of the following symptoms: • Your BIG-IP system temporarily stops processing traffic when configured to fail over to a peer device. • Your BIG-IP system generates a TMM core file in the /shared/core/ directory. • Your BIG-IP system logs a message to the /var/log/tmm file that appears similar to the following example: notice failed to find pool // notice ** SIGSEGV **