Re: How to clear old routes

[Charles Wilt <charles.wilt@xxxxxxxxx>]

90 seems unlikely to be a special value...

I suspect that just changing it causes the aged routes to be deleted...

Also the default appears to be 10s not 120...
*DFT
    The default assembly time of 10 seconds is used.

Charles

On Thu, Mar 23, 2017 at 9:52 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

> Change to a value you desire, other than 90.
> 90 is a special "hidden" value to clear the routes.
>
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Chris Bipes
> Sent: Thursday, March 23, 2017 11:50 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: How to clear old routes
>
> My IP reassembly time-out is set at 10 seconds.    Changed to 90.  New
> route is being used almost immediately.   Should I leave at 90 change back
> to 10 or set at default of 120?
>
> Chris Bipes
> Director of Information Services
> CrossCheck, Inc.
>
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Steinmetz, Paul
> Sent: Thursday, March 23, 2017 8:38 AM
> To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
> Subject: RE: How to clear old routes
>
> For "learned routes" I've use the procedure below.
>
> NETSTAT
> 2. Display IPv4 route information
> Find route in question
>
> CHGTCPA
> Change to 90
> IP reassembly time-out . . . . .   90           5-120, *SAME, *DFT
>
> Wait 2 minutes
> F5=Refresh
> Route in question should be gone.
>
> CHGTCPA
> Change back to  120
>
>
> IBM Incident Summary
>
>     Document Number:   21031416
>   ____________________________________________________________
>   Functional Area:                       Print
>   SubFunctional Area:               Network Print from iSeries
>   SubSubFunctional Area:       General
>   ____________________________________________________________
>   Product:
>   Release:  R440
>
>   Classification:       Entitled/Advanced
>
>   Keywords:
>  ____________________________________________________________
>  Document Title:ICMP Unable to PING Printer IP Address  Document Problem
> Summary:
>   IBM(r) OS/400(r) spooled files will not print to a LAN-attached printer,
> because the printer's IP address cannot be PINGed successfully from
> OS/400(r) .
>  Resolution:
>   Option 2 (Display TCP/IP route information) from the Work with TCP/IP
> Network Status (NETSTAT) command showed that an *ICMP route destination
> existed with the printer's IP address.
>
> This problem was resolved by using the Change TCP/IP Attributes (CHGTCPA)
> command to set the IP reassembly time-out (IPRSBTIMO) parameter to 90.
> This will cause OS/400(r) to delete aged ICMP redirect routes and allow IP
> packets to pass through the correct interface to the printer.
>  References:
>   None identified.
>
>
> Paul
>
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Rob Berendt
> Sent: Thursday, March 23, 2017 11:23 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: How to clear old routes
>
> Any of these help?
> https://www-304.ibm.com/support/docview.wss?uid=nas8N1015699
> http://www-01.ibm.com/support/docview.wss?uid=nas8N1017311
> https://www.itjungle.com/2014/03/05/fhg030514-story03/
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
> To:     "'Midrange Systems Technical Discussion'"
> <midrange-l@xxxxxxxxxxxx>
> Date:   03/23/2017 11:08 AM
> Subject:        How to clear old routes
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> We have just installed a new faster MPLS network. I have updated all the
> default routers, adding the new routes and removing the old routes.
>
> I still have one iSeries at V6R1 that is still using the old route.  I
> verified it is not in the local routing list, cfgtcp - Work with TCP/IP
> Routes.
>
> So it is sending data down the old route and receiving the responses
> through the new route.  (Not the best situation.)
>
> Anyone know how to flush the learned routing table on an iSeries at 6.1?
>
> Chris Bipes
> Director of Information Services
> CrossCheck, Inc.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD