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

chethan_181144's avatar
chethan_181144
Icon for Nimbostratus rankNimbostratus
Oct 17, 2016

Can we modify existing pool name ?

Hi F5 Team ,   I have a request to Modify the Pool name as below , Kindly advice if I can modify the pool name , If yes how do i do that ? Will this affect the active connection ?   Port 80 (...
application delivery
LTM
TMSH
Hannes_Rapp's avatar
Hannes_Rapp
Icon for Nimbostratus rankNimbostratus
Oct 17, 2016
 Ensure all latest changes are in the recent backup file
(bash)  tmsh save sys config

 Modify the backup file
(bash)  vi /config/bigip.conf
(vi)  :%s/STATEMENTS-PROD-80/STATEMENTS-DTCPROD-80
(vi)  :wq

 Load in the modified config from the backup file
(bash)  tmsh load sys config

I give no guarantees, but I've done this during peak business hours without a negative consequence.

Caution: does this exact name pattern exist in other objects, other than the LTM Pool names? Issue a grep command on the bigip.conf backup file before you start.

Hannes_Rapp's avatar
Hannes_Rapp
Icon for Nimbostratus rankNimbostratus
Oct 17, 2016

Interesting inputs. I've added comments

 Take the conf file back up
(bash)  cp /config/bigip.conf /config/bigip.conf_backup

Sure, why not.

This will give additional assurance in case you decide to roll back lets say a few days later, not shortly after the change. Naturally, there's another backup file (/config/bigip.conf.bak) which does the exact same thing. At all times, you effectively have an opportunity to roll back a single configuration change regardless if you take a backup or not. However, the bigip.conf.bak file like the main backup file updates itself automatically after changes to configuration are made. This backup file has a very short shelf life. If you consider a change risky, it's never a bad idea to take a hard backup for youself.

 Verify the config file
(bash)  tmsh load sys config verify

Not a fan.

If there are problems with the configuration file from which you try to load the active configuration, the operation is cancelled automatically and any errors will be reported. Despite F5 recommending this 'verify' flag in various SOL articles, I'd say this command is next to useless and only wastes your time in the long run.