<?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: mac address learning  of actual physical port on lacp in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251380#M71489</link>
    <description>&lt;P&gt;it only shows mac address of switch chassis not actual switch interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Feb 2019 15:49:43 GMT</pubDate>
    <dc:creator>MP18</dc:creator>
    <dc:date>2019-02-26T15:49:43Z</dc:date>
    <item>
      <title>mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/250924#M71356</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have LACP&amp;nbsp; aggregate connection to the switch.&lt;/P&gt;&lt;P&gt;is there any way i can learn the mac address of the switch port itself on the PA ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now PA only shows me mac address of chassis of the switch.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Feb 2019 15:54:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/250924#M71356</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-02-22T15:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251152#M71418</link>
      <description>&lt;P&gt;I may be misunderstanding the question, but isn't the firewall just learning the mac to the relevant IP addresses it is communicating with. unless the switch ports have an IP associated to it and performing L3 functions, the firewall wouldn't need to know their mac&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2019 12:43:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251152#M71418</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2019-02-25T12:43:27Z</dc:date>
    </item>
    <item>
      <title>Re: mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251182#M71429</link>
      <description>&lt;P&gt;we have point to point link with switch&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;show lacp aggregate-ethernet ae3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;LACP:&lt;/P&gt;&lt;P&gt;**********************************************************************************&lt;BR /&gt;AE group: ae3&lt;BR /&gt;Members: Bndl Rx state Mux state Sel state&lt;BR /&gt;ethernet1/18 yes Current Tx_Rx Selected&lt;BR /&gt;ethernet1/17 yes Current Tx_Rx Selected&lt;BR /&gt;Status: Enabled&lt;BR /&gt;Mode: Passive&lt;BR /&gt;Rate: Slow&lt;BR /&gt;Max-port: 8&lt;BR /&gt;Fast-failover: Disabled&lt;BR /&gt;Pre-negotiation: Disabled&lt;BR /&gt;Local: System Priority: 32768&lt;BR /&gt;System MAC: 00:86:9c:37:58:01&lt;BR /&gt;Key: 18&lt;BR /&gt;Partner: System Priority: 0&lt;BR /&gt;System MAC: e8:e7:32:51:0e:40&lt;BR /&gt;Key: 1&lt;BR /&gt;Port State&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;Interface Port&lt;BR /&gt;Number Priority Mode Rate Key State&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;ethernet1/18 81 32768 Passive Slow 18 0x3C&lt;BR /&gt;Partner 1024 0 Active Fast 1 0x3F&lt;/P&gt;&lt;P&gt;ethernet1/17 80 32768 Passive Slow 18 0x3C&lt;BR /&gt;Partner 1088 0 Active Fast 1 0x3F&lt;/P&gt;&lt;P&gt;Port Counters&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;Interface LACPDUs Marker Marker Response Error&lt;BR /&gt;Sent Recv Sent Recv Sent Recv Unknown Illegal&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;ethernet1/18 316426 10549 0 0 0 0 0 0&lt;BR /&gt;ethernet1/17 316441 10550 0 0 0 0 0 0&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 04:30:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251182#M71429</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-02-26T04:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251292#M71450</link>
      <description>&lt;P&gt;in our setup switch port has layer 3 IP address.&lt;/P&gt;&lt;P&gt;Yes you got it right i mean to say exactly what you said below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;isn't the firewall just learning the mac to the relevant IP addresses it is communicating with&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 04:35:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251292#M71450</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-02-26T04:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251366#M71482</link>
      <description>&lt;P&gt;have you tried &amp;gt; show arp all&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 14:51:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251366#M71482</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2019-02-26T14:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251380#M71489</link>
      <description>&lt;P&gt;it only shows mac address of switch chassis not actual switch interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 15:49:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251380#M71489</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-02-26T15:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: mac address learning  of actual physical port on lacp</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251861#M71616</link>
      <description>&lt;P&gt;is that default behaviour?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 04:46:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/mac-address-learning-of-actual-physical-port-on-lacp/m-p/251861#M71616</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2019-03-01T04:46:09Z</dc:date>
    </item>
  </channel>
</rss>

