Skip to main content
Close
Hitachi Vantara Knowledge

Raidcom add path Fails With Error raidcom could not convert to WWN from IP_Address and IQN

  1. Last updated
  2. Save as PDF

 

Symptom

  • raidcom: could not convert to WWN from IP_Address and IQN.
  • raidcom: [EX_ENOOBJ] No such Object in the RAID

Environment

  • Linux
  • raidcom
  • CCI
  • iSCSI
  • When attempting to add a new path for a quorum disk, the following linux command fails:

# raidcom add path -path_grp 2 -port CL1-G -external_iscsi_name iqn.2017-02.hdrs.hds.com:quorum1 -external_address 10.28.225.5 -I0 -s 358591 <enter>

raidcom: could not convert to WWN from IP_Address and IQN. raidcom: [EX_ENOOBJ] No such Object in the RAID

[root@localhost etc]#

 

Resolution

  1. # tgtadm --tid 2 --lun 0 --op update --mode logicalunit --params vendor_id=IET,product_id=VIRTUAL-DISK

Cause

The problem with changing the iSCSI configuration occurred when iscsi tgtadm was restarted on the host providing the Quorum disk.
When iscsi tgtadm is restarted it changes the SCSI identifier of LUN 0 to Controller and the storage rejects the change as it can't identify as IET anymore, the command below changes the identifier to VIRTUAL-DISK, after that the storage was able to communicate with LUN 0 via the new added path and showed the new added LUN (Quorum disk) on the new path.

tgtadm --tid 2 --lun 0 --op update --mode logicalunit --params vendor_id=IET,product_id=VIRTUAL-DISK

 

Additional Notes