11-09-2015 05:30 AM - edited 03-08-2019 02:37 AM
Hi,
Im trying to do PBR to a non-directly connected equipment using recursive command. Would it support it even if my next hop is 4 hops away?
Im trying to push packets to an equipment 4 hops when going to a public IP, problem is im also getting that same route from a directly connected interface.
When i tried to do a trace route, im seeing it going to the next hop equipment and going back in to my core.
Solved! Go to Solution.
11-09-2015 06:16 AM
I am not sure that I have a full understanding of your issue (or of your topology). But my first guess at an explanation of the problem is that PBR controls forwarding only for the device on which it is connected. If you are configuring PBR to a destination 4 hops away you may very well need to configure PBR on those hops.
What it sounds like to me is that PBR on this device is working as you intend and the traffic is forwarded to the first hop on its way to 4 hops away. But on that next device normal routing takes over and sends the traffic to your core. In that case you need PBR on at least these two devices (and likely on the devices one and two hops further along the path).
HTH
Rick
11-09-2015 06:16 AM
I am not sure that I have a full understanding of your issue (or of your topology). But my first guess at an explanation of the problem is that PBR controls forwarding only for the device on which it is connected. If you are configuring PBR to a destination 4 hops away you may very well need to configure PBR on those hops.
What it sounds like to me is that PBR on this device is working as you intend and the traffic is forwarded to the first hop on its way to 4 hops away. But on that next device normal routing takes over and sends the traffic to your core. In that case you need PBR on at least these two devices (and likely on the devices one and two hops further along the path).
HTH
Rick
11-09-2015 06:29 AM
thanks rick, was doing some research on the background as well and i have considered your suggestion but it will be really messy. I dont want to set it up and forget to remove it and cause some issues in the future.
Will need to do more research on how i can control the traffic to go to my desired next hop. VRF and VPN tunnels is out of the considerations since want to keep it simple as possible.
11-09-2015 06:35 AM
I am glad that my explanation correctly identified the issue. I agree that it can get messy if where you want the traffic to go is 4 hops away. Some customers I have worked with have used GRE tunnels to solve requirements like this. To do that you would configure a GRE tunnel between this device and the device 4 hops away and then forward the traffic over the GRE tunnel. I do not know if that would work on your devices.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide