NMC2 self-signed certificate expired -

Search FAQs

You are currently viewing the content available in Vietnam. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.

NMC2 self-signed certificate expired - "connection reset" in Web UI

Issue:
NMC2 devices with a self-signed SSL certificate refuse a web connection. Logging in via serial/telnet/SSH still work.

Product Lines:

Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH, AP9635/AP9635CH

Devices with an embedded Network Management Card 2 include (but are not limited to): 2G Metered/Switched Rack PDUs (AP86XX, AP88XX, AP89XX), AP44xx RackATS, Netbotz 250, Certain Audio/Video Network Management Enabled products.

Solution:
To fix this issue, a device would need to be upgraded to v7.0.4. After upgrading, the SSL certificate will need to be deleted from the NMC; there are a few methods that can be used:

Deleting the certificate via Web UI

Navigate to Configuration --> Network --> Web --> SSL Certificate
Select "remove", then "apply"
Reboot the NMC

Deleting the certificate via CLI

Open a Telnet/SSH session
Enter "cd ssl"
Enter "dir", should return with a file that has a .p15 extension
Delete the file with the command "delete <filename>.p15"
Reboot the NMC with the "reboot" command

Deleting the certificate via FTP

Open an FTP session
Enter "cd ssl"
Enter "dir", should return with a file that has a .p15 extension
delete the file with the command "delete <filename>.p15"
Close the FTP session, then reboot the NMC manually.

If a user wishes to remain on a firmware revision older than v7.0.4, the certificate can be deleted and the card rebooted to fix the issue, however the new certificate generated will be valid for only 1 year - the process would need to be repeated every year.