Configuration Guide for Cisco Unified MeetingPlace Release 8.5
Managing your Multinode Topology for Cisco Unified MeetingPlace
Downloads: This chapterpdf (PDF - 189.0KB) | Feedback

Configuring your Multinode Topology for Cisco Unified MeetingPlace

Table Of Contents

Configuring your Multinode Topology for Cisco Unified MeetingPlace

Prerequisites for Configuring a Multinode System

Restrictions for Multinode Systems

About Topology Management

Meeting Director Components

Configuring Your Multinode System

System Node Composition

Configuring Regions

Configuring Sites

Associating Users With a Site

About Conference Allocation

Associating Users With a Time Zone

Associating Users With a Preferred Site

Associating Users With a System Default Site

Configuring Nodes

Configuring Your First Node

Configuring Meeting Director Nodes

Configuring Your Meeting Director Settings

Changing a Node into a Meeting Director Node

Changing a Combined Node into a Meeting Director Node

Replacing Your Primary Meeting Director Node

Replacing Your Secondary Meeting Director Node

Changing the IP Address on Your Meeting Director Nodes

Single-Node Systems

About Regional Masters

Configuring Conferencing Nodes

Disabling Conference Overflow

Reconfiguring an Inoperative Conferencing Node

Viewing Node Operation Records


Configuring your Multinode Topology for Cisco Unified MeetingPlace


Release 8.5
Revised: March 27, 2013 9:30 am

You can configure a multinode system by using the Cisco Unified MeetingPlace Topology Management tools.

Prerequisites for Configuring a Multinode System

Restrictions for Multinode Systems

About Topology Management

Configuring Your Multinode System

System Node Composition

Configuring Regions

Configuring Sites

Associating Users With a Site

Configuring Nodes

Viewing Node Operation Records

Prerequisites for Configuring a Multinode System

Configure Cisco Unified Communications Manager (CUCM) dial patterns, SIP route patterns, and associated trunks.

Your deployment type must be Cisco Unified MeetingPlace with WebEx-scheduled. See the Installing the Cisco Unified MeetingPlace Application Server Software module for more information on selecting your deployment type. For more information on deployment types, refer to the Planning Guide for Cisco Unified MeetingPlace Release 8.5 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_
guides_list.html
.

A minimum of two application servers is required to configure a multinode system.

Restrictions for Multinode Systems

The following are multinode Cisco Unified MeetingPlace audio system capacity restrictions:

14,400 G.711 audio ports

16 Cisco Unified MeetingPlace application server nodes consisting of two Meeting Director nodes and 14 conferencing nodes

1,200 ports per conferencing node (G.711) until the 14,400 limit is reached (12 conferencing nodes are required so the other two nodes (creating a total of 14 conferencing nodes) provide supplemental capacity for failover, overflow, etc.)

Maximum of four nodes per region

Maximum of two sites per region (two sites with up to two nodes each or one site with up to four nodes)

Maximum of four regions


Note Video and other audio codecs or SRTP will affect overall system capacity per node depending on what features are enabled.


The following are multinode Cisco WebEx system capacity restrictions:

14,400 web sessions (cloud and/or nodes)

2,000 internal web sessions (using Cisco WebEx Node for MCS)

Four Cisco WebEx nodes (500 sessions each)

Cisco WebEx Node for ASR

Web conferencing per shared port adapter (SPA) (500 sessions each)

HQ Video/VoIP per SPA (capacity based on usage)

About Topology Management

The topology of a multinode system consists of three hierarchical components: nodes, sites, and regions.

Nodes are individual Cisco Unified MeetingPlace application servers. Nodes are grouped into sites. Sites are grouped into regions.

Following are detailed descriptions of each component:

Nodes—Individual Cisco Unified MeetingPlace application servers. Nodes are identified by a unique name in your system and can belong to only one site and one region. There are three types of nodes:

