Skip to main content
NetApp Knowledge Base

Solaris command "cfgadm -c configure" fails and causes the host to lose connectivity to the storage

  1. Last updated
  2. Save as PDF
Views:
1,024
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
SAN
Last Updated:

Applies to

  • ONTAP 9
  • Solaris 11
  • Emulex target ports
  • FCP

Issue

Using cfgadm -c can cause a loss of LUN/path access with ONTAP Emulex target ports:

Dec 14 12:49:48 solaris  Failed to create nodes for pwwn=200b00a098efxxxx; error=0x5
Dec 14 12:50:13 solaris scsi: [ID 243001 kern.warning] WARNING: /pci@31e/pci@1/SUNW,emlxs@0/fp@0,0 (fcp0):

Dec 14 12:51:43 solaris genunix: [ID 483743 kern.info] /scsi_vhci/ssd@g600a09803830477364244f63486axxxx (ssd8) multipath status: optimal: path 116 fp0/ssd@w201b00a098efxxxx,63 is offline
 root@solaris:~# cfgadm -c configure c4
cfgadm: Library error: report LUNs failed: 10000090fa02xxxx report LUNs failed: 500a098182eexxxx failed to create device node: 2001005056b1xxxx: I/O er
Operation partially successful. Some failures seen

Extended emlxs logs from the host show PRLI sequence timeout

emlxs_msgbuf.out:(PRLI: did=1bf981 Local Reject. Sequence timeout.)

[2020 Dec  7 09:42:58:352:475:115]   2636:[4.00F4]emlxs0:  DEBUG: 811:
Abnormal ELS completion.
(PRLI: did=1bfa01 Local Reject. Sequence timeout.)

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.