Open

by Calnex

1. Download the patch file into your downloads folder from the email you received or other mechanism e.g. AWS download.

2. Start a command shell or terminal and cd to your downloads folder on your computer.

3. Use scp, sftp (or filezilla or similar) to transfer the patch kit file to the NE-ONE.
   
   The example below shows this using scp, from the command prompt and assumes that the patch kit you received is called ne-one-patch-202204082031.
   
   NOTE Substitute your actual patch kit file name for ne-one-patch-202204082031 in this an all other examples below.
   
   scp -p ne-one-patch-202204082031 <username>@<your ne-one ip address>:
   
   [You’ll be prompted for the <password>]
   
   The file is now in the home folder of the <username> user /home/itrinegy
   
   

4. log in to the console of your NE-ONE :

Open

5. check whether you already have a patches folder under the /ippe folder, and whether that folder has any contents (a previous patch):
   
   <username>@NE-ONE:~$ ls -lR /ippe/patches
   /ippe/patches:
total 0
   
   In the above it finds the patches folder with no contents, just what we need.

   1. but you may be told the patches folder does not exist e.g.
      ls: cannot access '/ippe/patches': No such file or directory
      In which case create it like this

6. copy the ne-one-patch-202204082031 file to the patches folder

7. go the the patches folder:

8. expand the ne-one-patch-202204082031 tarball into this folder:

<username>@NE-ONE:/ippe/patches$ sudo tar -xvzf ne-one-patch-202204082031

Some files will be shown - this is just an example:

./bin/ipperte

./ext/Default

./ext/Expression

./ext/Generate

./ext/Labs

./ext/Service

./ext/Soft_Port

9. check that all the files are present in the patches folder, for example:

…

NOTES:

I) The dates and times may vary a little due to timezone and clock differences, the sizes should be the same as above

II) The files won’t be exactly the list above, it depends what’s in the patch

10. if the file ipperte has been supplied make sure it has the correct protections:

<username>@NE-ONE:/ippe/patches$ sudo chmod 555 /ippe/patches/bin/ipperte

NOTE - don’t worry if you’re told the file does not exist - it’s not part of all patches

11. The patch files are in the correct place. We can now restart NE-ONE’s engine

12. check that the patching has taken place properly by looking at the ippe.log file for patching messages, corresponding to your approximate current time (Note: log file times are in UTC)

<username>@NE-ONE:/ippe/patches$ grep -Eia 'ippe version|patching' /ippe/logs/ippe.log

…

2024-05-17 17:02:25.379402: PATCHING /ippe/ext/Labs
2024-05-17 17:02:25.384021: PATCHING /ippe/ext/Soft_Port
2024-05-17 17:02:25.386660: PATCHING /ippe/ext/Expression
2024-05-17 17:02:25.388602: PATCHING /ippe/ext/Generate
2024-05-17 17:02:25.390209: PATCHING /ippe/ext/Service
2024-05-17 17:02:25.391422: PATCHING /ippe/ext/Default
2024-05-17 17:02:25.394197: PATCHING restarting to patch ipperte (2024.05.000000 202405171503)
2024-05-17 17:02:25.394206: PATCHING Restarting with command: [/ippe/patches/bin/ipperte -z -d]
2024-05-17 17:02:25.450164: PATCHING /ippe/bin/ipperte from /ippe/patches/bin/ipperte
2024-05-17 17:02:25.769547: PATCHING Restarting with command: [/ippe/bin/ipperte -x -d]
2024-05-17 17:02:25.782195: PATCHING All patches have been applied
2024-05-17 17:02:25.782745: IPPE Version: 2024.05.000000

In the above output we’re looking for the PATCHING statements immediately above the last IPPE Version: - these should correspond to the files supplied.

That’s it patch (hotfix) applied,

Now refresh your GUI (<crtl-shift-R>) as it is cached in your bowser.