Unsolved

This post is more than 5 years old

155 Posts

1811

March 19th, 2009 03:00

how to identify the DMX symdev ID on AIX host?

friends,

here the situation is i need to find out the symdev id associated with hdisks. powermt display does show them but for 2 hdisks , it looks like powerpath not configured yet.

but the attributes of hdisks are showing as they were DMX sym devices. I need to find out the symdev LUN ID for these 2 hdisks . thanks

hdiskpower26 U787B.001.DNWG5R6-P1-C4-T2-L32 PowerPath Device
----------------

Consistency Group Name
Clear Queue (RS/6000) yes
Location
LUN ID 0xa4000000000000
FC Forced Open LUN yes
Maximum coalesce size 0x20000
Maximum transfer size 0x40000
Physical volume identifier 00063627d94f55cd0000000000000000
Takeover PVIDs from hdisks yes
Use QERR bit no
Queue TYPE simple
Queue DEPTH 16
REASSIGN time out value 120
Reserve device on open yes
READ/WRITE time out 40
SCSI ID 0xf1b00
START unit time out 180
World Wide Name 0x5006048c52a5c368

hdiskpower27 U787B.001.DNWG5R6-P1-C4-T2-L33 PowerPath Device
----------------
Consistency Group Name
Clear Queue (RS/6000) yes
Location
LUN ID 0xa5000000000000
FC Forced Open LUN yes
Maximum coalesce size 0x20000
Maximum transfer size 0x40000
Physical volume identifier 00063627d953a5a10000000000000000
Takeover PVIDs from hdisks yes
Use QERR bit no
Queue TYPE simple
Queue DEPTH 16
REASSIGN time out value 120
Reserve device on open yes
READ/WRITE time out 40
SCSI ID 0xf1b00
START unit time out 180
World Wide Name 0x5006048c52a5c368

111 Posts

March 19th, 2009 03:00

Hi,

- PowerPath not configured? Maybe you need a 'powermt config' command?
- Did you try using the inq utility? or installing SYMCLI and trying syminq?

155 Posts

March 19th, 2009 04:00

Maxim, actually i dont see that LUNs at storage end from symmaskdb masked to the host WWN. but those hdisks attributes are showing as they were DMX devices. thus, need to find out what was the LUN ID associated with that hdisks

6 Operator

 • 

2.8K Posts

March 19th, 2009 05:00

IMHO Vault devices can't be mapped on the Frontend .. Vaults are internal-only devices used while shutting down the DMX. I guess you are either looking at the wrong device or have to issue a symcfg discover.
Please note that it's hard to guess if you have to look at dev 0BAD or dev 1BAD since they both will show same serial number (XXBAD000).

155 Posts

March 19th, 2009 05:00

excellnt dynamox. i got the LUN IDs.

when i checked the device attributes, one of them is

Device Emulation Type : VAULT_DEVICE
Device Configuration : VAULT (Non-Exclusive Access)

wondering why VAULT is assigned to host?

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

March 19th, 2009 05:00

run lscfg -v

output will look something like this:


  hdisk11          U787E.001.AAA4729-P2-C2-T1-W5006048C52A54E07-L7F000000000000  EMC Symmetrix FCP Raid5
 
        Manufacturer................EMC
        Machine Type and Model......SYMMETRIX
        ROS Level and ID............5771
        Serial Number...............XX897000
        Part Number.................000000000000510027000290
        EC Level....................100XXX
        Device Specific.(Z0)........00
        Device Specific.(Z1)........51
        Device Specific.(Z2)........577101050000000000011408
        Device Specific.(Z3)........12000000
        Device Specific.(Z4)........54110008
        Device Specific.(Z5)........FF80
        Device Specific.(Z6)........4D


look at the serial number, the first two number are "last" two numbers of your box serial number and then the next 3 or 4 are the hyper id, in my case 897.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

March 19th, 2009 05:00

this is not normal:

emc171243

155 Posts

March 19th, 2009 06:00

i got that ID 000 from serial # Serial Number...............050000

hdiskpower26 U787B.001.DNWG5R6-P1-C4-T2-L32
PowerPath Device
Manufacturer................EMC
Machine Type and Model......SYMMETRIX
ROS Level and ID............5772
Serial Number...............050000
Part Number.................000000000000610028010290
EC Level....................101005
Device Specific.(Z0)........00
Device Specific.(Z1)........61
Device Specific.(Z2)........577200880000000000071708
Device Specific.(Z3)........12000000
Device Specific.(Z4)........54110008
Device Specific.(Z5)........FF80
Device Specific.(Z6)........45

155 Posts

March 19th, 2009 06:00

dynamox, no powerpath configured yet for that device. also, it is not allocated to that host . looks like it was assigned to it once. i am in the process of finding out the devices associated with hdiskpower26 and hdiskpower27.

hdiskpower27 is 2-way mirror device but not masked to the host wwn as per symmaskdb list. but at the host end, these 2 hdiskpower disks are referring to 000 and FF1 symdevices. not sure whether they were assigned to the host once and removed later. is there anyway i can figure that out by referring to the history or something like that?

6 Operator

 • 

2.8K Posts

March 19th, 2009 06:00

hdiskpower doesn't have valid serial numbers (only 7 digits)

Notice that Dynamox posted output of command against "hdiskX". Serial number have 8 digits, the first two are the rightmost part of box serial number.

powermt display dev=hdiskpower26 is a good advice. Powerpath will show you the s/n of the device.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

March 19th, 2009 06:00

can you run powermt display dev=hdiskpower26 ..

6 Operator

 • 

2.8K Posts

March 19th, 2009 07:00

Did you ever run symaudit command ?? :D

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

March 19th, 2009 07:00

do you take vcmdb backups as you should ? :)

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

March 19th, 2009 07:00

you can look in /var/log/syslog.log ..but it's a long shot.

155 Posts

March 19th, 2009 07:00

extremely sorry guys .. it was not 000, but FF0 :) and it is a 2-way mirror.

the only thing i wanted to make sure now whether they were assigned to that host once. is there anyway it can be done?

for sure, now FF0 and FF1 are not masked to any wwn (host)
No Events found!

Top