Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Ok fixed.... and fickle... but this is a good tip if anyone has this...

Down to fact i use iscsi for storage san backend on same blade and controller node.

You can double check if there is a problem by

lsof -i -n | grep iscsi

iscsid     1462      root    9u  IPv4 1591345      0t0  TCP 10.0.10.14:50846->10.0.10.66:iscsi-target (ESTABLISHED)
iscsid     1462      root   11u  IPv4 1591350      0t0  TCP 10.0.20.14:51876->10.0.20.65:iscsi-target (ESTABLISHED)
iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 10.0.10.14:54707->10.0.10.64:iscsi-target (ESTABLISHED)
iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 172.25.0.14:54707->172.25.0.14:iscsi-target (ESTABLISHED)
tgtd      25585      root    4u  IPv4 2078033      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25585      root    5u  IPv6 2078034      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25588      root    4u  IPv4 2078033      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25588      root    5u  IPv6 2078034      0t0  TCP *:iscsi-target (LISTEN)

see what is running. this daemon should NOT have been connected...

  iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 172.25.0.14:54707->172.25.0.14:iscsi-target (ESTABLISHED)

I fixed by stopping tgtd and killing any rogue tgtd threads still running

So there was a conflict with tgtd standard iscsi daemon was conflicting so stopped connections therefore breaking iscsi connections.

Ok fixed.... and fickle... but this is a good tip if anyone has this...

Down to fact i use iscsi for storage san backend on same blade and as controller node.

You can double check if there is a problem by

lsof -i -n | grep iscsi

iscsid     1462      root    9u  IPv4 1591345      0t0  TCP 10.0.10.14:50846->10.0.10.66:iscsi-target (ESTABLISHED)
iscsid     1462      root   11u  IPv4 1591350      0t0  TCP 10.0.20.14:51876->10.0.20.65:iscsi-target (ESTABLISHED)
iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 10.0.10.14:54707->10.0.10.64:iscsi-target (ESTABLISHED)
iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 172.25.0.14:54707->172.25.0.14:iscsi-target (ESTABLISHED)
tgtd      25585      root    4u  IPv4 2078033      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25585      root    5u  IPv6 2078034      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25588      root    4u  IPv4 2078033      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25588      root    5u  IPv6 2078034      0t0  TCP *:iscsi-target (LISTEN)

see what is running. this daemon should NOT have been connected...

  iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 172.25.0.14:54707->172.25.0.14:iscsi-target (ESTABLISHED)

I fixed by stopping tgtd and killing any rogue tgtd threads still running

So there was a conflict with tgtd standard iscsi daemon was conflicting so stopped connections therefore breaking iscsi connections.

Ok fixed.... and fickle... but this is a good tip if anyone has this...

Down to fact i use iscsi for storage san backend on same blade as controller node.

You can double check if there is a problem by

lsof -i -n | grep iscsi

iscsid     1462      root    9u  IPv4 1591345      0t0  TCP 10.0.10.14:50846->10.0.10.66:iscsi-target (ESTABLISHED)
iscsid     1462      root   11u  IPv4 1591350      0t0  TCP 10.0.20.14:51876->10.0.20.65:iscsi-target (ESTABLISHED)
iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 10.0.10.14:54707->10.0.10.64:iscsi-target (ESTABLISHED)
iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 172.25.0.14:54707->172.25.0.14:iscsi-target (ESTABLISHED)
tgtd      25585      root    4u  IPv4 2078033      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25585      root    5u  IPv6 2078034      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25588      root    4u  IPv4 2078033      0t0  TCP *:iscsi-target (LISTEN)
tgtd      25588      root    5u  IPv6 2078034      0t0  TCP *:iscsi-target (LISTEN)

see what is running. this daemon should NOT have been connected...

  iscsid     1462      root   13u  IPv4 1591353      0t0  TCP 172.25.0.14:54707->172.25.0.14:iscsi-target (ESTABLISHED)

I fixed by stopping tgtd and killing any rogue tgtd threads still running

So there was a conflict with tgtd standard iscsi daemon was conflicting so stopped connections therefore breaking iscsi connections.