If VDOMs are enabled on your FortiGate unit, all routing related CLI commands must be performed within a VDOM and not in the global context. |
B | BGP. The routing protocol used. |
10.160.0.0/23 | The destination of this route including netmask. |
[20/0] | 20 indicates and administrative distance of 20 out of a range of 0 to 255. 0 is an additional metric associated with this route, such as in OSPF |
10.142.0.74 | The gateway, or next hop. |
port3 | The interface used by this route. |
2d18h02m | How old this route is, in this case almost three days old. |
tab | table number. This will be either 254 (unicast) or 255 (multicast). |
vf | virtual domain of the firewall. This is the vdom index number. If vdoms are not enabled, this number will be 0. |
type | type of routing connection. Valid values include: 0 - unspecific 1 - unicast 2 - local 3 - broadcast 4 - anycast 5 - multicast 6 - blackhole 7 - unreachable 8 - prohibited |
proto | type of installation. This indicates where the route came from. Valid values include: 0 - unspecific 2 - kernel 11 - ZebOS routing module 14 - FortiOS 15 - HA 16 - authentication based 17 - HA1 |
prio | priority of the route. Lower priorities are preferred. |
->10.11.201.0/24 (->x.x.x.x/mask) | the IP address and subnet mask of the destination |
pref | preferred next hop along this route |
gwy | gateway - the address of the gateway this route will use |
dev | outgoing interface index. This number is associated with the interface for this route, and if VDOMs are enabled the VDOM will be included here as well. If an interface alias is set for this interface it will also be displayed here. |