<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">OBSOLETE Patch-ID# 114524-05

NOTE:
***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************

Keywords: sun fire firmware flashprom update 5.17.4 scapp rtos
Synopsis: Obsoleted by: 114524-06 Hardware/PROM: Sun Fire E6900/E4900/E2900/6800/4810/4800/3800 and V1280 Systems Firmware Update
Date: Feb/24/2005


Install Requirements: None                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: Hardware/PROM

Unbundled Release: ScApp:5.17.4,RTOS:41,SC POST:41

Xref: 

Topic: Sun Fire system controller and flashprom update 5.17.4

Relevant Architectures: sparc

BugId's fixed with this patch: 4634042 4667136 4683268 4690339 4828481 4837427 4848267 4874811 4906709 4911531 4913880 4914718 4915147 4915848 4915868 4915878 4916043 4916893 4918955 4919097 4919720 4919828 4926111 4926120 4928916 4931043 4933057 4934890 4935596 4936919 4939507 4939596 4940445 4941478 4943001 4944338 4945101 4945826 4945996 4946485 4946527 4946869 4947870 4948030 4948764 4950061 4950423 4950889 4951230 4951771 4953215 4955118 4955220 4955421 4955970 4956096 4956167 4957007 4957665 4958334 4958868 4958882 4959016 4959992 4960429 4960536 4962119 4962161 4962250 4962937 4963974 4964582 4965224 4965664 4966599 4966623 4967214 4967353 4967888 4968505 4969379 4971282 4973201 4974020 4975123 4975695 4975830 4976472 4976504 4976872 4976914 4978324 4979075 4979571 4979580 4979597 4981257 4981273 4981483 4982034 4982854 4983481 4983789 4984203 4984312 4984974 4985730 4987176 4988128 4990431 4990441 4992628 4993985 4994426 4994641 4994905 4997043 5002072 5002357 5004331 5006810 5009856 5009864 5010205 5011320 5012130 5015488 5027547 5029856 5030395 5031658 5034739 5034767 5035293 5036321 5042076 5042636 5049265 5051257 5051422 5053287 5058313 5062510 5065337 5068391 5070035 5077697 5080862 5083664 5091506 5093903 5099024 5099206 5106212 6183416 6190958 6193290 6202816 6217215 6217224 6217337

Changes incorporated in this version: 4690339 4828481 5009864 5012130 5058313 5070035 5091506 5093903 5106212 6183416 6190958 6193290 6202816 6217215 6217224 6217337

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 
See Special Instructions: Watchdog Timer information and configuration instructions.

Files included with this patch: 

Install.info
README.114524-05
Sun_Fire_Entry-Level_Midrange_System_Administration_Guide.pdf
Sun_Fire_Entry-Level_Midrange_System_Controller_Command_Reference_Manual.pdf
Sun_Fire_Entry-Level_Midrange_System_Firmware_5.17.0_Release_Notes.pdf
Sun_Fire_Midrange_System_Controller_Command_Reference_Manual.pdf
Sun_Fire_Midrange_Systems_Firmware_5.17.0_Release_Notes.pdf
Sun_Fire_Midrange_Systems_Platform_Administration_Manual.pdf
copyright
lw8cpu.flash
lw8pci.flash
sgcpu.flash
sgiowci.flash
sgiowci_sp.flash
sgpci.flash
sgrtos.flash
sgsc.flash

Problem Description:

(From 114524-05)
 
4690339 domain error isolation  CM_EACK in C accompanied by ConsolePortError in D
4828481 Console messages "addRecord: Segment TH Insufficient space Need 35 have 25"
5009864 SC Failover service port needs to be private
5012130 SC accepts packets with private IP addresses.
5058313 takes a long time to synchronize failover status after "setfailover force"
5070035 Alarm 3 on Lightweight 8 needs to be user programmable for backward compatiblity
5091506 6800 System fails to boot with 6 JAG's loaded with 2g  memory config.
5093903 SIGBUS error occurred during multiple showenvironment commands.
5106212 PS Failure Causes false FT Failure
6183416 Certain DIMM failures cannot be isolated
6190958 Change Vcore voltage from 1.225 to 1.25 volts for Jag 3.x
6193290 LW8 (V1280, Netra 1280, E2900) service mode contains engineering mode only comma
6202816 add warning for incompatible dimm sizes on V1 and V2 uniboards
6217215 Create a common webrev directory and change source to use that directory.
6217224 Copyright file needs updated for 2005.
6217337 Need to update the COBP banner to reflect the year 2005.
 
