2 Installing the SBus Quad Ethernet Controller Card



2.1 Hardware Installation

Note - Refer to the following section on the extender plate before installing the card.

    1. Remove the SQEC card from the antistatic bag and spread the bag on a firm surface to provide a protective mat.

    Figure 2-1 Handling the SQEC Card

    2. Place the SQEC card, component side up, on the bag.
    3. Install the SQEC card according to the SBus installation procedures in the hardware installation or service manual for your system.

Note - Do not boot the system until SQEC installation is verified. See "Testing the SQEC Card Before Booting the System."

    4. Verify SQEC installation by doing a test command and a watch command.

    See "Testing the SQEC Card Before Booting the System" on page 3.

2.1.1 Extender Plate

The SQEC card was shipped with a bag containing a sheet metal extender plate (see Figure 2-2) and two screws.

    Figure 2-2 SQEC Card with Back Panel, Screws, and Extender Plate

You must use the extender plate to install the SQEC card correctly in some systems, such as the SPARCclassic, SPARCstation IPC, and SPARCstation IPX. If you are installing the card in one of these systems, attach the extender plate to the SQEC card back panel. Refer to the hardware installation or service manual that shipped with your system for other information about installing SBus cards.

2.2 Testing the SQEC Card Before Booting the System

After the SQEC card is installed, before booting the system, verify installation by executing a test command and a watch command. Boot the system after successfully executing these commands. Then, for Solaris 1.x users, install the driver software using the CD provided as described in Chapter 3. For Solaris 2.x users the software is automatically installed when the initial OS version is loaded.

Follow these steps to verify installation:

    1. Use show-devs to find out SBus card information.

    The show-devs [device path] command displays all devices known to the system directly beneath a given level in the device hierarchy. The
    show-devs command used by itself shows the entire device tree. Examples below show information for a SPARCserver(TM) 1000 system with only one board (board 0). 

---------------------------------------------------------

<#0 ok show-devs 
/io-unit@f,e0200000/sbi@0,0/qec@1,20000
/io-unit@f,e0200000/sbi@0,0/lebuffer@3,40000
/io-unit@f,e0200000/sbi@0,0/dma@3,81000
/io-unit@f,e0200000/sbi@0,0/lebuffer@0,40000
/io-unit@f,e0200000/sbi@0,0/dma@0,81000
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@3,0
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@2,0
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@1,0
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@0,0
/io-unit@f,e0200000/sbi@0,0/lebuffer@3,40000/le@3,60000
/io-unit@f,e0200000/sbi@0,0/dma@3,81000/esp@3,80000
/io-unit@f,e0200000/sbi@0,0/dma@3,81000/esp@3,80000/st
/io-unit@f,e0200000/sbi@0,0/dma@3,81000/esp@3,80000/sd
/io-unit@f,e0200000/sbi@0,0/lebuffer@0,40000/le@0,60000
/io-unit@f,e0200000/sbi@0,0/dma@0,81000/esp@0,80000
/io-unit@f,e0200000/sbi@0,0/dma@0,81000/esp@0,80000/st
/io-unit@f,e0200000/sbi@0,0/dma@0,81000/esp@0,80000/sd
<#0 ok

---------------------------------------------------------
    2. Set the diag-switch to true.

    To test the qec node or qe node, the diag-switch must be set to true. At the ok prompt type: 

------------------------------

ok setenv diag-switch? true

------------------------------
    3. Use a test-all command to test all devices below the specified device tree node.

    Devices that have a built-in self-test method are tested.

    The following example shows the output of test-all when only SQEC channels 3 and 1 are connected to a network: 

--------------------------------------------------------------------

<#0 ok test-all /io-unit@f,e0200000/sbi/qec@1,20000
Testing /io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@3,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check -- passed.
Testing /io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@2,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check --  failed, transceiver cable problem? or check 
the hub.
Selftest failed. Return code = -1 
Testing /io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@1,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check -- passed.
Testing /io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@0,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check --  failed, transceiver cable problem? or check 
the hub.
Selftest failed. Return code = -1 
<#0 ok 

--------------------------------------------------------------------
    4. Use a watch command, either watch-net or watch-net-all, to watch net activity (or watch incoming Ethernet packets).

    The watch-net command does not take any arguments. watch-net only watches the specified network channel defined by the device alias "netX".

Note - To find out the OpenBoot PROM revision level on your system, type .version at the <#0 ok prompt.

      a. If the system has OpenBoot PROM 2.6 or above, use watch-net-all.

      This example shows output when channel 3 is connected to a network: 

