2 Getting Started

This chapter provides an overview of the steps required to implement the Oracle Communications Service Broker Netra 6000 High Availability Manager (HA Manager). It also provides information on the physical installation of the system and describes initial tasks, such as starting the system and resetting the Administration Console password.

Overview of Implementing HA Manager

As a complete, self-contained system, internal communication, redundancy, file sharing, and other capabilities are all built into the HA Manager system.

The HA Manager deployment configuration includes predefined domains and servers that require no manual modification. Therefore, after the Sun Netra 6000 hardware is physically installed, getting started requires relatively few steps.

An overview of the steps for getting started are:

Verify the physical installation and setup. See "HA Manager System Requirements" for more information.
Start the system. See "Starting the System" for more information.
Reset the Administration Console password. See "Resetting Passwords" for more information.
Log in to the Administration Console Web interface. See "Logging In to the Administration Console" for more information.
Verify and configure the global network settings. See Chapter 4, "Connecting to the Network" for more information.
Configure the blade-specific network settings. See Chapter 4, "Connecting to the Network" for more information.

After completing these initial steps, you can use the Signaling Servers Administration Console and the Processing Servers Administration Console to configure the traffic brokering properties and the behavior of the system.

HA Manager System Requirements

An HA Manager deployment is a set of four or more Sun Netra X6270 M2 Server Module blades installed on Oracle's Sun Netra 6000 Modular System chassis. The minimum system consists of four server modules, in which two operate as Bootstrap Blades and two as Worker Blades.

While detailed information about the installation and setup of the hardware and system components is beyond the scope of this document, this section provides an overview of the hardware and system setup requirements for an HA Manager deployment.

The hardware and system prerequisites for an HA Manager deployment are:

A Sun Netra 6000 chassis installed in a rack and Sun Netra X6270 M2 Server Modules installed in the chassis.
Ethernet cables connecting two rack-mounted Sun Blade 6000 Ethernet Switched NEM 24p 10 GbE switches to the external network. For redundancy, an additional cable connecting the two switches together.

Note that connectivity between the service modules within the system is automatically enabled. Each blade has a preconfigured dual port, 10 Gigabit Ethernet card that is connected to the rack-mounted switches through internal connectors on the midplane of the Sun Netra 6000 chassis.
The switches preconfigured to enable connectivity within HA Manager. Connectivity from the switches to the local network needs to be configured on a site-specific basis.

For information about configuring the switch for external connectivity, see the Sun Blade 6000 Ethernet Switched NEM 24p 10 GbE switches documentation.
The Chassis Monitoring Module (CMM) Integrated Lights Out Manager (ILOM) Web interface has to be accessible either on the network or by direct connection to the Ethernet NET MGT port or serial SER MGT port on the chassis. You need to set default username and password.

For complete information about the modular system, see the Sun Netra 6000 documentation, which is available on the Oracle Technology Network Web site.

See also the Sun Netra X6270 M2 Server Module documentation.

Starting the System

You apply power to the system by connecting four power cords from the AC power connectors to your power source. Powering on the system starts up the chassis as well as all blades that are installed in the chassis.

You can power on or power off individual blades in the chassis using the CMM ILOM Web interface or using the Service Broker System Administration Console. The power-related operations in the System Administration Console are provided as a convenience and do not differ from the equivalent operations in the CMM ILOM Web interface.

Accessing the Bootstrap Blade Operating System Environment

Certain HA Manager administration tasks, such as backing up configuration files or changing user account passwords, require access to the operating system command-line interface on the Bootstrap Blades. Such tasks typically need to be performed on all Bootstrap Blades in your system.

You can access the Bootstrap Blade operating system command-line environment using one of the following methods:

CMM ILOM Web interface
Linux Secure Shell SSH

Accessing the Bootstrap Blade Using the CMM ILOM Web Interface

To access the Bootstrap Blade through CMM ILOM:

In the CMM ILOM Web interface, select the Bootstrap Blade from the chassis tree.
In the Remote Control tab, click the Launch Remote console button.

For complete information on using the CMM ILOM Web interface, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 documentation.

Accessing the Bootstrap Blade Using SSH

The active Bootstrap Blade is accessible by an SSH connection to the OSS OAM IP address configured for the system. Note that the OSS OAM IP address is a virtual IP address that is adopted by whichever Bootstrap Blade is serving as the active (primary) Bootstrap. Therefore, extra steps are needed to access the command-line interface on the standby Bootstrap Blade.

To access the standby Bootstrap Blade:

Connect by SSH to the active Bootstrap Blade.
From the active Bootstrap Blade, make an SSH connection to the standby Bootstrap Blade, using the static internal IP address assigned to each Bootstrap Blade, for example:
- Bootstrap Blade 1 (slot 0): 192.168.1.1
- Bootstrap Blade 2 (slot 1): 192.168.1.2

Resetting Passwords

An HA Manager deployment includes various built-in user accounts. The passwords for these accounts are set individually for each system. When first using the system, you need to change the initial passwords.

