Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

600

May 14th, 2007 09:00

Added more devices from the same frame - paths missing for one device

This host already had 12 devices presented from this Clariion. We presented 10 more. Powermt looks right for all the devices except the last one added (not that I think that is the problem.)

Pseudo name=emcpower15a
CLARiiON ID=APM00041100xxx [Host X]
Logical device ID=60060160AE701000C83377C8FCF3DB11
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
2304 pci@8/lpfc@4 c2t43d15s0 SP A3 active alive 0 0
2304 pci@8/lpfc@4 c2t47d15s0 SP B2 active alive 0 0
2305 pci@8/lpfc@5 c3t42d15s0 SP A2 active alive 0 0
2305 pci@8/lpfc@5 c3t48d15s0 SP B3 active alive 0 0

Pseudo name=emcpower16a
CLARiiON ID=APM00041100xxx
Logical device ID=60060160AE7010001A7C04D3FCF3DB11
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
2304 pci@8/lpfc@4 c2t47d16s0 SP B2 active alive 0 0
2305 pci@8/lpfc@5 c3t48d16s0 SP B3 active alive 0 0

I had the host admin do a powermt config - nothing changed. All the connectivity on the frame is right or we'd have the same problem for all the devices, not just this one. I don't want to take the shotgun approach of tossing Solaris Scsi commands at it but I guess I can if no one knows why this is.

9 Legend

 • 

20.4K Posts

May 14th, 2007 11:00

I wonder if their sd.conf configured to go far enough for target 43 and target 42. Can you get a copy of sd.conf and see if it looks something like this:

name="sd" parent="lpfc" target=43 lun=16 hba="lpfc0" ;
name="sd" parent="lpfc" target=42 lun=16 hba="lpfc0" ;

1 Rookie

 • 

55 Posts

May 14th, 2007 10:00

They're supposed to be using them.

9 Legend

 • 

20.4K Posts

May 14th, 2007 10:00

are you using sd.conf and lpfc.conf ?

147 Posts

May 15th, 2007 17:00

I wonder if their sd.conf configured to go far enough
for target 43 and target 42.


I agree, this is the most likely cause based on symptoms.

9 Legend

 • 

20.4K Posts

May 17th, 2007 05:00

good ..so what does it look like now ?

1 Rookie

 • 

55 Posts

May 17th, 2007 05:00

That was it.

She had this in her sd.conf

name="sd" parent="lpfc" target=42 lun=15;
name="sd" parent="lpfc" target=43 lun=15;
name="sd" parent="lpfc" target=47 lun=16;
name="sd" parent="lpfc" target=48 lun=16;

So you add device 16 you're going to have an issue.

Thanks for the help.
No Events found!

Top