Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
m (Procedure)
 
(3 intermediate revisions not shown)
Line 156: Line 156:
# Install the Cisco MCS Operating System on a Cisco MCS server and the latest service pack. See the installation and upgrade guides in the following location: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guides_list.html  
# Install the Cisco MCS Operating System on a Cisco MCS server and the latest service pack. See the installation and upgrade guides in the following location: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guides_list.html  
-
# Connect port1 and port2 to the network.  
+
# Connect port1 and port2 to the network.
 +
'''Note:''' Cisco will provide an installer with Microsoft operating system updates on cisco.com, with instructions to download and deploy these updates.
 +
 +
* Software downloads for the Web Server Windows 2003 operating system is located in the Unified MeetingPlace Security Updates folder:
 +
:* Cisco Unified MeetingPlace Release 7.x - http://www.cisco.com/cisco/software/type.html?mdfid=282340975&flowid=5382
 +
 +
* 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:
 +
http://www.cisco.com/cisco/support/notifications.html
== How to Configure Network Settings ==
== How to Configure Network Settings ==
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Network Interface Card (NIC) Configurations|Network Interface Card (NIC) Configurations]]
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Network Interface Card (NIC) Configurations|Network Interface Card (NIC) Configurations]]
 +
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring the Binding on MCS 7835-I3 and MCS 7845-I3 Servers With Adobe Connect (Adobe Breeze)|Configuring the Binding on MCS 7835-I3 and MCS 7845-I3 Servers With Adobe Connect (Adobe Breeze)]]
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring a Single NIC with Both IP Addresses on the Web Server|Configuring a Single NIC with Both IP Addresses on the Web Server]]
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring a Single NIC with Both IP Addresses on the Web Server|Configuring a Single NIC with Both IP Addresses on the Web Server]]
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring One IP Address per NIC on the Web Server|Configuring One IP Address per NIC on the Web Server]]
* [[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring One IP Address per NIC on the Web Server|Configuring One IP Address per NIC on the Web Server]]
Line 235: Line 245:
[[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring One NIC with Two IP Addresses and One NIC with One Secure IP Address on the Web Server|Configuring One NIC with Two IP Addresses and One NIC with One Secure IP Address on the Web Server]]
[[Cisco Unified MeetingPlace, Release 7.1 -- Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server#Configuring One NIC with Two IP Addresses and One NIC with One Secure IP Address on the Web Server|Configuring One NIC with Two IP Addresses and One NIC with One Secure IP Address on the Web Server]]
|}
|}
 +
 +
 +
=== Configuring the Binding on MCS 7835-I3 and MCS 7845-I3 Servers With Adobe Connect (Adobe Breeze) ===
 +
 +
