NetApp ONTAP 9.5 Failed to add the Cserver record in RDB The certificate has expired

The other day I had a few NetApp FAS units to setup and each one had shipped with ONTAP 9.5. The initial install on the first unit went as per normal but when it came to the cluster setup it failed with the following error – Failed to add the Cserver record in RDB . The certificate has expired.

What was worse is the fact that the certificate had expired before I even opened the box so this was always going to happen. Turns out there is a known issue with these units that were shipped with ONTAP 9.5 as the certificate was set to expire on Jul 6, 2019. Luckily there is a way to get around it.

Below is a quick run through on how to set the initial management IP’s on each node and apply the fix which will allow you to continue with the cluster setup.

Go through setting the disk tray IDs as per normal procedure prior to starting the configuration

Connect the usb console cable to Node A and use the following settings in Putty (115,200 baud with N-8-1)

Once connected start the wizard as per normal. I have added in some example IP’s below to show the process,

Welcome to the cluster setup wizard.

You can enter the following commands at any time:

“help” or “?” – if you want to have a question clarified,

“back” – if you want to change previously answered questions, and

“exit” or “quit” – if you want to quit the cluster setup wizard.

Any changes you made before quitting will be saved.

You can return to cluster setup at any time by typing “cluster setup”.

To accept a default or omit a question, do not enter a value.

This system will send event messages and periodic reports to NetApp Technical

Support. To disable this feature, enter autosupport modify -support disable

within 24 hours.

Enabling AutoSupport can significantly speed problem determination and resolution should a problem occur on your system.

For further information on AutoSupport, see: http://support.netapp.com/autosupport/

Type yes to confirm and continue {yes}: yes

Enter the node management interface port [e0M]: Enter

Enter the node management interface IP address: 10.20.30.11

Enter the node management interface netmask: 255.255.255.0

Enter the node management interface default gateway: 10.20.30.1

A node management interface on port e0M with IP address 10.20.30.11 has been created.

Use your web browser to complete cluster setup by accessing https://10.20.30.11

Otherwise, press Enter to complete cluster setup using the command line interface:  Enter

The next line is where we need to exit out of the wizard and make the changes

Do you want to create a new cluster or join an existing cluster? {create, join}:   Hit CTRL + C here to cancel the setup and modify the date!

Exiting the cluster setup wizard. Any changes you made have been saved.

The cluster administrator’s account (username “admin”) password is set to the system default.

Next login with the username admin and since this is a new install you won’t be prompted for a password. Then type cluster date modify -date 07/01/2019 19:00:00 and hit enter to change the date back to July 1st. Lastly type cluster date show to confirm it has changed. Example of this part below,

login: admin

******************************************************

* This is a serial console session. Output from this *

* session is mirrored on the SP console session.     *

******************************************************

::> cluster date modify -date 07/01/2019 19:00:00

::> cluster date show

Node      Date                      Time zone

——— ————————- ————————-

localhost 7/1/2019 19:01:22 +00:00  Etc/UTC

From here you should see that the date has been set back to the 1st of July.

Now it’s time to connect the usb serial cable to Node B and repeat the process.

Node B setup

You can enter the following commands at any time:

“help” or “?” – if you want to have a question clarified,

“back” – if you want to change previously answered questions, and

“exit” or “quit” – if you want to quit the cluster setup wizard.

Any changes you made before quitting will be saved.

You can return to cluster setup at any time by typing “cluster setup”.

To accept a default or omit a question, do not enter a value.

This system will send event messages and periodic reports to NetApp Technical

Support. To disable this feature, enter autosupport modify -support disable

within 24 hours.

Enabling AutoSupport can significantly speed problem determination and resolution should a problem occur on your system.

For further information on AutoSupport, see: http://support.netapp.com/autosupport/

Type yes to confirm and continue {yes}: yes

Enter the node management interface port [e0M]: Enter

Enter the node management interface IP address: 10.20.30.12

Enter the node management interface netmask: 255.255.255.0

Enter the node management interface default gateway: 10.20.30.1

A node management interface on port e0M with IP address 10.20.30.12 has been created.

Use your web browser to complete cluster setup by accessing https://10.20.30.12

Otherwise, press Enter to complete cluster setup using the command line interface:  Enter

Do you want to create a new cluster or join an existing cluster? {create, join}:   Hit CTRL + C here to cancel the setup and modify the date!

Exiting the cluster setup wizard. Any changes you made have been saved.

The cluster administrator’s account (username “admin”) password is set to the system default.

Once again login with the username admin and since this is a new install you won’t be prompted for a password. Then type cluster date modify -date 07/01/2019 19:00:00 and hit enter to change the date back to July 1st. Lastly type cluster date show to confirm it has changed. Example of this part below,

login: admin

******************************************************

* This is a serial console session. Output from this *

* session is mirrored on the SP console session.     *

******************************************************

::> cluster date modify -date 07/01/2019 19:00:00

::> cluster date show

Node      Date                      Time zone

——— ————————- ————————-

localhost 7/1/2019 19:01:22 +00:00  Etc/UTC

 

Now you should be good to continue with the cluster setup via the gui or console, enjoy!

LINKEDIN

Related Post

Leave a Reply

Your email address will not be published. Required fields are marked *

LINKEDIN