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? 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.
Hugh Jim Trocki wrote: >On Wed, 17 Apr 2002, Hugh Caley wrote: > > > >>The silkworm monitor seems to work on our Brocades, except that it is >>generating errors because three of the ports don't have anything plugged >>into them. Is there any way to stop this behaviour? >> >>brocade-1 port portNum-0 failure (offline) >>brocade-2 port portNum-0 failure (offline) >>brocade-2 port portNum-12 failure (offline) >> >> > >you should administratively disable those ports on the brocade. log in to >the thing and do "portdisable (portnum)" for each port you're not using. > > > -- Hugh Caley, Unix Systems Administrator Affymetrix Inc., 510-428-8537 [EMAIL PROTECTED]
