Installer Discovery Methods: Default ONIE image server name onie-server

I have dns resolvable onie-server with onie-installer image files but the onie-discovery process does not seem to be trying to fetch the images.
ONIE:/ # nslookup onie-server
Server: x.x.x.x
Address 1: x.x.x.x
Name: onie-server
Address 1: x.x.x.x
ONIE:/ # ping onie-server
PING onie-server (x.x.x.x ): 56 data bytes
64 bytes from x.x.x.x : seq=0 ttl=121 time=5.228 ms
64 bytes from x.x.x.x : seq=1 ttl=121 time=1.221 ms
64 bytes from x.x.x.x : seq=2 ttl=121 time=1.113 ms

Any help?

6 replies

Userlevel 3
Just having an http server with the image is not enough. Something has to tell Onie where the file is so it can get it. Check out this link, and add the dhcp options to your setup. Jason
Jason Guy wrote:

Just having an http server with the image is not enough. Something has to tell Onie where the fil...

That is not true....
I have two Edgecore switches, kernel version 3.2.35 and 3.2.69.
The 3.2.69, without any help from the DHCP(no option 66 or 67) server, it used the DNS to resolve the 'onie-server' IP address, then it tried the http and tftp waterfall method and it worked, however the 3.2.35 did not even tried it.


Default ONIE image server name onie-server
If the default ONIE server name onie-server is resolvable by DNS it is included in the search for the default installer file names for both http and tftp protocols. The following URLs are attempted:

Here we go…

the ‘well known server name waterfall’ method is not available in onie version 3.2.35.

Looking at Github update documentation for;
“Update linux-3.2.35 to linux-3.2.69”
Image Discovery:
55b0b13 image discovery waterfall: add well known server name

Also, the latest onie version is 4.1.34
Userlevel 1
Hi -

I am glad that is sorted out for you.

A few notes on the term "version".

ONIE is a small operating system, consisting of a kernel plus several software components, which collectively makes up the "ONIE version".

The "ONIE version" where the feature was introduced is 2015.08.

The current version of ONIE is 2016.11. The next version will be 2017.02:

Features, like the waterfall discovery mechanism, are tied to an ONIE version.

The current "Linux kernel version" used by the kvm_x86_64 ONIE machine is 4.1.34.

A machine is free to use whatever "Linux kernel version" the hardware manufacturer wants, so long as the overall ONIE distribution implements the behaviors described in the specification.

The "Linux kernel version" may differ among machines for the same "ONIE version". The main reason for this is a particular CPU architecture (x86_64, powerpc, aarch64, arm32, etc..) may require a specific Linux kernel version, particularly for brand new "just released" chips. The overall behavior of ONIE, however, is consistent across.

Hi Curt,
Your name looks familiar from Github source code, also thanks for the "version" explanation, it does make sense and it kind supplements what I was looking on
Also, do you have a link on how to update between ONIE versions?
We are testing with arm-accton_as4610_54-r0 and x86_64-dell_s4000_c2338-r0, do you know if the current version of ONIE 2016.11 will work for these machines?

Userlevel 1
You should always use the ONIE version provided by the hardware vendor.

For Accton AS4610_54:

For Dell S4000:

The HW vendors also provide update instructions.

To update a 100 switches, the automated update instructions are recommended:

To update a single machine the manual method is recommended:

1. boot the machine in "ONIE rescue" mode

2. from the "ONIE#" prompt type "onie-self-update ", where points to the ONIE updater image:
ONIE# onie-self-update http://server/path/to/updater-image