RE: Bad TCP/IP routes

[Rob Berendt <rob@xxxxxxxxx>]

Buddy,

I didn't catch your earlier email.  We've had a real problem with these 
learned routes also.  Seems like we were doing something stupid like 
using internal addresses that are commonly used on the outside instead 
of reserved addresses, (like having them begin with 198 instead of 10).  
My boss's computer was usually the first one to take the big hit.  We 
started out by assigning him a couple of addressed to use until we could 
IPL the 400.  Dropping TCP didn't do squat.  We did some additional 
tricks.  Some were by playing with the Cisco routers.  One was by adding 
routes.  Detail as follows.  We have multiple rings with routers between 
each ring.  If boss's address was 198.4.1.123 we would add a route 
telling all the 198.4.... addresses to go to 198.4.1.201, an internal 
router.  This stopped it from trying the router pointing to the internet.
GO CFGTCP
2. Work with TCP/IP routes
198.4.0.0       255.255.0.0      198.1.1.2        198.1.1.201





MARK_WELTE@denso-diam.com on 04/19/99 10:01:04 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        RE: Bad TCP/IP routes

I cannot drop TCP/IP everytime this happens. That would cause me to have to
drop over 100 users that are functioning just fine. If I can delete the bad
routes "on the fly", then the users would not be impacted.

Thanks for the suggestion,
Mark



Alex A. Moore ~ CIO
Ellis Hosiery Mills, Inc.
alexm@ellishosiery.com <mailto:alexm@ellishosiery.com>


> I've done a NETSTAT *RTE and then press F6 for a listing of all the
routes.
> I can see the offending route there. I cannot delete it there. When I go
to
> CFGTCP option 2, it just shows me the routes that I've entered. None of
the
> *ICMP routes are there. I then created the offending route entry manually
> (CFGTCP option 2) and then deleted my manual entry and that cleaned it
up.
TCP/IP configuration manual states that a restart of TCP will force a
rebuild of the "learned" routes.



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---