LUN went in to Read only(RO) state during ontap upgrade

Applies to

Issue

• FC Lun went in to Read only(RO) state during the ontap upgrade
• Lun is online and mapped and no erroneous events were observed in the ems logs
• Switch logs did not reports any errors during the issue time stamp
• Below events were observed on the host side during the issue time stamp

Apr 1 11:42:55 tokdhso2p3a kernel: sd 3:0:0:10: [sdaw] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=8s
Apr 1 11:42:55 tokdhso2p3a kernel: sd 3:0:0:10: [sdaw] CDB: Write(10) 2a 00 03 7d 6a c0 00 00 08 00
Apr 1 11:42:55 tokdhso2p3a kernel: blk_update_request: I/O error, dev sdaw, sector 58550976
Apr 1 11:42:55 tokdhso2p3a kernel: sd 3:0:0:10: [sdaw] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
Apr 1 11:42:55 tokdhso2p3a kernel: sd 3:0:0:10: [sdaw] CDB: Write(10) 2a 00 04 42 a4 50 00 00 08 00
Apr 1 11:42:55 tokdhso2p3a kernel: blk_update_request: I/O error, dev sdaw, sector 71476304
Apr 1 11:42:55 tokdhso2p3a kernel: sd 3:0:0:10: [sdaw] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=8s
DID_NO_CONNECT: no link/cable transport connectivity exists to the specified device, unable to send io request.

• sdaw status is returned while the device still exists within the kernel configuration, but there is no transport link or connection available to transmit commands over to the target device