Archives and issues with upgrades.

Hey there!

 

 

I have had a problem with upgrading our BigIP Load Balancers. When we upgraded on of our redundant pairs it lost all of the configuration, save for a small amount in the common partition, and the SSL certificates. When i rolled back to the previous installation, on the volume which it was installed, that too had lost the configuration. Luckily i took a manual ftp backup of the bigip.conf file a week before so was able to salvage the entire operation.

 

 

When i went to reimport it, i had problems as one of the ssl profile names, there was a character space in the name which caused a problem when it was imported and loaded back in. I edited the files manually and removed the character spaces in names etc. Everything was fine, so now to my question...i guess its a gotcha kind of thing...

 

 

Is it when you use the Web front end to create nodes, profiles, servers etc you are allowed to use character spaces in your names, but in the command line you are not allowed as it reads the space as a seperator? When you create an archive in the GUI does it create it through the command line hence why the arcive was not complete (the character space in the name), and does this again apply for copying the configuration when upgrading / applying a hotfix.

 

 

Im not 100% how clear this is as it was a seriously confusing situation and took me a while to understand. Any help is of course whole heartedly appreciated.