Home > Articles > Operating Systems, Server > Solaris

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

Section 2.3: Configuring the Solaris JumpStart Server

Configure the management server (administrative workstation) to act as the Solaris JumpStart server, for each cluster node.

NOTE

This section is "optional" and should only be performed during a local (manual) installation, when configuring the administrative workstation (clustadm) as a JumpStart server.

Use JumpStart software to maintain consistency and to fully automate the installation of the Solaris Operating Environment (Solaris OE) and additional software packages. The JumpStart software can minimize operator errors that occur during a manual installation process. Combining JumpStart software and Flash archives (for example, flar and flarcreate), enables quick (consistent) disaster/recovery operations.

NOTE

For information about implementing Flash archives (flar and flarcreate), refer to recent publications available from Sun BluePrints, at http://www.sun.com/blueprints/, and the references in Appendix B.

Step 2.3.1—Inserting the Solaris OE CD

For local (manual) installations, insert the Solaris 8 OE CD into the CD-ROM drive of the management server (administrative workstation). (The vold(1M) daemon will automatically mount in the /cdrom directory).

Step 2.3.2—Creating the JumpStart OS Directory

For local (manual) installations, create the JumpStart OS directory by entering the following command in the management server (administrative workstation).

clustadm# mkdir -p /JumpStart/OS/Solaris_2.8_07.01

Key Practice: Where possible, use a directory name that reflects the contents of the directory. For example, the name "/JumpStart/OS/Solaris_2.8_07.01" clearly identifies the release date and version of the operating system.

CAUTION

In the following step, ensure that the directory you create has enough space to hold the contents of the entire operating system CD (approximately 1.3 Gbyte). Use the df -k command to confirm that adequate disk space is available.

Step 2.3.3—Setting up the JumpStart Server

For local (manual) installations, continue setting up the JumpStart server by entering the following command into the administrative workstation (this step takes approximately one hour to complete).

clustadm# cd /cdrom/cdrom0/s0/Solaris_8/Tools 

clustadm# ./setup_install_server /JumpStart/OS/Solaris_2.8_07.01

verifying target directory...
Calculating the required disk space for the Solaris_8 product
Copying the CD image to disk...
Install Server setup complete

Step 2.3.4—Accessing Directories Over a Network With NFS

For local (manual) installations, to ensure the operating system image can be installed on the nodes from a network, edit the /etc/dfs/dfstab file to include the following line, making the directories accessible over a network using NFS.

share -F nfs -o ro,anon=0 /JumpStart

{{Note: Add this line. The anon=0 option allows the 
install clients access as root to the 
specified file system}}

Step 2.3.5—Sharing Directories Without Rebooting

For local (manual) installations, ensure the NFS daemon (nfsd) is running, then share the directories by entering the following command at the administrative workstation.

clustadm# /etc/init.d/nfs.server stop
clustadm# /etc/init.d/nfs.server start
{{Note: This makes the directories available without 
rebooting}}

Step 2.3.6—Validating Directory Sharing

Validate that the directories have been successfully shared by entering the following command at the administrative workstation.

clustadm# share 
-        /JumpStart  ro,anon=0 ""
clustadm#

Step 2.3.7—Creating the sysidcfg File

For local (manual) installations, create the /JumpStart/OS/JumpStart/sysidcfg file and include the following lines: (the system locale and time zone entries should correspond to your JumpStart area and time).

system_locale=en_US #sample
timezone=US/Central #sample
terminal=sun
name_service=NONE
timeserver=JumpStarthost #should be hostname of admin workstation
network_interface=hme0{netmask=255.255.255.0}

Step 2.3.8—Making sysidcfg File Readable

For local (manual) installations, change the permissions of the sysidcfg file to be readable by all by entering the following command at the administrative workstation (management server).

clustadm# chmod 644 /JumpStart/sysidcfg

Step 2.3.9—Configuring the hosts File

To ensure the /etc/inet/hosts file is configured to support the SunPlex platform, add the IP address for each Solaris OE install client (cluster node) to be serviced by the JumpStart server. Also add the additional hostname entries required to support the cluster.

  • At this time, ensure that the corresponding entries are created in support of the SunPlex platform, including entries for each cluster node to be managed, for the clustadm workstation, for the terminal concentrator (tc), and for any additional site-specific entries, such as the two logical host entries (as required for our two data services).

    clustadm# more /etc/inet/hosts
    
    . . . {output omitted}
    
    xxx.xxx.xx.xxx clustadm loghost
    xxx.xxx.xx.xxx clustnode1
    xxx.xxx.xx.xxx clustnode2
    xxx.xxx.xx.xxx lh-hanfs
    xxx.xxx.xx.xxx lh-apache 
    xxx.xxx.xx.xxx tc 
    
    . . . {output omitted}

Step 2.3.10—Copying Sample Files

For local (manual) installations, copy the following files from the /JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Misc/jumpstart_sample directory to the /JumpStart directory.

  • rules

  • check

  • set_root_pw