'''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.
 +
# Install the Web Conferencing Server. See [[Cisco Unified MeetingPlace, Release 7.1 -- How to Install the Cisco Unified MeetingPlace Web Conferencing Server|How to Install the Cisco Unified MeetingPlace Web Conferencing Server]].
 +
=== Changing the IP Address for the NICs on the Web Server ===
=== Changing the IP Address for the NICs on the Web Server ===

Latest revision as of 15:30, 13 June 2012

Main page: Cisco Unified MeetingPlace, Release 7.1

Up one page: Installation


Contents

Reviewing System Requirements

Before preparing to install Cisco Unified MeetingPlace Web Conferencing, read the following:


The Cisco Media Convergence Server (MCS)

The Cisco Unified MeetingPlace Web Server is installed on a Cisco Media Convergence Server (MCS). You may also install it on the exact equivalent server from a different manufacturer.


For complete information about installing the Cisco MCS, see the documentation at this location: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guides_list.html.


Gathering Installation Values

Gather and record the information in Table: Installation Values for Cisco Unified MeetingPlace Web Conferencing.


Table: Installation Values for Cisco Unified MeetingPlace Web Conferencing
Parameter Description Your Value

Hostname of primary MeetingPlace server

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.


For more information on SMA configurations, see How to Install Cisco Unified MeetingPlace Web Conferencing for a Segmented Meeting Access (SMA) Deployment.

Database Location

  • Local server-To install SQL Server 2000 on the Web Server.
  • Existing remote server -To connect to a remote, standalone SQL Server that was previously installed on a separate system.

For information about installing SQL Server, see About Installing the SQL Server on a Remote, Standalone Server.

Remote SQL Server name

(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.

Note: If you choose the remote SQL Server option, you can use SQL Server 2005 (Service Pack 2) instead of SQL Server 2000 (Service Pack 4). To use SQL Server 2005, first install the SQL Server 2005 backward compatibility software (the Distributed Management Objects [DMO] component only) on the Web Server.


See SQL Server Requirements for information about the required service pack.

Installing the Cisco Unified MeetingPlace Application Server

You must install the Cisco Unified MeetingPlace Application Server software before you install Cisco Unified MeetingPlace Web Conferencing. See How to Install the Cisco Unified MeetingPlace Application Server. These are installed on separate servers.


Installing the Cisco MCS Operating System

Procedure
  1. Install the Cisco MCS Operating System on a Cisco MCS server and the latest service pack. See the installation and upgrade guides in the following location: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guides_list.html
  2. Connect port1 and port2 to the network.


Note: Cisco will provide an installer with Microsoft operating system updates on cisco.com, with instructions to download and deploy these updates.

  • Software downloads for the Web Server Windows 2003 operating system is located in the Unified MeetingPlace Security Updates folder:
  • 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:

http://www.cisco.com/cisco/support/notifications.html

How to Configure Network Settings


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.

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

Both NICs enabled, one IP address per NIC

  • 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.

Configuring One IP Address per NIC on the Web Server

Both NICs enabled, teamed, configured in Network Fault Tolerance (NFT) mode

  • One NIC is active, handling traffic for both IP addresses.
  • The other NIC is passive and takes over if the primary NIC fails.* This configuration is available only for HP MCS server models.

How to Configure NIC Teaming on the Web Server (HP Models Only)

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.

Configuring One NIC with Two IP Addresses and One NIC with One Secure IP Address on the Web Server


Configuring the Binding on MCS 7835-I3 and MCS 7845-I3 Servers With Adobe Connect (Adobe Breeze)

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:

  1. IBM USB Remote NDIS Network Device
  2. Broadcom BCM5709C NetXtreme II GigE (NDIS VRD Client) #2
  3. 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

  1. Change the binding order and move the IBM USB Remote NDIS Network Device to the third place in the order.
  2. Reboot the MCS Server.
  3. 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.
  4. Install the Web Conferencing Server. See How to Install the Cisco Unified MeetingPlace Web Conferencing Server.


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

  1. Stop all Cisco Unified MeetingPlace services.
  2. Stop the Cisco MeetingPlace Gateway SIM service.
  3. 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).
  4. Add a new connection to the Cisco Unified MeetingPlace Application Server, using the new client IP address.
  5. Restart the Cisco Unified MeetingPlace Web Conferencing service and wait for all child services to start.
  6. Wait for the end user web to become responsive.
  7. Sign in as the administrator by selecting Home > Administration > Web Server.
  8. 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.
  9. Change the "Hostname [Home Page]" and "Hostname [Web Conferencing]" to the new IP addresses. (The new IP addresses should already appear inside parentheses.)
  10. Click Submit.
  11. Sign out.
  12. 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.


Before You Begin

Follow the procedure for "Configuring Network Settings" in the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server Version 2003.1.2 which can be found here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/install/os200312.html.


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.


Procedure
  1. On the Start menu, click Settings > Network Connections > Local Area Connection.
  2. Click Properties.
  3. Double-click Internet Protocol (TCP/IP).
  4. Click Advanced.
  5. Click Add in the IP Settings tab, in the IP addresses area.
  6. Enter the secondary IP address and subnet mask.
  7. Click Add.
  8. Click OK three times to close the Local Area Connection Properties window.


What To Do Next

Installing Gateway SIM and the Web Conferencing Server Software


Configuring One IP Address per NIC on the Web Server

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


Before You Begin
  • Follow the procedure in the "Configuring Network Settings" section in Installing the Operating System on the Cisco Unified Communications Server Version 2003.1.2 which can be found here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/install/os200312.html.
    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.


Procedure
  1. On the Start menu, click Settings > Network Connections.
  2. Right click Local Area Connection 2 and click Enable.


What To Do Next

Installing Gateway SIM and the Web Conferencing Server Software


How to Configure NIC Teaming on the Web Server (HP Models Only)

Follow the steps in these procedures:


Before You Begin

Follow the procedure in the "Configuring Network Settings" section in Installing the Operating System on the Cisco Unified Communications Server Version 2003.1.2 which can be found here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/install/os200312.html.

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
  1. On the Start menu, click Settings > Network Connections.
  2. Right click Local Area Connection 2 and click Enable.


Configuring Network Teaming

Procedure
  1. On the Start menu, click Settings > Control Panel > HP Network to use the HP Network Configuration Utility.
  2. Refer to the HP Network Configuration Utility online help for instructions.
  3. Select either TLB or NFT.


Adding the Primary IP Address to the NIC Team

  1. On the Start menu, click Settings > Network Connections.
  2. Right-click Local Area Connection 3.
  3. Double-click Internet Protocol (TCP/IP).
  4. Click Properties.
  5. Click Use the following IP address.
  6. In the appropriate fields, enter the server primary IP address, subnet mask, and default gateway.
  7. Enter the DNS server address.
  8. Do one of the following:


Related Topics

Preparing to Install the Cisco Unified MeetingPlace Web Conferencing Server


Adding the Secondary IP Address to the NIC Team

Procedure
  1. On the Start menu, click Settings > Network Connections.
  2. Right-click Local Area Connection 3, then click Properties.
  3. Double-click Internet Protocol (TCP/IP).
  4. Click Advanced.
  5. On the IP Settings tab, in the IP Addresses area, click Add.
  6. Enter the secondary IP address and subnet mask and click Add.
  7. Click OK two times.


Verifying that the NIC Team is Configured Correctly

Procedure
  1. On the Start menu, click Run.
  2. Enter cmd. The command window opens.
  3. Enter ipconfig /all. The connection information displays in the command window. The Local Area Connection 3 (for the network team) should show two IP addresses.


What To Do Next

Installing Gateway SIM and the Web Conferencing Server Software


Configuring One NIC with Two IP Addresses and One NIC with One Secure IP Address on the Web Server

  1. Check the binding order of the NICs by following these steps:
    1. On the Start menu, click Settings > Control Panel > Network Connections.
    2. Click Advanced > Advanced Settings.
    3. Perform Step 2 and Step 3 on the first NIC (LAN or LAN2).
    4. Perform Step 4 on the second NIC.
  2. (To be performed on the first NIC only) Follow the procedure for "Configuring Network Settings" in the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server Version 2003.1.2 which can be found here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/install/os200312.html.


For this procedure, configure the first IP address on the first NIC in the binding order with a static IP address and with DNS, WINS, or the LMHosts file for hostname resolution.

  1. (To be performed on the first NIC only) Add the secondary IP address to the same NIC that you configured in Step 2 by following these steps:
    1. On the Start menu, click Settings > Network Connections.
    2. Right-click Local Area Connection, then click Properties.
    3. Double-click Internet Protocol (TCP/IP).
    4. Click Advanced.
    5. On the IP Settings tab, in the IP Addresses area, click Add.
    6. Enter the secondary IP address and subnet mask and click Add.
    7. Click OK three times to close the Local Area Connection Properties window.
  2. (To be performed on the second NIC only) Configure the second NIC in the binding order with a secure IP address that will be used to connect to the Application Server.
  3. (Optional) Continue performing the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server Version 2003.1.2 which can be found here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/win_os/install/os200312.html.
  4. 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.
  5. Restart the Web Server.

Rating: 0.0/5 (0 votes cast)

Personal tools