<?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 Re: FC2/1 LV IP problem in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/fc2-1-lv-ip-problem/m-p/290394#M305</link>
    <description>Firmware upgrade to 3.06 2009h fixes this problem, in case anyone else runs into it.</description>
    <pubDate>Tue, 23 Dec 2003 15:34:04 GMT</pubDate>
    <dc:creator>J. Levy</dc:creator>
    <dc:date>2003-12-23T15:34:04Z</dc:date>
    <item>
      <title>FC2/1 LV IP problem</title>
      <link>https://community.hpe.com/t5/msa-storage/fc2-1-lv-ip-problem/m-p/290393#M304</link>
      <description>Weird IP issue with this bridge (firmware 3.02.2006j). I can manage it on the local subnet but when I try to contact it off-subnet -- via Telnet, Web, or even a ping -- it doesn't respond. Ethernet trace shows that it is ARPing for the destination MAC even though the subnet mask and address indicate the destination is off-net. Has anyone else seen this issue? Thanks...</description>
      <pubDate>Thu, 11 Dec 2003 16:47:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fc2-1-lv-ip-problem/m-p/290393#M304</guid>
      <dc:creator>J. Levy</dc:creator>
      <dc:date>2003-12-11T16:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: FC2/1 LV IP problem</title>
      <link>https://community.hpe.com/t5/msa-storage/fc2-1-lv-ip-problem/m-p/290394#M305</link>
      <description>Firmware upgrade to 3.06 2009h fixes this problem, in case anyone else runs into it.</description>
      <pubDate>Tue, 23 Dec 2003 15:34:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fc2-1-lv-ip-problem/m-p/290394#M305</guid>
      <dc:creator>J. Levy</dc:creator>
      <dc:date>2003-12-23T15:34:04Z</dc:date>
    </item>
  </channel>
</rss>

