This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Register Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
JoseLuisMartinM
Occasional Contributor
Occasional Contributor
‎2021-09-20 11:21 AM

IDR not upgraded to SLES12

Hi all.

Last July I proceeded to upgrade my IDR cluster, formed by 3 IDRs that are absolutely identical in (virtual) hardware: same memory, disk space, and so on.

Two of the IDRs succefully upgraded to Software Version 12.12.0.0.9 and Operating System SLES12 SP5

But the third IDR upgraded to Software Version 12.12.0.0.9 but stayed in SLES11 SP4

As I said the three machines are identical, the three had enough disk space for the upgrade to SLES12... but it just didn't happen.

Any suggestions about what to do now? Do another upgrade as usual and cross fingers? Or shall I have to follow the procedure for machines without the requirements to upgrade automatically?

Thanks

0 Likes
Reply
4 Replies
SteveWoodley
Contributor
Contributor
‎2021-09-28 06:08 AM

Hi Jose,

If the IDR's are all within the same cluster and behind a load balancer, it is actually not difficult to just redeploy the problem IDR.

When obtaining the IDR image from the cloud portal it will already be the latest software release. Once deployed and added into the existing cluster all the settings will be applied to the new IDR. 

Don't delete the IDR entry in cloud, otherwise you will need to recreate the routes and firewall rules if any are configured.

 

 

0 Likes
Reply
JoseLuisMartinM
Occasional Contributor
Occasional Contributor
‎2021-09-28 07:03 AM

Hi Steve! Do you know if there's somewhere documentation with the steps to do the redeploy? Thanks!

0 Likes
Reply
SteveWoodley
Contributor
Contributor
In response to JoseLuisMartinM
‎2021-09-28 07:31 AM

I have attached the Migration guide which might help.

If you follow the steps within 'Migrate Using Swap and Replace procedure' on page 2. 

The second point has a link to Deploying an Identity Router - Advanced Setup. The steps are below but I have added and extra part 3 (A) to just power down the existing IDR, since you can re-use the hostname and IP's.

  1. Plan your deployment using the Deployment Planning Checklist.   -- (Not required as already deployed)
  2. Add an Identity Router Using the Cloud Administration Console.    -- (Not Required as already present)
  3. Obtain the Identity Router Image.
  4. (A) Power down current IDR (The one with the upgrade issue)
  5. (For VMware) Install the Identity Router Virtual Appliance for VMware.
  6. (For Microsoft Hyper-V) Create the Identity Router Hyper-V Virtual Machine
  7. (For Amazon Web Services) Launch the Identity Router for Amazon Web Services.
  8. (For VMware and Hyper-V) Configure Initial Network Settings for On-Premises Identity Routers Using the VM Console.
  9. Configure Network Settings Using the Identity Router Setup Console.
  10. Connect the Identity Router to the Cloud Administration Console.
  11. If you are adding an identity router to an existing cluster, back up user profiles for the cluster that includes the new identity router. See Back Up Now for a Single Cluster.

Hope that helps.

🙂

    Preview file
    520 KB
    0 Likes
    Reply
    JoseLuisMartinM
    Occasional Contributor
    Occasional Contributor
    In response to SteveWoodley
    ‎2021-10-05 05:46 AM

    Finally I solved the problem yesterday, thanks to a support tech suggestion.

    A reboot of the IDR before trying again the automatic upgrade fixed it 🙂

    0 Likes
    Reply
    © 2023 RSA Security LLC or its affiliates. All rights reserved.