Printer Class Problems

[Mark A. Nordman]

I am trying to setup redundant print servers to provide "increased availability" for print clients.

The basic technique I'm using is this -

1) On print server 1 (prtsrv1), add a network-based JetDirect printer (netprt). This has been done and works fine.

2) On print server 2 (prtsrv2), independently add the same nework-based printer as in step1 (netprt). This has been done and works fine.

3) On the print client (prtcli), add a remote printer (netprt1) which sends print requests to "netprt" on "prtsrv1". This has been done and works fine.

4) On the same print client (prtcli), add a second remote printer (netprt2) which sends print requests to "netprt" on "prtsrv2". This has been done and works fine.

5) On the same print client (prtcli), add "netprt1" and "netprt2" to the printer class "netprtc". This has been done but does not work.

Before step 5, print requests submitted on "prtcli" to remote printer "netprt1", or remote printer "netprt2", print successfully.

After performing step 5, print requests submitted on "prtcli" to the printer class "netprtc" cause both remote printers "netprt1" and "netprt2" to become disabled (down).

I would be very interested in the assessments of others who have had experience with printer classes.

[Alan Riggs · Accepted solution]

From "man lpadm"

'classes must not include remote printers. HP-UX systems do not have the ability to distribute print jobs in this way.'

You can create a class on a print server and access the class class through a remote queue, but that does not accomplish your apparent goal of having the local queue address two separate print servers through a single class. I am not at all sure that this is possible. I do know I have never seen it.

[Mark A. Nordman]

Right you are. I should have read the whole lpadmin man page. As you have noted, the WARNING section clearly states "classes must not contain remote printers". Thanks for your help.