- Products
- Learn
- Local User Groups
- Partners
- More
What's New in R82.10?
Watch HereWhen the Agents Attack
A Live Look at Agentic Exposure Validation
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
CheckMates Fest
Hello all,
We have 3 VSX appliances which work in VSLS mode. I created new regular VLAN interface (bond0.111) on one of the virtual systems. Everything on the management seemed fine, but after that I noticed that VLAN interface was created only on one of the VSX members and it's missing on the others. Hence currently we have only one Active VS and the others are in DOWN state, which is a normal behaviour after one of the VSs has more interfaces than the others. I didn't try to add the interface manually on the other two members, because we prefer to configure everything on the VSX cluster from the SmartConsole. We've never seen that issue on the previous version R80.30. It started when we upgraded to R81.10. I have tried cpstop/cpstart on the affected VS, but it didn't help. I know we can try to create the missing interface manually, but this is not the point. I want when I create something from the SmartConsole to be working properly.
The software version of the VSX appliances is R81.10 with JHF Take 45.
Have you ever seen similar issue on your environments? Ticket was opened also to TAC.
Thank you!
sk92784 solved the issue.
Can you provide a screenshot that the VLAN is existing in one member and not in the other one?
try to force fetching conf file by vsx fetch on affected vs https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_VSX_AdminGuide/Topics-VSXG/CLI/vsx...
please compare fwkern.conf files from both member
fwkern.conf is identical on all 3 members. I will try "vsx fetch" together with removing and adding the interface again, if vsx fetch doesn't help. This is the second time we face similar issue since we upgraded to R81.10 and I'm afraid we will face it again in future and won't be good if we have to run "vsx fetch" or another manual command every time. I'm waiting TAC for some reasonable explanation.
ok, share the fix when TAC's job will be done 🙂
sk92784 solved the issue.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 66 | |
| 22 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 2 | |
| 2 |
Thu 09 Jul 2026 @ 10:00 AM (CEST)
Schutz souveräner Workloads: Check Point & die AWS European Sovereign CloudThu 09 Jul 2026 @ 11:00 AM (CEST)
The Cloud Architects Series: Check Point Edge Protection SD-WAN & SASEThu 09 Jul 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #9 - What's New with Check Point Email SecurityFri 10 Jul 2026 @ 11:00 AM (IDT)
CheckMates Live Netherlands - Sessie 48: Nieuwe Check Point Workspace SecurityTue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 09 Jul 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #9 - What's New with Check Point Email SecurityFri 10 Jul 2026 @ 11:00 AM (IDT)
CheckMates Live Netherlands - Sessie 48: Nieuwe Check Point Workspace SecurityTue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 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