将 QLogic 光纤通道卡从一个 ESXi 主机移动到另一个 ESXi 主机

将 QLogic 光纤通道卡从一个 ESXi 主机移动到另一个 ESXi 主机

我们正在尝试使用 DL360p G8 升级 DL360 G6 ESXi 主机。G6 内部有一个 Qlogic ISP2532 FC 卡,一切运行正常。由于我没有备用的 FC 卡,因此我需要在新服务器中使用同一张卡。

我遇到的问题是,虽然卡在新服务器上似乎工作正常,但我看不到存储。整个 SAN/FC 交换机不在我的掌控之中,我无法访问它。

我不是 SAN 专家,但我认为这没什么关系。显然卡是相同的,WNN 也是相同的,所以理论上这不会影响交换机上的分区配置。

如果我将 FC 卡移回旧服务器,它就可以正常工作,并且我可以看到存储。这是内核在新服务器上显示的内容(当它不工作时):

2016-04-11T13:36:25.937Z cpu7:33267)Loading module qlnativefc ...
2016-04-11T13:36:25.941Z cpu7:33267)Elf: 1865: module qlnativefc has license GPLv2
2016-04-11T13:36:25.979Z cpu7:33267)Device: 191: Registered driver 'qlnativefc' from 20
2016-04-11T13:36:25.979Z cpu7:33267)Mod: 4943: Initialization of qlnativefc succeeded with module ID 20.
2016-04-11T13:36:25.979Z cpu7:33267)qlnativefc loaded successfully.
2016-04-11T13:36:25.981Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): MSI-X vector count from config space: 1f
2016-04-11T13:36:25.981Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): MSI-X vector count usable: 2
2016-04-11T13:36:25.981Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Found an ISP2532, iobase 0x0x41000a200000
2016-04-11T13:36:25.981Z cpu16:33266)IntrCookie: 1915: cookie 0x14 moduleID 20 <qlnativefc (default)0> exclusive, flags 0x1d
2016-04-11T13:36:25.981Z cpu16:33266)IntrCookie: 1915: cookie 0x15 moduleID 20 <qlnativefc (rsp_q)0> exclusive, flags 0x1d
2016-04-11T13:36:25.981Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): num_rsp_queues = 1, num_req_queues = 1
2016-04-11T13:36:25.981Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): MSI-X: Enabled (0x2, 0x0).
2016-04-11T13:36:25.981Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Calling initialize adapter
2016-04-11T13:36:28.941Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): FW: Loading via request-firmware...
2016-04-11T13:36:29.039Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Allocated (64 KB) for EFT...
2016-04-11T13:36:29.042Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Allocated (5414 KB) for firmware dump...
2016-04-11T13:36:29.054Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Setting Parameter to mark RDP ELS command as a passthrough ELS command
2016-04-11T13:36:29.066Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Enabling PUREX.
2016-04-11T13:36:29.078Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): FAWWN feature : disabled.
2016-04-11T13:36:29.091Z cpu16:33266)qlnativefc: (7:0.0): scsi(0): Unable to read FCP priority data.
2016-04-11T13:36:29.101Z cpu16:33266)Device: 326: Found driver qlnativefc for device 0x74b0430275473f33
2016-04-11T13:36:29.103Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): MSI-X vector count from config space: 1f
2016-04-11T13:36:29.103Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): MSI-X vector count usable: 2
2016-04-11T13:36:29.103Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Found an ISP2532, iobase 0x0x41000a1b8000
2016-04-11T13:36:29.103Z cpu16:33266)IntrCookie: 1915: cookie 0x16 moduleID 20 <qlnativefc (default)1> exclusive, flags 0x1d
2016-04-11T13:36:29.103Z cpu16:33266)IntrCookie: 1915: cookie 0x17 moduleID 20 <qlnativefc (rsp_q)1> exclusive, flags 0x1d
2016-04-11T13:36:29.103Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): num_rsp_queues = 1, num_req_queues = 1
2016-04-11T13:36:29.103Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): MSI-X: Enabled (0x2, 0x0).
2016-04-11T13:36:29.103Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Calling initialize adapter
2016-04-11T13:36:30.053Z cpu0:33098)qlnativefc: (7:0.0): scsi(0): LOOP UP detected (4 Gbps).
2016-04-11T13:36:30.226Z cpu2:33269)qlnativefc: (7:0.0): scsi(0): SNS scan failed -- assuming zero-entry result...
2016-04-11T13:36:31.698Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): FW: Loading via request-firmware...
2016-04-11T13:36:31.796Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Allocated (64 KB) for EFT...
2016-04-11T13:36:31.798Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Allocated (5414 KB) for firmware dump...
2016-04-11T13:36:31.811Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Setting Parameter to mark RDP ELS command as a passthrough ELS command
2016-04-11T13:36:31.823Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Enabling PUREX.
2016-04-11T13:36:31.835Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): FAWWN feature : disabled.
2016-04-11T13:36:31.847Z cpu16:33266)qlnativefc: (7:0.1): scsi(1): Unable to read FCP priority data.
2016-04-11T13:36:31.860Z cpu16:33266)Device: 326: Found driver qlnativefc for device 0x6eeb43027547401e
2016-04-11T13:36:32.812Z cpu2:33100)qlnativefc: (7:0.1): scsi(1): LOOP UP detected (4 Gbps).
2016-04-11T13:36:33.234Z cpu10:33271)qlnativefc: (7:0.1): scsi(1): SNS scan failed -- assuming zero-entry result...

有人向我建议,分区与服务器名称有某种关联,我应该更改新服务器的名称以反映旧服务器的名称。我不确定这与任何事情有什么关联,但在最后一次尝试中,我更改了 ESXi 主机名。但这没有帮助。

我是不是漏掉了什么?交换机上的分区配置是否需要重新进行?如果是,为什么?

任何帮助都将受到赞赏。

问候,斯蒂芬

答案1

尝试在 HBA 卡上运行硬件诊断程序。如果硬件显示为绿色,请联系硬件供应商将驱动程序更新为最新版本。

相关内容