Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

SKT2

2 Intern

 • 

1.3K Posts

2630

March 7th, 2008 07:00

power path and HP-UX 10.20

Any one have a working combination of Clarrion model (cx700) , HP-UX 10.20 and a power path s/w .

We had observed a tree passing issue on this setup and power path(dont know the exact version) module was removed (one year back)as it is reported unsupported on HP-UX 10.20.

Now we have two HBA in the system and 10 LUN is asigned to HBA1 remaining 10 LUN to HBA2 for load balancing.Also each of the 10 LUN is zoned to one HBA only so that only path is visible for each LUN.

I would like to keep all the LUNs zoned to both HBA so that the server is able to see two paths which can be added in VG as an alternate path.Currently the VG holds only one path of the each LUN.

The question is there a PP version which can work here, even though not supported? Or without PP can the VG or system handle the a tress pass in case of a SP failure or a HBA failure.

*** you can see the invisible path is reporting as zero size

/usr/local/bin/inq
Inquiry utility, Version V7.2-154 (Rev 4.0) (SIL Version V4.2-154)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

...............................................................................
...............................................................................
...............................................................................
...............................................................................
...............................................................................
...............................................................................
.....................................................................

-------------------------------------------------------------------------
DEVICE :VEND :PROD :REV :SER NUM :CAP(kb)
-------------------------------------------------------------------------
/dev/rdsk/c0t5d0 :SEAGATE :ST318436LC :HP05 :3BM0VMJ8 :17783240
/dev/rdsk/c0t6d0 :SEAGATE :ST318436LC :HP05 :3BM0W30M :17783240
/dev/rdsk/c1t2d0 :HP :DVD-ROM 304 :2.00 : 1999/10 : 190380
/dev/rdsk/c46t0d0 :DGC :CX700WDUNB :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :26516160
/dev/rdsk/c46t0d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t0d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t0d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t5d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t5d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t5d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t5d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t5d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t0d0 :DGC :CX700WDUNB :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :17677440
/dev/rdsk/c47t0d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t0d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t0d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t5d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t5d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t5d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t5d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t5d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0

xe2sdc

2 Intern

 • 

2.8K Posts

March 22nd, 2008 10:00

Best practicies suggest that you zone each HBA to both SPA and SPB.

Usually you'll have two fabrics. Each host have an HBA for every fabric. CX have at least 4 ports (SPA0 - SPA1 - SPB0 - SPB1). Let's call the two fabrics ODD and EVEN (guess why) :D

Now simply plug HBA0, SPA0 and SPB0 to the same fabric .. and HBA1, SPA1, SPB1 to the other fabric.

This will give you 4 available paths for every lun on the CX. 2 out of 4 will be available (through the SP that owns the lun) and the other 2 won't be available (the other SP). In case you loose an SP, you already know what happens .. In case you loose an HBA you'll loose an available and a standby path to your lun ..

But you'll still see the lun.

xe2sdc

2 Intern

 • 

2.8K Posts

March 7th, 2008 07:00

I'm neither a Clariion nor a Powerpath expert .. but AFAIK you HAVE to tell the Clariion if the connected host is an HPUX host, or if it's a Solaris host .. And the Clariion will change slightly its behaviour. Have a look at primus solution emc157830.

Powerpath is a better option since PP will take care of handling failed and resumed paths. But again let's wait some Clariion and powerpath guru to shade some light :D

dynamox

9 Legend

 • 

20.4K Posts

March 7th, 2008 08:00

santhosh,

would you please clarify a few things:

1) so you have 2 HBA's in your box, are both HBAs in the same storage group ? How are these HBAs zoned to Clariion SPs ?

2) is there a reason you are not running PowerPath on this system ? What do you mean by "not supported" in your last question ?

Thanks

Conor

341 Posts

March 7th, 2008 09:00

If you do not want to use PowerPath for whatever reasons, why don't you use PVLinks for path management? Comes as part of the HP-UX OS.
You will need to present all LUNs to both HBAs to have dual paths...

I don't have historical versions of the support matrix, so cannot tell you which versions of PP were supported for HP10.20 - sorry

dynamox

9 Legend

 • 

20.4K Posts

March 7th, 2008 10:00

the only negative i see is that you will have to manually load-balance your primary/alternate paths when you do your volume group work. You can use pvchange -s to specify primary path but remember that that's not persistent ..if you reboot you will need to do it again. If you want it to be persistent you will need to do it with LVM, where for one PV ..primary path is to SPA , second PV primary path is to SPB. Also have to pay attention when you do vgimport as not to use vgimport -s ..as it will grab the first path available ..so there goes your careful load balancing :). Hopefully if the application can afford ..upgrade HPUX and load PowerPath. I like pvlinks ..we use it on dev/test/qa systems ..but all prod is running PP.

my 5 cents :D

SKT2

2 Intern

 • 

1.3K Posts

March 7th, 2008 10:00

"What do you mean by "not supported" in your last question ?"

the tress passing or the path fail over not working as cause the FS/DB to hang.

"If you do not want to use PowerPath for whatever reasons, why don't you use PVLinks for path management? Comes as part of the HP-UX OS.
You will need to present all LUNs to both HBAs to have dual paths"

