- 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 some issues with the checkpoints and getting them to talk to A-Side partner over Datacenter fabric ports.
Essentially, I have configured physical interface eth3 on the 6200’s with two vlan 401 and 403. My understanding is that these would be treated as a traditional trunk port. (802.1q encapsulation)
IS there any *special * configuration on checkpoint side to get this working? The other end is a FortiGate and they are telling me they cannot see my side.
we got it working . the issue was non related to checkpoint - thanks,
Yes, subinterfaces on Check Point (and Linux in general) are normal 802.1q VLAN trunks. No, there's no special configuration needed. You have to apply the configuration in a different place on a Check Point box than on a generic Linux box, but it's the same basic configuration.
How exactly did you configure the VLANs? What commands?
I configured thru the gaia web ui . interfaces > add new interface > vlan > choose parent interface eth3 > create vlan id.
With that config, eth3 handles 802.1q-tagged traffic for VLANs 401 and 403. Since eth3 doesn't have an IP address, it isn't handling untagged traffic, but you didn't mention anything about untagged, so I assume that's fine.
I guess the question now is what is a "Datacenter fabric port"? If it's switch infrastructure managed by someone who isn't you, maybe it isn't allowing tagged traffic?
Did you follow below?
I dont think they are considered traditional trunk port the way you described it.
Please be a little bit more specific in your description of interconnects:
1. Make and model of the switch you are connecting to
2. Switch trunk port (that CP unit is connected to) config
The fabric issue should be irrelevant, as you are not connecting to a fabric port, those should be used for switches interconnects, but otherwise pass all traffic.
If those are not a true fabric ports, but trunk interconnects, make sure that your VLANs are enabled on them as well.
we got it working . the issue was non related to checkpoint - thanks,
Please share the cause and resolution anyway, thanks
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 5 | |
| 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 DefenseTue 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 DefenseAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION