SevOne logo
You must be logged into the NMS to search.

Table of Contents (Start)

Device Types

The Device Types page enables you to use discovery to classify and organize devices. Starter set device types use topology metadata driven rules to automatically add devices that topology sources discover to applicable device types. Device types enable you to associate a collection of SNMP object types to multiple devices. Each device can belong to multiple device types. Device types enable you to organize devices for SNMP polling purposes which expedites policy definition and enables you to run manufacturer independent reports for similar but not identical objects. You can associate an icon to each device type for topology reports. Device types appear in all Device Group lists and provide an additional method to secure, sort, and filter devices. For details, please refer to section Device Group in SevOne NMS User Guide.

To access the Device Types page from the navigation bar, click the Administration menu, select Monitoring Configuration, and then select Device Types.

images/download/attachments/33041383/devicetypes-version-1-modificationdate-1490733480922-api-v2.png

Device Type Hierarchy

The device type hierarchy appears on the left. First level device types display in alphabetical order under the parent All Device Types.

  1. Select the device type under which to add a new device type.

  2. Click Add Device Types to display a pop-up.

    1. In the Device Type Name field, enter the device type name.

    2. Click Save on the pop-up.

  3. images/download/attachments/163972880/metadata-version-1-modificationdate-1693242964553-api-v2.png - Click to edit the values for the metadata attributes you want to associate with the device types. See the Manage Metadata Values section below.

  4. images/download/attachments/163972880/editnew-version-1-modificationdate-1693242964507-api-v2.png - Click to edit a device type name.

  5. Drag and drop device types to different places in the custom device type hierarchy.

  6. images/download/attachments/163972880/deletenew-version-1-modificationdate-1693242964267-api-v2.png - Click to delete the device group. When you delete a device group that has associated policies, a message appears to inform you that associated policies will be deleted.

    1. On the message, click View Policies to display the Policy Association pop-up that lists the policies associated to the device group.

    2. Click Done to move the policies.

  7. Click images/download/attachments/163972880/editnew-version-1-modificationdate-1693242964507-api-v2.png above the right side of the page to display the Upload Device Type Icon pop-up that enables you to associate an icon to the device type for display in Topology reports - please see section Report Interactions in SevOne NMS User Guide. Please refer to section Device Type Icons below for the list of starter set icons.

    1. Click the Select File images/download/attachments/163972880/folder-version-1-modificationdate-1693242964511-api-v2.png to display the File Upload pop-up.

    2. Navigate your file hierarchy and select the image file to upload.

    3. Click Open to return to the Upload Device Type Icon pop-up.

    4. Click Save to associate the image with the device type or click Remove Icon to remove the icon associated with the device type.

Manage Metadata Values

The images/download/attachments/163972880/metadata-version-1-modificationdate-1693242964553-api-v2.png in the device type hierarchy Actions column provides access to the Edit Metadata pop-up that enables you to manage the values for the metadata attributes you want to associate with the device type. The Metadata Schema page enables you to manage metadata attributes.

  1. Click images/download/attachments/163972880/icon_editMetadata-version-1-modificationdate-1693242964543-api-v2.png in the Actions column to display the Edit Metadata pop-up.

  2. Click images/download/attachments/163972880/icon_greyWrench-version-1-modificationdate-1693242964548-api-v2.png to make the Values field editable.

  3. In the Values field, enter the value for the attribute with the applicable attribute type specific format.

    • Date/Time: Must have a valid date and time format and can use natural language processing such as; 3 Thursdays ago at 5pm.

    • Integer: Type: Value must be numeric.

    • IP Address: Must use one of the following formats:

      • IPv4: for example, 10.1.1.100 or 172.16.254.1

      • IPv6: supports Zero Suppression format. For example, 2001:db8::1234::567:8:1 or 2601::0800:200c:417a

    • Latitude and Longitude: Must have valid coordinates that are decimal values: -90.00 to 90.00 values for Latitude and -180.00 to 180.00 for Longitude

    • MAC Address: Must use the following format: 0A:00:27:00:00:00

    • Text (Validated): Supports up to 1024 UTF-16 characters including PCRE regex that uses preg-match (perform a regular expression match) to validate the regular expression you enter against the attribute definition from the Metadata Schema page.

    • Text: Supports up to 65K UTF-16 varchar characters.

    • URL: Complete the following fields:

      • Link Display Text: Enter the text to display in reports as the link caption.

      • URL: Enter the URL. Must have FQDN validation, supports username prefix, ports, protocol AND ?/& for HTTP GET variables, and optional additional PCRE regex for validation, and must be fewer than 255 characters.

  4. Click Update to save the value.

Device Type Membership Rules

