Device objects

By default, AppViz does not change device object definitions on the device. When you edit a network or service object that is a part of an application's flows, regardless of whether the object originated from AppViz, an import, or a device, AppViz initiates a traffic change request to adjust the traffic that is required for the application as a result of the object's new definition in AppViz. When an object that is not used in an active application is edited in AppViz, no change request opens. Additionally, AppViz will not permit deleting a device object, even when it is not used in an application.

Manage device objects in AppViz

Note: In ASMS A30.10 you can:

  • change the content of a network device object, i.e. you can add content to a network device object.

  • delete a network device object. However, you cannot specify from which device. It will be deleted from all devices.

You can choose to enable AppViz to manage device network object definitions on the device via the AppChange plugin. This will allow you to edit and delete device network objects directly from AppViz. AppChange initiates FireFlow object change request (using the Multi Device Object Change Request workflow) whenever a device network object is edited or deleted.

Note: The AppChange plugin applies only to network objects, not service objects. When this the AppChange plugin is configured, network objects will be changed on the device using an object change request, but service objects will still be changed using a traffic change request. Enabling AppChange has no affect on service objects at all.

Note: The AppChange plugin does not affect AppViz's handling of objects which originated in AppViz, objects which originated from a CSV or CMDB import, or objects that originated on a device but are no longer defined on a device.

When AppChange is enabled, the following occurs:

  • AppChange will open a FireFlow object change request to change the definition of the object on the device every time a device object is edited, regardless of whether the object is being used in an application's flows.
  • AppChange will allow deleting device objects and will open a FireFlow object change request to delete the objects from their device(s).
  • AppChange will not allow adding invalid members to device groups.

  • If you attempt to add a member to a group object where the member is defined on some, but not every device the group is defined on, AppViz provides the following options:

    • Creating the member object on the device(s) on which only the group is defined and then adding the member to the group.
    • Splitting the group into two groups in AppViz. AppChange will add the new member to the group on the devices on which the member is defined. For devices on which the member is not defined, the group will maintain its original definition (without the new member).
  • If you attempt to add a member to a group object where the group is defined on some, but not every device the member is defined on, AppChange will only modify the group on the devices where the group is defined.

For more details, see:

Back to top