Verify these files were copied correctly.

NOTE

The set_root_pw file is not needed when using the sysidcfg file.

Step 2.3.11—Enabling Solaris JumpStart Software

For local (manual) installations, enable Solaris JumpStart software for both cluster nodes (clustnode1 and clustnode2) by adding each as Solaris 8 OE install clients. Recall that your Ethernet (MAC) address will be different from the example shown. Ensure that these site-specific entries are correct for your implementation.

Example, adding clustnode1 as a Solaris JumpStart software client.

clustadm# cd /JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Tools

clustadm# ./add_install_client -e 8:0:20:cf:27:62 \
-i 192.9.200.2 \
-s clustadm:/JumpStart/OS/Solaris_2.8_07.01 \
-p clustadm:/JumpStart/sysidcfg
-c clustadm:/JumpStart \
clustnode1 sun4u

Where:

/JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Tools equals the location of the add_install_client utility.

Where:

-e 8:0:20:cf:27:62 equals the Ethernet address should correspond with the data gathered for this node during Module 1.

NOTE

Do not enter the Ethernet address used in these examples. Use the Ethernet address specific to your machine.

-i 192.9.200.2 equals the IP address assignment for clustnode1.

-s clustadm:/JumpStart/OS/Solaris_2.8 07.01 equals the location of the CD-ROM image.

-p clustadm:/JumpStart/sysidcfg equals the location of the sysidcfg file previously verified.

-c clustadm:/JumpStart equals the location of the rules.ok file that was previously verified.

clustnode1 sun4u specifies that clustnode1 is a Sun™ Enterprise 220R server (UltraSPARC® II architecture).

The following example shows how to add clustnode2 as a Solaris JumpStart client.

clustadm# cd /JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Tools

clustadm# ./add_install_client -e 8:0:20:cf:23:a3 \
-i 192.9.200.3 \
-s clustadm:/JumpStart/OS/Solaris_2.8_07.01 \
-p clustadm:/JumpStart/sysidcfg
-c clustadm:/JumpStart \
clustnode2 sun4u

Where:

/JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Tools equals the location of the add_install_client utility.

Where:

-e 8:0:20:cf:23:a3 equals the Ethernet address should correspond with the data gathered for this node, during Module 1.

NOTE

Do not enter the Ethernet address used in these examples. Use the Ethernet address specific to your machine.

-i 192.9.200.3 equals the IP address assignment for clustnode2.

-s clustadm:/JumpStart/OS/Solaris 2.8 07.01 equals the location of the CD-ROM image.

-p clustadm:/JumpStart/sysidcfg equals the location of the sysidcfg file previously verified.

-c clustadm:/JumpStart equals the location of the rules.ok file that was previously verified.

clustnode2 sun4u specifies that clustnode2 is a Sun Enterprise 220R server (UltraSPARC-II architecture).

Step 2.3.12—Verifying Successful Completion

Verify the add_install_client commands completed successfully.

NOTE

In this exercise the nodes to be configured for use with JumpStart software are named clustnode1 and clustnode2.

Confirm that the add_install_client command was executed by viewing the /etc/bootparams, and /etc/ethers files.

clustadm# more /etc/bootparams
clustnode1 root=clustadm:/JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Tools/Boot
 install=clustadm:/JumpStart/OS/Solaris_2.8_07.01/ boottype=:in
sysid_config=clustadm:/JumpStart install_config=clustadm:
JumpStart/sysidcfg rootopts=:rsize=32768

clustnode2 root=clustadm:/JumpStart/OS/Solaris_2.8_07.01/Solaris_8/Tools/Boot
 install=clustadm:/JumpStart/OS/Solaris_2.8_07.01/ boottype=:in
sysid_config=clustadm:/JumpStart install_config=clustadm:/
JumpStart/sysidcfg rootopts=:rsize=32768

clustadm# more /etc/ethers
8:0:20:cf:27:62 clustnode1 {{your ethernet address will differ}}
8:0:20:cf:23:a3 clustnode2 {{your ethernet address will differ}}

NOTE

Refer to the Appendix B references about configuring a JumpStart server. Note, also, that if the add_install_client command fails to add these entries correctly, or an older version of the file(s) had previously existed, it may be necessary to remove a failed entry (for example, from the /etc/bootparams file).

To remove a suspected entry for a specific failing install client, enter the following command.

clustadm# cd /JumpStart/OS/Solaris_2.8_07.01/Solaris_8 
clustadm# ./rm_install_client client_hostname

NOTE

After removing a failing node, re-run the add_install_client commands, as shown in the previous step where this was performed. This may be necessary if, somehow, the previous attempts failed and entries were not correctly removed.

Summary of Key Practices

Where possible, use a directory name that reflects the contents of the directory.

Confirm add_install_client was performed correctly.


End of Section 2.3

This completes this section. The Solaris JumpStart software has been verified, and each cluster node can be quickly (and consistently) installed with the Solaris OE version supported by the cluster.<

  • + 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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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