Cisco Cisco Meeting Server 2000
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
52
Figure 13: Co-located Call Bridges are automatically connected
4. Check that the initialization completed correctly by entering the following command until the
Status is reported as Enabled:
database cluster status
You should see messages similar to:
Status: Initializing
Nodes: 10.1.2.3 (me)
Nodes: 10.1.2.3 (me)
: Connected Master
Interface : a
And later if you re-run the status command:
Status: Enabled
Nodes: 10.1.2.3 (me)
Nodes: 10.1.2.3 (me)
: Connected Master
Interface : a
5.4 Attaching other Database Instances to the Database Cluster
Note: These server(s) can have an empty database and do not need to have a co-located Call
Bridge e.g. virtualized servers set up to be external databases only. (As mentioned
Bridge e.g. virtualized servers set up to be external databases only. (As mentioned
previously
,
these host servers require the dbcluster certificates and keys.)
CAUTION:
The contents of the database currently on this server (if any) will be destroyed.
1. Attach other servers hosting a database that you want to be part of this database cluster.
a. On each such server set the listening interface using the following command:
database cluster localnode <interface>
Note: <interface> can be in any of the formats listed previously in this section
5 Configuring the Databases