Skip to content

Hosts

Hosts is an inventory of every address GridNMS has actually seen on your network — not just the devices you’ve deliberately added. A host gets onto the list one of two ways, and every row says which:

  • Seen by a device — one of your monitored routers or switches reported it in its ARP table, which maps an IP address to a MAC address and the switch port it was seen on. This needs nothing beyond the gear you already monitor.
  • Found by a scan — a network scan reached the address and found at least one open port. A scan can cross routers, so it finds hosts your switches never see — but it can’t read a MAC address from another network, so these rows have none.

The two are different kinds of evidence, which is why the list keeps them apart instead of merging them.

Open Explore → Hosts.

Each row is one address GridNMS has learned about:

Column Description
Source Seen by a device or Found by a scan — how GridNMS came to know about the host.
MAC Address The hardware address of the host. A host found by a scan shows a dash, because a MAC can’t be read across a router.
Vendor The hardware manufacturer, looked up from the MAC address.
IP The IP address it was seen using.
Hostname The name GridNMS knows the host by, when it has one. A small marker beside the name means it wasn’t reported by the host itself — see Where a hostname comes from.
Device The managed device whose ARP table this host was learned from — click through to that device. Blank for a host found by a scan.
Interface The port on that device the host was seen on.
VLAN Which VLAN the host was on, if known.
Services How many open services GridNMS has found on the host. A dash means none have been found — the host may simply not have been scanned yet.
First Seen / Last Seen When GridNMS first and most recently saw this host.

Use the search box to filter by MAC, IP, hostname, device name, or interface. Narrow further with the filters beside it:

  • Service or port — show only hosts running a particular service. Type a service name (ssh, http, or part of a banner such as OpenSSH) or a port number (443, or 443/tcp to pin the protocol). A bare number is always treated as a port, so 22 finds hosts with port 22 open rather than any address containing “22”.
  • Source — show only hosts Seen by a device, or only hosts Found by a scan.
  • Device and VLAN pickers.
  • Network — show only the hosts whose IP address falls inside one of your site networks. Networks are grouped by site and shown as name and address range. You only see networks in sites you have access to.

The filters combine, and the count in the page header follows them. Clear filters resets all of them.

A host’s name can come from three places, and the list tells you which. The first one that has a name wins:

  1. The host itself — a name recorded for the host directly. No marker.
  2. DNS (globe marker) — when DNS lookups for hosts is turned on for the network the host is on, a collector asks a DNS server for the name belonging to each responsive host’s address, and shows what DNS returns. This happens during scheduled scans of that network, and when you scan a host from Discovery or Probe Host. Hover the marker to confirm the source.
  3. The matching managed device (device marker) — if the host is one of your managed devices, it shows that device’s DNS name, or failing that its name in GridNMS.

A host with no name from any of those shows —, or, when it was found by a scan, the first few services it’s running (for example Open: ssh, 8080/tcp) so the row is still recognisable. That’s common and doesn’t mean anything is wrong: many phones, laptops, and IoT devices have no DNS record for their address at all, so there’s no name to find. Names from DNS are only looked up for hosts that answered the scan, are refreshed as the scan repeats, and need a collector that has been updated to the latest version.

DNS lookups for hosts is off for every network until you turn it on. Open Configure → Sites & Networks, select the network, and use the Host names section. It works independently of port scanning: you can turn it on for a network without changing how often, or whether, that network is scanned.

With the switch on and no DNS server named anywhere, each collector asks the DNS server its own machine already uses. That is how lookups work today, and it is all you need to set.

The server is chosen from the most specific place that sets one:

  1. the network itself,
  2. the site the network belongs to (select the site and set DNS server),
  3. the collector doing the scan (the first address in DNS servers on the collector’s settings),
  4. the whole account (the first address in Custom DNS Servers under System Configuration).

A server must be an IPv4 address such as 192.0.2.53 — not a host name, and not a loopback, link-local or multicast address. One that is set but not usable pauses that network’s lookups and the Host names section says why.

Click any row to open a detail view for that host:

  • Current Location — whether it was Seen by a device or Found by a scan, its IP, hostname, vendor, the managed device and interface it was last seen on, its VLAN, and when it was first and last seen.
  • Services — any open ports GridNMS has found on this host’s IP address from a network discovery scan. This section stays empty until a scan has actually reached the host — it’s not a claim that the host has no open ports, only that none have been found yet.
  • Movement History — shown for hosts seen by a device (a host found by a scan has no MAC address to follow). Each time this host’s MAC address stopped being reported at an address it had been using: when it was noticed, the address it moved from and to, and the device and port it was seen on at that time, most recent first. If a host has moved many times, the latest are shown along with how many are recorded in all. A host that answers on two addresses at once is not moving, so it adds nothing here for as long as both addresses keep being reported; a move is recorded once the old address has been silent for several hours. Moves recorded before GridNMS began noting the device and port show only the addresses.

A scan adds a host to this list once it finds at least one open port on it. An address that answers a ping but has no open port isn’t listed, and neither is an address a scan couldn’t reach. If a host you expected isn’t here, check that the network it’s on is scanned for open ports and that the host is actually running a service.

A host is something GridNMS has merely observed — an address your network gear has reported seeing, with no monitoring performed on it directly. A managed device (see Devices & Inventory) is something you’ve explicitly added, with credentials GridNMS actively polls on a schedule, and which can raise its own events.

The two aren’t mutually exclusive. If a host’s IP or MAC address matches one of your managed devices, its detail view shows a “This node is a managed device” banner linking straight to that device — the same physical machine, seen from two angles.

The Hosts page itself doesn’t offer a way to promote a host into a managed device. If the host also shows open ports under Services, the Applications page can add it as a managed device — along with monitors for whatever it’s running — in a couple of clicks. Otherwise, add it manually under Devices & Inventory using the same IP address.

docs built 2026-11-12 · 945a2dec2