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

fpieressa's avatar
fpieressa
Icon for Altostratus rankAltostratus
Jun 01, 2014

Renaming Virtual Servers on 11.5.1

Hi! We need to rename a Virtual Server on 11.5.1, using the unsupported method of editing the bigip.conf is not working, as we are receiving the following error:

 

[root@f5:Active] config tmsh load sys config partitions all

 

Loading system configuration...

 

blablablah...

 

Loading configuration...

 

/config/bigip_base.conf

 

/config/bigip_user.conf

 

/config/bigip.conf

 

01020056:3: Error computing object status for virtual_server (/Common/vs-xxxx-http).

 

Unexpected Error: Loading configuration process failed.

 

With older versions we know it works perfect, is there any additional step required on this new version, or is there any other option available?

 

Thanks!

 

application delivery
LTM
management

12 Replies

Show More
  • Martin_Williams's avatar
    Martin_Williams
    Icon for Nimbostratus rankNimbostratus
    Jul 14, 2015

    I have used the mv command on a number of occasions to rename pools and virtual servers without any problems.

     

  • Hannes_Rapp's avatar
    Hannes_Rapp
    Icon for Nimbostratus rankNimbostratus
    Nov 25, 2015

    Renaming Virtual Servers by loading configuration in v11.5.1 is bugged. It does not work as previously, and any of the public hotfixes have not yet addressed the problem.

    You can circumvent the error if you rename Virtual Servers that have no Default Pool attched to them in Virtual Server settings. Obviously, removing the link between LTM Pool and Virtual Server is not an option as it comes with an impact. To successfully rename a Virtual Server without an impact, you will have to rename your Virtual Servers on a standby appliance, and then sync to active appliance only after you have restored the Default Pool configuration in Virtual Server settings.

    1) Remove Default Pool in VS config
2) Rename Virtual Server in bigip.conf
3) Load configuration
4) Restore Default Pool config in Virtual Server settings
5) Sync from Standby to Active

    Just upgrade to v11.5.3 HF2. Save yourself from having to deal with this crap every time.