C H A P T E R 1 |
![]() |
This manual describes initial system configuration of the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 servers. This product line has entry-level (M3000), midrange (M4000 and M5000) and high-end (M8000 and M9000) servers.
Once you have completed the initial configuration processes described here, see the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for day-to-day system administration and management tasks.
This chapter provides an overview of server firmware, server software, and initial system configuration. It has these sections:
Your server provides system management capabilities through eXtended System Control Facility (XSCF) firmware, pre-installed at the factory on the Service Processor[1] boards.
The XSCF firmware consists of system management applications and two user interfaces to configure and control them:
You can access the XSCF firmware by logging in to the XSCF command shell. This document includes instructions for using the XSCF interface as part of the initial system configuration. For more information about the XSCF firmware, see Chapter 2, and the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.
XSCF firmware, OpenBoot PROM firmware, and power-on self-test (POST) firmware are known collectively as the XSCF Control Package (XCP).
XSCF firmware has two networks for internal communication. The Domain to Service Processor Communications Protocol (DSCP) network provides an internal communication link between the Service Processor and the Oracle Solaris domains. The Inter-SCF Network (ISN) provides an internal communication link between the two Service Processors in a high-end server.
On a high-end server with two Service Processors, one Service Processor is configured as active and the other is configured as standby. This redundancy of two Service Processors allows them to exchange system management information and, in case of failover, to change roles. All configuration information on the active Service Processor is available to the standby Service Processor.
The Oracle Solaris OS is pre-installed at the factory on one domain by default. Within its domain, the Oracle Solaris OS includes features to manage Oracle Solaris OS system capabilities.
You can install applications on the domains. That process is managed through the Oracle Solaris OS tools. Likewise, any other software management applications that you prefer to use on the domains must be installed through the Oracle Solaris OS tools.
The DSCP network provides an internal communication link between the Service Processor and the Oracle Solaris domains.
TABLE 1-1 contains an overview of XSCF firmware services and networks that are part of your server, and where they are documented.
Access control includes logging in to the system, user accounts, passwords, privileges, and XSCF firmware control. See Chapter 2. |
|
Initial configuration of the services for the Service Processor and the domains, including DSCP network, XSCF network, DNS name service, LDAP service, NTP service, HTTPS service, Telnet service, SSH service, SNMP service, and SMTP service. See Chapter 3. |
|
Each domain runs its own copy of the Oracle Solaris OS. Domains are managed by the Service Processor XSCF firmware, and communicate with the Service Processor over the DSCP network. You can access a domain console from the Service Processor or, if your system is networked, log in to a domain directly. See Chapter 4. |
|
RAID technology enables the construction of a logical volume made up of several physical disks to provide data redundancy, improved performance, or both. The on-board SAS controller of M3000 servers with SPARC64 VII+ processors supports RAID 1 (mirroring) volumes using the Oracle Solaris OS raidctl utility. See Chapter 5. |
|
The auditing function logs all security-related events. See Chapter 6. |
|
The log archiving function allows you to set up a remote host to automatically receive and store log data from your server. See Chapter 7. |
|
The COD feature allows you to configure spare processing resources on your M4000/M5000 or M8000/M9000 server in the form of one or more COD CPUs which can be activated at a later date when additional processing power is needed. COD is not supported on the M3000 server To access each COD CPU, you must purchase a COD hardware activation permit. Under certain conditions, you can use COD resources before purchasing COD permits for them. See the SPARC Enterprise M4000/M5000/M8000/M9000 Servers Capacity on Demand (COD) User’s Guide. |
|
Security is provided through access control (user names, passwords, privileges), audit logs of security-related events, and various security protocols. Your server is secure by default. That is, other than setting up user accounts and privileges, no initial configuration has to be done related to security. For example, no insecure protocols, such as Telnet, are initially enabled. |
|
No initial configuration is needed.
See the Oracle Solaris OS documentation collection at http://www.oracle.com/technetwork/documentation/index.html |
|
No initial configuration is needed. PCI cards can be removed and inserted while your midrange or high-end (but not entry-level) server continues to operate. The Oracle Solaris OS cfgadm command is used to unconfigure and disconnect a PCI card. See the Service Manual, and the Oracle Solaris OS documentation collection at http://www.oracle.com/technetwork/documentation/index.html |
|
No initial configuration is needed. The External I/O Expansion Unit on midrange and high-end (but not entry-level) servers is a rack mountable PCI card chassis. See the External I/O Expansion Unit Installation and Service Manual. |
This section lists the information needed for initial system configuration and the initial configuration tasks.
Before you configure the software, have the following available:
More information about access is contained in Chapter 2.
Initial configuration requires these tasks:
1. Logging in to the Service Processor with the default log-in name over a serial connection. You must have physical access to the system.
2. Adding at least one user account with a minimum of one privilege, useradm. This user with useradm privileges can then create the rest of the user accounts.
3. Configuring the DSCP network.
4. Configuring the XSCF network.
5. Setting the Service Processor time. The Service Processor can be an NTP client, or an NTP client and NTP server for the domains.
6. Configuring or enabling any optional services you want to use immediately.
These services include Telnet, SNMP, SMTP, LDAP, NTP, HTTPS, DNS, SSH, domains, log archiving, and COD. COD is not supported on the M3000 server.
For additional information on this chapter’s topics, see:
man pages Note -(see the Note following this table) |
|
SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide |
|
Oracle Solaris OS documentation collection at http://www.oracle.com/technetwork/documentation/index.html |
|