Forum Discussion
NimbostratusError when restore the config file from 9.4.8-version's config
Hi forum,
I just upgrade directory from version 9.4.8 to version 10.2.4. In upgrade process I have to format all disk. It may also deleted my /config.ucs I has backup.When the F5 finish upgrade to 10.2.4, no ip change, and I can log in to it by the old user, but inside there is no other configs.
I have to upload and restore other backup config but I get errors during loading the config.
Installing the license file...
Reloading License and configuration - this may take a few minutes...
Configuration loading error: high-config-load-failed
Saving active configuration...
BIGpipe parsing error:
012e0028:3: There is no valid configuration to save.
Please check the logs for licensing, configuration, or other problems.
Current configuration backed up to /var/local/ucs/cs_backup.ucs.
Product : BIG-IP
Version : UCS : 9.4.8
System: 10.2.4
Hostname: f5lc-1.vietsov.com.vn
Installing --full-- configuration on host f5lc-1.vietsov.com.vn
Installing configuration...
ATTENTION REQUIRED:
The WAM configuration being restored is version 9.4.8 but
the current installation is version 10.2.4. The restored 9.4.8
WAM config files may require manual merging if they had been
customised, and will NOT overwrite the 10.2.4 files. If your
configuration had not been customised no merge is required.
Archiving /config/wa/pvsystem.dtd.9.4.8
Archiving /config/wa/globalfragment.xml.9.4.8
Archiving /config/wa/pvsystem.conf.9.4.8
Archiving /config/wa/transforms/common.zip.9.4.8
Post-processing...
Warning: network failover will not work unless the machine's management address is configured and the peer management address is specified.
WARNING: There were one or more errors detected during installation.
Check the error messages and take the proper actions if needed.
ERROR: UCS installation failed.
Operation aborted.
/tmp/configsync.spec: Error installing package
Config install aborted.
BIGpipe parsing error:
01110001:3: Error running config install
Can anyone help me what I have to do now?
Many thanks
6 Replies
Congtm_119941Can anyone provide me some suggestions?- Hi.
Could be due to several things.
A first suggestion would be to try the command "b load" or "tmsh load sys config" and see what exactly in the configuration is causing an issue so you can take the relevant corrective action.
If this doesn't assist, you could contact F5 Support and they will likely have a quick webex session to have a look at the configuration and get you back on track.
Hope that helps. - Congtm_119941Hi Idjiwa,
You mean, use "b load" to some config files noted in the error log?
Archiving /config/wa/pvsystem.dtd.9.4.8
Archiving /config/wa/globalfragment.xml.9.4.8
Archiving /config/wa/pvsystem.conf.9.4.8
Archiving /config/wa/transforms/common.zip.9.4.8
Please guide me the instruction, I 'm very new to F5. 
richard_77048Congtm,
Did you get that error after uploading the old config.ucs? Do you still have the bigip.conf in /config/ that you had after the upgrade? I think that file is going to be your best bet for getting back up and running.
Are you using irules? If you are, this could be the source of you troubles. There are some syntax differences between v9 and v10. I ran into this during my upgrade from v9 to v10.
It's been a while since I upgraded but I think if you ssh into your unit and run "b load" you will get some output giving you lines in your configuration files that have syntax errors. You can then open your bigip.conf in vi and edit the offending lines. Be sure to make a copy of this file before you start editing it.
Of course, if you aren't using irules, I am not sure what it would be but running "b load" from the command line on your unit is the place to start.
Richard- Congtm_119941Hi,
Yes I got this error when restoring the old config.ucs, I backup it and put one in my PC. I also follow the step b config save /config.ucs to use the feature "rolling forward". I did not backup any things in /config. Now after upgrade I still see some many .conf files in that directory include bigip.conf and bigip.config.backup but I not sure what version they are.
You are right, this F5 have irule configurations in it. The F5 has restored successful some config like most things in Systems and Network settings, but none of Link Controler and Local Traffic settings restored.
You mean run "b load /config/bigip.conf" ? I'm not sure what I have to do now. If I cannot restore the old config I have to manually config by comparing the config with active one. As suggested, just: b load
This will load the needed and should output you with errors in your case.You could actually try to load only the base configuration (network settings, etc.) first before loading it or even use the verify option (b verify load) but the command above, as is, should be a good starting point at this point.
[root@magda:Active] config b base load
Reading configuration from /config/low_profile_base.conf.
Reading configuration from /defaults/config_base.conf.
Reading configuration from /config/bigip_sys.conf.
Reading configuration from /config/bigip_base.conf.
Loading the configuration ...
[root@magda:Active] config
[root@magda:Active] config b load
Reading configuration from /config/low_profile_base.conf.
Reading configuration from /defaults/config_base.conf.
Reading configuration from /config/bigip_sys.conf.
Reading configuration from /config/bigip_base.conf.
Reading configuration from /usr/share/monitors/base_monitors.conf.
Reading configuration from /config/profile_base.conf.
Reading configuration from /config/daemon.conf.
Reading configuration from /config/bigip.conf.
Reading configuration from /config/bigip_local.conf.
Loading the configuration ...
HTH
