================================================================================
Intel(R) Server Platform Manageability Engine Firmware Release Notes
================================================================================

INTEL(R) Server Boards and Systems
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA

================================================================================

DATE    : Jan, 2015

SUBJECT : Manageability Engine Release notes for version SPS_03.00.07.154

================================================================================
                           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 (C) 2015 Intel Corporation.

================================================================================
                              ABOUT THIS RELEASE
================================================================================
Build Stamp : ME Firmware             --> 03.00.07.154
              ME Recovery Boot Loader --> 03.00.07.154
Build Date  : Jan, 2015

================================================================================
                           Supported Platforms
================================================================================
                             S2600WT Family
                             S2600KP Family
                             S2600TP Family
                             S2600CW Family

                
================================================================================
                        ME RECOVERY INSTRUCTIONS
================================================================================
The Recovery process can be initiated by setting the recovery jumper (called ME
FRC UPDT Jumper)

The following steps demonstrate this recovery process:
   1.  Power OFF the system.
   2.  Switch the ME FRC UPDT jumper. Details regarding the jumper ID and
       location can be obtained from the Board TPS.
   4.  Power ON the system.
   5.  Enter BIOS Setup and verify ME status in Server Management, it should be "recovery"
   6.  Boot to EfiShell and update ME if necessary
   7.  AC OFF the system, and return the ME FRC UPDT jumper position to its default position
   8.  Power ON the system.
   9.  Enter setup and verify ME status in Server Management, it should be "OK"

Note 1 : ME will continuously monitor recovery jumper. Whenever ME FRC UPDT is
         asserted ME will immediately switch to recovery mode.  AC Power cycle
         is required after de-asserting ME FRC UPDT jumper for ME to function
         normally.
Note 2 : When MC FRC UPDT jumper is asserted with AC OFF, ME will restore to
         factory default settings.


================================================================================
				ME FW Capsule INSTALLATION NOTES
================================================================================
WARNING:  It is very important to follow these instructions as they are written.
Failure to update using the proper procedure may cause damage to your system.

!!!!! AC failure during update may cause damage to your system and be unrecoverable !!!!!


Please follow the below procedure to update ME using UEFI iFlash32 13.0 Build 5
   1.  Boot the system to EFI Shell
   2.  Copy all update files to a USB Flash Drive or other storage device
   3.  Map the respective storage device in system with the command
           Shell> map -r
   4.  Change the Shell to mapped device file system
           Example: Shell> fs0: (or fs1:)
   5.  Run the updME.nsh script on the prompt.
       
   6.  Reboot system after the update is completed.

================================================================================
			KNOWN ISSUES in 03.00.07.154 release
================================================================================
If host main power delayed relatively to the standby power for 720-770ms ME stop responding.
Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for Inlet Temperature Trigger Type Policy. 
[MESDC] Compliance Test 7.8 Set PSU Configuration w/Power Cycle is failed.
[MESDC] ME FW Status in S3 State is failed. 
During Host Warm Reset flow, unexpected Intel® SPS 3.0 E5 Firmware exception may be promoted to Platform Global Reset. 
When auto configuration is performed and efficiency readings are provided from BMC, ME keeps requesting PSUs for readings. 
SpsInfox86 crashes when executed with 64-bit addressing enabled.
Permanent Node Busy completion code received when trying to ColdReset ME after setting new value of SlopeComp and Offset coefficients. 
After increasing scanning period of DC Power sensor, min correction time for policies in secondary power domain (DC power) will not be updated.  

================================================================================
			Issues fixed in 03.00.07.154 release
================================================================================   
NM Capabilities not available per MESDC Node Manager State Check.
Fast NM Limiting sometimes does not take effect after CLST immediately.
Throttling statistics are equal to 100 after execute EnableFastCLST IPMI command in scenario when FastCLST is disabled in xml. 
Permanent 'Node busy' completion code for non-NM IPMI commands 
Maximum throttling after ramp ends when NM policy is limiting 

================================================================================
			KNOWN ISSUES in 03.00.07.145 release
================================================================================
If host main power delayed relatively to the standby power for 720-770ms ME stop responding.
Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for Inlet Temperature Trigger Type Policy. 
[MESDC] Compliance Test 7.8 Set PSU Configuration w/Power Cycle is failed.
[MESDC] ME FW Status in S3 State is failed. 
During Host Warm Reset flow, unexpected Intel® SPS 3.0 E5 Firmware exception may be promoted to Platform Global Reset. 
When auto configuration is performed and efficiency readings are provided from BMC, ME keeps requesting PSUs for readings. 
SpsInfox86 crashes when executed with 64-bit addressing enabled.
Permanent Node Busy completion code received when trying to ColdReset ME after setting new value of SlopeComp and Offset coefficients. 


================================================================================
			Issues fixed in 03.00.07.145 release
