Re: Communications Problem - REALLY Strange/Weird...

Have to talk to the people who config'd the routers. I had a similar
problem, the controllers not communicating, so the AS/400 is not re-trying.
It may be spoofing only on the SNA packets. HTH.
Jim
----- Original Message -----
From: "Chuck Lewis" <clewis@iquest.net>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, June 15, 2000 3:52 AM
Subject: Re: Communications Problem - REALLY Strange/Weird...


> Duh question here Jim...
>
> I don't THINK so but how would I know for sure ?
>
> Normally I get error messages and such when devices disconnect or fail,
etc.
>
> Thanks !
>
> Chuck
>
>
> Jim Franz wrote:
>
> > Are the routers spoofing? (acknowleging the controllers & devices are
active
> > without really checking, to cut down on network traffic). The 400 will
never
> > know if they are down.
> > Jim
> > ----- Original Message -----
> > From: "Chuck Lewis" <clewis@iquest.net>
> > To: <MIDRANGE-L@midrange.com>
> > Sent: Wednesday, June 14, 2000 7:46 AM
> > Subject: Re: Communications Problem - REALLY Strange/Weird...
> >
> > > Chris,
> > >
> > > Yep, started with the wrkcfgsts *ctl ma* (for the ones at this site)
and
> > > everything appeared to be FINE. That is what I find SO strange and a
> > little
> > > unnerving. Usually you will get SOME kind of error to QSYSOPR...
> > >
> > > ???
> > >
> > > Chuck
> > >
> > > Chris Bipes wrote:
> > >
> > > > Most likely one of the sub-controllers was in a recovery canceled or
> > failed
> > > > condition.  Did you check their status before varying off/on?  I
always
> > > > start with wrkcfgsts *ctl Perle* to check the main Perle controller
with
> > > > also show each rmtxx controller, (card), inside of the Perle box as
well
> > as
> > > > all the devices attached to them.
> > > >
> > > > We found during a recent 3 second power flux that one of the hubs
was
> > not on
> > > > the UPS.  Just long enough to cause one of 5 controllers under the
Perle
> > to
> > > > fail.  No error message in QSYSOPR.  (Humm I still need to research
why
> > > > recover did not correct it or QSYSOPR did not get a message.)
> > > >
> > > > Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
> > > > Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
> > > > CrossCheck, Inc.         http://www.cross-check.com
> > > > 6119 State Farm Drive    Phone: 707 586-0551 x 1102
> > > > Rohnert Park CA  94928 Fax: 707 586-1884
> > > >
> > > > If consistency is the hobgoblin of little minds, only geniuses work
> > here.
> > > > Karen Herbelin - Readers Digest 3/2000
> > > >
> > > > -----Original Message-----
> > > > From: Chuck Lewis [mailto:clewis@iquest.net]
> > > > Sent: Wednesday, June 14, 2000 12:53 AM
> > > > To: MIDRANGE-L@midrange.com
> > > > Subject: Communications Problem - REALLY Strange/Weird...
> > > >
> > > > Hi Folks,
> > > >
> > > > Just had a weird one happen...
> > > >
> > > > We are running a 620 at V4R1 and connecting branches via a Frame
Relay
> > > > network with Perle 494e controllers, everything running TCP/IP.
> > > >
> > > > I get a call from one of our bigger branches (which is 20 miles from
> > > > here) that they are down. They have been having power trouble lately
so
> > > > I "assumed" it was that a checked QSYSOPR. NO messages... And they
said
> > > > they had NOT noticed any power disruption or anything. I had the
person
> > > > that called power off their workstation and power it back on -
nothing.
> > > > I varied it off and back on and the system issues a message that the
> > > > device is no longer communicating but they STILL have nothing on
their
> > > > screen. So I ping the router (Cisco) - NO problem. I ping the
> > > > controller(s) (each twin ax card in the Perle is looked at as a
separate
> > > > virtual control unit) and they are BOTH OK...
> > > >
> > > > So I vary each control unit and the associated virtual device off
and
> > > > back on and EVERYTHING is fine now...
> > > >
> > > > ANYBODY had ANY IDEA what happened or what else I could have checked
?
> > > >
> > > > TIA !!
> > > >
> > > > Chuck
> > > > +---
> > > > | 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
> > > +---
> >
> > +---
> > | 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
> +---

+---
| 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
+---