---------------------------------------------------------------------

<#0 ok watch-net-all /io-unit@f,e0200000/sbi/qec
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@3,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check -- passed.
Looking for Ethernet packets.
`.' is a good packet.  `X' is a bad packet.
Type any key to stop.
...............................................................
...............................................................
...............................................................
...............................................................
...........................
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@2,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check --  failed, transceiver cable problem?  or check
 the hub.
 
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@1,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check --  failed, transceiver cable problem? or check
 the hub.
 
/io-unit@f,e0200000/sbi@0,0/qec@1,20000/qe@0,0
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check --  failed, transceiver cable problem? or check
 the hub.
 
<#0 ok 

---------------------------------------------------------------------
      b. If the system has OpenBoot PROM 2.0 to 2.5, use watch-net as follows:
        i. Use devalias to specify the desired net channel to be watched: 
----------------------------------------------------------

<#0 ok devalias net2 /io-unit@f,e0200000/sbi/qec/qe@2,0

----------------------------------------------------------
        ii. Next, issue the watch-net command: 
-----------------------------------------------------------------

<#0 ok " net2" " watch-net" execute-device-method drop
 Qe register test -- succeeded.
 Internal loopback test -- succeeded.
 Internal (including Mendec) loopback test -- succeeded.
 Link state check -- passed.
Looking for Ethernet packets.
`.' is a good packet.  `X' is a bad packet.
Type any key to stop.
...............................................................
...............................................................
.................................
<#0 ok  

-----------------------------------------------------------------
    5. Set the diag-switch to false.

At the ok prompt type: 

-------------------------------

ok setenv diag-switch? false

-------------------------------

2.3 Rebooting the System and Examining Network Interfaces

    1. Reboot the system .

    To boot diskless over a qec channel, see Section A.3, "Booting from SQEC Devices with OpenBoot PROM 2.0 and Solaris 2.x," in Appendix A.

    2. Execute ifconfig -a and netstat -i commands after the system is up to examine the state of all network interfaces.

    Also use /usr/sbin/ping or /usr/sbin/spray commands to see if a network interface is active. Examples of output for ifconfig -a, ping, and netstat -i follow. 

-------------------------------------------------------------------

zardoz% ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST mtu 8232
	inet 127.0.0.1 netmask ff000000 
le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
	inet 129.144.10.57 netmask ffffff00 broadcast 129.144.10.255
qe0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
	inet 129.144.11.83 netmask ffffff00 broadcast 129.144.11.255
qe1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
	inet 129.144.12.41 netmask ffffff00 broadcast 129.144.12.255
qe2: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
	inet 129.144.13.18 netmask ffffff00 broadcast 129.144.13.255
qe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
	inet 129.144.14.95 netmask ffffff00 broadcast 129.144.14.255

-------------------------------------------------------------------


---------------------

zardoz% ping zelda
zelda is alive

---------------------


----------------------------------------------------------------------------------------

zardoz% netstat -i
Name  Mtu    Net/Dest       Address       Ipkts   Ierrs  Opkts   Oerrs  Collis  Queue 
lo0   8232   loopback       localhost     87      0      87      0      0       0     
le0   1500   umtv15-010-n   zardoz        421873  0      60009   1      183     0     
qe0   1500   umtv15-011-n   zardoz-11     427     0      253     0      0       0     
qe1   1500   umtv15-012-n   zardoz-12     6908    0      253     0      0       0     
qe2   1500   umtv15-013-n   zardoz-13     6834    0      0       0      0       0     
qe3   1500   umtv15-014-n   zardoz-14     5380    0      0       2      0       0     

----------------------------------------------------------------------------------------
    3. Once the card has been installed and the network examined:

Note - For diskless booting over an SQEC interface, see Appendix A.3 for the correct OpenBoot PROM command line.

Caution -

For Solaris 2.x only, do not change the SBus slot in which an SQEC card was installed once the system has been booted with an SQEC. The Solaris 2.x operating system remembers the location of each SBus card that has been installed. Switching SBus slots will cause the operating system to assume that you removed your original SQEC card and added a second SQEC card to the system. Refer to the on-line manual page about path-to-inst for more information.

Caution -

Do not connect more than one interface from any system to each net. Solaris does not support multiple Ethernet interfaces attached to the same physical network segment. Attaching multiple interfaces to the same net may introduce packet routing problems.