sync failed. The requested parent profile (tcp) was not found. upgrading two boxes from 11.2 - 11.6

Hi Kevin!

Never seen this issue before, but you could try to clear the config files (/config/bigip.conf and if you're using partitions /config/partitions/[partition name]/bigip.conf) and synchronize again. That could solve your issue.

/Patrik

I had similar issues but with various irules that all of sudden were needed to complete the sync but were actually deleted. It turns out this is an exisiting issues and its due to the mcpd database being out of sync with the text config file. Here is the solution article workaround

I ended up contacting support. Turns out the base TCP profile was different between the two units. We ended up removing that tcp profile from the bigip.conf and making a change to the masters config, resyncing and then it worked.

I had a similar issue after upgrading from 11.3 to 11.6. The message I got was mcpd[9330]: 01020036:3: The requested parent profile (/Common/analytics) was not found. Although this profile was showing in gui, it was missing in the bigip.conf file. To fix this I just synced back from the other unit, where the profile was present.

Is there a way to load this file by copying it from the same Version device

profile_base.conf

Is there a way to load this file by copying it from the same Version device

isn't it normally loaded when loading configuration?

[root@ve11c:Active:In Sync] config  tmsh load sys config
Loading system configuration...
  /defaults/asm_base.conf
  /defaults/config_base.conf
  /defaults/ipfix_ie_base.conf
  /defaults/ipfix_ie_f5base.conf
  /defaults/low_profile_base.conf
  /defaults/low_security_base.conf
  /defaults/policy_base.conf
  /defaults/wam_base.conf
  /defaults/analytics_base.conf
  /defaults/apm_saml_base.conf
  /defaults/app_template_base.conf
  /defaults/classification_base.conf
  /defaults/daemon.conf
  /defaults/profile_base.conf
  /defaults/sandbox_base.conf
  /defaults/security_base.conf
  /defaults/urldb_base.conf
  /usr/share/monitors/base_monitors.conf
Loading configuration...
  /config/bigip_base.conf
  /config/bigip_user.conf
  /config/bigip.conf
  /config/bigip_script.conf

here is the issue I had.

the devices platforms were also getting upgraded 2000 to 4000 series. So had to tweak the scf file from previous devices with the device type name and version etc. 1) upload the OS version which was on the 2000s base code and hf version before loading the edited scf file. (11.4 HF) which will make it similar to old boxes say HD1.1 2) create a new volume on these new 4000s install the New OS and HF version which in my case was 11.6 say HD1.3 run the commands cpcfg --source=HD1.1 HD1.3 This ensures that all the config is added to the new volume HD1.3 type switchboot and select HD1.3 as your default boot location reboot the box ...

This worked for me please try with caution and also in maintenance window. and also as this is new box you should not have any outages and quickly enable back the old boxes.

as far as the 4000s go , if this procedure does not light the green bulb you just have to reboot to the previous HD1.1 location.

I had almost the same issue when upgrading from 11.3 to 11.6, on one of the two devices the parent persistence profile "source_addr" was missing so synchronization was failing ... Two options to solve the issue : either force-synchronize the device with the correct profile to the other device, or edit manually the bigip.conf to add the missing parent profile ...

I know this thread is exceptionally old, but I just ran into a similar problem. I wasn't in the middle of an upgrade, but I receive the same type of sync issue. When attempting to sync the primary with the secondary, the sync would fail and state that the "tcp" protocol profile wasn't found which was strange because the "tcp" protocol profile was there on both systems.

To resolve the issue, I edited the default "tcp" protocol profile on the primary device by changing the "close wait" time from 5 seconds to 6 seconds. I figured this would force the system to write the file and update anything that it needed. After the change, I tried to sync the two devices and it worked without an issue. I then reversed my change and was still able to sync the configurations.

I am not sure why the issue occurred, but this did fix the issue for me.

I just ran into the same issue. I was able to back trace and found that someone modified the parent profile on the secondary. It caused us to not be able to sync. I reverted the changes back to default and we still couldn't sync. I followed the example above and removed from the bigip.conf on the secondary and we were able to sync. I've never seen this before prior to this issue. We are running version 12.1.2 HF2 so the issue is still present.