C H A P T E R 2 |
Configuring the Software |
This chapter describes how to set up the V210 Sun Fire server and use the software installation utility, ssmsconfig, to install the Sun StorEdge Management Portal and the other Sun StorEdge Enterprise Storage Manager (ESM) Base Applications. It includes the following topics:
The ESM Base Applications are hosted on a V210 Sun Fire server, which is typically rack mounted. Installation and mounting of the server is beyond the scope of this guide. For instructions on installing the V210 server, consult the Sun Fire V210 and V240 Servers Installation Guide.
After you have installed and mounted the server, make the following physical network connections to the server:
Advanced Lights-Out Management (ALOM) provides remote management and administration capabilities for the V210 server. The Network Management port is part of the V210's ALOM system. The ESM Base Applications system console is redirected to the Network Management port. You must establish a console session through ALOM to install and configure the ESM Base Applications.
Use the following procedure to establish a console session on the Network Management port.
1. Configure a network interface on another system to use 10.0.0.2 as an IP address with a netmask of 255.255.255.0.
2. From the other system, telnet to 10.0.0.1 (the default IP address of the Network Management port) and log in to the ALOM as admin, using the password ssmspass.
3. ALOM is active as soon as the system is powered up. To power up the system, type poweron at the sc> prompt. The system boots up in approximately 90 seconds.
4. To initiate a system console session from ALOM, type console -f and answer y to take control of the console.
5. At the V210 Open Boot Prom {1} ok prompt, type boot.
Before the system leaves the factory, it is set to an unconfigured state through the
sys-unconfig (1M) command. When you reboot the system, you are prompted for network and Solaris system configuration information, as would normally be the case during a system reboot following a sys-unconfig (1M) command.
Note - For a narrated, step-by-step example of a Solaris configuration session, see Appendix A. |
Make sure you have the following information before you start configuring the Solaris Operating System (OS). You will be prompted to provide this information, unless otherwise noted:
There are several other settings and selections you must make to complete the configuration of the Solaris OS. See the Solaris documentation for more information about these settings.
If you make a mistake during the Solaris configuration, you can go back and fix it. If you discover the error after the Solaris OS is configured, but before you have configured the ESM Base Applications, run sys-unconfig (1M) and reconfigure the Solaris OS. If the mistake is discovered after the ESM Base Applications are configured, you must reload the ESM Base Applications from the product DVD, then reconfigure the Solaris OS, and reinstall the ESM Base Applications. See Appendix A for details.
This section describes how to complete installation and configuration of these ESM Base Applications:
This also includes configuration of the Java ES. Installation and configuration of all components is accomplished through an automated script (ssmsconfig).
Use the following procedure to complete the installation and configuration of the ESM Base Applications.
1. Log in to the system as root, using the password you provided when you set up Solaris.
2. Open another shell window and start a second Telnet session on the system.
It is recommended that you start another Telnet session to avoid display of extraneous messages. Use the host name and password that you assigned to the system during Solaris setup, as in the following example:
3. Type /var/opt/SUNWbaconf/bin/ssmsconfig at the shell prompt to start the installation script.
4. When the license agreement is displayed, read it, press Return to accept the license terms, and continue with the installation.
If you do not accept the agreement, the installation terminates.
5. Specify the fully qualified domain name of the host.
Enter the fully qualified domain name you prefer to use. Enter y to confirm your response. For future reference, also record the location of the installation log file.
In the example, the system's host name is server1 and the domain name is lab.example.com. Thus, this system's fully qualified domain name is server1.lab.example.com.
Note - Once Java ES is configured, you cannot change the system's host name, domain name, or IP address. If you must change the host name, domain name, or IP address, you must reload and reconfigure the system as described in Appendix A. |
6. If the IP address listed as the default by ssmsconfig is correct, press Return to continue. If it is not correct, enter the IP address you prefer to use. Type y to confirm your response.
Please enter the IP address for the given host name [10.20.30.40]:<Return> You entered: 10.20.30.40 Is this correct? (Y/N) y |
After you confirm the system information, the ESM Base Applications installation and Java ES configuration process begins and takes approximately 45 minutes. No further user interaction is required.
Caution - Do not interrupt the installation process, as this may result in a partial configuration of the ESM Base Applications. In the event that the configuration is not completed, use the DVD recovery procedure described in Appendix A to reload and reconfigure the system. |
As a convenience for installation, CONSOLE=/dev/console has been commented out of the/etc/default/login file to allow non-console root logins. It is strongly recommended that you reset CONSOLE=/dev/console after installation.
After the ESM Base Applications are installed, you should change the ALOM default administrative password and network configuration to suit your particular site.
An ALOM password must meet the following requirements:
The default ALOM password is ssms. Change the default ALOM password by typing the new password at the Password and Re-enter Password prompts.
# PATH=$PATH:/usr/platform/SUNW,Sun-Fire-V210/sbin # export PATH # scadm userpassword admin Password: ******** Re-enter Password: ******** # |
The default ALOM network configuration probably is not useful to you after you have installed the ESM Base Applications. This procedure describes how to change the network configuration to better suit your location.
Note - Although this can be done directly from the ALOM application, this example shows how to configure the network settings from the root user's shell prompt. |
1. Display the current ALOM network configuration.
# PATH=$PATH:/usr/platform/SUNW,Sun-Fire-V210/sbin # export PATH # scadm shownetwork IP Address: 10.0.0.1 Gateway address: 10.0.0.1 Netmask: 255.255.255.0 Ethernet address: 00:03:ba:a6:eb:90 # |
2. Change the network interface configuration and reset ALOM (via resetrsc).
In the example, the IP address, the netmask, and default routing destination are changed to 10.10.10.10, 255.255.255.0, and 10.10.10.248 respectively. Resetting the ALOM takes about 10 seconds and does not affect the operation of the ESM Base Applications. Note that if you have a Telnet session running on ALOM, it will be terminated.
# scadm set netsc_ipaddr 10.10.10.10 # scadm set netsc_ipnetmask 255.255.255.0 # scadm set netsc_ipgateway 10.10.10.248 # scadm resetrsc |
3. Display the new ALOM configuration and make sure the settings are correct.
# scadm shownetwork IP Address: 10.10.10.10 Gateway address: 10.10.10.248 Netmask: 255.255.255.0 Ethernet address: 00:03:ba:a6:eb:90 # |
After you verify the settings, you can use Telnet to establish a new system console session with the new IP address.
Note - If you plan to use Sun StorEdge Data Replication Manager (DRM), you must enable it. See Chapter 4 for more information. |
The sa_admin role is automatically created during the Storage Automated Diagnostic Environment installation. You should assign the sa_admin role to any user who will do more than just view and refresh the configuration information.
Note - The user whose role you plan to modify must be logged out of the system. If the user is not logged out of the system, the role assignment will fail. |
To assign the sa_admin role to a user, you must be logged in as root.
1. Determine the existing roles of the user to whom you want to grant the sa_admin role.
2. Do one of the following, depending on the output from the preceding command:
3. Verify that the sa_admin role was granted to the user:
The sa_admin role should be listed in the output from the above command.
If sa_admin does not appear in the output and the user has existing roles, try running the command again by replacing `/usr/bin/roles username` with the output from the command issued in Step 3. Do not include spaces in the comma-separated list.
For more information about Storage Automated Diagnostic Environment, go to http://www.sun.com/products-n-solutions/hardware/docs/Software/index.html.
To change the sa_admin password, type the following:
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.