NimbostratusHi 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 (STATEMENTS-PROD-80) --- Could you change the pool name from STATEMENTS-PROD-80 to STATEMENTS-DTCPROD-80
Regards , Chethan
CirrusThere is no straight forward solution to rename the pool as such. You can create nw pool with your name convention and switch the pool on virtual server. After that you can delete the old pool. But it will impact the active/persisted connections.
Other solution is you can rename it from the bigip.conf file. Edit the pool name (where ever it comes) and load the config file in the big ip. This is risky if you are not familiar with conf file editing. I don't recommend this solution.
-Jinshu
Nacreous 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.
CirrusI would add one more step in this to be on safer side. What do you think Hannes?
Ensure all latest changes are in the recent backup file
(bash) tmsh save sys config
Take the conf file back up
(bash) cp /config/bigip.conf /config/bigip.conf_backup
Modify the backup file
(bash) vi /config/bigip.conf
(vi) :%s/STATEMENTS-PROD-80/STATEMENTS-DTCPROD-80
(vi) :wq
Verify the config file
(bash) tmsh load sys config verify
Load in the modified config from the backup file
(bash) tmsh load sys config
-Jinshu
NacreousInteresting 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.
CirrusCheers..!!
Nimbostratus 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.
CirrusI would add one more step in this to be on safer side. What do you think Hannes?
Ensure all latest changes are in the recent backup file
(bash) tmsh save sys config
Take the conf file back up
(bash) cp /config/bigip.conf /config/bigip.conf_backup
Modify the backup file
(bash) vi /config/bigip.conf
(vi) :%s/STATEMENTS-PROD-80/STATEMENTS-DTCPROD-80
(vi) :wq
Verify the config file
(bash) tmsh load sys config verify
Load in the modified config from the backup file
(bash) tmsh load sys config
-Jinshu
NimbostratusInteresting 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.
CirrusCheers..!!
Nimbostratuson 11.6 you could do that, you need to make sure the pool is not in any irules
1) enable move feature modify /sys db mcpd.mvenabled value true
2) move the pool mv ltm pool test-pool-2 test-pool2