• Alarms
  Alarm objects monitor objects in specified Sets for certain conditions. Alarms track these conditions and can fire actions (send an e-mail, launch an application, etc.) for these situations. See section 3.7 - Alarms for more information on creating alarms.
• Device
  Device objects represent specific physical devices within AutoNOC. The children of device objects include categories, components, and then specific logs and probes. For complete information on device objects see 3.2 - Devices.
• Networks
  Network objects are used for targeted discovery of certain parts of the network.
• Folders
  Every root tree in AutoNOC can have nested folders for the objects below the parent.
• Reports
  Reports in AutoNOC perform complex analytical work that is often computationally intensive. There are a variety of different report objects available and for a complete reference on them see 3.9 - Reports.
• Sets
  Set objects are one of the most powerful and useful objects in AutoNOC. They define dynamic queries on the objects in the operations model and can even look at the actual properties of objects and return only certain records from inside objects. For complete information on creating and using sets, see 3.3 - Sets.
• Templates
  Many objects in AutoNOC make use of templates to define shared behavior. For example, it is possible to have multiple instances of a traffic probe all making use of the same service level and data acquisition expression. Templates are a good way to reduce the amount of work required in the management model.
• Users
  Users in AutoNOC are objects that represent accounts for individual users to log in to the operations model. Complete information about users is available in 3.10 - Users.

A complete list of all objects and properties is available in the topic A.3 - Object Reference.

3.1.1 Object Flags
Every major object in AutoNOC has associated flags that describe general designations for the object. The following is a list of the flags and their functionality.

• Use Parent Flags
  AutoNOC will use the flag settings from the parent of this object. This is useful in the case where, for instance, an interface is hidden and disabled, and all child probes should be as well.
• Disable
  Disabled objects are not polled, are not analyzed by alarms, and are skipped however they might be used. They are effectively skipped whenever AutoNOC is performing calculations of some kind.
• Hide
  Hidden objects are not shown in any of the displays, reports, etc. If they are not disabled, they will however, still be operated on. For instance, a hidden alarm will not be visible anywhere but can still fire alerts.
• Ignore State
  State ignored objects are skipped when evaluating service levels. For instance, a state ignored ping probe that is down will not be factored against other objects and it's state will be skipped and ignored in any displays or in any service level computations.

3.1.2 Internal Object Representation
It is useful to know that internally AutoNOC generates a unique number that is representative of every object in the model. This internal number is used for performance reasons and to insure associated links between objects remain constant even though their names may change.