lw8 quick ref guide 0406

Sun Microsystems, LtdCitygate, Cross Street

SaleManchester

M33 7JF, UK

Sun Confidential: Internal Only Brian Jackson, April 2006

Sun Fire™ E2900 and V1280/Netra™1280

Quick Reference Guide

Copyright 2006 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303, U.S.A. All rights reserved.

This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Sun, Sun Microsystems, the Sun Logo, Sun Fire, and UltraSPARC III are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.

The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.

U.S. Government approval might be required when exporting the product.

RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015 (b)(6/95) and DFAR 227.7202-3(a).

DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Sun Confidential: Internal Only

PleaseRecycle

Copyright 2006 Sun Microsystems Inc., 901 San Antonio Road, Palo Alto, California 94303, Etats-Unis. Tous droits réservés.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.

Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Sun, Sun Microsystems, le logo Sun, Sun Fire, et UltraSPARC III sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Toutes les marques SPARC sont utilisées sous licence sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.

UNIX est une marques déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

L’interfaces d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour larecherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

L’accord du gouvernement américain est requis avant l’exportation du produit.

LA DOCUMENTATION EST FOURNIE “EN L’ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A L’ABSENCE DE CONTREFAÇON.

Sun Confidential: Internal Only Please

Recycle


PleaseRecycle

Table of Contents

Additional Resources ............................................................................9Sun Fire V1280/Netra 1280 - front view...........................................10Sun Fire V1280/Netra 1280 - back view ...........................................11Sun Fire V1280/Netra 1280 - top view .............................................12System Board layout............................................................................13I/O Board and System Controller (IB_SSC).....................................14

System Controller Version 2 (SC V2) .......................................156-slot PCI Riser ............................................................................15

Accessing the LOM Shell ....................................................................16Using the Serial Port ...................................................................16Using the telnet command..........................................................16Using the ssh Command.............................................................17RSA & DSA Authentication.......................................................17exiting an ssh session..................................................................18

Regenerating SSH host keys using ssh-keygen ...............................19Initial state after powering on. ...........................................................20Initial system verification - showboards, showcomponent ...........24

showcomponent ..........................................................................26Setting up the System Controller.......................................................27

Rebooting the system controller ...............................................28Tolerate correctable memory errors (5.19.x) ...........................29

Managing the System Controller date & time .................................30Displaying the date & time.............................................................30Setting the date & time....................................................................30Setting the date/time from a network time server..........................30

System Monitoring ..............................................................................31System/enclosure level LEDs.........................................................31Event Monitoring ...........................................................................31Power supply LEDs .......................................................................32Monitoring from Solaris and the lom shell......................................33Component/Module level LEDs ...................................................34Fan Tray considerations..................................................................34

Error logging.........................................................................................35


SunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services

Persistent Logging ...............................................................................36Check if you have an SC V2............................................................36Accessing the persistent log............................................................36

Firmware Upgrades.............................................................................37Do you need to flashupdate?..........................................................37Patch information...........................................................................37

5.19.x firmware for Sun Fire V1280/Netra 1280 Systems ..............38flashupdating from 5.13.x to 5.19.x..................................................38

ftp server setup.....................................................................................39ftp server setup at Solaris 9 .............................................................39ftp server setup at Solaris 8 .............................................................39mkdir /export/ftp/pub and copy the patch into it ........................40

Updating from lom shell - flashupdate ............................................41flashupdate - example ....................................................................42

Updating from Solaris - lom -G .........................................................46lom -G - example............................................................................46

Setting a LOM Shell Password...........................................................52Password example .........................................................................52

Resetting LOM Shell Passwords........................................................53Booting the system for the first time .................................................55show-post-results / probe-scsi-all .....................................................61bootmode options ................................................................................62Displaying NVRAM parameters .......................................................63Recommendations for NVRAM parameters....................................64

diag-level........................................................................................64reboot-on-error ...............................................................................64auto-boot?.......................................................................................65error-reset-recovery ....................................................................65local-mac-address? .........................................................................65diag-switch? ...................................................................................65

Resetting a hung system .....................................................................66resetsc.............................................................................................66break...............................................................................................66reset -x ............................................................................................67showresetstate ................................................................................67reset -a ............................................................................................67

Switching between different consoles...............................................68The default escape sequence will not work at the ok prompt.......69The default escape sequence will not work from solaris.. .............70

Serial escape sequences and dumb terminals .................................70I/O layout .............................................................................................71show-devs .............................................................................................72V1280/Netra 1280 System Configuration card ...............................73

Backing up the System Configuration card.....................................74V1280/Netra 1280 Physical Device Mapping..................................75

Node Mapping ............................................................................75

Sun Confidential: Internal OnlyV1280/Netra 1280 Quick Reference GuideSunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services

System Board Mapping..............................................................75Processor/Memory Controller AIDs (hex in brackets) .........76I/O Mapping ...............................................................................76Schizo AIDs (hex in brackets)....................................................77I/O Slot layout.............................................................................77

Internal Disk, DVD, and DDS Tape layout ......................................78Which disk is which?..................................................................78What’s the device path to the DVD? ........................................78

devalias & setenv .................................................................................79Device Aliases.......................................................................................80

Add a Device Alias .....................................................................80V1280/Netra 1280 Logical Device Mapping....................................81/dev/dsk & logical network mapping.............................................86Installing Lights out Management (LOM) 2.0 software .................87Installing and running Explorer ........................................................93

Interrogating the V1280 remotely ...................................................95Running the inventory command .....................................................98Advice on Dynamic Reconfiguration..............................................101Appendix.............................................................................................103

prtdiag -v output.......................................................................103lom -a output .............................................................................110

Sun Confidential: Internal Only SunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services

Additional Resources

Additional Resources

Additional resources – The following references provide additional details on the topics discussed in this quick reference guide:

● Sun Fire V1280/Netra 1280 Product Notes, 817-5342-xx

● Sun Fire V1280/Netra 1280 Compliance & Safety Manual, 817-0512-xx

● Sun Fire V1280/Netra 1280 Site Planning Guide, 817-3333-xx

● Sun Fire V1280/Netra 1280 Install Guide, 817-3334-xx

● Sun Fire V1280/Netra 1280 Service Manual, 817-0510-xx The above can be downloaded from:

http://www.sun.com/products-n-solutions/hardware/docs/Servers/

Note – Use the System Controller Command Reference Manual and System Administration Guide specific to the firmware you are working on. These manuals come bundled in with the firmware patch (see page 38)

● SUN SYSTEM HANDBOOK available at the following link

http://sunsolve.central.sun.com/handbook_internal/

● Kumar Loganathans blueprint Sun Fire V1280/Netra 1280 Server: Considerations for Improving RAS

http://www.sun.com/solutions/blueprints/0803/817-3342.html

● Sun Fire V1280/Netra 1280 Quick Reference Guide, latest rev available at the following link

http://sale-wts.uk.sun.com/~brianja/

Sun Confidential: Internal Only 9SunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services

Sun Fire V1280/Netra 1280 - front view

10

Sun Fire V1280/Netra 1280 - front view

SERVICE REQUIRED

SYSTEM ALARM POWER SOURCE

Main Fans

On/Standby Switch

Service Indicator Panel

System ConfigurationCard Reader

DVD-ROM Drive

DAT Tape Drive(optional)

Hard Disk Drives

Power Supply 0

Power Supply 1

Power Supply 2

Power Supply 3

Front View


Sun Fire V1280/Netra 1280 - back view

Sun Fire V1280/Netra 1280 - back view

SC

SI3

A

LA

RM

S

BBA

PCI 333MHz

PCI 133MHz

PCI 233MHz

PCI 433MHz

PCI 566MHz

PCI 033MHz

LinkActive

GBit

LinkActive

GBit

NET0

NET1

Serial A Serial BSSC1 SSC1

SC

SI3

A

LA

RM

S

BBA

PCI 333MHz

PCI 133MHz

PCI 233MHz

PCI 433MHz

PCI 566MHz

PCI 033MHz

LinkActive

GBit

LinkActive

GBit

NET0

NET1

Serial A Serial BSSC1 SSC1

AC3

AC2

AC1

AC0

SO

UR

CE

AS

OU

RC

E A

SO

UR

CE

B

PS3 Input

PS1 Input

PS0 Input

PS2 Input

Branch A

Branch B

68-pin SCSI

Alarms Port

Net0/Net110/100/1000 Base-T

Data NetworkConnections

10/100 Ethernet :LOM/System Controller/Console

RJ45 Serial :LOM/System Controller/Console

68-pin SCSI

Alarms Port

Net0/Net110/100/1000 Base-T

Data NetworkConnections

10/100 Ethernet :LOM/System Controller/Console

RJ45 Serial :LOM/System Controller/Console

Back View

DC0

DC1

DC3

DC2

+

-

-

-

-

+

+

+

SOURCEB

SOURCEA

Netra 1280Power Inlets

Sun Fire V1280Power Inlets


Sun Fire V1280/Netra 1280 - top view

12

Sun Fire V1280/Netra 1280 - top view

Top View

PUSH DOWN EVENLY

TO SEAT CONNECTOR

PUSH DOWN EVENLY

TO SEAT CONNECTOR

SB

WEIGHT: 12kg/26.5lbsSYSTEM

FRONT

PUSH DOWN EVENLY

TO SEAT CONNECTOR

PUSH DOWN EVENLY

TO SEAT CONNECTOR

SB


FRONT

PUSH DOWN EVENLY

TO SEAT CONNECTOR

PUSH DOWN EVENLY

TO SEAT CONNECTOR

SB


FRONT

IB-SSCIB FAN0IB FAN1

PUSH DOWN EVENLY

TO SEAT CONNECTOR

RP PUSH DOWN EVENLY

TO SEAT CONNECTOR

RP PUSH DOWN EVENLY

TO SEAT CONNECTOR

IB6

_S

SC

1R

P0

RP

2S

B0

SB

2S

B4

PCI Bay

IB6_SSC1

IB Fans

Level 2 Repeater RP0

Level 2 Repeater RP2

CPU/Memory SB0

CPU/Memory SB2

CPU/Memory SB4

Media Bay

Media Bay Cover

Inside:

• Tape Drive Connectors

• CD-DVD Drive Latch

• SCCR Fasteners

• RMM Bay Connectors

For IB_SSC Moduleremoval, refer to manual

IB Fan Bay Cover

Inside:

• 2 PCI Fans

Inside:

• 5 33MHz PCI Card Slots

• 1 66MHz PCI Card Slot

PCI Card Bay Cover


System Board layout

System Board layout

Check out the board layout and DIMM locations below:


I/O Board and System Controller (IB_SSC)

14


The above is all one FRU. You can not swap out an SC without the I/O assembly and vice-versa. See overleaf for details of the 6-slot PCI riser.



System Controller Version 2 (SC V2)

An SC V2 has 128MB of memory, which allows ssh connections and also persistent logging

IB_SSC with SCV1, FRU 540-5290 IB_SSC with SCV2, FRU 540-6045

6-slot PCI Riser

For slot addresses refer to page 77


Accessing the LOM Shell

16


Initial access to the LOM shell is through the RJ-45 serial port “SSC1 serial A” (see page 11) until such time as you can setup the System Controller network interface or until such time as the System Controller can come up on a network automatically via DHCP.

Note – Serial Port B on the back of the platform is not available for use. It is neither accessible from the LOM shell nor Solaris.

Using the Serial Port

To access the system controller from the serial port of a workstation:

# tip hardwire

If you cannot use TTY Port B on the workstation’s serial port, you must edit the /etc/remote file.

:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

Change /dev/term/b to /dev/term/a

# tip -9600 /dev/term/a

works just as well

Using the telnet command

# telnet <SC-hostname or IP address>

The network will have had to be configured to be able to telnet in, using the setupnetwork command

# telnet v1280a-sc1 Trying 172.20.33.2Connected to v1280a-sc1Escape character is ’^]’.

Connected.

LOM>



Using the ssh Command

You can use a secure shell session to access the LOM shell as long as you have an SC V2 installed (see page 15, 36). The workstation you are ssh’ing from must be running Solaris 9 or above. Note that you can ssh in from a PC if it has a win32 SSH client installed.

admin-ws% ssh v1280-sc1The authenticity of host ’v1280-sc1’ can’t be established.RSA key fingerprint in md5 is: 63:c6:d8:88:8f:05:fa:1a:20:42:6c:79:eb:f6:1a:56Are you sure you want to continue connecting(yes/no)? yesWarning: Permanently added ’v1280-sc1’ (RSA) to the list of known hosts.Enter Password: <--- As setup by the ‘lom> password’ commandConnected. <--- HIT RETURN

# <--- get to the lom shell using the escape sequence (default #.)

The above message is normal for the first time you ssh into an SC. On the admin-ws, the file $HOME/.ssh/known_hosts will have the following line added..

admin-ws% cat known_hosts

129.159.235.105 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAnVulAsfrYjjX5dMOK5xxLl95TxnOSmkzdLyUX/slTlmKGm0sZn+BDfag4DWsMZ1OB6V5AojkPS5sYXqmGhIRvWtceSGPb0unotaNxh4c1r78GUFyhKILDasC4Joj0XIOtyrf0WBS+IZ7kew9JNg37pvb7qvalBzh5lQdEUCuhR8=

v1280-sc1 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAy55Um2yo7AiVEEPkOzpARtU647LgVL3GxWkeERS5jpS2XSO0ujX+PGmdPAr+YqfQE6xQML+hndUlzVuRSBlUDiHezjYe86MPW213s/rENK7AwAIS7pJeEUbzUaDwFJZMCuQuMaiuHTEq8eGABzrahBqaX54ruwQ96ur02tfVaFc=

RSA & DSA Authentication

Secure shell on Solaris 9 does not support authenticating via the DSA key. The SSH protocol requires that the client and server auto negotiate the host key algorithm. Our Solaris 9 client and server always send "ssh-rsa,ssh-dsa" which says that they prefer RSA over DSA. This is not configurable.



18

Future releases of Solaris will introduce HostKeyAlgorithms, which will allow access using the DSA Host key on the system controller.

exiting an ssh session

To exit an SSH session, use ~. This will give you a problem if the lom shell escape sequence is ~.

Note – From the ssh manpage, “A single tilde character can be sent as ~~” So, the escape sequence to get to the lom shell will be “~~.” Depending how your session handles the ~ key you may also need an extra tilde character - “~~~.”

If you have any problems getting to the lom shell from an ssh session, you can always change the escape sequence by the following method.

admin-ws% ssh v1280-sc1Enter Password: Connected.

# <---- Type ~.# Connection to v1280-sc1 closed.admin-ws% ssh v1280-sc1Enter Password: Connected.

# lom -c | grep escapeserial escape sequence=~.# lom -X#.The LOM serial escape sequence is now "#."# <---- Type #.

lom>


Regenerating SSH host keys using ssh-keygen

Regenerating SSH host keys using ssh-keygen

It is good practice on a well managed platform to periodically update the SSH host keys.

lom> ssh-keygen -l63:c6:d8:88:8f:05:fa:1a:20:42:6c:79:eb:f6:1a:56 (RSA host key)lom>

lom> ssh-keygen -rRSA host key generated.Use ’restartssh’ to restart the SSH server with the new host key.lom>

lom> restartsshRestarting SSH server will disconnect all active SSH sessions.continue (yes/no) ? [no] yesConnection to v1280-sc1 closed by remote host.Connection to v1280-sc1 closed.admin-ws%

You will now need to remove the line in $HOME/.ssh/known_hosts pertaining to the original RSA key. If you don’t, you will see the following warning.

admin-ws% ssh v1280-sc1

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@Someone could be eavesdropping on you right now(man-in-the-middle attack)It is also possible that the RSA host key has been changed.The fingerprint for the RSA key sent by the remote host ismd5 6b:b9:e3:bf:f6:fb:bd:18:04:89:2b:99:68:94:ce:ca.Please contact your system administrator.Add correct host key in /home/brianja/.ssh/known_hostsOffending key is entry 2 in /home/brianja/.ssh/known_hostsRSA host key for v1280-sc1 has changed and you have requested strict checking.admin-ws%


Initial state after powering on.

20


After applying AC power to the v1280 or 48V DC to the Netra 1280, an auxiliary 48V is applied to the System Controller.

It will run SCPOST, load the RTOS and then run the LOM.

You do not need to actuate the System Indicator Panel rocker switch at this time.

Note – Initially, there will be no lights on the System Indicator Panel. These status LEDs are lit by the LOM, and will only light after the LOM is loaded. After applying power, open the front doors and you’ll see the green LEDS flashing on the four PSUs. If they’re not, check the power on the power inlet box for that PSU. You will also notice Fan 3 is spinning - this is to provide cooling to the system controller. Once the LOM firmware on the system controller is loaded, that’s when the source A&B LEDs on the System indicator board are lit.

Make sure you have a serial connection to the SC before applying power. This way, you will capture all messages from the system controller.

# tip -9600 /dev/term/a connected Hardware Reset...

