Sun Fire E25K Server
 
Sun Fire 12K Server
 
Sun Fire 15K Server
 
Sun Fire E20K Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 
_Old GCS Categories>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Goal

The dynamic reconfiguration (DR) feature on the Sun Fire[TM] 12K/15K/20K/25K servers enables you to perform hardware configuration changes to a live domain that is running the Solaris[TM] Operating System without causing machine downtime.

This article discusses a known condition with regards to DR operations on Sun Fire 12K/15K/20K/25K servers arising from portid conflicts introduced as a result of certain third party device drivers.

Solution

You can execute DR operations from the system controller (SC) by using the SMS commands: addboard(1M), moveboard(1M),deleteboard(1M), and rcfgadm(1M).

Alternatively, the same DR operations can also be initiated from the domain OS environment via the cfgadm(1M) command.
The DR attach/detach operations' failure signature associated with such events is as follows:

A. Failed DR attach operations

The above DR attach failure event is further marked by the following message logs in the domain OS environment:

B. Failed DR detach operations

The above DR detach failure event is further marked by the following message logs in the domain OS environment:

The root-cause of the above failure signatures have been isolated to the fact that there exists a device node within the domain OS environment whose portid maps to a board that is involved with the DR attach/detach operations & where this specific device driver instance does not have a "property-name" attribute, will result in the failure of the DR operations. The above example demonstrates different symptoms of the same error condition.

In the DR attach failure example detailed above, the device node originating the DR addboard failure was isolated to an instance of the Hitachi HDLM driver dlmfdrv, whilst in the DR detach failure example detailed above, the device node found to be in conflict with SB0's processors was isolated to an instance of the Compaq RAID driver swsp.

Underlying in the above conflicting portid scenarios is the incorrect assumption that the portid for devices attached to the Safari bus are unique. In both situations depicted above the third party device driver instance resulted in a duplicated portid condition.

This resulted in the DR failure problem, caused by the improper identification of devices (i.e., relying on the portid property attribute as the primary means of locating the device list of a DR operations' target board).

The above issue with regards to the employment of portid as the primary means of identifying device(s) can occur with either Solaris[TM] 8 or Solaris[TM] 9 environment.

This bug-fix to the Solaris Operating Environment is addressed via the following:

• Solaris 8

111335-27 = platform/SUNW,Sun-Fire-15000/kernel/misc/sparcv9/drmach
116979-04 = platform/SUNW,Sun-Fire-15000/kernel/misc/sparcv9/platmod
110836-06 = platform/sun4u/kernel/misc/sparcv9/gptwocfg

• Solaris 9

bug fixes are in patch 117124-05 which was integrated into 122300

Internal Comments
For internal Oracle/Sun use only
see Bug IDs 4873095 & 4913987
starcat, dr, cfgadm, addboard, deleteboard, deprobe, property, name, portid, attribute, drmach
Previously Published As Doc 80017

This solution has no attachment