Re: FTP and file transfer speeds

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

Well the numbers aren't as low as I'd like to see but this quantity of 
errors over this time period isn't going to drop speeds by the amount 
your statistics shown. It might hurt by a few percentage points at 
worst.  So now you need to find a new place to look, perhaps one of the 
servers on the DMZ that you are taking to. Can you FTP between servers 
in the DMZ and test speed there? That would test those servers 
connection to the switch there and eliminate that as a problem. Make 
sure you push data both in and out of the target server just to be sure.

- Larry

ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
> Ok... update time... here are the interface stats on the PIX from this
> morning since clearing them yesterday... i'm seeing the input errors more
> on the inside interface than the DMZ... should I be suspecting that
> instead?  I still see some runts on the DMZ also, though...
>
> Result of firewall command: "show interface"
>
> interface ethernet0 "outside" is up, line protocol is up
>   Hardware is i82559 ethernet, address is 0005.328f.cf66
>   IP address 12.161.209.241, subnet mask 255.255.255.248
>   MTU 1500 bytes, BW 100000 Kbit full duplex
>       253378 packets input, 184274615 bytes, 0 no buffer
>       Received 112 broadcasts, 0 runts, 0 giants
>       151 input errors, 97 CRC, 54 frame, 0 overrun, 97 ignored, 0 abort
>       231092 packets output, 69124183 bytes, 0 underruns
>       0 output errors, 0 collisions, 0 interface resets
>       0 babbles, 0 late collisions, 0 deferred
>       0 lost carrier, 0 no carrier
>       input queue (curr/max blocks): hardware (128/128) software (0/5)
>       output queue (curr/max blocks): hardware (0/37) software (0/4)
> interface ethernet1 "inside" is up, line protocol is up
>   Hardware is i82559 ethernet, address is 0005.328f.cf67
>   IP address 172.17.1.25, subnet mask 255.255.0.0
>   MTU 1500 bytes, BW 100000 Kbit full duplex
>       559103 packets input, 117982246 bytes, 0 no buffer
>       Received 99499 broadcasts, 1048 runts, 0 giants
>       1875 input errors, 955 CRC, 920 frame, 0 overrun, 955 ignored, 0
> abort
>       617775 packets output, 427740103 bytes, 0 underruns
>       0 output errors, 0 collisions, 0 interface resets
>       0 babbles, 0 late collisions, 0 deferred
>       0 lost carrier, 0 no carrier
>       input queue (curr/max blocks): hardware (128/128) software (0/38)
>       output queue (curr/max blocks): hardware (1/35) software (0/4)
> interface ethernet2 "dmz" is up, line protocol is up
>   Hardware is i82559 ethernet, address is 0002.b33d.3be0
>   IP address 172.18.1.25, subnet mask 255.255.255.0
>   MTU 1500 bytes, BW 100000 Kbit full duplex
>       453436 packets input, 284576767 bytes, 0 no buffer
>       Received 3269 broadcasts, 679 runts, 0 giants
>       27 input errors, 15 CRC, 12 frame, 0 overrun, 15 ignored, 0 abort
>       333512 packets output, 94196932 bytes, 0 underruns
>       0 output errors, 0 collisions, 0 interface resets
>       0 babbles, 0 late collisions, 0 deferred
>       0 lost carrier, 0 no carrier
>       input queue (curr/max blocks): hardware (128/128) software (0/12)
>       output queue (curr/max blocks): hardware (0/8) software (0/2)
> interface ethernet3 "dmz1" is up, line protocol is up
>   Hardware is i82558 ethernet, address is 00e0.b604.f78b
>   IP address 10.0.0.25, subnet mask 255.255.255.0
>   MTU 1500 bytes, BW 100000 Kbit full duplex
>       98743 packets input, 26035505 bytes, 0 no buffer
>       Received 90331 broadcasts, 0 runts, 0 giants
>       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
>       8236 packets output, 513548 bytes, 0 underruns
>       0 output errors, 0 collisions, 0 interface resets
>       0 babbles, 0 late collisions, 0 deferred
>       0 lost carrier, 0 no carrier
>       input queue (curr/max blocks): hardware (128/128) software (0/2)
>       output queue (curr/max blocks): hardware (0/1) software (0/1)
> interface ethernet4 "dmz2" is up, line protocol is up
>   Hardware is i82558 ethernet, address is 00e0.b604.f78a
>   IP address 172.19.1.25, subnet mask 255.255.255.0
>   MTU 1500 bytes, BW 100000 Kbit full duplex
>       3380 packets input, 226451 bytes, 0 no buffer
>       Received 381 broadcasts, 0 runts, 0 giants
>       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
>       10641 packets output, 838371 bytes, 0 underruns
>       0 output errors, 0 collisions, 0 interface resets
>       0 babbles, 0 late collisions, 0 deferred
>       0 lost carrier, 0 no carrier
>       input queue (curr/max blocks): hardware (128/128) software (0/1)
>       output queue (curr/max blocks): hardware (0/3) software (0/1)
> interface ethernet5 "intf5" is up, line protocol is up
>   Hardware is i82558 ethernet, address is 00e0.b604.f789
>   IP address 172.11.1.25, subnet mask 255.255.255.0
>   MTU 1500 bytes, BW 100000 Kbit full duplex
>       7732 packets input, 463920 bytes, 0 no buffer
>       Received 0 broadcasts, 0 runts, 0 giants
>       0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
>       7712 packets output, 462720 bytes, 0 underruns
>       0 output errors, 0 collisions, 0 interface resets
>       0 babbles, 0 late collisions, 0 deferred
>       0 lost carrier, 0 no carrier
>       input queue (curr/max blocks): hardware (128/128) software (0/1)
>       output queue (curr/max blocks): hardware (0/1) software (0/1)
>
>
>