Skip to content
Strands of fibre-optic cable carrying blue light

Capabilities

What PureView does

PureView watches your routers, switches, firewalls, access points and servers from a server inside your network. Open an area to see what it covers.

Request a demo

Scope

Network, sites and servers

PureView finds the devices on your network, shows how they connect, keeps their configurations, and places each one in the site, rack and server estate around it.

01Network visibilityWhat is on your network, what each device is, how the devices connect, and how they perform over time.

Subnet discovery

PureView sweeps the address ranges you give it and records every device that answers, including one that refuses the connection. It tries the ports that switches, routers and access points answer on as well as the common web ports, and the sweep needs no administrator rights on the server.

Device identification

PureView identifies the maker of each device from its hardware address and reads the model over SNMP where the device reports it. When the evidence fits more than one model, it leaves the model blank.

Links between devices

PureView draws the links between devices from the neighbour tables on your switches and routers. Because the devices report their own neighbours, the map follows the cabling as it is today.

Traffic history

PureView turns interface counters into traffic rates. When a device reboots and its counters reset, PureView recognises the reboot and records no false drop in traffic. Where readings are missing, the graph shows the gap.

Devices of any make

A Juniper, HPE Aruba, Huawei, H3C, Fortinet or other device that answers SNMP appears on the map with its ports, traffic, uptime and processor load. PureView reads these devices with SNMP v2c and a read only community.

Client register

PureView records every device on the network: each minute from the core router, and every five minutes from switches and controllers. For each one you can see the switch port it uses and every address it has held.

Cisco Meraki

Add-on

PureView reads Meraki sites, devices, status and licence dates through the Meraki dashboard. It raises an alarm when a device goes offline or a licence is 90 or 30 days from expiry, but it cannot change Meraki configuration.

Internet link health

PureView checks each internet link at its gateway and at an address beyond it. A link whose gateway answers while the internet does not is reported as degraded. While traffic is still flowing, PureView counts the link as up even if a probe fails.

Provider uptime reports

PureView measures each provider’s uptime against your contract target, 99.5% unless you set another. Each reading counts for the time it covers, and periods when PureView was not collecting are not charged to the provider.

Device logs on your server

PureView receives logs from your devices in both standard syslog formats, over UDP and TCP, and keeps them for 30 days. Because the receiver stays off until an administrator turns it on, an update never opens a new port on the server.

02Configuration and changesConfiguration built for each vendor, backups of what each device runs, and changes made within each person’s role.

Configuration for each vendor

PureView produces configuration in each vendor’s own syntax and checks it before anyone applies it. A firewall policy set with no final deny rule is flagged, and a rule that refers to an object that does not exist is refused.

Configuration backups

PureView backs up router, switch and firewall configurations on a schedule and compares each copy with the one before it. When a configuration changes without warning, PureView raises a notice.

Hotspot rollback

If a hotspot deployment fails part way, PureView returns the router to the state it started from and restores the settings the deployment replaced.

Network design

Describe the network you intend to build, independent of vendor. PureView checks the design and will not produce a deployment plan while a critical problem is open.

IP address management

PureView records which addresses are allocated, suggests the next free address in the range you choose, and compares the plan with the devices that answer on the network.

Port fixes and switch baseline

Your team can bounce, enable or disable a switch port from PureView, which refuses to act on trunks, port channels and uplinks. An administrator can also apply a standard baseline and login to each switch, one switch at a time. PureView reads each change back and records it in the audit trail, where it can be reversed.

Port guard

Enterprise

When the router log shows a client misbehaving, PureView traces it to its desk port and proposes shutting that port. Nothing is shut until a member of your team approves. If anything behind the switch then stops answering, PureView reopens the port at once.

03Sites and racksWhere each device is installed, what it depends on, and what else is affected when it fails.

Sites, rooms and racks

Each device is recorded in its site, room, row and rack, down to the rack unit it occupies.

Asset register

Track each piece of equipment through its life, with its relationships to other items: what powers it, what it hosts and what depends on it.

Power chain

Record how power reaches each item. When a feed fails, the chain shows which other equipment loses power with it.

04Servers and hypervisorsThe servers behind the network, monitored and managed from the same console.

Server management

Register your servers, see their state, and manage their services, processes, packages, scheduled jobs, networking and power.

Proxmox and VMware ESXi

Manage the virtual machines on Proxmox and ESXi hosts through each platform’s own interface: power, configuration, snapshots, storage and networking.

Server agents

A small agent on Linux or Windows reports a server’s details to PureView with a key issued for that server alone. The key is shown once.

05Alarms and incidentsAlarms that point to the cause of a failure, and a record of how each incident was handled.

