Home > Articles > Operating Systems, Server > Solaris

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

Default SC SMS Software Configuration

This section discusses the additional software which must be installed on a Sun Fire 15K SC. Specifically, this section covers the configuration of System Management Services (SMS) software.

SC Solaris OE SMS Packages

A Sun Fire 15K SC is based on Solaris 8 OE 10/01 (update 6) using the SUNWCall Solaris OE installation cluster.

The System Management Services (SMS) software, which is required on an SC, is critical for configuring the SC. It resides on the SC and oversees all SC operations. The entire SMS software bundle is comprised of the following fifteen packages:

application SUNWSMSdf   System Management Services Data Files
application SUNWSMSjh   System Management Services On-Line Javahelp
application SUNWSMSlp   System Management Services LPOST object files
application SUNWSMSmn   System Management Services On-Line Manual Pages
application SUNWSMSob   System Management Services OpenBoot PROM
application SUNWSMSod   System Controller Open Boot Prom
application SUNWSMSop   System Management Services Core Utilities
application SUNWSMSpd   System Controller Power On Self Test
application SUNWSMSpo   System Management Services POST Utilities
application SUNWSMSpp   System Management Services picld(1M) Plug-in Module
application SUNWSMSr    System Management Services, (Root)
application SUNWSMSsu   System Management Services User Environment
application SUNWufu    User Flash PROM Device Driver Header File
application SUNWufrx    User Flash PROM Device Driver (Root) (64-bit)
application SUNWscdvr   Sun Fire 15000 System Controller drivers

The preceding packages are specific to Sun Fire 15K SCs.

SC SMS Accounts and Security

The following are users added to the /etc/passwd file by SMS:

# grep sms /etc/passwd
sms-codd:x:10:2:SMS Capacity On Demand Daemon::
sms-dca:x:11:2:SMS Domain Configuration Agent::
sms-dsmd:x:12:2:SMS Domain Status Monitoring Daemon::
sms-dxs:x:13:2:SMS Domain Server::
sms-efe:x:14:2:SMS Event Front-End Daemon::
sms-esmd:x:15:2:SMS Environ. Status Monitoring Daemon::
sms-fomd:x:16:2:SMS Failover Management Daemon::
sms-frad:x:17:2:SMS FRU Access Daemon::
sms-osd:x:18:2:SMS OBP Service Daemon::
sms-pcd:x:19:2:SMS Platform Config. Database Daemon::
sms-tmd:x:20:2:SMS Task Management Daemon::
sms-svc:x:6:10:SMS Service User:/export/home/sms-svc:/bin/csh

Of the twelve preceding accounts, only one is actually used to administer the system. The sms-svc account is the default account for the administration of the Sun Fire 15K system. All of the other accounts provide privileges for the daemons they are associated with. These accounts should never be used to log into the system and can be secured in the same fashion as system accounts which are never used. These accounts are used for the daemons running the SC as described in the SC SMS Daemons section.

The following are the newly added SMS specific /etc/shadow contents:

# grep sms /etc/shadow 
sms-codd:NP:::::::
sms-dca:NP:::::::
sms-dsmd:NP:::::::
sms-dxs:NP:::::::
sms-efe:NP:::::::
sms-esmd:NP:::::::
sms-fomd:NP:::::::
sms-frad:NP:::::::
sms-osd:NP:::::::
sms-pcd:NP:::::::
sms-tmd:NP:::::::
sms-svc:lnrf21Ovf4G9s:11414::::::

All of the preceding accounts added, including the sms-svc account, are initially locked by having 'NP' as the encrypted password entry.

NOTE

The password for the sms-svc user should be set, on both SCs, immediately after installation of the SMS software or first power on of the Sun Fire 15K system.

The following are entries added to the /etc/group file by SMS:

# grep sms /etc/group
platadmn::15:sms-svc
platoper::16:sms-svc
platsvc ::17:sms-svc
dmnaadmn::18:sms-svc
dmnarcfg::19:sms-svc
dmnbadmn::20:sms-svc
dmnbrcfg::21:sms-svc
dmncadmn::22:sms-svc
dmncrcfg::23:sms-svc
dmndadmn::24:sms-svc
dmndrcfg::25:sms-svc
dmneadmn::26:sms-svc
dmnercfg::27:sms-svc
dmnfadmn::28:sms-svc
dmnfrcfg::29:sms-svc
dmngadmn::30:sms-svc
dmngrcfg::31:sms-svc
dmnhadmn::32:sms-svc
dmnhrcfg::33:sms-svc
dmniadmn::34:sms-svc
dmnircfg::35:sms-svc
dmnjadmn::36:sms-svc
dmnjrcfg::37:sms-svc
dmnkadmn::38:sms-svc
dmnkrcfg::39:sms-svc
dmnladmn::40:sms-svc
dmnlrcfg::41:sms-svc
dmnmadmn::42:sms-svc
dmnmrcfg::43:sms-svc
dmnnadmn::44:sms-svc
dmnnrcfg::45:sms-svc
dmnoadmn::46:sms-svc
dmnorcfg::47:sms-svc
dmnpadmn::48:sms-svc
dmnprcfg::49:sms-svc
dmnqadmn::50:sms-svc
dmnqrcfg::51:sms-svc
dmnradmn::52:sms-svc
dmnrrcfg::53:sms-svc