Meeting Director node—Contains the Meeting Director engine that manages the connection to Cisco WebEx and distributes conferences in your system. A multinode system has one Primary Meeting Director node and one Secondary Meeting Director node for redundancy. If the Primary Meeting Director fails or is manually disabled the Secondary Meeting Director becomes active. Cisco recommends that you configure your Meeting Directors as regional masters and that you locate your Meeting Directors in different data centers to provide greater system resiliency.

Conferencing node—Provides audio and video functionality. At least one conferencing node is required in order to host conferences. Additional conferencing nodes provide greater capacity assurance and active-active resiliency for your system.

Combined node—Provides both Meeting Director and conferencing functionality. Combined nodes are only present on systems with four or fewer nodes.

Sites—Logical groups of nodes that have similar functions and capabilities. For example, a site might contain nodes with high-definition video capabilities or it might support all users within a particular time-zone. Sites are identified by a unique name in your system and can belong to only one region. A site contains one to all of the nodes in a region. You can configure a preferred site to host all meetings for specific user profiles.

Regions—Groups of one or more sites. Regions are identified by a unique name in your system. You can have up to four regions in your system.

Related Topics

Configuring Your Multinode System

System Node Composition

Configuring Nodes

Configuring Sites

Configuring Regions

Meeting Director Components

A Meeting Director node performs the following tasks:

Connects each conferencing node to Cisco WebEx.

Distributes meetings through your system to your sites and nodes using the Meetings Broker layer. If a node fails, all meetings on that node are moved to another node by the Meeting Broker Director.


Note If a node fails, any meetings hosted on that node end. All meeting participants must manually rejoin the meeting when this occurs.


Provides system wide meeting event notification.

Provides support for Cisco WebEx nodes.

Performs user synchronization between Cisco Unified MeetingPlace and Cisco WebEx.

Your multinode system must have two Meeting Director nodes. The Primary Meeting Director is the only active Meeting Director unless a failover condition occurs. If a failure occurs, the Secondary Meeting Director, located on a separate node, assumes all Meeting Director tasks. When the Primary Meeting Director comes back online it resumes performing all Meeting Director tasks once it determines that it is an optimal time to resume control. No user action is required.

When you configure your Meeting Director nodes ensure that

You locate your Meeting Director nodes in your deployment where the majority of your conference traffic is.

Network connectivity to your Meeting Director nodes is optimal.

You configure your Meeting Director nodes on your most optimal systems if you are using different types of application servers in your deployment.

Configuring Your Multinode System

Before You Begin

Select MeetingPlace/WebEx with WebEx Scheduling for your deployment type when you install the Cisco Unified MeetingPlace software.

Procedure

 
High-Level Task
Where to Find Instructions

Step 1 

Determine how many nodes to configure and how to group them into sites and regions. Primary and Secondary Meeting Director nodes are required. At least one conferencing node is required in order to host conferences.

See the "System Node Composition" section to determine the node types to configure.

Step 2 

Configure Cisco Unified Communications Manager (CUCM) for multinode topologies.

How to Configure Cisco Unified Communications Manager for a Multinode Topology in the Configuring Call Control for Cisco Unified MeetingPlace module.

Step 3 

Determine which nodes will be your Primary and Secondary Meeting Director nodes.

"Configuring Meeting Director Nodes" section.

Step 4 

Sign in to the Administration Center on your Primary Meeting Director node.

Signing In to the Cisco Unified MeetingPlace Administration Center module.

Step 5 

Add nodes to your system from your Primary Meeting Director node. The second node you configure is your Secondary Meeting Director node. Then configure conferencing nodes.

"Configuring Your First Node" section; "Configuring Meeting Director Nodes" section; and "Configuring Conferencing Nodes" section

Step 6 

Group your nodes according to server type, function, and geographical location.

"System Node Composition" section

Step 7 

Determine how to arrange your nodes in sites and regions.

"Configuring Sites" section and "Configuring Regions" section.

Step 8 

Set your site associations based on time zone, preferred site, and system default site. Time zone is the preferred method of association. You can use the Preferred site setting as an alternative to time zone to establish an association with a site. The System Default site is the primary host for meetings when there is no association between the user and any given site.

