HELP ASAP!!!!!!!!

[Jarheadatheart]

Guru's,
Someone decided today to just start unplugging fiber and power cables to my va7400, that connects to my rp7420 running HP-UX 11.11.

Now If I run an ioscan -fnC disk, I can see all of the drives(they all show as claimed) but all of the physical paths and and device names are different and I can't run any san commands at all. Does anyone have any idea's?

[Bill Hassell]

You will need your copy of vgdisplay -v and strings /etc/lvmtab prior to the disaster so you can rebuild the volumes with vgimport.

[Benoy Daniel]

move /etc/lvmtab and recreate using vgscan

[Torsten.]

You see drives?
You should see LUNs!

Make sure fiber cables are plugged into the host ports!

Please provide such

# ioscan -fn

and

# armdsp -a

[Steve Post]

THIS PROCEDURE WAS FOR 11.0. Treat with a big bolder of salt.

I assume you have a previous ioscan.
I assume you want to keep the same device numbers for some unknown reason.
Perhaps it is not that big of a deal to keep the new device names?

Search for the hp document id to see if there is a similar one for hpux11.11. This is a very, very, small snippet of MY notes from a disaster I worked with years ago on a V2500 hpux11.0. I used HP document notes to fix it.

HP Doc id KBRC00004879

Problem: Wrong device names.
Disk /dev/dsk/c0t5d0 should be /dev/dsk/c8t5d0.
Disk /dev/dsk/c1t6d0 should be /dev/dsk/c0t6d0.
Lan cards are wrong too.
The # in c#tXdY is called the â Instance Number.â The original instance numbers are different from the cold-install version.

"edited to comply with ITRC guidelines"

Now remember this was v2500, hpux11.0, not hpux11.11.

[Steve Post]

Sorry about the grave quote `
and the double quote "
and the single quote '
I guess the curly braces worked at least. {}

[Steve Post]

Don't take my advice on this changing the device instance numbers document. I can't find anything that follows that procedure past hpux11.0.

If you put in these keywords, you will at least get the hp handbook on io: ext_bus dev device files ioconfig2infile

Maybe that will help. But really....I'd try to live with the new device names.

[Torsten.]

I have seen another thread in the past where somebody plugged the fiber cables into the disk ports instead of the host ports. The result was very strange, so it could be the same here.

[Jarheadatheart]

Thanks to posts on here, I figured it out. It wasn't pretty but it worked. see sttached:


Now the only issue unresolved is that my 2 systems attached to the array STILL don't "recognize" that it is a SAN that is attached. If I open launcher or any other GUI it see's the disks but not the VA. None of the arm commands work either. They all time out.

Any thoughts as to why this would occur?

[Jarheadatheart]

Oh torsten and the fibre is and was all connected correctly. That is the odd part. Shouldn't the device names have been the same? I was smart enough to create a cabling diagram some time ago.

[Torsten.]

>> Any thoughts as to why this would occur?

I already told you.

[Jarheadatheart]

you said you have seen it before because someone had plugged the fibre into the wrong ports............

I have everything plugged into the correct ports....... So it is a different issue.

[Torsten.]

You did not say you checked this so far ...

Could you post a

# ioscan -fn

# armdiscover

please?

[Torsten.]

I did not see your previous post because I was typing, sorry.

My idea was if somebody unplugged the cable, "somebody" maybe plugged them in wrongly.

However, if you cannot see the array from the host, consider to connect via serial line and check the status.

BTW, you should never see the arrays disks in ioscan, but LUNs only.

[Jarheadatheart]

ioscan finds all of the disks and the armdiscover only finds the local disks. See attached.

[Jarheadatheart]

I actually have a console open to the SAN itself. Oddly enough it reports no errors.

[Torsten.]

Well, it finds the array with alias "crdb_va".

[Jarheadatheart]

Yes, I reinstalled Command View software. Everything seems peachy keen now.

[Jarheadatheart]

Thank you all very much for your help.