RX packets overrun-juniper-junos

RX packets overrun-juniper-junos
0

RX packets overrun-juniper-junos

Vendor: juniper

OS: junos

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.
|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: Operational Commands

How does this work?
This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the “show interfaces extensive” command. The output includes all the interface related information and statistics.

Why is this important?
Capture the interface Receive Overrun errors counter.

Without Indeni how would you find this?
There are many solutions out there for tracking traffic flow on network interfaces and alerting when critical indicators are reached.

junos-show-interfaces-extensive

name: junos-show-interfaces-extensive
description: JUNOS get interface information (including stats)
type: monitoring
monitoring_interval: 1 minute
requires:
  vendor: juniper
  os.name: junos
comments:
  network-interface-state:
    why: |
      Capture the interface state. If an interface transitions from up to down an alert would be raised.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-admin-state:
    why: |
      Capture the interface administrative state.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-description:
    why: |
      Capture the interface description.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-speed:
    why: |
      Capture the interface speed in human readable format such as 1G, 10G, etc. indeni will alert if the speed is below 1G.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-duplex:
    why: |
      Capture the interface duplex in human readable format such as full or half. In modern network environments it is very uncommon to see half-duplex interfaces, and that should be an indication for a potential exception.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-rx-frame:
    why: |
      Capture the interface Receive Errors (CRC) counter. If this counter increases an alarm will be raised.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-mac:
    why: |
      Capture the interface MAC address.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-type:
    why: |
      Capture the interface type, for example "Ethernet".
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    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 logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-rx-dropped:
    why: |
      Capture the interface Received Errors counter. Packet loss may impact traffic performance.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-rx-packets:
    why: |
      Capture the interface Received Packets counter. Knowing the amount of bits and packets flowing through an interface can help estimate an interface's performance and utilization.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-ipv4-address:
    why: |
      Capture the interface IPv4 address. Only relevant for layer 3 interfaces, including Vlan interfaces (SVI).
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-ipv4-subnet:
    why: |
      Capture the interface IPv4 subnet mask. Only relevant for layer 3 interfaces, including Vlan interfaces (SVI).
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-tx-carrier:
    why: |
      Capture the interface carrier state change counter. It would increase every time the interface changes state from up to down.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-mtu:
    why: |
      Capture the interface MTU (Maximum Transmit Unit). A low MTU may cause issues.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  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 logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-tx-errors:
    why: |
      Capture the interface Transmit Errors counter. Transmission errors indicate an issue with duplex/speed matching.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-tx-packets:
    why: |
      Capture the interface Transmitted Packets counter. Knowing the amount of bits and packets flowing through an interface can help estimate an interface's performance and utilization.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
steps:
  -   run:
        type: SSH
        command: show interfaces extensive | display xml
      parse:
        type: XML
        file: show-interfaces-extensive.parser.1.xml.yaml

junos-show-interfaces-extensive

name: junos-show-interfaces-extensive
description: JUNOS get interface information (including stats)
type: monitoring
monitoring_interval: 1 minute
requires:
  vendor: juniper
  os.name: junos
comments:
  network-interface-state:
    why: |
      Capture the interface state. If an interface transitions from up to down an alert would be raised.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-admin-state:
    why: |
      Capture the interface administrative state.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-description:
    why: |
      Capture the interface description.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-speed:
    why: |
      Capture the interface speed in human readable format such as 1G, 10G, etc. indeni will alert if the speed is below 1G.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-duplex:
    why: |
      Capture the interface duplex in human readable format such as full or half. In modern network environments it is very uncommon to see half-duplex interfaces, and that should be an indication for a potential exception.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: true
  network-interface-rx-frame:
    why: |
      Capture the interface Receive Errors (CRC) counter. If this counter increases an alarm will be raised.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-mac:
    why: |
      Capture the interface MAC address.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-type:
    why: |
      Capture the interface type, for example "Ethernet".
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    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 logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-rx-dropped:
    why: |
      Capture the interface Received Errors counter. Packet loss may impact traffic performance.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-rx-packets:
    why: |
      Capture the interface Received Packets counter. Knowing the amount of bits and packets flowing through an interface can help estimate an interface's performance and utilization.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-ipv4-address:
    why: |
      Capture the interface IPv4 address. Only relevant for layer 3 interfaces, including Vlan interfaces (SVI).
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-ipv4-subnet:
    why: |
      Capture the interface IPv4 subnet mask. Only relevant for layer 3 interfaces, including Vlan interfaces (SVI).
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-tx-carrier:
    why: |
      Capture the interface carrier state change counter. It would increase every time the interface changes state from up to down.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-mtu:
    why: |
      Capture the interface MTU (Maximum Transmit Unit). A low MTU may cause issues.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  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 logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-tx-errors:
    why: |
      Capture the interface Transmit Errors counter. Transmission errors indicate an issue with duplex/speed matching.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
  network-interface-tx-packets:
    why: |
      Capture the interface Transmitted Packets counter. Knowing the amount of bits and packets flowing through an interface can help estimate an interface's performance and utilization.
    how: |
      This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show interfaces extensive" command.
      The output includes all the interface related information and statistics.
    can-with-snmp: true
    can-with-syslog: false
steps:
  -   run:
        type: SSH
        command: show interfaces extensive | display xml
      parse:
        type: XML
        file: show-interfaces-extensive.parser.1.xml.yaml

cross_vendor_rx_overrun

Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/crossvendor/cross_vendor_rx_overrun.scala