Setting Up an Additional Domino Partition on a Partitioned Server

Mindwatering Incorporated

Author: Tripp W Black

Created: 12/21/2008 at 12:38 AM


Domino Upgrades / Installations
Software Upgrade, Software (Re)Configuration

Setting Up a Domino Partition on a Server with One or More Preexisting Partitions Already

These instructions assume that you are using the model of 1 Domino program folder and <n> number of data/notesdata partitions.

1. Configure your network card with a new IP address.
(These instructions assume that no special Port Translation/Mapping Schemes are in play.)
    Control Panel --> Network Connections --> Local Area Connection --> Properties
    -- If re-using same NIC, then simply add an additional IP address to the card.
    -- If configurating a disabled, un-used Local Connection (NIC), then edit it's properties and assign an IP address, and enable it.
    You have an existing ethernet adapter/NIC defined as "eth0" and it's on the network 192.168.112.x. The existing address is and you are going to add

    - To do it temporarily, you could add it as an alias to eth0 with ifconfig:
    1. Enter the command:
    ifconfig eth0:1
    (This is useful to test and see that yes, it's working before updating your sysconfig/network files.)

    - To make it permanent:
    1. Verify the current ethernet configuration doesn't have a GATEWAY= parameter in it
    cat /etc/sysconfig/network-scripts/ifcfg-eth0
    If it does, remove that line from the file and add it to the /etc/sysconfig/network file "main" file.

    2. Copy the current configuration to a new file adding a :1 to the end. (Each additional IP is an incremental number.)
    cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0:1

    3. Update the eth0:1 file:
    nano /etc/sysconfig/network-scripts/ifcfg-eth0:1

    3a. Update the DEVICE line adding the ":1":

    3b. Update the IPADDR= line to the new IP address.
    3c. Save the changes.

    4. Start the new secondary network interface.
    ifup eth0:1

2. If the existing Domino server partitions are not already bound to specific IP addresses, update the notes.ini file.
Note: If you already have more than one, they should already be that way from the original install.
- Under the lines:
TCPIPportname=TCP, 0, 15, 0
add this line:

1st server:
TCPIP=TCP, 0, 15, 0

2nd server:
TCPIP2=TCP, 0, 15, 0

3. Repeat the process for the Internet protocols which each are running.
- POP3NotesPort=portname
- IMAPNotesPort=portname
- SMTPNotesPort=portname
- LDAPNotesPort=portname
- For the web, you simply bind it on the server document or the Internet Site document.

... (cont'd from 2nd server example above)

4. Register the new server.
- Register the new server in the appropriate OU or O.
- Make sure you don't give the server password.
- Make note where the new ID is located, so we can copy it to the new data directory once the directory exists.
Note: This could have obviously been done before now or after the next step.

5. Create additional partition for new server.
- You can do this "manually", by using an existing data folder's ini and templates and wiping the ini you copied. However, the recommened right way is to re-run the install program, specify the same /opt/lotus, but add a new data folder when that path comes up.
- For the iSeries, verify the LOTUS_SERVERS file contains the correct data directory path and partition number, "/qibm/userdata/lotus/LOTUS_SERVERS", where each server has a "SERVER=" entry.

6. Perform the setup of the new server.
- Copy the new server's id to its data folder.
- Make sure to specify in this unique Notes Port for the new server (e.g. TCPIP2).

Note: This is the Port field, not the Notes Network or Protocol fields.
- Do NOT start the server after you finish setup. You aer going to want to update the INI with its specific IP Address.

7. Now that we have a notes.ini, let's edit it and restict the old and the new server to their IP addresses by editing each notes.ini file as in step 2 above.
- Shut down the existing domino server for a moment to update it's IP address. Alternately, you should be able to simply edit the notes.ini and restart ports.
- Edit the notes.ini of the new setup server and specify its unique IP address. Don't forget to add the POP3, IMAP, SMTP, and LDAP lines, too, if they are running.

8. Start the new server.
- Restart the ports or restart the existing (newer) server and watch its console/log for errors.
- Verify that services for the existing server are binding to the correct IP address. NPing (NConnect) tool works great for this.
- Start the new server and watch its console/log for errors.
- Verify the new server is behaving and binding (only) to its correct IP address.


Notes for Upgrading Partitions:
- From Notes Admin "Installing Domino on UNIX systems" help page:
"Choose the Data Directories Only option when migrating a single server install to a multiple server install. If you are adding multiple partitions, select the option to install partitioned servers when specifying the corresponding program files directory name. Or, choose this option when you are upgrading only one partition on a multiple-partitioned server."

- From Notes Admin "Installing Domino on Linux on zSeries systems" help page:
"If you want all instances to be the same release, it is best to install a Domino partitioned server because all Domino partitions then share one program directory and, by doing so, conserve system resources. If you install a single Domino server and later want to make it a partitioned server, you can do so without removing the initial installation. When you have multiple instances of the Domino server, each with a separate program directory, one or more of the instances may be a partitioned server."
(Note: This paragraph is talking about partitions w/a single program directory (e.g. opt/lotus/) and the linux option of a with partitions each having a unique program directories. With the latter you can upgrade separately.)

previous page