In this topic, you will learn how to configure Arista™ CloudVision Cognitive Unified Edge (CV-CUE) to work together with the
Portnox™ Cloud captive portal for guest user authentication.
Before you begin, configure the guest network in Portnox Cloud, generate a random
shared secret of up to 40 characters (for example, using a password manager), edit the captive portal, enter the shared
secret in the Shared Secret field, and save the configuration. Note down the shared secret and the
values of the IP (for walled garden) and Captive Portal URL fields, since you
will need them later.
Important: This guide gives general instructions for integrating Portnox Cloud with
specific third-party devices. We try to provide useful examples for common models, but settings can differ between
manufacturers, models, and environments. Because of this, we cannot guarantee these steps will work in every case.
For questions or problems with RADIUS setup – which is an industry standard and not specific to Portnox – or with
device-specific settings and troubleshooting, we recommend checking the device manufacturer’s documentation and contacting
their support team. Portnox Support can help when possible, but detailed setup of third-party devices is usually best
handled by the manufacturer. We also recommend updating your NAS device firmware to the latest version, as old
firmware can cause issues.
Important: All values in this configuration are examples. Make sure to adjust the
configuration to your individual profile names, RADIUS server addresses, ports, and keys by replacing the values that are
presented as underlined italics.
Note: This topic assumes that you already have at least one Arista access point registered
and assigned to your Arista Cloud tenant. To access CV-CUE, log in to
Arista Launchpad and click on the
CV-CUE tile under
Dashboard. CV-CUE opens in a new tab.
Important: CV-CUE organizes configuration by locations (a tree
of folders and floors). A location inherits its parent’s configuration, but a child location can have a customized
configuration of its own. If a child location is customized, an SSID that you create at the parent is not automatically
active there – you must turn it on, or configure it directly, at that location too. If Wi-Fi clients cannot see an SSID that
you configured, check whether their location has a customized configuration.