Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Static & Dynamic Routing Monitor

The Static & Dynamic Routing Monitor displays the routing table on the FortiGate including all static and dynamic routing protocols in IPv4 and IPv6. You can also use this monitor to view the firewall policy route.

To view the routing monitor in the GUI:
  1. Go to Dashboard > Network.
  2. Hover over the Routing widget, and click Expand to Full Screen. The Routing monitor opens.
  3. To view the policy monitor, click the Policy tab.
  4. To filter the Interfaces and Type columns:
    1. Hover over the column heading, and click the Filter/Configure Column icon.
    2. Click Group By This Column, then click Apply.
  5. (Optional) Click Save as Monitor to save the widget as monitor.

To look up a route in the GUI:
  1. Click Route Lookup.
  2. Enter an IP address in the Destination field, then click Search. The matching route is highlighted on the Routing monitor.
To view the routing table in the CLI:

# get route info routing-table all

Sample output:

Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP

O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

* - candidate default

 

Routing table for VRF=0

S* 0.0.0.0/0 [1/0] via 10.0.10.1, To-HQ-A

[1/0] via 10.0.12.1, To-HQ-MPLS

[1/0] via 10.10.11.1, To-HQ-B

[1/0] via 10.100.67.1, port1

[1/0] via 10.100.67.9, port2

C 10.0.10.0/24 is directly connected, To-HQ-A

C 10.0.10.2/32 is directly connected, To-HQ-A

C 10.0.11.0/24 is directly connected, To-HQ-B

C 10.0.11.2/32 is directly connected, To-HQ-B

C 10.0.12.0/24 is directly connected, To-HQ-MPLS

C 10.0.12.2/32 is directly connected, To-HQ-MPLS

C 10.1.0.0/24 is directly connected, port3

C 10.1.0.2/32 is directly connected, port3

C 10.1.0.3/32 is directly connected, port3

C 10.1.100.0/24 is directly connected, vsw.port6

To look up a firewall route in the CLI:

# diag firewall proute list

Sample output:

list route policy info(vf=root):

 

id=0x7f450002 vwl_service=2(BusinessCritialCloudApp) vwl_mbr_seq=4 5 3 dscp_tag=0xff 0xff flags=0x0 tos=0x00 tos_mask=0x00 protocol=0 sport=0:65535 iif=0 dport=1-65535 oif=3(port1) oif=4(port2) oif=18(To-HQ-MPLS)

source(1): 0.0.0.0-255.255.255.255

destination wildcard(1): 0.0.0.0/0.0.0.0

internet service(4): Microsoft.Office.365(4294837472,0,0,0, 33182) Microsoft.Office.Online(4294837475,0,0,0, 16177) Salesforce(4294837976,0,0,0, 16920) GoToMeeting(4294836966,0,0,0, 16354)

hit_count=0 last_used=2020-03-30 10:50:18

 

id=0x7f450003 vwl_service=3(NonBusinessCriticalCloudApp) vwl_mbr_seq=4 5 dscp_tag=0xff 0xff flags=0x0 tos=0x00 tos_mask=0x00 protocol=0 sport=0:65535 iif=0 dport=1-65535 oif=3(port1) oif=4(port2)

source(1): 0.0.0.0-255.255.255.255

destination wildcard(1): 0.0.0.0/0.0.0.0

internet service(2): Facebook(4294836806,0,0,0, 15832) Twitter(4294838278,0,0,0, 16001)

hit_count=0 last_used=2020-03-30 10:50:18

 

id=0x7f450004 vwl_service=4(Ping-Policy) vwl_mbr_seq=1 2 dscp_tag=0xff 0xff flags=0x0 tos=0x00 tos_mask=0x00 protocol=1 sport=0:65535 iif=0 dport=1-65535 oif=16(To-HQ-A) oif=17(To-HQ-B)

Static & Dynamic Routing Monitor

The Static & Dynamic Routing Monitor displays the routing table on the FortiGate including all static and dynamic routing protocols in IPv4 and IPv6. You can also use this monitor to view the firewall policy route.

To view the routing monitor in the GUI:
  1. Go to Dashboard > Network.
  2. Hover over the Routing widget, and click Expand to Full Screen. The Routing monitor opens.
  3. To view the policy monitor, click the Policy tab.
  4. To filter the Interfaces and Type columns:
    1. Hover over the column heading, and click the Filter/Configure Column icon.
    2. Click Group By This Column, then click Apply.
  5. (Optional) Click Save as Monitor to save the widget as monitor.

To look up a route in the GUI:
  1. Click Route Lookup.
  2. Enter an IP address in the Destination field, then click Search. The matching route is highlighted on the Routing monitor.
To view the routing table in the CLI:

# get route info routing-table all

Sample output:

Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP

O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

* - candidate default

 

Routing table for VRF=0

S* 0.0.0.0/0 [1/0] via 10.0.10.1, To-HQ-A

[1/0] via 10.0.12.1, To-HQ-MPLS

[1/0] via 10.10.11.1, To-HQ-B

[1/0] via 10.100.67.1, port1

[1/0] via 10.100.67.9, port2

C 10.0.10.0/24 is directly connected, To-HQ-A

C 10.0.10.2/32 is directly connected, To-HQ-A

C 10.0.11.0/24 is directly connected, To-HQ-B

C 10.0.11.2/32 is directly connected, To-HQ-B

C 10.0.12.0/24 is directly connected, To-HQ-MPLS

C 10.0.12.2/32 is directly connected, To-HQ-MPLS

C 10.1.0.0/24 is directly connected, port3

C 10.1.0.2/32 is directly connected, port3

C 10.1.0.3/32 is directly connected, port3

C 10.1.100.0/24 is directly connected, vsw.port6

To look up a firewall route in the CLI:

# diag firewall proute list

Sample output:

list route policy info(vf=root):

 

id=0x7f450002 vwl_service=2(BusinessCritialCloudApp) vwl_mbr_seq=4 5 3 dscp_tag=0xff 0xff flags=0x0 tos=0x00 tos_mask=0x00 protocol=0 sport=0:65535 iif=0 dport=1-65535 oif=3(port1) oif=4(port2) oif=18(To-HQ-MPLS)

source(1): 0.0.0.0-255.255.255.255

destination wildcard(1): 0.0.0.0/0.0.0.0

internet service(4): Microsoft.Office.365(4294837472,0,0,0, 33182) Microsoft.Office.Online(4294837475,0,0,0, 16177) Salesforce(4294837976,0,0,0, 16920) GoToMeeting(4294836966,0,0,0, 16354)

hit_count=0 last_used=2020-03-30 10:50:18

 

id=0x7f450003 vwl_service=3(NonBusinessCriticalCloudApp) vwl_mbr_seq=4 5 dscp_tag=0xff 0xff flags=0x0 tos=0x00 tos_mask=0x00 protocol=0 sport=0:65535 iif=0 dport=1-65535 oif=3(port1) oif=4(port2)

source(1): 0.0.0.0-255.255.255.255

destination wildcard(1): 0.0.0.0/0.0.0.0

internet service(2): Facebook(4294836806,0,0,0, 15832) Twitter(4294838278,0,0,0, 16001)

hit_count=0 last_used=2020-03-30 10:50:18

 

id=0x7f450004 vwl_service=4(Ping-Policy) vwl_mbr_seq=1 2 dscp_tag=0xff 0xff flags=0x0 tos=0x00 tos_mask=0x00 protocol=1 sport=0:65535 iif=0 dport=1-65535 oif=16(To-HQ-A) oif=17(To-HQ-B)