The Device Type Membership Rules section enables you to define rules to automatically add devices to a device type from across multiple manufacturers/products that implement the same MIBs. Starter set rules automatically add devices to applicable device types for Topology reports - for details, please see section Report Interactions in SevOne NMS User Guide. Device type rules run during discovery to add the devices from which the SNMP plugin can poll the metrics you specify to the device types you create. You can manually pin devices to device types and the Device Manager also enables you to pin devices to device types. Rules are case sensitive and you can use Perl regular expressions to create rules.

  1. Click on a device type in the hierarchy to display the device type membership rules in the upper section on the right.

  2. Click Add Rule or click images/download/attachments/163972880/editnew-version-1-modificationdate-1693242964507-api-v2.png to display the Add/Edit Device Type Membership Rule pop-up. Each rule requires only one field. If you populate several fields per rule, the criteria you enter in that rule are cumulative.

    Example: Enter Remote in the Name field and enter ^192\.168 in the Management IP Address field in the same rule criteria row. The device must have both Remote in the name AND an IP address that starts with 192.168 to be added to the device type.

    • Device Name - The device name (wildcards are implied).

    • Device Description - The device description.

    • Management IP Address - The IP address of the device (^192\.168 adds all devices whose IP address starts with 192.168).

    • sysDescr - The text you get when you SNMP walk the sysDescr OID.

    • sysContact - The text you get when you SNMP walk the sysContact OID.

    • sysLocation - The text you get when you SNMP walk the sysLocation OID.

    • sysName - The text you get when you walk the sysName OID.

    • sysObjectID - The text you get when you SNMP walk the sysObjectID OID.

    • Walkable OID - Enter the number of the OID to walk. Make sure that the OID can actually be walked. You may be able to get an OID and get a response. However, if you walk an OID and the result from the snmpgetnext falls outside of the OID tree, discovery won't add the device to the device type.

      Example

      getnext .1.3.6.1.2.1.1.1.0 – get .1.3.6.1.2.1.1.2.0 - does not match the pattern .1.3.6.1.2.1.1.1.0.X

      getnext .1.3.6.1.2.1.1.1 – get .1.3.6.1.2.1.1.1.1 - matches the pattern .1.3.6.1.2.1.1.1.X

  3. Click Save to save the rule criteria.

  4. Repeat these steps to add additional rules to use the OR Boolean.

Example: Enter Remote in the Name field in the first row in the rule table then click Create Rule. Enter ^192\.168 in the second row in the rule table. The device can have either Remote in the name OR an IP address that starts with 192.168 to be added to the device type.

Object Types

The Object Types tab in the lower right section contains two groups of object types Inherited and Local. The Object Types tab displays the following information.

  • Object Types - Displays the list of object types that are associated to the device type.

  • Parent Path - Displays where the object type resides within the object type hierarchy.

  • Plugin - Displays the name of the plugin that polls the object type.

  • Defined In - Displays Local for object types that are defined at this level in the Device Type hierarchy or displays a link that navigates you to the level in the Device Types hierarchy from where the object type inherits its definition.

The Object Types tab enables you to associate the SNMP object types you want the SNMP plugin to attempt to poll on the devices that are members of the device type.

  1. On the Object Types tab, click Associate to display the Associate pop-up.

  2. Select the check box for each object type to poll on the devices that are members of the device type.

  3. Click Associate on the pop-up to associate the object types to the device type.

Manage SNMP Object Types

The Object Types tab duplicates the functionality of Object Types page to enable you to add and edit SNMP object types. For additional details see the SNMP topic. For interfaces and most SNMP objects, there is an OID that is dedicated to provide the index number.

Example: Walk ifIndex to yield the following

RFC1213-MIB::ifIndex.1 = INTEGER: 1
RFC1213-MIB::ifIndex.2 = INTEGER: 2
RFC1213-MIB::ifIndex.8 = INTEGER: 8

Each field on the Add/Edit SNMP Object Type pop-up has a corresponding check box on the right side to enable you to make changes at this level of the hierarchy and below. The changes you make when you select the right-hand check box override and do not affect the parent object type definition.

  1. Click Add then SNMP or click images/download/attachments/163972880/editnew-version-1-modificationdate-1693242964507-api-v2.png to display the Add/Edit SNMP Object Type pop-up.

  2. In the Name field, enter the object type name.

  3. Click the Indexed By images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the index OID.

  4. Select the Reverse Engineer check box to have instances of this object type be uniquely identified by evaluating the OID of the SNMP object specified in the Indexed By field, as opposed to its value. How the values encoded within the OID are evaluated is based on the configuration of the Index Keys field. You should leave this check box selected for the vast majority of object types.

  5. The Index Keys fields enable you to select the index keys to use to determine how to treat the remaining octets after the index. In the Possible Values field, select index keys to assign to the object type (use Ctrl or Shift keys to multi-select) then move the index keys to the Index Keys field. Index keys in the Index Keys field are assigned to the object type and they display in the sequence in which they appear listed. Possible values include the following:

    • Integer - A single number that indicates there is a constant amount of numbers following each OID.

    • String - A string prefixed with the string length. This typically appears with double quotes.

    • String (Implied) - A string with no length information. This must only occur as the last index value.

    • Variable - A variable amount of numbers prefixed with the amount of items. This is typically used for IPv4 versus IPv6 indexes.

    • Variable (Implied) - A Variable amount of numbers, but with no length information. This must occur as the last index value. This can be used to eat up the remainder of the index.

  6. Click the Name Expression images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID that results in a unique name for all object types on a device.

  7. Click the Description Expression images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID to add additional information about the object type.

  8. Click the Subtype images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID to define a subtype for the object type (used for thresholds and reports). This can generate the following variables:

    • - [TYPE]: The numerical value of the subtype.

    • - [TYPE]: The name of the subtype.

    • - [TYPE]: The description of the subtype.

  9. Click the Assert images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID to use in the assert expression that generates a list of individual object indexes. This is skipped if the object does not pass the assert expression. No variables are generated.

  10. Click the Last-change OID images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID to use to determine if a change was made to the object type since it was last polled. If the object type changed, the SNMP plugin invalidates the current data.

  11. Click the Admin-status images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID to use to determine the administrative status of the object.

  12. Click the Oper-status images/download/attachments/163972880/browse2-version-1-modificationdate-1693242964263-api-v2.png to display the SNMP OID Browser where you select the OID to use to determine the operational status of the object.

  13. In the Variable field, enter the variables, expressions, and operators you want to use to evaluate first for use with the other fields.

  14. Click Edit Subtypes to display the Object Subtype Manager where you manage the object subtypes.

  15. Click Save.

