Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1009350.1 : Sun Fire[TM] servers : DR attach of USIV+ system board yields error -- "WARNING: sbd_connect: no devices present on board 3"
PreviouslyPublishedAs 212934 Description 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. Steps to Follow With the introduction of UltraSPARC IV+ 1.5Ghz processor based system boards:
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. Product Sun Fire 4800 Server Sun Fire 6800 Server Sun Fire E4900 Server Sun Fire E6900 Server serengeti, amazon, panther, usiv+, dr, cfgadm, cheetah, jaguar, s10, s9u8, sbd_connect, no devices present Previously Published As 82894 29d3a694-0a18-11d6-92da-df959df44cdd|Sun Fire 4800 Server 29da7938-0a18-11d6-8a41-9ed1ad6d6779|Sun Fire 6800 Server bed24aa9-0598-11d8-84cb-080020a9ed93|Sun Fire E4900 Server 4fe39727-0599-11d8-84cb-080020a9ed93|Sun Fire E6900 Server Attachments This solution has no attachment |
||||||||||||
|