Home > Articles > Operating Systems, Server > Solaris

Like this article? We recommend

Backing Up, Restoring, and Updating the SC

This section provides information and recommendations for securely backing up and restoring the SC. In this section, the MSP is used as the dumpconfig, restoreconfig and flashupdate server.

Backing Up and Restoring Configurations

The dumpconfig command uses the FTP protocol to save the current platform and domain configurations to the MSP server. The restoreconfig command uses either the FTP or HTTP protocol to restore a previously saved configuration to the SC from the MSP server.

For complete descriptions and usage of the dumpconfig and restoreconfig commands, refer to the Sun Fire 6800/4810/4800/3800 Platform Administration Manual and the Sun Fire 6800/4810/4800/3800 System Controller Command Reference Manual.

All stored platform and domain configuration information is included in the dump file. This information includes the MD5 hash of the platform and domain administrator passwords, the OBP password, and the SNMP community strings.

The dump file is not encrypted. Hence the MD5 hash of the platform and domain administrator passwords and the non-encrypted OBP password and SNMP community strings are transmitted in clear text during the dumpconfig operation. For this reason, the dump files are saved on the MSP, thus ensuring that the insecure transmission of information is restricted to the private SC network, thus minimizing exposure to network snooping.

When a restoreconfig operation is carried out, the entire saved configuration is restored. This includes the platform administrator and domain administrator passwords. It is essential to ensure that the passwords are known before this operation is carried out. Refer to "Configuring Platform Administrator Settings" on page 14 and "Configuring Domain Administrator Settings" on page 25.

The Apache Web Server on the MSP is configured such that the /msp directory is made available to the SC. All backup and restore operations to the MSP must be contained in this directory. Because the backup files created during a dumpconfig are not differentiated by name or date, it is important that separate directories be created for each backup for version control and tracking. The recommended solution is to create a directory for each dumpconfig using the year, month, day, and hour. For example: the dumpconfig performed on July 16th, 2001 at 7 p.m. would be stored in a directory called 2001071619.

Backing Up Platform and Domain Configurations

Although the MSP is configured to respond to HTTP, it does not normally respond to FTP because the FTP service is disabled during MSP setup. To perform a dumpconfig, the FTP service needs to be enabled on the MSP.

After saving configurations, disable the FTP service again on the MSP. The MSP is configured such that a user ID and password are required for this operation, and the user ID should be used only for dumpconfig and restoreconfig operations.

To Back Up Configurations on the MSP

  1. To enable the FTP service on the MSP, log in to the MSP using Secure Shell, then su to root.

  2. Edit the file /etc/inetd.conf, and uncomment the following FTP entry:

    #ftp stream tcp6  nowait root /usr/sbin/in.ftpd in.ftpd -l
  3. Send the inetd daemon a SIGHUP signal with the following commands:

    # ps -ef | grep inetd
      root  221   1 0  Jun 08 ? 0:00 /usr/sbin/inetd -s -t
    # kill -HUP 221
  4. Create a directory with the appropriate time and date stamp on the MSP.

    Before the actual dumpconfig command can be run, a directory on the MSP must be created with the appropriate time and date stamp. Based on the example (July 16th, 2001 at 7 p.m. would be stored in a directory called 2001071619), the following directory would be created:

    # mkdir /msp/2001071619
    # chown msphttp:mspstaff /msp/2001071619
    # chmod 770 /msp/2001071619
  5. At the SC, dump the configuration using FTP with a user name and password.


    The following example assumes a user name "blueprints" and password "t00lk1t" on the MSP.

    The command and results should be similar to the following:

    ds7-sc0:SC> dumpconfig -f ftp://blueprints:t00lk1t@
    Created: ftp://blueprints:t00lk1t@
    Created: ftp://blueprints:t00lk1t@

  6. When the dump is complete, conclude the process by disabling the FTP entry in the /etc/inetd.conf by commenting out the following line in the /etc/inetd.conf:

    ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.ftpd -l
  7. Send the inetd daemon a SIGHUP signal in the following manner:

    # ps -ef | grep inetd
      root 221 1 0  Jun 08 ?  0:00 /usr/sbin/inetd -s -t
    # kill -HUP 221
  8. Confirm that the FTP service is disabled by executing the following commands:

    # ftp localhost
    ftp: connect: Connection refused
    ftp> quit

Restoring Platform and Domain Configurations

When it is necessary to restore configuration settings, first ensure that at least the platform administration password contained in the chosen dump file is known by the platform administrators. With the release of 5.13, it is possible for a platform administrator to reset the domain passwords without knowing the old ones. Ideally, of course, both the domain and platform passwords contained in the dump file should be known.

To avoid the necessity of enabling the FTP service on the MSP for this operation, we recommend that you use restoreconfig operation using HTTP. As with the dumpconfig operation, a user ID and password are required for this operation, and the user ID should only be used for dumpconfig and restoreconfig operations.

Restoring configuration settings using HTTP is documented in Sun Fire 6800/4810/4800/3800 Platform Administration Manual and the Sun Fire 6800/4810/4800/3800 System Controller Command Reference Manual. The only considerations are ensuring that the appropriate backup directory is available through the web server and that the passwords used for the domain and platform administrators, in the configuration being restored, are known.

Updating the SC

The flashupdate feature updates the firmware running on the SC, the CPU/Memory boards, and the I/O assemblies. The update is initiated by using the flashupdate command on the SC. The source flash image can be on a server or another board of the same type. This section describes updates executed from an image on a server. The MSP is used as the server for flashupdate images.

