- Products
- Learn
- Local User Groups
- Partners
- More
The State of Ransomware Q1 2026
Key Trends and Their Impact
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
Hey brother,
Here is something else to consider as well, but please be free to message me offline, happy to do remote, would just need to be either when Im taking a break or after hours, if okay with you.
*******************************
Since your new 9100s have different NIC layout (e.g. one ISP moved, new dedicated sync interface), yes — you’ll need to update the interface mappings in SmartConsole.
Here’s what to do:
Keep the same IP addresses and subnets that the old 5100 interfaces had (to avoid topology mismatches and policy issues).
In SmartConsole → Gateway Properties → Network Management:
Click each interface.
On the Advanced tab, check the Interface Name dropdown.
Choose the new interface name as it appears on the 9100 (e.g. eth1-01 instead of eth2).
Verify the topology and anti-spoofing settings are correct.
Make sure your Cluster Topology (under Cluster Object → Topology) reflects the correct network mapping for both new members:
Each member’s interface names should match what’s on the appliance.
Double-check your Sync interface — it must be the same subnet on both members and marked as "Cluster Synchronization".
Install policy after fixing all of that (with the “if fails” box unchecked for the first new member you bring in).
That’s the correct and clean way to handle the physical NIC name changes.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY