Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Networking
cancel
Showing results for 
Search instead for 
Did you mean: 

Duplicate Entry in routing table

shikhar_1
Regular Advisor

Duplicate Entry in routing table

Hi All,

 

This is regarding the issue reported by application team and claimed that they are facing some intermittent access problem, while accessing the DB server from their appl server.

 

I have checked but did not find any issue except duplicate entry in the routing table and issue occured after adding one route as shown below.

 

Routing tables

Destination           Gateway            Flags Refs Interface  Pmtu

127.0.0.1             127.0.0.1          UH    0    lo0       32808

192.179.0.244         192.179.0.244      UH    0    lan0      32808

196.179.0.244         196.179.0.244      UH    0    lan18     32808

135.179.32.244        135.179.32.244     UH    0    lan6      32808

135.179.33.34         135.179.33.34      UH    0    lan6:4    32808

135.179.33.35         135.179.33.35      UH    0    lan6:2    32808

135.179.33.33         135.179.33.33      UH    0    lan6:3    32808

135.179.33.44         135.179.33.44      UH    0    lan6:1    32808

135.179.44.88         135.179.44.88      UH    0    lan3      32808

135.179.44.121        135.179.44.121     UH    0    lan3:1    32808

135.179.44.113        135.179.44.113     UH    0    lan3:2    32808

135.179.44.112        135.179.44.112     UH    0    lan3:4    32808

135.179.44.111        135.179.44.111     UH    0    lan3:3    32808

192.179.0.0           192.179.0.244      U     2    lan0       1500

196.179.0.0           196.179.0.244      U     2    lan18      1500

135.179.32.0          135.179.32.244     U     6    lan6       1500

135.179.32.0          135.179.33.34      U     6    lan6:4     1500

135.179.32.0          135.179.33.33      U     6    lan6:3     1500

135.179.32.0          135.179.33.35      U     6    lan6:2     1500

135.179.32.0          135.179.33.44      U     6    lan6:1     1500

135.179.44.0          135.179.44.88      U     6    lan3       1500

135.179.44.0          135.179.44.112     U     6    lan3:4     1500

135.179.44.0          135.179.44.111     U     6    lan3:3     1500

135.179.44.0          135.179.44.113     U     6    lan3:2     1500

135.179.44.0          135.179.44.121     U     6    lan3:1     1500

10.3.240.0            135.179.44.1       UG    0    lan3       1500

135.179.106.0         135.179.44.1       UG    0    lan3       1500

135.179.108.0         135.179.44.1       UG    0    lan3       1500

135.179.40.0          135.179.44.1       UG    0    lan3       1500    <----- This route has been added recently.

135.179.40.0          135.179.44.1       UG    0    lan3       1500    <----- This route has been added recently.

127.0.0.0             127.0.0.1          U     0    lo0       32808

default               135.179.32.1       UG    0    lan6       1500

 

So my query is that can we have duplicate entry in the routing table or adding a route can affect the accessing issue.

1 REPLY
Ruel Alojado
Advisor

Re: Duplicate Entry in routing table

You need to delete  this route. 

 

135.179.40.0          135.179.44.1       UG    0    lan3       1500    <----- This route has been added recently.

135.179.40.0          135.179.44.1       UG    0    lan3       1500    <----- This route has been added recently.

 

Your server have already the route handled by this interface.

 

135.179.44.0          135.179.44.88      U     6    lan3       1500

 

 

I assume that 135.179.44.1 is your gateway to talk to other network segment. 

 

But it still not clear what is who is app and who is db server.  You have a lot of sub interface define too.