Network port(s) running in half duplex-checkpoint-gaia,secureplatform

Network port(s) running in half duplex-checkpoint-gaia,secureplatform
0

Network port(s) running in half duplex-checkpoint-gaia,secureplatform

Vendor: checkpoint

OS: gaia,secureplatform

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.
Review sk83760: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk83760",

How does this work?
The duplex of the interface is retrieved by running “ethtool”.

Why is this important?
If the interface has half-duplex setting, this will reduce throughput, and should be investigated.

Without Indeni how would you find this?
An administrator could login and manually check interface configuration, or use SNMP.

chkp-os-interfaces-novsx

name: chkp-os-interfaces-novsx
description: Get interface information
type: monitoring
monitoring_interval: 1 minute
requires:
    vendor: checkpoint
    and:
       -  or:
             -  os.name: gaia
             -  os.name: secureplatform
       -  or:
             -  vsx:
                    neq: 'true'
             -  mds: 'true'
comments:
    network-interface-state:
        why: |
            Interfaces in the "down" state could result in downtime or reduced redundancy.
        how: |
            The state of the interface is retrieved by running "ethtool".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-admin-state:
        why: |
            If the interface is disabled, then it is okay for it to be down. If the interface is enabled however, it should be up.
        how: |
            Retrieve the information by parsing the Gaia database in /config/active.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-speed:
        why: |
            If the interface speed is set to a low value, this could mean auto-negotiation is not working correctly and the interface does not utilize the full bandwidth available.
        how: |
            The speed of the interface is retrieved by running "ethtool".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-duplex:
        why: |
            If the interface has half-duplex setting, this will reduce throughput, and should be investigated.
        how: |
            The duplex of the interface is retrieved by running "ethtool".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-ipv4-address:
        why: |
            To be able to search for IP addresses in indeni, this data needs to be stored.
        how: |
            The IP address of the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-ipv4-subnet:
        why: |
            To be able to search for IP addresses in indeni, this data needs to be stored.
        how: |
            The subnet of the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-type:
        why: |
            The type of interface can be useful for administrators.
        how: |
            The type of the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-mtu:
        why: |
            The MTU sometimes needs to be adjusted. Storing this gives an administrator an easy way to view the MTU from a large number of devices, as well as identifying incorrectly set MTU.
        how: |
            The MTU of the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-mac:
        why: |
            To be able to search for MAC addresses in indeni, this data needs to be stored.
        how: |
            The MAC address of the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-description:
        why: |
            The description is an important way to identify interfaces.
        how: |
            Retrive the information by parsing the gaia database in /config/active.
        can-with-snmp: true
        can-with-syslog: false

    network-interface-tx-bits:
        why: |
            It is useful to know how much data has been transmitted by the interface.
        how: |
            How many bits sent by the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-rx-bits:
        why: |
            It is useful to know how much data has been received by the interface.
        how: |
            How many bits received by the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-tx-packets:
        why: |
            It is useful to know how many packets have been transmitted by the interface.
        how: |
            How many packets sent by the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-rx-packets:
        why: |
            It is useful to know how many packets have been received by the interface.
        how: |
            How many packets received by the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-tx-errors:
        why: |
            Transmit errors on an interface could indicate a problem.
        how: |
            The amount of transmit errors for the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-dropped:
        why: |
            Dropped packets on an interface could indicate a problem and potential traffic loss.
        how: |
            The amount of receive drops for the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-overruns:
        why: |
            Transmit overruns on an interface could indicate a problem.
        how: |
            The amount of transmit overruns for the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-overruns:
        why: |
            Receive overruns on an interface could indicate a problem.
        how: |
            The amount of receive overruns for the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-carrier:
        why: |
            A high carrier number could mean that the link is flapping.
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-rx-frame:
        why: |
            To get total number of recived frames on the the interfaces to understand
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "config/active".
        can-with-snmp: true
        can-with-syslog: false

    network-interfaces:
        why: |
            To get all the interfaces to collec the statistics of all the interfraces.
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "config/active".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-tx-collisions:
        why: |
            To get total number of tx-collisions on the interfaces to monitor duplex mis match issues.
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "config/active".
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-errors:
        why: |
            To get a total Recived erros on the interfaces
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "config/active".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-admin-state-logical:
        why: |
            To get a admin state of the interfaces to understand the state of the interface
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "config/active".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-state-logical:
        why: |
            To get a logical state of the interfaces to understand the state of the interface
        how: |
            The carrier counter for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "config/active".
        can-with-snmp: true
        can-with-syslog: false

    network-interface-:
        why: |
            To get the the list of all interface names
        how: |
            The carrier name for the interface is retrieved by running "ifconfig -a" as well as the Gaia
            database "/config/active"
        can-with-snmp: true
        can-with-syslog: false
steps:
   -  run:
          type: SSH
          file: show-interfaces-all-novsx.remote.1.bash
      parse:
          type: AWK
          file: show-interfaces-all-novsx.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