================================================================================   
Signed option ROM has incorrect PCIR information. 
NM-PTU OPROM fails to load when UEFI secure boot is enabled . 
Predictive power capping function is not accurate when first time AC power on.
Fast NM Limiting cannot release limiting after setting pwr draw range back to high value. 
Sometimes when ME configured for operating in SMArt&CLST assist mode the CLST assertion SEL event is sent after SMBAllert desertion. 
NM-PTU OPROM does not have proper version byte. 

================================================================================
			KNOWN ISSUES in 03.00.07.141 release
================================================================================
If host main power delayed relatively to the standby power for 720-770ms ME stop responding.
Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for Inlet Temperature Trigger Type Policy. 
[MESDC] Compliance Test 7.8 Set PSU Configuration w/Power Cycle is failed.
[MESDC] ME FW Status in S3 State is failed. 
During Host Warm Reset flow, unexpected Intel® SPS 3.0 E5 Firmware exception may be promoted to Platform Global Reset. 
When auto configuration is performed and efficiency readings are provided from BMC, ME keeps requesting PSUs for readings. 
NM policy power range for memory domain is changed to incorrect values after NM PTU characterization is run. 
SpsInfox86 crashes when executed with 64-bit addressing enabled.
Permanent Node Busy completion code received when trying to ColdReset ME after setting new value of SlopeComp and Offset coefficients. 


================================================================================
			Issues fixed in 03.00.07.141 release
================================================================================   
Set NM Power Draw Range IPMI command does not work in Sx states.    
NM constantly forces RAPL limit 2 to 0 Watt after a series of SMBAlerts.


================================================================================
			KNOWN ISSUES in 03.00.07.114 release
================================================================================
- If host main power delayed relatively to the standby power for 720-770ms ME stop responding.
- Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for Inlet Temperature Trigger Type Policy. 
- [MESDC] Compliance Test 7.8 Set PSU Configuration w/Power Cycle is failed.
- [MESDC] ME FW Status in S3 State is failed. 
- During Host Warm Reset flow, unexpected Intel? SPS 3.0 E5 Firmware exception may be promoted to Platform Global Reset. 
- When auto configuration is performed and efficiency readings are provided from BMC, ME keeps requesting PSUs for readings. 
- Permanent Node Busy completion code received when trying to ColdReset ME after setting new value of SlopeComp and Offset coefficients. 
- NM constantly forces RAPL limit 2 to 0 Watt after a series of SMBAlerts.
- NM policy power range for memory domain is changed to incorrect values after NM PTU characterization is run.


================================================================================
			Issues fixed in 03.00.07.114 release
================================================================================
- For Shared Power Supply configuration, power isn't kept in the range of 2% during power limiting. The power kept in range of 3C 4%.  
- SMLink0 utilization is too high after disabling Node Manager with Set ME FW capabilities command. 
- Sporadically MESDC hangs up during reading trace logs via IPMB/RMCPP/HECI interface.   
- Few events instead of one are send after Flash Wear-Out Protection occurs.
- OSPM and DCMI policies are not created when policies maximum number of policies defined in XML file.   
- BMC OEM readings discovery is working incorrectly in Sx when BMC responded with completion code different from Successful (0x00). 
- [MESDC]  Compliance test NM_13:  After running the test the PROCHOT# is not deasserted which may fail other compliance tests with power limiting. 
- Certain power delivery systems may provide power data which fluctuates outside of the tolerances of the NM PTU power data filtering algorithm causing the Get Node Manager Power Characterization Range command (0x61) to return 0xFFFE power data. 
- ME goes to recovery state after graceful shutdown when power and thermal readings are enabled. 
- In G3 to S5 transition ME sends 2 NM Health Events: power readings in domain 0 and inlet temp readings are missing. 
- BMC set as power source even if only PSU is available when auto configuration is enabled. 
- P-States cannot be set while platform is in idle state. 
- Unexpected CLST event is sent during S0->S5 transition. 
EPSD100242602
EPSD100242696

