× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Token Ring Horror Troubleshooting
  • From: "Ilena E. Ayala" <Ilena@xxxxxxxxxxxxxx>
  • Date: Mon, 9 Jun 1997 21:53:29 -0400

IANAC (I am not a CNE) but...
>Now the question:  What tools are available on the AS/400, short of
>buying a sniffer, which will help me check the health of our network. 

For a problem like this, it might be cheaper to find a local consultant
that already owns the appropriate tools, and knows how to use them, to do
the diagnostic for you.

>We may have a bad MAU, because a majority of the PCs reporting problems
>are connected to the same MAU, but how do I check?
One option is to play musical users.  Keep track of whos on the suspect MAU
"A" and thought-to-be-ok
MAU "B".  Swap all(or even just a sampling) of the users from the A to B
and see if the problem goes to the people who have been moved to the
suspect MAU or follows them to the new one.  (Hint:  Keep the patch cables
on the MAU following the end users; that way if there is a bad cable there,
the problem will follow the user.)

>Also, has anyone tried using two different brands of MAUs within the
>same ring?

Different brands should be OK if they are compatible.  IBM 8228s are
'passive'  MAUs.  I don't know about the
Andrew one you have, check to make sure it's passive not active, because I
don't think you can mix passive and active MAUs within a ring.    You said
it's supposed to be compatible with the 8228, but not how you determined
that.  Double check with their tech support, even if the documentation says
it is...typos happen. 

Did this problem show up when the Andrew MAU was added to the ring?  Or did
you previously have peaceful coexistance?

><snip> we run a combination of UTP and STP cables.  
I'm not sure if mixing UTP and STP on one ring is OK to do. Some cards have
to be told which they are attached to, might be better off to use one or
the other.  If you can't replace one or the other because of the amount of
each in existance, it might be easier (???) to split the ring into two
rings, one STP ring, and one UTP ring.  Might have to be careful with the
patch cabling if you go that route though.  STP is reccommended for IBM
products (at least that's what my Novell CNE Study Guide says.)  UTP at
16MBPS apparently doesn't work well in practice, so if possible replace it
with STP.  My aforementioned book says "...16 Mb/s Token Ring over UTP is
almost impossible to achieve."

And, if you haven't already, try reseating all the cabling & plugs on the
suspect MAU, including the ring in/ring out cables.  If some of the cabling
is homemade, and looks like it isn't well seated in the RJ45 plug or looks
like it got a bad kink/bend (the kind that might break wires internally,
resulting in intermittant contact), consider it suspect and replace them.

Hope that helps!

Ilena Ayala
Barsa Consulting Group
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.