"Associating Users With a Site" section.

Related Topics

Planning Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/
ps5664/ps5669/products_implementation_design_guides_list.html
.

System Node Composition

When you configure your multinode system, you can configure two Meeting Directors or combined nodes to ensure that you have a Secondary Meeting Director in the event a failure occurs on the Primary Meeting Director.

You must have one or more nodes that can host conferences. These nodes will either be combined nodes or conferencing nodes depending on the number of nodes in your deployment. In any deployment the first two nodes you configure are your Primary and Secondary Meeting Director nodes. Any additional nodes you add to your system will automatically be configured as conferencing nodes unless the Primary or Secondary Meeting Director nodes are not present.

Each region consists of a regional master node and multiple leaf nodes. Typically the first node added to a region is the regional master node. The regional master node synchronizes data with master nodes in other regions and then transmits the data to other nodes in its parent region.

Sites are logical groups of nodes that enable the system to associate users with a set of conferencing nodes. You can associate users by using the Preferred Site or Time Zone setting in the User Profile configuration.

All nodes in a site should provide the same service. For example, the audio conferencing and video conferencing service provided by all of the nodes within a site should be the same. This ensures a more consistent user experience.

See Table 1 for recommended system node compositions.

Table 1 Recommended System Node Compositions

Number of Nodes
System Composition

1

One application server configured as combined nodes

2

Two application servers configured as combined nodes

3-4

Two application servers configured as combined nodes and the remaining servers as conferencing nodes

5 or more

Two application servers configured as Meeting Director nodes and the remaining servers as conferencing nodes


Related Topics

Configuring Regions

Configuring Sites

Configuring Nodes

How to Configure User Profiles in the Configuring User Profiles and User Groups for Cisco Unified MeetingPlace module

Configuring Regions

New systems have a default region called Region-1 which contains a default site that contains a default node.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Regions.

Step 3 To add a new region, select Add New. The Add/Edit Region dialog box appears.

Step 4 Enter your region name and description and then select Save.

Creating a region automatically creates a site with the default name, Region name Default Site.


What to Do Next

Add or configure a site in a region as described in the "Configuring Sites" section.

Add or configure a node in a region as described in the "Configuring Nodes" section.

Related Topics

Configuring Nodes

Configuring Sites

Configuring Sites

New systems have a default site called Site-1 which contains the system's first node. You can add sites to a region or edit existing sites.


Note The system default site is indicated by a check mark icon.


Before You Begin

Determine whether or not you want to configure your site as a preferred site. For more information on preferred sites, see the "Associating Users With a Preferred Site" section.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Sites.

A listing of all sites on the system organized by region appears.

Step 3 Select Add New to add a site to the region or select the Edit link to modify an existing site.

The Add/Edit Site dialog box appears.

Step 4 Configure the fields.

Step 5 Select Save.


What to Do Next

Add or configure a node in a site as described in "Configuring Nodes" section.

Related Topics

Field Reference: Add/Edit Site Page

System Node Composition

Associating Users With a Site

Configuring Regions

How to Configure User Profiles in the Configuring User Profiles and User Groups for Cisco Unified MeetingPlace module

Associating Users With a Site

There are several mechanisms by which users are associated with sites. The following sections describe how conferences are allocated and how users can be associated with sites:

About Conference Allocation

Associating Users With a Time Zone

Associating Users With a Preferred Site

Associating Users With a System Default Site

About Conference Allocation

Cisco Unified MeetingPlace assigns conferences to nodes based on the following principles:

1. If the Preferred site setting lists a valid site then the system attempts to host your conference on a node in the Preferred Site.

2. If you have not configured a valid Preferred Site the system attempts to host your conference on a node in a site that has been configured to support the user's time-zone.

3. If there is neither a valid Preferred Site or time zone, your system attempts to host your conference on the System Default Site.

