wikiInstallation NICCLI under Proxmox VE
This article explains how to install the Configuration Utility NICCLI of Broadcom on your Proxmox server.
More information on common commands of NICCLI can be found at: Broadcom NICCLI Configuration Utility
Download NICCLI
First, download the latest version of Utility in the download area of your network card at Broadcom. In the following, there is an example for a P225P network card: Broadcom NICCLI Utility
Hint: The download link is the same for all network cards. Therefore, you do not have to download different Utilities for several different network cards.
After this, you can unpack the ZIP file on your device and upload the Linux folder, with for example FileZilla, on your server.
If the upload is successful, the folder should be displayed in the shell:
root@PMX6:~# ls Linux root@PMX6:~#
Installation NICCLI Utility
For the installation of the same tool, go to the directory /Linux/Linux_x86_64
root@PMX6:~# cd Linux/linux_x86_64/ root@PMX6:~/Linux/linux_x86_64# ls niccli-230.0.163.0-1.x86_64.rpm niccli_230.0.163.0-1_x86_64.deb niccli-230.0.163.0-linux_x86_64.tar.gz root@PMX6:~/Linux/linux_x86_64#
There are displayed three files again (.deb, .rpm und .gz) angezeigt. For the installation on the node, you need the .deb file. For this, perform the following command:
root@PMX6:~/Linux/linux_x86_64# apt install ./niccli_230.0.163.0-1_x86_64.deb Selecting previously unselected package niccli. (Reading database ... 156553 files and directories currently installed.) Preparing to unpack niccli_230.0.163.0-1_x86_64.deb ... Unpacking niccli (230.0.163.0) ... Setting up niccli (230.0.163.0) ... root@PMX6:~/Linux/linux_x86_64#
After this, you can verify your installation when you switch optionally to the directory /opt/niccli and perform niccli:
root@PMX6:/opt/niccli# niccli
-------------------------------------------------------------------------------
Scrutiny NIC CLI v230.0.163.0 - Broadcom Inc. (c) 2023 (Bld-61.52.25.90.16.0)
-------------------------------------------------------------------------------
BoardId MAC Address FwVersion PCIAddr Type Mode
1) BCM57508 84:16:0C:6F:3D:F0 226.0.145.1 00:01:00:00 NIC PCI
2) BCM57508 84:16:0C:6F:3D:F1 226.0.145.1 00:01:00:01 NIC PCI
3) BCM57416 00:62:0B:32:1E:C0 226.0.145.0 00:41:00:00 NIC PCI
4) BCM57416 00:62:0B:32:1E:C1 226.0.145.0 00:41:00:01 NIC PCI
5) BCM57504 00:62:0B:6F:C2:C4 226.0.145.1 00:81:00:00 NIC PCI
6) BCM57504 00:62:0B:6F:C2:C5 226.0.145.1 00:81:00:01 NIC PCI
7) BCM57504 00:62:0B:6F:C2:C6 226.0.145.1 00:81:00:02 NIC PCI
8) BCM57504 00:62:0B:6F:C2:C7 226.0.145.1 00:81:00:03 NIC PCI
Enter the target index to connect with :
Now, all ports of your Broadcom network card should be displayed and you can start with the configuration.
Known issues
If it is about elder installation packages, so-called Sliff Driver are required. When the installation of the package was made with the help of dpkg, it could be that dependence problems with the packages are displayed in the prompt:
root@PMX6:~/Linux/sliff# dpkg -i sliff-dkms_230.0.163.0_all.deb Selecting previously unselected package sliff-dkms. (Reading database ... 93084 files and directories currently installed.) Preparing to unpack sliff-dkms_230.0.163.0_all.deb ... Unpacking sliff-dkms (230.0.163.0) ... dpkg: dependency problems prevent configuration of sliff-dkms: sliff-dkms depends on dkms (>= 1.95); however: Package dkms is not installed. dpkg: error processing package sliff-dkms (--install): dependency problems - leaving unconfigured Errors were encountered while processing: sliff-dkms root@PMX6:~/Linux/sliff#
Workaround
apt --fix-broken install
When you perform the command for the installation of the Sliff Driver again, your host may display that the kernel headers are not installed:
root@PMX6:~/Linux/sliff# dpkg -i sliff-dkms_230.0.163.0_all.deb (Reading database ... 124007 files and directories currently installed.) Preparing to unpack sliff-dkms_230.0.163.0_all.deb ... Deleting module sliff-230.0.163.0 completely from the DKMS tree. Unpacking sliff-dkms (230.0.163.0) over (230.0.163.0) ... Setting up sliff-dkms (230.0.163.0) ... Loading new sliff-230.0.163.0 DKMS files... Building for 6.2.16-15-pve Building for architecture x86_64 Module build for kernel 6.2.16-15-pve was skipped since the kernel headers for this kernel do not seem to be installed. root@PMX6:~/Linux/sliff#
Here you can see that the kernel headers of a certain build are not installed, so you have to install the kernel headers again.
A similar error appears after the installation of NICCLI when executing the command:
root@PMX6:~# niccli modprobe: FATAL: Module sliff not found in directory /lib/modules/6.2.16-15-pve Unable to load required sliff module. Please see /opt/niccli/Readme.txt
Perform the following command in both cases:
apt install pve-headers-$(uname -r)
After this, the installation of the Sliff Driver runs through successfully:
root@PMX6:~/Linux/sliff# dpkg -i sliff-dkms_230.0.163.0_all.deb (Reading database ... 156553 files and directories currently installed.) Preparing to unpack sliff-dkms_230.0.163.0_all.deb ... Module sliff-230.0.163.0 for kernel 6.2.16-18-pve (x86_64). Before uninstall, this module version was ACTIVE on this kernel. sliff.ko: - Uninstallation - Deleting from: /lib/modules/6.2.16-18-pve/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... Deleting module sliff-230.0.163.0 completely from the DKMS tree. Unpacking sliff-dkms (230.0.163.0) over (230.0.163.0) ... Setting up sliff-dkms (230.0.163.0) ... Loading new sliff-230.0.163.0 DKMS files... Building for 6.2.16-15-pve 6.2.16-18-pve Building for architecture x86_64 Module build for kernel 6.2.16-15-pve was skipped since the kernel headers for this kernel do not seem to be installed. Building initial module for 6.2.16-18-pve Done. sliff.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.16-18-pve/updates/dkms/ depmod...
In order to reload the headers and use the drivers, you must reboot the server.
 |
Author: Niklas Pauli Niklas Pauli works in the product management team at Thomas-Krenn. He completed his general university entrance qualification at Freyung High School and then his training as an IT specialist for system integration at Thomas-Krenn.AG. After completing his training, he continued to work in the areas of Proxmox VE incl. Ceph, backup (Proxmox, Veeam, SEP). He is also a regular writer for the Thomas-Krenn-Wiki.
|
 |
Translator: Alina Ranzinger Alina has been working at Thomas-Krenn.AG since 2024. After her training as multilingual business assistant, she got her job as assistant of the Product Management and is responsible for the translation of texts and for the organisation of the department.
|
