This document describes the reasons behind telemetry connections failing and how to restore them.
on that Cisco IOS XE device's operating system, causing telemetry sent from affected devices to Catalyst Center to go down.Customers are required to use either of these three options to resolve the issue.
1. Access Catalyst Center
Log in to Catalyst Center.
From the main menu, navigate to Design > CLI Templates.
2. Create a template project
Click Add > New Project.
Enter a project name, for example: PKI_Trustpoint_Changes.
Click Continue.
3. Create a new CLI template
Select the newly created project.
Click Add > New Template.
Enter a template name, for example: Configure_sdn_network_infra_iwan_Trustpoint.
Set Template Type to Regular Template.
Set the Software Type to Cisco IOS XE.
Select the appropriate device family or series for the intended Cisco IOS XE devices.
Click Continue.
4. Add the CLI Configuration
In the Template Editor, enter these commands:
crypto pki trustpoint sdn-network-infra-iwan
no hash sha256
hash sha512
5. Commit the template
After saving the template, clickActionsand selectCommit.
Enter a commit message, for example:Update trustpoint hash to sha512.
Confirm the commit.
6. Provision the template to a device
On theDesign > CLI Templates page, select the template.
ClickProvision Templates.
Enter a task name, for example:Trustpoint_Update_Device1.
In the device selection step, selectone Cisco IOS XE device only.
ClickNext.
Review the applicable template assignment.
Since no template variables are used, continue to the next step.
On the Preview screen, verify that the commands are correct.
ClickDeploy Now.
7. Confirm Deployment Status in Catalyst Center:
Navigate toActivities > Tasks.
Verify that the deployment completed successfully.
If the deployment failed, review the task details and error output before retrying.
8. Repeat for additional devices
Repeat this deployment process for each Cisco IOS XE device individually.
Use a separate task name for each device to simplify tracking and troubleshooting.
9. Verify the configuration on the device
After deployment completes, connect to the device's CLI and run:
show run | sec crypto pki trustpoint sdn-network-infra-iwan
Confirm that the running-configuration includes these lines:
crypto pki trustpoint sdn-network-infra-iwan
hash sha512
The SMU (Software Maintenance Update) is available underSystem > Software Managementin the Catalyst Center GUI, If you are unable to see the SMU, please open a TAC service request and provide your Member ID.
device# show crypto pki certificates verbose sdn-network-infra-iwan
Sample Output:
Certificate
Status: Available
Version: 3
Certificate Serial Number (hex): 18831279321B12FA
Certificate Usage: General Purpose
Issuer:
cn=sdn-network-infra-ca
Subject:
Name: device.example.net
cn=C9300-48U_SN12345678_sdn-network-infra-iwan
hostname=device.example.net
Validity Date:
start date: 11:39:55 cdt Jul 10 2025
end date: 11:39:55 cdt Jul 16 2025
renew date: 06:51:54 cdt Jul 15 2025
...
Note: If the end date and renew date are before the current date on the device then the certificate has expired.
Sample Output:
Device# show logging %PKI-2-CERT_RENEW_FAIL: Certificate renewal failed for trustpoint sdn-network-infra-iwan
Reason : Failed to get ID certificate from CA server sdn-network-infra-iwan:Certificate renewal failed.
Sample Output:
Device#show tel con all
Telemetry connections
Index Peer Address Port VRF Source Address State State Description
-----------------------------------------------------------------------------------------
36284 x.x.x.x 25103 0 x.x.x.x Connecting Connection request made to transport handler
Note: In this example the telemetry connection is not up, just in the Connecting state.
When the device certificate has already expired and the device is in a degraded state, perform these two steps:
Step 1: Force push telemetry from the Catalyst Center GUI
Step 2: Update the hash algorithm for the trustpoint tosha512 on the device:
crypto pki trustpoint sdn-network-infra-iwan
no hash sha256
hash sha512
Does installing the SMU fix an already impacted system, or is it preventive?
The SMU is a preventive fix and must be installed before the issue occurs. If the issue has already occurred, installing the SMU does not automatically clear the issue. To recover existing failed systems review the additional information section.
| Revision | Publish Date | Comments |
|---|---|---|
2.0 |
28-Apr-2026
|
Initial Release |
1.0 |
08-Apr-2026
|
Initial Release |