On Wed, 17 Apr 2002, Hugh Caley wrote: > Thanks, Jim, but I was hoping not to have to do that. Are there > disadvantages to leaving them enabled, other than silkworm.monitor not > liking it?
no, and there are hardly any disadvantages to leaving them disabled, also. > We had a gbic fail a couple of weeks ago, and just plugged > our SAN host into another port, so downtime was a couple of minutes; it > would have taken quite a bit longer to find the password to the > brocade, log in, enable the port, etc. an alternative is to change the monitor to know the admin status of each port ahead of time. this means you'll have another config file to maintain, so the issue is to maintain the status of each port on the switch itself, or in some other location. to me it makes sense to just have the switch keep track of what the status of each port should be. logging in to the switch to change the admin status in some emergency situation isn't much of an issue at all. there may be other configurations to change in the event of a failure anyway. delays induced by not knowing the password to the brocade are hardly the fault of silkworm.monitor.