@(#) SYSTEM CONTROLLER(SC) POST 39 2004/04/19 19:20PSR = 0x044010e5PCR = 0x04004000

Memory size = 32MB

SelfTest running at DiagLevel:0x20 SC Boot PROM Test BootPROM CheckSum Test



IU Test IU instruction set Test Little endian access Test FPU Test FPU instruction set Test SparcReferenceMMU Test SRMMU TLB RAM Test SRMMU TLB Read miss Test SRMMU page probe Test SRMMU segment probe Test SRMMU region probe Test SRMMU context probe Test IIep Internal Cache Test DCACHE RAM access Test DCACHE TAG access Test DCACHE Read miss Test DCACHE Read hit Test DCACHE Write miss Test DCACHE Write hit Test ICACHE RAM access Test ICACHE TAG access Test ICACHE miss Test ICACHE hit Test ICACHE TAG flush Test PCIC Test PCIC Probe Test PCIC Config Register Access Test PCI Master Abort Test PCIC Init Test Memory Test Memory Address Test MemBankAddrTest: start address = 0x00010000 RIO Ebus Test Rio Ebus Probe Test RIO Ethernet Test Rio Enet Probe Test Rio Ethernet Int Loopbacks Test DUART(16552) InterSC Test Loopback Test COM3 port COM4 port Interrupt Test COM3 port Intr #2 COM4 port Intr #2System Clock Test System Clock verify Test Board0 Clock is selected 75MHZ Fixed Crystal is the selected Clock Source



22

CLK(Self) :0x0000ffff CLK(Other) : 0x00000000 REF : 0x00002223 CLOCK(SELF) FREQ : 74.99 MHZ CLOCK(OTHER) FREQ : 0.0 MHZ SBBC PCI Controller Test SBBC PCI Config Space probe Test SBBC Internal Reg Access Test SBBC Interrupts Test Port1 interrupt generation Tests INTR #14 Port0 interrupt generation Tests INTR #14SBBC Device0 Test PS Fail Reg(SBBC Dev0) Test SBBC Device1 Test SRAM (SBBC Dev1) Test Memory Address Test (Non-destructive) SBBC Device2 Test BId&MFG Reg (SBBC Dev2) Test SBBC Device3 Test FRU Prsnt Reg (SBBC Dev3) Test SBBC Device5 Test EPLD (SBBC Dev5) Test TOD(M48T59) Test TOD Init Test TOD Functional Test TOD NVRAM(Non-Destructive) Test TOD Interrupts Test I2C Register Access Test Enable Mux Register Test Channel Mux Register Test Add Command Register Test Data Register Test Local I2C AT24C64 Test EEPROM Device Test performing eeprom sequential readLocal I2C PCF8591 Test VOLT_AD Device Test channel[00000001] Voltage(0x0000009A) :1.50 channel[00000002] Voltage(0x0000009C) :3.35 channel[00000003] Voltage(0x0000009B) :5.4 channel[00000004] Voltage(0x00000000) :0.0 Local I2C LM75 Test TEMP0(IIep) Device Test Temperature : 18.50 Degree(C)Local I2C LM75 Test TEMP1(Rio) Device Test Temperature : 17.50 Degree(C)Local I2C LM75 Test



TEMP2(CBH) Device Test Temperature : 27.50 Degree(C)Local I2C PCF8574 Test Sc CSR Device Test Console Bus Hub Test CBH Register Access TestPOST Complete.ERI Device PresentGetting MAC address for SSC1Using SCC MAC addressMAC address is 0:3:ba:c0:ff:eeUsing DHCP to configure network interfaceAttached TCP/IP interface to eri unit 0Attaching interface lo0...doneInitializing DHCP librariesinterrupt: 100 Mbps full duplex link upInitiating DHCP negotiations for eri0dhcpcBind() failed: S_taskLib_NAME_NOT_FOUND

Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.

Sun Fire System FirmwareRTOS version: 39ScApp version: 5.17.1 SC POST diag level: min

The date is Thursday, August 5, 2004, 4:04:34 AM PDT.

Thu Aug 05 04:04:35 noname lom: Boot: ScApp 5.17.1, RTOS 39Thu Aug 05 04:04:43 noname lom: Caching ID informationThu Aug 05 04:04:44 noname lom: Clock Source: 75MHzThu Aug 05 04:04:49 noname lom: /N0/PS0: Status is OKThu Aug 05 04:04:50 noname lom: /N0/PS1: Status is OKThu Aug 05 04:04:50 noname lom: /N0/PS2: Status is OKThu Aug 05 04:04:51 noname lom: /N0/PS3: Status is OKThu Aug 05 04:04:51 noname lom: Chassis is in single partition mode.Thu Aug 05 04:04:55 noname lom: NOTICE: /N0/FT0 is powered off

Connected.

lom>


Initial system verification - showboards, showcomponent

24


Note – At this point, power on the system and check all the PSUs, fans, SBs and IBs using the showboards and showcomponent commands. Do not issue the poweron command. This will run POST and boot the system. Use the poweron all command, which will put the system into standby whilst you check the above.

lom> showboards

Slot Pwr Component Type State Status ---- --- -------------- ----- ------ SSC1 On System Controller Main Passed /N0/SCC - System Config Card Assigned OK /N0/BP - Baseplane Assigned Passed /N0/SIB - Indicator Board Assigned Passed /N0/SPDB - System Power Distribution Bd. Assigned Passed /N0/PS0 Off A166 Power Supply - OK /N0/PS1 Off A166 Power Supply - OK /N0/PS2 Off A166 Power Supply - OK /N0/PS3 Off A166 Power Supply - OK /N0/FT0 Off Fan Tray - Not tested RP0 Off No Grid Power Assigned - RP2 Off No Grid Power Assigned - SB0 Off No Grid Power Assigned - SB2 Off No Grid Power Assigned - IB6 Off No Grid Power Assigned - /N0/MB - Media Bay Assigned Not tested

lom> poweron all

Thu Aug 0504:14:27 noname lom: SysEvent 5 /N0/PS0, power state, On (5,1)Thu Aug 05 04:14:30 noname lom: /N0/SB0, hotplug status, SB0, module inserted (9,17)Thu Aug 05 04:14:30 noname lom: /N0/SB2, hotplug status, SB2, module inserted (9,17)Thu Aug 05 04:14:32 noname lom: /N0/IB6, hotplug status, IB6, module inserted (9,17)Thu Aug 05 04:14:32 noname lom: /N0/RP0, hotplug status, RP0, module inserted (9,17)/N0/PS0: powered on Thu Aug 05 04:14:32 noname lom: Device voltage stabilized: /N0/PS0 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DCThu Aug 05 04:14:33 noname lom: /N0/RP2, hotplug status, RP2, module inserted (9,17)Thu Aug 05 04:14:33 noname lom: /N0/PS0, sensor status, within acceptable limits (7,2,0x607000b000a0000)/N0/PS1: powered on




Thu Aug 05 04:14:34 noname lom: Device voltage stabilized: /N0/PS1 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DCThu Aug 05 04:14:34 noname lom: SysEvent 5 /N0/PS1, power state, On (5,1)Thu Aug 05 04:14:34 noname lom: /N0/PS1, sensor status, within acceptable limits (7,2,0x607010b000a0000)/N0/PS2: powered on Thu Aug 05 04:14:35 noname lom: Device voltage stabilized: /N0/PS2 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DCThu Aug 05 04:14:35 noname lom: SysEvent 5 /N0/PS2, power state, On (5,1)Thu Aug 05 04:14:35 noname lom: /N0/PS2, sensor status, within acceptable limits (7,2,0x607020b000a0000)/N0/PS3: powered on Thu Aug 05 04:14:36 noname lom: Device voltage stabilized: /N0/PS3 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DCThu Aug 05 04:14:36 noname lom: SysEvent 5 /N0/PS3, power state, On (5,1)Thu Aug 05 04:14:36 noname lom: /N0/PS3, sensor status, within acceptable limits (7,2,0x607030b000a0000)/N0/FT0: powered on Thu Aug 05 04:14:52 noname lom: /N0/FT0, fan speed, Low (4,1)/N0/RP0: powered on /N0/RP2: powered on /N0/SB0: powered on /N0/SB2: powered on /N0/IB6: powered on

lom> showboards

Slot Pwr Component Type State Status ---- --- -------------- ----- ------ SSC1 On System Controller Main Passed /N0/SCC - System Config Card Assigned OK /N0/BP - Baseplane Assigned Passed /N0/SIB - Indicator Board Assigned Passed /N0/SPDB - System Power Distribution Bd. Assigned Passed /N0/PS0 On A166 Power Supply - OK /N0/PS1 On A166 Power Supply - OK /N0/PS2 On A166 Power Supply - OK /N0/PS3 On A166 Power Supply - OK /N0/FT0 On Fan Tray Auto Speed Passed /N0/RP0 On Repeater Board Assigned OK /N0/RP2 On Repeater Board Assigned OK /N0/SB0 On CPU Board (Sun Fire V1280, Net Assigned Not tested /N0/SB2 On CPU Board (Sun Fire V1280, Net Assigned Not tested /N0/SB4 On CPU Board (Sun Fire V1280, Net Assigned Not tested /N0/IB6 On PCI I/O Board Assigned Not tested /N0/MB - Media Bay Assigned Passed

lom>

25SunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services


showcomponent

Check out the SBs and the IB using the showcomponent command:

lom> showcomponent /N0/SB0

Component Status Pending POST Description--------- ------ ------- ---- -----------/N0/SB0/P0 enabled - untest UltraSPARC-III+, 900MHz, 8M ECache/N0/SB0/P1 enabled - untest UltraSPARC-III+, 900MHz, 8M ECache/N0/SB0/P2 enabled - untest UltraSPARC-III+, 900MHz, 8M ECache/N0/SB0/P3 enabled - untest UltraSPARC-III+, 900MHz, 8M ECache/N0/SB0/P0/B0/L0 enabled - untest 512M DRAM/N0/SB0/P0/B0/L2 enabled - untest 512M DRAM/N0/SB0/P0/B1/L1 enabled - untest 512M DRAM/N0/SB0/P0/B1/L3 enabled - untest 512M DRAM/N0/SB0/P1/B0/L0 enabled - untest 512M DRAM/N0/SB0/P1/B0/L2 enabled - untest 512M DRAM/N0/SB0/P1/B1/L1 enabled - untest 512M DRAM/N0/SB0/P1/B1/L3 enabled - untest 512M DRAM/N0/SB0/P2/B0/L0 enabled - untest 512M DRAM/N0/SB0/P2/B0/L2 enabled - untest 512M DRAM/N0/SB0/P2/B1/L1 enabled - untest 512M DRAM/N0/SB0/P2/B1/L3 enabled - untest 512M DRAM/N0/SB0/P3/B0/L0 enabled - untest 512M DRAM/N0/SB0/P3/B0/L2 enabled - untest 512M DRAM/N0/SB0/P3/B1/L1 enabled - untest 512M DRAM/N0/SB0/P3/B1/L3 enabled - untest 512M DRAM

lom> showcomponent /N0/IB6

Component Status Pending POST Description--------- ------ ------- ---- -----------/N0/IB6/P0 enabled - untest IO Controller 0/N0/IB6/P1 enabled - untest IO Controller 1/N0/IB6/P0/B0 enabled - untest 66/33MHz. PCI Bus/N0/IB6/P0/B1 enabled - untest 33MHz. PCI Bus/N0/IB6/P1/B0 enabled - untest 66/33MHz. PCI Bus/N0/IB6/P1/B1 enabled - untest 33MHz. PCI Bus/N0/IB6/P0/B1/PCI0 enabled - untest 33MHz. 5V Short PCI card/N0/IB6/P0/B1/PCI1 enabled - untest 33MHz. 5V Short PCI card/N0/IB6/P1/B1/PCI2 enabled - untest 33MHz. 5V Short PCI card/N0/IB6/P1/B1/PCI3 enabled - untest 33MHz. 5V Short PCI card/N0/IB6/P1/B1/PCI4 enabled - untest 33MHz. 5V Short PCI card/N0/IB6/P0/B0/PCI5 enabled - untest 66/33MHz. 3.3V Short PCI card

lom>

Sun Confidential: Internal Only26 V1280/Netra 1280 Quick Reference Guide


Setting up the System Controller


There are a number of commands you need to run here: setupsc, setupnetwork,setdate and if the customer wishes to have a different serial escape sequence from the default, setescape.

Refer to the Sun Fire Entry-Level Midrange System Controller Command Reference Manual & System Administration Guide for complete explanations.

lom> setupsc

System Controller Configuration-------------------------------SC POST diag Level [min]: maxHost Watchdog [enabled]: Rocker Switch [enabled]: disabledSecure Mode [off]: on

PROC RTUs installed: 0PROC Headroom Quantity (0 to disable, 4 MAX) [0]: lom>

Note – Starting with firmware 5.18.0, we can now offer the Capacity on Demand (COD) option. For details review the Capacity on Demand chapter in the Sun Fire Entry-Level Midrange System Administration Manual.

lom> setupnetwork

Network Configuration---------------------Is the system controller on a network? [yes]: Use DHCP or static network settings? [DHCP]: staticHostname []: 1280-scIP Address []: 172.20.40.55Netmask []: 255.255.0.0Gateway []: 172.20.88.1DNS Domain []: uk.sun.comPrimary DNS Server []: 172.20.33.22Secondary DNS Server []: 172.20.33.31Connection type (ssh, telnet, none) [none]: telnet

Rebooting the SC is required for changes in network settings to take effect. lom>



Note – With 5.18..x, you will be offered the option of connecting with a secure shell (ssh) only if you have an SC V2 in the IB/SSC. (Part no 540-6045)

Rebooting the system controller

lom> resetsc

Are you sure you want to reboot the system controller now? [no] yesWaiting for critical processes to finish. This may take a while.Critical processes have finished.

Rebooting. All network client connections closed. Reestablish any needed connections.Mon Oct 25 12:24:31 noname lom: Stopping all services on this SCMon Oct 25 12:24:31 noname lom: All services on this SC have been stopped.

Software Reset...


Memory size = 32MB

Basic sanity checks done.Skipping POST ...ERI Device PresentGetting MAC address for SSC1Using SCC MAC addressMAC address is 00:03:ba:c0:ff:eeHostname: 1280-scAddress: 172.20.40.5Netmask: 255.255.0.0Attached TCP/IP interface to eri unit 0Attaching interface lo0...doneGateway: 172.20.88.1interrupt: 100 Mbps full duplex link up





Sun Fire System FirmwareRTOS version: 41ScApp version: 5.18.0 Build_14SC POST diag level: off

The date is Monday, October 25, 2004, 12:25:08 PM CEST.

Mon Oct 25 12:25:10 1280-sc lom: Boot: ScApp 5.18.0, RTOS 41Mon Oct 25 12:25:17 1280-sc lom: Caching ID informationMon Oct 25 12:25:19 1280-sc lom: Clock Source: 75MHzMon Oct 25 12:25:23 1280-sc lom: /N0/PS0: Status is OKMon Oct 25 12:25:24 1280-sc lom: /N0/PS1: Status is OKMon Oct 25 12:25:24 1280-sc lom: /N0/PS2: Status is OKMon Oct 25 12:25:25 1280-sc lom: /N0/PS3: Status is OKMon Oct 25 12:25:25 1280-sc lom: Chassis is in single partition mode.Mon Oct 25 12:26:19 1280-sc lom: Starting telnet server ...

Connected.

lom>

Tolerate correctable memory errors (5.19.x)

lom> setupsc

System Controller Configuration-------------------------------SC POST diag Level [min]: maxHost Watchdog [enabled]: Rocker Switch [enabled]: disabledSecure Mode [off]:

PROC RTUs installed: 0PROC Headroom Quantity (0 to disable, 4 MAX) [0]: Tolerate correctable memory errors [false]: lom>

Note – The ‘Tolerate correctable memory errors’ parameter was introduced at 5.19.x. For advice on how to set it, refer to the EIS checklist at http://sunweb.germany/EIS/Web/inst-support/checkl.html


Managing the System Controller date & time

30

Managing the System Controller date & time

Displaying the date & time

lom> showdateThu Aug 05 07:49:22 PDT 2004lom>

The syntax of the setdate command is:

setdate [-v] [-t <time zone>] mmddHHMM[[cc]yy][.SS]

Note – Do not do... lom> setdate [-t <time zone>] mmddHHMM[[cc]yy][.SS] Do it in two steps as below (Refer to Bug Id 4764374)

Setting the date & time

First, change the timezone:

lom> showdateThu Aug 05 07:51:41 PDT 2004lom> setdate -t Europe/LondonThu Aug 05 15:52:07 BST 2004lom>

If the date & time are correct for Pacific Standard Time, the will be correct for your timezone. If not, use the command below:

lom> setdate 080515542004Thu Aug 05 15:55:00 BST 2004lom>

Setting the date/time from a network time server

Note: The system must support rdate requests:

lom> setdate -r 192.200.100.89Thu Aug 05 16:01:44 BST 2004lom>


System Monitoring

System Monitoring

System/enclosure level LEDs

Event Monitoring

You can light the alarm LEDs from the lom shell:

lom> showalarm 1alarm1 is offlom> setalarm 1 onlom> showalarm 1alarm1 is onlom>

But a more practical use of the alarms is to use the Solaris LOM commands. A (very basic) example is overleaf:

Name Function

Locator(mirrored on rear)

Normally off. Useful for locating which platform you are working on in a rack. Remember to turn it off again.

lom> showlocatorlocator is offlom> setlocator onlom> showlocatorlocator is onlom>

System Fault(mirrored on rear)

Lights when the LOM detects a fault.

System Power(mirrored on rear)

Lights when the PSUs are powered on, extinguished when the PSUs are in standby.

Top, Access Required A faulty FRU which can only be accessed from above.

Unix Running Extinguished when a fault is detected

Alarm 1 & 2 Triggered by events specified in the LOM (See below)

Source A & B Lit when the relevant power-feeds are present. (See page 20)


System Monitoring

32


# if >lom -f | grep -i fan6 | grep -i fault>then >lom -A on,1 >lom -l>fi7 FT0/FAN6 ft_fan6 FAULT speed 0 %LOM alarm states:Alarm1=onAlarm2=offAlarm3=onFault LED=on#

Power supply LEDs

The power supply LEDs are lit by the PSU itself rather than being driven by the lom shell.

The Power indicator will blink when the system is in STANBY mode, and will become solid after a poweron.

The Fan fault LED will blink if the PSU fan speed falls below a specified limit. Note, the PSU is still providing current.

If the Fault LED lights, replace the PSU.

Note – The PSUs are redundant. You need two out of the four PSUs to be operational.

V1280/Netra 1280 Quick Reference GuideSunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services

System Monitoring

Monitoring from Solaris and the lom shell

You can find much of the information you need from either the lom shell or from Solaris. The only information you can’t get from solaris is the LOM/SC network information. (See appendix for full output)

lom shell command Solaris equivalent

showalarm # cd /usr/platform/sun4u/sbin# ./prtdiag -v | grep -i alarm or# lom -l

showboards prtdiag -v

showcomponent prtdiag -v

showdate # date

showenvironment # lom -t ; lom -v

showescape # lom -c | grep escape

showeventreporting # lom -a | grep event

showfault # lom -l or# lom -a | grep -i fault

showhostname # hostname

showlocator # prtdiag -v | grep -i locatoror# locatoror # lom -a | grep -i locator

showlogs # more /var/adm/messages or# lom -e n,<level>

showmodel # prtdiag -v | grep -i ’System Config’

shownetwork -v # arp 1280-sc1280-sc (192.20.14.6) at 0:3:ba:c0:ff:ee

showresetstate (See page 67)

showsc -v # lom -a | grep -i version

history

inventory # prtfru


System Monitoring

34

Component/Module level LEDs

The above LEDs are found on the following FRUs

● System board

● IB_SSC board (Ok-to-remove doesn’t apply)

● L2 Repeater boards

● Main fan Tray (Ok-to-remove doesn’t apply)

Fan Tray considerations

The fan tray always has the power light on, since the fan tray is available in ON and STANDBY modes

The fan tray will never have the OK-to-remove light on, since you can’t hot swap a fan tray

Caution – Losing main fans 6 & 7 will result in a system reboot. Refer to the Sun Fire V1280/Netra 1280 Systems Service Manual, 817-0510-xx Procedures for replacing individual fans are also in the Service Manual.

Name, Color, and Symbol On Off

Power (green) The board is activated. You must not remove the board when this LED is on.

The board is not activated. You can remove the board when this LED is off.

Fault (amber) An internal fault occurred. No internal fault occurred.

OK-to-remove (amber) You can safely remove the component under hot-pluggable conditions.

You must not remove the component under hot-pluggable conditions.


Error logging


Error logging

The system controller has a 128K error buffer, which is copied to /var/adm/messages. If the system has been down for any reason, the buffer gets flushed to /var/adm/messages at boot time (see page 82). There is no loghost facility for sending SC information to an external loghost.

Get error information by either

# more /var/adm/messages# lom -e n ,<level> for example lom -e 128,3lom> showlogs

Ensure that event reporting is properly configured

lom> showeventreporting

eventreporting is onreporting level is fatal, warning & information (3)lom>

Event reporting levels map to the following:

(0) - Event reporting level=none (1) - Event reporting level=fatal (2) - Event reporting level=fatal & warning (3) - Event reporting level=fatal, warning & information (4) - Event reporting level=fatal, warning, information & user

Level 4 is not used, use level 3.

The eventreporting is on status above, means that messages are printed at the lom prompt, which can be inconvenient if you are working on the console. To stop LOM displaying messages at the lom prompt, type either:

lom> seteventreporting off 3eventreporting is offreporting level is fatal, warning & information (3)lom>

# lom -E off

Note – This will not stop errors getting reported to /var/adm/messages or from going into the error buffer.


Persistent Logging

36

Persistent Logging

Messages are lost if the system controller is rebooted or loses power. Availability 1.2, introduced with 5.17.x firmware, implements persistent logging of error messages in the new 128KB battery backed up NVRAM assuming you have an IB/SSC with a System Controller V2 (FRU 540-6045)

Check if you have an SC V2

lom> showsc

SC: SSC1 System Controller V2Clock failover disabled.

SC date: Fri Aug 06 02:18:43 EST 2004SC uptime: 2 days 6 hours 16 minutes 45 seconds

ScApp version: 5.17.0 RTOS version: 38

Solaris Host Status: Active - Solarislom>

Accessing the persistent log

lom> showlogs -h

Usage: showlogs [-p [-f <filter>] [-n <nnn>]] -d -- specify a domain -p -- persistent log -f -- filter alert -- alert messages critical -- critical messages emergency -- emergency messages error -- error messages fault -- fault messages warning -- warning messages -n -- last number of messages nnn -- number of messages -v -- verbose mode -h -- display this help messagelom>


Firmware Upgrades

Firmware Upgrades

The following components have flash PROMs:

● System boards

● The IB_SSC (both the IB and SC components)

Note – You can upgrade firmware either from the lom shell or using the solaris lom commands. From the lom shell, do lom> flashupdate <options> From solaris, do # lom -G <options>

Do you need to flashupdate?

Use lom shell commands lom> showboards -p version lom> showsc -v to show the revision of your firmware.

Patch information

Firmware is available from sunsolve, in the form of a patch. Refer to

http://pts-americas.west/esg/msg/techinfo/platform/lw8/firmware/

for the latest patch info.


5.19.x firmware for Sun Fire V1280/Netra 1280 Systems

5.19.x firmware for Sun Fire V1280/Netra 1280 Systems

The latest firmware for V1280/Netra 1280 systems is 5.19.x, distributed in patch 114526-xx. This firmware supports Sun Fire E6900/6800/4900/4800/3800/2900, V1280 and Netra 1280 systems.

# ls 114526-06copyrightInstall.infolw8cpu.flash <------ V1280/E2900 system board code.lw8pci.flash <-------V1280/E2900 pci I/O board code.README.114526-06sgcpu.flash <-------E6900/6800/4900/4800/3800 system board code.sgiowci.flashsgiowci_sp.flashsgpci.flash <-------E6900/6800/4900/4800/3800 pci I/O board code.sgrtos.flash <-------Real Time Operating System (RTOS).sgsc.flash <-------System Controller Application (for LW8, LOM)

For V1280 platforms, refer to the Sun Fire Entry-Level Midrange System manuals.

Sun_Fire_Entry-Level_Midrange_System_Administration_Guide.pdfSun_Fire_Entry-Level_Midrange_System_Controller_Command_Reference_Manual.pdfSun_Fire_Entry-Level_Midrange_System_Firmware_5.19.0_Release_Notes.pdf

flashupdating from 5.13.x to 5.19.x

Upgrade from 5.13.x to 5.18.1 in two steps:

flashupdate -f <URL> rtos scapp flashupdate -f <URL> systemboards

Caution – The flashupdate utility at 5.13.x has no knowledge of lw8cpu.flash and lw8pci.flash. flashupdate -f <URL> all will install sgcpu.flash and sgpci.flash on the V1280 systemboards, rendering them inoperable with the message below. For more detail, see SRDB 75895.

WARNING: Incompatible firmware detected. Please use flashupdate to update the firmware on the board /N0/xx

To recover, you must downgrade to 5.13.0015, again in two steps; flashupdate -f <URL> rtos scapp flashupdate -f <URL> systemboards



ftp server setup


ftp server setup

The customer may be happy to allow you to do a flashupdate or a showresetstate using user passwords. For example:

flashupdate -f ftp://root:[email protected]/11xxxx-01 all showresetstate -v -f ftp://admin:[email protected]//home/admin/reset_info

However, they may not. You may need to setup an ftp server.

ftp server setup at Solaris 9

admin-ws# uname -aSunOS esg-admin 5.9 Generic_112233-12 sun4u sparc SUNW,Ultra-5_10admin-ws# ftpconfig /export/ftpCreating user ftp

Creating directory /export/ftpUpdating directory /export/ftp

admin-ws#

ftp server setup at Solaris 8

The procedure to setup an ftp server is wrapped up in the ftpd man page.

To set up anonymous ftp, add the following entry to the /etc/passwd file. In this example, /export/ftp was chosen to be the anonymous ftp area, and the shell is the non-existent file /nosuchshell. This prevents users from logging in as the ftp user.

ftp:x:30000:30000:Anonymous FTP:/export/ftp:/nosuchshell

Add the following entry to the /etc/shadow file:

ftp:NP:6445::::::

Now run the shell script from the ftpd man page. A way of doing this is as follows. Copy the man page output into /var/tmp.

# man ftpd > /var/tmp/ftp_script

Edit the file to extract the script. It starts in the usual manner...


ftp server setup

40

#!/bin/sh # script to setup anonymous ftp area # # verify you are root /usr/bin/id | grep -w ’uid=0’ >/dev/null 2>&1 . and finishes... . #fi #chown root ${ftphome}/pub #chmod 1755 ${ftphome}/pub

# cd /var/tmp # chmod 777 ftp_script # ./ftp_script Setting up anonymous ftp area /export/ftp cp: /usr/lib/security/sparcv9: is a directory

#

mkdir /export/ftp/pub and copy the patch into it

# cd /export/ftp/pub# unzip 114524-02.zip

Archive: 114524-02.zip creating: 114524-02/ inflating: 114524-02/Sun_Fire_Entry Level_Midrange_Sys_Admin_Guide.pdf inflating: 114524-02/Sun_Fire_Entry-Level_Midrange_SC_Comm_Ref_Manual.pdf .. inflating: 114524-02/copyright inflating: 114524-02/lw8cpu.flash inflating: 114524-02/lw8pci.flash inflating: 114524-02/sgcpu.flash inflating: 114524-02/sgiowci.flash inflating: 114524-02/sgiowci_sp.flash inflating: 114524-02/sgpci.flash inflating: 114524-02/sgrtos.flash inflating: 114524-02/sgsc.flash #


Updating from lom shell - flashupdate



lom> help flashupdate

flashupdate -- update firmware

Usage: flashupdate [-y|-n] -f <URL> all flashupdate [-y|-n] -f <URL> systemboards|scapp|rtos|<board> ... flashupdate [-y|-n] -u flashupdate [-y|-n] -c <source board> <destination board> ... flashupdate -h

-y -- do not prompt for confirmation -n -- do not execute command if confirmation is requested -f -- specify a URL as the source of the flash images <URL> -- the URL of the directory containing the flash images supported protocols: FTP and HTTP ftp://[<userid>:<password>@]<hostname>/<path> http://<hostname>/<path> -c -- specify a board as the source of the flash images -u -- upgrade boards to current firmware all -- the SC and all the system boards scapp -- the system controller Updating ScApp requires the SC to be rebooted.

rtos -- the Real Time OS for the SC Updating RTOS requires the SC to be rebooted.

systemboards -- all the CPU and IO boards

-h -- display this help message

lom>

● Systemboards values are:

● System board sb0, sb2 and sb4

● I/O assembly ib6

● flashupdate -u is not recommended.



42


flashupdate - example

Note – Since the SSC will reboot during this procedure, do this on the IB/SSC serial connection.

lom> flashupdate -f ftp://129.156.186.23/pub/114525-02 rtos scapp

As part of this update, the system controller will automatically reboot.RTOS will be upgraded automatically during the next boot. ScApp will be upgraded automatically during the next boot. Rebooting will interrupt any current operations.This includes keyswitch changes, Solaris reboots and all current connections.Do you want to continue? [no] yesWaiting for critical processes to finish. This may take a while.Critical processes have finished.No boards can be updated.

Rebooting the SC to automatically complete the upgrade.

Rebooting. All telnet connections closed. Reestablish any needed connections.

Software Reset...


Memory size = 32MB

Basic sanity checks done.Skipping POST ...ERI Device PresentGetting MAC address for SSC1Using SCC MAC addressMAC address is 0:3:ba:c0:ff:eeHostname: v1280a-scAddress: 10.16.43.41Netmask: 255.255.255.0Attached TCP/IP interface to eri unit 0Attaching interface lo0...doneGateway: 10.16.43.254interrupt: 100 Mbps full duplex link up




FlashupdateConnecting to 129.156.186.23...Transferring sgrtos.flash via FTP : 692552 Validating RTOS flash image...Updating flashprom sectors at address 0x20000000: 11/11 = 100%ok

Connecting to 129.156.186.23...Transferring sgsc.flash via FTP : 6349779 Validating ScApp flash image...Updating flashprom sectors at address 0x36000000: 97/97 = 100%ok

Software Reset...


Memory size = 32MB

Basic sanity checks done.Skipping POST ...ERI Device PresentGetting MAC address for SSC1Using SCC MAC addressMAC address is 0:3:ba:c0:ff:eeHostname: v1280a-scAddress: 10.16.43.41Netmask: 255.255.255.0Attached TCP/IP interface to eri unit 0Attaching interface lo0...doneGateway: 10.16.43.254interrupt: 100 Mbps full duplex link up



The date is Tuesday, March 29, 2005, 11:21:11 AM CEST.



44


Tue Mar 29 11:21:13 v1280a-sc lom: Boot: ScApp 5.18.1, RTOS 41Tue Mar 29 11:21:20 v1280a-sc lom: Caching ID informationTue Mar 29 11:21:21 v1280a-sc lom: Clock Source: 75MHzTue Mar 29 11:21:26 v1280a-sc lom: /N0/PS0: Status is OKTue Mar 29 11:21:27 v1280a-sc lom: /N0/PS1: Status is OKTue Mar 29 11:21:27 v1280a-sc lom: /N0/PS2: Status is OKTue Mar 29 11:21:28 v1280a-sc lom: /N0/PS3: Status is OKTue Mar 29 11:21:28 v1280a-sc lom: Chassis is in single partition mode.

Connected.

Mar 29 11:23:56 v1280a lw8: Starting telnet server ...

#

lom> showboards -p version

lom>showboards -p version

Component Compatible Version --------- ---------- ------- SSC1 Reference 5.18.1 Build_01 /N0/IB6 Yes 5.17.2 /N0/SB0 Yes 5.17.2

lom> flashupdate -f ftp://129.156.186.23/pub/114524-02 systemboards

Waiting for critical processes to finish. This may take a while.Critical processes have finished.

Retrieving: ftp://129.156.186.23/pub/114525-02/lw8cpu.flashValidating ................ Done

Programming PROM /N0/SB0/FP0Erasing ............... DoneProgramming ............... DoneVerifying ............... Done

Programming PROM /N0/SB0/FP1Erasing ............... DoneProgramming ............... DoneVerifying ............... Done

Retrieving: ftp://129.156.186.23/pub/114525-02/lw8pci.flashValidating ...... Done

Programming PROM /N0/IB6/FP0Erasing ...... Done




Programming ...... DoneVerifying ...... Donelom>lom> console

# prtconf -V

OBP 5.17.2 08/13/04 11:52

#

Note – You need to reboot (at the customers convenience) to load the new OBP into the system.

lom> shutdownShutting down Solaris ...lom>Powering boards off ......lom> poweron...


Updating from Solaris - lom -G

46


Place the patch in a suitable directory, for example /var/tmp, and issue the lom -G commands in the following order:

# lom -G sgrtos.flash # lom -G sgsc.flash lom> resetsc -y # lom -G lw8cpu.flash # lom -G lw8pci.flash

Note – At 5.19.x, the SC automatically reboots after updating the sgsc.flash firmware. Older revs of firmware still require the manual reboot using the resetsc -y command Also make sure you have the latest LOM patch 110208-xx installed

lom -G - example

# prtconf -V

OBP 5.19.0 06/30/05 14:08

# <--- Type escape sequence e.g. #.

lom> showb -p version

Component Compatible Version --------- ---------- ------- SSC1 Reference 5.19.0 Build_17.1 /N0/IB6 Yes 5.19.0 Build_17.1 /N0/SB0 Yes 5.19.0 Build_17.1

lom> showsc -v

SC: SSC1 System Controller

SC date: Wed Mar 29 16:15:37 BST 2006 Europe/London GMT+00:00 Greenwich Mean Time SC uptime: 19 minutes 29 seconds

ScApp version: 5.19.0 Build_17.1



Version build: 17.1Version String: 5.19.0RTOS version: 43

SC POST diag level: off

Clock source is: 75MHz

Solaris Host Status: Active - Solaris

Chassis HostID: 83199115PROC RTUs installed: 0PROC Headroom Quantity: 0lom> console

# lom -G /var/tmp/114526-06/sgrtos.flashThis program will replace LOM firmware with version 5.11.3 <--- See Bug ID: 6266849Are you sure you want to continue?Enter ’C’ and return to Continue or anything else to TerminateCTransferring 679 kB image to the system controller.This may take several minutes....................................................

Validating image...679 kB RTOS image transferred.Programming sun.serengeti.RTOSFlash@ff1803f3Comparing image and flash# Image and flash are different, proceeding with update.Erasing ........... DoneProgramming ........... DoneVerifying ........... DoneMar 29 16:20:51 v1280 lw8: sun.serengeti.RTOSFlash@ff1803f3 updated with version 5.11.3 09/07/2005.

Firmware update complete.

You must reboot the system controller to load the new firmware.At the lom> prompt enter ’’resetsc -y’’ to reboot the system controller.

<-- No need to reboot the SC yet - Hit RETURN

# lom -G /var/tmp/114526-06/sgsc.flashThis program will replace LOM firmware with version 5.19.5Are you sure you want to continue?Enter ’C’ and return to Continue or anything else to Terminate



48


CTransferring 6353 kB image to the system controller.This may take several minutes....................................................

Validating image...6353 kB SC image transferred.

ScApp firmware will now be updated and the system controller rebooted.Mar 29 16:35:33 v1280 lw8: Stopping all services on this SCMar 29 16:35:33 v1280 lw8: All services on this SC have been stopped.Updating flashprom sectors at address 0x36000000: 100/100 = 100%ok

Software Reset....


Memory size = 32MB

Basic sanity checks done.Skipping POST ...ERI Device PresentGetting MAC address for SSC1Using SCC MAC addressMAC address is 0:3:ba:c0:ff:eeHostname: v1280a-ssc1Address: 129.156.22.33Netmask: 255.255.248.0Attached TCP/IP interface to eri unit 0Attaching interface lo0...doneGateway: 129.156.208.1interrupt: 100 Mbps full duplex link up

Copyright 2006 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.


The date is Wednesday, March 29, 2006, 4:37:38 PM BST.



Connected.Mar 29 16:39:22 v1280 lw8: Unretrieved lom log history follows ...^MMar 29 16:39:22 v1280 ^MMar 29 16:39:22 v1280 lw8: 3/29/06 4:37:39 PM Boot: ScApp 5.19.5, RTOS 45^MMar 29 16:39:23 v1280 lw8: 3/29/06 4:37:46 PM Caching ID information^MMar 29 16:39:23 v1280 lw8: 3/29/06 4:37:47 PM Clock Source: 75MHz^MMar 29 16:39:23 v1280 lw8: 3/29/06 4:37:52 PM /N0/PS0: Status is OK^MMar 29 16:39:23 v1280 lw8: 3/29/06 4:37:52 PM /N0/PS1: Status is OK^MMar 29 16:39:23 v1280 lw8: 3/29/06 4:37:53 PM /N0/PS2: Status is OK^MMar 29 16:39:24 v1280 lw8: 3/29/06 4:37:53 PM /N0/PS3: Status is Failed^MMar 29 16:39:24 v1280 lw8: 3/29/06 4:37:55 PM Chassis is in single partition mode.^MMar 29 16:39:24 v1280 lw8: Starting telnet server ...

<--- Hit RETURN

# lom -G /var/tmp/114526-06/lw8cpu.flash

This program will replace LOM firmware with version 5.19.5Are you sure you want to continue?Enter ’C’ and return to Continue or anything else to TerminateCTransferring 1090 kB image to the system controller.This may take several minutes....................................................

Validating image...# 1090 kB CPU image transferred.Programming /N0/SB0/FP0Comparing image and flashImage and flash are different, proceeding with update.Erasing .................. DoneProgramming .................. DoneVerifying .................. DoneMar 29 16:51:29 v1280a lw8: /N0/SB0/FP0 updated with version 5.19.5 02/06/2006.Programming /N0/SB0/FP1Comparing image and flashImage and flash are different, proceeding with update.Erasing .................. DoneProgramming .................. DoneVerifying .................. DoneMar 29 16:52:29 v1280a lw8: /N0/SB0/FP1 updated with version 5.19.5 02/06/2006.


You must reboot Solaris to load the new firmware.<--- Hit RETURN



50

# lom -G /var/tmp/114526-06/lw8pci.flash

This program will replace LOM firmware with version 5.19.5Are you sure you want to continue?Enter ’C’ and return to Continue or anything else to TerminateCTransferring 410 kB image to the system controller.This may take several minutes....................................................

Validating image...# 410 kB IO image transferred.Programming /N0/IB6/FP0Comparing image and flashImage and flash are different, proceeding with update.Erasing ....... DoneProgramming ....... DoneVerifying ....... DoneMar 29 16:58:00 v1280a lw8: /N0/IB6/FP0 updated with version 5.19.5 02/06/2006.


You must reboot Solaris to load the new firmware.

<--- Hit RETURN# <--- Type escape sequence e.g. #.

lom> showboards -p version

Component Compatible Version --------- ---------- ------- SSC1 Reference 5.19.5 Build_01 /N0/IB6 Yes 5.19.5 Build_01 /N0/SB0 Yes 5.19.5 Build_01

lom> showsc

SC: SSC1 System Controller

SC date: Wed Mar 29 16:59:42 BST 2006SC uptime: 15 minutes 30 seconds

ScApp version: 5.19.5 Build_01RTOS version: 45



Solaris Host Status: Active - Solaris

Chassis HostID: 83199115PROC RTUs installed: 0PROC Headroom Quantity: 0

lom> console

# prtconf -V

OBP 5.19.0 06/30/05 14:08

#

Note – You need to reboot (at the customers convenience) to load the new OBP into the system.

lom> shutdownShutting down Solaris ...lom>Powering boards off ......lom> poweron...


Setting a LOM Shell Password

52

Setting a LOM Shell Password

The password command sets the password for the LOM shell.

Before allowing the password to be changed, the current password must be authenticated. Changed passwords take effect immediately. The old password is no longer accepted.

You can remove the password by pressing Return at the Enter new password and Enter new password again prompts.

Password example

To set a password, type the following:

lom> passwordEnter new password: xxyyzzEnter new password again: xxyyzz

lom>

When the password is already set and the administrator needs to change the password, type the following:

lom> passwordEnter current password: xxyyzzEnter new password: aabbccEnter new password again: aabbcclom>


Resetting LOM Shell Passwords


If the LOM shell password is lost, use the procedure below.

# telnet 1280-scTrying 192.200.10.55...Connected to 192.200.10.55.Escape character is ’^]’.Enter Password: <---hit Enter

Invalid password.Enter Password: <---hit Enter

Invalid password.Enter Password: <---hit Enter

Invalid password.

HostID: 831954f6ScApp version: 5.17.1RTOS version: 38

Connection to 192.200.10.55 closed by foreign host.bash-2.03#

Note – Or, the system will prompt as below from applying AC or DC power.

Hardware Reset...


Memory size = 32MB

Basic sanity checks done.Skipping POST .....Sun Fire System FirmwareRTOS version: 39ScApp version: 5.17.0 SC POST diag level: off



54

The date is Tuesday, April 13, 2004, 9:53:45 AM GMT+01:00.

Tue Apr 13 09:53:46 1280-sc lom: Boot: ScApp 5.17.0, RTOS 39Tue Apr 13 09:53:54 1280-sc lom: Caching ID informationTue Apr 13 09:53:56 1280-sc lom: Clock Source: 75MHzTue Apr 13 09:54:01 1280-sc lom: /N0/PS0: Status is OKTue Apr 13 09:54:01 1280-sc lom: /N0/PS1: Status is OKTue Apr 13 09:54:02 1280-sc lom: /N0/PS2: Status is OKTue Apr 13 09:54:02 1280-sc lom: /N0/PS3: Status is OKTue Apr 13 09:54:03 1280-sc lom: Chassis is in single partition mode.

Enter Password: <--- Hit enter

Invalid password.Enter Password: <--- Hit enter

Invalid password.Enter Password: <--- Hit enter

Invalid password.

HostID: 8319911eScApp version: 5.13.0009RTOS version: 23

Note – Go to the following URL to obtain a service mode password. https://sfservicepass.sfbay/ Notice below, you have entered the solaris operating environment.

Enter Password: <--- Use the service mode password obtained aboveConnected.

bash-2.03# lom -c | grep escapeserial escape sequence=#.bash-2.03# <--- Type #.

lom> passwordEnter current password: <--- Use the service mode password obtained aboveEnter new password: <--- Hit enterEnter new password again: <--- Hit enterlom>


Booting the system for the first time



To boot up a system for the first time, issue the bootmode and poweron commands as shown below.

Note – The default for the system is auto-boot?=true. Use bootmode forth to stop the boot sequence at the ok prompt, so a show-post-results and probe-scsi-all may be run. If the POST takes longer than 10 minutes to run, the forth option will time out and the system will attempt to boot. If it does, proceed as below: SunOS Release 5.8 Version Generic_108528-22 64-bit Copyright 1983-2003 Sun Microsystems, Inc.All rights reserved. / #. <--- escape sequence lom> break This will suspend Solaris. Do you want to continue? [no] yes Starting Forth interpreter - type "resume" to continue. {0} ok setenv auto-boot? false auto-boot? = false {0} ok reset-all Resetting ...

lom> bootmode forthlom> poweron

/N0/PS0: already on/N0/PS1: already on/N0/PS2: already on/N0/PS3: already onPowering boards on ...Testing CPU Boards ...{/N0/SB0/P0} Running CPU POR and Set Clocks{/N0/SB0/P1} Running CPU POR and Set Clocks{/N0/SB0/P0} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P2} Running CPU POR and Set Clocks{/N0/SB0/P1} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P3} Running CPU POR and Set Clocks{/N0/SB0/P0} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P2} @(#) lpost 5.18.0 2004/09/20 21:23



56

{/N0/SB0/P1} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P3} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P2} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P0} Use is subject to license terms.{/N0/SB0/P3} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P1} Use is subject to license terms.{/N0/SB0/P2} Use is subject to license terms.{/N0/SB0/P3} Use is subject to license terms.{/N0/SB0/P0} Running Basic CPU {/N0/SB0/P1} Running Basic CPU {/N0/SB0/P2} Running Basic CPU {/N0/SB0/P0} Subtest: Setting Fireplane Config Registers {/N0/SB0/P3} Running Basic CPU {/N0/SB0/P2} Subtest: Setting Fireplane Config Registers for aid 0x2{/N0/SB0/P1} Subtest: Setting Fireplane Config Registers {/N0/SB0/P3} Subtest: Setting Fireplane Config Registers for aid 0x3{/N0/SB0/P2} Subtest: Display CPU Version, frequency {/N0/SB0/P3} Subtest: Display CPU Version, frequency {/N0/SB0/P2} Version register = 003e0015.22000507{/N0/SB0/P3} Version register = 003e0015.22000507{/N0/SB0/P0} Subtest: Display CPU Version, frequency {/N0/SB0/P1} Subtest: Display CPU Version, frequency {/N0/SB0/P0} Version register = 003e0015.22000507{/N0/SB0/P2} Ecache Control Register 00000000.07a34c00{/N0/SB0/P1} Version register = 003e0015.22000507{/N0/SB0/P3} Ecache Control Register 00000000.07a34c00{/N0/SB0/P0} Ecache Control Register 00000000.07a34c00{/N0/SB0/P1} Ecache Control Register 00000000.07a34c00{/N0/SB0/P2} Cpu/System ratio = 6, cpu actual frequency = 900{/N0/SB0/P3} Cpu/System ratio = 6, cpu actual frequency = 900{/N0/SB0/P0} Cpu/System ratio = 6, cpu actual frequency = 900{/N0/SB0/P1} Cpu/System ratio = 6, cpu actual frequency = 900{/N0/SB0/P2} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P3} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P0} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P2} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P3} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P1} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P2} Use is subject to license terms.{/N0/SB0/P3} Use is subject to license terms.{/N0/SB0/P0} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P1} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P2} Subtest: I-Cache Initialization {/N0/SB0/P3} Subtest: I-Cache Initialization {/N0/SB0/P0} Use is subject to license terms.{/N0/SB0/P1} Use is subject to license terms.{/N0/SB0/P2} Subtest: D-Cache Initialization




