Common Tasks with SolarWinds UDT
4.
Enter the desired term for the search.
This example uses IP address '10.199.0.3' as the target device.
In general, specific matches are required sought unless wildcards are used in
the search term. This means that if you search for laptop and there is a
machine named laptop01, you will not find it unless you search for laptop01 or
laptop* (or other valid wildcard search).
5.
Press Enter or click the search button to begin the search.
The search results are displayed in a scrollable, tabular view. For each item, the
following information is displayed in columns:
n Match Item
n Match Type
In this example, searching on subnet '10.199.*', we get a list of one item and
the software automatically navigates to the Device Tracker Endpoint Details for
'10.199.0.3', showing us:
Node Port Node Name Connection Duration Connection Type
A1 Core-4500 24 days, 8 hours, 5 minutes Endpoint IP Address
(Router) Core-4500 24 days, 8 hours, 5 minutes Endpoint IP Address
Notes:
Search returns a separate row each for active and inactive connections.
If you cannot find a device, but know that it is connected, search using the MAC
address to find the port that points to a physical location. MAC addresses are
stored without formatting. You can successfully search for a MAC address with
format xxxx.xxxx.xxxx or xx-xx-xx-xx-xx-xx or xx:xx:xx:xx:xx:xx.
6.
To monitor this endpoint as a node, click Start monitoring as a node under
Endpoint details.
Seeing Rogue Endpoint Connections in Real-
time
Scenario: I have my White List set up but I want real-time or near real-time alerts
when a rogue device connects to the network.
To cover this scenario, you will need to set up your devices to send connection-
related traps to the UDT server. UDT checks the database for trap-related information
at set intervals. If an endpoint connects to a UDT device, and the endpoint is not on
the White List, UDT posts an alert in the web console.
80
To Next Page
Loading...