Example: Media Flow Controller Interface Configuration; Table 6 Example Machine Setup Of Management And Traffic Ports - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide

Example: Media Flow Controller Interface Configuration

When Media Flow Controller initializes, the on-board Ethernet interfaces are numbered Eth0,
Eth1, and so on. When a NIC, dual- or quad- port, is attached to the server, the 1st NIC (goes
by PCI channel number) gets interface names Eth10, Eth11, and so on to Eth19. Second NIC
gets the names Eth20, Eth21, and so on to Eth29; it is assumed that only up to 10 Ethernet
interfaces per NIC exist.
See Table 6, "Example Machine Setup of Management and Traffic Ports,"
Important!
mappings, all interface assignments are handled automatically during manufacturing.
In Table 6 on page
•
Eth 0: Running SNMP, sending analytics to another machine, Web management, SSH,
and Telnet; connected to your internal network.
•
Eth 1: Upstream fetching content from origin; connected to the network that connects to
the origin server.
•
Eth 2 - 5: Service traffic; connected to the public Internet. These interfaces must have IP
addresses.
Table 6 Example Machine Setup of Management and Traffic Ports
Interface
Eth 0
Eth 1
Eth 2
Eth 3
Eth 4
Eth 5
*Eth0 AND Eth1 can be on the same subnet; this examples indicates they are not.
For VXA Series Media Flow Engine appliances, do not ever change the eth name
63, and Figure 5 on page
Connectivity IP Address
onboard 192.168.1.100
onboard 172.20.46.10*
PCIe card 10.1.1.11
PCIe card 10.1.2.11
PCIe card 10.1.3.11
PCIe card 10.1.4.11
Media Flow Controller Configuration Tasks (CLI)
64, example, the wiring logic is:
Subnet
Mask
255.255.255.0 8080, 22
255.255.255.0 80
255.255.255.0 80
255.255.255.0 80
255.255.255.0 80
255.255.255.0 80
Example: Media Flow Controller Interface Configuration
for details.
Open Internet
Ports Access
yes Management
yes Origin fetch
not Traffic
applicable
not Traffic
applicable
not Traffic
applicable
not Traffic
applicable
Purpose
63