Monitoring the status of Sametime Bandwidth Manager modules

Use the Status tab to monitor the status of the IBM® Sametime® Bandwidth Manager modules. You can start, stop, or restart server modules as needed.

About this task

The Sametime Bandwidth Manager comprises three components, which can be started and stopped independently:

  • Bandwidth Pool Manager: Manages bandwidth allocations.
  • Media Session Controller: Implements the business logic of the bandwidth management component (such as user lookup and application of policies).
  • SIP Frontend: Handles incoming SIP requests and acts as SIP proxy.

To monitor Sametime Bandwidth Manager modules:

Procedure

  1. On the server hosting the Sametime Bandwidth Manager, open the IBM WebSphere® Application Server Integrated Solutions Console and log in as the WebSphere administrator.
  2. Click Sametime Servers > Bandwidth Manager.
  3. Click the Status tab.
  4. Examine the values in the table. Each row represents a component currently deployed in the environment.
  5. Note that the table displays most of the same information as the Configuration tab, but it adds one more column, State. This column indicates the current status of the component instance. It could take four values: Idle, Active, Stopping, and Down. All components go to Idle state after installation or WebSphere Application Server startup. Then all components can be activated or deactivated with "Start" or "Stop" buttons.
    OptionDescription
    Component type The type of the component instance: Bandwidth Pool Manager, Media Session Controller, or SIP Frontend.
    Server name The full IBM WebSphere Application Server name of the server where this component was installed, in the following format -- "CELL/NODE/SERVER" (for example, Websphere302Node01Cell\Websphere302Node01\server1).
    HTTP URI The HTTP URL of this particular instance of the component, in the following format http://HOSTNAME:HTTPPORT/APPLICATIONPATH/ where HOSTNAME is the hostname or IP address of the WebSphere Application Server where the component is installed. HTTPPORT is the HTTP port configured for this server.
    Cluster HTTP URI The common HTTP URL for all instances of the given component type on the cluster. For a single server installation use the same value as for the "HTTP URI" field.
    SIP URI The SIP Address of the bandwidth management component of this particular instance of the "SIP Frontend" (leave it blank for other types). It should be defined in the following format sip:HOSTNAME:SIPPORT where HOSTNAME is hostname or IP address of the WebSphere Application Server where the component is installed. SIPPORT is SIP Port configured for this server.
    Cluster SIP URI The common SIP address for all instances of "SIP Frontend" on the cluster (for single server installation use the same value as for "SIP URI").
    Priority The priority of the current instance. This is an integer value used only for "Bandwidth Pool Manager" components to determine which instance will be acting as primary and which will be running as secondary servers. A smaller number indicates a higher priority).