FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
This article provides a basic test to use when a ping to the next hop router from a worker blade fails.
This connectivity test can be used when it is possible to ping the ELBC cluster inside/outside from the router but it is not possible to ping the next hop router from the worker blade.
The FortiGate receiving the packet may or may not be the one which originated the echo request, therefore pinging from a worker blade may work or fail.
Follow the below recommendation for connectivity test during initial testing of ELBC:
In intra-chassis mode
• To perform connectivity tests for all the FortiGate worker blades, it is easier to force the hashing on one blade only by setting all the other blades as redundant blades. In this way, a connectivity test should be successful for this blade. Go through all the blades as active with all the others backup in the same way to test them all. All ping tests should be working.
In inter-chassis mode (or Intra-chassis mode)
• Remove worker blade from the Service Group and test worker blades one by one.