Perimeter Switch Configuration with Fortiswitch (Non-Fortilink)

By Manny Fernandez

May 1, 2019

Perimeter Switch Configuration with Fortiswitch (Non-Fortilink)

One of the designs I normally do for customers when they purchase Highly Available firewalls is HA perimeter switches. When using Fortiswitches, you can easily configure the switches with Fortilink which is integrated into the Fortigate GUI and as such can be managed via the GUI or via FortiManager (Centralized Manager). However in this quick post, I am going to use a pair of 108E POE Fortiswitches in stand-alone mode to configure them as perimeter Layer 2 switches handling multiple ISPs and multiple Fortigate Firewalls. Below is a moch up diagram of what something like this would look like.

Perimeter Switch.jpg

In the above scenario, I am configuring three ISPs. I will show how you can configure the following scenarios:

Scenario One – You will consume three ports on each Fortigate and three ports on each Fortiswitch. Each port on the switch will be an access port with 1-8 ports in a “trunk” (or port-channel for you Cisco folks) that is passing the different VLANs that you create.

Scenario Two – In this scenario, the Fortigates will have a single (or multiple in LAG or 802.3ad) 802.1q trunk port that passes all three ISP VLANs and each Fortigate will have multiple VLANs under the single physical (or LAG) port.

Either way, the switch configuration will have similarities and I will point them out.

First thing you should do is upgrade these switches to the 6.x code release.

NOTE: To console into these switches, you need to set the speed to 115200

Configuring the VLANs

We will now create VLANs for each ISP. In my scenario, I have FPL, AT&T and Comcast using VLANs 100, 101, and 102 respectively.

Above you can see I have already created two VLANs. This configuration is accessible via the ‘Switch’, ‘VLAN’ section of the switch GUI.

On the top right hand side of the ‘VLAN’ section, you need to click the ‘Add VLAN’ button.

Next you will add the VLAN ID under the ‘ID’ field. Give it a description. If you have read my blog posts before, I always say to use something meaningful. You can leave the rest default for now and click ‘Add’.

Now we can see that we have three VLANs 100 for FPL, 101 for Comcast and 102 for AT&T.

Configuring the Ports

Although I configured three physical ports using VLAN 100, 101, and 102, the goal of this configuration is to have different ISPs configured across different switches in case of a switch failure. Maybe have ISP1 (the primary) and ISP3 (the tertiary) on one switch and ISP2 (the secondary) on the other switch.

To configure the switch ports, go to ‘Switch’ then ‘Interface’ and the ‘Physical’

For the access-layer switch ports, set the ‘Native VLAN’ to whatever you want the VLAN ID to be.

I am using port 8 of the switches as a trunk port between the two perimeter switches. As you can see above. You can set the ‘Native VLAN’ to anything you want but the ‘Allowed VLANs’ sections needs to contain the multiple VLANs you created above (in our case 100, 101, and 102).

From the command line, we can see the physical access ports configured as well as the ‘tagged’ (802.1q) port.

You can view this by entering the following command:

show switch interface

We can also see the VLANs

This can be seen using the following command:

show switch vlan

Hope this helps.

Perimeter Switch Configuration with Fortiswitch (Non-Fortilink)

Configuring the VLANs

Configuring the Ports

Recent posts