Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Update the OS on the Nodes

The Routing Director OVA is pre-packaged with all the utilities, OS, and software required to create the VMs. The VMs are created with Ubuntu 24.04.4 LTS (Noble Numbat) Linux base OS. For existing installations where the Routing Director version has been upgraded, you must update the base OS to maintain the security, stability, performance, and compatibility of the Kubernetes cluster. The upgrade process is not complete until you update the base OS. Juniper provides you with the required OS update file to enable you to update the OS on your node VMs. The OS update functionality in Routing Director includes the following updates:

  • Linux kernel update

  • OpenSSL or OS security update

  • Any third-party packages required by Routing Director

  • All packages that are part of the base OS

To update the OS, perform the following steps:

  1. Download the routing-director_2.9_os-upgrade_date.tgz and routing-director_2.9_os-upgrade_date.tgz.psig files from the Juniper Software Download site on to your computer or local installer VM.
  2. Log in to any one of the Routing Director deployment cluster nodes as the root user.
  3. Type exit to exit Deployment Shell to the Linux root shell.
  4. Copy the routing-director_2.9_os-upgrade_date.tgz and routing-director_2.9_os-upgrade_date.tgz.psig files to the /root/epic/temp/ folder on your cluster node.
  5. Update the OS on the current node using the OS update files.

    The process takes between 30 and 60 minutes to complete depending on the size of the updated packages. Once the update is complete, the OS versions on the other nodes of the cluster are also automatically updated.

    If the update is interrupted, rerun the update script. The script checks the update status of each node. If a node has already been updated, it reports that no packages require updating and proceeds to the next node.

  6. Verify that the node is healthy and operational. Log in to Deployment Shell using the cli command. and check cluster health.
    If the cluster health is GREEN, the updated nodes must be rebooted to complete the update process.
  7. Log in to any other node in the cluster. When the kernel is updated you will see a welcome message similar to the following on the node.
  8. Reboot the cluster.
    After the nodes are rebooted, we recommend that you wait between 10 to 15 minutes for all nodes and services to come back online.
  9. Verify that cluster nodes are back online by checking that all pods are in Running state.
  10. Verify that the cluster is healthy and operational and that the cluster health status is GREEN.
  11. Verify the OS updates.

    • Log in to all the nodes to ensure that the welcome message displays the upgraded kernel version.

      Additionally, ensure that the welcome message does not state that a system restart or a reboot for kernel updates is required.

    • (Optional) You can also verify that the update completed successfully by checking the /var/log/apt/history.log log file for the timestamp of the most recent update and the list of updated packages.

  12. Delete the downloaded OS update and signature files after you have verified the updates on all the nodes in the cluster.

After you have updated the base OS, proceed to perform the post cluster upgrade tasks. See Post Cluster Upgrade Tasks.