Role of the model device in a template

The model device is a device configured to serve as the baseline for a template and provides the configuration context for the template, but its role differs slightly depending on how the template is created.

When creating a new template

The model device serves as a baseline configuration and capability reference.

It provides:

• A starting point for settings based on a real device

• The set of available features and configuration options for that device type

• Alignment with a specific firmware version and supported parameters

In this case, you are primarily building the configuration using the model device as your foundation.

When copying a template

The model device serves as a validation and adjustment context for the copied configuration.

It provides:

• A way to ensure compatibility between the copied template and the selected device type/firmware

• Visibility into supported settings and features for refinement

• A framework to update or modify settings, especially when changing firmware versions

In this case, the configuration comes from the existing template, and the model device helps you verify and adapt that configuration.

Summary

• New template: model device = baseline and starting point

• Copied template: model device = validation and refinement context

In both cases, the model device defines the valid configuration space, but the source of the configuration differs.