<?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: Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6950098#M156869</link>
    <description>&lt;P&gt;I asked a colleague what driver loads on the ML10 Gen9 and here is the output from RHEL 7.3 ethtool. Hopethis helps&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ML10-Nic-7.3.jpg" style="width: 400px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/92641i06D0056E3D82E04E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ML10-Nic-7.3.jpg" alt="ML10-Nic-7.3.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 21 Mar 2017 16:49:10 GMT</pubDate>
    <dc:creator>Jimmy Vance</dc:creator>
    <dc:date>2017-03-21T16:49:10Z</dc:date>
    <item>
      <title>Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946339#M156677</link>
      <description>&lt;P&gt;Trying to setup a HPE ProLient MS10 Gen 9 system.&amp;nbsp; The &lt;STRONG&gt;AMI Aptio (UEFI) Setup Utility&lt;/STRONG&gt;, v2.17.1254, is configured as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Advanced&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;Network Stack Configuration (UEFI)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;STRONG&gt;disabled&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;enabled (Preboot Execution Environment&amp;nbsp; - &lt;EM&gt;followingnot optioned if disabled&lt;/EM&gt;)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Ipv4 PXE support (enable/disable)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Ipv6 PXE support (enable/disable)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;PXE boot wait time&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Media detect count&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;CMS Configuration (Compatibility Support Module Configuration)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;CMS Support (&lt;STRONG&gt;enable&lt;/STRONG&gt;/disable)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;CMS16 module version 07.79 (static)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Boot option filter&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;&amp;nbsp;Legacy only&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;UEIF only&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;WHEA (Windows Hardware Error Architecture Support) &lt;STRONG&gt;disabled&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;CPU configuration (many options here)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Hyper-threading &lt;STRONG&gt;disabled&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;OS is FreeBSD v10.1 (and previous versions). . .have been working for 15 years+ on &lt;STRONG&gt;BIOS&lt;/STRONG&gt; booting system.&amp;nbsp; OS &lt;U&gt;does&lt;/U&gt; boot under &lt;STRONG&gt;CMS legacy&lt;/STRONG&gt; mode.&amp;nbsp; Problem is &lt;STRONG&gt;ifconfig&lt;/STRONG&gt; (FreeBSD &lt;EM&gt;command line utility&lt;/EM&gt;)does &lt;STRONG&gt;&lt;U&gt;NOT&lt;/U&gt;&lt;/STRONG&gt; recognize and/or report the onboard NIC.&amp;nbsp; All services that require ethernet interface will not/can not communicate via the NIC -- &lt;U&gt;no&lt;/U&gt; DNS, NTP, SMTP/POP3,&amp;nbsp; SSH, etc.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have read from other HP web pages that this is because a "driver" is not installed.&amp;nbsp;&amp;nbsp; Well, Drivers are installed in the FreeBSD kernel, so where else should such a dirver be installed?&amp;nbsp;&amp;nbsp; AMI is no help . . ."not &lt;EM&gt;my&lt;/EM&gt; problem, contact HP".&amp;nbsp; HP is virtually impossible to contact.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;System is unsuable.&amp;nbsp; What to do?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 00:36:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946339#M156677</guid>
      <dc:creator>rtwingfieldaven</dc:creator>
      <dc:date>2017-03-08T00:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946357#M156678</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1802013"&gt;@rtwingfieldaven&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;I have read from other HP web pages that this is because a "driver" is not installed.&amp;nbsp;&amp;nbsp; Well, Drivers are installed in the FreeBSD kernel, so where else should such a dirver be installed?&amp;nbsp;&amp;nbsp; AMI is no help . . ."not &lt;EM&gt;my&lt;/EM&gt; problem, contact HP".&amp;nbsp; HP is virtually impossible to contact.&amp;nbsp;&lt;/P&gt;&lt;P&gt;System is unsuable.&amp;nbsp; What to do?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The kernel may have drivers, but it would appear that the kernel does not have a driver that recognizes the PCI ID of this NIC. If there isn't an updated driver for FreeBSD your only option is to try and get the source and compile a driver yourself, or install an additional NIC that works with FreeBSD&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 03:07:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946357#M156678</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2017-03-08T03:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946615#M156683</link>
      <description>&lt;P&gt;Apparently, HP product documentation does not identify the on-board NIC. On another "&lt;I&gt;web-help&lt;/I&gt;" site post, I have read, "&lt;I&gt;It's an embedded NC105i PCI Express Gigabit Ethernet Server Adapter as HP calls it. Around the internet people identify it as a Broadcom BCM5722 card&lt;/I&gt;.", but I don't know for sure. It is not an actual physical PCIe card, but rather an on-board embedded chip system.&lt;/P&gt;&lt;P&gt;Can you tell me what the "&lt;EM&gt;NIC&lt;/EM&gt;" is on-board the HPE ProLiant ML10 GEN9 . . .is?&amp;nbsp;&amp;nbsp; . . .so I can load an appropriate driver.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 17:41:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946615#M156683</guid>
      <dc:creator>rtwingfieldaven</dc:creator>
      <dc:date>2017-03-08T17:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946627#M156685</link>
      <description>&lt;P&gt;According to the Quickspecs it is an Intel® Ethernet Connection I219-LM&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.hpe.com/h20195/V2/Getdocument.aspx?docname=c04922941" target="_blank"&gt;https://www.hpe.com/h20195/V2/Getdocument.aspx?docname=c04922941&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 18:34:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6946627#M156685</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2017-03-08T18:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6949243#M156817</link>
      <description>&lt;P&gt;Never been able to find (recognize)&amp;nbsp; and use the on-board NIC . . .so have installed (tried) two different PCIe NIC's, &lt;EM&gt;Rosewill (Realtek)&lt;/EM&gt;, and an &lt;EM&gt;Intel&lt;/EM&gt; brand.&amp;nbsp; OS (FreeBSD v10.1) can then see either of the devices.&amp;nbsp;&amp;nbsp; The &lt;STRONG&gt;ifconfig&lt;/STRONG&gt; display and &lt;STRONG&gt;netstat&lt;/STRONG&gt; status looks correct, but cannot interface with other public addresses on the WAN.&amp;nbsp; Cannot ping or otherwise communicate with other servers on the LAN or WAN.&amp;nbsp; Very disappointed with the limited options of the AMI "&lt;EM&gt;bios&lt;/EM&gt;", and the HP product in general.&amp;nbsp; Seems that there is something &lt;EM&gt;firewall-like &lt;/EM&gt;inside the ProLiant ML10 box that is choking the system.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Mar 2017 15:35:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6949243#M156817</guid>
      <dc:creator>rtwingfieldaven</dc:creator>
      <dc:date>2017-03-18T15:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to setup a HPE ProLient MS10 Gen 9 system.  -- NIC failing</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6950098#M156869</link>
      <description>&lt;P&gt;I asked a colleague what driver loads on the ML10 Gen9 and here is the output from RHEL 7.3 ethtool. Hopethis helps&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ML10-Nic-7.3.jpg" style="width: 400px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/92641i06D0056E3D82E04E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ML10-Nic-7.3.jpg" alt="ML10-Nic-7.3.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 16:49:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/trying-to-setup-a-hpe-prolient-ms10-gen-9-system-nic-failing/m-p/6950098#M156869</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2017-03-21T16:49:10Z</dc:date>
    </item>
  </channel>
</rss>

