https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-MDPS-on-an-exising-ClusterXL/m-p/180473#M33003 <P>ClusterXL R81.20T10.</P><P>I've read&nbsp; the SK about <A href="https://support.checkpoint.com/results/sk/sk138672" target="_self">Management Data Plane Separation</A> and would like to get a clarification&nbsp;&nbsp;about enabling it on an existing cluster of high-end appliances.</P><P>&nbsp;</P><P>The topology is currently simple, Mgmt is defined as Management interface with a dedicated subnet and there's just a static route through it for the SMS/Log subnet. The other interfaces serve the production traffic and only use dynamic routing.</P><P>I was then thinking of enabling MDPS through the HTML5 LOM and reconfigure the management plane as per the SK and I wonder if after reboot required to enable MDPS, does the cluster remains ACTIVE/STANDBY since the CPU allocation changes to accommodate MDPS, until the two cluster members have been set to use MDPS and also with the Sync set to MDPS as well.</P><P>In short, is there a moment in the configuration process where the cluster isn't synchronized anymore and could cause traffic disruption when failing over to configure the other member.</P> Wed, 10 May 2023 07:30:21 GMT Alex- 2023-05-10T07:30:21Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-MDPS-on-an-exising-ClusterXL/m-p/180473#M33003 <P>ClusterXL R81.20T10.</P><P>I've read&nbsp; the SK about <A href="https://support.checkpoint.com/results/sk/sk138672" target="_self">Management Data Plane Separation</A> and would like to get a clarification&nbsp;&nbsp;about enabling it on an existing cluster of high-end appliances.</P><P>&nbsp;</P><P>The topology is currently simple, Mgmt is defined as Management interface with a dedicated subnet and there's just a static route through it for the SMS/Log subnet. The other interfaces serve the production traffic and only use dynamic routing.</P><P>I was then thinking of enabling MDPS through the HTML5 LOM and reconfigure the management plane as per the SK and I wonder if after reboot required to enable MDPS, does the cluster remains ACTIVE/STANDBY since the CPU allocation changes to accommodate MDPS, until the two cluster members have been set to use MDPS and also with the Sync set to MDPS as well.</P><P>In short, is there a moment in the configuration process where the cluster isn't synchronized anymore and could cause traffic disruption when failing over to configure the other member.</P> Wed, 10 May 2023 07:30:21 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-MDPS-on-an-exising-ClusterXL/m-p/180473#M33003 Alex- 2023-05-10T07:30:21Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-MDPS-on-an-exising-ClusterXL/m-p/180548#M33011 <P>It is generally recommended you run this during a maintenance window because the management interface is unavailable for a short time during this process.<BR />See:&nbsp;<A href="https://support.checkpoint.com/results/sk/sk138672" target="_blank">https://support.checkpoint.com/results/sk/sk138672</A>&nbsp;<BR />Otherwise, I don't see any specific limitations related to sync.</P> Wed, 10 May 2023 17:08:34 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-MDPS-on-an-exising-ClusterXL/m-p/180548#M33011 PhoneBoy 2023-05-10T17:08:34Z