(From 114524-04)
 
5053287 E2900 gives "I2c error: slave did not ACK" message after resetsc
5077697 "6800-SC[service]&gt; testinterconnet" passes despite missing centreplane pin
5080862 system does not not have SC failover automatically enabled after power cycle
5099024 Persistent Msg Log Error count corrupted.
5099206 Seprom addRecord errors are not actionable
 
 
(From 114524-03)
 
4683268 SC POST should reset M48T59 watchdog at boot
4911531 SC drifts time of about 1 to 2 seconds
4984203 Frame fan tray and RTS status are not logged
5006810 Domain level POST need to handle failed CPUs(master/slave) effectively
5009856 Implement new Vcore setting for Jaguar 3.x
5011320 showboards displays invalid Cpu Mask for Jaguar 3.0
5027547 OBP needs to check for domain keyswitch state before dropping to OK prompt
5034739 show-post-results does not recognize Xmits IO boards
5036321 RFE to the SCAPP command "sepromupdate" with a new option
5042636 Faulty system board causes NullPointerException and causes an impression that se
5049265 SC hangs at Boot with virgin U2106
5051257 mem2 /N0/SB4/P3/Cx timeout, has no hearbeat, not responding
5051422 SCApp needs to support JG3.1 and JG2.4
5062510 DomainBufferWriter thread error
5065337 Reset of Domain causes CHS disable board.
5068391 postTestList may be null during startCpu/stopCpu
5083664 backout changes for bug#5060748 which can cause ssh disabled.
 
 
(From 114524-02)
 
