This appendix contains the following sections:
The commands described in this appendix are specific to Netra CP3260 blade server designed by Sun Microsystems. The Internet Assigned Numbers Authority (IANA) number assigned to Sun Microsystems is 42.
Refer to http://www.iana.org/assignments/enterprise-numbers for more information about IANA number assignments.
The netfunction (NetFn) used for these commands is 0x2E, which is the OEM netfunction as defined in the IPMI specification. For this netfunction, the first three data bytes in the request packet must be this IANA number and the first three bytes in the response packet following the completion code are the IANA number. For Sun ATCA node boards, these three bytes are 00 00 2A.
B.1 Get Version Command
Get Version returns the IPM controller (IPMC) firmware version and Standby CPLD version. Bytes 8, 9, and A are reserved for future use.
|
Command
|
NetFn
|
Opcode
|
Reference
|
|
Get_Version
|
0x2E (OEM)
|
0x80
|
- -
|
TABLE B-1 Get Version Command Data Bytes
|
Type
|
Byte
|
Data Field
|
|
Request data
|
Byte1
|
00
|
|
Byte2
|
00
|
|
Byte3
|
2A
|
|
Response data
|
Byte1
|
Completion code:
00 = OK
C1 = Command not supported
CC = Invalid data in request
(Refer to IPMI specification for more completion codes)
|
|
Byte2
|
00
|
|
Byte3
|
00
|
|
Byte4
|
2A
|
|
Byte5
|
CPLD version
|
|
Byte6
|
REV1 byte of IPMC firmware
|
|
Byte7
|
REV2 byte of IPMC firmware
|
|
Byte8
|
Reserved for future use (ignore)
|
|
Byte9
|
Reserved for future use (ignore)
|
|
ByteA
|
Reserved for future use (ignore)
|
Example (Terminal Mode):
[B8 00 80 00 00 2A] <-------Request
[BC 00 80 00 00 00 2A 02 02 00 00 00 00] <----Response
- The IPMC version is read as:
lower nibble of REV1 . high nibble of REV2 . low nibble of REV2
In the preceding example, the IPMC version is 2.0.0.
- The CPLD version is read as:
-> lower nibble of CPLD version byte
In the example, the CPLD version is 2.
B.2 Get RTM Status Command
You can use the Get RTM Status command to detect the presence of a rear transition module (RTM) in the system.
|
Command
|
NetFn
|
Opcode
|
Reference
|
|
Get_RTM_Status
|
0x2E (OEM)
|
0x88
|
CPLD Specification
|
TABLE B-2 Get RTM Status Command Data Bytes
|
Type
|
Byte
|
Data Field
|
|
Request data
|
Byte1
|
00
|
|
Byte2
|
00
|
|
Byte3
|
2A
|
|
Response data
|
Byte1
|
Completion code:
00 = OK
C1 = Command not supported
CC = Invalid data in request
|
|
Byte2
|
00
|
|
Byte3
|
00
|
|
Byte4
|
2A
|
|
|
Byte5
|
RTM presence
Bits 7 to 1 = 0
Bits 0 = RTM presence (0 = RTM not detected, 1 = RTM detected)
|
Example (Terminal Mode):
[B8 00 88 00 00 2A] <------Request
[BC 00 88 00 00 00 2A 01] <------Response
B.3 Solaris OS Graceful Shutdown Commands
Users can change the graceful shutdown time out of Solaris OS with an IPMI command executed from ShMM or a user application. Note that this setting is not persistent; the Solaris FSM will overwrite it after every Solaris OS boot.
SUNWctfsm is the Solaris FSM for ATCA graceful shutdown and reboot. For installation and requirements, refer the README file included in the release package and the Sun Netra CP3260 Blade Server Product Notes (820-0455).
The commands and parameters are described in the following table.
TABLE 1 Solaris OS Graceful Shutdown Parameters in /etc/fsmd.conf
|
Parameter
|
Description and Parameters
|
|
GS_SHUTDOWN_TIMEOUT
|
Sets the payload graceful shutdown timeout in increments of 100 milliseconds. The legal value range is from 0 to 0xffff (0 second to 6553 seconds).
The default value is 1200, which is 120 seconds. This 1200 will overwrite the default value 300 in IPMC.
Solaris might panic during graceful shutdown if this parameter value is too short. Conversely, if this value is too long, the shutdown could take too long. See Note that follows this table.
|
|
GR_COMPLETION_NOTICE
|
Determines if Solaris FSM will send a reboot succeed notice to IPMC. The legal values are yes and no.
The default value is no. IPMC might or might not support/use it.
|
|
GR_TIMER_DISARM
|
Determines if Solaris FSM will disarm graceful reboot timer. The legal values are yes and no.
The default value is no. Set to yes only if the blade server’s firmware has no graceful reboot support.
|
Any parameter changes you make will become effective only after you execute the Solaris command svcadm restart fsm.
| Note - As of the R3U2 release, Netra CP3260 sysfw 7.2.1 has graceful shutdown support.
|
| Note - To use the graceful shutdown effectively, users must determine a component’s shutdown time “cost,” which depends on hardware, software, and configuration. For example, the default 120 seconds could be too short for a Sun Netra CP3260 blade server with a heavy I/O configuration. Conversely, it could be too long for a Sun Netra CP3220 blade server. Ignorance of the shutdown time could cause a panic during graceful shutdown.
|
For more information, refer to the following documentation:
- Netra CT 900 Server Administration and Reference Manual (819-1177) for ShMM commands.
- Netra CT 900 Software Developer’s Guide (819-1178) for IPMI commands.
Even if you are using a third-party chassis, the commands and options apply, and these documents are available online:
http://docs.sun.com/app/docs/prod/n900.srvr#hic
B.4 Send Sensor State Command
Send Sensor State is used by the firmware progress sensor or any other sensor that intends to send sensor states to the IPM controller (IPMC). The IPMC uses this information to put a sensor in the correct state and send the event data to the system event log.
|
Command
|
NetFn
|
Opcode
|
Reference
|
|
Get_Version
|
0x2E (OEM)
|
0x80
|
- -
|
TABLE B-3 Send Sensor State Command Data Bytes
|
Type
|
Byte
|
Data Field
|
|
Request data
|
Byte1
|
00
|
|
|
Byte2
|
00
|
|
|
Byte3
|
2A
|
|
|
Byte4
|
Sensor type byte
Indicates event class or type of sensor that generates the event message. (Refer to IPMI specification for sensor type codes.)
|
|
|
Byte5
|
Sensor # (optional); Write to 0
Unique number representing the sensor within the management controller that generates the event message. The BIOS, OBP, ILOM, and OS does not have to know and send the sensor number for the sensors that are maintained and reported by the IPMC.
Reserved for future use.
|
|
|
Byte6
|
EventDir | EventType
- 1 bit for EventDir, which indicates the event transition direction. A value of 0 means assertion event; a value of 1 means deassertion event.
- 7 bits for EventType, which indicates the type of threshold crossing or state transition (trigger) that produces the event. Encode using the Event/Reading Type code. (Refer to IPMI specification for type codes.)
|
|
|
Byte7
|
Sensor offset
Tells the sensor generic or sensor specific offset as defined in the IPMI specification. IPMC uses this data to define the state of the sensors. (Refer to the IPMI specification.)
|
|
|
Byte8
|
Event Data 1
Represents the remainder of the event message data according to the class of the event type for the sensor (threshold, discrete, or OEM). (Refer to the IPMI specification.)
|
|
|
Byte9
|
Event Data 2
Represents the remainder of the event message data according to the class of the event type for the sensor (threshold, discrete, or OEM). (Refer to the IPMI specification.)
|
|
|
Byte10
|
Event Data 3
Represents the remainder of the event message data according to the class of the event type for the sensor (threshold, discrete, or OEM). (Refer to the IPMI specification.)
|
|
|
Byte11
|
Reserved for future use. (Write zero)
|
|
|
Byte12
|
Reserved for future use. (Write zero)
|
|
Response data
|
Byte1
|
Completion code:
00 = OK
C1 = Command not supported
CC = Invalid data in request
(Refer to IPMI specification for more completion codes)
|
|
|
Byte2
|
00
|
|
|
Byte3
|
00
|
|
|
Byte4
|
2A
|
| Sun Netra CP3260 Blade Server User’s Guide
|
820-0457-11
|
    |
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.