Configuration Management Archives Not Being Created Due to Missing Capture Keys or Prompt Handling

Configuration Management tasks complete successfully, but no configuration archives are created. In some cases, the device output is visible in the debug session, but nothing is stored in the archive repository.

Oct 6, 2026
Knowledge

Title

URL Name

000306451

Article Number

000306451

Environment

WhatsUp Gold Configuration Management Aruba 7205 Controllers (ArubaOS 8.10) Cisco Email Security Appliance (AsyncOS 16.0)

Question/Problem Description

I encountered an issue with Configuration Management backup for Aruba 7205 and Cisco ESA.

The backup task shows Success, and the configuration output is displayed correctly in the Task Results (see attached PNG). However, the configuration is not saved as a backup.

I performed debugging to investigate the issue and found errors in the attached Debug logs.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Configuration Management only creates archives when output is tagged with a valid archive capture key such as:

[running-config]

[startup-config]

If the capture key is missing, incorrectly positioned, or the device output is interrupted by paging or prompt matching issues, WhatsUp Gold may successfully execute the script but capture no archive data.

When this occurs, the log records:

Alert: Task: <task>: <device>: no archives to check threshold against

This is logged at the INFO level in:

C:\Program Files (x86)\Ipswitch\WhatsUp\Data\Logs\NetworkConfigService.log

Resolution

For future Configuration Management integrations, I would recommend following the same process used here before opening a support case.

Review the vendor's CLI/export documentation alongside the WhatsUp Gold Configuration Management Guide to verify:

The command required to generate the configuration output.
Any interactive prompts that require a response.
Paging behavior and how to disable it.
The correct archive capture key placement ([running-config], [startup-config], etc.).
Prompt patterns that may interfere with configuration collection.

Using the vendor documentation in combination with the WhatsUp Gold Configuration Management Guide can often identify the required script changes without the need for Support involvement and can significantly reduce troubleshooting time.

The recommendations below are specific to ArubaOS 8.10 and Cisco ESA AsyncOS 16.0 and should not be assumed to apply to other device types.

ArubaOS 8.10

Actual Fix

Modify the script as follows:

@login
no paging
[running-config] show running-config
@logout

Why This Fix Works

The [running-config] tag instructs Configuration Management to save the command output as an archive.

The no paging command prevents ArubaOS from displaying --More-- prompts during output generation. Large controller configurations can be truncated when paging is enabled, resulting in incomplete or empty captures.

Additional Recommendation

If archive captures continue to be inconsistent, review the Aruba CLI Settings definition and consider using a more specific CommandPrompt expression.

The default prompt pattern may match lines within the running configuration itself, causing Configuration Management to incorrectly assume command completion before all output has been received.

Cisco ESA (AsyncOS 16.0)

Actual Fix

Place the capture key on the response line rather than on the showconfig command:

@login
showconfig
[running-config] 2
@logout

Why This Fix Works

When showconfig is executed, Cisco ESA prompts for a configuration export option.

Option:

exports the configuration using encrypted passphrases and produces a restorable backup.

Placing [running-config] on the response line ensures the resulting configuration output is captured and archived correctly.

Using the inline query format may fail because the command prompt can be matched before the query handler processes the response.

Verification

After updating the scripts:

Run the Configuration Management task.
Open:
- Device Properties → Tasks/Archives, or
- Analyze → Configuration Management → Archive Search
Confirm a new archive is created.

Review the debug logs for entries similar to:

Record archive: running-config, command: ...

and

Archive: running-config, characters: NNNNN

Verify the command output appears under the Capture section of the debug session.

Expected Behavior

The following behaviors are normal and do not indicate a defect:

No Configuration Changes

If the newly captured configuration is identical to the previously stored archive, no new archive record is created.

The log will report:

no archive changes detected

Store Backup to File System Enabled

When Store backup to file system is enabled, tasks that capture no configuration data will report:

Failed Save

instead of Success.

This setting can help identify archive capture problems more quickly.

Summary

The issue is not caused by a Configuration Management product defect.

The root cause is that Configuration Management is not receiving valid archive content due to:

Missing or misplaced archive capture keys.
ArubaOS paging interruptions.
Prompt matching behavior during command execution.

The corrective action is to update the device scripts to use the appropriate [running-config] capture tags and, for Aruba controllers, disable paging before collecting the running configuration. This ensures the configuration output is successfully captured and stored as an archive.

Workaround

Notes

Keyword Phrase

Last Modified Date

10/7/2026 12:15 PM