4. If there is no valid Preferred Site, time zone, or System Default Site, your system attempts to host your meeting on any node in the system.

Associating Users With a Time Zone

Cisco recommends that you use the Time zone to form the required association. You should only use the Preferred site setting when the time zone setting does not provide ample differentiation between users and groups. For example, if you have two locations (sites) within the same time zone then the administrator can differentiate users based on the Preferred site setting. When determining which site will host a user's meeting, the Preferred site setting takes precedence over the Time zone setting.

Note that the time-zone setting is derived from the time zone of the Cisco WebEx User Profile (provided your profiles are WebEx-owned). The Preferred Site setting is an administrator-only setting.

Configure the time zone to match the time zones specified on a user profile or group.


Note One site can support multiple time zones. When you schedule a meeting from Cisco WebEx you can overwrite the user's or group's time zone for the purpose of scheduling the meeting with a different time zone.


Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Sites.

Step 3 Select Add New to add a new site or Edit to edit an existing site.

Step 4 In the Time Zones section, select the time zones you want to associate your site with from the Available time zones list and click the right arrow to move them to the Time zones for this site.

Step 5 Select Save.

Step 6 Select User Configuration.

Step 7 Select User Groups or User Profiles depending on whether you want to associate a time zone with a user group or a specific user profile.

Step 8 Select a time zone from the Time zone drop-down menu.

Step 9 Select Save.


Associating Users With a Preferred Site

Configure your site to use the Preferred site as your site association. Your system uses the Preferred Site setting when the Time zone setting is insufficient to differentiate between two sets of users that are associated with two different sites.

Cisco recommends that you use your time zone to form the required association. You should only use the Preferred Site setting when the time zone setting does not provide ample differentiation between users and groups. For example, if you have two locations (sites) within the same time zone then the administrator must differentiate users based on the Preferred Site setting. The Preferred Site setting takes precedence over the time zone setting.

You can configure a preferred site for specified groups and users. You can use this feature to associate groups and users with a site that contains nodes configured for a specific purpose. For example, you might configure a site that contains nodes that use high-definition video. Configuring a preferred site can help you ensure that resources are available for large meetings (for example, 250 attendees) that are spread over a small number of hosts.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select User Configuration.

Step 3 Select User Groups or User Profiles depending on whether you want to associate your Preferred Site with a user group or a specific user profile.

Step 4 Select a site from the Preferred site drop-down menu.

Step 5 Select Save.


Associating Users With a System Default Site

Your system uses the System Default Site when neither the Time zone or Preferred site setting results in an association with a site.

It is preferable that you associate users with a site using the time zone or Preferred Site mechanisms.

Configuring Nodes

You must have a Cisco Unified MeetingPlace application server for each node that you want to add to your system. Adding nodes to your system does not disrupt service. The first node you add to your system is your Primary Meeting Director node. You add nodes to your system from your Primary Meeting Director node.


Note The administrative password used to log in to the Cisco Unified MeetingPlace Administration Center of each node that you add to your system is changed to the administrative password of your Primary Meeting Director node.


Configuring Your First Node

Configuring Meeting Director Nodes

About Regional Masters

Configuring Conferencing Nodes

Reconfiguring an Inoperative Conferencing Node

Configuring Your First Node

The first node you configure is your Primary Meeting Director node. The Primary Meeting Director node is also the regional master node for the default region in your system. You build your multinode system from your first node by adding nodes to the system.

The minimum requirement for a multinode system is two Meeting Director nodes and at least one node that can host conferences. Two Meeting Director nodes are required for redundancy purposes.

Your system creates your first node as a combined node which provides both Meeting Director and conferencing functionality. You can change this node into a Meeting Director node by disabling conferencing ability on the node.

Your first node is automatically assigned to a default site and that site is automatically assigned to a default region. You can rename the default site and region.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Nodes.

A listing of the system nodes appears. Initially this list is populated only by the default node. Its node type is Primary Meeting Director (Active) and it is assigned to Site-1 and Region-1.

Step 3 Select the Edit link to modify the node.

