Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

automatic reboot of NSR 2402 and unknown log entires

SOLVED
Go to solution

automatic reboot of NSR 2402 and unknown log entires

Hello,

We are running 3 NSR 2402 with the latest firmware, 5.9.44.

During the run of Data Protector 6.0 backup of different systems, using all 3 NSR, we had an autoamtic reboot of one of them.

In the log, we do not find any information, why that reboot was done.

1153. 04/09/2009 23:01:12 4d20h54m37.05s BUFFER Memory Integrity Test Passed
1154. 04/10/2009 02:55:12 0d00h00m00.00s Unit restart and initialization, Firmware Version: 5.9 Build Level: 5.9.44
1155. 04/10/2009 02:55:26 0d00h00m19.28s pSCSI discovery requested for port -1 (all) via initialize SCSI (PS_INIT)
1156. 04/10/2009 02:56:11 0d00h01m22.26s New device is added to location 0/6/0 Rte x1 SN JF92778872
1157. 04/10/2009 02:56:11 0d00h01m22.51s hpInitifcHandle returned is 256
1158. 04/10/2009 02:56:11 0d00h01m22.91s HttpifcHandle returned is 257
1159. 04/10/2009 02:56:11 0d00h01m22.91s AsyncifcHandle returned is 258
1160. 04/10/2009 02:56:12 0d00h01m24.11s FC Port 0 Link is UP.

1. From time to time, we have messages like that:
CHK COND with Sense Key=0x4, ASC=0x8, ASCQ=0x0 from SCSI LUN 0/6/0 Rte x1
2. FC port 0 non-persistent exchange NOT completed

but noting found about in the documentation. The second message indicates as I assume a problem in the device access.

Message 1 we have since 13 hours, every 10-15 minutes and message 2 we had for about 30 times in 20 seconds.

Our assumption is, that something in SAN configuration could be wrong althrough it is running since several years.

Best regards
Daniel
6 REPLIES
Víctor Cespón
Honored Contributor
Solution

Re: automatic reboot of NSR 2402 and unknown log entires

ASC=0x8, ASCQ=0x0 means LOGICAL UNIT COMMUNICATION FAILURE

Message 2 seems to indicate the same

During reboot the NSR discovers 0/6/0 again

What kind of device is 0/6/0? I can't find it from the serial number.

Re: automatic reboot of NSR 2402 and unknown log entires

Device 0/6/0 is an Ultrium 7000 with SN JF92778872

Re: automatic reboot of NSR 2402 and unknown log entires

I have checked the power and SCSI cabling for that device such as the fibre connections. I could not find that something is wrong.

I also belive that for that 30 seconds, there were some problems in accessing the device and therefore it was terminated.

Message 1 is for much more important because we have them permanently and the FC port is affected. When I compare the NSR's, that only that NSR has this message with nearly the same cabling.

Best regards
Daniel
Marino Meloni_1
Honored Contributor

Re: automatic reboot of NSR 2402 and unknown log entires

BUFFER Memory Integrity Test Passed
this indicate that all is ok, the message is the result of an internal diag task, and is only informazional, so untill you see it, all is working fine

Re: automatic reboot of NSR 2402 and unknown log entires

In my reply Apr 16, 2009 08:36:19 GMT, I was wrong with the number of message. Message 2, the FC related message is my major concern.
Marino Meloni_1
Honored Contributor

Re: automatic reboot of NSR 2402 and unknown log entires


FC port 0 non-persistent exchange NOT completed

This is not a failure, it seems this is something the NSR is receiving from a Host (link service or extended link service) and the NSR ignore it, then the Frame is dropped. Usualy caused by a host that is loosing the link or the device.
Looking at the complete traces before this is recorded may help in identifying the host and the cause, but usualy the traces in teh NSR itself are flushed out when you notice that message