Packet capture, also known as sniffing or packet analysis, records some or all of the packets seen by a network interface (that is, the network interface is used in promiscuous mode). They can compare your configurations, line by line, and highlight parts that are new, modified, or deleted.įor instructions, see your difference program’s documentation. There are many such difference-finding programs, such as WinMerge ( ) and the original diff ( ). You want to recreate something configured previously, but do not remember what the settings were.ĭifference programs can help you to quickly find all changes.A previously configured feature is no longer functioning, and you are not sure what in the configuration has changed.You can compare backups of the core configuration file with your current configuration. To configure the severity threshold, go to Log&Report > Log Config > Global Log Settings. To enable logging of different types of events, go to Log&Report > Log Config > Other Log Settings.ĭuring troubleshooting, you may find it useful to reduce the logging severity threshold for more verbose logs, to include more information on less severe events. The FortiWeb appliance must be enabled to record event, attack, and traffic log messages otherwise, you cannot analyze the log messages for events of that type. FortiWeb appliances can record log messages when errors occur that cause failures, upon significant changes, and upon processing events.ĭepending on the type, log messages may appear in either the event, attack, or traffic logs. Log messages often contain clues that can aid you in determining the cause of a problem. 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. Traceroute to 192.0.2.55 (192.0.2.55), 32 hops max, 72 byte packetsįor details about CLI commands, see the FortiWeb CLI Reference:įor details about troubleshooting connectivity, see Connectivity issues.īoth ping and traceroute require that network nodes respond to ICMP. If the host is not reachable, you can use traceroute to determine the router hop or host at which the connection fails: You can do this from the FortiWeb appliance using CLI commands.įor example, you might use ping to determine that 192.0.2.87 is reachable: If your FortiWeb appliance cannot connect to other hosts, try using ICMP ( ping and traceroute) to determine if the host is reachable or to locate the node of your network at which connectivity fails, such as when static routes are incorrectly configured. Some CLI commands provide troubleshooting information not available through the web UI third-party tools on external hosts can test connections from perspectives that cannot be achieved locally.
Troubleshooting methods and tips may use: To locate network errors and other issues that may prevent connections from passing to or through the FortiWeb appliance, FortiWeb appliances feature several troubleshooting tools.
0 kommentar(er)
