From: John Little <jslittl@hendricks.org>
To: dm-devel@redhat.com
Cc: James.Smart@emulex.com, egoggin@emc.com
Subject: RE: multipath and san fabric
Date: Tue, 14 Nov 2006 08:09:20 -0500 [thread overview]
Message-ID: <200611140809.21110.jslittl@hendricks.org> (raw)
Hi all
Wow. thanks for the responses...
James Smart <James.Smart@Emulex.Com> wrote on 11/13/2006 02:54:15 PM:
> >>> Example 2:
> >>> Fabric A contains HBA1, TargetPort1, and TargetPort3.
> >>> Typically a zone
> >>> would exist within Fabric A that contains these 3 ports.
> >>> Fabric B contains HBA2, TargetPort2, and TargetPort4.
> >>> Typically a zone
> >>> would exist within Fabric B that contains these 3 ports.
> >>> The storage array contains 2 controllers, with 2 ports per
> >>> controller.
> >>> Meaning TargetPort1 and TargetPort2 are on controller A,
> >>> and TargetPort3
> >>> and TargetPort4 are on controller B. The ports are cross
> >>> connected on
> >>> the fabrics for redundancy. All storage can be seen from
> >>> any port.
> >>> --
> >>> This would ahve 4 DM paths
> >>> The I_T nexus's are:
> >>> HBA1_TargetPort1
> >>> HBA1_TargetPort3
> >>> HBA2_TargetPort2
> >>> HBA2_TargetPort4
Ok I'm new to SAN and multipathing so maybe it's just the way it is worded.
Here is what we have and the instructions that were given to me.
####
FCSW00 xxx.xxx.xxx.233 Fabric A
FCSW01 xxx.xxx.xxx.234 Fabric B
FCSW02 xxx.xxx.xxx.235 Fabric A
FCSW03 xxx.xxx.xxx.236 Fabric B
Summary: One HBA is attached to each fabric; two zones per HBA. One is zoned
to a port on SPA and one is zoned to a port on SPB We have a CX600 which has
4 ports per SP. So, it could be zoned to SPA0 (0-3)and SPB0(0-3)
####
If I understand correctly what I have is Example 2 (typo corrected). Then I
would, for an hba connected to Fabric A on a port on FCSW00, setup a zone on
FCSW00 and another on FCSW02. The same would apply for the hba in Fabric B
using FCSW01 and FCSW03.
Is this correct or am I still lost?
Thanks,
John
next reply other threads:[~2006-11-14 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 13:09 John Little [this message]
2006-11-14 20:41 ` multipath and san fabric Edward Goggin
-- strict thread matches above, loose matches on Subject: below --
2006-11-13 16:35 John Little
2006-11-13 19:18 ` James Smart
2006-11-13 19:39 ` Edward Goggin
2006-11-13 19:52 ` Philip R. Auld
2006-11-13 19:54 ` James Smart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200611140809.21110.jslittl@hendricks.org \
--to=jslittl@hendricks.org \
--cc=James.Smart@emulex.com \
--cc=dm-devel@redhat.com \
--cc=egoggin@emc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.