ftp large files fail, small files succeed

[Oswald Knoppers_1]

>okay, but given that I had to abort it after 20 minutes, I'm concerned about its impact on the system, and I don't know how long it's going to run, therefore my hesitation on running it on the prod system or targeted at the prod system...

>sorry, I like to understand things fully before I do things on/to prod...

It won't have any impact. But just start the commando om HNATST with /port=remote=20 on a separate window and then do your FTP command. You can also compare with getting the small file.

Oswald

[Hoff]

>file either.......unless I'm missing something?
>longer answer is that ftp under "server options" on both systems is started and enabled.

Without a view into the network (and diagnostics and log files and...), I'm shot-gunning. Like the rest of this thread has been doing, for a week or so now.

>as you can see below, the log file is configured, I don't know why it's not coming out...

That's close to the nub, isn't it One obvious potential answer being "you're not getting to the host you think you're connecting to".

Check the login directory for whatever user is involved here for ftp logs, too.

It's distinctly possible that there's something in the remote login that's blowing up ftp, too. Wouldn't be the first time somebody had a buggy LOGIN or SYLOGIN.

Could also be a ;32767 file version is blocking creation.

Trace from source to destination, confirm the IP addresses, confirm open ports, and why FTP is going into the weeds, and see if sftp works.

It's arguably more remarkable when ftp works than when it fails; in the recent era of network design, the default state of ftp is "not working".

[Ron Kaledas]

okay, I will try that. wasn't clear that I needed to do an ftp at the same time, sorry!

anyway, an update - once the firewall issue got fixed, I was able to transfer my large file directly to hnatst from my laptop (via ftp put).

so now I can go laptop to hnaa, and laptop to hnatst, but not hnaa to hnatst (via get on hnatst nor put on hnaa).

[Ron Kaledas]

Hoff - yeah, I understand the "shot in the dark" aspect of helping via forum...imagine my frustration!

I think most of what you're suggesting can be eliminated by the examples I've shown, I am connecting to the correct system, there is no disk space or version number problem, no login.com problem, etc...

haven't tried sftp yet, but could that really work where ftp doesn't (in this case)? I'll take a look, probably more out of frustration than anything else...

[Robert Gezelter]

Ron,

In addition to what Hoff has mentioned, do check the Disk Quotas on the relevant disks (e.g., log file creation and other file creation can become interesting if the disk quotas are exceeded).

The command is SHOW QUOTA/USER=[identifier]

- Bob Gezelter

[Ron Kaledas]

okay, here's (part of) the results of that tcptrace while the ftp was being attempted...in the interest (somewhat) of brevity, I did not include all of the output - there was a lot!

so, does this tell you anything? or, did I not include the right parts of the output, maybe?


--------------------------------------------------------------------------------

TCPtrace full display XMT packet 891 at 20-JUL-2010 10:42:32.40

