%_load manual.var%
For the purpose of these examples we'll name one server tenor.webmaster.com and the second one soprano.webmaster.com
Tenor.* is running the Professional edition and Soprano.* is running the Enterprise edition of ConferenceRoom. My first step will be to determine who will be the hub server and accept downlink connections.
Soprano will be the hub so I will type on the server soprano
/as general set hub
On the server tenor.* I will do the opposite I will type
/as general set leaf
Now that we have determined who will be the hub and leaf servers, we need to determine which server will keep on running services. Since the soprano server is Enterprise it means services has more features so we will disable services on the tenor.* server.
On the tenor server type the following
/as services disable
/squit services no longer need these services.
Now we are ready to add the C/N lines
On the soprano server type the following commands:
/as server tenor add
/as server tenor set name tenor.webmaster.com
/as server tenor set host 209.133.0.0
/as server tenor set port 7000
/as server tenor set ping 280
/as server tenor set inpass allegro
/as server tenor set outpass allegro
/as server tenor enable
On the tenor server I will now type the following commands:
/as server soprano add
/as server soprano set name soprano.webmaster.com
/as server soprano set host 209.133.1.1
/as server soprano set port 7000
/as server soprano set ping 280
/as server soprano set inpass allegro
/as server soprano set outpass allegro
/as server soprano enable
Substitute the information for server name host port and password to reflect the information from your servers. Do note that if you do not enter a valid IP address you will not be able to connect the servers, if you should decide to do it all via DNS you need a valid DNS. If you are unsure about setting up Valid IP and DNS you can always contact your own ISP (internet service provider) who will assist you with this.
Once the information is correctly entered on both servers you can now connect both servers together by using the following command:
From the soprano.* server type this:
/connect tenor.* 7000
From the tenor.* server type this:
/connect soprano.* 7000
You need to be a server administrator to enter the configuration of both respective servers, however you simply need to be an IRCop to be able to reconnect servers together. Pay attention to server side messages as they are a good indication as to why 2 servers could not link together.
Linking Multiple Servers Together
Linking 5 or fewer servers
When there are 5 or fewer servers to be linked together, the networking is very simple. Each server defines every other server in its Downstream configuration.
To link a server, you must define it on your console's 'servers' tab, then the administrator of the 'other' server must define you in a similar fashion on his console. To define your end of the connection, perform the following:
Open the ConferenceRoom Configuration tool (control panel) by using the following menu sequence from the Operating System's 'START' button:
START->Programs->Webmaster18->Configure ConferenceRoom
Click the 'servers' tab
Double click in the Server window and enter the following information about the other server connecting to you.
Configuration Name - This is the name of the server or the short name for it example shell.ca.us.webchat.org we would call the configuration name SHELL.
Disabled/Enable- Leave this unchecked
Leaf server/hub server - you will select the type of server it is in this section. If you will allow the server to connect other servers to it or if it can't allow server to connect to it.
Server Name - This would be shell.ca.us.webchat.org
Ping Timeout- Leave this at the default value of 90
Hostname-TCP/IP hostname (or IP address) of the other server
Port -This value must match the value on the other server.
Auto Connect- If this is not checked, you will be required to manually issue the /connect command in order to establish and re-establish the connection
Password Sent -This field must match the other server's 'Password expected' field on his definition for your server on his control panel, servers tab (this is also referred to as inpass)
Password Expected -You invent a value for this field. The other server's 'Password Sent' field on his definition for your server on his control panel, servers tab must match this value (this is also referred to as outpass)
After you have completed this and clicked 'ok' on the dialog, the other server must define you using this same procedure on the configuration tool on his system. Be sure to provide him with your Server name, port number, hostname (or ip address), and a password that you expect. Networks Containing More than 5 Servers
If your network is of greater size, it will benefit you to define your network as an organized hierarchy. There are two basic roles servers can play: hubs and leaves.
Hub - A hub is a server which connects to more than one other server and therefore performs routing functions.
Leaf - A leaf is an end node server. It connects to only one other server, which is always considered 'upstream' to it.
The first step in setting up this networking is to delineate which of the servers will be hubs and which can be leaves. This decision may be affected by geographic or organizational considerations.
To illustrate a geographic approach to building a network, consider the case of a network of 8 servers in which 4 of them are located in San Diego, and while the remaining 4 are in New York.
A logical approach to creating this network is to designate 2 hubs (one in each city) and have all the servers in each city connect to it's city's hub. The final step in completing the network is to link the two hubs together.
The server names assigned for our test network were as follows:
hub1.sd.com hub1.ny.com
leaf1.sd.com leaf1.ny.com
leaf2.sd.com leaf2.ny.com
leaf3.sd.com leaf3.ny.com
Upstream - Downstream
hub1.sd.com (auto-connect) -
Definitions for hub1.sd.com - Definitions for Leaves in San Diego
Upstream - Downstream
leaf2.sd.com
Upstream - Downstream
Definitions for hub1.ny.com - Definitions for Leaves in New York
Upstream - Downstream
leaf1.sd.com
leaf3.sd.com
hub1.ny.com (auto-connect) -
leaf1.ny.com
leaf2.ny.com
leaf3.ny.com