Re: Hooking a networked printer to a Solaris 10 system
- From: jeff@xxxxxxxx (Jeffery Small)
- Date: Fri, 7 Mar 2008 20:32:10 GMT
Martin Paul <map@xxxxxxxxxxxxxxxx> writes:
Even if you don't run a BOOTP service, the /etc/bootptab file might still
exits (leftover?). Have you checked whether the file is non-existant or
empty?
No, there is no /etc/bootptab file on the system.
A shot in the dark - have you added the printer to /etc/inet/hosts and
/etc/ethers before running hppi? I usually do so, and I'm using the JD
printer installer without BOOTP as well.
I had added the host table entry but not the entry to /etc/ethers. I did that
but it made no difference.
The message you get comes from /opt/hpnpl/admin/option_arp:
grep "ip=$IPADDR:" $BOOTPTABLE > $HPNP/tmp/tmp0 2>&1
if [ -s $HPNP/tmp/tmp0 ]
then
$ECHO "The address \"$IPADDR\" has an existing entry ...
...
fi
If /etc/bootptab doesn't exist, check if /opt/hpnpl/tmp/tmp0 is empty.
Actually, I think the above grep command is not correct - if the bootptab
file doesn't exist, the 2>&1 will make an error message show up in the
file which triggers the [ -s ... ] test. I guess option_arp shouldn't be
run at all if BOOTP isn't used.
Martin, you did what I was too tired to do at 4 AM this morning! And you
are correct about the problem. It occurs in a couple of places in that
file, so I surrounded the offending code with:
if [ -s $BOOTPTABLE ] ; then
...
fi
and now get by these erroneous tests. The process continues and it is
unable to communicate with the printer, so it trys the default built-in IP
address of 192.0.0.192 which it expects the printer to self-assign when it
can't obtain one from DHCP. Unfortunately, it appears that these new HP
printers use the J7949E embedded print server and now self-assign a default
address of 169.254.48.167. So I modified the "option2" and "option_arp"
files to use the new default address and it actually worked! I was able to
get a telnet session to the printer and reset the JetDirect card for static
(manual) IP assignment.
The sorry state of affairs is that there is apparently no one at HP in the
printer group that seems to even know what UNIX is and there is no one
in the server group that handles HPUX that knows anything at all about
printers. So, despite the fact that they state in their printer manuals
that they support the TCP/IP protocol for the Solaris OS and further
support Solaris for both the HP Jetdirect Printer Installer as well as the
HP Web Jetadmin software, there is, in fact, no support to be had from
HP. The E.10.34 version of the JetDirect Printer Installer is the latest
version available according to the web site and it obviously will not work
with the current crop of printers unmodified. It makes me wonder what
people running HPUX are doing? I suspect that they will have the same
problem I did. This lack of support from HP will probably dissuade me from
purchasing another HP product.
Again, thanks to Martin and anyone else who responded to my plea for help.
Regards,
--
Jeffery Small
.
- References:
- Re: Hooking a networked printer to a Solaris 10 system
- From: Martin Paul
- Re: Hooking a networked printer to a Solaris 10 system
- Prev by Date: How long does it take for Solaris Volume Manager to fail a disk?
- Next by Date: Re: SIGBUS in One Thread. Can Other Threads Continue?
- Previous by thread: Re: Hooking a networked printer to a Solaris 10 system
- Next by thread: dladm show-dev
- Index(es):
Relevant Pages
|
