Forum Discussion

Lilly_Tizian's avatar
2 years ago

Cisco Network Interface ARP information

Hi Community,

wanted to check if anyone had already build something in this direction or to get some additional guidance on how to best realize this.

Our company is currently in the process of implementing LogicMonitor to monitor our Network equipment - we already on-boarded all of our network devices and started to grant access to additional groups.
We´ve been asked now if there is a way to show the MAC and IP-address currently been connected to a switch port. Doesnt really matter where we would display that data but having them per switch would be the goal. The data doesnt need to be live a snapshot per day would be good enough. We are Cisco shop and unfortunately i havent figured out an easy way to do this.

One challenge is that the IP information are not available on L2 Switches - granted we are able to pull in Port and MAC address information into LM, is there a way to identify the next Core/Distro (L3) Switch to pull the IP address information and add them to the existing information? This would probably require some advanced scripting running comands in the CLI while exporting and merging the results.

Also for the pulling of information for the Interface and MAC address i am currently struggling. Is it easier to create a ConfigSource which would display differences and we would try to adjust the existing iOS config pulls to run with the required comands to show MAC and port or try to achieve via Datasource and SNMP. Eitherway it seems we would need to format the MAC output from Cisco to Windows format (dot to colon/dash notation).

Anyone out there with similar challenges who might´ve figured it out maybe even partially? Every idea and input is appreciated.

  • You *might* be able to do this with a Topology source it would not be simple to do though

  • Anonymous's avatar
    Anonymous

    Just do a configsource. Log into the device, issue the appropriate commands to gather the data, then output in a text format that is easy to consume. Then you just go to the configsource and look at the most recent version. This has the added benefit of being able to maintain a history of the connections to each switch port.