<?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: BL870 HBA connection in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350858#M5018</link>
    <description>Joe,&lt;BR /&gt;&lt;BR /&gt;there is nothing special you should do at the HBA or config level to "ACTIVATE" the FC HBA's.&lt;BR /&gt;&lt;BR /&gt;Do you have server profiles created for the LAN and SAN  and have they been succesfully assigned to the three server blades ?&lt;BR /&gt;&lt;BR /&gt;Any status information available via the VC manager i.e. the external SAN fabric status or any entries in the System Log i.e.&lt;BR /&gt;&lt;BR /&gt;What is the VC FC module uplink connected to and is that link up i.e. ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
    <pubDate>Wed, 04 Feb 2009 08:28:21 GMT</pubDate>
    <dc:creator>kris rombauts</dc:creator>
    <dc:date>2009-02-04T08:28:21Z</dc:date>
    <item>
      <title>BL870 HBA connection</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350857#M5017</link>
      <description>Is there something I have to do to activate the HBA devices on a BL870 ? The c7000 shows that the connections from the VC FC module to the switch are up and active at 2Gb. When I do an ioscan on the BL870 i see the HBA devices:&lt;BR /&gt;Class     I  H/W Path     Driver   S/W State   H/W Type     Description&lt;BR /&gt;========================================================================&lt;BR /&gt;fc        0  0/4/0/0/0/0  fcd      CLAIMED     INTERFACE    HP 4Gb Dual Port PCIe Fibre Channel Mezzanine (FC Port 1)&lt;BR /&gt;                         /dev/fcd0&lt;BR /&gt;fc        1  0/4/0/0/0/1  fcd      CLAIMED     INTERFACE    HP 4Gb Dual Port PCIe Fibre Channel Mezzanine (FC Port 2)&lt;BR /&gt;                         /dev/fcd1&lt;BR /&gt;fc        2  0/5/0/0/0/0  fcd      CLAIMED     INTERFACE    HP 4Gb Dual Port PCIe Fibre Channel Mezzanine (FC Port 1)&lt;BR /&gt;                         /dev/fcd2&lt;BR /&gt;fc        3  0/5/0/0/0/1  fcd      CLAIMED     INTERFACE    HP 4Gb Dual Port PCIe Fibre Channel Mezzanine (FC Port 2)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Using the fcmsutil command it shows&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;  Vendor ID is = 0x001077&lt;BR /&gt;                           Device ID is = 0x002432&lt;BR /&gt;            PCI Sub-system Vendor ID is = 0x00103c&lt;BR /&gt;                   PCI Sub-system ID is = 0x001705&lt;BR /&gt;                               PCI Mode = PCI Express x4&lt;BR /&gt;                       ISP Code version = 4.2.2&lt;BR /&gt;                       ISP Chip version = 2&lt;BR /&gt;                      Previous Topology = UNINITIALIZED&lt;BR /&gt;                             Link Speed = UNKNOWN&lt;BR /&gt;                     Local N_Port_id is = None&lt;BR /&gt;                  Previous N_Port_id is = None&lt;BR /&gt;            N_Port Node World Wide Name = 0x5001438002ae5041&lt;BR /&gt;            N_Port Port World Wide Name = 0x5001438002ae5040&lt;BR /&gt;            Switch Port World Wide Name = 0x0000000000000000&lt;BR /&gt;            Switch Node World Wide Name = 0x0000000000000000&lt;BR /&gt;                           Driver state = AWAITING_LINK_UP&lt;BR /&gt;                       Hardware Path is = 0/4/0/0/0/0&lt;BR /&gt;                     Maximum Frame Size = 2048&lt;BR /&gt;         Driver-Firmware Dump Available = NO&lt;BR /&gt;         Driver-Firmware Dump Timestamp = N/A&lt;BR /&gt;                         Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx &amp;amp; 24xx Driver B.11.23.0803 /ux/core/isu/FCD/kern/src/common/wsio/fcd_init.c:Dec 11 2007,03:23:13&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It's showing topology of uninitialized, no link speed, no local port and status of awaiting_link_up. I have six servers in three enclosures all showing the same status. Is there something that is not configured ?</description>
      <pubDate>Tue, 03 Feb 2009 18:51:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350857#M5017</guid>
      <dc:creator>Joe Camilleri</dc:creator>
      <dc:date>2009-02-03T18:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: BL870 HBA connection</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350858#M5018</link>
      <description>Joe,&lt;BR /&gt;&lt;BR /&gt;there is nothing special you should do at the HBA or config level to "ACTIVATE" the FC HBA's.&lt;BR /&gt;&lt;BR /&gt;Do you have server profiles created for the LAN and SAN  and have they been succesfully assigned to the three server blades ?&lt;BR /&gt;&lt;BR /&gt;Any status information available via the VC manager i.e. the external SAN fabric status or any entries in the System Log i.e.&lt;BR /&gt;&lt;BR /&gt;What is the VC FC module uplink connected to and is that link up i.e. ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Feb 2009 08:28:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350858#M5018</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2009-02-04T08:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: BL870 HBA connection</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350859#M5019</link>
      <description>Thanks Kris. I had checked everything but the server profile. Somehow the FC connections in the server profile were set as unassigned.</description>
      <pubDate>Wed, 04 Feb 2009 13:40:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl870-hba-connection/m-p/4350859#M5019</guid>
      <dc:creator>Joe Camilleri</dc:creator>
      <dc:date>2009-02-04T13:40:45Z</dc:date>
    </item>
  </channel>
</rss>

