Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

System Controller Enhancements

When the system encounters a fatal hardware error that causes a domain to be error paused, the hardware fault is automatically diagnosed. The result of auto diagnosis (AD) is persistently stored in the component health status (CHS). During the auto restoration phase, POST consults the CHS and restores the domain with the fault isolated.

In addition to the preceding, if POST encounters a test failure, it diagnoses the faulty component and marks its CHS appropriately.

The SC has been enhanced to detect domain hangs and recover from such situations by resetting and rebooting the domain. Another SC enhancement is to run POST at increasing diagnostic levels when the domain panics repeatedly so that the system can identify and isolate any persistent hardware faults.

Auto Diagnosis

The SC monitors the domains for hardware faults. AD is automatically invoked on hardware faults, which cause a domain pause or data parity errors. On Sun Fire 6800/4810/4800/3800 systems the data path is protected by parity and ECC. Domain operation is not impacted if data parity errors occur. Domain pauses are fatal errors and stop domain operation. AD analyzes the following errors:

  • Interconnect port errors

  • Interconnect errors

  • Data parity errors

  • Internal ASIC errors

FIGURE 1 shows the AD phase, Steps 1 through 5. Depending on the fault, three types of diagnosis results are possible:

  • Fault diagnosed to a single component

  • Fault diagnosed to a set of components

  • Unresolved fault diagnosis

Note that when a fault is diagnosed to a set of components, it does not mean that all the components are faulty, just that the fault is located in a subset of these components (usually one).

Figure 1FIGURE 1 Auto Diagnosis Process

Auto Diagnosis Recording and Reporting

After the fault has been diagnosed, AD records its diagnosis persistently in the CHS and reports it to the console and loghost as shown in FIGURE 2.

Figure 02FIGURE 2 Auto Diagnosis Recording and Reporting

TABLE 1 TABLE 2, "Example 1," shows the AD result that is output to the domain console for a single FRU diagnosis.

TABLE 2 Example 1

[AD] Event: SF3800.ASIC.SDC.PAR_SGL_ERR.60111010

CSN: 124H58EE DomainID: A ADInfo: 1.SCAPP.15.0

Time: Thu Jan 23 20:47:11 PST 2003

FRU-List-Count: 1;FRU-PN:5014362;FRU-SN: 011600; FRU-LOC:/N0/SB0

Recommended-Action: Service action required

AD reports a unique event code for the failure type and the diagnostic time. A full description of the AD output format is in the Sun Fire 6800/4810/4800/ 3800 Systems Platform Administration Manual. In this example AD determined that the error is within CPU/Memory board at FRU-LOC:N0/SB0

The reported information enables your service provider to make a quick determination of the problem and initiate corrective service action.

CHS on a Sun Fire 6800/4810/4800/3800 is implemented for the following FRUs and components:

  • CPU/Memory boards

  • CPUs

  • L2_SRAM modules

  • DIMMs

  • I/O boards

  • Fireplane switches

Since the CHS and diagnostic information is persistently stored on a component, it moves with the component, which prevents the recurrence of a fault even if the component is moved to a different location. Preventing the recurrence of a fault improves the availability characteristic of Sun Fire 6800/4810/4800/3800 systems. The diagnosis information is contained inside the component. This makes service and repair of these systems easier.

Auto Restoration

POST performs the domain auto restoration function. POST runs automatically after Auto Diagnosis or is manually started by issuing the setkey command on the SC. POST consults the CHS of the domain hardware and tries to reconfigure the domain to isolate the fault (FIGURE 3).

Figure 3FIGURE 3 Auto Restoration

After the domain has been restored, you can run the showcomponent command to check which components have been disabled due to CHS.

If a FRU or component is disabled because of its CHS, immediate replacement is not necessary because the domain is restored with the fault isolated. Utilizing dynamic reconfiguration (DR), the FRU can be replaced at any given time with minimal impact to the Solaris OE and user applications. For more information about DR, see the Sun BluePrints OnLine article Sun Fire™ 3800-6800 Servers Dynamic Reconfiguration.

