Forum Discussion

Karol_Biernack2's avatar
Karol_Biernack2
Icon for Nimbostratus rankNimbostratus
Feb 07, 2017

Change conflict on cluster members.

Hello All

I can imagine that few of You will find this tool useful at some point

Problem Sync Summary StatusChanges Pending SummaryThere is a possible change conflict between f5-1.bigip.example.com and f5-2.bigip.example.com. Details Recommended action: Synchronize f5-1.bigip.example.com to group device_group_failover

Solution:

[root@f5-2:Standby:In Sync] share  /usr/local/bin/cmi_diff 10.1.20.242
    /Common/f5-1.bigip.example.com (192.168.2.128)                                      /Common/f5-2.bigip.example.com (192.168.2.129)
=== /Common/device_trust_group: 18 objects (2 diffs)

For sake of testing I created dummy node 1.1.1.1 and 1.1.1.2 respectively on other device and those are results

None                                           \    node_address {
                                           >       node_address_name "/Common/1.1.1.1"
                                           >       node_address_fqdn ""
                                           >       node_address_ephemeral 0
                                           >       node_address_addr 1.1.1.1
                                           >       node_address_app_id ""
                                           >       node_address_description ""
                                           >       node_address_fqdn_addr_type 0
                                           >       node_address_fqdn_down_interval 5
                                           >       node_address_fqdn_up_interval 3600
                                           >       node_address_autoscale 0
                                           >       node_address_conn_limit 0
                                           >       node_address_ratio 1
                                           >       node_address_dynamic_ratio 1
                                           >       node_address_rate_limit 0
                                           >       node_address_bigd_monitor_state 0
                                           >       node_address_monitor_state 0
                                           >       node_address_new_session_enable 2
                                           >       node_address_monitor_rule ""
                                           >       node_address_leaf_name "1.1.1.1"
                                           >       node_address_folder_name "/Common"
                                           >       node_address_strict_app_updates 0
                                           >    }

Output is a little bit clunky, but after redirecting it to file it should be easy to investigate