TX packets experienced collisions-paloaltonetworks-panos

TX packets experienced collisions-paloaltonetworks-panos
0

TX packets experienced collisions-paloaltonetworks-panos

Vendor: paloaltonetworks

OS: panos

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

Remediation Steps:
Packet collisions usually occur when there is a mismatch in duplex settings on two sides of a cable.

How does this work?
This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the number of packets transmitted through the interface.

Why is this important?
Tracking the number of packets flowing through each network interface is important to identify potential issues, spikes in traffic, etc.

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

panos-show-interface

name: panos-show-interface
description: Fetch interface information and statistics
type: monitoring
monitoring_interval: 15 minute
requires:
    vendor: paloaltonetworks
    os.name: panos
    product: firewall
comments:
    network-interface-admin-state:
        why: |
            If a network interface is set to be up (what's known as "admin up") but is actually down (a cable is not connected, the device on the other side is down, etc.) it is important to know.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for interfaces that are set to be up, but are actually down.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-speed:
        why: |
            Generally, these days network interfaces are set at 1Gbps or more. Sometimes, due to a configuration or device issue, an interface can be set below that (to 100mbps or even 10mbps). As that is usually _not_ the intended behavior, it is important to track the speed of all network interfaces.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the actual runtime speed of each interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-bandwidth-mbps:
        why: |
            Generally, network interfaces are set at 1Gbps or more. Sometimes, due to a configuration or device issue, an interface can be set below that (to 100mbps or even 10mbps). As that is usually _not_ the intended behavior, it is important to track the bandwidth of all network interfaces.
        how: |
            This alert logs into the Palo Alto Networks firewall through ssh and retrieves the status of all network interfaces and their speeds/bandwidth. In that output, it looks for the actual bandwidth of each interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-duplex:
        why: |
            Generally, these days network interfaces are set at full duplex. Sometimes, due to a configuration or device issue, an interface can be set to half duplex. As that is usually _not_ the intended behavior, it is important to track the duplex setting of all network interfaces.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the actual runtime duplex of each interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-tx-packets:
        why: |
            Tracking the number of packets flowing through each network interface is important to identify potential issues, spikes in traffic, etc.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the number of packets transmitted through the interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-tx-bits:
        why: |
            Tracking the amount of data flowing through each network interface is important to identify potential issues, spikes in traffic, etc.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the number of bits transmitted through the interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-rx-packets:
        why: |
            Tracking the number of packets flowing through each network interface is important to identify potential issues, spikes in traffic, etc.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the number of packets received through the interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-rx-bits:
        why: |
            Tracking the amount of data flowing through each network interface is important to identify potential issues, spikes in traffic, etc.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the number of bits received through the interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-rx-dropped:
        why: |
            If incoming packets are being dropped on a network interface, it is important to be aware of it. This may be due to a high load on the firewall, or another capacity issue.
        how: |
            This script logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for the number of packets dropped on an interface.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-state:
        why: |
            If a network interface is set to be up (what's known as "admin up") but is actually down (a cable is not connected, the device on the other side is down, etc.) it is important to know.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it looks for interfaces that are set to be up, but are actually down.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-mtu:
        why: |
            The MTU of an interface may be inadvertently set to a low value. It's important to know if this happens and fix it.
        how: |
            This alert logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it retrieves the MTU values.
        can-with-snmp: true
        can-with-syslog: true
    network-interface-mac:
        why: |
            Capture the MAC address for the interface. This information is important to be able to search for MAC addresses, inventoring and troubleshooting purposes.
        how: |
            Indeni logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it retrieves the MAC address.
        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: |
            Indeni logs into the Palo Alto Networks firewall through api and retrieves the status of all network interfaces. In that output, it retrieves the interface receive errors counter.
        can-with-snmp: true
        can-with-syslog: false
    network-interfaces:
        why: |
            Capture the interface name.
        how: |
            Indeni logs into the Palo Alto Networks firewall through api and retrieves the network interfaces.
        can-with-snmp: true
        can-with-syslog: false
steps:
-   run:
        type: HTTP
        command: /api?type=op&cmd=<show><interface>all</interface></show>&key=${api-key}
    parse:
        type: XML
        file: show-interface.parser.1.xml.yaml
-   run:
        type: HTTP
        command: /api?type=op&cmd=<show><interface>${nic}</interface></show>&key=${api-key}
    parse:
        type: XML
        file: show-interface.parser.2.xml.yaml

CrossVendorTxCollisions

// 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 CrossVendorTxCollisions() extends NearingCapacityWithItemsTemplateRule(
  ruleName = "CrossVendorTxCollisions",
  ruleFriendlyName = "All Devices: TX packets experienced collisions",
  ruleDescription = "Indeni tracks the number of packets that had issues and alerts if the ratio is too high.",
  usageMetricName = "network-interface-tx-collisions",
  limitMetricName = "network-interface-tx-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 collision rate. Review the ports below.",
  alertItemDescriptionFormat = "%.0f collisions identified out of a total of %.0f transmitted.",
  baseRemediationText = "Packet collisions usually occur when there is a mismatch in duplex settings on two sides of a cable.",
  alertItemsHeader = "Affected Ports")(
  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 
)