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.

Discovery and adoption

PureView sweeps the address ranges you give it and records every device that answers, including one that refuses the connection. A discovered device becomes a managed one in a single step, once PureView has tested the login you give it.

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.

Router monitoring

PureView reads each MikroTik router every minute: interface traffic, processor, memory and temperature. A Cisco, Juniper or FortiGate router can take the core router role too, read over SNMP and, on Cisco, with show commands over SSH.

Devices of any make

A Juniper, HPE Aruba, Huawei, H3C, Fortinet, Palo Alto or other device that answers SNMP appears on the map with its ports, traffic, uptime and processor load. PureView reads SNMP v2c, and SNMP v3 with authentication and privacy (SHA-2 and AES), and tests each login before saving it.

Topology map

PureView draws the links between devices from CDP, LLDP, MAC tables and MikroTik neighbour tables. Because the devices report their own neighbours, the map follows the cabling as it is today. It can be viewed building by building and floor by floor.

Traffic history

PureView keeps one minute readings for seven days, then hourly readings for 90 days unless you choose otherwise. When a device reboots and its counters reset, PureView recognises the reboot and records no false drop in traffic.

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 its maker, the switch port it uses and every address it has held, and act on it from the same page.

Internet line health

PureView finds the internet lines on the core router and checks each one at its gateway and at an address beyond it. A line whose gateway answers while the internet does not is reported as degraded, and the backup line is known for what it is.

Provider service level reports

PureView measures each provider’s uptime against the targets you record for that line. Periods when PureView was not collecting are not charged to the provider. The service level and router restart reports print or download as CSV.

Fibre optics

PureView reads the light levels, temperature and module of every optic on your uplinks and internet lines each day, and learns a baseline for each one. It raises an alarm when the received light falls 3 dB below that baseline or past the maker’s warning, and describes a failing link from both ends in plain words: weak fibre, no light, loss in one direction, or a hot or mismatched optic.

Wireless register

PureView lists every MikroTik access point and its clients, and audits the channel plan across the building.

Wi-Fi coverage

On a MikroTik wireless network, PureView reads the signal of every connected client and reports, for each access point and by floor and room, how many readings were weak. On the floor plan, a heatmap shows the coverage predicted from the walls and each access point’s position, and the page says that it is an estimate.

Building model

Import your floor plan PDFs and PureView reads the walls, rooms, stairs and departments from each page. Access points and switches are placed on their floors and shown in 3D in their live state. A scanned drawing has no lines to read, so its walls and rooms are drawn in the editor.

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.

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 unless an administrator chooses between 1 and 365. The logs are indexed for search by host, severity or text, and a daily digest picks out loops and risks. Because the receiver stays off until an administrator turns it on, an update never opens a new port on the server.

02Diagnosis and Ask PureViewWhen someone says their PC or Wi-Fi is not working, an account of why, drawn from what the network has already recorded.

Diagnose

Your helpdesk types a person’s name, room, PC name or address, and PureView reads the records it holds for the last few days. It writes the conclusion, the next steps and a timeline, and every statement opens the records it rests on. Live checks and a cable test run from the same page. The account is worked out by fixed rules, so the same records always give the same answer.

Ask PureView

Ask about the whole network in your own words, such as which access points are busiest on the third floor or how the fibre links are, and follow up as you would with a colleague. Every line of the answer cites the records it came from, and PureView shows how it read the question. It runs on your PureView server, so your network data stays inside your network.

Watches and a morning brief

Ask PureView to tell you when something happens, for example when a line goes down more than three times in a day. PureView checks every five minutes and tells you through your alarm channels. It can also send you a morning brief.

Alarm diagnosis

When errors appear on a port, a switch stops answering, access points drop on one switch or an internet line goes down, PureView works through the checks an engineer would make and records each result with the alarm. For a line that is down, it reads the router and says which side the fault is on: your equipment, weak fibre at the router, or the provider.

Diagnosis alarms and reports

PureView raises an alarm when a client keeps hopping between access points or a desk port goes dark, and any diagnosis prints as a report.

A role for the helpdesk

Helpdesk staff can open Diagnose, Ask PureView, the connected clients, Wi-Fi coverage, alerts and incidents, and cannot change anything. A plain English guide for people with no network background comes with it.

Staff name their own PCs

