<?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 Strange ARP table in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/strange-arp-table/m-p/4296301#M57163</link>
    <description>Default ARP config on TCP 5.3 eco 2 on VMS 7.3.&lt;BR /&gt;&lt;BR /&gt;I do ucx show arp and find an entry. The timer value of the entry goes up all the time from 1 to 120 (or 119?). I do ucx sho dev for the address : nothing.&lt;BR /&gt;&lt;BR /&gt;The node is not communicating (did tcptrace/prot=ip) but still the arp entry stays. I removed it with arp -d. 10 minutes later it's still not back.&lt;BR /&gt;&lt;BR /&gt;Q1) Why did the entry stay in the arp table ? The flags were UC.&lt;BR /&gt;&lt;BR /&gt;Q2) Why did the arprefresh of 120 was this time in seconds while I found that it's otherwise in minutes ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
    <pubDate>Wed, 29 Oct 2008 12:25:05 GMT</pubDate>
    <dc:creator>Wim Van den Wyngaert</dc:creator>
    <dc:date>2008-10-29T12:25:05Z</dc:date>
    <item>
      <title>Strange ARP table</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-arp-table/m-p/4296301#M57163</link>
      <description>Default ARP config on TCP 5.3 eco 2 on VMS 7.3.&lt;BR /&gt;&lt;BR /&gt;I do ucx show arp and find an entry. The timer value of the entry goes up all the time from 1 to 120 (or 119?). I do ucx sho dev for the address : nothing.&lt;BR /&gt;&lt;BR /&gt;The node is not communicating (did tcptrace/prot=ip) but still the arp entry stays. I removed it with arp -d. 10 minutes later it's still not back.&lt;BR /&gt;&lt;BR /&gt;Q1) Why did the entry stay in the arp table ? The flags were UC.&lt;BR /&gt;&lt;BR /&gt;Q2) Why did the arprefresh of 120 was this time in seconds while I found that it's otherwise in minutes ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 29 Oct 2008 12:25:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-arp-table/m-p/4296301#M57163</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-10-29T12:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: Strange ARP table</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/strange-arp-table/m-p/4296302#M57164</link>
      <description>Stranger. Did another test on another node on which I can play.&lt;BR /&gt;&lt;BR /&gt;It seems that the arprefresh is rounded up to the minute. 1-60 : 60 sec, 61-120 : 120 sec. So 1 means rounded to 60 instead of 1 minute (thus my mistake).&lt;BR /&gt;&lt;BR /&gt;The default router of that node however gets a timout that's bigger (seen 240 - 588) but not always the same patern.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 29 Oct 2008 14:17:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/strange-arp-table/m-p/4296302#M57164</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-10-29T14:17:02Z</dc:date>
    </item>
  </channel>
</rss>

