Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

This thread has been viewed 0 times
  • 1.  ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 03:45 PM

    I see that there is a patch for Version 5.1.0.41000 to get to 5.1.1, but my case is to move from 5.0.1.38855 to 5.1.1 and I am using the upgrade file eTIPS-x86_64-5.1.1.41874-upgrade.bin and getting to:

     

    ERROR - Setting up upgrade area failed

    ERROR - Exception performing upgrade:  Pre-install task=30-prepare-second-partition failed

    ERROR - Upgrade failed

     

    I don't see any directions and yes it looks to be release not too long ago.

     

    Thanks!

     



  • 2.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 04:13 PM

    I've just come across this too, are you using a VM environment? If so, I don't believe they run the secondary partition like the hardware appliances do so there this upgrade package doesn't work.

     

    I ended up having to build a VM machine from scratch in 5.1.0, install the patch to 5.1.1 and then restore from a backup taken from your original 5.0.1 Policy Manager.



  • 3.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 04:33 PM

    Just an FYI, the patch update instructons have an error.  It says to perform the update, use the command system update <Patch filename>.

     

    The correct command is system update -i <Patch filename>



  • 4.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 04:34 PM

    Correct, using a VM environment.  I wonder if installing the 5.1.1 and restoring the 5.0.1 backup would work. 



  • 5.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 04:36 PM

    Will the patch work on other environments besides the 5.0.1.4000?



  • 6.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 04:40 PM

    Looks like there's a patch if you're running 5.1.0.4100 and there's an upgrade image if you're running an earlier version.  So, I believe the patch is only going to work if you're on 5.1.0.4100.

     

    I would backup what you have, build a 5.1.0.4100 VM, restore your data, then apply the patch.



  • 7.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 11:38 PM

    Yes, this will work.



  • 8.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted Jun 06, 2012 09:44 AM

    I just want to clarify the upgrade procedure from a clearpass policy manager VM on version 5.0.1.38855 to 5.1.1.

     

    From reading the above am I understanding it that I will need to:

    • backup the policy manager settings
    • download 5.1.0
    • create a new policy manager instance
    • import the backed up setting
    • re-import certificates
    • install the 5.1.1 patch

    The CPPM 5.1.1 Upgrade instructions documentation make it seem MUCH easier.

     

    Not impressed if I have to do this I'm afraid.



  • 9.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted Jun 11, 2012 11:23 AM

    What I did to accomplish:

     

    • backup the policy manager settings
    • download 5.1.1 vm ovf
    • import the backed up setting
    • re-import certificates
    •  re-auth AD
    • Get new license key from Aruba as TAC said I needed one when changing versions.


  • 10.  RE: ClearPass Policy Manager 5.0.1.38855 upgrade to 5.1.1

    Posted May 31, 2012 05:20 PM
    Yeah, I had to upgrade first and then update with the patch. This took me from 5.0.1 to 5.1.0 and then the patch took me to 5.1.1. My restore worked but I did have to import the server certificate again for some reason, so make sure you export that too just in case!
    Also, we have a Guest Manager installation which writes information to the Policy Manager Guest User Repository, but once updated this is written to the Onboard repository. So if you are using Guest User Repository in any service definitions in this way you may need to alter these.