[SUMMARY] HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH

From: EBOVE@bouyguestelecom.fr
Date: Wed May 29 2002 - 06:56:23 EDT


Thanks to :
Jan Mark Holzer [SMTP:JanMark.Holzer@hp.com]
Raul Sossa S. [RSossa@datadec.co.cr]
alan@nabeth.cxo.cpqcorp.net
Rainer Wolf [rainer.wolf@rz.uni-ulm.de]
Haesaerts, Corinne [Corinne.Haesaerts@hp.com]
Frank Chu-Cheong [frank@digi-data.com]
Hannes Visagie [visageh@mtn.co.ug]

who replied.

The fact is that there is no automatic way to reassign an unit to its
original controler.
the only way to do it is to use "scu" with the sbtl command. This will
rebalance the unit,
using the CAM and not the multipathing.

Following, all the answers :

> -----Message d'origine-----
> De: Jan Mark Holzer [SMTP:JanMark.Holzer@hp.com]
> Objet: RE: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH
>
>
>
> Hello,
>
> the HSG80 does not support automatic failback after a controller
> failure.
> If you need to rebalance the units after a controller
> reboot/failure
> you'd have to use scu (and hsxterm) to move them to a different
> controller port .
>
> Hth,
>
> Jan
>
>
-----Message d'origine-----
De: Raul Sossa S. [SMTP:RSossa@datadec.co.cr]
Date: mardi 28 mai 2002 19:59
À: BOVE, Emmanuel
Objet: RE: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH
Importance: Haute

PREFERRED_PATH does not mean FAIVORED_CONTROLLER.
In other words, this functionality does only work for controller booting.
Do not pretend it to change online.

It really works when you restart both controllers at the same time.
 ---------------------------------------------------------------

De: alan@nabeth.cxo.cpqcorp.net [SMTP:alan@nabeth.cxo.cpqcorp.net]
Objet: Re: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH

Date: Tue, 28 May 02 11:07:35 -0600
From: alan@nabeth.cxo.cpqcorp.net
X-Mts: smtp

        I'm told that the HSG side of this behavior is what is
        expected. The operating system tries to know as little
        as possible about the storage subsystem behind a particular
        unit, so it isn't likely to do anything special. What you
        might try is using scu(8) to send a "start" to the unit
        and if that doesn't work a "stop" followed by a "start".

        Not having ever tried this, I'd only try the stop/start
        cycle with the unit out of service. My limited experience
        is that the operating system often copes with unit that
        aren't ready by doing the "start" itself, but I wouldn't
        press the issue, except under controlled conditions.
-----------------------------------------------------------------------

De: Frank Chu-Cheong [SMTP:frank@digi-data.com]
Objet: RE: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH

Is this of any use??
Document AA-RHGWC-TE, pg.6-11 states in part: If you have preferred
units , and ... one controller (re)starts before the other controller.
the HSG80 controller (re)starting first will take all the units, whether
they are preferred or not. When the other controller starts, it will not
have access to the preferred units, and wil be inactive. Therefore, you
want to ensure that both HSG80 controllers start at the same time, under
all circumstances so that the controller sees its own preferred units

----------------------------------------------------------------------------
-

De: Kevin Jones [SMTP:Kevin.Jones@compelsolve.co.uk]
Objet: RE: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH

Emmanul

Unfortunately this is the expected (correct) behaviour. If the unit is to be
'served' by the preferred HSG80 controller, then the pair must be rebooted
together within a short time of each other (30 seconds I think). As you have
seen when one HSG80 in the pair is rebooted, the unit fails over to the
other HSG80 but does NOT fail back. The only way of making it fail back is
by use of the scu utility and forcing a start on the unit via a specific
bus, target, lun, unfortunately I have never seen the precise syntax for
doing this but I assume it will be in the scu man page.

Regards

Kevin Jones
 
----------------------------------------------------------------------------

---
De:	Hannes Visagie [SMTP:visageh@mtn.co.ug]
Objet:	RE: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH
AFAIK from docs a while back, that is what will happen in 8.5.  Preferred
path will not fail back to original controller.  But this was +1 year ago.
You should be able to reset by "hsxterm5" if "Command console lun" enabled.
Perhaps you can force from Unix to use preferred path.
----------------------------------------------------------------------------
----------------------
De:	Rainer Wolf [SMTP:rainer.wolf@rz.uni-ulm.de]
Objet:	Re: HSG80 8.6 P - 5.1A : Fun whith PREFERRED_PATH
Hi,
I remember to have the same problem but on another hardware.
The solution there was to use a 'force' flag to get it/change it 
back to the controller you want - just an idea : you may look for 
a force-flag 
 
Greetings
Rainer 
>     
> 
> 
> 
----------------------- ORIGINAL POST :
-------------------------------------------
> We are runing a configuration of ES40, 2 KGPSA connected to a pair
> of HS80 redondant in multibus failover mode, usin two brocade switches.
> When creating an unit , everything is fine. The Preferred_path is
correctly
> set and
> the unit is online on the right controler.
> When you reboot the controler, the unit is correctly active on the other
> controler.
> After the reboot, when the controler is up, the unit stays where it is,
> ignoring completly
> the "Prefered_path" .
> Even with :
> # hwmgr -scan scsi
> or making I/o on the unit, it stays on the wrong controler and don't come
> back to
> its original state.
> 
> Any ideas would be helpfull,
> 
> TIA
> 
> Emmanul Bove


This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:42 EDT