"Critical configuration files mismatch across cluster members" for fwkern.conf


#1

We identify the following as a difference between two clustered devices due to md5sum mismatch.


The reason is that each device assigns it's own IP for fwx_bridge_reroute_ipv4.


Should we ignore this difference?



[GW2:0]# cat /opt/CPsuite-R80/fw1/boot/modules/fwkern.conf
fwha_active_standby_bridge_mode=1
fwha_monitor_if_link_state=1
fwx_bridge_reroute_ipv4=x.x.x.14
[GW2:0]#


[GW1:0]# cat /opt/CPsuite-R80/fw1/boot/modules/fwkern.conf
fwha_active_standby_bridge_mode=1
fwha_monitor_if_link_state=1
fwx_bridge_reroute_ipv4=x.x.x.13
[GW1:0]#






#2

Interesting. I would think we should ignore it, since we ignore unique lines in other files.


#3

I am seeing something similar in the /$FWDIR/conf/local.arp file. There is a static NAT listed in the active members local.arp file that are not in the standby members. I believe this is by design.


#4

This difference is safe to ignore