Renaming Virtual Servers on 11.5.1

have you tried this?

sol13030: Forcing the mcpd process to reload the BIG-IP configuration

Force mcpd load works, but the same problem arises the very next time you try to rename a server. Really hope there's another solution to this than mcpd reload and reboot... :/

/Patrik

Perhaps a feature request is in order to build the databases manually and then load them without requiring a reboot (certainly there will be some pre-conditions about what types of change one can apply this way)?

Not the greatest answer, but I just have one file with all the virtual servers removed and the other file is the real config with the names changed. I first load the one with the virtual servers removed, then immediately load the other with the names changed.

From

http://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-6-0.html:

New in 11.6.0 ... General Functionality Object move and rename (early access)

This release provides early access to the feature that enables move/rename of specific BIG-IP object types, such as virtual servers, virtual addresses, pools (implicitly moves pool members), nodes, monitors, profiles, iRules, iApps, device names, self IP addresses, iCall, and folders. Note that this functionality is not provided for VLANs or Partitions.

same question here ... It's possible to rename a pool but not a Virtual Server ... This used to work pretty well with previous versions

there is no ther way in 11.5.1 but: 1. Detach pool 2. Rename VS 3. Attach pool

PS. I really hate that this behavious has changed compared to previous versions.

Anybody tried 11.6.0 and renaming objects there ?

For redundant setups I change it on the passive device and synchronize the changes. Other than that I've not found a solution for 11.5.1 yet.

/Patrik

I've played around a little with the object renaming functionality in v11.6 and it appears to work. Keep in mind that it's considered to be 'early access' (use at your own risk). The functionality is currently available only via tmsh (not the GUI), and is disabled by default. The DB value 'mcpd.mvenabled' is used to control its enabled/disabled state.

To display current state of DB 'mcpd.mvenabled':

tmsh list /sys db mcpd.mvenabled

To enable or disable:

tmsh modify /sys db mcpd.mvenabled value [true|false]

To rename/move an object use the tmsh 'mv' command. For example, to rename pool 'test1' to 'test2', the command would be:

tmsh mv /ltm pool test1 test2

For example:

[root@f5:Active:Standalone] ~  tmsh list /ltm pool test1
ltm pool test1 { }
[root@f5:Active:Standalone] ~  tmsh mv /ltm pool test1 test2
[root@f5:Active:Standalone] ~  tmsh list /ltm pool test2
ltm pool test2 { }
[root@f5:Active:Standalone] ~  list /ltm pool test1
01020036:3: The requested Pool (/Common/test1) was not found.

Keep in mind when renaming objects that there may be dependences with other modules (e.g. GTM). For example, if you rename an LTM virtual server and the GTM refernces that object, you will most likely need to re-add that object in the GTM config.

Has anybody encountered any nasty bug with "mv"? I am very tempted to use this, but baulked at it, as this was only experimental.