Troubleshooting
Page 132
FortiRecorder 2.4.2 Administration Guide
For example, you might use
ping
to determine that 172.16.1.10 is reachable:
FortiRecorder-200D#
execute ping 172.16.1.10
PING 172.16.1.10 (172.16.1.10): 56 data bytes
64 bytes from 172.16.1.10: icmp_seq=0 ttl=64 time=2.4 ms
64 bytes from 172.16.1.10: icmp_seq=1 ttl=64 time=1.4 ms
64 bytes from 172.16.1.10: icmp_seq=2 ttl=64 time=1.4 ms
64 bytes from 172.16.1.10: icmp_seq=3 ttl=64 time=0.8 ms
64 bytes from 172.16.1.10: icmp_seq=4 ttl=64 time=1.4 ms
--- 172.20.120.167 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.8/1.4/2.4 ms
or that 192.168.1.10 is
not
reachable:
FortiRecorder-200D#
execute ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10): 56 data bytes
Timeout ...
Timeout ...
Timeout ...
Timeout ...
Timeout ...
--- 192.168.1.10 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
3.
Use the
tracert
or
traceroute
command on both the camera (temporarily, the
computer) and FortiRecorder to locate the point of failure along the route, the router hop or
host at which the connection fails. For example, if it fails at the second hop, you might see:
FortiRecorder-200D#
execute traceroute 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 32 hops max, 72 byte
packets
1 192.168.1.2 2 ms 0 ms 1 ms
2 * * *
Each line lists the routing hop number, the IP address and FQDN (if any) of that hop, and the
3 response times from that hop. Typically a value of
<1ms
indicates a local router. The
asterisks ( * ) indicate no response from that hop in the network routing.
If the route is broken when it reaches the FortiRecorder, first examine its network interfaces
and routes. To display network interface addresses and subnets, enter:
FortiRecorder-200D#
show system interface
To display all recently-used routes (the routing table cache) with their priorities, enter:
FortiRecorder-200D#
diagnose netlink rtcache list
The index number of the route in the list of static routes in the web UI is not necessarily the
same as its position in the cached routing table (
diagnose netlink rtcache list
).
