Symptom
When creating more than 128 L3Out (across VRF/Tenant) each with OSPF enabled. There may be failures in policy-map (route-map) creation inside OSPF.
This error will be seen in OSPF event history.
scale4-leaf-bl-204# show ip ospf internal event-history event | grep "policy index"
2020-08-13T17:52:28.494158000-07:00 ospf default [24011]: TID 25036:ospf_policy_attach:164:(Tenant99:VRF-149-(NULL)) Could not allocate policy index
2020-08-13T17:52:28.494121000-07:00 ospf default [24011]: TID 25036:ospf_policy_attach:164:(Tenant99:VRF-149-(NULL)) Could not allocate policy index
There is no fault generated for this condition.
Conditions
When creating more than 128 L3Out (across VRF/Tenant) each with OSPF enabled. This will cause failure in policy-map (route-map) creation inside OSPF.
This may lead to incorrect OSPF behavior in new L3Outs. Following can get impacted:
1. redistribution from other protocols
2. area-filter
3. default route LSA generation
Workaround
Create upto 128 L3Out with OSPF enabled. This limit is per OSPF process.
More number of OSPF instances can be created to get higher limit.
Further Problem Description
This is day-1 behavior which is being enhanced now.
This is applicable to almost all the older releases.
