Chapter 7 Running Solaris Bandwidth Manager

This chapter gets you started running and explains how to maintain and monitor Solaris Bandwidth Manager.

Starting, Restarting, and Stopping Solaris Bandwidth Manager

To Start Solaris Bandwidth Manager Policy Agent:

1. Log in as root or become superuser.

2. Type:

   # /etc/init.d/bagent.control start

The policy agent is started automatically when you reboot your machine. It starts at run level 2.

To Prevent the Policy Agent Being Restarted When You Reboot

1. Remove the file S89bagent from the /etc/rc2.d directory or rename it so that it no longer begins with the letter S.

To Restart the Solaris Bandwidth Manager Policy Agent

You can also restart the Solaris Bandwidth Manager policy agent, forcing it to reread the configuration information

1. Log in as root or become superuser.

2. Type:

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

To Stop the Solaris Bandwidth Manager

1. Log in as root or become superuser.

2. Type:

   # /etc/init.d/bagent.control stop

   ---

   Note -

   If you are using Solaris Bandwidth Manager in IP-transparent mode, stopping the Solaris Bandwidth Manager policy agent prevents any network traffic being forwarded by the system. To stop bandwidth management without stopping all network traffic, change the configuration so that the interface is in stats mode and restart the Solaris Bandwidth Manager policy agent.

   ---

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.

Monitoring Solaris Bandwidth Manager with SNMP

You can monitor Solaris Bandwidth Manager using Solstice Site Manager, Solstice Domain Manager, or any SNMP monitoring station. The Solaris Bandwidth Manager SNMP agent runs on hosts running the Solaris 2.6, 7, or 8 operating system. It implements the management information base (MIB) found in the file /opt/SUNWconn/ba/snmp/ba_mib. The files associated with SNMP monitoring are all installed in the /opt/SUNWconn/ba/snmp directory.

Ten tables of information are available:

• Interface information

• Class information

• Filter information

• Information on the associations between classes and filters

• Information on parent/child relationships between classes

• A list of routers configured on an interface in IP transparent mode

• Information on the hosts and subnetworks defined in a filter

• A list of the URLs defined in a filter

• A list of the services defined in a filter

• Information on flows

Three traps are defined:

• baDaemonUp, indicating that the Solaris Bandwidth Manager policy agent has started

• baDaemonDown, indicating that the Solaris Bandwidth Manager policy agent has stopped

• baReconfig, indicating that the configuration being used has changed

Configuring SNMP Monitoring

This section assumes you are using either Solstice Site Manager or Solstice Domain Manager as your management platform. In the following instructions, the term SNM refers to either Solstice Site Manager or Solstice Domain Manager.

The Solaris Bandwidth Manager SNMP agent is compatible with the Solstice Enterprise Agents.

To Integrate Solaris Bandwidth Manager SNMP Agents with Solstice Enterprise Agents

1. Copy the files ba.rsrc, ba.reg and ba_read.acl to the /etc/snmp/conf directory.

2. Edit the file /etc/snmp/conf/ba_read.acl to specify hosts that will have read access to the SNMP agent. By default all hosts have access.

3. Copy the files SnmpAgent.html and qm_snmp.zip to the /opt/SUNWconn/ba/html/beans directory.

4. Edit the file /opt/SUNWconn/ba/snmp/ba_trap.acl to specify trap destinations. This file must also contain the local hostname, in order to give the SNMP Master Agent read access to the subagent. Specify the trap destinations as a comma-separated list of hostnames, as follows:

   trap-recipients = { host1, host2, host3 }

5. Stop and restart the Solaris Bandwidth Manager agent and then the SNMP master agent.

Using a Solstice Site or Domain Manager Console

The files ba_mib.oid and ba_mib.schema in the /opt/SUNWconn/ba/snmp directory allow you to query the Solaris Bandwidth Manager SNMP agent from a Solstice Site or Domain Manager console. Copy them to the agents directory (by default /opt/SUNWconn/snm/agents) on the management station. Then rebuild the OID database using the command build_oid. The file ba_mib.traps in the /opt/SUNWconn/ba/snmp directory is used to map the trap numbers to an ASCII string. Append it to the trap file (by default /var/opt/SUNWconn/snm/snmp.traps). See the Solstice Site and Domain Manager documentation for more information about this process.