Directory Tree for Solaris Bandwidth Manager

When you save the Solaris Bandwidth Manager configuration to the directory, a dedicated subtree is created in the directory. This section explains the structure of the entries in the Solaris Bandwidth Manager subtree.

Figure 6-1 shows the tree structure and the different types of entries allowed at each level in the tree. Refer to "Object Classes" for a definition of each type of entry.

A complete configuration is stored under an entry of type baConf. The subentries stored under the baConf entry describe conditions, groups, policies, and interfaces.

A policy entry usually associates a list of conditions with a list of actions. When all the conditions are satisfied, the associated actions are performed.

Figure 6-1 Directory Information Tree Structure

There is not a one-to-one mapping between the elements of the Solaris Bandwidth Manager configuration file and the way that those elements are stored in the Directory Tree. The diagram below summarizes the way in which the mapping is carried out:

Figure 6-2 Mapping between Solaris Bandwidth Manager and a Directory

In particular, note that Filters are handled using a combination of Conditions and Policies. The condition type used depends on the content of the filter. The condition name is suffixed with -R, -I,-U or -D, depending on the condition type.

Pre-defined services are not saved into the directory structure. Instead, if the policy agent finds a reference to a nonexistent Condition, it is assumed to be a pre-defined service.

Table 6-1 shows the allowed containment relationships for entries stored below baConf. There are no constraints on the superior class for baConf.

Example Directory Tree

When you save the example configuration file shown in "Configuration Examples", the entry is structured like this:

Figure 6-3 Example Directory Tree

The pre-configured services, such as ftp, do not appear as conditions, as pre-configured services are not saved to the directory.