- PSU Monitoring service error during GetSelftestResults IPMI command. 
- BackBone exceptions during various power flows (SX/Global Reset) or after SKU burning / NMon alwaysOn/ s0only. 
- Unexpected ME resets during SMBAlert stress test (backbone exception). 
- MESDC over IPMI causes FW crash in Recovery if MeMdesAddr is disabled in xml. 
- ME failed during cold reset after continuously setting and resetting ME recovery jumper - two exceptions occurred. 
- Get NM Capabilities IPMI command return CompCode 0xC0 (Node Busy) when power telemetry is enabled. 
- Unable to assign GPIO > 15 to MEMHOT, PROCHOT, SMBALERT. 
- HMRFPO_ENABLE does not always respond during FW update after EOP. 
- Missing readings policy causes maximum throttling after S3. 
- Me does not send SMB Alert mask when setting redundant PSU. 
- Me switches to recovery image when auto configuration is enabled and no sensors are enabled. 
- Send Raw PMBUS command PMBUS_Revison does not work on SiEn SKU. 
- Get Sel Entry IPMI command returns too few bytes in Recovery. 
- SPS FW switches to Recovery during BMC DC Reboot. 
- BMC OEM readings discovery does not work correctly in Sx. 
- Platform shuts down during AC Cycles with 0W policies set on all domains. 
- Threshold Exceeded event desertion not received when BMC sets new power threshold. 
- Incorrect NM-PTU SHA-256 hash. 
- Inband PECI Failure health events are not sent in some cases. 
- "Get Self-Test Results"IPMI command reports PSU Monitoring error for PSU configured as redundant that is missing.    
- When user issues ˇ°Set Max Allowed CPU P-state/T-stateˇ± command CPU will operate on Max Turbo frequency instead P1.
    
  
================================================================================
			KNOWN ISSUES in 03.00.06.277 release
================================================================================
If host main power delayed relatively to the standby power for 720-770ms ME stop responding.
Sporadically Watchdog reset occurs when ME is working as MCTP Proxy. 
For Shared Power Supply configuration power isn't kept in the range of 2% during power limiting. The power kept in range of 3 - 4%.   
SMLink0 utilization is too high after disabling Node Manager with Set ME FW capabilities command. 
Sporadically MESDC hangs up during reading trace logs via IPMB/RMCPP/HECI interface.  
Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for Inlet Temperature Trigger Type Policy. 
Few events instead of one are send after Flash Wear-Out Protection occurs.  
OSPM and DCMI policies are not created when policies maximum number of policies defined in XML file.   
[MESDC] Compliance Test 7.8  Set PSU Configuration w/Power Cycle is failed. 
[MESDC] ME FW Status in S3 State is failed. 
During Host Warm Reset flow, unexpected Intel? SPS 3.0 E5 Firmware exception may be promoted to Platform Global Reset. 
Certain power delivery systems may provide power data which fluctuates outside of the tolerances of the NM PTU power data filtering algorithm causing the Get Node Manager Power Characterization Range command (0x61) to return 0xFFFE power data. 
BMC OEM readings discovery is working incorrectly in Sx when BMC responded with completion code different from Successful (0x00). 
[MESDC]  Compliance test NM_13:  After running the test the PROCHOT# is not deasserted which may fail other compliance tests with power limiting. 
Sometimes after setting coefficients via ˇ°Set Intel? NM Parameterˇ± IPMI command the ME may respond ˇ°Node Busyˇ± (0xC0) on all NM commands for one minute. 


================================================================================
			Issues fixed in 03.00.06.277 release
================================================================================
System idle power consumption rise after proactive power limit enable.    


Boot time power policy stop working after MIC card installed.
EPSD100244030
EPSD100026783       

Unexpected ME health events may be observed during DC cycles.
EPSD100243480
EPSD100243264
EPSD100243181
EPSD100243480
EPSD100243264
EPSD100243181



================================================================================
		Production Release	KNOWN ISSUES in 03.00.06.274 release
================================================================================
If host main power delayed relatively to the standby power for 720-770ms ME stop responding.
Sporadically Watchdog reset occurs when ME is working as MCTP Proxy. 
For Shared Power Supply configuration power isn't kept in the range of 2% during power limiting. The power kept in range of 3 - 4%.   
SMLink0 utilization is too high after disabling Node Manager with Set ME FW capabilities command. 
Sporadically MESDC hangs up during reading trace logs via IPMB/RMCPP/HECI interface.  
Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for Inlet Temperature Trigger Type Policy. 
Few events instead of one are send after Flash Wear-Out Protection occurs.  
OSPM and DCMI policies are not created when policies maximum number of policies defined in XML file.   
[MESDC] Compliance Test 7.8  Set PSU Configuration w/Power Cycle is failed. 
[MESDC] ME FW Status in S3 State is failed. 
During Host Warm Reset flow, unexpected Intel? SPS 3.0 E5 Firmware exception may be promoted to Platform Global Reset. 
Certain power delivery systems may provide power data which fluctuates outside of the tolerances of the NM PTU power data filtering algorithm causing the Get Node Manager Power Characterization Range command (0x61) to return 0xFFFE power data. 
BMC OEM readings discovery is working incorrectly in Sx when BMC responded with completion code different from Successful (0x00). 
[MESDC]  Compliance test NM_13:  After running the test the PROCHOT# is not deasserted which may fail other compliance tests with power limiting. 
Sometimes after setting coefficients via ˇ°Set Intel? NM Parameterˇ± IPMI command the ME may respond ˇ°Node Busyˇ± (0xC0) on all NM commands for one minute. 

