Showing results for 
Search instead for 
Did you mean: 


ACI explicit prefix-list for Route Control export seem to affect all routes

Hi there,


I would need your experience to determine if some behavior documented in the ACI L3 Config Guide is true or if I am reading it wrong. The document is here and the statement is:




When Allow all ( with aggregate flag) is used in explicit prefix-list for export route-control, only the routes learned from a routing protocol (such as BGP, OSPF, or EIGRP) will be advertised. The 0/0 aggregate flag will not advertise prefixes corresponding to the following:

  • Bridge domain (BD) subnets

  • Directly Connected Interfaces on the border leaf switch

  • Static routes defined on the L3Out

So, I have 2 L3outs on a VRF, each L3out talks OSPF with an external router each. Simple transit routing. Some OSPF routes are learned from L3outA and I need them redistributed on L3outB with some higher OSPF metric.


So, L3outA by default learns properly the OSPF Routes and I can see them on all leafs of the Fabric. In order to export them on L3outB, my configuration is:


L3outB has the following RouteMap object:


RouteMap: Fabric.To.OSPF, using 'Match Routing Policy Only' to have the Match statement as source of truth

Order 1: Permit, Match Subnet as Aggregate, Set Metric to 50


This RouteMap is applied as Export Policy on L3outB's external network.

  • L3outB-ExtNet: Subnet used only as External Subnet, not Export Control nor Aggregate.
  • Route Control Profile: RouteMap Fabric.To.OSPF as Export


With this configuration, and considering the Note above in the Config Guide, I would expect the exported routes to have a metric of 50 only for the routes learned from L3outA. However, all routes out of L3outB have set a metric of 50, all are affected by the RouteMap. This will indicate that the statement is false and should be corrected, and in the configuration I need to specify on the RouteMap only the L3outA's routes so that only those are affected.


To complete, some BD subnets are associated with L3outB to be advertised over the L3out (in theory, not affected by the route-map) and 2 static routes on L3outB's Node (which should not be affected either). APIC is version 3.1(2o)


If this interests anyone, I could provide some diagrams, exported XML config and show commands.


My guess is that the statement is not accurate, a subnet Aggregate in the RouteMaps does match all routes subnet to export on the L3out.


All the best,


Content for Community-Ad
This widget could not be displayed.