350-401 Question 352
Single answerA network engineer configured a route map named 'TAGGING' to tag specific routes before redistributing them into OSPF. However, some routes are not appearing in the OSPF database as expected. Upon investigation, the route map uses a 'match' statement to filter routes based on an ACL, followed by a 'set' statement to add a tag. What could be the issue with the route map configuration?
- A
The ACL used in the 'match' statement does not match any routes.
- B
The 'set' statement is incorrectly configured to tag routes with an unsupported value.
- C
The route map is missing a 'permit' statement to allow matched routes.
- D
The OSPF process does not support redistribution with tagged routes.
Show answer and explanation
Correct answer: A
Explanation
The issue likely stems from the ACL referenced in the 'match' statement. If the ACL does not match any prefixes, the route map will not process or redistribute those routes. Ensuring the ACL matches the intended routes will resolve the problem and allow proper tagging and redistribution into OSPF.
- A. Correct.
If the ACL used in the 'match' statement does not match any routes, the route map will not process those routes, resulting in the routes being filtered and not redistributed into OSPF.
- B. Incorrect.
The 'set' statement in a route map can typically tag routes with supported values, and an incorrect 'set' statement would not prevent routes from appearing in the OSPF database, although it might result in incorrect tagging.
- C. Incorrect.
Route maps do not require an explicit 'permit' statement unless the default behavior is to deny all. For matched routes, the 'permit' action is implicit unless specified otherwise.
- D. Incorrect.
OSPF supports route redistribution with tagged routes, so this is not a valid reason for the issue.