Operating System - Tru64 Unix
1748089 Members
4979 Online
108758 Solutions
New Discussion юеВ

check paths to SAN disk

 
SOLVED
Go to solution
lawrenzo
Trusted Contributor

check paths to SAN disk

Hello all,

I am new to tru64 and just starting to get my head around the command syntax etc ....

I have been tasked to check the data paths to SAN attached disk on my system:

root@cgcu007a # hwmgr -show scsi -full

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
0: 70 cgcu007a processor none 0 1 (null)

WWID:0b000008:1000-0000-c927-8784


BUS TARGET LUN PATH STATE
---------------------------------
0 254 0 stale

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
0: 71 cgcu007a processor none 0 1 (null)

WWID:0b000008:1000-0000-c927-9a1f


BUS TARGET LUN PATH STATE
---------------------------------
2 253 0 stale

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
523: 115 cgcu007a disk none 2 4 dsk3901 [2/5/1]

WWID:01000010:6005-08b4-0001-363e-0002-a000-06f4-0000


BUS TARGET LUN PATH STATE
---------------------------------
2 5 1 valid
2 6 1 valid
0 7 1 valid
0 1 1 valid

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
524: 116 cgcu007a disk none 2 4 dsk3902 [2/5/2]

WWID:01000010:6005-08b4-0001-363e-0002-a000-06f9-0000


BUS TARGET LUN PATH STATE
---------------------------------
2 5 2 valid
2 6 2 valid
0 7 2 valid
0 1 2 valid

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
239: 35 cgcu007a raid none 0 1 (null)

WWID:02000008:5000-1fe1-0010-1330


BUS TARGET LUN PATH STATE
---------------------------------
2 16 0 stale

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
240: 36 cgcu007a raid none 0 1 (null)

WWID:02000008:5000-1fe1-0014-a920


BUS TARGET LUN PATH STATE
---------------------------------
2 17 0 stale


I ran a comparison of what is in the hwmgr list and what is present in /etc/fdmns and there are some disks that are not in the directory and when i run:

# disklabel -r disklabel -r dsk3902
disklabel: dsk3715: No such file or directory

my task is basically to check the paths - can anyone provide some guidance or help please?

Thanks

Chris.
hello
6 REPLIES 6
Rob Leadbeater
Honored Contributor
Solution

Re: check paths to SAN disk

Hi Chris,

The command you've already used "hwmgr show scsi -full" shows the paths to the disks...

In the output above you can see that dsk3902 has four valid paths to the SAN.

It appears however that there are references to some old devices in the hardware databases, hence why you have some null devices stale entries.

Not all disk devices will necessarily be found under /etc/fdmns - only those used in AdvFS domains. For example if you have any UFS file systems you won't find them there. Same for a quorum disk.

Hope this helps,

Regards,

Rob
lawrenzo
Trusted Contributor

Re: check paths to SAN disk

ok thanks for that, so my next question would be what is the best way to identify if there is a valid path down?

I have read the man page for hwmgr_show which gives some good examples.

Chris.
hello
Ivan Ferreira
Honored Contributor

Re: check paths to SAN disk

hwmgr show scsi -full is the command. The paths with valid state are good. If you have one or more invalid paths, you will see them as "stale".

If you get (null), then the device should be removed from the database using:

hwmgr delete -id
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Hein van den Heuvel
Honored Contributor

Re: check paths to SAN disk

Well, if hwmgr indicated a valid path, then there is!? If it indicates 4 then there are 4.. to the same device, and Tru64 can and will use them all if warranted.

What version of tru64 is this now?

You may want to do a: hwmgr scan scsi
Before the: hwmgr scan scsi

>> # disklabel -r disklabel -r dsk3902
>> disklabel: dsk3715: No such file or directory

Is that a typo?
I would only ever ask for 1 item, as per man page.

The man page mostly suggests just a devive name, but I would specify a full path to that special file, like:
/dev/rdisk/dsk0c

Did you ask for dsk3902 and it came back with dsk3715?
Time to look in /dec/rdisk !

Those are high numbers!
Whta is happening here?
Are devices often (re)created?
Have folks been playing with dsfmgr
Check out the dsfmgr options -e and -m

Once you start understanding this stuff, you may want to consider cleaning up the stale devices.
No rush, that don't hurt, and only confuse operaters, not the OS.
Eventually you may use:
hwmgr -delete component -id
No rush, and pick a quiet time
May even just before or after a reboot.

Enjoy!
Hein.






lawrenzo
Trusted Contributor

Re: check paths to SAN disk

Thanks for the input hein,

yes disklabel was a typo and copied the wrong output so:

root@cgcu007a # disklabel -r dsk3715
disklabel: dsk3715: No such file or directory

version is

OSF1 cgcu007a V5.1 2650 alpha

the problem I have is that I am new to the company and have picked up this work.

I'll take your advice and learn a bit more, but from your comments I dont have anything to worry about ....

what should I be looking for with issues regarding the datapath?

basically they have upgraded firmware on the switch and I am attempting to identify any errors?

Thanks

Chris.


hello
Kapil Jha
Honored Contributor

Re: check paths to SAN disk

Hello Lawrenzo,
Simplest way to see data path is
#hwmgr view dev
this would beautifully show the location of devices.
You can add -cluster if system is in cluster.
Please follow the advices given above also.
They are very precious.
BR,
Kapil
I am in this small bowl, I wane see the real world......