Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Руководство администратора, Страница: 63 / 400

Example: Media Flow Controller Interface Configuration 63
Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI)
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," for details.
Important! For VXA Series Media Flow Engine appliances, do not ever change the eth name
mappings, all interface assignments are handled automatically during manufacturing.
In Table 6 on page 63 , and Figure 5 on page 64 , example, the wiring logic is:
•
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 Connectivity IP Address
Subnet
Mask
Open
Ports Internet
Access
Purpose
Eth 0 onboard 192.168.1.100 255.255.255.0 8080, 22 yes Management
Eth 1 onboard 172.20.46.10* 255.255.255.0 80 yes Origin fetch
Eth 2 PCIe card 10.1.1.11 255.255.255.0 80 not
applicable Traffic
Eth 3 PCIe card 10.1.2.11 255.255.255.0 80 not
applicable Traffic
Eth 4 PCIe card 10.1.3.11 255.255.255.0 80 not
applicable Traffic
Eth 5 PCIe card 10.1.4.11 255.255.255.0 80 not
applicable Traffic
*Eth0 AND Eth1 can be on the same subnet; this examples indicates they are not.