Most of my large customers (and the 2 ISPs I worked for in the past) trap this information using SNMP.
And yes, you might have multiple alarms on the same problem, but getting a “bad cable” trap is better than knowing a NIC is flapping for an unknown reason. From: [email protected] [mailto:[email protected]] On Behalf Of Joseph L. Casale Sent: Tuesday, December 2, 2014 2:08 PM To: [email protected] Subject: [NTSysADM] RE: fault finder on switches I guess that depends on whether or not you read switch logs right? If you have a problem and you dont query the switch, having the switch indicate a condition is useless... jlc ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Jesse Rink <[email protected]<mailto:[email protected]>> Sent: Tuesday, December 2, 2014 12:03 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] fault finder on switches I’m just curious, do other network gurus bother with putting the following configuration commands into their switches? (these are from HP, but I’m assuming there are identical/similar commands on the cisco and comware stuff) fault-finder bad-driver sensitivity high fault-finder bad-transceiver sensitivity high fault-finder bad-cable sensitivity high fault-finder too-long-cable sensitivity high fault-finder over-bandwidth sensitivity high fault-finder broadcast-storm sensitivity high fault-finder loss-of-link sensitivity high fault-finder duplex-mismatch-HDx sensitivity high fault-finder duplex-mismatch-FDx sensitivity high Has putting those entries in –ever- actually helped you determine network problems or finding issues you otherwise would NOT have found? Or do you not usually bother? JR
