User guide

E–ULP Troubleshooting
Troubleshooting VirtualNIC and VIO Hardware Issues
E-2 IB0054606-02 A
Verify that the proper VirtualNIC driver is running
Check that a VirtualNIC driver is running by issuing an lsmod command on the IB
host. Make sure that the qlgc_vnic is displayed on the list of modules.
Following is an example:
st186:~ # lsmod
Module Size Used by
cpufreq_ondemand 25232 1
cpufreq_userspace 23552 0
cpufreq_powersave 18432 0
powernow_k8 30720 2
freq_table 22400 1 powernow_k8
qlgc_srp 93876 0
qlgc_vnic 116300 0#
Verifying that the qlgc_vnic.cfg file contains the correct
information
Use the following scenarios to verify that the qlgc_vnic.cfg file contains a
definition for the applicable virtual interface:
Issue the command ib_qlgc_vnic_query to get the list of IOCs the host
can see.
If the list is empty, there may be a syntax error in the qlgc_vnic.cfg file (e.g., a
missing semicolon). Look in /var/log/messages at the time qlgc_vnic was
last started to see if any error messages were put in the log at that time.
If the qlgc_vnic.cfg file has been edited since the last time the VirtualNIC
driver was started, the driver needs restarted. To restart the driver, so that it uses
the current qlgc_vnic.cfg file, issue a /etc/init.d/qlgc_vnic restart.