|C H A P T E R 2|
Configuring RSC Software
This chapter provides information about how to configure Sun Remote System Control (RSC) software. For installation instructions, see the instructions that accompany your release media. Downloadable software is also available at the following web site: http://www.sun.com/servers/rsc.html.
The RSC configuration script allows you to set up RSC configuration. You can change RSC configuration after initial configuration using RSC shell commands, the RSC graphical user interface (GUI), or the rscadm utility. However, before running the configuration script, you must decide how you will use RSC software to manage your server. The basic decisions you need to make are:
RSC has three dedicated communication ports on the rear of the RSC card: a serial port, an Ethernet port, and a connector to RSC's PCMCIA internal modem. RSC can use any or all of these to communicate with users. You can connect the serial port to an ASCII terminal or workstation, or to a terminal "concentrator"; see your hardware owner's guide for more information.
Note - Sun Enterprise 250 servers have an RSC Ethernet port and an RSC serial port, but no internal modem. You can connect an external modem to the RSC serial port. See "Invalid Cross-Reference Format".
The RSC Ethernet port, when connected to your local Ethernet, is most useful for accessing RSC from within your company network. You can connect to RSC remotely using any standard telnet and PPP (point-to-point protocol) clients with TCP/IP (Transmission Control Protocol/Internet Protocol). For example, you may use a pool of modems attached to a terminal server running PPP.
You can use the RSC modem to send alerts to pagers. For sending pager alerts, RSC is designed to operate with any modem paging service that complies with the Telocator Alphanumeric Protocol (TAP).
To use the RSC GUI, users must have RSC client software installed on their machines. If an incoming connection uses PPP, then RSC can support several remote user sessions simultaneously. Otherwise, only one remote user can be active at a time.
The RSC serial port allows access to the RSC command line interface (CLI). You can connect an ASCII terminal or a workstation to the serial port, or you can connect a serial line to a workstation or PC that is running a terminal emulator. You can also connect a terminal server or a concentrator port to the serial port.
When a server problem occurs, RSC sends an alert message. RSC always sends alert messages to all users who are logged in to RSC accounts on that server.
You can also configure RSC to send alerts to people who are not logged in to RSC accounts on that server. These additional alerts can be sent to an email address, to alphanumeric pagers, or to both. After receiving an alert, an RSC user can connect to their RSC account for that server and address the alert condition.
If the RSC Ethernet port is enabled, you can set an email address to use for alerts. Although only a single email address is permitted, you can notify several people that a problem has occurred by using an email alias or mailing list.
If the RSC modem is enabled and connected, you can page one or two alphanumeric pagers when an alert occurs. Use this alert mechanism if your system administrators typically carry pagers. For sending pager alerts, RSC is designed to operate with any modem paging service that complies with the Telocator Alphanumeric Protocol (TAP).
After deciding which communication ports to enable and how to configure alerts, write down your planned responses to the RSC configuration script system prompts shown below. After you have recorded this information, you can refer to it when you configure RSC software on the server. If some of this information is not available yet or changes, you can use RSC interfaces or the rscadm utility to change your configuration after installation.
You may want to use the server's service contract number (recommended), location, system administrator's name, or responsible department as customer information.
Note - Sun recommends setting the RSC device name associated with the Internet address in name server maps (either NIS or DNS) to be the name of the server with -rsc appended to it. For instance, if your server's hostname is bert, the recommended name to assign to the RSC device for that server is bert-rsc. Sun also recommends that if you use DHCP, you configure the DHCP server to assign a fixed IP address to RSC.
Note - Sun Enterprise 250 servers use the RSC serial port for modem connection. If you are configuring RSC on a Sun Enterprise 250 server, the configuration script asks if you want to enable the RSC serial port, and if you respond yes it prompts for a value for serial port baud rate, serial data bits, serial parity, serial stop bits, whether to use hardware handshaking, and whether to enable PPP over the RSC serial port.
See Chapter 4 for information about account usernames, permissions, and passwords.
After you have installed RSC software on the server and decided how you want to configure RSC, log in to the server as root and run the configuration script using the following command:
You can obtain the string to use for platform-name using the Solaris command
uname -i. For example:
The script prompts you for configuration information. Some prompts may not appear, depending on choices you make. To respond to the prompts, refer to the information you recorded following the instructions in "Invalid Cross-Reference Format" beginning on "Invalid Cross-Reference Format".
Prompts relating to enabling alerts, the RSC Ethernet port, or the RSC modem include a skip option. This option is useful only if you run the script again after initial configuration to change selected options of the RSC configuration. When you choose skip when running the script after initial configuration, configuration for that option will not change. If you choose skip and that option has not been previously set, RSC uses the default setting (shown in brackets).
After you have responded to all configuration setting prompts, the configuration script displays a summary for each section of the procedure and asks whether it is correct. For each section, respond y or yes to confirm your choices, or respond n or no to revisit that section of the configuration procedure.
When you have confirmed all sections, the configuration procedure updates the RSC flash PROM.
Caution - It takes a few minutes to update the RSC flash PROM. Do not interrupt this process by aborting the configuration procedure or removing system power. If the update is interrupted, you must restart the configuration script, and it must complete successfully, before RSC can function properly.
After setting up RSC as you specified, the configuration procedure prompts you for the password for the user account, if you chose to create a user account. Then it prompts you to repeat the password.
Finally, the procedure asks if you want to reset RSC. A reset is required before Ethernet configuration takes effect. This completes RSC server software configuration.
After RSC software is installed and configured, the system console is still available as on any normal Sun machine. To enable RSC as the system console device instead, you must access the server console, shut down the system, and type the following commands at the ok prompt:
Note - For Sun Enterprise 250 servers, use the following commands at the okprompt: diag-output-to rsc, setenv input-device rsc, setenv output-device rsc.Also, use diag-output-to ttyain the next example below.
These commands take effect after the next server reset. At any time, you can use the following command to remove RSC as the default console:
If your server has a keyboard and monitor, you also need to type the following commands after removing RSC as the default console:
If RSC is not designated as the system console, you cannot use RSC to access the console. You can temporarily redirect the console to RSC using the RSC bootmode -u command, or by choosing Set Boot Mode using the RSC GUI and checking the box labeled "Force the host to direct the console to RSC." These methods affect the next boot only.
After initial configuration, you can control configuration and add or modify user accounts by using the GUI or RSC shell commands. You can also log in to the host as root and use the rscadm utility to control RSC configuration and user accounts; see Chapter 5.
If you are using an uninterruptible power supply (UPS) for the host, you must configure it properly. For an example of UPS configuration, see Appendix A.
If PPP is enabled on the modem, RSC supports multiple sessions, either shell or GUI, through one modem connection. If PPP is not enabled, you can run only one session over the modem, and it must be a shell session. RSC supports multiple sessions over its Ethernet port.
To use PPP for dialing in to the RSC modem, the RSC configuration variable ppp_enabled must be set to true, or PPP must be enabled using the RSC GUI. In addition, you must configure PPP on each client machine that will use PPP to dial in to RSC accounts on the RSC modem.
To allow connection to RSC from a remote client using PPP, you must configure PPP on the client. For a Solaris client, see Configuring and Using Solstice PPP 4.0 Clients. For a Microsoft Windows client, see your Microsoft Windows documentation.
The Solstice PPP client configuration script /usr/bin/pppinit creates a CHAT script in /etc/opt/SUNWconn/ppp/script that defines the dialog that occurs between a client and server during the connection phase. The contents of this CHAT script are not needed to establish a PPP connection to RSC. In order to successfully establish connection to RSC from a Solstice PPP client, comment or delete the contents of the CHAT script, but do not delete the file.
To complete alert configuration, choose Configure Alerts in the GUI, or set the following configuration variables using the RSC shell or rscadm utility:
The GUI provides help for configuring RSC alerts. For help configuring RSC alert variables in the shell, see Alert Variables. RSC generates alert messages with the following format:
You can also use the rscadm subcommand send_event -c to send a customized alert at any time. You can do this directly at the superuser prompt, and you can also create a command file that runs and sends the alert under special circumstances. See Appendix C.
You should periodically use rscadm commands to create a backup file that records RSC configuration settings on a remote system. For example (after setting your path to the rscadm utility):
Use a meaningful file name that includes the name of the server that RSC controls.
Later, you can refer to this file to restore the settings if you need to reinstall RSC software on the server or replace RSC hardware.