<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic MSA1000 &amp;amp; RHEL4 Connection Issues in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/msa1000-amp-rhel4-connection-issues/m-p/4117085#M31047</link>
    <description>I have a Proliant DL380 running RedHat4.  I also have an HP MSA1000.  I have installed the proliant support pack on the server.  I can see a state of READY and a WWNN for the hba.  All the lights are lit on the connections to the switch.  But the host doesn't show up in the array management tool?  It is my understanding that it should show up automagically?  Or do I need to somehow let the MSA know that the host is out there?  &lt;BR /&gt;&lt;BR /&gt;Any insight would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanx&lt;BR /&gt;&lt;BR /&gt;Brian Pyle</description>
    <pubDate>Fri, 14 Dec 2007 18:34:13 GMT</pubDate>
    <dc:creator>brian.pyle</dc:creator>
    <dc:date>2007-12-14T18:34:13Z</dc:date>
    <item>
      <title>MSA1000 &amp; RHEL4 Connection Issues</title>
      <link>https://community.hpe.com/t5/operating-system-linux/msa1000-amp-rhel4-connection-issues/m-p/4117085#M31047</link>
      <description>I have a Proliant DL380 running RedHat4.  I also have an HP MSA1000.  I have installed the proliant support pack on the server.  I can see a state of READY and a WWNN for the hba.  All the lights are lit on the connections to the switch.  But the host doesn't show up in the array management tool?  It is my understanding that it should show up automagically?  Or do I need to somehow let the MSA know that the host is out there?  &lt;BR /&gt;&lt;BR /&gt;Any insight would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanx&lt;BR /&gt;&lt;BR /&gt;Brian Pyle</description>
      <pubDate>Fri, 14 Dec 2007 18:34:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/msa1000-amp-rhel4-connection-issues/m-p/4117085#M31047</guid>
      <dc:creator>brian.pyle</dc:creator>
      <dc:date>2007-12-14T18:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 &amp; RHEL4 Connection Issues</title>
      <link>https://community.hpe.com/t5/operating-system-linux/msa1000-amp-rhel4-connection-issues/m-p/4117086#M31048</link>
      <description>Shalom Brian,&lt;BR /&gt;&lt;BR /&gt;This can be a little annoying to deal with.&lt;BR /&gt;&lt;BR /&gt;We have a multi-step process for making this work. Here is the crux of the procedure.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;In /etc/modprobe.conf you have an entry like:&lt;BR /&gt;&lt;BR /&gt;alias scsi_hostadapter2 qla2320&lt;BR /&gt;Change it to.&lt;BR /&gt;alias scsi_hostadapter2 qla2400&lt;BR /&gt;cd /boot&lt;BR /&gt;rename your current initrd file (uname -a)to .bck&lt;BR /&gt;mkinitrd -f initrd-$(uname -r).img $(uname -r)&lt;BR /&gt;&lt;BR /&gt;Most likely unless there are other issues these steps will be enough. These steps assume qlogic cards.&lt;BR /&gt;&lt;BR /&gt;Also check the lights on the cards against the manual. Having the lights light may not be enough, the card(s) could still require a hardware visit.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 16 Dec 2007 13:06:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/msa1000-amp-rhel4-connection-issues/m-p/4117086#M31048</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-12-16T13:06:04Z</dc:date>
    </item>
  </channel>
</rss>

