The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can unload the sNIC driver, but uninstalling the sNIC drivers requires uninstalling the OS.
To unload an sNIC driver that is in use, reboot the host.
| Command or Action | Purpose |
|---|
This example shows how to unload sNIC drivers:
# modprobe -r snic
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.
If you are booting from SAN storage, you cannot remove the existing fNIC driver using the rmmod fNIC command because this driver is required to use the SAN LUNs. Instead, enter the rpm --erase old-kmod-fnic-rpm-name command to erase the old RPM.
Feedback