Contents
Installation and ConfigurationHP JetAdmin Utility for UNIX
|
Contents Overview
Status Monitors
Using a Network Printer
Before You Configure the Printer
Requirements
2 HP Support for UNIX (HP-UX, SunOS, and Solaris) Networks
Introduction
Installation and Configuration Requirements
Running the HP JetAdmin Software
Configuring the HP JetDirect Print Server
Using BOOTP/TFTP
Using RARP
Using Telnet
Telnet Configuration Parameter Examples
DHCP Configuration 2
Using the Printer Control Panel
Configuring the Host Spooler
Adding a Network Print Queue from the Local Spooler
Modifying the Existing Network Print
Queue from the Local Spooler
Deleting a Network Print Queue
from the Local Spooler
Removing Printers from HP-UX, SunOS, and
Solaris Networks
Deleting a Network Print Queue from the
Local Spooler
Removing the Printer from the BOOTP Server
Moving to Another Network
Running the HP JetPrint Software
3 Troubleshooting
Overview
HP-UX, SunOS, and Solaris Checklist
Verifying the Host Software Installation
Verifying the Network Configuration Data
Verifying the Communication Path
Verifying Spooler Configuration
Troubleshooting an LPD Configuration
4 Trademark Credits and Warranty
This Software Update Notice describes how to install and configure the software for HP product JD300EN.
This software provides a TCP/IP based solution for
configuring and managing the HP JetDirect print server on the
following systems:
This software provides full printer feature support, graphical job and printer monitors, management features, and diagnostic features. The supported features may vary for different HP JetDirect print servers, different printers, and different operating systems.
For command line lp users, the product provides enhanced features in the supplied model scripts for HP printers (for example, net_lj5x), with several option flags. These model scripts apply only to HP-UX and Solaris systems.
The type of printer and print server you have affects the network reporting capability of the HP JetAdmin utility for UNIX systems. Some printers, such as the HP LaserJet 5Si, are capable of reporting a greater variety of printer statistics than earlier printer models. In the same way, HP JetDirect internal print servers using modular input/output (MIO) specifications allow the software to report more network statistics than print servers using other specifications, such as extended input/output (XIO).
The following table shows examples of internal print
servers that use MIO specifications and XIO specifications, and
external print servers that use parallel specifications (EX, EX
Plus, and EX Plus3). See your printer and print server manuals
for guidance on their reporting capabilities.
| Table 1-1
HP JetDirect Print Servers That Use UNIX Software | ||
| HP JetDirect Product | Network Connector Type | Printer I/O Configuration |
| J2550A | RJ-45 (Ethernet) | MIO |
| J2552A | RJ-45, BNC, (Ethernet) and 8-pin mini-DIN (LocalTalk) | MIO |
| J2555A | DB9 and RJ-45 (Token Ring) | MIO |
| J2371A | RJ-45 (Ethernet) | MIO |
| J2372A | RJ-45 and BNC (Ethernet) | MIO |
| J2373A * | DB9 (Token Ring) | MIO |
| J2337A* | RJ-45 and BNC (Ethernet) | MIO |
| J2338A* | RJ-45 and BNC (Ethernet) | MIO |
| J2339A* | RJ-45 and BNC (Ethernet) | MIO |
| J2340A* | RJ-45 and BNC (Ethernet) | MIO |
| C2059T | BNC and AUI (Ethernet) | MIO |
| J2593A | RJ-45, BNC (Ethernet) | EX Plus3 |
| J2594A | DB9 and RJ-45 (Token Ring) | EX Plus3 |
| J2382A* | RJ-45 and BNC (Ethernet) | EX |
| J2383A* | DB9 (Token Ring) | EX |
| J2382B | RJ-45 and BNC (Ethernet) | EX |
| J2383B* | DB9 (Token Ring) | EX |
| C2071S | RJ-45 (Ethernet) | XIO |
| C2071T | BNC (Ethernet) | XIO |
| J2591A | RJ-45 and BNC (Ethernet) | EX Plus3 |
| J2590A | RJ-45 (Ethernet)/100 VG Any LAN | EX Plus3 |
| SIMM Upgrades | ||
| J2546B | Ethernet | MIO |
| J2547B | Ethernet | EX |
| J2548B | Token Ring | EX |
| J2549B | Token Ring | MIO |
| *These products require a Flash SIMM upgrade. | ||
Two X-Windows Motif based graphical status monitors, DeviceMonitor and JobMonitor, provide real-time job and printer status and alert users to error conditions. The status monitors are only available on HP-UX and Solaris systems.
The DeviceMonitor utility provides the ability to monitor printers and to select a printer to monitor through an automatic discovery mechanism. The utility acquires its information by polling the specified printer using the Simple Network Management Protocol (SNMP).
As an SNMP agent, the HP JetDirect print server responds to requests for the standard MIB-II (Management Information Base II) variables that are provided by all systems. The HP JetAdmin utility is able to obtain MIB-II values from the print server over the network.
Depending on which printer you are using, the JobMonitor
utility tracks individual print jobs, reports an actual count
of pages printed, monitors the condition of the printer servicing
the job, and provides the user the option of end-of-job notification
when the last page of the job is placed in the output bin.
Ethernet: LAN HW ADDRESS: 080009xxxxxx
Token Ring: LAN HW ADDRESS: 100090xxxxxx
For HP-UX and Solaris systems, an appropriate model script name is needed for your printer. The HP JetAdmin utility has a default script, which you can change to fit your needs.
The HP JetPrint included with this software is designed to simplify printing for end users on the network by providing a graphical (Motif) interface to the lp command. Some functions are available only if the selected printer or print server supports that function.
Depending on your printer and print server, you can perform the following administrative functions:
For systems running Motif, you can also perform the following functions:
See the man pages, online help, and online README files for more information on the HP JetAdmin software.
The HP JetPrint software is designed to simplify printing for end users on the network by providing a graphical (Motif) front end to the lp command. Some functions are available only if the selected printer or print server supports that function. From the HP JetPrint software, users can perform the following operations:
For a complete listing of HP JetPrint functions,
see the man pages, online help, and online README files. For command
line lp users, the product provides enhanced features in the supplied
model scripts for HP printers (for example, net_lj5x),
with several option flags.
Ethernet: LAN HW ADDRESS: 080009xxxxxx
Token Ring: LAN HW ADDRESS: 100090xxxxxx
If you have not printed a configuration page from your printer, see the hardware installation guide for your print server or your printer's getting started guide for instructions.
HP-UX 9.x and SunOS: Creates the /usr/lib/hpnp directory for HP JetAdmin for UNIX
HP-UX 10.x and Solaris: Creates the /opt/hpnp directory for HP JetAdmin for UNIX
Creates the following subdirectories inside the hpnp directory (contents of subdirectories listed in parentheses):
The HP JetAdmin software helps the administrator configure the print server and the spooling system. To run the HP JetAdmin software from the default paths, type the following. (If you installed HP JetAdmin in a different directory, the paths will be different.)
For HP-UX 9.x and SunOS 4.1.3 and 4.1.4, type:
/usr/lib/hpnp/jetadmin
For HP-UX 10.x and Solaris 2.x, type:
/opt/hpnp/bin/jetadmin
To use HP JetAdmin software in a UNIX based TCP/IP environment, you must first configure the HP JetDirect print server and configure the host spooler.
To operate properly, the HP JetDirect print server must be configured with network configuration data, such as a valid IP address. Depending on your printer and system, this can be done in the following ways:
This section describes how to configure the print server using BOOTP.
If your system uses NIS, you may need to rebuild
the NIS map with the BOOTP service (as shown below) before performing
the BOOTP configuration steps. To rebuild the NIS map for Solaris,
see your Solaris system documentation.
To rebuild the NIS services map for SunOS, first
go to the correct directory by typing: cd /var/yp
Rebuild the map by typing: make services
Verify that the BOOTP service is now present in the map by typing:
ypcat services | grep bootp
There should be an entry for bootps and bootpd displayed.
To determine the process ID (PID) for inetd (internet services
daemon), type:
ps -ef | grep inetd (HP-UX and Solaris)
ps -ax | grep inetd (SunOS only)
Use the PID to signal inetd to re-read its configuration file:
kill -1 <inetd-PID>
where 1 is the number
"one" and <inetd-PID>
is the PID for inetd.
For the HP JetDirect print server to obtain its configuration
data over the network, the BOOTP server must be set up with the
appropriate configuration files. The HP JetAdmin software automatically
creates or edits these files. To set up the configuration files
on the BOOTP server, run the HP JetAdmin software and perform
the following steps:
1. Turn off the printer.
2. Select Configuration
from the Main menu. The Configuration menu appears.
3. Select Create printer configuration in BOOTP/TFTP database.The software interactively prompts you for BOOTP/TFTP configuration parameters listed in Table 2-1, and automatically makes the necessary entries in the appropriate files. Some parameters are optional.
The data that you configure determines which entries and files are created. Some data is intended for the /etc/bootptab file, while other data is placed in a Network Printer Interface (NPI) configuration file.
BOOTP is used by the print server to obtain entries
in the /etc/bootptab file, while
TFTP is used to obtain additional configuration information from
a configuration file. If you do not specify any SNMP configuration
entries, and default values are used for the host access list
and idle timeout, an NPI configuration file is not created.
HP recommends that the BOOTP server be located on the same subnet as the printers it serves. BOOTP broadcast packets may not be forwarded by routers unless they are properly configured.
You can interactively configure the Simple Network Management Protocol (SNMP) parameters. SNMP configuration parameters are listed in Table 2-1, and are optional.
To receive SNMP traps, the systems listed on the SNMP trap destination list must have a trap daemon to listen to those traps. The HP JetAdmin software does not provide such a daemon.
4. After creating the BOOTP/TFTP database, the HP JetAdmin software conducts a BOOTP/TFTP self-test, then prompts you to turn on the printer.
5. Turn on the printer. When it receives power, the HP JetDirect print server sends BOOTP requests and should receive its configuration data from the configured BOOTP server.The HP JetAdmin software tests if the printer is configured by pinging the IP address.
6. Verify that the printer is correctly configured by
typing "y" for the
following prompt:
Do you want to send the test file(s) to this printer (y/n,
default = n)?
| Table 2-1.
Standard Configuration Parameters | |
| LAN Hardware Address: | Link-level, or station address of the HP JetDirect print server. This is a required entry. This address is printed with the card status information as the ''LAN HW ADDRESS'' (see the printer configuration page, also called the self-test page or configuration plot). |
| Name: | Name of the printer. This is a required entry. It should be an IP name assigned by your network administrator. The name must begin with a letter and must end with either a letter or a number. Other characters in the name are limited to letters, numbers, periods, and hyphens. The maximum length is 32 characters. This name is returned when the SNMP sysName is requested. |
| IP Address: | Internet Protocol address used for communication between network nodes. This is a required entry. |
| Subnet Mask: | Mask used when a network is subnetted. This is required only if subnetting is being used. If the subnet mask is not provided, the default network mask is used. |
| Default Gateway: | IP address of the gateway. This information is needed for a printer to respond to a host on a different subnet. Only one default gateway can be configured at a time. |
| Syslog Server: | The IP address of the host that receives syslog messages from the print server. Only one syslog server may be configured. If a syslog server is not configured, the print server does not send syslog messages. |
| Syslog Facility: | Describes the part of the system that generates the syslog messages. This is configured only if a syslog server is configured. The print server can be configured to generate syslog messages with the facilities local 0 through local 7. The default facility is LOG_LPR. |
| Idle Timeout: | The number of seconds that an idle print data connection is allowed to remain open. Since the card supports only a single TCP connection, the idle timeout balances the opportunity of a host to recover or complete a print job against the ability of other hosts to access the printer. The acceptable values range from 0 to 3600 (1 hour). If ''0'' is typed, the timeout mechanism is disabled. The default is 90 seconds. |
| Access List: | Specifies from which hosts or subnets the interface accepts print data connections. It also determines which hosts can use SNMP SetRequests. Up to 10 entries are allowed. If the host access list is empty, the interface accepts connections from all hosts. The default is an empty list. |
| Location: | Identifies the physical location of the printer. Only printable ASCII characters are allowed. The maximum length is 64 characters. The default location is undefined. (Example: 1st floor, south wall) |
| Contact: | Name of the person who administers or services the printer. This may include how to contact this person. The default contact is undefined. |
| SNMP Get Community Name: | Password that allows a host to acquire SNMP information on the HP JetDirect print server. This is optional. If set, the request must supply the correct community name. Otherwise, the HP JetDirect print server does not respond. The HP JetAdmin software automatically saves this name in this BOOTP server's hpnpsnmp file. The community name must be ASCII characters. The maximum length is 32 characters. |
| SNMP Set Community Name: | Password that allows SNMP access to control functions on the HP JetDirect print server. The community name of an incoming SNMP SetRequest must match the print server's "set community name" for the print server to respond. If the print server has no "set community name,'' it does not respond to any SetRequests. SetRequests must come from hosts that are configured in the print server's host access list. Community names must be ASCII characters. The maximum length is 32 characters. |
| SNMP Trap Destination List: | List of IP addresses for systems in which the print server sends SNMP traps. If the list is empty, the print server does not send SNMP traps. The list may contain up to four entries. The default SNMP Trap Destination List is empty. |
| SNMP TrapCommunity Name: | Community name (password) used by the print server when it sends SNMP traps. The default community name is "public." Community names must be ASCII characters. The maximum length is 32 characters. |
| SNMP Authentication Trap: | Configures the print server to send (on) or not send (off) SNMP authentication traps. Authentication traps indicate that an SNMP request was received, but the community name check failed. The default is "off." |
| Telnet: | If set to 1, this parameter instructs the print server not to allow incoming Telnet connections. If this parameter is set to 0, incoming Telnet connections are allowed. (This setting is not available through the HP JetAdmin software.) |
This setup procedure enables the RARP daemon running
on your system to respond to a RARP request from the HP JetDirect
print server and to supply the IP address to the print server.
1. Turn off the printer.
2. Log on to your UNIX system as a superuser.
3. Make sure the RARP daemon is
running on your system by typing the following command at the
system prompt:
ps -ef | grep rarpd (HP-UX and Solaris)
ps -ax | grep rarpd (SunOS only)
The system response should be similar to the following:
861 0.00.2 24 72 5 14:03 0:00 rarpd -a
860 0.00.5 36 140 5 14:03 0:00 rarpd -a
If the system does not display a process number for
the RARP daemon, see the rarpd
man page for instructions on starting the RARP daemon.
4. Edit the /etc/hosts
file to add your designated IP address and node name for the HP
JetDirect print server. For example:
13.32.11.24 laserjet1
5. Edit the /etc/ethers file to add the LAN hardware address/station address (from the configuration page, also called the self-test page or configuration plot) and the node name for the HP JetDirect print server. For example:
08:00:09:a8:b0:00 laserjet1
6. Turn on the printer.
7. To verify that the card is configured with the correct IP address, use the ping utility. At the prompt, type:
ping <IP address>
where <IP address>
is the assigned address from RARP. The default IP address is 192.0.0.192.
If ping does not respond, see the troubleshooting
chapter.
To set configuration parameters, you must set up a Telnet connection from your UNIX system to the HP JetDirect print server.
1. Type the following at the system
prompt:
Telnet <IP address>
where <IP address>
may be the assigned address from BOOTP, RARP, DHCP, the printer
control panel, or the default IP address. The default IP address
is 192.0.0.192.
2. When the server responds connected
to IP address, press [Return] twice to make
sure that the Telnet connection is initialized.
3. When you are prompted for a password,
type the correct password (for example: kfuejs)
By default, Telnet does not require a password, but you can set up to a 14 character password by using the password command (passwd). Once a password is set, password protection is enabled. Subsequently, you can change a password, but you cannot disable password protection unless you perform a cold reset on the printer.
? then press [Return] to view available configuration parameters,
the correct command format, and a list of additional commands
to display or print configuration information that you have typed.
At the Telnet prompt ">" type: parameter:
value then press [Return], where parameter
refers to the configuration parameter you are defining, and value
refers to the definitions you are assigning to that parameter.
Each parameter entry is followed by a carriage return.
See Table 2-1 for information about configuration
parameters.
5. Repeat step 4 to set any additional
configuration parameters.
6. When you have finished typing
the configuration parameters, type: quit and press [Return] to
activate the configuration parameters.
To exit without activating parameters, type exit
and press [Return].
ip: 13.32.11.24
where ip identifies
the parameter and 13.32.11.24
specifies the address for the printer. By typing this parameter,
you can overwrite the IP address used to make the Telnet connection
with one you have selected.
subnet-mask: 255.255.255.0
where subnet-mask
identifies the parameter and 255.255.255.0
specifies the subnet mask.
default-gw: 13.32.11.85
where default-gw
identifies the parameter and 13.32.11.85
specifies the IP address of the gateway.
syslog-server: 13.32.11.85
where syslog-server
identifies the parameter and 13.32.11.85
specifies the IP address of that server.
idle-timeout: 120
where idle-timeout
identifies the parameter and 120 specifies
the number of seconds an idle print data connection is allowed
to remain open. If you set this parameter to 0, the connection
does not terminate and no other host is able to make a connection.
banner: 0
where banner identifies
the parameter and 0 disables the banner page print out. Substitute
1 for 0
to enable the banner page print out.
set-cmnty-name: my_network
where set-cmnty-name
identifies the parameter and my_network
specifies the name you want to set.
The Set Community Name parameter is a network management security mechanism that enables external network management entities to set internal print server management (mib) values. The name can be from 1 to 32 alpha and numeric characters and can include the minus (-) and underscore (_) symbols.
If you do not want your HP JetDirect print server configured via DHCP, you must disable DHCP configuration.
When you disable a DHCP configuration via Telnet,
the print server automatically releases any names and IP addresses
associated with the DHCP server and re-initializes the TCP/IP
protocol for the print server. At this point, the print server
is unconfigured and begins to send bootp and rarp requests to
acquire new (non-DHCP) configuration information.
If you manually provide an IP address when disabling DHCP via Telnet, the print server still releases its DHCP-provided IP address but does not send bootp and rarp configuration requests. Instead, it uses the configuration information you have provided. Therefore, if you provide the IP address you should also manually set all of the configuration parameters, such as subnet mask, default gateway, and idle timeout.
dhcp-config: 1
where dhcp-config:
identifies the Dynamic Host Configuration Protocol and 1 indicates
that this protocol is enabled. This is the default setting. To
disable DHCP, type: dhcp-config: 0
name: <alphanumeric>
This subsection describes how to configure the HP JetDirect print server using the printer's control panel.
If configuration of the HP JetDirect print server
is supported from your printer control panel, you can set the
network configuration parameters listed below. If the printer
control panel configuration is supported, see the hardware installation
guide for your print server or the getting started guide for your
printer for instructions on how to configure the print server
from the printer control panel.
If you need to configure other parameters, use BOOTP/TFTP to configure all the parameters for the print server.
If the HP JetDirect print server is configured to receive its configuration from the printer control panel, the configuration is saved on the print server over power cycles. For information on these parameters see Table 2-1.
Similar to other serial or parallel connected printers, a network printer (represented by its IP address) must be configured to the local spooler before you can access it.
The spooling system is a set of programs, shell scripts,
and directories that control your printers and the flow of data
going to them. This section explains how to use the HP JetAdmin
software to configure your network-based printer into the spooling
system.
To configure a print queue for your network-based
printer into a spooler, follow these steps (type ? for online
help):
1. Run the HP JetAdmin software.
/usr/lib/hpnp/jetadmin
/opt/hpnp/bin/jetadmin
2. Select Configuration from the software's main menu. The Configuration menu appears.
3. Select Add printer
to local spooler.
4. When the following prompt appears:
Enter the network printer name:
type the name of your network printer, which is the
name typed in NIS (Network Information Service), DNS (Domain Name
Service), or /etc/hosts for the
printer. It is the printer's node name.
5. When the HP JetAdmin software
displays a list of configurable parameters, change the parameters
you want to change, then select 0
(zero).
6. Before the software shuts down
the spooler to make configuration changes, it prompts you for
confirmation. Press [Return] for the HP JetAdmin software to shut
down the spooler.
7. At the prompt, press [Return] to display the configuration menu.
The printer should now be configured in your HP-UX,
SunOS, or Solaris spooling system.
You can modify the existing network spool queue using
the HP JetAdmin software.
1. Run the HP JetAdmin software.
/usr/lib/hpnp/jetadmin
/opt/hpnp/bin/jetadmin
2. Select Configuration
from the software's main menu. The Configuration menu appears.
3. Select Modify
existing spooler queue(s) from the software's
Configuration menu.
4. Type the name of the queue you
want to modify.
5. When the HP JetAdmin software displays a list of configurable parameters, change the parameters you want to change, then select 0 (zero).
If necessary, you can delete an existing network spool queue using the HP JetAdmin software.
1. Log on as a superuser.
2. Run the HP JetAdmin software.
/usr/lib/hpnp/jetadmin
/opt/hpnp/bin/jetadmin
3. Select Configuration from the Main menu. The HP JetAdmin for UNIX Configuration menu appears.
4. Select the option for removing the queue.
5.Type the print queue name, then press [Enter]. If there are jobs in this print queue, this operation is aborted.
lpadmin
to remove queues.
The first step in removing a printer from the network is to delete the printer configuration at the server. The printer must not be servicing a job when you do this.
1. Log on as a superuser.
2. Run the HP JetAdmin software.
For HP-UX 9.x and SunOS 4.1.3 and 4.1.4, type:
/usr/lib/hpnp/jetadmin
For HP-UX 10.x and Solaris 2.x , type:
/opt/hpnp/bin/jetadmin
3. Select Configuration from the Main menu. The HP JetAdmin for UNIX Configuration menu appears.
4. Select the option for removing the queue.
5. Type the print queue name, then press [Enter].
6. Repeat steps 4 and 5 for each queue directed toward this printer.
Once the queues are deleted, the printer is removed from the spooler. Continue only if you want to remove the printer from the BOOTP server. If there are jobs in this print queue, this operation is aborted.
1. Log on as a superuser.
2. Run the HP JetAdmin software.
/usr/lib/hpnp/jetadmin
/opt/hpnp/bin/jetadmin
3. Select Configuration from the Main menu. The HP JetAdmin for UNIX Configuration menu appears.
4. Select the option for removing the printer, which is represented as a BOOTP entry.
When moving an HP JetDirect print server that has been configured with an IP address to a new network, make sure that the IP address does not conflict with addresses on the new network. You may change the IP address of the print server to one that can be used on the new network, or erase the current IP address and configure another address after you install the print server on the new network.
If the print server was configured using bootp, remove
the bootp configuration with the HP JetAdmin software. If the
print server was configured with RARP, erase the entry in the
/etc/ethers file.
cold-reset
and press [Return].
quit and press
[Return] to exit Telnet.
When you exit the Telnet session, the IP address is erased.
For HP-UX 9.x, type:
usr/lib/hpnp/bin/jetprint
For HP-UX 10.x and Solaris 2.x, type:
/opt/hpnp/bin/jetprint
For SunOS 4.1.3 and 4.1.4, consult the man pages for the HP JetPrint software.
This chapter describes how to troubleshoot problems you may have configuring the HP JetDirect print server or software.
Error messages are listed in current HP JetDirect product manuals. If an error occurs during installation or operation of the software, see your HP JetDirect print server documentation for information about the message.
If the print server and network hardware appear to be functional, verify that the HP JetAdmin software has been installed correctly.
1. Run the HP JetAdmin software.
2. In the main menu of the HP JetAdmin software, select Diagnostics. The Diagnostics menu appears.
3. Select Examine printing path
to help isolate the source of a print problem. This feature tests
the local spooler operation by sending a file to the printer using
the lp command. Any file may be submitted for this test. Typically,
this test is used to diagnose printing problems with a particular
file. The test first verifies that the local spooler is functional
for a user provided queue. A functional spooler satisfies the
following conditions:
You are prompted for a (test) filename with options. The idea is to re-create the job submittal process but intercept the spooler output. You are then provided the job profile as determined by the spooler output. This displays information such as: resolution setting (optional), number of collated copies requested, and the Printer Description Language (PDL) to be used (PCL, PostScript, or Relay). A non-functional spooler terminates this test and returns you to the Diagnostics menu.
On SunOS 4.1.x, this feature is not supported and
displays only queue status.
4. Select Verify
installation of software to display any
files that are missing or services that are not available.
5. Select Test network printer accessibility to perform the following three operations:
6. Select Print a test page to send a test page directly to the target printer, bypassing the spooler to prove that data can be sent to the printer and printed.
7. Select View HP JetDirect interface's current configuration to display the current configuration settings. The configuration setting can also be printed out and filed for archival purposes.
8. Select Check BOOTP and TFTP operations to verify that the local host's BOOTP and TFTP are functional. This conducts a self-test, simulates a bootup query, and responds. This requires superuser privileges.
9. Select Show HP JetDirect interface's protocol settings to test multi-protocol HP JetDirect print servers. A list of status for each protocol is displayed. The information can be printed and filed for archival or diagnostic purposes.
10. Select Display operational and protocol statistics to display detailed information on network packet transmissions or collisions.
11. On SunOS, check the install
log /tmp/hpnpinstall.log to check
for error or warning messages.
12. If necessary, repeat all of
the steps in Chapter 2, "HP Support for UNIX (HP-UX, SunOS,
and Solaris) Networks," to install and configure the software.
To verify that the HP JetDirect print server contains the correct network configuration data, use the following instructions that correspond to the method you used to configure the print server.
1. Print a configuration page (also called a self-test page or configuration plot) that contains the print server status information.
2. Verify that the following parameters are set correctly:
To change these or other parameters, delete the BOOTP entry and re-create one with the new settings. Then turn the printer off and back on so the printer re-reads the bootp information. For more information, see "Removing the Printer from the BOOTP Server" and "Using BOOTP/TFTP" in Chapter 2.
3. Verify that your BOOTP server
responds to the print server's BOOTP request. Run the HP JetAdmin
software and select Test network printer accessibility
from the Diagnostics menu.If
this test fails, look in your syslog file for messages from the
bootpd daemon program to identify possible causes such as configuration
issues in inetd.sec.
4. On SunOS systems that use NIS, check the NIS services map to make sure BOOTP services are provided.For more information, see the section "Configuring the HP JetDirect Print Server" in Chapter 2.)
1. Make sure the IP address indicated
on the status page and the entry in the /etc/ethers file are the
same.
2. Verify that the RARP daemon on the host responds to RARP requests from your HP JetDirect print server.
For more information on RARP, see the RARP man page on your UNIX host.
1. Print a configuration page (which contains the print server status information).
2. Verify that the following parameters are set correctly:
If you need to correct any of these parameters, see any of the following:
The HP JetAdmin software has a script that uses ping to test the connectivity.
1. Run the HP JetAdmin software
(/usr/lib/hpnp/jetadmin) and
select Test network printer accessibility
from the Diagnostics menu.
2. If the connectivity test fails:
/etc/hosts,
NIS (Network Information Service), or DNS (Domain Name System)
are typed correctly.
3. If the connectivity test succeeds, select Print a simple test page to printer from the Diagnostics menu. Then select an appropriate file type for your printer. This sends a test file to the printer that bypasses the spooler.
This test also uses the hpnpadmin utility to verify
that the host can print to the printer. You can change the host
access list (those hosts that are allowed to print to this printer)
by changing the BOOTP/TFTP print server configuration parameters.
If you are able to print a file on the printer when you bypass the spooler, but you are not able to print through the spooler (using the lp command), you may have a bad file or your spooler configuration may not be correct.
If you used the HP JetAdmin software to set up the spooler, follow the steps below:
1. Run the HP JetAdmin software.
2. Select Examine Printing Path from the Diagnostics menu.
3. Send the same file that you were not able to print previously using the same options to the same spool queue as when the problems occurred.
The HP JetAdmin software leads you through the printing process and identifies the possible trouble areas.
/dev/null. The permissions
should be 666.
If you used the HP JetAdmin software to set up the spooler, follow the steps below:
1. Look for an error message in the default log file for spooler errors:
/var/adm/lpd-errs
There is another log file for each specific printer.
The log file is specified in the printer's /etc/printcap
entry. The log file's printcap entry looks similar to the following:
:lf=/var/spool/printername/log:
2. Determine the name and path of the printer's log file, then look for an error message in that file.
3. If required, see your host system manuals to troubleshoot the spooler subsystem.
The troubleshooting steps below describe how to troubleshoot printing problems you may have with the HP JetDirect print server.
1. Print a configuration page (also called a self-test page or configuration plot).
2. Verify that the IP configuration values are correct. If they are not, reconfigure the HP JetDirect print server.
3. Log onto the host system and type:
ping <IP address>
where <IP address>
is the IP Address assigned to the printer.
4. If ping fails, make sure the IP Address on the configuration page is correct. If the address is correct, the problem is in the network.
5. If the ping test passes, print a test file. At the UNIX prompt, type:
lpr -Pprinter_name test_file (BSD based
systems)
lp -dprinter_name test_file (Sys V based
systems)
where printer_name
is the name of your printer and test_file
is an appropriate file (ASCII, PCL, PostScript, HP-GL/2, or text
) for the printer defined in the :rp tag in the printcap file.
6. If the test file does not print, do the following:
/usr/spool/lpd/error_log_filename
/var/adm/messages /var/adm/lpd_errs
/usr/adm/syslog
| ©Copyright Hewlett-Packard Company 1996
All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Publication number JD302HTM |
Warranty
The information contained in this document is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. |
Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection
with the furnishing, performance, or use of this material.
One software kit can be purchased for loading onto multiple host systems and will support multiple HP JetDirect print servers. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. |
Trademark Credits
Ethernet is a registered trademark of Xerox Corporation. PostScript is a trademark of Adobe Systems, Incorporated, which may be registered in certain jurisdictions. UNIX® is a registered trademark of UNIX System Laboratories Inc. in the United States and other countries, licensed exclusively through X/Open Company Limited. |
- End of Document -