Weird Tracert

Unanswered Question

Hi All,


I have 2 servers one is 10.203.125.176 and the other is 10.203.125.174.


I can reach 10.203.125.176 fine but I cant reach 10.203.125.174.



when I do a tracert to 10.203.125.174 I see a 148.242.31.210 reply But router 10.207.21.9 (1 hop before) doesn't even have a route for 148.242.31.x and 10.203.125.x is directly connected.


Here is a traceroute of the Production Server:

traceroute to 10.203.125.176 (10.203.125.176), 30 hops max, 40 byte packets

1 150.110.234.3 (150.110.234.3) 0.446 ms 0.479 ms 0.451 ms

2 150.110.238.250 (150.110.238.250) 0.447 ms 0.412 ms 0.478 ms

3 RNJ7DIS03-FE1-0-0.nam.nsroot.net (150.110.238.25) 0.462 ms 2.156 ms 12.835 ms

4 rusnj7-t2a02-6509-tenge1-4.nam.nsroot.net (169.185.123.26) 0.463 ms 0.432 ms 0.481 ms

5 rusnj7-t2b02-6509-tenge2-1.nam.nsroot.net (169.185.97.205) 0.587 ms 0.439 ms 0.526 ms

6 RUSNJ19-T2B02-6509-TENGE1-2.nam.nsroot.net (169.185.99.53) 0.871 ms 0.804 ms 0.851 ms

7 rusnj19-t2a01-6509-tenge1-1.nam.nsroot.net (169.185.98.90) 4.459 ms 1.066 ms 0.977 ms

8 rusnj19-csp02-6509-ge1-1.nam.nsroot.net (199.67.219.193) 0.837 ms 0.820 ms 0.853 ms

9 RUSNJ19-CSP14-6509-GE5-2.nam.nsroot.net (199.67.219.69) 0.839 ms 0.820 ms 0.854 ms

10 10.207.98.77 (10.207.98.77) 62.877 ms 62.829 ms 62.997 ms

11 10.207.98.93 (10.207.98.93) 62.983 ms 62.821 ms 63.151 ms

12 10.213.211.137 (10.213.211.137) 81.954 ms 81.904 ms 81.834 ms

13 10.213.211.98 (10.213.211.98) 81.966 ms 82.330 ms 82.110 ms

14 10.207.21.9 (10.207.21.9) 83.763 ms 84.725 ms 85.591 ms

15 10.203.125.176 (10.203.125.176) 84.700 ms 85.156 ms 85.756 ms

$

Trace Route to Backup server:

traceroute to 10.203.125.174 (10.203.125.174), 30 hops max, 40 byte packets

1 150.110.234.3 (150.110.234.3) 0.515 ms 0.416 ms 0.457 ms

2 150.110.239.250 (150.110.239.250) 0.576 ms 0.414 ms 0.473 ms

3 RNJ7DIS04-FE1-0-0.nam.nsroot.net (150.110.238.29) 0.461 ms 0.426 ms 0.353 ms

4 rusnj7-t2a02-6509-tenge1-4.nam.nsroot.net (169.185.123.26) 0.464 ms 0.445 ms 0.479 ms

5 rusnj7-t2b02-6509-tenge2-1.nam.nsroot.net (169.185.97.205) 0.588 ms 0.443 ms 0.479 ms

6 RUSNJ19-T2B02-6509-TENGE1-2.nam.nsroot.net (169.185.99.53) 0.838 ms 0.820 ms 0.855 ms

7 rusnj19-t2a01-6509-tenge1-1.nam.nsroot.net (169.185.98.90) 1.339 ms 0.824 ms 0.852 ms

8 rusnj19-csp02-6509-ge1-1.nam.nsroot.net (199.67.219.193) 0.965 ms 0.823 ms 0.856 ms

9 RUSNJ19-CSP14-6509-GE5-2.nam.nsroot.net (199.67.219.69) 0.967 ms 0.820 ms 0.858 ms

10 10.207.98.77 (10.207.98.77) 62.870 ms 62.817 ms 62.766 ms

11 10.207.98.93 (10.207.98.93) 62.858 ms 63.074 ms 62.894 ms

12 10.213.211.137 (10.213.211.137) 82.207 ms 82.169 ms 82.374 ms

13 10.213.211.98 (10.213.211.98) 82.295 ms 81.973 ms 82.014 ms

14 10.207.21.9 (10.207.21.9) 86.311 ms 85.332 ms 84.298 ms

15 148.242.31.210 (148.242.31.210) 85.182 ms 84.375 ms 85.086 ms ?what is this????



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Mohamad Qayoom Fri, 02/13/2009 - 11:33
User Badges:
  • Bronze, 100 points or more

Does the backup server has two active NICs ?

Harold Ritter Fri, 02/13/2009 - 13:28
User Badges:
  • Cisco Employee,

Israel,


Bear in mind that this is the address with which the server is responding. Is it possible that this address is somehow configured on one of the server interface (physical or logical).


Regards

Actions

This Discussion