HPUX initiator problem

Status
Not open for further replies.

Dana French

Cadet
Joined
May 22, 2017
Messages
3
I am having an issue that appeared from nowhere. My HPUX initiator will no longer discover iSCSI disks from FreeNAS ( it has been working for years). When I run the command "ioscan -NH 64000" on the HPUX system to discover new iSCSI disks from FreeNAS, I see the following message appear on the FreeNAS /var/log/message file:

May 23 01:57:19 sosan02 ctld[50830]: 10.255.254.98 (iqn.2017-05.com.siteox.istgt:sohpi75): protocol error: received invalid opcode 0x44

May 23 01:57:19 sosan02 ctld[50831]: 10.255.255.98 (iqn.2017-05.com.siteox.istgt:sohpi75): protocol error: received invalid opcode 0x44

It appears in the file twice and it does NOT discover the new iSCSI disks. does anybody have any idea of what this is attempting to tell me?
 
D

dlavigne

Guest
Which build version of FreeNAS (from System -> Information)? Did you recently upgrade either the FreeNAS sytem, the client system, or the intiator software?
 

Dana French

Cadet
Joined
May 22, 2017
Messages
3
Which build version of FreeNAS (from System -> Information)? Did you recently upgrade either the FreeNAS sytem, the client system, or the intiator software?

BuildFreeNAS-9.10.2-U3 (e1497f269)
Platform Intel(R) Xeon(R) CPU 3070 @ 2.66GHz
Memory 8162MB

System Time Thu May 25 10:10:27 CDT 2017

Uptime 10:10AM up 2 days, 12:09, 1 user

Load Average 0.47, 0.34, 0.28

We upgraded freenas over a year ago.
 
D

dlavigne

Guest
We upgraded freenas over a year ago.

You have a different definition of upgrade then as U3 was released only a month ago on April 20. When did the errors start appearing?
 

Dana French

Cadet
Joined
May 22, 2017
Messages
3
Sorry, we went from 9.2 to the latest version about a year ago. I am checking with the SAN admin to see when they did the U3 update, but I would suspect the problems began about the same time. Is there a way to roll-back the update?
 
D

dlavigne

Guest
Yup, simply reboot and select the previous boot environment in the boot menu.

If it turns out that it works in the previous version but not in the update, it may be a bug that was introduced.
 
Status
Not open for further replies.
Top