ISM Errata: Important Information about ISM 5.5.5 For Your HP cc3310 Carrier Grade Server

5
Platform Instrumentation (PI)
1. BMC/BIOS will not maintain changes to dynamic IP address unless ISM PI component is running.
PROBLEM: If you configure a DHCP (dynamic) IP address for a server using the SSU or Client SSU, the IP address
is maintained by the Baseboard Management Controller (BMC). Ordinarily, a floating IP address will expire from
time to time and the server is notified by the DHCP server of the new IP address. However, under certain
circumstances the BMC/BIOS will retain the expired address, causing a network conflict with the entity that now has
been assigned that IP address. This occurs if:
o The ISM PI component is not installed or is not running on the server (a PI agent keeps the BMC’s IP in sync
with the OS’s IP address)
or
o The OS is not running (for example, the server is in standby mode or is running only DOS)
Under these circumstances, the BMC may issue LAN Alerts or Gratuitous-ARP broadcasts (which are enabled by
default) using the expired IP address, until the server is brought back to running the OS. This can occur on the SCB2,
SDS2, or later platforms.
IMPLICATION: Network traffic may be slow or exhibit access problems.
WORKAROUND: Configure the DHCP server to issue only a “fixed” DHCP address to any servers using the BMC.
Then the DHCP server will always issue the same IP address to those servers. You cannot use the SSU to do this,
but must configure it directly on the DHCP server. Alternatively, you can use SSU to assign a Static IP address to
the server, and not use DHCP.
2. Unloading SENSOR.NLM may show a small number of short-term memory allocations that were not free.
PROBLEM: SENSOR.NLM may not free all memory associated with some functions. This will cause NetWare to
display a message when it frees the memory after unloading the NLM.
IMPLICATION: A small amount of memory will be used and will not be made available again until the NLM is
unloaded. This should not be a significant number of bytes and should not impact server performance.
WORKAROUND: No workaround has been identified.
3. The ISM Console health indication might not correctly display current health status for servers running the Red Hat
Linux operating system.
PROBLEM: The colored icon representing health status displayed in the ISM Console for servers running Red Hat
Linux 8.0 might not be the same as the colored icon displayed in the PIC user interface. This situation only occurs
in servers running Red Hat Linux and using a static IP address. In this situation, the health icon displayed in PIC
represents the correct current health status, while the icon displayed in the ISM Console represents an incorrect health
status. The condition is caused by the DMI Service Provider running under Red Hat Linux. Servers running Red Hat
Linux 8.0 which use DHCP and have access to a DNS server for name/address resolution, do not experience this
problem.
IMPLICATION: The user might see conflicting health information if comparing the colored icon in the ISM
Console interface to the colored icon in the PIC interface. For these cases, the icon displayed in the PIC interface is
correct. All actions and logging of system events continue to operate correctly.
WORKAROUND: If the managed server running Red Hat Linux 8.0 is configured with a static IP address, the
following steps will resolve the issue.
a. Edit the “hosts” file (located in "/etc" folder).
b. Add the IP address of the server along with the server name, if it is not already in the file. (for example,
10.7.180.45 scb2_45).
c. Save the edits.