大网数据广告活动
服务器运维问答

iSCSI Discovery Issue

· 52CE 我爱测

I have an issue with iSCSI discovery. Just some background, I'm using Openstack Cinder and part of Cinder requires the use of iSCSI for networked drives. Cinder is unable to get the list of nodes anymore for some reason, and afte…

问题原文

原帖链接 · Elf · CC BY-SA 4.0

I have an issue with iSCSI discovery. Just some background, I'm using Openstack Cinder and part of Cinder requires the use of iSCSI for networked drives. Cinder is unable to get the list of nodes anymore for some reason, and after tracing, it seems to be due to the inability of my Openstack controller to get the list of nodes via iscsiadm.

The command I'm referring to is iscsiadm --mode discovery --op update --type sendtargets --portal <target_address>:3260

I'll get the following error message

iscsiadm: connecting to <target_address>:3260
iscsiadm: connected local port 58654 to <target_address>:3260
iscsiadm: connected to discovery address <target_address>
iscsiadm: discovery session to <target_address>:3260 starting iSCSI login
iscsiadm: sending login PDU with current stage 1, next stage 3, transit 0x80, isid 0x00023d000000 exp_statsn 0

iscsiadm: Connection to Discovery Address <target_address> failed
iscsiadm: Login I/O error, failed to receive a PDU

Interestingly enough, this command runs fine when running on the host directly. It cannot run from any other network-ed server, whether Linux or Windows.

Now if I create a new portal via the following command tgtadm --lld iscsi --op new --mode portal --param portal=0.0.0.0:1234

I'm able to get the list of nodes just fine via the command iscsiadm --mode discovery --op update --type sendtargets --portal <target_address>:1234

So it rules out a network issue, at least.

For the record, nothing else is running on port 3260 aside form iscsid and tgtd, both of which are related to iSCSI. When I create a portal on port 1234, I get similar outputs when I netstat -nltp | grep <port_number>

I'm running Ubuntu 20.04 LTS Server Edition. The firewall is disabled, iptables are empty aside from the rule to allow incoming packets at port 3260, SELinux is also disabled.

已采纳解答

原帖链接 · Elf · CC BY-SA 4.0

The issue that I had was due to a kernel update that broke something at the lower level.

Wireshark dumps of the working connection via 1234, and 3260 showed that the 3-way TCP handshake mentioned here https://elatov.github.io/2012/06/iscsi-login-packet-capture/ was not established when communicating via 3260.

Downgrading the Linux Kernel to 5.15.0-41-generic from 5.15.0-46-generic resulted in the issue being solved.

For reference, I'm using a SuperMicro File Server Model SSG-6049P-E1CR24H

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2022-08-17)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。