HP Storage Platform 2.1 Release Notes

• Incorrect status reporting the storage is degraded when it is not occurs because the monitoring

software did not know that the credentials to the storage array had been changed and could not

communicate with the array and became confused. A future release will correct the events and

make them more useful.

The following are known hardware monitoring issues on any HPSP Platform:

• Platform hardware monitoring software does not notice updates by FMT for up to 24 hours. You

may force a re-evaluation of the installed firmware versions by the monitoring system by applying

the tip below:

TIP:

If the diagnostic message to perform updates persists after performing the update, you

can force a re

-evaluation of the installed firmware versions by issuing this command to the

platform monitor:

hpspmonControl --refresh

Networking

The following section describes known issues with networking functionality:

• In the 9730 platform, when a blade is reseated, the Onboard Administrator may allow it to be

manually powered on before the Virtual Connect profile is applied. If the blade is powered up

before a Virtual connect profile can be assigned to the server the server will have only 2 Ethernet

devices (eth0 and eth1) instead of eight (eth0 through eth7). The result is that server comes up

with no networking, there may be an error in the Onboard Administrator and on POST of the

server you may see lots of “……xxxxxxx….xxxxx…” when the NIC is bannering. The Virtual

Connect could have the error of “Profile pending” for the blade bay in question or it can look

correctly configured.

To resolve this issue, follow these steps:

1. Power down the blade and let it sit powered off for 10 minutes. If you are watching the

OA GUI at this time you will see the blade change from “Configured for Virtual Connect”

to “Not configured for Virtual Connect” and then back. It is then safe to boot the blade. If

for some reason you do not see this change take place then proceed to step 2 using the

Virtual Connect GUI.

2. In the Virtual Connect GUI navigate to the assigned profiles and the profile for the bay in

question. Remove the profile from the blade bay and then re assign the profile back to the

blade bay. Once the Onboard Administrator says the blade is “Configured for Virtual

Connect” you can then power on the blade.

This procedure will be included in the next edition of the troubleshooting volume of the 9730

platform guide. The root cause of the problem will be fixed in a future release of Virtual Connect

firmware.

HPSP 2.1 Release Notes