EasyManua.ls Logo

Fortinet FortiMail-100 - Troubleshooting Tools; Ping and Traceroute

Fortinet FortiMail-100
174 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Testing the installation Troubleshooting tools
FortiMail™ Secure Messaging Platform Version 4.0 Patch 1 Install Guide
Revision 2 161
http://docs.fortinet.com/Feedback
Troubleshooting tools
To locate network errors and other issues that may prevent email from passing to or
through the FortiMail unit, FortiMail units feature several troubleshooting tools. You may
also be able to perform additional tests from your management computer or the
computers of SMTP clients and servers.
This section includes the following topics:
Ping and traceroute
Nslookup
Telnet connections to the SMTP port number
Log messages
Greylist and sender reputation displays
Mail queues and quarantines
Packet capture
Ping and traceroute
If your FortiMail unit cannot connect to other hosts, you may be able to use ICMP ping and
traceroute to determine if the host is reachable or locate the node of your network at which
connectivity fails, such as when static routes are incorrectly configured. You can do this
from the FortiMail unit using CLI commands.
For example, you might use ICMP ping to determine that 172.16.1.10 is reachable
(commands that you would type are highlighted in bold; responses from the FortiMail unit
are not bolded):
FortiMail-400 # 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:
FortiMail-400 # 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
Note: Both ping and traceroute require that network nodes respond to ICMP ping. If you
have disabled responses to ICMP on your network, hosts may appear to be unreachable to
ping and traceroute, even if connections using other protocols can succeed.

Table of Contents

Other manuals for Fortinet FortiMail-100

Related product manuals