Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

routing problems

Status
Not open for further replies.
mrn

mrn

MIS
Apr 27, 2001
3,993
GB
AIX 4320

I'm having a couple of very strange routing problems. I have added through smitty the following static route.

host
des add = 10.10.5.40
gateway = 1.1.60.1

do a netstat -rn|grep 10.10.5.40

10.11.5.40 1.1.60.1 UGHM 1 12 en0 - -

now ping 10.11.5.40 it drops packets

10.11.5.18
PING 10.11.5.40: (10.11.5.40): 56 data bytes
64 bytes from 10.11.5.40: icmp_seq=0 ttl=254 time=0 ms
64 bytes from 10.11.5.40: icmp_seq=1 ttl=254 time=0 ms
64 bytes from 10.11.5.40: icmp_seq=3 ttl=254 time=0 ms
64 bytes from 10.11.5.40: icmp_seq=5 ttl=254 time=0 ms

----10.11.5.40 PING Statistics----
6 packets transmitted, 4 packets received, 33% packet loss
round-trip min/avg/max = 0/0/0 ms

do a netstat -rn|grep 10.10.5.40

10.11.5.40 1.71.0.1 UGHMS 1 19 en0 - -

Why is the gateway changing?

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

 
Sort by date Sort by votes
The M in UGHMS means that the route has been modified by a redirect, so I guess your routers don't think 1.1.60.1 is the right gateway, or maybe it's down.

I don't imagine using IANA reserved addresses for the routers helps, either, though it might not hurt, either.



Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L
CompTIA Linux+
CompTIA Security+

 
Upvote 0 Downvote
Thanks Rod,

The gateway is available and ping-able from the same machine. The IANA isn't the problem.

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

 
Upvote 0 Downvote
I would turn off path mtu discovery. It can change your routing table and have very undesirable affects.
no -o udp_pmtu_discover=0
no -o tcp_pmtu_discover=0


Jim Hirschauer
 
Upvote 0 Downvote
root coloning is already turned off.

From /etc/rc.net

# Turn off route coloning
no -o tcp_pmtu_discover=0
no -o udp_pmtu_discover=0

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

 
Upvote 0 Downvote
Found the following

1st traceroute

traceroute 10.11.5.40
trying to get source for 10.11.5.40
source should be 1.0.0.138
traceroute to 10.11.5.40 (10.11.5.40) from 1.0.0.138 (1.0.0.138), 30 hops max
outgoing MTU = 1500
1 * * *
2 * server_liv (10.11.5.40) 2 ms *

2nd traceroute

traceroute 10.11.5.40
trying to get source for 10.11.5.40
source should be 1.0.0.138
traceroute to 10.11.5.40 (10.11.5.40) from 1.0.0.138 (1.0.0.138), 30 hops max
outgoing MTU = 1500
1 * * *
2 server_liv (10.11.5.40) 3 ms * 2 ms

3rd trace route

traceroute 10.11.5.40
trying to get source for 10.11.5.40
source should be 1.0.0.138
traceroute to 10.11.5.40 (10.11.5.40) from 1.0.0.138 (1.0.0.138), 30 hops max
outgoing MTU = 1500
1 * * vpn1 (1.1.50.1) 6 ms
2 * * *
3 * server_liv (10.11.5.40) 10 ms *

It looks as though it's finding different routes to the same server!



Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

 
Upvote 0 Downvote
I'm still having problems with this. Anyone else got any ideas?

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

 
Upvote 0 Downvote
I bit more info. I've discovered that the 1.17.0.1 address is a firewall. I have another machine with the same route connected to the same switch that works with no problems. I'm still failing to understand where the "new route" is comming from.

netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups

