This post is more than 5 years old

4 Apprentice

 • 

542 Posts

2013

May 25th, 2010 09:00

Cant get Lun's to trepass

Hello,   I have about 5 lun's (all from the same 2 host active/passive cluster) that i cannot trespass.  I have tried the GUI and CLI.  The hosts are W2008 SP2 and are zoned to both SPA & SPB.  Paths to both SP's are logged in. I have other host connected to the system that I can trespass just fine.

Am i missing something...

I need to do a FLARE upgrade from R28 to R29 and i was testing something and just noticed this.

Are there any logs that would tell me why the trespass doesnt go thru.    I dont get a failure message when attempting to do it.   using clariion/failover mode 1

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

May 25th, 2010 15:00

powermt.custom

433 Posts

May 25th, 2010 10:00

Hi Kenn,

Please check the Powerpath. Does it states "PowerPath shows only paths to one SP". If yes then Change the zoning so that the HBA is zoned to both SPs. Is this the case.

If not please reply i can provide you some more solutions.

6 Operator

 • 

4.5K Posts

May 25th, 2010 11:00

A couple things to look at:

Each host has one HBA zoned to SPA and SPB:

Host1_HBA0  <---> SPA

Host1_HBA0  <---> SPB

Check to see what the Default Owner for the LUN is, then change the Default ownership to the SP you want to trespass the LUN to then from the host run the PowerPath command:

powermt restore dev=all

That should cause PowerPath to move the LUN to the Default owner.

glen

4 Apprentice

 • 

542 Posts

May 25th, 2010 11:00

well this is a touchy subject...

I opened a thread on the switch forums about this customers setup.  long story short is that they have to many VSAN's without IVR and so they are not able to place multiple FE ports from each SP into each VSAN.  Becuase of that they also do not use licensed powerpath.

So the VSAN's that they are a members of only have one port for HBA0 (A0) and one port (B0) for HBA1.  With this setup,  that still gives the host connectivity to both SP's.

I have other hosts with the same setup that can trespass fine.

I am trying to find someone with host access to check powerpath..

will update later

4 Apprentice

 • 

542 Posts

May 25th, 2010 12:00

when i run the dev=all command right now,  it shows that harddisk 4

default=A  current=A

When i right click on the lun for properties,

default=A   Current=B

this is after a update request.

It is like powerpath is not showing the correct info

4 Apprentice

 • 

542 Posts

May 25th, 2010 12:00

because if the limited number of SP ports available, we are not able to zone like this:

Host1_HBA0  <---> SPA

Host1_HBA0  <---> SPB

It is more like this:

Host1_HBA0  <---> SPA

Host1_HBA1  <---> SPB

Here is the powerpath readout


C:\Program Files (x86)\EMC\PowerPath>powermt display dev=all

Pseudo name=harddisk4
CLARiiON ID=APM00091102446 [MODBDIST-CLS]
Logical device ID=60060160267022004675E63B3751DE11 [MODBDIST1_LOGS]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP B       Array failover mode: 1
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   2 port2\path0\tgt0\lun3     c2t0d3    SP B0     active  alive      0      1
   3 port3\path0\tgt0\lun3     c3t0d3    SP A0     active  alive      0      2

I tried your recommendation on harddisk 4 and did the restore command.  Now display dev=all shows

Pseudo name=harddisk4
CLARiiON ID=APM00091102446 [MODBDIST-CLS]
Logical device ID=60060160267022004675E63B3751DE11 [MODBDIST1_LOGS]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A       Array failover mode: 1
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   2 port2\path0\tgt0\lun3     c2t0d3    SP B0     active  alive      0      1
   3 port3\path0\tgt0\lun3     c3t0d3    SP A0     active  alive      0      2

But the GUI still shows that it is listed under SPB and it shows up when i run "trespass lun status"

I need to make sure that all these lun's will trespass back and forth before i perfom a FLARE upgrade.

And i just noticed that this host is using licensed Powerpath...

And to complicate things,  i was able to trespass one of the luns for this cluster to other SP.  when i tried a second lun, the first one trespassed back.

sorry if i am making this confusing

6 Operator

 • 

4.5K Posts

May 25th, 2010 12:00

You'll notice that the LUN trespassed:

Pseudo name=harddisk4
Owner: default=SP A,  current=SP B

Pseudo name=harddisk4
Owner: default=SP A,  current=SP A

Check in Navisphere GUI - right click on the LUN and select Properties - do the Default and Current owner match?

Try right click on array icon and "Update Now" and see if that changes.

glen

4 Apprentice

 • 

542 Posts

May 25th, 2010 12:00

There are not many trespass messages in the event logs for either SP.

Toddjam10,

I cant remember if the powermt config dev=all command is disruptive.   I have already done the other 2  do you mean powermt reconfig?  I dont see an option for "config"

30 Posts

May 25th, 2010 12:00

How about running:

powermt config dev=all

powermt restore dev=all

powermt display dev=all

6 Operator

 • 

4.5K Posts

May 25th, 2010 12:00

Look in the Event log for SPA - are you seeing a lot of trespass messages?

glen

30 Posts

May 25th, 2010 13:00

yes, my fault please disregard, powermt config doesn't look to be supported on windows

6 Operator

 • 

4.5K Posts

May 25th, 2010 14:00

PowerPath seems to be the problem - if Navisphere is displaying the correct information (and I have high confidence that it is) then PowerPath must not be working correctly.

There is a persistent configuration in PP - in UNIX systems you can find the file, rename it, then reboot and it will re-create the persistence based on a new bus scan. In Windows I believe you have to reboot the OS.

One obvious way is to un-install PP and re-install.

Have you tried posting in the PowerPath forum?

glen

4 Apprentice

 • 

542 Posts

May 25th, 2010 14:00

I think the file your talking about is a powerpath.common file or something close.  i will have to research my notes on it.

Are you thinking that that file is keeping a persistant path and wont let the lun trespass?

And where are the powerpath forums located?   i dont see an entry under the support list.

Thanks for your help

2.2K Posts

May 25th, 2010 15:00

Yeah the PowerPath forum got kind of hidden after the move from the old forum format. Look under host systems, you will see the powerpath forums under there.

6 Operator

 • 

4.5K Posts

May 26th, 2010 09:00

In UNIX there is a powermt.custom file created when you run the powermt save command - in Windows it's in the registry somewhere.

glen

No Events found!

Top