RX packets dropped ratio too high-gigamon-GigaVUE-OS

RX packets dropped ratio too high-gigamon-GigaVUE-OS
0

RX packets dropped ratio too high-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 drops usually occur when the rate of packets received is higher than the device’s ability to handle.

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 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.

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

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_drop

// 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 CrossVendorRxDrop() extends NearingCapacityWithItemsTemplateRule(
  ruleName = "cross_vendor_rx_drop",
  ruleFriendlyName = "All Devices: RX packets dropped ratio too high",
  ruleDescription = "Indeni tracks the number of packets that had issues and alerts if the ratio is too high.",
  usageMetricName = "network-interface-rx-dropped",
  limitMetricName = "network-interface-rx-packets",
  applicableMetricTag = "name",
  threshold = 0.5,
  minimumValueToAlert = 100.0, // We don't want to alert if the number of packets is really low
  alertDescription = "Some network interfaces and ports are experiencing a high drop rate. Review the ports below.",
  alertItemDescriptionFormat = "%.0f dropped packets identified out of a total of %.0f received.",
  baseRemediationText = "Packet drops usually occur when the rate of packets received is higher than the device's ability to handle.",
  alertItemsHeader = "Affected Ports")(
  RemediationStepCondition.VENDOR_CISCO ->
    """|
       |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. Check for traffic bursts and high traffic utilization.
       |2. Use the "show hardware rate-limit" NX-OS command (if supported) to determine if packets are being dropped because of a rate limit.
       |3. Execute the "show policy-map interface control-plane" NX-OS command to determine if packets are being dropped because of a QoS policy.
       |4. Use the "show hardware internal statistics rates" to determine if packets are being dropped by the hardware.
       |5. Run the "show hardware internal statistics pktflow all" NX-OS command to display per ASIC statistics, including packets into and out of the ASIC. This command helps to identify where packet loss is occurring.""".stripMargin,
  RemediationStepCondition.VENDOR_JUNIPER ->
    """|1. Run the “show interface extensive” command to review the interface statistics.
       |2. Check for packet drops and input/output traffic rate.
       |3. Run the “show class-of-service interface x/x/x detail"  to determine any QoS policy applied to interface which may cause packet drops.
       |4. If the interface is saturated, the number of packets dropped by the is indicated by the input queue of the I/O Manager ASIC. This number increments once for every packet that is dropped by the ASIC's RED mechanism.
       |5. 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">Ethernet Switching and Layer 2 Transparent Mode Feature Guide for Security Devices</a>
       |6. 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 
)