Help replacing FC10

[John Demeny]

We had an A5236A FC10 generating errors so we replaced the enclosure, keeping the same drives.
However, ioscan shows the last drive and the fcp as NO_HW, tho drives 0-8 are working normally.

ioscan -fn shows:
target 43 0/7/0/0.8.0.255.0.9 tgt NO_HW DEVICE
disk 31 0/7/0/0.8.0.255.0.9.0 sdisk NO_HW DEVICE HP 18.2GST318452FC
/dev/dsk/c6t9d0 /dev/rdsk/c6t9d0
target 44 0/7/0/0.8.0.255.0.10 tgt NO_HW DEVICE
ctl 6 0/7/0/0.8.0.255.0.10.0 sctl NO_HW DEVICE HP A5236A
/dev/rscsi/c6t10d0
ext_bus 7 0/7/0/0.8.0.255.4 fcpdev CLAIMED INTERFACE FCP Device Interface
target 45 0/7/0/0.8.0.255.4.9 tgt CLAIMED DEVICE
disk 34 0/7/0/0.8.0.255.4.9.0 sdisk CLAIMED DEVICE HP 18.2GST318452FC
/dev/dsk/c7t9d0 /dev/rdsk/c7t9d0

We did not previous have 0/7/0/0.8.0.255.4

Where did this come from?
How do I get rid of it?

[Steven E. Protter]

Shalom,

You may need updated drivers.

With some disk arrays there is a 8 LUN limit in HP-UX, but updated drivers for the HBA may permit more LUNS.

SEP

[John Demeny]

I have two other FC10's running normally, and the one I replaced worked normally.
How do I determine what firmware the box is currently running?

[TTr]

> We did not previous have 0/7/0/0.8.0.255.4
This is probably caused by the FC domain ID on the replaced FC10 not being set the same with the old one. If so then setting the new FC10 to the same FC domain ID and rebooting the server might fix this.

[John Demeny]

The replacement enclosure was bad.
Replaced enclosure again and problem went away.

[John Demeny]

See comment above.