- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Announcing Quantum R82.10!
Learn MoreOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
What you have found aligns perfectly with the behavior you are seeing.
I can't see why a Netscaler or any other device would try to use or take over another system's MAC address, unless you got extremely unlucky and the Netscaler and the cluster happened to dynamically derive the exact same VMAC address for their use. Here is how the Check Point cluster computes the VMAC to use:
|
First 24 bits |
Unique constant value. |
00:1C:7F |
|
Next 8 bits |
VSX Virtual System ID. |
|
|
Last 16 bits |
Unique value that the Management Server
assigns to each cluster object. This makes the VMAC value unique for each managed cluster. |
Unique value for each cluster |
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY