Network port(s) running in half duplex-fortinet-FortiOS
Vendor: fortinet
OS: FortiOS
Description:
Indeni will alert one or more network ports is running in half duplex.
Remediation Steps:
Many times ports are in half duplex due to an autonegotation error or a misconfiguration.
|
|1. Monitor hardware network operations and speed by using the "diag hardware deviceinfo nic " FortiOS command.
|2. Run the command "diag hardware deviceinfo nic " command to display a list of hardware related names and values. Review the next link for more details: http://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-toubleshooting-54/troubleshooting_tools.htm
|3. Run the hidden FortiOS command “fnsysctl cat /proc/net/dev” to get a summary of the interface statistics.
|4. Check for a mismatch in the speed and duplex interface settings on both sides of a cable, or for a damaged cable. Try to manually configure both sides to the same mode when you can. Review the next link “Symptoms of Ethernet speed/duplex mismatches” for more info: http://kb.fortinet.com/kb/documentLink.do?externalID=10653
How does this work?
This script logs into the Fortinet firewall using SSH and retrieves the output of the “get system interface physical” FortiOS command. The output includes all the interface related information and statistics.
Why is this important?
Capture the physical interface duplex in human readable format such as full or half. In modern network environments it is very uncommon to see half-duplex interfaces, and that should be an indication for a potential exception. More details can be found to the next link: http://help.fortinet.com/cli/fos50hlp/56/Content/FortiOS/fortiOS-cli-ref-56/config/system/interface.htm
Without Indeni how would you find this?
It is possible to poll this data through SNMP.
fortios-get-system-interface
name: fortios-get-system-interface
description: Fortinet firewall check interface stats
type: monitoring
monitoring_interval: 1 minute
requires:
vendor: fortinet
os.name: FortiOS
product: firewall
comments:
network-interface-state:
why: |
Capture the physical interface state. If a physical interface transitions from up to down an alert will be raised. More details can be found to the next link:http://help.fortinet.com/cli/fos50hlp/56/Content/FortiOS/fortiOS-cli-ref-56/config/system/interface.htm
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" and "get system interface" FortiOS commands. The output includes all the interface related information and statistics.
can-with-snmp: true
can-with-syslog: true
network-interface-speed:
why: |
Capture the physical interface speed in human readable format such as 1G, 10G, etc. More details can be found to the next link: http://help.fortinet.com/cli/fos50hlp/56/Content/FortiOS/fortiOS-cli-ref-56/config/system/interface.htm
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" and "get system interface" FortiOS commands. The output includes all the interface related information and statistics.
can-with-snmp: true
can-with-syslog: false
network-interface-duplex:
why: |
Capture the physical interface duplex in human readable format such as full or half. In modern network environments it is very uncommon to see half-duplex interfaces, and that should be an indication for a potential exception. More details can be found to the next link: http://help.fortinet.com/cli/fos50hlp/56/Content/FortiOS/fortiOS-cli-ref-56/config/system/interface.htm
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" FortiOS command. The output includes all the interface related information and statistics.
can-with-snmp: true
can-with-syslog: false
network-interface-mode:
why: |
Capture the the interface IP addressing allocation type: static, from external dhcp or external pppoe. More details can be found to the next link: http://help.fortinet.com/cli/fos50hlp/56/Content/FortiOS/fortiOS-cli-ref-56/config/system/interface.htm
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" FortiOS command. The output includes all the interface related information and statistics.
can-with-snmp: false
can-with-syslog: false
network-interface-type:
why: |
Capture the the interface type e.g. vdom-link, tunnel, physical. More details can be found to the next link: http://help.fortinet.com/cli/fos50hlp/56/Content/FortiOS/fortiOS-cli-ref-56/config/system/interface.htm
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" and "get system interface" FortiOS commands. The output includes all the interface related information and statistics.
can-with-snmp: true
can-with-syslog: false
network-interface-ipv4-address:
why: "Capture the physical interface IPv4 address. \n"
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" and "get system interface" FortiOS commands. The output includes all the interface related information and statistics.
can-with-snmp: true
can-with-syslog: false
network-interface-ipv4-subnet:
why: |
Capture the interface IPv4 subnet mask.
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "get system interface physical" and "get system interface" FortiOS commands. The output includes all the interface related information and statistics.
can-with-snmp: true
can-with-syslog: false
network-interface-admin-state:
why: |
Capture the interface administrative status. Alerts won't fire for interfaces that are administratively down."
how: |
This script logs into the Fortinet firewall using SSH and retrieves the output of the "show system interface" command.
can-with-snmp: true
can-with-syslog: false
steps:
- run:
type: SSH
file: get_system_interface.remote.1.bash
parse:
type: AWK
file: get_system_interface.parser.1.awk
cross_vendor_network_port_duplex_half
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/crossvendor/cross_vendor_network_port_duplex_half.scala