ENA Configuration Management requires:
- an appropriate ENA license.
- available remote shell protocols, e.g. Telnet and Secure Shell (SSHv1 and SSHv2). You would require device login credentials.
- a running transfer server, i.e. FTP, TFTP, SCP or RCP server.
- activation of configuration monitoring on required devices.
To install Configuration Management:
This example provides an overview of installation using the provided TFTP server, and sample policy, exclusion and retrieval files.
- Configure and start the TFTP server. The transfer directory you specify here must be the same as set during configure.
- Accept the sample setup of the mandated policy, exclusion and retrieval script files. In practice it is likely that you would want to amend the supplied files. In this case, you should rename them to prevent them being overwritten during ENA upgrades, and/or create your own.
- Ensure you have an ENA license with the ENA Configuration Management module enabled and then run configure. You should set the transfer directory to the same directory as specified for the TFTP server.
- Start ENA. To activate Configuration Management:
- wait for ENA Auto Discovery to complete one cycle, after which Configuration Management fully available.
- initiate a configuration retrieval from the web UI, schedule a retrieval or configure a retrieval to occur when there is a change in the startup or running configuration files.
- For each device you can:
- assign CLI credentials. These credentials are used when Configuration Management initiates the command line access with the device, using Telnet or SSH.
- associate configuration management tasks.
To configure Configuration Management:
In ENA, the Configuration Management module is enabled by default. Please see this article for further help and information on configuring Configuration Management.