4934890 ScApp 5.15.X intermittently loses network connectivity
4982034 Ecache tag ecc err test needs to handle THCE
4987176 panic trying to lock ISM page that isn't there
4988128 CPU Time-out (TO) from system bus during POST is not evaluated (ESC#550091)
4993985 Interconnect fails but all FRUs are still included (ESC#550922)
4994905 functioning A184 PS are not detected and acknowledged as powered on
4997043 "interrupt: panic:netJobAdd: ring buffer overflow!" w/o any issues from tNetTask
5010205 POST support for 1200 MHz USIV processors
5015488 rtos workspace structure considered harmful
5029856 PS failure caused I2C problems with other FRUs.
5030395 Serengeti POST does not use new FPROM Access Timing during domain level tests
5031658 Need to handle setBytes failure when write log messages to the persistent log
5034767 regression test stopper: POST fails SB0 and excludes it
5035293 Jar's Manifest isn't treated properly by SC JVM
5042076 setk on failed to standby mode
 
 
(From 114524-01)
 
4634042 ScApp needs intermediate environmental warnings
4667136 "sepromupdate -h" does not show help screen
4837427 Serengeti Availability 1.2.
4848267 Serengeti XMITS support
4874811 Implement fpu aligned test for POST
4906709 RFE Incorporate LW8 development into parent Serengeti source tree
4913880 lom -t , -f , -a missing output
4914718 showcomp ib6 throw exeption
4915147 lom -f and showenv missing 7 other fans, as a result of poweroff operations
4915848 RP0 RP2 not assigned in showboards output - test stopper SSTT
4915868 shutdown does not bring system to standby after solaris reboots
4915878 java exception fatal error, when showcomp after poweroff
4916043 "Starting telnet server ..." when networking is not enabled
4916893 "Entering OBP" now appears after the ok prompt (serengeti/lw8)
4918955 media tray appear not tested
4919097 OBP MMU miss results in OBP hang instead of drop to ok prompt
4919720 engineering cli - 5.16.0 features are visible
4919828 behavior does not match 4718798
4926111 java exeption from testboard and (bootmode skipdiag, poweron)
4926120 5.13.0014 outofmemory exception with lom -G of 5.16.0 scapp ima
4928916 ssh client connection hangs
4931043 bootmode diag, poweron hangs the console
4933057 IDE controller Error in POST
4935596 obpCallBackThread: Initiating keyswitch: off, domain A.
4936919 fault led is not on
4939507 under voltage margin Warning Thresholds are not changeing to the correct values.
4939596 reset/reset-all in obp - sun.serengeti.IllegalKeyException
4940445 Error closing connection:java.io.IOException: S_errno_EPIPE
4941478 cannot change bootmode
4943001 SC Main must send SC spare the time it will take to be back up after reboot.
4944338 Add ScApp support for new Amazon E2900
4945101 errorjava.lang.OutOfMemoryError during setfailover
4945826 serengeti: post errors with wci board in domain
4945996 LW8 SC hanged while rebooting the SC
4946485 "showfru -r manr" time and vend column are not properly aligned
4946527 On new ID board rtos should not be allowed to downgrade
4946869 serengeti: showsc does not show spare or main sc in the output
4947870 cannot "boot" from rtos prompt
4948030 setdate does not set a timezone properly when offset to GMT is X.X
4948764 line in flashupdate -h wraps around
4950061 Jaguar reports a CDPE when it receives data with an ECC error.
4950423 showfru needs a update indicator to indicate it is running
4950889 Fail POST when interleave-scope is across-boards and interleave-mode is off
4951230 Continuous setkeyswitch of domains caused Domain to stop at off_to_on status
4951771 ERROR case: DR in certain stuck at fault system board crashes the domain
4953215 ScApp needs to recognize Cheetah++ 1.2
4955118 message; Connection refused, console busy on domain A
4955220 REGRESSION: Amazon putback undo bugid 4922709
4955421 lw8 messages got removed!
4955970 LW8 must be secure out-of-the-box
4956096 wildcat fabric manager should be turned off for secure out-of-the-box
4956167 Specify an invalid connection type cause exception to be displayed.
4957007 ckdimm probe breaks starcat in some configurations
4957665 HPE should be disabled by default on Jaguar systems
4958334 confused msg while system detects error
4958868 showfru "time" column is in 12 hr format, but inventory shows 24 hour format
4958882 setupplatform -p network should not mention Explorer with ssh
4959016 CH+ SB failed during "setkeyswitch on" on mixed CH+/Jag domain.
4959992 ECC error scrolling on the main SC.
4960429 WARNING: DomainBufferReader thread did die
4960536 Reboot after CPU indictment results in panic
4962119 Jaguar POST MEM2 is taking 20 hours to complete
4962161 system hard hang after multi reset-all
4962250 Move Avail CLI options into the platfrom CLI so serengeti and lw8 is the same
4962937 connection to serial port, after max # of SSH connections causes errors
4963974 confused msg while enable a component
4964582 Jaguar CPU temperature max should be 110C as it is for StarCat.
4965224 UltraSPARC-s420 (impl 0x19) recognized as SUNW,UltraSPARC-IV (impl 0x18)
4965664 Implement new FPROM timing support for POST test time improvements
4966599 LogError reports wrong sbbc group for cheetah errors
4966623 LogError does not create Error Control block for AFAR low
4967214 persistentlog should not be allowed in user mode.
4967353 remove "-t" option from restoreconfig help message
4967888 typo in SpShell.java
4968505 lw8 should clear a corrupted nvci assigned-list
4969379 ovenmode may not work correctly on lw8
4971282 Need to be able to use DC/MD Replacement Centerplanes on both Serengeti &amp; Amazon
4973201 Platadmin module fails to update when SC is powered off or hotswapped out
4974020 sc_app uses old power numbers for new Jaguar, IO, and fan tray brds.
4975123 trying to go to console from SC hangs SC when using max # of connections
4975695 lom -t output is missing t_ambient1
4975830 SC Table displays some meaningless/invalid/wrong values
4976472 POST error during DR causes domain to crash
4976504 SC Power Status in SCApp MIB is not updated after power off the spare SSC1
4976872 A MIB trap should be sent when a power supply is powered off
4976914 domain A cannot recover automatically after error injection system panic
4978324 showlogs -d, domains exposed in lw8
4979075 avl 1.2 is not working
4979571 Native methods of children of class Spd accessing private members of Spd
4979580 Platform.isLw8 not reliable at startup
4979597 showlogs -f/-n [options] error message expose internals of the code.
4981257 showlogs -v (illegal option with SC classic) and ++
4981273 Regression: API in OccupantApi should not print error message
4981483 java.lang.ArrayIndexOutOfBoundsException: 2 - domain does not reboot
4982854 Reg name field for Jaguar should be in sync Cheetah through addImpedance()
4983481 scapp should warn if jaguar cpus are powered on in a non-supporting chassis.
4983789 CONSOLE_RETRY_TIME needs to be increased
4984312 check for serengeti prom images on a lw8
4984974 lom -t lom -a prtpicl -c regression
4985730 SCApp needs to support Jaguar TO3.0
4990431 regression in nightly build: poweron ib6 throws exception
4990441 null pointer exception is encountered when showp command is issued on qads6-sc1.
4992628 A CPU is being diagnosed as failed during an ECC event
4994426 undefined message in Chassis.java
4994641 ERROR: MailboxWorkerThread caught exception(error injection)/dr disconnect
5002072 Unable to run 0Meg serengeti boards with diag level set to mem2
5002357 'setdefaults' arbitraily clears BootFlags when some must remain set.
5004331 incorrect data used for amazon fan tray power consumption.
5005640 ScApps for LW8 Amazon will not support 2N power.
5006812 Update Artesyn D149 2.5 voltage margin for XMIT board.

Patch Installation Instructions:
--------------------------------
Please refer to the Install.info file for instructions on updating
the firmware using the files included in this patch.
 
Special Instructions:
---------------------
Watchdog Timer - Sun Fire Entry-Level Midrange Systems 5.17.4 - 2/17/2005
=========================================================================
 
 
This text gives information on the application mode of the watchdog
timer on the Netra 1280 server.
 
The enhancement allows users to:
 
o Configure the watchdog timer - User applications running on the host can 
configure and use the watchdog timer, enabling customers to detect fatal 
problems from their applications and to recover automatically.
 
o Program Alarm 3 - This enables users to generate this alarm in case of 
critical problems in their applications.
 
This README text provides the following sections to help you understand how to 
configure and use the watchdog timer and program Alarm3:
 
o Upgrading the Firmware Using the lom -G Command
o Understanding the Watchdog Timer Application Mode
o Using the ntwdt Driver
o Understanding the User APIs
o Setting the Time-out Period
o Enabling or Disabling the Watchdog
o Rearming, or Patting, the Watchdog
o Getting the State of the Watchdog Timer
o Finding and Defining Data Structures
o Using the Sample Watchdog Program
o Programming Alarm3
o Understanding Error Messages
o Knowing Unsupported Features and Limitations
 
 
 
Upgrading the Firmware Using the lom -G Command
-----------------------------------------------
 
1) Upgrade the firmware on the system controller (SC):
 
       #lom -G sgsc.flash
       #lom -G sgrtos.flash
 
2) Escape to lom&gt; and reset the SC:
 
       lom&gt; resetsc -y
 
   To get to the lom prompt, you can telnet directly into the Ethernet port of   
   the SC (this is different from the Solaris IP address), or you can attach a   
   console to the serial port on the SC. If you are remote from the system,      
   configure the SC's ethernet port, or attach the SC serial port to a network   
   terminal server.
 
