Symptom
After creating a static L3Out in the same VRF instance as an OSPF L3Out, fault F0467 appears for the OSPF L3Out:
# fault.Delegate
affected : resPolCont/rtdOutCont/rtdOutDef-[uni/tn-XXX/out-YYYYYYY]/nwissues
code : F0467
ack : no
cause : configuration-failed
changeSet : configQual:rtctrl-enforce-policy-conflict, configSt:failed-to-apply, temporaryError:no
childAction : deleteNonPresent
created : 2018-09-03T12:02:14.147+01:00
descr : Fault delegate: Configuration failed for uni/tn-XXX/out-YYYYYYY due to Different Route Control Enforcement Policies are Defined for Context(VRF) Deployed on the Node from Different L3 Outsides., debug message:
dn : uni/tn-XXX/out-YYYYYYY/fd-[resPolCont/rtdOutCont/rtdOutDef-[uni/tn-voice/out-YYYYYYY]/nwissues]-fault-F0467
domain : tenant
highestSeverity : minor
lastTransition : 2018-09-03T12:04:20.089+01:00
lc : raised
modTs : never
occur : 1
origSeverity : minor
prevSeverity : minor
rn : fd-[resPolCont/rtdOutCont/rtdOutDef-[uni/tn-XXX/out-YYYYYYY]/nwissues]-fault-F0467
rule : fv-nw-issues-config-failed
severity : minor
status :
subject : management
type : config
Conditions
This issue occurs when there are OSPF L3Outs with import/export route control and you create a static L3Out.
Workaround
Enable OSPF for all static L3Outs in the VRF instance of the OSPF L3Outs, then disable OSPF.
