Cisco Tools - Knowledge Base

1. In the Config File Manager tool, I am not getting the Startup Config file. It says "Cisco Copy Config MIB" is not supported?

The Startup Config file of a Cisco device is retrieved through SNMP using the Cisco Copy Config MIB. For devices running older IOS versions, which do not support Cisco Copy Config MIB, the Running Config file can only be retrieved.

2. Why do I get the error "E5003: Unable to bind to Port -69" in Config File Manager?

The Config files from the cisco devices are downloaded using the TFTP server, which listens at port 69. If this port is occupied or when you run OpUtils in a Linux machine without root privileges, you will get this error.

3. I tried to retrieve a config file from a Cisco device. But, when I click to view the config files, it is blank.

The possible reasons could be:

1. If you are running OpUtils in a Windows m/c, check whether the Windows Firewall is blocking the communication. You can either check retrieving the config files after stopping the firewall or by adding UDP port 69 to the exceptions list.
2. If you are running OpUtils in a dual IP m/c, there is a possibility that the TFTP Server is bind to a wrong IP. Click the Settings link available in the Config File Manager tool and specify the IP Address to which the TFTP Server has to be bind. Click Stop and Start so that the TFTP Server gets bind to the specified IP Address.

4. When I try to get the Access Lists, I get an error as "E4002: Wrong CLI authentication parameters". How do I fix this?

The Access List of the Cisco devices are retrieved through CLI. Check the command prompt and password prompt of the device and set it in OpUtils by clicking the CLI Settings link available in the Device Explorer tool.

5. I get an error as "Error Retrieving Config File" during both scheduled and manual operations. What could be the problem?

The possible reasons for this error could be:

• UDP Port 69 has been blocked by the firewall running in the computer where OpUtils is installed. Stop the firewall or add UDP Port 69 to the exceptions list.
• The computer where OpUtils is installed has more than one IP Address and the TFTP Server is bind to a wrong IP. You can specify the IP Address to which the TFTP Server should be bind in Config File Manager Settings.
  1. Click Config File Manager --> Settings
  2. Specify the IP Address to which the TFTP Server has to be bind in the TFTP Server IP field. For example, if the computer has one public IP and one private IP and when the cisco device is not aware of the Private IP, you should specify the Public IP here.
  3. Click Save and Restart the TFTP Server.

Note: When you move the OpUtils installation from one computer to another, you should also have to change the IP Address to which the TFTP Server has to be bind after migration.