Difference between revisions of "Node Deployment Guide"
From Internet Computer Wiki
(Direct people to use latest IC-OS installer) |
m |
||
| Line 3: | Line 3: | ||
The physical machine is expected to be racked and stacked according to its respective manual. | The physical machine is expected to be racked and stacked according to its respective manual. | ||
| − | To complete these steps, you are expected to by physically present with your machine(s). Once you successfully | + | To complete these steps, you are expected to by physically present with your machine(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel. |
If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]]. | If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]]. | ||
| − | + | ==1. Choose onboarding path (HSM vs. no HSM)== | |
| − | |||
| − | == 1. Choose onboarding path (HSM vs no HSM) == | ||
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes. | If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes. | ||
If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.''' | If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.''' | ||
| − | == 2. Obtain requirements == | + | ==2. Obtain requirements == |
| − | * A USB (3.0 speed that can hold at least 4GB) to put the image file on. | + | *A USB (3.0 speed that can hold at least 4GB) to put the image file on. |
| − | ** Faster USBs will allow the process to go much faster. | + | **Faster USBs will allow the process to go much faster. |
| − | * The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) | + | *The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) |
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades. | * It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades. | ||
| − | == 3. Download installation image == | + | == 3. Download installation image== |
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases]. | Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases]. | ||
*Note that you should always use a release that is less than 6 weeks old in order to ensure that your node can keep up with the blockchain. | *Note that you should always use a release that is less than 6 weeks old in order to ensure that your node can keep up with the blockchain. | ||
| − | == 4. Verify checksum and unarchive file == | + | == 4. Verify checksum and unarchive file== |
| − | === Mac OS X === | + | ===Mac OS X === |
| − | # Open the Terminal and type: | + | #Open the Terminal and type: |
| − | #: <syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.gz</syntaxhighlight> | + | #:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.gz</syntaxhighlight> |
| − | # Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]]. | + | #Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]]. |
| − | #: Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight> | + | #:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight> |
| − | === Linux / Ubuntu === | + | ===Linux / Ubuntu=== |
| − | # Open the Terminal and type: | + | #Open the Terminal and type: |
| − | #: <syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.gz</syntaxhighlight> | + | #:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.gz</syntaxhighlight> |
| − | # Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]]. | + | #Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]]. |
| − | #: Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight> | + | #:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight> |
| − | === Windows === | + | ===Windows=== |
| − | # Open PowerShell and type: | + | #Open PowerShell and type: |
| − | #: <syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.gz</syntaxhighlight> | + | #:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.gz</syntaxhighlight> |
| − | # Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]]. | + | #Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]]. |
| − | #: Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.gz</syntaxhighlight> | + | #:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.gz</syntaxhighlight> |
| − | == 5. Create Bootable USB Stick == | + | ==5. Create Bootable USB Stick == |
| − | === Mac OS X === | + | ===Mac OS X=== |
# Open the Terminal and type: | # Open the Terminal and type: | ||
| − | #:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight> | + | #:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight> |
| − | # All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive: | + | #All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive: |
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight> | #:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight> | ||
| − | # The file path is an example. Use the absolute path to the downloaded image. '''Warning:''' You risk losing your own data if you specify a wrong device. | + | #The file path is an example. Use the absolute path to the downloaded image. '''Warning:''' You risk losing your own data if you specify a wrong device. |
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command: | #:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command: | ||
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight> | #:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight> | ||
| − | === Linux / Ubuntu === | + | === Linux / Ubuntu=== |
| − | # Open the Terminal and type | + | #Open the Terminal and type |
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight> | #:<syntaxhighlight lang="shell">blkid</syntaxhighlight> | ||
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive: | # All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive: | ||
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight> | #:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight> | ||
| − | # Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. '''Warning:''' You risk losing your own data if you specify a wrong drive. | + | #Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. '''Warning:''' You risk losing your own data if you specify a wrong drive. |
| − | #:<syntaxhighlight lang="shell">sudo dd if=~/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight> | + | #:<syntaxhighlight lang="shell">sudo dd if=~/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight> |
| − | === Windows === | + | ===Windows=== |
| − | # Download and install [https://rufus.ie/en/ Rufus Portable] | + | #Download and install [https://rufus.ie/en/ Rufus Portable] |
| − | # Start Rufus | + | #Start Rufus |
| − | # Select the USB stick under device and select the previously downloaded IC-OS disk image and press start | + | #Select the USB stick under device and select the previously downloaded IC-OS disk image and press start |
| − | #: [[File:05.png|480px|screenshot]] | + | #:[[File:05.png|480px|screenshot]] |
| − | # You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK | + | #You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK |
| − | #: [[File:06.png|480px|screenshot]] | + | #:[[File:06.png|480px|screenshot]] |
| − | #: [[File:07.png|480px|screenshot]] | + | #:[[File:07.png|480px|screenshot]] |
# The "Ready" bar will go from left to right as it completes. | # The "Ready" bar will go from left to right as it completes. | ||
| − | == 6. Add configuration == | + | ==6. Add configuration== |
| − | === A. Open Config.ini in a text editor === | + | ===A. Open Config.ini in a text editor=== |
| − | ==== '''Mac OS X''' ==== | + | ===='''Mac OS X'''==== |
| − | # Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again. | + | #Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again. |
#:[[File:mac_01.png|580px|screenshot]] | #:[[File:mac_01.png|580px|screenshot]] | ||
| − | # Double-click <code>config.ini</code> to open it in TextEdit. | + | #Double-click <code>config.ini</code> to open it in TextEdit. |
===='''Linux'''==== | ===='''Linux'''==== | ||
| − | # Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again. | + | #Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again. |
#:[[File:linux_01.png|580px|screenshot]] | #:[[File:linux_01.png|580px|screenshot]] | ||
| − | # Double-click <code>config.ini</code> to open it in KWrite. | + | #Double-click <code>config.ini</code> to open it in KWrite. |
| − | ==== '''Windows''' ==== | + | ===='''Windows'''==== |
| − | # Open the Disk Management utility with a right click on the Start menu | + | #Open the Disk Management utility with a right click on the Start menu |
#:[[File:09-b.png|300px|screenshot]]#: | #:[[File:09-b.png|300px|screenshot]]#: | ||
| − | # Right click the CONFIG partition | + | #Right click the CONFIG partition |
# Select Change drive letter or paths... | # Select Change drive letter or paths... | ||
#:[[File:10-b.png|780px|screenshot]] | #:[[File:10-b.png|780px|screenshot]] | ||
# Select any letter from the drop-down list | # Select any letter from the drop-down list | ||
#:[[File:11-b.png|480px|screenshot]] | #:[[File:11-b.png|480px|screenshot]] | ||
| − | # Click OK. | + | #Click OK. |
| − | # You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file | + | #You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file |
#:[[File:12-b.png|780px|screenshot]] | #:[[File:12-b.png|780px|screenshot]] | ||
| − | # Click on Edit to open it. | + | #Click on Edit to open it. |
| − | === B. Edit Config.ini === | + | ===B. Edit Config.ini=== |
| − | # Insert your IPv6 prefix, subnet and gateway. | + | #Insert your IPv6 prefix, subnet and gateway. |
#:[[File:Edit config ini.png|580px|screenshot]] | #:[[File:Edit config ini.png|580px|screenshot]] | ||
| − | #:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits. | + | #:*The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits. |
| − | #:* For example, a valid prefix could look like this: <code>2a00:fb01:400:100</code> | + | #:*For example, a valid prefix could look like this: <code>2a00:fb01:400:100</code> |
#:*'''Important:''' | #:*'''Important:''' | ||
| − | #:** The prefix should not have a trailing ':' | + | #:**The prefix should not have a trailing ':' |
| − | #:** IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the | + | #:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. Hence, the '::' shorthand should '''not''' be used: even if some groups are all zeros, they must be explicitly written out. |
| − | # Save the changes. | + | #Save the changes. |
#:* If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place. | #:* If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place. | ||
#:* If you need help, please do not hesitate to post your issue in the [[Node Provider Matrix channel]]. | #:* If you need help, please do not hesitate to post your issue in the [[Node Provider Matrix channel]]. | ||
#:*:[[File:mac_03.png|580px|screenshot]] | #:*:[[File:mac_03.png|580px|screenshot]] | ||
| − | === C. Copy Node Operator private key to config partition === | + | === C. Copy Node Operator private key to config partition=== |
| − | # Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder. | + | #Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder. |
| − | == 7. Connect Crash Cart == | + | ==7. Connect Crash Cart== |
| − | # In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine. | + | #In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine. |
| − | # Plug-in the VGA/Video, keyboard and IC-OS USB stick | + | #Plug-in the VGA/Video, keyboard and IC-OS USB stick |
| − | #: [[File:08.png|580px|screenshot]] | + | #:[[File:08.png|580px|screenshot]] |
| − | == 8. UEFI Setup and Boot Menu == | + | ==8. UEFI Setup and Boot Menu== |
Use the related page below to set up the BIOS/UEFI according to your hardware vendor. | Use the related page below to set up the BIOS/UEFI according to your hardware vendor. | ||
| − | * [[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]] | + | *[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]] |
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]] | **[[IC-OS Installation - UEFI Configuration - Gen2 Dell]] | ||
** [[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]] | ** [[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]] | ||
** [[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]] | ** [[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]] | ||
| − | ** [[IC-OS Installation - UEFI Configuration - Gen2 ASUS]] | + | **[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]] |
| − | * [[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]] | + | *[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]] |
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]] | **[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]] | ||
| − | ** [[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]] | + | **[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]] |
| − | *** | + | *** |
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation. | '''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation. | ||
Resume from this point when you are finished configuring the BIOS. | Resume from this point when you are finished configuring the BIOS. | ||
| − | == 9. IC-OS Installation == | + | ==9. IC-OS Installation== |
| − | # Please wait while the USB Installer is booting up. This process can take up to 3 minutes. | + | #Please wait while the USB Installer is booting up. This process can take up to 3 minutes. |
| − | #: [[File:35-sm.png|580px|screenshot]] | + | #:[[File:35-sm.png|580px|screenshot]] |
| − | # The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors. | + | #The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors. |
#:[[File:36-sm.png|580px|screenshot]] | #:[[File:36-sm.png|580px|screenshot]] | ||
| − | # If the installation finished successfully, it will initiate a reboot. | + | #If the installation finished successfully, it will initiate a reboot. |
#:[[File:38-sm.png|580px|screenshot]]<br /> | #:[[File:38-sm.png|580px|screenshot]]<br /> | ||
| − | == 10. First Boot == | + | ==10. First Boot== |
Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors onboarding. | Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors onboarding. | ||
'''🚨 Do NOT re-try the IC-OS installation after completing this section, as this can cause duplication within the registry.''' | '''🚨 Do NOT re-try the IC-OS installation after completing this section, as this can cause duplication within the registry.''' | ||
| − | # Once you see this message, you may unplug the USB stick and VGA/Video. | + | #Once you see this message, you may unplug the USB stick and VGA/Video. |
#:[[File:Node join message.png|580px|screenshot]] | #:[[File:Node join message.png|580px|screenshot]] | ||
| Line 160: | Line 158: | ||
🚨 Again: Once you reach this stage and see this message, '''do not attempt to restart the onboarding process.''' Doing so may cause duplicate entries in the registry. | 🚨 Again: Once you reach this stage and see this message, '''do not attempt to restart the onboarding process.''' Doing so may cause duplicate entries in the registry. | ||
| − | == 11. Verify node onboarding == | + | ==11. Verify node onboarding== |
| − | # Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard] is set to either “Awaiting Subnet” or “Active in Subnet”. | + | #Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard] is set to either “Awaiting Subnet” or “Active in Subnet”. |
| − | #* The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node (Node ID is outputted in step 10). | + | #*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node (Node ID is outputted in step 10). |
| − | #* If the status of your node is not either “Awaiting Subnet” or “Active in Subnet”, or if it is not listed under your Node Provider principal, you should contact the [[Node Provider Matrix channel]] for assistance. | + | #*If the status of your node is not either “Awaiting Subnet” or “Active in Subnet”, or if it is not listed under your Node Provider principal, you should contact the [[Node Provider Matrix channel]] for assistance. |
#*:[[File:Dashboard-node-verification.png|thumb|998x998px]] | #*:[[File:Dashboard-node-verification.png|thumb|998x998px]] | ||
Revision as of 20:59, 19 November 2023
This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).
The physical machine is expected to be racked and stacked according to its respective manual.
To complete these steps, you are expected to by physically present with your machine(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.
If you encounter issues through any of these steps, check the Node Provider Troubleshooting page. If that does not solve your problem, you are encouraged to ask for assistance in the Node Provider Matrix channel.
1. Choose onboarding path (HSM vs. no HSM)
If you chose the HSM Node Provider Onboarding Path, follow the NitroKey HSM installation runbook to onboard your nodes.
If you chose to onboard without a Nitrokey HSM, continue to the next step.
2. Obtain requirements
- A USB (3.0 speed that can hold at least 4GB) to put the image file on.
- Faster USBs will allow the process to go much faster.
- The
node_operator_private_key.pemfor your data center (Acquired from Node Provider Onboarding step 6) - It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.
3. Download installation image
Download the latest release of the IC-OS USB Installer Image and the corresponding checksum from the Internet Computer Dashboard Releases.
- Note that you should always use a release that is less than 6 weeks old in order to ensure that your node can keep up with the blockchain.
4. Verify checksum and unarchive file
Mac OS X
- Open the Terminal and type:
shasum -a 256 ~/Downloads/disk-img.tar.gz
- Compare the calculated checksum with the IC-OS installation image checksum file downloaded in the previous step. Warning: Only continue if they are identical, otherwise please post your issue in the Node Provider Matrix channel.
- Open the Terminal and type:
tar xzvf ~/Downloads/disk-img.tar.gz
- Open the Terminal and type:
Linux / Ubuntu
- Open the Terminal and type:
sha256sum ~/Downloads/disk-img.tar.gz
- Compare the calculated checksum with the IC-OS installation image checksum file downloaded in the previous step. Warning: Only continue if they are identical, otherwise please post your issue in the Node Provider Matrix channel.
- Open the Terminal and type:
tar xzvf ~/Downloads/disk-img.tar.gz
- Open the Terminal and type:
Windows
- Open PowerShell and type:
Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.gz
- Compare the calculated checksum with the IC-OS installation image checksum file downloaded in the previous step. Warning: Only continue if they are identical, otherwise please post your issue in the Node Provider Matrix channel.
- Open PowerShell and type:
tar xzvf .\Downloads\disk-img.tar.gz
- Open PowerShell and type:
5. Create Bootable USB Stick
Mac OS X
- Open the Terminal and type:
diskutil list
- All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1
- The file path is an example. Use the absolute path to the downloaded image. Warning: You risk losing your own data if you specify a wrong device.
- If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M
sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4
Linux / Ubuntu
- Open the Terminal and type
blkid
- All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1
- Replace /dev/YOUR_USB_DEVICE with the device that corresponds to your USB stick. Warning: You risk losing your own data if you specify a wrong drive.
sudo dd if=~/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M
Windows
- Download and install Rufus Portable
- Start Rufus
- Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
- You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
- The "Ready" bar will go from left to right as it completes.
6. Add configuration
A. Open Config.ini in a text editor
Mac OS X
- Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
- Double-click
config.inito open it in TextEdit.
Linux
- Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
- Double-click
config.inito open it in KWrite.
Windows
- Open the Disk Management utility with a right click on the Start menu
#:
- Right click the CONFIG partition
- Select Change drive letter or paths...
- Select any letter from the drop-down list
- Click OK.
- You should now be able to see the CONFIG partition in your Windows Explorer. Select the
config.iniconfiguration file - Click on Edit to open it.
B. Edit Config.ini
- Insert your IPv6 prefix, subnet and gateway.
- The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
- For example, a valid prefix could look like this:
2a00:fb01:400:100 - Important:
- The prefix should not have a trailing ':'
- IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does not support '::'. Hence, the '::' shorthand should not be used: even if some groups are all zeros, they must be explicitly written out.
- Save the changes.
- If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
- If you need help, please do not hesitate to post your issue in the Node Provider Matrix channel.
C. Copy Node Operator private key to config partition
- Copy
node_operator_private_key.pem(created in Node Provider Onboarding step 6) to theCONFIGpartition. This file should have the namenode_operator_private_key.pem, and sit next toconfig.ini, NOT inside thessh_authorized_keysfolder.
7. Connect Crash Cart
- In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
- Plug-in the VGA/Video, keyboard and IC-OS USB stick
8. UEFI Setup and Boot Menu
Use the related page below to set up the BIOS/UEFI according to your hardware vendor.
Important: Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.
Resume from this point when you are finished configuring the BIOS.
9. IC-OS Installation
- Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
- The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the Possible Node Onboarding Errors page if you encounter any errors.
- If the installation finished successfully, it will initiate a reboot.
10. First Boot
Please remember to check the Possible Node Onboarding Errors page if you encounter any errors onboarding.
🚨 Do NOT re-try the IC-OS installation after completing this section, as this can cause duplication within the registry.
- Once you see this message, you may unplug the USB stick and VGA/Video.
Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!
🚨 Again: Once you reach this stage and see this message, do not attempt to restart the onboarding process. Doing so may cause duplicate entries in the registry.
11. Verify node onboarding
- Verify that your node was successfully onboarded by checking its status on the dashboard is set to either “Awaiting Subnet” or “Active in Subnet”.
- The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node (Node ID is outputted in step 10).
- If the status of your node is not either “Awaiting Subnet” or “Active in Subnet”, or if it is not listed under your Node Provider principal, you should contact the Node Provider Matrix channel for assistance.
