Interfaces used to install a policy on ClusterXL Gateways

[pattymcpherson]

When installing a policy on clusterXL gateways,   does the management server send the policy via the management interfaces of the Gateways or does is get send to the ClusterXL IP Address (VIP)?

[Chris_Atkinson]

The member IP defined in SmartConsole.

[PhoneBoy]

For ClusterXL, the IP that is always used to push policy to cluster members is the main IP of each cluster member.
This is listed in the General tab of the network object for each individual cluster member.
And yes, the policy is pushed to both members.
What interface that traffic will be sent on depends on the routing configuration, both on the gateways and the management.

Note that in R82 with ElasticXL, the policy will be pushed similar to how it operates on Maestro today (policy sent to the SMO IP, which replicates to other members).

[Martin_Raska]

Is there any change for the behaviour? The customer has dual ISP on GW cluster and management for some reason sometimes its trying to push policy over public IP ISP-B instead of public IP ISP-A which is the main IP. Is there any mechanism that management will choose because it is causing issues?

I am adding a screenshot where Mamangent decided to push policy over ISP-B which is NOT main IP.

[PhoneBoy]

I may have been wrong about the behavior to begin with 🙂
TAC may need to be consulted here.