Security

Reply
Valued Contributor I

Clustered Clearpass 6.7 upgrade - painless or painfull ?

Hi,

I've been runnnig CPPM 6.7 on a standalone server since it came out and that upgrade "just worked" Now want to upgrade a 2 node cluster to 6.7. Always been suspicious of the GUI cluster upgrade tool since we had a major upgrade failure when the GUI way of doing it 1st came out ( that was a long time ago I should point out)

 

So ... 2 nodes , 1 hardware 1 VM 5K servers running 6.6.8 painless or painfull ?

 

Rgds

Alex

 

Re: Clustered Clearpass 6.7 upgrade - painless or painfull ?

I have upgraded a few customers now and no issues thus far

just make sure you follow the instructions on the release notes and it should be a straight forward upgrade.
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Valued Contributor I

Re: Clustered Clearpass 6.7 upgrade - painless or painfull ?

Release notes could mention to make sure that the cluster password doesn;t have @ and other special characters in it. Not applicable to me but found that in the help pages on the server. Not mentioned in the release notes

 

A

Valued Contributor I

Re: Clustered Clearpass 6.7 upgrade - painless or painfull ?

o.k. so after I remembered about the VM ware delete network interfaces and recreate them, the cluster upgrde tool seemed to work .... in that I had lots . of green lights saying everything was done ... except the master publisher still thought the secondarty was disabled. 

 

I then tried logging onto the secondary on the cli and that worked with appadmin /pw

 

logged in via the GUI and the secondary was sitting there thinking it was a standalone machine

 

Currently restoring secondary . from the on disk backup file, config/session and cluster info to see if that brings it back.

Valued Contributor I

Re: Clustered Clearpass 6.7 upgrade - painless or painfull ?

Well, now in situation where my master publisher says its a master with a secondary that is disabled. ......

 

And the sedondary says its in a cluster ..... with the ream master publisher that is a disabled secondary .....

 

Dropping (disabled) secondaries in both clusters allowed me to join the old secondary back into the real cluster

 

Sigh!

Glad this isn't our production cluster ... yet

 

A

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: