Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

Port Shutdown with Broadcast Storm

 
Bwheaton
Occasional Contributor

Port Shutdown with Broadcast Storm

I have been looking at a configuration guide for Aruba Procurve Switches.  In it, it talks about port shutdown with broadcast storm.  Using fault-finder broadcast-storm, I can potentially set a percentage threshold for broadcast traffic to warn and/or disable the port when it reaches the maximum threshold.   
 
Have you ever looked at anything like this?  We already use loop protect, but I read about this and was really curious.
 
1 REPLY 1
rajkumar787
HPE Pro

Re: Port Shutdown with Broadcast Storm

Hi,

Yes the fault finder has the below options

 

HP switches feature automatic fault detection, which helps protect against network loops and defective equipment. The fault detection sensitivity setting determines the types of alerts reported to the Alert Log based on their level of severity or sensitivity.

The sensitivity levels are:

High Sensitivity. This policy directs the switch to send all alerts to the Alert Log. This setting is most effective on networks that have none or few problems.

Medium Sensitivity. This policy directs the switch to send alerts related to network problems to the Alert Log. If you want to be notified of problems which cause a noticeable slowdown on the network, use this setting.

Low Sensitivity. This policy directs the switch to send only the most severe alerts to the Alert Log. This policy is most effective on a network where there are normally a lot of problems and you want to be informed of only the most severe ones.

Disabled. Disables the Alert Log and transmission of alerts (traps) to the management server (in cases where a network management tool such as ProCurve Manager is in use). Use this option when you don’t want to use the Alert Log.

Syntax:

 

 fault-finder [fault] [sensitivity ] [action ]

 

[fault]: Supported values are:

•all: All fault types

•bad-driver: Too many undersized/giant packets

•bad-transceiver: Excessive jabbering

•bad-cable: Excessive CRC/alignment errors

•too-long-cable: Excessive late collisions

•over-bandwidth: High collision or drop rate

•broadcast-storm: Excessive broadcasts

•duplex-mismatch-HDx: Duplex mismatch. Reconfigure to Full Duplex

•duplex-mismatch-FDx: Duplex mismatch. Reconfigure port to Auto

•link-flap: Rapid detection of link faults and recoveries

•loss-of-link: Link loss detected. (Sensitivity not applicable)

 

Thank You!
I am an HPE Employee

Accept or Kudo