All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Gregory <dan.gregory@mci.com>
To: dm-devel@redhat.com
Subject: Multipathing to a LUN through brocade switch
Date: Mon, 09 Jan 2006 14:49:14 -0500	[thread overview]
Message-ID: <43C2BE3A.8030309@mci.com> (raw)

Hullo,

I know this list has handle many issues of users not knowing how to
setup multipathing, but I've read all of them and Christophe's wiki and
I can't get my system to talk to my storage array.

OS: RHEL 4.2, device-mapper-multipath-0.4.5-6.0.RHEL4

Configuration:  I have a SunFire 4100 with one 2 port qla hba pci card
dual connected to a single 16 port brocade silkworm which in turn in
dual connected to a Sun StorEdge 3511.  Interestingly, I get 4
/dev/sd[c-f] associated with the same LUN.  I presume that each device
can see the LUN through each of the 2 connections from the switch to the
3511.

I know that mapper is working because there are 2 devices that the LVM
creates, one for / and one for swap, but the LUNs don't show up.
multipath -v2  does not give any output, but -v3 gives information on
all 6 of the sd[a-f] devices.  The only differences in the output of
sd[c-f] are dev_t and h:b:t:l fields (see below).  I've tried to add
entries into the multipath.conf file, but nothing changes the output and
I never get any more devices in /dev/mapper.

What am I doing wrong?


Thanks,
Dan



(I diffed the sections in the multipath -v3 output)

< ===== path sdc =====
---
> ===== path sdf =====
3c3
< dev_t = 8:32
---
> dev_t = 8:80
8c8
< h:b:t:l = 1:0:0:0
---
> h:b:t:l = 2:0:1:0
17,18c17
< path sdd not found in pathvec
<
---
> path sdg not found in pathvec

             reply	other threads:[~2006-01-09 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 19:49 Dan Gregory [this message]
2006-01-11 21:43 ` Multipathing to a LUN through brocade switch Dan Gregory

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=43C2BE3A.8030309@mci.com \
    --to=dan.gregory@mci.com \
    --cc=dm-devel@redhat.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.