SSMC 3.6 3par Warning: The certificate is not yet valid.

[sharizman]

Hi there,

1 of my storage certificate is expired. I've already create self-signed certificate at 3par CLI. Copy the .pem and put add the certicicate in the SSMC 3.6 manage certificate.

At SSMC 3.6 admin console there is warning certificate acceptance needed for that box.

Please help me.

[Dardan · Accepted solution]

After you have renewed your StoreServ's certificate, you will need to accept it in your SSMC portal.

1) Navigate to SSMC
2) Check the box "Administrator Console"
3) Log in with ssmcadmin userID and password
4) Finally, accept the array's certificate and you should be good.

[sharizman]

Thank you.

[credmond]

When I attempt to accept the new cert, the Accept and Cache button is greyed out, so I am not able to accept.

The preceding warning states "Warning: The certificate is not yet valid."

Has anyone seen this before?  Any ideas??

Thanks in advance!

[sbhat09]

Hello @credmond,

Till when your certificate is valid? Please find the certificate validity details from 'showcert' command.

Regards,

Srinivas Bhat

[credmond]

@sbhat09 - the accept button eventually became active.  Turns out there was time clock mismatch between the SSMC and the arrays, however SSMC still wont connect.

The certs were re-issued today, and are good for 3 years (the default).  First connection attempt after regenerating certs did recognize that the new certs had to be Accepted.  However, after accepting the certs it then/now displays "Unable to Connect".

Note:  

First 7400 array
Enddate
Dec 21 21:27:55 2024 GMT 

2nd 7400 array
Enddate 
Dec 21 21:23:07 2024 GMT 

(output redacted to not publish additional info from command).

SSMC appliance was upgraded from v3.7.

[sbhat09]

@credmond, What is the 3PAR OS on your 7400s?

Srinivas Bhat

[credmond]

@sbhat09 the 7400 OS versions are 3.2.1 (MU2).  Thanks!

[sbhat09]

Hello @credmond 

3.2.1 is more than 6-7 years old and it has reached EoSL long back.
I strongly recommend you to upgrade to any of the supported versions (3.2.2MU6 or 3.3.1 or 3.3.2).
The latest SSMC v3.8.2.1 supports 3PAR OS 3.2.2 MU4 or above.
Your current version of 3PAR OS (3.2.1MU2) is supported by SSMC upto v3.6. But that doesn't serve the purpose if you are looking to safeguard from Log4j vulnerability.

Here is the latest SSMC support matrix for your reference - https://h20272.www2.hpe.com/spock/utility/document.aspx?docurl=Shared%20Documents/sw/array_3par/hpe_3par_ssmc.pdf

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[credmond]

Thanks @sbhat09  - I understand we are running an old version of microcode, but my previous version of SSMC was 3.7 and it was able to connect to the arrays (and you stated our code level was only officially supported up to 3.6).

Can you confirm with 100% certainty that 3.8.2.1 is not able to connect to the arrays by design?  and I don't mean in terms of what is officially supported, given that 3.7 was newer than the last officially supported version and still worked.   Thanks!