Release Notes

uninstall libsmbios versions (and the dependent software) before installing Server

Administrator.

•

The USB arbitration service of VMWare ESX 4.1 makes the USB devices invisible to the

Hypervisor. So, when DUPs or the Inventory Collector runs on the MN, the partitions

exposed as USB devices are not displayed, and it reaches timeout after 15 to 20 minutes.

The timeout occurs in the following cases:

o When you start DSM SA Shared Service on the VMware ESX 4.1 managed node, it

runs the Inventory Collector. While the USB arbitration service is running, you must

wait for 15 to 20 minutes for the Inventory Collector to complete the execution

before attempting to stop this service, or uninstall Server Administrator.

o When you manually run the Inventory Collector (invcol) on the VMware ESX 4.1

managed node while the USB arbitration service is running, you must wait for 15 to

20 minutes before the operations end. The invcol output file has the following:

<Message> Inventory Failure: Partition Failure - Attach partition has failed</Message>

</SPStatus><SPStatus result="false" module="MaserIE -i">

<Message>Invalid inventory results.</Message>

</SPStatus><SPStatus result="false">

To fix the issue, stop the USB arbitration service and run the DUPs or Inventory

Collector. To stop the USB arbitration service, do the following:

1. Use ps aux | grep usb to find out if the USB arbitration service is running.

2. To stop the USB arbitration service during booting, use chkconfig

usbarbitrator off.

Reboot the server after stopping the usbarbitrator to allow the DUPs and/or the

Inventory collector to run.

If you require the usbarbitor, enable it manually. To enable the usbarbitrator, run

the command - chkconfig usbarbitrator on. (373924)

User Notes for Supported Red Hat Enterprise Linux, SUSE Linux

Enterprise Server, and VMware ESX Operating Systems

• Under certain conditions with DKMS versions prior to 2.0.9, device driver building may fail. This

may prevent Server Administrator installation. You may see the following error message:

"Building module: cleaning build area....(bad exit status: 2) make KERNELRELEASE=2.6.5-7.232-smp -

C src KSP=/lib/modules/2.6.5-7.232-smp/build MANDIR=%{_mandir}....(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.5-7.232-smp (x86_64)

Consult the make.log in the build directory

/var/lib/dkms/e1000/6.2.11/build/

for more information."