UDT locator

Hi All,

I am looking to use SWISS or the RESTAPI to perform some search functions through UDT. I am looking to search by MAC address and/or IP (can be two seperate scripts) to essentialy return a custom attribute on a port. I made an attribute called RoomNumber on ports.

In a nutcase if I put in Ip 10.0.0.5, UDT knows it sits on SwitchA port G1/0/47. Simply return the value of the RoomNumber attribute.

Find more posts tagged with

udt_query

sdk

Accepted answers

All comments

tdanner

Where are you storing this RoomNumber attribute? UDT does not support custom attributes/properties on Ports.

rschroeder

Without custom properties supported, you might find it simpler (if your network isn't large) to just include a DNS entry in the device name. We do that across 60,000 active addresses, for those which are static in location, like switches. A DNS entry scheme that might be used could look like this:

A-BCDE-FGHI-JKLMN-OPQRS

A = Geographic Region or State or Country or City

BCDE = Specific Building / Site / Facility

FGHI = Department or Room Number

JKLMN= Room Number or Device Type

OPQRS= Unique ID referencing this particular device, separating it from all similar devices in the room.

I'll grant you, this requires careful planning and thought. Implementing a manual naming convention that is location-dependent isn't something to enter lightly if you've got a lot of devices that will be moving or will retire on regular basis and be replaced, or if there is significant growth in your device count, or if there is much turnover in your IT support staff. Getting everyone to use the appropriate naming convention can be daunting if you don't train the people to succeed 100% of the time.

The names and characters used can vary per your unique needs. Once it's set up, UDT and IPAM and NPM and NCM and your staff can leverage the names. It's important to update the names and databases each time a device changes location, dies and is replaced, or a new device is added.

rootdet

This would not work out. We are looking for where phone endpoints sit and

move throughout a building to further be compliant with local 911

standards. For an 800 phone system, they want the 911 address down to a

room address, and staff tend to move within a building. DNS would just not

help with since they do not have DNS names.

On Thu, May 31, 2018 at 6:19 PM, rschroeder

rootdet

The CustomProperty is stored on the interface within NPM. Similar to an

interface attribute like CarrierName or Circuit Number (both I think come

as defaults).

In reality once UDT tells us the port info, we can do a separate query to

get the attribute from NPM. I can easily find that with a SQL query, just

falling short on identifying the port first.

On Thu, May 31, 2018 at 5:33 PM, tdanner

tdanner

Here's a SWQL query that will find the port where a given MAC address was most recently seen:

SELECT TOP 1 P.NodeID, P.PortID, P.Node.Caption, P.Name, P.EndpointsHistory.LastSeen, P.EndpointsHistory.Endpoint.MACAddress

FROM Orion.UDT.Port P

WHERE P.EndpointsHistory.Endpoint.MACAddress='0123456789AB'

ORDER BY P.EndpointsHistory.LastSeen DESC

And here's the same thing for an IP address:

SELECT TOP 1 P.NodeID, P.PortID, P.Node.Caption, P.Name, P.EndpointsHistory.LastSeen, P.EndpointsHistory.Endpoint.IPAddresses.IPAddress

FROM Orion.UDT.Port P

WHERE P.EndpointsHistory.Endpoint.IPAddresses.IPAddress='1.2.3.4'

ORDER BY P.EndpointsHistory.LastSeen DESC