× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2005

Re: FTP and file transfer speeds

Yah that's high. Although a CLEAR COUNTERS will set everything back to 0 to see if those are new or old errors. I've got PIXs moving TB of data with errors less than 1000 total and you are only in the MB range yet. This is one reason why we typically avoid unmanaged equipment in the data center - no way to get into it and see errors. The Netgear stuff typically works but when it doesn't you have no idea if it's just a port or something else. Try new cables first and use a different port in the switch too. After the CLEAR COUNTERS see if the connection is better. - Larry 

ChadB@xxxxxxxxxxxxxxxxxxxx wrote:

I notice the input errors to a lesser extent on the other PIX interfaces,
but it sounds like you're sure that's way high.  Our DMZ setup is the
Netgear switch, a cable to the primary PIX, a cable to the failover PIX, a
cable to a model 520 5706 integrated ethernet port, and a cable to a model
800 2849 ethernet port.
Larry Bolhuis <lbolhuis@arbsol. com> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 11/28/2005 01:56 Subject PM Re: FTP and file transfer speeds Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> 



Chad,

  Can't tell why just yet but this is your problem: (Snipped from the
DMZ interface statistics)

      Received 2900311 broadcasts, 124672 runts, 0 giants
      3198558 input errors, 695102 CRC, 2502959 frame, 497 overrun, 695102
ignored, 0 abort

   What is the device on the DMZ side of the PIX? The connected between
that device (hopefully another switch) and the PIX is not happy. Over 3
million errors and since they are splattered amongst CRC, Frame,
Overrun, and 'Ignored' it's likely a bad cable, bad port, or bad device
on that end. It COULD be a bad PIX port but I've not had any of those fail.

   I'd start there!

       - Larry

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.