root user on the operating system
ocsb user on the operating system
admin user for the System Administration Console
admin user for the Signaling Servers Administration Console
admin user for the Processing Servers Administration Console

In addition, the CMM ILOM interface and service module SP ILOM interfaces have their own user accounts. For information on modifying the passwords for ILOM accounts, see the Sun Netra 6000 documentation.

Modifying Operating System Account Passwords

You modify the passwords for the operating system users, root and ocsb, from the operating system command-line environment on the Bootstrap Blades.

The procedure for changing passwords for user accounts differs between Bootstrap Blades and Worker Blades.

For Bootstrap Blades, you change passwords using standard Linux user account modification mechanisms.

Because the Worker Blade operating systems are dynamically loaded at startup through the pre-boot execution environment (PXE) boot process, changing user accounts on Worker Blades requires modifying the boot image. Changing the Bootstrap Blade image affects all subsequently loaded Worker Blades.

Changing Bootstrap Blade User Passwords

Follow these steps to change user account passwords on both Bootstrap Blades:

As the root user, access the operating system command-line interface for the active Bootstrap Blade.

See "Accessing the Bootstrap Blade Operating System Environment" for more information.
Change the password for the root and ocsb user accounts using the passwd command or other standard Linux password change mechanism.

For example, to change the password for the ocsb user with the passwd command, enter the command as follows:
```
passwd ocsb 
Changing password for user ocsb.
New UNIX password: 
Retype new UNIX password: 
passwd: all authentication tokens updated successfully.
```

The change takes effect immediately.

Changing Worker Blade User Passwords

Like Bootstrap Blades, the Worker Blades have two operating system user accounts, root and ocsb. However, the Worker Blade operating system image is loaded on to the Worker Blade modules dynamically through the PXE boot process. Therefore, to change user passwords on the Worker Blades, you need to modify the image that is loaded by the Bootstrap Blades.

You need to perform the following procedure only once. It modifies the user accounts for all subsequently loaded Worker Blades.

To modify the user account passwords for Worker Blades:

As the root user, access the operating system command-line interface for the active Bootstrap Blade.

See "Accessing the Bootstrap Blade Operating System Environment" for more information.
At the command line, navigate to the directory that contains the Worker Blade disk image:

cd var/ocsb/workerblade-ramdisk/
Start the script that compiles and builds the Worker Blade image used for the PXE boot process as follows:

./build.sh

This script builds a new image for the Bootstrap Blade based on the parameters you supply to the script.
When prompted, enter a new password for the user accounts.

This change affects only the Worker Blades that are started subsequent to the change. That is, Worker Blades that were running while performing this procedure maintain their former user passwords until the blades are restarted.

Modifying Administration Console Passwords

You need to modify the user name and password for HTTP basic authentication credentials to access Administration Console interfaces.

To modify the user name and password:

As the root user, access the operating system command-line interface for the active Bootstrap Blade.

See "Accessing the Bootstrap Blade Operating System Environment" for more information.
At the command line, navigate to the directory that contains the password change script:

cd /var/ocsb/ocsb/
At the command line, run the Administration Console user modification script:

./set_web_user_and_password.sh
At the following prompt, enter the new user name for the Administration Console user, or enter admin to keep the existing username:

Please enter the name of the console user
At the following prompt, enter the new password for the Administration Console user:

Please enter the password of the console user

Note that the values you type do not appear on screen.

The changes take effect immediately.

Logging In to the Administration Console

You configure and administer HA Manager using the browser-based Web interface. The Web administration interface is made up of three separate Web applications:

System Administration Console
Signaling Servers Administration Console
Processing Servers Administration Console

Each console is served on a different TCP port number. When you open a console, you initiate a new HTTPS session.You can open each console directly from the System Administration Console interface, which typically serves as the entry point for HA Manager administration.

To log in to the System Administration Console:

Open your Web browser.

The console works with the following browsers:
- Internet Explorer version 8.0 or later from Microsoft Corporation.
- Firefox version 3.0 or later from Mozilla Corporation.
- Safari version 3.0 or later from Apple, Inc.
- Chrome version 3.0 or later from Google Inc.
- Opera version 9.0 or later from Opera Software ASA.
Enter the URL:
```
https://ipaddress:9002/console
```
ipaddress is the IP address assigned to the OAS OAM interface for your system. This address is assigned at system initialization time.

The default listening ports are as follows:.
- System Administration Console: 9002
- Signaling Servers Administration Console: 9001
- Processing Servers Administration Console: 9000
If required, add a security exception to continue.

If this is the first time you have logged in to the Administration Console and you have not replaced the default, self-signed security certificate, a connection warning appears and you must add a security exception to continue. The procedure for this differs according to the Web browser you use. If you have installed a certificate that was signed by one of your browser's trusted certificate authorities, no warning appears.

For information on replacing the default security certificate for the Administration Console, see "Configuring Security" in the Oracle Communications Service Broker 5.0 System Administration Guide.
When prompted, enter the user name and password.

The default username is admin. The default password is set at system initialization.

After logging in, the Overview tab of the System pane appears. For overview information on navigating and using the Administration Console, see Chapter 3, "About System Administration."