The LFA SPF policy feature generalizes the use of admin-group and SRLG to other types of interfaces. To that end, it is important that the new IP admin groups and SRLGs be compatible with the ones already supported in MPLS. The following rules are implemented:
The definition of admin groups and SRLGs are moved under the new config>router>if-attribute context. When upgrading customers to the release which supports the feature, all user configured admin groups and SRLGs under config>router>mpls context is automatically be moved into the new context. The configuration of admin groups and SRLGs under the config>router>mpls context in CLI is deprecated.
The binding of an MPLS interface to a group, that is, configuring membership of an MPLS interface in a group, continues to be performed under the config>router>mpls>interface context.
The binding of a local or remote MPLS interface to an SRLG in the SRLG database continues to be performed under the config>router>mpls>srlg-database context.
The binding of an IS-IS or OSPF interface to a group is performed in the config>router>interface>if-attribute context. This is used by IS-IS or OSPF in route next-hop policies.
Only the admin groups and SRLGs bound to an MPLS interface context or the SRLG database context are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.