FortiADC
FortiADC enhances the scalability, performance, and security of your applications whether they are hosted on premises or in the cloud.
JohnDevNet_FTNT
Article Id 198488
Description

This article describes some basic commands for troubleshooting IP Routing, ARP and Interface configuration.


Scope

FortiADC


Solution

INTERFACE CONFIGURATION, VERIFICATION AND TROUBLESHOOTING

1) Show IP interface configuration:

Example:

FortiADC-VM # diagnose netlink ip list

IP=127.0.0.1 MASK=255.255.255.0 index=1 devname=lo
IP=127.129.1.1 MASK=255.255.255.255 index=1 devname=lo
IP=192.168.157.78 MASK=255.255.255.0 index=4 devname=port1
IP=172.16.100.100 MASK=255.255.255.255 index=4 devname=port1
IP=172.16.100.100 MASK=255.255.255.0 index=5 devname=port5
IP=192.168.82.100 MASK=255.255.255.0 index=7 devname=port2
IP=10.10.10.100 MASK=255.255.255.0 index=9 devname=port10
IP=169.254.59.16 MASK=255.255.0.0 index=17 devname=haport0
IP=172.30.10.79 MASK=255.255.255.0 index=18 devname=VLAN_10

FortiADC-VM (root) # get router info routing-table kernel-connected

C       10.10.10.0/24 dev port10  proto kernel  scope link  src 10.10.10.100
C       169.254.0.0/16 dev haport0  proto kernel  scope link  src 169.254.59.16
C       172.16.100.0/24 dev port5  proto kernel  scope link  src 172.16.100.100
C       172.30.10.0/24 dev VLAN_10  proto kernel  scope link  src 172.30.10.79
C       192.168.82.0/24 dev port2  proto kernel  scope link  src 192.168.82.100
C       192.168.157.0/24 dev port1  proto kernel  scope link  src 192.168.157.78

2) The address MAC of a specific interface:

# get system interface port5:

type                          : physical
mode                          : static
vdom                          : root
redundant-master              :
ip                            : 172.16.100.100/24
ip6                           : ::/0
allowaccess                   : https ping ssh snmp http telnet
mtu                           : 1500
speed                         : auto
status                        : up
mac-addr                      : 00:0c:29:55:3b:38
secondary-ip                  : disable
ha-node-secondary-ip          : disable

3) ARP cache table:

FortiADC-VM (root) # diagnose netlink neighbor list

ifindex=9 ifname=port10 10.10.10.80 00:50:56:c0:00:0a state=00000004 use=5653 confirm=11653 update=5653 ref=0
ifindex=1 ifname=lo 192.168.157.78 00:00:00:00:00:00 state=00000040 use=5668 confirm=11668 update=5668 ref=0
ifindex=5 ifname=port5 172.16.100.1 00:0c:29:5b:36:cc state=00000002 use=626 confirm=626 update=626 ref=1
ifindex=5 ifname=port5 172.16.100.80 00:50:56:c0:00:05 state=00000004 use=4169 confirm=10169 update=78 ref=0
ifindex=4 ifname=port1 192.168.157.1 state=00000001 use=53 confirm=16375 update=253 ref=1
ifindex=1 ifname=lo 172.16.100.100 00:00:00:00:00:00 state=00000040 use=5493 confirm=11493 update=5493 ref=0

4) Display IP routing table:

(M) FortiADC-VM (root) # get router info routing-table all

Codes: K - kernel route, C - connected, S - static, O - OSPF, P - PPPoE
       i - isp route, > - selected route, * - FIB route
 
S   0.0.0.0/0 [10/0] via 192.168.157.1 inactive
C>* 10.10.10.0/24 is directly connected, port10
C>* 169.254.0.0/16 is directly connected, haport0
C>* 172.16.100.0/24 is directly connected, port5
C>* 192.168.82.0/24 is directly connected, port2

Contributors