Intel® Modular Server System MFYSY25 
P2.3.5 Unified Firmware Update 
Release Notes & Installation Instructions
Copyright © 2007-2008 Intel Corporation
All Rights Reserved


October 14, 2008
RELEASE NOTES FOR: P2.3.5



A.	RELEASE PACKAGE CONTENTS

This section enumerates the contents of the release package.
•	BIOS: SB5000.86B.10.10.0048.100920081914 
•	BMC: 1.30.3
•	Management Module GUI opération Code: 2.4.100.20081010.13743
•	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 support rollback to previous version of the Unified Firmware Update (UFU) package P2.3.1.

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.  

P2.3.2, P2.3.3 are no longer supported and should not be used.  Upgrade immediately to this release P2.3.5.



C.	DEPENDENCIES

The system must be at firmware level P2.3.1, P2.3.2, or P2.3.3 prior to starting this update.
If the system contained two SCMs at firmware level P2.3.1 this update can 
continue with both SCMs installed.  If you intend to install a second SCM to a 
system which previously contained only one SCM, the second SCM should be 
installed after the system has been updated to P2.3.5. 
 
After the firmware update has been completed insert the second SCM into 
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

none



E.	NEW FEATURES/FUNCTIONS IMPLEMENTED IN THIS RELEASE

Intel® Xeon® processor 5400 series - This release added support for the 
E0 stepping of the Intel® Xeon® processor 5400 series.



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 - 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_5.zip for the 
	MFSYS25 system (including the MFS5000SI Compute Module).
•	Copy the CMM_Core.zip file to a folder labeled P2_3_5 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.5 unified software update – all server 
	modules in the system must be powered down.
•	If you intend to add a second SCM to the chassis as part of this 
	update, please follow the procedures below for adding the second 
	SCM in SCM slot 2.  
•	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.3.1, P2.3.2, or P2.3.3 to P2.3.5:

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_5 you previously created, select the CMM_Core.zip 
	file and the update will automatically begin. 
4.	The upload process will 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.20081010.13743.
6.	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.
7.	Login to the GUI when prompted.
8.	Browse to the Firmware tab and scroll down to the Server Module section 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.
9.	A dialogue box will appear – Click “Apply” to power on servers.  
10.	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)”.
11.	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. 
12.	The BIOS status will eventually display “BIOS updating to SB5000.86B.10.10.0048….”. 
13.	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.10.0048... 
	will be displayed.
14.	Repeat steps 8 – 13 for each server populated in the system.
15.	Continue with step 16 below under the Verify Updates Completed and Load Defaults section


Verify Updates Completed and Load Defaults:

16.	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.
17.	On boot Enter BIOS Setup by pressing “F2” when prompted.
18.	Verify the BIOS flashed successfully by entering BIOS setup, on the first tab, 
	the “System BIOS” version displayed should be SB5000.86B.10.10.0048...
19.	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.
20.	Repeat steps 16 through 19 for each server to verify BIOS version and load 
	default settings. 
	

Install Second SCM in SCM2 Slot: (Only required if adding second SCM)

21.	Login to the GUI and browse to the Firmware tab (bottom selection in the left 
	navigation pane.
22.	Install the second SCM in SCM2 slot.
23.	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”. 
24.	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. 
25.	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.
26.	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.
27.	The chassis fault LED will stop illuminating and the warning message at the 
	top of the screen will disappear.
28.	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.

