ERROR 250 on FUP DUP to another Node

[Bry Pas]

Hello everyone,

We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?

[Keith Dick]

Post by Bry Pas
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?

I don't remember whether there is a different error for system down.

Do you know whether the Expand paths in your network are carried via TCP/IP vs. an old-style leased line or some other old-style way? If you know the Expand paths are carried over TCP/IP, you should be able to learn the IP address of the target system and use Linux or Windows tools to look at paths to that system to see whether the paths are up, and maybe whether the system itself is up (or at least whether its TCP/IP handlers are up).

[wbreidbach]

Post by Keith Dick

Post by Bry Pas
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?

I don't remember whether there is a different error for system down.
Do you know whether the Expand paths in your network are carried via TCP/IP vs. an old-style leased line or some other old-style way? If you know the Expand paths are carried over TCP/IP, you should be able to learn the IP address of the target system and use Linux or Windows tools to look at paths to that system to see whether the paths are up, and maybe whether the system itself is up (or at least whether its TCP/IP handlers are up).

Error 250 just says that there is no way to reach the target system from the local system. The reason can be either a network problem or a problem with the target system. You can use SCF INFO PROCESS $NCP, NETMAP to see all systems you can reach from your local system.

[Randall]

Post by Bry Pas
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?

I hate to ask... is your EXPAND network running over a public IP network? I do not a few customers who do this. I saw error 250 (pretty sure, it was a decade ago) resulting from transient router problems on the upstream network.

[Bill Honaker]

Post by Bry Pas
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?

Whether your connection is old-fashioned WANs or (more likely these days) TCP/IP, Expand has configurations on those paths for retransmissions and timeouts.
Those are designed to allow the connections to be resilient to temporary commucations issues.

TCP/IP also has similar settings, with defaults for end-to-end processing. If I recall, the per-session defaults can be overridden in the Expand configuration.

Do you have access to the EMS logs on your system and on the target system? Can you check to see if errors were reported wheny your FUP failed?

You didn't say whether this was a 'constant' failure which never resolves, or an occasional one. Although it's been a very long time since I diagnosed these,
I seem to remember that it's possible to configure path connection parameters in such a way that large file transfers can cause failures.

Have you reached out to the Systems Administrators to see if they're aware of the failures?

Good luck with this. Please keep us informed with what you learn.

Bill

[Bry Pas]

Post by Bill Honaker

Post by Bry Pas
Hello everyone,
We are having an error 250 (All paths to the system are down) while transferring files from one node to another. Is it a Network or a System issue?

Whether your connection is old-fashioned WANs or (more likely these days) TCP/IP, Expand has configurations on those paths for retransmissions and timeouts.
Those are designed to allow the connections to be resilient to temporary commucations issues.
TCP/IP also has similar settings, with defaults for end-to-end processing. If I recall, the per-session defaults can be overridden in the Expand configuration.
Do you have access to the EMS logs on your system and on the target system? Can you check to see if errors were reported wheny your FUP failed?
You didn't say whether this was a 'constant' failure which never resolves, or an occasional one. Although it's been a very long time since I diagnosed these,
I seem to remember that it's possible to configure path connection parameters in such a way that large file transfers can cause failures.
Have you reached out to the Systems Administrators to see if they're aware of the failures?
Good luck with this. Please keep us informed with what you learn.
Bill

Hello All,

Thank you for your feedback, we just figured out that the issue was actually our link (leased line) going to another node. It went down and our network team have to recover it. Thanks again.