Maas_Tunnel Mismatched

[DominusRex23]

Hi Checkmates,

I'm running into a strange issue with an ElasticXL cluster where the mass_tunnel interface on both firewalls shows mismatched IPv4 addresses. One member has X.X.3.80, while the other two show X.X.3.71.

I’ve already tried correcting the IP via Clish

Then I fetch the topology and install the policy from management. Everything looks fine for a moment—but after a while, the problematic member reverts to its previous IP address automatically.

All members are active, and I’ve confirmed the config change was applied correctly. But something keeps overwriting it. Has anyone seen this behavior before?

• Is there a sync mechanism or config push that could be causing this?
• Could it be tied to a misconfigured object in SmartConsole or a lingering topology cache?
• Any tips on making the change stick permanently?

Appreciate any insights. Thanks!

[Dmitrie_Shaiman · Accepted solution]

Hi @DominusRex23  -

In general, it is not recommended to correct the IP of a MaaS tunnel via clish.

A proper investigation is required. Please raise a Service Request (TAC ticket) and share it with us.
Thank you.

[the_rock]

I cant speak for elasticxl, but I know for regular clusterxl, it pretty much applies what @Dmitrie_Shaiman had said, though sounds like same method would be applicable in your case.

Andy