A Booting with OpenBoot PROM





To utilize the SQEC card, OpenBoot PROM level 2.0 or later is required.

A.1 SQEC Device Path Information

    Table A-1 PROM Device Tree Path and Boot Description

----------------------------------------------------------------------------------------------
Platform Host (Bus Bus Card Type@ Channel Type @ System Examples Type Interface) Slot x (0 - 3) Channel c (0 - 3) ----------------------------------------------------------------------------------------------
                                                                           
Sun-4c                         /sbus  /qec@x,20000      /qe@c,0            SPARCstation 1*, 1+*, 
                                                                           2, IPC, IPX
                                                                           
Sun-4m    /iommu               /sbus  /qec@x,20000      /qe@c,0            SPARCserver 600MP, 
                                                                           SPARCstation 10
                                                                           
Sun-4d    /io-unit@f,eB200000  /sbi   /qec@x,20000      /qe@c,0            SPARCcenter 2000, 
                                                                           SPARCserver 1000
                                                                           
                                      *Do not install                      
                                      SQEC in slot 3;                                              
                                      slave only.                                                  

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

A.1.1 Sun-4c Platforms, such as SPARCstation 1, 1+, 2, IPC, and IPX

The device tree for SQEC cards installed in Sun-4c platforms will be:

/ --- sbus -------- qec -- qe

    Figure A-1 SPARCstation 2 Sample Bootpath

Legend:

(1) The first field of the qec (or qe) node identifies slot number.
(2) The first field of the qe node identifies channel number.

When there are multiple SQEC cards in a SPARCstation(TM) 2 or other Sun-4c system, the device nodes indicate the number of qe channels. In the example that follows, the device nodes indicate there are two qe channels.

a) /sbus/qec@2,20000/qe@0,0

b) /sbus/qec@3,20000/qe@1,0

"a" above refers to qe channel 0 of the SQEC card in slot 2

"b" above refers to qe channel 1 of the SQEC card in slot 3

Note - Do not install the SQEC card in slot 3 (slave-only) of SPARCstation 1 and SPARCstation 1+ systems.

A.1.2 Sun-4m Platforms, such as SPARCserver 600MP, SPARCstation10, SPARCclassic, and SPARCstation LX

The device tree for SQEC cards installed in Sun-4m platforms will be:

/ --- iommu ---- sbus -------- qec -- qe

    Figure A-2 600MP Sample Bootpath

Legend:

(1) The first field of the qec (or qe) node identifies slot number.
(2) The first field of the qe node identifies channel number.

When there are multiple SQEC cards in a 600MP or other Sun-4m system, the device nodes indicate the number of qe channels. In the example that follows, the device nodes indicate there are three qe channels.

a) /iommu/sbus/qec@2,20000/qe@0,0

b) /iommu/sbus/qec@3,20000/qe@1,0

c) /iommu/sbus/qec@3,20000/qe@3,0

"a" above refers to qe channel 0 of the SQEC card in slot 2

"b" above refers to qe channel 1 of the SQEC card in slot 3

"c" above refers to qe channel 3 of the SQEC card in slot 3

A.1.3 Sun-4d Platforms, such as SPARCserver 1000 and SPARCcenter 2000

The device tree for SQEC cards installed in Sun-4d platforms will be:

/ --- io-unit ---- sbi -------- qec -- qe

    Figure A-3 1000 or 2000 Sample Bootpath

Legend:

(1) The second nibble of the second field of the io-unit node identifies
board number:
(0 through 9 on 2000 system board; 0 through 3 on 1000 system board)
(2) The first field of the qec (or qe) node identifies slot number.
(3) The first field of the qe node identifies channel number.

When there are multiple SQEC cards in a SPARCcenter(TM) 2000 or other Sun-4d system, the device nodes indicate the number of qe channels. In the example that follows, the device nodes indicate there are three qe channels.

a) /io-unit@f,e2200000/sbi@0,0/qec@2,20000/qe@0,0

b) /io-unit@f,e2200000/sbi@0,0/qec@3,20000/qe@1,0

c) /io-unit@f,e6200000/sbi@0,0/qec@3,20000/qe@1,0

"a" above refers to qe channel 0 of the SQEC card in slot 2 of board 2

"b" above refers to qe channel 1 of the SQEC card in slot 3 of board 2

"c" above refers to qe channel 1 of the SQEC card in slot 3 of board 6

A.2 Link Integrity Test

The link integrity test feature is a requirement of the IEEE 10Base-T standard. The purpose of the test feature is to enable a 10Base-T node to detect a link failure. The standard requires that on a periodic basis, each station on the net transmit link pulses whenever it is not transmitting valid packets. Sampling the link pulses, the receiver will assume that the network connection (link) is intact and assumes a link pass state. This is indicated as the link LED being on whenever such LEDs are provided.

