If the management connection is over the eNIC, Cisco recommends
using the serial or KVM console to complete the driver installation. Completing
an rmmod of the current driver results in a loss of eNIC network connectivity.
Note |
On SLES 12 SP1 and later, the Cisco eNIC and usNIC drivers are bundled together in to a single RPM (vs. being packaged in
separate RPMs, as they are for other Linux distributions). Bundling both drivers into a single RPM is necessary because of
how kernel module dependencies are managed in SLES 12 SP1 and later. If you are not using Cisco usNIC functionality, the usNIC
driver will effectively be ignored.
The eNIC and usNIC drivers have their own distinct version numbers. If you install the cisco-enic-usnic RPM on SLES 12 SP1 or later, once those drivers are loaded into the running kernel (e.g., via rebooting), use cat /sys/module/enic/version and cat /sys/module/usnic_verbs/version to view their respective version numbers. The cisco-enic-usnic RPM has its own distinct version number as well. Because it represents the packaging of the eNIC and usNIC drivers, the RPM
version number may look similar, but does not reflect the specific version of either driver. You can also query the Description
of the RPM to see exactly what versions of the drivers will be installed.
|
The following shows a sample query of the Description of the RPM to view the driver versions to be installed:$ rpm -qip cisco-enic-usnic-kmp-default-<RPM_VERSION>.x86_64.rpm
Name : cisco-enic-usnic-kmp-default Relocations: (not relocatable)
...
Summary : Cisco VIC Ethernet NIC drivers
Description :
This RPM contains both the Cisco VIC Linux Ethernet driver (enic.ko,
version <ENIC_VERSION>) and the Cisco Userspace NIC (usNIC) Linux
Ethernet driver (usnic_verbs.ko, version <USNIC_VERSION>). Some
Linux distros require both kernel modules to be in the same RPM in
order to properly test for symbol compatibility (because
usnic_verbs.ko depends on enic.ko) when installing into post-GA
upgrade kernels.