Intel® Modular Server System MFYSY25 
P2.3.1 Unified Firmware Update 
Release Notes & Installation Instructions
Copyright © 2007-2008 Intel Corporation
All Rights Reserved
June 18, 2008
RELEASE NOTES FOR: P2.3.1


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 opération Code: 2.4.100.20080610.11578
•	Remote KVM Java Applet – 1.40
•	EBF: 1.24
•	Storage
•	IOP FW/SW: 2.91.0140.50
•	IOP SW: 2.91.0140.50
•	Expander FW: 1.03.0140.02
•	Redboot image: 1.01.0140.08
•	Switch Boot Code: 1.0.0.6
•	Switch FW: 1.0.0.27
•	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 two SCM for Microsoft® Windows 2003 R2 SP2
	and Microsoft® Windows 2008. Dual SCM operation is not supported in this release for LINUX operating systems. 
	This release supports system configurations with only one SCM in Slot SCM1 for all supported Operating Systems.  
 
	Drivers to support this release can be found within a package titled: Intel(R) Modular Server System MFSYS25 - 
	Dual SCM Controller OS Installation Instructions and Drivers.  

C.	DEPENDENCIES
	
	The system must be at firmware level P2.2.2 or P2.2.3 prior to starting this update.  

	The system should have only one SCM installed during the firmware update. After the firmware update
	has been completed the second SCM can be installed in the SCM2 slot. After installation of the 
	second SCM, the system will then start an update for the firmware of the second SCM and expander
	on the interposer. Please see instructions for 2nd SCM installation and firmware update process
	in the Install Second SCM in SCM2 Slot section below. The update process will take approximately
	15 – 20	minutes for the second SCM and should not be interrupted.

D.	DEFECTS FIXED IN THIS RELEASE

Area		Description

CMM GUI		ESM up time in CMM GUI is incorrect.
CMM GUI		Browse is not enabled when Redirect CDROMImage is selected 
CMM GUI		RKVM F1 brings up local console help and does not pass F1 to remote compute module server
CMM GUI		Storage Pool view disappears
CMM GUI		IPMI requests/responses to/from the compute module out of synch

CMM GUI		Actions will complete if user clicks OK without typing “CONFIRM” 
CMM GUI		Popup error when user does not select a replaced drive for the rebuild of a Storage Pool
CMM GUI		GUI error message needs clear instructions for user when a rebuild is attempted without an available spare drive for rebuild
BMC		BMC does not log events to compute module SEL if the CMM is nonoperational
BMC		Intermittent system fan boost due to readings from compute modules
Switch Module	Ethernet switch port flapping on slots without compute modules
Switch Module	ESM GUI switch uptime does not match that of CMM GUI




E.	NEW FEATURES/FUNCTIONS IMPLEMENTED IN THIS RELEASE

•	Dual SCM Controller - This release provides support for redundant SCM controllers with Failover / Failback
	functionality for Microsoft® Windows 2003 and Microsoft® Windows 2008 only. A future release will add
	support for Redhat® Enterprise LINUX 5 U 1 and Suse® Enterprise LINUX 10 U1.  Note that there are BKMs
	for each OS installation with the dual SCM controller configuration, as well as MPIO drivers. Please refer
	to the BKMs for proper installation of the operating system and drivers.

	BKM documents can be found within a package titled: Intel(R) Modular Server System MFSYS25 - Dual SCM Controller 
	OS Installation Instructions and Drivers.


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.

•	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 to guarantee that this issue is not encountered. 

•	
•	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_3_1.zip for
	the MFSYS25 system (including the MFS5000SI Compute Module)
	o   Copy the CMM_Core.zip file to a folder labeled P2_3_1 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.3.1 unified software update – all server
	modules in the system must be powered down.
•	Only 1 SCM in SCM1 slot can be installed in the chassis. The second SCM can not
	be installed in the chassis until after this firmware update has been completed.
•	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.2.2 or P2.2.3 to P2.3.1:

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_3_1 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 2.4.100.20080610.11578.
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 “Storage Controller resetting. This mat take up to 4 minutes.  
8.	It will then go to a screen that says “Reset of controller SCM1 to Safe Mode successful”.
	Hit OK. The screen will 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). The CMM will
	take several minutes to boot prior to displaying the Login screen.
10.	Login to the GUI when prompted.
11.	Browse to the Firmware tab and scroll down to the Ethernet Switch module 1 line. 
	The Ethernet Switch module line will indicate that the Ethernet Switch module firmware
	is updating to version 1.0.0.27. The update will take 5 minutes to complete.
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 is updating to 
	version 2.91.140.50. The update will take 5 - 10 minutes. Do not disturb the system while 
	the update is in progress. While the update is still in process the Firmware tab will indicate
	that the Storage Controller Module is at 2.91.140.50. Do not interrupt the system while the 
	system fans are at high speed. Wait until the system fans have returned to normal speed before
	verifying that all updates have been completed.  
13.	Do NOT move the SCM to slot 2 – it should remain in Slot 1 only for all future use.
14.	Continue with step 15 below under the Verify Updates Completed section


Verify Updates Completed:

15.	Login to the GUI and browse to the Firmware tab (bottom selection in the left 
	navigation pane.
16.	At the top of the Firmware page – verify the Current Build Version is  
	2.4.100.20080610.11578.
17.	Verify the Ethernet Switch module firmware line under each installed Ethernet Switch Module
	shows firmware level 1.0.0.27, boot 1.0.0.6.
18.	Verify the Storage Control Module firmware level is 2.91.140.50.
19.	Insure that all Chassis fans are running at normal speed prior to installing the Second SCM
	in SCM2 slot.

Install Second SCM in SCM2 Slot:

20.	Login to the GUI and browse to the Firmware tab (bottom selection in the left navigation pane.
21.	Install the second SCM in SCM2 slot.
22.	After the second SCM has booted, the firmware update page will either indicate “Firmware update
	to this component will begin soon” or “Update to version 2.91.140.50 queued”. 
23.	The second SCM line on the firmware tab will then indicate “updating to 2.91.140.50. The firmware
	update will take approximately 5 - 10 minutes. During this time the chassis fans will be at high
	speed and the chassis fault LED will illuminate. 
24.	The Firmware tab will then indicate that the second SCM has been updated to 2.91.140.50, however,
	the fans will remain at high speed and the chassis fault LED will remain illuminated. The Firmware
	tab will then indicate “updating expander”. Do not disturb the expander update process which will 
	take approximately 10 minutes.
25.	At the end of the expander update, a warning message at the top of the screen will indicate
	“Controller Fail-back in progress. Storage Management functions may be temporarily unavailable.
26.	The chassis fault LED will stop illuminating and the warning message at the top of the screen will
	disappear.
27.	Browse to the event log. The event log should now display “Storage Controller Operational” for 
	Storage Controller 2
 



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.
