Sorry, I'm jumping into the middle of this conversation (have not been following it) and I probably should just stay out of it, maybe, but...

an *ICMP route? This occurs when another system sends an ICMP redirect packet to tell your system to use a different route. So it seems strange to me that you say you are changing it yourself... this is not something you would normally edit/setup yourself...?!

Also, I'm wondering what this has to do with the FTP problem you describe. Is 10.5.42.129 the IP address of one of the systems involved?



On 3/22/2014 7:46 PM, Steinmetz, Paul wrote:
The issue is back, the ICMP route was recreated, FTP to 2nd port again failing.

Route Subnet Next Route Type of Route Route Route
Destination Mask Hop Available Service MTU Type Source
10.5.42.129 *HOST 10.5.0.1 *YES *NORMAL 1492 *HOST *ICMP

Paul
From: Steinmetz, Paul
Sent: Wednesday, March 19, 2014 11:39 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: FTP intermittanly not working to 2nd iSeries port from PC

Found and resolved the issue.

Route Subnet Next Route Type of Route Route Route
Destination Mask Hop Available Service MTU Type Source
10.5.42.129 *HOST 10.5.0.1 *YES *NORMAL 1492 *HOST *ICMP

ICMP routes needed to be flushed, CFGTCP, option 3, change IP reassembly time-out from 120 to 90 then back to 120.
If an ICMP route previously existed for the 1st port, when the FTP was issued for the 2nd port, the ICMP route was forcing the FTP response to the 1st port, resulting in FTP failure.
I still need to identify how and why an ICMP route is improperly created and flushing needed.
Does anyone routinely flush their ICMP routes?
Are there any negatives or known issues from flushing these routes.
I'm not a network person, I need some help in this area.
IBM suggested I ask our network folks if redirects are enabled for the default gateway.
I have 2 ports, 2 default gateways, I assume both need to be questioned.
*DFTROUTE *NONE 10.5.0.2 10.5.2.5
*DFTROUTE *NONE 10.5.23.254 10.5.23.5

From: Steinmetz, Paul
Sent: Friday, March 14, 2014 3:51 PM
To: 'Midrange Systems Technical Discussion'
Subject: FTP intermittanly not working to 2nd iSeries port from PC


We have two LPARS, production and r&d.

Each LPAR has a 2-port 9055(5767) 10/100/1000 Base-TX Ethernet PCI Express Adapt

The first port only goes through the main corporate firewall.

The 2nd port also goes through a 2nd firewall for each partition.



Both LPARs configured the same.

Production is V6R1M1, R&D V7R1M0.



Each LPAR has two interfaces and two default routes.

Internet Subnet Line Line

Address Mask Description Type



10.5.2.5 255.255.248.0 ETHERLAN01 *ELAN

10.5.23.5 255.255.255.0 ETHERLAN02 *ELAN



Route Subnet Next Preferred

Destination Mask Hop Interface



*DFTROUTE *NONE 10.5.0.2 10.5.2.5

*DFTROUTE *NONE 10.5.23.254 10.5.23.5



R&D, both ports(IPS) work, no issue.

Production, first port always works, no issue.

Production, 2nd port works from some PCs with no issue, other PC inconsistent.

Our network/firewall/security staff confirmed all should working, they can production 2nd port without any issue.

They are stating it is a setting on the iSeries.

For the last few weeks I could not FTP to production 2nd port.

I rebooted PC, worked for a bit, today not working.

When it fails, I never get a FTP user log in screen.

Any thoughts from the group.



ftp 10.5.23.5<ftp://ftp%2010.5.23.5>

ftp>



Thank You

_____

Paul Steinmetz

IBM i Systems Administrator



Pencor Services, Inc.

462 Delaware Ave

Palmerton Pa 18071



610-826-9117 work

610-826-9188 fax

610-349-0913 cell

610-377-6012 home



psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>

http://www.pencor.com/






As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.