The Add/Edit Node dialog box appears.

Step 4 Configure the fields. The hostname and region cannot be changed.

Step 5 Select Save.


What to Do Next

Add and configure additional nodes to your multinode system as described in the "Configuring Nodes" section. See the "System Node Composition" section for recommendations on the types of nodes you should configure.

Edit the site information of your first node as described in the "Configuring Sites" section.

Edit the region information of your first node as described in the "Configuring Regions" section.

Change a combined node to a Meeting Director node as described in "Changing a Combined Node into a Meeting Director Node" section if your system has the required number of nodes described in "System Node Composition" section.

Related Topics

Field Reference: Add/Edit Node Dialog Box

System Node Composition

Configuring Conferencing Nodes

Configuring Meeting Director Nodes

Changing a Combined Node into a Meeting Director Node

Configuring Sites

Configuring Regions

Configuring Meeting Director Nodes

Your first node is automatically configured as the Primary Meeting Director node. The second node you add to your system is automatically configured as the Secondary Meeting Director node. If your Primary Meeting Director node fails, your Secondary Meeting Director node becomes the active Meeting Director. Any conferences currently running on the system are interrupted but attendants can dial back in immediately.

If at any time your system does not have a Secondary Meeting Director node (for example, if the Secondary Meeting Director node has been deleted or it has become inactive), the next node that you add to your system is automatically configured as the Secondary Meeting Director node.

Your Meeting Director nodes are initially configured as combined nodes that provide both Meeting Director and conferencing functionality. You can use combined nodes on systems with four or fewer nodes. Once you have added a fifth node to your system, you must change your combined nodes into Meeting Director nodes by disabling conferencing on both the Primary and Secondary Meeting Director nodes.

You can configure a Meeting Director as a regional master or leaf node. Cisco recommends that you configure Meeting Director nodes as regional masters to ensure optimal system performance.

Configuring Your Meeting Director Settings

Changing a Node into a Meeting Director Node

Changing a Combined Node into a Meeting Director Node

Replacing Your Primary Meeting Director Node

Replacing Your Secondary Meeting Director Node

Changing the IP Address on Your Meeting Director Nodes

Single-Node Systems

Configuring Your Meeting Director Settings

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Meeting Director.

The Meeting Director page appears.

Step 3 Configure the fields described in Table 2.

Table 2 Field Reference: Meeting Director Page

Field
Description

Primary Meeting Director Node

Select the Primary Meeting Director node from the list of available nodes.


Note To change your Primary Meeting Director node you must put it into maintenance mode.


Secondary Meeting Director Node

Select the Secondary Meeting Director node from the list of available nodes.


Note To change your Secondary Meeting Director node you must put it into maintenance mode.


Can Host Conferences

Select No to disable conference hosting. If you select Yes, your Meeting Director is configured as a combined node.


Note Your node must be in maintenance mode to change the conferencing setting.


DSCP (IPv4)

Select your DSCP preference for IPv4.

System Default Site

Select a system default site. A system default site hosts meetings for users who are not associated with any other site in the system. Association is established by the user profile time zone or preferred site setting.


Note The selected site must contain one or more conferencing or combined nodes.



Step 4 Select Save.


Changing a Node into a Meeting Director Node

You can change any node on your system into a Meeting Director node. Your system can only have two Meeting Director nodes so in order to configure another node as a Meeting Director node, you must either delete one of your Meeting Director nodes or reconfigure it as a conferencing node. To change the function of a node, you must first put the node into maintenance mode.

Procedure


Step 1 Sign in to the Administration Center on the Meeting Director node you want to change.

Step 2 Select Maintenance > Maintenance Configuration.

Step 3 Select Start Maintenance Mode Now.


Note It takes approximately one minute for a node to enter maintenance mode. Make sure that the status of the node on the Nodes page and the Maintenance Configuration page indicates that the node is in maintenance mode before you proceed.


Step 4 Sign in to the Administration Center on the node you want to change into a Meeting Director node.

