| Title: | Digital PostScript printers and their associated software |
| Moderator: | REGENT::LASKO HER |
| Created: | Wed Jan 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 7230 |
| Total number of notes: | 31971 |
Hello,
I'm having problems booting a printserver through a PPP link between two
routers connecting two IP subnets.
The scenario is the following:
-------LAN A------- -------LAN B-------
| | | |
| | | |
Load Host DECnis ------- PPP link ------- RBOUT LPS
- The printserver is a LPS20 located on LAN A trying to load via BOOTP
from a host located on LAN A and running Digital UNIX V3.2
- All hosts directly connected to LAN B belong to the IP subnet
16.190.224. The addresses of the RBOUT and the LPS are:
RBOUT ---> Eth addr: 16.190.224.1
PPP addr: 16.254.197.2
LPS ---> 16.190.224.65 (the address to be loaded in the LPS)
- The load host and DECnis belong to the IP subnet 16.38.0. These are
their addresses:
Load host ---> 16.38.0.29
DECnis ---> 16.38.0.1
- The Routeabout has been configured to act as a BOOTP relay and
forwards BOOTP requests to the IP address of the load host on LAN A
- The Load Host has one entry in the /etc/bootptab file
> lpsbsb: ht=1: ha=08002b281cfd: ip=16.190.224.65:\
> bf="/tftpboot/lps.sys":\
> sm=255.255.255.0: gw=16.190.224.1: vm=rfc1048:
where the gw is the RBOUT aforementioned, the ha is the hardware
address of the LPS, and the ip is the IP address to be loaded.
When the printer boots I can see that a BOOTP request pass through the
Routeabout and in the daemon.log file of the load host I can see that the
request come and the host send reply to gateway 16.190.224.1, but the LPS
is never loaded.
This is the sequence in the daemon.log file:
Feb 12 11:39:41 ib003 bootpd[554]: recvd pkt from IP addr 16.254.198.2
Feb 12 11:39:41 ib003 bootpd[554]: bootptab mtime: Wed Feb 12 11:38:48 1997
Feb 12 11:39:41 ib003 bootpd[554]: request from Ethernet address 08.00.2B.28.1C.
FD
Feb 12 11:39:41 ib003 bootpd[554]: found 16.190.224.65 (08.00.2B.28.1C.FD) at (l
psbsb)
Feb 12 11:39:41 ib003 bootpd[554]: file /tftpboot/lps.sys.lpsbsb not found
Feb 12 11:39:41 ib003 bootpd[554]: bootfile="/tftpboot/lps.sys"
Feb 12 11:39:41 ib003 bootpd[554]: vendor magic field is 0.0.0.0
Feb 12 11:39:41 ib003 bootpd[554]: sending reply (with no options)
Feb 12 11:39:41 ib003 bootpd[554]: sending reply to gateway 16.190.224.1
In the console of the RBOUT I can see how the answer arrives to the remote LAN
and the packet has the right information, even those rfc1048 options, as gw and
sm. However is very likely that the printer receives something because the first
request, got from a trace facility, looks like this:
|
UDP port: BOOTPS
operation Request | Hardware type Ethernet (10Mb)
Hardware length 6 | Hops 1
XID 0x2B281CFD | Boot attempt time 00:00:00
Flags 0x0000 | Client IP address 0.0.0.0
Your IP address 0.0.0.0 | Gateway IP address 16.190.224.1
Client hardware address 08-00-2B-28-1C-FD [Dec] | Server name
File |
No more decoding possible but 64 octets remain after offset 268
Whereas the subsequent requests have in the filed "Your IP address" the address
to be load.
UDP port: BOOTPS
operation Request | Hardware type Ethernet (10Mb)
Hardware length 6 | Hops 1
XID 0x2B281CFD | Boot attempt time 00:00:00
Flags 0x0000 | Client IP address 0.0.0.0
----> Your IP address 16.190.224.65 <-------- | Gateway IP address 16.190.224.1
Client hardware address 08-00-2B-28-1C-FD [Dec] | Server name
File |
No more decoding possible but 64 octets remain after offset 268
I can load the LPS from a node on the same LAN (B) and everything is all right.
Other LPSs connected to LAN A are loaded from the load host without any problem.
The same problem in a Frame Relay link and with an LPS17.
Has anybody attempt to perform this configuration?
Could it be that the printer doesn't know how to handle the options related
with the inter-subnet downloading?
Any help is greatly appreciated.
Alfonso.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7077.1 | Some questions | REGENT::WOLF | Wed Feb 12 1997 16:56 | 22 | |
In V 5.1 of PrintServer software, we successfully dealt with
intersubnet booting.
So what version of PrintServer software are you running?
And what boot firmware version is your printer running (anything < 3.8
and all bets are off.
What does the front panel say as the failure? generally it is either
?54 (no one answered my bootp request) or ?56 Bootp was successful but
tftp is failing).
Are you sure that the boot server is properly configured to answer
bootp and tftp requests?
Is the boot file lps.sys in the expected location?
Is the printer's ip address unique?
Is this lps20 a base 20, a turbo 20 or a turbo 20 with the expanded
memory?
jeff
| |||||
| 7077.2 | f/w under required, but another problem | MDRA1::ADIAZ | ALFONSO DIAZ @SQO | Thu Feb 13 1997 06:03 | 51 |
Hello,
> So what version of PrintServer software are you running?
> And what boot firmware version is your printer running (anything < 3.8
> and all bets are off.
I'm afraid I have much to do. The printserver firmware is 1.1, and, in
addition of this, it is an LPS20, not Turbo LPS20, so according to my
information, a first upgrade to Turbo LPS20 would be required, because
no upgrade is available for LPS20 (Note 4749 in this conference).
But, as I mentioned in the last lines of my note, I have exactly the
same problem with the same symptoms in a Frame Relay link between a
DECnis and a RouteAbout (which is performing the bootp forwarding as
in the PPP link). The server is the same, but the printer is a
LPS17/600 with firmware version 2.1
Related to your questions, here you the answers referring to the LPS17:
> So what version of PrintServer software are you running?
V5.1
> And what boot firmware version is your printer running (anything < 3.8
> and all bets are off.
LPS17 firmware version 2.1
> What does the front panel say as the failure? generally it is either
> ?54 (no one answered my bootp request) or ?56 Bootp was successful but
> tftp is failing).
The front panel of the LPS17 shows ?55.
> Are you sure that the boot server is properly configured to answer
> bootp and tftp requests?
Yes, it is serving other printservers in the same LAN.
> Is the boot file lps.sys in the expected location?
Yes.
> Is the printer's ip address unique?
Yes.
Cheers,
Alfonso.
| |||||
| 7077.3 | some answers and a few questions more | NECSC::HARVEY | Printserver Support- America's Zone | Thu Feb 13 1997 11:44 | 20 |
Alfonso,
The LPS20s firmware is real old. The firmware can be upgraded by
MCS with the ROM part numbers, 23-259E7-00 and 23-258E7-00. This will
upgrade the firmware to 1.3 revision. MCS can also upgrade the printer
to a TurboLPS20 by installing a Turbo controller part number 54-20830-01,
most likely for a fee. The firware part number for the Turbo controller
is LPS2X-FW for the 3.8 revision.
The LPS17 has the latest and greatest firmware 2.1 revision. So
this is not the problem with the LPS17. So is the LPS17 booting from
the same UNIX server? If it is then the load file must be lps17.sys
not the lps.sys image.
Is there a DHCP server on the net? Is the printers MAC addresses
excluded from the DHCP server? Your gateway info looks correct for the
network as you have outlined it. I have seen ?55 errors when a DHCP
server replies to the LPS printer.
Renis
| |||||
| 7077.4 | DHCP does not seem to interfere | MDRA1::ADIAZ | ALFONSO DIAZ @SQO | Mon Feb 17 1997 06:16 | 28 |
Hi, The LPS17 is booting from the same UNIX server, and the file to be downloaded is lps17.sys. Here you can see the entry for this LPS17 in the /etc/bootptab file: lpsval: ht=1: ha=08002b9fa47d: ip=16.38.80.6:\ bf="/tftpboot/lps17.sys":\ gw=16.38.80.1: sm=255.255.255.0: vm=rfc1048: (Note that the scenario is exactly the same as shown in .0 with the only difference of the remote subnet 16.38.80.0 instead of 16.190.224.0) > Is there a DHCP server on the net? Yes, there is a DHCP server in the same subnet as the UNIX server is. However, it is configure to not to respond to the boot requests coming, form the printserver's subnet and it is working so, as far as I can see with both the analyzer and the router console. One more thing about the behaviour of the LPS17: it sends boot requests continuously, about 4 or 5 times each minute, whereas an LPS17 in the same LAN as the server, does not do this. Alfonso. | |||||