Cisco Cisco Unified MeetingPlace Express 2.1 White Paper
Cisco Systems
Network Provisioning and Configuration
Page 12
conferencing on another, thus separating the high bandwidth traffic from the time critical
traffic. The assignment of services to IP addresses and IP addresses to Ethernet ports,
described above, can provide good control of incoming traffic. However, this only
partially controls how Linux divides outbound traffic.
Cisco MeetingPlace Express only supports traditional Linux (UNIX) packet routing. The
simple rule is Linux always sends traffic on the “cheapest” port for the destination. Only
the destination IP address is used in this calculation, not the source IP address, TCP, or
UDP port. As a result, Cisco MeetingPlace Express does not divide output traffic by type,
only by destination IP address.
In cases where the destination IP address is related to the traffic type, it is possible to
influence routing using the Linux routing tables. This would be the case, for instance,
where voice traffic is separated onto a distinct network, with its own range of IP
addresses. In that case, configure the system as follows:
traffic. The assignment of services to IP addresses and IP addresses to Ethernet ports,
described above, can provide good control of incoming traffic. However, this only
partially controls how Linux divides outbound traffic.
Cisco MeetingPlace Express only supports traditional Linux (UNIX) packet routing. The
simple rule is Linux always sends traffic on the “cheapest” port for the destination. Only
the destination IP address is used in this calculation, not the source IP address, TCP, or
UDP port. As a result, Cisco MeetingPlace Express does not divide output traffic by type,
only by destination IP address.
In cases where the destination IP address is related to the traffic type, it is possible to
influence routing using the Linux routing tables. This would be the case, for instance,
where voice traffic is separated onto a distinct network, with its own range of IP
addresses. In that case, configure the system as follows:
1.
Connect Ethernet port 1 (eth0) to the voice network.
2.
Connect Ethernet port 2 (eth1) to the “all other traffic” network.
3.
Set up the ports and IP addresses using model #3, above.
4.
Set a default gateway on Ethernet port 2 to send most traffic to a router connected
to Ethernet port 2.
5.
Set up a static route, covering the range of audio IP addresses, to send audio
traffic to a router connected through Ethernet port 1. Do not assign a default
gateway to port 1.
gateway to port 1.
The net command can be used to set static routes (described in Configuration Methods).
4 C o n f i g u r a t i o n Me t h o d s
4 .1 D u r i n g I n st a l l a t i on
The Cisco MeetingPlace Express installation program prompts you for the values for the
basic configuration parameters for the two Ethernet ports. This sets the system up using
method 2 (described in Configuration Models).
basic configuration parameters for the two Ethernet ports. This sets the system up using
method 2 (described in Configuration Models).
4 .2 U si n g t h e net Com m a n d
After installation, you can use the net command to modify the initial configuration
settings. To access the net command, use SSH to log in to the CLI as the user called
mpxadmin and then enter net.
Notes:
settings. To access the net command, use SSH to log in to the CLI as the user called
mpxadmin and then enter net.
Notes:
•
You do not need to be logged in as root to use the net command.
•
Shut down the application before changing network settings by entering the
following:
sudo mpx_sys stop
•
Most changes take effect after you reboot the system.