After you have created a Broker and Print Manager, you must complete the following configuration tasks:
Load and unload scripts are required by Novell Cluster Services to start and stop iPrint and mount the print volume on servers in the cluster. Use the default timeout value on the Scripts page.
To configure the print volume load and unload scripts:
In iManager, click Clusters > Cluster Options.
Browse to and select the Cluster you want to manage.
Select the check box of the Print Cluster object you want to modify, and then click the Properties link under Cluster Objects heading > Scripts.
Click the Load Script tab on the property page and add the following lines to the end of the load script.
load broker .broker_name.broker_context /allowdup load ndpsm .manager_name.manager_context /dbvolume=nocheck /dnsname=print_service_dns
Replace broker_name and broker_context with the Broker object's name and context; replace the manager_name and manager_context with the Print Manager's name and context; replace secondary_cluster_address with the IP address assigned to the cluster-enabled volume.
The /allowdup command line switch instructs the Broker to avoid its check for duplicate Brokers at start-up. Because Novell Cluster Services ensures that only one Broker NLM runs and references the same eDirectory Broker configuration object at a time, this option allows the Broker to start faster without human intervention by avoiding a communication timeout.
The /dbvolume=nocheck command line switch instructs the Print Manager to avoid checking whether its database volume is local or remote. This switch allows the Print Manager to simply open the cluster volume identified in its eDirectory configuration object.
The /dnsname command line switch assigns a DNS name for the print service to the Print Manager. When the print service fails over to another node, the DNS name for the print service also moves to the new node.
NOTE:In prior releases the /ipaddress option was recommended and is still a valid option; however, if the IP address was ever changed, installed printers could no longer print. We recommend you use the /dnsname option.
Example Load Script:
nss /poolactivate=IPP mount IPP VOLID=254 CLUSTER CVSBIND ADD IPP_CLUST_IPP_SERVER 192.168.1.75 NUDP ADD IPP_CLUST_IPP_SERVER 192.168.1.75 add secondary ipaddress 192.168.1.75 load broker .broker1.print.novell /allowdup load ndpsm .psm1.print.novell /dbvolume=nocheck /dnsname=printing.novell.com
Click Unload Script and add the following lines to the beginning of the unload script to dismount the print volume from a server. In addition, add the following lines to the
UNLOAD NDPSM UNLOAD BROKER
Example Unload Script:
unload ndpsm unload broker del secondary ipaddress 192.168.1.75 CLUSTER CVSBIND DEL IPP_CLUST_IPP_SERVER 192.168.1.75 NUDP DEL IPP_CLUST_IPP_SERVER 192.168.1.75 nss /pooldeactivate=IPP /overridetype=question
Novell Cluster Services by default assigns the print volume resource to all nodes in the cluster. The order of assignment is the order the nodes appear in the resource list. To view or edit the print volume resource node assignments or change the server failover order, do the following:
In iManager, click Clusters > Cluster Options the print volume resource object and select Properties.
Browse to and select the Cluster you want to manage.
Select the check box of the Print Cluster object you want to modify, and then click the Properties link under Cluster Objects heading.
Enable the Ignore Quorum by selecting the check box because you want print to be launched immediately on any server in the Assigned nodes list as soon as any server in the list in brought online.
View the current Preferred Nodes assignments, and if necessary, click the right or left arrow button to assign or unassign servers to the print volume resource.
You can click the up or down arrow button to change the failover order of the servers assigned to the print volume.
IMPORTANT:In order for the Broker to load and enable the Resource Management Service properly, you must ensure that the IP address of the print pool is added to the \etc\hosts file of each server in the cluster that will host the print volume.
Use a text editor to open the hosts file, and if necessary, add the IP address you assigned to the print pool resource when you cluster-enabled it.
For example, if the print cluster volume is named cluster_printpool_server and the IP address for that cluster volume is 192.168.1.70, you would add the following line:
192.168.1.70 cluster_printpool_server
Novell Cluster Services by default sets the print cluster volume Start Mode and Failover Mode to Auto, and the Failback Mode to Disable. If the print volume Start Mode is set to Auto, iPrint automatically starts on a server when the cluster is first brought up. If the print volume Start Mode is set to Manual, you must manually start print on a server when you want, instead of having it automatically start when servers in the cluster are brought up.
If the print volume Failover Mode is set to Auto, iPrint automatically starts on the next server in the Assigned Nodes list in the event of a hardware or software failure. If the print volume Failover Mode is set to Manual, you can intervene after a failure occurs and before iPrint is moved to another node.
If the print volume Failback Mode is set to Disable, iPrint will not fail back to its most preferred node when the most preferred node rejoins the cluster. If the print volume Failback Mode is set to Auto, iPrint will automatically fail back to its most preferred node when the most preferred node rejoins the cluster. Generally, you want a failback to a preferred node to occur after business hours.You can set the print volume Failback Mode to Manual to prevent iPrint from moving back to its preferred node when that node is brought back online, until you are ready to allow it to happen.
IMPORTANT:We recommend you use the default settings for Start, Failover and Failback modes.
To view or change the print volume Start, Failover, and Failback modes:
In iManager, click Clusters > Cluster Options the print volume resource object and select Properties.
Browse to and select the Cluster you want to manage.
Select the check box of the Print Cluster object you want to modify, and then click the Properties link under Cluster Objects heading.
The Failover and Failback modes are displayed.
If you are using the default iPrint configurations or are embedding URLs in your iPrint Web pages, you need to be aware of the following:
Links to the default iPrint Printer List Web page or other custom pages in \ippdocs should use the DNS name of the print service. This address moves with the volume to other servers in the cluster during a failover. If you use the cluster's master IP address or the server's primary DNS name or IP Address, after a failover the Printer List might display blank or give an error.
If you are using custom map files that are saved in sys:\apache2\htdocs\ippdocs\images\maps, you must copy the maps to each file server in the cluster that is hosting iPrint. This will make the maps available if a failover occurs.
When adding drivers to Resource Management Service, make sure that the files in the ndps\resdir directory are not flagged as read-only. This is not an issue when copying the \resdir to sys:; however, if you extract the files from .zip files on a CD, the directories might be flagged read-only.