Users Guide

845| Management Access Dell Networking W-Series ArubaOS 6.5.x| User Guide
Column Description
Model Controller model.
Version Version of software currently running on the controller.
Upgrade Status A controller configured to use the centralized image update feature can have one
of the following upgrade status types:
l N/A: Not applicable. Only the master controller has this status type. (Or the
active master if a standby controller is configured.)
l Rebooting: The local controller upgraded its image and is rebooting.
l Up-to-date: The local or standby controller is running the same image as the
master controller.
l Waiting, image not verified: The local controller is waiting for the master
controller to verify the images are present in the file server.
l Not Supported: The local controller version is lower than ArubaOS 6.3 and
does not support the upgrade feature.
l Upgraded, reboot required: The local controller upgraded its image and a
reboot is needed. A controller can have this status if the auto-reboot setting is
not enabled in the upgrade profile.
l Not part of target: The local controller image version does not match with the
master and requires an upgrade, but is not part of the target upgrade list.
Managing Certificates
The controller is designed to provide secure services through the use of digital certificates. Certificates provide
security when authenticating users and computers and eliminate the need for less secure password-based
authentication.
There is a default server certificate installed in the controller to demonstrate the authentication of the
controller for captive portal and WebUI management access. However, this certificate does not guarantee
security in production networks. Dellstrongly recommends that you replace the default certificate with a
custom certificate issued for your site or domain by a trusted Certificate Authority (CA). This section describes
how to generate a Certificate Signing Request (CSR) to submit to a CA and how to import the signed certificate
received from the CA into the controller.
The controller supports client authentication using digital certificates for specific user-centric network services,
such as AAA FastConnect, VPN (see Virtual Private Networks on page 342), and WebUI and SSH management
access. Each service can employ different sets of client and server certificates.
During certificate-based authentication, the controller provides its server certificate to the client for
authentication. After validating the controller’s server certificate, the client presents its own certificate to the
controller for authentication. To validate the client certificate, the controller checks the certificate revocation
list (CRL) maintained by the CA that issued the client certificate. After validating the client’s certificate, the
controller can check the user name in the certificate with the configured authentication server (this action is
optional and configurable).
When using X.509 certificates for authentication, if a banner message has been configured on the controller, it
displays before the user can login. Click on a “login” button after viewing the banner message to complete the login
process.