3) Upgrade the firmware on the system boards:
 
       #lom -G lw8cpu.flash
       #lom -G lw8pci.flash
 
4) Shutdown the Solaris OS.
 
5) Power off the system.
 
6) Power on the system.
 
 
 
Understanding the Watchdog Timer Application Mode
-------------------------------------------------
 
 
The watchdog mechanism detects a system hang, or an application hang or crash, 
should they occur. The watchdog is a timer that is continually reset by a user 
application as long as the operating system and user application are running. 
 
When the application is rearming the application watchdog, an expiration can be 
caused by:
 
o Crash of the rearming application
o Hang or crash of the rearming thread in the application
o System hang
 
When the system watchdog is running, a system hang, or more specifically, the 
hang of the clock interrupt handler causes an expiration.
 
The system watchdog mode is the default. If the application watchdog is 
not initialized, then the system watchdog mode is used.
 
The "setupsc" command, an existing command on the system controller (SC) 
Lights Out Management (LOM) can be used to configure the recovery for the system 
watchdog ONLY:
 
lom&gt;setupsc
 
The system controller configuration should be as follows:
 
SC POST diag Level [off]:
Host Watchdog [enabled]:
Rocker Switch [enabled]:
Secure Mode [off]:
 
PROC RTUs installed: 0
PROC Headroom quantity (0 to disable, 4 MAX) [0]:
 
The recovery configuration for the application watchdog is set using 
Input/Output Control codes (IOCTLs) that are issued to the ntwdt driver.
 
 
 
Using the ntwdt Driver
----------------------
 
 
To use the new application watchdog feature, you must install the ntwdt 
driver. To enable and control the watchdog's application mode, you must 
program the watchdog system using the LOMIOCDOGxxx IOCTLs, described in the 
section "Understanding the User API".
 
