Overriding a Management Configuration

1. Select Configuration > Devices > Device Overrides from the web UI.
2. Select Management.
   

   Note

   A blue override icon (to the left of a parameter) defines the parameter as having an override applied. To remove an override go to the Basic Configuration section of the device and click Clear Overrides. This removes all overrides from the device.
3. Refer to the Message Logging field to define how the profile logs system events.
   It is important to log individual events to discern an overall pattern that might be negatively impacting performance.

   Enable Message Logging	Select this option to enable the profile to log system events to a log file or a syslog server. Selecting this check box enables the rest of the parameters required to define the profile‘s logging configuration. This option is disabled by default.
   Remote Logging Host	Use this table to define numerical (non DNS) IP addresses and ports for up to four external resources where logged system events can be sent on behalf of the profile. Select the thrash icon as needed to remove an IP address from the list.
   Facility to Send Log Messages	Use the drop-down menu to specify the local server (if used) for profile event log transfers
   System Logging Level	Event severity coincides with the syslog logging level defined for the profile. Assign a numeric identifier to log events based on criticality. Severity levels include 0 - Emergency, 1 - Alert, 2 - Critical, 3 - Errors, 4 - Warning, 5 - Notice, 6 - Info and 7 - Debug. The default logging level is 4.
   Console Logging Level	Event severity coincides with the syslog logging level defined for the profile. Assign a numeric identifier to log events based on criticality. Severity levels include 0 - Emergency, 1 - Alert, 2 - Critical, 3 - Errors, 4 - Warning, 5 - Notice, 6 - Info and 7 - Debug. The default logging level is 4.
   Buffered Logging Level	Event severity coincides with the syslog logging level defined for the profile. Assign a numeric identifier to log events based on criticality. Severity levels include 0 - Emergency, 1 - Alert, 2 - Critical, 3 - Errors, 4 - Warning, 5 - Notice, 6 - Info and 7 - Debug. The default logging level is 4.
   Time to Aggregate Repeated Messages	Define the increment (or interval) system events are logged on behalf of the profile. The shorter the interval, the sooner the event is logged. Either define an interval in seconds (0 - 60) or minutes (0 -1). The default value is 0 seconds.
   Forward Logs to Controller	Select this option to define a log level for forwarding event logs to the control. Log levels include Emergency, Alert, Critical, Error, Warning, Notice, Info and Debug. The default logging level is Error.

4. Refer to the System Event Messages field to define or override how system messages are logged and forwarded on behalf of the profile.
   1. Select Enable System Events to allow the profile to capture system events and append them to a log file.
      It is important to log individual events to discern an overall pattern that may be negatively impacting performance. This setting is enabled by default.
   2. Select Enable System Event Forwarding to enable the forwarding of system events.
      This setting is enabled by default.
5. Refer to the Events E-mail Notification field to define or override how system event notification emails are sent.

   SMTP Server	Specify either the hostname or IP address of the outgoing SMTP server where notification emails are originated.
   Port of SMTP	If a non-standard SMTP port is used on the outgoing SMTP server, select this option and specify a port from 1 - 65,535 for the outgoing SMTP server to use.
   Sender E-mail Address	Specify the email address from which notification email is originated. This is the from address on notification email.
   Recipient's E-mail Address	Specify one or more email addresses to be the recipients of event email notifications.
   Username for SMTP Server	Specify the username of the sender on the outgoing SMTP server. Many SMTP servers require users to authenticate with an username and password before sending email through the server.
   Password for SMTP Server	Specify password associated with the username of the sender on the outgoing SMTP server. Many SMTP servers require users to authenticate with an username and password before sending email through the server.

6. In the Persist Configuration Across Reloads field, use the Configure drop-down menu to define whether the access point saves a configuration received from a Virtual Controller AP to flash memory.
   The configuration would then be made available if the this access point reboots and the Virtual Controller AP is not reachable. Options include Enabled, Disabled, and Secure.
7. Refer to the HTTP Analytics field to define analytic compression settings and update intervals.

   Compress	Select this option to use data compression to when sending updates to the controller.
   Update Interval	Set the interval – in minutes, seconds, or hours – when the collected data is sent to the external analytics engine.

8. Click OK to save the changes and overrides made to the profile‘s management settings.
   Click Reset to revert to the last saved configuration.
9. Select the Firmware tab from the Management menu.
10. Refer to the Auto Install via DHCP Option field to configure automatic configuration file and firmware updates.

    Enable Configuration Update	Select this option to enable automatic configuration file updates for the controller profile from a location external to the access point. If this option is enabled (it is disabled by default), provide a complete path to the target configuration file used in the update.
    Enable Firmware Update	Select this option to enable automatic firmware updates for this profile from a user-defined remote location. This value is disabled by default.

11. Use the parameters in the Automatic Adopted AP Firmware Upgrade section to define an automatic firmware upgrade from a local file.

    Enable Configuration Update of Device Firmware	Select the access point model to upgrade using its associated Virtual Controller AP‘s most recent firmware file for that model. This parameter is enabled by default.
    Number of Concurrent Upgrades	Use the spinner control to define the maximum number (1 - 128) of adopted APs that can receive a firmware upgrade at the same time. Keep in mind that during a firmware upgrade, theaccess point is offline and unable to perform its normal client support role until the upgrade process is complete.

12. Click OK to save the changes and overrides made to the profile‘s management firmware configuration.
    Click Reset to revert to the last saved configuration.
13. Select Heartbeat from the Management menu.
14. Select the Service Watchdog option to implement heartbeat messages.
    This ensures that associated devices are up and running and can interoperate effectively. The Service Watchdog is enabled by default.
15. Click OK to save the changes and overrides made to the profile‘s configuration.
    Click Reset to revert to the last saved configuration.