full-disclosure - Maybe not a disclosure but request for information.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date: Wed Apr 27 18:19:03 2005
From: leife at dls.net (Leif Ericksen)
Subject: Maybe not a disclosure but request for
	information.

I work with a bunch of HS20 Blades in a 8677 Chassis and we are using
the Qlogics cards (that was a mistake) connected to an IBM FAStT-900.

Talking to IBM with regards to my problems (blade and san related versus
personal!) I have found that there are known issues with the Qlogics
cards. I do not know if this is a Qlogics, fAStT or combo issue, BUT one
day you might be able to see your SAN the next day you reboot and you
loose the SAN!  Even without making any changes to the servers! I was
told that this is a fairly common but non-repeatable as such Qlogcis and
IBM have given up on finding a solution.

Full disclosure elements working with QLogics and an IBM FAStT is a real
pain in the rear!
IBM wants tools on the servers to better build the qla2300.conf file,
but those tools require that you have no firewall installed and port
mapper has to be running so I do not do that.

If I were to start this project over and if my voice carried any weight
in the final choice I would say we are NOT going to use Qlogics because
they are way to unreliable.

QUESTION:
I am trying to find list servers that might be able to answer my
questions and since I am feeling lazy (after being unsuccessful with
google thus far) I am asking here does anybody know of (a) list server
(s) that fit the needs of managing a FASTtT in a Linux environment. 

IBM was fairly useless here as well.
-- 
Leif Ericksen <leife@....net>