[comp.unix.questions] "ie0: Ethernet jammed" on a Sun 4/110

@aplvax.jhuapl.edu:trn@warper.jhuapl.edu (Tony Nardo) (08/17/88)

Recently the group I'm in obtained a Sun 4/110.  We are having a problem
getting the Sun 4 to interface with our ohter processors.  Regardless of
whether an Ethernet cable is plugged in or not, attempts to use the network
generate the message

	ie0: Ethernet jammed

This same Ethernet cable works when plugged into our Sun-3.

The Sun 4 is a VMEbus machine (*not* multibus).  Anyone have any suggestions
as to what might be wrong before I start screaming, "Hardware problem!"?

							Thanks,
							   Tony

==============================================================================
ARPA:   @aplvax.jhuapl.edu:trn@warper	   \
        nardo%str.decnet@capsrv.jhuapl.edu  }  one of these should work
UUCP:	{backbone!}aplvax!warper!trn	   /
USnail: c/o Johns Hopkins University/APL, Room 7-53
	Johns Hopkins Road
	Laurel, Md. 20707

"You can't win, you can't break even, you can't even quit the game."
==============================================================================

trdill@ihlpf.ATT.COM (Diller) (08/18/88)

I can't say for sure but in the Sun 3/60 there is an internal
jumper which when set one way will work with "cheaper-net" and
when set the other way works with ether-net. I can't say for
sure but the error you are getting sounds like you may have an
un-terminated network. You may want to check if this jumper
situation applies to the Sun 4/xxx.

root@helios.toronto.edu (Operator) (08/18/88)

In article <1670@aplcomm.jhuapl.edu> @aplvax.jhuapl.edu:trn@warper.jhuapl.edu (Tony Nardo) writes:
> ... Regardless of
>whether an Ethernet cable is plugged in or not, attempts to use the network
>generate the message
>
>	ie0: Ethernet jammed
>
>This same Ethernet cable works when plugged into our Sun-3.
>
Does the same *transceiver* work when you connect the Sun 3 to it? You may
run into problems if the transceiver is generating heartbeat, which the Suns
(using 802.3) don't want. Also, I'm not sure how configurable the on-board
ie is, but you might want to check whether it's set for the right level of
Ethernet. I know this has to be done for the second Ethernet interface, by
means of a jumper (level 1.0 vs. 2.0).

Other than that, I'd say "start screaming". If you don't have the cable
plugged in, your Sun 4 should be saying "ie0: no carrier", not "jammed".

-- 
 Ruth Milner          UUCP - {uunet,pyramid}!utai!helios.physics!sysruth
 Systems Manager      BITNET - sysruth@utorphys
 U. of Toronto        INTERNET - sysruth@helios.physics.utoronto.ca
  Physics/Astronomy/CITA Computing Consortium

hans@taeva.UUCP (Hans von Kleist-Retzow) (09/02/88)

In article <5720@ihlpf.ATT.COM> trdill@ihlpf.ATT.COM (Diller) writes:
>
>I can't say for sure but in the Sun 3/60 there is an internal
>jumper which when set one way will work with "cheaper-net" and
>when set the other way works with ether-net. I can't say for
>sure but the error you are getting sounds like you may have an
>un-terminated network. You may want to check if this jumper
>situation applies to the Sun 4/xxx.

The Sun 4/110 has an automatic Ethernet/Thin-Ethernet selection
feature.

I add some part of the Sun 4100 Board Set Configuration Procedures:

"If your Ethernet cable is hooked up to a multiplexer box with less
than 30 milliamps on a +12V return, the Auto Select function allowing
you to connect either Ethernet or Cheapernet automatically will not
work. You should disable the Auto Select function by forcing
Ethernet. To do this, install jumper J1800."

The location of the jumper is D-3.

---------------------------------------------
Hans von Kleist-Retzow, Dipl.-Inform.
TA Triumph-Adler AG
Hundingstr. 11b
D-8500 Nuernberg
West-Germany
Tel: +49 911 322 6355
E-Mail: hans@taeva.uucp
  uucp: ...!mcvax!unido!taeva!hans
---------------------------------------------

animal@ernie.NECAM.COM (Alan R. Silverman) (09/03/88)

	I have some of the same problems.  I noticed that on some of the
machines, the connector was a bit loose or slightly bent down.  When I
straighten out the connector, the errors disappear for a while.

	Another possibility is, your backbone may be too close to a 
florescent light or other 'noisy' object.  One time, someone layed a
florescent light unit next to the end of my backbone cable, in a dark
corner and the ethernet went into cardiac arrest with nothing but
ie0: Ethernet jammed  messages blasting the consoles!!!  

-animal