{/N0/SB0/P3} Subtest: D-Cache Initialization {/N0/SB0/P2} Subtest: W-Cache Initialization {/N0/SB0/P3} Subtest: W-Cache Initialization {/N0/SB0/P0} Subtest: I-Cache Initialization {/N0/SB0/P1} Subtest: I-Cache Initialization {/N0/SB0/P2} Subtest: P-Cache Initialization {/N0/SB0/P3} Subtest: P-Cache Initialization {/N0/SB0/P0} Subtest: D-Cache Initialization {/N0/SB0/P1} Subtest: D-Cache Initialization {/N0/SB0/P2} Subtest: Branch Prediction Initialization {/N0/SB0/P3} Subtest: Branch Prediction Initialization {/N0/SB0/P0} Subtest: W-Cache Initialization {/N0/SB0/P1} Subtest: W-Cache Initialization {/N0/SB0/P2} Subtest: E-Cache Global Variables Initialization {/N0/SB0/P3} Subtest: E-Cache Global Variables Initialization {/N0/SB0/P0} Subtest: P-Cache Initialization {/N0/SB0/P1} Subtest: P-Cache Initialization {/N0/SB0/P2} Subtest: Fast Init. Verification Test {/N0/SB0/P3} Subtest: Fast Init. Verification Test {/N0/SB0/P0} Subtest: Branch Prediction Initialization {/N0/SB0/P1} Subtest: Branch Prediction Initialization {/N0/SB0/P0} Subtest: E-Cache Global Variables Initialization {/N0/SB0/P1} Subtest: E-Cache Global Variables Initialization {/N0/SB0/P0} Subtest: Fast Init. Verification Test {/N0/SB0/P1} Subtest: Fast Init. Verification Test {/N0/SB0/P0} Running Enable MMU{/N0/SB0/P1} Running Enable MMU{/N0/SB0/P2} Running Enable MMU{/N0/SB0/P3} Running Enable MMU{/N0/SB0/P3} Subtest: IMMU Initialization {/N0/SB0/P2} Subtest: IMMU Initialization {/N0/SB0/P0} Subtest: IMMU Initialization {/N0/SB0/P1} Subtest: IMMU Initialization {/N0/SB0/P0} Subtest: DMMU Initialization {/N0/SB0/P1} Subtest: DMMU Initialization {/N0/SB0/P0} Subtest: Map LPOST to local space {/N0/SB0/P1} Subtest: Map LPOST to local space {/N0/SB0/P2} Subtest: DMMU Initialization {/N0/SB0/P3} Subtest: DMMU Initialization {/N0/SB0/P2} Running FPU Tests{/N0/SB0/P0} Running FPU Tests{/N0/SB0/P1} Running FPU Tests{/N0/SB0/P3} Running FPU Tests{/N0/SB0/P2} Subtest: Map LPOST to local space {/N0/SB0/P3} Subtest: Map LPOST to local space {/N0/SB0/P0} Running Basic Ecache{/N0/SB0/P1} Running Basic Ecache{/N0/SB0/P2} Running Basic Ecache



