Networker

Re: [Networker] DDS

2006-06-13 10:25:07
Subject: Re: [Networker] DDS
From: "Wood, R A (Bob)" <WoodR AT CHEVRON DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 13 Jun 2006 15:24:05 +0100
I'd just like to chip in and say that you're alright with multiple
targets (destinations) in a zone but you should only have one initiator
(host) per zone. 

Regards
Bob

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Pascal Rijs
Sent: 13 June 2006 15:04
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] DDS

We have and HP SAN. Two FC switches, 16 port each. Two Libraries, each
connected to only one of the FC switches. I created zones for each link.
A SAN storage node would have four links/zones:

HOST1 HBA1 - SWITCH1 - LIB1
HOST1 HBA1 - SWITCH1 - STORAGE BLOCK1 INTERFACE1
HOST1 HBA2 - SWITCH2 - LIB2
HOST1 HBA2 - SWITCH2 - STORAGE BLOCK1 INTERFACE2

Zoning is configured on the FC switches. It's quite easy on the HP
switches. The best thing to do is to create an overview of the WWN
(World Wide Names) of each HBA and create an ALIAS for it on the FC
switch (like HOST1A (Host1, adapter A). Next create zones for each link;
mapping a source to a destination. Try to prevent having more
destinations in one zone.

Your SAN administrator should know all about this and if you are the SAN
administrator, try to make this material your own.

Kind regards,

Pascal

Fazil Saiyed wrote:

>Hello,
>We employ single initiator single target zoning, drive re-sequiencing 
>is sometime troublesome, please explain your zoning statergy in detail 
>if possible so that everyone can banefit.
>Persistant binding etc.
>Diagrams, conifig etc.



On Mon, 12 Jun 2006 09:08:39 -0400, Fazil Saiyed
<fazil.saiyed AT ANIXTER DOT COM> wrote:

>Hello,
>Initially, had trouble with FC Drives being recognized by the SN 
>server( not legato issues), Driver\etc.
>Once setup and drives configured, pools\groups etc, its working like a 
>charm, no issues what so ever.
>As a failover, you can specify serverhost in the preferences that way 
>if any issues occour with SN mount request can go to the serverhost, 
>also special attention with Serial numbers\drivers\zoning\jbconfig 
>needs to be paid so that the envroment is stable, test first and then 
>switch slowly to production servers.
>Our enviroent is Windows 2003\64 for MS, Windows 2003\32 bit for SN.
>Networker 7.2.1
>Thank
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
>body of the email. Please write to 
>networker-request AT listserv.temple DOT edu
if you have any problems
>wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>=======================================================================
>==

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems wit this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>