Traceroute and backup traffic issue

[R.O.]

Hello,

Why does traceroute choose "lan3" instead "lan7" to go to "10.40.78.69"? I have added routes (*) to force backup traffic go through lan7, but backup traffic and traceroute still go through lan3


server1:/># netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
10.40.47.138 10.40.47.138 UH 0 lan7 4136
192.168.0.1 192.168.0.1 UH 0 lan0 4136
10.40.4.247 10.40.4.247 UH 0 lan3 4136
10.40.4.219 10.40.4.219 UH 0 lan3:1 4136
10.40.78.69 10.40.47.138 UH 0 lan7 0 (*)
10.40.78.38 10.40.47.138 UH 0 lan7 0 (*)
10.40.78.30 10.40.47.138 UH 0 lan7 0 (*)
10.40.176.18 10.40.47.138 UH 0 lan7 0 (*)
10.40.176.23 10.40.47.138 UH 0 lan7 0 (*)
10.40.47.0 10.40.47.138 U 2 lan7 1500
10.40.4.0 10.40.4.247 U 3 lan3 1500
10.40.4.0 10.40.4.219 U 3 lan3:1 1500
192.168.0.0 192.168.0.1 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 10.40.4.1 UG 0 lan3 0


server1:/># traceroute 10.40.78.69
traceroute: Warning: Multiple interfaces found; using 10.40.4.247 @ lan3
traceroute to 10.40.78.69 (10.40.78.69), 30 hops max, 40 byte packets
....


Regards,

[TTr · Accepted solution]

If you have multiple interfaces, you have to *tell* traceroute which one to use, it does not look at the routing table. The traceroute command is meant to show you what route is followed outside your server so you have to tell traceroute which interface to use as in
traceroute -i 10.40.47.138 10.40.78.69
Now for the backup traffic, which software are you using and is the server above the backup server or a backup client?

[R.O.]

Thanks, my question was specially about traceroute command. Backup team has succeded in configuring backup through backup network.

Kind regards,