58


{/N0/SB0/P3} Running Basic Ecache{/N0/SB0/P0} Subtest: E-Cache Initialization of first 1K {/N0/SB0/P1} Subtest: E-Cache Initialization of first 1K {/N0/SB0/P2} Subtest: E-Cache Initialization of first 1K {/N0/SB0/P3} Subtest: E-Cache Initialization of first 1K {/N0/SB0/P0} Subtest: E-Cache Initialization {/N0/SB0/P1} Subtest: E-Cache Initialization {/N0/SB0/P2} Subtest: E-Cache Initialization {/N0/SB0/P3} Subtest: E-Cache Initialization {/N0/SB0/P2} Running Memory Registers Tests{/N0/SB0/P3} Running Memory Registers Tests{/N0/SB0/P0} Running Memory Registers Tests{/N0/SB0/P3} Subtest: Disable Memory Controllers {/N0/SB0/P1} Running Memory Registers Tests{/N0/SB0/P2} Subtest: Disable Memory Controllers {/N0/SB0/P0} Subtest: Disable Memory Controllers {/N0/SB0/P1} Subtest: Disable Memory Controllers {/N0/SB0/P0} Running Memory Configuration Tests{/N0/SB0/P2} Running Memory Configuration Tests{/N0/SB0/P1} Running Memory Configuration Tests{/N0/SB0/P3} Running Memory Configuration Tests{/N0/SB0/P0} Subtest: Memory Controller Configuration {/N0/SB0/P1} Subtest: Memory Controller Configuration {/N0/SB0/P2} Subtest: Memory Controller Configuration {/N0/SB0/P3} Subtest: Memory Controller Configuration {/N0/SB0/P0} Subtest: UP Memory Clear {/N0/SB0/P1} Subtest: UP Memory Clear {/N0/SB0/P2} Subtest: UP Memory Clear {/N0/SB0/P3} Subtest: UP Memory Clear {/N0/SB0/P2} Running Memory Tests{/N0/SB0/P3} Running Memory Tests{/N0/SB0/P0} Running Memory Tests{/N0/SB0/P1} Running Memory Tests{/N0/SB0/P0} Running Advanced CPU Tests{/N0/SB0/P1} Running Advanced CPU Tests{/N0/SB0/P2} Running Advanced CPU Tests{/N0/SB0/P3} Running Advanced CPU Tests{/N0/SB0/P0} Running CPU ECC Tests{/N0/SB0/P1} Running CPU ECC Tests{/N0/SB0/P2} Running CPU ECC Tests{/N0/SB0/P3} Running CPU ECC Tests{/N0/SB0/P0} Running System Level Tests{/N0/SB0/P2} Running System Level Tests{/N0/SB0/P3} Running System Level Tests{/N0/SB0/P1} Running System Level Tests{/N0/SB0/P0} Running Board Memory Interleave{/N0/SB0/P1} Running Board Memory Interleave{/N0/SB0/P0} Subtest: Board Memory Interleave Configuration




