PRTG Manual: Configuration Task Progress
When device configuration capture tasks are started the progress of the task can be seen within the Configuration Task Progress dialog.
Each device participating in the configuration task will be listed in the dialog results. The devices will be grouped within the list depending on their current task state. Task states include, Pending, Running, Succeeded, and Failed.
Understanding Failure Messages
If the configuration capture failed a message indicating the reason for the failure will be provided. Some common failures and suggested fixes are provided below.
Missing SSH and Telnet credentials
UVexplorer requires SSH or Telnet credentials to create a command line terminal session. If SSH or Telnet credentials are not provided in the settings or on the device configuration capture will not be able to continue.
See Managing Device Credentials, and Capturing Device Configurations for more information.
When UVexplorer runs configuration tasks it must find the correct script to run against the device. If UVexplorer is unable to find a script for the device is could be because it does not have a discovered SNMP OID or because there is no available script.
See Understanding Configuration Capture Scripts for more information.
This message indicates that UVexplorer was unable to connect to the device. This could occur because the device is unavailable, you could try pinging the device to ensure it is responding. It is also possible that the device is not configured to support the attempted SSH or Telnet protocol. You could try connecting to the device manually using a tool such as Putty to ensure the device is configured properly. If the device does not accept the manual connection the device will likely need to be configured to accept SSH or Telnet connections.
This message could occur if the provided credentials are incorrect. You could verify the credentials manually using a tool such as Putty. Also you could ensure that the correct credentials are provided and properly configured within UVexplorer. See Managing Device Credentials for more help configuring credentials.
Another cause of this error message is that UVexplorer didn't recognize the login sequence required for the device. When UVexplorer connects to a device it looks for command prompts such as 'login as:' or 'User Name: ' to begin the login sequence. If the device is unsupported UVexplorer may not recognize the device login prompts and will be unable to connect to the device. If you have verified that the correct credentials are being used for the configuration task then it is possible your device is unsupported. Contact UVexplorer customer support for help with Device Support.
Unable to enter privileged mode
Many devices require the logged in user to have privileged access to display the device configuration. These devices typically have a command to enter privileged mode such as 'enable'. When this error occurs, UVexplorer attempted to enter privileged mode and the command failed.
One cause of this failure could be that the privileged command prompted for a password and the wrong password was provided. To fix this ensure that the correct privileged password is provided with the device credential.
Another problem could be that the UVexplorer command line settings were unable to recognize the privileged password prompt or command prompt, or the device didn't understand the response to these prompts that UVexplorer sent.
Another potential cause of this error message is that the device does not support a privileged mode, or requires a privileged command different from the one being sent by UVexplorer if this is the case there is an issue with device support. See Understanding Configuration Capture Scripts for more help with this error.
This message occurs when an error occurs while running a command within the script. See Understanding Configuration Capture Scripts for help with this error message.
Canceling Configuration Capture Tasks
Configuration capture tasks started manually can be canceled in the task progress dialog by selecting the cancel button. Canceling a configuration task will keep any pending device captures from starting. For any running captures the next command will not be run but UVexplorer will wait for the currently running command to complete before it can cancel the task entirely. If a configuration capture task is canceled the results of any completed captures will not be stored on the device.
