v10.2.4 -> v11.4.1 upgrade problems

I'm going to answer your second question first.

I'm curious where you got that command "bigpipe base daol" from, what is the intent with that command?

My unit was entirely blank after the upgrade - no self-IPs or LTM objects, and I got that from a forum search about v11 upgrade problems. Then I searched the KB for "daol" and came up with a couple of relevant articles. Based on those articles, I found a reference to a config load failure in my /var/log/ltm. My base config failed to load because the unit needed to be re-licensed:

Sep 26 08:53:00 localhost err load_config_files: "/usr/libexec/bigpipe base daol" - failed. -- BIGpipe unknown operation error: 01070356:3: vlan failsafe feature not licensed. Reading configuration from /config/bigpipe/low_profile_base.conf. Reading configuration from /config/bigpipe/config_base.conf. Reading configuration from /config/bigpipe/bigip_sys.conf. Reading configuration from /config/bigpipe/bigip_base.conf. Loading the configuration

By the time I found that, the unit had been re-licensed so I just re-ran that command. It makes zero sense to me why the unit would even try to load the base config before being re-licensed - why make customers fight through this manual process of trying to load the base config, and then the LTM config????

Anyway after trying to load the base config, I'm running into this error:

Sep 26 15:22:35 ltm2 err tmsh[16221]: 01420006:3: Error in remote-role: "remoterole" not found. 01020036:3: The requested configuration item ( /Common/remoterole remoterole) was not found.Sep 26 15:22:35 ltm2 err devmgmtd[16201]: 015a0000:3: shell call failed: Error in remote-role: "remoterole" not found. 01020036:3: The requested configuration item ( /Common/remoterole remoterole) was not found.

You may have to delve into /config/_.conf and find the reference to "remoterole" and delete it.

That's another problem - the files /config/*.conf files are basically empty - they have no reference to any of my old config. the /config/bigip_base.conf file has a couple of references to the correct hostname and the management IP, but that's it. It seems like it's trying to load the old config (from where??!!!) into /config, but there's zero documentation about this process. So frustrated...

You may check the directory /config/bigpipe/ for configuration files. Please proceed as recommended by Josh to look for incompatible settings. Now you can try to re-run:

/usr/libexec/bigpipe daol

As the option 'base' indicates, perhaps the base config would be loaded only.

Just to close out this thread, I opened a case and the engineer advised me to execute the /usr/libexec/bigpipe daol command, which did load the configuration - both the base, and the ltm config.

Hi -

I first did a "cpcfg HD1.1" to copy the config file from the partition running v10.2.4 to the partition running v11.4.1. Then I rebooted into HD1.1 which had v11.4.1 HF8 installed on it.

That simply worked. I had no other issues.

Jayanth