{/N0/SB0/P1} Subtest: Board Memory Interleave Configuration {/N0/SB0/P2} Running Board Memory Interleave{/N0/SB0/P3} Running Board Memory Interleave{/N0/SB0/P2} Subtest: Board Memory Interleave Configuration {/N0/SB0/P3} Subtest: Board Memory Interleave Configuration {/N0/SB0/P0} Passed{/N0/SB0/P1} Passed{/N0/SB0/P2} Passed{/N0/SB0/P3} PassedTesting IO Boards ...Copying IO PROM to CPU DRAM............................................{/N0/SB0/P0} Running PCI IO Controller Basic Tests{/N0/SB0/P0} Jumping to memory 00000000.00000020 [00000010]{/N0/SB0/P0} System PCI IO post code running from memory{/N0/SB0/P0} @(#) lpost 5.18.0 2004/09/20 21:28{/N0/SB0/P0} Running PCI IO Controller Functional Tests{/N0/SB0/P0} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P0} Use is subject to license terms.{/N0/SB0/P0} Subtest: PCI IO Controller Register Initialization for aid 0x18{/N0/SB0/P0} Running PCI IO Controller Ecc Tests{/N0/SB0/P0} Running SBBC Basic Tests{/N0/SB0/P0} Subtest: SBBC PCI Reg Initialization for aid 0x18{/N0/SB0/P0} Running IDE Controller Tests{/N0/SB0/P0} Subtest: IDE Controller PCI Config Space Test for aid 0x18{/N0/SB0/P0} Running SCSI Controller Tests{/N0/SB0/P0} Subtest: SCSI Controller PCI Config Space Test for aid 0x18{/N0/SB0/P0} Running Probe io Devices{/N0/SB0/P0} Running PCI IO Controller Basic Tests{/N0/SB0/P0} Subtest: PCI IO Controller Register Initialization for aid 0x19{/N0/SB0/P0} Running PCI IO Controller Functional Tests{/N0/SB0/P0} Running PCI IO Controller Ecc Tests{/N0/SB0/P0} Running Ethernet0 Tests{/N0/SB0/P0} Subtest: Ethernet0 PCI Config Space Test for aid 0x19{/N0/SB0/P0} Running Ethernet1 Tests{/N0/SB0/P0} Subtest: Ethernet1 PCI Config Space Test for aid 0x19{/N0/SB0/P0} Running Probe io Devices{/N0/SB0/P0} @(#) lpost 5.18.0 2004/09/20 21:23{/N0/SB0/P0} Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.{/N0/SB0/P0} Use is subject to license terms.{/N0/IB6/P0} Passed{/N0/IB6/P1} PassedTesting domain ...{/N0/SB0/P0} Running Domain Level Tests{/N0/SB0/P0} Subtest: Mapping IO SRAM {/N0/SB0/P0} Subtest: Memory interleaving config {/N0/SB0/P0} Running Domain Basic Tests{/N0/SB0/P0} Subtest: Cross Call Test {/N0/SB0/P0} Running Domain Advanced Tests



60


{/N0/SB0/P0} Subtest: MP Memory Clear Test {/N0/SB0/P0} CORE 1 clearing 00000000.00000000 to 00000000.80000000{/N0/SB0/P0} CORE 2 clearing 00000000.80000000 to 00000001.00000000{/N0/SB0/P0} CORE 3 clearing 00000001.00000000 to 00000001.80000000{/N0/SB0/P0} CORE 0 clearing 00000001.80000000 to 00000002.00000000{/N0/SB0/P0} Running Domain Stick Sync Tests{/N0/SB0/P0} Subtest: Sync. Stick Registers Test {/N0/SB0/P0} Running Domain Verify Stick Sync Tests{/N0/SB0/P0} Subtest: Verify Sync. Stick Registers Test {/N0/SB0/P0} DCB_DECOMP_OBP command succeeded {/N0/SB0/P0} Decompress OBP done{/N0/SB0/P0} DCB_ENTER_OBP command succeeded {/N0/SB0/P1} DCB_ENTER_OBP command succeeded {/N0/SB0/P2} DCB_ENTER_OBP command succeeded {/N0/SB0/P3} DCB_ENTER_OBP command succeeded Entering OBP ...

lom>Sun Fire V1280OpenFirmware version 5.18.0 (09/20/04 21:22)Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.SmartFirmware, Copyright (C) 1996-2001. All rights reserved.8192 MB memory installed, Serial #51992949.Ethernet address 0:3:ba:19:59:75, Host ID: 83195975.

NOTICE: Ignoring auto-boot? setting because bootmode "forth" is set{0} ok

Note – bootmode forth does not work on a reboot or init 6. bootmode forth only works with the poweron command (Refer to BugId 4748606)


show-post-results / probe-scsi-all


show-post-results / probe-scsi-all

{0} ok show-post-results

Board 0, Type: CPU/Memory

port 0 - Status = Pass, Type: CPU/Memory E-cache: 8 MB R-freq: 900 MHz A-freq: 900 MHz port 1 - Status = Pass, Type: CPU/Memory E-cache: 8 MB R-freq: 900 MHz A-freq: 900 MHz port 2 - Status = Pass, Type: CPU/Memory E-cache: 8 MB R-freq: 900 MHz A-freq: 900 MHz port 3 - Status = Pass, Type: CPU/Memory E-cache: 8 MB R-freq: 900 MHz A-freq: 900 MHz

Board 6, Type: Sun Fire V1280 PCI IO

port 24 - Status = Pass, Type: Sun Fire V1280 PCI IO port 25 - Status = Pass, Type: Sun Fire V1280 PCI IO

{0} ok probe-scsi-all

/ssm@0,0/pci@18,600000/scsi@2,1

/ssm@0,0/pci@18,600000/scsi@2

Target 0 Unit 0 Disk SEAGATE ST373453LSUN72G 0249Target 1 Unit 0 Disk SEAGATE ST373453LSUN72G 0249Target 4 Unit 0 Removable Tape HP C7438A V309

/ssm@0,0/pci@18,600000/scsi@1,1

/ssm@0,0/pci@18,600000/scsi@1

/ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4

{0} ok


bootmode options

62


bootmode options

Say we want to get to the ok prompt from poweron, but the NVRAM parameter is set to auto-boot? true. Here is another method of doing so.

lom> bootmode skipdiag forthlom> bootmodeUsage: bootmode normal bootmode [diag|skipdiag] [forth] [reset_nvram] bootmode -h

bootmode is forth skipdiaglom>

Note – Don’t use bootmode diag if you are running a pre 5.13.0014 platform. SunAlert 53523 refers.

lom> poweronPowering boards on ...Testing CPU Boards ...{/N0/SB0/P0} Passed{/N0/SB0/P1} Passed{/N0/SB0/P2} Passed{/N0/SB0/P3} Passed..Testing IO Boards ...{/N0/IB6/P0} Passed{/N0/IB6/P1} PassedTesting domain ...Entering OBP ...lom>

Sun Fire V1280OpenFirmware version 5.17.0 (03/05/04 11:28)Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.SmartFirmware, Copyright (C) 1996-2001. All rights reserved.8192 MB memory installed, Serial #51991789.Ethernet address 0:3:ba:c0:ff:dc, Host ID: 83c0ffdc.

NOTICE: Ignoring auto-boot? setting because bootmode "forth" is set{0} ok


Displaying NVRAM parameters

Displaying NVRAM parameters

NVRAM parameters are stored in the NVCI on the SC, and determine the system configuration and related communication characteristics.

{0} ok printenv

Variable Value (Default Value)-------------------------------------------------------------------------nvramrcdiag-level init (init)reboot-on-error false (false)interleave-mode optimal (optimal)interleave-scope within-board (within-board)error-level max (max)verbosity-level min (min)secondary-diag? false (false)auto-boot-timeout 512 (512)scsi-initiator-id 7 (7)powerfail-time 0 (0)fcode-debug? true (true)output-device /sgcn (/sgcn)input-device /sgcn (/sgcn)load-base 0x4000 (0x4000)boot-command boot (boot)auto-boot? true (true)error-reset-recovery sync (sync)diag-file ()boot-file ()diag-device disk (disk diskifp diskglm diskc net)boot-device disk (disk diskifp diskglm diskc net)local-mac-address? false (false)ansi-terminal? true (true)screen-#columns 80 (80)screen-#rows 34 (34)silent-mode? false (false)use-nvramrc? false (false)oem-logo ()oem-logo? false (false)oem-banner ()oem-banner? false (false)security-mode none (none)security-password security-#badlogins ()hardware-revision ()last-hardware-update ()#power-cycles ()diag-switch? false (false){0} ok


Recommendations for NVRAM parameters

64


You can generally leave the NVRAM parameters at there defaults. Certainly, if you’re not sure what a parameter does, leave it alone. Below are some specific recommendations for normal operation.

Note – You will want to adjust these NVRAM parameters for troubleshooting purposes. For example, set auto-boot? false before doing show-post-results and probe-scsi-all.

diag-level

The marketplace for the V1280/Netra 1280 will not tolerate long boot times. Which is why the default is init. However, after install or FRU replacement or to troubleshoot generally, run a max level POST.

lom> bootmode forthlom> poweron

This should bring the system into the Open Boot PROM..

{1}ok setenv diag-level max{1}ok #. (or the appropriate escape sequence back to the lom> prompt.)

lom> poweroff lom> poweron

Don’t forget to put the diag level back to init

# eeprom | grep diag-leveldiag-level=max# eeprom diag-level=init;eeprom | grep diag-leveldiag-level=init#

reboot-on-error

It is recommended that this be set to true.

{0} ok setenv reboot-on-error truereboot-on-error = true{0}



auto-boot?

It is recommended that this be set to true.

{0} ok printenv auto-boot?auto-boot? false (true){0} ok set-default auto-boot?{0} ok printenv auto-boot?auto-boot? true (true){0} ok

error-reset-recovery

It is recommended that this be set to sync.

{0} ok setenv error-reset-recovery syncerror-reset-recovery = sync{0}

local-mac-address?

You will need to set this as true if the customer is using IPMP on his system, although if you are going to use ce0 and ce1 note that that already have their own MAC addresses.

{0} ok setenv local-mac-address? truelocal-mac-address? = true{0}

diag-switch?

A useful parameter to set for troubleshooting. It prints out the probe-list for the PCI devices.

bash-2.03# eeprom | grep diag-switchdiag-switch?=falsebash-2.03# eeprom diag-switch?=true;eeprom | grep diag-switchdiag-switch?=truebash-2.03#


Resetting a hung system


resetsc

The system controller should not hang, since there is a watchdog mechanism which prevents this. If you can’t get access via the ethernet port, access via the serial port. Reboot the SC, if required, in the following manner:

lom> resetscAre you sure you want to reboot the system controller now? [no] yes..

break

System really hung? Try sending a break to the system.

# <type escape sequence here, for example, #.>

lom> break

This will suspend Solaris.Do you want to continue? [no] yesType ’go’ to resumedebugger entered.{1} ok sync

panic[cpu1]/thread=2a1001b7d20: sync initiated

sched: software trap 0x7fpid=0, pc=0xf000c518, sp=0x2a1001b6ea1, tstate=0x4400001602, context=0x0g1-g7: f0493400, 1043c000, 1043c000, 15, 42c, 0, 2a1001b7d20

00000000f046eb10 unix:sync_handler+160 (f08240d0, 10000000, 8004, f048d4a0, 5e74fed, 77) %l0-3: 00000000f048d4a0 00000000000001e0 0000000000000220 0000000000000000 %l4-7: 00000000f048d4a0 0000000000000000 0000000000000000 0000000000000188..

syncing file systems... donedumping to /dev/dsk/c1t0d0s1, offset 40566784100% done: 51630 pages dumped, compression ratio 9.24, dump succeededrebooting...Resetting ...





reset -x

Break didn’t work? Issue an externally initiated reset (xir) to reset the processors in the system.

lom> reset -x

This will abruptly terminate Solaris.Do you want to continue? [no] yesNOTICE: XIR on CPU 3debugger entered.{3} ok

The XIR reset forces control of the system into the OpenBoot PROM and begins the error reset as defined by the error-reset-recovery configuration variable. In the above example, error-reset-recovery is set to none.

showresetstate

Note – If error-reset-recovery=sync as per best practice, you won’t get any register information. However, in the case above, we can issue the following

lom>showresetstate -v -f ftp://172.156.195.82//home/admin/V1280_xir_info_030626

lom> console{1} ok sync

panic[cpu1]/thread=2a100013d20: sync initiated

sched: software trap 0x7fpid=0, pc=0xf000c518, sp=0x2a1001b6ea1, tstate=0x4400001602, context=0x0g1-g7: f0493400, 1043c000, 1043c000, 15, 42c, 0, 2a1001b7d20.

reset -a

All else fails ? Do a reset all


Switching between different consoles

Switching between different consoles

This page contains procedures on how to navigate within the system controller.

The default escape sequence is #.



The default escape sequence will not work at the ok prompt..

The default escape sequence will not work at the ok prompt..

If you find that you can’t get back to the LOM shell from the ok prompt using the default escape sequence (since it has been changed to something else and forgotten) proceed as below:

{0} ok #.

ERROR: do_interpret: no such symbol "#."ERROR: undefined word

{0} ok

Note – Press the standby switch in the front panel for less than 4 seconds. This will bring you back to the lom> prompt. If the rocker switch has been disabled, you will need to completely remove the AC/DC source from the V1280/Netra 1280 or reboot the SC.

{0} ok Tue Dec 03 13:23:08 1280-sc lom: Shutdown requested by rocker switch

Powering boards off .../N0/PS0: powered off/N0/PS1: powered off/N0/PS2: powered offTue Dec 03 13:23:54 1280-sc lom: SysEvent 5 /N0/PS0, power state, Off (5,0)Tue Dec 03 13:23:54 1280-sc lom: SysEvent 5 /N0/PS1, power state, Off (5,0)Tue Dec 03 13:23:54 1280-sc lom: SysEvent 5 /N0/PS2, power state, Off (5,0)/N0/PS3: powered offTue Dec 03 13:23:54 1280-sc lom: CAUTION: Physically removing the last power supply will cause the system controller to lose power.Tue Dec 03 13:23:54 1280-sc lom: System is in standbyTue Dec 03 13:23:54 1280-sc lom: SysEvent 5 /N0/PS3, power state, Off (5,0)Tue Dec 03 13:23:54 1280-sc lom: /N0/FT0, fan speed, Off (4,0)

lom>lom> showescape?.lom> setescape "#."lom> showescape#.lom> console

{0}


The default escape sequence will not work from solaris..

70


The default escape sequence will not work from solaris..

If you find that you can’t get back to the LOM shell from the Solaris operating environment using the default escape sequence (since it has been changed to something else and forgotten) procede as below:

v1280a console login: #.

Password: Login incorrect

v1280a console login: rootPassword: Last login: Mon Dec 2 10:13:24 on console

bash-2.03# lom -c | grep escape

serial escape character=?

bash-2.03# lom -X#.

The LOMlite serial escape sequence is now "#."

bash-2.03#

Note – Note above that there is no space after the X in the lom -X command line above.

Serial escape sequences and dumb terminals

If you are using a dumb terminal (a VT100, for example) to access the serial port, you may find that #. does not work.

Try (British pound sign) .

£.

On my laptop keyboard, the British pound sign sits over numeral 3.


I/O layout

I/O layout


show-devs

72


show-devs

{0} show-devs/ (gptwo)/ssm@0,0 (gptwo)/ssm@0,0/pci@19,600000 (pci)/ssm@0,0/pci@19,600000/network@2 (network)/ssm@0,0/pci@19,600000/network@1 (network)/ssm@0,0/pci@19,700000 (pci)/ssm@0,0/pci@19,700000/pci@2 (pci)/ssm@0,0/pci@19,700000/pci@2/network@0 (network)/ssm@0,0/pci@18,600000 (pci)/ssm@0,0/pci@18,600000/scsi@2,1 (scsi-2)/ssm@0,0/pci@18,600000/scsi@2,1/tape (byte)/ssm@0,0/pci@18,600000/scsi@2,1/disk (block)/ssm@0,0/pci@18,600000/scsi@2 (scsi-2)/ssm@0,0/pci@18,600000/scsi@2/tape (byte)/ssm@0,0/pci@18,600000/scsi@2/disk (block)/ssm@0,0/pci@18,700000 (pci)/ssm@0,0/pci@18,700000/ide@3 (ide)/ssm@0,0/pci@18,700000/ide@3/cdrom (block)/ssm@0,0/pci@18,700000/ide@3/disk (block)/ssm@0,0/pci@18,700000/bootbus-controller@4/ssm@0,0/memory-controller@3,400000 (memory-controller)/ssm@0,0/SUNW,UltraSPARC-III+@3,0 (cpu)/ssm@0,0/memory-controller@2,400000 (memory-controller)/ssm@0,0/SUNW,UltraSPARC-III+@2,0 (cpu)/ssm@0,0/memory-controller@1,400000 (memory-controller)/ssm@0,0/SUNW,UltraSPARC-III+@1,0 (cpu)/ssm@0,0/memory-controller@0,400000 (memory-controller)/ssm@0,0/SUNW,UltraSPARC-III+@0,0 (cpu)/todsg (tod)/sgcn (serial)/failsafe (serial)/virtual-memory (virtual-memory)/memory@0,0 (memory)/packages/packages/SUNW,builtin-drivers/packages/obp-tftp/packages/terminal-emulator/packages/disk-label/packages/deblocker/chosen/options/aliases/openprom/openprom/client-services{0} ok


V1280/Netra 1280 System Configuration card


Caution – Take particular care of the SCC - the system won’t boot without it. And, don’t remove it from a running system - it will shut down in 60 seconds.

lom> shownet -v

Network-------The system controller is configured to be on a network.Network settings: staticHostname: 1280-scIP Address: 172.20.40.55Netmask: 255.255.0.0Gateway: 172.20.33.31DNS Domain: SFbay.Sun.COMPrimary DNS Server: 172.20.14.32Secondary DNS Server: 172.20.14.77

MAC Address HostID ------------------------------- --------Host net0 00:03:ba:c0:ff:dc 83c0ffdcHost net1 00:03:ba:c0:ff:dd 83c0ffddSC net 00:03:ba:c0:ff:ee 83c0ffee

lom>



74

If the SCC is stolen or develops a fault, do one of the following:

Obtain a new SCC, FRU part number 370-5155

Note – The above FRU comes with 10 MAC addresses/hostids pre-programmed. This will invalidate any hostid licensed applications your customer is running

To obtain a System Configuration Card with the original hostid/MAC addresses, as obtained from the shownet -v output, go to:

http://pts-americas.west/esg/msg/techinfo/platform/lw8/documentation/SCC-process.html

Backing up the System Configuration card

There is no “dumpconfig” command you can run. Make sure you have noted the following information.

From Solaris:

# eeprom# prtdiag -v

From the Open Boot PROM:

{0} ok printenv{0} ok devalias{0} ok show-disks{0} ok show-nets{0} ok show-devs

From the lom shell:

showboards -- show board informationshowcomponent -- show state of a componentshowdate -- show the current date and time for the systemshowescape -- show system controller (LOM) escape sequenceshoweventreporting -- show status of event reportingshowhostname -- show hostnameshowmodel -- show the platform modelshownetwork -- show SC (LOM) network settings and MAC addressesshowresetstate -- show CPU registers after resetshowsc -- show system controller (LOM) version and uptimesetupsc -- configure the system controller (LOM)


V1280/Netra 1280 Physical Device Mapping



The physical address represents the physical characteristics unique to the device (such as the bus address or the slot number where the device is installed).

Each physical device is referenced by its node identifier and Sun Fireplane agent identifier (AID)

AIDs range from 0 to 25 (0 to 19, hexadecimal).

There is a mixture of ways that the system numbers agents. The obp numbers in hex, POST numbers in decimal, solaris numbers processors in decimal, and device paths are in hex.

Refer to the tables on the next two pages for AIDs

Node Mapping

The node identifier for the Sun Fire V1280 and Netra 1280 is always 0.

For example, the device tree entry is:

/ssm@0,0

System Board Mapping

CPU and memory AIDs range from 0 to 19 (0 to 13, hexadecimal). Each system board can have up to four processors.

There are up to eight banks of memory per system board, two per CPU. Each pair of banks is controlled by one memory management unit (MMU). The MMU is co-packaged with its respective processor. Thus, the AID for an MMU is the same as its processor AID but with a different offset. The offset is 0 for processors and 400000 for memory.

Node ID 0



76

Device tree entries for a CPU and associated memory are:

/ssm@0,0/SUNW,UltraSPARC-III@b,0

/ssm@0,0/SUNW,memory-controller@b,400000

In the proceeding examples, the first device tree entry maps to Slot SB2, Processor Instance P3. The second entry maps to the memory management unit packaged with the processor shown in the first entry.

Processor/Memory Controller AIDs (hex in brackets)

I/O Mapping

When mapping an I/O device tree entry to a physical component in the system, there are up to six nodes in the device tree that must be considered:

● Node ID – 0 for Sun Fire V1280 & Netra 1280.

● Schizo AID – see refer to the I/O layout.

● Schizo PCI bus offset – Determines which PCI bus: A or B.

● Device number – Determines which slot in the IB_SSC.

● PCI controller – Determines which I/O device drive to use.

● Device instance – Specifies device referencing, which is used by the kernel.

CPU AIDCPU offset

Memory AIDMemory offset

Location P3 AID P2 AID P1 AID P0 AID

SB0 3 2 1 0 SB2 11 (b) 10 (a) 9 8 SB4 19 (13) 18 (12) 17 (11) 16 (10)



● For example:

/ssm@0,0/pci@19,700000/pci@3/SUNW,isptwo@4/sd@5,0

/ssm@0,0/pci@18,700000/pci@1/SUNW,hme@0,1

/ssm@0,0/pci@19,600000/pci@1/SUNW,qfe@2,1

/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0

Schizo AIDs (hex in brackets)

Schizo PCI Bus Offset

Bus A - offset 600000 - Provides 66/33 MHz PCI bus Bus B - offset 700000 - Provides 33 MHz PCI bus

I/O Slot layout

Bus offsetSchizo AID Device # PCI Controller

Device instanceNode ID

Location Even AID (Schizo 0)

Odd AID (Schizo 1)

IB6 24 (18) 25 (19)

Slot number Device tree

0 /ssm@0,0/pci@18,700000/*@1,*

1 /ssm@0,0/pci@18,700000/*@2,*

2 /ssm@0,0/pci@19,700000/*@1,*

3 /ssm@0,0/pci@19,700000/*@2,*

4 /ssm@0,0/pci@19,700000/*@3,*

5 /ssm@0,0/pci@18,600000/*@1,*


Internal Disk, DVD, and DDS Tape layout

78

Internal Disk, DVD, and DDS Tape layout

{0} ok probe-scsi-all

/ssm@0,0/pci@18,600000/scsi@2,1

/ssm@0,0/pci@18,600000/scsi@2

Target 0 Unit 0 Disk SEAGATE ST336605LSUN36G 0638Target 1 Unit 0 Disk SEAGATE ST336605LSUN36G 0638

{0} ok

Note – If the optional DDS4 Tape drive is present, it will show up as target 4. The DVD will not show up, since it is not connected to the SCSI backplane.

Which disk is which?

What’s the device path to the DVD?

{0} ok pwd/ssm@0,0/pci@18,700000/ide@3/cdrom{0} ok .propertiesdevice_type blockname cdromcompatible ide-cdrom{0} ok

Internal Drive Target

Logical Device Path Location

0 /ssm@0,0/pci@18,600000/scsi@2/sd@0,0 Bottom Disk Drive Slot

1 /ssm@0,0/pci@18,600000/scsi@2/sd@1,0 Top Disk Drive Slot


devalias & setenv


devalias & setenv

Caution – Cautiously adjust configuration variables. These NVCI variables determine the startup routine of the system so their configuration, if incorrect, can cause the system to operate in an unexpected manner.

The setenv Command

To change a parameter, use the setenv command:

{0} ok setenv local-mac-address? true

local-mac-address? = true

{0} ok

The devalias Command

Check out the device aliases:

{0} ok devalias disk

disk /ssm@0,0/pci@18,600000/scsi@2/disk@0,0

{0} ok devalias cdrom

cdrom /ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:f

{0} ok devalias net

net /ssm@0,0/pci@19,600000/network@1

{0} ok


Device Aliases

80

Device Aliases

{0} ok devaliasAlias Device Path--------------------------------------------------xdisk /ssm@0,0/pci@18,600000/scsi@2,1/disk@0,0xnet /ssm@0,0/pci@19,600000/network@2cdrom /ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:fdisk /ssm@0,0/pci@18,600000/scsi@2/disk@0,0disk0 /ssm@0,0/pci@18,600000/scsi@2/disk@0,0disk1 /ssm@0,0/pci@18,600000/scsi@2/disk@1,0disk2 /ssm@0,0/pci@18,600000/scsi@2/disk@2,0disk3 /ssm@0,0/pci@18,600000/scsi@2/disk@3,0disk4 /ssm@0,0/pci@18,600000/scsi@2/disk@4,0disk5 /ssm@0,0/pci@18,600000/scsi@2/disk@5,0tape /ssm@0,0/pci@18,600000/scsi@2/tape@5,0def-cn /sgcndiskglm /ssm@0,0/pci@18,600000/scsi@2/disk@0,0scsi1 /ssm@0,0/pci@18,600000/scsi@2,1scsi /ssm@0,0/pci@18,600000/scsi@2net1 /ssm@0,0/pci@19,600000/network@2net /ssm@0,0/pci@19,600000/network@1{0} ok

Add a Device Alias

You may want to add a devalias for the mirror of the root disk:

{0} ok show-disks

a) /ssm@0,0/pci@18,600000/scsi@2,1/diskb) /ssm@0,0/pci@18,600000/scsi@2/diskc) /ssm@0,0/pci@18,700000/ide@3/cdromd) /ssm@0,0/pci@18,700000/ide@3/diskq) NO SELECTIONEnter Selection, q to quit:

/ssm@0,0/pci@18,600000/scsi@2/disk has been selected.Type ^Y ( Control-Y ) to insert it in the command line.e.g. ok nvalias mydev ^Y for creating devalias mydev for/ssm@0,0/pci@18,600000/scsi@2/disk{0} ok nvalias boot-mirror /ssm@0,0/pci@18,600000/scsi@2/disk@1,0{0} ok devalias boot-mirrorboot-mirror /ssm@0,0/pci@18,600000/scsi@2/disk@1,0{0} ok


V1280/Netra 1280 Logical Device Mapping


{0} ok boot -vSize: 356496+157450+492250 BytesSunOS Release 5.8 Version Generic_108528-22 64-bitCopyright 1983-2003 Sun Microsystems, Inc. All rights reserved.Ethernet address = 0:3:ba:c0:ff:dcmem = 16777216K (0x400000000)avail mem = 16494100480root nexus = Sun Fire V1280ssm0 at root: SSM Node 0ssm0 is /ssm@0,0pci108e,80010 at ssm0: Node 0 Safari id 24 0xc700000pcisch0 is /ssm@0,0/pci@18,700000pci108e,80011 at ssm0: Node 0 Safari id 24 0xc600000pcisch1 is /ssm@0,0/pci@18,600000pci108e,80012 at ssm0: Node 0 Safari id 25 0xcf00000pcisch2 is /ssm@0,0/pci@19,700000pci108e,80013 at ssm0: Node 0 Safari id 25 0xce00000pcisch3 is /ssm@0,0/pci@19,600000/ssm@0,0/pci@18,600000/scsi@2 (glm0): glm0 supports power management./ssm@0,0/pci@18,600000/scsi@2 (glm0): Rev. 0 Symbios 53c1010-33/66 found.PCI-device: scsi@2, glm0glm0 is /ssm@0,0/pci@18,600000/scsi@2/ssm@0,0/pci@18,600000/scsi@2,1 (glm1): glm1 supports power management./ssm@0,0/pci@18,600000/scsi@2,1 (glm1): Rev. 0 Symbios 53c1010-33/66 found.PCI-device: scsi@2,1, glm1glm1 is /ssm@0,0/pci@18,600000/scsi@2,1PCI-device: ide@3, uata0uata0 is /ssm@0,0/pci@18,700000/ide@3sd30 at uata0: target 0 lun 0sd30 is /ssm@0,0/pci@18,700000/ide@3/sd@0,0sd0 at glm0: target 0 lun 0sd0 is /ssm@0,0/pci@18,600000/scsi@2/sd@0,0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>sd1 at glm0: target 1 lun 0sd1 is /ssm@0,0/pci@18,600000/scsi@2/sd@1,0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>root on /ssm@0,0/pci@18,600000/scsi@2/disk@0,0:a fstype ufsmemory-controller0 at ssm0: Node 0 Safari id 0 0x400000 ...mc-us30 is /ssm@0,0/memory-controller@0,400000



82

memory-controller1 at ssm0: Node 0 Safari id 1 0xc00000 ...mc-us31 is /ssm@0,0/memory-controller@1,400000memory-controller2 at ssm0: Node 0 Safari id 2 0x1400000 ...mc-us32 is /ssm@0,0/memory-controller@2,400000memory-controller3 at ssm0: Node 0 Safari id 3 0x1c00000 ...mc-us33 is /ssm@0,0/memory-controller@3,400000memory-controller4 at ssm0: Node 0 Safari id 8 0x4400000 ...mc-us34 is /ssm@0,0/memory-controller@8,400000memory-controller5 at ssm0: Node 0 Safari id 9 0x4c00000 ...mc-us35 is /ssm@0,0/memory-controller@9,400000memory-controller6 at ssm0: Node 0 Safari id 10 0x5400000 ...mc-us36 is /ssm@0,0/memory-controller@a,400000memory-controller7 at ssm0: Node 0 Safari id 11 0x5c00000 ...mc-us37 is /ssm@0,0/memory-controller@b,400000PCI-device: bootbus-controller@4, sgsbbc0sgsbbc0 is /ssm@0,0/pci@18,700000/bootbus-controller@4pseudo-device: sgenv0sgenv0 is /pseudo/sgenv@0pseudo-device: lw80lw80 is /pseudo/lw8@0Hardware watchdog enabledcpu0: SUNW,UltraSPARC-III+ (upaid 0 impl 0x15 ver 0x22 clock 900 MHz)cpu1: SUNW,UltraSPARC-III+ (upaid 1 impl 0x15 ver 0x22 clock 900 MHz)cpu2: SUNW,UltraSPARC-III+ (upaid 2 impl 0x15 ver 0x22 clock 900 MHz)cpu3: SUNW,UltraSPARC-III+ (upaid 3 impl 0x15 ver 0x22 clock 900 MHz)cpu8: SUNW,UltraSPARC-III+ (upaid 8 impl 0x15 ver 0x22 clock 900 MHz)cpu9: SUNW,UltraSPARC-III+ (upaid 9 impl 0x15 ver 0x22 clock 900 MHz)cpu10: SUNW,UltraSPARC-III+ (upaid 10 impl 0x15 ver 0x22 clock 900 MHz)cpu11: SUNW,UltraSPARC-III+ (upaid 11 impl 0x15 ver 0x22 clock 900 MHz)

Unretrieved lom log history follows ...

Note – This is the information kept on the IB_SSC, in the 128 KB buffer held on the system controller. Any outstanding messages get flushed to /var/adm/messages on the system on the next reboot.

6/27/03 5:34:25 AM SysEvent 5 /N0/PS0, power state, Off (5,0) 6/27/03 5:34:25 AM SysEvent 5 /N0/PS1, power state, Off (5,0) 6/27/03 5:34:25 AM SysEvent 5 /N0/PS2, power state, Off (5,0) 6/27/03 5:34:26 AM CAUTION: Physically removing the last power supply will cause the system controller to lose power. 6/27/03 5:34:26 AM System is in standby 6/27/03 5:34:26 AM SysEvent 5 /N0/PS3, power state, Off (5,0)



6/27/03 5:34:26 AM /N0/FT0, fan speed, Off (4,0) 6/27/03 5:36:00 AM SysEvent 5 /N0/PS0, power state, On (5,1) 6/27/03 5:36:07 AM Device voltage stabilized: /N0/PS0 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:36:07 AM /N0/PS0, sensor status, under limit (7,2,0x607000b000a0000)PCI-device: pci@2, pci_pci0pci_pci0 is /ssm@0,0/pci@19,700000/pci@2configuring IPv4 interfaces: ce1. 6/27/03 5:36:08 AM Device voltage stabilized: /N0/PS1 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DCHostname: v1280 6/27/03 5:36:09 AM SysEvent 5 /N0/PS1, power state, On (5,1) 6/27/03 5:36:09 AM /N0/PS1, sensor status, under limit (7,2,0x607010b000a0000) 6/27/03 5:36:09 AM Device voltage stabilized: /N0/PS2 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:36:10 AM SysEvent 5 /N0/PS2, power state, On (5,1) 6/27/03 5:36:10 AM /N0/PS2, sensor status, under limit (7,2,0x607020b000a0000) 6/27/03 5:36:11 AM Device voltage stabilized: /N0/PS3 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DCdump on /dev/dsk/c1t0d0s1 size 193 MB 6/27/03 5:36:11 AM SysEvent 5 /N0/PS3, power state, On (5,1) 6/27/03 5:36:11 AM /N0/PS3, sensor status, under limit (7,2,0x607030b000a0000) 6/27/03 5:36:26 AM /N0/FT0, fan speed, Low (4,1) 6/27/03 5:41:30 AM SysEvent 5 /N0/PS0, power state, Off (5,0) 6/27/03 5:41:30 AM SysEvent 5 /N0/PS1, power state, Off (5,0) 6/27/03 5:41:30 AM SysEvent 5 /N0/PS2, power state, Off (5,0) 6/27/03 5:41:30 AM CAUTION: Physically removing the last power supply will cause the system controller to lose power. 6/27/03 5:41:30 AM System is in standby 6/27/03 5:41:30 AM /N0/FT0, fan speed, Off (4,0) 6/27/03 5:41:30 AM SysEvent 5 /N0/PS3, power state, Off (5,0) 6/27/03 5:47:12 AM SysEvent 5 /N0/PS0, power state, On (5,1) 6/27/03 5:47:19 AM Device voltage stabilized: /N0/PS0 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:47:19 AM /N0/PS0, sensor status, under limit (7,2,0x607000b000a0000) 6/27/03 5:47:20 AM Device voltage stabilized: /N0/PS1 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:47:20 AM SysEvent 5 /N0/PS1, power state, On (5,1) 6/27/03 5:47:20 AM /N0/PS1, sensor status, under limit (7,2,0x607010b000a0000) 6/27/03 5:47:21 AM Device voltage stabilized: /N0/PS2 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC



84

6/27/03 5:47:21 AM SysEvent 5 /N0/PS2, power state, On (5,1) 6/27/03 5:47:21 AM /N0/PS2, sensor status, under limit (7,2,0x607020b000a0000) 6/27/03 5:47:22 AM Device voltage stabilized: /N0/PS3 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:47:22 AM SysEvent 5 /N0/PS3, power state, On (5,1) 6/27/03 5:47:22 AM /N0/PS3, sensor status, under limit (7,2,0x607030b000a0000)pseudo-device: devinfo0devinfo0 is /pseudo/devinfo@0 6/27/03 5:47:37 AM /N0/FT0, fan speed, Low (4,1) 6/27/03 5:53:29 AM SysEvent 5 /N0/PS0, power state, Off (5,0) 6/27/03 5:53:29 AM SysEvent 5 /N0/PS1, power state, Off (5,0)The system is coming up. Please wait. 6/27/03 5:53:29 AM SysEvent 5 /N0/PS2, power state, Off (5,0) 6/27/03 5:53:30 AM CAUTION: Physically removing the last power supply will cause the system controller to lose power.pseudo-device: sgfru0sgfru0 is /pseudo/sgfru@0 6/27/03 5:53:30 AM System is in standby 6/27/03 5:53:30 AM SysEvent 5 /N0/PS3, power state, Off (5,0)NIS domainname is uk.sun.comStarting IPv4 router discovery.starting rpc services: rpcbind keyserv 6/27/03 5:53:30 AM /N0/FT0, fan speed, Off (4,0) nis_cachemgr done. 6/27/03 5:57:47 AM SysEvent 5 /N0/PS0, power state, On (5,1) 6/27/03 5:57:54 AM Device voltage stabilized: /N0/PS0 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:57:54 AM /N0/PS0, sensor status, under limit (7,2,0x607000b000a0000) 6/27/03 5:57:55 AM Device voltage stabilized: /N0/PS1 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:57:55 AM SysEvent 5 /N0/PS1, power state, On (5,1) 6/27/03 5:57:55 AM /N0/PS1, sensor status, under limit (7,2,0x607010b000a0000) 6/27/03 5:57:56 AM Device voltage stabilized: /N0/PS2 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:57:56 AM SysEvent 5 /N0/PS2, power state, On (5,1) 6/27/03 5:57:56 AM /N0/PS2, sensor status, under limit (7,2,0x607020b000a0000)Setting netmask of ce1 to 255.255.0.0Setting default IPv4 interface for multicast: add net 224.0/4: gateway v1280 6/27/03 5:57:57 AM Device voltage stabilized: /N0/PS3 normal operating state: 48 VDC 0 Volt. 0 Value: 48.0 Volts DC 6/27/03 5:57:57 AM SysEvent 5 /N0/PS3, power state, On (5,1)



syslog service starting.Jun 27 06:05:01 nis_cachemgr: authdes_refresh: keyserv(1m) is unable to encrypt session key 6/27/03 5:57:57 AM /N0/PS3, sensor status, under limit (7,2,0x607030b000a0000) 6/27/03 5:58:12 AM /N0/FT0, fan speed, Low (4,1)Print services started.volume management starting.The system is ready.

v1280a console login: rootPassword: Last login: Fri Jun 27 05:22:08 on consolebash-2.03# uname -a

SunOS v1280 5.8 Generic_108528-22 sun4u sparc SUNW,Netra-T12

bash-2.03#

Note – Be aware of the different names for these systems: SUNW,Netra-T12 LW8 Lightweight 8 Sun Fire V1280/Netra 1280


/dev/dsk & logical network mapping

86

/dev/dsk & logical network mapping

bash-2.03# cd /dev/dskbash-2.03# ls

c0t0d0s0 c0t0d0s3 c0t0d0s6 c1t0d0s1 c1t0d0s4 c1t0d0s7 c1t1d0s2 c1t1d0s5 c0t0d0s1 c0t0d0s4 c0t0d0s7 c1t0d0s2 c1t0d0s5 c1t1d0s0 c1t1d0s3 c1t1d0s6 c0t0d0s2 c0t0d0s5 c1t0d0s0 c1t0d0s3 c1t0d0s6 c1t1d0s1 c1t1d0s4 c1t1d0s7

bash-2.03# ls -la c0t0d0s0

lrwxrwxrwx 1 root root 50 Oct 15 10:03 c0t0d0s0 -> ../../devices/ssm@0,0/pci@18,700000/ide@3/sd@0,0:a


lrwxrwxrwx 1 root root 51 Oct 15 10:03 c1t0d0s0 -> ../../devices/ssm@0,0/pci@18,600000/scsi@2/sd@0,0:a


lrwxrwxrwx 1 root root 51 Oct 15 10:03 c1t1d0s0 -> ../../devices/ssm@0,0/pci@18,600000/scsi@2/sd@1,0:a

bash-2.03# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.200.100.47 netmask ffffff00 broadcast 192.200.100.255 ether 0:3:ba:19:91:15

bash-2.03#

Note – Due to the probe order of the pci-busses, /dev/[r]dsk/c0t0d0s0 is the DVD and /dev/[r]dsk/c1t0d0s0 is the boot disk. Note also the new 10/100/1000 Base-T ethernet, ce0


Installing Lights out Management (LOM) 2.0 software


The LOM software is on the supplemental CD which comes with comes with Solaris.

Install this software, and add patch 110208-xx which is available from http://sunsolve.central

bash-2.03# cd /supp_cd/Lights_Out_Management_2.0/Productbash-2.03# pkgadd -d .

The following packages are available: 1 SUNWlomm LOMlite manual pages (sparc) 2.0,REV=2000.08.22.14.14 2 SUNWlomr LOMlite driver (root) (sparc) 2.0,REV=2000.08.22.14.14 3 SUNWlomu LOMlite Utilities (usr) (sparc) 2.0,REV=2000.08.22.14.14

Select package(s) you wish to process (or ’all’ to processall packages). (default: all) [?,??,q]:

Processing package instance <SUNWlomm> from </var/tmp/Lights_Out_Management_2.0/Product>

LOMlite manual pages(sparc) 2.0,REV=2000.08.22.14.14Copyright 2000 Sun Microsystems, Inc. All rights reserved.Using </> as the package base directory.## Processing package information.## Processing system information. 3 package pathnames are already properly installed.## Verifying disk space requirements.## Checking for conflicts with packages already installed.

The following files are already installed on the system and are beingused by another package: /usr/share/man/man1m <attribute change only>

Do you want to install these conflicting files [y,n,?,q] y## Checking for setuid/setgid programs.

Installing LOMlite manual pages as <SUNWlomm>

## Installing part 1 of 1.71 blocks



88

Installation of <SUNWlomm> was successful.

Processing package instance <SUNWlomr> from </var/tmp/Lights_Out_Management_2.0/Product>

LOMlite driver (root)(sparc) 2.0,REV=2000.08.22.14.14Copyright 2000 Sun Microsystems, Inc. All rights reserved.## Executing checkinstall script.Using </> as the package base directory.## Processing package information.## Processing system information. 9 package pathnames are already properly installed.## Verifying package dependencies.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-userpermission during the process of installing this package.

Do you want to continue with the installation of <SUNWlomr> [y,n,?] y

Installing LOMlite driver (root) as <SUNWlomr>

## Installing part 1 of 1.20 blocksi.drivers (INFO): Startingi.drivers (INFO): Installing /var/tmp/Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platform/sun4u/kernel/drv/lomi.drivers (INFO): Installing /var/tmp/Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platform/sun4u/kernel/drv/lompi.drivers (INFO): Installing /var/tmp/Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platform/sun4u/kernel/drv/sparcv9/lomi.drivers (INFO): Installing /var/tmp/Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platform/sun4u/kernel/drv/sparcv9/lompi.drivers (INFO): Installing /var/tmp/Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platform/sun4u/kernel/drv/sparcv9/lomv

i.drivers (INFO): Identified drivers ’lom lomp lomv’i.drivers (INFO): Cleaning up old driver ’lom’...i.drivers (INFO): Cleaning up old driver ’lomp’...




i.drivers (INFO): Cleaning up old driver ’lomv’...i.drivers (INFO): Cleaning up old driver ’lomh’...

i.drivers (INFO): Adding driver ’lomp’... driver = ’lomp’ aliases = ’’ link = ’lomp’ spec = ’lomp’

Adding devlink entry ’type=ddi_pseudo;name=lomp lomp’adding driver with aliases ’’ perm ’* 0644 root sys’devfsadm: driver failed to attach: lompWarning: Driver (lomp) successfully added to system but failed to attach

i.drivers (INFO): Adding driver ’lomv’... driver = ’lomv’ aliases = ’SUNW,lomv’ link = ’SUNW,lomv lomv’ spec = ’\M0’

Adding devlink entry ’type=ddi_pseudo;name=SUNW,lomv \M0’Adding devlink entry ’type=ddi_pseudo;name=lomv \M0’adding driver with aliases ’SUNW,lomv’ perm ’* 0644 root sys’devfsadm: driver failed to attach: lomvWarning: Driver (lomv) successfully added to system but failed to attach

i.drivers (INFO): Adding driver ’lom’... driver = ’lom’ aliases = ’SUNW,lomh SUNW,lom’ link = ’SUNW,lomh SUNW,lom’ spec = ’lom’

Adding devlink entry ’type=ddi_pseudo;name=SUNW,lomh lom’Adding devlink entry ’type=ddi_pseudo;name=SUNW,lom lom’adding driver with aliases ’SUNW,lomh SUNW,lom’ perm ’* 0644 root sys’devfsadm: driver failed to attach: lomWarning: Driver (lom) successfully added to system but failed to attachi.drivers (SUCCESS): Finished

[ verifying class <drivers> ]

Installation of <SUNWlomr> was successful.

Processing package instance <SUNWlomu> from </var/tmp/Lights_Out_Management_2.0/Product>

LOMlite Utilities (usr)



(sparc) 2.0,REV=2000.08.22.14.14Copyright 2000 Sun Microsystems, Inc. All rights reserved.Using </> as the package base directory.## Processing package information.## Processing system information. 4 package pathnames are already properly installed.## Verifying package dependencies.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.

Installing LOMlite Utilities (usr) as <SUNWlomu>

## Installing part 1 of 1.1432 blocks

Installation of <SUNWlomu> was successful.

The following packages are available: 1 SUNWlomm LOMlite manual pages (sparc) 2.0,REV=2000.08.22.14.14 2 SUNWlomr LOMlite driver (root) (sparc) 2.0,REV=2000.08.22.14.14 3 SUNWlomu LOMlite Utilities (usr) (sparc) 2.0,REV=2000.08.22.14.14

Select package(s) you wish to process (or ’all’ to processall packages). (default: all) [?,??,q]: q

bash-2.03# pkginfo | grep lom

system SUNWlomm LOMlite manual pagessystem SUNWlomr LOMlite driver (root)system SUNWlomu LOMlite Utilities (usr)

bash-2.03# cd /var/tmpbash-2.03# patchadd 110208-19

Checking installed patches...Verifying sufficient filesystem capacity (dry run method)...Installing patch packages...

Patch number 110208-19 has been successfully installed.See /var/sadm/patch/110208-19/log for detailsExecuting postpatch script...postpatch (INFO): Starting




postpatch (INFO): Identified drivers ’lom lomp lomv’postpatch (INFO): Cleaning up old driver ’lom’...driver is present, removing itCleaning up old devlink entry ’type=ddi_pseudo;name=SUNW,lom lom’postpatch (INFO): Cleaning up old driver ’lomp’...driver is present, removing itCleaning up old devlink entry ’type=ddi_pseudo;name=lomp lomp’postpatch (INFO): Cleaning up old driver ’lomv’...driver is present, removing itCleaning up old devlink entry ’type=ddi_pseudo;name=SUNW,lomv \M0type=ddi_pseudo;name=lomv \M0’postpatch (INFO): Cleaning up old driver ’lomh’...Cleaning up old devlink entry ’type=ddi_pseudo;name=SUNW,lomh lom’

postpatch (INFO): Adding driver ’lomp’... driver = ’lomp’ aliases = ’’ link = ’lomp’ spec = ’lomp’

Adding devlink entry ’type=ddi_pseudo;name=lomp lomp’adding driver with aliases ’’ perm ’* 0644 root sys’devfsadm: driver failed to attach: lompWarning: Driver (lomp) successfully added to system but failed to attach

postpatch (INFO): Adding driver ’lomv’... driver = ’lomv’ aliases = ’SUNW,lomv’ link = ’SUNW,lomv lomv’ spec = ’\M0’

Adding devlink entry ’type=ddi_pseudo;name=SUNW,lomv \M0’Adding devlink entry ’type=ddi_pseudo;name=lomv \M0’adding driver with aliases ’SUNW,lomv’ perm ’* 0644 root sys’devfsadm: driver failed to attach: lomvWarning: Driver (lomv) successfully added to system but failed to attach

postpatch (INFO): Adding driver ’lom’... driver = ’lom’ aliases = ’SUNW,lomh SUNW,lom’ link = ’SUNW,lomh SUNW,lom’ spec = ’lom’

Adding devlink entry ’type=ddi_pseudo;name=SUNW,lomh lom’Adding devlink entry ’type=ddi_pseudo;name=SUNW,lom lom’adding driver with aliases ’SUNW,lomh SUNW,lom’ perm ’* 0644 root sys’devfsadm: driver failed to attach: lom



Warning: Driver (lom) successfully added to system but failed to attachpostpatch (SUCCESS): Finished

Patch packages installed: SUNWlomm SUNWlomr SUNWlomubash-2.03#

bash-2.03# showrev -p | grep 110208-19

Patch: 110208-19 Obsoletes: Requires: Incompatibles: Packages: SUNWlomm, SUNWlomr, SUNWlomu

bash-2.03# lom

No options specified

Usage: lom [-pfvclbwtaUCLB] [-A on|off,alarm-no] [-F on|off][-W on|off,<watchdog-timeout>,<watchdog-pat-interval>] [-R on|off][-E on|off|default,<level>] [-X char(s)] [-G <filename>|default] [-e n,<level>]

bash-2.03#

Note – Run the following commands on the V1280/Netra 1280 only after referring to the Sun Fire Entry level Midrange System Administration Guide lom -c lom -l lom -e lom -f lom -v lom -t Other lom commands lom -A, lom -E, lom -X, lom -G



Installing and running Explorer


Explorer software can be downloaded from Sunsolve. It is also available on the EIS-CD.

# zcat SunExplorer.tar.Z | tar xf -# pkgadd -d .

The following packages are available: 1 SUNWexplo Sun(TM) Explorer Data Collector (all) 5.0,REV=2005.02.23.09.02 2 SUNWexplu Sun(TM) Explorer Data Collector Config Files (all) 5.0,REV=2005.02.23.09.02

Select package(s) you wish to process (or ’all’ to processall packages). (default: all) [?,??,q]: ...

Update the explorer defaults file with explorer -g

# /opt/SUNWexplo/bin/explorer -g

# /opt/SUNWexplo/bin/explorer

Mar 24 15:07:17 V1280[948] explorer: explorer ID: explorer.83195975.V1280-2005.03.24.14.07Mar 24 15:07:18 V1280[948] patch: RUNNINGMar 24 15:07:19 V1280[948] pkg: RUNNINGMar 24 15:07:20 V1280[948] sysconfig: RUNNINGMar 24 15:07:54 V1280[948] sysconfig: exited: AP not installedMar 24 15:07:55 V1280[948] cluster: RUNNINGMar 24 15:07:55 V1280[948] cluster: exited: Cluster software not installedMar 24 15:07:55 V1280[948] cst: RUNNINGMar 24 15:07:55 V1280[948] cst: exited: CST not installedMar 24 15:07:55 V1280[948] disks: RUNNINGMar 24 15:08:05 V1280[948] emc: RUNNINGMar 24 15:08:05 V1280[948] emc: exited: EMCpower not installedMar 24 15:08:05 V1280[948] etc: RUNNINGMar 24 15:08:05 V1280[948] fcal: RUNNINGMar 24 15:08:06 V1280[948] firelink: RUNNINGMar 24 15:08:06 V1280[948] firelink: exited: Sun Firelink Interconnect not installedMar 24 15:08:06 V1280[948] fma: RUNNING



94

Mar 24 15:08:06 V1280[948] fma: exited: OS is not Sun OS 5.10Mar 24 15:08:06 V1280[948] fru: RUNNINGMar 24 15:19:15 V1280[948] hds: RUNNINGMar 24 15:19:15 V1280[948] hds: exited: No Hitachi software foundMar 24 15:19:15 V1280[948] init: RUNNINGMar 24 15:19:16 V1280[948] j2se: RUNNINGMar 24 15:19:20 V1280[948] ldap: RUNNINGMar 24 15:19:20 V1280[948] lic: RUNNINGMar 24 15:19:20 V1280[948] lp: RUNNINGMar 24 15:19:21 V1280[948] lvm: RUNNINGMar 24 15:19:21 V1280[948] messages: RUNNINGMar 24 15:19:21 V1280[948] nbu: RUNNINGMar 24 15:19:22 V1280[948] nbu: exited: NetBackup not installedMar 24 15:19:22 V1280[948] ndd: RUNNINGMar 24 15:19:33 V1280[948] netinfo: RUNNINGMar 24 15:19:35 V1280[948] photon: RUNNINGMar 24 15:19:35 V1280[948] photon: exited: No photons installedMar 24 15:19:35 V1280[948] samfs: RUNNINGMar 24 15:19:35 V1280[948] samfs: exited: SAM-FS or QFS not installedMar 24 15:19:36 V1280[948] sanextended: RUNNINGMar 24 15:19:36 V1280[948] sap: RUNNINGMar 24 15:19:36 V1280[948] sap: exited: SAP not installedMar 24 15:19:36 V1280[948] sbu: RUNNINGMar 24 15:19:36 V1280[948] sbu: exited: Solstice Backup not installedMar 24 15:19:36 V1280[948] se3k: RUNNINGMar 24 15:19:36 V1280[948] se3k: exited: SUNWsccli not installedMar 24 15:19:36 V1280[948] se6130: RUNNINGMar 24 15:19:36 V1280[948] se6130: SUNWstade package not installedMar 24 15:19:36 V1280[948] se6320: RUNNINGMar 24 15:19:36 V1280[948] se6320: exited: wget not foundMar 24 15:19:36 V1280[948] se6920: RUNNINGMar 24 15:19:37 V1280[948] sf15k_ndd: RUNNINGMar 24 15:19:37 V1280[948] sf15k_sc: RUNNINGMar 24 15:19:37 V1280[948] sf15k_sc: exited: SMS not installedMar 24 15:19:37 V1280[948] sonoma: RUNNINGMar 24 15:19:37 V1280[948] sonoma: exited: No A3X00 installedMar 24 15:19:37 V1280[948] ssa: RUNNINGMar 24 15:19:37 V1280[948] ssa: exited: No SSAs installedMar 24 15:19:37 V1280[948] ssp: RUNNINGMar 24 15:19:37 V1280[948] ssp: exited: Not an SSP systemMar 24 15:19:37 V1280[948] storade: RUNNINGMar 24 15:19:37 V1280[948] storade: exited: StorAde Data Service’s not installedMar 24 15:19:37 V1280[948] storedge: RUNNINGMar 24 15:19:37 V1280[948] storedge: exited: StorEdge Data Service’s not installedMar 24 15:19:37 V1280[948] stortools: RUNNING



Mar 24 15:19:37 V1280[948] stortools: exited: StorTools not installedMar 24 15:19:38 V1280[948] sunray: RUNNINGMar 24 15:19:38 V1280[948] sunray: exited: SUNWuto not installedMar 24 15:19:38 V1280[948] t3: RUNNINGMar 24 15:19:38 V1280[948] t3: exited: T3 and T4 not installedMar 24 15:19:38 V1280[948] t3extended: RUNNINGMar 24 15:19:38 V1280[948] u4ft: RUNNINGMar 24 15:19:38 V1280[948] u4ft: exited: Not an FT1800 systemMar 24 15:19:38 V1280[948] var: RUNNINGMar 24 15:19:39 V1280[948] vtsst: RUNNINGMar 24 15:19:39 V1280[948] vtsst: exited: StorTools Diagnostics not installedMar 24 15:19:39 V1280[948] vxfs: RUNNINGMar 24 15:19:39 V1280[948] vxfs: exited: VxFS not installedMar 24 15:19:39 V1280[948] vxvm: RUNNINGMar 24 15:19:39 V1280[948] vxvm: exited: VxVM not installedMar 24 15:19:39 V1280[948] explorer: data collection completeMar 24 15:19:42 V1280[948] explorer: removing previous explorers from /opt/SUNWexplo/outputMar 24 15:19:42 V1280[948] explorer: Explorer finished#

Interrogating the V1280 remotely

Explorer 5.0 has a new option, whereby if you have an admin workstation which can access the IB_SSC ethernet port, you can gather information remotely. If the V1280 system is down, this is an extremely useful way of gathering troubleshooting information.

lom>shownetwork

Network-------The system controller is configured to be on a network.Network settings: staticHostname: v1280a-scIP Address: 10.16.12.31Netmask: 255.255.255.0Gateway: 10.16.43.254DNS Domain: sweden.sun.com sun.comPrimary DNS Server: 129.159.210.20Secondary DNS Server: 129.156.85.45Connection type: telnetlom>



96

# /opt/SUNWexplo/bin/explorer -w 1280extended Mar 24 13:28:29 esg-admin[11672] explorer: explorer ID: explorer.80a2e045.esg-admin-2005.03.24.13.28Mar 24 13:28:29 esg-admin[11672] patch: RUNNINGMar 24 13:28:36 esg-admin[11672] pkg: RUNNINGMar 24 13:28:47 esg-admin[11672] sysconfig: RUNNINGMar 24 13:29:13 esg-admin[11672] sysconfig: exited: AP not installedMar 24 13:29:14 esg-admin[11672] 1280extended: RUNNING

You will be prompted for a System Controller name If hostname cannot be resolved, please use IP address.

Type return to end the list.

Please enter the name of the SC: 10.16.12.31Please enter the SC platform password for 10.16.12.31:

Please enter the name of the SC: <--- Hit Return here

Mar 24 13:41:43 esg-admin[11672] explorer: data collection completeMar 24 13:41:46 esg-admin[11672] explorer: removing previous explorers from /opt/SUNWexplo/outputMar 24 13:41:47 esg-admin[11672] explorer: Explorer finished#

Note – The explorer is running on an admin workstation which is on the same network as the V1280 SC. (Note that the switch is 1280extended even if interrogating an E2900 IB_SSC) The connection type must be telnet (not ssh on an SCV2). This is being addressed in BugId 6235170 Need SSH protocol support for 1280extended

# cd explorer.80a2e045.esg-admin-2005.03.24.13.28/sc/10.16.12.31# ls

history.outinventory.outshowalarm.outshowboards_-e.outshowboards_-p_proms.outshowboards_-v.outshowboards_-v_-p_board.out



showboards_-v_-p_clock.outshowboards_-v_-p_cpu.outshowboards_-v_-p_io.outshowboards_-v_-p_memory.outshowboards_-v_-p_power.outshowboards_-v_-p_version.outshowcomponent_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_@[email protected]_-v_SSC1.outshowdate_-v.outshowenvironment_-v.outshowescape.outshoweventreporting.outshowfault.outshowhostname.outshowlocator.outshowlogs_-v.outshowmodel.outshownetwork_-v.outshowresetstate_-v.outshowsc_-v.out

#


Running the inventory command


Running the inventory command is another method of gathering FRU data. If this info is all you want, it’s quicker than running explorer

lom> inventory

SSC1: SSC: 501-6459-01-50 serial# 000009 "System Controller (1280)" Made on Tue Aug 20 05:28:46 PDT 2002 by 012c at Celestica,Toronto,Ontario Powered on for 376 days 13 hours 48 minutes /N0/SCC: no seprom data/N0/BP: BP: 540-4968-04-00 serial# 1103 "Baseplane 1280" Made on Wed Dec 31 16:00:00 PST 1969 by 0000 at Powered on for 376 days 16 hours 43 minutes /N0/SIB: Ind: 540-5187-04-00 serial# 1030 "System Indicator (1280)" Made on Wed Dec 31 16:00:00 PST 1969 by 0000 at Powered on for 376 days 13 hours 58 minutes /N0/SPDB: PDB: 370-4394-03-07 serial# F00231 "Power Distribution Board (1280)" Made on Tue Jul 02 10:06:23 PDT 2002 by 03ad at DELTA ELECTRONICS DONGGUAN CHINA Powered on for 376 days 14 hours 28 minutes /N0/PS0: PS: 300-1523-02-05 serial# E01127 "Power Supply (A166, V1280)" Made on Tue Jul 02 19:24:44 PDT 2002 by 03ad at DELTA ELECTRONICS DONGGUAN CHINA Powered on for 292 days 22 hours 11 minutes /N0/PS1: PS: 300-1523-02-05 serial# E01104 "Power Supply (A166, V1280)" Made on Mon Jul 01 15:02:00 PDT 2002 by 03ad at DELTA ELECTRONICS DONGGUAN CHINA Powered on for 293 days 21 hours 55 minutes /N0/PS2: PS: 300-1523-02-05 serial# E01074 "Power Supply (A166, V1280)" Made on Mon Jul 01 10:18:47 PDT 2002 by 03ad at DELTA ELECTRONICS DONGGUAN CHINA Powered on for 294 days 4 hours 49 minutes /N0/PS3: PS: 300-1523-02-05 serial# E01068 "Power Supply (A166, V1280)" Made on Mon Jul 01 08:58:51 PDT 2002 by 03ad at DELTA ELECTRONICS DONGGUAN CHINA Powered on for 293 days 23 hours 14 minutes /N0/FT0: FT: 540-4972-04-00 serial# 1024 "Fan Tray (1280)" Made on Wed Dec 31 16:00:00 PST 1969 by 0000 at Powered on for 295 days 3 hours 18 minutes /N0/MB: MB: 540-4966-04-00 serial# 0436 "Media bay for drives (1280)" Made on Wed Dec 31 16:00:00 PST 1969 by 0000 at Powered on for 376 days 16 hours 36 minutes /N0/SB0: CPU: 540-5467-01-50 serial# 000062 "CPU Board (1280)" Made on Thu Sep 05 05:18:12 PDT 2002 by 012c at Celestica,Toronto,Ontario Powered on for 295 days 14 hours 31 minutes /N0/SB0/P0/B0/D0: DIMM: 501-5401-03-50 serial# 811541 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 02:39:53 PDT 2002 by 00ce at ONYANG,KOREA Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes

/N0/SB0/P0/B0/D1: DIMM: 501-5401-03-50 serial# 811403 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 03:26:01 PDT 2002 by 00ce at ONYANG,KOREA




Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P0/B0/D2: DIMM: 501-5401-03-50 serial# 811466 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 03:27:14 PDT 2002 by 00ce at ONYANG,KOREA Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes .../N0/SB0/P1/B0/D3: DIMM: 501-5401-03-50 serial# 811533 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 02:33:56 PDT 2002 by 00ce at ONYANG,KOREA Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P1/B1/D0: DIMM: 501-5401-03-50 serial# 811401 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 03:02:59 PDT 2002 by 00ce at ONYANG,KOREA Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P1/B1/D1: DIMM: 501-5401-03-50 serial# 811408 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 03:02:59 PDT 2002 by 00ce at ONYANG,KOREA Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P1/B1/D2: DIMM: 501-5401-03-50 serial# 811404 "256 MB NG SDRAM DIMM" Made on Sun Aug 25 03:02:59 PDT 2002 by 00ce at ONYANG,KOREA Signature = 00000000259f7e82 Powered on for 291 days 21 hours 4 minutes .../N0/SB0/P0/E0: ECACHE: 370-4128-03-50 serial# 4A4VHZ "4MB Ecache Module" Made on Thu Aug 22 01:09:53 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P0/E1: ECACHE: 370-4128-03-50 serial# 4A4VH7 "4MB Ecache Module" Made on Thu Aug 22 01:09:50 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P1/E0: ECACHE: 370-4128-03-50 serial# 4A4VHX "4MB Ecache Module" Made on Thu Aug 22 01:09:58 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P1/E1: ECACHE: 370-4128-03-50 serial# 4A4VHW "4MB Ecache Module" Made on Thu Aug 22 01:10:00 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P2/E0: ECACHE: 370-4128-03-50 serial# 4A4W7G "4MB Ecache Module" Made on Thu Aug 22 00:51:53 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P2/E1: ECACHE: 370-4128-03-50 serial# 4A4W82 "4MB Ecache Module"



10

Made on Thu Aug 22 00:51:39 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P3/E0: ECACHE: 370-4128-03-50 serial# 4A4W42 "4MB Ecache Module" Made on Thu Aug 22 01:02:33 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/SB0/P3/E1: ECACHE: 370-4128-03-50 serial# 4A4W0X "4MB Ecache Module" Made on Thu Aug 22 00:59:39 PDT 2002 by 00f1 at Celestica Toronto, Canada Signature = 000000004a7a7895 Powered on for 291 days 21 hours 4 minutes /N0/IB6: PCI: 540-4967-06-00 serial# A00441 "IB_SSC Assembly (1280)" Made on Wed Dec 31 16:00:00 PST 1969 by 0000 at Powered on for 295 days 2 hours 12 minutes /N0/RP0: RP: 540-4974-05-50 serial# 000170 "Repeater Board (1280)" Made on Sat Aug 31 18:25:43 PDT 2002 by 012c at Celestica,Toronto,Ontario Powered on for 295 days 4 hours 36 minutes /N0/RP2: RP: 540-4974-05-50 serial# 000021 "Repeater Board (1280)" Made on Sun Sep 01 12:29:04 PDT 2002 by 012c at Celestica,Toronto,Ontario Powered on for 294 days 22 hours 15 minutes lom>



Advice on Dynamic Reconfiguration


Read and understand the issues surrounding DR in the V1280/Netra 1280 System Administration Guide. The only additional advice I would make to the Admin guide, is to run a max diag level POST on a System Board prior to dynamically adding it into the system.

# cfgadm

Ap_Id Type Receptacle Occupant ConditionN0.IB6 PCI_I/O_Boa connected configured okN0.SB0 CPU connected configured okN0.SB2 CPU connected configured okN0.SB4 unknown empty unconfigured unknownc0 scsi-bus connected configured unknownc1 scsi-bus connected configured unknownc2 scsi-bus connected unconfigured unknownc3 scsi-bus connected unconfigured unknownc4 scsi-bus connected unconfigured unknownc5 scsi-bus connected unconfigured unknown

# cfgadm -av | grep -i permanent

N0.SB0::memory connected configured ok base address 0x0, 8388608 KBytes total, 868128 KBytes permanent

# cfgadm -c disconnect N0.SB4# cfgadm -o platform=diag=max -c configure N0.SB4

cfgadm: Hardware specific failure: test N0.SB4: option invalid: diag=max

Note – Refer to BugId 4890061.

# cfgadm -o platform=diag=default -c configure N0.SB4

{/N0/SB2/P2} Running CPU POR and Set Clocks{/N0/SB2/P3} Running CPU POR and Set Clocks{/N0/SB2/P0} Running CPU POR and Set Clocks{/N0/SB2/P1} Running CPU POR and Set Clocks{/N0/SB2/P2} @(#) lpost 5.17.0 2004/03/05 11:28



{/N0/SB2/P0} @(#) lpost 5.17.0 2004/03/05 11:28{/N0/SB2/P3} @(#) lpost 5.17.0 2004/03/05 11:28..Apr 13 20:23:14 1280 picld[54]: sgfru ioctl 0xf handle 0x70 failed: Connection timed out

Note – Refer to BugId 4854333 and Internal SRDB 74637

{/N0/SB2/P0} Subtest: Board Memory Interleave Configuration {/N0/SB2/P2} Subtest: Board Memory Interleave Configuration {/N0/SB2/P3} Subtest: Board Memory Interleave Configuration {/N0/SB2/P1} Subtest: Board Memory Interleave Configuration {/N0/SB2/P0} Passed{/N0/SB2/P1} Passed{/N0/SB2/P2} Passed{/N0/SB2/P3} Passed{/N0/SB2/P0} DCB_ENTER_OBP command succeeded {/N0/SB2/P1} DCB_ENTER_OBP command succeeded {/N0/SB2/P2} DCB_ENTER_OBP command succeeded {/N0/SB2/P3} DCB_ENTER_OBP command succeeded

#

In this example, the cfgadm command took 14 minutes for a 4 proc uniboard with 8 GB main memory.



Appendix

Appendix

prtdiag -v output

In the example below, /usr/platform/sun4u/sbin has been added to the PATH in /.profile

Note – In the following examples, SB0 has been dr’d out of the system.

bash-2.03# prtdiag -v

System Configuration: Sun Microsystems sun4u Sun Fire V1280System clock frequency: 150 MHZMemory size: 8GB

==================================== CPUs ==================================== E$ CPU CPU TemperatureCPU Freq Size Implementation Mask Die Amb. Location--- -------- ---------- ------------------- ----- ---- ---- -------- 8 900 MHz 8MB SUNW,UltraSPARC-III+ 2.2 46C 24C SB2/P0 9 900 MHz 8MB SUNW,UltraSPARC-III+ 2.2 46C 25C SB2/P1 10 900 MHz 8MB SUNW,UltraSPARC-III+ 2.2 48C 24C SB2/P2 11 900 MHz 8MB SUNW,UltraSPARC-III+ 2.2 47C 26C SB2/P3

================================= IO Devices ================================= Bus FreqBrd Type MHz Slot Name Model--- ---- ---- ---------- ---------------------------- -------------------- 0 pci 33 PCI0 pci108e,1000 0 pci 33 PCI0 SUNW,hme (network) SUNW,cheerio 0 pci 33 PCI0 SUNW,isptwo (scsi) QLGC,ISP1040B 0 pci 33 PCI5 scsi-pci1000,f (scsi-2) 0 pci 33 PCI5 scsi-pci1000,f (scsi-2) 0 pci 66 1 pci108e,abba (network) SUNW,pci-ce 0 pci 33 2 scsi-pci1000,21 (scsi-2) 0 pci 33 2 scsi-pci1000,21 (scsi-2) 0 pci 66 2 pci108e,abba (network) SUNW,pci-ce 0 pci 33 3 pci1095,646 (ide) 0 pci 33 4 bootbus-controller-sgsbbc SUNW,sgsbbc

============================ Memory Configuration ============================Segment Table:-----------------------------------------------------------------------Base Address Size Interleave Factor Contains-----------------------------------------------------------------------0x0 8GB 16 BankIDs 44,45,46,47,40,41,42,43,36,37,38,39,32, 33,34,35


Appendix

104

Bank Table:----------------------------------------------------------- Physical LocationID ControllerID GroupID Size Interleave Way-----------------------------------------------------------44 11 0 512MB 345 11 1 512MB 746 11 0 512MB 1147 11 1 512MB 1540 10 0 512MB 241 10 1 512MB 642 10 0 512MB 1043 10 1 512MB 1436 9 0 512MB 137 9 1 512MB 538 9 0 512MB 939 9 1 512MB 1332 8 0 512MB 033 8 1 512MB 434 8 0 512MB 835 8 1 512MB 12

Memory Module Groups:--------------------------------------------------ControllerID GroupID Labels--------------------------------------------------8 0 SB2/P0/B0/D08 0 SB2/P0/B0/D18 0 SB2/P0/B0/D28 0 SB2/P0/B0/D38 1 SB2/P0/B1/D08 1 SB2/P0/B1/D18 1 SB2/P0/B1/D28 1 SB2/P0/B1/D39 0 SB2/P1/B0/D09 0 SB2/P1/B0/D19 0 SB2/P1/B0/D29 0 SB2/P1/B0/D39 1 SB2/P1/B1/D09 1 SB2/P1/B1/D19 1 SB2/P1/B1/D29 1 SB2/P1/B1/D310 0 SB2/P2/B0/D010 0 SB2/P2/B0/D110 0 SB2/P2/B0/D210 0 SB2/P2/B0/D310 1 SB2/P2/B1/D010 1 SB2/P2/B1/D110 1 SB2/P2/B1/D210 1 SB2/P2/B1/D311 0 SB2/P3/B0/D011 0 SB2/P3/B0/D111 0 SB2/P3/B0/D211 0 SB2/P3/B0/D311 1 SB2/P3/B1/D0


Appendix

11 1 SB2/P3/B1/D111 1 SB2/P3/B1/D211 1 SB2/P3/B1/D3

============================ Environmental Status ============================Fan Speeds:---------------------------------------------Location Sensor Status Speed---------------------------------------------FT0/FAN3 ft_fan3 self-regulating FT0/FAN0 ft_fan0 self-regulating FT0/FAN1 ft_fan1 self-regulating FT0/FAN2 ft_fan2 self-regulating FT0/FAN4 ft_fan4 self-regulating FT0/FAN5 ft_fan5 self-regulating FT0/FAN6 ft_fan6 self-regulating FT0/FAN7 ft_fan7 self-regulating IB6/FAN0 ft_fan0 okay 100% IB6/FAN1 ft_fan1 okay 100%

Temperature sensors:-----------------------------------------------------------------------------Location Sensor Temperature Lo LoWarn HiWarn Hi Status-----------------------------------------------------------------------------SSC1 t_sbbc0 30C -12C -2C 102C 107C okaySSC1 t_cbh0 39C -12C -2C 102C 107C okaySSC1 t_ambient0 19C -12C -2C 82C 87C okaySSC1 t_ambient1 17C -12C -2C 82C 87C okaySSC1 t_ambient2 27C -12C -2C 82C 87C okayRP0 t_ambient0 17C -12C -2C 82C 87C okayRP0 t_ambient1 18C -12C -2C 53C 63C okayRP0 t_sdc0 58C -12C -2C 102C 107C okayRP0 t_ar0 42C -12C -2C 102C 107C okayRP0 t_dx0 55C -12C -2C 102C 107C okayRP0 t_dx1 58C -12C -2C 102C 107C okayRP2 t_ambient0 17C -12C -2C 82C 87C okayRP2 t_ambient1 16C -12C -2C 53C 63C okayRP2 t_sdc0 56C -12C -2C 102C 107C okayRP2 t_ar0 38C -12C -2C 102C 107C okayRP2 t_dx0 52C -12C -2C 102C 107C okayRP2 t_dx1 54C -12C -2C 102C 107C okaySB0 t_sdc0 - -12C -2C 102C 107C unknownSB0 t_ar0 - -12C -2C 102C 107C unknownSB0 t_dx0 - -12C -2C 102C 107C unknownSB0 t_dx1 - -12C -2C 102C 107C unknownSB0 t_dx2 - -12C -2C 102C 107C unknownSB0 t_dx3 - -12C -2C 102C 107C unknownSB0 t_sbbc0 - -12C -2C 102C 107C unknownSB0/P0 Ambient - -12C -2C 82C 87C unknownSB0/P1 Ambient - -12C -2C 82C 87C unknownSB0/P0 Die - -12C -2C 92C 97C unknownSB0/P1 Die - -12C -2C 92C 97C unknownSB0 t_sbbc1 - -12C -2C 102C 107C unknownSB0/P2 Ambient - -12C -2C 82C 87C unknownSB0/P3 Ambient - -12C -2C 82C 87C unknown


Appendix

106

SB0/P2 Die - -12C -2C 92C 97C unknownSB0/P3 Die - -12C -2C 92C 97C unknownSB2 t_sdc0 55C -12C -2C 102C 107C okaySB2 t_ar0 43C -12C -2C 102C 107C okaySB2 t_dx0 52C -12C -2C 102C 107C okaySB2 t_dx1 57C -12C -2C 102C 107C okaySB2 t_dx2 58C -12C -2C 102C 107C okaySB2 t_dx3 54C -12C -2C 102C 107C okaySB2 t_sbbc0 52C -12C -2C 102C 107C okaySB2/P0 Ambient 24C -12C -2C 82C 87C okaySB2/P1 Ambient 25C -12C -2C 82C 87C okaySB2/P0 Die 46C -12C -2C 92C 97C okaySB2/P1 Die 46C -12C -2C 92C 97C okaySB2 t_sbbc1 36C -12C -2C 102C 107C okaySB2/P2 Ambient 24C -12C -2C 82C 87C okaySB2/P3 Ambient 26C -12C -2C 82C 87C okaySB2/P2 Die 48C -12C -2C 92C 97C okaySB2/P3 Die 47C -12C -2C 92C 97C okayIB6 t_ambient0 23C -12C -2C 82C 87C okayIB6 t_ambient1 23C -12C -2C 82C 87C okayIB6 t_sdc0 68C -12C -2C 102C 107C okayIB6 t_ar0 51C -12C -2C 102C 107C okayIB6 t_dx0 58C -12C -2C 102C 107C okayIB6 t_dx1 51C -12C -2C 102C 107C okayIB6 t_sbbc0 43C -12C -2C 102C 107C okayIB6 t_schizo0 42C -12C -2C 102C 107C okayIB6 t_schizo1 39C -12C -2C 102C 107C okay----------------------------------------------------------------------Voltage sensors:----------------------------------------------------------------------Location Sensor Voltage Lo LoWarn HiWarn Hi Status----------------------------------------------------------------------SSC1 v_1.5vdc0 1.50V 1.35V 1.42V 1.57V 1.65V okaySSC1 v_3.3vdc0 3.35V 2.97V 3.13V 3.46V 3.63V okaySSC1 v_5vdc0 5.05V 4.50V 4.75V 5.25V 5.50V okayRP0 v_1.5vdc0 1.50V 1.35V 1.42V 1.58V 1.65V okayRP0 v_3.3vdc0 3.35V 2.97V 3.13V 3.47V 3.63V okayRP2 v_1.5vdc0 1.49V 1.35V 1.42V 1.58V 1.65V okayRP2 v_3.3vdc0 3.39V 2.97V 3.13V 3.47V 3.63V okaySB0 v_1.5vdc0 - 1.35V 1.42V 1.58V 1.65V unknownSB0 v_3.3vdc0 - 2.97V 3.13V 3.47V 3.63V unknownSB0/P0 v_cheetah0 - 1.46V 1.54V 1.73V 1.78V unknownSB0/P1 v_cheetah1 - 1.46V 1.54V 1.73V 1.78V unknownSB0/P2 v_cheetah2 - 1.46V 1.54V 1.73V 1.78V unknownSB0/P3 v_cheetah3 - 1.46V 1.54V 1.73V 1.78V unknownSB2 v_1.5vdc0 1.52V 1.35V 1.42V 1.58V 1.65V okaySB2 v_3.3vdc0 3.31V 2.97V 3.13V 3.47V 3.63V okaySB2/P0 v_cheetah0 1.63V 1.46V 1.54V 1.73V 1.78V okaySB2/P1 v_cheetah1 1.65V 1.46V 1.54V 1.73V 1.78V okaySB2/P2 v_cheetah2 1.64V 1.46V 1.54V 1.73V 1.78V okaySB2/P3 v_cheetah3 1.63V 1.46V 1.54V 1.73V 1.78V okayIB6 v_1.5vdc0 1.52V 1.35V 1.42V 1.57V 1.65V okayIB6 v_3.3vdc0 3.33V 2.97V 3.13V 3.46V 3.63V okayIB6 v_5vdc0 4.98V 4.50V 4.75V 5.25V 5.50V okayIB6 v_12vdc0 11.95V 10.80V 11.40V 12.60V 13.20V okay


Appendix

IB6 v_3.3vdc1 3.32V 2.97V 3.13V 3.47V 3.63V okayIB6 v_3.3vdc2 3.28V 2.97V 3.13V 3.47V 3.63V okayIB6 v_1.8vdc0 1.83V 1.62V 1.71V 1.89V 1.98V okayIB6 v_2.4vdc0 2.53V 2.25V 2.37V 2.62V 2.75V okayPS0 v_input0 - - - - - okayPS0 v_output0 - - - - - okayPS1 v_input0 - - - - - okayPS1 v_output0 - - - - - okayPS2 v_input0 - - - - - okayPS2 v_output0 - - - - - okayPS3 v_input0 - - - - - okayPS3 v_output0 - - - - - okay--------------------------------------------------Led State:--------------------------------------------------Location Led State Color-------------------------------------------------- - fault OFF amber - power ON green - locator OFF white - top_access OFF amber - alarm1 OFF amber - alarm2 OFF amber - system ON green - supplyA ON green - supplyB ON green DISK0 fault OFF amber DISK0 power ON green DISK0 ok_to_remove OFF blue DISK1 fault OFF amber DISK1 power ON green DISK1 ok_to_remove OFF blue PS0 fault OFF amber PS0 power ON green PS0 predicted_fault OFF amber PS1 fault OFF amber PS1 power ON green PS1 predicted_fault OFF amber PS2 fault OFF amber PS2 power ON green PS2 predicted_fault OFF amber PS3 fault OFF amber PS3 power ON green PS3 predicted_fault OFF amber FT0/FAN3 fault OFF amber FT0/FAN0 fault OFF amber FT0/FAN1 fault OFF amber FT0/FAN2 fault OFF amber FT0/FAN4 fault OFF amber FT0/FAN5 fault OFF amber FT0/FAN6 fault OFF amber FT0/FAN7 fault OFF amber FT0 fault OFF amber FT0 power ON green FT0 ok_to_remove OFF amber


Appendix

108

RP0 fault OFF amber RP0 power ON green RP0 ok_to_remove OFF amber RP2 fault OFF amber RP2 power ON green RP2 ok_to_remove OFF amber SB0 fault OFF amber SB0 power OFF green SB0 ok_to_remove ON amber SB2 fault OFF amber SB2 power ON green SB2 ok_to_remove OFF amber IB6/FAN0 fault OFF amber IB6/FAN1 fault OFF amber IB6 fault OFF amber IB6 power ON green IB6 ok_to_remove OFF amber

=========================== FRU Operational Status ===========================-------------------------Fru Operational Status:-------------------------Location Status -------------------------PS0 okayPS1 okayPS2 okayPS3 okayFT0 okayFT0/FAN3 okayFT0/FAN0 okayFT0/FAN1 okayFT0/FAN2 okayFT0/FAN4 okayFT0/FAN5 okayFT0/FAN6 okayFT0/FAN7 okayRP0 okayRP2 okaySB0 okSB0/P0 disabledSB0/P0/B0/D0 disabledSB0/P0/B0/D1 disabledSB0/P0/B0/D2 disabledSB0/P0/B0/D3 disabledSB0/P0/B1/D0 disabledSB0/P0/B1/D1 disabledSB0/P0/B1/D2 disabledSB0/P0/B1/D3 disabledSB0/P1 disabledSB0/P1/B0/D0 disabledSB0/P1/B0/D1 disabledSB0/P1/B0/D2 disabledSB0/P1/B0/D3 disabledSB0/P1/B1/D0 disabled


Appendix

SB0/P1/B1/D1 disabledSB0/P1/B1/D2 disabledSB0/P1/B1/D3 disabledSB0/P2 disabledSB0/P2/B0/D0 disabledSB0/P2/B0/D1 disabledSB0/P2/B0/D2 disabledSB0/P2/B0/D3 disabledSB0/P2/B1/D0 disabledSB0/P2/B1/D1 disabledSB0/P2/B1/D2 disabledSB0/P2/B1/D3 disabledSB0/P3 disabledSB0/P3/B0/D0 disabledSB0/P3/B0/D1 disabledSB0/P3/B0/D2 disabledSB0/P3/B0/D3 disabledSB0/P3/B1/D0 disabledSB0/P3/B1/D1 disabledSB0/P3/B1/D2 disabledSB0/P3/B1/D3 disabledSB2 okSB2/P0 onlineSB2/P0/B0/D0 okaySB2/P0/B0/D1 okaySB2/P0/B0/D2 okaySB2/P0/B0/D3 okaySB2/P0/B1/D0 okaySB2/P0/B1/D1 okaySB2/P0/B1/D2 okaySB2/P0/B1/D3 okaySB2/P1 onlineSB2/P1/B0/D0 okaySB2/P1/B0/D1 okaySB2/P1/B0/D2 okaySB2/P1/B0/D3 okaySB2/P1/B1/D0 okaySB2/P1/B1/D1 okaySB2/P1/B1/D2 okaySB2/P1/B1/D3 okaySB2/P2 onlineSB2/P2/B0/D0 okaySB2/P2/B0/D1 okaySB2/P2/B0/D2 okaySB2/P2/B0/D3 okaySB2/P2/B1/D0 okaySB2/P2/B1/D1 okaySB2/P2/B1/D2 okaySB2/P2/B1/D3 okaySB2/P3 onlineSB2/P3/B0/D0 okaySB2/P3/B0/D1 okaySB2/P3/B0/D2 okaySB2/P3/B0/D3 okaySB2/P3/B1/D0 okay


Appendix

110

SB2/P3/B1/D1 okaySB2/P3/B1/D2 okaySB2/P3/B1/D3 okayIB6 okIB6/FAN0 okayIB6/FAN1 okay

================================ HW Revisions ================================ASIC Revisions:---------------pci: Rev 4pci: Rev 4pci: Rev 4pci: Rev 4

bash-2.03#

lom -a output

Has the latest Netra Lights Out Management 2.0 patch been applied ?

bash-2.03# lom -a

PSUs:PS0 OKPS1 OKPS2 OKPS3 OK

Fans: 1 FT0/FAN3 ft_fan3 OK speed self-regulating 2 FT0/FAN0 ft_fan0 OK speed self-regulating 3 FT0/FAN1 ft_fan1 OK speed self-regulating 4 FT0/FAN2 ft_fan2 OK speed self-regulating 5 FT0/FAN4 ft_fan4 OK speed self-regulating 6 FT0/FAN5 ft_fan5 OK speed self-regulating 7 FT0/FAN6 ft_fan6 OK speed self-regulating 8 FT0/FAN7 ft_fan7 OK speed self-regulating 9 IB6/FAN0 ft_fan0 OK speed 100 %10 IB6/FAN1 ft_fan1 OK speed 100 %

LOM configuration settings:serial escape sequence=#.serial event reporting=defaultEvent reporting level=fatal, warning & informationfirmware version=5.17.0, build 6.4product ID=Netra T12

LOM Event Log: Tue Apr 13 10:50:04 1280-sc lom: SysEvent 5 /N0/PS2, power state, On (5,1) Tue Apr 13 10:50:04 1280-sc lom: /N0/PS1, sensor status, within acceptable


Appendix

Tue Apr 13 10:50:04 1280-sc lom: Device voltage stabilized: /N0/PS2 normal Tue Apr 13 10:50:05 1280-sc lom: SysEvent 5 /N0/PS3, power state, On (5,1) Tue Apr 13 10:50:05 1280-sc lom: /N0/PS2, sensor status, within acceptable Tue Apr 13 10:50:05 1280-sc lom: Device voltage stabilized: /N0/PS3 normal Tue Apr 13 10:50:05 1280-sc lom: /N0/PS3, sensor status, within acceptable Tue Apr 13 10:50:20 1280-sc lom: Domain Shell - A: poweron: Initiating key Tue Apr 13 10:50:20 1280-sc lom: Domain Shell - A: poweron: Initiating key Tue Apr 13 10:50:20 1280-sc lom: /N0/FT0, fan speed, Low (4,1)

LOM alarm states:Alarm1=offAlarm2=offAlarm3=onFault LED=off

Supply voltages: 1 SSC1 v_1.5vdc0 status=ok 2 SSC1 v_3.3vdc0 status=ok 3 SSC1 v_5vdc0 status=ok 4 RP0 v_1.5vdc0 status=ok 5 RP0 v_3.3vdc0 status=ok 6 RP2 v_1.5vdc0 status=ok 7 RP2 v_3.3vdc0 status=ok 8 SB0 v_1.5vdc0 status=unknown 9 SB0 v_3.3vdc0 status=unknown10 SB0/P0 v_cheetah0 status=unknown11 SB0/P1 v_cheetah1 status=unknown12 SB0/P2 v_cheetah2 status=unknown13 SB0/P3 v_cheetah3 status=unknown14 SB2 v_1.5vdc0 status=ok15 SB2 v_3.3vdc0 status=ok16 SB2/P0 v_cheetah0 status=ok17 SB2/P1 v_cheetah1 status=ok18 SB2/P2 v_cheetah2 status=ok19 SB2/P3 v_cheetah3 status=ok20 IB6 v_1.5vdc0 status=ok21 IB6 v_3.3vdc0 status=ok22 IB6 v_5vdc0 status=ok23 IB6 v_12vdc0 status=ok24 IB6 v_3.3vdc1 status=ok25 IB6 v_3.3vdc2 status=ok26 IB6 v_1.8vdc0 status=ok27 IB6 v_2.4vdc0 status=ok

System status flags: 1 PS0 status=okay 2 PS1 status=okay 3 PS2 status=okay 4 PS3 status=okay 5 FT0 status=okay 6 FT0/FAN3 status=okay 7 FT0/FAN0 status=okay 8 FT0/FAN1 status=okay 9 FT0/FAN2 status=okay10 FT0/FAN4 status=okay


Appendix

112

11 FT0/FAN5 status=okay12 FT0/FAN6 status=okay13 FT0/FAN7 status=okay14 RP0 status=okay15 RP2 status=okay16 SB0 status=ok17 SB0/P0 status=disabled18 SB0/P0/B0/D0 status=disabled19 SB0/P0/B0/D1 status=disabled20 SB0/P0/B0/D2 status=disabled21 SB0/P0/B0/D3 status=disabled22 SB0/P0/B1/D0 status=disabled23 SB0/P0/B1/D1 status=disabled24 SB0/P0/B1/D2 status=disabled25 SB0/P0/B1/D3 status=disabled26 SB0/P1 status=disabled27 SB0/P1/B0/D0 status=disabled28 SB0/P1/B0/D1 status=disabled29 SB0/P1/B0/D2 status=disabled30 SB0/P1/B0/D3 status=disabled31 SB0/P1/B1/D0 status=disabled32 SB0/P1/B1/D1 status=disabled33 SB0/P1/B1/D2 status=disabled34 SB0/P1/B1/D3 status=disabled35 SB0/P2 status=disabled36 SB0/P2/B0/D0 status=disabled37 SB0/P2/B0/D1 status=disabled38 SB0/P2/B0/D2 status=disabled39 SB0/P2/B0/D3 status=disabled40 SB0/P2/B1/D0 status=disabled41 SB0/P2/B1/D1 status=disabled42 SB0/P2/B1/D2 status=disabled43 SB0/P2/B1/D3 status=disabled44 SB0/P3 status=disabled45 SB0/P3/B0/D0 status=disabled46 SB0/P3/B0/D1 status=disabled47 SB0/P3/B0/D2 status=disabled48 SB0/P3/B0/D3 status=disabled49 SB0/P3/B1/D0 status=disabled50 SB0/P3/B1/D1 status=disabled51 SB0/P3/B1/D2 status=disabled52 SB0/P3/B1/D3 status=disabled53 SB2 status=ok54 SB2/P0 status=online55 SB2/P0/B0/D0 status=okay56 SB2/P0/B0/D1 status=okay57 SB2/P0/B0/D2 status=okay58 SB2/P0/B0/D3 status=okay59 SB2/P0/B1/D0 status=okay60 SB2/P0/B1/D1 status=okay61 SB2/P0/B1/D2 status=okay62 SB2/P0/B1/D3 status=okay63 SB2/P1 status=online64 SB2/P1/B0/D0 status=okay


Appendix

65 SB2/P1/B0/D1 status=okay66 SB2/P1/B0/D2 status=okay67 SB2/P1/B0/D3 status=okay68 SB2/P1/B1/D0 status=okay69 SB2/P1/B1/D1 status=okay70 SB2/P1/B1/D2 status=okay71 SB2/P1/B1/D3 status=okay72 SB2/P2 status=online73 SB2/P2/B0/D0 status=okay74 SB2/P2/B0/D1 status=okay75 SB2/P2/B0/D2 status=okay76 SB2/P2/B0/D3 status=okay77 SB2/P2/B1/D0 status=okay78 SB2/P2/B1/D1 status=okay79 SB2/P2/B1/D2 status=okay80 SB2/P2/B1/D3 status=okay81 SB2/P3 status=online82 SB2/P3/B0/D0 status=okay83 SB2/P3/B0/D1 status=okay84 SB2/P3/B0/D2 status=okay85 SB2/P3/B0/D3 status=okay86 SB2/P3/B1/D0 status=okay87 SB2/P3/B1/D1 status=okay88 SB2/P3/B1/D2 status=okay89 SB2/P3/B1/D3 status=okay90 IB6 status=ok91 IB6/FAN0 status=okay92 IB6/FAN1 status=okay

System Temperature Sensors: 1 SSC1 t_sbbc0 30 degC : warning 102 degC : shutdown 107 degC 2 SSC1 t_cbh0 39 degC : warning 102 degC : shutdown 107 degC 3 SSC1 t_ambient0 19 degC : warning 82 degC : shutdown 87 degC 4 SSC1 t_ambient1 17 degC : warning 82 degC : shutdown 87 degC 5 SSC1 t_ambient2 27 degC : warning 82 degC : shutdown 87 degC 6 RP0 t_ambient0 17 degC : warning 82 degC : shutdown 87 degC 7 RP0 t_ambient1 18 degC : warning 53 degC : shutdown 63 degC 8 RP0 t_sdc0 58 degC : warning 102 degC : shutdown 107 degC 9 RP0 t_ar0 42 degC : warning 102 degC : shutdown 107 degC10 RP0 t_dx0 55 degC : warning 102 degC : shutdown 107 degC11 RP0 t_dx1 58 degC : warning 102 degC : shutdown 107 degC12 RP2 t_ambient0 18 degC : warning 82 degC : shutdown 87 degC13 RP2 t_ambient1 17 degC : warning 53 degC : shutdown 63 degC14 RP2 t_sdc0 56 degC : warning 102 degC : shutdown 107 degC15 RP2 t_ar0 38 degC : warning 102 degC : shutdown 107 degC16 RP2 t_dx0 52 degC : warning 102 degC : shutdown 107 degC17 RP2 t_dx1 55 degC : warning 102 degC : shutdown 107 degC18 SB0 t_sdc0 - : warning 102 degC : shutdown 107 degC19 SB0 t_ar0 - : warning 102 degC : shutdown 107 degC20 SB0 t_dx0 - : warning 102 degC : shutdown 107 degC21 SB0 t_dx1 - : warning 102 degC : shutdown 107 degC22 SB0 t_dx2 - : warning 102 degC : shutdown 107 degC23 SB0 t_dx3 - : warning 102 degC : shutdown 107 degC24 SB0 t_sbbc0 - : warning 102 degC : shutdown 107 degC


Appendix

114

25 SB0 t_sbbc1 - : warning 102 degC : shutdown 107 degC26 SB0/P0 Ambient - : warning 82 degC : shutdown 87 degC27 SB0/P0 Die - : warning 92 degC : shutdown 97 degC28 SB0/P1 Ambient - : warning 82 degC : shutdown 87 degC29 SB0/P1 Die - : warning 92 degC : shutdown 97 degC30 SB0/P2 Ambient - : warning 82 degC : shutdown 87 degC31 SB0/P2 Die - : warning 92 degC : shutdown 97 degC32 SB0/P3 Ambient - : warning 82 degC : shutdown 87 degC33 SB0/P3 Die - : warning 92 degC : shutdown 97 degC34 SB2 t_sdc0 55 degC : warning 102 degC : shutdown 107 degC35 SB2 t_ar0 43 degC : warning 102 degC : shutdown 107 degC36 SB2 t_dx0 53 degC : warning 102 degC : shutdown 107 degC37 SB2 t_dx1 58 degC : warning 102 degC : shutdown 107 degC38 SB2 t_dx2 58 degC : warning 102 degC : shutdown 107 degC39 SB2 t_dx3 54 degC : warning 102 degC : shutdown 107 degC40 SB2 t_sbbc0 52 degC : warning 102 degC : shutdown 107 degC41 SB2 t_sbbc1 37 degC : warning 102 degC : shutdown 107 degC42 SB2/P0 Ambient 24 degC : warning 82 degC : shutdown 87 degC43 SB2/P0 Die 45 degC : warning 92 degC : shutdown 97 degC44 SB2/P1 Ambient 25 degC : warning 82 degC : shutdown 87 degC45 SB2/P1 Die 47 degC : warning 92 degC : shutdown 97 degC46 SB2/P2 Ambient 24 degC : warning 82 degC : shutdown 87 degC47 SB2/P2 Die 48 degC : warning 92 degC : shutdown 97 degC48 SB2/P3 Ambient 26 degC : warning 82 degC : shutdown 87 degC49 SB2/P3 Die 48 degC : warning 92 degC : shutdown 97 degC50 IB6 t_ambient0 23 degC : warning 82 degC : shutdown 87 degC51 IB6 t_ambient1 23 degC : warning 82 degC : shutdown 87 degC52 IB6 t_sdc0 68 degC : warning 102 degC : shutdown 107 degC53 IB6 t_ar0 51 degC : warning 102 degC : shutdown 107 degC54 IB6 t_dx0 58 degC : warning 102 degC : shutdown 107 degC55 IB6 t_dx1 52 degC : warning 102 degC : shutdown 107 degC56 IB6 t_sbbc0 43 degC : warning 102 degC : shutdown 107 degC57 IB6 t_schizo0 42 degC : warning 102 degC : shutdown 107 degC58 IB6 t_schizo1 39 degC : warning 102 degC : shutdown 107 degC

LOM led states:1 OFF amber chassis fault 2 ON green chassis power 3 OFF white chassis locator 4 OFF amber chassis top_access 5 OFF amber chassis alarm1 6 OFF amber chassis alarm2 7 ON green chassis system 8 ON green chassis supplyA 9 ON green chassis supplyB 10 OFF amber PS0 fault 11 ON green PS0 power 12 OFF amber PS0 predicted_fault 13 OFF amber PS1 fault 14 ON green PS1 power 15 OFF amber PS1 predicted_fault 16 OFF amber PS2 fault


Appendix

17 ON green PS2 power 18 OFF amber PS2 predicted_fault 19 OFF amber PS3 fault 20 ON green PS3 power 21 OFF amber PS3 predicted_fault 22 OFF amber FT0 fault 23 ON green FT0 power 24 OFF amber FT0 ok_to_remove 25 OFF amber RP0 fault 26 ON green RP0 power 27 OFF amber RP0 ok_to_remove 28 OFF amber RP2 fault 29 ON green RP2 power 30 OFF amber RP2 ok_to_remove 31 OFF amber SB0 fault 32 OFF green SB0 power 33 ON amber SB0 ok_to_remove 34 OFF amber SB2 fault 35 ON green SB2 power 36 OFF amber SB2 ok_to_remove 37 OFF amber IB6 fault 38 ON green IB6 power 39 OFF amber IB6 ok_to_remove 40 OFF amber DISK0 fault 41 ON green DISK0 power 42 OFF blue DISK0 ok_to_remove 43 OFF amber DISK1 fault 44 ON green DISK1 power 45 OFF blue DISK1 ok_to_remove 46 OFF amber FT0/FAN3 fault 47 OFF amber FT0/FAN0 fault 48 OFF amber FT0/FAN1 fault 49 OFF amber FT0/FAN2 fault 50 OFF amber FT0/FAN4 fault 51 OFF amber FT0/FAN5 fault 52 OFF amber FT0/FAN6 fault 53 OFF amber FT0/FAN7 fault 54 OFF amber IB6/FAN0 fault 55 OFF amber IB6/FAN1 fault

bash-2.03#


Appendix

116


lw8 quick ref guide 0406

Documents