When Allow all (0.0.0.0/0 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 0.0.0.0/0 as Aggregate, Set Metric to 50
This RouteMap is applied as Export Policy on L3outB's external network.
L3outB-ExtNet: Subnet 0.0.0.0/0 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 0.0.0.0/0 Aggregate in the RouteMaps does match all routes subnet to export on the L3out.
Original Blog published @ https://blogs.cisco.com/datacenter/spinning-up-an-nvme-over-fibre-channel-strategy
Every so often there comes a time when we witness a major shift in the networking industry that fundamentally changes the landscap...
Let me start by telling you that there is already a very nice document in the Cisco Community Forums which describes the procedure to upgrade the APIC CIMC. In case you came across this document before looking into the mentioned one, here is...