RX packets overrun-gigamon-GigaVUE-OS

RX packets overrun-gigamon-GigaVUE-OS
0

RX packets overrun-gigamon-GigaVUE-OS

Vendor: gigamon

OS: GigaVUE-OS

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

Remediation Steps:
Packet overruns usually occur when there are too many packets being inserted into the port’s memory buffer, faster than the rate at which the kernel is able to process them.

How does this work?
Login to the device’s CLI, change to enable mode and issue “show port stats”. This would present a table with statistics about the all the ports.

Why is this important?
Need total packets received in order to calculate the ratio of total dropped packets with respect to the total packets received.

Without Indeni how would you find this?
The traffic statistics of network interfaces can be manually reviewed through the CLI.

gigamon-show-port-stats

name: gigamon-show-port-stats
description: Fetch port stats
type: monitoring
monitoring_interval: 5 minutes
requires:
    vendor: gigamon
    os.name: GigaVUE-OS
    privileged-mode: 'true'
comments:
    network-interface-rx-dropped:
        why: |
            Need to determine which ports are dropping packets on ingress. Dropping ingress packets on a network port indicates that too much traffic is coming from either a TAP or SPAN, and would require the admin to provision a higher speed port (1G -> 10G -> 40G -> 100G). When a tool port shows ingress packet drops it indicates that too much traffic is being aggregated from the network ports and would require either the configuration of a GigaStream (LAG) or provision of higher speed ports.
        how: |
            Login to the device's CLI, change to enable mode and issue "show port stats". This would present a table with statistics about the all the ports.
        without-indeni: |
            The traffic statistics of network interfaces can be manually reviewed through the CLI.
        can-with-snmp: true
        can-with-syslog: false
        vendor-provided-management: |
            Can be done through Fabric Manager (FM) GUI with REST API calls.
    network-interface-rx-packets:
        why: |
            Need total packets received in order to calculate the ratio of total dropped packets with respect to the total packets received.
        how: |
            Login to the device's CLI, change to enable mode and issue "show port stats". This would present a table with statistics about the all the ports.
        without-indeni: |
            The traffic statistics of network interfaces can be manually reviewed through the CLI.
        can-with-snmp: true
        can-with-syslog: false
        vendor-provided-management: |
            Can be done through Fabric Manager (FM) GUI with REST API calls.
steps:
-   run:
        type: SSH
        command: show port stats
    parse:
        type: AWK
        file: gigamon-show-port-stats.parser.1.awk

cross_vendor_rx_overrun

// 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 CrossVendorRxOverrun() extends NearingCapacityWithItemsTemplateRule(
  ruleName = "cross_vendor_rx_overrun",
  ruleFriendlyName = "All Devices: RX packets overrun",
  ruleDescription = "Indeni tracks the number of packets that had issues and alerts if the ratio is too high.",
  usageMetricName = "network-interface-rx-overruns",
  limitMetricName = "network-interface-rx-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 overrun rate. Review the ports below.",
  alertItemDescriptionFormat = "%.0f packets overrun out of a total of %.0f received.",
  baseRemediationText = "Packet overruns usually occur when there are too many packets being inserted into the port's memory buffer, faster than the rate at which the kernel is able to process them.",
  alertItemsHeader = "Affected Ports")(
  RemediationStepCondition.VENDOR_CISCO ->
    """|
       |In a small number of cases, the overrun counter may be incremented because of a software defect. However, in the majority of cases, it indicates that the receiving capability of the interface was exceeded. Nothing can be done on the device that reports overruns. If possible, the rate that frames are coming should be controlled at the remote end of the connection.
       |1. Run the "show interface" command to review the interface overrun & underun counters and the bitrate. Consider to configure the "load-interval 30" interface sub command to improve the accuracy of the interface measurements.
       |2. If the number of overruns is high, the hardware should be upgraded.
       |
       |In case of high bandwidth utilization:
       |1. Run the "show interface" command to review the interface counters and the bitrate. Consider to configure the "load-interval 30" interface sub command to improve the accuracy of the interface measurements.
       |2. If the interface bitrate is too high and close to the upper bandwidth limit consider to use multiple links with the port-channel technology or upgrade the bandwidth of the link.
       |3. Consider to implement QoS in case of high bandwidth utilization.""".stripMargin,
  RemediationStepCondition.VENDOR_JUNIPER ->
    """|The issue can not be resolved on the device that reports overruns. The rate that frames are coming should be controlled at the remote end of the connection.
       |1. Run the “show interface extensive” command to review the interface overrun counters. 

       |2. If the number of overruns is high, consider upgrading the hardware.
       |3. 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>""".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
)