iSCSI login negotiation failure
Ste
125 Posts
May 4, 2020, 1:10 pmQuote from Ste on May 4, 2020, 1:10 pmHi, one of my 3 nodes is continuously issuing this error on the console screen, can I do something to fix this ? Actually the iSCSI disk managed by this host seems to work correeclty and is attached to the clients.
Hi, one of my 3 nodes is continuously issuing this error on the console screen, can I do something to fix this ? Actually the iSCSI disk managed by this host seems to work correeclty and is attached to the clients.
Last edited on May 4, 2020, 1:10 pm by Ste · #1
admin
2,930 Posts
May 4, 2020, 1:50 pmQuote from admin on May 4, 2020, 1:50 pmin some cases this is caused by an old client trying to connect to a non existent disk, for example if ip x.x.x.x maps to disk 10 but the same ip was used before, either in a earlier cluster or disks were detached/attached., and that same ip was used for disk 20 which is no longer exists, but you still have a client on your network somewhere trying to periodically connect on this ip to the non existent disk.
in some cases this is caused by an old client trying to connect to a non existent disk, for example if ip x.x.x.x maps to disk 10 but the same ip was used before, either in a earlier cluster or disks were detached/attached., and that same ip was used for disk 20 which is no longer exists, but you still have a client on your network somewhere trying to periodically connect on this ip to the non existent disk.
iSCSI login negotiation failure
Ste
125 Posts
Quote from Ste on May 4, 2020, 1:10 pmHi, one of my 3 nodes is continuously issuing this error on the console screen, can I do something to fix this ? Actually the iSCSI disk managed by this host seems to work correeclty and is attached to the clients.
Hi, one of my 3 nodes is continuously issuing this error on the console screen, can I do something to fix this ? Actually the iSCSI disk managed by this host seems to work correeclty and is attached to the clients.
admin
2,930 Posts
Quote from admin on May 4, 2020, 1:50 pmin some cases this is caused by an old client trying to connect to a non existent disk, for example if ip x.x.x.x maps to disk 10 but the same ip was used before, either in a earlier cluster or disks were detached/attached., and that same ip was used for disk 20 which is no longer exists, but you still have a client on your network somewhere trying to periodically connect on this ip to the non existent disk.
in some cases this is caused by an old client trying to connect to a non existent disk, for example if ip x.x.x.x maps to disk 10 but the same ip was used before, either in a earlier cluster or disks were detached/attached., and that same ip was used for disk 20 which is no longer exists, but you still have a client on your network somewhere trying to periodically connect on this ip to the non existent disk.