Try now the Tanaza
WiFi Management Platform

✔︎ No credit card needed ✔︎​ Easy configuration

✔︎ Free up to 3 APs

or continue to read more
about Zero Touch Provisioning.

Today, the most valuable study conducted about the emissions for MSPs, ISPs and SPs shows that:

“Average CO2/km emissions vary by vehicle type and age, so the 120gr/km considered here is an optimistic scenario.​ If you multiply these numbers with several hundreds of field interventions typically run per day you can quickly see that there are tons of CO2 emitted per month.”
– Cisco Study

How does zero-touch provisioning work?

At this point, if the location of the DNS server is not provided or unreachable, DHCP uses other DNS services.

When the device has obtained an IP address, it faces other configuration obstacles such as:
– firewalls.

The device processes the DHCP options and locates configuration files, executes scripts, and upgrades and/or downgrades software.

If both the image and configuration files are present, the image is installed and the configuration is applied.

If only the image file is present, the image is installed on the device.

If the image is the same as the image already installed on the device, ZTP continues and skips the installation step.

If the image was unable to be fetched by the device, ZTP will try to fetch the image again.

If the image has corrupted, the installation fails.

If installation fails for any reason, ZTP will restart.

If there is no image or configuration file, the ZTP process starts again.

If there is no file server information, the ZTP process starts again.
Once the configuration is committed, the ZTP process has been deemed successful and terminates.

The precedent list is only a brief sequence of the operation that occurs during the ZTP provisioning process.
In the best cases, we have counted 19 operations that network administrators can solve with further sub-tasks and manual commands.
In these steps, random events and triggers that can cause the restart of the process can suddenly happen, increasing the number of time-consuming operations.

For instance, these events are:
– Request for the configuration file, script file, or image file fails.
– The configuration file is incorrect, and the commit fails.
– No configuration files and no image files are available.
– The image file has been corrupted, and installation fails.
– No file server information is available.
– The DHCP server does not have valid ZTP parameters configured.
– When none of the DHCP client interfaces goes to a bound state.
– ZTP transaction fails after six attempts to fetch the configuration file or image file.

Advantages of Zero-touch provisioning

Why Tanaza?

• Tanaza software upgrades existing Wi-Fi networks.
• Tanaza works with the most common easy-to-procure Wi-Fi access points available in most countries, such as Ubiquiti, MikroTik, TP-Link. If a device model is not supported yet, Tanaza may support it on request for medium to large network deployments. Discover all devices compatible.
• IT teams do not need to deploy any hardware controller. Tanaza is 100% cloud-based and ready to use with no need for AWS instance deployments.
• Our platform provides unlimited scalability.
• It’s powerful and it has an intuitive user interface.

The Tanaza team can help you to select the best hardware that runs the Tanaza Operating System out-of-the-box from our OEM partners for a plug-and-play experience. Discover the Tanaza Powered Devices.

Try now the Tanaza
WiFi Management Platform

✔︎ No credit card needed ✔︎​ Easy configuration

✔︎​ Free up to 3 APs

or continue to read more
about how to receive notifications
when access points go offline.

Sometimes, access points can disconnect from networks for various technical reasons (wrong IP configuration settings, loss of power, poor network connectivities by Service Providers, WiFi interferences).
This could happen without warning, at different moments of the day or night.
Tanaza allows users to trigger WiFi notifications sending automatic emails to members or external guests when a device loses contact with the cloud.

Set up offline device notifications and receive real-time alerts when something goes wrong in your network

Network administrators can scan the network status in specific time intervals:

– 1 minute;
– 5 minutes;
– 30 minutes;
– 1 hour;
– 1 day.

The procedure of AP scan starts when the cloud sends multiple pings to the entire network. (Here we use generically the term “ping”. We suggest you read the technical guide about alert notification system to understand more about what ping means)

When the process has terminated, network administrators can visualize a global vision of device status on Mapbox and obtain detailed information about networks, access points and connected clients.

If one or more WiFi devices don’t answer to this ping, the system understands possible network problems are happening and sends as many email alerts as the offline devices are.

Cloud-managed WiFi access points configured in Tanaza are divided in three different categories:

– APs with TanazaOS included in the firmware;
– APs that support SNMP protocol;
– APs that don’t support SNMP protocol.

The first category of the access point is monitored via a proprietary protocol that takes advantage of keepalive packets. These packets can include statistical information about the device. In this case, if TanazaCloud stops receiving keepalive packets, the device is considered “offline”.

The second category of access points is monitored through SNMP protocol. The Tanaza agent, distributed in the AP’s LAN, asks in polling the status through an SNMP request. If the device does not respond to SNMP, the device is considered offline.

The third category of access points is monitored by a simple ping executed by the Tanaza agent and distributed in the AP’s LAN. If the device does not respond to Ping, the device is considered offline.

At that moment the alert notification system triggers real-time emails.
Network administrators can select to send a notification to internal members or external email addresses.

Forget VPN and manual pings on the network

Until now, for this type of scanning, VPNs and manual pings were required.
Thanks to the Tanaza WiFi remote monitoring interface, network administrators can avoid learning useless technical activities and saving time and money without using additional platforms or network solutions.

Network APIs for WiFi alert notifications

The Tanaza WiFi alert notification system works thanks to the integration of multiple types of APIs. Soon we will publish the full list of APIs compatible with Tanaza

With Tanaza WiFi notification system you avoid to receive tons of emails for multiple disconnections

When multiple access points disconnect at the same moment, ideally, network administrators should receive as many emails as the device number. It’s not improbable that it happens.

Tanaza has studied three different mechanisms to avoid this:
1) an anti-email-storm spike that aggregates emails in a single one.
2) an inhibitor that postpones email alerts with a time interval of 1 hour.
3) a large set of APIs to detect when devices go offline and warn network administrators.