<?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: No MAC address showing in redundant team NIC in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315832#M85953</link>
    <description>When a team is created, TCP/IP stack will be bound to the team, it will take the MAC address of the first NIC by default, for the rest of the network it will be seen as a single NIC, just 1 MAC address can be used, the other port will reaming on standby mode till the acutal NIC fails, then the MAC address will be bound to the other port.</description>
    <pubDate>Tue, 02 Dec 2008 13:26:28 GMT</pubDate>
    <dc:creator>Lmm_1</dc:creator>
    <dc:date>2008-12-02T13:26:28Z</dc:date>
    <item>
      <title>No MAC address showing in redundant team NIC</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315830#M85951</link>
      <description>Hi,&lt;BR /&gt; All our servers are currently configured with a "Fault Tolerent" team. when I get a report of active network ports from the network team none of the ports with the failover NIC connected show up as having a MAC address, is this normal functionality? if so is there a way to force the redundant NIC to show it's MAC address?</description>
      <pubDate>Mon, 01 Dec 2008 12:51:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315830#M85951</guid>
      <dc:creator>DaveSheeran</dc:creator>
      <dc:date>2008-12-01T12:51:44Z</dc:date>
    </item>
    <item>
      <title>Re: No MAC address showing in redundant team NIC</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315831#M85952</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;As the Team is built on the principal that it should appear as one NIC only one of the NICs in the team can present it self with the "virtual" MAC adress the Team is assigned.&lt;BR /&gt;&lt;BR /&gt;If this logic is completly correct it would be impossible to force the redundant NIC to show the MAC adress as it is shared between NICS in the team and would make your network infrastructure go crazy and not knowing where to send the IP packages...</description>
      <pubDate>Tue, 02 Dec 2008 12:11:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315831#M85952</guid>
      <dc:creator>Cederberg</dc:creator>
      <dc:date>2008-12-02T12:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: No MAC address showing in redundant team NIC</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315832#M85953</link>
      <description>When a team is created, TCP/IP stack will be bound to the team, it will take the MAC address of the first NIC by default, for the rest of the network it will be seen as a single NIC, just 1 MAC address can be used, the other port will reaming on standby mode till the acutal NIC fails, then the MAC address will be bound to the other port.</description>
      <pubDate>Tue, 02 Dec 2008 13:26:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315832#M85953</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2008-12-02T13:26:28Z</dc:date>
    </item>
    <item>
      <title>Re: No MAC address showing in redundant team NIC</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315833#M85954</link>
      <description>Firstly, thanks for the replies. Is it not the case when setup in failover only mode that the "spare" NIC has a different MAC address and that when a failover occurs then the 2 NICs swap MAC addresses?</description>
      <pubDate>Tue, 02 Dec 2008 16:42:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315833#M85954</guid>
      <dc:creator>DaveSheeran</dc:creator>
      <dc:date>2008-12-02T16:42:24Z</dc:date>
    </item>
    <item>
      <title>Re: No MAC address showing in redundant team NIC</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315834#M85955</link>
      <description>The MAC address actually belongs to the team, there is no need for the physical NIC to swap MAC address.</description>
      <pubDate>Tue, 02 Dec 2008 17:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315834#M85955</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2008-12-02T17:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: No MAC address showing in redundant team NIC</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315835#M85956</link>
      <description>This is how i understood it to work and it explains why networks ports are having problems as they are set to auto-disable after a certain time when no device is connected, so the port the failover NIC is connected to is disableing it's self. thanks again for the info.</description>
      <pubDate>Tue, 02 Dec 2008 18:21:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/no-mac-address-showing-in-redundant-team-nic/m-p/4315835#M85956</guid>
      <dc:creator>DaveSheeran</dc:creator>
      <dc:date>2008-12-02T18:21:47Z</dc:date>
    </item>
  </channel>
</rss>

