Description | This article describes the effects of route priority on PING operations from the FortiGate CLI. |
Scope | FortiGate. |
Solution |
Network:
IP=10.47.1.80->10.47.1.80/255.255.240.0 index=3 devname=port1
1. Static Route or SD-WAN member have the same priority.
S* 0.0.0.0/0 [1/0] via 10.47.15.254, port1, [1/0]
Behavior: A ping from FortiGate CLI sourcing from the respective IP addresses of Port1 and Port2 will work in both cases.
execute ping-options source 10.47.1.80
execute ping-options source 10.47.17.80 execute ping 1.1.1.1
2. Static Route or SD-WAN member have different priority.
S* 0.0.0.0/0 [1/0] via 10.47.15.254, port1, [1/0]
Behavior:
execute ping 1.1.1.1
Ping with source IP of Port2 will fail since traffic will egress on Port1 (preferred) instead of Port2.
execute ping 1.1.1.1 --- 1.1.1.1 ping statistics ---
execute ping-options source 10.47.17.80 execute ping-options interface port2 execute ping 1.1.1.1 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.