|
I bet the real problem is that 2721 is Not detected.
This may happen if you have wrong cable on port - makes IOA crazy.
Best regards
Alexei Pytel
Jon.Paris@halinfo.it on 11/23/99 05:03:16 PM
Please respond to MIDRANGE-L@midrange.com
To: midrange-l@midrange.com
cc: Susan.Gantner@halinfo.it
Subject: Ops Console problems
After 3 weeks of trying we still cannot get the "new style" console on our
new
V4R4 Mod 170 to work. We've got the CA PTFs loaded and with those we get
further but ......
When we try to connect we get asked for the DST User Id and PW and then it
just
sits "validating" for a while before issuing a message (no ref # of
course!)
that indicates a communications failure while trying to validate the
signon. We
have enabled all logging options in CA but nothing is logged. A look at
the log
from the "Modem" that was generated by the install indicates that the 400
was
contacted and responded (with a <CR>) nothing else significant appears
until we
disconnect.
We have worked with IBM on this, and they have a problem log identical to
ours
which was closed because the customer got fed up with wasting so much time
on it
and (as we have had to do to use the machine at all) went back to the old
style
console.
Anyone got any ideas? Or if you have a new 170 at V4R4 perhaps you could
tell
me what your line descriptions etc. look like. Our hardware cfg looks a
little
odd but I have no idea what "normal" looks like. Our console IOP is a 9745
but
this doesn't show up - what we see is below - a 2745 which is operational
and a
2721 marked as "not detected".
Resource Type Status Text
CMB01 6757 Operational Combined function IOP
LIN03 2721 Not detected Comm Adapter
CMN04 2721 Not detected Comm Port
CMN05 2721 Not detected Comm Port
LIN01 2745 Operational Comm Adapter
CMN01 2745 Operational V.24 Port
CMN02 2745 Operational Comm Port
This is all taking up way too much time and I'm wondering just what I'll
lose if
we just give up and save ourselves the frustration!
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
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.