<?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: Latency on Internal Interface in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194310#M58155</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/45418"&gt;@Farzana&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Just wanted to state that I can't reproduce the issue on either 3020s, 3050s, or 200s all running 8.0.7. Do you have a physical firewall or is this through a VM model?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jan 2018 18:42:04 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2018-01-08T18:42:04Z</dc:date>
    <item>
      <title>Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194224#M58134</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Using PAN-OS 8.0.7. When we ping a trusted interface, we see latency up and down. Any clues?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;root@test-machine:~# ping 10.2.2.100&lt;BR /&gt;PING 10.2.2.100 (10.2.2.100) 56(84) bytes of data.&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=1 ttl=63 time=3.46 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=2 ttl=63 time=1.25 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=3 ttl=63 time=19.9 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=4 ttl=63 time=17.9 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=5 ttl=63 time=18.6 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=6 ttl=63 time=16.6 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=7 ttl=63 time=3.39 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=8 ttl=63 time=2.25 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=9 ttl=63 time=11.5 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=10 ttl=63 time=17.9 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=11 ttl=63 time=9.48 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=12 ttl=63 time=11.3 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=13 ttl=63 time=7.23 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=14 ttl=63 time=14.1 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=15 ttl=63 time=3.14 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=16 ttl=63 time=1.15 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=17 ttl=63 time=9.94 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=18 ttl=63 time=18.0 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=19 ttl=63 time=16.8 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=20 ttl=63 time=14.9 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=21 ttl=63 time=12.5 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=22 ttl=63 time=4.19 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=23 ttl=63 time=1.17 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=24 ttl=63 time=11.1 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=25 ttl=63 time=10.6 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=26 ttl=63 time=8.15 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=27 ttl=63 time=7.21 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=28 ttl=63 time=6.46 ms&lt;BR /&gt;64 bytes from 10.2.2.100: icmp_seq=29 ttl=63 time=2.64 ms&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 03:34:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194224#M58134</guid>
      <dc:creator>Farzana</dc:creator>
      <dc:date>2018-01-08T03:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194260#M58137</link>
      <description>&lt;P&gt;hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/45418"&gt;@Farzana&lt;/a&gt;!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you experiencing slowdowns in packets passing through the firewall, is there packetloss or lots of resends?&lt;/P&gt;
&lt;P&gt;What's the current load on the dataplane?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Pings to the dataplane interface get the lowest possible priority when processing packets, so if your dataplane is under any type of load you may see some latency&lt;/P&gt;
&lt;P&gt;Is there a direct link from your host to the firewall, is there a routing device or a switch in between?&lt;/P&gt;
&lt;P&gt;did you verify the speed and duplex settings of the firewall interface to match what it is connected to?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 09:07:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194260#M58137</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2018-01-08T09:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194308#M58153</link>
      <description>&lt;P&gt;Same "issue" here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This latency when ping the interface adress started after upgrade to&amp;nbsp; PAN 8.0.x&amp;nbsp;&lt;/P&gt;&lt;P&gt;previous versions had only higher latency when the firewall or interace was under high load,&lt;/P&gt;&lt;P&gt;The mgmt interface does not show latency,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Througput and latency when going "through" the device is normal and the same as&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;previous pan-os versions&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Also when dataplane usage is 0 the latency is bouncing between 2 and 12 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 18:58:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194308#M58153</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2018-01-08T18:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194310#M58155</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/45418"&gt;@Farzana&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Just wanted to state that I can't reproduce the issue on either 3020s, 3050s, or 200s all running 8.0.7. Do you have a physical firewall or is this through a VM model?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 18:42:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194310#M58155</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-01-08T18:42:04Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194311#M58156</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;For me its a VM-50 stand alone and VM-100 HA clusters.&lt;/P&gt;&lt;P&gt;All our physical firewall's are still on 7.1.1x&lt;/P&gt;&lt;P&gt;Latency for the interfaces IP's&amp;nbsp; happends on all 8.0.x versions&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 18:47:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194311#M58156</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2018-01-08T18:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194314#M58159</link>
      <description>&lt;P&gt;@Retired Member,&lt;/P&gt;&lt;P&gt;Interesting. Maybe this is actually limited to the VMs and doesn't actually effect hardware units?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 18:48:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194314#M58159</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-01-08T18:48:55Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194316#M58160</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;I think you are right, that is only affect the VM models&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 18:57:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194316#M58160</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2018-01-08T18:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194713#M58229</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just wanted to let you know I have logged a case with TAC regarding the issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So far we have seen that when DPDK is off, latency is dropped. Still checking the issue.&lt;/P&gt;&lt;P&gt;I will update it here.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 22:00:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/194713#M58229</guid>
      <dc:creator>Farzana</dc:creator>
      <dc:date>2018-01-10T22:00:08Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/199389#M59099</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/45418"&gt;@Farzana&lt;/a&gt;&amp;nbsp; Any news on this?&lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2018 17:20:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/199389#M59099</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2018-02-07T17:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: Latency on Internal Interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/199444#M59109</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@Retired Member,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the follow up. TAC asked to perform the following.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Perform ping test and take specific packet capture by filtering only source and destination in both directions for 15 minutes (Kindly note down the time).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;2. Capture output of ethernet1 Interface from ESXi Host at start and end of testing after 15 minutes.&lt;BR /&gt;net-stats -l | grep &amp;lt;Firewall name&amp;gt;&lt;/P&gt;&lt;P&gt;Sample output below&lt;/P&gt;&lt;P&gt;ID Number DVS Port No MAC-Address Interface&lt;BR /&gt;33554978 5 9 DvsPortset-0 00:49:3b:ee:e3:14 FW.eth5&lt;/P&gt;&lt;P&gt;The above output would give port details for the Firewall.&lt;/P&gt;&lt;P&gt;Once port detail is obtained, for eth1 interface run below command:&lt;BR /&gt;cat /net/portsets/&amp;lt;DVS Port No&amp;gt;/ports/&amp;lt;ID Number of eth1&amp;gt;/vmxnet3/rxSummary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Take output of below command after every 5 minutes:&lt;/P&gt;&lt;P&gt;debug dataplane pow performance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, a&lt;SPAN&gt;fter trying the following command latency has dropped to expectancy level. So&amp;nbsp;&lt;/SPAN&gt;our customer did not go ahead with further testing. Case is closed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;admin@PA-VM&amp;gt; show system setting dpdk-pkt-io&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Device current Packet IO mode: DPDK&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Device DPDK Packet IO capable: yes&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Device default Packet IO mode: DPDK&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;admin@PA-VM&amp;gt; set system setting dpdk-pkt-io off&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Enabling/disabling DPDK Packet IO mode requires a device reboot. Do you want to continue? (y or n)&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Device is now in non-DPDK IO mode, please reboot device&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;admin@PA-VM&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2018 21:24:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/latency-on-internal-interface/m-p/199444#M59109</guid>
      <dc:creator>Farzana</dc:creator>
      <dc:date>2018-02-07T21:24:53Z</dc:date>
    </item>
  </channel>
</rss>

