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 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.
Install the MarkNet Utilities by placing the Utilities diskette in the diskette drive and entering:
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)
The steps are:
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
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
* 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
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
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.
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.
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.
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.
The following special queue names are defined on the MarkNet XLe for lpr/lpd printing.
There is limited setup protocol available by telnetting to port 9000 and following instructions on the MarkNet XLe.
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) |
psroff -man /usr/lpp/lap/man/*.man
| 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 |
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 ControlIf 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:
| 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. |
| 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. |
[ Doc Ref: 92031899117586 Publish Date: Mar. 28, 2000 4FAX Ref: 6426 ]