Baseline Configurations - Extreme Networks Ridgeline Guide Manual

Managing Network Device Configurations and Updates
Figure 249: Scheduling archival configuration file uploads
You can schedule daily or weekly uploads, and specify the time of day (and day of the week) at which
they should be done. This lets you schedule uploads at times when it will have the least impact on your
network load. You can create different schedules for each individual device, if that suits your needs.
Archival uploads are saved in subdirectories by the year, month and day that the archive was done.
The file is named based on the device IP address and timestamp, and is in ASCII text format.
You can manage your historical archives by limiting the number of archived configurations Ridgeline
saves, especially if you have a large number of devices on your network or choose to do frequent
archiving, You can limit either the number of files Ridgeline saves for each device, or limit the length of
time Ridgeline keeps a file. In either case, when the limit is reached, the oldest files are deleted first.
If you don't want to schedule all your devices individually, you can set the Global Schedule, which will
then archive all other devices (those not individually scheduled) based on the global schedule.
To upload configuration files from your Extreme devices to Ridgeline on a one-time basis, select
Configuration > Tasks > Upload from device from the Tools menu. You can also initiate an upload for
an individual device by selecting the device in the Configuration Manager window and then selecting
Upload from device from the Config menu. When you upload a device configuration on demand, you
can save it at a location and under a filename of your choice, rather than being restricted to the default
naming scheme that Ridgeline uses.

Baseline Configurations

By creating baseline configuration files for your devices, you can establish a set of configurations that
act as a reference configuration for the device. You can use the baseline configuration as a "known
good" configuration in case of configuration problems, and you can use it as a reference to compare
against archived configuration files to identify any configuration changes that have been made.
Ridgeline Concepts and Solutions Guide
294