Forum Discussion

Kevin_Bozman_15's avatar
Kevin_Bozman_15
Icon for Nimbostratus rankNimbostratus
Oct 07, 2014

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

I upgraded a box Friday night with no problem and let it run active in production for a few days. Today I ran the upgrade on the other box and when I went to sync the config to the newest box I get t...
application delivery
availability
LTM
management
system upgrades
telsey_91061's avatar
telsey_91061
Icon for Nimbostratus rankNimbostratus

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.

 

Kai_Wilke's avatar
Kai_Wilke
Icon for MVP rankMVP
Oct 24, 2017

Hi Telsey,

 

whenever is experience this error message I simply switch from "Incremental Sync" to "Full Sync", then sync the device group as usual and finally turn on the "Incremental Sync" option again.

 

Well, changing something in the object which raises the error will also make sure the "Incremental Sync" will catch those objects...

 

Cheers, Kai