Solution · By Stack

Networks & Wireless

Switches, firewalls, WAN links, wireless controllers and cloud-managed access points each arrive with their own console. Unified360 brings them together: SNMP templates for the wired estate, firewall and SD-WAN health, controller and cloud Wi-Fi status, link quality and topology, with configuration changes tracked.

  • Wiredswitches and firewalls
  • Wirelesscontrollers and cloud
  • WANlinks and SD-WAN
Your network estateBreak something to see what Unified360 raises · sample data
ISP 1ISP 2MPLSWAN circuitCloud Wi-FiAruba · Meraki · CambiumFirewall pairFortigate · Palo Alto HACore switchSNMPWireless controllerCisco WLCCloud-managed APsAccess switch AAccess switch BController APsSSID clients
Illustrative example. Alert rules are configured per environment.

The problem

Network and Wi-Fi trouble hides in three places

The devices are monitored somewhere. The trouble is that "somewhere" is six different places.

01

Fragmented

One tool per vendor, one for the firewalls, another for Wi-Fi and a spreadsheet for the carriers. Nobody has the whole picture.

02

Silent

A circuit degrades, an AP disappears or a firewall fails over, and users notice first because nothing raised an alert.

03

Unmapped

Nobody can say how it is connected, or what changed on a device last week.

Where it goes wrong

Six gaps, and how each one is closed

A console for every switch vendor

How it goes wrongThe estate mixes Cisco, Arista, Dell, Cumulus and NVIDIA, and each one brings its own tool.

Closed withVendor SNMP templates with a generic-switch fallback: CPU, memory, temperature, power and fans where the platform exposes them, and interfaces with errors and discards.

Interface noise and blind ports

How it goes wrongThousands of interfaces, most of them unimportant, and one uplink that matters.

Closed withInterface up/down rules that fire after consecutive down polls, baseline newly seen interfaces so they don't alert, and page through very large interface counts.

Firewalls that fail quietly

How it goes wrongA firewall can be up and still be in trouble: full memory, exhausted sessions, a failed-over HA pair.

Closed withFortigate memory, sessions, VPN tunnel state and traffic, and SD-WAN link health. Palo Alto management and data-plane CPU and HA state. Per-device dashboards for each.

Wi-Fi nobody can see into

How it goes wrongAccess points live on a controller, in a vendor cloud, or both, and nobody has one view.

Closed withCisco WLC AP status and SSID clients over SNMP, Ruckus and Extreme templates, and Aruba Central, Meraki and Cambium cnMaestro through their APIs, with overview dashboards for devices, alerts and clients.

WAN links with a contract and no evidence

How it goes wrongThe carrier says the circuit was fine. You have no data to say otherwise.

Closed withLink monitoring for ISP, ILL and MPLS circuits: latency, jitter, packet loss and utilization against provisioned bandwidth, with the circuit ID, vendor and committed uptime on record.

Configs change and nobody knows

How it goes wrongA switch or firewall is edited, and the first sign is an outage.

Closed withConfig Backup captures configurations on a schedule, keeps a snapshot only when something changed, lets you compare two snapshots, and raises a drift alert.

Vendor coverage

What's covered, and how well

Built from the SNMP templates and integrations shipped today, including where a template still needs you to confirm your platform.

Cisco 9000Switches

CPU over 5 seconds and 1 minute, memory, temperature, power supplies, fans and interfaces.

Config backup SSH · confirmed
Cisco Smart SwitchSwitches

C1200 and C1300 series: interface counters, CPU utilization, discards and temperature. Tested on a Catalyst 1200.

Config backup CLI · needs validating
AristaSwitches

System, interface, CPU and memory metrics.

Config backup SSH · confirmed
Dell N2048Switches

System information, CPU, memory and network interface metrics.

Config backup SSH · needs validating
Dell SmartFabric OS10Switches

System, CPU, memory and interface metrics.

Config backup SSH · confirmed
Cumulus NetworksSwitches

System, interface, CPU and memory metrics.

Config backup SSH · needs validating
NVIDIASwitches

System, interface, CPU and memory metrics.

Config backup CLI · needs validating
Generic switchSwitches

Any switch with standard MIBs: CPU and memory, interfaces with errors, discards and duplex, temperature, fans, power and spanning-tree changes.

Config backup CLI · unverified
FortigateFirewalls

System, memory, sessions, VPN tunnels and SD-WAN health checks, with per-interface status and traffic.

Config backup REST API · confirmed
Palo AltoFirewalls

Model, serial and version, management and data-plane CPU, memory, sessions and HA state.

Config backup REST API · confirmed
Fortiweb, Imperva and ArraySecurity appliances

Basic health templates for these appliances.

Config backup CLI · unverified
Cisco WLCWireless controllers

Catalyst 9800 and AireOS-compatible: CPU, memory, interfaces, AP status and SSID client counts. Confirmed on a C9800.

Config backup SSH · needs validating
RuckusWireless controllers

ZoneDirector: AP status, radios and SSID clients.

Confirm your platform first. SmartZone uses different tables and needs the template adjusted.

Config backup CLI · unverified
ExtremeWireless controllers

A template for Extreme wireless controllers.

Confirm the platform family before relying on it. Extreme's controllers use different management models.

Config backup CLI · unverified
Aruba CentralCloud wireless

