SUMMARY: Multiple jetadmin print servers

From: Young, Jim x3125 (
Date: Wed Jun 25 1997 - 16:01:01 CDT

Thanks to: (Rick von Richter) (Steve Snodgrass) (Glenn Satchell) (John Stoffel)
The questions:
> Managers,
> We currently have as a print server a SPARC 10 w Solaris 2.5.1 and
> jetadmin software. I would like to reduce our dependence on this
> as a print server. Can I create a 2nd print server on another system
> with causing conflict with the first?
> If so, how would I identify the printers and properly route requests
> through one server or the other?
> Thanks
For my situation, the 3 most useful summaries are:
No problem, I have 12 Sparc stations (2.5.1), which support about 400
users, and
about 85 printers. Two of the sparcstations are jetadmin servers and
the other
10 are clients. The two jetadmin servers are set up identically and
five of the
clients send their requests to one server and the other 5 to the other
This is the line I use to set up a printer for a client;

lpadmin -p <printer> -s printserver1 -I any -D "<desc>"
lpadmin -p <printer> -s printserver2 -I any -D "<desc>"

In my hosts file for the two printservers I added the aliases
printserver1 &
printserver2 to the entries for my two print servers; Example; starfire printserver1 # Sparc 20 Jet Admin Printserver #1 sunfire printserver2 # Sparc 20 Jet Admin Printserver #2

Then if one of the printservers goes down, all I have to do is go into
the host
file and move the alias to the other printserver. No reconfiguration
on the clients. Example: printserver1 goes down. I would modify my
hostfile to
look like this:

# starfire printserver1 # Sparc 20 Jet Admin Printserver #1
(down) sunfire printserver1 printserver2 # Sparc 20 Jet Admin
Printserver #2

The clients will keep on printing but just redirected their jobs to a
printserver and I had to change only one line.
FROM Glenn
This is easily done. Just install the jetadmin software on the second
system, make sure that you use the same print queue name(s). In your
DNS / NIS / NIS+ setup define an alias called printhost (or whatever
you like) for one of these systems. All your print clients then spool
their requests to the remote system 'printhost'. If this system fails
then redefine the alias for printhost to be the other system with
jetadmin installed and print requests should start going via the new

Alternatively, you could just get half the systems to spool to the
second system. Only one will be able to talk to the printer at a time
so the software will just back off and retry the connection until it
gets through should bopth try and print at the same time.
FROM Steve:
This should work fine. Here at FORE, we have a pair of identical print
servers each running Solaris, JetAdmin, and Samba, and I will probably
bring up a third. If one server is talking to a printer, the other one
just wait until its done and the connection becomes available. This is
assuming you are running a recent version of JetAdmin, some ancient
(the B.* series) started daemons that opened permanent connections to
printers, so you couldn't use multiple servers.

You could even potentially load-balance the servers by using round robin
but we are not doing this because most of our access comes through
Samba, and
unfortunately NetBIOS naming doesn't lend itself to load sharing like
James Young, as of 30 June, 1997 at

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:58 CDT