Deploying or upgrading Cisco ISR 1000 series routers to Cisco IOS XE 17.15.x introduces stricter cryptographic enforcement that can silently break existing PKI-based IPsec VPN deployments.
When using Simple Certificate Enrollment Protocol (SCEP) against a Microsoft Network Device Enrollment Service (NDES) server, routers running 17.15.x may fail to enroll their identity certificates – leaving IKEv2 rsa-sig tunnels completely down.
On the surface, the failure looks like a generic VPN or enrollment issue. The router successfully authenticates and downloads the issuing CA certificate, yet it never obtains its own operational identity certificate, causing Phase 1 IKEv2 authentication (authentication local rsa-sig) to abort and keeping the IPsec tunnel offline.
If you trigger a manual enrollment (crypto pki enroll) from a standard SSH/VTY session without debug messaging enabled, the router only displays a high-level enrollment failure without explaining why the request was aborted.
To see what the router’s cryptographic engine is actually doing during the SCEP handshake, you need to enable PKI transaction and message debugging.
Because SSH/VTY sessions route debug output to the internal logging buffer rather than the terminal by default, make sure you run terminal monitor from privileged EXEC mode (#) before triggering enrollment:
terminal monitor
debug crypto pki transactions
debug crypto pki messages
With debug messaging active, trigger the enrollment again (ensuring enrollment mode ra is configured under the trustpoint):
crypto pki enroll <TRUSTPOINT_NAME>
Answer yes when prompted to request the certificate from the CA. Immediately after the router prints % Certificate request sent to Certificate Authority, the debug messaging exposes the real reason for the failure:
%PKI-3-CSDL_COMPLIANCE_KEY_SIZE_FAIL: The RSA bit key size 1024 is a weak key size used in a certificate under trustpoint <TRUSTPOINT_NAME> and is non compliant
%PKI-3-CSDL_COMPLIANCE_KEY_SIZE_FAIL: The RSA bit key size 1024 is a weak key size used in a certificate under trustpoint <TRUSTPOINT_NAME> and is non compliant
%PKI-2-CERT_ENROLL_FAIL: Certificate enrollment failed for trustpoint <TRUSTPOINT_NAME>
Reason : Failed to create PKCS7 PKCS request
(Tip: If packet policers or SSH buffer limits truncate live screen output, you can pull the captured debug trace directly from the router’s buffer using show logging | include PKI. Always run undebug all once you have captured the logs).
At first glance, %PKI-3-CSDL_COMPLIANCE_KEY_SIZE_FAIL points toward an outdated key on the router itself. However, standard local checks come back clean:
The critical clue from the debug output is that %PKI-3-CSDL_COMPLIANCE_KEY_SIZE_FAIL prints twice in a row right before Failed to create PKCS7 PKCS request.
When enrollment mode ra is configured on a Cisco trustpoint, SCEP executes a multi-step handshake:
In many enterprise Windows PKI environments built years ago, the CEP Encryption and Exchange Enrollment Agent templates on the Active Directory Certificate Authority were issued with 1024-bit RSA keys.
In earlier software releases (such as IOS XE 17.9.x), Cisco logged a non-fatal warning for 1024-bit RA certificates and allowed the enrollment to proceed. Starting in newer trains and enforced permanently in IOS XE 17.15.x, Cisco hardcoded Cisco Secure Development Lifecycle (CSDL) compliance rules directly into the crypto engine. Any RSA key under 2048 bits encountered anywhere in the PKCS#7 assembly causes an unconditional local abort – with no CLI toggle to bypass it.
To support IOS XE 17.15.x, the Windows PKI must be upgraded the NDES service certificates to 2048 bits:
If your Windows PKI cannot be updated, IOS XE 17.15.x cannot be used with 1024-bit SCEP infrastructure.
Downgrading the routers to the IOS XE 17.9 Extended Maintenance train (e.g., 17.9.6a) serves as the highest available release cutoff that permits 1024-bit RA certificates. On 17.9.x, the router logs a warning during PKCS#7 creation rather than aborting, allowing automated SCEP enrollment and IKEv2 tunnels to establish normally until the PKI servers are upgraded.
Upgrading to Cisco IOS XE 17.15.x removes the safety net for legacy cryptography. Even when your router’s local keys and issuing CA certificates already meet modern 2048-bit standards, a single legacy 1024-bit Registration Authority certificate on a Microsoft NDES server will halt SCEP enrollment and keep IPsec tunnels down – with no CLI workaround available to bypass the check.
Before rolling out IOS XE 17.15.x, keep these three takeaways in mind:
See the following Cisco links that have been used to construct this article:
For more useful article please visit our knowledgebase.