General
When associating a route-map to the ipv6 local policy, the order of operations can cause a CLI error stating the route-map contains unsupported configuration.
If:
local policy assigned before ACL creation before route-map creation -- This is successfully associated and works.
ACL created before route-map created before local policy assigned -- This fails with the error:
%FMANRP_PBR-3-UNSUPPORTED_RMAP: Route-map
Note, any other order of operations other than ACL -> route-map -> local policy works. We've tested through packet capture that the local policy, once associated does have the correct behavior.
Symptom
%FMANRP_PBR-3-UNSUPPORTED_RMAP: Route-map has unsupported options for Policy-Based Routing. It has been removed from the interface, if applied.
Conditions
ACL created before route-map created before local policy assigned -- This fails with the error:
%FMANRP_PBR-3-UNSUPPORTED_RMAP: Route-map has unsupported options for Policy-Based Routing. It has been removed from the interface, if applied.
Workaround
Create the route-map before the ACL is created, or assign the local ipv6 policy before the ACL is created. Any other order of operations will be successful.
Further Problem Description
When associating a route-map to the ipv6 local policy, the order of operations can cause a CLI error stating the route-map contains unsupported configuration.
If:
local policy assigned before ACL creation before route-map creation -- This is successfully associated and works.
ACL created before route-map created before local policy assigned -- This fails with the error:
%FMANRP_PBR-3-UNSUPPORTED_RMAP: Route-map has unsupported options for Policy-Based Routing. It has been removed from the interface, if applied.
Note, any other order of operations other than ACL -> route-map -> local policy works. We've tested through packet capture that the local policy, once associated does have the correct behavior.
