× 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.



I think you are "mixing" wiring methods...

Twinax doesn't generally use muxs, are you sure about this being 
twinax ??? What is the purpose of the mux ??

You refer to "controllers" several times, "which" controllers
are you working with and what are using to check them with ??

One device on a twinax line would not normally "drag down" all the
other devices "unless" it was the first device on the line and it
failed quite badly, it "might" bring down other devices by not
allowing communications. The device status on any line can be
checked with wrkcfgsts *dev and making note if a printer has a 
associated writer started. You can also determine if displays are 
working this way.



ouuch@xxxxxxxxxxx wrote:
> 
> Hello,
> 
> we still have a bunch of Twinax devices (displays and printers). The printers 
> are actually normal
> laser printers with an IPDS twinax converter box.
> 
> The twinax controllers are connected through fibre optic cables and 
> multiplexers to the twx-
> hubs.
> 
> Every other month one of the IPDS boxes fails and will pull down all other 
> twx-devices on that
> multiplexer.
> 
> Is there any twinax voodoo to find the failing box faster, i.e. w/o 
> disconnecting all suspected
> devices?
> 
> Or are there any controller settings, special connectors or whatever so a 
> failing device won't kill
> a lot of others?
> 
> I've been searching 3 hours this morning for the failing device...

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.