At first glance the preceding entries seem to be a tremendous number of group additions, but they are simply the groundwork to allow delegation of administrative capabilities for the frame, and each of the 18 domains a Sun Fire 15K system is capable of supporting. This allows for separation of the administrative privileges and operator privileges for each domain and the entire frame. The SMS Security chapter in the System Management Services (SMS) 1.1 Administrator Guide referenced in the Bibliography has detailed descriptions of which commands require which group's privileges for execution.

SC SMS Daemons

The SMS-specific daemons can be broken up into three separate types. These three types are each listed below with sample ps output.

First, there are the platform or core SMS daemons which run on both the main and spare SC:

root   8108  1 0 17:53:04 ?    0:01 mld
root   8123  1 0 17:53:05 ?    31:35 hwad
root   8126  1 0 17:53:05 ?    0:00 mand
sms-frad 331  1 0 12:41:21 ?    0:00 frad
root   8132  1 0 17:53:06 ?    0:03 fomd

Secondly, there are the SMS daemons that only run on the main SC:

sms-pcd  393   1 0 12:41:43 ?    0:03 pcd
sms-tmd  402   1 0 12:41:43 ?    0:00 tmd
sms-dsmd 405   1 0 12:41:44 ?    0:00 dsmd
sms-esmd 414   1 0 12:41:45 ?    0:05 esmd
sms-osd  419   1 0 12:41:46 ?    0:00 osd
root   8218  1 0 17:53:33 ?    0:00 kmd
sms-efe  475   1 0 12:41:47 ?    0:00 efe
sms-codd 483   1 0 12:41:48 ?    0:00 codd

Lastly, there are the SMS daemons which communicate to the domains:

sms-dxs 4428  291 0 13:14:31 ?    0:00 dxs -d A
sms-dca 4429  291 0 13:14:31 ?    0:00 dca -d A

NOTE

The listing of services above is a sample of the services that may be encountered. Depending on how many domains are in use, more SMS daemons will be running for each of those domains.

These SMS daemons are started by /etc/rc2.d/S99sms based on its startup daemon (ssd) configuration file in /etc/opt/SUNWSMS/SMS1.1/startup/ssd_start.

Each of these SMS daemons is briefly described below:

  • dca (Domain Configuration Administration) – supports remote Dynamic Reconfiguration (DR) by facilitating communication between applications and the dcs daemon running on the domain. A separate instantiation of the dca daemon is executed on the SC for each domain running Solaris OE.

  • dsmd (Domain Status Monitoring Daemon) – monitors domain state, CPU reset conditions, and the Solaris OE heartbeat for up to 18 domains. This daemon notifies the dxs daemon and Sun Management Center software for all changes.

  • dxs (Domain X Server) – provides a variety of software support for a running domain including DR, Hot-Pluggable PCI I/O Assembly (HPCI) support, domain driver requests and events, in addition to virtual console support. One dxs daemon is started on the SC for each running domain.

  • efe (Event Front End) – receives notification of events from various SMS daemons and forwards them on to subscribed clients. With SMS 1.1, the only client that can subscribe is Sun Management Center 3.0 software.

  • esmd (Environmental Status Monitoring Daemon) – provides monitoring of the environment conditions of the Sun Fire 15K system including system cabinet conditions and fan tray and power supply temperatures. One instance of the esmd is run on the main SC.

  • fomd (Failover Management Daemon) – is the center of the SC failover mechanism through its ability to detect faults on remote and local SC, and take appropriate action. One instance of fomd will be run on the main SC. This daemon uses RPC services on the SC and is the reason why rpcbind is not disabled.

  • frad (FRU Access Daemon) – is the field replaceable unit (FRU) access daemon for SMS. It is the mechanism by which access is provided to the SEEPROMs, within the Sun Fire 15K frame, to which the SC has access. The frad is run locally on the main and spare SCs.

  • hwad (Hardware Access Daemon) – implements hardware access for SMS daemons which is used by the daemons to control, access, configure, and monitor hardware. The hwad is run on the main SC.

  • kmd (Key Management Daemon) – is used to manage the secure socket communication between the SC and domains. One instance of kmd is run on the main SC.

  • mand (Management Network Daemon) – supports the Management Network (MAN). The role played by the mand daemon is specified by fomd. Similar to kmd, one instance of mand is executed on the main SC.

  • mld (Message Logging Daemon) – accepts the output of all SMS daemons and processes and logs those messages based on its configuration files. One instance of the mld is executed on the main SC.

  • osd (OpenBoot PROM Support Daemon) – supports the OpeBoot_ PROM process running on a domain through the mailbox that resides on the domain. When the domain OpenBoot PROM writes requests to the mailbox, the osd daemon executes those requests. Only the main SC is responsible for booting domains; correspondingly, one instance of the osd is run on the main SC.

  • pcd (Platform Configuration Database Daemon) – is responsible for managing and controlling access to platform and domain configuration information. As with osd the pcd is only executed on the main SC.

  • tmd (Task Management Daemon) – implements task management services for the SMS software such as scheduling. Currently, this daemon is used by setkeyswitch, and other daemons, to schedule Hardware Power-On Self Test (HPOST) invocations. The main SC is responsible for these types of events, so one instance of tmd is run on the main SC.

Additional information on each of these daemons can be obtained in the SMS Administration and Reference guides listed in the Bibliography.

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