Forum Discussion
Wally_Steadman_
Jun 13, 2012Nimbostratus
modifying object names
Greetings all,
I am new to using tmsh and am trying to learn command line configuration stuff.
So we created some nodes and they are named with their IP address and Route Domain ID
so for example: output of a list ltm node:
ltm node 1.2.3.4%2 {
address 1.2.3.4
partition Private
}
Since we went to 11.2 and set the partitions as the defaults we no longer need then name to indicate the %2 for the route domain so I am trying to change just the name from the command line.
I hvae to do this with our self-ips also and just not sure where they reside from command line. I am reading the tmsh for version 11 document but I guess I am missing something so asking if anyone can show an example of how to change these things from the tmsh command line
our self IP names are in the same format with IP and ROUTE DOMAIN ID
Any assistance would be appreciated.
Thanks
Wally
- hoolioCirrostratusHi Wally,
- Chris_W__13732NimbostratusThis can be done, but not within tmsh. If you drop to the unix shell ("run util bash" from tmsh), you can use standard unix utilities to edit the /config/bigip.conf file and change the name of any element you choose (when you're done, type "exit" to end the bash session and return to the tmsh prompt). Then load the modified file (from tmsh, "load sys config verify", then "load sys config" after the validation succeeds), and then if you have an HA cluster, sync it to the other units (run cm config-sync to-group $GROUPNAME) after confirming everything's working.
- Steven_J__WilliNimbostratusI have followed your recommendation and after modifying the bigip.config file with vi and doing a verify I get this error: 107003c:3: Invalid pool member modification. An IP address change from (10.0.0.30) to (10.0.0.31) is not supported. Unexpected Error: Validating configuration process failed. [admin@F5LTM:Active:Standalone] ~ Thoughts?
- nitassEmployee
107003c:3: Invalid pool member modification. An IP address change from (10.0.0.30) to (10.0.0.31) is not supported.
i think it may be this bug. you can open a support case to verify.
ID382040 - Deleting and recreating pool members with named nodes can cause config sync to fail
by the way, not sure if forcing mcpd to reload helps.
sol13030: Forcing the mcpd process to reload the BIG-IP configuration
- sprashanthac_81Nimbostratus
isn't it true that iapp objects reside elsewhere and are independent of the bigip.conf ?
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