ITEM: U2075L

Jetdirect on Welfleet router won't boot



Response:

DESC: customer has setup jetdirect printers locally before.  They are
now trying to setup an external jetdirect card across two Wellfleet
routers.  They have seen that bootp kicks off when they power cycle
the jetdirect card.

ACT: I had him put the bootpd in debug by commenting out the bootps
line in /ect/inetd.conf, "inetimp", "refresh -s bootpd", "bootpd -s -d
-d -d -d -d&".  This did not show any entries read or dumped.  A ps
showed the old bootpd still running, so I had him kill that one and
run the bootpd line again.  This did show a successful bootp request
received and the correct information was sent back out.

I had him print a test page and the card did not receive the ip
address.

A traceroute to a pc on the network with the jetdirect showed
(93.0.0.1)

89.98.99.1 
92.98.99.1 
* * * 
* * * 
up to 14 hops

however, a ping shows a round-trip time of 34ms.

Response:

E: RISC/570 --- Wellfleet --- WAN --- Wellfleet ---PC=93.0.0.102
   AIX 3.2.5    router                router       Printer=93.0.0.1
   89.0.0.89    89.98.99.1
                92.98.99.1
D: The RISC cannot ping the printer, but was able to ping the PC.
A: The RISC can ping itself.  It can ping only one interface on
   the router on this end, that is, it can ping 89.98.99.1 but
   not 92.98.99.1.  The RISC can ping the PC (93.0.0.102), but
   it cannot ping the printer.  Had customer checked the routing
   table.  It shows as follow:
        89         89.0.0.89    U       en0
        93         89.98.99.1   UG      en0
        127        127.0.0.1    U       lo0
   Had customer flushed the routing table then run minimum
   configuration.  Used 89.98.99.1 as a default route.  The new
   routing now shows as:
        default    89.98.99.1   UG      en0
        89         89.0.0.89    U       en0
        127        127.0.0.1    U       lo0
   The RISC was now able to ping everything, except the printer.
   The RISC can ping the PC but traceroute shows that there is
   problem at second hop, or at 92.98.99.1.  Don't know if bootp
   can be heard accross router.
N: Customer will call back tomorrow.  Queue item to 7x24 for further
   assistance.

Had customer try trace route.
   The output shows the following:
        1.      88.98.99.1
        2.      92.98.99.1
        3.      ***
        4.      ***
   This indicated that packets cannot get through other interface
   of the router.  Suggested customer to check the router.  One
   thing that puzzle me was that e

Response:

Response:

DESC:  Customer says that he is able to ping both routers, but 
still cannot ping the printer.

Welfleet enabled agents from to enable the bootpd.

arp packet came in from the card
udp back to the router
protocol icmp coming back - says destination unreachable
        checksum error.  
udp back to the router.

Response:

Welfleet people are on site.  They have a sniffer,
and they say that when they pass the bootp to AIX, that aix
responds to the wrong well known port (67 instead of 67).
In fact they say that we send both source and destination
of the udp at port 67, giving an error on the router.

I need to get someone with more bootp experience to explain
when bootpc and bootps are used and how this might be, and
how we can trace to determine which system is at error.

Found a similar item:  Problem was fixed by setting the
broadcast address of the router to enabled.

Response:

Had to change the gateway address number from the local routers
ip address, but to the remote routiners ip address.   Now they
can ping the  jetdirect.  Printing will follow  

NEXT:  Closing


Support Line: Jetdirect on Welfleet router won't boot ITEM: U2075L
Dated: May 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:35
Comments or suggestions? Contact us