Intel® Modular Server System MFYSY25 P2.2.3 Unified Firmware Update Release Notes & Installation Instructions Copyright © 2007-2008 Intel Corporation All Rights Reserved May 30, 2008 RELEASE NOTES FOR: P2.2.3 A. RELEASE PACKAGE CONTENTS This section enumerates the contents of the release package. • BIOS: SB5000.86B.10.00.0043.041620081415 • BMC: 1.30.3 • Management Module GUI operation Code: 1.3.100.20080527.11328 • Remote KVM Java Applet – 1.39 • EBF: 1.24 • Storage o IOP FW/SW: 2.91.0140.45 o IOP SW: 2.91.0140.45 o Expander FW: 1.03.0140.01 o Redboot image: 1.01.0140.08 • Switch Boot Code: 1.0.0.6 • Switch FW: 1.0.0.25 • Fan Controller Op code – 01.1 • Fan Controller Boot Block – 01.2 • MIB files B. GENERAL INFORMATION This release does not support rollback to previous versions of the Unified Firmware Update (UFU) package. This release supports system configurations with only one SCM in Slot SCM1. C. DEPENDENCIES The system must be at firmware level P2.07 or P2.2.2 prior to starting this update. D. DEFECTS FIXED IN THIS RELEASE Area Description CMM GUI General usability improvements throughout the Modular Server Control GUI. Improvements include but are not limited to the following areas: • Help content improvements • Sensor labels modified for easier identification • Improved dialog instructions and labels to create and manage Storage Pools and Virtual Drives • Added additional help links to the Create Virtual Drive dialog box. • Optimized button locations for Edit Ports dialog • Edit User dialog • Storage Layout reformatted • Fixes for diagnostic dump • Error messages updated to provide additional information BIOS Mixed Processors population will report incorrect CPU information. CMM GUI New Storage Pool Expanded size is displayed before migration completes or unallocated space is displayed. BIOS Mezzanine NIC/MAC information not available in SMBIOS (Type 10 and/or Type 177) SW Components being reported as 'unmanageable' during known down-states such as rebooting after FW update. Remote Apps Keyboard/mouse error during a remote Windows Server 2008 installation BIOS Fault led is not illuminated for some critical errors Remote Apps Sometimes rSOL loses connection. CMM GUI When designating a HDD as a spare drive for a storage pool IE will crash if the selected HDD is smaller than the drives currently in the storage pool. CMM GUI Delete a virtual drive when the storage pool is migrating fails with no error message CMM GUI SCM - Expansion Port - confirmation Window does not list all the Servers granted access Remote Apps Simultaneous installs of OS or applications fail. BIOS A bad DIMM (NO SPD) in A1 and a good DIMM in A2 generates unexpected POST code. CMM GUI Non-admin user's edits to Email Alerts do not stick CMM GUI No critical error or fault indication when a SCM is pulled Storage Module There is no indication that the SEP is flashing code CMM GUI Invalid E-Mail Message Title BIOS SEL Timestamp Ahead One Day CMM GUI Chassis SNMP agent fails diagnostics test when SNMP community string is changed BMC After resetting the BMC the SOL client will become un-manageable. After rebooting the Server the problem goes away. CMM GUI Create virtual drive action not available after a Storage Pool expansion is initiated. CMM GUI Not all Battery Data is displayed CMM GUI Internal Communication Test do not distinguish between power supplies and fan blanks SW FW Update manager reporting BMC update pending when BIOS update is queued. CMM GUI Start Rebuild action has problems when a bad drive is missing or if the replacement drive size does not match original drive size. CMM GUI Fully loaded system shows max expected load in the red on the dashboard with 3 power supplies. Should display as yellow. Storage Module Hot spare drive after rebuild does not show "force drive offline" menu item Storage Module Disk drive array WWN and Operational Status are wrong after a storage pool rebuild CMM GUI STALE drives are candidates for rebuild, but start rebuild action fails if one is chosen as rebuild candidate Remote Apps Mouse Acceleration values through the rKVM menus do not properly check for valid ranges CMM GUI Error popup on storage layout when there are drives not present CMM GUI Start Rebuild action: Don't allow STALE drive from another storage pool to be a rebuild candidate CMM Missing SWM (ESM) on CMM startup prevents servers from coming out of Unfit state CMM GUI User allowed to set no password for Admin, notified of change, but change never takes effect. CMM Compute servers appearing stuck in updating or initializing. CMM GUI Communication Error while trying to power on Server 2 CMM Action reset failure on Management module Remote Apps rKVM redirection menu activated with BIOS F10 hotkey Storage Module Some LDs are reported "unreadable" at server Storage Module After insert/extract drive is left in strange state that GUI actions can not resolve CMM GUI Message about javascript being blocked in IE when viewing diagnostic dump CMM GUI Powered-off compute modules GUI displays critical Red-X. CMM GUI Some drives/storage pools with less than GOOD health not listed in Dashboard Storage hover-data Remote Apps Remote KVM unstable via windows client OS while installing office application with Linux OS. CMM GUI Progress events not logged into CMM GUI. CMM GUI Detailed description does not display correct information in CMM GUI. CMM Server module failed to power on via GUI CMM GUI The rKVM session disconnected when booting the server into Windows 2003 from standby or hibernate mode. Storage Module Expanding a virtual drive using non contiguous space in a storage pool could result in a corrupt storage configuration CMM GUI SCM reset dialog doesn't always wait for the reset to complete. Storage Module Storage Pool unconfigured capacity is incorrect when deleting Virtual Drives out of order. CMM GUI A user with Chassis Administrator: Read Only rights can initiate a firmware rollback CMM GUI Virtual drive name substitution error CMM GUI Extra data associated with events is not currently supported in e-mails. CMM GUI Unable to login to the UI after firmware update or Restore Settings. CMM GUI Event without corresponding event policies are dropped from the event log. CMM GUI IPMI request/responses to/from the server become out of sync. CMM SNMP not correctly reporting mezzanine NICs. CMM GUI Incorrect popup information displayed when LUN is reassigned. • Cooling Algorithm updates - This release contains updates to the CMM cooling algorithm to cover several PSU cooling corner cases. This release MUST be used if the customer will be using the ASE kit. E. NEW FEATURES/FUNCTIONS IMPLEMENTED IN THIS RELEASE • Restore System Settings – Restore system settings to last automatic backup version or factory defaults while optionally preserving important information such as network settings and administrator password. This feature enables a user to restore the below system configuration settings: o Users and Passwords used to access the Modular Server Control GUI o Network configuration (CMM IP address) o Event policies o Notification settings o SNMP Configuration • New Storage Layout Table View – This release includes a tabular view of the Storage Layout configuration. Users can quickly switch between the Graphic view and the Table view. • OEM logo customization - This release contains an enhancement to the existing OEM customization support of the BIOS boot logo (splash bitmap) so that the logo is persistent from one FW update to the next. • Configurable CMM Host Name - The CMM Host name can be modified on the IP Configuration screen. F. KNOWN ISSUES • Reset BIOS default settings - Certain settings and features such as Remote USB (essential for proper Remote KVM operation) may not be functional until BIOS Defaults are loaded. To ensure proper operation, reset BIOS defaults as soon as possible after updating BIOS. BIOS defaults are set by pressing F9 (Reset To Defaults) while in BIOS Setup. • GUI inconsistencies with physical state - The GUI can be inconsistent with the state of the system because this is a web application. If you suspect an inconsistency, just reload the page (the page automatically refreshes once a minute). Some HW inventory changes (such as compute module insertion) can take up to 60 seconds to be reflected in the GUI unless you push the refresh button. The application may also appear inconsistent with the real state of the system if you have connectivity issues with the CMM. • SCM reset immediately after update NOT REQUIRED as indicated. Immediately after the SCM firmware is updated (and the rotating symbol stops in the firmware update page for the SCM1 row), the FW page may say 'Update is pending/queued. Reset Required'. You do not have to reset the SCM again. Please wait for a minute and refresh the firmware page and the correct SCM firmware version will be displayed. If you do nothing and just wait on the FW page, the normal refresh will occur within 2 minutes and it will reflect the correct SCM firmware version. • Complete System Diagnostics - Under synthetic stress test it is possible although rare for the SCM to reset if the user requests an All Subsystems diagnostics also called Complete System diagnostics. Prior to running the All Subsystems diagnostics feature the user should first power off all server modules within the chassis. • CONFIRM dialog box action - Any dialog box which prompts the user to type "confirm" before clicking OK in order to perform an action will actually complete the specific action if the user clicks OK without typing "confirm". The action will complete if the user leaves the box blank or types any combination of letters including "confirm" before clicking OK. • MIB Files: 1. MIB files provide read only access to system information. System management and configuration are handled via the Modular Server Control GUI. Read/Write access will be available in future release. • Remote applications: 1. When starting rKVM with a Linux host, you must change the mouse mode to relative mode. If the remote mouse does not respond to local mouse movements, try switching to absolute mode and then immediately back to relative mode. 2. Due to the way Linux handles the mouse (relative vs. absolute) there are instances when the remote mouse on a Linux host will be slow or appear to stop functioning. Many times a stuck mouse can be awakened by toggling between relative and absolute mouse modes via the menu or the keyboard by pressing Alt-s. 3. If the local and remote mouse pointers do not synchronize (the remote mouse moves but is offset from the local mouse), try toggling the Synchronize mouse option. If that does not work, check the mouse acceleration parameters on the server with the command "xset q". Set the mouse acceleration settings in Remote KVM in the Options menu to match those on the server. By default, the Remote KVM application will use an acceleration value of 2 and an acceleration threshold value of 4. These values are what the Red Hat Enterprise Linux Server 5 (RHEL5) and SuSE Linux Enterprise Server (SLES) operating systems expect, unless they have been modified after installation of the OS. 4. If the Internet connection is lost during an existing RKVM session, the session will report video data lost. The user must close the message, and restart the session. 5. Lost Keyboard/Mouse usage in SLES can sometimes be recovered by toggling full screen on and off. 6. Remote media is best used with one server at a time. If you map a CD to six compute modules, the compute modules will drop the CD mapping, due to latency issues. 7. The RKVM client version included in this release is 1.32. Check the version after installing the new release by launching the RKVM application and then using Help->About in the RKVM client window menus. If the version is something other than 1.32, close all RKVM client windows and delete the application from the client machine's Java browser cache. (Run 'javaws - viewer', select the application titled 'Networked KVM applet' and press the delete key.) 8. Remote Floppy is not supported during a RKVM session. 9. Pressing F1 during a RKVM session will bring up the local KVM console help not the remote system application help. G. INSTALLATION INSTRUCTIONS Preparing For Update: • Download the current Unified Firmware Update package MFSYS25_UFU_P2_2_3.zip for the MFSYS25 system (including the MFS5000SI Compute Module) o Copy the CMM_Core.zip file to a folder labeled P2_2_3 on a formatted flash drive. CMM_Core.zip is the update package and is loaded as a zip file by the CMM Firmware Update tool. Do not modify the file name, otherwise it will not be recognized by the Update tool. • If you have not already done so, connect the appropriate power cords to the Modular Server System power supplies and wait for the chassis management module to fully boot: approximately 3-4 minutes, when the CMM is fully booted the system cooling fans will slow down • Prior to loading and using the P2.2.3 unified software update – all server modules in the system must be powered down. • Ensure that no Storage Pool or Virtual Drive build or rebuild operation is in progress. If a build, rebuild, or migration operation is in progress, allow the operation to complete before attempting to update the firmware via the Unified Firmware Update package. Unified Firmware Update from P2.0.7 to P2.2.3: 1. Launch a browser from a client system connected to the CMM 2. Login into the GUI and browse to the Firmware tab (bottom selection in the left navigation pane. 3. Ensure all servers are powered down, then click on the browse button and browse to the folder P2_2_3 you previously created, select the CMM_Core.zip file and the update will automatically begin. 4. The upload process may take several minutes – a progress bar is displayed. 5. After the file has been uploaded, the screen will display “A new Firmware File has been uploaded with build version 1.3.100.20080527.11328. 6. A box below this message labeled Actions will state – This update can not be started until the following actions have been completed: Reset Storage Control Module 1 into Safe Mode. Click on the link. 7. It will then go to a screen that says Reset Controller SCM1 with a box checked that says “Come back in safe mode after reset.” Type CONFIRM and hit Apply. The screen will then display “Reset of Controller SCM1 to Safe Mode started. Controller will reset and return in a few minutes.” Hit OK. 8. Wait 60 seconds, then return to the Firmware Update page, and click on the “Start Update” button. 9. A dialogue box will appear – select the “Reboot CMM & Start Update” button. (fans will speed up and then return to normal as the CMM restarts) 10. Login to the GUI when prompted. 11. Browse to the Firmware tab and scroll down to the installed compute module line, each installed server will show an update to 1.30.3 12. Scroll down to the Storage Controller line item. The Storage Controller 1 line item in the Firmware tab will change, indicating that the SCM update is in process. Most updates will take 10 minutes. Do not disturb the system until the update is complete and the Storage Controller Module version is shown to be 2.91.140.45. • Note: If the FW page states ‘Update is pending/queued. Reset Required’. You do not have to reset the SCM again. Please wait for a minute and refresh the firmware page and the correct SCM firmware version will be displayed. If you do nothing and just wait on the FW page, the normal refresh will occur within 2 minutes and it will reflect the correct SCM firmware version. 13. Do NOT move the SCM to slot 2 – it should remain in Slot 1 only for all future use. 14. When the SCM update is complete, the CMM will automatically update the BIOS for each installed compute module as necessary. 15. Continue with steps below starting at step 16 under Complete BIOS Update section Unified Firmware Update from P2.2.2 to P2.2.3: 1. Launch a browser from a client system connected to the CMM 2. Login into the GUI and browse to the Firmware tab (bottom selection in the left navigation pane. 3. Ensure all servers are powered down, then click on the browse button and browse to the folder P2_2_3 you previously created, select the CMM_Core.zip file and the update will automatically begin. 4. The upload process may take several minutes – a progress bar is displayed. 5. After the file has been uploaded, the screen will display “A new Firmware File has been uploaded with build version 1.3.100.20080527.11328. 6. A box below this message labeled Actions will state – This update can not be started until the following actions have been completed: Reset Storage Control Module 1 into Safe Mode. Click on the link. 7. It will then go to a screen that says Reset Controller SCM1 with a box checked that says “Come back in safe mode after reset.” Type CONFIRM and hit Apply. The screen will then display “Reset of Controller SCM1 to Safe Mode started. Controller will reset and return in a few minutes.” Hit OK. 8. Wait 60 seconds, then return to the Firmware Update page, and click on the “Start Update” button. 9. A dialogue box will appear – select the “Reboot CMM & Start Update” button. (fans will speed up and then return to normal as the CMM restarts) 10. Login to the GUI when prompted. 11. Browse to the Firmware tab and scroll down to the installed compute module line, each installed server will show version 1.30.3 12. Scroll down to the Storage Controller line item. The Storage Controller 1 line item in the Firmware tab will indicate that the Storage Controller Module version is 2.91.140.45. 13. Do NOT move the SCM to slot 2 – it should remain in Slot 1 only for all future use. 14. Continue with steps 24 and 25 below under Verify Updates Completed and Load Defaults section. Complete BIOS Update: 16. After verifying the BMC was updated on all servers, the BIOS status will show “Updates Pending – Power on required”. You can either click on the link, and follow the prompts to power on the server via the software OR you can manually power up all servers installed in the system via the front panel buttons. Note: Multiple servers can be powered on at the same time. The firmware update process can now update multiple servers at the same time. 17. A dialogue box will appear – Click “Apply” to power on servers. 18. Navigate to the Firmware screen. The status of each of the powered on server modules will show a BIOS Status of “Updates Pending (power on in progress)”. 19. Once the power on is complete the status may change to “Updates Pending - reset required”. DO NOT CLICK ON THIS LINK – wait a few minutes and the BIOS update will begin automatically. 20. The BIOS status will eventually display “BIOS updating to SB5000.86B.10.00.0043….”. 21. Once the BIOS update has completed, the Firmware Status page in the GUI will show the BIOS status as “OK” and the version SB5000.86B.10.00.0043 will be displayed. 22. Repeat steps 16 – 21 for each server populated in the system. 23. Continue with steps below starting at step 24 under Verify Updates Completed and Load Defaults section. Verify Updates Completed and Load Defaults: 24. Login to the GUI and browse to the Firmware tab (bottom selection in the left navigation pane. 25. At the top of the Firmware page – verify the Current Build Version is 1.3.100.20080527.11328. 26. Verify the BMC Firmware line under each installed server shows as 1.30.3. 27. Enter BIOS setup on each server to verify BIOS update completed successfully and to load default settings. To restart a server and enter BIOS setup remotely using the Modular Server Control GUI follow the steps below: a. From the Server screen, select a server and click the Remote KVM & CD action item to start a remote KVM session. b. Restart the selected Server either from within the Remote KVM session or by selecting the Reset action within the Modular Server Control GUI for the selected Server. 28. On boot Enter BIOS Setup by pressing “F2” when prompted. 29. Verify the BIOS flashed successfully by entering BIOS setup, on the first tab, the “System BIOS” version displayed should be SB5000.86B.10.00.0043. 30. Verify the BMC was correctly updated by scrolling to the Server Management tab, scroll down to System Information and hit enter – the BMC Firmware version listed should be 1.30.3. 31. Prior to loading default BIOS settings document all custom BIOS settings. Then press F9 to load system default settings. Modify default settings as necessary to match documented custom settings previously used and Press F10 to save and exit. 32. Repeat steps 25 through 29 for each server to verify BIOS and BMC versions and load default settings. LEGAL INFORMATION Information in this document is provided in connection with Intel Products and for the purpose of supporting Intel developed server boards and systems. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel’s Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Intel is a registered trademark of Intel Corporation. *Other names and brands are the property of their respective owners. Copyright © 2007-2008 Intel Corporation.