How to Remove stale ISCSI Target Node Information from ISCSI Initiator Server
(Doc ID 2552338.1)
Last updated on AUGUST 17, 2024
Applies to:
Linux OS - Version Oracle Linux 5.1 to Oracle Linux 7.6 [Release OL5U1 to OL7U6]Oracle Cloud Infrastructure - Version N/A to N/A [Release 1.0]
Linux x86
Linux x86-64
Symptoms
Stale ISCSI target connections which are still present on Initiator node can lead to various issues like:
- - hung iscsid service which can lead to global outage
- - flood of messages error like:
messages:Jun 3 13:58:00 <HOSTNAME> iscsid: iscsid: Connection5:0 to [target: iqn-name, portal: ip-here,3260] through [iface: default] is shutdown.
messages:Jun 3 13:58:00 <HOSTNAME> iscsiadm: iscsiadm: Could not login to [iface: default, target: iqn-name, portal: ip-here,3260].
messages:Jun 3 13:58:00 <HOSTNAME> iscsiadm: Logging in to [iface: default, target: iqn-name, portal: ip-here,3260] (multiple)
messages:Jun 7 04:24:15 <HOSTNAME> iscsid: iscsid: Connection2:0 to [target: iqn-name, portal: ip-here,3260] through [iface: default] is shutdown.
messages:Jun 7 04:24:15 <HOSTNAME> iscsiadm: iscsiadm: Could not login to [iface: default, target: iqn-name, portal: ip-here,3260].
messages:Jun 7 04:24:15 <HOSTNAME> iscsiadm: Logging in to [iface: default, target: iqn-name, portal: ip-here,3260] (multiple)
- - booting issues ( long/hung boot )
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |