- Products
- Learn
- Local User Groups
- Partners
- More
Maestro Masters
Round Table session with Maestro experts
Hi Expert,
I facing Maestro cabing proble,. Topology as showing MHO is working in the Layer 2 mode . All the gateway are in the Core-Switch.
Bond1:Eth1-13 、Eth1-14、Eth2-13、 Eth2-14
Bond2:Eth1-15、Eth1-16、Eth2-15、 Eth2-16
Bridge:Bond1 、Bond2 (work at Tunk 802.3AD mode )
MHO and GW are running R81.10 version and T66 HF .
Base on this design can we cross connect the core switch or access switch between two MHO. Thanks !
@Anatoly @Lari_Luoma can you guys assist, please?
Looks like it should work
Hi Anatoly,
Thanks for your replay !
Topology desing have 3 bridge in the network :
We meet the MAC inconsistency problem , flowing is the error message In special Brige :
Then we open a technical case ,TAC tell us across device bond setting is not support. So We want clear know that there are some limitation on the Layer2 deployment and across device bond setting? Thanks !
Why do you think there is a cabling problem, how is STP / Portfast configured?
Hi Chris ,
Nice to see you again .
I am not sure there is a problem or not . All the interface are the trunk mode not change to edge/portfast port mode ,so have the STP on there but all the interface are in the forwarding statues .
Ok. For context I have the follow questions
* How is the distribution mode configured?
* What hashing mechanism is used on the bond/trunks?
Hi Chris ,
I comfirm form my enduser side that Core /distribute switch are using src/dst IP hash arithmetic . In the 2 MHO distribute mode using auto-topology(per-port) arithmetic .
Switch
I don't see any issues with this. What makes you doubt this kind of cabling?
Hi Lari,
We meet the MAC inconsistency issuse that tac tell us across device bond setting is not support . I think across device bond is very important in the netwrok design .hope you could give us advise ,Thanks !
Without knowing the details I cannot comment whether your configuration is supported, but if TAC is telling you it's not I would trust them.
Here are some general thoughts.
- In order to configure LACP bonding that peers with two different physical switches, the switches must have vPC, VSS or similar configured
- MAC inconsistency does not necessarily indicate a problem. Sometimes this is fixable by tuning the garbage collector threshold or ARP table size. Work with TAC to get the most accurate solution in your environment.
In addition what @Lari_Luoma it say to work with LACP /802.3ad (active/active) switch must be in stack. If they are independent then the bonding must be Active/Backup as well.
Keep in mind in A/B you must define the primary interface of the bond.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
13 | |
5 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY