- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Having an unusual issue with a cluster firewall interface. Firewall was rebooted and post reboot one side of the sync interface is showing an issue where the inbound is up but the outbound is down. The other side is UP & UP.
fw1-cxl1:0]# cphaprob -a if
Required interfaces: 7
Required secured interfaces: 1
eth7 Inbound: UP Outbound: DOWN (6062.3 secs) sync(secured), multicast
eth5 UP non sync(non secured), multicast (eth5.71 )
bond2 UP non sync(non secured), multicast, bond Load Sharing (bond2.32 )
bond0 UP non sync(non secured), multicast, bond Load Sharing (bond0.17 )
bond1 UP non sync(non secured), multicast, bond Load Sharing (bond1.80 )
bond0 UP non sync(non secured), multicast, bond Load Sharing (bond0.245 )
eth5 UP non sync(non secured), multicast (eth5.246 )
Any obvious (to you!) ideas what might cause this before I roll up my sleeves?
TIA
Just to close the circle on this. My issue turned out to be a problem with mis-matching count of CoreXL instances on both nodes. Visible under cpview 'SysInfo'. Once I matched the number of instances by changing the config in cpconfig and rebooting, the previous stable status was restored.
Why it stopped using the sync interface IP addresses while the mismatch occurred is unknown.
What is the physical setup of the sync interface? Just an Ethernet cable or connected through a switch?
igmp snooping on switch side could be a cause too.
you can verify that by setting the cluster to unicast or broadcast for testing purpose.
See sk20576.
Just to close the circle on this. My issue turned out to be a problem with mis-matching count of CoreXL instances on both nodes. Visible under cpview 'SysInfo'. Once I matched the number of instances by changing the config in cpconfig and rebooting, the previous stable status was restored.
Why it stopped using the sync interface IP addresses while the mismatch occurred is unknown.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 30 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION