install configuration
3 Topics"Install Configuration" During activating new boot location
Hi, I'm preparing to upgrade my devices, and one thing is not completely clear to me. While activating Boot location you can choose to install configuration. According to documentation when activating a boot location, the Install Configuration option allows you to select a configuration to be installed from a boot location other than the boot location being activated. I'm not completely following it. If I choose not to install configuration will I get a clean, out of the box install? Alternatively - should I choose to have a configuration installed from the previously active partition, in order to retain my current setup?Solved1.3KViews1like3CommentsFailed Hotfix update
Hi, Just tried to apply Hotfix-BIGIP-13.0.0.2.0.1671-HF2 to existing 13.0.0.0.0.1645 volume - HD1.3. Result was failed with info below: tail -f /var/log/liveinstall.log info: /: Not enough free space info: 268609536 bytes required info: 226794496 bytes available info: /var/local/ucs/config.ucs: Not enough free disk space to install! info: Operation aborted. info: >---- info: Removing boot loader reference Terminal error: UCS application failed; unknown cause. *** Live install end at 2017/05/22 09:39:59: failed (return code 2) *** So I mounted /var from HD1.3 with mount -t ext3 /dev/mapper/vg--db--sda-set.3._var /mnt/tmp_root Then I did df -h with result: Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg--db--sda-set.3._var 3.0G 1.3G 1.6G 45% /mnt/tmp_root Seems like there is plenty of space on /var so why the error? Is there a way to increase size of directories of not active volume (like when using tmsh modify /sys disk directory /shared new-size for active volume)? Side question I did fresh hotfix install on new volume HD1.4, then used GUI Boot Locations to select it with Install Configuration: No After reboot my whole config was copied to new volume - why so? My db.liveinstall are like that (I doubt I was changing them from defaults) tmsh list sys db liveinstall.* one-line sys db liveinstall.checksig { value "disable" } sys db liveinstall.longmode { value "enable" } sys db liveinstall.moveconfig { value "enable" } sys db liveinstall.movelicense { value "enable" } sys db liveinstall.packageset { value "default" } sys db liveinstall.saveconfig { value "enable" } sys db liveinstall.savelicense { value "enable" } Piotr699Views0likes7CommentsInstalling with tmsh automatically copies active config?
I am going through the process of upgrading an F5 BIG-IP and decided to do it from the cli with tmsh this time. Previously when using the UI you had the option when setting the boot location to "Install Configuration [yes/no]" and "Source Volume [select list]". I read this article https://support.f5.com/csp/article/K13438 that seems to state doing the install via tmsh the config is automatically copied based on the values of LiveInstall.MoveConfig and LiveInstall.SaveConfig which default to enable. Is this correct and installing an upgrade from tmsh automatically will copy the current config to the new volume?290Views0likes1Comment