Excellent video. Clear, concise and informative whilst not having too much content to actually communicate the concepts. Also like how the topology is kept on screen simultaneously with the CLI
This video is well made and explained the concept very clearly in a simple way. Thanks for sharing this with us! BTW, I have subscribed to your channel as well!
I believe there was a caveat with PBR in that it only affects transit when applied to the interface, and not if you were to ping from the router itself, iirc? I forget the details of it, or the command to make it affect the router itself, though. Cool feature still!
@blendonator Yes, PBR only takes effect on the ingress* direction of the Interface that it's applied on. In other words, "transit traffic" like you said. In order to apply PBR on packets originating from the Router itself, you would need to enter the "ip local policy (Route-Map Name)" Global Config command. This will apply the route-map to the Router's control plane. So, functions like pings originating from the Router will take the actions specified in the route-map.
Very clear and straight to the point. I plan on taking my CCNP soon and will like to have a complete course from you. Some concepts such as MPLS, VPN, GRE, Qos, VXLan are quite difficult for me. I like how you simplified this topic. Do you have a full ccnp course I can buy?
If the next hop is unreachable (e.g. the Gig 0/2 interface on R1 connected to ISP-B goes down), the router will ignore the route map and bypass the PBR configuration, routing the traffic according to the IP routing table. In the case of this example, the traffic would again go over the ISP-A router. It's also worth mentioning that there are ways to track this next-hop connectivity, such as IP SLA object tracking, or the optional "verify-availability" parameter during PBR configuration.
@@CharlesJudd Thanks, I thought that because it does not conform to normal routing it will be treated like other "weird" packets (e.g. fragmented IP, or tunnels)
Excellent video. Clear, concise and informative whilst not having too much content to actually communicate the concepts. Also like how the topology is kept on screen simultaneously with the CLI
Charles, you have a knack at making complex technology very simple and easy to understand.
thank you. simple and clearly
wow u r great , you make it very simple , it was my fisrt time to understand it se easily , thanks
You make this seem so simple. I like how you break it down into steps: match, set and apply and where PBR is applied in packet forwarding.
Excellent topic, definitely need to understand Policy Based Routing... Thank you, Charles!
This video is well made and explained the concept very clearly in a simple way. Thanks for sharing this with us! BTW, I have subscribed to your channel as well!
Excellent, nicely explained and demoed , thanks for posting
Excellent. Keep it up..😍😍
Thanks for sharing!
I believe there was a caveat with PBR in that it only affects transit when applied to the interface, and not if you were to ping from the router itself, iirc? I forget the details of it, or the command to make it affect the router itself, though. Cool feature still!
@blendonator Yes, PBR only takes effect on the ingress* direction of the Interface that it's applied on. In other words, "transit traffic" like you said. In order to apply PBR on packets originating from the Router itself, you would need to enter the "ip local policy (Route-Map Name)" Global Config command. This will apply the route-map to the Router's control plane. So, functions like pings originating from the Router will take the actions specified in the route-map.
Excellent
Very clear and straight to the point. I plan on taking my CCNP soon and will like to have a complete course from you. Some concepts such as MPLS, VPN, GRE, Qos, VXLan are quite difficult for me. I like how you simplified this topic. Do you have a full ccnp course I can buy?
Magic👍
you look exhausted. Keep going
What will happen if the link to ISPB goes down ( line protocol)?
If the next hop is unreachable (e.g. the Gig 0/2 interface on R1 connected to ISP-B goes down), the router will ignore the route map and bypass the PBR configuration, routing the traffic according to the IP routing table. In the case of this example, the traffic would again go over the ISP-A router. It's also worth mentioning that there are ways to track this next-hop connectivity, such as IP SLA object tracking, or the optional "verify-availability" parameter during PBR configuration.
@@CharlesJudd thanks for clarification...
Is CEF still used when forwarding packets by PBR instead of normal RIB?
Yes, if CEF and PBR are enabled on the router, CEF-switched PBR is used by default.
@@CharlesJudd Thanks, I thought that because it does not conform to normal routing it will be treated like other "weird" packets (e.g. fragmented IP, or tunnels)
Userfulllllll