Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
I have been working to install a private SSL on our new APC UPS, and keep hitting a road block. I have been able to generate a CSR and private key via the APC Network Management Card Security Wizard CLI 1.0.1, but when I try to use the --import function, I receive the following:
Unhandled Exception: cryptlib.CryptException: -3: Bad argument, parameter 3 at NMCSecurityWizardCLI.Program.ImportSignedCSR(String sCertFile, String sKeyFile, String sOutFile) at NMCSecurityWizardCLI.Program.Main(String[] args)
I've found a number of forum posts that seem to point towards the APC Network Management Card Security Wizard v1.0.4 (GUI) being the solution, so I was wondering if I might get access to that, or perhaps work with someone on another way. Please see below for relevant posts
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-03-0701:30 AM
When encountering issues importing a private SSL certificate to a Network Management Card (NMC), it's essential to follow specific steps to troubleshoot and resolve the problem. Here's a guide to help you solve this issue:
Verify Certificate Format: Ensure that the SSL certificate and the private key are in the correct format. NMC typically requires certificates to be in PEM format. If your certificate is in a different format, you may need to convert it using tools like OpenSSL.
Check Certificate Chain: Make sure that your SSL certificate includes the entire certificate chain, including any intermediate certificates or the root CA certificate. Without the complete chain, the NMC may not be able to verify the certificate's authenticity.
Confirm Compatibility: Verify that the SSL certificate is compatible with the version of firmware running on the NMC. Older firmware versions may have limitations or requirements regarding SSL certificate formats or encryption algorithms.
Review Import Procedure: Double-check the documentation or user manual for your specific NMC model to ensure that you're following the correct procedure for importing SSL certificates. Some NMCs may have slightly different processes or requirements.
Check for Errors: Review any error messages or logs generated during the import process. These messages can provide valuable information about what went wrong and help you diagnose the issue more effectively.
Try Different Methods: If you're encountering issues with one method of importing the SSL certificate (e.g., web interface), try using an alternative method (e.g., command-line interface or SNMP). Different methods may have varying levels of reliability or compatibility.
Restart NMC: Sometimes, simply restarting the NMC can resolve issues with certificate imports. Try power cycling the device or restarting the management services to see if it makes a difference.
By following these steps, you should be able to diagnose and resolve issues with importing private SSL certificates to your NMC.