Intel® Modular Server System MFYSY25 P2.0.7 Unified Firmware Update Release Notes & Installation Instructions Copyright © 2007-2008 Intel Corporation All Rights Reserved January 25, 2008 RELEASE NOTES FOR: P2.0.7 A. RELEASE PACKAGE CONTENTS This section enumerates the contents of the release package. • BIOS: SB5000.86B.10.00.0035 • BMC: 1.27.1 • Management Module GUI operation Code: 1.2.100.01242008.9431 • Remote KVM Java Applet – 1.32 • EBF: 1.23 • Storage o IOP FW/SW: 2.91.140.11 o IOP SW: 2.91.140.11 o Expander FW: 1.02.140.81 o Redboot image: 1.00.140.52 • 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. DEFECTS FIXED IN THIS RELEASE Area Description BMC Compute Module may not power on after BMC update following AC cycle BMC Remote Console Output Errors and Local Console Controller Errors BMC Add support in the BMC for tracking BIOS Version in order to enable single-reboot BIOS update BMC Addressed remote console errors while in EFI. Chassis Compute Module may become unmanageable, indicating FW update is in process , when there is no firmware update in progress. GUI Changed temperature reporting in CMM GUI from Farenheit to Celsius GUI CMM Email Forwarding of events will not work when a MS Exchange* mail server IP address is configured in the "Notification" screen. GUI FW update process needs to add additional informational messages to show firmware update progress with better time estimates. GUI Debug events showing up in the event log. GUI Question mark help icon for initialization function in Create Virtual Drive Dialog box GUI Updated help needed for initialization function GUI Add a button to a virtual drive to Clear Master Boot Record GUI 3 Critical events do not have email alerting enabled as default GUI Add New Feature: End-user accessible diagnostics GUI Some Event Policy Critical Descriptions are vague - i.e. references to "The Controller" or "The Partner Controller" GUI User warned if they select SCM Action / Reset during an in progress SCM Firmware update. GUI Updated Help files to address incorrect links on Firmware, Notification, SNMP, IP Configuration, Event Policies and User Pages. GUI User data, SNMP, Notification, DNS settings are deleted after updating CMM GUI Hot key "F1" for "RConsole Client Help" does not work in Full Screen mode. Host OS Chassis LED does not come on if SCMs or ESMs are completely dead. Remote Apps Linux OS installation problems while using rMedia from a Linux Client Remote Apps rKVM loses mouse and keyboard if server has SLES 10 SP1 installed Remote Apps Unable to uninstall KVM Console Viewer on remote system via Add or Remove Programs Remote Apps Duplicate hot keys in Keyboard menu Remote Apps rKVM Ctl-alt-del does not always work during OS install. Remote Apps Restarting redirection four to five times (within the rKVM application session) after a KVM session is established, may cause session to be a blank screen, and the server may become unmanageable until rKVM session is closed. Remote Apps ALT-D menu open does not work Remote Apps RKVM Help does not document the hot key functions Remote Apps When user selects Options, mouse acceleration, then cancels to close the popup, the default values disappear Remote Apps Video takes too long to show up when SLES Linux is installed on the server Remote Apps Mouse/keyboard functions unreliable with RHEL5 installed on the server SCM, GUI Stale data left on virtual drive after deletion SCM Changed SCM default settings to disable cache on hard drives within internal storage subsystem UFUM UFUM change to enable single Compute Module reboot during BIOS Update UFUM Add start time and end time and # of tries to FW Update events C. NEW FEATURES/FUNCTIONS IMPLEMENTED IN THIS RELEASE User diagnostics – A new test called “Diagnostic Data” was added to the Tests section of Diagnostics. This new test rolls up information from several areas in the user interface, including all component tab information, all configuration pages, all dashboard information, events, and storage layout. Unlike the Service Data, this information is not password-protected, so it can be used by users as a system-at-a-glance. D. DEPENDENCIES None E. KNOWN ISSUES • Misconfigured Silver Compute Module SAS FW – For Silver Compute Modules (-402 ONLY) the SAS controller FW must be updated prior to update to P2.0.5 or later. This update is NOT REQUIRED for Production servers (-404 and later). Update procedure is documented in section D of the P2.0.5 Upgrade Instruction document (MFSYS25_Unified_Firmware_Update_P2_0_5.doc) included with the Silver version of the P2.0.5 UFU package. • 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 GUI 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. • 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. • Storage Pool View may disappear - After user creates Storage Pool - Storage Pool view may disappear, even after user selects drive - storage pool view may still be blank. Select "storage" tab in upper right and all storage pool data and virtual drives will become present • With DHCP selected for IP configuration, the DHCP assigned IP/ Netmask, Subnet and DNS information is not visible to the user. The IP is locatable via the address bar. • In the CMM GUI, the VLANs tabs associated with ESM1 may not correctly display newly added VLANs and ports if the port belongs to multiple VLANs. • Duplicate BMC FW Update successful events may be logged. After the CMM updates the management controller FW on a server, two events with the description ‘Firmware Update Successful’ and with the detailed description ‘Updated firmware: BMC from version to ’ for each server my be seen in the event log. This does not mean that the FW was updated twice. It is just duplicate events which can be safely ignored. • BIOS update may be automatically performed twice – On rare occasions, the CMM may update the BIOS on a server twice in succession. This would be noticed via a monitor attached to the VGA port on the faceplate of the server or via remote KVM to the server. There is no negative effect, the BIOS will get updated the second time and the firmware page in the UI will show the correct version information. F. INSTALLATION INSTRUCTIONS Preparing For Update: • Download the current Unified Firmware Update package MFSYS25_UFU_P2_0_7.zip for the MFSYS25 system (including the SB5000SI Compute Module) o Copy the CMM_Core.zip file to a folder labeled P2_0_7 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. • Prior to loading and using the P2.0.7 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. • 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 Unified Firmware Update from P2.0.5 to P2.0.7: 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_0_7 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.2.100.01242008.9431. 6. A box below this message labeled Actions will state – Click Start Update to start the firmware update – Click on the Start Update button. 7. The CMM will automatically update the BMC firmware for each installed compute module as necessary. 8. 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) 9. Login to the GUI when prompted. 10. Continue with steps below starting at step 14 under Verify Updates Completed section Unified Firmware Update from P1.0 to P2.0.7: 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_0_7 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.2.100.01242008.9431. 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 Storage Controller line item. The Storage Controller 1 line item in the Firmware tab will change, indicating that the SCM update is in process. This update should take less than 5 minutes. Do not disturb the system until the update is complete and the Storage Controller Module version is shown to be 2.91.140.11. • 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. 12. NOT move the SCM to slot 2 – it should remain in Slot 1 only for all future use. 13. When the SCM update is complete, the CMM will automatically update the BMC firmware for each installed compute module as necessary. Verify Updates Completed: 14. Login to the GUI and browse to the Firmware tab (bottom selection in the left navigation pane. 15. At the top of the Firmware page – verify the Current Build Version is 1.2.100.01242008.9431. 16. Verify the BMC Firmware line under each installed server shows as 1.27.1. Complete BIOS Update: 17. 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. 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.0035….”. 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.0035 will be displayed. 22. Repeat steps 17 – 21 for each server populated in the system. Verify Updates and Load Defaults: 23. Verify the BIOS flashed successfully by entering BIOS setup, on the first tab, the “System BIOS” version displayed should be SB5000.86B.10.00.0035. 24. 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.27.1. 25. Enter BIOS setup for each server by Pressing F2, then press F9 to load system defaults. Make necessary Changes to match settings previously used and Press F10 to save and exit. 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.