Hostname of the Cisco Unified MeetingPlace Application Server to which this Web Server will be attached.

We recommend that you enter a Fully Qualified Domain Name (FQDN).

If you are installing multiple Web Servers that share a database and point to the same Application Server, make sure that the Application Server hostname on all of these Web Servers is the same.

Ensure that you can access the Web Server by this hostname.

Client IP address entry

IP address of the Cisco Unified MeetingPlace Web Server that you are currently installing.

Use the IP address of the Local Area Connection and not the IP address of the Local Area Connection 2. This should be the first NIC in the binding order.

If you are using NIC teaming, enter the IP address that is listed second.

Server location

Internal (Full Access)-Cisco Unified MeetingPlace Web Conferencing is installed with all features enabled, and this server is placed inside your corporate network. In SMA deployments, this server functions as the internal web server.

External (Limited Access)-Cisco Unified MeetingPlace Web Conferencing is installed with attend-only capability. In SMA deployments, this server is placed outside your corporate firewall in an Internet-accessible network, such as a DMZ, and functions as the external web server.

The first time that you install a Web Server, select Internal. You can select external for subsequent Web Servers. If you only have one Web Server, you must select Internal.

(Optional) If you are connecting to a remote, standalone SQL Server, enter its Fully Qualified Domain Name (FQDN). Ensure that you can access the server by this FQDN.

SQL Server account info

If you are installing SQL Server on the local Web Server, the system automatically enters sa as your user name. Do not change this value. You can change it after the installation.

If you are connecting to a remote, standalone SQL Server, we strongly suggest that you enter sa as your user name. After the installation, you can configure a least-privileged SQL account and configure web conferencing to use this account instead.

Caution! The web conferencing installer does not create or verify the existence of the SQL Server account or check the validity of the user name and password combination.

sa

SQL Server password

Password for the SQL Server user name. Enter this twice.

Note: You cannot use a blank password. If you are connecting to a remote, standalone SQL Server, the password you enter during this installation must match the SQL Server password that you used when originally installed SQL Server on the remote, standalone server.

About Installing the SQL Server on a Remote, Standalone Server

Cisco Unified MeetingPlace Web Conferencing requires a SQL Server. You can choose to install the SQL Server on either the same server as the Web Server or on a separate, remote, standalone server.

If you install the SQL Server on the same server, the installer handles the installation of the SQL Server 2000 and service pack 4 on your local system automatically; in this case, no pre-installation steps are required.

If you choose to install the SQL Server on a remote, standalone server, install both the SQL Server and the appropriate service pack on a separate Windows server before installing the Web Server. Ensure that the time on the SQL Server is synchronized to the time on the Application Server and the Web Server.

Frequency of updates: Two weeks after Microsoft Patch Tuesday (Microsoft Patch Tuesday is the second Tuesday of each month).

Sign up to receive a notification whenever new versions are posted to the software download site. Use the Cisco Notification Service to create customized, flexible notification alerts to be sent to you via email or by RSS feed, on critical product support subjects: Security Advisories, Field Notices, End of Sale/Support statements, Software Updates, and Known Bugs:

Network Interface Card (NIC) Configurations

After you install the Cisco MCS operating system, you must configure the network interface cards (NICs). The Cisco Unified MeetingPlace system has two NICs.

Cisco Unified MeetingPlace Web Conferencing has the following networking requirements:

Both NICs need individual IP addresses and distinct hostnames. The hostnames (we recommend you use FQDN) must be resolvable from any location to which you want to provide the web conferencing capability.

Note: The system requires the two host names and IP addresses to distinguish web conferencing traffic from other types of traffic. However, the binding between IP addresses and ports is weak and the Cisco MCS operating system may transmit traffic from either IP address on either port. Consequently, do not assume that the traffic is cleanly divided by type between the two ports.

The two IP interfaces cannot share the same hostname or aliases in DNS. (Hostnames are only required if the server will be configured for SSL.)

Both NICs must be connected to the same Layer 3 subnet and the same Layer 2 Ethernet broadcast domain.

Note: We highly recommend that you configure the duplex of your NICs for Full Duplex (either 100/Full or 1000/Full, as applicable). Autonegotiation may impact Web Conferencing traffic flow.

Cisco Unified MeetingPlace Web Conferencing supports assigning the two required IP addresses by using the following NIC configurations:

Note: Choose and perform only one configuration.

Configuration

Description

Section

One NIC enabled and configured with two IP addresses; second NIC is disabled

Only utilizes one of the two NICs on the system.

The NIC is a single point of failure.* This configuration is available for both HP and IBM MCS server models.

Each NIC on the system is used, although one NIC may be more heavily used than the other.

