Network Management

I have an Airwave deployment (primary and failover) that we installed a certificate on in order to access it using a valid DNS name,

 

When upgrading the servers is there anything I need to do to make sure the certificate is there after the upgrade?

 

I am going from 7.6.4 -> 7.7.2 -> 7.7.11

 

 

Did you use the Aruba recommended method when you installed it (creating the pointer file to the real certificate) or did you just replace the cert and private key in the certs folder?

Ah Tim, now you;re making me question myself...lol

I followed the following kb article but I need to double check the server as I know I ran into problems that night when I did.

https://arubanetworkskb.secure.force.com/pkb/articles/FAQ/How-to-install-your-own-certificate-on-AMP-versions-7-2-4-and-greater.

Looks l did the symlink.
[root@mlixwibmgofams ssl.crt]# pwd
/etc/httpd/conf/ssl.crt
[root@mlixwibmgofams ssl.crt]# ls -al
total 12
drwxr-xr-x 2 root root 4096 Mar 18 17:59 ./
drwxr-xr-x 4 apache apache 4096 Mar 18 17:59 ../
lrwxrwxrwx 1 root root 87 Mar 18 17:59 server.crt -> /var/airwave/custom/ssl-certs/mlixwibmgofams_americas_net_cert_root_interm.pem

So it *should* leave the certs since they're in the custom folder. You may have to recreate the pointer files when you get into 7.7

ya I hope not, but ill post here what happens on the 4th.

Well started the upgrade and i'm on the phone with TAC...my window timed out and was left at this:

STEP 5: Installing upgrade.

and my upgrade log shows

Starting update_db at Wed Jun 4 21:24:58 2014
make[1]: *** [updatedb] Hangup
make: *** [upgrade] Hangup

that's it.

We will see what they say..

I KNEW IT!!

Good ol' root; make fixed the issue

I also didn't have to redo the symlinks.