HPE H7B50B User Manual
HPE Integrity MC990 X Server User Guide
Abstract
This guide provides an overview of the architecture, general operation, and descriptions of the
major components that comprise the HPE Integrity MC990 X Server system. It also provides
the standard procedures for powering on and powering off the system, basic troubleshooting
and maintenance information, Foundation Software usage information, and important safety
and regulatory specifications.
Part Number: 855704-006
Published: January 2019
Edition: 6
Contents
HPE Integrity MC990 X Server overview............................................... 6
Operational procedures........................................................................13
MC990 X server chassis............................................................................................................... 6
System components......................................................................................................................6
Unit numbering.................................................................................................................10
Rack numbering............................................................................................................... 10
HPE Integrity MC990 X system features.................................................................................... 10
Distributed shared memory (DSM)...................................................................................10
Distributed shared I/O.......................................................................................................11
Rack management controller............................................................................................11
Reliability, availability, and serviceability.......................................................................... 12
Precautions................................................................................................................................. 13
ESD precaution................................................................................................................ 13
Safety precautions........................................................................................................... 13
System control network...............................................................................................................13
Accessing the system control network........................................................................................14
Connecting to the system control network.................................................................................. 14
Communicating with the system................................................................................................. 15
The command line interface.............................................................................................15
Powering the system up and down............................................................................................. 16
Preparing to power up......................................................................................................16
Powering up and down from the command line interface................................................ 17
Booting directly from an RMC.......................................................................................... 17
Remote LAN connection to the RMC............................................................................... 18
Establishing RMC IP hardware connections.................................................................... 18
Power up the system using the RMC network connection...............................................20
Monitoring power up.........................................................................................................20
Power down the system................................................................................................... 21
System control...................................................................................... 22
Levels of system control............................................................................................................. 22
System management overview........................................................................................ 22
RMC overview..................................................................................................................23
BMC overview.................................................................................................................. 24
System controller interaction.......................................................................................................24
System controllers.......................................................................................................................24
RMC functions..................................................................................................................25
Using the Foundation Software........................................................... 26
Monitoring main memory health..................................................................................................26
About main memory health monitoring............................................................................ 26
Retrieving main memory health information.....................................................................26
Monitoring system performance..................................................................................................27
About the system monitoring software............................................................................. 27
hubstats command ...................................................................................................... 27
2
linkstat command ...................................................................................................... 28
gr_systat command .................................................................................................... 28
nodeinfo command ...................................................................................................... 28
topology command ...................................................................................................... 29
Enabling CPU frequency scaling................................................................................................ 31
About CPU frequency scaling.......................................................................................... 31
CPU frequency scaling for Integrity MC990 X systems................................................... 31
Additional Foundation Software utilities...................................................................................... 36
Component replacement procedures................................................. 38
Maintenance precautions and procedures..................................................................................38
Preparing the system for maintenance or upgrade.......................................................... 38
Returning the system to operation................................................................................... 39
Removing the chassis top cover................................................................................................. 39
Adding or replacing PCIe or GPU cards..................................................................................... 40
Installing cards in the MC990 X server chassis............................................................... 40
Installing or replacing a drive...................................................................................................... 42
Remove or replace a 2.5-inch hard drive......................................................................... 43
Remove or replace a 1.8-inch SSD option drive.............................................................. 44
Replacing an MC990 X server chassis power supply.................................................................45
Replacing an MC990 X server chassis fan assembly.................................................................46
Integrity MC990 X system Troubleshooting....................................... 48
Troubleshooting chart................................................................................................................. 48
LED status indicators.................................................................................................................. 48
Power supply LEDs..........................................................................................................49
System motherboard status LEDs................................................................................... 49
Technical specifications and pinouts................................................. 51
Integrity MC990 X system specifications.................................................................................... 51
Integrity MC990 X system physical specifications...................................................................... 51
Integrity MC990 X system environmental specifications.............................................................52
Integrity MC990 X system electrical specifications..................................................................... 53
I/O port specifications................................................................................................................. 54
Motherboard VGA port information.................................................................................. 55
Ethernet port.....................................................................................................................56
Serial port.........................................................................................................................57
USB port...........................................................................................................................57
System technical information.............................................................. 59
System architecture.................................................................................................................... 59
ccNUMA architecture.................................................................................................................. 60
Cache coherency............................................................................................................. 60
Non-uniform memory access (NUMA)............................................................................. 61
Safety and regulatory information.......................................................62
Safety information....................................................................................................................... 62
Regulatory information................................................................................................................63
Regulatory Model Numbers............................................................................................. 63
3
Websites................................................................................................ 64
Support and other resources...............................................................65
Accessing Hewlett Packard Enterprise Support......................................................................... 65
Accessing updates......................................................................................................................65
Customer self repair....................................................................................................................66
Remote support.......................................................................................................................... 66
Warranty information...................................................................................................................66
Regulatory information................................................................................................................67
Documentation feedback............................................................................................................ 67
4
©
Copyright 2016, 2019 Hewlett Packard Enterprise Development LP
Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett
Packard Enterprise products and services are set forth in the express warranty statements accompanying
such products and services. Nothing herein should be construed as constituting an additional warranty.
Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained
herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession,
use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer
Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard
Enterprise website.
Acknowledgements
Intel® and Intel Xeon® are trademarks of Intel Corporation in the in the U.S. and other countries.
Google® is a registered trademark of Google Inc.
Linux® is a registered trademark of Linus Torvalds in the U.S. and other countries.
Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.
SUSE LINUX is a registered trademark of Novell Inc.
Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
NUMAlink® and NUMAflex® are trademarks or registered trademarks of Silicon Graphics International
Corp. or its subsidiaries in the United States and/or other countries worldwide.
HPE Integrity MC990 X Server overview
This chapter provides an overview of the physical and architectural aspects of the HPE Integrity MC990 X
system. The major components of the Integrity MC990 X system are described and illustrated.
The Integrity MC990 X system is an advanced symmetric multiprocessing (SMP) computer system with
multiple Intel processor sockets as a cache-coherent single system image (SSI). Each processor socket
in the system houses multiple compute cores.
In an SMP system, each MC990 X chassis contains memory that it shares with all other processors in the
system. Because the Integrity MC990 X system is modular, it combines the advantages of lower entrylevel cost with global scalability in processors, memory, and I/O. You can install and operate the Integrity
MC990 X system in your lab or server room. One 42U rack holds one or more MC990 X chassis, the rack
management controller (RMC) unit, power distribution units (PDU), and optional mass storage units.
MC990 X server chassis
The basic enclosure within the Integrity MC990 X system is the MC990 X server chassis. The MC990 X
server chassis contains one four-socket motherboard connected to support up to 28 NUMAlink ports,
each with a maximum bidirectional bandwidth communication rate of up to 7.47 GB/sec.
Each MC990 X server chassis has ports that are brought out to external NUMAlink connectors on the
front of the enclosure. The single rack houses up to eight MC990 X server chassis (making up the MC990
X server), an RMC unit, and optional external storage.
Figure 1: MC990 X server chassis on page 6 shows an example of an MC990 X server chassis prior
to mounting in a rack.
The system requires a minimum of one rack with enough PDUs to support as many as eight MC990 X
server chassis, one RMC, and any optional equipment installed in the rack.
You can also add PCIe expansion cards or RAID and non-RAID disk storage to your server system.
1. System drive assembly
2. NUMAlink connectors (28)
Figure 1: MC990 X server chassis
System components
The Integrity MC990 X system includes the following major components:
6 HPE Integrity MC990 X Server overview
• 42U rack—These racks are used for the MC990 X enclosures, RMC, and optional external storage in
the Integrity MC990 X system. Up to eight MC990 X enclosures can be installed in each 42U rack.
• Server chassis—The Integrity MC990 X system includes one base server chassis and can include
one or more expansion server chassis. Each 5U-high server chassis contains four power supplies, one
four-processor compute/memory board, and other optional riser enabled drives and boards for the
Integrity MC990 X system. The base server chassis also has a BaseIO riser not present in the
expansion server chassis. MC990 X base server chassis front components shows the MC990 X
server chassis front panel components.
1. USB ports (4)
2. ETH0
3. DVD drive
4. System drive assembly
5. RMC
6. MGMT
7. Serial port
8. VGA port
9. Optional 1.8-inch SSD drive bays
10. NUMAlink ports (28)
Figure 2: MC990 X base server chassis front components
HPE Integrity MC990 X Server overview 7
1. PCIe card slots (16)
2. RMC port
3. MGMT port
4. Serial port
5. VGA port
6. NUMAlink ports (28)
Figure 3: MC990 X expansion server chassis front components
• Motherboard—Holds four processor sockets and eight memory risers. Each memory riser has up to
12 DIMMs, for a maximum of 96 DIMMs per motherboard. Each motherboard can be ordered with
risers that enable the base MC990 X server chassis to support up to four full-height x16 PCIe cards
and up to eight full-height x8 PCIe cards.
• Drives—Each MC990 X base server chassis has a drive tray that supports one optional slim-line
SATA DVD drive and four 2.5-inch hard disk or solid-state drives. An MC990 X expansion server
chassis does not require a drive assembly and can accommodate four additional PCIe cards.
• Internal PCIe enabled slots—The MC990 X enclosure and motherboard support the following types
of PCIe option boards:
◦ Four full-height, half-length, Gen3 x8 PCIe slots
◦ Four full-height, 10.5-inch length, Gen3 x8 PCIe slots
◦ Four full-height, doublewide, 10.5-inch length, Gen3 x16 PCIe slots
NOTE: The x16 PCIe slots support cards with a maximum power consumption of 300 watts.
• NUMAlink Connectors —The external NUMAlink connectors are on the lower-front portion of each
MC990 X enclosure.
• BaseIO board—Optional I/O riser board, connected directly to the motherboard. Supports base
system I/O functions including one Gbit Ethernet connector (top), four USB ports, and bays for two
optional external 1.8-inch solid-state drives (SSDs).
Internally, the BaseIO board supports:
8 HPE Integrity MC990 X Server overview
◦ Four internal 3GB/s SATA ports (for the four 2.5-inch disk drives in the MC990 X server chassis)
◦ Two internal 6GB/s SATA ports (for the two optional mini 1.8-inch SSDs)
◦ One internal USB 2.0 port (for the internal DVD)
NOTE: Each Integrity MC990 X system (or SSI within a system) requires one BaseIO board. BaseIO
board front panel components shows the front components of the BaseIO board. The SSD drives
(bottom) are enclosed with a metal cover.
1. Ethernet port
2. USB ports (4)
3. Solid-state Drives (2)
Figure 4: BaseIO board front panel components
• RMC---This 1U-high rack management controller provides external LAN and USB connections into the
Integrity MC990 X system. It acts as a top layer of system control. An internal 24-port Ethernet switch
allows system control for up to multiple MC990 X enclosures in an expanded Integrity MC990 X
system.
HPE Integrity MC990 X Server overview 9
1. Network ports (24)
2. WAN port
3. AUX port
4. CNSL port
5. RST button
6. PG (Power Good) LED indicator
7. HB (Heart Beat) LED indicator
Figure 5: RMC front panel connections
Unit numbering
Bays in the racks are numbered using standard units. A standard unit (U) is equal to 1.75 inches (4.445
cm). Because the chassis occupy multiple units, locations within a rack are identified by the bottom unit
(U) in which the chassis resides. For example, in a 42U rack, an MC990 X server chassis positioned in
U01 through U05 is identified as U01.
Rack numbering
Each rack is numbered with a three-digit number sequentially beginning with 001. A rack contains one or
more MC990 X server chassis, one RMC, optional mass storage enclosures, and other optional
components. In a single rack system, the rack number is always 001.
HPE Integrity MC990 X system features
The HPE Integrity MC990 X server is a modular system. The compute, memory, and PCIe components
are housed in the MC990 X chassis. Additional optional mass storage may be added to the system along
with additional MC990 X chassis.
You can add different types of PCIe board options to a server to achieve the desired system
configuration. You can easily configure systems around processing capability, I/O capability, memory size,
or storage capacity. Each air-cooled MC990 X chassis has redundant, hot-swap fans and redundant, hotswap power supplies.
Distributed shared memory (DSM)
In the Integrity MC990 X system, memory is physically distributed both within and among the MC990 X
server chassis (compute/memory/I/O); however, it is accessible to and shared by all NUMAlinked devices
within the SSI. This means all NUMAlinked components sharing a single Linux operating system operate
and share the memory fabric of the system. Memory latency is the amount of time required for a
processor to retrieve data from memory. Memory latency is lowest when a processor accesses local
memory. Note the following subtypes of memory within a system:
10 HPE Integrity MC990 X Server overview
• If a processor accesses memory that it is connected to on an MC990 X server chassis motherboard,
the memory is referred to as the processor local memory. Figure 6: MC990 X server chassis
memory riser block diagram on page 11 shows a conceptual block diagram of the motherboard
memory riser board pathways.
• If processors access memory located in another NUMAlinked MC990 X server chassis motherboard
within the system, the memory is referred to as remote memory.
• The total memory within the NUMAlinked Integrity MC990 X system is referred to as global memory.
Physical memory riser
Physical memory nodes are memory risers and each is made up of two board assemblies: memory riser
board and power board. Eight memory riser assemblies plug into each MC990 X server chassis
motherboard. The memory riser power board receives power directly from the motherboard. A maximum
of 12 DDR4 memory DIMMs are supported in each memory riser.
Memory controller
Figure 6: MC990 X server chassis memory riser block diagram
Distributed shared I/O
Like DSM, I/O devices are distributed within the MC990 X server chassis. Each BaseIO riser is accessible
by all compute nodes within the SSI through the NUMAlink interconnect fabric.
Rack management controller
Each Integrity MC990 X system has a rack management controller (RMC) located directly above or below
the MC990 X server chassis in a rack. The RMC supports powering up and down of the system
motherboards and environmental monitoring of all Integrity MC990 X system units within the SSI. In
addition, the RMC provides the top layer of system control for Integrity MC990 X system. Through the use
of an internal 24-port Ethernet switch, a single RMC can provide system control for multiple MC990 X
server chassis in an expanded Integrity MC990 X system.
One GigE port from each MC990 X server chassis motherboard connects to the RMC via Cat-5 cable.
HPE Integrity MC990 X Server overview 11
Reliability, availability, and serviceability
HPE Integrity MC990 X system components have the following features to increase the reliability,
availability, and serviceability (RAS) of the systems.
• Power and cooling:
◦ MC990 X server chassis power supplies are redundant and can be hot-swapped.
◦ MC990 X server chassis have overcurrent protection at the motherboard and power supply level.
◦ MC990 X server chassis fans are redundant and can be hot-swapped.
◦ MC990 X server chassis fans run at multiple speeds. Speed increases automatically when
temperature increases or when a single fan fails.
• System monitoring:
◦ System controllers monitor the internal power and temperature of the MC990 X server chassis
components, and can automatically shut down an enclosure to prevent overheating.
◦ All main memory has Intel Single Device Data Correction to detect and correct 8 contiguous bits
failing in a memory device. Additionally, the main memory can detect and correct any two-bit errors
coming from two memory devices (8 bits or more apart).
◦ All high speed links including Intel Quick Path Interconnect (QPI), Intel Scalable Memory
Interconnect (SMI), and PCIe have cyclic redundancy check (CRC) check and retry.
◦ The NUMAlink interconnect network is protected by CRC.
◦ Each MC990 X server chassis installed has status LEDs that indicate the server operational
condition; LEDs are viewable at the front of the unit.
• Power-on and boot:
◦ Automatic testing occurs after you power on the system. These power-on self-tests or POSTs are
also referred to as power-on diagnostics or PODs.
◦ Processors and memory are automatically disabled when a self-test failure occurs.
◦ Boot times are minimized.
• Further RAS features:
◦ Systems can report status inventory information, provide hardware logs of out-of-range conditions,
or perform recovery procedures through remote commands.
◦ All system faults are logged in files.
◦ Memory can be scrubbed using error checking code (ECC) when a single-bit error occurs.
12 HPE Integrity MC990 X Server overview
Operational procedures
This chapter provides an overview on how to operate your new system in the following sections:
•
Precautions on page 13
• System control network on page 13
• Powering the system up and down on page 16
Precautions
Before operating your system, familiarize yourself with the safety information in the following sections:
ESD precaution on page 13
•
• Safety precautions on page 13
ESD precaution
CAUTION:
Observe all ESD precautions. Failure to do so can result in damage to the equipment.
HPE recommends wearing an approved wrist strap when you handle any ESD-sensitive device to
eliminate possible ESD damage to equipment. Connect the wrist strap cord directly to earth ground.
Safety precautions
WARNING: Before operating or servicing any part of this product, read the Safety information on
page 62.
WARNING: Keep fingers and conductive tools away from high-voltage areas. Failure to follow these
precautions will result in serious injury or death. The high-voltage areas of the system are indicated
with high-voltage warning labels.
CAUTION: Power off the system only after the system software has been shut down in an orderly
manner. If you power off the system before you halt the operating system, data may be corrupted.
System control network
All MC990 X server chassis use an RMC which communicates with the chassis board level BMCs within
each SSI. These components in concert are generically known as the system control network.
The Integrity MC990 X system control network provides control and monitoring functionality for each
motherboard, power supply, and fan assembly in each MC990 X server chassis in the system.
The RMC network provides the following functionality:
• Powering the entire system up and down.
• Powering individual MC990 X server chassis up and down.
• Monitoring the environmental state of the system, including voltage levels.
Operational procedures 13
• Monitors and controls status LEDs on the enclosure.
• Supports entry of controller commands to monitor or change particular system functions within a
particular MC990 X server chassis. See the HPE Integrity MC990 X Server RMC Software User Guide
for a complete list of command line interface (CLI) commands.
• Provides access to the system OS console allowing you to run diagnostics and boot the system.
• Provides the ability to flash system BIOS.
Accessing the system control network
Access to the system control network is accomplished by the following methods:
• A LAN connection to the RJ-45 WAN port on the RMC, (see Figure 7: RMC front panel connections
on page 14).
• A USB-to-micro-USB serial connection to the “Console” port (see CNSL in Figure 7: RMC front panel
connections on page 14) on the RMC front panel example.
1. Network ports (24)
2. WAN port
3. AUX port
4. CNSL port
5. RST button
6. PG (Power Good) LED indicator
7. HB (Heart Beat) LED indicator
Figure 7: RMC front panel connections
Connecting to the system control network
The Ethernet connection is the preferred method of accessing the system console.
Administrators can perform one of the following options for connectivity:
14 Operational procedures
• A portable system console can be directly connected to the RMC micro-USB connect port, (labeled
CNSL). See Figure 7: RMC front panel connections on page 14. This requires connecting from a
laptop or workstation that is physically located near the system.
• A LAN connection is used to communicate directly with the RMC, using the IPMI 2.x protocols. This
LAN connection must be made to the RJ-45 WAN port on the RMC. This connection can be used with
a local or remote IPMI-enabled console device.
Communicating with the system
The two primary ways to communicate with and administer the MC990 X system are through the RMC
interface command line interface (CLI) or through an IPMI 2.x LAN interface.
The command line interface
The Integrity MC990 X system CLI is accessible by logging directly into a RMC.
Log in to the RMC as root:
asylum$ ssh root@mc990x-rmc
root@mc990x-rmc's password:
MC990 X RMC, Rev. 1.1.xx [Bootloader 1.1.x]
RMC:r001i01c> help
NOTE: HPE recommends changing all default logins and passwords.
Once a connection to the RMC is established, system control commands can be entered. See Example
CLI commands used on page 15 for some examples.
See Powering up and down from the command line interface on page 17 for additional specific
examples of using the CLI commands.
Example CLI commands used
The following is a list of some available CLI commands:
auth
authenticate SSN/APPWT change
bios
perform bios actions
bmc
access BMC shell
rmc
access RMC shell
config
show system configuration
console
access system consoles
help
list available commands
Operational procedures 15
hel
access hardware error logs
hwcfg
access hardware configuration variable
leds
display system LED values
log
display system controller logs
power
access power control/status
Type <cmd> --help for help on individual commands.
Powering the system up and down
This section explains how to power up and power down individual units, or your entire Integrity MC990 X
system, as follows:
Preparing to power up on page 16
•
• Powering up and down from the command line interface on page 17
• Booting directly from an RMC on page 17
Using an RMC connection, you can power up and power down an individual MC990 X server chassis, or
the entire system.
Preparing to power up
To prepare to power up your system, follow these steps:
Procedure
1. Check to ensure that the power connector on the cable between the rack PDUs and the wall power-
plug receptacles are securely plugged in.
2. For each individual MC990 X server chassis that you want to power up, make sure that the power
cables are plugged into all the chassis power supplies correctly, see the example in Figure 8: MC990
X server chassis power supply cable location on page 17. Setting the circuit breakers on the
PDUs to the (On) position will apply power to the individual MC990 X server chassis and will start the
RMC if it is plugged into the same PDU. Turn (Off) the PDU breaker switch on the PDU(s) that supply
power to the MC990 X server chassis or RMC power supplies if you want to remove all power from a
particular unit.
16 Operational procedures
Figure 8: MC990 X server chassis power supply cable location
1. Enclosure fan assembly (4) 2. HARP fan assembly
3. Enclosure power supply with power input
connector (4)
3. If you plan to power up an Integrity MC990 X system that includes optional mass storage enclosures,
make sure that the power switch on the rear of each PSU/cooling module (one or two per enclosure) is
in the (On) position.
4. Make sure that all PDU circuit breaker switches (see the examples in the following subsection) are
turned (On) to provide power to the server when the system is powered up.
Powering up and down from the command line interface
The Integrity MC990 X system CLI is accessible by logging into the RMC as “root”.
Commands issued at the CLI of a local console prompt typically only affect the local SSI or a part of the
system. Depending on the directory level you are logged in at, you may power up an entire SSI, a single
rack, or a single MC990 X server chassis. In CLI command console mode, you can obtain only limited
information about the overall system configuration. An RMC has information about all the MC990 X server
chassis in its rack or SSI. Each MC990 X server chassis has information about its internal motherboard
and options, and also (if other enclosures are attached via NUMAlink to the unit) information about those
MC990 X server chassis units.
Booting directly from an RMC
Use a USB-to-micro USB cable to administer your system locally from the RMC.
Connect the cable from your administrative laptop or other device directly to the port labeled CNSL on the
RMC. Note that the RMC will not (by default) require a password when you login via the CNSL port.
The console type and how these console types are connected to the Integrity MC990 X system is
determined by what console option is chosen. Establish either a serial connection and/or network/
Ethernet LAN connection to the RMC.
Operational procedures 17
USB-connected console hardware requirements
The local USB-connected terminal should be set to the following functional modes:
• Baud rate of 115,200
• 8 data bits
• One stop bit
• No parity
• No hardware flow control (RTS/CTS)
The physical console is located on the MC990 X server chassis that has the BaseIO board installed.
Figure 9: RMC Ethernet LAN (WAN port) location
1. Network ports (24) 2. WAN
3. AUX port 4. CNSL
5. RST button 6. PG LED indicator
7. HB LED indicator
Remote LAN connection to the RMC
If you have an Integrity MC990 X system and wish to use a remote or local system to administer the
system via LAN, you can connect via Ethernet cable to the RMC node WAN port identified in Figure 9:
RMC Ethernet LAN (WAN port) location on page 18.
• The terminal should be set to the operational modes described in the previous subsection.
• If you intend to use a LAN-connected administrative server to communicate with the RMC, the RMC
will either need to be assigned a DHCP IP address, or you will need to configure it with a static IP
address. See the following subsections for more information.
Establishing RMC IP hardware connections
For IP address configuration, there are two options: DHCP or static IP. The following subsections provide
information on the setup and use of both.
NOTE:
Both options require the use of the RMC micro-USB serial port, refer to Figure 7: RMC front panel
connections on page 14.
18 Operational procedures
LAN Network (LAN RJ-45) connections to the RMC are always made via the WAN port.
For DHCP, you must determine the IP address that the RMC has been assigned; for a static IP, you must
also configure the RMC to use the desired static IP address.
To use the serial port connection, you must attach and properly configure a micro-USB interface cable to
the RMC CNSL port. Configure the serial port as described in USB-connected console hardware
requirements on page 18.
When the serial port session is established, the console will show an RMC login, and the user can login to
the RMC as user "root". Note that there is not (by default) a password required to access the RMC via the
CNSL port.
Using DHCP to establish an IP address
To obtain and use a DHCP generated IP address, plug the RMC external RJ-45 network port (WAN) into
a network that provides IP addresses via DHCP; the RMC can then acquire an IP address.
To determine the IP address assigned to the RMC, you must first establish a connection to the RMC serial
LAN port (as indicated in the section
and run the command "ifconfig eth1". This will report the IP address that the RMC is configured to
use.
NOTE:
Running the RMC with DHCP is not recommended as the preferred option for Integrity MC990 X systems.
The nature of DHCP makes it difficult to determine the IP address of the RMC, and it is possible for that
IP address to change over time, depending on the DHCP configuration usage. The exception would be a
configuration where the system administrator is using DHCP to assign a "permanent" IP address to the
RMC.
USB-connected console hardware requirements on page 18),
To switch from a static IP back to DHCP, the configuration file /etc/sysconfig/ifcfg-eth1 on the
RMC must be modified. To edit this file, see additional instructions in the Using a static IP address on
page 19 section. The file must contain the following line to enable use of DHCP:
BOOTPROTO=dhcp
Using a static IP address
To configure the RMC to use a static IP address, the user/administrator must edit the configuration
file /etc/sysconfig/ifcfg-eth1 on the RMC. The user can use the vi command (i.e. "vi /etc/
sysconfig/ifcfg-eth1") to modify the file.
The configuration file should be modified to contain these lines:
BOOTPROTO=static
IPADDR=<IP address to use>
NETMASK=<netmask>
GATEWAY=<network gateway IP address>
HOSTNAME=<hostname to use>
NOTE:
The "GATEWAY" and "HOSTNAME" lines are optional.
After modifying the file, save, and write it using the vi command ":w!", and then exit vi using ":q". Then
reboot the RMC using the reboot command. After reboot, it will be configured with the specified IP
address.
Operational procedures 19
Power up the system using the RMC network connection
You can use a network connection to power on your Integrity MC990 X system as described in the
following steps:
Procedure
1. You can use the IP address of the RMC to perform an SSH login, as follows:
ssh root@<IP-ADDRESS>
The following example shows the RMC prompt:
MC990 X RMC, Rev. 1.1.xx [Bootloader 1.1.x]
RMC:r001i01c>
This refers to rack 1, RMC 1.
NOTE: HPE recommends changing all default logins and passwords.
2. Power up your Integrity MC990 X system using the power on command, as follows:
RMC:> power on
The system will take time to fully power up (depending on size and options). Larger systems take
longer to fully power up. Information on booting Linux from the shell prompt is included at the end of
Monitoring power up.
The following command options may be used with the RMC CLI:
Power up
Usage: power [-vcow] on|up [TARGET]—turns power on
-v, --verbose verbose output
-c, --clear clear EFI variables (system and partition targets only)
-o, --override override partition check
-w, --watch watch boot progress
Power down
Usage: [-vo] off |down [TARGET]—shuts power down
Reset system
Usage: power [-vchow] reset [TARGET]—resets the system power
Power status check
Usage: power [-vl0ud] status [TARGET]—checks power-on status.
To monitor the power-on sequence during boot, see
must be included.
Monitoring power up
Establish another connection to the RMC and use the uvcon command to open a system console and
monitor the system boot process. Use the following steps:
Monitoring power up, the -uvpower option
RMC:> uvcon
uvcon: attempting connection to localhost...
uvcon: connection to RMC (localhost) established.
uvcon: requesting baseio console access at r001i01b00...
uvcon: tty mode enabled, use ’CTRL-]’ ’q’ to exit
20 Operational procedures
uvcon: console access established
uvcon: RMC <--> BASEIO connection active
************************************************
******* START OF CACHED CONSOLE OUTPUT *******
************************************************
** [20100512.143541] BMC r001i01b10: Cold Reset via NL broadcast reset
** [20100512.143541] BMC r001i01b07: Cold Reset via NL broadcast reset
** [20100512.143540] BMC r001i01b08: Cold Reset via NL broadcast reset
** [20100512.143540] BMC r001i01b12: Cold Reset via NL broadcast reset
** [20100512.143541] BMC r001i01b14: Cold Reset via NL broadcast reset
** [20100512.143541] BMC r001i01b04: Cold Reset via NL....
NOTE: Use CTRL+]+q to exit the console when needed.
Depending on the size of your system, it can take 5 to 10 minutes for the Integrity MC990 X system to
boot to the EFI shell. When the shell> prompt appears, enter fs0: as in the following example:
shell> fs0:
At the fs0: prompt, enter the Linux boot loader information, as follows:
fs0:> /efi/suse/elilo.efi
The ELILO Linux Boot loader is called and various configuration scripts are run and the SUSE Linux
Enterprise Server 12 Service Pack x installation program appears.
Power down the system
To power down the MC990 X system, use the power off command, as follows:
RMC:> power off
==== r001i01c (PRI) ====
You can also use the power status command, to check the power status of your system:
RMC:> power status
==== r001i01c (PRI) ====
on: 0, off: 16, unknown: 0, disabled: 0
Operational procedures 21
Loading...