Alarm thresholds

An alarm opens only after a reading stays past its threshold for the time you set, and clears only once the reading has recovered. No alarm opens during an approved maintenance window, and an out of date reading does not count as a breach.

Root cause alarms

When a device fails and takes the devices behind it offline, PureView marks their alarms as consequences and links them to the device that failed. The alert inbox leads with the failed device.

Incidents and change records

Each incident has a timeline whose entries cannot be edited afterwards. A major incident needs a named person in charge, and evidence of the fix before anyone can close it. Change records sit alongside, and approving one needs the right permission.

06Finding devices on siteWhere a device is plugged in, which room it sits in, and a way to make it show itself to the engineer in that room.

Trace

Trace shows where an access point, switch or port plugs in: the switch, port and VLAN, the room if PureView knows it, and for a switch its uplink. Where it cannot find the answer, it gives the reason. Trace only reads; it changes nothing on the device.

Locate

Locate flashes a device’s lights for about two minutes so that someone at the rack can find it, then restores its usual setting. It never shuts or bounces a port.

Port finder and tracer walk

Port finder follows the switches’ address tables from the core router to the port any device is plugged into. To map the cabling itself, an engineer carries a small tracer from room to room while PureView spots it on each switch port, and one walk covers a whole building.

Access point management

Restart, locate and configure access points from PureView, and open a terminal on one even when it has no working address.

07Access control and auditWho can see and change what, how device passwords are protected, and a record of every change.

Roles

Every account is an administrator, an operator or a viewer, and PureView checks that role on the server for every request. A viewer who opens a page they cannot use is taken back to one they can.

Access by site, rack or device

Beyond their role, a person can be given a site, room, rack, group or single device, and then sees only that. A grant only ever narrows what someone sees within your organisation.

Encrypted device passwords

The passwords PureView uses to reach your equipment are encrypted with a key that belongs to your installation. Once saved, they are never shown again in the console.

Two step verification

PureView asks for a code from an authenticator app before applying a system update, approving an integration change or opening a shell on a server. Each account also has one time recovery codes.

Audit trail

Every change is recorded with who made it, what it affected, its values before and after, and where the request came from. No password or other secret is copied into the record.

08InstallationWhere PureView runs and what you install.

Runs on your own server

PureView runs on a Linux server inside the network it manages. One installer sets up the database, the application and the secure web front end, and sizes the database to the server.

Desktop console

A desktop application for macOS and Windows opens your PureView console and lends it the laptop’s console cable, so that an engineer at the rack can configure a switch over serial. It can also scan the laptop’s own network.

Read-only dashboard

A separate desktop build for people who only need to watch. It contains no management functions.

Offline installation

Enterprise

For a site with no internet access, the release bundle carries the application, its database and its web front end, and installs from media.

09Licences and updatesHow each installation is licensed and kept up to date.

Signed licences

Each installation carries a licence that Zenaclove signs for that installation alone. The appliance checks it without an internet connection and opens only the modules it names. A licence copied from another server, or edited, is refused.

Signed updates

Zenaclove signs every release, and the appliance checks that signature before it installs anything. An administrator confirms each update with two step verification. Small fixes install on their own, with the previous version kept ready to restore.

Supported equipment

PureView signs in to managed equipment to read its configuration, back it up and change it. It watches monitored equipment over SNMP without signing in. Send us your models and we will confirm support before a deployment.

MikroTik RouterOSManaged
Routers and CAPsMAN access points: monitoring, the client register with every client action, configuration backup and configuration changes.
Cisco IOS and IOS XEManaged
Monitoring, the map, clients with port actions and configuration backup. Changes cover port fixes, the switch baseline, saved logins and port guard.
Cisco ASAManaged
Monitoring and configuration backup.
Palo Alto PAN-OSManaged
Monitoring, configuration backup and read only pages.
Ubiquiti UniFi and TP-Link OmadaManaged
Through the controller: health, devices, clients with block and disconnect, and read only pages.
Juniper, HPE Aruba and ProCurve, Huawei, H3C, FortinetMonitored
On the map with ports, traffic, uptime and processor load over SNMP, and link alarms from syslog.
Cisco MerakiAdd-on
Sites, devices, status and licence dates through the Meraki dashboard. Read only.
Any other device that answers SNMPMonitored
Ports, traffic, uptime and LLDP links on the map.
Linux, Proxmox VE and VMware ESXiManaged
Server monitoring, server and virtual machine operations, and software deployment on Linux.
Windows serversMonitored
Monitoring and the asset register, through the agent.

Demonstration

See PureView running

We begin with the area you ask for: monitoring, configuration, racks or servers.

Request a demo