Ensure that the connections between all Unified Communications applications and Platform Manager are established before you run a task. All Unified Communications applications must be contacted at least once before you run the first Platform Manager task. SFTP or FTP and Unified Communications applications must be routable from Platform Manager; for example, if NATs are used, use public IP. Likewise, the SFTP or FTP servers must be routable from the Unified Communications applications.

A backup schedule task exists but needs some updates

A backup task cannot be edited after it is created; however, you can edit a backup schedule task.

1. Save settings for the backup that needs to be changed.

2. Create a new backup with the saved settings.

3. When you create the new backup, use the saved settings from the first step.

4. Modify the settings, as required.

5. Save the backup.

6. Delete the old backup.

Backup server task was cancelled but some servers were still backed up

Backup schedule tasks can be cancelled while in process. Any servers in the group, however, that have started backing up when you cancel the task do not stop mid-task. These servers are still backed up.

A backup failed and more details are required to determine the issue

If a backup schedule task fails, review the DRS logs.

The backup server task completed but some servers were listed as "Skipped"

"Skipped" servers have a first node server. After the first node server is backed up, all other servers in the group are skipped. Backing up the first node server ensures that the other servers in the group are also backed up. These servers appear as "Skipped" in the Backup Task List. A server also appears Skipped if it has a pre-9.x release version. Backup Scheduler can only backup servers with software versions higher than 9.0.

Service Inventory job scheduling relies on the service provider name for Cisco Unified Communications Domain Manager, which appears in the Infrastructure Manager administrative interface (Service Provider > Administration) and exists in the Shared Data Repository.

If Cisco Unified Communications Domain Manager 10.6(1) is used, the Service Provider is automatically pushed to HCM-F.

If Cisco Unified Communications Domain Manager 8.1(x) is used, the Service Provider is retrieved by using the Cisco HCS CUCDMSync service (strongly recommended).

If Cisco Unified Communications Domain Manager 10.6(1) is not used, the Service Provider can be manually configured in Infrastructure Manager.

Tip

For deployments using Cisco Unified Communications Domain Manager 8.1(x), use the Cisco HCS CUCDMSync service to synchronize data configuration between Cisco Unified Communications Domain Manager and Cisco HCM-F. If you use the Cisco HCS CUCDMSync service, Service Inventory requires that at least one synchronization has occurred before a report is generated. If necessary, perform a manual synchronization after you verify that the Cisco HCS CUCDMSync service is running. Be aware that if you manually configure the service provider in HCM-F and then activate the Cisco HCS CUCDMSync service for Cisco Unified Communications Domain Manager 8.1(x), or configure the service provider on Cisco Unified Communications Domain Manager 10.6(1), the information that you manually configured is overwritten with the information that comes directly from Cisco Unified Communications Domain Manager.

Perform the following tasks, depending on your configuration:

• Verify that the service provider name appears correctly in the Infrastructure Manager administrative interface. In addition, open Cisco Unified Communications Domain Manager and verify that the service provider name for Cisco Unified Communications Domain Manager is correct.

• If the name is correct in Cisco Unified Communications Domain Manager 8.1(x) and you use the Cisco HCS CUCDMSync service, perform troubleshooting tasks for the Cisco HCS CUCDMSync service, as described in the Troubleshooting Cisco HCS CUCDMSync Service.

• If the name is correct in Cisco Unified Communications Domain Manager 8.1(x), perform troubleshooting tasks for the Cisco HCS NBI REST SDR Web Service.

• If you do not use Cisco Unified Communications Domain Manager 8.1(x) or Cisco Unified Communications Domain Manager 10.6(1), update the configuration in the HCM-F Infrastructure Manager interface. To manually configure the Service Provider name in the Infrastructure Manager interface, select Administration > Service Provider.

The Service Inventory service encountered a runtime error and cannot validate the request from Cisco Unified Communications Domain Manager; therefore, the Service Inventory service cannot receive the files from Cisco Unified Communications Domain Manager.

Verify that you configured the username and password correctly for Cisco Unified Communications Domain Manager in the Infrastructure Manager administrative interface.

The Service Inventory service encountered a runtime error and cannot connect to the Cisco Unified Communications Domain Manager; therefore, the Service Inventory service cannot receive the files from Cisco Unified Communications Domain Manager.

Perform the following tasks:

• Verify that Cisco Unified Communications Domain Manager is up and running.

• In the Infrastructure Manager administrative interface, verify that you correctly configured the SOAP port for Cisco Unified Communications Domain Manager.

• In the Infrastructure Manager administrative interface, verify that you correctly configured the hostname and IP address for Cisco Unified Communications Domain Manager.

Service Inventory did not receive the files from Cisco Unified Communications Domain Manager after one hour passed.

Perform the following tasks:

• Log in to Cisco Unified Communications Domain Manager. Select General Tools > Transactions. Review the transactions to determine if the transactions failed.

  • For example, the following message may appear in the transaction: "Unhandled exception encountered while performing request processing. Report generation failure. FTP failure. Is there a file of the same name on the FTP server?"

    In the Service Inventory administrative interface, verify that you configured the SFTP port correctly on the Configuration page.

  • For example, the following message may appear in the transaction: "Unhandled exception encountered while performing request processing. Report generation failure. FTP failure. Authentication failed."

    On the Configuration page in the Service Inventory administrative interface, correct the user credentials for Cisco Unified Communications Domain Manager SFTP access to Service Inventory.

  • For example, the following message may appear in the transaction: "Unhandled exception encountered while performing request processing. Report generation failure. FTP failure. Is there a file of the same name on the FTP server? [Errno -2] Name or service not known."

  • Ensure that the Cisco HCM-F platform network connection works as expected.

  • If Cisco Unified Communications Domain Manager has DNS enabled, run the nslookup command on Cisco Unified Communications Domain Manager to ensure that the Service Inventory hostname resolves.

  • If Cisco Unified Communications Domain Manager does not use DNS, verify that you configured the IP address for the Service Inventory server on the Configuration page in the Service Inventory administrative interface.

Service Inventory received the file from Cisco Unified Communications Domain Manager, but the file is empty or does not contain all data.

In the Infrastructure Manager administrative interface, verify that the Provider configuration matches the configuration that is in Cisco Unified Communications Domain Manager.

The remote SFTP server did not receive the report that Service Inventory transferred.

On the Configuration page in the Service Inventory administrative interface, verify that the remote SFTP server configuration is correct.

If the an aggregate report is required, but Service Inventory is not generating it, check the report settings in Service Inventory. Verify that the Each reseller and customer checkbox is checked.