Step 5 Select Maintenance > Maintenance Configuration.

Step 6 Select Start Maintenance Mode Now.


Note It takes approximately one minute for a node to enter maintenance mode. Make sure that the status of the node on the Nodes page and the Maintenance Configuration page indicates that the node is in maintenance mode before you proceed.


Step 7 Sign in to the Administration Center on the Meeting Director node that you put into maintenance mode in Step 3.

Step 8 Select Topology Management > Meeting Director.

The Meeting Director page appears displaying the Primary and Secondary Meeting Director drop-down menus.

Step 9 Select the node that you put into maintenance mode in Step 6 from the Primary or Secondary Meeting Director drop-down menu, depending on which Meeting Director you are changing.

Step 10 Select Save.

Step 11 Sign in to the Administration Center on the node you selected in Step 9.

Step 12 Select Maintenance > Maintenance Configuration.

Step 13 Select Stop Maintenance Mode Now.


Note It takes approximately one minute for a node to exit maintenance mode. Make sure that the status of the node on the Nodes page and the Maintenance Configuration page indicates that the node is in maintenance mode before you proceed.


Step 14 Sign in to the Administration Center on the Meeting Director node that you put into maintenance mode in Step 3.

Step 15 Select Maintenance > Maintenance Configuration.

Step 16 Select Stop Maintenance Mode Now.


What to Do Next

Configure conferencing nodes on your system as described in the "Configuring Conferencing Nodes" section.

Install a license on your new Meeting Director node as described in "Installing and Managing Licenses for Cisco Unified MeetingPlace" section.

Related Topics

System Node Composition

Configuring Conferencing Nodes

Configuring Sites

Configuring Regions

Changing a Combined Node into a Meeting Director Node

You can change your conferencing setting to change a combined node into a Meeting Director node. To change the function of a node, you must first put the node into maintenance mode.


Note If you have only one node on your system and change it from a combined node to a Meeting Director node, you will not be able to host conferences on your system. If you already have two nodes configured as your Primary and Secondary Meeting Director nodes, you cannot configure another node as a Meeting Director node.


Procedure


Step 1 Sign in to the Administration Center on the node you want to change.

Step 2 Select Maintenance > Maintenance Configuration.

Step 3 Select Start Maintenance Mode Now. The system might take a few seconds to enter maintenance mode.


Note It takes approximately one minute for a node to enter maintenance mode. Make sure that the status of the node on the nodes page and the Maintenance Configuration page indicates that the node is in maintenance mode before you proceed.


Step 4 Select Topology Management > Meeting Director.

Step 5 Select No on the Can Host Conferences drop-down list.

Step 6 Select Save.

If you have not configured any other conferencing or combined nodes, a warning message appears: "There are no Nodes with conferencing ability in the System Default Site." You must add one or more conferencing or combined nodes to your system.

Step 7 Remove the node from maintenance mode. Select Maintenance > Maintenance Configuration.

Step 8 Select Stop Maintenance Mode Now.


What to Do Next

Configure conferencing nodes on your system as described in the "Configuring Conferencing Nodes" section.

Install a license on your new Meeting Director node as described in "Installing and Managing Licenses for Cisco Unified MeetingPlace" section.

Related Topics

System Node Composition

Configuring Conferencing Nodes

Configuring Sites

Configuring Regions

Replacing Your Primary Meeting Director Node

You can replace your Primary Meeting Director node by putting it into maintenance mode, deleting it from your system, and then adding a new node to your system.

Before You Begin

Install Cisco Unified MeetingPlace on a new node to add to your system after you have deleted the Primary Meeting Director node.

Procedure


Step 1 Sign in to the Administration Center on your new node.

Step 2 Select Maintenance > Maintenance Configuration.

Step 3 Select Start Maintenance Mode Now.

Step 4 Sign in to the Administration Center on your Primary Meeting Director node.

Step 5 Select Maintenance > Maintenance Configuration.

Step 6 Select Start Maintenance Mode Now.