If the ntwdt driver, as opposed to the system controller, initiates a reset of 
the Solaris(TM) Operating System (OS) on application watchdog expiration, the 
value of the following property in the ntwdt driver's configuration file 
(ntwdt.conf) is used:
 
ntwdt-boottimeout="600";
 
In case of a panic, or an expiration of the application watchdog, the ntwdt 
driver reprograms the watchdog time-out to the value specified in the property.
 
Assign a value representing a duration that is longer than the time it takes to 
reboot and perform a crash dump. If the specified value is not large enough, the 
SC resets the host if reset is enabled. Note that this reset by the SC occurs 
only once.
 
 
 
Understanding the User API
---------------------------
 
 
The ntwdt driver provides an application program interface by using IOCTLs. You 
must open the /dev/ntwdt device node before issuing the watchdog IOCTLs.
 
--------------------------------------------------------------------------------
NOTE: Only a single concurrent instance of open() is allowed on /dev/ntwdt. Any 
subsequent open() generates the following error message: EAGAIN - (The driver is 
busy, try again.)
--------------------------------------------------------------------------------
 
You can use the following IOCTLs with the watchdog timer:
 
o LOMIOCDOGTIME -  Set time-out period for watchdog timer 
o LOMIOCDOGCTL -   Enable or disable watchdog timer
o LOMIOCDOGPAT -   Rearm, or pat, watchdog timer
o LOMIOCDOGSTATE - Get state of watchdog timer
o LOMIOCALCTL -    Set value of Alarm3
o LOMIOCALSTATE -  Get state of Alarm3
 
 
 
Setting the Time-out Period
---------------------------
 
 
The LOMIOCDOGTIME IOCTL sets the time-out period of the watchdog. This IOCTL 
programs the watchdog hardware with the time specified in this IOCTL. You must 
set the time-out period (LOMIOCDOGTIME) before attempting to enable the watchdog 
timer (LOMIOCDOGCTL).
 
The argument is a pointer to an unsigned integer. This integer holds the
new time-out period for the watchdog in multiples of 1 second.
 
The watchdog framework allows only time-outs in excess of 1 second. You can 
specify any time-out period in the range of 1 second to 180 minutes.
 
If the watchdog function is enabled, the time-out period is immediately
reset so that the new value can take effect. An error (EINVAL) is displayed if 
the time-out period is less than 1 second or longer than 180 minutes.
 
-----------------------------------------------------------------------------
NOTE: The LOMIOCDOGTIME is not intended for general purpose use. Setting the
watchdog time-out to too low a value might cause the system to receive a
hardware reset if the watchdog and reset functions are enabled. If the
time-out is set too low, the user application must be run with a higher
priority (for example, as a real time thread) and must be rearmed more
often to avoid an unintentional expiration.
-----------------------------------------------------------------------------
 
 
 
Enabling or Disabling the Watchdog
----------------------------------
 
 
The LOMIOCDOGCTL IOCTL enables or disables the watchdog, and it enables or 
disables the reset capability. (See the "Data Structures" section for the 
correct values for the watchdog timer.) 
 
The argument is a pointer to the lom_dogctl_t structure (described in
greater detail in the "Data Structures" section).
 
Use the reset_enable member to enable or disable the system reset function. 
Use the dog_enable member to enable or disable the watchdog function. An
error (EINVAL) is displayed if the watchdog is disabled and reset is
enabled.
 
--------------------------------------------------------------------------------
NOTE: If LOMIOCDOGTIME has not been issued to set up the time-out period prior 
to this IOCTL, the watchdog is NOT enabled in the hardware.
--------------------------------------------------------------------------------
 
 
 
Rearming, or Patting, the Watchdog
----------------------------------
 
 
The LOMIOCDOGPAT IOCTL rearms, or pats, the watchdog so that the watchdog starts 
ticking from the beginning; that is, to the value specified by LOMIOCDOGTIME. 
This IOCTL requires no arguments. If the watchdog is enabled, this IOCTL must be 
used at regular intervals that are less than the watchdog time-out, or the 
watchdog expires.
 
 
 
Getting the State of the Watchdog Timer
---------------------------------------
 
 
The LOMIOCDOGSTATE IOCTL gets the state of the watchdog and reset
functions and retrieves the current time-out period for the watchdog. If
LOMIOCDOGSTATE was never issued to set up the time-out period prior to
this IOCTL, the watchdog is not enabled in the hardware.
 
