ClusterXL issue with MDPS enabled

[the_rock]

Hey guys,

I really hope someone might be able to give some sigguestion/opinion on this, as to me, it makes no logical sense why this fails...could be because of mdps, not really sure. Anyway, to make long story short, customer is replacing their existing 4 15000 fws with new 4 9700 devices (2 separate clusters). We did migrate export from existing mgmt, imported to new one, connected both new clusters, built basic policy after setting up mdps, with ONLY 2 interfaces active (mgmt and sync).

But, here is the problem. Though policy is fine, when installed, only fw1 sdhows as active and fw is down (same on both clusters). We just assigned 169.254.x.x IPs as sync, since customer wanted to give it IP from same mgmt subnet, but that cannot work.

Oddly enough, pings to sync IP work from both members, but fw2 always shows as down...we tried cphastop; start, cprestart, reboot,. disable/re-enable cluster, no dice.

Worked with TAC, they kept telling us its layer 2 iussue, but I cant really understand how that can be the problem. Client even verified everything on of their Fortigates as well, all is allowed and even he was surprised they were "forcing" layer 2 argument.

Thoughts?

Thanks as always!

 

[the_rock]

Since they want brand new version installed, I will have client upgrade to R82.10, see what happens and we will do remote with TAC if that fails. Will update once done, hopefully tomorrow.

[the_rock · Accepted solution]

Hey guys,

We got all this working by updating clusters to R82.10. Not sure how that worked, as R82.10 release notes dont mention anything about mdps, but either way, Im so happy it was fine, and customer was very relieved. Web UI is fine, as well as cluster state.

Tx for everyone's help!!

[Vincent_Bacher]

The main thing is that it works and the customer is satisfied.

[the_rock]

Thats it!