AIX Printer Tips: Lexmark MarkNet XLe Adapter 4033 and Internal
NetWorkCards
AIX Printer Tips: Lexmark MarkNet XLe Adapter 4033 and Internal NetWorkCards
Contents
The information in this document applies to AIX Versions 3.2 through 4.x.
The MarkNet adapter is the network print server from Lexmark.
This adapter has origins in the IBM 4033 network print server, but contains
many enhancements. The MarkNet protocol is supported in both
internal cards that fit in Lexmark printers, and in external boxes which
can be utilized with any parallel printer. The current models support
three basic print conventions.
-
Lexmark protocol that writes to MAC address
-
LPD protocol that writes to a TCP/IP address
-
Lexmark adapters accept print requests to a socket (this allows them
to be used with HP JetDirect backends)
In addition to the software for printing using these adapters, Lexmark
also provides print management software that can be used to determine paper
and other print status. This software is called MarkVision
and is available from Lexmark.
Problems and Differences With Older Adapters
Older 4033 adapters do not support the lpd protocol. New adapters can
have more than one host attached at once, but older adapters cannot. The
MarkNet software supports all Lexmark adapters and cards.
Differences in models:
-
The model 4033-301 allows two parallel printers and one serial printer.
-
The model 4033-302 allows only two parallel printers.
Hardware setup is described in detail in the MarkNet XLe Setup and Service manual
(SA40-0821-01). Basically, the adapter is attached to the network and to
one or two printers. If the network is active two solid lights will show
at this time. These are the power and status lights. Check the printer
setup by pushing the TEST button until the Test light comes on. This will
print the protocol and configuration information to the attached printer.
Virtual printers can be set up using the Lexmark MarkNet utilities that
come with the adapter or that are available over the Internet from Lexmark.
Problems with connecting this adapter are supported by Lexmark, and the
AIX Systems Center will only support the setup of the adapters in local
installations and using the normal AIX protocols. Also see the MarkVision
documentation for more detailed network printer control.
The MarkNet software adds new SMIT menu functions when installed on
AIX. In AIX 4, this is done though a LexLink.attach file in
/usr/lib/lpd/pio/etc.
At AIX 3, the file used ends in .config.
Installing the MarkNet Utilities
Note: Before installing make sure you
have installed bos.dlc.com (DLC). DLC must be installed for
the appropriate adapter.
Install the MarkNet Utilities by placing the Utilities diskette in the
diskette drive and entering:
-
installp -aXd/dev/fd0 all
This should remove any old utilities and install the utilities in in /usr/lpp/lap.
Print and/or read /usr/lpp/lap/README.DOC.
These new adapters install a new series of SMIT screens for managing
MarkNet and IBM 4033 adapters.
In AIX 4, you will see the new option when you add a queue with smitty
mkpq.
In AIX 3.2 when using the command mkvirprt you will now find:
(# is next number in sequence)
-
Printer or Plotter Attached to MarkNet Adapter
Adding a MarkNet Attached Printer at AIX 4
In AIX 4, MarkNet attached printers should be added
with SMIT. The ASCII version or "smitty" will usually work faster.
The steps are:
-
Use the SMIT fastpath: smitty mkpq
-
Choose: LexLink
Printer LAN attached to IBM 4033 or MarkNet Adapter
-
Choose your network type. This will
be like ent0 or tok0.
-
The install program will do a network search for
MarkNet adapters. Choose the adapter from the table. For example:
x # Address
Port Num Status
Description
x
x 0020001A5B00
internal 0 Available 0020001A5B00
Std x
x 10005ABE5AC5
serial 0 Available Airborne Label Printer
4033 x
x 10005ABE5AC5
parallel 1 Available Airborne Label Printer
4033 x
x 10005ABF010D
serial 0 Available 10005abf010d
4033 x
x 10005ABF010D
parallel 1 Associated 10005abf010d
4033 x
x 10005ABF17FC
serial 0 Available PS291480 - 1480 Sec Bay
4033 x
x 10005ABF17FC
parallel 1 Associated PS291480 - 1480 Sec Bay 4033
x
x 10005ABF46F2
serial 0 Associated 10005abf46f2
4033 x
x 10005ABF46F2
parallel 1 Associated 10005abf46f2
4033 x
x [MORE...25]
x
-
Choose printer manufacturer and model. For
example, choose from the list of Lexmark printers if an internal adapter
was chosen:
x
Printer Type
x
x
x
x Move cursor to desired item and
press Enter.
x
x
x
x lex4039+
Lexmark LaserPrinter Plus
x
x lex4047
Lexmark ValueWriter 600
x
x lex4049
Lexmark Optra laser printer
x
x lex4076-2c Lexmark
ExecJet IIc
x
x lex4079+
Lexmark Color Jetprinter Plus
x
x lexOptra+
Lexmark Optra Plus laser printer
x
x lexOptraC
Lexmark Optra C color laser printer
x
x lexOptraE
Lexmark Optra E laser printer
x
x lexOptraN
Lexmark Optra N laser printer
x
-
Fill out the information on the form page.
Key items are the printer language (PostScript or ASCII), the network adapter
address (get this from the printer testpage), the queue name, and whether
the adapter will be used in a shared mode with other print clients.
* Data Stream
Use F4 to select
+
NAME of Queue Device
[i0@tok0-0020001A5B00]
* NAME of Queue to Add
[Enter queue name]
Log File
[]
/
User Id for Intervention Messages
[]
Queuing DISCIPLINE
First Come First Serve +
Print HEADER Pages
Never
+
Print TRAILER Pages
Never
+
Network Type
tok0
Network Address
0020001A5B00
Adapter Type
Std
Force 4033 Association
No
+
Adapter Port
0
Adapter Port Type
internal
Printer Type
lexOptraE
Singlehost / Multihost
M
[BOTTOM]
Repeat for each Data Stream type or special
virtual printer queue
Some options to take special note of are:
-
Log File:
To record all activity of the queue, select a name for the queue log file.
This action is optional, but if present must begin with a '/' and contain
the full path and file name for the log file. Each print job will add an
entry to the log containing a time stamp and file name, along with a copy
of any messages created during the job.
-
User Id for Intervention Messages:
Select an alternate userid to receive Printer Intervention messages. This
action is optional, but allows a printer administrator to be notified of
a printer problem such as being out of paper. By default these messages go to
the system console.
-
Single or Multihost:
This indicated if the adapter can accept jobs from multiple hosts or only
from a single host (S). Adapters that are multihost (M) can have print
queues defined on multiple systems that directly send data to the printer.
Adapter Microcode
Other utilites allow the user to upload microcode to the adapter and look
at detailed adapter information.
Adding a MarkNet Attached Printer at AIX 3.2
The steps are:
-
smit spooler - or - smitty mklanprt
-
Choose: LexLink LAN Attached Printers (MarkNet and IBM 4033 Adapters)
-
The new items on this menu are:
-
Change / Show Characteristics of a MarkNet or IBM 4033 Adapter
-
Add a Virtual Printer (MarkNet or IBM 4033 Attached)
-
Change / Show Characteristics of a Virtual Printer
-
Remove a Printer
-
Update MarkNet Adapter Microcode
-
Show Status of All MarkNet Adapters
-
Show Vital Product Data of a MarkNet Adapter
-
Select: Add a Virtual Printer (MarkNet or IBM 4033 Attached)
-
Select: Network Type - tok0 or ent0.
-
Choose: Adapter Port - Note that both ports on adapter will be listed.
-
0020000347B1 parallel 1 Available 0020000347b1 XLe
-
0020000347B1 parallel 2 Available 0020000347b1 XLe
-
Select: Printer / Plotter Type
-
Hit enter to create the queue.
The selection screen is somewhat different from old screens and looks like
this:
Network Printer Configuration
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Data Stream pcl
* NAME of Queue to Add [mnet]
Log File [/var/spool/lpd/mnet.log]
User Id for Intervention Messages [root]
Queuing DISCIPLINE First Come First Serve
Print HEADER Pages Never
Print TRAILER Pages Never
Network Type tok0
Network Address 0020000347B1
Adapter Type XLe
Force 4033 Association No
Adapter Port 1
Adapter Port Type parallel
Printer Type hplj-3
Singlehost / Multihost M
Some options to take special note of are:
- Log File:
To record all activity of the queue, select a name for the queue log file.
This action is optional, but if present must begin with a '/' and contain
the full path and file name for the log file. Each print job will add an
entry to the log containing a time stamp and file name, along with a copy
of any messages created during the job.
-
User ID for Intervention Messages:
Select an alternate userid to receive Printer Intervention messages. This
action is optional, but allows a printer administrator to be notified of
a printer problem such as being out of paper. By default these messages go to
the system console.
-
Single or Multihost:
This indicated if the adapter can accept jobs from multiple hosts or only
from a single host (S). Adapters that are multihost (M) can have print
queues defined on multiple systems that directly send data to the printer.
Adapter Microcode
Other utilites allow the user to upload microcode to the adapter and look
at detailed adapter information.
Verifying Queue Installation
-
Print to the queue
-
Check the status of the queue
-
lpstat -vmnet
-
mnet p1@to READY
-
Show the queue information
-
lsque -q mnet
-
mnet:
device = p1@tok0-0020000347B1
discipline = fcfs
-
Show the queue device information
-
lsquedev -q mnet -d p1@tok0-0020000347B1
-
p1@tok0-0020000347B1:
file = /var/spool/lpd/pio/dev/p1@tok0-0020000347B1
header = never
trailer = never
backend = /usr/lpp/lap/lpabe -A XLe -n 0020000347B1 -T tok0 \
-a 1 -t p -h M -W 0 -END
Objective
Describe how to set up printing from AIX to
the Lexmark MarkNet XLe Adapter.
Overview
The MarkNet Adapter can be attached to AIX using the
TCP/IP protocol. Since this is an external adapter, the TCP/IP internet
address must be assigned using the bootbd utility in AIX. Once this is
done, the printer can be printed to using standard lpr/lpd protocol (set up
as a remote printer).
Caveat
Attaching the MarkNet adapter as a remote queue
as described here has a drawback: if the adapter is busy when AIX goes to
print, very often the queue will go down. This problem does not occur
when added with the LexLink protocol or even when added as an HP JetDirect
device.
Setup
You must install this as root user.
STEP 1: Install Hardware
STEP 2: Set Up Bootp Download of the IP Address
If this is an integrated network adapter, set the IP address from the front
panel. If the Box already has a TCP/IP address, you can telnet to the box
to make adjustments to the network parameters.
-
Add the name and IP address to be assigned to the marknet box to
the /etc/hosts file. This example uses:
-
Add a line to the /etc/bootptab file to enable bootp setup for this
device. For example:
-
mnetf1:ht=tr:ha=0020000347B1:ip=9.19.169.91:sm=255.255.255.000:gw= 9.19.169.12:
-
mnetf1 is the name of the adapter.
-
ht is the hardware type. Use ether for ethernet & tr for token ring.
-
ha is the hardware address printed on the MarkNet box and also printed
out on the test page in STEP 1 above.
-
ip is the ip address name to assign to the adapter.
-
sm is the subnet mask.
-
gw is the network gateway, needed for routers and so on.
-
Make sure the inetd is running the tftpd and bootpd. This can be
done by looking at the /etc/inetd.conf file and making sure that
the '#' character is not in the front of the line for either of these services.
Once this character is removed, run inetimp and refresh -s inetd
to make the services active.
-
Turn off and on the MarkNet box.
-
Push the TEST button on the MarkNet box until the test light comes
on. This will now print out the information which should now contain the
assigned ip address.
-
Ping the MarkNet box. You should also be able to ping the address
at this time. If you cannot ping the address and it does not show up on
the test page, proceed to the debug section at the end of this document.
STEP 3:
Set up the remote print queue
The MarkNet supports an LPD protocol, but it is not as full function as
a UNIX system might be. Therefore, it is highly recommended that you set up your
printers using the Lexmark MarkNet protocol. However, if you must use lpd/lpr
protocol, simply set up as an AIX remote print queue. There is some chance
of problems with large jobs.
The following special queue names are defined on the MarkNet XLe
for lpr/lpd printing.
-
printer_cr Sends print jobs to parallel port 1 with cr added.
-
printer Sends print jobs to parallel port 1.
-
printer2_cr Sends print jobs to parallel port 2 with cr added.
-
printer2 Sends print jobs to parallel port 2.
-
printer9_cr Sends print jobs to serial port with cr added.
-
printer9 Sends print jobs to serial port.
Adding a Remote Queue at AIX 3.2.5
Provides no local formatting.
-
smitty spooler
-
Choose: Manage Remote Printer Subsystem
-
Choose: Client Services
-
Choose: Remote Printer Queues
-
Choose: Add a Remote Queue
-
Fill in the following:
-
NAME of queue to add: This is name you will print to.
-
DESTINATION HOST for remote jobs: This is HOSTNAME of NETque.
-
Pathname of the SHORT FORM FILTER: Use /usr/lpd/bsdshort
-
Pathname of the LONG FORM FILTER: Use /usr/lpd/bsdlong
-
Name of QUEUE on remote printer: Use printer_cr
-
NAME of device to add: Use netqd
-
Hit enter or Do to add the queue.
Adding a Remote Queue at AIX 4
-
smitty mkpq
-
Choose: remote Printer Attached to Remote Host
-
Choose: Local filtering before sending to print server
-
Choose: Printer manuf.
-
Choose: Printer model
-
Enter the following items:
-
Names of NEW print queues to add: Fill in as needed. These are the queues
that you will print to with lpr, lp, enq or qprt.
-
HOSTNAME of remote server: This is HOSTNAME of NETque.
-
Name of QUEUE on remote server: Use printer
-
TYPE of print spooler on remote server: BSD
-
Send PASS-THROUGH FLAG to queue: Choose 'no'
-
Hit enter or Do to add the queue.
This adapter ignores control files sent to it. Therefore, options contained
in the control file do not work such as banner page, indentation, mail
response, pitch, and so on do not work. Use the virtual printer method to add
these.
There is limited setup protocol available by telnetting to port 9000
and following instructions on the MarkNet XLe.
Printing With TFTP
You can use TFTP to send a job to the printer as if sending it to another
host. This is slower than FTP and not generally supported in the AIX queueing and spooling
system. MarkNet XLe adapters recognize these destinations:
-
/prt1 = parallel 1
-
/prt2 = parallel 2
-
/ser or /prt9 = serial
From tftp send a file like:
-
tftp>put <printfile> /prt0
Debugging bootpd Setup
-
Insert a # in the bootpd line in /etc/inetd.conf
-
run inetimp
-
refresh -s inetd.
-
ps -ef | grep boot. See if bootpd is still running.
If it is kill it with 'kill -9 pid#'.
-
Now start bootpd in debug mode.
bootpd -d -d -d -d -s &
This will show the boot requests as they come to the server. Look for
the wrong hardware address, or packets that are not being returned. Also
look for the wrong ip address for the gateway, or a bad subnet mask.
Example output from good boot:
-
bootpd: bootptab mtime is Sat Sep 23 10:56:10 1995
-
ddr = 9.request from hardware address 0020000347B1
-
bootpd: found 9.19.169.91 mnetf1
-
bootpd: vendor magic field is 99.130.83.99
-
ddr - 9.unsigned char bp_vend[64];
-
99.130.83.99.1.4.255.255.255.128.3.4.9.19.143.10.255.0.0....y
bp->bp_cia
-
ddr = 9.19.169.91 dre
-
bootpd: bp->bp_siaddr = 9.19.129.12
-
bootpd: bp-?bp_giaddr - 9.19.143.10
-
bootpd: Dats all folks...
Some Hints, Tips, and FAQs
-
With the 4033, the MAC address is associated with a machine. If
the 4033 queue is added from another system, the address becomes
associated
with the new machine, but dissociated with the original machine.
The 4033 can only be associated with one host at a time. The original
host can regain the association in two ways:
-
Removing and readding the queue
-
Running /usr/lpp/lap/splpa -c
-
Creating a trace file.
-
See /usr/lpp/lap/traces/README.TRACES
-
If system dies while running, you may need to remove a lock from
-
/usr/lpp/lap/locks
-
Permissions on this directory should be drwxrwxrwx.
The most recent information on the MarkNet Utilities is
in /usr/lpp/lap/README.DOC
The programs that are associated with the MarkNet software are:
Lexmark Programs
|
| Program |
Description |
| catlpabe |
Program that actually sends data to the MarkNet adapter |
| catlpabe3 |
Program that actually sends data to the MarkNet XLe adapter |
| chlanprt |
Either calls splpa3 or acts as SMIT fastpath |
| lslanprt |
Lists network adapters and their status |
| lpabe |
AIX Printer Backend, calls piobe & catlpabe |
| mklanprt |
Program to create new connections |
| rmlandev |
Program to remove existing connections |
| rmlanprt |
Program to remove existing queues |
| splpa, (splpa3) |
configures network adapters (XLe) |
| updlanprt, (updlanprt3) |
Program to update adapter firmware (XLe) |
The man pages for most of these programs are found in
/usr/lpp/lap/man.
To
print a man page use the command:
psroff -man /usr/lpp/lap/man/*.man
Optional lpabe Flags
When you add a queue, the mklanprt program adds the mandatory flags as
described in the readme file. However there are other flags that can be
added for diagnostic or other reasons. These flags are:
| Flag |
Description |
Example |
| -l <full_path> |
Log queue activity |
-l /var/spool/log/print1.log |
| -D |
Enable creation of trace file |
-D |
| -M <message_id> |
Id of user to get intervention messages
From catlpabe usually sent to console |
-M hotstuff@sizzle |
| -U <SAP number> |
User Defined SAP number, See readme |
-U 36 |
| -w # |
Seconds to wait for continue |
-w 20 |
| -W # |
Minutes to wait for flush |
-W 1 |
| -b <custom backend> |
Add a custom formatter to replace piobe |
-b /usr/local/bin/myformat |
Where to Get Software and Support
Network Communications Method
Note: DLC (bos.dlc.com) must be installed for the appropriate adapter.
All modules in this subsystem use the AIX version 3 data link control
interface to communicate with the selected network adapter. The dlc interface,
also known as logical link control (llc), is an IEEE 802.2 compliant network
communications interface which provides a standard medium for communications
to either the IEEE 802.5 Token-Ring network driver or the IEEE 802.3 Ethernet
network driver. This method allows LexLink to co-exist with other network
communications software, such as TCP/IP, SNA, X25, NETBIOS and Novell NETWARE.
However, there may be communications packages that cannot co-exist with
the AIX dlc interface.
The AIX dlc interface manages the network using SAP 0. If you experience
problems using these utilities with other network communications software,
make sure that the software is not trying to manage the network using SAP
0 as well. Only one software package can manage the network using SAP 0.
To see if dlc is installed on your system try:
lslpp -l | grep dlc
or
lslpp -h bos.dlc.*
The response should be (or similar to):
bos.dlc.8023 4.2.1.0 COMMITTED IEEE Ethernet (802.3) Data
bos.dlc.com 4.2.1.0 COMMITTED Common Data Link Control files
bos.dlc.com_enet 4.2.0.0 COMMITTED Common Ethernet Data Link
bos.dlc.ether 4.2.1.0 COMMITTED Standard Ethernet Data Link
bos.dlc.fddi 4.2.1.0 COMMITTED FDDI Data Link Control
bos.dlc.qllc 4.2.1.0 COMMITTED X.25 QLLC Data Link Control
bos.dlc.sdlc 4.2.1.0 COMMITTED SDLC Data Link Control
bos.dlc.token 4.2.1.0 COMMITTED Token-Ring Data Link Control
If the message "Error opening device manager" is received, make sure that
the network specified with the -T flag is available. Use the lsdev -C -l
<network> command to verify that the network is available. Typical
network names are tok0 for Token-Ring and ent0 for Ethernet.
NOTE: If network type is not specified with lslanprt or splpa,
the default is tok0. catlpabe does not have a default.
The Network Printer Utilities use network Service Access Points (SAP)
to access the network. Each command is a stand-alone utility. Since no
daemon is used as a common access point to the network, two or more modules
may try to use the same SAP. Usually this is not a problem. If a SAP is
in use, the utility will simply select a different one. However, this will
cause an entry in the AIX error log which should be ignored.
You can assign unique SAP numbers to each queue device by editing the
/etc/qconfig file to add the -U flag to the backend= statement. See documentation
above on lpabe for more information on flags. SAP numbers should be in
the range of 32 to 216 and should be divisible by 4. If the number specified
is invalid or cannot be used, catlpabe selects a different number and no
error message is issued.
NOTE: AIX Version 3 allows up to 32 SAPS to be opened at the
same time. Occasionally, when several commands or print jobs are running,
one of the commands may report an error opening a SAP. Should this occur,
wait a few seconds and retry the command.
If the error log contains communications interface failure errors such
as the following:
-
Could not add element to the DLC ring queue
Increase the number of buffers in the DLC receive queue (the default is
32) as follows:
-
chdev -E -ldlctoken -aqueue_depth=128
-
chdev -E -ldlcether -aqueue_depth=128
Queue Status
Following is a summary of the print queue status messages displayed
by lpstat or enq along with their meaning (in print job order):
| Status |
Description |
| NEW |
The job has been submitted but has not yet been recognized by the printer
backend subsystem. |
| INITING |
The utility is setting up the lockfile. If this status is displayed
for more than a second, then a lockfile problem exists, such as more than
one device name being used for the same printer. |
| CONNECT |
The utility is establishing communications with the network. This should
take less than a second. |
| DEV_WAIT |
The utility is locating the network printer and, if necessary, waiting
for the printer to complete a print job from another host. This status
is also displayed whenever the printer requires intervention such as paper
out, paper jam, toner low, off line, and so on. |
| RUNNING |
The print job is being transferred to the printer. |
| DOWN |
The previous print job could not be completed due to an error. See
the messages provided by the printer backend for details. |
| DEV_BUSY |
The queue or queue device may not be properly configured. Insure the
file listed in /etc/qconfig for the affected queue / device exists. This
status will also be displayed if two queues are configured for the same
queue device and both try to print at the same time. |
| UNKNOWN |
The queue or queue device has been added but not yet recognized
by the qdaemon. |
Other README Files
There are four other README files for this package that provide additional
information. They are located in:
| Directory |
Readme File Description |
| /usr/lpp/lap/dev/ |
describes the contents of the dev directory. |
| /usr/lpp/lap/logs/ |
describes the contents of the logs directory. |
| /usr/lpp/lap/locks/ |
describes the contents of the locks directory. |
| /usr/lpp/lap/traces/ |
describes the contents of the traces directory. |
Lexmark MarkNet XLe Adapter 4033 and Internal NetWorkCards: AIX Printer Tips: marknet.html ITEM: FAX
Dated: 99/03/10~00:00 Category: zap
This HTML file was generated 99/06/24~12:42:10
Comments or suggestions?
Contact us