> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Network and Devices

> SNMP devices, Cisco Meraki, IP phones, monitors and the shared network view – which types arise and how they are structured.

What sits on the network but reports no operating system is captured via
SNMP. Two vendor-specific scan modules add to that, plus the monitors from
scans of systems and three types with no scan of their own that combine every
module's network data.

## SNMP devices

*SNMP v1 and v2* and *SNMPv3* create one of thirteen types depending on the
detected device class — including *Switch*, *Router*, *Firewall*, *Printer*,
*Load Balancer* and *UPS*. All thirteen share the same three groups —
General, Network, Device Information — and differ only in what appears
under *Device Information*: a printer carries paper trays and supplies, a
switch carries VLAN configuration and switch port assignment.

<Note>
  The specialized device classes carry **fewer** areas under *Device
  Information* than *Generic*, never more. The most reduced is the *Access
  Point*, with only two areas (physical interfaces, system components).
</Note>

## Cisco Meraki

The *Cisco Meraki* scan creates the organization with six groups: General,
Organization, Licensing (subscriptions, co-term, per-device licenses),
Security (administrators, login security, policies, RADIUS servers), Device
Management and Network Management.

<Note>
  Meraki is the only family with its own *Licensing* group — it separates the
  *Co-Term*, *Per Device (PDL)* and *Subscriptions* license models into their
  own areas.
</Note>

## IP phones

The *IP Phones* scan creates one type with manufacturer, model, firmware and
network addressing.

## Monitor

Created by a scan with *Windows (AD)*, *Windows (IP)*, *Linux* or *macOS*: a monitor is
captured on the system it is connected to, and at the same time created as
its own asset.

<Note>
  The same monitor is therefore visible in two places: as its own asset in the
  inventory, and on the system under *System Components* › *Monitors*, see
  [Systems](/docs/en/assets/systems).
</Note>

## Shared network view

Three internal types with no view and no detail page of their own arise from
any scan that delivers network systems: from *Windows* and *Linux* through
*SNMP v1 and v2* and *Cisco Meraki* to *VMware* and *Hyper-V*. They combine the
network data that the topology, network and routing plans are built from.

## Related

Credentials and target details for these scan modules are under
[SNMP](/docs/en/scan/snmp) and [Cisco Meraki](/docs/en/scan/cisco-meraki), and for IP
phones in the [Scan Reference](/docs/en/scan/reference). What is captured for
storage systems, backups and permissions is described under
[Storage, Backup, Permissions](/docs/en/assets/storage-backup).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.