Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:veos:installation [2024/05/13 07:00] – elena.krasnobryzh | en:veos:installation [2026/05/28 15:46] (current) – created elena.krasnobryzh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ======VEOS installation and configuration====== |
| {{indexmenu_n> | {{indexmenu_n> | ||
| - | <note tip>Due to the fact that Red Hat discontinued support | + | =====1. Requirements |
| - | **The transition to the new OS edition is planned in the form of an in-house upgrade (without reinstallation), | + | ====1.1. Hardware requirements==== |
| + | Before mounting the server into the rack, make sure it meets the **required specifications**: | ||
| + | * [[en: | ||
| + | | ||
| + | | ||
| - | <note important> | + | :!: If any discrepancies are identified at this stage, contact [[en: |
| - | * [[en: | + | ====1.2. Disk partitioning |
| - | * [[en: | + | Disk partitioning for SSG software: |
| - | * [[en: | + | * ~20 GB for the root partition. |
| + | * Allocate the remaining space to the ''/ | ||
| + | * SSG does not use a SWAP partition directly, but it is required for system tasks. Allocate 4 GB for it. | ||
| - | If any discrepancies are found at this stage, contact [[en: | + | Use the GPT partition table type. |
| - | ===== ISO Links ===== | + | =====2. Preparing for VEOS installation===== |
| - | - [[https:// | + | ====2.1. Server preparation==== |
| + | | ||
| + | * Configure the server for maximum performance | ||
| + | |||
| + | ====2.2. Creating bootable media==== | ||
| + | === ISO links === | ||
| + | * [[https:// | ||
| [[en: | [[en: | ||
| - | ===== Preparation of the installation | + | === Method 1. Preparing a bootable |
| - | The most popular current method of installing | + | The most common way to install |
| - | <note warning> | + | <note warning> |
| - | ==== Writing a USB disk on Linux ==== | + | == Writing a USB drive on Linux == |
| - | To create a USB installation disk on Linux/Unix, run the dd command: | + | To create a bootable |
| > dd if=VEOS-8.7-x86_64-Minimal.iso of=/dev/sdz bs=1M | > dd if=VEOS-8.7-x86_64-Minimal.iso of=/dev/sdz bs=1M | ||
| - | <note important> | + | :!: When writing |
| - | ==== Writing a USB Disk to Windows | + | == Writing a USB drive on Windows == |
| - | === Rufus === | + | **1. Rufus** |
| - | To burn an ISO to a USB drive on Windows, you can use the [[https:// | + | |
| - | | + | |
| - | {{: | + | |
| - | | + | |
| - | {{: | + | |
| - | === Diskdupe (dd) for Windows === | + | To write the ISO image to a USB drive on Windows, you can use [[https://rufus.ie/ru/#|Rufus]], making sure to select the "DD Image mode": |
| - | The command parameters are similar | + | * Rufus main screen\\ {{: |
| + | * write mode selection dialog\\ {{: | ||
| - | When using dd for Windows, first run dd --list and, after carefully reviewing the NT block device list, select a device similar to {\? | ||
| - | ===== Preparation of the installation disk ===== | + | **2. Diskdupe (dd) for Windows** |
| - | The most common way to install an operating system on a computer is to install from an installation DVD. | + | |
| - | ==== Recording a disk image in the MS Windows operating system ==== | + | The command parameters are the same as on Linux. The DD distribution for Windows |
| - | An ISO disk image file is a special format file prepared to burn on a disk. To burn an ISO image in the MS Windows | + | |
| - | === Recording a disk image with Small CD-Writer === | + | When using dd for Windows, first run '' |
| - | The entire process of burning an installation disk with Small CD-Writer consists of the following steps: | + | |
| - | - download | + | |
| - | - download the Small CD-Writer program archive http:// | + | |
| - | - extract program files from the archive | + | |
| - | - insert | + | |
| - | - enter the directory and run SCDWriter.exe; | + | |
| - | - start Disk → Burn ISO image to disk and, in the window that appears, specify the path to the disk image; | + | |
| - | - click the Burn button. | + | |
| - | ==== Recording a disk image in the Linux operating system ==== | + | === Method 2. Preparing an installation |
| - | To burn ISO images it is recommended to use K3b or Brasero programs that come with any Linux distribution. | + | The traditional way to install an operating system |
| - | === Recording | + | == Burning |
| - | The entire process of burning an installation | + | An ISO disk image file is a specially formatted file prepared for burning |
| - | - if the k3b program | + | |
| - | - run the k3b program. If properly configured, the program will tell you that there are no problems with the system and will prompt you to proceed to disk burning; | + | |
| - | | + | |
| - | | + | |
| - | - the k3b program will show you the information about the ISO file and start calculating the checksum. This operation may take a few minutes. The checksum you get may be compared with the MD5SUM on the distribution page; | + | |
| - | - if the checksums do not match, that means you have selected a wrong file for burning or the downloaded ISO image was broken during data transfer over the network; | + | |
| - | - if the checksums match, insert the disk into your drive. Wait for the Start button to activate; | + | |
| - | - click the Start button. | + | |
| - | ===== Installation ===== | + | The entire process of creating an installation disk using Small CD-Writer consists of the following steps: |
| - | To boot your computer | + | - Download the distribution image; |
| + | - Download the [[http:// | ||
| + | - Extract the program files from the archive into any directory; | ||
| + | - Insert a blank disk into the drive; | ||
| + | - Open the extracted directory and run SCDWriter.exe; | ||
| + | - Open the menu item Disk → Burn ISO Image to Disk and specify | ||
| + | - Click the Burn button. | ||
| - | ===== Installation sequence ===== | + | == Burning a disk image on Linux (using K3b) == |
| - | After successful initialization of the hardware, the bootloader menu with installation options is displayed: | + | It is recommended to use K3b or Brasero for burning ISO images, as these programs are included in most Linux distributions. |
| + | The entire process of creating an installation disk using K3b consists of the following steps: | ||
| + | - if the k3b program is not installed, install it using the standard package management tools of your distribution; | ||
| + | - launch the k3b program. If the system is configured correctly, the program will report that there are no issues and offer to proceed with burning the disk; | ||
| + | - in the main window menu, select Service → Burn DVD Image; | ||
| + | - in the Burn DVD Image window, click the button to select the file for burning. A dialog will open where you need to choose the ISO image and click OK; | ||
| + | - k3b will display information about the ISO file and begin calculating the checksum. This may take several minutes. The resulting checksum can be compared with the MD5SUM value on the distribution page; | ||
| + | - if the checksums do not match, either the wrong file was selected or the downloaded ISO image was corrupted during transfer; | ||
| + | - if the checksums match, insert a writable disk into the drive and wait for the Start button to become active; | ||
| + | - click the Start button. | ||
| + | |||
| + | =====3. Installation process===== | ||
| + | ====3.1. Booting from media and startup menu==== | ||
| + | To boot the computer for system installation, | ||
| + | |||
| + | After successful hardware initialization, | ||
| {{ : | {{ : | ||
| - | Selecting the normal | + | Selecting the standard |
| - | Technical information about the installation | + | Technical information about the installation |
| - | The following steps are used to install the system: | + | Each step includes a short help section available |
| - | - choosing the language of the installation interface; | + | The installation process consists of the following steps: |
| - | - configuring | + | - Selecting |
| - | - installing | + | - Configuring |
| - | - finishing | + | - Installing |
| + | - Completing the installation and rebooting | ||
| - | < | + | ====3.2. Verifying successful installation==== |
| - | * When partitioning a disk for SSG software: < | + | You can verify the installation in two ways: |
| - | Allocate the remaining space for the /var directory. | + | * Check the VEOS version: < |
| - | The Stingray SG does not use a SWAP partition, but it is needed for system | + | * Download any test package from the repository |
| - | * Disable Hyper-threading in BIOS for SSG software! | + | |
| - | </ | + | |
| - | ===== Pre-configuring VEOS ===== | + | =====4. Providing access for further configuration===== |
| - | If you received a preinstalled | + | If you received a preconfigured |
| - | Otherwise, you need to install the VEOS operating system on your server yourself and give us remote SSH access and root rights to perform | + | Otherwise, you need to install the VEOS operating system on your server yourself and provide |
| + | After the work is completed, remote access can be disabled. | ||
| - | - Create | + | - Create |
| - | - Set a **complex** password for the user **vasexpertsmnt**: | + | - Set a **strong** password for the **vasexpertsmnt** |
| - Save the password for **vasexpertsmnt**. | - Save the password for **vasexpertsmnt**. | ||
| - | - Set permission for users of the wheel group to use all commands | + | - Allow users from the wheel group to execute |
| - | - To provide remote | + | - To provide remote SSH access |
| < | < | ||
| - | iptables -A INPUT -m conntrack --ctstate RELATED, ESTABLISHED -j ACCEPT | + | iptables -A INPUT -m conntrack --ctstate RELATED, |
| - | iptables -A INPUT -p tcp -s 45.151.108.0/ | + | iptables -A INPUT -p tcp -s 45.151.108.0/ |
| - | iptables -A INPUT -p tcp -s 94.140.198.64/ | + | iptables -A INPUT -p tcp -s 94.140.198.64/ |
| - | iptables -A INPUT -p tcp -s 78.140.234.98 | + | iptables -A INPUT -p tcp -s 193.218.143.187 -m tcp --dport 22 -j ACCEPT |
| - | iptables -A INPUT -p tcp -s 193.218.143.187 | + | iptables -A INPUT -p tcp -s 93.100.73.160 -m tcp --dport 22 -j ACCEPT |
| - | iptables -A INPUT -p tcp -s 93.100.47.212 | + | iptables -A INPUT -p tcp -s 78.140.234.98 -m tcp --dport 22 -j ACCEPT |
| - | iptables -A INPUT -p tcp -s 93.100.73.160 -m tcp --dport 22 -j ACCEPT | + | iptables -A INPUT -p tcp -s 93.159.236.11 -m tcp --dport 22 -j ACCEPT |
| - | iptables -A INPUT -p tcp -s 77.247.170.134 -m tcp --dport 22 -j ACCEPT | + | iptables -A INPUT -p tcp -s 46.243.181.35 -m tcp --dport 22 -j ACCEPT |
| - | iptables -A INPUT -p tcp -s 91.197.172.2 -m tcp --dport 22 -j ACCEPT | + | iptables -A INPUT -p tcp -s 46.243.181.242 -m tcp --dport 22 -j ACCEPT |
| - | iptables -A INPUT -p tcp -s 46.243.181.242 -m tcp --dport 22 -j ACCEPT | + | iptables -A INPUT -p tcp --dport 22 -j DROP |
| - | iptables -A INPUT -p tcp -s 93.159.236.11 -m tcp --dport 22 -j ACCEPT | + | service iptables save |
| - | iptables -A INPUT -p tcp --dport 22 -j DROP | + | |
| - | service iptables save | + | |
| </ | </ | ||
| - | If you are using firewalld: | + | If you use firewalld: |
| < | < | ||
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --permanent --zone=public --add-rich-rule=' |
| - | firewall-cmd --permanent --zone = public --add-rich-rule = 'rule family = " | + | firewall-cmd --zone=public --remove-service=ssh --permanent |
| - | firewall-cmd | + | firewall-cmd --reload |
| - | firewall-cmd --reload | + | |
| - | firewall-cmd --zone = public --remove-service = ssh --permanent | + | |
| </ | </ | ||
| - | **!Save your settings | + | **!Save your settings, since the server will be rebooted during installation!** \\ |
| \\ | \\ | ||
| - | After making sure that remote | + | After confirming |
| < | < | ||
| - | Installation of the Stingray | + | SSG software |
| </ | </ | ||
| - | |||
| <note warning> | <note warning> | ||
| - | Do not update the operating system kernel until the system is activated | + | Do not update the operating system kernel until the [[en: |
| - | this may cause the network card driver to fail (([[en: | + | as this may cause the network card driver to fail. |
| </ | </ | ||
| + | =====5. Updating VEOS===== | ||
| + | To update VEOS, install the new version according to the standard [[en: | ||
| + | |||
| + | =====6. Troubleshooting===== | ||
| + | ====6.1. VEOS does not start after installation==== | ||
| + | Boot issues can be caused by various reasons, from BIOS/UEFI settings to missing drivers. | ||
| + | * Analyze the error messages displayed during boot. | ||
| + | * The most common causes: | ||
| + | * Secure Boot is enabled — disable it in UEFI settings. | ||
| + | * Incorrect boot order — make sure the disk with VEOS is first in the boot device list. | ||
| + | * GRUB bootloader is corrupted — boot into Rescue mode from the installation media and restore it. | ||
| + | * Missing drivers (kernel panic) — use a DUD ISO with the inst.dd boot parameter. | ||
| + | * If the cause is unclear, contact [[en: | ||
| + | |||
| + | ====6.2. The installer does not detect the hard drive==== | ||
| + | In most cases, the issue is related to hardware or the disk controller operating mode. | ||
| + | * Check the physical disk connection: cables, ports, and power. | ||
| + | * Check the SATA controller mode in BIOS/UEFI — switch between AHCI and RAID and try both options. | ||
| + | * If the disk is connected to a RAID or HBA controller, there may be no built-in driver available — use a DUD ISO (see section 2.2.1). | ||
| + | * To rule out disk failure, test the drive on another server. | ||
| + | ====6.3. Network issues after installation==== | ||
| + | If network connectivity is unavailable after booting VEOS, first check whether NetworkManager is running. | ||
| + | * Check the NetworkManager status: < | ||
| + | * If the service is disabled or not running, enable it: < | ||
| + | systemctl start NetworkManager</ | ||
| + | * If NetworkManager is running but the network still does not work, check the interface settings (DHCP or static IP), default gateway, and DNS. | ||