Printer pooling with HP-UX

[Andy Dye]

I have several printers currently running via serial I/F that are "pooled" using our application software. I need to do this using HP-UX over Ethernet.

Current config - HP9000 K580 10.20, 5 Lexmark 40 ppm printers.

Apparently, I need to use JetDirect to accomplish this through HP-UX.

Will the external print servers (HP JetDirect 300X) accomplish the task?

If so, up to what print speed?

We're planning to replace the printers with faster models and will need faster communication. Currently the 40ppm at 38400 baud is getting close to the serial line speed limit.

[A. Clay Stephenson · Accepted solution]

I think what you are talking about is referred to as a printer "class". The application sends output to the class rather rather a printer and the first available class member is used.

To accomplish this:

1) Add the network printers in the usual way using jetadmin (obsolete JetAdmin software) or hppi (newer JetDirect software).

2) Create a new class:
lpadmin -p myprinter1 -c myclass
Add more printers:
lpadmin -p myprinter2 -c myclass
lpadmin -p myprinter3 -c myclass

You may also need to run accept and enable on the class -- I can't remember off the top of my head.

Finally,

lp -dmyclass file1

rather than
lp -dmyprinter1

Man lpadmin for details.

[Andy Dye]

Will it work with printers that aren't using HP Jetdirect I/F?

I'm getting errors when trying to set these up using hppi.

"incorrect GET community name" when installing through Jetdirect printer installer. The printer is currently running on the network.


Related problem - I just installed the Jetdirect installer (HP10e134.SD) and SAM tells me there is no installer loaded. I can access it directly by running "hppi".

[A. Clay Stephenson]

Forget using SAM, run the hppi command directly. It is interactive and will guide you through adding a printer. If you have hard-set an IP address and subnet using the printer's front panel (or a telnet session) then you don't need to configure bootp/dhcpd to set the printers IP address. You simply invoke hppi, and use option 1) Spoller Administration to add each printer.

Completely unrelated printers can be members of a class. You can group network, remote, and serially connected printers in a class -- even different printer models. Normally, you make the faster printers the first members of the group so that they will preferentially be used.

[Andy Dye]

Yeah, it's working!

Here's what was causing some of my grief:(other than ignorance)

1. The Jetdirect admin complains about setting up a printer that it can't "talk" to. Was able to ping fine. I just had to pick a printer and go with it. Even though it wasn't the type of printer I'm running.

2. The network connection is soooo much faster than serial, I couldn't submit the job fast enough to activate the second printer. (Solution - Opened 2 sessions, typed the command and left it to where I just needed to press to get them to go more quickly.)


Thanks for the help.

btw - You do need to "accept printerclass"