To avoid the necessity of enabling FTP on the MSP for this operation, we recommend that you carry out the flashupdate operation using HTTP.

The MSP is configured such that a user ID and password are required for this operation, and the user ID should only be used for flashupdate operations.


It is important to be sure of the authenticity and integrity of the flash images before they are loaded from the server using the flashupdate command. Loading a corrupted or malicious image can cause damage to hardware, and may compromise security.

It is recommended that the RTOS be updated whenever SCapp is updated. When a new firmware is released, SCapp is normally only tested with the RTOS included with the firmware update. If an RTOS flash fails, then a service call to Sun is required to replace or repair the SC. In order to establish whether a RTOS flash is necessary, refer to the product release notes accompanying the image and the flashupdate command documentation in the Sun Fire 6800/4810/4800/3800 Platform Administration Manual.

To Update the SC

  1. Download the latest flashupdate for the SC from the Product Patches section of the SUNSOLVE ONLINE Web site at:


  2. Make a note of the checksum listed for the patch in the Patch Checksums section of the SUNSOLVE ONLINE Web site, similar to the following:

       MD5: 5e84f09ebf5743eb5426b5be6c6a777f
       SysV Sum: 7075  13729
       Sum: 43381  13729
  3. Confirm that the checksum of the file matches the checksum listed on the SUNSOLVE ONLINE Web site, using the following commands:
    # sum 111346-02.zip
    7075 13729 111346-02.zip
    # sum -r 111346-02.zip
    43381 13729 111346-02.zip

    A more robust file integrity check is to use the MD5 hash value listed for the patch. For more information about downloading and using MD5 hashes to verify patch integrity, refer to the Sun BluePrints OnLine article titled The Solaris™ Fingerprint Database - A Security Tool for Solaris Software and Files.

  4. Unpack the files containing the patch and place them in a subdirectory under the Apache Web Server document root directory /msp as follows:

    # cd /msp
    # unzip 111346-02.zip
    Archive: 111346-02.zip
      creating: 111346-02/
     inflating: 111346-02/Install.info 
     inflating: 111346-02/VERSION.INFO 
     inflating: 111346-02/copyright   
     inflating: 111346-02/sgcpu.flash  
     inflating: 111346-02/sgpci.flash  
     inflating: 111346-02/sgrtos.flash 
     inflating: 111346-02/sgsc.flash  
     inflating: 111346-02/README.111346-02
  5. Follow the instructions in the Install.info file.

    In our example, sc-app, SB0, SB2, IB7, and IB9 are to be updated from version 5.11.6 to 5.11.7. The RTOS will be updated from release 17 to 17B. Not all system boards are powered up, so the all option cannot be used.

    The following example downloads and installs the flashupdate file from the MSP:

    ds7-sc0:SC> flashupdate -f http://blueprints:t00lk1t@ SB0 SB2 IB7 IB9 scapp rtos

    The RTOS flash image will be upgraded automatically during the next boot. The ScApp flash image will be upgraded automatically during the next boot. After this update you must reboot each active domain that you have upgraded. After this update, the system controller will automatically reboot itself. Do you want to continue? [no] y

    Retrieving: http://blueprints:t00lk1t@
    Validating ............ Done
    Programming PROM 0 on /N0/SB0
    Erasing   ............ Done
    Programming ............ Done
    Verifying  ............ Done
    Programming PROM 1 on /N0/SB0
    Erasing   ............ Done
    Programming ............ Done
    Verifying  ............ Done
    Programming PROM 0 on /N0/SB2
    Erasing   ............ Done
    Programming ............ Done
    Verifying  ............ Done
    Programming PROM 1 on /N0/SB2
    Erasing   ............ Done
    Programming ............ Done
    Verifying  ............ Done
    Retrieving: http://blueprints:t00lk1t@
    Validating .... Done
    Programming PROM 0 on /N0/IB7
    Erasing   .... Done
    Programming .... Done
    Verifying  .... Done
    Programming PROM 0 on /N0/IB9
    Erasing   .... Done
    Programming .... Done
    Verifying  .... Done
    Rebooting the SC to automatically update flash image.

    The SC reboots, and the flashupdate proceeds as follows:

    Copyright 2001 Sun Microsystems, Inc. All rights reserved.
    RTOS version: 17
    ScApp version: 5.11.6
    SC POST diag level: off
    Auto Flashupdate
    Retrieving: http://blueprints:t00lk1t@
    Retrieving: http://blueprints:t00lk1t@
    Validating .................................................... Done
    Updating: RTOS
    Erasing   ........... Done
    Programming ........... Done
    Verifying  ........... Done
    Updating: ScApp from version 5.11.6 to version 5.11.7
    Erasing   .................................................... Done
    Programming .................................................... Done
    Verifying  .................................................... Done
    Flashupdate completed successfully.
    The SC is being rebooted to use the new images.

    The SC then reboots with the new image.

  6. Halt the Solaris OE image running in each domain gracefully by using the shutdown command.

    You must perform this step before issuing the setkeyswitch off command.

  7. For each domain affected by the updates, set the keyswitch to the off position by issuing the setkeyswitch off command from the domain shell.

    In the following example, domain-a is affected:

    ds7-sc0:A> setkeyswitch off
    This will abruptly terminate Solaris in domain A.
    Do you want to continue? [no] y
  8. Set the domain keyswitch to the on position using the following setkeyswitch on command:

    ds7-sc0:A> setkeyswitch on

The flashupdate operation is now complete. At this point, the domain boots itself either to the OBP prompt or Solaris OE. In either case, the flashupdate operation is now complete.

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