This post is more than 5 years old
2 Intern
•
259 Posts
0
4711
April 28th, 2008 10:00
cisco port auto-disable feature
we have experienced two issues where the cisco san os disabled a port on one of our 9513 directors due to a BitErrThreshold level. In one instance, we had a single hba attached host that experienced downtime. I was able to re-enable the port and have it come back online - and I subsequently replaced the gbic. But, if I can re-enable the port and have the port allow a login again, I'm not too keen of the cisco os disabling the port.
Is this a setting I can set where I receive an email or some other type of alert indicating these types of errors without the port being disabled? To me, disabling a port, when it generates errors (but otherwise still functioning) is not a good thing. If I can receive an alert, then I can proactively work with the system administrators on a scheduled downtime window to replace the necessary gbic (or component).
Has anyone else experienced this?
Is this a setting I can set where I receive an email or some other type of alert indicating these types of errors without the port being disabled? To me, disabling a port, when it generates errors (but otherwise still functioning) is not a good thing. If I can receive an alert, then I can proactively work with the system administrators on a scheduled downtime window to replace the necessary gbic (or component).
Has anyone else experienced this?
No Events found!
RRR
6 Operator
•
5.7K Posts
0
April 29th, 2008 04:00
ConnectrixHelpe
259 Posts
1
April 28th, 2008 12:00
You can disable the port auto-disable feature. It is covered in the CLI guide. The guide states:
To prevent the detection of bit error threshold events from disabling the interface on Fibre Channel interfaces, use the switchport ignore bit-errors command. To revert to the default, use the no form of the command.
switchport ignore bit-errors
no switchport ignore bit-errors
The bit error rate threshold is used by the switch to detect an increased error rate before performance degradation seriously affects traffic.
Bit errors can occur for the following reasons:
¿ Faulty or bad cable
¿ Faulty or bad GBIC or SFP
¿ GBIC or SFP is specified to operate at 1 Gbps but is used at 2 Gbps
¿ Short haul cable is used for long haul or long haul cable is used for short haul
¿ Momentary sync loss
¿ Loose cable connection at one or both ends
¿ Improper GBIC or SFP connection at one or both ends
A bit error rate threshold is detected when 15 error bursts occur in a 5-minute period. By default, the switch disables the interface when the threshold is reached. You can issue a shutdown/no shutdown command sequence to reenable the interface.
Note Regardless of the setting of the switchport ignore bit-errors command, the switch generates a syslog message when bit error threshold events are detected.
========
As you stated you ran into a problem with a single hba hosts, that is one of reasons that EMC best practices state that all host should be multipathed so that failures of one port will not be disruptive to the host.
a syslog message is created so you could create an email alert based on the occurence of the message.
Thank you.
jimkunysz
2 Intern
•
259 Posts
0
April 29th, 2008 04:00
config t
# configures the specified interface
interface fc1/1
switchport ignore bit-errors
the above are the three steps in the guide. Isn't there a global parameter for the entire switch?
jimkunysz
2 Intern
•
259 Posts
0
April 29th, 2008 04:00
RRR
6 Operator
•
5.7K Posts
0
April 29th, 2008 04:00
# configures the specified interface
interface fc1/1
switchport ignore bit-errors
config t
interface fc1/1-48
switchport ignore bit-errors
This way you set it for all 48 ports at the same time !
jimkunysz
2 Intern
•
259 Posts
0
April 29th, 2008 04:00
RRR
6 Operator
•
5.7K Posts
0
April 29th, 2008 04:00
I don't know
AranH1
2.2K Posts
0
April 29th, 2008 08:00
jimkunysz
2 Intern
•
259 Posts
0
April 29th, 2008 11:00