Strict routing policy validation is used for model-driven interfaces. The routing policy must exist for the management interface configuration mode to be changed. Remove references to non-existent routing policies before attempting to switch modes. Strict policy validation is applied to the following routing policy references:
ARP and ND in the Base router and VPRN instances
BGP in the Base router and VPRN instances
global and local variables in main policies and sub-policies
IGMP, MLD, and PIM in the Base router and VPRN instances
IS-IS in the Base router and VPRN instances
LDP
OSPF and OSPFv3 in the Base router and VPRN instances
policy-option in from, to, action, and default-action statements
policy-option in sub-policies, prefix-list, as-path, as-path-group, damping, and community policies
RIP and RIPng in the Base router and VPRN instances
RSVP
single policy-statement or logical policy expressions
static routes in the Base router and VPRN instances
subscriber management, except for in mld-policy configuration for a local user database (LUDB) host
VPLS for BGP VSI
VPRN for GRT, MVPN, and VRF