This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Reporting

1. I would like to see a report or an alerting capability when an address changes status from unused to used.

2. I would like the product to be able to interrogate an address to the same level as the switch port mapper in the engineers toolset.

3. The ability to exclude certain ranges within a network from reports. This would be useful in segments where DHCP is being used.

4. It would be nice if it had the ability to integrate with Orion NCM to determine DHCP pools and report on the percentage of the pool being used.

5. The ability to track MAC addresses in a database and report on MAC addresses not previosly seen on the network. The could be useful in situations where sticky macs are not an ideal solution for port security.

  • #1 - we have as an enhancement in the system to alert on this.  If you own APM you can setup a monitor to look for this change on an IP as a workaround currently.

    #2 - So what you are looking for here is the ability to understand which port an IP is using and then the ability to track that over time?  What else beyond that?

    #3 - What types of reports are you looking to create?  Usage reports?  You always have custom SQL to create any type of report against the data in the system

    #4 - Why NCM?  Would you not prefer this to directly communicate with the DHCP Server and pull back stats and report on them?  What DHCP vendor do you use?

    #5 - We do log all events into the IPAM event system, you can see that in the last 250 events report.  You could slim that down to only look at a specific MAC address history in the network.  I like the idea of a MAC not in the network before, alert me on that, good idea.

    These are good comments, please keep them coming.



  • #1 - we have as an enhancement in the system to alert on this.  If you own APM you can setup a monitor to look for this change on an IP as a workaround currently.

    Good to know. Are there instructions for this?

    #2 - So what you are looking for here is the ability to understand which port an IP is using and then the ability to track that over time?  What else beyond that?

    I'm looking for the IPAM module to mark an ip address as used even if ICMP and SNMP fail. Some addresses belong to windows machines with a software firewall blocking these protocols. The only way I know to detect these type of addresses being used is via the arp table on the switch or via NMAP.

    #3 - What types of reports are you looking to create?  Usage reports?  You always have custom SQL to create any type of report against the data in the system

    I would like to run a report of all of the addresses that have changed status but I need to exclude my DHCP ranges. I want to know anytime something new is added to my network or removed.

    #4 - Why NCM?  Would you not prefer this to directly communicate with the DHCP Server and pull back stats and report on them?  What DHCP vendor do you use?

    We enable DHCP on our cisco routers for each of our remote sites. We would like to know if the available address via DHCP are adequate for the number of nodes at the site.

    #5 - We do log all events into the IPAM event system, you can see that in the last 250 events report.  You could slim that down to only look at a specific MAC address history in the network.  I like the idea of a MAC not in the network before, alert me on that, good idea.

    Thanks. Basically I'm looking to track when someone adds a device to my network if i haven't seen its MAC address before.

    These are good comments, please keep them coming.



  • #2 - ah perfect, got it, internally we have been calling that indirect discovery

    #4 - so if we could pull DHCP directly from Cisco devices, then NCM would not need to be apart of the equation then.

    I am looking into getting you more data on 1 and 3

  • #4 I imagine this could be accomplished directly between the IPAM and the Cisco router. The NCM doesn't really need to be a part of it.

  • #1
    Create and HTTP component monitor in APM to monitor the IPAM Summary Page.  If an Event occurs for an IP change you can alert off of the keywords showing up under the IPAM events such as “Changed” or "added".  You will then create an alert for the APM component. in the Advanced Alert Engine.
     
    3/30/2009 6:03 PM
    ADMIN
    The group 'Austin Dev' has been added
     
    3/30/2009 6:01 PM
    ADMIN
    The group 'Europe' has been added
     
    3/30/2009 5:54 PM
    ADMIN
    The group 'Austin Lab' has been added
     
    3/30/2009 5:45 PM
    ADMIN
    The group 'Asia Pacific' has been added
     
    3/30/2009 12:56 PM
    ADMIN
    The custom field 'Purpose' has been added
     
    3/27/2009 2:00 PM
    ADMIN
    The custom field 'Custom_1' has been removed
     
    3/27/2009 2:00 PM
    ADMIN
    The custom field 'Custom_1' has been added
     
    3/25/2009 5:55 PM
    SYSTEM
    The scanning of '10.199.2.0 / 24' started at 3/25/2009 4:54:08 PM has been finished successfully. 14 IP(s) have been found. The scan duration was '0.8' minutes
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.229' fields have been changed :Status to 'Used'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.232' fields have been changed :Status to 'Used'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.238' fields have been changed :Status to 'Used'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.240' fields have been changed :Status to 'Used'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.242' fields have been changed :DNS to 'LAB-VM04-2K3-05.lab.tex', Status to 'Used'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.22' fields have been changed :Last Boot to '2/27/2009 8:48:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.10' fields have been changed :System Location to 'Tokyo1'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.2.11' fields have been changed :Last Boot to '3/24/2009 12:23:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The scanning of '10.199.1.0 / 24' started at 3/25/2009 4:54:08 PM has been finished successfully. 51 IP(s) have been found. The scan duration was '0.8' minutes
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.1.27' fields have been changed :Last Boot to '10/23/2008 10:11:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.1.116' fields have been changed :Last Boot to '3/20/2009 4:58:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.1.150' fields have been changed :Last Boot to '3/25/2009 2:23:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.1.151' fields have been changed :Last Boot to '3/25/2009 2:31:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.1.153' fields have been changed :Last Boot to '3/25/2009 2:08:00 PM'
     
    3/25/2009 5:55 PM
    SYSTEM
    The IP '10.199.1.20' fields have been changed :Status to 'Used'
     
    3/25/2009 5:52 PM
    SYSTEM
    The scanning of '10.199.6.0 / 24' started at 3/25/2009 4:51:43 PM has been finished successfully. 8 IP(s) have been found. The scan duration was '0.5' minutes
     
    3/25/2009 5:52 PM
    SYSTEM
    The IP '10.199.6.13' fields have been changed :Last Boot to '2/23/2009 12:15:00 PM'