The argument is a pointer to the lom_dogstate_t structure (described in
greater detail in the section on "Data Structures"). The structure members
are used to hold the current states of the watchdog reset circuitry and
current watchdog time-out period. Note that this is not the time
remaining before the watchdog is triggered.
 
The LOMIOCDOGSTATE IOCTL requires only that open() be successfully called. This 
IOCTL can be run any number of times after open() is called, and it does not 
require any other DOG IOCTLs to have been executed.
 
 
 
Finding and Defining Data Structures
------------------------------------
 
 
All data structures and IOCTLs are defined in lom_io.h, which is available in 
the SUNWlomu package.
 
The data structures for the watchdog timer are shown here:
 
1. The watchdog/reset state data structure is as follows:
 
typedef struct { 
	int reset_enable; /* reset enabled if non-zero */ 
	int dog_enable; /* watchdog enabled if non-zero */ 
	uint_t dog_timeout; /* Current watchdog time-out in seconds */ 
} lom_dogstate_t; 
 
2. The watchdog/reset control data structure is as follows:
 
typedef struct { 
        int reset_enable; /* reset enabled if non-zero */ 
        int dog_enable; /* watchdog enabled if non-zero */ 
} lom_dogctl_t;
 
 
 
Using the Sample Watchdog Program
-----------------------------
 
 
Following is a sample program for the watchdog timer:
 
#include &lt;sys/types.h&gt;
#include &lt;lom_io.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/stat.h&gt;
 
void
main()
{
        uint_t timeout = 30;
        lom_dogctl_t dogctl;
        dogctl.reset_enable = 1;
        dogctl.dog_enable = 1;
 
        int fd = open("/dev/ntwdt", O_EXCL);
 
        /* Set timeout */
        ioctl(fd, LOMIOCDOGTIME, (void *)&amp;timeout);
 
        /* Enable watchdog */
        ioctl(fd, LOMIOCDOGCTL, (void *)&amp;dogctl);
 
        /* Keep patting */
        while (1) {
                ioctl(fd, LOMIOCDOGPAT, NULL);
                sleep (5);
        }
 
     return (0);
} 
 
 
 
Programming Alarm3
------------------
 
 
Alarm3 is available to Solaris Operating System users irrespective of the 
watchdog mode. Alarm3 or system alarm ON and OFF have been redefined (see the 
table below.) 
 
 
Set the value of Alarm3 using the LOMIOCALCTL IOCTL. You can program Alarm3 like 
you set and clear Alarm1 and Alarm2.
 
The following table presents the behavior of Alarm3:
 
                            Alarm3        Relay       System LED (Green)
  ---------------------------------------------------------------------
  Poweroff                    ON          COM -&gt; NC    OFF
  Poweron/LOM up              ON          COM -&gt; NC    OFF
  Solaris running             OFF         COM -&gt; NO    ON  
  Solaris not running         ON          COM -&gt; NC    OFF
  Host WDT expires            ON          COM -&gt; NC    OFF
  User sets to ON             ON          COM -&gt; NC    OFF
  User sets to OFF            OFF         COM -&gt; NO    ON 
 
Alarm3 ON = Relay(COM-&gt;NC), System LED OFF
Alarm3 OFF = Relay(COM-&gt;NO), System LED ON
 
When programmed, you can check Alarm3 or the system alarm with the showalarm 
command and the argument "system".
 
For example:
 
sc&gt;showalarm system
system alarm is on
 
The data structure used with the LOMIOCALCTL and LOMIOCALSTATE IOCTLs is as 
follows:
 
#include lom_io.h
#define ALARM_NUM_1 1 
#define ALARM_NUM_2 2 
#define ALARM_NUM_3 3 
#define ALARM_OFF 0 
#define ALARM_ON 1 
typedef struct {
	int alarm_no; 
	int alarm_state;
} lom_aldata_t; 
 
 
 
Understanding Error Messages
----------------------------
 
 
Following are the error messages that might be displayed and what they mean:
 
 
EAGAIN 
 
This error message is displayed if you attempt to open more than one instance 
of open() on /dev/ntwdt.
 
 
EFAULT
 
This error message is displayed if an incorrect user-space address was
specified.
 
 
EINVAL 
 
This error message is displayed if a nonexistent control command
was requested or invalid parameters were supplied.
 
 
EINTR 
 
This error message is displayed if a thread awaiting a component state change 
is interrupted.
 
 
ENXIO 
 