Route Tree for Protocol Family 2 (Internet):
default 1.161.50.1 UG 1 15697 en0 - -
1/8 1.0.0.138 U 155 1408733 en0 - -
1.1/16 1.0.5.1 UG 1 150 en0 - -
1.1.1.3 1.161.50.1 UGH 0 6586 en0 - -
1.1.1.18 1.161.50.1 UGH 0 0 en0 - -
1.1.4.100 1.161.50.1 UGHD 0 0 en0 - 1
10.10/16 1.161.50.1 UG 0 315 en0 - -
10.11.1/24 1.161.50.1 UG 0 1465 en0 - -
10.11.1.10 1.161.50.1 UGH 0 0 en0 - -
10.11.5/24 1.161.50.1 UG 0 7 en0 - -
10.11.5.10 1.71.0.1 UGH 0 0 en0 - -
10.11.28.18 1.162.0.26 UGH 0 0 en0 - -
10.14.131.23 1.162.0.26 UGH 0 0 en0 - -
10.14.149.254 1.162.0.26 UGH 0 0 en0 - -
10.17/16 1.162.0.26 UG 0 0 en0 - -
10.17.1.152 1.162.0.26 UGH 1 9608 en0 - -
10.22.100.15 1.0.0.39 UGH 0 0 en0 - -
10.23.100.102 1.0.0.39 UGH 0 12266 en0 - -
10.23.100.105 1.0.0.39 UGH 0 2044 en0 - -
10.103.161.1 1.162.0.26 UGH 0 0 en0 - -
10.106.9.20 1.162.0.26 UGH 1 381 en0 - -
10.137.66.20 1.162.0.26 UGH 0 998 en0 - -
10.160.36.24 1.162.0.26 UGH 0 0 en0 - -
10.160.38.70 1.162.0.26 UGH 0 184 en0 - -
10.160.38.100 1.162.0.26 UGH 0 0 en0 - -
10.160.39.34 1.162.0.26 UGH 0 3 en0 - -
10.162.31.28 1.162.0.26 UGH 0 0 en0 - -
10.192.2.18 1.162.0.26 UGH 2 12096 en0 - -
10.192.2.45 1.162.0.26 UGH 0 3132 en0 - -
10.224.9.249 1.162.0.26 UGH 0 0 en0 - -
71/8 71.1.1.199 U 0 590 en1 - -
71.1.1.11 1.71.0.1 UGH 0 0 en0 - -
71.2.13.1 1.71.0.1 UGH 0 0 en0 - -
71.2.33.3 1.1.254.3 UGH 0 0 en0 - -
123.123.123/24 123.123.123.1 U 0 0 en3 - -
127/8 127.0.0.1 UR 0 1 lo0 - -
127.0.0.1 127.0.0.1 UH 12 28932295 lo0 - -
128.199/24 1.161.50.1 UG 0 0 en0 - - =>
128.199/16 1.162.11.1 UGS 0 0 en0 - -
129.199/24 1.161.50.1 UG 0 0 en0 - -
130.36.40.2 1.161.50.1 UGH 0 0 en0 - -
130.36.100.100 1.162.0.26 UGH 0 10 en0 - -
130.130.74.1 1.162.5.5 UGH 0 8770 en0 - -
138.0/24 1.162.4.243 UG 0 0 en0 - -
138.80/24 1.162.4.243 UG 0 0 en0 - -
138.81/24 1.162.4.243 UG 0 0 en0 - -
144.11/16 1.161.50.1 UG 0 0 en0 - -
164.0/8 1.162.5.1 UG 0 0 en0 - -
167.184.208.23 1.161.50.1 UGH 0 0 en0 - -
167.184.208.24 1.161.50.1 UGH 0 0 en0 - -
172.0/8 1.0.0.34 UG 0 0 en0 - -
172.16.99/24 1.161.50.1 UG 0 0 en0 - -
172.30.20.10 1.162.4.243 UGH 0 0 en0 - -
192.168.0/24 1.6.1.200 UGS 0 0 en0 - -
192.168.2.10/32 1.192.2.197 UG 0 0 en0 - -
192.168.2.13/32 1.192.2.197 UG 0 0 en0 - -
192.168.3/24 1.162.4.202 UG 0 0 en0 - -
192.168.9/24 1.161.50.1 UG 3 19176 en0 - -
192.168.10/24 1.0.5.1 UGS 0 0 en0 - -
192.168.192.234 1.161.50.1 UGH 0 0 en0 - -
192.168.240/24 1.162.11.2 UG 0 0 en0 - -
194.201.64.96/28 194.201.64.106 U 1 4600 en2 - -
194.201.64.108/32 1.192.2.197 UG 0 0 en0 - -
198.168.20/24 1.161.50.1 UG 0 0 en0 - -
213.239.59.27 1.161.50.1 UGH 0 0 en0 - -

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

austinhealy
  • Locked
  • Question
routing table
Replies
1
Views
53
w5000
w5000
nmorph
  • Locked
  • Question
HA Problems
Replies
2
Views
122
nmorph
nmorph
holdahl
  • Locked
  • Question
problems using DSH
Replies
5
Views
200
holdahl
holdahl
holdahl
  • Locked
  • Question
problems with NFS mount
Replies
3
Views
157
holdahl
holdahl
phorbiuz
  • Locked
  • Question
HACMP routing
Replies
3
Views
56
DSMARWAY
DSMARWAY

Part and Inventory Search

Sponsor

Back
Top