<?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 reachability issue to PA FW interface vlan in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/309227#M80156</link>
    <description>&lt;P&gt;there is high-available Paloalto fw PAN-OS 9.0.3-h3 connected to the same switch witch aggregate ethernet interface. interface VLANs created and on the firewall with ip address 10.1.1.1/24 to work as GW for some servers and other interface VLAN as GW for users with ip address 10.1.2.1/24. all thing was working fine and a change was required to make GW on a router that required to change the ip address of the interface vlans after changing the ip address to 10.1.1.88/24 and commit the change is rollbacked and I changed the IP address again to be 10.1.1.1/24.&lt;/P&gt;&lt;P&gt;when checking reachability between servers and FW (ping) it failed for troubleshooting interface vlan created on the switch when ping from fw using source interface 10.1.1.1 to this interface vlan it passed and ping from switch interface vlan to servers it also passed. but from fw to server failed which caused issue between servers and users vlan. when switchover done to passive fw all is working fine.&lt;/P&gt;</description>
    <pubDate>Mon, 03 Feb 2020 19:10:21 GMT</pubDate>
    <dc:creator>Ahmed_Youssef</dc:creator>
    <dc:date>2020-02-03T19:10:21Z</dc:date>
    <item>
      <title>reachability issue to PA FW interface vlan</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/309227#M80156</link>
      <description>&lt;P&gt;there is high-available Paloalto fw PAN-OS 9.0.3-h3 connected to the same switch witch aggregate ethernet interface. interface VLANs created and on the firewall with ip address 10.1.1.1/24 to work as GW for some servers and other interface VLAN as GW for users with ip address 10.1.2.1/24. all thing was working fine and a change was required to make GW on a router that required to change the ip address of the interface vlans after changing the ip address to 10.1.1.88/24 and commit the change is rollbacked and I changed the IP address again to be 10.1.1.1/24.&lt;/P&gt;&lt;P&gt;when checking reachability between servers and FW (ping) it failed for troubleshooting interface vlan created on the switch when ping from fw using source interface 10.1.1.1 to this interface vlan it passed and ping from switch interface vlan to servers it also passed. but from fw to server failed which caused issue between servers and users vlan. when switchover done to passive fw all is working fine.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2020 19:10:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/309227#M80156</guid>
      <dc:creator>Ahmed_Youssef</dc:creator>
      <dc:date>2020-02-03T19:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: reachability issue to PA FW interface vlan</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/310585#M80427</link>
      <description>&lt;P&gt;hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/113201"&gt;@Ahmed_Youssef&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it feels like you're trying to explain too much in too few words, could you break it down into a series of events? that may help in troubleshooting with you &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2020 13:15:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/310585#M80427</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-02-11T13:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: reachability issue to PA FW interface vlan</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/310591#M80430</link>
      <description>&lt;P&gt;Hi Ahemd,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes please explain bit more. Also best to start checking all the configs again there must be something you have overlooked or missed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am sure mgmt profile is attached to the interface and ping is allowed. you can also try traceroute from the problem server and see where it stops.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2020 13:44:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/reachability-issue-to-pa-fw-interface-vlan/m-p/310591#M80430</guid>
      <dc:creator>umar00o</dc:creator>
      <dc:date>2020-02-11T13:44:51Z</dc:date>
    </item>
  </channel>
</rss>

