A customer has raised some interest in Bandwidth Manager to help monitor and control the bandwidth being used between their various offices in various locale so I went about installing it on my home environment. I won’t add all the screen shots but I will run through the high level steps and add my thoughts.
Before you start though you will want to raise a PMR and reference LO67698: BANDWIDTH MANAGER MODULES DO NOT START UP WITH THE BANDWIDTH MANAGER WAS SERVER which describes a problem where the BWM modules do not start automatically. I noticed this after I installed BWM and have been sent the hot fix which requires a reinstall.
You are required to create a new database. I installed on CentOS 6.4 (64bit) and running the Control Center is difficult. So below is the command you can run using the DB2 command line. This assumes that you already have DB2 installed and that your instance owner is db2inst1.
CREATE DATABASE BWM_DATA AUTOMATIC STORAGE YES ON ‘/opt/IBM/DB2/db2inst1’ DBPATH ON ‘/opt/IBM/DB2/db2inst1’ USING CODESET UTF-8 TERRITORY US COLLATE USING UCA400_NO PAGESIZE 8192;
I used the part number CZYA2ML to instal WAS 188.8.131.52 and CZYH1ML for the iFixes.
The wiki insinuates that you need to use a bind account that has read and write access to LDAP. This is not the case, a read only bind account is fine.
“The bandwidth manager requires an LDAP server to which it has administrative “read/write” access since it looks up, creates, and modifies both users and groups while applying bandwidth management policies. This LDAP server can be any supported LDAP server using the Virtual Member Manager through federated repositories in WebSphere Application Server; use the same LDAP server that is used by the rest of the Sametime deployment. Configuring the WebSphere Application Server LDAP directory for bandwidth manager requires a Bind DN that is a valid LDAP user with administrative privileges.”
When at the “Verifying the SIP Proxy and Registrar virtual host used by the Bandwidth Manager” step of the wiki make a note of the port number for SIP_ProxyRegHOST of the SIP Proxy and Registrar.
When creating the two rules in “Setting up routing from the SIP Proxy and Registrar to the Bandwidth Manager” then use the port number for the port name SIP_DEFAULTHOST of the Conference Manager in the “Conditions” section and also SIP_DEFAULTHOST for the BWM in the “Destination” section.
At first I couldn’t get the traffic filtering from the SIP Proxy Registrar through the BWM. I wasn’t sure whether it was due to mismatch with SIP and TLS. The clients were using TLS to connect to the SIP Proxy Registrar and I configured the routing between the SIP Proxy Registrar and the BWM using SIP over TCP. I wanted to take encryption and certificate exchange out of the equation so I did the following.
Disabled TLS by following the steps in Using the Transport Layer Security (TLS) protocol with Sametime Audio/Video in a load balancing environment. I also changed from TLS to TCP in the screen shot below which is also documented in Changing the SIP transport protocol in the Sametime Media Manager.
I also added the BWM to the trusted IP list as mentioned in Configuring the trusted IP list for the SIP Proxy/Registrar server.
I restarted the Community server as well as BWM and Media Manager components and it still didn’t work.
I then changed from using IP addresses to using host names in both rules on the SIP Proxy Registrar and the configuration section of the BWM and after a restart it started working.
- It’s worth mentioning that if your BWM stops then all audio and video will fail and the clients will have errors pop up.
- I installed this on a new node so I had to install WAS. You can co-locate this and run the Profile Management Tool to create a new profile.
- I would refrain from installing this on another SIP application unless you want to fiddle with ports and virtual hosts.
- If installing on an unsupported OS then ensure all the libraries are installed prior.
- Use the hot fix supplied by IBM.
- Useful documents to help