Devices, status, alerts and wireless clients through the cloud API: access points, switches and gateways up, and a refresh-token watch.

Cisco MerakiCloud wireless

Organizations, devices and active clients, with device-down alerts and an AP client-count threshold rule.

Cambium cnMaestroCloud wireless

Cloud tenant or on-prem server: access points and clients, with device-down alerts and AP radio performance thresholds.

"Confirmed" means the mapping was checked against a real device. "Needs validating" and "unverified" mean it's provided but should be tried against your platform first. Any SNMP-capable device falls back to the generic template.

Topology and addressing

Know how it all connects

The map is built from what the network already says about itself, with room for the links discovery can't see.

LLDPCDPARPSubnetManual
  • Filter by discovery sourceSee which protocol confirmed each link, and run a rediscover to refresh the map.
  • Switch ports and addressesIPAM tracks subnets, IPs and conflicts, and maps addresses to switch ports.
  • Links by siteWAN circuits grouped by site, with live status and quality.
Unified360 topology map of discovered devices connected by LLDP, CDP, ARP, subnet and manual links
The topology map. Screen from Unified360 running test data.

See it live

Real screens from Unified360

Unified360 Cambium overview with connected accounts, access points, online count, wireless clients and active alerts, an online and offline access point split, model mix, wireless clients over 24 hours, and recent access point down alerts; device names and accounts blurred
Cambium cnMaestro in Unified360: access points online and offline, model mix, clients over 24 hours and recent AP-down alerts. Test data.
Unified360 SNMP monitoring page for a Fortigate firewall with device status, ports up and down, CPU, memory, sessions and an interface status grid; hostname, address and customer blurred
A Fortigate firewall: ports, CPU, memory, sessions and interface status. Test data.
Unified360 SNMP monitoring page for a Palo Alto firewall with a system snapshot showing model, software version, operational mode and HA state, plus CPU, memory, sessions and dataplane cores; identifiers blurred
A Palo Alto firewall: system snapshot, HA state and load. Test data.
Unified360 SD-WAN links panel with latency, jitter, loss and status for five health checks and a latency chart over time; link names blurred
SD-WAN links: latency, jitter, loss and status per health check. Test data.
Unified360 link detail with status, availability, latency, packet loss, jitter, utilization and a latency trend chart; addresses blurred
A WAN link's availability, latency, loss and utilization. Test data.
Unified360 link monitoring map with links grouped by site and live up and down status; addresses blurred
WAN links by site, live. Test data.

Screens are from Unified360 running test data; hostnames, addresses, serial numbers, access point names, customer names and carrier names have been blurred.

What changes

When wired and wireless share one view

One view of wired and wireless

Switches, firewalls, controllers and cloud Wi-Fi report into the same platform, instead of one console each.

Faults reach you as alerts

Interfaces, firewalls, links, access points and config changes each have rules, with recovery when they clear.

Links you can hold carriers to

Measured latency, loss and availability sit beside the committed uptime for each circuit.

Changes you can trace

Config snapshots and a diff show what changed on a device, and drift raises an alert.

Questions

Frequently asked

Which vendors do you cover?

There are SNMP templates for Cisco, Arista, Dell, Cumulus, NVIDIA, Fortigate, Palo Alto, Fortiweb, Imperva, Array and a generic switch, plus Cisco, Ruckus and Extreme wireless controllers. Aruba Central, Meraki and Cambium cnMaestro are covered through their APIs. Any other SNMP-capable device falls back to the generic template.

Do I need an agent at each site?

Monitoring runs through a Unified360 agent at the site, and proxy servers let remote sites report back to one console. The cloud wireless platforms are polled by the site agent through their APIs too.

How good is the wireless coverage?

Cisco WLC coverage is confirmed on a Catalyst 9800, and Cambium cnMaestro is running against a live account. The Ruckus template is written for ZoneDirector, and SmartZone needs its tables swapped in. The Extreme template needs the platform family confirmed. For the cloud platforms, coverage is device status, alerts and clients, with AP thresholds on Meraki and Cambium.

What happens when an AP drops off a controller?

Cisco controllers stop listing an AP that has left instead of marking it down, so the status never changes. Unified360 treats an AP whose last-seen time has gone stale as down, and raises the alert.

Will a flapping interface flood us with alerts?

Interface alerts fire only after the interface has been down for a set number of consecutive polls, and recover when it comes back up. A newly discovered interface is baselined and doesn't alert.

Can it monitor ISP and MPLS circuits?

Yes. Link monitoring tracks latency, jitter, packet loss and utilization for each circuit against its provisioned bandwidth, and records the circuit ID, vendor and committed uptime. Links can use SNMP v2c or v3.

How does config backup work?

Configs are captured on an interval set by device role and stored as snapshots only when something changed. You can compare any two snapshots, and a drift rule alerts on a change. Fortigate and Palo Alto use their APIs, and Cisco 9000, Arista and Dell SmartFabric use SSH. Other vendors use a CLI fallback and are flagged as unverified.

How is the topology built?

From LLDP, CDP, ARP and subnet data, with manual links for anything discovery can't see. You can filter the map by discovery source and run a rediscover to refresh it.

See it on your own network

Bring your switches, firewalls and Wi-Fi into one view

Tell us which vendors you run and we'll show you Unified360 covering them. No commitment required.