Forum Discussion
HA config sync issue in lab
Hi Friends,
I need help! I just started learning about f5 and while I was labbing HA with two virtual devices, facing challenges even thou I tried multiple times to do the reconfiguration. Kindly help me solve the issue. I have created couple of VS on bigip1 and when I try it to sync bigip1 to the group which has peer bigip2 it gives below errors.
===============================================================================================
Changes Pending
1 devices with older configuration
Recommended action: Synchronize this device to group device-group-failover-2c1fa5e3ab07
Getting below logs on bigip2
Sat Dec 22 23:01:51 IST 2018errbigip1tmm[10479]01340004HA Connection detected dissimilar peer: local npgs 1, remote npgs 1, local npus 1, remote npus 2, local pg 0, remote pg 0, local pu 0, remote pu 1. Connection will be aborted.
Thanks for your help Hemant
- Raman_KaushikRet. Employee
"NTP not configured on device 10.3.0.146 - within a trust"
Make sure that you have NTP configured and in sync.
https://support.f5.com/csp/article/K10240
- cciehemant_3007
Nimbostratus
Thanks for help!!
But both these virtual appliances are on same VM so I assume time is in sync. I am currently unable to add internet connectivity to my appliances. Is defining NTP is mandatory?
Thanks Hemant
- Raman_KaushikRet. Employee
Your configuration synchronization (ConfigSync) operation may not function properly if the network time protocol (NTP) server is not configured on all the devices in a device group.
Configuring an NTP server is required for all device group members. If a BIG-IP system with no defined NTP server is added to a device group, the device group members may fail to synchronize their configuration, and the system in which no NTP server is configured will log the listed error message.
Refer--->https://support.f5.com/csp/article/K51323327
- cciehemant_3007
Nimbostratus
Ok, so I have now defined external NTP servers in both the device but problem remains same.
Device trust group remains in sync where as failover group is not able to sync.
Below are the logs from current active.
Mon Dec 24 11:40:00 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:40:05 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:40:40 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:40:57 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:41:01 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }.
- Raman_Kaushik_3Historic F5 Account
"NTP not configured on device 10.3.0.146 - within a trust"
Make sure that you have NTP configured and in sync.
https://support.f5.com/csp/article/K10240
- cciehemant_3007
Nimbostratus
Thanks for help!!
But both these virtual appliances are on same VM so I assume time is in sync. I am currently unable to add internet connectivity to my appliances. Is defining NTP is mandatory?
Thanks Hemant
- Raman_Kaushik_3Historic F5 Account
Your configuration synchronization (ConfigSync) operation may not function properly if the network time protocol (NTP) server is not configured on all the devices in a device group.
Configuring an NTP server is required for all device group members. If a BIG-IP system with no defined NTP server is added to a device group, the device group members may fail to synchronize their configuration, and the system in which no NTP server is configured will log the listed error message.
Refer--->https://support.f5.com/csp/article/K51323327
- cciehemant_3007
Nimbostratus
Ok, so I have now defined external NTP servers in both the device but problem remains same.
Device trust group remains in sync where as failover group is not able to sync.
Below are the logs from current active.
Mon Dec 24 11:40:00 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:40:05 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:40:40 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:40:57 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }. Mon Dec 24 11:41:01 IST 2018noticebigip1mcpd[4237]0107168eUnable to do incremental sync, reverting to full load for device group /Common/device-group-failover-2c1fa5e3ab07 device %cmi-mcpd-peer-/Common/bigip2.test.com from commit id { 30 6638437165593595024 /Common/bigip2.test.com } to commit id { 731 6638437410619421304 /Common/bigip1.test.com }.
- JacobCaballero
Nimbostratus
Double check your vlan and self IP that you want to use for HA. Setup NTP on both devices. Add the self ip to the config-sync, mirroring, anbd network failover dropdowns. Then establish the trust and then put them into the device group. Make sure that your device group is a failover group and not a sync only group. Assuming you did all of this correctly, I believe your issue has to do with a sizing issue. Look at this article. This should solve your problem.
https://support.f5.com/csp/article/K41410404
Let me know if this helps you! If it does please upvote this answer! I would greatly appreciate it.
- Isla777_377548
Nimbostratus
If you have enabled configuration synchronization on both peers in an HA pair, most of the configuration settings you configure on one peer will automatically sync to the other peer upon commit mypremiercreditcard.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com