Filter
Top Products
A–Troubleshooting
Collecting System Logs for Troubleshooting
A-10 FC0054607-00 A
Collecting System Logs for Troubleshooting
To collect all relevant data on the running system into one tar file, execute the
following command:
# vm-support
Frequently Seen Issues
Table A-8 lists some common issues and questions and provides tips for their
resolution.
Table A-8. Frequently Seen Issues
Issue Troubleshooting Tip
What is the SANsurfer FC HBA Manager pass-
word?
The password is config.
One specific adapter in the system has perfor-
mance issues, while all other adapters in the sys-
tem are okay.
Ensure that the adapter is plugged into a slot that
allows the adapter to use the full bandwidth avail-
able. Also check that the bus the adapter is on is
not shared by other high bandwidth PCI cards.
Errors similar to the following occur when the sys-
tem is booted up. In addition, the
ALT+Q
QLogic
BIOS banner is not shown; or FlashUTIL! is hang-
ing when trying to flash the adapters.
00180101 10772422 PCID device
resource allocation failure
00180101 10772422 PCID device
resource allocation failure
There are too many devices taking up extended
BIOS data area (EBDA) memory resources. To
free up enough resources to allow the adapters to
work properly, you can disable unused onboard
services such as Wake on LAN, PXE boot, and so
on.
Different target numbers can be assigned to the
various storage devices for the adapters on the
SAN. What is the correct method to assign persis-
tent bindings?
QLogic recommends that you assign the target
numbers of the devices in the same order on multi-
ple adapters. For example, if controller A of an
array is assigned to target 0 on HBA0, you should
assign controller B of an array to target 0 on HBA1,
and then continue this same methodology for all
targets and adapters. Note that the driver and OS
must be reloaded for the changes to take effect.
Rescanning an adapter port for target/LUN discov-
ery.
# esxcfg-rescan vmhba<X>
You can find the vmhba value corresponding to
an adapter port by examining the
/var/log/vmkernel log, where the adapter is
assigned a vmhba<X> vector.