APPENDIX G:

FIXING "FAULTED" PRINTERS (2)

Please see my notes at the end.


Name: Craig Ouellette    4/29/1999

Q. At V4.3/6.1 printer is marked at faulted on Remote client box but will 
print fine (printscreen, lp etc) from the box hosting the printer. 
The following error is seen in the lpstat -t command:

  printer LP04 faulted.  enabled since Fri April 16 12:52:33 GMT 1999.  
  system not responding.

A. Remote printers hosted by 50 series boxes are defined as system printers 
using the lpsystem command with a protocol type of "s5". The box hosting 
the printer has a listen process which has an "s5" channel and a "bsd" 
channel.  The remote box (client) will use lpNet to communicate with the
listen process using either "s5" or "bsd" protocol. The "s5" channel appears 
to go to sleep.

Use the lpsystem command to change the protocol type of the box hosting 
the printer.  

1. Go to the client box which has the remote printer marked as faulted.
2. Turn the scheduler off:   /usr/lib/lpshut
3. Change the protocol type for remote host (not hosting printer)
   Example:   AW5101 has LP01 marked as faulted. LP01 is hosted by AW5102. 
   Run lpsystem on the client box (AW5101)
      lpsystem -t bsd AW5102
      /usr/lib/lpsched
      accept LP01
      enable LP01

Notes:   On AWs and APs when the OS is installed a script is run called 
upd_padmin which installs printers and creates a file in /usr/tmp called 
padmin.ia.  
The file padmin.ia will be run via foxboro.local every time the box is 
REBOOTED!.  If lpsystem commands are run to change the protocol type from 
"s5" to "bsd" the 'padmin.ia' will change the protocol type back to "s5".  
There is no 'padmin.ia' script on WPs. 

In order to avoid the above problem do the following:

1. Edit /usr/tmp/padmin.ia and replace "s5" with "bsd"

	vi /usr/tmp/padmin.ia
	:g/s5/s//bsd/
	:wq

2. Edit the 'upd_padmin' script so that future installs of the OS don't create
   a new padmin.ia with bsd commands.

	cd /opt/fox/[OSNAME]/install    

  Where [OSNAME] is:
             OS6AW1 (AW51)   
             OS6AW2 (AW51I)
             OS5AW1 (AW50)
             OS6FS1 (AP51)   
             OS6FS2 (AP51I)
             OS5FS1 (AP50)
             OS6GC1 (WP51)
             OS5GC1)(WP50)

	vi upd_padmin
	:g/s5/s//bsd/
	:wq

Whenever you issue the "lpsystem -t" command to change the protocol type, the file "/etc/lp/Systems" will be modified.

This is an ascii file you can check to see the current protocols assigned to each printer (from this station). See below a sample of the last part of this file.

+:x:-:s5:-:n:10:-:-:Allow all connections

LP10:x:-:bsd:-:n:10:-:-:
3AWD01:x:-:bsd:-:n:10:-:-:

LP14:x:-:bsd:-:n:10:-:-:
3AWDI1:x:-:bsd:-:n:10:-:-:

LP12:x:-:bsd:-:n:10:-:-:
3AWE01:x:-:bsd:-:n:10:-:-:

LP16:x:-:bsd:-:n:10:-:-:
3WPB01:x:-:bsd:-:n:10:-:-:

LP22:x:-:bsd:-:n:10:-:-:
4AWB01:x:-:bsd:-:n:10:-:-:

NOTE: Even when "padmin.ia" does not exist on WP51s doesn't mean it will loose the protocols assignments after reboot because the "/etc/lp/Systems" file has them.

1