Cisco Cisco MeetingPlace Gateway SIM Guia De Configuração Rápida

The interface eth0 mentioned throughout this module actually refers to the physical Ethernet port 1 on 
the Application Server.

When a node is rebooted, interface eth0 is initially disabled. However, during startup of the 
Cisco Unified MeetingPlace application, the node checks for an active Application Server on the 
network by attempting to ping the eth0 IP address, which is identical on both nodes. If the ping is 
unsuccessful, then the rebooted node enables the eth0 interface and becomes the active server.

Planning Guide for Cisco Unified MeetingPlace at 

Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace at 

 

Learn about failover deployment options in the Planning Guide for Cisco Unified MeetingPlace at 

Install Cisco Unified MeetingPlace as described in the Installation, Upgrade, and Migration Guide 
for Cisco Unified MeetingPlace at 

.

Determine the hostname, IP address, subnet mask, and default gateway for each of the following:

Node 1 eth0 and Node 2 eth0—Shared hostname and IP address, for example: 
meetings.example.com, 10.0.0.1

Node 1 eth0:0—Unique hostname and IP address, for example: 
meetings1.example.com, 10.0.0.2

Node 2 eth0:0—Unique hostname and IP address, for example: 
meetings2.example.com, 10.0.0.3

Configure the Domain Name System (DNS) server for forward and reverse DNS lookup of all three 
hostname–IP address pairs. Verify by running the nslookup hostname and nslookup ip-address 
commands.

Whether you configure Application Server failover before or after you install any Web Server(s) and 
your call-control devices (such as Cisco Unified Communications Manager), make sure that these 
devices identify the active Application Server by using the shared hostname and IP address of eth0.