Forum Discussion
DanRose_19691
Nimbostratus
Oct 30, 2012node name re-written: Upgrade from v10 - V11
Am running VE BIG-IP 11.2.1 Build 797.0 Final, and have successfully imported ucs configuration files from v10.x to the new platform.
I have noticed is that the node list imported from version 1...
Kevin_Stewart
Employee
Apr 16, 2013You could consider scripting this in Bash.
Start with a list of the nodes and dump to a file:
cat bigip.conf |grep "ltm node" |awk -F" " '{ print $3 }'
Create a copy of your bigip.conf file - you'll be working with the copy (bigip.conf.replace)
cp bigip.conf bigip.conf.replace
Now create a Perl script and add the following line for as many nodes as you have:
perl -pi -e 's/OLD-NAME/NEW_NAME/g' bigip.conf.replace
Where OLD-NAME is the (escaped) current value. So for example, if an existing node name is "/Common/10.70.0.3", your Perl script line will look something like this:
perl -pi -e 's/\/Common\/10.70.0.3/local-dot-3/g' bigip.conf.replace
** The -i means to edit in place.
If you dumped the original list into a text file:
1. replace any instance of "/" with "\/"
2. add "perl -pi -e 's/" to the beginning of each line
3. add "/g' bigip.conf.replace" to the end of each line
4. manually fill in the second part of each replace string to meet your naming requirements.
Open the bigip.conf.replace file to make sure everything looks good. If it does, swap it with bigip.conf (don't delete the original in case you run into problems - make another copy), and reload:
tmsh load sys config
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects