Sun Fire V20z and Sun Fire V40z Servers Release Notes Table Of ContentsPrevious ChapterNext ChapterNoIndex

C H A P T E R  3
NSV (SP and BIOS) Changes By Version

This chapter lists the features, known issues, and workarounds in the latest major NSV versions.

3.1 NSV Release 2.4.0.28

3.1.1 New Features and Resolved Issues

NSV release 2.4.0.28 is a maintenance release that contains a fix for the chipkill function issue. Release 2.4.0.28 contains no other changes, and is provided solely for the resolution of this issue. For more information, see Section 1.2.1, BIOS Chipkill Function Not Working.

3.2 NSV Release 2.4.0.26

3.2.1 New Features

NSV 2.4.0.18 includes the following hardware and software features:


TABLE 3-1 NSV 2.4.0.26 Components

Component

Change or Additions

Red hat Enterfprise Linux 4

Update 4, 2.6 Kernel (32-bit & 64-bit)

NSV

Version 2.4.0.26

SP Base Software

Version 2.4.0.18

Diagnostics Software

Version 2.4.0.14


3.2.2 Resolved Issues

The following known issues are resolved in NSV 2.4.0.26


Component

Issue

SP/BIOS

Added Service Processor command to enable changing the network port that the POCI driver uses.

Software

Fixed issue with POCI driver with newer 64-bit Solaris release.


3.3 NSV Release 2.4.0.18

3.3.1 New Features

NSV 2.4.0.18 includes the following hardware and software features:


TABLE 3-2 NSV 2.4.0.18 Components

Component

Change or Addition

Red Hat Enterprise Linux 3

Update 8, 2.4 Kernel (64-bit) support

SUSE Linux Enterprise Server 10

2.6 Kernel (64-bit)

AMD Opteron Processor Support

Sun Fire V40z Server:

  • AMD Opteron 890, E-6

NSV

Version 2.4.0.18

4300 (V40z) Platform BIOS

Version 2.35.3.2

SP Base Software

Version 2.4.0.14

Diagnostics Software

Version 2.4.0.14


3.3.2 Resolved Issues

The following known issues are resolved in NSV 2.4.0.18.


TABLE 3-3 Issues Resolved in NSV 2.4.0.18

Component

Issue

SP

Remote console access to LSI MegaRAID firmware fixed; delete entry function fixed.

Diagnostics

Resolved I2C conflict causing erroneous and faulty DIMM topology gathering.

 

Resolved high failure when 4 GB DIMM installed on Sun Fire V40z with chassis 380-1378.

 

Resolved triple faults when diagnostics with ECC encounter DIMM with taped pin.

Other

Removed ssh version 1 from service processor.

 

Resolved diagnostics memory tests giving false error indications with 4 GB DIMMs.

 

Delivered the proper NVData image for Sun Fire V40z with chassis 380-1010 and 380-1206 onboard LSI 1020/1030 controller.

BIOS

Added support for Opteron 890 CPUs.

 

LSI MegaRAID card qualified but remote console feature is planned in future release.

 

Added SLES 10 support for POCI/TDU.

 

Implemented AMD errata #169 for Sun Fire V40z.

 

Resolved bad memory not always detected when in upper 64-bits of bank or causes hang in lower 64 bits.

 

With certain configuration including a megaRAID card and 875 CPUs, unable to run diagnostics.

 

Server does not post with a MegaRAID card installed.


3.4 NSV Release 2.4.0.12

3.4.1 New Features

NSV 2.4.0.12 includes the following hardware and software features:


TABLE 3-4 NSV 2.4.0.12 Components

Component

Change or Addition

RoHS 5 compliance

BIOS supports RoHS compliant Sun Fire V40z Servers

Red Hat Enterprise Linux 3

Update 7, 2.4 Kernel (32-bit and 64-bit) support

Red Hat Enterprise Linux 4

Update 3, 2.6 Kernel (32-bit and 64-bit) support

SUSE Linux Enterprise Server 9

Support for SP3, 2.6 Kernel (64-bit)

AMD Opteron Processor Support

Sun Fire V40z Server:

  • AMD Opteron 856, E-4
  • AMD Opteron 885, E-6

NSV

Version 2.4.0.12

2100 (V20z) Platform BIOS

Version 1.35.2.2

4300 (V40z) Platform BIOS

Version 2.35.2.2

SP Base Software

Version 2.4.0.10

Diagnostics Software

Version 2.4.0.6


3.4.2 Resolved Issues

The following known issues are resolved in NSV 2.4.0.12.


TABLE 3-5 Issues Resolved in NSV 2.4.0.12

Component

Issue

Software

Slow DIMMs in Node 0 cause Multi-Bit ECC Error due to initialization not completing

Drivers: TDU

The tdulog naming convention changed in version 2.3.0.11. This is corrected in version 2.4.0.12.

BIOS

CD diagnostics sporadically reboots if a bad DIMM is encountered.

BIOS

IPMI KCS code might hang if BMC (PIP) stops responding. There were inadequate provisions for time out or failure handling in the KCS stack. This usually appeared as a hang at postcode D9.

BIOS

Command used to instruct BIOS to PXE boot works only if the boot image is on the network connected to eth0. If the image is available using eth1, the server boots from the local disk.


3.5 NSV Release 2.4.0.8

3.5.1 New Features

This release includes the following software features:

3.5.2 Resolved Issues

TABLE 3-7 lists issues resolved in the NSV 2.4.0.8 release.


TABLE 3-7 Issues Resolved in NSV 2.4.0.8

Component

Issue

BIOS

Customers configuring Sun Fire V40z Servers with one or more Endace DAG 4.3GE cards must update to NSV 2.4.0.8.

BIOS

Deliver the proper NVData image for the V40z onboard LSI 1020/1030 controller.

Diagnostics

Some V40z (Rev. E) super FRUs fail to load platform diagnostics if a daughtercard is not installed.

Service Processor

Software inventory is reporting “factory installed,” in error.

Diagnostics

Memory diags sometimes reports incorrect configuration or cannot identify a failing DIMM.

Service Processor

Value for MIB entry for SP-SP-MIB::spPort80 is always zero. Enable the appropriate value.

BIOS

Set the Maximum Outstanding Split Transactions (MOST) to 1 in PCI configuration space, to work-around LSI 53C1020-B2 Device Errata Listing 865, item 10.


3.6 NSV Release 2.4.0.6

The following is a list of the features and fixes contained in BIOS v1.34.4.2 (Sun Fire V20z Server) and v2.34.4.2 (Sun Fire V40z Server), as well as the service processor (SP) firmware v2.4.0.6.

3.6.1 Features in NSV 2.4.0.6

Release 2.4 features AMD Opteron processors that include AMD PowerNow! Technology with Optimized Power Management. This feature allows IT and workstation customers to decrease overall power consumption by enabling optimization of performance on demand. It also aids in platform investment protection for demanding enterprise server environments by lessening strain on data center cooling and ventilation systems.

This new option was added in the BIOS Configuration, Advanced menu. If enabled, it reserves resources for Hot Plug PCI-X slots. If Disabled, it allocates resources only for cards that were installed at boot. This option applies only to Sun Fire V40z Servers. The default is Disabled.

Release 2.4 includes a CMOS Save-Restore feature that saves any CMOS setting changes you initiate for boot order, time/date, and so on. If the CMOS becomes corrupted, the saved settings are restored rather than the default settings.

3.6.2 Resolved Issues in NSV 2.4.0.6

TABLE 3-8 lists issues resolved in the NSV 2.4.0.6 release.


TABLE 3-8 Issues Resolved in NSV 2.4.0.6

Component

Issue

System Management: IPMI

For ICTS SDR/sensor tests:

  1. Return data that specifies that unreadable sensors have no data, rather than IPMI_ILLEGAL_COMMAND_FOR_SENSOR.
  2. Return IPMI_ILLEGAL_COMMAND_FOR_SENSOR instead of IPMI_SENSOR_DATA_NOT_PRESENT if a request is made for a sensor that does not exist.

System Management: SM Commands

Commands for setting community strings show incorrect help message.

System Management: SM Commands

The ipmi get sel command should understand manufacturer ID and display sel record type, consistent with other data.

System Management: IPMI

Node Busy message is not returned after the set command, during time when the command is executing.

System Management: SNMP

In SNMP MIB, SP inventory install dates display “Uninstalled.”

System Management: SM Commands

The ipmi get sel command should analyze timestamp before converting it to time.

System Management: SM Commands

The ipmi get sel command does not display all sel entries appropriately.

System Management

Cannot change DHCP setting with same IP address.

System Management: SM Commands

Support forced option for platform update bios command when OS is in “on” state.

System Management: IPMI

Add set/get system information commands.

System Management: IPMI

The ipmi get supported cipher suites should address specification clarification.

System Management: IPMI

The dates returned from the get sel info command “Most recent addition timestamp” and “Most recent deletion timestamp” are not persistent across SP boots.

System Management: Op Panel Executive

When the SP boots, if it is already configured for DHCP and the network is unplugged or non-functional, the SP will become unusable when Opexec times out and resets the networking to DHCP mode.

System Management

Add sp commands to modify SNMP community string. The sp snmp set/get community string commands were added.

System Management: SM Commands

If /pstore is filled to near-capacity, the access add trust SM command gives no indication of a failure, even though an event warning displays: “Error persisting user information. It is likely that the persistent filesystem is full.”

System Management: SM Commands

The ipmi get sel command does not display all sel entries appropriately.

System Management: Op Panel

Op panel server menu does not show reboot option when going in reverse direction.


3.6.3 Known Issues in NSV 2.4.0.6

3.6.3.1 HPET Timer Off Might Cause System Clock to Lose Ticks

When the HPET timer is off, the system clock might lose ticks. This loss of timer ticks might result in timing errors in the kernel and in user applications. Symptoms might include timers that prematurely time out and the time of day clock appearing to behave erratically. The HPET timer must be enabled when using the PowerNow! feature on a SMP kernel.

3.6.3.2 Incorrect Sensor Number Used in BIOS for System Firmware Progress SEL Entries

BIOS does not use the correct sensor number when generating System Firmware Progress SEL entries. If certain errors occur during system boot, such as keyboard or floppy disk errors, the system BIOS generates a System Firmware Progress SEL entry and send it to the service processor. Currently the BIOS incorrectly uses a sensor number of 0x00 when creating those SEL entries.

3.6.3.3 BIOS Update Failure

Updating the BIOS might fail due to an error in transmitting the file. If this occurs, retry the update.

 



Sun Fire V20z and Sun Fire V40z Servers Release Notes 819-1771-25 Table Of ContentsPrevious ChapterNext ChapterNoIndex

Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.