yes that part is i am looking forward..Cross chekcing any other negative impact doing this way..

SKT2

2 Intern

 • 

1.3K Posts

March 7th, 2008 11:00

here is the distribution. As you can see only one path is made visible to the system as of now. We are planning to zone all the LUNs to both HBA and create alternate PV links on VG level. Zoning is required for that..

--- Physical volumes ---
PV Name /dev/dsk/c46t0d3
PV Status available
Total PE 2157
Free PE 0
Autoswitch On

PV Name /dev/dsk/c46t0d7
PV Status available
Total PE 2157
Free PE 0
Autoswitch On

PV Name /dev/dsk/c46t1d3
PV Status available
Total PE 2157
Free PE 0
Autoswitch On

PV Name /dev/dsk/c47t0d5
PV Status available
Total PE 2157
Free PE 0
Autoswitch On

PV Name /dev/dsk/c47t1d1
PV Status available
Total PE 2157
Free PE 0
Autoswitch On

PV Name /dev/dsk/c47t1d5
PV Status available
Total PE 2157
Free PE 942
Autoswitch On

dynamox

9 Legend

 • 

20.4K Posts

March 7th, 2008 11:00

good ..and you have each PV's primary and alternate path in the Volume group ?

SKT2

2 Intern

 • 

1.3K Posts

March 7th, 2008 11:00

VGs are already load balanced with half the disk to use SPA and other half to SPB.

dynamox

9 Legend

 • 

20.4K Posts

March 7th, 2008 12:00

sounds like a plan ..good luck

SKT2

2 Intern

 • 

1.3K Posts

March 10th, 2008 18:00

now both the HBA are zoned to see all the LUNs. then ran the ioscan and insf.

But i am still not able to access the secondory path. what you feel lokking at the o/p?

Here is the new inq o/p

r#oot [/root] /usr/local/bin/inq
Inquiry utility, Version V7.2-154 (Rev 4.0) (SIL Version V4.2-154)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

...............................................................................
...............................................................................
...............................................................................
...............................................................................
...............................................................................
...............................................................................
.......................................................................

-------------------------------------------------------------------------
DEVICE :VEND :PROD :REV :SER NUM :CAP(kb)
-------------------------------------------------------------------------
/dev/rdsk/c0t5d0 :SEAGATE :ST318436LC :HP05 :3BM0VMJ8 :17783240
/dev/rdsk/c0t6d0 :SEAGATE :ST318436LC :HP05 :3BM0W30M :17783240
/dev/rdsk/c1t2d0 :HP :DVD-ROM 304 :2.00 : 1999/10 : 190380
/dev/rdsk/c46t0d0 :DGC :CX700WDUNB :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :26516160
/dev/rdsk/c46t0d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t0d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t0d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t0d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t1d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t1d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t2d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t2d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t3d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t3d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t4d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t4d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t5d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t5d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t5d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c46t5d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c46t5d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t0d0 :DGC :CX700WDUNB :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT :17677440
/dev/rdsk/c47t0d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t0d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t0d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t0d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t1d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t1d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t2d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t2d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t3d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t3d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d5 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t4d6 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t4d7 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t5d0 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t5d1 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t5d2 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0
/dev/rdsk/c47t5d3 :DGC :CX700WDR5 :HP03 :Ch2 CONT :8838720
/dev/rdsk/c47t5d4 :DGC :CX700WDR5 :HP03 :Ch2 CONT : 0

Message was edited by:
santhosh theyyan

RRR

2 Intern

 • 

5.7K Posts

March 11th, 2008 03:00

If there's an active zoneset (database) already running in your switches and you add a new one to it, you need to activate it (and save it too). That's it.

SKT2

2 Intern

 • 

1.3K Posts

March 11th, 2008 03:00

Even though the zone was removed earlier , all the paths were visible till a reboot. So i am thnking in the reverse order,.. even though zoned the devices are not visible till a reboot.

is there way to refresh the zoning(database) like the way "symmask refresh" or an equivalnet one.

MarcT2

2 Intern

 • 

131 Posts

March 11th, 2008 04:00

I have seen that behaviour with HPUX 10.20 before. If you unzone a path it may require a reboot to actually get rid of it from the OS.

In general, zoning only limits what the fabric nameserver in the switch reports to an HBA and therefore which devices the HBA discovers. There's nothing to actually stop the HBA (initiator) from logging into an arbitrary storage port in a different zone, provided it knows the DID.

Usually when the active zoneset changes a state change notification is sent out by the nameserver to the affected ports (ie HBAs) to update their list of devices. In this case it seems that the update didn't work or was ignored, so the host continues to access devices it's no longer zoned to.

Some switches do offer hardware enforcement of zonesets which would prevent this from occuring.

Marc

RRR

2 Intern

 • 

5.7K Posts

March 11th, 2008 04:00

Waaaw, this is pretty scary stuff.... You mentioned that some switches offer hardware enforcement. Could you name a few ? I've never seen this behavior.....

Was this post helpful?

View All

No Events found!

Top