- Products
- Learn
- Local User Groups
- Partners
- More
On-Premise SD-WAN Management
Register HereWhat's New in R82.10?
Watch Here AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
The Moment Before
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 |
|---|---|
| 12 | |
| 8 | |
| 5 | |
| 4 | |
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
Tue 28 Jul 2026 @ 11:00 AM (EDT)
Under the Hood - Check Point and Illumio – Modern Network Defense Against AI-Based ThreatsThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 20 Aug 2026 @ 10:00 AM (PDT)
AI Security Masters E13: READY OR NOT: Securing the AI Ent 5/5 - AI Research & Threat LandscapeTue 28 Jul 2026 @ 11:00 AM (EDT)
Under the Hood - Check Point and Illumio – Modern Network Defense Against AI-Based ThreatsThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 20 Aug 2026 @ 10:00 AM (PDT)
AI Security Masters E13: READY OR NOT: Securing the AI Ent 5/5 - AI Research & Threat LandscapeAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY