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.

What we are working on for UDT

UDT 2.0 has been available since the end of last year. Since then, we have been hard at work for expanding the wireless support in UDT. Currently, UDT can collect information from autonomous or standalone access points. However, since most users have controller based environments, UDT doesn't provide detailed views about what thin AP the user is connected to or what SSID they are associated with. In addition to adding the wireless information, we are also focused on improving the performance for larger customers.

PLEASE NOTE:  We are working on these items based on this priority order, but this is NOT a commitment that all of these enhancements will make the next release.  We are working on a number of other smaller features in parallel.   If you have comments or questions on any of these items (e.g. how would it work?) or would like to be included in a preview demo, please let us know!

Mav

  • Great improvement!

    We have both Cisco and Aruba Wireless Controllers. And also some Cisco Standalone (Autonomous) APs. Which brands are you going to support on the vNext?

  • What you need to do next is to support dynamic updates from access switches.


    UDT would be able to alert us when a port becomes active. Thus allowing us to pinpoint possible rouge clients or internal threats.  We would have bought the product on the spot if this feature was available.  -taken from a user comment to UDT 1.01 RC.


    Taken from Cisco's User Tracking Utility's definition:

    In addition to polling the network at regular intervals, UTU tracks changes in the end hosts and users on the network to provide real-time updates. Dynamic Updates are asynchronous updates that are based on SNMP MAC notifications traps.

    When an endhost is connected to a switch managed by LMS, an SNMP MAC notification trap is sent immediately from the switch to the LMS Server, indicating an ADD event. This trap contains the MAC address of the end host connected to the switch.

    Similarly if an end host is disconnected from a switchport, an SNMP MAC notification trap is sent from the switch to the LMS indicating a DELETE event. Thus LMS provides real time data about end hosts coming into and moving out of the network.

    Traps from suspended devices are not processed by LMS.

    The difference between a UTMajor Acquisition and a Dynamic UT process is:

    LMS collects data from the network at regular intervals for UTMajor Acquisition. In Dynamic UT, the devices send traps to LMS as and when changes happen in the network.

    This implies that you need not wait till next UTMajor Acquisition cycle to see the changes that have happened in your network. This is an improvement over the earlier versions, where updates on endhost information happened based on the polling cycle.

    As a result of Dynamic updates, the following reports contain up-to-date information:

    • End-Host Report : Contains information from UT Major Acquisition and the recently added end-hosts.

    • History Report: Contains information from UT Major Acquisition and the recently disconnected end-hosts or end-hosts that have moved between ports or VLANs.

    • Switch Port reports: Contains information about the utilization of switch ports.

    SNMP Traps are generated when a host is connected to the network, disconnected from the network or when it moves between VLANs or ports in the network.

    .....

    And I have one more request along with the dynamic update. Please make a UDT Search Band like UTU Search Band. In our environment nobody wants to use web for this. They like Cisco UTU 2.0.

  • My company will not approve us purchasing UDT until the wireless controllers are supported.  We currently have 70+ controllers with plans for over 100...

    Many devices connect via thin AP's and the location is VERY important.

    Hope it comes soon....

    Thanks!!!

  • We have Cisco and Aruba controllers. We are waiting for this too.

  • Most of our network uses firewalls as layer 3 gateways. Since getting arp tables is not allowed via SNMP by most firewall vendors, why not to consider retrieving this information using login credindials instead of SNMP?

  • +1 here to I already have a way to get the info from our PaloAlto firewalls just no way to give that to UDT emoticons_sad.png

  • We have also Palo Alto and Checkpoint at the same time. And you are right PaloAlto has a weak MIB support.

  • Yup bit of digging and although the PaloAlto supports some MIB's it doesn't support the ipNetToPhysicalTable which i think is needed to UDT for work correctly. I have however been able to get that the ARP information with the PaloAlto web API just now don't know hoe to add it to UDT without some heavy database reverse engineering which i would rather not do.