Ncsw10301 Unable To Download ((free)) The Image From Cisco.com Invalid Metadata Trans-id • Simple

notes that affected releases would stop downloading images after April 26, 2024. Recommended Workarounds

Example: iosxe-17.9.1a.SPA.bin . This will help later when forcing a fresh metadata fetch.

SSH into your DNAC appliance (maglev user) and run:

is a known issue typically encountered in Cisco Catalyst Center (formerly DNA Center) during Software Image Management (SWIM) operations. While the main software image may download successfully, the associated ISSU Compatibility Matrix (comp_matrix.xml) fails due to this metadata error. Review of Error NCSW10301 notes that affected releases would stop downloading images

In Catalyst Center, navigate to Design > Image Repository and use the Import function to upload the file from your local machine.

Though less common, DNA Center’s SWIM feature can throw similar Crosswork-related errors when backend services fail to validate the image signature.

If the automated SWIM process continues to fail, use these manual steps to bypass the API error: SSH into your DNAC appliance (maglev user) and

The trans-id ensures that:

NCS often caches image metadata to reduce repeated queries. If the cache is not refreshed before the trans-id expires (typically 15–60 minutes), subsequent download attempts fail.

When the switch throws the invalid metadata trans-id error, it means the automated process broke down due to one of the following reasons: 1. Cisco Smart Account or CCO ID Sync Issues Though less common, DNA Center’s SWIM feature can

To resolve the NCSW10301 error, work through these troubleshooting steps sequentially, starting with the easiest workarounds. Step 1: Verify Direct Connectivity and DNS

: Specifically, the download of the ISSU Compatibility Matrix ( comp_matrix.xml ) may fail even if the image itself is retrieved. Service Registration

Sometimes the session token between Catalyst Center and your Smart Account becomes stale.

The NCSW10301 error is frustrating because it seems like a simple download failure, but it actually points to a deeper metadata integrity check. The good news? It’s rarely a network or permissions problem—it’s almost always a cache or token mismatch.