C H A P T E R  3

Software Configuration

This chapter provides procedures and information about configuring the software.

This chapter contains the following topics:


3.1 Operating Systems

The Sun Netra CP3220 blade server has been tested for compatibility with the following operating systems:

For information on the WindRiver Linux operating system, see the documentation that came with the WindRiver operating system.

For information on versions of the Solaris OS, including installation, see the appropriate Solaris Documentation Collection at the Sun Documentation web site at:

http://docs.sun.com


3.2 Software Updates

Software updates and support information for the Sun Netra CP3220 blade server, Sun Netra CP32x0 ARTM, and the Sun Netra CT 900 system can be found at the Sun Download Center:

http://www.sun.com/download

For information on your specific configuration, contact your local Sun Services representative.

http://www.sun.com/service/contacting/solution.html


3.3 SunVTS Software



Note - The Sun Validation Test Suite (SunVTS software) runs on the Solaris OS only. There are similar test suites available for the Linux operating systems.


The SunVTS software is a comprehensive software suite that tests and validates the Sun Netra CP3220 blade server by verifying the configuration and function of most hardware controllers and devices on the blade server.

SunVTS software is used to validate a system during development, production, inspection, troubleshooting, periodic maintenance, and system or subsystem stressing. SunVTS software can be tailored to run on various types of machines, ranging from desktops to servers with modifiable test instances and processor affinity features.

You can perform high-level system testing by using the appropriate version of SunVTS software. For detailed information on SunVTS software support and downloads, refer to the following web site:

http://www.sun.com/oem/products/vts/

You will be prompted for your Sun Online Account name and password.

Ensure that the SunVTS software version is compatible with the Solaris OS being used. You can find information about the SunVTS software version installed on your system by viewing the content of the .version file:


# cat /opt/SUNWvts/bin/.version

To obtain SunVTS documentation, contact your local Customer Service representative, field applications engineer, or system support engineer.



Note - For security reasons, only a superuser is permitted to run SunVTS software. Installation and starting instructions are included with the software when it is downloaded.



3.4 Configuring Sun Netra CP3220 For 1GbE or 10GbE Switches

The extended fabric on the Sun Netra CP3220 blade server is capable of operating at either 1 Gbps or 10 Gbps. The Sun Netra CP3220 can be used in the Sun Netra CT 900 server with either the Sun Netra CP3240 10-GbE switch or the Sun Netra CP3140 1-GbE switch. Therefore it is important that the driver configuration file be modified accordingly.

The network interface driver configuration file, nxge.conf, for the extended fabric ports of the Sun 10GbE ASIC might need to be modified to employ the proper switch and ARTM configurations. The nxge.conf file is located in the /platform/i86pc/kernel/drv directory. The following examples show the proper entries for each switch configuration.

Example 1: If both network interface ports are routed to Sun Netra CP3240 switches in Slot 7 and Slot 8, the nxge.conf file should have the following entries:


name = "pciex108e,abcd" parent = "/pci@0,0/pci10de,377@f" unit-address ="0" phy-type = "xgsd"; 
name = "pciex108e,abcd" parent = "/pci@0,0/pci10de,377@f" unit-address ="0,1" phy-type = "xgsd"; 

Example 2: If both network interface ports are routed to Sun Netra CP3140 switches in Slot 7 and Slot 8, the nxge.conf file should have the following entries:


name = "pciex108e,abcd" parent = "/pci@0,0/pci10de,377@f" unit-address ="0" phy-type = "gsd"; 
name = "pciex108e,abcd" parent = "/pci@0,0/pci10de,377@f" unit-address ="0,1" phy-type = "gsd"; 


3.5 Configuring Alternate OOS LED Behavior

Administrators and service technicians can change the default behavior of the out-of-service (OOS) LED through the IPMC by using an LED1 control bit. This bit is available only on the Sun Netra CP3220 blade server.

Use the set and get IPMC control byte IPMI commands, which are the same commands used to control the Green OK LED, to change the default OOS LED behavior to the following:

The alternate behavior remains enabled after firmware upgrades and IPMC cold, warm, and hard resets. Also, it remains enabled after firmware downgrades, as long as the version being downgraded to supports this feature.

When blade servers are shipped from manufacturing, they are set to the default LED behavior. The default OOS LED behavior is as follows:


procedure icon  Displaying Configuration of OOS LED Behavior

Use the following command to display the current configuration of OOS LED behavior.


Command

NetFn

Opcode

Get IPMC Control Bits

0x2E

0xE8


Data Bytes


Type

Byte

Data Field

Request Data

1

00

 

2

00

 

3

2A

Response Data

1

Completion Code:

[00] OK

[C1] Command not supported

[CC] Invalid data in request

(Refer to IPMI specification for more completion codes)

 

2

00

 

3

00

 

4

2A

 

5

IPMC control bit:

  • Bit 0 : Green LED control bit.
  • Bit 1 : LED1 control bit.
  • Bits 2 to 7: Reserved for future use.


procedure icon  Setting Configuration of OOS LED Behavior

Use the following command to set the configuration of OOS LED behavior.


Command

NetFn

Opcode

Set IPMI Control Bits

0xE9

0xE9


Data Bytes


Type

Byte

Data Field

Request Data

1

00

 

2

00

 

3

2A

 

4

Control byte.

Bit 0 = LED 2 (Green LED) control bit:

  • 1 = IPMC controls green LED.
  • 0 = IPMC does not control green LED.

Bit 1 = LED1 (Amber/Red LED) control bit.

  • 1 = IPMC controls LED1 for default behavior.
  • 0 = IPMC does not control LED1.

Bits 2 to 7 = Reserved for future use. Write as 1s. (See Note.)

Response Data

1

Completion Code:

[00] OK

[C1] Command not supported

[CC] Invalid data in request

(Refer to IPMI specification for more completion codes)

 

2

00

 

3

00

 

4

2A




Note - If an attempt is made to write 0 to any reserved bit (2 to 7), IPMC will reject the command with completion code 0xCC.