Staff open a page on the PureView server from their own PC, without signing in, and enter their name or official email address, which PureView checks against your staff list. Your administrators see how many PCs are named on each floor, and confirm or correct each name.

03Alarms and incidentsAlarms that point to the cause of a failure, delivered where your team will see them, 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.

Port and security alarms

PureView raises alarms on switch ports that flap or count errors, telling output drops from real errors, and on security events in the router log.

Alarm email

PureView sends alarms by email through your own mail server or Resend account. A site with neither can use PureView mail, a short notice from [email protected] that carries no device names or addresses. Only the cause of a failure is mailed, with the devices behind it listed in the same email.

Alarm SMS and webhooks

PureView sends alarms by SMS through your own Twilio or Termii account, or as a signed webhook to a system you run. As with email, one message goes out for each cause.

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 other systems can propose changes through the integration interface.

Wall display

A full screen view for the operations room that rotates through the views your administrators choose. A new critical fault comes to the front at once. It runs on the local network without anyone signing in, and shows no addresses or client details.

04Backups and changesA backup of what each device runs, configuration built for each make, and changes made within each person’s role with a way back.

Configuration backups

PureView backs up MikroTik, Cisco IOS, IOS XE and ASA, Palo Alto, Juniper, Huawei, H3C, FortiGate and HPE Aruba configurations on a schedule, and keeps UniFi and Omada controller backups as the controller’s own file. Any two backups can be compared line by line, and a change nobody announced raises a notice.

Restore a Cisco backup

PureView restores a Cisco IOS or IOS XE backup onto its switch, with an automatic way back to the configuration the switch had before.

Restore a MikroTik backup

In development

PureView will restore a MikroTik backup onto its router from the restore points it keeps there, with an automatic way back.

Configuration for each make

PureView produces configuration in each make’s own syntax, from templates for gateways, VLANs, hotspots and wireless, 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.

Changes with a way back

Your team changes MikroTik routers within each person’s role. On Juniper, Huawei, H3C and HPE Aruba CX switches, PureView applies a change that the switch itself rolls back unless your engineer confirms it. On Palo Alto it edits address objects, groups and security rules, and on UniFi and Omada it turns wireless networks on and off and sets VLANs and port profiles, each with a preview and a revert.

Port fixes and switch baseline

Your team can bounce, enable or disable a Cisco switch port from PureView, which refuses to act on trunks, port channels and uplinks. Port diagnostics can label each port with the one device it recognises behind it. 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.

Firewall and WAN review

PureView reviews a MikroTik router’s firewall and its multi WAN set-up and reports what it finds without changing either. It also handles RouterOS updates and containers on RouterOS 7.4 and later.

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 make, and give each device its role. PureView checks the design, will not produce a plan while a critical problem is open, and applies the compiled design to your switches and routers.

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. Naming rules keep device names consistent.

Quarantine of home routers

When staff plug a personal router into the network, PureView can cut its internet access and that of the devices behind it, and send their web pages to the page where staff identify their PC. It stays off until an administrator turns it on, and watches without acting before it enforces.

Traffic policy

In development

Your team will set quality of service, filtering and quotas on MikroTik routers from PureView.

DHCP snooping planner

PureView works out which ports on each Cisco switch should be trusted for DHCP snooping, from the topology and the devices it has seen, and gives you the plan to review.

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.

Port lock

Enterprise

Ports on your core and distribution switches that have had no link for a month can be shut, moved to an unused VLAN and labelled with the date. An engineer previews each switch and presses Lock, and a locked port that comes up raises an alarm. Only an administrator can unlock a port, and must give a reason.

05Finding 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 turns a device’s lights on for five seconds and off for five, for 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.

Location walk and Crosswalk

During a location walk, a Zenaclove engineer plugs a laptop into each switch and access point cable, and PureView finds the switch and port within seconds, so that the room and rack position are recorded on the spot. For wall jacks, your own staff use Crosswalk: a phone page shows which switch port comes up when a device is plugged in.

Access point management

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

Web console

Open a terminal on a Cisco switch, a MikroTik router or a Linux server from the browser. A block of commands pasted into the console runs as one job, and PureView refuses a block that would reload, erase or overwrite the configuration. A switch can be renamed from PureView, and the new name is saved and read back.

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

Sites, rooms and racks

Professional

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

Asset register

Professional

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

Professional

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

Estate reports

Professional

