ZenPlus · Device Tracker guide

Find and investigate an endpoint

Search MAC and IP evidence, verify an observed switch port, and read connection, address and authentication history without guessing ownership.

Applies to ZenPlus 1.24.13Updated 2026-10-11Audience Network operatorsReading time ~12 min
Start with verified evidence

This guide describes the current appliance. Availability, vendor features and access depend on your device firmware and Windows policies. Screenshots use the development UI with fictional addresses, users and device names; they contain no customer inventory.

02 Interpret the columns #

ColumnMeaning
MACObserved interface identity. A locally administered/random address may have no reliable hardware vendor.
IP addressObserved address association; inspect its reporting gateway and history.
Connected toBest available switch/port observation. Indirect does not establish a direct access port.
VLANObserved or mapped VLAN; unavailable/ambiguous data stays unknown.
UserRecent correlated authentication activity, where permission allows; not proof of continuous use.
Last seenSource observation freshness. Offline state preserves historical inventory.

03 Read the endpoint detail #

Endpoint detail distinguishes an observed managed-switch port from a confirmed direct attachment and retains address evidence.
Endpoint detail distinguishes an observed managed-switch port from a confirmed direct attachment and retains address evidence. Development UI · fictional documentation data. Open image for full size.

Use Current location and Connection timeline together. A controller location is shown as Observed port. The switch link opens its port workspace. Expand additional sightings where available; a MAC on an upstream port is not another physical device.

04 Check attachment periods #

Each period records switch, local port, VLAN, first/last observation and whether it is active or closed. A move may temporarily overlap while upstream and old switch tables age. A 15-minute observation gap closes current attachment state while keeping history. Compare the source time and topology before changing an uplink override.

05 Inspect IP history and reporters #

Open the address row

IP history summarizes one address with its first/last times and active state.

Choose View history

Inspect retained periods rather than treating all observations as a continuous lease.

Inspect reporter evidence

Review the gateway, routed interface, source, observation count and repeated/legacy status. Three recent observations from the same evidence key are required for positive replacement; overlapping candidates are not exclusive ownership.

Address evidence shows a fictional reporting gateway and routed interface; it preserves source and observation history.
Address evidence shows a fictional reporting gateway and routed interface; it preserves source and observation history. Development UI · fictional documentation data. Open image for full size.

DHCP reuse, roaming and overlapping routing contexts can produce more than one candidate. Do not delete history to force a clean-looking address mapping.

06 Understand randomized addresses #

A locally administered MAC can be valid but cannot reliably identify the hardware manufacturer from its prefix. Keep unknown vendor rather than inventing an OUI match. Use an approved hostname rule or manual endpoint type when you have supporting inventory evidence.

07 Investigate Activity and alerts #

Activity records fictional new-endpoint and watch observations with their switch, MAC and time.
Activity records fictional new-endpoint and watch observations with their switch, MAC and time. Development UI · fictional documentation data. Open image for full size.

Filter Activity by event type and time range, then open the related endpoint. New, moved, watched and rogue events depend on collected evidence and configured policy. Alert delivery additionally depends on enabled alert rules and notification channels. A delayed poll or cache expiry is not a confirmed device outage.