Pillar Axiom: Solaris APM Host Status Not Communicating due to Duplicate iSCSI Qualified Name
(Doc ID 1514153.1)
Last updated on DECEMBER 19, 2012
Applies to:Pillar Axiom 300 Storage System - Version All Versions to All Versions [Release All Releases]
Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Pillar Axiom 500 Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
A Solaris host running the Axiom Path Manager may show as Not Communicating in the Axiom GUI. If any of the following happen, the hosts that are affected can change:
- The Axiom system is restarted
- The Active Pilot CU on the Axiom is restarted or changed
- The Solaris hosts are restarted
- The ethernet network between the Solaris hosts and the Axiom is interrupted, then restored.
The "Not Communicating" status can have other causes. This article documents how to identify and resolve the issue when this failure is due to duplicate iSCSI Qualified Names in multiple Solaris hosts.
This Not Communicating will happen any time there are multiple Solaris hosts using the same iSCSI Qualified Name, whether or not the host is using iSCSI.
Only a single host with the same iqn will be allowed to log in. The rest will fail the APM login due to duplicate iqn and be in "Not Communicating" status. If the host that successfully logs in loses the TCP connection for any reason, some other Solaris host with the same iqn may log in successfully, which can result in the Communicating/Not Communicating status changing.
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