Traffic forwarding to wrong Node/ip

[muralikrishnan.chelakara]

Hello Guys,

I need a expert advise on my query .

Situation : I have a destination ip 45.xx.xx.xx and this ip i am learning from ebgp AS19xx . If i run a trace route from the the router or any where from my network  trace is forwarding to wrong hop and node , but if i check the cef and bgp table everything is good but the trace is weird , trace is going to another link which the destination don't have any relation with that node . 

sh cef exact-route 12.xx.xx.xx 45.xx.xx.xx
45.xx.xx.0/24, version 6200272, internal 0x5000001 0x0 (ptr 0x55b207c4) [1], 0x0 (0x0), 0x0 (0x0)
 Updated Jun 28 21:54:59.174
 Prefix Len 24, traffic index 0, precedence n/a, priority 4
 BGP Attribute: id: 0x48d74, Local id: 0x3535, Origin AS: 19xx, Next Hop AS: 19xx 
 
   via Bundle-Ether22
   via 192.xx,xx,xx, 3 dependencies, recursive, bgp-ext [flags 0x6020]
    path-idx 0 NHID 0x0 [0x5a7ab06c 0x0]
    next hop 192.xx.x.xx.x via 192.xx.xx.xx

traceroute  45.xx.xx.xx

Type escape sequence to abort.
Tracing the route to 45.xx.xx.xx

 1  116.xx.xx.xx 1 msec  0 msec  0 msec >>>> wrong next hop it should go via 192.xx.xx.xx
 2   *  * 

[Georg Pauwen]

Hello,

how are you connected to 116.xx.xx.xx ? Is that in your routing table ? Can you post the output of 'show ip route' ?

[muralikrishnan.chelakara]

sh route 116.xx.xx.xx

Routing entry for 116.xx.xx.xx/30
Known via "connected", distance 0, metric 0 (connected)
Installed Jun 28 20:26:22.832 for 5d23h
Routing Descriptor Blocks
directly connected, via GigabitEthernet100/0/0/18
Route metric is 0
No advertising protos.

[Georg Pauwen]

Hello,

116.xx.xx.xx/30 is directly connected. When you do a traceroute, what is the source of the traceroute (when you use an extended traceroute) ?

[muralikrishnan.chelakara]

with any source the traffic is not forwarding to actual next-hop , 

traceroute 45.xx.xx.xx  source  lo0

Type escape sequence to abort.
Tracing the route to 45.xx.xx.xx

 1  116.xx.xx.xx msec  0 msec  0 msec 
 2  

please note : actaul next-hop and the wrong next-hop where the traffic forwarding is connected on same device .

sh cef exact-route 12.xx.xx.xx 45.xx.xx.xx
45.xx.xx.0/24, version 6200272, internal 0x5000001 0x0 (ptr 0x55b207c4) [1], 0x0 (0x0), 0x0 (0x0)
 Updated Jun 28 21:54:59.174
 Prefix Len 24, traffic index 0, precedence n/a, priority 4
 BGP Attribute: id: 0x48d74, Local id: 0x3535, Origin AS: 19xx, Next Hop AS: 19xx 
 
   via Bundle-Ether22
   via 192.xx,xx,xx, 3 dependencies, recursive, bgp-ext [flags 0x6020]
    path-idx 0 NHID 0x0 [0x5a7ab06c 0x0]
    next hop 192.xx.x.xx.x via 192.xx.xx.xx

[Georg Pauwen]

Hello,

weird indeed. Can you post the config of your router, and possibly also the config of the next hop router ?

[muralikrishnan.chelakara]

hello georg,

sorry , i can't give the config it is highly confidential , as you said this is weird issue i ever seen in my profession , the configuration is pretty straight forward , this issue is only for the one specific destination . 

[Georg Pauwen]

Hello,

understood...posting configurations is not always possible. Is it an option to add a static route in order to resolve this:

ip route 45.xx.xx.xx xx.xx.xx.xx

?