Device Type Membership

The Device Type Membership tab displays the devices that are members of the device type. When you pin a device to a device type, rules do not affect the device's membership and you must manually unpin the device to remove its membership. When a rule adds a device to a device type, if you change the rule, the devices that were added by the rule can automatically be removed from the device type.

  • images/download/attachments/163972880/pin-version-1-modificationdate-1693242964557-api-v2.png - Indicates the device is a member that was pinned to the device type at this level.

  • images/download/attachments/163972880/grouprule-version-1-modificationdate-1693242964529-api-v2.png - Indicates the device is a member that was added by a device type membership rule at this level.

Membership Management

The following tools enable you to manage the devices that are members of the device type you select in the hierarchy.

  • Click Pin Devices to display a pop-up that displays all devices in SevOne NMS.

    1. Select the check box for each device to pin to the device type.

    2. Click Pin to Type on the pop-up to pin the devices you select to the device type.

  • Select the check box for each device to unpin from the device type and click Unpin Devices. If you pin a device that was added by a rule, when you unpin the device it is removed from the membership list. If you do not change the rule, the device appears in the list again upon the next discovery.

  • Click images/download/attachments/163972880/metadata-version-1-modificationdate-1693242964553-api-v2.png in the Actions column to display the Edit Metadata pop-up. See the Manage Metadata Values section above.

Device Type Icons

Topology related device types use the following icons by default. You can change the icon from the images/download/attachments/163972880/editnew-version-1-modificationdate-1693242964507-api-v2.png as described above.

images/download/attachments/163972880/dt-bridge-version-1-modificationdate-1693242964297-api-v2.png - Bridge

images/download/attachments/163972880/dt-cloud-version-1-modificationdate-1693242964302-api-v2.png - Cloud

images/download/attachments/163972880/dt-nocloudaccess-version-1-modificationdate-1693242964447-api-v2.png - Cloud No Access

images/download/attachments/163972880/dt-computer-version-1-modificationdate-1693242964305-api-v2.png - Computer

images/download/attachments/163972880/dt-computers-version-1-modificationdate-1693242964308-api-v2.png - Computers

images/download/attachments/163972880/dt-controller-version-1-modificationdate-1693242964432-api-v2.png - Controller

images/download/attachments/163972880/dt-device-version-1-modificationdate-1693242964436-api-v2.png - Device

images/download/attachments/163972880/dt-firewall-version-1-modificationdate-1693242964440-api-v2.png - Firewall

images/download/attachments/163972880/dt-host-version-1-modificationdate-1693242964443-api-v2.png - Host

images/download/attachments/163972880/dt-pbx-version-1-modificationdate-1693242964450-api-v2.png - PBX

images/download/attachments/163972880/dt-printer-version-1-modificationdate-1693242964453-api-v2.png - Printer

images/download/attachments/163972880/dt-rack-version-1-modificationdate-1693242964456-api-v2.png - Rack

images/download/attachments/163972880/dt-switch-version-1-modificationdate-1693242964459-api-v2.png - Switch

images/download/attachments/163972880/dt-ups-version-1-modificationdate-1693242964489-api-v2.png - UPS

images/download/attachments/163972880/dt-user-version-1-modificationdate-1693242964492-api-v2.png - User

images/download/attachments/163972880/dt-users-version-1-modificationdate-1693242964496-api-v2.png - Users

images/download/attachments/163972880/dt-vm-version-1-modificationdate-1693242964499-api-v2.png - VM

images/download/attachments/163972880/dt-wireless-version-1-modificationdate-1693242964504-api-v2.png - Wireless