
Solarflare
Server
Adapter
User
Guide
Solarflare
Adapters
on
VMware
Issue
20
©
Solarflare
Communications
2017
270
5.7
Solarflare
Utilities
Package
support.solarflare.com/
‐
(Downloads
>
Linux
>
Misc).
The
utilities
(sfboot,
sfupdate,
sfkey,
sfctool)
can
be
built
on
a
standard
Linux
OS
server
i.e.
RHEL,
before
the
binary
utilities
are
extracted
from
the
RPM
package
and
copied
to
the
ESXi
host.
1
Download
package
SF
‐
105095
‐
LS
to
a
temp
directory
(e.g
/tmp)
on
a
standard
Linux
machine:
SF
‐
105095
‐
LS
‐
Solarflare_Linux_and_VMware_ESX_Utilities_Source.zip
2
Unzip
and
build
the
binary
RPM
in
the
temp
directory
from
the
source
package:
#
cd
/tmp
#
unzip
SF
‐
105095
‐
LS
‐
Solarflare_Linux_and_VMware_ESX_Utilities_Source.zip
#
rpmbuild
‐‐
rebuild
sfutils
‐
<version>.src.rpm
The
“Wrote…”
line
at
the
end
of
the
build
process
identifies
the
location
of
the
binary
RPM:
Wrote:
/root/rpmbuild/RPMS/x86_64/sfutils
‐
<version>.x86_64.rpm
3
Identify
where
the
binary
tools
would
be
installed
(but
don’t
actually
install
them):
#
rpm
‐
qlp
/root/rpmbuild/RPMS/x86_64/sfutils
‐
<version>.x86_64.rpm
/usr/sbin/sfaoepackage
/usr/sbin/sfboot
/usr/sbin/sfctool
/usr/sbin/sfkey
/usr/sbin/sfupdate
4
From
the
binary
extract
the
utility
tools
(sfupdate
example):
#
rpm2cpio
/root/rpmbuild/RPMS/x86_64/sfutils
‐
<version>.x86_64.rpm
\
|
cpio
‐
ivd
./usr/sbin/sfupdate
NOTE
the
.
(dot)
before
the
/usr/sbin/sfupdate
to
create
the
directories
and
copy
the
file
within
the
current
directory.
chanX
eventq.poll
Verifies
the
adapter’s
event
handling
capabilities
by
posting
a
software
event
on
each
event
queue
created
by
the
driver
and
checking
it
is
delivered
correctly.
The
driver
utilizes
multiple
event
queues
to
spread
the
load
over
multiple
CPU
cores
(RSS).
phy.bist
Examines
the
PHY
by
initializing
it
and
causing
any
available
built
‐
in
self
tests
to
run.
Table
62:
Adapter
Diagnostic
Tests
Diagnostic
Test
Purpose