Domain Hang Recovery

This section describes the domain hang detection and automatic domain hang recovery. Available parameters and hang messages are discussed.

A situation in which a domain is not updating its heartbeats or is unreachable by using the console is categorized as domain hang. In this situation, the domain is typically providing no service to its users. There are various reasons why a domain could be hung.

On a Sun Fire 6800/4810/4800/3800 system, the SC acts as an external monitor for each domain. The SC automatically checks for a domain hang condition (FIGURE 4).

Figure 4FIGURE 4 Domain Hang Restoration

The SC initiates an XIR domain reset if the domain heartbeat register is not updated within a maximum timeout limit. The default timeout value is three minutes. This default can be overridden by the watchdog_timeout_seconds parameter in the /etc/systems file of each domain. For additional details, refer to the system(4) man page. If watchdog_timeout_seconds is set to a value below three minutes, the SC defaults to three minutes. TABLE 2, "Example 2," shows the console output of a domain which was declared hung and reset by the SC.

TABLE 2 Example 2

Jan 22 17:02:06 sc0 Domain-A.SC: Domain watchdog timer expired.

Jan 22 17:02:06 sc0 Domain-A.SC: Using default hang-policy (RESET).

In addition to the heartbeat monitoring, the SC also checks if the domain is picking up the interrupts sent to it by the SC. The SC sends interrupts to the domain when, for example, characters are entered on the domain console. If on a second interrupt, the previous one has not been picked up by the domain, the SC waits for one minute before declaring the domain hung. TABLE 3, "Example 3," shows the console output of a domain that is hung because it has not been picking up its interrupts.

TABLE 3 Example 3

Jan 22 18:09:02 sc0 Domain-A.SC: Domain is not responding to interrupts.

Jan 22 18:09:02 sc0 Domain-A.SC: hang-policy is NOTIFY. Not resetting domain.

The hang-policy is set by the setupdomain command, to notify or reset. If set to notify, the SC reports the hang condition on the domain console and does not reset the domains (code example 3). If set to reset, the SC reports the hang condition on the domain console, and initiates a domain reset (code example 2). By default the hang-policy is set to reset. For more information about domain setup, refer to Sun Fire™ 6800/4810/4800/3800 Systems Platform Administration Manual.

By default, the domain is set up to dump core when it is reset. To identify the cause of the domain hang, consult your service provider while referring to the core file.

Hang conditions are automatically detected and the necessary steps are initiated. Hence the availability of Sun Fire 6800/4810/4800/3800 systems is enhanced.

Recovery From Repeated Domain Panics

Domain panics can be caused by software and by hardware. To prevent hardware faults from causing panic-reboot loops, the SC firmware has been enhanced to run POST diagnostics at increasing diagnostic levels on recurring panics.

On the first panic, the domain reboots and writes a core file, which can be used to analyze the problem. However, if further panics occur within a short time period, it is desirable to run POST automatically at a higher level as part of domain restoration. POST diagnostics verify the status of the hardware and could identify and isolate faulty components (if any). After identifying faulty components, POST updates the appropriate CHSs. With firmware release 5.14.0 and higher, the SC keeps track of the number of domain panics over time. A panic reboot of a domain has a unique register signature that differs from the normal reboot of a domain. If the domain is manually rebooted in the meantime the panic-reboot counter is reset.

On recurring panics, the domain POST diagnostic level is increased to the next higher level from diag-level quick. In increasing order, POST levels are init, quick, default, mem1, and mem2. The domain is put into standby position if it continues to panic undetected by the user after the highest level of POST is run (FIGURE 5). For further analysis, consult your service provider while referring to the core file.

Figure 5FIGURE 5 Domain Panic Restoration

This feature prevents a panic reboot loop of domains. If recurring panics are caused by a software bug, the increased POST level minimizes hardware as a possible cause. Downtime for running further POST diagnostics is not required because the system automatically takes the necessary measures.Hence the availability and serviceability of Sun Fire 6800/4810/4800/3800 system is enhanced.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020