<?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: DL380p-Gen8: correlate physical port to windows server 2012 device information in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl380p-gen8-correlate-physical-port-to-windows-server-2012/m-p/6638238#M145168</link>
    <description>&lt;P&gt;I've always had this problem too... trying to figure out how the Windows NIC assignments correlate with the physical NIC ports.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's important to me because I run each of our production servers to diverse switches for redunancy... knowing which NIC in Windows goes to which switch matters for monitoring, balancing loads, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My best guess is to look at the MAC address. &amp;nbsp;I *think* that HP assigns the lowest MAC address to the port labeled #1 on the back, and they go up from there. &amp;nbsp;But I don't know that for sure.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's kind of a goofy solution but sometimes I"ll unplug each port and see which NIC says it was disconnected in Windows, then I rename each one to LAN #1 through LAN #4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hate that there's no actual link between the port #'s on the back and what Windows shows. &amp;nbsp;It's been a pain for me since day one, but it's not just HP, it's any system with multi-port network cards. &amp;nbsp;Windows seems to do it randomly. &amp;nbsp;You could do the same install on the same system twice and it would match them up differently each time I think. LOL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe not... maybe there's some method based on the vendor ID substrings, but it bugs me.&lt;/P&gt;</description>
    <pubDate>Fri, 03 Oct 2014 23:35:55 GMT</pubDate>
    <dc:creator>waaronb</dc:creator>
    <dc:date>2014-10-03T23:35:55Z</dc:date>
    <item>
      <title>DL380p-Gen8: correlate physical port to windows server 2012 device information</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl380p-gen8-correlate-physical-port-to-windows-server-2012/m-p/6636748#M145135</link>
      <description>&lt;P&gt;Hi Folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;a customer in another country has a DL380p-Gen8 which has a 4-port Ethernet controller, the Broadcom 331FLR.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to the&amp;nbsp; "Device Manager", the ports have the following properties:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;Adapter  PCI-Bus  Device  Function
-------  -------  ------  --------
(blank)  3        0       2
#2       3        0       0
#3       3        0       3
#4       3        0       1&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to tell someone exactly which port on the back to stick a cable into. How can I correlate the controller to a particular physical slot, looking at the system from the rear, and how can I correlate the adapter numbers to the physical ports on the card?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;</description>
      <pubDate>Wed, 01 Oct 2014 20:17:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl380p-gen8-correlate-physical-port-to-windows-server-2012/m-p/6636748#M145135</guid>
      <dc:creator>Rob Urban</dc:creator>
      <dc:date>2014-10-01T20:17:26Z</dc:date>
    </item>
    <item>
      <title>Re: DL380p-Gen8: correlate physical port to windows server 2012 device information</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl380p-gen8-correlate-physical-port-to-windows-server-2012/m-p/6638238#M145168</link>
      <description>&lt;P&gt;I've always had this problem too... trying to figure out how the Windows NIC assignments correlate with the physical NIC ports.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's important to me because I run each of our production servers to diverse switches for redunancy... knowing which NIC in Windows goes to which switch matters for monitoring, balancing loads, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My best guess is to look at the MAC address. &amp;nbsp;I *think* that HP assigns the lowest MAC address to the port labeled #1 on the back, and they go up from there. &amp;nbsp;But I don't know that for sure.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's kind of a goofy solution but sometimes I"ll unplug each port and see which NIC says it was disconnected in Windows, then I rename each one to LAN #1 through LAN #4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hate that there's no actual link between the port #'s on the back and what Windows shows. &amp;nbsp;It's been a pain for me since day one, but it's not just HP, it's any system with multi-port network cards. &amp;nbsp;Windows seems to do it randomly. &amp;nbsp;You could do the same install on the same system twice and it would match them up differently each time I think. LOL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe not... maybe there's some method based on the vendor ID substrings, but it bugs me.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Oct 2014 23:35:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl380p-gen8-correlate-physical-port-to-windows-server-2012/m-p/6638238#M145168</guid>
      <dc:creator>waaronb</dc:creator>
      <dc:date>2014-10-03T23:35:55Z</dc:date>
    </item>
  </channel>
</rss>

