Groups can be defined as a Group Type
(predefined or custom), a Group Instance (within a Group Type), or
any combination of these items. Cisco VXC Manager allows you to use
predefined Group Types (OS, Platform, Image/Firmware Image Number,
Subnet, Location, TimeZone, VendorID, Custom1, Custom2, and
Custom3) or create any number of custom Group Types and Group
Instances to facilitate the organization of your devices into
functional hierarchies. You can then use these groups to create
custom Views of your devices.
Views offer a way to visually organize your
devices functionally so that you can better manage them. Because
Cisco VXC Manager provides predefined Group Types and allows you to
create custom Group Types and Group Instances, you can easily
organize your devices in ways that best suit your organizational
needs. By combining predefined Group Types, custom Group Types, and
Group Instances you can achieve high levels of granularity in your
Views (for information on creating Views, see Views Management).
In a simple View, you would have a single Group
Type and any number of Group Instances to accommodate your devices.
For example, assume that your company devices are spread among two
buildings. You might want a View that organizes your devices by the
building where the devices reside physically. In this example
- Every View is identified by a View name. In
our example, the view name could be By Building.
- A single-level View uses one Group Type to
organize the devices. In our example, the Group Type is
- The Group Instances within the Group Type
define specific instances of that Group Type. In our example, Cisco
I Building and Cisco II Building could be the two Group Instances
of the general Group Type Building.
Multi-level Views use more than a single
hierarchical level. Each additional level is nested within the
larger level. Just as you can create your own custom Group Type for
a single-level View, you can continue creating custom Group Types
for nested hierarchical levels. For example, assume that, in
addition to organizing your devices by building, your company also
wants to distinguish the devices in each building by the department
in which each device operates. Such a View would assume a slightly
more granular hierarchy than our simple View example. In this
multi-level View case:
- The View name should match the hierarchy of
your view for easy identification. In our example, the View could
be named By Building => Departments.
- Each Group Type corresponds to a view level in
the View. In our example, Building is the Group Type for the View
Level-1, and Departments is the Group Type for View
- The View Level-2 Groups are Group Instances of
the Group Type for that level. In our example, groups such as
Engineering, Sales, and Marketing are all Group Instances of the
general Group Type Departments.