|
I erred. It is actually a 2746 controller. It has 14 active devices on it. I am having trouble when configuring the 6th device on port 1. I even tried deleting the device description and having it recreated on another existing cat 5 data cable. Invariably, a new device will be created, but as soon as I sign on the new device, I have trouble with one (or sometimes all) devices on the port. I had a somewhat similar problem a year or so ago (again with an Andrew multilplexor) and I the IBM support line clued me into duplicate resource names issue. I just do not remember the solution. -----Original Message----- From: Andy Nolen-Parkhouse [mailto:aparkhouse@attbi.com] Sent: Wednesday, June 26, 2002 12:21 PM To: midrange-l@midrange.com Subject: RE: How do you find a resource name for a DEVD? Bryan, The resource name is a logical assumption, but I can't ever remember experiencing any conflicts with resource names on terminals in fifteen plus years of working with the midrange. Here's a thought: The 6050 controller will support only forty active devices, yet it has forty-eight addresses available. Is it possible that you are exceeding this forty device limit? If so, results could be unpredictable, but definitely only forty of them could be active at one time. The timing of the error noted below would coincide with this theory. Regards, Andy Nolen-Parkhouse > Subject: RE: How do you find a resource name for a DEVD? > > 1. I am looking for the resource name of a specific 3476 dumb terminal, > not > the resource name of the controller. > > 2. Problem: A certain device on a port stops communicating (CPF2677) > when > the system auto configures a new device on the same port. The devices do > HAVE DIFFERENT ADDRESSES. > > The existing device stops communicating when signing-on to the new device, > not when it is auto configured. > > The devices are attached to a 6050 controller through a ANDREW repeater > (multiplexed). We are running a V4R5 on an 820. > > I was thinking may be devices with duplicate resource names... _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.