Incident and rack capacity reports print as PDF or download as CSV.

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

Server monitoring

PureView reads processor, memory, disk and service state from Linux servers, Proxmox and VMware ESXi hosts, and scores each server against a compliance baseline.

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.

Server operations

Professional

Manage services, processes, packages, scheduled jobs, networking and power on your servers, and open a shell on one from the console.

Proxmox and VMware ESXi

Professional

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

Software deployment

Enterprise

Install, detect and remove about twenty common applications, among them Nginx, PostgreSQL, Docker and Fail2ban, and prepare a new server with its administrator account and a hardening baseline.

08Access control and auditWho can see and change what, how people sign in, how device passwords are protected, and a record of every change.

Roles

Every account is an administrator, an operator, a viewer or a member of the helpdesk, and PureView checks that role on the server for every request.

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.

Two step verification

Your administrators can require a second step at sign in, by a code from an authenticator app or by a passkey. PureView also asks again before any change that widens someone’s access. An account locks after repeated failed attempts, and an administrator can end any session.

Single sign on

Enterprise

Staff sign in with the accounts they already have, through OpenID Connect (Microsoft Entra ID, Google Workspace, Keycloak, Okta), SAML 2.0 (Entra ID, ADFS, Okta, Keycloak) or your Active Directory and LDAP directories.

Encrypted device passwords

The passwords and SSH keys 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.

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.

Signed audit export

Professional

Each audit entry is chained to the one before it, and the trail exports as a signed file that shows whether anything was removed or altered.

09Installation and appsWhere PureView runs, what you install, and the apps your team uses with it.

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 the server backs itself up every night.

Found by name

Once your gateway is set up, staff reach PureView at pureview.lan and the read-only dashboard finds the server with nothing typed. PureView prepares the gateway settings for this on MikroTik, Cisco, Juniper, FortiGate, Palo Alto, UniFi, Omada, HPE Aruba, Huawei and H3C equipment.

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 and opens the wall display full screen.

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.

iPad app

In development

The PureView console will be available as an iPad app through the App Store.

Android app

In development

The PureView console will be available as an Android app through Google Play.

High availability

Add-on

Run an active and a standby PureView server at one site. The standby holds a live copy of the database, and a shared address follows whichever server is active. An engineer promotes the standby with one command. High availability is a paid option on Enterprise.

Distributed pollers

In development

Small remote nodes will read the sites your PureView server cannot reach directly.

Site certificate

Zenaclove issues and renews a publicly trusted HTTPS certificate for your PureView server, under its own name at pureview.ng, so that browsers open it without a warning.

Remote management

In development

At your request, Zenaclove’s operations centre will manage your PureView server remotely.

10Licences 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 server checks it without an internet connection and opens only the modules it names. A licence copied from another server, or edited, is refused. When your licence is renewed or changed, the server collects the new one at its daily check, without a new activation.

Signed updates

Zenaclove signs every release, and the server 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 every minute, the client register with every client action, Wi-Fi coverage, configuration backup with restore points, and configuration changes.
Cisco IOS and IOS XEManaged
Monitoring, the map, the core router role, clients with port actions, fibre optics, configuration backup and restore. Changes cover port fixes, the switch baseline, saved logins, port guard and port lock.
Cisco ASAManaged
Monitoring and configuration backup.
Juniper JunosManaged
Monitoring, the core router role, configuration backup, and changes that the device rolls back unless your engineer confirms them.
Huawei VRP and H3C ComwareManaged
Monitoring, configuration backup, and changes that the device rolls back unless your engineer confirms them.
HPE Aruba AOS-CX and ProCurveManaged
Monitoring and configuration backup on both. Changes on AOS-CX, rolled back by the switch unless your engineer confirms them.
Fortinet FortiGateManaged
Monitoring, the core router role and configuration backup.
Palo Alto PAN-OSManaged
Monitoring, configuration backup, read only pages, and changes to address objects, groups and security rules with a preview and a revert.
Ubiquiti UniFi and TP-Link OmadaManaged
Through the controller: health, devices, clients with block and disconnect, controller backups, and changes to wireless networks, VLANs and port profiles with a revert.
Cisco MerakiAdd-on
Sites, devices, status and licence dates through the Meraki dashboard.
Any other device that answers SNMPMonitored
Ports, traffic, uptime and LLDP links on the map, over SNMP v2c or v3.
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