This Post is the last part of Configuring Azure Hub and Spoke – Configure Forced Tunnel so all traffic (paritcularly internet traffic) can be routed via the IPsec tunnel. Overall Topology Environment *On-prem Environment has a pair of Fortinet Fortigate firewalls with a public IP of 4.4.4.4 *Hub and Spoke are on different subscriptions. Note: […]
How to Configure Azure Hub and Spoke Topology Part 3 – Forced Tunnel Read More »
This post is about configuring VRRP between Fortinet Fortigate and Cisco Environment Fortigate firewall and Cisco router’s interfaces are configured using sub-interface, the physical interface will also work here. 100 is the VRRP Group ID FortiGate Firewall has a higher priority 255, so it will be the master Cisco Configuration Fortinet FortiGate Firewall Configuration As
How to Configure VRRP between Fortinet and Cisco Read More »
Environment Forti AP U431F – WiFi 6/AX enabled access points FortiGate Firewall is used as Wireless Controller to upgrade the firmware for Forti AP FortiGate Firewall and Forti AP are on different VLAN/Networks DHCP Option 138 is configured on Windows Server 2022 to point to the FortiGate (Wireless Controller) address Issue Solution Go to the
How to Fix Forti AP Rebooting Loop – Fail to Write the Image Read More »
Environment Forti AP U431F – WiFi 6/AX enabled access points FortiGate Firewall is used as Wireless Controller FortiGate Firewall and Forti AP are on different VLAN/Networks. DHCP Option 138 is configured on Windows Server 2022 to point to the FortiGate (Wireless Controller) address Error You can see the Image ID is “MERU SECONDARY“ Solution You
How to Fix Forti AP boot loop – Wrong Image Read More »
Issue Summary FortiGuard ID: FG-IR-22-377CVE ID: CVE-2022-40684Severity: Critical / CVSS: 9.6 Specific versions of Fortinet FortiOS (FortiGate Firewall) and FortiProxy may allow an unauthenticated attacker to perform operations on the administrative interface via specially crafted HTTP or HTTPS requests. Affected Products FortiOS version 7.0.0 to 7.0.6 FortiOS version 7.2.0 through 7.2.1 FortiProxy: From 7.0.0 to
This post is about the configuration of IPsec VPN between Azure and Fortinet Fortigate firewall, as part 2 of the post “How to Configure Azure Hub and Spoke Topology” Overall Topology Environment *On-prem Environment has a pair of Fortinet Fortigate firewalls with a public IP of 4.4.4.4 *Virtual Network Gateway (with local gateway and connection
How to Configure IPsec VPN between Azure and Fortigate Firewall Read More »
This serial of posts is about configuring Azure Hub and Spoke topology, as well as connecting Azure with On-prem environment over IPsec VPN. Overall Topology Environment *On-prem Environment has a pair of Fortinet Fortigate firewalls with a public IP of 4.4.4.4 *Hub and Spoke are on different subscriptions. Note: they can sit within the same
How to Configure Azure Hub and Spoke Topology Part 1 Read More »
This post is about configuring LACP between FS and Cisco Switches. Environment * FS Switch end * Cisco Switch end * 4x 10G connection in between FS switch configuration ====Change the port speed to 10G as our Cisco 9300 can only support 10G ====Configure the LACP Cisco Switch configuration LACP status Useful links https://www.cisco.com/c/en/us/td/docs/ios/12_2sb/feature/guide/gigeth.html https://resource.fs.com/mall/file/user_manual/s5860-20sq-and-s5860-24xb-u-switches-configuration-guide.pdf
How to Configure LACP between FS and Cisco Read More »
This post is to fix the “Set-Csuser : This cmdlet has been deprecated. Use the new Set-CsPhoneNumberAssignment and Remove-CsPhoneNumberAssignment cmdlets instead” error in Teams PowerShell. Environment *Microsoft Teams configured with Direct Routing for PSTN calling *All users Were migrated from On-Prem Skype for Business *All AD users are created locally in Domain Controller first, then
How to Fix “Set-Csuser : This cmdlet has been deprecated” in Teams PowerShell Read More »
This post is about configuring LACP between Juniper QFX (EVPN-VXLAN design) and VMware ESXi hosts. Environment *2x Juniper QFX 5120 Switches configured with EVPN-VXLAN, the design is a Collapsed Spine Fabric as described below: https://www.juniper.net/documentation/en_US/release-independent/solutions/topics/task/configuration/collapsed-spine-fabric-cloud-dc-configuring.html *If you connect your ESXi hosts directly to the QFX switches, you have to use LACP in between as this
How to Connect Juniper QFX EVPN-VXLAN and VMware ESXi using LACP Read More »
