F5-BIGIP-Rename virtual server and pool names:

March 4, 2019 Raghavendra Seshumurthy

Please follow below steps to rename virtual server and pool on F5 BIGIP :

Enable database so that you can modify the virtual server and pool.

tmsh modify /sys db mcpd.mvenabled value true

2. Rename virtual server with mv command

tmsh mv ltm virtual <original_VS_name> <new_VS_name>

3. Rename your pool with same command

tmsh mv ltm pool <original_pool_name> <new_pool_name>

4. Disable database so no one can modify configurations

tmsh modify /sys db mcpd.mvenabled value false

Published by Raghavendra Seshumurthy

My name is Raghavendra Seshumurthy. Presently I am working as a technolgy manager for Microland Organization. I have experience on security/cloud products: F5, Checkpoint, ASA, PA, AWS, Bluecoat, VPN, PITC, Zscaler, Azure, GCP, network, security, cloud. This blog is created just to share thoughts on new technologies and features in the network, security and cloud environment. View all posts by Raghavendra Seshumurthy

4 thoughts on “F5-BIGIP-Rename virtual server and pool names:”

timelordx says:

March 26, 2019 at 7:04 pm

“tmsh mv” commands could make F5 unstable, unfortunately 😦

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

LikeLike

Reply
1. Raghavendra Seshumurthy says:
  
  August 3, 2019 at 2:40 am
  
  we did on multiple devices without any issue but still we need to use with extreme caution.
  
  LikeLike
  
  Reply
Stephan says:

May 29, 2019 at 12:10 pm

Renaming pools and virtualservers work like you’ve written it. Indeed, I’ld like to add a big warning sign, since during mv, bigip clusters will temporarily get out of sync and consequently devicegroups will move across nodes, which could lead to service disruption.

LikeLike

Reply
1. Raghavendra Seshumurthy says:
  
  August 3, 2019 at 2:39 am
  
  yeah, we need to use commands with extreme caution but it will work like a charm.
  
  LikeLike
  
  Reply