Cisco Unified MeetingPlace Express, Release 2.x -- System Requirements

From DocWiki

Revision as of 23:05, 17 December 2009 by Docwikibot (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified MeetingPlace Express, Release 2.x

Previous page: Preparing to Install Cisco Unified MeetingPlace Express


All system requirements for the Cisco Unified MeetingPlace Express system, including the hardware and software supported, are listed in the Release Notes for Cisco Unified MeetingPlace Express Release 2.0 or the Release Notes for Cisco Unified MeetingPlace Express Release 2.1 at this location: http://www.cisco.com/en/US/products/ps6533/prod_release_notes_list.html. Be sure that you have read and understand the system requirements before you proceed with the installation.


Port and IP Address Requirements

The Cisco Unified MeetingPlace Express system has two network interfaces, labeled "port 1" and "port 2" on the rear panel of the Cisco MCS server. The operating system calls these network interfaces "eth0" and "eth1," respectively.


Note: To reiterate, eth0 = port 1, and eth1 = port 2.

  • Both eth0 and eth1 need individual IP addresses and distinct hostnames. The hostnames must be resolvable from any location to which you want to provide the web conferencing capability.
  • Port 1 (eth0) is primarily used for voice media and HTTP signaling, the end-user web interface, and the Administration Center. The hostname associated with port 1 is the one that end users see.
  • Port 2 (eth1) is primarily used for web conferencing.
  • Both eth0 and eth1 must be on the same subnet.
  • Changes to service bindings are not supported at this time. To clarify, audio and HTTP must use port 1 (eth0), while Real Time Messaging Protocol (RTMP) must use port 2 (eth1).


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 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. A benefit to this is partial failure tolerance: provided both ports are connected to the same virtual LAN segment (subnet), if the system starts up with one port disconnected, the operating system will direct all traffic to the other port.


Switch Requirements

  • Ensure that the network configurations for port 1 (eth0) and port 2 (eth1) match the network configurations for the connected switch ports. Specifically:
    • If one side is set to 1000 Mbps full duplex, then also set the other side to 1000 Mbps full duplex.
    • If one side is set to autonegotiate, then also set the other side to autonegotiate.
  • You may use either 100 or 1000 Mbps full duplex. We do not support 10 Mbps links.
  • Your switch must be set to auto negotiation if your speed is set to 1000 Mbps. Otherwise, the interface will not synchronize with the switch and you will not see any network connectivity. If you look at the back of the switch, it will show no connectivity and if you look at the back of the eth0 server, no lights will be lit.

Rating: 0.0/5 (0 votes cast)

Personal tools