SR870BN4 server may contain design defects or errors known as errata that may cause the product to deviate
from published specifications. Current characterized errata are available on request.
Information in this document is provided in connection with Intel
®
products. 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 products are not designed, intended
or authorized for use in any medical, life saving, or life sustaining applications or for any other application in which the failure
of the Intel product could create a situation where personal injury or death may occur. Intel may make changes to
specifications and product descriptions at any time, without notice.
This document contains information on products in the design phase of development. The information here is subject to
change without notice. Do not finalize a design with this information.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the
FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be
required to correct the interference at his/her own expense.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and
other countries.
†
Other names and brands may be claimed as the property of others.
INI File Structure ........................................................................................................299
The [INF_FILE] Section.............................................................................................. 299
The [DISPLAY] Section.............................................................................................. 299
E SDRViewer Splash Screen File Format.................................................... 302
F SELViewer Splash Screen File Format..................................................... 303
G Glossary ...................................................................................................... 305
H Troubleshooting ......................................................................................... 306
Index ................................................................................................................. 308
10 Intel® SR870BN4 Server System Product Guide
Page 11
<This page intentionally left blank.>
Intel® SR870BN4 Server System Product Guide 11
Page 12
Page 13
Part I: User’s Guide
1 System Description
2 Board Set Description
3 Configuration Software and Utilities
4 Hot-swapping System Components
This manual consists of two parts:
User’s Guide, beginning on page 13describes procedures that DO NOT REQUIRE internal
server access. The user does not need to be a qualified service technician to perform
procedures listed in the User’s Guide.
Service Technician’s Guide, beginning on page 175describes procedures that REQUIRE
internal server access. The user must be a qualified service configuration technician to perform
procedures listed in the Service Technician’s Guide.
WARNING
Only a QUALIFIED SERVICE TECHNICIAN is authorized to remove
the server’s covers and to access any of the components inside the server,
except as noted herein. Before removing top covers or modules, see
“Figure 58. Locating System Modules” on page 181 and “Warnings and
Cautions” on page 179.
WARNING
Anchor the equipment rack: The equipment rack must be anchored to an
unmovable support to prevent it from falling over when one or more
servers are extended in front of the rack on slides. The anchors must be
able to withstand a force of up to 113 kg (250 lbs.). The user must also
consider the weight of any other device installed in the rack. A crush
hazard exists should the rack tilt forward which could cause serious injury.
Main AC power disconnects: The user is responsible for installing an
AC power disconnect for the entire rack unit. This main disconnect
must be readily accessible, and it must be labeled as controlling power to
the entire unit, not just to the server(s).
Grounding the rack installation: To avoid the potential for an electrical
shock hazard, the user must include a third wire safety-grounding
conductor with the rack installation. If the server power cord is plugged
into an AC outlet that is part of the rack, then the user must provide
proper grounding for the rack itself. If the server power cord is plugged
into a wall AC outlet, the safety-grounding conductor in the power cord
provides proper grounding only for the server. The user must provide
additional, proper grounding for the rack and other devices installed in it.
Intel® SR870BN4 Server System Product Guide 13
Page 14
Overcurrent protection: The server is designed for an AC line voltage
source with up to 20 amperes of overcurrent protection. If the power
system for the equipment rack is installed on a branch circuit with more
than 20 amperes of protection, the user must provide supplemental
protection for the server.
WARNING – POWER CORD RATING
Do not attempt to modify or use an AC power cord that is not the exact
type required. The user must use a power cord that meets the following
criteria:
• Rating: For U.S./Canada cords must be UL Listed/CSA Certified, 16/3,
75C type, VW-1, SJT/SVT, with NEMA 5-15P or NEMA 6-15P
attachment plug and IEC 320 C13 input power connector rated 15 amps.
For outside U.S./Canada cords must be flexible harmonized (<HAR>)
rated 250 V, 1.0 mm minimum conductor size with IEC 320 C13 input
power connector and rated for no less than 10 amps.
• AC Attachment Connector, wall outlet end for outside U.S./Canada:
The AC wall attachment plug should be a three conductor grounding
type, rated at 125 V, 15 amps and must be for the configuration of the
specific region or country. The AC wall attachment plug must bear at
least an accepted safety agency certification mark for the specific region
or country.
• Input Power Connector, server end: The connectors that plug into the
AC receptacles on the server must be an IEC 320, sheet C13, type
female connector and are rated for 125 V/250 V, 15 A.
• Cord length and flexibility: Cords must be less than 4.5 meters (14.76
feet) long.
CAUTION
Temperature: The range of temperatures in which the server operates when
installed in an equipment rack, must not go below 10 °C (50 °F) or rise above
35 °C (95 °F). Extreme fluctuations in temperature can cause a variety of
problems in your server.
Ventilation: The equipment rack must provide sufficient airflow to the front
of the server to maintain proper cooling. The rack must also include
ventilation sufficient to exhaust a maximum of 1500 W (5,100 BTU/hr) for
the server. The rack selected and the ventilation provided must be suitable to
the environment in which the server will be used.
14 Intel® SR870BN4 Server System Product Guide
Page 15
Regulatory Specifications and Disclaimers
Declaration of the Manufacturer or Importer
We hereby certify that this product is in compliance with European Union EMC Directive
89/336/EEC, using standards EN55022 (Class A) and EN55024 and Low Voltage Directive
73/23/EEC, Standard EN60950.
Safety Compliance
USA: UL 1950 – 3rd Edition/CSA 22.2. No. 950-M93
Canada: UL Certified – 3rd Edition/CSA 22.2. No. 950-M93 for Canada (product bears
the single UL mark for U.S. and Canada)
Europe: Low Voltage Directive, 73/23/EECTUV/GS to EN60950 2nd Edition with
Australian / New Zealand: CB Report to IEC 60950, 3rd Edition plus Australian deviations
Electromagnetic Compatibility (EMC)
USA: FCC CFR 47 Part 2 and 15, Verified Class A Limit
Canada: IC ICES-003 Class A Limit
Europe: EMC Directive, 89/336/EEC:
EN55022, Class A Limit, Radiated & Conducted Emissions
EN55024, ITE Specific Immunity Standard
EN61000-4-2, ESD Immunity (Level 2 Contact Discharge, Level 3 Air Discharge)
EN61000-4-3, Radiated Immunity (Level 2)
EN61000-4-4, Electrical Fast Transient (Level 2)
EN61000-4-5, AC Surge
EN61000-4-6, Conducted RF
EN61000-4-8, Power Frequency Magnetic Fields
EN61000-4-11, Voltage Dips and Interrupts
EN61000-3-2, Limit for Harmonic Current Emissions
EN61000-3-3, Voltage Flicker
Japan: VCCI Class A ITE (CISPR 22, Class A Limit) IEC 1000-3-2 Limit for Harmonic
Current Emissions
Australia/New Zealand: AS/NZS 3548, Class A
Taiwan: BSMI Approval, Class A
Korea: RRL Approval, Class A
Russia: GOST Approved
International: CISPR 22, Class A Limit
Intel® SR870BN4 Server System Product Guide 15
Page 16
FCC Electromagnetic Compatibility Notice (USA)
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operating in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference. In this
case, the user is required to correct the interference at the users own expense. If this equipment
does cause harmful interference to radio or television reception, which can be determined by
turning the equipment off and on; the user is encouraged to try to correct the interference by one or
more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and the receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
Consult the dealer or an experienced radio/TV technician for help.
Any changes or modifications not expressly approved by the grantee of this device could void the
user’s authority to operate the equipment.
The customer is responsible for ensuring compliance of
the modified product.
FCC Declaration of Conformity
Product Type: SR870BN4
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) This device may not cause harmful interference, and (2) this device must accept any
interference received, including interference that may cause undesired operation.
For questions related to the EMC performance of this product, contact:
Intel Corporation
2800 Center Drive
Dupont, WA 98327 USA
Laser Compliance Notice
Intel products that use laser technology comply with Class 1 laser requirements.
Class 1 Laser Product
Luokan 1 Laserlaite
Klasse 1 Laser Apparat
Laser Klasse 1
This product has been tested in accordance too, and complies with the Low Voltage Directive
(73/23/EEC) and EMC Directive (89/336/EEC). The product has been marked with the CE Mark
to illustrate its compliance.
Japan EMC Compatibility
English translation of the notice above:
This is a Class A product based on the standard of the Voluntary Control Council for Interference
by Information Technology Equipment (VCCI). If this equipment is used in a domestic
environment, radio disturbance may arise. When such trouble occurs, the user may be required to
take corrective actions.
ICES-003 (Canada)
Cet appareil numérique respecte les limites bruits radioélectriques applicables aux appareils
numériques de Classe A prescrites dans la norme sur le matériel brouilleur: “Appareils
Numériques”, NMB-003 édictée par le Ministre Canadian des Communications.
English translation of the notice above:
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital
apparatus set out in the interference-causing equipment standard entitled “Digital Apparatus,”
ICES-003 of the Canadian Department of Communications.
BSMI (Taiwan)
The BSMI Certification number and the following warning is located on the product safety label
which is located visibly on the external chassis.
Intel® SR870BN4 Server System Product Guide 17
Page 18
1 System Description
Introduction
The Intel® SR870BN4 as shown in Figure 1 is a compact, high-density rack-mount server system
®
with support for one to four Intel
system is based on the Intel S870BN4 board set and the Intel
hot-plug PCI and PCI-X add-in cards; hot-swap, redundant power supply modules; hot-swap,
redundant cooling fans; and hot-swap hard disk drives. The system also provides interlock status
LEDs for critical system interconnects. The system supports Symmetric Multiprocessing (SMP)
and a variety of operating systems. Table 1 presents an overview of the server system’s physical
characteristics.
Itanium® 2 processors and 32-GB DDR SDRAM memory. The
®
E8870 chipset. The system supports
OM12884
Figure 1. SR870BN4 Front View
Table 1 Server Physical Specifications
Characteristic Specification
Height 178 mm (6.9 inches, 4U)
Width 445 mm (17.5 inches)
Depth 711 mm (28.0 inches)
Weight (max.) 48 kg (106 lbs)1
Required front clearance 76 mm cm (3 inches)
Required rear clearance 152 mm (6 inches)
Required side clearance 25 mm (1 inch)
Heat Dissipation 1500 W (5,100 BTU/hr)
1. The system weight listed above is an estimate for a fully configured system and will vary depending on the number of
peripheral devices and add-in cards as well as the number of processors and DIMMs installed in the system.
18 Intel® SR870BN4 Server System Product Guide
Page 19
Chassis Description
The chassis provides a modularized processor/memory subsystem, I/O subsystem, and peripheral
bay. Other features are outlined in Table 2.
Table 2. Chassis Feature Summary
Feature Comment
Server
Configuration
Expansion and
Servicing
Management
Upgrades
System-level
scalability
Stand-alone system including external I/O PCI slots and disk expansion as needs grow
Supports Intel Itanium 2 processors
32-GB Double Data Rate (DDR) Synchronous Dynamic Random Access Memory
(SDRAM) memory support with 2-GB DIMMs
Front access to hot-swap hard disk drives
Three hot-swap 1-inch Ultra320 SCSI hard disk drives
Rear access to hot-swap power supplies
Two hot-swap 1200-W power supplies in a redundant (1+1, 220 V) configuration with
redundant power cords (one per power supply)
Four top access hot-swap system fans in a redundant (3+1) configuration
Dockable processor/memory subsystem, I/O subsystem and peripheral bay
Dockable slim-line LS-240 and DVD/CD-ROM drives
Interlock status indicator LEDs for major modulesEight 64-bit hot-plug PCI-X slots
Remote management through LAN or modem
Emergency Management Port
Intelligent Platform Management Interface (IPMI) 1.5 compliant
Wired for Management (WfM) 2.0 compliant
Remote diagnostics support through LAN or modem
Field upgradeable to the next generation Itanium processor family
Multi-generational chassis
Up to 64GB DDR SDRAM (with -5XX revision and higher memory boards. 32 GB
supported on -4XX revision memory boards)
One to four Intel
External I/O (8 PCI slots) and disk expansion
External SCSI connector
Itanium 2 processors
Intel® SR870BN4 Server System Product Guide 19
Page 20
External Chassis Features
System controls and indicators are located in several places on the chassis as follows:
Chassis front:
Front panel: Front panel switches and LEDs
Peripheral bay: Hard disk drive LEDs
Processor/memory module: Subsystem serviceability LEDs
Chassis back:
Power supply modules (See Power Subsystem on page 31 for details)
Hot-plug Indicator Board (HPIB)
Chassis top:
I/O subsystem
Fan bay (See Cooling Subsystem on page 32 for details)
Each of these areas is discussed in this section.
Chassis Front
Figure 2 shows the front view of the chassis with the snap-on bezel in place. The bezel provides
access to the front panel board and the peripheral bay.
OM12885
B
A
C
A Bezel
B Front Panel
C Peripheral Bay
Figure 2. Chassis Front View
20 Intel® SR870BN4 Server System Product Guide
Page 21
Front Panel
The front panel is located to the right of the processor/memory subsystem and provides user
interface for system management via switches and status indicator LEDs. The front panel also
contains the speaker. Figure 3 shows the control buttons and status indicators on the front panel.
Table 3 describes their features.
A
E
B
C
D
F
G
H
I
Figure 3. Front Panel Controls and Indicators
Table 3. Front Panel Control and Indicator Description
Item Feature Description
Switches
A System ID Switch Toggle switch for blue System ID LEDs (the front panel system ID LED
is located inside the system ID switch). See E below for description of
LED operation.
B Assert SDINT (System
Diagnostic Interrupt)
Switch
C Reset switch Resets the system.
D Power switch Toggles system power. A delay of ~5 seconds is required between
Asserts SDINT. This switch is accessible through a small opening and
requires a narrow tool to activate.
pressing the power switch to power down and then power up the
system.
OM12886
continued
Intel® SR870BN4 Server System Product Guide 21
Page 22
Table 3. Front Panel Control and Indicator Description (continued)
Item Feature Description
LED Indicators
E System ID (Blinking or
Solid Blue). The system
ID LEDs are located
inside the system ID
switch on the front panel
and on the back panel
F Main Power (Solid or
Blinking Green)
G Power Fault (Solid
Amber)
H Cooling Fault (Solid
Amber)
I General Fault (Solid
amber)
Identifies the system. The system ID is activated either by the system
ID switch or through server management software.
Pressing the system ID switch once turns on the LEDs solid blue.
Press the system ID switch again, the solid blue LEDs turn off.
Remove activation - LEDs turn on blinking for 4 minutes (max). The
system ID LEDs cannot be turned off by pressing the switch.
A continuously lit LED indicates the presence of DC power in the
system. The LED goes out when the power is turned off or the power
source is disrupted. Blinking Green indicates the system is in sleep
mode.
Indicates any system power faults. Off indicates power is OK.
Indicates any system cooling faults. Off indicates system cooling is OK.
Indicates a system failure. Off indicates system is OK.
22 Intel® SR870BN4 Server System Product Guide
Page 23
Peripheral Bay
CAUTION
Removal of the LS240 and the DVD/CD drives requires removal of the
peripheral bay from the chassis. Therefore, the LS240 and the DVD/CD
drives cannot be hot-swapped. Power must be removed from the system
when installing or removing these drives to avoid component damage.
The peripheral bay consists of two sections:
The hot-swap hard drive bay (upper section) supporting three 1-inch hot-swap Ultra320 SCSI
hard disk drives (A in Figure 4).
The removable media drive bay (lower section) supporting:
- One ½-inch IDE DVD/CD-ROM (B in Figure 4)
- One ½-inch IDE LS-240 drive (C in Figure 4) or removable EMI Filler Panel (D in Figure 4).
A
B
C
D
TP00229
Figure 4. Peripheral Bay
Intel® SR870BN4 Server System Product Guide 23
Page 24
Hot-swap Hard Disk Drive Bay
The hot-swap hard disk drive carrier (see Figure 5) is designed to accept 15,000-RPM (and slower)
Ultra320 SCSI technology SCA-type hard disk drives.
The peripheral bay is designed to support Low Voltage Differential (LVD) SCSI disk drives only.
Single-Ended (SE) SCSI devices are not supported in the peripheral bay. SE drives are only
supported on the external SCSI connector.
A
B
OM12933
A Carrier latch
B Status indicator
Figure 5. Hard Disk Drive Carrier
The carriers contain light-pipes that allow dual color LED indicators to show through the bezel to
display hard disk drive status as described in Table 4.
Table 4. SCSI Hard Drive LED Details
Feature Description
Green, flashing Indicates the hard drive is active
Yellow/Green flashing Indicates a hard drive fault and hard drive is powered
Yellow/Blank flashing Indicates a hard drive fault and hard drive is not powered
Not illuminated Indicates no hard drive is installed in the bay
24 Intel® SR870BN4 Server System Product Guide
Page 25
Removable Media Drive Bays
The slim-line LS-240 and DVD/CD-ROM drives and their adapter boards are installed in plastic
carriers (see Figure 6) and are inserted from the front of the removable media drive bay. The user
must switch off system power and remove the peripheral bay to remove or install these drives. If
the LS-240 is not included with the server, then a filler panel must be used (see D in Figure 6).
C
B
A
DVD/CD-ROM LS-240 Floppy Disk Drive
A Latch A Latch
B Adapter board with locking connector B Adapter board with locking connector
C Plastic Carrier C Plastic Carrier
Figure 6. DVD/CD-ROM and LS-240 Drive Carriers
A
C
B
SCSI Backplane Board
The SCSI backplane board mates with the midplane board connector. It contains three 80-pin
Single Connector Attachment (SCA)-2 connectors for hot-swap hard disk drives. The SCSI
backplane board performs the tasks associated with hot-swapping the hard disk drives and
enclosure monitoring and management. The features supported by the SCSI backplane board
include the following:
Monitoring the SCSI bus for enclosure services messages, and acting on them appropriately.
Examples of such messages include: activate a drive fault indicator; power down a drive that
has failed; and report SCSI backplane temperature.
SAF-TE intelligent agent, which acts as proxy for “dumb” I2C devices (that have no bus
mastering capability) during intrachassis communications.
D
TP00230
✏ NOTE
Because all hard disk drives have different cooling, power and vibration
characteristics, Intel validates specific hard disk drive types in the
SR870BN4 system. Refer to the SR870BN4 Server System Validation
Summary on the Intel Business Link for a list of these drives available.
Intel® SR870BN4 Server System Product Guide 25
Page 26
Processor/Memory Subsystem Serviceability Status Indicators
The serviceability status indicators contained in the processor/memory subsystem are shown in
Figure 7 and described in Table 5. To view these indicators, remove the front bezel.
ACE
BDF
Figure 7. Location of Processor/Memory Subsystem Serviceability Indicators
A Processor 1 Present (green) On – Processor 1 is present and installed properly
Off – Processor 1 not detected
B Processor 2 Present (green) On – Processor 2 is present and installed properly
Off – Processor 2 not detected
C Processor 3 Present (green) On – Processor 3 is present and installed properly
Off – Processor 3 not detected
D Processor 4 Present (green) On – Processor 4 is present and installed properly
Off – Processor 4 not detected
E Memory Board 1 Interlock to
Processor Board (green)
F Memory Board 2 Interlock to
Processor Board (green)
On – Memory board 1 is inserted properly into the processor board
Off – Memory board 1 to processor board interlock not detected
On – Memory board 2 is inserted properly into the processor board
Off – Memory board 2 to processor board interlock not detected
✏ NOTE
Two additional LEDs (Green and Amber) and a switch appear on the left side
of the processor board. These components are not implemented in the
SR870BN4 system and are not visible or accessible through the front bezel.
OM12896
26 Intel® SR870BN4 Server System Product Guide
Page 27
Chassis Back
Figure 8 shows the features found on the chassis back panel including the I/O bay, the power
supply modules, and user-accessible connectors.
ACDE
B
J
I
FGH
OM12888
A AC input power connectors
B
PCI Slots (All slots support hot-plug PCI add-in cards)
Slots 1 through 4 100-MHz, 64-bit PCI-X slot, half length
Slot 5 100-MHz, 64-bit PCI-X slot, full length
Slots 6 through 8 133-MHz, 64-bit PCI-X slot, full length
C Video port, standard VGA compatible, 15-pin connector
D External SCSI connector (optional)
E Serial port, 9-pin RS-232 connector
F Ethernet port, RJ45 connector
G Four USB ports, 4-pin connectors
H ICMB connectors in/out (optional)
ICMB port 1, SEMCONN 6-pin connector
ICMB port 2, SEMCONN 6-pin connector
I Power supply 2
J Power supply 1
Notes: 1. PCI slots support 3.3 V signal adapter cards only.
2. External SCSI bus supports both LVDS and SE signals via the external SCSI connector.
3. Emergency Management Port (EMP) access is provided via shared serial port.
2
3
1
Figure 8. Chassis Back Features
Intel® SR870BN4 Server System Product Guide 27
Page 28
Back Panel
Figure 9 shows the location of the indicators and controls found on the back panel.
AB
C
D
System ID Indicator LED
A System ID LED (blue) Identifies the system. The system ID LED is activated either by the
System ID switch on the front panel or through server management.
Hot-plug PCI Add-in Card Switches and LEDs
B
Attention Switch Notifies PCI hot-plug system software (ACPI PHP ASL) that a PCI
hot-plug operation is about to take place.
WARNING: Verify in BIOS release notes that this feature is
supported before using the Attention button.
MRL (Manually-operated
Retention Latch) Switch
Green LED On – PCI slot is powered.
Amber LED On – PCI slot or card fault condition.
Ethernet Interface Status LED Indicators
C Network Interface Status
LED (green)
D Network Interface Status
LED (yellow)
Disables power to the PCI slot if a PCI add-in card is present.
Off – PCI slot is powered down.
Shows activity and status.
Shows activity and status.
Figure 9. Back Panel View Showing Indicator and Switch Locations
OM12889
28 Intel® SR870BN4 Server System Product Guide
Page 29
Power Supply LED Indicators
Each power supply module has three status LEDs the location and operating conditions for which
are shown in Figure 10.
ACB
OM12887
A Power LED (green) On - indicates the presence of DC power in the system
Blinking - indicates the system is in ACPI sleep mode
Off - indicates the power is turned off or the power source is
disrupted
B Failure LED (amber) Indicates a power supply failure
C Predictive Failure LED (amber) Indicates a power supply failure is imminent
Figure 10. Power Supply Indicators
Table 6. Power Supply LED Status Indicators
A
No AC power to all PSU OFF OFF OFF
No AC power to this PSU only or PS
failure
AC present / Standby Output On Blinking OFF OFF
Power supply DC outputs ON and OK ON OFF OFF
Current limit ON OFF Blinking
Predictive failure ON Blinking/Latched OFF
✏ NOTE
Proper system cooling requires that the power supply bay be filled either by
two power supply modules, or a power supply module and a filler panel.
B
(PWR)
Power Supply
(Green LED)
OFF OFF ON
(FAIL)
Power Supply Fail
(Amber LED)
C
(PFAIL)
Predictive Failure
(Amber LED)
Intel® SR870BN4 Server System Product Guide 29
Page 30
Chassis Top
I/O Subsystem Serviceability Indicators
Figure 11 shows the I/O subsystem serviceability indicators. The indicators are located on the I/O
board and are visible through the system top cover via light pipes. The I/O serviceability indicators
provide system power, system reset, and interlock status for various subsystem and module
connectors. These LEDs are powered by standby voltage to provide status as long as AC power is
supplied to the system.
System In Reset (amber) On – system reset asserted
Off – system reset not asserted
System Power Good
(green)
I/O Board to Midplane
Board Interlock (green)
I/O Riser to I/O Board
Interlock (green)
Processor/Memory/CPU
Board Interlock (green)
SCSI Board to Midplane
Board Interlock (green)
On – system power within normal operational range
Off – system power failure
On – I/O subsystem inserted properly into midplane board
Off – I/O subsystem to midplane board interlock not detected
On – I/O riser inserted properly into I/O board
Off – I/O riser to I/O board interlock not detected
On – processor/memory subsystem inserted properly into midplane board
Off – processor/memory subsystem to midplane board interlock not detected
On – SCSI backplane board inserted properly into midplane board
Off – SCSI backplane board to midplane board interlock not detected
Only qualified technical personnel should access the processor, memory,
and non-hot-plug I/O subsystem areas while the system is energized as
some exposed circuits exceed 240 VA and may cause burn injury if
accidentally contacted.
The power subsystem can be configured as following:
Two power supply modules installed, (1+1) redundancy at 220 VAC
One power supply module installed, non-redundant at 220 VAC only
Two power supply modules installed, non-redundant for 120 VAC
The power subsystem consists of the following:
Power supply modules
Plug-in DC-to-DC converters
Power pods (located adjacent to the processors on processor board)
The power distribution board
Power Supply Modules
The power supply modules are Server System Infrastructure (SSI) compliant, universal AC input
with Power Factor Correction (PFC) Distributed Power Supplies (DPS). The power supply
modules are rated at 1200 W over an input range of 180-264 VAC, and at 700 W over an input
range of 90-132 VAC.
One power supply module connected to 220 VAC is capable of handling the worst-case power
requirements for a fully configured system: four processors, 32 GB of memory, eight PCI add-in
cards, three hard disk drives, a DVD or CD drive, and an LS-240 drive.
The power supply has two DC outputs: 48 V (main) and 12 V (standby). The 48 V main power is
distributed throughout the server and is converted locally at point-of-load using either embedded or
plug-in DC-to-DC converters.
In an N+1 configuration the 48 VDC outputs have active (forced) current sharing and 12 VDCSB
outputs have passive current sharing.
The two externally enabled outputs have the following ratings:
+48 VDC at: 24.0 A @HI line /13.5 A @LO line
+12 VDCSB at: 4 A @any line
Intel® SR870BN4 Server System Product Guide 31
Page 32
Redundant AC Power Source Operation
Each power supply module requires one power cord to supply AC power to the system. When two
power supply modules and two power cords are installed, the system supports (1+1) power cord
redundancy at 220 VAC. This feature allows the system to be powered by two separate AC
sources. In this configuration, the system continues to operate without interruption if one of the AC
sources fails.
Plug-in DC-to-DC Converters
Two types of plug-in DC-to-DC converters are used in the system:
5 V output
Voltage ID (VID) (2.5 or 3.3 V output)
A control bit set by the board determines output voltage on the VID DC-to-DC converters. The
T-DC-to-DC converters contain an LED for failure indication.
The processor board supports three VID T-DC-to-DC converters (one 3.3 V and two 2.5 V).
The I/O board supports two 5 V and two VID (3.3 V) T-DC-to-DC converters. Each T-DC-to-DC
converter powers a separate plane on the board; therefore all DC-to-DC converter slots must be
populated.
Processor Power Pods
Dedicated power pods supply power to each processor. The input connector of the power pod is
connected to the 48 V power on the processor board via a short cable. The output connector of the
power pod mates directly with the processor package.
The Power Distribution Board
The power distribution board supplies 48 V main and 12 V standby power to all server system
components.
Cooling Subsystem
CAUTION
The chassis top cover must be installed and closed for proper system cooling.
Additionally, cooling components must be hot-swapped within a limited time
period. This time period applies only to the time that the cooling component
is physically removed, not from the time of failure.
The cooling subsystem consists of a hot-swap, redundant (3+1) system fan array installed in the fan
bay, and the fans in the power supply modules. In the event of a cooling component failure, system
cooling is maintained and the system continues to operate while the component is being
hot-swapped. All system fans have tachometer output and internal speed control.
✏ NOTE
The server supports only a fully populated system fan configuration. All
configurations are redundant except those with only one power supply
installed.
32 Intel® SR870BN4 Server System Product Guide
Page 33
A series pair of 120x38 mm system fans cools the processors and part of the I/O subsystem. The
rest of the processor/memory and I/O subsystem components, hard drives and power supplies are
cooled by a series pair of 120x25 mm system fans along with the power supply fans. Hot-swap
system fans drop into the fan bay and interface with connectors on the I/O board.
The fan bay also contains the individual fan status indicators that can be seen when the back top
chassis cover is open. A system fan failure is indicated by two LEDs, the LED on the
corresponding fan (A in Figure 12), and the Cooling Fault LED on the front panel (B in Figure 12).
A
B
Figure 12. Fan Status Indicators
OM12937
Intel® SR870BN4 Server System Product Guide 33
Page 34
2 Board Set Description
Figure 13 displays a block diagram of the system and the board set within the system.
Power PodPower PodPower PodPower Pod
Processor Board
Memory BoardMemory Board
Intel®
Itanium 2
CPU 1
FWH
P64H2P64H2
133 MHz PCI-X Full Length
Intel®
Itanium 2
CPU 2
LPC
VHDM Connector
VHDM Connector
VHDM Connector
VHDM Connector
HL-2
HL-2
P64H2
133 MHz PCI-X Full Length
133 MHz PCI-X Full Length
SNC-M
SP1
SP1
100 MHz PCI-X Full Length
FSB
SIOH
100 MHz PCI-X Half Length
Intel®
Itanium 2
CPU 3
SP2
SP2
HL-2
100 MHz PCI-X Half Length
100 MHz PCI-X Half Length
Intel®
Itanium 2
CPU 4
RDRAM0
RDRAM1
RDRAM2
Mid-plane Board
Front Panel
Ultra-4
SCSI
IDE
Internal SCSI
External SCSI
100 MHz PCI-X Half Length
HDM Connector
(passes through mid-plane board)
HDM Connector
HL-1
RDRAM3
FWH
Sahalee
BMC
ICH-4
Fan Sense
LPC
82540EM
NIC
SCSI Backplane Board
DMHDMHDMHDMH
I/O Baseboard
I/O Riser Board
SMC
Super IO
Rage XL
ICMB
Board
Power Supply
Power Supply
Power Distribution
Board
Front
Panel
ICMB Port
Serial Port
Dual USB Ports
Dual USB Ports
+ Ethernet Port
Video Port
External SCSI
Connector
LS240 Adapter Board
Dockable IDE Devices
1/2"
LS240
34 Intel® SR870BN4 Server System Product Guide
DVD/CD Adapter Board
1/2" DVD/
CD
Figure 13. Server System Block Diagram
Hot Swap SCSI Drives
Page 35
System Board Set
This section highlights the main features of the board set. The board set contains the following:
The processor board contains sockets for installing up to four Intel Itanium 2 processors and
supports up to four power pods. It also accepts the memory boards.
The processor board and memory boards are installed horizontally in the processor/memory
module. The processor/memory module docks into the front of the chassis and mates with the
midplane board mounted vertically in the middle of the chassis.
The processor board supports the following:
Sockets for up to four Intel Itanium 2 processors. Two of the processor sockets are mounted on
the secondary side of the processor board.
Provision for up to four 48 V DC-to-DC converter power pods, one for each Intel Itanium 2
processor.
DC-to-DC voltage converters:
Two 48 V to 2.5 V plug-in DC-to-DC converters for DDR memory support
One 48 V to 3.3 V plug-in DC-to-DC converter
Embedded regulators:
3.3 V to 1.2 V
3.3 V to 1.5 V
3.3 V to 1.8 V
1.8 V to 1.3 V linear regulator
One SNC-M component of the Intel®E8870 chip set.
Three Firmware Hubs (FWH) for BIOS and system configuration utility (SCU) software.
Two memory board connectors that support two Rambus channels each. One memory
connector is mounted on the secondary side of the processor board.
One VHDM 360-pin connector for I/O connections.
One debug port for use with an In-Target Probe (ITP) (debug only).
Two I2C system management buses (SMBus).
Serviceability LEDs.
✏ NOTE
The processor board also contains a switch and two LEDs on the front left
corner of the primary side of the board that are not used in the SR870BN4
server system.
36 Intel® SR870BN4 Server System Product Guide
Page 37
Processor Overview
Each Intel Itanium 2 processor plugs into a 700-pin Zero Insertion Force (ZIF) socket. Each
processor is powered by a 48 V power pod located adjacent to the processor on the processor board.
Attached to the top of each processor is a heat sink that dissipates thermal energy.
CAUTION
When shipping, unpacking, or handling Intel Itanium 2 processors, be sure to
follow the guidelines described in “Handling the Intel Itanium 2 Processors”
on page 211.
Memory Boards
The processor board is designed to support two memory boards (both of which must be installed for
the system to operate). The memory boards are installed on the primary and secondary side of the
processor board assembly as shown in Figure 84 on page 206.
The main components of the memory boards are shown in Figure 98 on page 222 and described as
follows:
Eight 184-pin, DDR-SDRAM DIMM sockets support up to 16 GB of memory using eight
2 GB DIMMs per memory board for a total of 32 GB per system using -4XX revision memory
boards, or up to 32 GB of memory using eight 4 GB DIMMs per memory board for a total of
64 GB per system using -5XX revision memory boards.
Two DMH (DDR Memory Hub) components of the E8870 chip set. This allows two Rambus
channels from the E8870-memory controller (SNC-M) to be extended to four DDR channels on
the memory boards. The Rambus channel supports 400 MHz operation and the DDR channels
support 100 MHz operation.
An integrated 2.5 V to 1.25 V DC-to-DC converter provides voltage for DDR signal
termination.
I2C logic.
Field Replaceable Unit (FRU) device ID accessed through a private I2C bus.
Voltage/temperature sensors.
DIMMs must be installed on a memory board in groups of four (a group of four constitutes a row)
as shown in Installing DIMMs on page 223.
CAUTION
DIMMs should only be installed, removed, or replaced by a technically
qualified person.
CAUTION
The system does not support mixed-sized DIMMs or DIMMs from different
vendors within the same row.
✏ NOTE
The BIOS automatically detects, sizes, and initializes the memory array,
depending on the type, size, and speed of the installed DIMMs. The BIOS
Intel® SR870BN4 Server System Product Guide 37
Page 38
reports memory size and allocation to the system through configuration
registers.
I/O Board
The I/O board is installed horizontally in the I/O bay. The I/O riser card plugs into a connector on
the I/O board. The I/O provides the following features:
Intel E8870 chip set with Scalability Port system interface
Six functionally independent Peripheral Component Interconnect (PCI) bus segments
Three hot-plug 133-MHz, 64-bit PCI-X slots
Five hot-plug 100-MHz, 64-bit PCI-X slots
Integrated dual channel LSI 53C1030 Ultra320 Low Voltage Differential SCSI (LVDS)
controller
I/O riser support connector for I/O interface
On-board power conversion from 48 V bulk power
System reset and clock generation circuits
I2C server management interface
Redundant hot-plug system fan interface
I/O Riser
To conserve space on the I/O board, most system I/O and server management functions have been
placed on the I/O riser card that plugs into the I/O board. The I/O connectors include video, serial,
Local Area Network (LAN), and Universal Serial Bus (USB). The I/O riser:
Contains an IDE bus controller and connector. The IDE bus is routed to the I/O board where it
is further routed to the midplane board’s disk bay connector.
Converts 12 V STDBY (standby) to +5 V STDBY and +3.3 V STDBY and supplies them to
the I/O board.
Mates directly onto the I/O board and together they contain all of the I/O interfaces for the
board set.
38 Intel® SR870BN4 Server System Product Guide
Page 39
The I/O riser provides the following features:
One I/O Control Hub 4 (ICH4) component
Four Universal Serial Bus (USB) ports
One IDE interface routed through the I/O board connector
3 MB of flash memory
Server management controller
Integrated Intelligent Chassis Management Bus (ICMB)
Integrated Rage† XL video controller and memory
Video port
Power control - Advanced Configuration and Power Interface (ACPI)
Speaker control
Integrated standby voltage DC-to-DC converters generating 3.3 V standby and 5 V standby
Midplane Board
The passive midplane board contains the following features:
VHDM connectors for the processor/memory subsystem and the I/O subsystem
An HDM connector that routes the SCSI bus, two IDE busses, and miscellaneous signals
between the I/O board and the SCSI backplane
Routing of four scalability ports
48 V power distribution
12 V standby distribution
3.3 V standby distribution
12 V distribution from the SCSI backplane board to the I/O board and power distribution board
Blind-mate power distribution board connector
Blind-mate front panel connector
Front Panel Board
The front panel board contains switches, LEDs, and the speaker for system interface.
Intel® SR870BN4 Server System Product Guide 39
Page 40
SCSI Backplane Board
The SCSI backplane board supports three LVDS hard drives. Its features include:
Three SCA connectors for hot-swap 1-inch SCSI hard drives
One blind-mate connector for dockable slim-line IDE LS240 device
One blind-mate connector for dockable slim-line IDE DVD or CD device
SCSI accessed fault-tolerant enclosures (SAF-TE) logic
48 V to 12 V integrated DC-to-DC converter
12 V to 5 V integrated DC-to-DC converter
5 V to 2.5 V linear regulator
Peripherals
The server connects to supported peripheral devices through interfaces located on the I/O Board.
The Super I/O on this board provides four USB ports, an Ethernet port, a serial port, an external
SCSI connector (optional),
For a detailed view of the I/O Board connections, see Figure 8 on page 27.
External SCSI Connector (Optional)
An external SCSI connector is available as an option. A cable runs from the I/O board to the
external SCSI connector installed on the back panel.
The I/O board contains two Ultra320 compliant SCSI channels. One channel is used internally
while the other is for external system use. While the internal channel supports only Low Voltage
Differential (LVD) signaling, the external channel supports both LVD and SE (single-ended)
signaling. With LVD signaling, the channels can each support a maximum data rate of
320 MB/sec.
a VGA video output port, and in and out ICMB connectors (optional).
✏ NOTE
The internal SCSI signal is routed to the midplane board’s disk bay
connector to interface with internal SCSI devices. There is an optional
connector on that bus that allows an external SCSI controller to drive the
internal bus.
40 Intel® SR870BN4 Server System Product Guide
Page 41
Add-In Board Slots
The I/O board has three 64-bit/133 MHz hot-plug PCI-X and five 64-bit/100 MHz PCI-X
expansion slots contained in the following three PCI segments:
P64H2,0 provides for PCI-X slots 1 through 3 (all 100 MHz) and the dual channel LVDS
controller
P64H2,1 provides for PCI-X slots 4 through 6 (two 100 MHz and one 133 MHz)
P64H2,2 provides for PCI-X slots 7 and 8 (both 133 MHz)
Video
The onboard, integrated ATI RAGE XL 64-bit SVGA chip contains an SVGA controller that is
fully compatible with industry video standards. The system comes with 8 MB of 10-nanosecond
onboard video memory.
The video controller supports pixel resolutions of up to 1600 x 1200 and up to 16.7 million colors.
The controller also provides hardware accelerated bit block transfers of data.
The SVGA controller supports analog VGA monitors (single and multiple frequency, interlaced
and noninterlaced) with a maximum vertical retrace noninterlaced frequency of 100 Hz.
The video connector is located on the I/O riser. See Figure 8 on page 27 for the location of this
connector.
SCSI Controller
A LSI 53C1030 Ultra3 SCSI chip is a highly integrated bus master, dual-channel SCSI I/O
processor for SCSI initiator and target applications. The chip supports dual channel, Ultra3
(Fast-80) SCSI functionality. This device interfaces the PCI bus to two Ultra3 SCSI buses. The
53C1030 is a fully autonomous device, capable of managing multiple I/O operations and associated
data transfers from start to finish without host intervention. The 53C1030 provides power
management feature support in accordance with the PCI Bus Power Management Interface Specification.
ICH4 IDE Controller
The ICH4 IDE controller is a multifunction device on the I/O Board that acts as a PCI-based Fast
IDE controller. The device controls the following:
PIO and IDE DMA/bus master operations
Mode 4 timing
Transfer rates up to 22 MB/sec (33 MB/sec using ultra DMA transfers)
Buffering for PCI/IDE burst transfers
Master/slave IDE mode
Intel® SR870BN4 Server System Product Guide 41
Page 42
Server Management
The server management features are implemented using two micro controllers: the Baseboard
Management Controller (BMC) on the I/O board and the QLogic
†
GEM359 SCSI hot-swap
controller on the SCSI backplane board. The ICMB controller is integrated in the BMC and
provides an interface to the external ICMB via the ICMB board.
The firmware for the BMC of each micro controller is field-upgradeable using the Firmware
Update utility. For information on the Firmware Update Utility, refer to “Running the Firmware
Update Utility” on page 67. The GEM359 firmware can be updated using a separate utility.
Baseboard Management Controller (BMC)
The Intel Baseboard Management Controller (BMC) and its associated circuitry reside on the I/O
riser card. The BMC autonomously monitors system platform management events and logs their
occurrences in the non-volatile System Event Log (SEL). This includes events such as
over-temperature and over-voltage conditions, and fan failures. The BMC can also provide the
interface to the monitored information so system management software can pole and retrieve the
present status of the platform.
The BMC also provides the interface to the non-volatile ‘Sensor Data Record (SDR) Repository’.
Sensor Data Records provide a set of information that system management software can use to
automatically configure itself for the number and type of IPMI sensors (such as temperature and
voltage sensors) in the system.
The following is a list of the major functions of the BMC:
System power control
Platform Event Paging (PEP) / Platform Event Filtering (PEF)
Power distribution board monitoring
Temperature and voltage monitoring
Fan failure monitoring
Processor presence monitoring (no processors installed)
Interlock monitoring
Speaker ‘Beep’ capability on standby and when system is powered up
Intel Itanium 2 processor SEEPROM interface (for processor information ROM [PIROM] and
scratch EEPROM access)
Processor temperature monitoring
Hot-plug PCI slot status reporting
Processor core ratio speed setting
Chassis general fault light control
Chassis cooling failure light control
Chassis power fault light control
Chassis power light control
Chassis ID LEDs control
System Event Log (SEL) interface
Sensor Data Record (SDR) repository interface
SDR/SEL timestamp clock
Board set FRU information interface
42 Intel® SR870BN4 Server System Product Guide
Page 43
Fault resilient booting
System management watchdog timer
Front panel system diagnostic-interrupt handling
Platform Management Interruption (PMI) / System Diagnostic Interrupt (SDI) status monitor
Event receiver
System interface to the IPMB (via system interface ports)
IPMI Management Controller Initialization Agent (MCIA)
Emergency Management Port (EMP) interface
Serial/modem and LAN alerting
In this platform, the BMC also plays the role of the chassis bridge controller, thus providing
integrated ICMB support. ICMB transports server management information between various
chassis in a cluster configuration that can contain multiple servers and peripherals.
QLogic GEM359 SCSI Hot-swap Controller
The QLogic GEM359 Hot-swap Controller resides on the SCSI backplane board. The primary
functions of the GEM359 are as follows:
Implements the SAF-TE command set
Controls the SCSI Hard Drive fault LEDs
Provides a path for management information via the SCSI
Retrieves hard disk drive fault status, SCSI backplane temperature, and fan failure information
via IPMB
Queries the status of the power distribution board by retrieving information from the BMC
via IPMB
Controls hard disk drive power-on and power-down, facilitating hot-swapping
Intel® SR870BN4 Server System Product Guide 43
Page 44
3 Configuration Software and Utilities
Power-on Sequence and Power-on Self-Test (POST)
Turning on the system causes POST to run and control to pass to the Boot Manager. From the Boot
Manager, the user can choose to invoke the Extensible Firmware Interface (EFI) Shell or the user
can choose to go to the Boot Maintenance Menu. For information on the EFI Shell, refer to “The
Extensible Firmware Interface (EFI) Shell” on page 48.
Follow these steps to power up the SR870BN4 server:
1. Press the power button on the front control panel. Pressing this button causes the server fans to
start up and POST to begin running. The user can monitor boot progress on the video display
on a monitor attached to the system.
2. POST, which is stored in flash memory, begins running. POST checks the drive carriers,
processors, memory, keyboard, and most installed peripheral devices. During the memory test,
POST displays the amount of memory it is able to access and test. The length of time needed
to test memory depends on the amount of memory installed.
3. Video appears on the monitor attached to the system and begins to display boot progress. The
AMI BIOS banner displays the loaded versions of the BIOS, PAL, SAL, and EFI.
4. POST concludes and passes control to the boot manager.
5. From the boot manager, the arrow keys can be used to highlight the option that invokes the EFI
shell operating system (if installed), or the user can highlight and select the boot maintenance
menu. Selecting the boot maintenance menu lets the user configure boot options and other boot
environment variables. Booting to the EFI shell causes the following prompt to appear:
Shell>
6. When the user sees this prompt, the user can load and start an operating system.
The Extensible Firmware Interface (EFI) Boot Manager
The EFI boot manager allows the user to control the server’s booting environment. Depending on
how the user has configured the boot options, after the server is powered up the boot manager
presents the user with different ways to bring up the system. For example, the user can boot to the
EFI Shell, to an operating system located on the network or residing on media in the server, or to
the Boot Maintenance Menu.
EFI Shell: A simple, interactive environment that allows EFI device drivers to be loaded, EFI
applications to be launched, and operating systems to be booted. The EFI shell also provides a
set of basic commands used to manage files and the system environment variables. For more
information on the EFI Shell, refer to “The Extensible Firmware Interface (EFI) Shell” on page
48.
44 Intel® SR870BN4 Server System Product Guide
Page 45
Boot Options: Files that the user includes as boot options. The user adds and deletes boot
options by using the Boot Maintenance Menu. Each boot option specifies an EFI executable
with possible options. For information on the Boot Maintenance Menu options, refer to Table
7.
Boot Maintenance Menu: A menu of items allowing the user to configure boot options and
other boot environment variables. Table 7 describes each menu item in the Boot Maintenance
Menu.
Table 7. Boot Maintenance Menu Options
Option Description
Boot from a File Automatically adds EFI applications as boot options or allows the user to
boot from a specific file.
When the user chooses this option, the system searches for an EFI
directory in all EFI System Partitions in the system. For each EFI directory
the system finds, it searches through that directory’s subdirectories. Within
each subdirectory, the system looks for the first file that is an executable EFI
Application. Each file that meets this criterion can be automatically added
as a boot option. In addition, legacy boot options for A: and C: are also
added if those devices are present.
Using this option, the user can also launch a specific application without
adding it as a boot option. In this case the EFI Boot Manager searches the
root directories of all of the EFI System Partitions present in the system for
the specified EFI Application.
To boot from a file:
At the menu, select Boot from a File Option with the arrow key.
Hit the <Enter> key to select.
Select the EFI file to boot from with the arrow key.
Hit <Enter> to select.
Add a Boot Option Adds a boot option to the EFI Boot Manager. The user specifies the option
by providing the name of the EFI application. Along with the name the user
can also provide either ASCII or UNICODE arguments the file might use.
Given the EFI application name and any options, the EFI Boot Manager
searches for the executable file in the same partitions and directories as
described in “Boot from a File” option. When the file is found, it is executed.
To add a boot option:
At the menu, select Add Boot Option with the arrow key.
Hit the <Enter> key to select.
Type in the name of the EFI application to add and hit <Enter>.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
continued
Intel® SR870BN4 Server System Product Guide 45
Page 46
Table 7. Boot Maintenance Menu Options (continued)
Option Description
Delete Boot Options This feature allows the user to delete a specific boot option or all boot
options.
To delete boot options:
At the menu, select Delete Boot Option with the arrow key.
Hit the <Enter> key to select.
Select the boot option to delete with the arrow key.
Hit <Enter> to select.
Enter <Y> to confirm.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
Change Boot Order This feature allows the user to control the relative order in which the EFI
Boot Manager attempts boot options. For help on the control key
sequences the user needs for this option, refer to the help menu.
To change the boot order:
At the menu, select Change Boot Order with the arrow key.
Select the Option to move with the arrow key.
Hit <u> to move up in the boot order.
Hit <d> to move down in the boot order.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
Manage BootNext Setting This feature allows the user to select a boot option to use one time (the next
boot operation).
To manage boot next setting:
At the menu, select Manage Boot Next Setting with the arrow key.
Select the Option to boot next with the arrow key.
Hit <b> to make this option the next boot option.
Hit <r> to reset.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
Set Auto Boot Timeout This feature allows the user to define the value in seconds that pass before
the system automatically boots without user intervention. Setting this value
to zero disables the timeout feature.
To set auto boot timeout:
At the menu, select Set Auto Boot Timeout with the arrow key.
Three options are available.
Select the Choose Value option with the arrow key and enter a value of “0”
to disable auto boot.
Select the Delete option with the arrow key and select the Delete setting
with the arrow key and hit <Enter>.
Choose a time out value of 65535 (0xFFFF) to allow the user to press any
key while booting to EFI to disable timeout.
continued
46 Intel® SR870BN4 Server System Product Guide
Page 47
Table 7. Boot Maintenance Menu Options (continued)
Option Description
Select Console Output
Device
Select Console Input Device This feature allows the user to select the device that the console receives
Select Standard Error Device This feature allows the user to select the standard error device.
Cold Reset Performs a platform-specific cold reset of the system. A cold reset means a
Exit Returns control to the EFI Boot Manager main menu. Selecting this option
This feature allows the user to select the device that the console output is
sent to.
To select the console output device:
At the menu, select Manage Boot Next Setting with the arrow key.
Select the Option to boot next with the arrow keyHit <b> to make this option
the next boot option.
Hit <r> to reset.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
input from.
To select the console input device:
At the menu, select Manage Boot Next Setting with the arrow key.
Select the Option to boot next with the arrow key.
Hit <b> to make this option the next boot option.
Hit <r> to reset.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
To select the standard error device:
At the menu, select Manage Boot Next Setting with the arrow key.
Select the Option to boot next with the arrow key.
Hit <b> to make this option the next boot option.
Hit <r> to reset.
Select Save to NVRAM.
Select Exit to return to the Boot Manager.
full platform reset.
To perform a cold reset:
At the menu, select Set Auto Boot Timeout with the arrow key.
Hit <Enter>.
The system resets.
displays the active boot devices, including a possible integrated shell.
Intel® SR870BN4 Server System Product Guide 47
Page 48
The Extensible Firmware Interface (EFI) Shell
The EFI Shell is an EFI application that allows other EFI applications to be launched, EFI device
drivers to be loaded, and operating systems to be booted. The combination of the EFI firmware and
the EFI Shell provides an environment that can be modified to easily adapt to many different
hardware configurations.
The EFI shell also provides a set of basic commands used to manage files and EFI NVRAM shell
and boot variables. A list of these basic commands is shown in Table 8. A more detailed
description of the commands is available on the EFI website. To obtain the document, navigate to
the http://developer.intel.com/technology/efi URL and click on the Tools hyperlink. Next, click on
“EFI Sample Implementation”, and follow the appropriate links to download the sample
implementation. After downloading the sample, locate the “EFI1.1ShellCommands” document.
Descriptions of the EFI shell commands are also available when operating in the EFI Shell by
typing “help” and hitting the <Enter> key.
In addition to the standard shell commands available in the EFI Shell, the EFI environment allows
the user to create your own shell commands and EFI applications. For detailed information about
the EFI Shell, its commands, and the ability to develop within the environment, refer to the EFI
Developer’s Guide. To obtain the document, navigate to the
http://developer.intel.com/technology/efi URL and click on the Tools hyperlink. Next, click on
“EFI Application Toolkit”, and follow the appropriate links to download the toolkit. After
downloading the toolkit, locate the document named “Efi_dg”.
48 Intel® SR870BN4 Server System Product Guide
Page 49
Table 8. EFI Shell Commands
Command Description
<drive_name>:
alias [-bdv] [sname] [value] Sets or gets alias settings
attrib [-b] [+/- rhs] [file] Views or sets file attributes
bcfg -? Configures boot driver and load options in EFI NVRAM
botmaint Launches Boot Maintenance Manager
break Executes a breakpoint
cd [path] Changes the current directory
cls [background color] Clears the screen
comp file1file2 Compares two files
connect [-r] [-c] Handle#
½DeviceHandle# DriverHandle#
cp [-r] file [file] ... [dest] Copies files and directories, [-r] = recursive
date [mm/dd/yyyy] Gets or sets the date
dblk device [Lba] [Blocks] Performs a hex dump of BlkIo Devices
devices [-b] [-1XXX] Displays devices
devtree [-b] [-d] Displays device tree
dh [-b] [-p prot_id] | [handle] Dumps handle information
disconnect DeviceHandle#
[DriverHandle# [ChildHandle#]
dmem {address] [size] [;MMIO] Displays the contents of memory
dmpstore Dumps the variable store
drivers [-b] [-lXXX] Displays drivers
drvcfg [-c] [-lXXX] [-f] [-v] [-s] Invokes the driver configuration protocol
drvdiag [-c] [-lXXX] [-s] [-e] [-m] Invokes the driver diagnostics protocol
echo [[-on | -off] | [text] Echoes text to the standard output device or toggles script echo
edit [filename] Opens the text editor allowing the user to create or edit a file
eficompress infile outfile Compresses an EFI file
Efidecompress infile outfile Decompresses an EFI file
endfor Provides a delimiter for loop constructs (scripts only)
endif Provides a delimiter for IF THEN constructs (scripts only)
for var in <set>
goto label Makes batch file execution jump to another label
guid [-b] [sname] Dumps known guid ids
help [-b] [internal_command] Displays help information
hexedit [[-f]FileName|[-d DiskName
Offset Size]|[-m Offset Size]]
if [not] condition then Provides conditional constructs (scripts only)
Changes drives. For example, entering fs0: and pressing the
<Enter> key changes the drive to the LS-240 drive
Binds the EFI driver to a device and starts the driver
Disconnects device from driver
Edits in HEX mode
continued
Intel® SR870BN4 Server System Product Guide 49
Page 50
Table 8. EFI Shell Commands (continued)
Command Description
load driver_nameLoads a driver
loadbmp [-c] [-t] [-i[UGA Instance]] file Displays a bitmap file on the screen
loadpcirom romfile Loads a PCI option ROM
ls [-b] [dir] [dir] ... Obtains directory listings
map [-bdvr] [sname[:]] [handle] Maps sname to device path
mem [address] [size] [;MMIO] Dumps Memory or Memory Mapped IO
memmap [-b] Dumps memory map
mkdir dir [dir] Creates a new directory
mm address [Width] [;Type] [n] Memory Modify: type = Mem, MMIO, IO, PCI, [n] for non
interactive mode when inside a .nsh file
mode [col row] Sets or gets the current graphics mode
mount BlkDevice [sname[:]] Mounts a file system on a block device
mv [src…] [dst] Move one or more files/directories to destination
pause Prompts to quit or continue (scripts only)
pci [bus_dev] [func] Displays PCI device information
rconnect DeviceHandle#
[DriverHandle# [ChildHandle#]] | [-r]
reset [reset_string] Performs a cold reset
rm file/dir [file/dir] Removes files or directories
setsize file Sets size of a new file
stall microseconds Delays for the specified number of microseconds
time [hh:mm:ss] Gets or sets the time
type [-a] [-u] [-b] file Displays the contents of a file
ver Displays version information
vol fs [volume_label] Sets or displays a volume label
Reconnects one or more drivers from a device
50 Intel® SR870BN4 Server System Product Guide
Page 51
Using BIOS Setup
This section describes the BIOS Setup Utility. Use this utility to change the server configuration
defaults. The user can run the utility with or without an operating system present on the server.
Setup stores most of the configuration values in battery-backed CMOS. The rest of the values are
stored in flash memory. The values take effect when the user boots the server. POST uses these
values to configure the hardware. If the values and the hardware do not agree, POST generates an
error message and the user must then run Setup to specify the correct configuration.
Run Setup to view or modify such server board features as:
Serial port configuration
Time/date (to be stored in RTC)
IDE settings (LS-240, DVD/CD-ROM, etc.)
SCSI BIOS
Default CMOS settings and fail safe settings
Password security
Advanced chip set settings for boot up
Information on system configuration, version, peripheral population, RAM size, and cache size
Starting Setup
To start Setup during the power-on sequence, follow these steps:
1. Press the power button on the front control panel of the server. For the location of the power
button, see Figure 3 on page 21
2. When POST shows the message “Hit <F2> if the user wants to run SETUP,” press <F2>. If the
server has an administrator password configured, the system prompts the user to enter the
password. If the server does not have a password configured, the main screen of the BIOS
Setup Utility appears. For information on the setup screens, refer to “Primary Screens” on page
52.
Record Your Setup Settings
Before the user alters any settings the user should be sure that the current values are recorded. If
the default values ever need to be restored (after a CMOS clear, for example), the user must run
Setup again. Referring to recorded original settings could make your task easier.
Intel® SR870BN4 Server System Product Guide 51
Page 52
Navigating Setup Utility Screens
The BIOS setup utility consists of five primary menus. Each menu occupies a single screen and
presents a list of menu items. Some menu items are sub-menus, while others are settings that the
user can change from the screen. Table 9 describes how to navigate the utility screens and menus.
Table 9. Using Setup Screens
Press To
← Scroll left through the main menu screens
→ Scroll right through the main menu screens
ENTER Select a sub-menu item or accept a drop-down choice
TAB Select a field within a value (for example, date field)
F9 Select the default value
F10 Save your changes and exit Setup
ESC Go back to a previous screen
↑ Scroll up through menu items or value lists
↓ Scroll down through menu items or value lists
Primary Screens
The BIOS Setup Utility uses these five primary screens:
MainDisplays the BIOS version and details on processor type, and lets the user
configure the system time, date, and language. For details on this screen,
see “Main” on page 53.
AdvancedLets the user configure Option ROMs, configure peripheral devices, clear the
event log, and disable POST error pauses. For details on this screen, see
“Advanced” on page 55
SecurityLets the user set a password. For details on this screen, see “Security” on
page 56.
System Management Lets the user configure Console Redirection, Quite Boot, Serial Over
LAN, and Service Partition options. Also displays BMC and HSC
firmware revisions. For details on this screen, see “System
Management” on page 57.
ExitExits the utility with or without saving utilities and allows management of
custom settings. For details on this screen, see “Exit” on page 59.
52 Intel® SR870BN4 Server System Product Guide
Page 53
Main
Table 10 describes the menu items available on the Main screen. Default values appear in
brackets.
Table 10. BIOS Setup Main Screen Menu Items
Menu Item Default Value Description
Language [English (US)]
Spanish
Italian
French
German
System Time HH:MM:SS Set the System Time in hour:minute:second format.
System Date MM/DD/YYYY Set the System Date in month/day/year format.
Processor
Settings
BIOS Version [bios_version_number] The currently loaded version of BIOS. The user cannot
PAL Version [PAL_version_number] The currently loaded version of PAL. The user cannot
SAL Version [SAL_version_number] The currently loaded version of SAL. The user cannot
FPSWA Version [FPSWA_version_num] The currently loaded version of FPSWA. The user cannot
Press <Enter> to
present selection
submenu
Selects which language BIOS displays.
Selects the Sub-menu.
change this value. It appears for informational purposes
only.
change this value. It appears for informational purposes
only.
change this value. It appears for informational purposes
only.
change this value. It appears for informational
purposes only.
If yes, BIOS clears historical processor status
and retests all processors on the next boot
54 Intel® SR870BN4 Server System Product Guide
Page 55
Advanced
Table 12 describes the menu items available on the Advanced screen. Five menu items exist on
this screen. Each of these items contains sub-menus that in turn can also lead to subsequent
sub-menus. Default values appear in brackets.
Table 12. BIOS Setup Advanced Screen Menu Items
Primary
Menu Item
Peripheral
Configuration
Option ROM
Configuration
Sub
Menu Items Value
Serial Port B [Auto]
Enabled
Disabled
Base I/O
Address
Interrupt IRQ3
PCI SLOT 1
ROM
PCI SLOT 2
ROM
PCI SLOT 3
ROM
PCI SLOT 4
ROM
PCI SLOT 5
ROM
PCI SLOT 6
ROM
PCI SLOT 7
ROM
PCI SLOT 8
ROM
3F8
[2F8]
3E8
2E8
[IRQ4]
[Enabled]
Disabled
[Enabled]
Disabled
[Enabled]
Disabled
[Enabled]
Disabled
[Enabled]
Disabled
[Enabled]
Disabled
[Enabled]
Disabled
[Enabled]
Disabled
Description
Configures Serial Port B at boot time.
Auto Causes the server to determine the Base I/O
address and interrupt to use for the port.
Enabled Requires the user to supply the Base I/O
address and the interrupt value.
Disabled Causes the server to disable the port.
Determines the Base I/O Address for the port.
Determines the Interrupt for the port.
Enables Slot 1 Option ROM.
Enables Slot 2 Option ROM.
Enables Slot 3 Option ROM.
Enables Slot 4 Option ROM.
Enables Slot 5 Option ROM.
Enables Slot 6 Option ROM.
Enables Slot 7 Option ROM.
Enables Slot 8 Option ROM.
continued
Intel® SR870BN4 Server System Product Guide 55
Page 56
Table 12. BIOS Setup Advanced Screen Menu Items (continued)
Primary
Menu Item
Configuration
POST Error
Pause
Sub
Menu Items Value
Event
Logging
Clear All
Logs
[Enabled]
[Enabled]
Disabled
[No]
Yes
Disabled
Description
Select Enabled to allow logging to System Event Log. Event Log
Setting to Yes will clear the System Event Log..
Select “Disabled” if the user wants the system to boot
with no user intervention on critical POST errors.
Security
Table 13 describes the menu items available on the Security screen.
✏ NOTE
With the removal of legacy keyboard and mouse support, the legacy security
core has been removed. Therefore, the security menu is briefer than on other
server products. Also, the two-level password has been replaced with a
single-level password.
Table 13. BIOS Setup Security Screen Menu Items
Menu Item Default Value Description
Administrator
Password Is
Set Password Press <Enter> When the <Enter> key is pressed, the user is prompted for a
[Not Installed]
Installed
Status only, the user cannot modify. Once set, can be
disabled by setting to a null string, or clear password jumper
on board.
password, press ESC key to abort. Once set, can be
disabled by setting to a null string, or clear password jumper
on board.
Note that only alpha-numeric characters are supported for
the password. Other key entries are ignored
Also the password is not case-sensitive.
56 Intel® SR870BN4 Server System Product Guide
Page 57
System Management
Table 14 describes the menu items available on the System Management screen. Default values
appear in brackets.
Table 14. BIOS Setup System Management Screen Menu Items
Selecting this option enables the BIOS to display the OEM
logo during POST. If disabled, the BIOS displays the normal
POST messages.
This option is hidden if the BIOS does not detect a valid logo
in the flash area reserved for this purpose.
Enabling this option disables serial redirection.
Enabling this item allows the user to boot into Service
Partition Boot mode. The item automatically resets to
“Disabled” on the next system boot.
Selecting this option allows the user to configure for console
redirection.
Sets the time allowed for booting an OS, from media or PXE.
The currently loaded version of Baseboard Management
Controller firmware. The user cannot change this value. It
appears for informational purposes only.
Information field only, hidden if not detected. Displays the Hot
Swap Controller revision.
Table 15. Setup Console Redirection Sub Menu Items
Sub Menu Item Default Value Description
Serial Console
Redirection
Baud Rate 9600
Flow Control No Flow Control
Intel® SR870BN4 Server System Product Guide 57
Enabled/Disabled When enabled, Console Redirection uses only COM2.
When Console Redirection is enabled, use the baud rate
[19.2K]
38.4K
57.6K
115.2K
[CTS/RTS]
CTS/RTS + CD
XON/XOFF
specified. When EMP is sharing the COM port as console
redirection, the baud rate must be set to 19.2K to match
EMP baud rate.
No flow control.
CTS/RTS = Hardware based flow control.
CTS/RTS +CD = Hardware based + Carrier Detect flow
control. When EMP is sharing the COM port as console
redirection, the flow control must be set to CTS/RTS or
CTS/RTS+CD depending on whether a modem is used.
Page 58
Sub Menu Item Default Value Description
Xon/Xoff = Software based flow control
Terminal Type PC-ANSI
VT100+
VT-UTF8
Serial Port COM2 2F8 IRQ3
Remote Console
Reset
ACPI OS Headless
Operation
ACPI OS Baud Rate 9600
ACPI OS Flow Control No Flow Control
ACPI OS Terminal
Type
Enabled/Disabled Enables remote reset via escape key sequence;
Disabled
Same as BIOS
Serial Port
19.2k
38.4K
57.6k
115.2k
CTS/RTS
XON / XOFF
CTS/RTS + CD
PC-ANSI
VT100+
VT-UTF8
Select terminal type. Vt100+ only available when English
selected as the language. VT-UTF8 uses UNICODE.
PC-ANSI is the standard PC-type terminal.
Hardcoded – no selection available. Note that if Console
Redirection is enabled, then the Base I/O address and
IRQ selection of Serial Port B (under Menu Advanced,
sub-menu Peripheral Configuration) should match this
Serial Port setting under the Console Redirection
submenu.
ESC R ESC r ESC R
Used to pass information about serial redirection to ACPI
OS.
Only available when ACPI OS Headless Operation is
Same as BIOS or Serial Port.
Only available when ACPI OS Headless Operation is
Same as BIOS or Serial Port . Same options as above;
these are passed to the OS.
Only available when ACPI OS Headless Operation is
Same as BIOS or Serial Port . Same options as above;
these are passed to the OS.
58 Intel® SR870BN4 Server System Product Guide
Page 59
Exit
Table 16 describes the menu items available on the Exit screen. Default values appear in brackets.
Table 16. BIOS Setup Exit Screen Menu Items
Menu Item
Exit Saving Changes Lets the user exit Setup with or without saving your changes in CMOS. Clicking
Exit Discarding Changes Lets the user exit Setup with or without discarding your changes. Clicking on
Load Setup Defaults Lets the user load Setup with factory defaults. Clicking on the menu item
Save Custom Defaults
(This menu will not be
available until post
platform release)
Discard Changes Lets the user discard the changed values the user has accumulated during this
Description
on the menu item causes the system to prompt the user for a Yes or No
response.
Yes Saves your changes and exits the utility.
No Discards your changes and exits the utility.
the menu item causes the system to prompt the user for a Yes or No response.
Yes Discards your changes and exits the utility.
No Saves your changes and exits the utility.
causes the system to prompt the user for a Yes or No response.
Yes Loads the system setup defaults.
No Aborts the action.
Lets the user load Setup with custom defaults. Clicking on the menu item
causes the system to prompt the user for a Yes or No response.
Yes Loads setup values from a file previously saved through the Save
Custom Defaults menu item. the user must specify the file name.
No Aborts the action.
setup session. Clicking on the menu item causes the system to prompt the user
for a Yes or No response.
Yes Discards the setup values for the current setup utility session.
No Aborts the action.
Intel® SR870BN4 Server System Product Guide 59
Page 60
LSI SCSI Utility
The LSI SCSI utility allows the user to configure the SCSI capabilities of the server. This
configuration utility can be accessed using an EFI-based utility provided by Intel. This utility is
®
available on the Resource CD or from Intel
Business Link (IBL). Please contact your Intel
representative for more information on obtaining this utility.
The EFI utility can be evoked from the EFI shell prompt with the command EFICnfg.efi. From
here the SCSI drives can be configured. The utility contains help information at the bottom of each
screen. More information on this utility will be documented in a future revision of this document.
✏ NOTE
This utility is still being defined and changes may occur in the menus shown
below. Entrance into this utility may be updated in a future revision of this
document.
To run the LSI SCSI utility:
1. From the EFI Shell, run EFICnfg.efi to enter the LSI Logic SCSI Utility. The following
information is displayed on your monitor:
Intel’s EFI Configuration program ver 0.6 Serial # Controller description
1. OnBoard Function0 Usb Universal Host Controller
2. OnBoard Function1 Usb Universal Host Controller
To select the adapter the user wishes to configure, use the arrow keys to highlight the adapter then
press <Enter>. The screen clears and a message reading “Scanning for devices…” appears.
Intel® SR870BN4 Server System Product Guide 61
Page 62
Figure 15 shows the adapter properties and its different configuration settings.
LSI Logic MPT SCSI Setup Utility Version v1.00.04.00
The following list shows the available options for each setting category.
Driver Support Enabled BIOS & OS or Enabled OS Only or Enabled BIOS
only or Disabled
Host SCSI ID 0 to 15
SCSI Bus Scan Order Low to High (0..Max) or High to Low (Max..0)
Spin up delay (seconds) 1 to 15
Secondary Cluster Server No or Yes
Termination Auto
The <Restore Defaults> option allows the user to restore the default configuration of the SCSI
adapter.
The <Device Properties> option takes the user to the Device Properties menu shown in Figure 16.
62 Intel® SR870BN4 Server System Product Guide
Page 63
LSI Logic MPT SCSI Setup Utility Version v1.00.04.00
Device Properties
SCSIDevice IdentifierMB/ MT/ Data Scan Scan Luns Disconnect SCSI Queue
IDSec Sec Width ID >0Timeout Tags
The Device Properties Menu shows options of devices attached to the adapter. It is a large menu
and requires the use of the arrow keys to move fully to the left and fully down to see all
configuration options. There are “slide bars” (not shown above) to the right and on the bottom to
help define your location in the menu. The following list shows the available options for each
setting category:
MB/Sec 320
MT/Sec 0 or 5, 10, 20, 40, 80, 160
Data Width 16 or 8
Scan ID Yes or No
Scan Luns >0 Yes or No
Disconnect On or Off
SCSI Timeout <10>
Queue Tags On or Off
Format, Verify, and Restore Defaults are all functions. They are located on the far left of the menu,
but are shown below the other configuration options in the figure above. Format and Verify takes
the user to another menu, see Figure 17 and Figure 18 below. These menus give appropriate
warnings and allows the user the option of continuing with the function or canceling. Restore
Defaults function do not take the user to another menu and does not give the user the option to
cancel. If the user makes changes and then accidentally select the Restore Defaults function, all
changes will be discarded.
Intel® SR870BN4 Server System Product Guide 63
Page 64
LSI Logic MPT SCSI Setup Utility Version v1.00.04.00
Format
SCSIDevice Identifier
ID
12Maxtor
Status
WARNING! Format will change the sector size to 512 bytes. Format will
Permanently erase all data on this device. Format may take hours to complete
and cannot be stopped. Hit ENTER to continue or any other key to cancel.
Figure 19. Adapter and/or Device Properties Exit Menu
When exiting the Adapter Properties Menu, if any changes have been made, the Exit Menu appears
giving the following three options. Cancel Exit, Save Changes then exit, or Discard changes
and exit.
LSI Logic MPT SCSI Setup Utility Version v1.00.04.00
When exiting the LSI Logic MPT SCSI Setup Utility, if any changes have been made, the Exit
Menu appears giving the user these options. Cancel Exit, Save Changes then exit, or Discard
changes and exit. The above menu shows the exit menu that appears if no changes have been made
to the Setup Utility.
After exiting, the user is returned to the EFI Shell prompt.
66 Intel® SR870BN4 Server System Product Guide
Page 67
The SR870BN4 Resource CD
The SR870BN4 Resource CD has the following contents:
Utilities:
System Maintenance Utility (SMU)
Save and Restore System Configuration Utility
One-Boot Flash Update (OFU) Utility
EFI Platform Diagnostics
EFI Configuration Tool
Ramdriver
The Product Guide
Adobe† Acrobat† Reader
The Resource CD comes with a menu driven program that can be used for the following:
Create removable media device containing utilities, service partition and diagnostics.
Install EFI Service Partition. The EFI service partition provides the ability to remotely access
SR870BN4 via modem or LAN for the purpose of executing configuration/setup utilities and
diagnostics.
Run SR870BN4 EFI based utilities.
Running Software Utilities Directly from the Resource CD
The following procedure allows the user to run the software utilities directly from the SR870BN4
Resource CD.
1. Insert the System Resource CD into the server’s CD-ROM drive before booting to EFI Shell.
2. Boot the system into EFI Shell, the EFI CD Menu program launches automatically. If the EFI
CD Menu program does not launch in the EFI Shell, mount and map to the CD drive and type
‘startup’ and press <Enter> to launch the EFI CD Menu.
3. Move the curser over to the Utilities and select the utility the user wants to run.
Upgrading the Firmware
Use the Firmware Update Utility to upgrade the firmware. This utility is an EFI application
program that updates the following server management controllers:
You can run the utility interactively by providing commands through the EFI shell, or the user can
run it in non-interactive mode by supplying the command with any options. For information on the
command-line options, see Table 17 on page 69.
Running the Firmware Update Utility
The following procedure shows how to use the interactive method to upgrade the firmware with the
Firmware Update Utility.
1. Boot to the EFI Shell. For information on how to boot the server, refer to “The Extensible
Firmware Interface (EFI) Boot Manager” on page 44.
Intel® SR870BN4 Server System Product Guide 67
Page 68
2. Copy the following files to a removable media device. The current release of these files is
available through IBL. Download the following files from IBL. (If the user does not have
access to IBL, contact your Intel Sales Representative.)
Where <name> represents the hex image for the controller being
updated. For example, the files lnbmc11.hex and lnbmc11.txt
represent the firmware and release note files, respectively for
BMC release 11. Make a note of the name of the HEX file as you
will need it later.
3. You can update the firmware either by the ‘FWUpdate’ utility’s command line interface or
through the GUI interface.
4. To run the Firmware Update Utility through the Command line Interface:
a. Invoke the utility by entering the following command:
fwupdate [HEX File Name] [Options]
b. To view the command-line help, type:
fwupdate /h
or
fwupdate /?
c. To update boot block as well as operational block of the firmware from the command line
interface:
fwupdate [HEX File Name] /upload /bootena
Note: An external jumper may be required in order to enable the boot block to be
uploaded.
d. To update the operational block only from the command line interface:
fwupdate [HEX File Name] /upload
Note: Check the FW release notes for the FW release that the user is trying to update. It
may require updating both boot code and operational code.
e. Go to step 8 and continue.
5. To run the Firmware Update Utility through the GUI interface:
a. Invoke the utility by entering the following command:
fwupdate <name>.hex
b. In the command, <name>.hex is the file the user copied earlier in Step 2.
c. Wait for the HEX file to load and the utility to display its menu items.
d. Use the arrow keys to select the Update Flash menu item.
e. Press the <Enter> key.
f. The utility asks the user to update the boot code and/or the operational code. Check the
firmware release notes for the release that the user is trying to update for information on
what the user needs to update. The update might require the user to update both boot code
and operational code or it might require the user to just update the operational code.
68 Intel® SR870BN4 Server System Product Guide
Page 69
g. After the update completes successfully, the utility verifies the update by reading back the
programmed code and comparing it to the HEX file.
h. Select the File menu tab and choose Exit to exit the utility.
6. If the user needs to update the firmware for additional controllers, repeat the above steps for
each controller.
7. Power down the system by pressing and holding the power button on the front control panel.
8. Disconnect the AC power cords from the system and wait 60 seconds.
9. Connect the AC power cords and power up the system by pressing the power button.
Firmware Update Utility Command-line Options
Table 17 describes the command-line options for the Firmware Update Utility.
Table 17. Firmware Update Utility Command-line Options and Parameters
Option or
Parameter
FWUpdate The name of the utility.
[Hex_File_Name] The name of the input hex file used for the update/verification. The file path can be
/h Or /? Display command line help.
/upload Upload the FW flash with the operational code contained in the hex file. The Platform
/norestore When used in conjunction with /upload, the utility does not restore the user
/noverify When used in conjunction with /upload, the utility does not compare the flash against
/ignorerevs When used in conjunction with /upload, the firmware version in the hex file is not
/nopc When used in conjunction with /upload, the platform check is disabled. Without this
/bootena When used in conjunction with /upload, the boot-block of the device is uploaded in
Description
specified with the file name. There is no default filename or extension.
Information Area (PIA) will also be uploaded, if it is present in the hex file. Upon
completion, the firmware is verified against the hex file to ensure the upload was
successful.
configuration settings after performing the update. Without this switch, the utility saves
the user configurations prior to updating the FW, and then restores the saved user
configuration settings after updating the FW.
the hex file after performing the update, as is usually done to verify a successful
update. When not used in conjunction with /upload, this switch has no effect.
checked. Without this switch, the utility only allows uploading a version of the firmware
that is greater than or equal to the version being replaced. When not used in
conjunction with /upload, this switch has no effect.
switch, the utility only allows uploading firmware that is intended for the target platform.
The target platform is determined by reading the BIOS ID of the system and compares
it against the Platform Name field in the boot code info block of the hex file. In the case
of the PIA, the target platform is determined from the Platform Group and Platform ID
fields of the PIA info block. When not used in conjunction with /upload, this switch has
no effect.
addition to the operational code and PIA if present in the hex file. NOTE: An external
jumper may be required in order to enable the boot block to be uploaded (a jumper is
not required for SR460AC4 platforms). On systems requiring the jumper, the boot
block upload fails if the jumper is not set, and an error is generated indicating that the
boot block could not be uploaded. However, the utility still attempts to upload the
operation code and PIA, if present in the hex file. This switch may only be used in
conjunction with /upload.
Intel® SR870BN4 Server System Product Guide 69
Page 70
/verify Verify the firmware. The utility compares the flash contents of boot code, operation
code, and PIA (if applicable), with that contained in the hex file.
/fwversion Display firmware version, for all supported devices in the system.
/infoblock Display device info block of input hex file.
/nopause Suppresses keyboard wait at end of transfer or on an error. This switch allows updates
to be performed in a batch style environment without requiring user interaction.
Upgrading the BIOS by Using IFlash64
The BIOS is implemented as firmware that resides in the processor board and I/O riser flash ROMs.
Use the EFI (Extensible Firmware Interface) based utility IFlash64.EFI to upgrade the BIOS.
✏ NOTES
Refer to information at the Intel Business Link (IBL) for the latest
information on upgrading the BIOS. If the user does not have access to the
IBL, contact your Intel Sales Representative.
After the user completes the Iflash64 BIOS update, the user must clear
CMOS. For information on how to clear CMOS, refer to “Clearing CMOS”
on page 72.
BIOS Upgrade Procedure
A BIOS upgrade procedure can be done using the latest available System Update Package (SUP)
for the SR870BN4 system. This package is available on IBL and is a script file that automatically
runs IFlash64 and other firmware update utilities as required. However, the user can also use the
IFlash64 utility to upgrade the BIOS following these steps:
1. Boot to the EFI Shell. For information on how to boot the server, refer to “The Extensible
Firmware Interface (EFI) Shell” on page 48.
2. Copy the utility
binary file contains the new BIOS. All firmware, BIOS, and utility updates are posted to the
Field Division Business Link (FDBL), which is maintained and accessible by Intel Customer
Support. When the user needs updates, your designated Field Engineer authorizes the user to
download files from the Intel Business Link (IBL). Refer to the update instructions provided
with each BIOS release for the most current instructions.
IFlash64.EFI and the binary input file to a removable media device. The
70 Intel® SR870BN4 Server System Product Guide
Page 71
3. Running the IFlash64 utility through the Command line Interface:
a. Invoke the utility by entering the following command:
IFlash64 [File Name] [Options]
b. To view the command-line help, type:
IFlash64 /h
or
IFlash64 /?
c. NOTE: For information on IFlash64 command-line options and parameters, refer to
Table 18.
d. To update System BIOS from the command line interface, type:
IFlash64 [File Name] /update
e. To verify System BIOS from the command line interface, type:
IFlash64 [File Name] /verify
f. Go to Step 4
4. Running the IFlash64 Utility through the GUI Interface:
a. Invoke the utility by entering the following command:
IFlash64
or
IFlash64 [File Name]
b. Use the arrow keys to browse through the menu and press the <Enter> key to select. A
brief description of the selected menu item is displayed in the Tip-View window, which is
displayed at the bottom of the screen.
c. To update System BIOS from the GUI interface, select "Update System BIOS".
d. To verify System BIOS from the GUI interface, select "Verify System BIOS".
5. Turn off the computer and follow the procedure to clear CMOS as described on “Clearing
CMOS” on page 72.
IFlash64 Utility Command-line Options
Table 18 lists the command-line options for the IFlash64 Utility.
Table 18. IFlash64 Utility Command-line Options and Parameters
Parameter Description
Iflash64 The name of the utility.
[Volume_File_Name] Name of the BIOS binary volume file used for the update. The file path can be
specified with the file name. There is no default file name.
/d Display header and FLASH areas information of volume file.
/f Load default values from CMOS on next boot.
/quiet Quiet or non-interactive mode. It displays only error messages and disables
prompting the user for input.
/reboot Reboot system after update.
/update Update system BIOS in non-interactive mode. Note that it only updates flash areas
that are different than the ones found in the input binary file. Use “/o” to override
this default operation.
/verify Verify current Flash with contents of input binary file in non-interactive mode.
/h Or /? Displays command line help.
Intel® SR870BN4 Server System Product Guide 71
Page 72
Clearing CMOS
WARNING
Make sure that the rack is anchored securely so it will not tilt forward
when the server chassis is extended. A crush hazard exists should the
rack tilt forward which could cause serious injury.
The user must clear CMOS after the user completes the IFlash64 BIOS update. Clearing CMOS
involves changing a jumper setting on the I/O riser card, restarting the server with the new jumper setting,
restoring the jumper setting to its original position, and restarting the server a final time.
To clear CMOS follow these steps:
(Clearing CMOS by DIP switch)
1. Power down the server by pressing and holding the power button on the front control panel.
The user might have to hold the power button down for several seconds.
2. Remove standby power from the server by unplugging both power cords from the system and
removing them from the server.
3. Remove the screw that secures the non-hot-plug I/O cover over the I/O riser card and slide the
cover off.
4. Remove the I/O riser card by following the procedure described in “Removing the I/O Riser
Card” on page 187.
5. Position switch #3 on the five-position DIP switch at location S8A1 to the ON position as
shown in Figure 137 on page 265.
6. Replace the I/O riser card by following the procedure described in “Replacing the I/O Riser
Card” on page 187.s
7. Reinstall the server’s power cords and plug them into the power source.
8. Power on the server by pressing the power button on the front control panel.
9. Wait for the message 'NVRAM cleared by jumper' to appear. When the options 'Hit <F1> to
load defaults or <F2> to run SETUP or <ESC> to continue, hit <F1> to load the defaults.
After the user clears CMOS, the switch setting must be restored to it’s “OFF” position and the
server restarted. Follow these steps to return the switch to the default position and reboot the
system.
1. Power down the system by pressing and holding the power button on the front control panel.
The user might have to hold down the power button for several seconds.
2. Remove standby power from the server by unplugging both the power cords from the power
source and removing them from the server.
3. Remove the I/O riser card by following the procedure described in “Removing the I/O Riser
Card on page 187.
4. Reposition jumper switch #3 on the 5-position switch at location S8A1 so that it is in the
“OFF” position. See Figure 137 on page 265 for the default position.
5. Replace the I/O riser card by following the procedure described in “Installing the I/O Riser
Card” on page 189.
6. Close and secure the rear part of the top cover.
7. Reinstall the power cords and plug them into the power source.
8. If the chassis is rack mounted, push the system back into the cabinet rack.
9. Power on the server by pressing and holding the power button on the front control panel.
72 Intel® SR870BN4 Server System Product Guide
Page 73
BIOS Recovery Mode
The BIOS Recovery Mode permits re-flashing the BIOS when the flash ROM has been corrupted.
The usual sequence of events for automatic recovery is:
1. Request recovery media by repeating a low-tone beep with POST code.
2. Insert recovery media and reset the system.
3. One beep indicates recovery media valid, and flash update started.
4. Approximately two minutes later, two beeps indicate flash update complete.
5. System automatically resets and starts the new BIOS.
The BIOS Recovery Mode, when using an LS240, is initiated using the following procedure:
1. Prior to attempting recovery for the first time, either use a previously formatted unused or a
blank LS-240 diskette.
2. Unzip the recovery image and copy the S870BN4A.REC file (S870BN4B.REC for Madison)
onto the LS-240 diskette. The file S870BN4A.rec should be the only file on the disk.
3. With the system switched off and AC power disconnected:
a. Place I/O riser toggle switch #1 to the ON position (S8A1) for forced BIOS recovery. For
toggle switch location, refer to “I/O Riser Card Settings” the on page 265.
b. Insert diskette in LS-240 drive.
c. Reconnect the AC power and switch server power on.
d. LS-240 diskette activity started.
e. One full beep (start load S870BN4A.REC from disk to memory).
f. Wait two minutes. No indication of LS-240 activity will be seen until two beeps are heard
that indicate the BIOS recovery has completed successfully.
g. Remove the LS-240 recovery diskette, switch system power off, and disconnect AC power.
h. Replace the I/O toggle switch #1 to the OFF position, reconnect AC power and switch the
system on per updated BIOS release notes (i.e. clear CMOS first time booting).
The BIOS Recovery Mode, when using a CD, is initiated using the following procedure:
1. Unzip the recovery image and burn the included .iso file to a blank CD. The file
S870BN4A.rec should be the only file on the disk.
2. With the system switched off and AC power disconnected:
a. Place I/O riser toggle switch #1 to the ON position (S8A1) for forced BIOS recovery. For
toggle switch location, refer to “I/O Riser Card Settings” on page 265.
b. Reconnect the AC power and switch server power on.
c. Quickly insert CD into DVD drive
d. LS-240 diskette activity should start.
e. There should be one full beep (start load SR870BN4A.REC from disk to memory).
f. Wait two minutes. No indication of LS-240 activity will be seen until two beeps are heard
that indicate the BIOS recovery has completed successfully.
g. Remove the LS-240 recovery diskette, switch system power off, and disconnect AC power.
Replace the I/O toggle switch #1 to the OFF position, reconnect AC power and switch the system
on per updated BIOS release notes (i.e., clear CMOS first-time booting).
Intel® SR870BN4 Server System Product Guide 73
Page 74
✏ NOTE
The system supports BIOS recovery using CD-ROM or DVD. The recovery
image should be copied to the CD in El Torito format.
Using the FRUSDR Load Utility
The Field Replacement Unit (FRU) and Sensor Data Record (SDR) Load Utility (FRUSDR.EFI) is
an Extensible Firmware Interface (EFI) program that updates or modifies the server management
subsystem’s product level FRU and SDR repository.
The user should run the FRUSDR Load Utility each time the user upgrades or replaces the
hardware in your server; excluding add-in boards, hard drives, and RAM. The utility programs the
sensors the server uses to monitor server management.
Using the FRUSDR Load Utility, the user can do the following:
Discover the product configuration based on instructions in a master configuration file.
Display the FRU information.
Update the non-volatile storage device associated with the baseboard management controller
(BMC) that holds the SDR and FRU information.
Generically handle FRU devices that might not be associated with the BMC.
Supply command lines and interactive input through the standard input device.
View and direct results to the standard output device.
Running the FRUSDR Load Utility
Follow these steps to run the FRUSDR Load Utility:
1. Boot to the EFI Shell. For information on how to boot the server, refer to “Booting the Server
from the Service Partition” on page 142
2. Copy the FRUSDR package to a removable media device or to the hard drive. The user can
find the FRUSDR package on the CDROM included in the Country Kit that shipped with the
server.
3. Load the Intelligent Platform Manager Interface (IPMI) driver by typing the following
command:
load ipmi.efi
✏ NOTE
The IPMI driver file name might change independently of the FRUSDR
Load Utility.
4. Run the utility by entering a frusdr command based on the following syntax:
frusdr [option] [/p]
The frusdr command accepts single options only. The user can accompany any option with the
/p switch to cause the output to pause between blocks of displayed output. For descriptions of
the FRUSDR Load Utility command-line options, see “FRUSDR Load Utility Command-line
Options,” below.
74 Intel® SR870BN4 Server System Product Guide
Page 75
✏ NOTE
The user can run the utility directly from the configuration software CDROM or from diskettes the user creates from the CD-ROM included in the
Country Kit shipped with the system. If the user chooses to run the
FRUSDR Load Utility from a diskette, the user must copy the utility from
the CD-ROM and follow the instructions in the included README.TXT
FRUSDR Load Utility Command-line Options
file.
5. Use the FRUSDR Load Utility to manage the server management subsystem’s product level
FRU and SDR repository.
6. Reboot the system by powering off and powering on the server. The reboot operation is
necessary because the firmware must reload to properly initialize the sensors after
programming and thus effect the changes the user has made to the FRU and SDR repository.
/? or /H Displays usage information
/D SDR Displays the sensor data records
/D FRU (Address) Displays the FRU located at a given address
/CFG (filename.cfg) Uses the specified custom configuration file
/P Pause the display between blocks of data to prevent the displayed data from scrolling
off the screen
The /D FRU option displays FRU information from a device at the specified address allowing any
FRU to be displayed. The parameters following the /D FRU are the same values as the FRU file
header addresses, namely: NVS_TYPE, DEVICE_ID, DEV_CNTR (aka Device Controller),
NVS_LUN, DEV_BUS and DEV_ADDRESS.
Intel® SR870BN4 Server System Product Guide 75
Page 76
There are two addressing modes for FRU devices: Indirect and Direct.
Indirect: FRUSDR /D FRU [NVS_TYPE | DEV_CNTR | NVS_LUN | DEVICE_ID]
NVS_TYPE The type of EEPROM; Either AT24C02, DS1624S, or IMBDEVICE. If not specified,
IMBDEVICE is assumed.
DEV_CNTR The controller’s IPMB device address; defaults to ‘C20’. Must be prefixed by ‘C’ and must be
3 characters in length, including the ‘C’.
NVS_LUN The Logical Unit Number. Must be prefixed by ‘L’ and defaults to ‘L0’. LUN value may be
any number between 0 – 3, though any value except the default is uncommon.
DEVICE_ID The Device ID; defaults to 00. Used only if NVS_TYPE is IMBDEVICE, (i.e. Indirect
Addressing).
DEV_BUS The device’s bus number; it has no default. Required if NVS_TYPE is not IMBDEVICE (i.e.
Direct Addressing). It has no default value.
DEV_ADDR The device’s address; it has no default. Required if NVS_TYPE is not IMBDEVICE (i.e.
Direct Addressing). It has no default value.
All numbers entered for DEV_CNTR, DEV_ID, DEV_BUS, and DEV_ADDR are interpreted as
hexadecimal values, and must be in the range 0 – FF; the NVS_LUN must be 0, 1, 2 or 3. The
command line arguments may be specified in any order and if one of the arguments is not specified,
then its default value is used, if it has one. If DEV_BUS and DEV_ADDR are specified, i.e. Direct
Addressing is used, then DEV_BUS is assumed to precede DEV_ADDR. If no arguments are
specified for [Address] then the BMC FRU is displayed.
Example using Indirect addressing:
FRUSDR /D FRU IMBDEVICE CC0 L0 0
The utility interprets this as DEV_CNTR = 0xC0, NVS_LUN = 0, DEV_ID = 0;
Because many of these values are the default values, the same result could be accomplished with
the following:
FRUSDR /D FRU CC0 0
Example using Direct addressing:
FRUSDR /D FRU AT24C02 C20 L0 9 AA
The utility interprets this as DEV_CNTR = 0x20, NVS_LUN = 0, DEV_BUS = 0x09,
DEV_ADDR = 0xAA.
Because many of the values are the default values, the same result could be accomplished with the
following:
FRUSDR /D FRU AT24C02 9 AA
Whenever more than one number is listed on the command line, the utility assumes the numbers are
DEV_BUS and DEV_ADDR in that order. So the following command line:
FRUSDR /D FRU CC0 L0 5 AT24C02 A9
Would be interpreted as DEV_CNTR = 0xC0, NVS_LUN = 0, DEV_BUS 0x05, DEV_ADDR =
0xA9. And since NVS_TYPE is not IMBDEVICE, Direct addressing would be used.
76 Intel® SR870BN4 Server System Product Guide
Page 77
The /CFG command line options uses the specified Configuration file. The configuration file may
be used to load multiple FRU and SDR files. In the configuration file, each FRU and SDR file
name must be called out. Additionally, each FRU area and field to be programmed must also be
specified. The configuration file may be used to prompt or request information from the user, and
to inquire from the user which FRU areas to program. For more information on the configuration
file see page 82.
The /P command may be used with all other commands. It causes the data being displayed on the
screen to pause after a pre-determined amount is written, so that the displayed data does not scroll
off the screen. In some cases, if there is not enough data being displayed to warrant a pause, then
the pause command is ignored.
Command Line Precedence
Command line precedence simply means, the first command found is operated on, followed by the
next command, and so on. Commands can be broken up into two categories: Flag commands and
action commands. The only flag command is the Pause (/P) flag command. This flag is then used
by the action commands. The action commands are: /?, /D FRU, /D SDR, and /CFG.
The pause command only affects the execution of certain action commands. For example, the
Pause flag command only provides additional information when used with the help and display
FRU and SDR action commands.
If an action command does not use the Pause Flag, no error is displayed. It was felt that this is a
minor error and should not prevent the utility from functioning. If more than one action command
is listed on the command line, then an error is displayed and the utility exits. The error that is
displayed depends on what the command was.
Displays Usage Information
When the utility is invoked with the /? or /H command line arguments, the following message is
displayed on your screen:
FRUSDR Load Utility, Version 2.0
Copyright (c) 2002 Intel Corporation, All Rights Reserved
_________________________________________________________________________
Usage: FRUSDR
/? or /H Displays detailed usage information.
/D SDR Displays Sensor Data Records.
/D FRU [Address] Displays the FRU located at a given Address.
/CFG [CFG File] Uses the specified custom Configuration file.
/P Pauses the display between blocks of data.
This utility is used to program, compare, or display FRU and/or SDR information. It must be run
on an Intel Itanium 2 system executing NSHELL under the EFI environment. Upon completing the
programming of the FRU and/or SDR areas, the server should be rebooted.
Display the FRU located at a given Address
Usage: FRUSDR /D FRU [Address]
The Addressing mode may be 'Indirect' or 'Direct'
Indirect: FRUSDR /D FRU [NVS_TYPE | DEV_CNTR | NVS_LUN | DEV_ID]
Intel® SR870BN4 Server System Product Guide 77
Page 78
Direct: FRUSDR /D FRU [NVS_TYPE | DEV_CNTR | NVS_LUN | DEV_BUS | DEV_ADDR]
NVS_TYPE - The type of EEPROM, { AT24C02, DS1624S, or IMBDEVICE (default) }
DEV_CNTR - Controller's Address; defaults to 'C20'. Must be prefixed by 'C'
NVS_LUN - The LUN; defaults to 'L00'. Must be prefixed by 'L'
DEV_ID - The Device ID; defaults to 00. Used only if NVS_TYPE is IMBDEVICE
DEV_BUS - The Device's bus; has no default value
DEV_ADDR - The Device's address; has no default value
The DEV_BUS and DEV_ADDR are required only if NVS_TYPE is not IMBDEVICE
If DEV_CNTR is specified, it must be 3 characters in length, including the 'C'
All numbers entered for DEV_CNTR, DEV_ID, DEV_BUS, and DEV_ADDR are interpreted as
hexadecimal values, in the range 0 - FF; LUN must be 0, 1, 2 or 3.
The command line arguments may be specified in any order, and if one of the arguments is not
specified then its default value is used; if it has one. If no arguments are specified for [Address]
then the BMC FRU is displayed.
Use a specified custom configuration file.
Usage: FRUSDR /CFG [Configuration file name].
If not specified, the name of the CFG file defaults to 'MASTER.CFG'. The configuration file may
be used to load multiple FRU and SDR files. In the configuration file, each FRU and SDR file
name must be called out.
Additionally, each FRU area and field to be programmed must also be specified. The configuration
file may be used to prompt or request information from the user, and to inquire from the user which
FRU areas to program.
Displays Given Area
When the utility is invoked with the /d FRU or /d SDR command line argument, the indicated area
is displayed. If the given display function fails because of an inability to parse the data present or
hardware failure the utility displays an error message.
Displaying FRU Area
The FRU area is displayed in ASCII format when the field is ASCII or as a number when the field
is a number. The FRU field strings are specified in the IPMI Platform Management FRU Information Storage Definition. Each FRU area displayed is headed with the FRU area designated
name. Each FRU field has a field name header, followed by the field in ASCII or as a number.
The Internal Use area is displayed in hex format, 16 bytes per line. The Board, Chassis and Product
FRU areas are ended with an END OF FIELDS CODE, which indicate there is no more data in
this area.
Example:
FRU IMBDEVICE on Controller 20h, LUN 00h, Device ID 00h
Display Header Area
Common Header Area (Version 1, Length 8)
Internal Area Offset = 01h
Chassis Area Offset = 0Ah
78 Intel® SR870BN4 Server System Product Guide
Page 79
Board Area Offset = 0Eh
Product Area Offset = 16h
Multi-Record Offset = 00h
Pad = 00h
Checksum = D0h
Displaying Internal Use Area
Internal Information Area (Version 0, Length 72)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 01 00
Displaying Chassis Area
Chassis Information Area (Version 1, Length 32)
Chassis Type = 11h
Part Number (ASCII) = SBALMADSTD02PP
Serial Number (ASCII) = A05884265
END OF FIELDS CODE
Displaying Board Area
Board Information Area (Version 1, Length 64)
Unicode Country Base = 00h
Manufacturing Time (mins) = 733803
Manufacturer Name (ASCII) = Intel
Product Name (ASCII) = B440FX DP
Serial Number (ASCII) = N03121530
Part Number (ASCII) = 664653-001
Mftr FRU File ID (ASCII) = 0123
END OF FIELDS CODE
Displaying Product Area
Product Information Area (Version 1, Length 80)
Unicode Country Base = 00h
Manufacturer Name (ASCII) = Intel
Product Name (ASCII) = B440FX DPServer
Part Number (ASCII) = SBALMADSTD02PP
Product Version (ASCII) =
Serial Number (ASCII) = A05884265
Asset Tag (ASCII) =
Mftr FRU File ID (ASCII) = 0123
END OF FIELDS CODE
Intel® SR870BN4 Server System Product Guide 79
Page 80
Displaying SDR Area
The SDR non-volatile storage area is displayed in the following hex format. A Sensor Record
Number X header separates the data, where X is the number of that sensor record in the SDR area.
The next line after the header is the sensor record data in hex format delineated by spaces. Each
line holds up to 16 bytes. The data on each line is then followed by the same data in ASCII format,
non/printable characters (ch < 32 || ch > 126) are substituted by a ‘.’.
The utility is normally invoked with the command line parameter of /CFG [“Filename”] where the
“filename” can be any accepted character filename string. This feature loads the indicated CFG
file. The utility uses the entries in the configuration file to probe the hardware and to select the
proper Sensor Data Records to be programmed into non-volatile storage. If the argument /CFG is
used without a filename, then the default file ‘MASTER.CFG’ is used, if it exists.
Loads Specified FRU File
The normal method of loading one or more FRU files is through the use of a configuration file.
Each FRU file name is specified using the FRUNAME configuration command. The first time a
FRU file is programmed, all areas in the FRU file need to be written, and this initialization should
be done in manufacturing. The FRUSDR utility does not support first time programming of
FRU areas.
Once the FRU file has been initially programmed, then the FRUSDR utility may be used to update
specific FRU areas and fields. The user may not change the size of any FRU area from the size
defined in the original FRU Header. Through the use of a configuration file, each area of the FRU
may selectively be programmed. The FRU information written to the non-volatile storage device is
verified after programming and an appropriate message is displayed. For more detailed information
on creating and using a configuration file see “Configuration File” on page 82.
In the FRU file header there exists a pad byte that may be any one-byte value without directly
causing an error, this pad byte is used in calculating the header checksum. If the header checksum
is incorrect, then a message is displayed so indicating.
80 Intel® SR870BN4 Server System Product Guide
Page 81
Comparing the FRU File
The configuration “COMPARE” command allows the validation of information to what exists in
the non-volatile storage device without programming that information. The “COMPARE”
command is used in a configuration file, and placed on the same line after the FRU name to be
compared.
The compare functionality does a byte-by-byte comparison of the non-volatile storage device and
what was to be programmed. The internal use area is never compared; this utility considers all
bytes of the internal use area to be dynamic and subject to change at will by the firmware. In the
board area, the manufacturing date and time, and the board area checksum are also not compared,
although the rest of the board area bytes are compared.
Loads Specified SDR File
The normal method of loading an SDR file is through the use of a configuration file. Typically all
possible Sensor Data Records exist in one master SDR file. Each SDR file name is specified after
the SDRNAME configuration command. Through the configuration file, tags may be use to
selectively chose which records are to be programmed using tags. The maximum allowable length
of any Sensor Data Record is 64 bytes. Any larger records are flagged as an error.
Example:
Writing SDR Record #36
Reading SDR Repository
SDR file was successfully written!
Programming complete, reboot server for normal operation
Comparing the SDR File
The configuration “COMPARE” allows the comparing of SDR information to what is in the SDR
Repository without programming that information. The “COMPARE” command is used in a
configuration file and placed on the same line after the SDR name to be compared. The compare
feature does a byte-by-byte comparison of the non-volatile storage device and what was to be
programmed. No checksum is used. During a comparison, the first two bytes of each Sensor Data
Record are ignored, because when the repository was programmed, the first two SDR bytes were
modified by the BMC and a pointer inserted.
Functional Operation
Display Utility Title and Version
The utility displays as its title during development:
FRUSDR Load Utility, Version 2.0 Build X where ‘X’ is the build number for the
particular version of the utility.
Upon final release, the banner is modified and the build status removed, therefore:
FRU & SDR Load Utility, EFI Version 2.0, Build 4
Will become the production release:
FRU & SDR Load Utility, EFI Version 2.0
Intel® SR870BN4 Server System Product Guide 81
Page 82
Configuration File
A CFG file may be used by the utility. The configuration file is ASCII text and editable. The file
is parsed, then pertinent information is stored internally by the utility. The information obtained
from the configuration file is used to direct the execution path of the utility and to establish a
configuration for the product. The configuration file allows the user to override values contained in
an associated FRU file; it does not allow the user to add areas to a FRU file. One should think of
the FRU in the non-volatile storage device as containing the default values. If the user decides to
leave out FRU areas or fields during programming, then the information already contained in those
FRU areas or fields on the Server will remain.
The utility executes commands formed by the strings present in the configuration file. These
commands cause the utility to perform various tasks needed to ultimately load the proper Sensor
Data Records into the non-volatile storage of the BMC and possibly generic FRU devices. Some of
the commands are user interactive and require a choice to be made by the user.
For detailed information on the configuration file format, see the “FRU and SDR Load Utility Plus
Configuration File Format EPS.”
Probing Product Configuration
Using the information in the configuration file, the utility can probe the product configuration. For
more information see page 82 on the configuration file format of the “FRU and SDR Load Utility
Plus Configuration File Format EPS.”
Checking the FRU Data Integrity
The utility needs the FRU Common Header offsets to be correct. The Utility checks the Common
Header Area in each NVS device against the FRU file, and also runs a checksum on it. If the
Common Header Area in the FRU file is correct and matches what is in the NVS device, then the
information is programmed. An incorrect Common Header means the FRU area is corrupted or has
never been initialized.
If the Internal Use Area of the BMC is loaded from the FRU file, then the BMC will be cold reset.
This is so the BMC re-initializes its internal copy of the Internal Use area from the FRU. The effect
of re-initializing the Internal Use Area is that both the SDR table and the SEL (System Event Log)
table are cleared. All information in both areas is lost and the SDRs must be reprogrammed.
Updating the SDR Non-Volatile Storage Area
After the utility validates the header area of the supplied SDR file, then it updates the SDR
repository area. Before programming begins, the utility clears the SDR repository area. When
loading an SDR file from a Configuration File, the utility filters all tagged Sensor Data Records
using a list of tags determined by the user, which represent the product’s configuration.
Non-tagged Sensor Data Records are automatically programmed.
Updating the FRU Non-Volatile Storage Area
After the system configuration is determined, a typical configuration file updates the FRU
non-volatile storage area. It will first verify the Common Header area and checksum from the
specified FRU file with what is programmed in the FRU non-volatile storage device. If specified,
the Internal Use Area is then read out of the specified FRU file and is programmed into the
82 Intel® SR870BN4 Server System Product Guide
Page 83
non-volatile storage device. Then Chassis, Board, and Product areas are read out of the specified
FRU file and programmed into the non-volatile storage device. Lastly the Multi-Record Area is
read out of the specified FRU file, and then the area is programmed into the FRU non-volatile
storage device.
Cleanup and Exit
Finally, if any update was successfully performed, a single message is displayed and the
utility exits.
If the utility fails, then it exits with an error message and exit code. See the “FRU and SDR Load
Utility Plus Configuration File Format EPS” for a list of possible exit codes and error messages.
System Maintenance Utility
The System Maintenance Utility is an EFI-based program that provides the ability to view or
modify the server management firmware configuration, which is maintained by the BMC. The
executable program for the SMU is smu.efi.
The SMU lets the user:
Configure serial/modem channels for remote server management over a modem or direct serial
connection.
Configure LAN channels for remote server management over the network.
Configure users and associated passwords for channel access. Users and channels can be
assigned privilege levels to further define the access levels.
Configure platform events to define the actions that should take place when specific events
occur.
Configure serial over LAN and terminal mode capabilities.
Configure the power restore policy for the server.
View, save and clear the BMC System Event Log.
View and save the BMC Sensor Data Records.
View and save the Field Replaceable Unit records.
The SMU core components are installed as part of the service partition software installation process
and the remote SMU application is part of the Intel
are copied to a directory specified during that installation process. It is also possible to run the
local SMU application from a CD without installing a service partition.
®
Server Management installation. SMU files
The SMU software consists of a user interface and core components. The user interface
components present the user interface, gather user input, and send input to the core components.
The core components interpret data and perform necessary actions to the hardware. The core
components also maintain the state of the application and determine the screens to be shown.
Specific state information is stored in the data that is exchanged between the user interface and core
components.
The core components of the SMU are the same for the local and remote applications. If the SMU is
run locally, the user interface component will be an EFI application that uses the Portable
Embedded GUI (PEG) graphics library to present the user interface. When running remotely, the
Intel® SR870BN4 Server System Product Guide 83
Page 84
user interface component will be a Java application. Running the remote SMU requires the use of
Intel Server Management.
NOTE
The local SMU application is available only in English.
Remote Keyboard Navigation
The remote SMU application requires a pointing device for operation; it does not support
accelerator keys. Other keys work as described in Table 19.
Table 19. Keyboard Support for Remote SMU Client
Key Function
<Enter>
<Tab>
<Shift><Tab>
Pressing <Enter> when focus is on a button causes the action associated with that button
to occur.
Moves focus to the next control in the tab order in the primary information pane.
Moves focus to the previous control in the tab order.
Local Keyboard Navigation
The local SMU application provides keyboard support as follows:
Table 20. Keyboard Support for Local SMU Client
Key Function
<Enter>
<Tab>
<Up arrow>
<Down arrow>
<Right
arrow>
<Left arrow>
<F5> key
<F6> key
<F7> key
<F8> key
<F10> key
<ESC> key
If the cursor is in an edit box, the <Enter> key moves the cursor to the next selectable
control in the currently active pane. When the focus is on a task menu item, a task button, a
radio button, or a check box, pressing <Enter> selects the control. If the focus is on a
single-select control (combo box), pressing <Enter> has no effect.
Moves focus to the next control in the tab order in the primary information pane.
Moves the cursor to the previous selectable control in the currently active pane.
Moves the cursor to the next selectable control in the currently active pane. (Same as the
<Tab> key.)
Moves the cursor to the next selectable control in the currently active pane. (Same as the
<Tab> key.)
Moves the cursor to the previous selectable control in the currently active pane. (Same as
the <UP arrow> key.)
If a horizontal scroll bar is in the active pane, pressing <F5> scrolls the display left.
If a horizontal scroll bar is in the active pane, pressing <F6> scrolls the display right.
If a vertical scroll bar is in the active pane, pressing <F7> scrolls the display up.
If a vertical scroll bar is in the active pane, pressing <F8> scrolls the display down.
Toggles the focus between the task pane and the primary information pane.
Displays the Exit dialog.
84 Intel® SR870BN4 Server System Product Guide
Page 85
The following are true when using the above keys while running the local SMU application:
For single-select controls (combo boxes), the <up arrow> and <down arrow> keys can be
used to move through the items in the list. To move to a different control, the <Tab>, <left
arrow>, or <right arrow> keys are used.
For a set of grouped radio buttons from which only one can be selected, the <up arrow>,
<down arrow>, <left arrow>, and <right arrow> keys can be used to move between buttons in the group. To move to a different control, the <Tab> key is used.
For edit box controls, the <left arrow> and <right arrow> keys can be used to move
the cursor within the edit box. To move to a different control, the <Tab>, <Enter>, <up arrow>, or <down arrow> key are used.
About Box Information
The SMU includes an “About” item in the task pane when the task list is displayed. When
“About” is selected, a dialog box is displayed showing information about the SMU application
version. The information displayed consists of a set of four numbers, defined as follows:
The major feature release number
The minor platform or maintenance release number
The variant, used for things like different operating systems or languages
The build number
See the example below.
Intel® SR870BN4 Server System Product Guide 85
Figure 21. SMU Application About Box
Page 86
The About box contains an Advanced button that can be used to show version information for
components related to the SMU application. See the example below.
Figure 22. SMU Application About Box (Advanced button selected)
Server Discovery
The remote SMU application requires that the Intel Server Management software be installed on the
client system. When the ISM software is run, it performs a discovery of all servers that support
tools available within ISM. The discovered servers are displayed in the ISM Console. By clicking
on a server name in the table, a list of tools supported on that server is displayed. The SMU is
contained in the set of tools listed under the heading “Reboot to Service Partition”.
Remote SMU Application
The path used to connect to a target server is defined by the ISM software, based on information it
has about each server. After a LAN connection is established between the remote SMU application
and SMU core components on the server, the application and the core components set up a socket
connection to communicate through.
The sequence of steps that occur when starting the remote SMU application is listed below. These
steps occur under the control of the ISM software, not the SMU software, and all errors are handled
by the ISM software.
1. In the ISM Console software, click on Reboot to Service Partition under the list of
tools for a server shown.
2. Enter the username and password for an out-of-band connection on the Service Partition
Utilities screen.
3. Click Login.
86 Intel® SR870BN4 Server System Product Guide
Page 87
4. When the server has been successfully rebooted to the service partition software, the supported
service partition utilities are displayed, as shown below. Click on System Maintenance Utility to launch the SMU application. ISM passes connection information to the SMU so
the SMU can communicate with the target server. Up to this point, all errors are handled by the
ISM software, not the SMU.
Figure 23. Service Partition Utilities
The remote SMU application attempts to establish a socket connection to the server and uses the
Service Partition Utilities services to execute the server-side SMU core components. If a
connection is established, the application sends information to the SMU core components to request
a session. If the connection fails, a dialog box is displayed to indicate an error condition. In the
event of an error, the user can attempt to restart the SMU from the ISM console.
After the session with the SMU core components is established, a version check is made to
determine if the remote SMU application is able to communicate with the SMU core components
on the server. If the versions do not match, an error message is displayed, the SMU application is
closed, and control is returned to the Service Partition Utilities application.
Intel® SR870BN4 Server System Product Guide 87
Page 88
After the session between the SMU application and the core components is established, the window
below is displayed. The primary information pane at the right directs the user to select an activity
from the task pane at the left.
88 Intel® SR870BN4 Server System Product Guide
Figure 24. SMU Home
Page 89
Local SMU Application
The local SMU application and the core components exchange XML documents using a procedural
interface. There is no socket connection between the application and the core components.
The local SMU application can be run either from the system Resource CD or, if the SMU software
has been installed locally, from the directory where it was installed on the system partition. The
software can be run from a CD, regardless of whether it has been installed locally.
Running from CD
The target server must have a CD drive (EFI currently supports only CDs that contain information
in the “El Torito” format). No network connection is required.
The following sequence of steps is followed to start the SMU locally (assuming the system
Resource CD is being used):
1. Insert the system Resource CD into the CD drive on the target server and boot the server to the
EFI shell. The Resource CD menu program begins running automatically and displays a splash
screen followed by the main menu.
2. Use the arrow keys to move to the Utilities menu item. Press the <Enter> key.
3. Use the down arrow key to highlight the System Maintenance Utility menu item. Press the
<Enter> key to start the local SMU application.
Running from the System Partition
To run the SMU application from a service partition on which it has been installed, follow the steps
below:
1. If an EFI shell prompt is available on the local console and the files on the system partition can
be accessed, skip to step three.
2. Reset the server and boot to the EFI shell.
3. Locate the file system (e.g. fs0:, fs1:) that contains the service partition software and change
directory to \efi\service\smu.
4. Run smu.efi.
Intel® SR870BN4 Server System Product Guide 89
Page 90
Shutdown SMU Application
Exit either the local or remote SMU application by clicking on the Exit item in the task pane or by
clicking the Close button in the upper right hand corner of the container. A user can also use the
Close option in the system menu of either container. An exit operation can be started at any time
(unless the application is blocked while it waits for a response from the server). During the exit
process, the following steps occur:
1. The application sends a message to the SMU core components asking to end the SMU session.
2. The SMU core components send a message to the application asking for user confirmation of
the exit request. This message is displayed as a dialog box with an OK button and a Cancel
button.
3. Clicking the OK button causes the SMU application to send another message to the server to
confirm the exit request. If Cancel is clicked, the request to close is canceled.
4. A final message is sent to the application from the server before the application shuts down.
When the local SMU application is used, it exits to the EFI shell. When the remote SMU
application is used, control is returned to the Service Partition Utilities application.
Server Management Configuration Task
The server management configuration task appears in the task pane of the SMU. This task allows
the user to configure server management settings maintained by the Baseboard Management
Controller. The server management configuration task supports configuring of the following,
which are displayed as sub-tasks:
LAN Channel
Users
Platform Event Filtering (PEF)
Serial/Modem Channel
Power Settings
Upon selecting one of the above sub-tasks, a screen is displayed that contains some or all of the
configuration items that pertain to the selected sub-task. The data that is initially displayed is read
from the server management controller of the server. You can update the settings and save them
back to the server.
Sub-tasks can be made up of one or more screens, depending on the server management
configuration settings that are enabled. Buttons that are common to the server management
configuration tasks are described in Table 21.
Table 21. Common Buttons for Configuration Management Sub-tasks
Button Description
Save
Edit
90 Intel® SR870BN4 Server System Product Guide
Causes the current values of the settings in the current sub-task to be
stored in non-volatile memory on the server.
Causes a screen to be displayed that allows settings related to a single
entry in a table to be changed.
Page 91
LAN Channel Configuration Sub-task
The LAN channel configuration sub-task allows settings related to the LAN channel to be
modified. The initial screen for configuring the LAN channel is shown in the figure below. The
configuration settings are described below the figure.
Figure 25. LAN Channel Configuration
After completing this screen, click Next to move to the next screen to continue this sub-task.
Default LAN Configuration Settings Set by the SMU
The SMU automatically configures some server management firmware settings. These are not
displayed on the screen above, but are listed below. Before these settings are set by the SMU, the
user must click through each LAN configuration screen by clicking the Next button until the Save button on the final LAN configuration screen is reached.
Gratuitous ARPs may be enabled: This setting allows the BMC to generate gratuitous ARPs,
which provide a mechanism for IP devices to locate the hardware addresses of other devices on
the local network. If the server has a valid IP address and the LAN channel is enabled for
messaging (the access mode is not set to Disabled) or alerting, then gratuitous ARPs are
enabled.
Authentication enables are enabled: These bits define what types of authentication are enabled
to authenticate messages sent to the BMC by users of different privilege levels. The SMU
enables authentication of type straight password, MD2, MD5, and none.
User-level authentication is disabled: The SMU disables user-level authentication so that if a
user is attached with a privilege level of User, no authentication is done on messages sent to or
from the BMC. This improves the session performance.
Intel® SR870BN4 Server System Product Guide 91
Page 92
Access Mode
This drop-down box configures the access mode for the LAN channel. The available options are:
Always Available: The channel is dedicated to communication with the BMC and is available
during all system states (powered-down, powered-up, pre-boot, sleep, run-time, etc.).
Disabled: The channel is not allowed to communicate with the BMC.
Privilege Level Limit
This drop-down box determines the maximum privilege level at which communication on the
channel can take place. It is a global privilege level that takes precedence over user privilege
levels. For example, if a channel privilege level is set to the user level then only user-level
commands can be executed, regardless of the user privilege level.
The meanings of the different privilege levels are described below:
Callback: Only commands needed to initiate a callback session are allowed. Although ISM
software does not support callback as a connection mechanism, it is still a valid privilege level
because it defines a set of BMC commands that can be executed by a user.
User: Only “benign” commands are allowed. These are primarily commands that read data
structures and retrieve status. Commands that can be used to alter BMC configuration, write
data to the BMC or other management controllers, or perform system actions such as resets,
power on/off, and watchdog activation are disallowed.
Operator: All BMC commands are allowed, except for configuration commands that can
change the behavior of the out-of-band interfaces. For example, Operator privilege does not
allow the capability to disable individual channels, or to change user access privileges.
Administrator: All BMC commands are allowed, including configuration commands. An
administrator can execute configuration commands that would disable the channel that the
Administrator is communicating over.
Enable DHCP
The Enable Dynamic Host Configuration Protocol (DHCP) check box enables / disables the
dynamic host configuration protocol to allow the server to automatically assign the Host IP address,
Default Gateway IP address and Subnet Mask. DHCP is enabled when the box is checked.
When this option is enabled, the Host IP Address, Subnet Mask, and Default Gateway IP Address
edit boxes are disabled. The system must be reset before this setting takes effect.
Host IP Address
This edit box is for the logical or Internet address of the host. The IP address is required when
DHCP is disabled. The IP address is entered as a dotted notation, such as 192.168.0.2.
Subnet Mask
The edit box is for the host’s subnet mask. The server uses this to decide if alert destinations are in
the local subnet or in another subnet relative to the client console. The Subnet Mask is required
when DHCP is disabled. The Subnet Mask is entered as a dotted notation, such as 255.255.0.0.
Default Gateway IP Address
This edit box is for the IP address of the router used when the BMC sends a message or an alert to a
system on a different subnet than the BMC is on. It is required when DHCP is disabled. The IP
address is entered as a dotted notation, such as 192.168.0.2.
92 Intel® SR870BN4 Server System Product Guide
Page 93
Default Gateway MAC Address
This edit box allows the MAC address of the default gateway router to be entered. The MAC
address is entered as a series of six pairs of hex digits separated by dashes, such as 00-01-62-d0-3e-
66. Alphabetic hex digits (a-f) can be entered in uppercase or lowercase. This edit box is disabled
by default and is only activated if the check box for Automatically resolve Default Gateway MAC
address is not checked. If the edit box is cleared (no address is supplied), a message is displayed
asking that a valid address be entered. This edit box is disabled if DHCP is enabled.
Automatically Resolve Default Gateway MAC Address
This check box allows the user to specify whether the BMC should automatically attempt to resolve
the MAC address of the default gateway router. This box is checked by default unless the MAC
address edit box appears to include a valid MAC address.
If this box is not checked, the MAC address in the Default Gateway MAC Address field must be
provided.
When the OK button is clicked, the firmware attempts to resolve the gateway MAC address. If the
BMC cannot resolve the address, the screen is redisplayed with the box unchecked and the user is
asked to provide the MAC address in the Default Gateway MAC Address field. If the screen is
redisplayed due to a MAC address resolution issue, any user data previously entered, other than the
MAC address information, remains in place.
This check box is disabled if DHCP is enabled.
Backup Gateway IP Address
This edit box allows the IP address of a backup gateway router to be entered. The IP address is
entered as a dotted notation, such as 192.168.0.2.
Backup Gateway MAC Address
This edit box allows the MAC address of the backup gateway router to be entered. The MAC
address is entered as a series of six pairs of hex digits separated by dashes, such as 00-01-62-d0-3e-
66. Alphabetic hex digits (a-f) can be entered in uppercase or lowercase. This edit box is disabled
by default and is only activated if the check box for Automatically resolve Backup Gateway MAC
address is not checked. If the edit box is cleared (no address is supplied), a message is displayed
asking that a valid address be entered. .
Automatically Resolve Backup Gateway MAC Address
This check box allows the user to specify whether the BMC should automatically attempt to resolve
the MAC address of the backup gateway router. This box is checked by default unless the MAC
address edit box appears to include a valid MAC address.
If this box is not checked, the MAC address in the Backup Gateway MAC Address field must be
provided.
When the OK button is clicked, the firmware attempts to resolve the gateway MAC address. If the
BMC cannot resolve the address, the screen is redisplayed with the box unchecked and the user is
asked to provide the MAC address in the Backup Gateway MAC Address field. If the screen is
redisplayed due to a MAC address resolution issue, any user data previously entered, other than the
MAC address information, remains in place.
Intel® SR870BN4 Server System Product Guide 93
Page 94
LAN Alert Configuration
The LAN Alert Configuration screen is displayed when the user clicks Next from the LAN
Channel Configuration screen. The LAN Alert Configuration screen shows all configured
destination IP addresses for LAN alerts and their associated settings. If no IP addresses are
configured as alert destinations, the Edit and Delete buttons are disabled.
Figure 26. LAN Alert Configuration
After completing this screen, click Next to move to the next screen to continue this sub-task.
Enable LAN Alerting
This check box is used to enable or disable alerts on the LAN channel.
SNMP Community String
This edit box is used to enter a string for Platform Event Traps (PETs). This field can optionally be
used for a vendor-specific string that is used to provide the network name identity of the system
that generated the event. This string is restricted to a maximum of 18 bytes and it is typically set to
public. This string can be null.
94 Intel® SR870BN4 Server System Product Guide
Page 95
Alert Settings
Up to four LAN alert destinations can be configured. When one or more IP addresses are
configured as alert destinations, this part of the screen shows those addresses, along with the
following associated configuration settings:
Gateway IP address for the destination IP address.
Whether alert acknowledge is enabled for the alerts sent to this destination.
The number of times the alert will be retried.
The interval in milliseconds between retries.
New, Edit, and Delete Buttons
If no alerts are configured, only the New button is enabled.
New: When the New button is clicked, the user is shown a screen on which a new LAN
destination address can be configured. See the following section for details.
Edit: If the user selects an IP address and then clicks the Edit button, screen where the user
can edit the configuration for the selected IP address is shown. See the following section for
details.
Delete: If the user selects an IP address and then clicks the Delete button, the selected IP
address is deleted. Before deleting the IP address, the user is prompted by a confirmation
prompt. If the user clicks OK to confirm deleting the address, the LAN Alerting Configuration
screen is redisplayed with the deleted address no longer shown.
These buttons affect only the copy of the firmware data internal to the SMU. Changes are written
to non-volatile storage in the firmware only after the user selects the Save button in the last LAN
configuration screen.
Intel® SR870BN4 Server System Product Guide 95
Page 96
New/Edit LAN Alert
The New/Edit LAN Alert screen is displayed when teh user clicks either New or Edit on the LAN
Alert Configuration screen. The New/Edit LAN alert screen allows the user to configure or change
the settings related to an IP address that is to receive alerts. The screen displayed either to
configure a new alert destination or to edit an existing alert is the same, except that when editing an
existing alert destination, the current settings read from the firmware are automatically displayed.
Figure 27. New / Edit LAN Alert
After completing this screen, click OK to return to the LAN Alert Configuration screen.
Destination IP Address
This edit box allows the user to enter the IP address to which an alert is to be sent. The IP address
is entered as a dotted notation, such as 192.168.0.2. The SMU does not check whether an IP
address matches a previously entered address.
Destination MAC Address
This edit box is used to enter the MAC address of the destination machine to which the alert should
be sent. This box is used when the destination IP address is outside the subnet that the server is on.
The MAC address should be entered as a series of six pairs of hex digits separated by dashes, such
as 00-01-62-d0-3e-66. Alphabetic hex digits (a-f) can be entered in uppercase or lowercase. This
edit box is disabled by default and is only activated if the check box is not checked for
Automatically will resolve destination MAC address.
96 Intel® SR870BN4 Server System Product Guide
Page 97
Automatically Resolve Destination MAC Address
This check box allows the user to specify whether the BMC should automatically attempt to resolve
the MAC address of the destination system. This box is checked by default unless the MAC
address edit box appears to include a valid MAC address.
If this box is not checked, the MAC address in the Destination MAC Address field must be
provided.
When the OK button is clicked, the firmware attempts to resolve the destination MAC address. If
the BMC cannot resolve the address, the screen is redisplayed with the box unchecked and the user
is asked to provide the MAC address in the Destination Gateway MAC Address field. If the screen
is redisplayed due to a MAC address resolution issue, any user data previously entered, other than
the MAC address information, remains in place.
Number of Retries
This edit box allows the number of times to retry sending an alert to a given destination to be
entered. If alert acknowledge is enabled, then retries are sent only if a timeout occurs while waiting
for the acknowledgement. If alert acknowledge is disabled, the number of retries is equal to the
number of times an unacknowledged alert is sent out.
If the number of retries is set to 0, only a single attempt is made to send the alert. When a number
greater than 0 is entered, the alert will be retried only if a timeout occurs while waiting for the
acknowledgement.
The number of retries must be between zero and seven.
Retry Interval
This edit box is used to set the retry interval for sending an alert or to set the acknowledge timeout
when Enable Alert Acknowledge is enabled. The value entered into this field is disregarded if
Enable Alert Acknowledge is disabled.
The retry interval is in seconds, with a recommended value of three seconds. The retry value must
be between 1 and 255.
Enable Alert Acknowledge
This check box should be checked if the destination IP address should send an acknowledgement
when an alert is received. If this box is checked, then an alert is only assumed to have been
successfully sent if an acknowledgement is received.
Use Default Gateway
This check box should be checked if the IP address entered as the default gateway IP address for
the LAN channel on the first LAN configuration screen should be used as the gateway for this
destination IP address. If this box is not checked, the backup gateway IP address is used as the
gateway IP address.
Intel® SR870BN4 Server System Product Guide 97
Page 98
Serial Over LAN Configuration
The Serial Over LAN screen is displayed after the user clicks Next on the LAN Alert
Configuration screen. The Serial Over LAN screen, shown in the following diagram, allows the
user to configure the operation of the serial over LAN capability of the BMC.
The SMU sets up the SOL configuration such that SOL packets do not have to be authenticated.
This enhances the performance of an SOL session.
Figure 28. Serial Over LAN Configuration
After configuring the Serial Over LAN information, click Save to complete this sub-task.
Enable Serial Over LAN
This check box is used to enable or disable the serial over LAN capability.
SOL Privilege Level
This setting is used to select the minimum operating privilege level that is required to be able to
activate SOL. The choices are User, Operator, and Administrator. For the best
performance, User should be selected.
Number of Retries
This field sets the number of times that the BMC tries to resend a SOL message to a remote
console.
The number of retries must be between zero and seven.
98 Intel® SR870BN4 Server System Product Guide
Page 99
Retry Interval
This field sets the number of milliseconds that the BMC waits between trying to send SOL
messages to a remote client.
The value entered must be between 0 and 2559. The SMU truncates the digit in the ones column
from any input number because the firmware maintains this value in 10 millisecond intervals.
Therefore, any value that is entered between 0 and 9 is displayed as 0.
Baud Rate
This field sets the baud rate at which serial data is transferred by the BMC when SOL is active.
The choices are Default IPMI, 9600 bps, 19.2 kbps, 38.4 kbps, 57.6, and 115.2 kbps. If Default IPMI is selected, the baud rate used is the rate currently set for BIOS serial
redirection. When SOL is active, serial communication with the BMC always occurs with eight
data bits, no parity, one stop bit, and RTS/CTS (hardware) flow control.
Intel® SR870BN4 Server System Product Guide 99
Page 100
User Configuration Sub-task
The User Configuration sub-task provides a way to configure the user access to the LAN and
Serial/Modem channels. Up to four users are allowed. Some of the options presented in these
screens depend on how the channels have been configured; therefore, the channels should be
configured before the user accesses these settings.
Sessions allow a framework for user authentication and allow multiple IPMI messaging streams on
a single channel.
After clicking on the User Configuration sub-task, the screen displayed below is shown. This
screen displays an entry for each possible user that can be configured. This screen shows:
Whether a particular user is enabled or disabled for channel access
Whether a password is set for the user
The privilege level the user has for each of the available channels that supports sessions (users
can only access channels that support sessions)
The first user is always present and is used to support an anonymous login. The username for this
user is null (blank) and cannot be changed; the user name displays the text Anonymous User.
The password can be set to a desired value.
It is possible for multiple user entries to have the same username. This occurs if a different
password is needed for the same user on different channels. In this case, the privilege level for the
channel that is not to be accessed with the associated password should be set to No Access.
Otherwise, the firmware attempts to use the first entry in the user table that it finds that allows
access to the specified channel and would expect the password associated with that entry to be the
one entered to gain access to the specified channel.
100 Intel® SR870BN4 Server System Product Guide
Figure 29. User Configuration
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.