Fault-finder

[PEI_1]

Hi,

Could someone explain the fault-finder command for Procurve switches.

I see a few lines of fault-finder configurations in show run, but not sure what they are for.

I can't find fault-finder information in the manuals.

Please advise.

Pei

[Gerhard Roets]

Hi Pei

Look at the following URL

http://h17007.www1.hp.com/device_help/ProCurveJ9472A/SHelp.htm

What you are looking for is under

System ==> Logging

Then Alert Descriptions

http://h17007.www1.hp.com/device_help/ProCurveJ9472A/System/Logging/AlertDescriptions.htm

and Fault-finder

http://h17007.www1.hp.com/device_help/ProCurveJ9472A/System/Logging/FaultFinder.htm

This is for the web interface but you can configure it from the CLI. Remember to use the context sensitive help in the CLI.

HTH

Gerhard

[PEI_1]

The weblinks do not work

[Gerhard Roets]

Hi Pei

Really odd. I tested the links from home and the office and in both cases it works ( Different PCs as well).

The basic function of fault finder is to detect common issues that can be simply detected by counters, and in some cases take some mitigating actions depending on the model of switch off course.

Anyways Let me see if I can do a semi decent copy and paste. ( Anyone else reading this please be aware that there might be updated data on the web since this is a static copy and not exactly the same layout)

Alert Descriptions

Alert

Description

First Time Install

Important installation information for your switch.

Too many undersized/giant packets

A device connected to this port is transmitting packets shorter than 64 bytes or longer than 1518 bytes (longer than 1522 bytes if tagged) with valid CRCs (unlike runts, which have invalid CRCs).

Excessive jabbering

A device connected to this port is incessantly transmitting packets (jabbering).

Excessive CRC/ alignment errors

A high percentage of data errors has been detected on this port. Possible causes include:

• Faulty cabling or invalid topology

• Duplex mismatch (full-duplex configured on one end of the link and half-duplex configured on the other)

• A malfunctioning NIC, NIC driver, or transceiver

Excessive late collisions

Collisions detected after transmitting 64 bytes have been detected on this port. Possible causes include:

• An overextended LAN topology

• Duplex mismatch (full-duplex configured on one end of the link and half-duplex configured on the other)

• A misconfigured or faulty device connected to the port

High collision or drop rate

A large number of collisions or packet drops have occurred on the port. Possible causes include:

• An extremely high level of traffic on the port

• Duplex mismatch

• A misconfigured or malfunctioning NIC or transceiver on a device connected to this port

• A topology loop in the network

Excessive broadcasts

An extremely high percentage of broadcasts was received on this port. This degrades the performance of all devices connected to the port. Possible causes include:

• A network topology loop (the usual cause)

• A malfunctioning device, NIC, NIC driver, or software package

Loss of Link

Lost connection to one or multiple devices on the port.

Loss of Stack Member

The Commander has lost the connection to a stack member.

In addition, the Web Browser Interface generates the following alerts:

• Auto Partition

• Backup Transition

• Excessive broadcasts

• Excessive CRC/alignment errors

• Excessive jabbering

• Excessive late collisions

• First Time Install

• Full-Duplex Mismatch

• Half-Duplex Mismatch

• High collision or drop rate

• Loss of Link

• Mis-Configured SQE

• Network Loop

• Polarity Reversal

• Security Violation

• Stuck 10BaseT Port

• Too many undersized (runt)/giant packets

• Transceiver Hot Swap

- The second link

Logging Configuration

ProCurve switches feature automatic fault detection, which can protect your network from being brought down by problems such as network loops, defective cables, transceivers and faulty network interface cards.

The Fault Detection sensitivity setting on the Logging>Configuration pane determines the types of alerts reported to the Alert Log based on their level of severity or sensitivity. Click Change to change the sensitivity level.

The fault detection severity levels are:

Disabled

Alerts controlled by the Fault Finder are no longer displayed. The Fault Finder list does not include all alerts shown in the Alert Log (e.g., Hot swap)

Low Sensitivity

Only the most severe alerts are sent to the Alert Log.

This setting is most effective on a network with a lot of problems where you want to be informed of only the most severe problems.

Medium Sensitivity (default)

Only alerts related to network problems are sent to the Alert Log.

Use this setting when you want to be notified of problems that cause a noticeable slowdown on the network.

High Sensitivity

All alerts are sent to the Alert Log.

This setting is most effective on networks that have few or no problems.

 

HTH

Gerhard

[Suresh_Babu_K_C]

It's wonderful explanation. thanks of your guide.