Sun Fire E6900 Server
 
Sun Fire 6800 Server
 
Sun Fire E4900 Server
 
Sun Fire 4800 Server
 

GCS>Sun Microsystems>Servers>Midrange Servers
 

Sun Fire[TM] E6900/E4900 systems and midrange Sun Fire servers with UltraSPARC[R] IV+ CPU/Memory boards or PCI-X I/O boards (or both) require 5.19.0 firmware and compatible releases of the Solaris[TM] 10 HW1 or Solaris 9 Update 8 Operating System (when available) as the minimum requirement.

With the introduction of UltraSPARC IV+ 1.5Ghz processor based system boards:

• Sun Fire[TM] 12K/15K/E20K/E25K platforms will require SMS 1.5 with LPOST
  revision 5.19.0.
• Midrange Sun Fire E6900/E4900 and Sun Fire[TM] 6800/4800 platforms will require the ScApp firmware version 5.19.0 to facilitate support for the new board type.

All domain configurations resident on the above platforms employing UltraSPARC IV+ 1.5Ghz processor based system boards will require Solaris 10 HW1 or Solaris 9 Update 8 operating system (when available) as their minimum requirement.

The error condition encountered through the course of DR attaching a USIV+ based system board:

v4u-6900a-domc sbd: WARNING: sbd_connect: no devices present on board 3
cfgadm: Hardware specific failure: connect N0.SB3: No such device

was reported from a Sun Fire platform that appears to be loaded with the above requisite OS/firmware requirements.

For example, the firmware deployed on the system controller is running off ScApp 5.19.2 rev:

ScApp version: 5.19.2 Build_01
Version build: 1.0
Version String: 5.19.2
RTOS version: 43

And the domain OS where the DR operations was attempted is running off the support Solaris 9 Update 8 Operating System:

# more /etc/release
Solaris 9 9/05 s9s_u8wos_05 SPARC
Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
Use is subject to license terms.
Assembled 04 August 2005

An example of the sequence of events leading up to the DR error is as follows:

# cfgadm
Ap_Id                          Type         Receptacle   Occupant     Condition
N0.IB9                         PCI_I/O_Boa  connected    configured   ok
N0.SB0                         CPU_V3       connected    configured   ok
N0.SB3                         CPU_V3       disconnected unconfigured unknown
N0.SB4                         CPU_V3       disconnected unconfigured unknown
c0                             scsi-bus     connected    configured   unknown

# cfgadm -v -c configure N0.SB3
assign N0.SB3
assign N0.SB3 done
poweron N0.SB3
poweron N0.SB3 done
test N0.SB3
{/N0/SB3/P0/C0} Running CPU POR and Set Clocks
{/N0/SB3/P1/C0} Running CPU POR and Set Clocks

               :

{/N0/SB3/P0} Passed
{/N0/SB3/P1} Passed
{/N0/SB3/P2} Passed
{/N0/SB3/P3} Passed
test N0.SB3 done
connect N0.SB3
Oct 14 12:10:51 v4u-6900a-domc sbd: WARNING: sbd_connect: no devices present on board 3
cfgadm: Hardware specific failure: connect N0.SB3: No such device

As observed from the reported error messages above, the generic (non-platform specfic) driver "sbd", which is responsible as a general interface between the DR nexus driver and the platform-specific "sbdp" driver is reporting the fact that it does not recognize any attachment points on the USIV+ based system board (i.e. SB3).

The above error is typically observed in situations where the currently resident system board(s) i.e. SB0, is either not flashed to firmware rev 5.19.0 (or greater) or is already flashed to firmware rev 5.19.0 but have not taken effect via a keyswitch ops/Solaris reboot.

In our example, the resident system board (i.e. SB0) is not flashed to maintain consistency with the main SC:

Component   Segment Compatible In Date       Time  Build Version
---------   ------- ---------- -- ----       ----  ----- -------          

SSC0/FP0    -       -          -  -          -     -     RTOS version: 43
SSC0/FP1    ScApp   Reference  12 09/16/2005 12:17 1.0   5.19.2
SSC0/FP1    Ver     -          -  09/16/2005 12:17 1.0   5.19.2 Build_01     

/N0/SB0/FP0 POST    Yes        12 09/20/2004 21:22 14.1  5.18.0
/N0/SB0/FP0 OBP     Yes        12 09/20/2004 21:21 14.1  5.18.0
/N0/SB0/FP0 Ver     -          -  09/20/2004 21:26 14.1  5.18.0 Build_14
/N0/SB0/FP1 POST    Yes        12 09/20/2004 21:22 14.1  5.18.0
/N0/SB0/FP1 OBP     Yes        12 09/20/2004 21:21 14.1  5.18.0
/N0/SB0/FP1 Ver     -          -  09/20/2004 21:26 14.1  5.18.0 Build_14    

The DR attach operations of the USIV+ based system board (SB3) will be allowed to proceed as expected when the resident system board (SB0) have been flashed to rev 5.19.0 (or greater) and the domain OS rebooted to allow the new firmware to take effect.

This solution has no attachment