This error message is displayed if the driver is not installed in
the system.
 
 
 
Knowing Unsupported Features and Limitations
--------------------------------------------
 
 
1) In the case of the watchdog timer expiration detected by the SC, the recovery 
is attempted only once; there are no further attempts of recovery if the first 
attempt fails to recover the domain.
 
 
2) When you break into the OpenBoot(TM) PROM (OBP) when the application watchdog 
is enabled, the watchdog timer is disabled automatically by the SC. However, 
when you reenter the Solaris Operating System, the watchdog timer is NOT enabled 
automatically by the SC. You must re-enable the watchdog timer to turn it on.
 
--------------------------------------------------------------------------------
NOTE: A warning message appears on the console to inform you that the watchdog 
timer remains disabled when you return to the Solaris OS.
--------------------------------------------------------------------------------
 
 
3) If you perform a dynamic reconfiguration (DR) operation in which a system 
board containing kernel (permanent) memory is deleted, then you must 
disable the watchdog timer's application mode before the DR operation and 
enable it after the DR operation.  This is required because Solaris software 
quiesces all system IO and disables all interrupts during a memory-delete of
permanent memory. As a result, system controller firmware and Solaris software 
can not communicate during the DR operation. Note that this limitation affects 
neither the dynamic addition of memory nor the deletion of a board not 
containing permanent memory. In those cases, the watchdog timer's application 
mode can run concurrently with the DR implementation.
 
You can execute the following command to locate the system boards that contain 
kernel (permanent) memory:
 
sh&gt; cfgadm -lav | grep -i permanent
 
 
4) If the Solaris Operating System hangs under the following conditions, the 
system controller firmware cannot detect the Solaris software hang:
 
o Watchdog timer's application mode is set 
o Watchdog timer is not enabled 
o No rearming is done by the user
 
 
5) The watchdog timer provides partial boot monitoring. You can use the 
application watchdog to monitor a domain reboot.
 
However, domain booting is not monitored for:
 
o Bootup after a cold powerup
o Recovery of a hung or failed domain
 
In the latter cases, a boot failure is not detected and no recovery attempts are 
made.
 
 
6) The watchdog timer's application mode provides no monitoring for application 
startup. In application mode, if the application fails to start up, the failure is 
not detected and no recovery is provided. 
 
 
--------------------------------------------------------------------------------
 
Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
 
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 related documentation 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,
if any, is copyrighted and licensed from Sun suppliers.
 
Sun, Sun Microsystems, Solaris, the Sun Logo, Sun Fire, and SPARC 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.
 
Federal Acquisitions: Commercial Software - Government users subject to
standard license terms and conditions.
 
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.
 
--------------------------------------------------------------------------------
 
Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
 
Ce produit ou document est prot\351g\351 par un copyright et distribu\351 avec
des licences qui en restreignent l'utilisation, la copie, la distribution,
et la d\351compilation.  Aucune partie de ce produit ou document ne peut \352tre
reproduite sous aucune forme, par quelque moyen
que ce soit, sans l'autorisation pr\351alable et \351crite de Sun et de ses
bailleurs de licence, s'il y en a.  Le logiciel d\351tenu par des tiers,
et qui comprend la technologie relative aux polices de caract\350res, est
prot\351g\351 par un copyright et licenci\351 par des fournisseurs de Sun.
 
Sun, Sun Microsystems, Solaris, le Sun logo, Sun Fire, et SPARC sont des
marques de fabrique ou des marques d\351pos\351es de Sun Microsystems, Inc. aux
Etats-Unis et dans d'autres pays. Toutes les marques SPARC sont utilis\351es
sous licence et sont des marques de fabrique ou des marques d\351pos\351es de
SPARC International, Inc. aux Etats-Unis et dans d'autres pays.  Les
produits portant les marques SPARC sont bas\351s sur une architecture
d\351velopp\351e par Sun Microsystems, Inc.
 
LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
D\311CLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES
DANS LA MESURE AUTORIS\311E PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE
GARANTIE IMPLICITE RELATIVE \300 LA QUALIT\311 MARCHANDE, \300 L'APTITUDE \300 U
NE UTILISATION PARTICULI\310RE OU \300 L'ABSENCE DE CONTREFA\307ON.

Special Install Instructions:
-------------------------------------------
None.

README -- Last modified date:  Wednesday, August 31, 2005

</pre></body></html>