A.2.1 Link Integrity Test Problems

The IEEE 10Base-T specification states that the link test feature should always be enabled at the host and hub. Complications may arise because:

    1. Some hubs do not provide link pulses.
    2. Some hubs are configured not to send link pulses.

Under either of the two conditions, the receiving station translates the lack of link pulses into a link failure, unless the receiving station is programmed to ignore the link pulses.

The SQEC card is equipped with this programming feature. The default state is for the SQEC card to check for link pulses. If the hub cannot be configured to send link pulses, the SQEC card can be programmed on a per channel basis to disable the link test, and thus ignore link pulses and assume link pass state. Four LEDs are provided, one for each channel. Once the cable to the hub is plugged in, the LEDs will light up green under the following conditions:

    1. Link test is enabled on the SQEC card and link pulses are received.
    2. Link test is disabled on the SQEC card.

The LEDs will be off under the following condition:

Note - The SQEC card will transmit link pulses independent of the state of the link integrity test feature.

A.2.2 Link Integrity Test Commands

This section explains how to enable (default) or disable the link test for all SQEC channels or for each channel individually.

When these commands are entered at the OpenBoot PROM prompt, they are lost when the system is powered down. To execute these commands each time the system is powered on, edit the NVRAMRC as shown in Section A.2.2.4, "NVRAMRC patch," on page A-8.

A.2.2.1 set-tpe-test and no-tpe-test

The SQEC Prom provides a method set-tpe-test and a property no-tpe- test for the associated Ethernet nodes (qe node).

If n is non-zero, it will enable tpe-link-test and remove the property
no-tpe-test; if n is zero, it will disable tpe-link-test and add the
property no-tpe-test.

It is a property with null value. If it exists, it means tpe-link-test is
disabled; if it does not exist, it means tpe-link-test is enabled.

A.2.2.2 Disabling tpe-link-test

Enter the following code into NVRAMRC if tpe-link-test must be disabled on some Ethernet ports. Repeat the line of code, specifying the node, for each node that must be disabled:

------------------------------------------------------------------------------
false " <Ethernet-node1-pathname" " set-tpe-test" execute-device-method drop false " <Ethernet-node2-pathname" " set-tpe-test" execute-device-method drop false " <Ethernet-node3-pathname" " set-tpe-test" execute-device-method drop false " <Ethernet-node4-pathname" " set-tpe-test" execute-device-method drop ------------------------------------------------------------------------------

A.2.2.3 tpe-link-test Enable/Disable Status

Enable/disable tpe-link-test status can be checked from the ok prompt.

----------------------------------
ok cd <Ethernet-node-pathname'> .attributes ----------------------------------

-------------------------------------------
ok " <Ethernet-node-pathname" select-dev true set-tpe-test -------------------------------------------

or

--------------------------------------------------------------------------------
ok true " <Ethernet-node-pathname" " set-tpe-test" execute-device-method drop --------------------------------------------------------------------------------

-------------------------------------------
ok " <Ethernet-node-pathname" select-dev false set-tpe-test -------------------------------------------

or

---------------------------------------------------------------------------------
ok false " <Ethernet-node-pathname" " set-tpe-test" execute-device-method drop ---------------------------------------------------------------------------------

A.2.2.4 NVRAMRC patch

Following are examples of lines that must be added to the NVRAMRC to automatically disable tpe-link-test each time the system is powered-on:

probe-all install-console
false " /sbus/qec@1,20000/qe@0,0"
" set-tpe-test" execute-device-method drop
false " /sbus/qec@1,20000/qe@1,0"
" set-tpe-test" execute-device-method drop
false " /sbus/qec@1,20000/qe@2,0"
" set-tpe-test" execute-device-method drop
false " /sbus/qec@1,20000/qe@3,0"
" set-tpe-test" execute-device-method drop
banner

probe-all install-console
false " /iommu/sbus/qec@1,20000/qe@0,0"
" set-tpe-test" execute-device-method drop
false " /iommu/sbus/qec@1,20000/qe@1,0"
" set-tpe-test" execute-device-method drop
false " /iommu/sbus/qec@1,20000/qe@2,0"
" set-tpe-test" execute-device-method drop
false " /iommu/sbus/qec@1,20000/qe@3,0"
" set-tpe-test" execute-device-method drop
banner

probe-all install-console
false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@0,0"
" set-tpe-test" execute-device-method drop
false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@1,0"
" set-tpe-test" execute-device-method drop
false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@2,0"
" set-tpe-test" execute-device-method drop
false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@3,0"
" set-tpe-test" execute-device-method drop
banner

