This chapter mainly describes operation of the server hardware.
4.1 Display Server Hardware Environment
This section describes methods for checking the configuration and status of the server hardware during system configuration or operation.
To display the configuration and status of a server, use the XSCF Shell.
Commands Used to Display Information
Execute the following commands individually, as appropriate. For details of these commands, see Chapter 5.
- showhardconf
- version
- showdate
- showenvironment
- showstatus
- cfgdevice
4.1.1 Displaying System Information
1. Use the showhardconf(8) command to check the mode switch status.
XSCF> showhardconf
SPARC Enterprise xxxx;
+ Serial:PP20605005; Operator_Panel_Switch:Locked;
+ Power_Supply_System:Single; SCF-ID:XSCF#0;
+ System_Power:On; System_Phase:Cabinet Power On;
Domain#0 Domain_Status:Powered Off;
MBU_B Status:Normal; Ver:0101h; Serial:7867000282 ;
:
|
2. Use the showdate(8) command to display the system time.
XSCF> showdate
Thu Jul 6 14:48:01 UTC 2006
|
3. Use the version(8) command to display the XCP comprehensive firmware version, XSCF version, and OpenBoot PROM version.
XSCF> version -c xcp -v
XSCF#0 (Active)
XCP0 (Current): 1082
OpenBoot PROM : 02.09.0000
XSCF : 01.08.0005
XCP1 (Reserve): 1082
OpenBoot PROM : 02.09.0000
XSCF : 01.08.0005
XSCF#1 (Standby )
XCP0 (Current): 1082
OpenBoot PROM : 02.09.0000
XSCF : 01.08.0005
XCP1 (Reserve): 1082
OpenBoot PROM : 02.09.0000
XSCF : 01.08.0005
OpenBoot PROM BACKUP
#0: 02.08.0000
#1: 02.09.0000
|
(This screenshot is provided as an example.)
4. Use the showstatus(8) command to display information on degraded components in the system.
XSCF> showstatus
* BP_A Status:Degraded;
* DDC_A#0 Status:Faulted;
* PSU#0 Status:Faulted;
|
(This screenshot is provided as an example.)
5. Use the showenvironment(8) command to display the ambient temperature, humidity, and voltage of the system.
XSCF> showenvironment
Temperature:30.70C
Humidity:90.00%
XSCF> showenvironment temp
Temperature:30.70C
CMU#0:43.00C
CPUM#0-CHIP#0:65.00C
CPUM#1-CHIP#0:61.20C
CPUM#2-CHIP#0:64.80C
CPUM#3-CHIP#0:63.60C
CMU#1:45.50C
:
XSCF> showenvironment volt
MBU_B
1.0V Power Supply Group:1.000V
1.8V Power Supply Group:1.910V
CPUM#0-CHIP#0
1.0V Power Supply Group:1.050V
:
|
(This screenshot is provided as an example.)
| Note - The humidity information is only displayed in M8000/M9000 servers.
|
Environmental Temperature and Fan Speed Level
With the altitude setting, the fan speed level varies by the environmental temperature. To display the fan speed for each environmental temperature, execute the showenvironment(8) command. Fan speed level indicates Low speed, Middle speed, or High speed.
The M8000/M9000 servers do not indicate Middle speed. The M3000 server indicates multi levels. In case errors detected in the fan, Full or High speed will be indicated.
TABLE 4-1, TABLE 4-2 and TABLE 4-3 list the fan speed level indicated by using the showenvironment(8) command, which corresponding to the altitude configured and the environmental temperature.
TABLE 4-1 Fan speed levels corresponding to altitude and environmental temperature (Entry-Level system)
|
Fan speed levels
|
Environmental temperatures by altitude
|
|
|
500 m or less
|
501-1000 m
|
1001-1500 m
|
1501-3000 m
|
|
Low speed (level-1)
|
20˚C or less
|
18˚C or less
|
16˚C or less
|
14˚C or less
|
|
Low speed (level-2)
|
19-22˚C
|
17-20˚C
|
15-18˚C
|
13-16˚C
|
|
Low speed (level-3)
|
21-24˚C
|
19-22˚C
|
17-20˚C
|
15-18˚C
|
|
Low speed (level-4)
|
23-26˚C
|
21-24˚C
|
19-22˚C
|
17-20˚C
|
|
Middle speed (level-5)
|
25-28˚C
|
23-26˚C
|
21-24˚C
|
19-22˚C
|
|
Middle speed (level-6)
|
27-30˚C
|
25-28˚C
|
23-26˚C
|
21-24˚C
|
|
High speed (level-7)
|
29-32˚C
|
27-30˚C
|
25-28˚C
|
23-26˚C
|
|
High speed (level-8)
|
31-34˚C
|
29-32˚C
|
27-30˚C
|
25-28˚C
|
|
High speed (level-9)
|
More than 33˚C
|
More than 31˚C
|
More than 29˚C
|
More than 27˚C
|
TABLE 4-2 Fan speed levels corresponding to altitude and environmental temperature (Midrange system)
|
Fan speed levels
|
Environmental temperatures by altitude
|
|
|
500 m or less
|
501-1000 m
|
1001-1500 m
|
1501-3000 m
|
|
Low speed
|
25˚C or less
|
23˚C or less
|
21˚C or less
|
19˚C or less
|
|
Middle speed
|
23-30˚C
|
21-28˚C
|
19-26˚C
|
17-24˚C
|
|
High speed
|
More than 28˚C
|
More than 26˚C
|
More than 24˚C
|
More than 22˚C
|
TABLE 4-3 Fan speed levels corresponding to altitude and environmental temperature (Highend system)
|
Fan speed levels
|
Environmental temperatures by altitude
|
|
|
500 m or less
|
501-1000 m
|
1001-1500 m
|
1501-3000 m
|
|
Low speed
|
27˚C or less
|
25˚C or less
|
23˚C or less
|
21˚C or less
|
|
High speed (level-9)
|
More than 24˚C
|
More than 22˚C
|
More than 20˚C
|
More than 18˚C
|
For the altitude setting, see Section 2.2.17, Altitude Administration
Power consumption and Exhaust air
To display power consumption and exhaust air of a server, use the power consumption monitoring function and the airflow incdicator. Power consumption monitoring function and airflow indicator make it possible to routinely confirm the amount of power consumed on and airflow emitted while the server is up and running.
Note - The power consumption monitoring function is supported only on M3000 server that run certain versions of XCP firmware as below. The M4000/M5000/M8000/M9000 servers do not support the power consumption monitoring function.
- M3000 server; XCP 1081 or later
The airflow indicator is supported only on M3000/M4000/M5000/M8000/M9000 servers that run certain versions of XCP firmware as below.
- M3000 server; XCP 1082 or later
- M4000/M5000 servers; XCP1100 or later
- M8000/M9000 servers; XCP1090 or later
|
For specific information about these minimum software and firmware requirements, see the latest version of the Product Notes (no earlier than the XCP 1081 edition) for your server.
To display the power consumption, use the showenvironment power command. The results displays the maximum (Permitted AC power consumption) and actual (Actual AC power consumption) power consumption values. When the power type is DC [direct-current] power supply, "... DC power ..." is displayed. To display the amount of exhaust air, use the showenvironment air command. You can also obtain the data of power consumption and exhaust air using the SNMP agent function.
The following is the showenvironment examples on M3000 server:
XSCF> showenvironment air
Air Flow:63CMH
XSCF> showenvironment power
Permitted AC power consumption:470W
Actual AC power consumption:450W
|
| Note - Power consumption and airflow values are for reference only. These values vary depending on factors such as system load.
|
The showenvironment power and showenvironment air commands do not include the information of External I/O Expansion Unit and peripheral I/O device. Also, the M4000/M5000/M8000/M9000 servers do not indicate power consumption by showenvironment command. For a power consumption value of the M4000/M5000/M8000/M9000 servers, see the SPARC Enterprise M4000/M5000 Servers Site Planning Guide or the SPARC Enterprise M8000/M9000 Servers Site Planning Guide.
For details of the showenvironment(8) command, see the the XSCF Reference Manual and man page. For the installation of server, see the Site Planning Guide for your server.
| Note - To obtain the data of exhaust air using the SNMP agent function, install the latest XSCF extension MIB definition file to the SNMP manager. For details on obtaining the XSCF extension MIB definition file, see the Product Notes for your server or download site for firmware.
|
Note - The amount of power consumption and exhaust air may not be indicated correctly in the MIB information, in the showenvironment power, showenvironment air commands output, and on the XSCF Web in the following cases; and you should wait for one minute and check the value again.
- During the server powering on or powering off, or for a while after the power-on or power-off complete
- During the active replacement of power supply unit, or for a while after the active replacement complete
|
4.1.2 Display Server Configuration/Status Information
Use the showhardconf(8) command to check the status of a device.
XSCF> showhardconf
SPARC Enterprise xxxx;
+ Serial:PP20605005; Operator_Panel_Switch:Locked;
+ Power_Supply_System:Single; SCF-ID:XSCF#0;
+ System_Power:On; System_Phase:Cabinet Power On;
Domain#0 Domain_Status:Powered Off;
MBU_B Status:Normal; Ver:0101h; Serial:7867000282 ;
:
|
The status information of each device is as below.
- CPU/Memory board unit / Motherboard unit information
Unit number, status, version, serial number, FRU number, memory capacity, and type.
In the M3000 server, the displayed information is CPU status, CPU operating frequency, CPU type, number of CPU cores, and number of CPU strands.
Unit number, status, version, serial number, FRU number, CPU operating frequency, CPU type, number of CPU cores, and number of CPU strands.
Unit number, status, version, serial number, FRU number, and information on each memory slot. In the M3000/M8000/M9000 servers, there is information on each memory slot.
The displayed information on each memory slot includes the unit number, status, code, type and memory capacity.
Note that the type field indicates the size and rank of the DIMM using a two-character code, as follows:
i. Type 1A = 1 GB, 1 rank
ii. Type 2A = 2 GB, 1 rank
iii. Type 2B = 2 GB, 2 rank
iv. Type 4A = 4 GB, 1 rank
v. Type 4B = 4 GB, 2 rank
vi. Type 8B = 8 GB, 2 rank
Unit number, status
Unit number, status, version, serial number, FRU number, type, and information on each PCI and DDC.
The displayed information on each PCI includes the unit number, name property, card type, serial number, FRU number, and type.
The displayed information on each DDC includes the unit number and status. In the M3000 server, there is information on each PCI slot.
- External I/O Expansion Unit (IOBOX) information
Unit number, serial number and information on each I/O boat and power supply unit in an I/O expansion unit (see Note).
The displayed information on each I/O boat includes the unit number, serial number, and link information.
The displayed link information includes the version, serial number, and type.
The displayed information on each power supply unit includes the unit number and serial number.
Unit number, status, version, serial number, and FRU number
- Crossbar Unit (XBU) information
Unit number, status,version, serial number, and FRU number
- Backplane (BP) information
Unit number, status, version, serial number, FRU number and each DDC information
The displayed information on each DDC includes the unit number version, serial number, and FRU number.
Unit number, status, version, serial number, and FRU number
- Operator panel information
Unit number, status, version, serial number and FRU number
- Power supply unit information
Unit number, status, serial number, FRU number, power status, power type, and voltage
Note that the power type field indicates "AC", which is AC power supply or "DC", which is DC power supply.
- Fan backplane information
Unit number, status, version, serial number, and FRU number
Unit number, status, serial number
| Note - The configuration information might change based on model configuration in M3000/M4000/M5000/M8000/M9000 servers.
|
| Note - The External I/O Expansion Unit may be referred to as IOBOX in example program output and the text in this manual.
|
Note - 8GB DIMM is supported in XCP1081 or later.
"Type" in the CPU/Memory board unit information is supported in XCP1090 or later on M8000/M9000 servers.
"Type" in the Motherboard unit information is supported in XCP1100 or later on M4000/M5000 servers.
"Type" in the I/O unit information is supported in XCP1100 or later on M4000/M5000/M8000/M9000 servers.
These "Type" information of the CPU/Memory board unit, Motherboard unit, and I/O unit, are shown by the alphabet or the figure, such as "Type:A" or "Type:B", and it shows that the hardware mounted in the unit is different. When the alphabet and the figure of the "Type" are larger, new hardware is installed.
The power type in the Power supply unit information is supported in XCP1091 or later on M3000 server.
|
4.2 Display Domain Information
This section describes methods for checking the configuration and status of a domain.
| Note - For details on domain management, configuration and each command, see Chapter 2, the XSCF Reference Manual, or the Administration Guide.
|
Commands Used to Display Domain Information
Execute the following commands individually, as appropriate. For details of commands, see Chapter 5.
- showdcl
- showboards
- showdomainstatus
- version
4.2.1 Domain Information
1. Use the showdcl(8) command to check the domain ID, LSB number, configuration policy, No memory state (true/false), No IO state (true/false), floating board state, and degradation information.
<Example 1> In the SPARC Enterprise M4000/M5000/M8000/M9000 servers
XSCF> showdcl -va
DID LSB XSB Status No-Mem No-IO Float Cfg-policy
00 Running FRU
00 00-0 False False False
01 -
02 -
03 -
04 01-0 False True False
05 -
:
15 -
<Example 2> In the M3000 servers
XSCF> showdcl -va
DID LSB XSB Status No-Mem No-IO Float Cfg-policy
00 Running FRU
00 00-0 False False False
|
2. Use the showdomainstatus(8) command to check the domain status.
XSCF> showdomainstatus -a
DID Domain Status
00 Running
01 -
02 Powered Off
03 Panic State
04 Shutdown Started
05 Booting/OpenBoot PROM prompt
06 Initialization Phase
07 OpenBoot Execution Completed
|
3. Use the showboards(8) command to check the XSB number, domain ID, LSB number, and XSB status.
XSCF> showboards -a
XSB DID(LSB) Assignment Pwr Conn Conf Test Fault
---- -------- ----------- ---- ---- ---- ------- --------
00-0 00(00) Assigned y y y Passed Normal
00-1 00(01) Assigned y y y Passed Normal
00-2 SP Available y n n Passed Normal
00-3 02(00) Unavailable y n n Unknown Normal
|
4. Use the version(8) command to check the OpenBoot PROM version of a domain.
XSCF> version -c cmu
DomainID 0: 02.09.0000
DomainID 1: 02.09.0000
:
DomainID 3: 02.09.0000
|
4.3 Adding or Removing Domains
The system can adopt a domain configuration by combining multiple system boards in a server. Each domain can operate independently.
To configure domains for a server, use the XSCF Web console or the XSCF Shell commands.
| Note - In the M3000 server, the domain configuration policy can be changed by using the setdcl(8) command. However, other domain configurations cannot be changed.
|
Commands Used to Setup or Display Information
Execute the following commands individually, as appropriate. For details of these commands, see Chapter 5.
- setdcl
- setupfru
- addboard
- deleteboard
- moveboard
For details on adding or changing a domain, see Chapter 2 of the XSCF Reference Manual or the Administration Guide.
For details on using the DR function to change the domain configuration, see the Dynamic Reconfiguration User’s Guide.
4.4 Server and Domain Power Operations
This section describes power operations for servers and domains, and it explains how to display the power status of a server or domain.
To perform the power operations, use the XSCF Shell commands.
Commands Used for the Operations or Status Display
Execute the following commands individually, as appropriate. For details of these commands, see Chapter 5.
- poweron
- poweroff
- reset
- sendbreak
- setpowerupdelay
- showpowerupdelay
- setshutdowndelay
- showshutdowndelay
- setdualpowerfeed
- showdualpowerfeed
With the power operations, the following can be performed:
- System power on
- System power off
- Domain power on
- Domain power off
- Sending a Domain Panic Request (Solaris OS dump request)
- Domain reset
- Sending break signal to a domain
- Air-conditioning wait time administration
- Warm-up time administration
- Dual power feed
4.4.1 System Power On
1. Use the showlogs power command to check the status of system power off.
The System Power Off status means one of the following.
- The input power supply has been turned on, and the poweron(8) command is not yet executed or the POWER switch of the operator panel is not yet pressed; that is, all domains have not yet been powered on.
- The poweroff(8) command has been executed or the POWER switch of the operator panel has been pressed, to power off all domains; and "System Power Off" is displayed in the showlogs power command execution result.
XSCF> showlogs power
Feb 26 13:52:19 JST 2010 SCF Reset Power on -- Service
Or
Feb 26 13:52:19 JST 2010 System Power Off Operator -- Service
|
2. Use the poweron(8) command to turn on power to all domains.
XSCF> poweron -a
DomainIDs to power on:00,01,02,03
Continue? [y|n] :y
00 :Not powering on: The power supply has already been turned on.
01 :Powering on
02 :Powering on
03 :Powering on
*Note*
This command only issues the instruction to power-on.
The result of the instruction can be checked by the
"showlogs power".
|
| Note - Only the domains that are able to be powered on are displayed.
|
3. Use the showlogs power command to check the system power on.
XSCF> showlogs power
Feb 26 14:12:19 JST 2010 System Power On Operator -- Service
|
| Note - Use the showdomainstatus(8) command to check the power status of the domain.
|
4.4.2 System Power Off
1. Use the showlogs power command to check the power status of the system.
XSCF> showlogs power
Feb 26 14:12:19 JST 2010 System Power On Operator -- Service
|
2. Use the showdomainstatus(8) command to check the power status of the system.
XSCF> showdomainstatus -a
DID Domain Status
00 Running
01 Running
02 Running
03 Running
|
3. Use the poweroff(8) command to turn off power to all domains.
XSCF> poweroff -a
DomainIDs to power off:00,01,02,03
Continue? [y|n] :y
00 : Powering off
01 : Powering off
02 : Powering off
03 : Powering off
*Note*
This command only issues the instruction to power-off.
The result of the instruction can be checked by the
"showlogs power".
|
| Note - Only the domains that are able to be powered off are displayed.
|
| Note - If the poweroff(8) command is performed, and the shutdown has completed, then the domain is powered off.
|
4. Use the showlogs power command to check the system power off.
XSCF> showlogs power
Feb 26 14:22:19 JST 2010 System Power Off Operator -- Service
|
4.4.3 Domain Power On
1. Use the showdomainstatus(8) command to check the power status of all domains.
XSCF> showdomainstatus -a
DID Domain Status
00 Powered Off
01 Running
02 Powered Off
03 Powered Off
|
2. Use the poweron(8) command to turn on power to the specified domain.
<Example 1> Turn on power to the specified domain.
XSCF> poweron -d 0
DomainIDs to power on:00
Continue? [y|n] :y
00 :Powering on
*Note*
This command only issues the instruction to power-on.
The result of the instruction can be checked by the
"showlogs power".
<Example 2> Cancel domain power on in progress.
XSCF> poweron -d 0
DomainIDs to power on:00
Continue? [y|n] :n
XSCF>
|
4.4.4 Domain Power Off
1. Use the showdomainstatus(8) command to check the power status of all domains.
XSCF> showdomainstatus -a
DID Domain Status
00 Running
01 Running
02 Running
03 Powered Off
|
2. Use the poweroff(8) command to turn off power to the specified domain.
<Example 1> Turn off power to the specified domain.
XSCF> poweroff -d 1
DomainIDs to power off:01
Continue? [y|n] :y
01 : Powering off
*Note*
This command only issues the instruction to power-off.
The result of the instruction can be checked by the
"showlogs power".
<Example 2> Cancel domain power off in progress.
XSCF> poweroff -d 1
DomainIDs to power off:01
Continue? [y|n] :n
<Example 3> Forcibly turn off power to a domain.
XSCF> poweroff -f -d 1
DomainIDs to power off:01
The -f option will cause domains to be immediately reset.
Continue? [y|n] :y
01 :Powering off
*Note*
This command only issues the instruction to power-off.
The result of the instruction can be checked by the
"showlogs power".
|
| Note - If the poweroff(8) command is performed, and the shutdown has completed, then the domain is powered off.
|
|
Caution - IMPORTANT -See the following paragraphs for important information about the domain power-off procedure.
|
- When Oracle Solaris OS of the domain is being booted, the power cannot be turned off. After Oracle Solaris OS booting is completed, execute the poweroff(8) command again.
- When Oracle Solaris OS of the domain is running in single user mode, the power cannot be turned off using the poweroff(8) command. Execute the shutdown(1M) command on the domain.
Note that when Oracle Solaris OS of the domain is running, domain power-off (shutdown -i5, or equivalent) is required.
Also, even if a system abnormality (like a fan or temperature abnormality) is detected while the Oracle Solaris OS is being booted, or the system is running in single user mode, there may be cases where the power cannot be turned off. (An Oracle Solaris OS shutdown is not executed.) In such cases, immediately perform the procedure above.
4.4.5 Sending a Domain Panic Request
1. Use the showdomainstatus(8) command to check the power status of the domain to which a panic instruction is to be issued.
XSCF> showdomainstatus -a
DID Domain Status
00 Running
01 Running
02 Running
03 Running
|
2. Use the reset(8) command to issue a panic instruction to the specified domain.
<Example> Issue a panic instruction to the specified domain.
XSCF> reset -d 0 panic
DomainID to panic:00
Continue? [y|n] :y
00 :Panicked
*Note*
This command only issues the instruction to reset.
The result of the instruction can be checked by the
"showlogs power".
|
4.4.6 Domain Reset
1. Use the showdomainstatus(8) command to check the power status of the domain.
XSCF> showdomainstatus -a
DID Domain Status
00 Running
01 Running
02 Running
03 Running
|
2. Use the reset(8) command to issue a reset instruction to the specified domain.
<Example 1> Issue a domain ID 0 reset instruction.
XSCF> reset -d 0 por
DomainID to reset:00
Continue? [y|n] :y
00 :Reset
*Note*
This command only issues the instruction to reset.
The result of the instruction can be checked by the
"showlogs power".
<Example 2> Issue an XIR reset instruction.
XSCF> reset -d 0 xir
DomainID to reset:00
Continue? [y|n] :y
00 :Reset
*Note*
This command only issues the instruction to reset.
The result of the instruction can be checked by the
"showlogs power".
|
3. Use the showdomainstatus(8) command to check the power status of the domain specified to be reset.
XSCF> showdomainstatus -a
DID Domain Status
00 Booting/OpenBoot PROM prompt
01 Running
02 Running
03 Running
|
| Note - When the mode switch on the operator panel is set to "Service" or auto boot is disabled by the setdomainmode(8) command, automatic boot of the Oracle Solaris OS after the reset instruction is suppressed.
|
| Note - Since the reset(8) command forcibly resets the system, this command may cause a failure in a hard disk drive or other components. Use this command only for the purpose of recovery, such as if the Oracle Solaris OS hangs, and for other limited purposes.
|
4.4.7 Sending a Break Signal to a Domain
1. Use the showdomainstatus(8) command to confirm the domain status.
XSCF> showdomainstatus -a
DID Domain Status
00 Running
01 Running
02 Running
03 Running
|
2. Use the sendbreak(8) command to send a Break signal to the specified domain.
XSCF> sendbreak -d 0
Send break signal to DomainID 0?[y|n] :y
|
3. Confirm ok prompt on the specified domain console.
| Note - To send the break signal to the domain, the domain mode setting is required. When the mode switch on the operator panel is set to Service, the automatic boot and host watchdog functions are suppressed and the break signal is received, regardless of the domain mode settings. For details of the domain mode settings, see Section 2.2.15, Domain Mode Configuration.
|
4.4.8 Air-Conditioning Wait Time Administration
The air-conditioning wait time is intended to prevent the server from performing power-on processing until the room temperature environment is prepared by air-conditioning facilities. Once the air-conditioning wait time is set, the server will start power-on processing after its power is turned on and the set air-conditioning time elapses.
1. Use the showpowerupdelay(8) command to display the air-conditioning wait time (wait time).
XSCF> showpowerupdelay
warmup time : 10 minute(s)
wait time : 20 minute(s)
|
2. Use the setpowerupdelay(8) command to set the air-conditioning wait time. Set the air-conditioning wait time from 0 to 255 (min). The default is "0 min."
<Example> The air-conditioning wait time is set to 15 min.
XSCF> setpowerupdelay -c wait -s 15
|
3. Use the showpowerupdelay(8) command to confirm the setting. Also, to apply the setting, turning on the server power supply.
XSCF> showpowerupdelay
warmup time : 10 minute(s)
wait time : 15 minute(s)
|
4. Confirm whether the setting time is valid when turning on the server power supply the next time, by checking the time from when you perform the power on till when the power supply unit is actually turned on.
4.4.9 Warm-Up Time Administration
The warm-up time is intended to prevent the power supply unit and the fan from running until the power supply environments of peripheral units are prepared after the server starts the power-on processing. Once the warm-up time is set, the OpenBoot PROM will start after the server power supply is turned on, the power-on processing starts, and the set warm-up time elapses.
| Note - The fan in an M3000/M4000/M5000 server is driven at low speed as the server starts the power-on process.
|
1. Use the showpowerupdelay(8) command to display the warm-up time (warmup time).
XSCF> showpowerupdelay
warmup time : 10 minute(s)
wait time : 20 minute(s)
|
2. Use the setpowerupdelay(8) command to set the warm-up time. Set the warm-up time from 0 to 255 (min). The default is "0 min."
<Example> The warm-up time is set to 5 min.
XSCF> setpowerupdelay -c warmup -s 5
|
3. Use the showpowerupdelay(8) command to confirm the setting. Also, to apply the setting, turning on the server power supply.
XSCF> showpowerupdelay
warmup time : 5 minute(s)
wait time : 20 minute(s)
|
4. When turning on the server power supply the next time, please confirm that it takes more time than usually by checking the amount of time it takes from the power on until the time when the first Power On Self Test (POST) start message is displayed.
| Note - Once the air-conditioning time is set, the warm-up time will be valid after the power is turned on and the air-conditioning time elapses.The air-conditioning time and the warm-up time are also valid when the power is turned on at the power recovery after the power failure.
|
|
|
Caution - IMPORTANT- When the power is turned on from the operator panel, the air-conditioning time and warm-up time that you set are ignored. If you have set these times and wish to observe them at startup, perform the poweron(8) command.
|
4.4.10 Shutdown Wait Time Administration
The shutdown wait time administration is a setting to delay the shutdown start by specifying the shutdown start time when a power failure has occurred in the system with the UPS.
1. Use the showshutdowndelay(8) command to display the shutdown wait time.
XSCF> showshutdowndelay
UPS shutdown wait time : 500 second(s)
|
2. Use the setshutdowndelay(8) command to set the shutdown wait time. Set the shutdown wait time from 0 to 9999 (sec). The default is "10 sec."
<Example> The shutdown wait time is set to 600 sec.
XSCF> setshutdowndelay -s 600
|
4.4.11 Dual Power Feed Administration
The dual power feed is a type of power feed for high-reliability systems that contain dual lines to the power supply. If one line stops, the other line does not stop and enables the system to continue operation. This capability can be enabled or disabled using an XSCF Shell command. This setting is done by FEs.
| Note - The ability to enable and disable the dual power feed or display its current status is available on M3000/M4000/M5000 servers only. However, the dual power feed mode cannot be used with 100V power on M4000/M5000 servers. When the optional power cabinet for dual power feed is connected on M8000/M9000 servers, it automatically configures the dual power feed mode. For details about the setting the dual power feed, see the Installation Guide for your server.
|
1. Use the showdualpowerfeed(8) command to display the current setting status of the dual power feed.
XSCF> showdualpowerfeed
Dual power feed is disabled.
|
2. Use the setdualpowerfeed(8) command to enable or disable the dual power feed of this system.
<Example 1> Enabling the dual power feed.
XSCF> setdualpowerfeed -s enable
disable -> enable
NOTE: Dual power feed will be enabled the next time the platform is powered on.
<Example 2> Disabling the dual power feed.
XSCF> setdualpowerfeed -s disable
enable -> disable
NOTE: Dual power feed will be disabled the next time the platform is powered on.
|
3. Confirm the new setting, and if it is correct, turn off the input power and then turn on to apply the specified configuration. When you enabled the dual power feed mode, you can apply the configuration by executing the rebootxscf(8) command.
XSCF> showdualpowerfeed
disable -> enable
NOTE: Dual power feed will be enabled the next time the platform is powered on.
|
4. Confirm whether the setting is valid after turning off/on the input power.
XSCF> showdualpowerfeed
Dual power feed is enabled.
|
4.5 Identifying the Location of the System
When more than one same type of system is installed in the same area, it may be difficult to locate the target system. You can easily find target machine, even when it does not have any faulty components, by using the XSCF Shell showlocator(8) command and looking for the blinking the CHECK LED on the operator panel.
1. Use the showlocator(8) command to display the current status of the CHECK LED.
XSCF> showlocator
Locator LED status: Off
|
2. Use the showlocator(8) command to blink or reset the CHECK LED.
<Example 1> Blink the CHECK LED.
XSCF> setlocator blink
<Example 2> Reset the CHECK LED.
XSCF> setlocator reset
|
3. Use the showlocator(8) command to display the state of the CHECK LED.
XSCF> showlocator
Locator LED status: Blinking
|
4.6 Managing Fault Degradation4.6.1 Displaying the Degraded Component
The status of a faulty or degraded component, or a part of such component, can be displayed by using the following methods:
Use the showstatus(8) command to display the unit status. An asterisk (*) is attached to a unit in abnormal status.
<Example 1> The memory board and memory on the motherboard unit (MBU) are degraded due to failure.
XSCF> showstatus
MBU_B Status:Normal;
* MEMB#1 Status:Deconfigured;
* MEM#3B Status:Deconfigured;
<Example 2> The CPU is degraded due to the effect of the crossbar unit (XBU) being degraded.
XSCF> showstatus
MBU_B Status:Normal;
* CPUM#1-CHIP#1 Status:Deconfigured;
* XBU_B#0 Status:Degraded;
<Example 3> No degraded component is found.
XSCF> showstatus
No failures found in System Initialization.
|
The meaning of each component status is as follows:
|
Faulted
|
The component is faulty and not operating.
|
|
Degraded
|
The component is operating. However, either an error has been detected or the component is faulty. As a result, the component might be operating with reduced functionality or performance.
|
|
Deconfigured
|
As a result of another component’s faulted or degraded status, the component is not operating. (The component itself is not faulted or degraded.)
|
|
Maintenance
|
The corresponding component is under maintenance. A deletefru(8), replacefru(8), and addfru(8) operation is currently underway.
|
|
Normal
|
The component is operating normally.
|
4.6.2 Clearing the Fault/Degradation Information
The information on a faulty or degraded component is cleared when the component is replaced. For a component replacement, please contact a field engineer.
4.7 Changing the Time
The time of the server is based on the XSCF time. Time can be displayed or set to local time or UTC. For details on displaying or setting the system time, see Chapter 2.
4.8 Switching the XSCF Unit
In some cases, such as when an error occurs in the LAN route of the XSCF Unit on the active side in a system in which the XSCF Unit is redundantly configured, it may be necessary to switch the active side over to the standby side.
The procedure for switching the XSCF Unit status from standby to active is as follows:
1. Log in the XSCF Unit on the standby side.
2. Use the switchscf(8) command to switch the XSCF Unit from standby status to active status.
| Note - If possible, confirm that the ACTIVE LED states changes on the front panels of both XSCF Units. Execute the switchscf(8) command only on one side (active side or standby side) of the XSCF Units to automatically switch active/standby status of the other XSCF Unit.
|
For specifying an option in the switchscf(8) command, see the XSCF Reference Manual.
Processing Continued at XSCF Reset or Failover
In case an XSCF reset or failover was generated while the following processes are executing, the process will be continued:
- Domain power-on process
- Domain power-off process
- DR function
|
|
Caution - IMPORTANT- An XSCF reset or failover might prevet the above setting operation from completing. If a reset or failover occurs during the operation, log in to the active XSCF to determin if the operation succeeded. If not, try it again. For details on DR, see the Dynamic Reconfiguration User’s Guide.
|
4.9 Displaying State of an External I/O Expansion Unit and Administration
This section describes the management overview of an External I/O expansion unit connected to the server, components in the External I/O Expansion Unit such as I/O boards, link cards, and power supply units (PSUs), and downlink cards mounted in PCI slots in the server, and cards that contain Energy Storage Modules (ESM) and are attached to the host system.
| Note - For the hardware configuration of an External I/O Expansion Unit, see the External I/O Expansion Unit Installation and Service Manual or the Service Manual for your server. For details and examples of use of commands, see the XSCF Reference Manual and the ioxadm(8) man page.
|
TABLE 4-4 lists terms used in External I/O Expansion Unit administration.
TABLE 4-4 External I/O Expansion Unit Administration Terms
|
Term
|
Description
|
|
Host path
|
Device path. A device name and device number are used to represent the layer location of a component in the component layer structure. (Example: IOU#1-PCIE#4)
|
|
Downlink card path
|
A downlink card that is mounted in a PCI slot in an I/O unit of the server and connected to an External I/O Expansion Unit. An External I/O Expansion Unit is connected to one or two downlink cards. A downlink card path represents the layer location indicating which downlink card is connected to the External I/O Expansion Unit in the layer structure. (Example: IOU#1-PCIE#2)
|
TABLE 4-5 lists setting items and the corresponding shell commands.
TABLE 4-5 External I/O Expansion Unit Administration
|
Item
|
Description
|
Shell Command
|
Remarks
|
|
Display list
|
Displays a list of External I/O Expansion Units and cards in the host slot is identified by the host_path to the card. The following is displayed:
- Set External I/O Expansion Unit numbers and downlink card paths
- Exernal I/O Expansion Units, I/O boards, link cards (Note 1), downlink cards, power supply unit types, firmware versions, serial numbers, part numbers, and states
|
ioxadm
|
External I/O Expansion Unit numbers are set in two ways: specifying last four digits of serial numbers such as iox@nnnn, and specifying instance numbers such as ioxn.
|
|
Display environment information
|
Displays the status of the environment of the specified External I/O Expansion Unit or downlink card as sensor measurement values. Also displays the environmentals of a FRU in an I/O Expansion Unit or a card in a host slot.
The following is displayed:
- Current (A)
- Voltage (V)
- Fan speed (RPM)
- Temperature (C)
- LED state
- SWITCH
|
ioxadm
|
Also, the preciseness is displayed together with the sensor measurement values.
|
|
Display/set locator LED (Note 2)
|
Displays and sets the locator LED state for individual components in the specified External I/O Expansion Unit.
Each locator LED is in one of the following states:
Any of the following locator LED states can be set:
- Enabled (on)
- Disabled (off)
|
ioxadm
|
Only one locator LED can be enabled or disabled at a time in an External I/O Expansion Unit.
|
|
Power on/off
|
Turns on or off power to the specified I/O board or power supply unit.
Note: To forcibly disconnect an IO board belonging to a domain, use the -f option.
|
ioxadm
|
Even after the power switch is set to off, LEDs and fans continue operating as long as they are supplied with power.
|
|
Display/set runtime of card with ESM
|
Displays and clears runtime of the card with ESM.
|
ioxadm
|
|
| Note - (1) Also called uplink cards. They are mounted on I/O boards.
|
| Note - (2) A locator LED that indicates a location. The names of locator LEDs depend on the corresponding components. For the External I/O Expansion Unit and LED types and the descriptions of components contained in an External I/O Expansion Unit, see the External I/O Expansion Unit Installation and Service Manual for your server.
|
Displaying a List of External I/O Expansion Units, I/O Boards, Link Cards, and Power Supply Units or Displaying Their Environment Information
Use the ioxadm(8) command to display a list of External I/O Expansion Units and downlink card paths and to display information for each component.
<Example 1> Display a list of External I/O Expansion Units and downlink cards
XSCF> ioxadm list
IOX Link 0 Link 1
IOX@5309 IOU#2-PCI#2 IOU#3-PCI#1
IOX@A3B5 - IOU#1-PCI#1
- - IOU#2-PCI#1
<Example 2> Display a list of External I/O Expansion Units, I/O ports, link cards, and power supply units
XSCF> ioxadm -v list IOU#1-PCI#1
Location Type FW Ver Serial Num Part Num State
IOX@A3B5 IOX 1.4 CP0001 5016937-01 On
IOX@A3B5/PS0 A195 - PS0001 3001701-02 On
:
<Example 3> Display a card using host_path in verbose mode with headers suppressed
XSCF> ioxadm -p -v list IOU#1-PCI#2
IOU#1-PCI#2 F20 - 000004 5111500-01 On
<Example 4> Display environment information based on sensor measurements
XSCF> ioxadm env -te IOX@A3B5
Location Sensor Value Res Units
IOX@A3B5/PS0 T_AMBIENT 28.000 1.000 C
IOX@A3B5/PS0 V_ISHARE 0.632 0.040 V
IOX@A3B5/PS0 I_DC 2.316 0.289 A
IOX@A3B5/PS0 S_FAN_SET 4500.000 300.000 RPM
:
|
Displaying and Setting the Locator LED State of Each Specified Component in an External I/O Expansion Unit
Use the ioxadm(8) command to display or set the locator LED state of the specified component.
<Example 1> Display the locator LED states of an External I/O Expansion Unit and components.
XSCF> ioxadm locator iox@12B4
Location Sensor Value Res Units
IOX@12B4 LOCATE Fast - LED
IOX@12B4/PS0 SERVICE Fast - LED
<Example 2> Set the locator LED state of PSU0 to on.
XSCF> ioxadm locator on iox@12B4/ps0
Location Sensor Value Res Units
IOX@12B4 LOCATE Fast - LED
IOX@12B4/PS0 SERVICE On - LED
|
Turning On or Off Power to an I/O Board or Power Supply Unit
Use the ioxadm(8) command to display, turn on or off power to the specified component.
<Example 1> Display the PSU states of an External I/O Expansion Unit and components.
XSCF> ioxadm -v list IOX@12B4
Location Type FW Ver Serial Num Part Num State
IOX@12B4 IOX 1.0 XCX033 5016937-03 On
IOX@12B4/PS0 A195 - T01056 3001701-03 On
IOX@12B4/PS1 A195 - T01074 3001701-03 On
IOX@12B4/IOB0 PCIX - XX00A3 5016938-04 On
IOX@12B4/IOB0/LINK OP 1.3 XF00X8 5017040-03 On
<Example 2> Turn off power to I/O board 0.
XSCF> ioxadm poweroff iox@12B4/iob0
<Example 3> Turn on power to I/O board 0 again.
XSCF> ioxadm poweron iox@12B4/iob0
|
Displaying and Clearing the Card with ESM
Use the ioxadm(8) command to display and clear runtime of the card with ESM.
<Example 1> Display runtime of card with ESM using verbose output.
XSCF> ioxadm -v lifetime IOU#0-PCI#1
NAC Total Time On (% of life) Warning Time Fault Time
IOU#0-PCI#1 1052370 100 1041120 1051200
<Example 2> Clear runtime of card with ESM, show runtime is cleared.
XSCF> ioxadm lifetime -z IOU#0-PCI#1
XSCF> ioxadm lifetime IOU#0-PCI#1
NAC Total Time On (% of life)
IOU#0-PCI#1 0 0
|
| SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide
|
821-2797-10
|
   
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.