Is there anyway to get back the switch layout under the Manage FortiSwitch tab? In version 6.2.15 and earlier it displays pictorial diagram of the actual switches connected and shows you all the active/inactive ports etc. But in version 6.4 and upwards that display layout is no longer there. It's as if Fortinet went backwards with this aspect of the firmware upgrade.
Yes there's ways to get more redundancy but as for the ISL that's just the naming for a link between two FortiSwitches (unless using MCLAG in which case it's called ICL). Here's a couple examples of getting some better redundancy: docs.fortinet.com/document/fortiswitch/7.2.4/fortilink-guide/801204/single-fortigate-unit-managing-a-stack-of-several-fortiswitch-units - So there's a ring style between all the switches, theoretically if any one link in the topology is lost then the network should recover docs.fortinet.com/document/fortiswitch/7.2.4/fortilink-guide/780635/switch-redundancy-with-mclag - This one uses MCLAG and also improves redundancy. This gives additional scalability and performance advantages too I think this is a good topic to cover, I'll make a video on this (ie. has some more focus on redundancy/scale/performance considerations with ring topology and MCLAG topology)
Can I create a LAG across multiple FortiSwitch aka MC-LAG for redundancy? For example, I want to connect my server to multiple FortiSwitch with LACP LAG for redundancy. If yes, how can I achieve that on the FortiSwitch side?
Check out this video which shows how to configure MCLAG: th-cam.com/video/OpfhQxkQyog/w-d-xo.html After MCLAG is configured, then I assume your server can bond links with LACP? In which case, you go to WiFi & Switch Controller > FortiSwitch Ports > Trunk and Create New Trunk Group, select ports on both FortiSwitch MCLAG members
11/5000 拼音 翻译
Wonderful sharing! Thank you!
Im preparing myself for an implementation. And this is all i want... Thanks for this video...👍🤝
one of the best videos i seen!
thanks for uploading, keep them coming.
very very informative. keep posting more. much thanks
Very helpful! Keep them coming!
very helful, thanks !!!
Is there anyway to get back the switch layout under the Manage FortiSwitch tab? In version 6.2.15 and earlier it displays pictorial diagram of the actual switches connected and shows you all the active/inactive ports etc. But in version 6.4 and upwards that display layout is no longer there. It's as if Fortinet went backwards with this aspect of the firmware upgrade.
Excelent video, very helpful. Just one question, don´t you have to configure the ISL protocol in order to have real redundancy among switches...?
Yes there's ways to get more redundancy but as for the ISL that's just the naming for a link between two FortiSwitches (unless using MCLAG in which case it's called ICL).
Here's a couple examples of getting some better redundancy:
docs.fortinet.com/document/fortiswitch/7.2.4/fortilink-guide/801204/single-fortigate-unit-managing-a-stack-of-several-fortiswitch-units
- So there's a ring style between all the switches, theoretically if any one link in the topology is lost then the network should recover
docs.fortinet.com/document/fortiswitch/7.2.4/fortilink-guide/780635/switch-redundancy-with-mclag
- This one uses MCLAG and also improves redundancy. This gives additional scalability and performance advantages too
I think this is a good topic to cover, I'll make a video on this (ie. has some more focus on redundancy/scale/performance considerations with ring topology and MCLAG topology)
@@tothepointfortinet3823 Thanks for your answer and the links. Looking foward for those videos configurating and using ISL and ICL .
The second switch picked up a DHCP address from the default vlan. I need it to get an address from the fortilink subnet. How? Cheers!!
Can I create a LAG across multiple FortiSwitch aka MC-LAG for redundancy? For example, I want to connect my server to multiple FortiSwitch with LACP LAG for redundancy. If yes, how can I achieve that on the FortiSwitch side?
Check out this video which shows how to configure MCLAG:
th-cam.com/video/OpfhQxkQyog/w-d-xo.html
After MCLAG is configured, then I assume your server can bond links with LACP? In which case, you go to WiFi & Switch Controller > FortiSwitch Ports > Trunk and Create New Trunk Group, select ports on both FortiSwitch MCLAG members
Thanks!
Thanks!