Domino remote setup for DPAR on Z

hcl-bot · January 21, 2010, 4:15pm

I am having issues with remote server setup for a new DPAR on zLinux. This is my first implementation of multiple Domino Partitions.

*Example of existing DPAR is running as follows:

ip: 1.1.1.1

hostname: host1.ibm.com

user: notes

group: notes

*Adding a second DPAR as follows:

new IP added 1.1.1.2

new hostname host2.ibm.com

(/etc/hosts updated)

new user notesa

new user’s group notes

echo $PATH

/opt/lotus/bin:/opt/lotus/bin/tools:/sodpar1/data:/usr/lib/mit/sbin:/bin:/usr/X11R6/bin:/usr/bin:/usr/local/bin:/home/notesa/bin

ssh login to 1.1.1.2, set hostname to host2, as sudoer user and install with script.dat as follows:

installation_type = 2

template_install_option = 1

add_data_directories_only = 1

program_directory = “/opt/lotus”

data_directories: “/sodpar1/data”

data_UNIX_user = “notesa”

data_UNIX_group = “notes”

*The current install has owner notes notes permissions , 755, for everything in /opt/lotus/bin and /opt/lotus/notes/latest/zlinux with stickybits and chown and chmod proper on tunekrnl and bindsock

After installation:

notesa@host2~:/sodpar1/data> /opt/lotus/bin/server -listen

Starts and listens on 8585, showing properly also host2.

Connect via remote setup on windows workstation, but it will only reach 1.1.1.1:8585 . It finds the DPARs and allows selection of /sodpar1/data. Attempt the setup, first server in new domain, and it hangs at screen stating it will create the .ID files.
While that is hanging, I checked netstat -n -a | grep :8585

tcp 0 0 :::8585 :::* LISTEN

tcp 0 0 1.1.1.1:8585 9.49.213.186:4587 ESTABLISHED

setuplog.txt stops at the Admin ID file and logs nothing further:

FILE_EXISTS

processing FileExists

File /sodpar1/data/admin.id does not exist.

ServerConnectionManager.command request= CAN_WRITE

processing CanWrite

/sodpar1/data/admin.id is writeable.

Question: Shouldn’t the server be listening and remote setup connect to all IPs, including 1.1.1.2:8585 for remote server setup?

Question: If I follow instruction to /opt/lotus/bin/server -q host2 does this have any chance to shutdown the server running properly on host1?

Question: Can notes.ini specify the TCPIP port prior to Domino setup being run, to ensure the listen task runs on the proper IP? Is there a way to control the listener task’s IP?

Question: Does the existing DPAR need to be restarted after adding the new IP? Or should it be shut down? It is production and has been avoided.

We are trying to determine if this could be a firewall issue, or if this is working as designed and something is being missed. We do not have VNC capability to do local server setup.

Thank you!

hcl-bot · January 22, 2010, 9:16am

Subject: Problem found and question answers

I am now able to answer my own questions.

While checking setuplog.txt on the server, I was failing to check setuplog.txt on the remote workstation performing the update. Evidence of errors File is read only directed me to check the permissions at this point in the install.

The new DPAR data directory permissions needed to be modified, and I performed chmod updates until the setup succeeded.

Question: Shouldn’t the server be listening and remote setup connect to all IPs, including 1.1.1.2:8585 for remote server setup?

Answer: I found this was not a requirement, as the server was successfully setup using the first DPAR’s IP address. Still, I set the notes.ini with TCPIP parameters to ensure the server would use the proper IP address for it’s hostname.

Question: If I follow instruction to /opt/lotus/bin/server -q host2 does this have any chance to shutdown the server running properly on host1?

Answer: Instead I used CTRL-C to close the domino DPAR setup attempt when it had failed, and logged out of notesa (occasionally ensuring it was logged out with kill -9 -u notesa

Question: Can notes.ini specify the TCPIP port prior to Domino setup being run, to ensure the listen task runs on the proper IP? Is there a way to control the listener task’s IP?

Answer: Listen never succeeded on the new IP address, though the server was still able to complete setup and started up properly using the new IP address.

Question: Does the existing DPAR need to be restarted after adding the new IP? Or should it be shut down? It is production and has been avoided.

Answer: No.

Thank you.