Federating a node into the Sametime Bandwidth Manager cell on Windows

Federating a secondary node running on Windows™ to an IBM® Sametime® Bandwidth Manager cluster allows a central point of administration for the network deployment. Federate the primary node and the secondary node using this procedure.

Before you begin

Expected state: the deployment manager is running.

About this task

Follow these steps to federate a primary node and a secondary node to a Bandwidth Manager cluster. This procedure is located with the information pertaining to secondary nodes because it is easiest to federate both nodes at this time.

Procedure

Set the system clock to exactly the same time as the deployment manager's system clock.
Ping the deployment manager node from the secondary node to make sure the host name is resolvable.
On the secondary node, open a command window and navigate to the bwm_profile_root\bin directory.
Run the following command to add the secondary node to the deployment manager's cell:
```
addNode.bat DM_hostname DM_port_number -includeapps
```
Where DM_hostname is the host name of the deployment manager server. For example:
```
addNode.bat bwm_dm.example.com 8879 -includeapps
```
Port 8879 is the default port on which the deployment manager listens.
Note: After upgrading, the default port on which the deployment manager listens changes. The list of default ports can be found in the bwm_profile_root\logs\AboutThisProfile.txt file for the deployment manager profile.
When prompted, provide the deployment manager's administrative user ID and password. Click OK.
Wait for the operation to complete before proceeding. Look for a success message similar to the following when complete:
```
Node MyserverNodeSecondary has been successfully federated.
```
To verify that the secondary node has joined the deployment manager's cell, log into the Integrated Solutions Console using your administrative user ID and password. Click Log in.
Click Servers > Server Types > WebSphere Application servers. Make sure you can see the deployment manager server and the secondary node's information.
If you already logged in, you must log out and then log in again before you can see changes.
If you have not yet federated the primary node, repeat this procedure to do so. If you have additional Bandwidth Manager application servers, repeat this procedure for each additional server.