• Not all the data in a Device’s configuration is modeled. Only the most frequently used data will be modeled.

  • Not all Devices will support the Attributed Model. The strategy is to support modeling for the most frequently used attributes on the most common Devices. Even within a Device that supports the model, it may not provide certain facilities. For example, a switch may not implement OSPF Protocol settings.

    Review the information contained within the Appendix A, “Model Coverage by Device Class,” for an overview of the current model coverage by Device class.

    Although the Attributed Model supports Attributed Compliance Tests today, neither the generation of attributed remedies, nor the ability to edit attributes and generate pushes from attributed information is currently supported. However support for these capabilities is anticipated in a future release.

    The set of pre-defined queries are accessible from the Automation Library, Library Manager Tree accessible from the Tools option in the menu bar.

    Once a query is selected, the results of the query are displayed. The information is rendered in a spreadsheet-like view called a Result View. The rows within the table represent Objects, and the columns represent Attributes of those Objects. Each cell represents a particular attribute value for a particular object.