Invalid Model Mappings

Some configurations in the template may not be supported on all device models. Unsupported configurations, if any, are not applied to the device. Valid model mappings can also become invalid when you modify template configurations. For example, when you add a new interface on the template and assign a name to it, the new interface must be mapped to the appropriate interface on the device model.

Model mapping can also be invalidated due to any of the following reasons:

• Number of configured VRF instances exceeds the limit for a specific model.

• Interfaces mapped to incompatible models, versions, or interfaces. See Requirements and Prerequisites for more information.

• Number of interfaces exceeds the model limit.

• Deleted an interface that was mapped.

• Newly added physical interfaces are not mapped to a compatible model interface.

• Model mapping is not done for a named interface.

• Model mapping is not done for an interface related to other logical interfaces, such as sub-interfaces, PC interfaces, and so on.

• Making policy or configuration changes that are unsupported on some device models. For example, enabling switch port configuration on interfaces.

You can also save a template with invalid model mappings. However, you must review and fix the model mapping before initiating application of the template on the device.

You can hover over Invalid under Mapping Status to view the errors that caused the invalid mapping status. Fix the errors before initiating application of the template on the device.