Re: abort errors, again...

Stephen Fisher (lithium@cia-g.com)
Thu, 19 Sep 1996 15:30:09 -0600 (MDT)

I used to get more errors than that when my Frame-relay T1 was fine.

I now use a Cisco on the line (I'm going to expand what is thought the
PM2eR can handle well) and now get 0 errors (the only thing that has
changed was the V.35 cable) and the lowest possible ping rate to my NAP
dropped 5ms.

This doesn't seem to be the only case, at a remote site I have a 56k
frame-relay going to a PM2eR and get lots of errors there too.

On Thu, 19 Sep 1996, Jacob Suter wrote:

> Command> sh w1
> ----------------------- Current Status - Port W1
> ---------------------------
> Status: ESTABLISHED
> Input: 290350674 Abort Errors: 15
> Output: 51002508 CRC Errors: 0
> Pending: 0 Overrun Errors: 0
> TX Errors: 0 Frame Errors: 0
> Modem Status: DCD+ CTS+
>
> Active Configuration Default Configuration
> -------------------- ---------------------
> Port Type: Netwrk Netwrk (Hardwired)
> Line Speed: Ext 56K Ext Clock
> Modem Control: off off
> Modem Config: Not Configured card-288
> Remote Host: CISCO.INTRASTAR.NET CISCO.INTRASTAR.NET
> Local Address: WAN1.INTRASTAR.NET WAN1.INTRASTAR.NET
> Netmask: 255.255.255.0 255.255.255.0
> Interface: ptpW1 (PPP,Listen) (PPP,Quiet)
> Mtu: 1500 1500
> Dial Group: 0
>
> This in a period of...
>
> Command> ver
> Livingston Enterprises PortMaster Version 3.3.2
> System uptime is 2 days 17 hours 33 minutes
> Command>
>
> This is about five times as fast as it usually occurs. GTE claims
> everything is "ok" (lie lie lie, I tell you!), so what do I tell GTE to
> go fix?