If you are running Oputils in a m/c that has multiple IP Addresses, it is required to bind the TFTP Server to a specific IP Address to successfully back up the configuration files.
Click Settings link from the Config File Manager tool.
If the TFTP Server is already running, click Stop.
Specify the IP Address to which the TFTP Server has to be bind.
Optionally change the location of the TFTP Root Directory. The downloaded config files are stored in the TFTP Root Directory.
Click Start to start the TFTP Server and bind to the new IP Address specified.
Click the Tools tab.
Choose Config File Manager available under the CISCO Tools category.
To configure SNMP properties click Settings located at the top right corner or click Admin -> Settings. For details read the Configuring SNMP section.
Enter the Device Name or its IP Address.
Enter the SNMP Community String of the Cisco device. The Community specified should have read/write permissions.
TFTP /NAT IP: This refers to the IP Address of the machine where TFTP Server is running. For downloading config files in the same LAN, leave this as it is. For downloading the config files of the devices in across WAN, specify the NAT IP here. The TFTP Server will, by default, be bound to the local IP Address of the machine where OpUtils is installed. Since this IP cannot be reached directly, you need to specify a NAT IP that can be reached across WAN, which will be translated to the local IP by the router.
Click Add. The added Cisco device gets added to the table below. The Config File Manager tool will fetch both the startup and running config files of the specified cisco device in the background.
To manually download the startup and running config files, click the icon corresponding to that device from the table.
The SNMP community string specified while adding a Cisco device (Switch / Router) is used for subsequent downloads of the startup and running config files. If the community string is changed in the device at a later date, subsequent downloads will fail. Click the icon corresponding to that cisco device and change the community string.
The Cisco devices should have the CISCO-COPY-CONFIG MIB implemented in order to download the startup config files.
Click the icon of a device to view its Startup Config file.
Click the icon of a device to view its Running Config File.
Click the icon to view the difference between the startup and running config files.
Daily - to update everyday. You need to specify the starting time.
Weekly - to update on specific day(s) in a week. You need to specify the starting time and the day(s) on which the update should happen.
Monthly - to update on a specific day every month(s). You need to specify starting time, select a day and select a month/months.
Once Only - to run the tool only once at the scheduled time.
Click Schedule to save the changes.
Note: When you schedule backup, the startup and running config files of all the cisco devices added to the tool will be backed up at the specified interval.
Click the Compare Config File link.
Select the files you wish to compare by selecting the appropriate options.
Select the device from the combo box. This will list all the files that are downloaded previously.
Select the versions to be compared and click Compare.
Click the Upload Config File link.
You have an option to upload the config files to a single device or to multiple devices. Select the appropriate tab.
Select whether to upload Startup or Running Config File.
Select the device(s) to which it has to be uploaded.
Browse and select the config file to be uploaded and click Upload.
Note: The downloaded config files are located in <Installed_Dir>/ AdventNet/ ME/ OpUtils/ webapps/ tftp/ <Device IP> from where you can edit the files, if required and upload.
Error Messages : E1001: Unknown Host, E1002: Unreachable Host, E2001: No Response to SNMP Queries, E2004: Community with read/write permission required, E4005: Not a CISCO Device, E5003 : Unable to bind to Port