Enabling the OTP system management service on another OTP host is comprised of the following two tasks:
Configuring the OTP system management service to run on the OTP host as described in To Configure the OTP System Management Service on Another OTP Host.
To ensure that the system management service runs correctly on the OTP host, you must configure the system management to use the provisioning and management network interfaces of the OTP host.
Restoring the OTP system management service database and configuration files to the OTP host as described in To Restore the OTP System Management Service on the OTP Host.
The restoration process restores the system management database and configuration files, which contain information about the clustered OTP hosts, DNS servers, SMTP settings, logging options, and more.
This section describes how to configure the system management on the OTP host and then restore the system management database and configuration files to the OTP host.
This procedure describes how to configure the OTP system management service on another OTP host within the clustered OTP system.
A backup of the OTP System Management Service database and configuration files must exist on a server external to the clustered OTP system. See To Back Up the OTP Master Server Database and Configuration Files for further information.
Log in as root to the OTP host you have chosen for OTP system management service database and configuration file restoration.
Type n1smconfig to configure the system management service.
# /usr/bin/n1smconfig |
The current system configuration appears, and lists the network interfaces. You are then asked to specify the DHCP server.
For example:
# /usr/bin/n1smconfig - - - - - - CURRENT CONFIGURATION - - - - - - - Provisioning Interface = ce0 : 10.11.52.79 DHCP IP range: none Management Interface = ce0 : 10.11.52.79 Logging values: job.plan-timeout = 1440 job.step-timeout = 120 filter.topic = all filter.severity = 0 Days before deleting log entries = 365 DNS settings = none. Web console auto login enabled = no Serial console with SSHv1 enabled = no Current SSH policy: accept CHANGED host keys for Management IP address = yes accept CHANGED host keys for Platform IP address = yes accept UNKNOWN host keys for Management IP address = yes accept UNKNOWN host keys for Platform IP address = yes ALOM email server = internal server DHCP server = Solaris Discover servers by the OS IP addresses = no CURRENT RIS Servers: - - - - - - - - - - - - - - - - - - - - - - - - This program configures the N1SM Management Server. Only options that can be changed will be displayed. Would you like to continue? ([n]/y) y |
Choose the Solaris DHCP server.
Type s to choose the Solaris DHCP server. The Open Telecommunications Platform does not support ISC DHCP.
A description of the tasks you can perform at this point appears. You are then asked whether you want to modify the interface that is to be used by the provisioning network.
Type y to specify the provisioning network interface.
Even if the provisioning interface shown matches the current provisioning interface, type y to rebind the provisioning interface IP addresst of the new system management host.
The available interfaces are listed. You are asked to specify the provisioning network interface port.
Type the interface name that is to be used for the provisioning interface.
Type the interface name that is to be used for the provisioning interface, for example ce0, eth0, hme0, bge0 and so on depending on the host architecture and installed OS.
You are asked if you want the DHCP server to use a specific IP address range.
Type n to disable DHCP IP address range use.
You are asked if you want to modify the interface that is to be used by the management network.
Type y to specify for the management network interface.
Even if the provisioning interface shown matches the current provisioning interface, type y to rebind the management interface IP addresst of the new system management host.
A description of the management network appears, followed by a list of the network interfaces that have been detected. You are then prompted to specify the interface that is to be used by the management network.
Type the interface name that is to be used for the management interface.
Type the interface name that is to be used for the management interface, for example ce0, eth0, hme0, bge0 and so on depending on the host architecture and installed OS.
You are asked whether you want to configure the DNS name servers and search list entry.
Type n.
The OTP system management restore process will restore the OTP DNS and search list configuration data.
You are asked whether you want to configure the SMTP server for event notification.
Type n.
The restore process will restore the SMTP configuration data.
You are asked whether you want to modify the logging configuration.
Type n.
The restore process will restore the logging configuration data.
You are asked whether you want to enable auto-login for the ILOM Web GUI.
Type n.
The restore process will restore the auto—login configuration data.
You are asked whether you want to enable SSHv1 protocol.
Type n.
The restore process will restore the SSHv1 configuration data.
You are asked whether you want to modify SSH policies for changed and unknown host keys.
Type n.
The restore process will restore the SSH configuration data.
The current status of the ALOM email server is displayed. You are asked whether you want to modify the ALOM email server.
Type n.
The restore process will restore the ALOM email configuration data.
You are asked whether you want to add, delete, or modify the WindowsTM RIS server.
Type n.
This release of the Open Telecommunications Platform does not support Windows.
A description of OS Discovery appears. You are asked whether you want to enable OS discovery.
Type n.
The Open Telecommunications Platform requires IP address-based discovery.
You are asked whether you want to modify the default password on the execution server.
Type n.
The Open Telecommunications Platform requires IP address-based discovery.
You are asked whether you want to modify the default password on the execution server.
Type n.
The restore process will restore the execution server password.
The configuration process then displays the settings you have specified, and asks whether you want to apply the settings.
Review the proposed settings.
Type y to apply the settings.
The settings are applied, and the OTP system management service is restarted.
Type n if the settings are not correct.
You are notified that you must reconfigure and apply settings for the system managementservice to work properly. The configuration process then exits to the system prompt. To configure the system management service, run the n1smconfig command again.
Restore the system management database and files to the OTP host as described in the next procedure.
Log in as root on the OTP host.
Type mkdir -p /var/tmp/n1smbackup.
Copy the n1smbackup.tgz backup file you created in To Back Up the OTP Master Server Database and Configuration Files to the /var/tmp/n1smbackup directory.
Type /opt/sun/n1gc/bin/n1smrestore.sh -f /var/tmp/n1smbackup/n1smbackup.tgz to restore the system management database and files.
For example:
# /opt/sun/n1gc/bin/n1smrestore.sh -f /var/tmp/n1smbackup/n1smbackup.tgz This program will restore Sun N1SM from backup files. The N1SM services will be restarted and N1SM will be interrupted during the process. All files related to N1SM, including network interface configuration, will be restored. Therefore, it is recommended that these files are restored to an identical hardware setup. The restore process will take about 8 minutes. Would you like to continue? [y/N] y Restoring configuration files (done) Restoring SCS database (done) Restoring SCS database (done) N1SM restarted. N1SM restore completed.Run n1smconfig and verify that N1SM settings are correct. |
Type n1smconfig to reconfigure the system management services.
The current configuration is displayed, and you are asked whether you want to continue.
Type y to continue. Reconfigure the system management as described in To Configure the OTP System Management Service on Another OTP Host.
Verify that the OTP System Management Service is working properly.
Open a web browser and log in to the system management service on the OTP host.
Go to URL https://OTP host:6789 where OTP host is either the IP address or the fully qualified name of the OTP host.
The Java Web console log in page is appears. Type your system management user name and password to log in.
The system management page appears.
Type /opt/sun/n1gc/bin/n1sh to open the OTP command shell. For example:
# /opt/sun/n1gc/bin/n1sh N1-ok> |
Successful display of the system management web page and of the N1–ok> prompt signifies successful configuration and restoration of the system management service to the OTP host.
If the system management Web page or the N1–ok> prompt fail to appear, log in as root to the OTP host and type the command svcadm disable n1sm. Wait for the services to stop, and then type the command svcadm enable n1sm. Wait for the services to complete startup, and then retry verification.
(Optional) Remove any OS distributions or OS profiles that exist on the OTP host before creating new OS distributions and OS profiles.
N1-ok> show os all ID Name Type Version 2 s10 solaris solaris10x86 N1-ok> show osprofile ID Name Distribution 2 s10 s10 N1-ok> delete osprofile s10 N1-ok> delete os s10 N1-ok> show os No items found. N1-ok> show osprofile No items found. |