Note Cisco Unified MeetingPlace takes approximately one minute to put a node into maintenance mode. Make sure that the status of the node on the Nodes page and the Maintenance Configuration page indicates that the node is in maintenance mode before you proceed.


Once your Primary Meeting Director node enters maintenance mode, the Secondary Meeting Director node becomes the active Meeting Director node.

Step 7 Sign in to the Administration Center on your Secondary Meeting Director node.

Step 8 Select Topology Management > Nodes.

Step 9 Select the check box of your Primary Meeting Director node and select Delete Selected.

Your Primary Meeting Director node is deleted and your Secondary Meeting Director node becomes the new Primary Meeting Director node.

Step 10 Select Topology Management > Nodes.

Step 11 Select Add Node.

Step 12 Configure the fields on the Add Node page, specifying the hostname and other information of your new node. Your new node will automatically be configured as your new Secondary Meeting Director node. Cisco recommends that you put your new Secondary Meeting Director node in a different region than your Primary Meeting Director node and that you configure your new Secondary Meeting Director node as a Regional Master. Select Save after you have configured the fields.

Step 13 Sign in to the Administration Center on your new Secondary Meeting Director node.

Step 14 Select Maintenance > Maintenance Configuration.

Step 15 Select Stop Maintenance Mode Now.


What to Do Next

Install a license on your new Secondary Meeting Director node as described in the Installing and Managing Licenses for Cisco Unified MeetingPlace module.

Related Topics

Configuring Your First Node

Configuring Meeting Director Nodes

About Regional Masters

Replacing Your Secondary Meeting Director Node

You can replace your Secondary Meeting Director node by putting it in maintenance mode, deleting it from your system, and then adding a new node to your system.

Before You Begin

Install Cisco Unified MeetingPlace on a new node to add to your system after you have deleted the Secondary Meeting Director node.

Procedure


Step 1 Sign in to the Administration Center on your new node.

Step 2 Select Maintenance > Maintenance Configuration.

Step 3 Select Start Maintenance Mode Now.

Step 4 Sign in to the Administration Center on the node your Secondary Meeting Director node.

Step 5 Select Maintenance > Maintenance Configuration.

Step 6 Select Start Maintenance Mode Now.


Note Cisco Unified MeetingPlace takes approximately one minute to put a node into maintenance mode. Make sure that the status of the node on the Nodes page and the Maintenance Configuration page indicates that the node is in maintenance mode before you proceed.


Step 7 Sign in to the Administration Center on your Primary Meeting Director node.

Step 8 Select Topology Management > Nodes.

Step 9 Select the check box of your Secondary Meeting Director node and select Delete Selected.

Step 10 Sign in to the Administration Center on your Primary Meeting Director node.

Step 11 Select Topology Management > Nodes.

Step 12 Select Add Node.

Step 13 Configure the fields on the Add Node page, specifying the hostname and other information of your new node. Your new node will automatically be configured as your new Secondary Meeting Director node. Cisco recommends that you put your new Secondary Meeting Director node in a different region than your Primary Meeting Director node and that you configure your new Secondary Meeting Director node as a Regional Master. Select Save after you have configured the fields.

Step 14 Sign in to the Administration Center on the node your new Secondary Meeting Director node.

Step 15 Select Maintenance > Maintenance Configuration.

Step 16 Select Stop Maintenance Mode Now.


What to Do Next

Install a license on your new Meeting Director node as described in "Installing and Managing Licenses for Cisco Unified MeetingPlace" section.

Related Topics

Configuring Your First Node

Configuring Meeting Director Nodes

About Regional Masters

Changing the IP Address on Your Meeting Director Nodes

To change the IP address on a Meeting Director node, you must delete the node from your system, reconfigure the IP address on the node, and then add the node back to your system. Once the node is back on your system, you can reconfigure it as a Meeting Director node.

Related Topics

Changing a Node into a Meeting Director Node

Replacing Your Primary Meeting Director Node

