Device Templates

A Device Template is set of pre-loaded device details such as device type, category, monitoring interval, unique SysObject ID and performance monitors.

What is the purpose of a device template?

Device templates help in automatically classifying the device under a specific device type (device model) and associate the necessary performance monitors during the process of device discovery.
It enables you to effect a configuration once and apply it to several devices at a time whenever there is a change.

OpManager comes with 11000+ device templates which carry the initial configurations to classify the devices into the pre-defined device types, thereby greatly reducing the deployment time. However, you can further define custom templates or modify the existing ones to meet your environmental needs.

Basic configuration

If you are looking just to classify your device based on device type and category upon initial device discovery,

Go to Settings -> Configuration -> Device Templates.
Click on the Add Template option.
Enter the mandatory fields - Device template name, vendor, category, availability monitoring interval and device image.
Define a unique device identifier (SysObject ID) received from vendor or by querying the device itself.
Click on Save.

Once the discovery is initiated, OpManager automatically classifies the discovered devices based on the matching device type, and starts monitoring the devices for its availability or uptime and generates device Up/Down alarms.

Advanced configuration

If you wish to perform in-depth monitoring of the devices in your network, along with the above mentioned mandatory parameters specify the performance monitors and thresholds (for performance monitoring alerts) based on your requirement. You can also add multiple device identifiers or edit the existing device identifiers to provide SysOID criteria for more specific classification of devices.

The changes will be automatically reflected for devices that match the specified SysOID on further discovery or upon rediscovery. The changes can also be manually associated once the template is saved.

Properties required to create a new device template

Device Template Name: The device model name. This will be determined as the device model in the inventory list.
Vendor Name: The vendor name of device. You can either select from the existing list of vendors or add a new vendor.
Category: The category your device belongs in (server, desktop, WLC, storage devices, etc). This helps OpManager categorize similar device types together and organize better. You can either select from the existing list of categories or add a new one. Learn more about device categories.
Monitoring Interval: The interval at which OpManger contacts the device for availability monitoring. You can also edit the monitoring interval of devices in bulk or category wise from the Quick Configuration Wizard under Settings. Learn more.

Note: During device discovery, the interval configured for the respective category under Quick Configuration Wizard > Monitoring Intervals) will be assigned to the device.

Device Image: A image or icon that represents a particular device type. You can either select from the available set of icons or create a customized image.
Device Identifier: Device identifier is a vendor's authoritative identification (sysOID) value to determine the device model. You can either manually add the sysOID or let OpManager fetch the value by querying the sysObjectID (.1.3.6.1.2.1.1.2) from RFC1213 MIB if the device is available in OpManager. If you are yet to add the device, you can query through the MIB Browser to identify the sysObjectID. How to query sysOID using MIB browser?
Note: Please note that every sysID should be unique and should not be repeated for multiple device categories or types. You will not be able to create two device templates with the same sysOID value. However, to differentiate similar devices with different templates, multiple sysOID criteria can be included while specifying the device identifier. For example, if a Linux Redhat and Linux Ubuntu device types hold the same SysOids, it can be classified using different sysOid criteria. Learn more.
Associated Monitors: A set of monitors that are automatically associated with the devices during discovery. You can either
- Associate existing vendor based and performance monitors.
- Create a new custom SNMP or WMI monitor. Learn more.
Edit Thresholds: Helps you edit the thresholds values of the associated monitors. Select the monitor and edit thresholds to receive alerts and notifications accordingly.
Associating templates: Once monitors are assigned and thresholds are set, you can further customize how it should reflect. The 'Associate' option lets you apply the changes to monitors added in the future. The 'Associate and Overwrite' option lets you overwrite the changes to all the existing monitors.

What does the Sync Device Template option do?

Note:

Device templates are automatically associated to devices upon discovery. However, it can also be carried out manually post discovery if valid credentials are associated. Click here
Device templates can also be imported from ManageEngine Support and Community Forums or from a different instance of OpManager. Click here to learn how.
During discovery, if none of the device template match with the discovered device, OpManager creates a custom template by matching sysOID with the vendor template. This will only help in the availability monitoring of the device. No default monitors or device category will be associated and performance monitoring will not be initiated, unless done manually.

Frequently asked questions:

Are you looking for availability monitoring in OpManager? Click here to know more.

Was this content helpful?