Installing PicOS on Bare Metal Switches
- Tracy Yang (Unlicensed)
Notes and Tools
The Pica8 PicOS software can be installed on any switch listed in the PicOS Hardware Compatibility List.
• You need to log in through the console port of the switch and perform the ONIE installation.
• If you are using X86 platform and have installed other OS’s, please first uninstall the other OS and then install PICOS.
You can enter ONIE and then using ONIE’s uninstall OS mode to uninstall all the OS’s and then install PICOS, or you can enter ONIE mode and then delete all those partitions manually on which other OS’s are installed.
• If you enter GRUB rescue mode and switch is GPT format partition, you can use the following command to reset the GRUB boot variable to enter ONIE GRUB and then install PicOS.
grub rescue> set prefix=(hd0,gpt2)/grub
grub rescue> set root=(hd0,gpt2)
grub rescue> insmod normal
grub rescue> normal
- Do not plug in the USB disk during onie-nos-installer process until ONIE starts up. If you have plugged in the USB disk before installation operation, ONIE will find the installer in the USB disk when beginning the installation. When installation is complete, the installer will display: Please take out the usb disc, then remove the USB disk within 10 seconds after installation success, and before machine restart.
For AG6248C, insert the external USB disk before installing the system, and install PicOS on the USB disk. Do not take out the USB disc after finished installation.
- If partitions are not continuous, installation will abort.
- List of x86 platform: AS5712-54X, AS6712-32X, AS7712-32X, DCS7032Q28, NIAGRARA2632XL, NIAGRARA2948-6XL, S4048, Z9100.
- When using ONIE installer, it will install new image to "PicOS" partition (maybe there are both two partitions "PicOS" and "PicOS2"), and set the system on "PicOS" partition as the default and sole system.
What is U-Boot
Das U-Boot (Universal Boot Loader), or U-Boot for short, is an open source, primary boot loader developed for embedded systems. A boot loader is a computer program that loads the operating system or some other system software. U-Boot comes pre-installed as firmware on bare metal network switches.
What is ONIE
ONIE (Open Network Install Environment) is an open source project of OCP (Open Compute Project). ONIE provides the environment to install any network operating system on a bare metal network switch. ONIE liberates users from captive pre-installed network operating systems, like the Cisco IOS, and provides them with a choice.
ONIE is a small Linux operating system that comes pre-installed as firmware on bare metal network switches. ONIE acts as an enhanced boot loader, extending the features provided by U-Boot. ONIE is used to install Pica8 PicOS on compatible switches. The bare metal switches listed in the PicOS Hardware Compatibility List must be pre-loaded with ONIE prior to installing PicOS.
Traditional Installation
NOTE：
|
Mind Map of Installation Process
Figure1 shows the mind map of PicOS installation process.
Figure1 Mind Map of PicOS installation process
Manual Installation Process
The following example describes the installation of PicOS via manual installation method.
Step1
Make sure that the installation package of .bin file has been load to the server (server could be HTTP, TFTP, or an FTP server or the switch local directory according to the actual installation environment).
Step2 Enter ONIE installation environment. The process is different on the following two types of platforms:
- PowerPC and ARM Platforms
a)
Verify that the switch is pre-loaded with ONIE, which will be used to load PicOS on the switch. Power on the switch and interrupt the boot sequence by pressing any key when the following line is shown:
Hit any key to stop autoboot:
b)
User will then reach the U-Boot command prompt indicated by ->. Run the printenv command at the U-Boot prompt. If the information displayed contains keywords like onie_initargs and onie_machine, the switch is pre-loaded with ONIE.
LOADER->printenv
active=image1
autoload=no
baudrate=115200
bootcmd=run check_boot_reason;run PicOS_bootcmd;run onie_bootcmd
bootdelay=10
check_boot_reason=if test -n $onie_boot_reason; then setenv onie_bootargs boot_reason=$onie_boot_reason; run onie_bootcmd; fi;
consoledev=ttyS0
dhcp_user-class=arm-agema_ag6248c-poe-r0_uboot
dhcp_vendor-class-identifier=arm-agema_ag6248c-poe-r0
ethact=eth-0
ethaddr=00:18:23:30:E7:8F
fdtaddr=0xc00000
fpboot=setenv bootargs console=${consoledev},${baudrate} maxcpus=2 mem=1024M root=/dev/ram ${mtdparts} ubi.mtd=4 ethaddr=$ethaddr quiet
gatewayip=192.168.0.1
initrd_high=0x80000000
ipaddr=192.168.0.1
loadaddr=0x70000000
loads_echo=1
mfg=mfg
mfgdiags=run fpboot ; nand read ${loadaddr} diags ; bootm ${loadaddr}
mfgdiags_recovery=nand read ${loadaddr} diags2 ; nand erase.part diags ; nand write ${loadaddr} diags
mtdids=nand0=nand_iproc.0
mtdparts=mtdparts=nand_iproc.0:1m(uboot),2m(shmoo),1m(nenv),12m(onie),3992m(open),12m(onie2),2m(vpd),6m(sys_eeprom),16m(diags),16m(diags2),32m(diags_fs)
netmask=255.255.255.0
nos_bootcmd=true
onie_args=run onie_initargs onie_platformargs
onie_bootcmd=echo Loading Open Network Install Environment ...; echo Platform: $onie_platform ; echo Version : $onie_version ; nand read $loadaddr $onie_start 0x00c00000 && run onie_args && bootm ${loadaddr}
onie_dropbear_dss_host_key=begin-base64@600@d#AAAAB3NzaC1kc3MAAACBAIN7HOS7UGtQ+RS9R5Rdim9s4iadCBQ9SEFnHJZ2#ulK15hN2p1BOJ1Mf4qb/oHFGIt8hvopq157ejsJcSPuR9scXE2aYQO7r1+Ie#1MKoR3HyEFKgPhNUr0qYNiIaWGw2UUXivLUlhjmaPhjItsttb6AezNB6N1ap#TmIeEUse0NQBAAAAFQDndwbRrSsw6G/W4wd0LJVAjuyq2QAAAIAe/zGPyPNn#UwwV+i+j3l1W9IFhjA/ovXfX7PQtjHB7OJcInSpOA2gXLXHU2kYDkn+ymJQI#8Tn558nLHq64n9hIJzwaQH4ajMipBNwqR0WtpPXEaow9InDzjs+qFY0HAcTv#7DMEY9BGiJAUUSSCSFZ9dEYHIWUdk6WIpDUMX4b2ewAAAIB6bC+fHzr+Qaet#GjzynI0tApbzyydXKuIiIH6EDh2QEaP0E+TSxJ+C4xfyBAp1j0kvj0IYWR2P#H9ur0RaxDaCmKwIQs1gTJh/137Yd+OsqEV3JnrZxlEKk2DmI5c2wrGtl4oUp#XJfc+viahpFeCsGzsqGHHADWNsjlpKt457QCuQAAABUAk5406cTH4nZO0qlj#6irYf4WA65E=#====#
onie_dropbear_rsa_host_key=begin-base64@600@r#AAAAB3NzaC1yc2EAAAADAQABAAAAgQCMTqwNhnJpuSLYAdRA/jjm1lyBaJF1#ovs3Hp0G7XkYnY4+JNPTCYgnmfMQnM83PQncuy89AqehJ2V22LGjpRiqT56K#MRr+hQoSWEbAObRd1azZF45pbxiQaQiQxNzIKbHDDWlGlycXfv8w9ZCElbxj#Ja7bkwmwg9EsBlW0d5u0BQAAAIAFr0FOyfn0OR1FiatvF624Aorcbl9oV/pc#JRghGfl8SxPihizz4bC7xAPCUkwd9ZHi+M2E6AjhIV69xjFKS0vYuQplvl8G#9R8YsnmP5B45TyLE3dW5V2/g+LQERQdFpRaSsPqEPHSlXPq4XHLGLRFItEBt#ohp41Qm+eA6efsAMIQAAAEEA4Y90xi8N1SuwjRk53fqpP8dC+FPnU850XtC1#cKG0rBt6v9qD+BTxxfE6GEpYM+N0fLyECbgBjA2LQF6CG3G15QAAAEEAnz3v#3POrcsMK2LkSNjWzAhzUqOWyOaNlhcvgh+2Xfj2tHyOTpZ09gCm483v1rui9#63uYu4QQurpATrHMcLIjoQ==#====#
onie_initargs=setenv bootargs quiet console=$consoledev,$baudrate
onie_machine=agema_ag6248c-poe
onie_machine_rev=0
onie_platform=arm-agema_ag6248c-poe-r0
onie_platformargs=setenv bootargs $bootargs serial_num=${serial#} ${platformargs} eth_addr=$ethaddr $onie_bootargs $onie_debugargs
onie_recovery=nand read ${loadaddr} onie2 ; nand erase.part onie ; nand write ${loadaddr} onie
onie_rescue=setenv onie_boot_reason rescue && boot
onie_start=onie
onie_sz.b=0x00c00000
onie_uninstall=setenv onie_boot_reason uninstall && boot
onie_update=setenv onie_boot_reason update && boot
onie_vendor_id=27658
onie_version=master-201603091701-dirty
PicOS_bootcmd=usb start;run platformargs;setenv bootargs root=/dev/sda1 rw noinitrd console=$consoledev,$baudrate rootdelay=10 $mtdparts;ext2load usb 0:1 $loadaddr boot/uImage;bootm $loadaddr
platform=agema_ag6248c-poe
platformargs=mtdparts=nand_iproc.0:1m(uboot),2m(shmoo),1m(nenv),12m(onie),3992m(open),12m(onie2),2m(vpd),6m(sys_eeprom),16m(diags),16m(diags2),32m(diags_fs) maxcpus=2 mem=1024M
ramdiskaddr=0x3000000
serial#=A626P1DL174300014
serverip=192.168.0.10
stderr=serial
stdin=serial
stdout=serial
ubifscfg=ubi part nand0,4 0x0; ubifsmount fs
ver=U-Boot 2012.10-gcbef171 (Mar 09 2016 - 17:01:14) - ONIE master-201603091701-dirty
Environment size: 3992/65532 bytes
c) From U-Boot prompt, boot ONIE in rescue mode.
LOADER-> run onie_rescue
- x86 Platform
On x86 platform, it uses GRUB menu to install OS via ONIE.
a) Reboot the system, and enter ONIE installation environment from the GRUB menu:
+----------------------------------------------------------------------------+
| PicOS |
|*ONIE |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
b) From GRUB prompt, choose ONIE: Rescue to Install OS, boot ONIE in rescue mode.
GNU GRUB version 2.02~beta2+e4a1fe391 +----------------------------------------------------------------------------+ |*ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | DIAG: Accton Diagnostic | | | | | | | | | | | | | +----------------------------------------------------------------------------+
Step3 Run onie-nos-install command as follows to manually install PicOS.
- Install via TFTP
ONIE# onie-nos-install tftp://<path to image>/PicOS.bin
- Install via FTP
When installing via FTP, you need to type username and password of the FTP server on which the image file is loaded.
ONIE# onie-nos-install ftp://username:password@<path to image>/PicOS.bin
- Install via HTTP
ONIE# onie-nos-install http://<path to image>/PicOS.bin
- Install via Local Directory
a) In ONIE rescue mode, copy the image file to the current directory.
ONIE# scp username@<path to image>/PicOS.bin .
b) Run onie-nos-install command to start installation.
ONIE# onie-nos-install PicOS.bin
The installer runs and after finishing installation will reboot automatically, the system will come up running the new network operating system.
NOTE：
|
Automatic Installation Process
Step1 Make sure the switch is connected to DHCP and HTTP servers, and the PicOS installer image is downloaded to the HTTP server.
a) DHCP server configuration and starting DHCP server service:
host pica8-3922 {
hardware ethernet 70:72:cf:12:34:56;
fixed-address 192.168.2.50;
option default-url = "http://192.168.2.42/onie-installer-powerpc.bin";
}
b) Check if the .bin installation file is loaded on HTTP server:
root@dev:/var/www# ls index.html onie-installer-powerpc.bin
Step2 Install PicOS via ONIE. The process is different on the following two types of platforms:
- PowerPC and ARM Platforms
a)
Verify that the switch is pre-loaded with ONIE, which will be used to load PicOS on the switch. Power on the switch and interrupt the boot sequence by pressing any key when the following line is shown:
Hit any key to stop autoboot:
b)
User will then reach the U-Boot command prompt indicated by ->. Run the printenv command at the U-Boot prompt. If the information displayed contains keywords like onie_initargs and onie_machine, the switch is pre-loaded with ONIE.
LOADER->printenv
active=image1
autoload=no
baudrate=115200
bootcmd=run check_boot_reason;run PicOS_bootcmd;run onie_bootcmd
bootdelay=10
check_boot_reason=if test -n $onie_boot_reason; then setenv onie_bootargs boot_reason=$onie_boot_reason; run onie_bootcmd; fi;
consoledev=ttyS0
dhcp_user-class=arm-agema_ag6248c-poe-r0_uboot
dhcp_vendor-class-identifier=arm-agema_ag6248c-poe-r0
ethact=eth-0
ethaddr=00:18:23:30:E7:8F
fdtaddr=0xc00000
fpboot=setenv bootargs console=${consoledev},${baudrate} maxcpus=2 mem=1024M root=/dev/ram ${mtdparts} ubi.mtd=4 ethaddr=$ethaddr quiet
gatewayip=192.168.0.1
initrd_high=0x80000000
ipaddr=192.168.0.1
loadaddr=0x70000000
loads_echo=1
mfg=mfg
mfgdiags=run fpboot ; nand read ${loadaddr} diags ; bootm ${loadaddr}
mfgdiags_recovery=nand read ${loadaddr} diags2 ; nand erase.part diags ; nand write ${loadaddr} diags
mtdids=nand0=nand_iproc.0
mtdparts=mtdparts=nand_iproc.0:1m(uboot),2m(shmoo),1m(nenv),12m(onie),3992m(open),12m(onie2),2m(vpd),6m(sys_eeprom),16m(diags),16m(diags2),32m(diags_fs)
netmask=255.255.255.0
nos_bootcmd=true
onie_args=run onie_initargs onie_platformargs
onie_bootcmd=echo Loading Open Network Install Environment ...; echo Platform: $onie_platform ; echo Version : $onie_version ; nand read $loadaddr $onie_start 0x00c00000 && run onie_args && bootm ${loadaddr}
onie_dropbear_dss_host_key=begin-base64@600@d#AAAAB3NzaC1kc3MAAACBAIN7HOS7UGtQ+RS9R5Rdim9s4iadCBQ9SEFnHJZ2#ulK15hN2p1BOJ1Mf4qb/oHFGIt8hvopq157ejsJcSPuR9scXE2aYQO7r1+Ie#1MKoR3HyEFKgPhNUr0qYNiIaWGw2UUXivLUlhjmaPhjItsttb6AezNB6N1ap#TmIeEUse0NQBAAAAFQDndwbRrSsw6G/W4wd0LJVAjuyq2QAAAIAe/zGPyPNn#UwwV+i+j3l1W9IFhjA/ovXfX7PQtjHB7OJcInSpOA2gXLXHU2kYDkn+ymJQI#8Tn558nLHq64n9hIJzwaQH4ajMipBNwqR0WtpPXEaow9InDzjs+qFY0HAcTv#7DMEY9BGiJAUUSSCSFZ9dEYHIWUdk6WIpDUMX4b2ewAAAIB6bC+fHzr+Qaet#GjzynI0tApbzyydXKuIiIH6EDh2QEaP0E+TSxJ+C4xfyBAp1j0kvj0IYWR2P#H9ur0RaxDaCmKwIQs1gTJh/137Yd+OsqEV3JnrZxlEKk2DmI5c2wrGtl4oUp#XJfc+viahpFeCsGzsqGHHADWNsjlpKt457QCuQAAABUAk5406cTH4nZO0qlj#6irYf4WA65E=#====#
onie_dropbear_rsa_host_key=begin-base64@600@r#AAAAB3NzaC1yc2EAAAADAQABAAAAgQCMTqwNhnJpuSLYAdRA/jjm1lyBaJF1#ovs3Hp0G7XkYnY4+JNPTCYgnmfMQnM83PQncuy89AqehJ2V22LGjpRiqT56K#MRr+hQoSWEbAObRd1azZF45pbxiQaQiQxNzIKbHDDWlGlycXfv8w9ZCElbxj#Ja7bkwmwg9EsBlW0d5u0BQAAAIAFr0FOyfn0OR1FiatvF624Aorcbl9oV/pc#JRghGfl8SxPihizz4bC7xAPCUkwd9ZHi+M2E6AjhIV69xjFKS0vYuQplvl8G#9R8YsnmP5B45TyLE3dW5V2/g+LQERQdFpRaSsPqEPHSlXPq4XHLGLRFItEBt#ohp41Qm+eA6efsAMIQAAAEEA4Y90xi8N1SuwjRk53fqpP8dC+FPnU850XtC1#cKG0rBt6v9qD+BTxxfE6GEpYM+N0fLyECbgBjA2LQF6CG3G15QAAAEEAnz3v#3POrcsMK2LkSNjWzAhzUqOWyOaNlhcvgh+2Xfj2tHyOTpZ09gCm483v1rui9#63uYu4QQurpATrHMcLIjoQ==#====#
onie_initargs=setenv bootargs quiet console=$consoledev,$baudrate
onie_machine=agema_ag6248c-poe
onie_machine_rev=0
onie_platform=arm-agema_ag6248c-poe-r0
onie_platformargs=setenv bootargs $bootargs serial_num=${serial#} ${platformargs} eth_addr=$ethaddr $onie_bootargs $onie_debugargs
onie_recovery=nand read ${loadaddr} onie2 ; nand erase.part onie ; nand write ${loadaddr} onie
onie_rescue=setenv onie_boot_reason rescue && boot
onie_start=onie
onie_sz.b=0x00c00000
onie_uninstall=setenv onie_boot_reason uninstall && boot
onie_update=setenv onie_boot_reason update && boot
onie_vendor_id=27658
onie_version=master-201603091701-dirty
PicOS_bootcmd=usb start;run platformargs;setenv bootargs root=/dev/sda1 rw noinitrd console=$consoledev,$baudrate rootdelay=10 $mtdparts;ext2load usb 0:1 $loadaddr boot/uImage;bootm $loadaddr
platform=agema_ag6248c-poe
platformargs=mtdparts=nand_iproc.0:1m(uboot),2m(shmoo),1m(nenv),12m(onie),3992m(open),12m(onie2),2m(vpd),6m(sys_eeprom),16m(diags),16m(diags2),32m(diags_fs) maxcpus=2 mem=1024M
ramdiskaddr=0x3000000
serial#=A626P1DL174300014
serverip=192.168.0.10
stderr=serial
stdin=serial
stdout=serial
ubifscfg=ubi part nand0,4 0x0; ubifsmount fs
ver=U-Boot 2012.10-gcbef171 (Mar 09 2016 - 17:01:14) - ONIE master-201603091701-dirty
Environment size: 3992/65532 bytes
c) Input command run onie_bootcmd, which will automatically install PiCOS on the switch.
LOADER -> run onie_bootcmd Loading Open Network Install Environment ... Platform: powerpc-accton_5652-r1 Version : 1.6.1.3 WARNING: adjusting available memory to 30000000 ## Booting kernel from Legacy Image at 02000000 ... Image Name: as5600_52x.1.6.1.3 Image Type: PowerPC Linux Multi-File Image (gzip compressed) Data Size: 3514311 Bytes = 3.4 MiB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 2762367 Bytes = 2.6 MiB Image 1: 733576 Bytes = 716.4 KiB Image 2: 18351 Bytes = 17.9 KiB Verifying Checksum ... OK ## Loading init Ramdisk from multi component Legacy Image at 02000000 ... ## Flattened Device Tree from multi component Image at 02000000 Booting using the fdt at 0x02355858 Uncompressing Multi-File Image ... OK Loading Ramdisk to 2ff4c000, end 2ffff188 ... OK Loading Device Tree to 03ff8000, end 03fff7ae ... OK Cannot reserve gpages without hugetlb enabled setup_arch: bootmem as5600_52x_setup_arch() arch: exit pci 0000:00:00.0: ignoring class b20 (doesn't match header type 01) sd 0:0:0:0: [sda] No Caching mode page present sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] No Caching mode page present sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] No Caching mode page present sd 0:0:0:0: [sda] Assuming drive cache: write through ONIE: Using DHCPv4 addr: eth0: 192.168.2.77 / 255.255.255.0 discover: installer mode detected. Running installer. Please press Enter to activate this console. ONIE: Using DHCPv4 addr: eth0: 192.168.2.77 / 255.255.255.0 ONIE: Starting ONIE Service Discovery ONIE: Executing installer: http://192.168.2.42/PicOS-2.4-P3924-16656.bin Verifying image checksum ... OK. Preparing image archive ... OK. PicOS installation .............................................. ./var/local/ ./var/run Setup PicOS environment ... .............................................. XorPlus login: admin Password: You are required to change your password immediately (root enforced) Changing password for admin. (current) UNIX password: Enter new UNIX password: Retype new UNIX password: admin@XorPlus$
- x86 Platform
On x86 platform, it uses GRUB menu to choose install OS via ONIE.
a) Reboot the system, and enter ONIE installation environment from the GRUB menu:
+----------------------------------------------------------------------------+
| PicOS |
|*ONIE |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
b) From GRUB prompt, choose ONIE: Rescue to Install OS, boot ONIE in rescue mode.
GNU GRUB version 2.02~beta2+e4a1fe391 +----------------------------------------------------------------------------+ |*ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | DIAG: Accton Diagnostic | | | | | | | | | | | | | +----------------------------------------------------------------------------+
The installer runs and will reboot the system after installation is complete.
NOTE：
|
Nos-boot-mode Installation
NOTE：
|
The installation methods described in 1.2 Traditional Installation must be performed through the console port. When you want to install the system through a non-console port, you can use the nos-boot-mode command to perform the installation which is described in this section.
Usage of nos-boot-mode command: admin@Xorplus$sudo nos-boot-mode USAGE install or uninstall NOS(es) SYNOPSIS nos-boot-mode [install|uninstall] DESCRIPTION install- Install NOS uninstall- Remove all NOS(es) including PICOS When nos-boot-mode install command is executed, PICOS will switch to ONIE install mode, and the user should go on to complete the subsequent installation. The steps for the manual installation process and the automatic installation process using the nos-boot-mode install command are described below. When nos-boot-mode unsinstall command is executed, the system will remove all NOS(es) including PICOS from the device. Therefore, it is suggested to use the nos-boot-mode unsinstall command with caution. |
Manual Installation Process
Step1 Make sure that the installation package of .bin file has been loaded to the server (server could be HTTP, TFTP, or an FTP server or the switch local directory depending on the actual installation environment).
Step2 Execute the nos-boot-mode install command to enter ONIE installation environment.
admin@Xorplus:~$ sudo nos-boot-mode install
Step3 Type “yes” when the below prompt is shown, which will take the system will to ONIE install mode.
Type 'yes' to install NOS! Type 'no' to exit [no]/yes:
Step4 Run onie-nos-install command as follows to manually install PICOS.
- Install via TFTP
ONIE# onie-nos-install tftp://<path to image>/PicOS.bin
- Install via FTP
When installing via FTP, you need to type in the username and password for the FTP server on which the image file is loaded.
ONIE# onie-nos-install ftp://username:password@<path to image>/PicOS.bin
- Install via HTTP
ONIE# onie-nos-install http://<path to image>/PicOS.bin
- Install via Local Directory
a) In ONIE rescue mode, copy the image file to the current directory.
ONIE# scp username@<path to image>/PicOS.bin .
b) Run onie-nos-install command to start installation.
ONIE# onie-nos-install PicOS.bin
The installer runs and after finishing installation will reboot automatically, the system will come up running the new network operating system.
NOTE：
|
Automated Installation Process
Step1 Make sure the switch is connected to DHCP and HTTP servers, and the PICOS installer image is downloaded to the HTTP server.
a) DHCP server configuration and starting DHCP server service:
host pica8-3922 {
hardware ethernet 70:72:cf:12:34:56;
fixed-address 192.168.2.50;
option default-url = "http://192.168.2.42/onie-installer-powerpc.bin";
}
b) Check if the .bin installation file is loaded onto the HTTP server:
root@dev:/var/www# ls index.html onie-installer-powerpc.bin
Step2 Execute the nos-boot-mode install command to enter ONIE installation environment.
admin@Xorplus$ sudo nos-boot-mode install
Step3 Type “yes” when the below prompt is shown, and the system will automatically complete the installation.
Type 'yes' to install NOS! Type 'no' to exit [no]/yes:
The installer runs automatically and will reboot the system after installation is completed.
NOTE：
|
Verifying Version after Installation
After system reboots automatically, the system will come up running the new network operating system.
admin@XorPlus$version Copyright (C) 2009-2017 Pica8, Inc. =================================== Hardware Model : as7712_32x Linux System Version/Revision : 2.10/e9c9eaf Linux System Released Date : 10/06/2017 L2/L3 Version/Revision : 2.10 /e9c9eaf L2/L3 Released Date :10/06/2017 OVS/OF Version/Revision : 2.10/e9c9eaf OVS/OF Released Date :10/06/2017
Copyright © 2025 Pica8 Inc. All Rights Reserved.