lspath output interpretation Post: 302600778

Sponsored Content

Operating Systems AIX lspath output interpretation Post 302600778 by petervg on Wednesday 22nd of February 2012 04:39:24 AM

02-22-2012

Registered User

lspath output interpretation

On my VIo I see the following for my disks:

Code:

$ lspath | grep hdisk6
Enabled hdisk6 fscsi0 200600a0b82193f7,4000000000000
Enabled hdisk6 fscsi0 200700a0b82193f7,4000000000000
Enabled hdisk6 fscsi2 200600a0b82193f8,4000000000000
Failed hdisk6 fscsi2 200700a0b82193f8,4000000000000
 
$ lspath | grep hdisk7
Enabled hdisk7  fscsi0 200600a0b82193f7,5000000000000
Enabled hdisk7  fscsi0 200700a0b82193f7,5000000000000
Failed  hdisk7  fscsi2 200600a0b82193f8,5000000000000
Failed  hdisk7  fscsi2 200700a0b82193f8,5000000000000
 
$ lspath | grep hdisk23
Enabled hdisk23 fscsi0 200600a0b82193f7,14000000000000
Enabled hdisk23 fscsi0 200700a0b82193f7,14000000000000
Enabled hdisk23 fscsi2 200600a0b82193f8,14000000000000
Enabled hdisk23 fscsi2 200700a0b82193f8,14000000000000

Is see that some disks have a failed path on fscsi2. Other disks are just running fine with a path over fscsi2.

May I conclude that the hardware is working and that ther is a problem with the zoning of the SAN? Or could HW still be a problemen? All LUNS are provided from the same SAN storage box meaning that if hdisk23 is available on all paths, the cables between the SAN box and the server are correct.

--Peter

petervg

View Public Profile for petervg

Find all posts by petervg

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

shell interpretation

I executed the following command in the korn shell: $ variable1="qwerty" ls | sort and the shell executed the 'ls | sort' command. I would have expected an error message from the shell, but instead of that the shell ran the 'ls | sort' command and didn't realize the variable assignement. ...

2. UNIX for Advanced & Expert Users

SAR -b interpretation

I have used SAR -b to get some Unix cache / buffer metrics and the results are confusing me a bit. The pread/s & pwrit/s are showing 0. However the lread/s and lwrit/s are showing figures. I note also that the bread/s and bwrit/s are showing figures. I believe that pread/s and pwrit/s is not...

3. AIX

interpretation of sar

hello with a sar i have this result: System configuration: lcpu=48 ent=4.00 14:06:37 %usr %sys %wio %idle physc %entc 14:06:39 26 9 3 62 1.63 40.7 14:06:41 26 9 3 63 1.58 39.4 14:06:43 ...

4. IP Networking

DNS ENUM RR interpretation

Hi Guys, This is really really urgent. Am looking out for some quick answers. I'm developing a DNS Resolver client that interprets DNS Query repsonses & pass on the needful to DNS applications. When an ENUM query(modified to an nslookup naptr query) is issued & an NAPTR RR(Resource Record)...

5. Shell Programming and Scripting

Weird Interpretation by Awk

Hi, I am not sure what I am doing wrong but I am messing up some logic here. The input file is something like this: *___String Type A Here___String Type B Here___123 *___ ___String Type B Here___123 *___ ___String Type B Here___123 *___ ...

6. AIX

SDD SDDPCM MPIO lspath Jargon

Can anyone recommend me some reading material surrounding how AIX handles LUNs: - with and without MPIO installed - with and without SDD or SDDPCM installed Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed? I guess...

7. Solaris

solaris versions interpretation

Hi What means Solaris 10 5/09 and Solaris 10 10/09, I mean the suffix 5/09 and 10/09 ? thx for help.

8. Shell Programming and Scripting

Negating shell interpretation

I'm writing a Korn script but am having trouble because the shell interprets the asterisk in this case. Can anyone tell me if there is a way to fix this so that grep takes in STDIN without the interpretation? line="30 09 * * 1-4 /home/user01/bin/start" echo "$line" | grep 'start'

9. UNIX for Advanced & Expert Users

Truss output interpretation

hi, anyone can help on this piece of truss output? 8094: 0.7028 write(4, 0x0043BE90, 236) = 236 8094: T S H \0\0\0EC020101\0\0\0\0\0\0\0\0\0 "02\0\0 303\0\0 I D 8094: \f %\0\0\0\0 2\0F67F\0\0\0\0 @06FFC99A ; 8094: L D6\0 303 8094: ...

LEARN ABOUT OSF1

ppmtosixel

ppmtosixel(1)						      General Commands Manual						     ppmtosixel(1)

NAME

       ppmtosixel - convert a portable pixmap into DEC sixel format

SYNOPSIS

       ppmtosixel [-raw] [-margin] [ppmfile]

DESCRIPTION

       Reads  a  portable  pixmap  as input.  Produces sixel commands (SIX) as output.	The output is formatted for color printing, e.g. for a DEC
       LJ250 color inkjet printer.

       If RGB values from the PPM file do not have maxval=100, the RGB values are rescaled.  A printer control header and a color assignment table
       begin the SIX file.  Image data is written in a compressed format by default.  A printer control footer ends the image file.

OPTIONS

       -raw   If  specified,  each  pixel  will  be explicitly described in the image file.  If -raw is not specified, output will default to com-
	      pressed format in which identical adjacent pixels are replaced by "repeat pixel" commands.  A raw file is often an order	of  magni-
	      tude larger than a compressed file and prints much slower.

       -margin
	      If  -margin  is not specified, the image will be start at the left margin (of the window, paper, or whatever).  If -margin is speci-
	      fied, a 1.5 inch left margin will offset the image.

PRINTING

       Generally, sixel files must reach the printer unfiltered.  Use the lpr -x option or cat filename > /dev/tty0?.

BUGS

       Upon rescaling, truncation of the least significant bits of RGB values may result in poor color conversion.  If the original PPM maxval was
       greater	than  100,  rescaling  also reduces the image depth.  While the actual RGB values from the ppm file are more or less retained, the
       color palette of the LJ250 may not match the colors on your screen.  This seems to be a printer limitation.

SEE ALSO

       ppm(5)

AUTHOR

       Copyright (C) 1991 by Rick Vinci.

								   26 April 1991						     ppmtosixel(1)