What is User Defined SNMP Polling?

Introduction

User permissions

Licensing

No system downtime

Raising events

Introduction:

User Defined SNMP Polling allows you to define rules on how to poll new MIB variables from an SNMP device. Entuity manages an extensive set of devices, and discovers and polls a comprehensive set of attributes. However, there may be occasions when you want to customize device management, e.g. to:

• provide self-service device support.
  • e.g. if Entuity is managing a device that has an unusual data model, and so is not collecting particular fan, power supply, memory or processor attributes, then you can augment the system collectors with your own user defined collectors.
• add user defined attributes.
  • e.g. you can define new attributes and their collectors, and associate them with existing system objects or custom objects. For example, if you want to collect additional information on all your switch devices, you can select the SwitchDevice object and create user defined attributes and collectors.
• use predefined empty objects, against which you can define attributes and collectors.
  • Entuity provides 20 user defined object types (UDComponentN) that are part of the Entuity data model, but are unsued. Because an object type is the sum of its attributes, you can configure Entuity to manage totally components of a managed object.

User permissions:

Adding new user defined attributes and user defined collectors can be achieved in the UI. These can be made by administrators and users with the "User Defined Polling" administrator tool permission.

Licensing:

• Entuity v19.0 and Entuity v20.0: Each component created by a user defined SNMP poller consumes one Associated Items license credit.
• Entuity v21.0 upwards: Each component created by a user defined SNMP poller consumes one Objects license credit.

No system downtime:

Unlike the procedure for adding new polling definitions using new configuration files, the User Defined Polling allows new attributes and collectors to be added and used without system downtime. All changes are made in the UI and take effect as soon as they are defined.

Raising events:

You can set up events against user defined attributes:

• status events - these are events raised when the attribute value returns the set status.
• threshold events - these are events raised when the polled attibute value is within the set ranges.

Status and threshold events have associated status and threshold incidents.