Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • CLI Reference

    Home FortiWeb 7.6.1 CLI Reference
    7.6.1
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.10
    7.2.9
    7.2.8
    7.2.7
    7.2.6
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.3.23
    6.3.19
    6.3.18
    6.3.17
    6.3.16
    6.3.15
    6.3.14
    6.3.13
    6.3.11
    6.3.10
    6.3.9
    6.3.7
    6.3.6
    6.3.5
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.2
    6.1.1
    5.7.0
    5.6.1
    5.6.0

    network rtcache

    network rtcache

    Use this command to display the routing cache.

    Unlike network route, this command displays the cache of the most recently used routes, not necessarily the entire configuration. (You may have configured many routes, and these configurations will be saved to disk and appear in network route, but rarely used ones will not usually appear in the route cache, which keeps recently used routes in RAM for performance reasons.)

    To use this command, your administrator account’s access control profile must have rw or w permission to the sysgrp area. For details, see Permissions.

    Syntax

    diagnose network rtcache list

    Example

    This example displays the ARP cache.

    172.20.120.52(port1)->256.256.256.256(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 3181 expires 0 error 0 used 855

    172.20.120.100(port3)->172.20.120.256(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 434 expires 0 error 0 used 0

    172.20.120.230(port1)->256.256.256.256(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 47386 expires 0 error 0 used 7

    10.0.1.1(none)->10.0.1.1(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 223 expires 0 error 0 used 29551

    0.0.0.0(none)->10.0.1.1(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 223 expires 0 error 0 used 7387

    ::(none)->::1(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 155845 expires 0 error 0 used 417

    ::(none)->2607:f0b0:f:420:20c:29ff:fe4d:3ad3(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 354923 expires 0 error 0 used 1

    ::(none)->2607:f0b0:f:420:20c:29ff:fe4d:3ae7(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 2590615 expires 0 error 0 used 0

    ::(none)->2607:f0b0:f:420:20c:29ff:fe4d:3af1(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 2590615 expires 0 error 0 used 0

    ::(none)->2607:f0b0:f:420::(port1) via ::, pri 256 prot 0 scope 0 ref 0 lastuse 2590616 expires 214715722 error 0 used 0

    ::(none)->ff00::(port4) via ::, pri 256 prot 0 scope 0 ref 0 lastuse 2590615 expires 0 error 0 used 0

    ::(none)->ff00::(lo) via ::, pri -1 prot 0 scope 0 ref 1 lastuse 449431651 expires 0 error -101 used 1

    Example

    This example adds a route to the routing table.

    diagnose network route add vlan2 160.1.12.0 256.0.0.0 172.20.01.169 32 3 verify

    Related topics

    Previous
    Next

    network rtcache

    network rtcache

    Use this command to display the routing cache.

    Unlike network route, this command displays the cache of the most recently used routes, not necessarily the entire configuration. (You may have configured many routes, and these configurations will be saved to disk and appear in network route, but rarely used ones will not usually appear in the route cache, which keeps recently used routes in RAM for performance reasons.)

    To use this command, your administrator account’s access control profile must have rw or w permission to the sysgrp area. For details, see Permissions.

    Syntax

    diagnose network rtcache list

    Example

    This example displays the ARP cache.

    172.20.120.52(port1)->256.256.256.256(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 3181 expires 0 error 0 used 855

    172.20.120.100(port3)->172.20.120.256(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 434 expires 0 error 0 used 0

    172.20.120.230(port1)->256.256.256.256(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 47386 expires 0 error 0 used 7

    10.0.1.1(none)->10.0.1.1(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 223 expires 0 error 0 used 29551

    0.0.0.0(none)->10.0.1.1(lo) via 0.0.0.0, pri 0 prot 0 scope 0, ref 0 lastuse 223 expires 0 error 0 used 7387

    ::(none)->::1(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 155845 expires 0 error 0 used 417

    ::(none)->2607:f0b0:f:420:20c:29ff:fe4d:3ad3(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 354923 expires 0 error 0 used 1

    ::(none)->2607:f0b0:f:420:20c:29ff:fe4d:3ae7(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 2590615 expires 0 error 0 used 0

    ::(none)->2607:f0b0:f:420:20c:29ff:fe4d:3af1(lo) via ::, pri 0 prot 0 scope 0 ref 1 lastuse 2590615 expires 0 error 0 used 0

    ::(none)->2607:f0b0:f:420::(port1) via ::, pri 256 prot 0 scope 0 ref 0 lastuse 2590616 expires 214715722 error 0 used 0

    ::(none)->ff00::(port4) via ::, pri 256 prot 0 scope 0 ref 0 lastuse 2590615 expires 0 error 0 used 0

    ::(none)->ff00::(lo) via ::, pri -1 prot 0 scope 0 ref 1 lastuse 449431651 expires 0 error -101 used 1

    Example

    This example adds a route to the routing table.

    diagnose network route add vlan2 160.1.12.0 256.0.0.0 172.20.01.169 32 3 verify

    Related topics

    Previous
    Next