Dynamic Reconfiguration

You can change the configuration of Solaris Bandwidth Manager dynamically, without disrupting network traffic.

If you change the configuration and restart Solaris Bandwidth Manager using batool, the policy agent reads the updated file and implements the changes.

If you modify the current configuration, or if you edit ba_config.location to indicate a different configuration file, you can use batool to restart the policy agent. Alternatively, become root or superuser and type the following command:

$ /etc/init.d/bagent.control restart

You can have several configurations to match different traffic patterns at different times of the day. For example, you might want one configuration to be used during normal working hours when there is more interactive traffic, and another to be used overnight and at weekends when files are being updated or backed up over the network.

Creating a Dynamic Reconfiguration Schedule

Using the Schedule window of batool, you can configure Solaris Bandwidth Manager to switch automatically between configuration files at pre-defined times. To display the Schedule window, select Schedule from the tab window. You must configure the following information:

• Filename

  The path and name of the configuration file you want to use.

• Start Date

  The date on which you want to start using this configuration file.

• Start Time

  The time at which you want to start using this configuration file.

• Frequency

  The frequency with which this configuration file will be used: once only, daily, weekly, every 2 weeks, every 4 weeks or yearly.

• Repetitions

  Uses the units of time specified in the frequency field to determine how often the configuration file will be used. For example, if frequency is set to daily, and repetitions to 7, the file will be used daily for 7 days. If frequency is set to weekly, and repetitions to 2, the file is used weekly for 2 weeks. Set this value to Forever if you want the file to be used until you say otherwise.

Restrictions on Dynamic Reconfiguration

There are some restrictions on what can be changed dynamically:

• You cannot change from IP-transparent to non-transparent mode, or from non-transparent to IP-transparent mode.

• If you add an interface, you may have to reboot your system. For more information, see "Configuration Files and Directories ".

• When the policy agent is running in lightweight mode, it is not possible to restart it.