After installation of the SBus adapter card device driver as indicated in Chapter 2, the basic SBus Expansion Subsystem (SES) Board installation process consists of the following:
To remove the system board in the 670MP system (12 slot office pedestal), halt the SPARCsystem or SPARCserver and then turn off power as follows:
Before you turn off the system power, you must halt the operating system or loss of data can occur. To shut down the system and give users a shutdown warning:
Note - This screen display is an example only. The actual message displayed on the screen will depend on the software running on the system.
Caution -
To remove the system board in the 690MP system (56-inch data center cabinet), halt the SPARCsystem or SPARCserver and then turn off power as follows:
Before you turn off the system power, you must halt the operating system or loss of data can occur. To shut down the system and give users a shutdown warning:
Note - This screen display is an example only. The actual message displayed on the screen will depend on the software running on the system.
Caution -
The expansion adapter card is an SBus card. One expansion adapter card must be installed on the system board for each SBus expansion subsystem you connect. For example, if you connect two expansion subsystems, install two expansion adapter cards.
Four SBus slots are available on the subsystem board. If two SPARC modules are installed, only three SBus slots are available. If all system board SBus slots are occupied, then one of the Sbus cards must be relocated onto the SBus expansion board to make room for the SBus expansion adapter card. Refer to "Installing SBus Cards in Deskside and Data Cabinet Systems" to remove and relocate an SBus card to the SBus expansion board if required, and to install the SBus adapter card on the system board.
Note - A requirement of the SBus expansion subsystem is that SBus slot 0 on the expansion board be occupied.
To install SBus cards on the SBus expansion board, refer to "Installing SBus Cards in Deskside and Data Cabinet Systems".
The SBus Expansion Subsystem is transparent to the computer system to which you have connected the subsystem. Because of this, when you are connecting multiple SCSI devices to a computer system using a SBus Expansion Subsystem, you are still limited to the parameters of the SCSI standards of the computer system to which your Expansion Subsystem is attached.
The additional ports of the SBus Expansion Subsystem do not necessarily guarantee additional SCSI ports. The System Administration Guide for your system, or your operating system documentation, should provide you with this information.
Caution -
To replace the system or SBus expansion boards:
The board will not seat easily unless the levers are extended.
Caution -
If the system is a 690MP, first replace the rear panel using two screws, then proceed to the next section.
To connect an SBus expansion subsystem to a SPARCsystem or SPARCserver:
Note - A requirement of the SBus expansion subsystem is that SBus slot 0 on the expansion board be occupied.
Caution -
Check that both ends of the cable are firmly connected.
Note - This screen display is an example only. The actual message displayed on the screen will depend on the software running on the system.
If you installed an SBus card on the SBus expansion board and you want to boot from the device connected to it each time the board is powered up, go to the next step.
If you do not want to boot from the device connected to an SBus card installed on the SBus expansion board, boot your system in the usual manner. For complete booting instructions, refer to the installation guide for your system.
Examples of bootable SBus cards are:
Caution -
You can boot from a bootable SBus card installed in an SBus Expansion Subsystem. Consult the manual accompanying your SBus card to determine if the SBus card is bootable. The following describes one example, a bootable FSBE/S card. You boot from all bootable SBus cards the same way.
In this case you are booting from an FSBE/S card that you installed in the SBus Expansion Subsystem slot 2 and the Expansion Adapter card in slot 1 of the computer system. Type the following at the ok prompt:
------------------------------------------------------------------
ok boot /iommu/sbus/SUNW,xbox@1,0/dma@2,81000/esp@2,80000/sd@0,0 ------------------------------------------------------------------
Table 3-1 lists descriptions of the syntax used:
Table 3-1 FSBE/S Boot Syntax Description
-----------------------------------------------------------------------
syntax Description -----------------------------------------------------------------------
/iommu Main logic board of your computer system
/sbus Resides on the main logic board of your computer
system
in the MMU chip (Memory Management Unit)
/SUNW,xbox@1 Expansion Adapter card installed in slot 1
/dma@2,81000 FSBE/S card installed in slot 2 of the SBus Expansion
and Subsystem
/esp@2,8000
/sd@0,0 SCSI disk set to target #0 and connected to FSBE/S SCSI
port
-----------------------------------------------------------------------
Note - SBus cards manufactured by different suppliers may have different card SBus Expansion Subsystem codes. Therefore, you should get the proper card code from the source of the SBus card.
During the installation of your SBus Expansion Subsystem hardware, you may receive one or more of the following error messages
Note - Any screen reference to XBox is assumed to be a refernce to the SES Board.
Error message
----------------------------------------
Test failed, expected <# observed <#'> ----------------------------------------
Action: Review the test results and determine probable cause of error. Take steps to correct the problem and rerun the installation procedures.
Error message
-------------------
No child hardware -------------------
Explanation: The system will generate this message if there is no SBus Expansion Subsystem hardware in the system.
Action: Make sure the Sbus Expansion Subsystem cable is properly plugged in to the Expansion Adapter card and that the power is on. Retry the installation.
-------------------------------
Invalid XBox slot number <#'> -------------------------------
Explanation: When decoding a child slot address, the system found a slot out of range (0 through 2 or 3 depending on the system). The system provides the slot number that is in error.
Action: Replace the SBus card reported. If that fails, replace the Adapter card in the computer system.
Error message
---------------------------------------
Invalid FCode in SBus <# XBox at <#'> ---------------------------------------
Explanation: While probing at the child level, the system found something that isn't an FCode header. The system provides the number of the slot identified by the code. Either you have a bad SBus card or the autoconfig won't work
Action: Change the SBus card. If the problem still exists, contact your authorized Sun technical support person for assistance.
Error message
--------------------------------
Invalid FCode start byte <cr'> --------------------------------
Explanation: The probe-self command detects a bad FCode header in child FCode image. This is the result of a bad SBus card
Action: Replace the SBus card with a good SBus card.
Error message
----------------------
Nothing there <cr'> ----------------------
Explanation: The probe-self command, while in diagnostic mode, did not find the proper code present.
Action: Reset the equipment and retry the installation. If the problem still exists, check the cables to see if they are making the proper contact.
Error message
------------------------------------------------------------
The card in slot <# of SBus <# XBox uses too much address space.<cr'> ------------------------------------------------------------
Explanation: During auto-configuration the system detected a card size that was too large.
Action: Change the order of the sbus cards in the Sbus Expansion Subsystem slots. Always place the SBus cards in the slots in order of their address size. The SBus card with the largest address space requirements should be in the lowest available slot.
Error message
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Unable to clear errors for S Bus <# XBox <cr -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Explanation: A test detected errors persisting after test completion.
Action: Your system has bad hardware. Check your computer system and SBus Expansion system for problems. Either fix the hardware or exchange the bad equipment for good hardware.
Error message:
---------------------------------
SBus <# XBox xac-error <# <cr'> ---------------------------------
Explanation: This a severe warning message. This message, although severe, is not normally fatal. It is an indication of a problem in the system that will manifest in another error at a later time.
Action: Continue running the system
Error message:
---------------------------------
SBus <# XBox xbc-error <# <cr'> ---------------------------------
Explanation: This a severe warning message. This message, although severe, is not normally fatal. It is an indication of a problem in the system that will manifest in another error at a later time.
Action: Continue running the system.
Error message
------------------------------------------------
XBox at SBus <# child not ready --<cr'> perhaps the cable is not plugged in<cr'> or the expansion box is not turned on.<cr'> ------------------------------------------------
Explanation: During initial setup, the system did not detect the SBus Expansion Subsystem hardware that it was expecting.
Action: Turn off the SBus Expansion Subsystem and reset. Then reinstall the software.
