beautypg.com

29 troubleshooting lun presentation, 29 troubleshooting lun presentation -49, Troubleshooting lun presentation (section 9.29) – HP StorageWorks Scalable File Share User Manual

Page 273: E section 9.29

background image

Troubleshooting LUN presentation

9–49

( 2: 2): Total reqs 24, Pending reqs 0, flags 0x2, 0:0:84 00
( 2: 3): Total reqs 24, Pending reqs 0, flags 0x2, 0:0:83 00
( 2: 4): Total reqs 24, Pending reqs 0, flags 0x2, 0:0:84 00
( 2: 5): Total reqs 24, Pending reqs 0, flags 0x2, 0:0:83 00
( 3: 0): Total reqs 3, Pending reqs 0, flags 0x0, 0:0:84 0c
( 4: 0): Total reqs 3, Pending reqs 0, flags 0x0, 0:0:85 0c
( 4: 1): Total reqs 24, Pending reqs 0, flags 0x2, 0:0:85 00
( 4: 2): Total reqs 28, Pending reqs 0, flags 0x2, 0:0:86 00
( 5: 0): Total reqs 3, Pending reqs 0, flags 0x0, 0:0:86 0c

9.29 Troubleshooting LUN presentation

If LUNs are presented correctly, each LUN will only be visible through one controller on an EVA4000 array.

If the

OPERATING_SYSTEM

parameter for a host is not set to

UNKNOWN

when the host is configured, a LUN

may be visible through both of the controllers on an EVA4000 array when the LUN is presented to the host.

Information about the LUNs is stored in the

/proc/partitions

directory. When LUNs are created and

presented to a host, and the Fibre Channel module is loaded on the host, the LUNs are listed in the

/proc/partitions

directory as

/dev/sdn

where

n

=

a

,

b

,

c

,

d

, and so on. The LUN sizes are also

listed.

You can use the

/usr/opt/hpls/diags/bin/controller_check.bash

command to check the

information for any LUN that you suspect may be incorrectly presented. You can run the command on an

Object Storage Server, the administration server, or the MDS server to verify that the correct number of

controllers and controller pairs are visible to the server, and that the LUNs presented to the server are

correctly distributed amongst the controllers.

Enter the command as follows:

# /usr/opt/hpls/diags/bin/controller_check.bash

The syntax of this command is as follows:

controller_check.bash [-h] | [-e=num_eva] [-s binary]

Where:

-h

Prints help on the command.

-e --eva

Specifies the number of EVA4000 controller pairs that should be

attached to the server.

-s --scsi_info binary

Specifies that a binary other than the default (

/usr/bin/

hpls_scsi_info

) is to be used. Use this option only if there is a

problem with the default binary.

The following is an example of the output from the command where LUNs from an EVA4000 array are

(correctly) visible to only one controller in the controller pair:

# /usr/opt/hpls/diags/bin/controller_check.bash

Controller Pair: 50001fe15003a6d0
Controller: P5849E1AAQF05K
Lun: 600508b4001012d10000400000460000
Disks: /dev/sda Size: 2 GB
Lun: 600508b4001012d10000400000490000
Disks: /dev/sdb Size: 555 GB
Controller: P5849E1AAQH04A
Lun: 600508b4001012d100004000003e0000
Disks: /dev/sdc Size: 2 GB
Lun: 600508b4001012d10000400000430000
Disks: /dev/sdd Size: 555 GB
Controller Check PASSED