TX packets experienced errors-radware-alteon-os

TX packets experienced errors-radware-alteon-os
0

TX packets experienced errors-radware-alteon-os

Vendor: radware

OS: alteon-os

Description:
Indeni tracks the number of packets that had issues and alerts if the ratio is too high.

Remediation Steps:
Packet errors usually occur when there is a mismatch in the speed and duplex settings on two sides of a cable, or a damaged cable.

radware-api-config-portStatsTable

name: radware-api-config-portStatsTable
description: Fetch the packet statistics of the ports.
type: monitoring
monitoring_interval: 1 minute
requires:
    os.name: alteon-os
    vendor: radware
    or:
    -   vsx: 'true'
    -   standalone: 'true'
comments:
    network-interface-tx-bits:
        why: |
            Capture the interface Transmitted bits counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-bits:
        why: |
            Capture the interface Received bits counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-errors:
        why: |
            Capture the interface Transmit Errors counter. Transmit errors indicate an issue with duplex/speed matching.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-errors:
        why: |
            Capture the interface Receive Errors counter. Receive errors indicate an issue with duplex/speed matching.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-dropped:
        why: |
            Capture the interface Transmit Drop counter. Packet loss may have severe impact to the traffic utilization
            (retransmission for TCP apps) and to the performance of the applications.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-dropped:
        why: |
            Capture the interface Receive Drop counter. Packet loss may have severe impact to the traffic utilization
            (retransmission for TCP apps) and to the performance of the applications.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-packets:
        why: |
            Capture the interface Received Packet counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-packets:
        why: |
            Capture the interface Transmitted Packet counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
steps:
-   run:
        type: HTTP
        command: /config/PortStatsTable
    parse:
        type: JSON
        file: api-config-portStatsTable.parser.1.json.yaml

radware-api-config-portStatsTable

name: radware-api-config-portStatsTable
description: Fetch the packet statistics of the ports.
type: monitoring
monitoring_interval: 1 minute
requires:
    os.name: alteon-os
    vendor: radware
    or:
    -   vsx: 'true'
    -   standalone: 'true'
comments:
    network-interface-tx-bits:
        why: |
            Capture the interface Transmitted bits counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-bits:
        why: |
            Capture the interface Received bits counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-errors:
        why: |
            Capture the interface Transmit Errors counter. Transmit errors indicate an issue with duplex/speed matching.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-errors:
        why: |
            Capture the interface Receive Errors counter. Receive errors indicate an issue with duplex/speed matching.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-dropped:
        why: |
            Capture the interface Transmit Drop counter. Packet loss may have severe impact to the traffic utilization
            (retransmission for TCP apps) and to the performance of the applications.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-dropped:
        why: |
            Capture the interface Receive Drop counter. Packet loss may have severe impact to the traffic utilization
            (retransmission for TCP apps) and to the performance of the applications.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-rx-packets:
        why: |
            Capture the interface Received Packet counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
    network-interface-tx-packets:
        why: |
            Capture the interface Transmitted Packet counter. Knowing the amount of bits and packets flowing through an
            interface can help estimate an interface's performance and utilization.
        how: |
            This script gets the information using "/config/PortStatsTable" path through the Alteon API gateway.
        can-with-snmp: true
        can-with-syslog: false
steps:
-   run:
        type: HTTP
        command: /config/PortStatsTable
    parse:
        type: JSON
        file: api-config-portStatsTable.parser.1.json.yaml

cross_vendor_tx_error

// Deprecation warning : Scala template-based rules are deprecated. Please use YAML format rules instead.

package com.indeni.server.rules.library.templatebased.crossvendor

import com.indeni.server.rules.RuleContext
import com.indeni.server.rules.library.templates.NearingCapacityWithItemsTemplateRule
import com.indeni.server.rules.RemediationStepCondition

/**
  *
  */
case class CrossVendorTxError() extends NearingCapacityWithItemsTemplateRule(
  ruleName = "cross_vendor_tx_error",
  ruleFriendlyName = "All Devices: TX packets experienced errors",
  ruleDescription = "Indeni tracks the number of packets that had issues and alerts if the ratio is too high.",
  usageMetricName = "network-interface-tx-errors",
  limitMetricName = "network-interface-tx-packets",
  applicableMetricTag = "name",
  threshold = 0.5,
  minimumValueToAlert = 100.0, // We don't want to alert if the number of error packets is really low
  alertDescription = "Some network interfaces and ports are experiencing a high error rate. Review the ports below.",
  alertItemDescriptionFormat = "%.0f error packets identified out of a total of %.0f transmitted.",
  baseRemediationText = "Packet errors usually occur when there is a mismatch in the speed and duplex settings on two sides of a cable, or a damaged cable.",
  alertItemsHeader = "Affected Ports")(
  RemediationStepCondition.VENDOR_CISCO ->
    """|
       |1. Run the "show interface" command to review the interface error counters and the bitrate. Consider to configure the "load-interval 30" interface sub command to improve the accuracy of the interface measurements.
       |2. Check for a mismatch in the speed and duplex interface settings on two sides of a cable, or for a damaged cable.
       |3. Use the "show interface counters errors" NX-OS command to display detailed interface error counters. If you do not specify an interface, this command displays information about all Layer 2 interfaces.""".stripMargin,
  RemediationStepCondition.VENDOR_JUNIPER ->
    """|1. Run the "show interface extensive" command to review the interface error counters.

       |2. Check for a mismatch in the speed and duplex interface settings on the both sides.
       |3. Check the physical cable. It might be damaged or incorrect type is used.
       |4. Review the following article on Juniper tech support site: <a target="_blank" href="https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/show-interfaces-security.html#jd0e1772">Operational Commands</a>
       |5. If the problem persists, contact the Juniper Networks Technical Assistance Center (JTAC)""".stripMargin,
  RemediationStepCondition.VENDOR_FORTINET ->
    """
       |1. Run "diag hardware deviceinfo nic <interface>" command to display a list of hardware related error names and values. Review  the next link for more details: http://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-toubleshooting-54/troubleshooting_tools.htm
       |2. Run command "fnsysctl cat /proc/net/dev" to get a summary of the interface statistics.
       |3. Check for speed and duplex mismatch in the interface settings on both sides of a cable, and check for a damaged cable. Review the next link for more info: http://kb.fortinet.com/kb/documentLink.do?externalID=10653""".stripMargin
)