Cisco Cisco Unified MeetingPlace Express 1.1 Libro bianco
Cisco Systems
Network Provisioning and Configuration
Page 11
3 .2 Con f i g u r a t i on Mod e l s
Consistent with the above rules, the following configurations can be supported: (Only the
voice, HTTP, and RTMP services are listed because the other services can be accessed
using any of the IP addresses assigned to the server.)
voice, HTTP, and RTMP services are listed because the other services can be accessed
using any of the IP addresses assigned to the server.)
1.
One Ethernet port, two IP addresses:
a.
Primary: HTTP and voice
b.
Secondary: RTMP
2.
Two Ethernet ports, two IP addresses:
a.
Port 1 (eth0): HTTP and voice
b.
Port 2 (eth1): RTMP
3.
Two Ethernet ports, three IP addresses:
a.
Port 1 (eth0): Voice
b.
Port 2 (eth1), primary: HTTP
c.
Port 2 (eth1), secondary: RTMP
The standard configuration is model 2 and that is the only model supported by the
installation software. You can switch to a different model using the net command after
installation is complete. Model 2 assumes that both ports have connectivity to all clients.
With models 2 and 3, if you connect both ports to the same LAN segment you get a
redundancy effect where failure of one port will, after a timeout, cause traffic to divert to
the other. Note that this mechanism is only supported at the layer 1 network level, so it
will not work if you divide the links between different LAN segments.
Choose model 1 only if you have a gigabit Ethernet port or you are sure all the traffic can
comfortably coexist on a single 100Mb link. Systems with more than six web
conferencing licenses should normally not choose this configuration unless gigabit
Ethernet is employed.
Choose model 3 if it is necessary to isolate the audio onto its own link. This choice is
offered to support dual-network installations, where the audio is isolated onto its own
network. Note the requirement for three distinct IP addresses in this model.
The current configuration options for Cisco MeetingPlace Express do not support the
following:
•
Separation of user and administrative traffic onto different ports.
•
Connecting the two ports onto disjoint networks for security purposes (for
example, one port internal and one on a DMZ).
3 .3 B i n d i n g of T r a f f i c t o Por t s
With two Ethernet ports, it can be useful to control the type of traffic that flows on each
port. For instance, it can be desirable to run the voice on one port and the web
port. For instance, it can be desirable to run the voice on one port and the web