Editing NVRAMRC

To patch NVRAMRC, use nvedit and nvstore commands. If you use the tip window for tty input/output, use Shell Tool to create the tip window.

If you use Command Tool to create the tip window, type
stty intr \^i
before you enter the tip command.

Editing NVRAMRC from the ok prompt

To edit NVRAMRC from the ok prompt:

    1. Type nvedit and enter a carriage-return <CR'>.

    The screen will display 0:indicating line 0.
    (A symbol other than the colon ":" may follow the line number.)

    2. Type in the patch line and a <CR'> after the 0: on the screen.

    A 1: will be displayed for line 1.

    3. Type another patch line and a <CR'> after the 1:.

    A 2:, indicating line 2, will be displayed.

    4. Type another patch line and a <CR'> after the 2:.
    5. Continue editing by adding patch lines.
    6. Type control-c (^c) to return to the ok prompt.
---------------------------------------------------------
<#0 ok nvedit 0: probe-all install-console 1: false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@0,0" 2: " set-tpe-test" execute-device-method drop 3: false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@1,0" 4: " set-tpe-test" execute-device-method drop 5: false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@2,0" 6: " set-tpe-test" execute-device-method drop 7: false " /io-unit@f,e1200000/sbi/qec@1,20000/qe@3,0" 8: " set-tpe-test" execute-device-method drop 9: banner 10: ^c <#0 ok nvstore <#0 ok setenv use-nvramrc? true <#0 ok reset ---------------------------------------------------------

A.3 Booting from SQEC Devices with OpenBoot PROM 2.0 and Solaris 2.x

The tables and displays in this section identify bootpaths that are required for a diskless boot over an SQEC interface.

Table A-2 provides bootpath information for booting a Sun-4m system (such as SPARCserver 600MP) with OpenBoot PROM (OBP) 2.0 and higher, under the Solaris 2.x environment.

Table A-3 provides bootpath information for booting a Sun-4c system (such as SPARCstation 2).

Table A-4 provides bootpath information for a Sun-4d system (such as SPARCcenter 2000).

    Table A-2 600MP (Sun-4m) Sample Bootpath

--------------------------------------------------------
Description Bootpath --------------------------------------------------------
                   
General path name  /iommu/sbus/qec@S,20000/qe@C,0
                   where S = SBus slot #, C = channel #
                   
SQEC in slot 2,    
channel 3          /iommu/sbus/qec@2,20000/qe@3,0

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

To boot from the OBP ok prompt, type boot. In this example, slot 0, channel 0:

------------------------------------------
ok boot /iommu/sbus/qec@0,20000/qe@0,0 ------------------------------------------

For SQEC card in slot 1, channel 1, the path changes to:

------------------------------------------
ok boot /iommu/sbus/qec@1,20000/qe@1,0 ------------------------------------------

If you want information about the valid path names on your machine, type this command:

---------------
ok show-devs ---------------

The path name for each device is displayed on the screen.

    Table A-3 SPARCstation 2 (Sun-4c) Sample Bootpath

--------------------------------------------------------
Description Bootpath --------------------------------------------------------
                   
General path name  /sbus/qec@S,20000/qe@C,0
                   where S = SBus slot #, C = channel #
                   
SQEC in slot 1,    
channel 2          /sbus/qec@1,20000/qe@2,0

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

To boot from the OBP ok prompt, type boot. In this example, slot 2, channel 1:

------------------------------------
ok boot /sbus/qec@2,20000/qe@1,0 ------------------------------------

For SQEC card in slot 1, channel 0, the path changes to

------------------------------------
ok boot /sbus/qec@1,20000/qe@0,0 ------------------------------------

    Table A-4 SPARCcenter 2000 (Sun-4d) Sample Bootpath

-----------------------------------------------------------------------------------
Description Bootpath -----------------------------------------------------------------------------------
                   
General path name  /io-unit@f,eB200000/sbi@0,0/qec@S,20000/qe@C,0
                   where B = board #, S = SBus slot #, C = channel #
                   (Board # can be 0 - 9 on a 2000 system, 0 - 3 on a 1000 system)
                   
SQEC in board 9,   
slot 1, channel 2  /io-unit@f,e9200000/sbi@0,0/qec@1,20000/qe@2,0

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

To boot from the OBP ok prompt, type boot. In this example, board 1, slot 1, channel 0:

------------------------------------------------------
ok boot /io-unit@f,e1200000/sbi/qec@1,20000/qe@0,0 ------------------------------------------------------

For SQEC card in board 2, slot 3, channel 2, the path changes to:

------------------------------------------------------
ok boot /io-unit@f,e2200000/sbi/qec@3,20000/qe@2,0 ------------------------------------------------------