<?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: problem with ARP cache? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067827#M572722</link>
    <description>When I snmpwalk mail.milwaukee.tec.wi.us for the arp cache all entries in the cache have the same physical address.&lt;BR /&gt;&lt;BR /&gt;We do have a PIX firewall here, so I'll get with the network team and see what they can find out.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 10 Sep 2003 15:30:47 GMT</pubDate>
    <dc:creator>Sean OB_1</dc:creator>
    <dc:date>2003-09-10T15:30:47Z</dc:date>
    <item>
      <title>problem with ARP cache?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067825#M572720</link>
      <description>Hello.  &lt;BR /&gt;I'm seeing the following messages created in OVO.  From what I understand this trap can result from either a duplicate IP, or a stale ARP cache for a machine that received a new NIC.&lt;BR /&gt;&lt;BR /&gt;I'm concerned that the same MAC address is being reported for many different IP addresses, and the traps are coming from a few different machines.&lt;BR /&gt;&lt;BR /&gt;Any thoughts on what is going on here?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Major  --X---- 19:13:58 09/09/03 webcalendar.matc.edu SNMPTraps SNMP webcalendar.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.32.103, webcalendar.matc.edu reported 0x0002A5EF221B via SNMP &lt;BR /&gt;Major 7 --X--X- 16:46:26 09/09/03 dataware.matc.edu SNMPTraps SNMP dataware.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.32.77, dataware.matc.edu reported 0x080020CFC12B via SNMP &lt;BR /&gt;Major 14 --X--X- 16:46:26 09/09/03 cricket.matc.edu SNMPTraps SNMP cricket.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.32.78, cricket.matc.edu reported 0x080020B085B0 via SNMP &lt;BR /&gt;Major 11 --X--X- 17:01:26 09/09/03 gwise5.matc.edu SNMPTraps SNMP gwise5.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.60.15, gwise5.matc.edu reported 0x000BCD9C61AB via SNMP &lt;BR /&gt;Major 7 --X--X- 19:43:58 09/09/03 mms2.matc.edu SNMPTraps SNMP mms2.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.60.25, mms2.matc.edu reported 0x0002A56B97DA via SNMP &lt;BR /&gt;Major 1 --X--X- 21:13:58 09/09/03 cw2000.matc.edu SNMPTraps SNMP cw2000.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.60.34, cw2000.matc.edu reported 0x0002A5AD47F1 via SNMP &lt;BR /&gt;Major 8 --X--X- 16:16:25 09/09/03 mms1.matc.edu SNMPTraps SNMP mms1.matc.edu mail.milwaukee.tec.wi.us reports address 0x00000C07AC80 for 148.8.60.35, mms1.matc.edu reported 0x0002A56B9CC0 via SNMP &lt;BR /&gt;Major 12 --X--X- 17:01:13 09/09/03 is1.matc.edu SNMPTraps SNMP is1.matc.edu blackboard.matc.edu reports address 0x00000C07AC80 for 148.8.60.122, is1.matc.edu reported 0x0002A55C5DA6 via SNMP &lt;BR /&gt;Major 8 --X--X- 17:16:13 09/09/03 ovis.matc.edu SNMPTraps SNMP ovis.matc.edu blackboard.matc.edu reports address 0x00000C07AC80 for 148.8.60.7, ovis.matc.edu reported 0x000BCD9C3A73 via SNMP &lt;BR /&gt;Major 2 --X--X- 20:47:17 09/09/03 dataware.matc.edu SNMPTraps SNMP dataware.matc.edu blackboard1.matc.edu reports address 0x00000C07AC80 for 148.8.32.77, dataware.matc.edu reported 0x080020CFC12B via SNMP &lt;BR /&gt;</description>
      <pubDate>Wed, 10 Sep 2003 14:01:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067825#M572720</guid>
      <dc:creator>Sean OB_1</dc:creator>
      <dc:date>2003-09-10T14:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: problem with ARP cache?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067826#M572721</link>
      <description>I think its most likely that you have proxy-ARP enabled on a device close to the mail.milwaukee.tec.wi.us system, mainly because of the number of events you're getting and because the mismatch is always with the same layer 2 address (0x00000C07AC80).&lt;BR /&gt;&lt;BR /&gt;Incorrectly configured Cisco PIX firewalls are notorious for responding to ARP request by proxy, so if you have one of these in your network I would start there.  Otherwise you need to locate the device that owns the address 0x00000C07AC80. &lt;BR /&gt;&lt;BR /&gt;I've attached the description text from my trapd.conf file describing some troubleshooting steps that you may or may not have seen.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Steve</description>
      <pubDate>Wed, 10 Sep 2003 14:32:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067826#M572721</guid>
      <dc:creator>Steven Gillard_2</dc:creator>
      <dc:date>2003-09-10T14:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: problem with ARP cache?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067827#M572722</link>
      <description>When I snmpwalk mail.milwaukee.tec.wi.us for the arp cache all entries in the cache have the same physical address.&lt;BR /&gt;&lt;BR /&gt;We do have a PIX firewall here, so I'll get with the network team and see what they can find out.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Sep 2003 15:30:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067827#M572722</guid>
      <dc:creator>Sean OB_1</dc:creator>
      <dc:date>2003-09-10T15:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: problem with ARP cache?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067828#M572723</link>
      <description>The 00000C in the vendor portion of the address indicates that the culprit is a Cisco device so it is probably the Pix or a router which is answering the phone.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.iana.org/assignments/ethernet-numbers" target="_blank"&gt;http://www.iana.org/assignments/ethernet-numbers&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I suspect it's the Pix and that this is the way the Pix works so you may just have to tell OV to ignore this sort of thing.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Thu, 11 Sep 2003 15:58:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/problem-with-arp-cache/m-p/3067828#M572723</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-09-11T15:58:35Z</dc:date>
    </item>
  </channel>
</rss>