Replacing Your Secondary Meeting Director Node

Single-Node Systems

You can configure a single-node system with a single combined node that provides Meeting Director and conferencing features.


Note Single-node systems are supported by Cisco Unified MeetingPlace 8.5 MR2.


About Regional Masters

Regional masters propagate any changes to their subordinate nodes. If a regional master stops operating or if you delete a regional master, change information will not be propagated to your system. If you have a Meeting Director node in a region, Cisco recommends that you configure that node as your regional master.

Related Topics

System Node Composition

Configuring Meeting Director Nodes

Configuring Conferencing Nodes

Conferencing nodes host meetings on your system. Multinode systems provide resiliency by allowing conferences to be hosted on other nodes in the system when an overflow condition occurs.

If your system has four or fewer nodes, your Meeting Director nodes are combined nodes that provide both Meeting Director and conferencing functionality. If your system has five or more nodes, you have dedicated Primary and Secondary Meeting Director nodes that only provide Meeting Director functionality. The remainder of the nodes on your system are conferencing nodes.

When you add a node to a system that has a Primary and Secondary Meeting Director, that node is automatically configured as a conferencing node.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Nodes.

A listing of all nodes on the system organized by region and site appears.

Step 3 Select Add New Node to add a new node or select an Edit link to modify an existing node.

The Add/Edit Node dialog box appears.

Step 4 Configure the fields described in Table 3.

Table 3 Field Reference: Add/Edit Node Dialog Box 

Field
Description

Node Name

Enter a unique name for the node.

Hostname

Enter the unique hostname or IP address of the node.

mpxadmin user password

Enter the mpxadmin user password for the node you want to add or edit.

mpxadmin user password confirm

Confirm the mpxadmin user password for the node you want to add or edit.

Description

Provide a description of the node and its function. For example, "Conferencing node for main campus."

Region

Specify the region. This field will only be usable when adding a node.

Site

Specify the site. You can select a site when adding a node or change the site of an existing node.


Step 5 Select Save.


Troubleshooting Tip

If you add a node to a topology that already has four regions, this new node should automatically sync up with the rest of the system deployment. The sync process can take up to four hours.

If you see the following message during the sync process, let the node continue to sync up with the rest of the system deployment; do not restart service.

Critical data out of sync. Error code 3.

What to Do Next

View or edit the site your node is in as described in the "Configuring Sites" section.

Disabling Conference Overflow

Multinode systems provide system resiliency by allowing conferences to be hosted on other nodes when overflow conditions occur. However, if you do not want one or more sites on your system to allow conference overflow, you must specify that when you configure your site.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select Topology Management > Sites.

Step 3 Select Add Site to add a new site or Edit to edit an existing site.

Step 4 Select No in the Allow overflow meetings from other sites field.

Step 5 Select Save.


Related Topics

Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace module

About Maintenance Windows in the Configuring Maintenance Windows module

Reconfiguring an Inoperative Conferencing Node

If a conferencing node on your system becomes inoperative, you can delete the node and reconfigure it.

Procedure


Step 1 Sign in to the Administration Center on an operating node.

Step 2 Select Topology Management > Nodes.

Step 3 Find the inoperative node that you want to delete. Inoperative nodes are indicated by an icon in the Operational Status column on the nodes page. Select the Delete icon to delete the node and select OK.

Step 4 Install Cisco Unified MeetingPlace on your replacement node.

Step 5 To reconfigure the node, select Add Node.

The Add/Edit Node dialog box appears.

Step 6 Configure the fields described in Table 3, entering the hostname of your replacement node.

Step 7 Select Save.


Viewing Node Operation Records

Use the Node Operation Records page to display a listing of your node additions and deletions. You can view your latest addition or deletion on the Nodes page but to view a complete listing of node operations that have occurred over the previous three days, you must view the Node Operation Records page.

To view your node operation records, select Topology Management > Node Operation Records.

Node operation records are automatically removed after three days. You can manually remove a node operation record by selecting its corresponding Clear Record icon.