DescriptionIndeni tracks the number of packets that had issues and alerts if the ratio is too high.
Remediation StepsPacket errors usually occur when there is a mismatch in the speed and duplex settings on two sides of a cable, or a damaged cable.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: Operational Commands
5. If the problem persists, contact the Juniper Networks Technical Assistance Center (JTAC)""",
.VENDOR_FORTINET -> ""
1. Run "diag hardware deviceinfo nic
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
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 Received Packets counter. Knowing the amount of bytes and packets flowing through an interface can help estimate an interface's performance and utilization.
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.
View Source Code