Sun / CalComp Printer networking problems (was: Thick Ethernet/Sun networking problems)

From: Arno Kletzander <Arno_1983_at_gmx.de>
Date: Mon Nov 5 00:40:04 2001

Oh Gosh, that's a lot of stuff... I think I should've mentioned I'm in
digest
mode...

1. Douglas Quebbeman and Dan Wright wrote about scanning all possible IP
adresses. Besides taking an awful lot of time, this is no longer necessary
because we got a status page printed out which states the IP address to be still
111.1.0.1.

2. Lawrence LeMay wrote:
>So, it would help me if you briefly restated the exact problem. I'm
assuming you have a calcomp plotter >(but i dont know which one), that it has a M971
ethernet card...

That is, mostly, correct. What we're having here is a CalComp CCL600ES, a
large laserprinter, hooked up to a Thick Ethernet segment together with two SUN
SPARCstations (1+ and 2) (and a 486 PC for sniffing purposes).

>...and that you dont know what the IP address is set to. (...) Well, one
way of solving this problem is to >reset the M971 card back to factory
defaults, and then setting the IP address. Unfortunately I dont
>have the manuals, but if you have the manuals you should be able to look
some of this up. There is a >reset jumper on the ethernet card, so you power
down the printer, remove the card, install the jumper, >power it up, then
repeat to remove the jumper (assuming i recall the procedure correctly).

We're positive that the IP address is still the one it was set to all the
time (111.1.0.1) because we finally got the Ethernet Adapter Status Page
printed out. This is done by setting the JP1 jumper on the 971, reinserting the
card into the printer, and then powering up. (I suppose this means we don't have
to do all that 'automated pinging' stuff...).

>http://www.calgraphinc.com/Support/unix_networking.html

I'd already found and read this page. Amazingly, they mention only two of
the three LEDs my Ethernet Adapter has (IP, DATA and LINK). During the warmup
phase, IP (green) and DATA (amber) are illuminated. After that, the IP LED
goes on with a blink (rather 2 than 5 Hz, I'd say...), while the DATA LED
flickers whenever something is transmitted on the Ethernet. The LINK LED
stays off all the time. All of this seems to belong to the "NORMAL" column.

3. Pete Turnbull wrote:
>> OK, as the IP Adress of the SUN 1+ is 111.0.0.14 and the Subnet Mask
ff:00:00:00 (says so at boot):
>
>Which is correct for a Class A network...

But isn't it outside the address section which is allowed for equipment
which might possibly be connected to Internet? - But the PC we want to connect
has got a modem!!! (OK, skip that until they work with their current addresses)

>For Arno, this means:
>create /etc/ethers if it doesn't exist
>append a line with printer name and MAC (Ethernet) address
>/etc/hosts must already exist for the Sun to work, so append a line for the
printer
>start up rarpd if it's not already running
>(the order in which you do these shouldn't matter)
>If we call the printer "calcomp", the line in /etc/ethers is:
>
>00:C0:E2:00:0C:8E calcomp
>
>and the line in /etc/hosts is
>
>111.1.0.1 calcomp (...)

OK. /etc/hosts is present, reading in total:
# Local Net 111.x.x.x -- 10 Mb/s Ethernet -- DAZIX
#
127.0.0.1 localhost loghost
111.0.0.14 hombre
111.0.0.23 papa
111.1.0.1 pa3

/etc/ethers does not exist, but...I must stress once again that the system
worked once and I don't suppose it existed back then (because nobody who had
access to the system since then would have deleted anything).

Also, at boot time, a line appears reading

Starting local daemons: auditd sendmail (...) rarpd (...).

>Is "pa3" the printer name?
Yes.

>Some more experimentation is needed to be sure what all the symptoms really
mean. However, >obviously the printer isn't responding to an ARP request
for what should be its own IP address. >Therefore either it is using some
other IP address, or it has lost it's configuration and needs to be
>supplied an IP address (by RARP or otherwise), or the interface is
broken/dormant.

I agree to that. We now know the IP adress is still correctly stored. We
also know the Ethernet interface is receiving every packet transmitted
(flickering DATA LED). And we know that it doesn't respond - from the (incomplete); so
the interface might really be kaputt - I don't hope so, however...

>Ethan Dicks wrote:
>>(...)
>> I think it's useful when you have an ancient network where the broadcast
address uses 0-bits, rather >>than 1-bits - i.e., ip 192.168.1.1 with a
netmask of 192.168.1.0 and a broadcast address of >>192.168.1.0 *not*
192.168.1.255. It's archaic, but allowed.
>
>So it is -- I forgot about that! The rest of what I wrote may well be
drivel :-)

That might be contributing to our problem. At boot, the complete network
section reads:

network interfache configuration:
le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>
        inet 111.0.0.14 netmask ff000000 broadcast 111.0.0.0
        ether 8:0:20:9:bc:d7 ^^^^^^^^^
lo0: flags=49<UP,LOOPBACK,RUNNING>
        inet 127.0.0.1 netmask ff000000

4. Iggy Drougge wrote:
>You can find out the ethernet MAC address for the printer, right? Then
create an ARP entry for that one. >On BSDs (the UNIX type I'm familiar with),
it's done with:
>arp -s arp -s hostname ether_addr
>(...)
>Try:
>telnet 111.1.0.1 2002

hombre_tcsh (1) telnet 111.1.0.1 2002
Trying 111.1.0.1 ...
telnet: connect: Connection timed out
telnet> quit

;>All right, if that doesn't work, we'll have to do the abovementioned entry
in the ARP table, using the ;>Ethernet address seen above:
;>arp -s calcomp 00:c0:e2:00:0c:8e

hombre_tcsh (2) arp -s calcomp 00:0c:e2:00:0c:8e
arp: calcomp: unknown host

;>Now you've made an ARP entry.
;Seemingly not...trying with the correct hostname:

hombre_tcsh (3) arp -s pa3 00:0c:e2:00:0c:8e
pa3: Not owner

;logging in as SU:
hombre# arp -s pa3 00:0c:e2:00:0c:8e

hombre#

;Seems to have succeeded, checking:

hombre# arp -a
pa3 (111.1.0.1) at 0:c0:e2:0:c:8e permanent

hombre# telnet pa3 2002
Trying 111.1.0.1 ...
telnet: connect: Connection timed out

;Same as it was before...pinging also still times out (no answer from pa3).

Oh, and "permanent": After a reboot, the old (incomplete) is there again
instead of the MAC address. Very permanent indeed...

Okay, that's it for this time. I hope we'll bring that printer back up
again. Thanks for your given and coming assistance.

Arno Kletzander
DO4NAK (2m; 70cm)
Arno_1983_at_gmx.de

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
Received on Mon Nov 05 2001 - 00:40:04 GMT

This archive was generated by hypermail 2.3.0 : Fri Oct 10 2014 - 23:34:13 BST