Forum Discussion
Jorge_Cabanilla
Nimbostratus
NimbostratusModifying variable 'configsync.peerconfigtimeraw'
I'm having the next log all the time in both clustered devices BIGIP LTM 6800
Dec 28 16:13:23 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:13:46 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:13:53 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:14:17 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:14:24 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:14:46 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:14:53 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:15:16 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:15:23 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:15:47 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:15:54 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:16:17 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
Dec 28 16:16:23 bpimlb01 bigdbd[1837]: 01080038:5: Modifying variable 'configsync.peerconfigtimeraw'.
This is the version:
Kernel:
Linux 2.4.21-9.4.7.320.0smp
Package:
BIG-IP Version 9.4.7 320.1
Final Edition
This is the csTest.pl --v , output:
csTest.pl --v
Status of daemons:
All required daemons are up and running (MCPD, CSSD, HTTPD, and BigDBD).
Configsync configuration:
Failover address (Self): 172.30.0.1
Peer IP address: 172.30.0.2
Configsync port: 443
Configsync username: admin
Acceptable time difference: 600 seconds
Configsync auto detect status:
1 - Local config modified, recommend configsync to peer
Last change (Self): 12/28/2010 15:51:15 (1293580275)
Peer state is: known
Last change (Peer): 12/08/2010 01:23:08 (1291800188)
Last configsync: 12/08/2010 01:23:08 (1291800188)
Peer update interval: 30 (seconds)
Network connection status:
Local system is listening on configsync port (443).
Ping test to peer 172.30.0.2 succeeded.
SOAP connection test to peer 172.30.0.2 succeeded.
SOAP time difference check:
Within the acceptable range.
Product version test:
Major and minor product versions are identical. The maintenance
versions are different.
The configsync tests completed successfully. You can run this
diagnostic tool on the peer 172.30.0.2 for further information.
[root@bpimlb01:Active] log
Any idea how to fix this?
Thanks in advanced
hoolioCirrostratus
Hi Jorge,
There have been a few bugs and configuration scenarios over the versions that caused this. I suggest opening a case with F5 Support to find out what may be causing this message being logged.
Aaron
Jorge_CabanillaHi hoolio,
Running the "csTest.pl --v" tool it shows that maintenance versions are different, how can I check them and how can I make them the same?
[root@bpimlb01:Active] config csTest.pl --v
Status of daemons:
All required daemons are up and running (MCPD, CSSD, HTTPD, and BigDBD).
Configsync configuration:
Failover address (Self): 172.30.0.1
Peer IP address: 172.30.0.2
Configsync port: 443
Configsync username: admin
Acceptable time difference: 600 seconds
Configsync auto detect status:
1 - Local config modified, recommend configsync to peer
Last change (Self): 01/03/2011 11:37:14 (1294083434)
Peer state is: known
Last change (Peer): 12/28/2010 17:02:01 (1293584521)
Last configsync: 12/28/2010 17:02:01 (1293584521)
Peer update interval: 30 (seconds)
Network connection status:
Local system is listening on configsync port (443).
Ping test to peer 172.30.0.2 succeeded.
SOAP connection test to peer 172.30.0.2 succeeded.
SOAP time difference check:
Within the acceptable range.
Product version test:
Major and minor product versions are identical. The maintenance
versions are different.
The configsync tests completed successfully. You can run this
diagnostic tool on the peer 172.30.0.2 for further information.
[root@bpimlb01:Active] config