Each NIC is a single point of failure. If either NIC fails, Web Conferencing will be unavailable.* If the Web Conferencing server is connected to a 100 MB/sec network, the NIC capacity may be exceeded in large meetings with heavy application sharing.

This configuration is available for both HP and IBM MCS server models.

One NIC enabled and configured with two IP addresses; second NIC enabled and configured with a secure IP address

Each NIC on the system is used, although one NIC may be more heavily used than the other.

Each NIC is a single point of failure. If either NIC fails, Web Conferencing will be unavailable.* If the Web Conferencing server is connected to a 100 MB/sec. network, the NIC capacity may be exceeded in large meetings with heavy application sharing.

This configuration is available for both HP and IBM MCS server models.

Note: This procedure only applies if you are using Adobe Connect (Adobe Breeze) with your Cisco Unified MeetingPlace system.

After installing the Cisco MCS operating system on a MCS 7835-I3 or MCS 7845-I3 server, there are three network interfaces:

IBM USB Remote NDIS Network Device

Broadcom BCM5709C NetXtreme II GigE (NDIS VRD Client) #2

Broadcom BCM5709C NetXtreme II GigE (NDIS VRD Client)

By default, the IBM USB Remote NDIS Network Device interface is the first in the binding order. However, you need to change it to the third position in the binding order. Otherwise, the Cisco Unified MeetingPlace Web Conferencing Server will not work properly (you will not be able to ping it) if Adobe Breeze is installed on this network interface.

To avoid this issue and to configure the system properly, complete the following procedure.

Procedure

Change the binding order and move the IBM USB Remote NDIS Network Device to the third place in the order.

Reboot the MCS Server.

Configure the other two network interfaces. For example, you can place Adobe Breeze as first, home page as second, while the third IBM USB Remote NDIS Network Device is disabled.

Changing the IP Address for the NICs on the Web Server

Follow these steps to change the IP addresses on an existing Cisco Unified MeetingPlace Web Server.

Restriction

Change the IP address for BOTH network interface card (NICs) at the same time.

Before You Begin

Record the current Cisco Unified MeetingPlace gateway configuration settings. Make a note of where it is using an Application Server hostname or an IP address. If you do not do this, you will not be able to reconfigure the gateway after you have performed this procedure and the gateway will not connect to the Application Server.

Make sure that the network administrator has updated the DNS records in accordance with the new configuration.

Procedure

Stop all Cisco Unified MeetingPlace services.

Stop the Cisco MeetingPlace Gateway SIM service.

Delete the connection to the existing Cisco Unified MeetingPlace Application Server from the Cisco Unified MeetingPlace Gateway configuration tool (shown as an orange door in the system tray).

Add a new connection to the Cisco Unified MeetingPlace Application Server, using the new client IP address.

Restart the Cisco Unified MeetingPlace Web Conferencing service and wait for all child services to start.

Wait for the end user web to become responsive.

Sign in as the administrator by selecting Home > Administration > Web Server.

Click on the name of the existing Web Server in the lower part of the page. The system loads the Web Server details in the upper part of the page.

Change the "Hostname [Home Page]" and "Hostname [Web Conferencing]" to the new IP addresses. (The new IP addresses should already appear inside parentheses.)

Click Submit.

Sign out.

Restart the Cisco Unified MeetingPlace Web Conferencing service, and wait for the Cisco Unified MeetingPlace Web Server to become accessible.

Configuring a Single NIC with Both IP Addresses on the Web Server

In this procedure you add the secondary IP address to the primary NIC.

In that procedure, you configure the primary NIC on the system with a static IP address and with DNS, WINS, or the LMHosts file for hostname resolution.

Repeat the procedure above for the secondary NIC on the system, using a different IP address on the same subnet, with the same subnet mask and default gateway. If you receive a warning about using the same default gateway, click OK to accept the warning and continue.

In that procedure, you configure the primary NIC on the system with a static IP address and with DNS, WINS, or the LMHosts file for hostname resolution. If you are using the LMHosts file for hostname resolution, add an entry for both the primary and secondary IP addresses and hostnames.

Note: NIC teaming is only supported on HP servers.

Enabling the Secondary NIC

Procedure

On the Start menu, click Settings > Network Connections.

Right click Local Area Connection 2 and click Enable.

Configuring Network Teaming

Procedure

On the Start menu, click Settings > Control Panel > HP Network to use the HP Network Configuration Utility.

Refer to the HP Network Configuration Utility online help for instructions.

When installing the Web Server, replace the IP addresses on the Web Server with the hostnames you configured previously. Hostname [Home Page] is the hostname that you configured in Step 2 and Hostname [Web Conferencing] is the hostname that you configured in Step 3.

Note: You only need to replace the IP addresses with hostnames if you are enabling SSL.