IntelÃ‚Â® Server System Server System "Emerald Ridge ... - CTL

More documents

Recommendations

Info

Intel® Server System "Emerald Ridge” ” Integrated Baseboard Management Controller EPS 錯誤 ! 尚未定義樣式。During a standard firmware update, the BMC will respond normally to all IPMI commands.However, the BMC will not respond to commands for the 15 seconds after exiting firmwareupdate mode (either normal or force-update) while it reboots.5.3 Boot Recovery ModeThe BMC’s boot block (Uboot) also supports firmware transfer updates. It uses the samecommands as the operational Firmware Transfer mode, but writes directly to the flash.Operational Firmware Transfer mode preserves several of the files in the PIA Linux file system.Boot Recovery mode cannot preserve the files because it does not understand Linux filesystems, and treats it as a large binary data section. This means a Boot Recovery updatecompletely replaces the PIA with the factory default version: an empty SEL, a default SDR, anddefault IPMI configuration and user settings.Boot Recovery mode can successfully complete an update in some situations where theOperational Firmware Transfer mode will fail. If there is an incompatibility or bug in theoperational code causing it to crash or hang; only a Boot Recovery Mode Update will work.Another example is if the flash layout of the sections changes across an update. Since, theoperational Firmware Transfer mode tries to preserve the contents of the PIA section; in thiscase it will corrupt the flash where the old PIA section was, because the Boot Recovery mode isblindly writing binary data to flash, in this case it will succeed.Note: The flash layout should never change in a field update.There are two ways to enter Boot Recovery mode:The Force Firmware Update jumper is asserted when A/C power is applied.The operational code is corrupt and the boot loader cannot boot.In Boot Recovery mode the BMC only responds to the small set of commands listed above.Only the KCS SMS interface is supported. USB-based Fast Firmware Update is not supported.5.4 Force Firmware Update JumperThe Force Firmware Update jumper can be used to put the BMC in Boot Recovery mode for alow level update. It causes the BMC to abort its normal boot process and stay in the boot loaderwithout executing any Linux code.The jumper is normally in the deasserted position. The system must be completely powered off(A/C power removed) before the jumper is moved. After power is re-applied and the firmwareupdate is complete, the system must be powered off again and the jumper returned to thedeasserted position before normal operation can begin.There is no boot block write protection jumper.Revision 1.1Intel ® Confidential 75
BMC Flash UpdateIntel® Server System "Emerald Ridge” Integrated Baseboard Management Controller EPS5.5 Restore Default ConfigurationThe BMC supports an OEM command, RestoreConfiguration, to restore all configuration valuesto their defaults. All IPMI configuration parameters and all Linux user configuration files (passwd,group, etc.) are restored.When the Restore Configuration command is implemented by the BMC, configuration files arecopied from a read-only default directory (/etc/defconfig) to a standard read-write location (/conf).The SDR and SEL are not restored to defaults by this command, so these two files arepreserved. Standard IPMI commands should be used to clear the SEL and SDR. The IPMIconfiguration file PMConfig.dat is special because it does not exist by default (in which case theBMC uses configuration values from an internal default array), so this file is deleted from /conf.The BMC switches to using RAM shadow copies of the files before copying them to flash,similar to an Operational Firmware Transfer mode update, so the BMC must be reset before itcan use the new values from flash. The reset is completed by the utilities (FWPIAUPD andSysCfg) and not by the BMC for historical reasons.5.6 Fast Firmware Update over USBThe BMC supports a Fast Firmware Update mode in addition to the standard KCS SMSinterface. This is a special AMI proprietary protocol that goes over the USB connection betweenthe host and the BMC. Called “IPMI over USB”, it is implemented in the LIBIPMI library on bothhost and BMC sides to transfer large blocks of data (up to 32 K) much faster than KCS can.Note that block transfer size is independent of USB or KCS interface. IPMI commands areembedded in data written/read to a virtual CD-ROM device. See AMI LIBIPMI documentation fordetails.Update utilities should try to use this method first. If a USB session cannot be established, theupdate utilities should use the standard slower KCS interface. If the BMC is in Boot Recoverymode, only KCS updates are supported.76Intel ConfidentialRevision 1.1
Page 1:
Intel ® Server System "Emerald Rid
Page 4 and 5:
錯誤 ! 尚未定義樣式
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43: 錯誤 ! 尚未定義樣式
Page 70 and 71: Intel® Server System "Emerald Ridg
Page 142 and 143:
Intel® Server System "Emerald Ridg
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Intel® Server System "Emerald "Rid
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
show all

IntelÃ‚Â® Server System Server System "Emerald Ridge ... - CTL

Create successful ePaper yourself

Delete template?

Save as template?