Jetdirect Printserver TFTP Configuration file format

Aus Knowledgebase
Wechseln zu: Navigation, Suche

HP JETDIRECT PRINT SERVERS - UNIX (R), EXPLANATION OF TFTP OR NPI CONFIGURATION FILE ENTRIES

Discussion of TFTP Configuration and Implementation

NOTE: The following information was taken from the hpnp examples file tftp.cfg on an HP-UX9 system with HP JetAdmin d.01.20. It is a listing of tftp configuration file [sometimes called a Network Printer Interface (NPI) configuration file] entries and explanations. This document is not intended to explain the workings of tftp in any particular environment, it is being listed here as a means for those who purchase HP JetDirect without HP JetAdmin-like utilities to obtain tftp configuration parameters related to the HP JetDirect product.

An example of name and location information of a tftp configuration file (or NPI configuration file) is:

/home/tftpdir/hpnp/jd_ip_name.cfg  (HPUX10.x)
/usr/tftpdir/hpnp/jd_ip_name.cfg   (HPUX9.x)

A typical tftp configuration file would contain the following data:

idle-timeout: 120
location: 1st floor, south wall
contact: Phil, ext 1234

The printer accesses the configuration file according to certain bits set when using BOOTP configuration method for IP address allocation.

  • the bootfile parameter has to bet set and
  • some other parameter has to bet set (which?)

Detailed Syntax

Below are the correct syntax for each line entry and brief explanations.

name: picasso
Name is the peripheral (or node) name. It is displayed on the peripheral's self-test page or configuration plot, and when sysName is obtained through SNMP. This name can be provided in the BOOTP response or can be specified in the NPI configuration file to prevent the BOOTP response from overflowing the packet. The domain portion of the name is not necessary because the peripheral does not perform Domain Name System (DNS) searches. Name is limited to 64 characters.
location: 1st floor, south wall
Location describes the physical location of the peripheral. This is the value used by the interface for the MIB-II sysLocation object. The default location is undefined. Only printable ASCII characters are allowed. Maximum length is 64 characters.
contact: Phil, ext 1234
Contact is the name of the person who administers or services the peripheral and may include how to contact this person. It is limited to 64 characters. This is the value used by the interface for the MIB-II sysContact object. The default contact is undefined. Only printable ASCII characters are allowed. Maximum length is 64 characters.
allow: 10.0.0.0 255.0.0.0
allow: 15.1.2.3
The host access list contains the list of hosts or networks of hosts that are allowed to connect to the peripheral. The format is "allow: netnum [mask]", where netnum is a network number or a host IP address. Mask is an (optional) address mask of bits to apply to the network number and connecting host's IP address to verify access to the peripheral. The mask usually matches the network or subnet mask, but this is not required. If netnum is a host IP address, the mask 255.255.255.255 can be omitted. Up to ten access list entries are permitted.
idle-timeout: 120
Idle timeout is the time (in seconds) after which an idle print data connection is closed. A value of zero disables the timeout mechanism. The default timeout is 90 seconds.
get-community-name: blue
A community name is a password that allows SNMP access to MIB values on the network peripheral. Community names are not highly secure; they are not encrypted across the network. The get community name determines which SNMP GetRequests are responded to. By default, the network peripheral responds to all GetRequests. The get community name is limited to 32 characters.
For hpnpstat and hpnpadmin, the community name can be stored in /usr/lib/hpnp/hpnpsnmp.
set-community-name: yellow
The set community name is similar to the get community name. The set community name determines which SNMP SetRequests are responded to. In addition, SetRequests are only honored if the sending host is on the host access list. By default, the network peripheral does not respond to any SetRequests. The set community name is limited to 32 characters.
The set community name can come from /usr/lib/hpnp/hpnpsnmp if it is the same as the get community name. We recommend that the set community name be different from the get community name though.
trap-community-name: red
SNMP traps are asynchronous notifications of some event that has occurred. SNMP traps are useful only with network management software. Traps are sent to specific hosts and include a trap community name. Up to 12 hosts can be sent with firmware X.06.XX or greater, and up to four hosts can be sent with firmware less than X.06.XX. The trap community name is limited to 32 characters. The default name is public.
trap-dest: 15.1.2.3
The SNMP trap destination list specifies systems to which SNMP traps are sent. Up to 12 addresses are allowed with firmware X.06.XX or greater, and up to four IP addresses are allowed with firmware less than X.06.XX. If no trap destinations are listed, traps are not sent.
authentication-trap: on
The SNMP authentication trap parameter enables or disables the sending of SNMP authentication traps. Authentication traps indicate that an SNMP request was received and the community name check failed. By default, the parameter is off.
syslog-facility: local2
The syslog-facility parameter sets the source facility identifier that the card uses when issuing syslog messages. Other facilities, for example, include the kernel (LOG_KERN), the mail system (LOG_MAIL), and the spooling system (LOG_LPR). The card only allows its syslog facility to be configured to one of the local user values (LOG_LOCAL0 through LOG_LOCAL7). The selectable option strings, local0 through local7 (configured to LOG_LOCAL0 through LOG_LOCAL7, respectively) are case insensitive. The default syslog- facility for the card is LOG_LPR.
subnets-local: on
This parameter allows the card to treat hosts on other subnets as if the hosts were on the card's subnet. This parameter determines the TCP Maximum Segment Size (MSS) advertised by the card to hosts on other subnets and affects the card's initial receive-window size. The card will use a TCP MSS of 1460 bytes for local hosts, and 536 bytes for a non-local host. The default is off, that is, the card will use the maximum packet sizes only on the card's configured subnet.
The configuration utility does not allow access to this parameter. If you want to configure it, you must manually edit the NPI configuration file and add it to the bottom of the entry for the network peripheral.
old-idle-mode: off
This parameter affects how the card handles TCP connection requests from the host. By default, the HP JetDirect MPS card will accept a TCP connection even if the peripheral is off-line. If this parameter is set to "on," then the card will only accept a TCP connection when the peripheral is online.

Copyright Notice

UNIX (R) is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.

Copyright ( Hewlett-Packard Co. 1998 This information is subject to change without notice and is provided "as is" with no warranty. Hewlett-Packard shall not be liable for any direct, indirect, special, incidental or consequential damages in connection with the use of this material.