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

Configuring the SNMP Agent (CLI) 203
Media Flow Controller Administrator’s Guide Media Flow Controller Common Configuration Tasks (CLI)
Configuring the SNMP Agent (CLI)
You can configure the SNMP agent running in the Media Flow Controller to integrate with
3rdparty Network Management Systems (NMS). The following are the key Media Flow
Controller configuration items:
•
Configure the NMS IP address:
snmp host <NMS_IP_address>
•
Configure the community string, a shared secret between the NMS & Media Flow
Controller:
snmp host <NMS_IP_address> traps <community_string>
•
Enable generation of traps in the Media Flow Controller:
snmp enable traps
•
Configure the events for which traps have to be generated and sent to the NMS:
snmp traps event <trap_event>
See also snmp traps events .
Pre-Staging Content with FTP (CLI)
You pre-stage content to a Media Flow Controller edge cache or origin so it is there when the
first request arrives. Typically, content is pre-staged to origin; however, you can pre-stage
content to the edge, but always pre-stage such content to origin as well because edge caches
function as volatile storage and evict content rapidly.
When you create a namespace, an FTP user is automatically created with the name
<namespace>_ftpuser, without a password. You need to use the CLI username or
namespace commands to give the user a password; then you can log in as that namespace’s
FTP user and issue the FTP commands to push the content to Media Flow Controller (default
FTP port is 21). In this way, each FTP session transfers content only for one namespace at a
time and users cannot view the content of another FTP user.
If the pre-staging is to an attached library (2 machine arrangement), then you can see the
listing of the files using your FTP client. If the pre-staging is to Media Flow Controller directly,
then you can use the namespace object list all command to see the listing of transferred
files.
Note! Pre-staging content in this manner simply places the files on the Media Flow Controller.
In order to pre-process for SmoothFlow, you must follow a different procedure. See Chapter 8,
“SmoothFlow Deployment for more information.
Note! FTP in Media Flow Controller has no checksum support.
Configuring Media Flow Controller Mid-Tier Proxy (CLI)
Service providers are using 3-tier architectures de-coupling front end servers from back-end
storage servers by deploying mid-tier proxies. Mid-tier proxies reduce network latency, save
bandwidth costs, offload origin servers, and scale front-end server throughput. Media requests
are handled by front-end servers, supporting multiple protocols, that issue HTTP fetch