Welcome to Netcordia Connection Sign in | Join | Help
in Search

FindIT - Devices where ARP table is on the firewall

Last post 08-13-2008 11:40 AM by keitzmann. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 12-17-2007 1:28 PM

    FindIT - Devices where ARP table is on the firewall

    I'm noticing that any device that sits behind a routed-mode firewall NetMRI will not identify it in a search.  The ARP table of the firewall has the IP addresses....not the router connected to the switch.  Is there any way that netMRI can poll those arp tables and be able to to coorleate the ARP table ont he firewall (to get the mac) and the mac-address-table on the switch to identify the port

    BB

  • 07-17-2008 11:05 PM In reply to

    • keitzmann
    • Top 25 Contributor
    • Joined on 05-16-2008
    • Lincoln, Nebraska

    Re: FindIT - Devices where ARP table is on the firewall

    If your talking about Cisco firewalls, NetMRI can't currently do this. I have been told that this is going to addressed in a 2.4.2 patch but there is no time frame for the release. Here is the internal tracking number for this issue

     US822 - NetMRI not collecting Firewall Route and ARP Tables via CLI

  • 08-13-2008 9:34 AM In reply to

    Re: FindIT - Devices where ARP table is on the firewall

     2.4.2 is available now -- does NetMRI now handle your request appropriately/as expected?

    Nick Sanders
    Sr. Systems Engineer
    Netcordia, Inc.
    --------------------------------
    No trees were harmed in the transmission of this message; however, a tremendous number of electrons were extremely inconvenienced.
  • 08-13-2008 10:30 AM In reply to

    Re: FindIT - Devices where ARP table is on the firewall

     I installed 2.4.2 and it's not working for me.  I'll open a support ticket to see what's going on.

    B

  • 08-13-2008 11:40 AM In reply to

    • keitzmann
    • Top 25 Contributor
    • Joined on 05-16-2008
    • Lincoln, Nebraska

    Re: FindIT - Devices where ARP table is on the firewall

     I just wanted to add that upgrading to 2.4.2.34 resolved this issue for me.

Page 1 of 1 (5 items)