A is correct.
For a static route to be redistributed into BGP, it must be considered valid by the routing process. One common issue is that if the static route does not have a valid next hop (i.e., the next hop is not reachable or not properly resolved in the routing table), it will not be redistributed into BGP.
D is correct. Because there is the next-hop seen in static route(1st one is Fully Qualified Static Router and other is Static Router to an interface). Both NEXT are valid because they are not in hidden table in inet.0 Routing table.
So, when we configure "no-re advertise" knob in static route, the policy used in BGP for redistribution does not match able to match it and there will no redistribution happens further.
A is correct.
For successful redistribution of static routes into BGP, the static routes must have a valid next hop. The next hop is crucial because it determines where the traffic should be forwarded. If the next hop is invalid or unreachable, the static routes will not be redistributed into BGP.
The other options provided are incorrect:
B. The as-path parameter is not a requirement for redistributing static routes into BGP.
C. A community string is not necessary for redistributing static routes into BGP.
D. The no-readvertise feature prevents routes from being advertised to other BGP peers, but it does not affect the redistribution of static routes into BGP.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Rajmund
2 weeks agobymboolu
2 months, 1 week agoDIbyam
3 months, 3 weeks agojharosev2
4 months, 1 week agoavneesh_14
6 months agoavneesh_14
6 months, 1 week ago