Home > Articles > Operating Systems, Server > Solaris

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

Platform and Domain Administration

The SC has a administration scheme in which operations affecting the entire system are administered through a platform shell and operations affecting separate domains are administered through a domain shell.

This section contains general descriptions of administering the SC and detailed descriptions of the following topics:

  • "Monitoring Through the Serial Port, syslog, and SNMP"

  • "Setting Up Information Recording and Logging"

You can access multiple platform shells simultaneously. The platform shell can view the status of any component within the system and can also control its allocation. One example of how the platform shell is used to manage the entire system is through access control lists (ACLs). You can set up ACLs by using the setupplatform -p acl command. You can also use the ACLs to restrict domain access to resources.

While the platform shell manages and administers overall system resources, domain specific operations, such as the turning of the virtual keyswitch, are controlled by the domain shell. The domain shell can only access resources specified in the ACL set up for it by the platform shell, and only one shell per domain can be active at any time. The ACL restricts the domain shell so that it views only the resources that the domain is currently using, resources that are allocated to the domain, or any resources that are unassigned on the platform and are available to the domain according to the ACL.

One advantage to this setup is that you can restrict the access to the platform shell (and administration of the overall system resources) to a group of administrators, who are separate from a group of administrators for the domains. You can control access to platform and domain shells by using passwords that you can set and change by using the password command on the SC. From the platform shell, you can set or change the platform and domain shell passwords. From a domain shell, you can change only the password of the particular domain. Because the platform has additional privileges, its password should be different from those selected for the domains.

Monitoring Through the Serial Port, syslog, and SNMP

Administration of a Sun Fire server is designed to be performed primarily through the SC, which can be accessed in two ways: RS-232 serial port and 10/100BASE-T Ethernet. Both ports should remain available at all times, and you should monitor the platform console and all of the domain consoles.

After the initial platform setup, the serial port performs an important role in the administration of the Sun Fire server. The system in the event of a network outage and the location where the system outputs platform and SC error messages to the serial port. While output is buffered (up to 4 kilobytes) and can be directed to a syslog host if a network is configured, you should continuously monitor the serial port output either with a logging terminal server or by connecting the serial port to an MSP, which can capture the terminal output with a mechanism such as script(1) in the Solaris? Operating Environment (Solaris OE). This mechanism provides additional error detection and information in the event of a failure. Finally, network connectivity to the SC will be lost during firmware updates because the SC is rebooted. Thus, serial port access is critical to monitor the progress of the update procedure and for diagnostics, should a problem arise.

For routine tasks, the preferred method of accessing the SC is the Ethernet interface. In addition to providing multiple high-speed shell connections, the Ethernet interface on the SC enables you to set up syslog(3) and SNMP messages to be sent to a designated administration platform. The Ethernet interface is required for performing firmware updates on the system and for saving and restoring the SC configuration information. You should enable and configure both syslog and SNMP facilities; however, you should record system consoles by using a mechanism such as script(1M) because not all of the messages can be logged with syslog or SNMP.

Note

SNMP should not be enabled unless a Sun MC server has been configured to support the system.

Setting Up Information Recording and Logging

You should perform the setup of information recording and logging during the initial platform setup. Although you can also make these changes at other times, you should set up syslog(3) to record the information to a central location so that information can be quickly located in the event of a problem and to prevent the SC message buffer from being overwritten.

Because the SC message buffer is in volatile memory, messages can be lost if the SC loses power. The SC maintains a 4 kilobyte ring buffer for messages from each domain and the platform. It also maintains an additional buffer to record particular failure messages for retrieval by authorized service personnel.

When setting up the platform or domain using the setupplatform or setupdomain, respectively, you are prompted for a syslog(3) log host. You can supply a syslog(3) log host by using an IP address or hostname, as well as a facility level.

Note

For older firmware, you will not see the Log Facility prompt, as shown in the following example of how to set up log host. The syntax for the log hostname is hostname:facility (for example, mysysloghost:local0).

The following shows an example of how to set up the log host.

heslab-16-sc0:SC> setupplatform -p loghost

Loghosts
--------
Loghost [10.1.63.251]: loghost_name
Log Facility [local0]:

heslab-16-sc0:SC>

heslab-16-sc0:B> setupdomain -p loghost

Loghosts
--------
Loghost [ ]: loghost_name
Log Facility [local0]: local1

heslab-16-sc0:B>

Corresponding changes need to be made to the /etc/syslog.conf file on the syslog(3) host or on the MSP. You can find further information on the configuration of syslog(3)) in the Solaris OE system administration guides in the Solaris OE System Administrator AnswerBook2? collection.

Based on the number of systems and syslog(3) devices that a single syslog(3) host will be monitoring, you should establish a convention to maximize use of the limited number of syslog(3) facilities. There are only eight syslog(3) facilities available for users in the Solaris OE, so it is likely that an administrator will quickly run out of unique syslog(3) facilities. Organization of message logging is important to enable administrators to quickly find the desired information. A good way to organize syslog(3) logging is to assign the local0 facility to all platform messages and then assign local1-4 to domains A through D, respectively. The syslog(3) facility in the Solaris 8 OE identifies each syslog(3) entry with the originating hostname and syslog(3) facility. This identification makes it easy to quickly separate messages coming from different hosts.

When setting up the platform, you can configure the SC to interface with the latest versions of the Sun MC software through SNMP. This improves the monitoring and administration capabilities of the platform. It is strongly recommended that the default community strings be changed during installation for security reasons. The following values for platform and domain public and private community strings are set by default.

Platform Public:  P-public
Platform Private: P-private

Domain A Public:  A-public
Domain A Private: A-private

Domain B Public:  B-public
Domain B Private: B-private

Domain C Public:  C-public
Domain C Private: C-private

Domain D Public:  D-public
Domain D Private: D-private

SNMP must be enabled on the platform by using the setupplatform command before SNMP can be enabled on any of the domains. The following shows an example of the setupplatform command.

heslab-16:SC> setupplatform -p snmp

SNMP
----
Platform Description [Sun Fire 3800]:
Platform Contact [email_address]:
Platform Location [Lab]:
Enable SNMP Agent? [no]: yes
Trap Hosts [ ]: 10.1.221.11
Public Community String []: P-public
Private Community String []: P-private

For more information on how to set up SNMP, refer to the security articles by Alex Noordergraaf at the Sun BluePrints Online website at:

http://www.sun.com/blueprints/

The following shows an example of the setupdomain command.

heslab-16:A> setupdomain -p snmp

SNMP
----
Domain Description [test]:
Domain Contact [email_address]:
Trap Hosts [ ]: 10.1.221.11
Public Community String [ ]: A-public
Private Community String [ ]: A-private

heslab-16:A>

The port for the Trap Hosts value can be entered in the form of hostname:port in firmware 5.13.0, or higher. Do not change the port setting unless specifically instructed to do so for the installation of other software on the trap host. To find additional information on configuring the Sun MC software, refer to the Sun MC software documentation at the following site:

http://docs.sun.com

In addition to setting up syslog(3) and SNMP, you should monitor domain console sessions in a manner similar to that described for the platform and the serial port connection. While the SC has a buffer for each domain shell's messages, the SC will not send domain console messages or error messages generated by the Solaris OE (such as panic strings) to an external log host. Therefore, if you do not constantly monitor the domain consoles, critical messages and valuable diagnostic information could be lost in the event of a failure. With multiple domains to monitor, you should access the domain shells through the Ethernet port because it allows multiple connections.

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