|
Thanks Michael :-) It was just plain weird because thus unit has 2 twin-ax cards in it and the session for one errored out and the session on the other did not (i.e. a message for one on QSYSOPR and not the other when normally you would see both) and they both showed Active... And it was confirmed that EVERYTHING in this rack, including switches, hubs, etc. were/are on the UPS so this was a weird one. Maybe ANYNET was doing something funky ? Thanks ! Chuck -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rooney, Michael P Sent: Monday, June 14, 2004 10:38 AM To: Midrange Systems Technical Discussion Subject: RE: Question on Perle 494 Control Unit/Communications... Chuck, Opinions are always free.... :) Any feedback on Larry's comments (i.e. a switch or something not on UPS)? It's amazing how slow x494's take to reboot (I prefer antiquated 5394's), so if terminals activated quickly when power was restored, the Perl was probably trying to "bind" with the host the entire time. BTW: It's been several years since I worked with SNA however, the underlying LU6.2 protocol uses simple EVOKE, INVITE and DETACH-like verbs at the physically layer. That said, if the Perl failed to normally "detach" from the connection, you would receive failure messages on QSYSOPR, as you probably did. Terminals and printers, on the other hand, use a different "PU" (physical unit) protocol that is independent from the LU6.2 session managed by the x94. So, in addressing your original post, it's unlikely the Perl manages the LU6.2 session based on the availability of attached devices. Again, just my opinion(s). Regards, Michael Rooney -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Chuck Lewis Sent: Monday, June 14, 2004 10:39 AM To: 'Midrange Systems Technical Discussion' Subject: RE: Question on Perle 494 Control Unit/Communications... Well you are entitled to your opinion Michael :-) but it DEFINITELY happened that way. I double checked with the folks at the site and they touched ABSOLUTELY nothing (there are only a couple of folks that know anything about the wiring closet, it is not easy to get to, etc. and they did nothing...) The Perle IS on an APC UPS and the UPS shows it stayed up during the outage. And as I noted, they had dumb terminal sign-on screens almost instantly once the power was restored to those devices, and if you work with this diskette based Perle units, you know there is NO WAY they boot up that quickly :-) Chuck -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rooney, Michael P Sent: Friday, June 11, 2004 2:09 PM To: Midrange Systems Technical Discussion Subject: RE: Question on Perle 494 Control Unit/Communications... Chuck, I seriously doubt that the Perl or any other x94 controller does what you think it did. As 5x94 controllers use SNA/LU6.2, they connect with the AS/400 regardless of the status of it's attached devices. Are you 100% certain that the Perl had power at this time? BTW: To test your theory try powering off all the local devices. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Chuck Lewis Sent: Friday, June 11, 2004 2:59 PM To: 'Midrange Systems Technical Discussion' Subject: Question on Perle 494 Control Unit/Communications... Hi Folks, We had our largest distribution center down this morning for about 30 minutes - no power. We use a frame relay network. Adtran DSU/CSU, Cisco Router, Perle Control Unit w/Ethernet card, Netgear Switch and APC rack mount UPS. While they were without power I could ping the Cisco Router, telnet into it, etc. but I could not successfully ping the Perle Control unit. Get the Controller Failed messages on QSYSOPR, etc. So not being a communications guru by any stretch, but does the Perle "poll" for responding devices to keep it's connection alive or something ? Reason I ask is that the minute they got power back to the devices there were back up and they touched absolutely nothing in the wiring closet. Thanks ! Chuck -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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-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.