Perform the steps in this section to set up iPrint and an iPrint cluster resource on the OES nodes in the mixed-mode cluster.
Because iPrint on NetWare and iPrint on Linux are different, cluster migrating the iPrint cluster resource from NetWare to Linux is not an option. You create a new pool cluster resource on an OES node that will be the iPrint cluster resource on Linux. To set up iPrint on each server, you move the iPrint configuration information from the default Linux installation path on each node to the newly created shared NSS pool resource. Later, you will move the iPrint Driver Store and Print Manager information from the NetWare resource to the OES resource.
In a web browser, open iManager, then use the Storage role to create a new shared pool and volume on one of the OES servers where iPrint is installed.
This is the iPrint cluster resource that will contain the iPrint data.
For information about creating a clustered NSS pool and volume, see Creating Cluster-Enabled Pools and Volumes
in the OES 2018 SP2: OES Cluster Services for Linux Administration Guide.
On the first OES node, set up clustering for iPrint on the shared NSS volume that you created in Step 1.
Log in as the root user to the OES node where the shared pool resource is active, then open a terminal console.
Go to the /opt/novell/iprint/bin directory, then run the iprint_nss_relocate script by entering
./iprint_nss_relocate -a admin_fdn -p admin_password -n nss_volume_path -l cluster [-c <Specify Container FDN where iPrint LUM object already exists or should be created>] [-w <Specify Container FDN where Apache LUM objects exist>]
Replace admin_fdn with the comma-delimited fully distinguished name of the iPrint administrator user (such as cn=admin,o=mycompany). Replace admin_password with the actual password of the specified iPrint administrator user. Replace nss_volume_path with the Linux path (such as /media/nss/NSSVOL1) to the shared NSS volume where you want to relocate the iPrint configuration data.
For information about the script options, see Setting up iPrint on the NSS File System
in the OES 2018 SP2: iPrint Administration Guide.
For example, enter
./iprint_nss_relocate -a cn=admin,o=mycompany -p password -n /media/nss/NSSVOL1 -l cluster -c o=mycompany,t=iPrint_Tree -w o=mycompany,t=iPrint_Tree
Review the messages displayed on the screen to confirm the data migration from the local Linux path to the shared NSS path is completed.
For each remaining Linux node in the cluster where iPrint is installed, set up clustering for iPrint by doing the following:
Log in as the root user to the OES node where the shared pool resource is active, then open a terminal console.
Cluster migrate the shared NSS pool resource from the active OES node to this OES node by entering
cluster migrate resource_name node_name
Log in to the newly active OES node as the root user, then open a terminal console.
Run the iprint_nss_relocate script as described in Step 2.b, using the same values.
Repeat Step 3.a through Step 3.d until all of the OES nodes are configured for iPrint.
In iManager, select iPrint > Create Driver Store, then create a Driver Store on the OES node where the iPrint cluster resource is active.
See Creating a Driver Store
in the OES 2018 SP2: iPrint Administration Guide.
Use the IP or DNS name of the shared NSS pool resource that you created in Preparing the OES Nodes for iPrint as the Target Server. For the eDirectory Server Name, choose an eDirectory server that holds a copy of the replica where the Printer Agents will be created.
In iManager, select iPrint > Create Print Manager, then create a Print Manager on the OES node where the iPrint cluster resource is active.
See Creating a Print Manager
in the OES 2018 SP2: iPrint Administration Guide.
Use the IP or DNS name of the shared NSS pool resource that you created in Preparing the OES Nodes for iPrint as the iPrint Service. For the eDirectory Server Name, choose same server that you specified for the Driver Store. Deselect the Start print manager after creation option.
Configure the Preferred Nodes list for the Linux shared NSS pool cluster resource to prevent an inadvertent failback of the resource to a NetWare server.
In iManager, click Clusters > Cluster Manager, then select the cluster where the Linux shared NSS pool resource is currently active.
Select the link for the OES shared NSS pool cluster resource to open its Properties page.
Go to the Preferred Nodes tab.
Move all of the NetWare nodes from the Assigned Nodes list to Unassigned Nodes list.
Click OK to save your changes.
Edit the load and unload scripts for the OES iPrint cluster resource.
Edit the load script. Add the following lines to the existing load script before the exit 0 statement
ignore_error mv /media/nss/NSSVOL1/var/opt/novell/iprint/iprintgw.lpr /media/nss/NSSVOL1/var/opt/novell/iprint/iprintgw.lpr.bak
NOTE:Replace /media/nss/NSSVOL1 in the above command with your actual cluster volume mount point.
exit_on_error rcnovell-idsd start exit_on_error rcnovell-ipsmd start
The daemons can also be started by using the file path /etc/init.d/novell-idsd start and /etc/init.d/novell-ipsmd start.
Edit the unload script. Add the following lines to the existing unload script after the /opt/novell/ncs/lib/ncsfuncs statement:
ignore_error rcnovell-ipsmd stop ignore_error rcnovell-idsd stop
The daemons can also be stopped by using the file path /etc/init.d/novell-ipsmd stop and /etc/init.d/novell-idsd stop.
Activate the load and unload scripts by taking the resource offline, then bringing the resource online.
Verify that the iPrint cluster resource is working by cluster migrating the OES iPrint cluster resource to each OES node in turn and performing the following checks:
Log in as the root user on the OES node where the iPrint cluster resource is active, then open a terminal console.
Check the status of the Print Manager and Driver Store.
rcnovell-ipsmd status
rcnovell-idsd status
Test the ability of iprntman to authenticate the admin user (or other user given with miggui).
iprntman psm -l -u admin
Cluster migrate the iPrint cluster resource to another OES node by entering
cluster migrate resource_name node_name
Repeat this check for each OES node in the mixed-mode cluster.