Before you can use the N1 System Manager to discover manageable servers, each manageable server must be set up as follows:
An IP address must be assigned to each manageable server's management port.
For ILOM, ALOM, and SP-based manageable servers, refer to the server documentation for the server's management port IP address assignment procedure. You can also locate the server documentation online at http://sunsolve.sun.com/handbook_pub/Systems/.
For RSC-based manageable servers, assign an IP address to each server as described in To Configure the RSC IP Address and Credentials.
Management processor account credentials must be configured on each manageable server.
For ALOM-based manageable servers, refer to the server documentation for the server's management port telnet configuration procedure.
For SP and ILOM-based manageable servers, refer to the server documentation for the server's management port ssh and IPMI configuration procedures.
For RSC—based manageable servers, assign credentials to each server's RSC and redirect the server's console to the RSC as described in To Configure the RSC IP Address and Credentials.
Discovery of a manageable server will fail if the server's management port has not been configured.
If you do not specify the management server management port credentials when running discovery, the discovery process will use the default credentials shown in the following table.
Table 2–11 SPARC Architecture Manageable Server Default Credentials
Server Type |
Management Port Type |
Telnet Login |
Telnet Password |
---|---|---|---|
Netra 240 and 440 |
ALOM |
admin |
admin |
Sun Fire V210, V240, and V440 |
ALOM |
admin |
admin |
Sun Fire V490, V890 |
RSC |
admin |
n1smadmin |
Sun Fire T1000 and T2000 |
ALOM |
admin |
admin |
To manage RSC-based manageable servers, you must first configure the RSC credentials and the Online Boot Prom (OBP) as described in Preparing RSC-based Manageable Servers.
If you do not specify the management server management port credentials when running discovery, the discovery process will use the default credentials shown in the following table.
Table 2–12 x86 Architecture Manageable Server Default Credentials
Server Type |
Management Port Type |
SSH Login |
SSH Password |
IPMI Login |
IPMI Password |
SNMP Read Community String |
---|---|---|---|---|---|---|
Sun Fire V20z and V40z |
SP |
admin |
admin |
- |
admin |
public |
Sun Fire X2100 |
SP |
- |
- |
Admin |
admin |
- |
Sun Fire X4100 and X4200 |
ILOM |
root |
changeme |
root |
changeme |
public |
If only one credential is specified during discovery for x86 architecture manageable servers, the missing credential is configured with one of the defaults specified above.
Automatic configuration of credentials during discovery is supported for Sun Fire V20z and V40z servers if they are in the factory default state. If you do specify the login accounts and passwords for discovery of a Sun Fire V20z or V40z, the discovery process configures the Sun Fire V20z or V40z using the credentials you provide.
Although the Sun Fire X2100 does not support SNMP, the X2100 does support IPMI platform event trap (PET), which generates SNMP V1 traps for IPMI events. The N1 System Manager listens for the X2100 IPMI events.
The Sun Fire V490 and V890 RSC IP address and credentials, are configured by running configuration utilities from the Solaris root command line prompt on the server. The servers are shipped with Solaris pre-installed. Configuration of the Online Boot Prom (OBP) is done using a telnet session to the RSC.
Preparation of an RSC-based manageable server is comprised of the following tasks:
Assign an IP address, netmask and gateway to the server. You must download the RSC utilities version 2.2.3 or later to the server and run the utilities before you can configure the server's RSC.
Log in as root to the V490 or V890 manageable server.
Download the RSC version 1.2.3 utilities zip file.
Go to http://www.sun.com/servers/rsc.html. Download the zip file appropriate for the Solaris operating system installed on the server:
Solaris 9 or later: rsc2.2.3_packages_s9.zip
Solaris 8: rsc2.2.3_packages_s8.zip
When the download has completed, unzip the file to a temporary directory, and then change directory to the temporary directory.
Install the RSC version 2.2.3 packages on the manageable server.
Install the following packages on the server using the pkgadd command:
SUNWrsc - the RSC base package for installation on the host machine
SUNWrscd - the RSC documentation package
SUNWrscj - the RSC GUI package to display the RSC GUI
If you are asked whether to install conflicting files, type Y to override the existing version.
For example:
# pkgadd -d . SUNWrsc The following files are already installed on the system and are being used by another package: /usr <attribute change only> Do you want to install these conflicting files [y,n,?,q] y ## Checking for setuid/setgid programs Installing Remote System Control as <SUNWrsc> . . . Installation of <SUNWrsc> was successful # pkgadd -d . SUNWrscd Processing package instance <SUNWrscd> . . . Installation of <SUNWrscd> was successful # pkgadd -d . SUNWrscj Processing package instance <SUNWrscj> . . . Installation of <SUNWrscj> was successful |
Configure the server's RSC as described in the next procedure.
The Sun Fire V490 and V890 RSC credentials are configured by running configuration utilities from the Solaris root command line prompt on the server. The servers are shipped with Solaris pre-installed.
This procedure describes only the information required by the N1 System Manager. For detailed information about the RSC configuration utility, see the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12 and the Sun Remote System Control (RSC) 2.2.3 Release Notes at http://docs.sun.com/source/819–2022.
RSC Configuration Utilities version 2.3.3 must be installed on the server as described in To Download and Update the RSC Utilities
Log in as root on the RSC-based manageable server.
Run the RSC configuration utility.
If you are configuring a V490 server, type /usr/platform/SUNW,Sun-Fire-V490/rsc/rsc-config.
If you are configuring a V890 server, type /usr/platform/SUNW,Sun-Fire-V890/rsc/rsc-config.
Respond to each prompt according to the requirements of your network, except for the RSC user account prompts:
When prompted for the RSC user account, type admin.
When prompted for the RSC user account password, type n1smadmin.
When prompted for the RSC user privileges, type cuar.
Redirect the server console to the RSC, and configure the Online Boot Prom (OBP) settings.
The Sun Fire V490 and V890 RSC credentials are configured by running configuration utilities from the Solaris root command line prompt on the server. The servers are shipped with Solaris pre-installed.
This procedure describes only the information required by the N1 System Manager. For detailed information about console redirection on an RSC-based server and OBP configuration, see the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12 and the Sun Remote System Control (RSC) 2.2.3 Release Notes at http://docs.sun.com/source/819–2022.
RSC Configuration Utilities version 2.3.3 must be installed on the server as described in To Download and Update the RSC Utilities.
The RSC must be configured as described in To Configure the RSC IP Address and Credentials.
Log on to the manageable server's RSC using the command telnet IP address where IP address is the address you assigned to the RSC.
Redirect the server's console to the RSC as described in the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12.
Configure the server's OBP as described in the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12.
Ensure the following environment variables are set to the values shown:
OBP Environment Variable |
Value |
---|---|
local-mac-address? |
true |
output-device |
rsc-console |
input-device |
rsc-console |
diag-device |
disk |
diag-script |
none |
diag-level |
off |
diag-switch? |
false |
For example:
> setenv local-mac-address? true > setenv output-device rsc-console |
To verify the settings, type printenv.