attaching the hosts to the SAN

[Mad Unix]

Thanks again for your help Haralad from DELL  and Matthew too,
I think I am now able to attach the SAN to my Linux server.
I have done the following

No additonal driver installed for the HBA's, I have just rebooted all the
SAN and servers

[root at linux1 ~]# uname -a
Linux 2.6.18-8.el5xen #1 SMP Fri Jan 26 14:29:35 EST 2007 x86_64 x86_64
x86_64 GNU/Linux

[root at linux1 ~]# rpm -aq | grep multi  (from the RHEL 5 DVD)
device-mapper-multipath-0.4.7-8.el5

in the multi path config file i made the following moldification

 Blacklist all devices by default. Remove this to enable multipathing
# on the default devices.
#blacklist {
 #       devnode "*"
#}

## By default, devices with vendor = "IBM" and product = "S/390.*" are
## blacklisted. To enable mulitpathing on these devies, uncomment the
## following lines.
#blacklist_exceptions {
#       device {
#               vendor  "IBM"
#               product "S/390.*"
#       }
#}

## Use user friendly names, instead of using WWIDs as names.
defaults {
        user_friendly_names yes
}
##
## This is a template multipath-tools configuration file
## Uncomment the lines relevent to your environment
##
#defaults {
        udev_dir                /dev
        polling_interval        10
        selector                "round-robin 0"
        path_grouping_policy    multibus
        getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
        prio_callout            /bin/true
        path_checker            readsector0
        rr_min_io               100
        rr_weight               priorities
        failback                immediate
        no_path_retry           fail
        user_friendly_name      yes
}

[root at linux1 ~]# service multipathd restart
Stopping multipathd daemon: [  OK  ]
Starting multipathd daemon: [  OK  ]


[root at linux1 ~]# multipath -v1 -ll
mpath1
[root at linux1 ~]# multipath -v2 -ll
mpath1 (360060160ddd01d00dc2348c90187dc11) dm-2 DGC,RAID 5
[size=50G][features=1 queue_if_no_path][hwhandler=1 emc]
\_ round-robin 0 [prio=2][enabled]
 \_ 1:0:0:0 sdb 8:16  [active][ready]
 \_ 2:0:0:0 sdd 8:48  [active][ready]
\_ round-robin 0 [prio=0][enabled]
 \_ 1:0:1:0 sdc 8:32  [active][ready]
 \_ 2:0:1:0 sde 8:64  [active][ready]
[root at linux1 ~]# fdisk -l

Disk /dev/sda: 72.7 GB, 72746008576 bytes
255 heads, 63 sectors/track, 8844 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           5       40131   de  Dell Utility
/dev/sda2   *           6        1543    12353985   83  Linux
/dev/sda3            1544        1556      104422+  83  Linux
/dev/sda4            1557        8844    58540860    5  Extended
/dev/sda5            1557        8844    58540828+  8e  Linux LVM

Disk /dev/sdb: 53.6 GB, 53687091200 bytes
64 heads, 32 sectors/track, 51200 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdd: 53.6 GB, 53687091200 bytes
64 heads, 32 sectors/track, 51200 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/dm-2: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-2 doesn't contain a valid partition table
when I finish the setup i ll report it back

On 10/31/07, Matthew Geier <matthew at acfr.usyd.edu.au> wrote:
>
> Kristoffer Knigga wrote:
> > Why can't you use Powerpath?  A technical reason or something else?
> >
> > We don't use the exact setup you do, but when I do this I get regular
> > SCSI disk devices (/dev/sdx) that show up for each path to each LUN.
>
>
> You don't need Powerpath, but you do need (or at least it makes it a
> LOT easier) if you have the EMC host agent installed.
>
> I had a RHEL cluster connected to a CX300, where we had the host agent
> installed but used multipathd to do the multi-path fail over, not
> PowerPath.
>
> The host agent talks to the array so that you get host names in the
> Navisphere manager program and feedback on what device names the LUNS
> get allocated back on the host.
>
> If you don't use the host agent you have to work out what the WWNs are
> of your FC interfaces manually and associate the LUNS with the hosts by
> the WWN instead of the host name.
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>



-- 
madunix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20071102/0b0caea7/attachment-0001.htm