connect debian etch to IBM SAN, meaning of "SNS scan failed" ?
Hi, I installed a debian etch 4.0r0 amd64 on an ibm blade HS21, with a qlogic HBA 2422 included. I would like to connect them to an IBM SAN 4700.
I installed with apt-get the debian package "firmware-qlogic" and afterwards did a "update-initramfs -u". My colleague said he has done the necessary changes in the SAN. After a reboot, I get the following messages in dmesg: qla2xxx 0000:08:01.0: Found an ISP2422, irq 90, iobase 0xffffc20000004000 qla2xxx 0000:08:01.0: Configuring PCI space... qla2xxx 0000:08:01.0: Configure NVRAM parameters... qla2xxx 0000:08:01.0: Verifying loaded RISC code... qla2xxx 0000:08:01.0: Allocated (64 KB) for EFT... qla2xxx 0000:08:01.0: Allocated (1413 KB) for firmware dump... qla2xxx 0000:08:01.0: Waiting for LIP to complete... qla2xxx 0000:08:01.0: LOOP UP detected (4 Gbps). qla2xxx 0000:08:01.0: Topology - (F_Port), Host Loop address 0x0 qla2xxx 0000:08:01.0: SNS scan failed -- assuming zero-entry result... scsi0 : qla2xxx qla2xxx 0000:08:01.0: qla2xxx 0000:08:01.1: Found an ISP2422, irq 114, iobase 0xffffc20000006000 qla2xxx 0000:08:01.1: Configuring PCI space... qla2xxx 0000:08:01.1: Configure NVRAM parameters... qla2xxx 0000:08:01.1: Verifying loaded RISC code... qla2xxx 0000:08:01.1: Allocated (64 KB) for EFT... qla2xxx 0000:08:01.1: Allocated (1413 KB) for firmware dump... qla2xxx 0000:08:01.1: Waiting for LIP to complete... qla2xxx 0000:08:01.1: LOOP UP detected (4 Gbps). qla2xxx 0000:08:01.1: Topology - (F_Port), Host Loop address 0x0 qla2xxx 0000:08:01.1: SNS scan failed -- assuming zero-entry result... scsi1 : qla2xxx qla2xxx 0000:08:01.1: I was wondering what the "SNS scan failed" means. It seems to me that I can't connect to the san. If I look in /proc/scsi I don't see the SAN-drive either. Does anybody know where the problem is? |
SNS, Simple Name Server
Hi,
Some extra information. According to documentation of qlogic, "SNS" stands for "Simple Name Server", "software that runs inside a fabric switch, used for zoning". Is there someone who knows where I have to look or do some tests to solve these problem? Thanks. |
Just an update, problem was due to a misconfiguration on our san.
|
Hi,
Could you elaborate a bit on what the misconfiguration was? I have the exact same problem. Thanks Doktora |
HI,
I don't know that much about SAN, it was my colleague who has done the settings. According to him, the problem was due to the settings of the zoning of the SAN-switches. greetings. |
All times are GMT -5. The time now is 10:35 AM. |