- 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
Improve Your Security Posture with
Threat Prevention and Policy Insights
Overlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Good Morning,
I have a single CP 5800 running R80.30 that has a single interface configured with multiple (128) VLANS. I now need to set the uplink to a Bond so I can use vPC from a pair of Cisco N5K
from what I have read it appears that I need to
1. Delete the VLANS which will remove them from the interface as well as the firewall configuration
2. Create the Bond group
3. Add the VLAN including IP address, VLAN number and make it a member of the Bond.
As I am lazy and not really looking forward to doing this is there a smarter way of doing this ?
I have learnt my lesson, next time I need to put VLANS on an interface I will create the Bond, even if it is a single interface, and then create the VLANS.
Could I follow the advice given in Solved: How to add VLAN interface in cluster - Check Point CheckMates and
Delete the VLANS via the GUI then using the CLI and using excel or similar create something like
add interface Bond5 vlan 3128
set interface Bond5.3128 ipv4-address 192.168.200.2 mask-length 24
save config
Then in Smart Console Get Interface without topology, then update the topology on the bond, I assume I would also need to update the topology on all the other interfaces, or is Smart Console smart enough to deal with that?
Cheers
If I were you, I would do it clish method. Just write down all the commands needed (change vlan ID and ip on each new line for new vlan) and then simply paste that into clish. Before doing that though, maybe save the current config by running from expert -> clish -c "show configuration" > /var/log/config.txt
And yes, the link you pasted is perfect reference. And no, you are NOT lazy, because if you were, I dont think you would have put 5% of effort into your research : - )
Cheers,
Andy
Sounds about right.
Thanks Val,
Which part sounds right, me being lazy, having to do each vlan through the GUI or being able to generate the CLI commands and copy and paste 🙂
Cheers
lol, either would work, but CLI is the way
Thanks, have a great week
If I were you, I would do it clish method. Just write down all the commands needed (change vlan ID and ip on each new line for new vlan) and then simply paste that into clish. Before doing that though, maybe save the current config by running from expert -> clish -c "show configuration" > /var/log/config.txt
And yes, the link you pasted is perfect reference. And no, you are NOT lazy, because if you were, I dont think you would have put 5% of effort into your research : - )
Cheers,
Andy
Thanks for the replies, looks like CLI is the way to go, I will update the post after I have made the change, may be a week or two
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 25 | |
| 20 | |
| 8 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 |
Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY