The file /etc/opt/SUNWconn/ba/ba_config.location indicates the location of the configuration file currently being used. This can be done by specifying:
A file name -- by default, the configuration file is stored in the directory/etc/opt/SUNWconn/ba
A full pathname -- this is useful if you do not store the configuration file in the default location
A URL, if the configuration is stored in a Directory Service
When the Solaris Bandwidth Manager policy agent starts, it reads the file named in ba_config.location. If ba_config.location does not exist or cannot be read, the policy agent assumes that the configuration file is ba.conf. If the configuration changes while the policy agent is running, it can be re-read by the policy agent (see "Dynamic Reconfiguration").
The directory /etc/opt/SUNWconn/ba also contains the following files:
ba_config.location-sample -- The template for the ba_config.location file
agent.properties-- A file configuring the properties of the policy agent
agent.properties-sample -- A sample file containing policy agent properties
autopush.ba-sample -- The template for the autopush.ba and autopush_usr.ba files. These files are used to insert ipqos between IP and the interface drivers.
Use the autopush.ba file to specify interface drivers located in the /kernel/drv directory.
Use the autopush_usr.ba file to specify interface drivers located in the /usr/kernel/drv directory.
When you configure an interface in Solaris Bandwidth Manager, the relevant changes are made to the autopush.ba and autopush_usr.ba files when you try to reload the new configuration. You must then reboot your system for the changes to take effect. Do not change autopush.ba-sample
/etc/default/ba_info -- A script that sets the environment variables needed by the Solaris Bandwidth Manager software. If you do not install Solaris Bandwidth Manager in the default location, edit this file and specify the correct values for BACONFIGFILES and BAHOME.