Owner's Manual

file:///T|/htdocs/SOFTWARE/smbmcmu/BMCMU_3_0/en/readme/readme.txt[10/26/2012 11:28:52 AM]
* The Linux operating system shell prompt has a path cache that
can under some circumstances cause a different ipmish to be
invoked if ipmish is execute immediately after it is installed.
To resolve this, type "hash -r" at the same shell prompt to clear
the cache and then execute ipmish.
* To run ipmitool inband on Windows 2003 R2 systems, the Windows
IPMI driver needs to be installed. For instructions on how to
install the driver, visit the following web address:
http://technet2.microsoft.com/windowsserver/en/library/8c6c90e8-16b8-4d51-bf1e-efad5f5a61081033.mspx?mfr=true
* Running ipmitool on Linux systems requires the OpenIPMI driver
to be installed and running. Use the command "service ipmi start"
to start the ipmi service at runtime, and "chkconfig ipmi on" to
start the services automatically at boot.
#####################################################################
Known Issues
#####################################################################
This section provides information concerning open issues with systems
management software.
=====================================================================
Issues For Dell PowerEdge(TM) 1855 System
=====================================================================
The following apply only for the Dell PowerEdge 1855 system:
* Any host application that communicates with port 623 cannot be
executed from LOM_1 (the first one) of a server module. If you
attempt this, the network packets will be sent to the BMC instead
of the host. So use LOM_2, and ensure that the IP address, IP
subnet mask, and the gateway settings for the LOM_1 and the BMC
match to prevent possible network disruptions.
* The following subsection explains how to identify and resolve a
possible IP address conflict.
Problem: An "IP address conflict" message is displayed after
assigning identical IP addresses to Local Area Connection and the
BMC as instructed.
Cause: When the operating system first detects hardware devices
such as the onboard network adapters, the order in which the
devices are enumerated is not guaranteed. Therefore, LOM_1
(the first one) may be assigned Local Area Connection #2 and LOM_2
may be assigned Local Area Connection #1. Due to this switch, when
you assigned identical addresses to the BMC and Local Area
Connection, in reality, identical addresses are being assigned to
the BMC and LOM_2. This creates the IP address conflict.