Re: Leased Line checking?

[mcrump@xxxxxxxxxxxxxx]

 Tim Wrote:

>Hello all:
>I am wondering if someone knows a simple way we can check the quality of
>our own AT&T Leased Line that we use for 2 of our remote sites?

Couple of ways that I use to help - what you use depends on your
preferences......

1.) You can set your LIND to monitor and report temporary errors:
 I quote:
The level of temporary error threshold monitored by the system.  A
permanent error is reported only if the errors occurred contiguously
and exceeded the retry limit.  The valid levels are:
 o  *OFF: Threshold errors are reported.
 o  *MIN: A minimum level of error threshold monitoring is done by
    the system.
 o  *MED: A medium level of error threshold monitoring is done by
    the system.
 o  *MAX: A maximum level of error threshold monitoring is done by
    the system.

    Note:  This value applies to all threshold errors.  They cannot
    be individually set.

2.)   You can track different types of errors with the performance
collection monitor.  File QPFRDATA/QAPMHDLC tracks all kinds of
HDLC.  Check out the appendix in the Work Management Guide for a
description of the file...

3.)  You can run a comm. trace from SST.

4.)  Problem analysis can sometimes be used - historically this has only
helped during install times.

5.)  VFYCMN will let you run a number of different communication tests -
port tests, line wraps, etc.  I typically will only use this when the
network provider or DTE provider is stubborn and can't/won't find/admit to
the cause of the problem.

My preference for determining problems 'real time' is the comm. trace.  You
 can see data in a fairly raw form (send, receive), and you
bypass host issues.  The comm. trace may not come out and directly tell you
 what the problem is but if there are 'line' type problems
it will most likely indicate that - you will have to become familiar with
it and there are a few key things to look at when you format the
report - sends and no receives; rejected frames, command/response not
valid; etc.  It has been my experience that the majority of
'comm' problems are network related....... I will usually start here to
confirm to myself that there is some type of line problem.....and then
revert to the other options when things get nasty...



 HTH

 Michael Crump
 mcrump@ballfoster.com





* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *