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.
If you are looking just to classify your device based on device type and category upon initial device discovery,
You can add multiple device identifiers, either SNMP-based (using SysOID) or CLI-based (using a CLI command), you can also modify existing ones to allow for more precise device classification.
These changes will be automatically applied to devices that match the specified identifiers during subsequent discoveries or rediscoveries. Additionally, the changes can be manually associated with devices after the template is saved.
- 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: A Device Identifier in OpManager is used to accurately determine the model or type of a device enabling effective monitoring. The SNMP Device Identifier uses the device's system Object Identifier (sysOID), a unique value retrieved via the SNMP protocol. OpManager obtains this value by querying the sysObjectID OID .1.3.6.1.2.1.1.2, as defined in the RFC1213 MIB. Users may either manually input the sysOID or allow OpManager to automatically retrieve it, provided the device is already added and reachable. If the device has not yet been added, the sysOID can be identified using the MIB Browser by querying the device directly.How to query sysOID using MIB browser?
In addition to SNMP-based identifiers, OpManager supports CLI-based Device Identifiers, offering an alternative method for identifying devices. It is particularly useful in environments where CLI offers more precise or device-specific identification. A CLI device identifier consists of a CLI command and a matching condition that compares the provided value with the command output to identify the device uniquely.
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.
Likewise, it is recommended to add
unique criteria when defining CLI identifiers to ensure accurate device classification. To differentiate similar devices with different templates, you can specify multiple criteria in the CLI identifier. For example, if the same matching criteria are met by two different device templates, you can still classify them separately by adding additional criteria through other CLI commands or by applying different matching conditions.
Learn more about CLI identifiers.
- Associated Monitors: A set of monitors that are automatically associated with the devices during discovery. You can either
- 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.
