endpointlocation.v1

The list of possible locations, in order from most likely to least likely

Explanation for ports that have unspecified likelihood

Explanation for ports directly connected to the queried endpoint device in LLDP

Explanation for ports directly connected to at least one non-inventory device in LLDP

Explanation for ports not directly connected to any device in LLDP

Explanation for ports only connected to inventory devices in LLDP

Explanation for ports that are on the inventory device itself

Explanation for ports directly connected to the queried device in LLDP (for inventory devices)

Explanation for ports not directly connected to any device in LLDP (for inventory devices)

Explanation for ports connected to only other devices besides queried inventory device

Explanation for ports containing a virtual interface

Explanation for wireless clients that are directly connected to a wireless access point

Onboarded or inventory devices

May be used for some unknown LLDP chassis id type

These ports have unspecified likelihood

These ports are very likely to be physically connected to the queried device

These ports are likely to be physically connected to the queried device

These ports are somewhat likely to be physically connected to the queried device

These ports are less likely to be physically connected to the queried device

This is used for capturing future MAC types

Key uniquely identifies a EndpointLocation instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

EndpointLocation instance in this response.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this EndpointLocation’s last modification.

Operation indicates how the EndpointLocation value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.