IP Version = 4, IHL = 5, TOS = 00, Total Length = 192 = ^x00C0
IP Identifier = ^x0287, Flags (0=0,DF=1,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 60 = ^x3C, Protocol = 6 = ^x06, Header Checksum = ^x0533
IP Source Address = 10.252.16.60
IP Destination Address = 10.252.16.75

TCP Source Port = 20, TCP Destination Port = 49207
TCP Sequence Number = 2041910197 = ^x79B513B5
TCP Acknowledge Number = 3193669793 = ^xBE5B88A1
Flags (URG=0,ACK=1,PSH=1,RST=0,SYN=0,FIN=0),
Window = 61440 = ^xF000
TCP Checksum = ^x6394, Urgent Pointer = 0 = ^x0000

3C10FC0A 3305063C 00408702 C0000045 0000 E.....@.<..3...<
A1885BBE B513B579 37C01400 | 4B10FC0A 0010 ...K...7y....[..
0D313B45 58455049 | 00009463 00F01850 0020 P...c...IPEXE;1.
20202020 20202020 20202020 2020200A 0030 .
3230312F 32323532 30312020 20202020 0040 102522/102
322D4345 442D3731 20202020 20383235 0050 528 17-DEC-2
535B2020 35333A39 323A3831 20393030 0060 009 18:29:35 [S
20202020 20202020 20205D4D 45545359 0070 YSTEM]
522C4457 522C4445 57522820 20202020 0080 (RWED,RWD,R
20666F20 6C61746F 540A0D0A 0D29522C 0090 ,R)....Total of
37393239 3138202C 73656C69 66203231 00A0 12 files, 819297
0A0D736B 636F6C62 20363933 3931382F 00B0 /819396 blocks..




--------------------------------------------------------------------------------

TCPtrace full display XMT packet 893 at 20-JUL-2010 10:42:32.40

IP Version = 4, IHL = 5, TOS = 00, Total Length = 40 = ^x0028
IP Identifier = ^x0289, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 60 = ^x3C, Protocol = 6 = ^x06, Header Checksum = ^x45C9
IP Source Address = 10.252.16.60
IP Destination Address = 10.252.16.75

TCP Source Port = 20, TCP Destination Port = 49207
TCP Sequence Number = 2041910349 = ^x79B5144D
TCP Acknowledge Number = 3193669793 = ^xBE5B88A1
Flags (URG=0,ACK=1,PSH=0,RST=0,SYN=0,FIN=1),
Window = 61440 = ^xF000
TCP Checksum = ^xF408, Urgent Pointer = 0 = ^x0000

3C10FC0A C945063C 00008902 28000045 0000 E..(....<.E....<
A1885BBE 4D14B579 37C01400 | 4B10FC0A 0010 ...K...7y..M.[..
| 000008F4 00F01150 0020 P.......




--------------------------------------------------------------------------------

TCPtrace full display RCV packet 894 at 20-JUL-2010 10:42:32.40

IP Version = 4, IHL = 5, TOS = 00, Total Length = 40 = ^x0028
IP Identifier = ^x895B, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 60 = ^x3C, Protocol = 6 = ^x06, Header Checksum = ^xBEF6
IP Source Address = 10.252.16.75
IP Destination Address = 10.252.16.60

TCP Source Port = 49207, TCP Destination Port = 20
TCP Sequence Number = 3193669793 = ^xBE5B88A1
TCP Acknowledge Number = 2041910350 = ^x79B5144E
Flags (URG=0,ACK=1,PSH=0,RST=0,SYN=0,FIN=0),
Window = 60040 = ^xEA88
TCP Checksum = ^xF980, Urgent Pointer = 0 = ^x0000

4B10FC0A F6BE063C 00005B89 28000045 0000 E..(.[..<......K
4E14B579 A1885BBE 140037C0 | 3C10FC0A 0010 ...<.7...[..y..N
0000 00000000 | 000080F9 88EA1050 0020 P.............




--------------------------------------------------------------------------------

TCPtrace full display RCV packet 895 at 20-JUL-2010 10:42:32.40

IP Version = 4, IHL = 5, TOS = 00, Total Length = 40 = ^x0028
IP Identifier = ^x895C, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 60 = ^x3C, Protocol = 6 = ^x06, Header Checksum = ^xBEF5
IP Source Address = 10.252.16.75
IP Destination Address = 10.252.16.60

TCP Source Port = 49207, TCP Destination Port = 20
TCP Sequence Number = 3193669793 = ^xBE5B88A1
TCP Acknowledge Number = 2041910350 = ^x79B5144E
Flags (URG=0,ACK=1,PSH=0,RST=0,SYN=0,FIN=0),
Window = 61440 = ^xF000
TCP Checksum = ^xF408, Urgent Pointer = 0 = ^x0000

4B10FC0A F5BE063C 00005C89 28000045 0000 E..(.\..<......K
4E14B579 A1885BBE 140037C0 | 3C10FC0A 0010 ...<.7...[..y..N
0000 00000000 | 000008F4 00F01050 0020 P.............




--------------------------------------------------------------------------------

TCPtrace full display RCV packet 896 at 20-JUL-2010 10:42:32.40

IP Version = 4, IHL = 5, TOS = 00, Total Length = 40 = ^x0028
IP Identifier = ^x895E, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 60 = ^x3C, Protocol = 6 = ^x06, Header Checksum = ^xBEF3
IP Source Address = 10.252.16.75
IP Destination Address = 10.252.16.60

TCP Source Port = 49207, TCP Destination Port = 20
TCP Sequence Number = 3193669793 = ^xBE5B88A1
TCP Acknowledge Number = 2041910350 = ^x79B5144E
Flags (URG=0,ACK=1,PSH=0,RST=0,SYN=0,FIN=1),
Window = 61440 = ^xF000
TCP Checksum = ^xF407, Urgent Pointer = 0 = ^x0000

4B10FC0A F3BE063C 00005E89 28000045 0000 E..(.^..<......K
4E14B579 A1885BBE 140037C0 | 3C10FC0A 0010 ...<.7...[..y..N
0000 00000000 | 000007F4 00F01150 0020 P.............

[jjinva]

"this is a new test system, that got set up for this upgrade."

How was it setup? Image Backup/Restore? If so maybe a network card conflict.

TCPIP> Show int/full

On both Systems and compare. I have seen this behavior with Ethernet Address conflicts from the Image restore.

[Ron Kaledas]

well, guess what?? it's fixed!

they "looked again" at the ports...he apparently got confused because I had 2 nics on the same node, both configured to the same subnet (for lan failover).

when he figured out there was another port involved, he said that port was set to auto! and interestingly, it appeared to be negotiating to half...but lancp said the nic was 100 full. I didn't have console access remotely, so I couldn't check the console setting for ewa0, but could this be that "failed auto" problem that I was alluding to earlier?

thanks for everyone's input...bottom line was bad information from their network folks... (I had already suspected the half duplex problem, but.......)

SIGH!

(I'm still curious about an answer to the above question...)

[Ron Kaledas]

to make it clear, the port that was set to auto was connected to hnatst, and when he set it to full (fixed), the system was disconnected for a minute (so don't do this on a prod system!) and then upon reconnection, everything worked as expected...

[Hoff]

Never trust managed switches, nor the folks that run them. This not intending to impugn the vendors nor the staff, but rather the complexity of many of the managed network devices and the configurations and the UIs and the random port weirdnesses; constructs in aggregate that conspire to flummox.