Synchronisation Problem

[vijayant]

Failover takes place successfully.

cphaprob state

1 10.0.0.1 100% active
2 (local) 10.0.0.2 0% down

[Expert@MOON]# cphaprob -ia list

Built-in Devices:

Device Name: Problem Notification
Current state: problem

Device Name: Interface Active Check
Current state: OK

Device Name: HA Initialization
Current state: OK

Device Name: Load Balancing Configuration
Current state: OK

Registered Devices:

Device Name: Synchronization
Registration number: 0
Timeout: none
Current state: problem
Time since last report: 174268 sec

Device Name: Filter
Registration number: 1
Timeout: none
Current state: OK
Time since last report: 41.2 sec

Device Name: cphad
Registration number: 2
Timeout: 2 sec
Current state: OK
Time since last report: 0.1 sec

Device Name: fwd
Registration number: 3
Timeout: 2 sec
Current state: OK
Time since last report: 0.4 sec


For primary all is fine

I can see traffic between Primary and Secondary Firewalls on Sinc interface.---> So its not down.

There are alot of traffic in error between primary and secondary

please check the attachment...

Now where should I dig in ..

[daz306td]

I'd be very interested to see replies on this as I am experiencing the same issue and it does seem to be effecting a VPN tunnel we have confgiured on the cluster.

I am tempted to try THIS

[daz306td]

Originally Posted by daz306td

I am tempted to try THIS

I'm unable to find a 'mgha' directory on my system (SPLAT)

[vijayant]

Hi daz306td

Please check for 'mgha' on Smart Center Server.

1 10.0.0.1 100% active
2 (local) 10.0.0.2 0% down

down may indicate a cable issue.

For my case I have registered some of the devices (cphaprob -register) that i supose gave me problem initially. Later I removed it and rebooted but still problem is there. But now I see it is resolved automatically. I dont know how. But now as I ping the peer sync ip from any cluster member, I get very high ing response 450 ms to 9000 ms. I also checked for traffic on sync interface at that time but found nothing. So I suspect it may be the interface issue or the cable may be faulty.