topic Dedicated Sync Interfaces as an internal or external interface in Firewall and Security Management

Dedicated Sync Interfaces as an internal or external interface

maddah87 — Wed, 31 Dec 2025 11:38:20 GMT

Hi,

Can one of the dedicated sync interfaces of 19100 or 19200 be used as an internal or external interface of a clustered environment.

early 2025 we had an issue of assigning one of the sync interfaces to an internal interface. we used different interfaces rather sticking in to that. Currently we try to match number of ports of one customer's req. If one of the sync can be used to internal or external interface we can refrain adding another line card.

Re: Dedicated Sync Interfaces as an internal or external interface

Martijn — Wed, 31 Dec 2025 13:24:59 GMT

The name of the port is just a name and to my knowledge you can use this port for any other type of interface.
But don't become confused when you see the name Sync in Gaia and SmartConsole in the interface section.

In ElasticXL the Sync is used for building the ExlasticXL setup so do not use the Sync in such setups.

Re: Dedicated Sync Interfaces as an internal or external interface

Chris_Atkinson — Wed, 31 Dec 2025 14:35:55 GMT

Also refer to sk92755 for supported SFPs for the Sync ports.

Re: Dedicated Sync Interfaces as an internal or external interface

Bob_Zimmerman — Wed, 31 Dec 2025 15:15:31 GMT

To help minimize potential confusion, you can build a bond and put the interface named Sync into the bond. That way, your topology says bond5.284 or whatever instead of Sync2.284. It keeps the interface name as an implementation detail, where it should be. Then if you want that interface to be 40g or 100g or whatever, you get a new card and change the physical interface which backs the bond.

Re: Dedicated Sync Interfaces as an internal or external interface

the_rock — Fri, 02 Jan 2026 02:14:17 GMT

Technically yes, it can be used for that. Personally, I would not do it, but thats just me. Anyone I know and ever worked with related to CP firewalls, used Sync as dedicated sync interface.

Re: Dedicated Sync Interfaces as an internal or external interface

Vincent_Bacher — Fri, 02 Jan 2026 08:54:59 GMT

Same here.

Re: Dedicated Sync Interfaces as an internal or external interface

the_rock — Fri, 02 Jan 2026 13:11:35 GMT

@Martijn made an EXCELLENT point. Say you set it as external, but you cant actually change the name, it would ALWAYS show as SYNC...would be way too confusing.

Re: Dedicated Sync Interfaces as an internal or external interface

Vincent_Bacher — Fri, 02 Jan 2026 13:39:50 GMT

This is why I would never use it as data interface.

Re: Dedicated Sync Interfaces as an internal or external interface

the_rock — Fri, 02 Jan 2026 13:41:07 GMT

💯

Re: Dedicated Sync Interfaces as an internal or external interface

Vincent_Bacher — Fri, 02 Jan 2026 14:51:11 GMT

Just as a heads-up: The competition from Sunnyvale, California actually lets you set an alias for an interface that fully replaces the original interface name. So unlike Check Point, you’ll actually see the alias name everywhere in the UI (and cli I think) instead of the default interface label.

Re: Dedicated Sync Interfaces as an internal or external interface

the_rock — Fri, 02 Jan 2026 15:06:11 GMT

Yes sir, done that before lol