Configuring Server Maps (Cli) - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Tags:
•
Response Scode—The standard response code when indicating success in calling the
NFS service; you can modify the description:
•
PublishingPoints Interval-Sec—The polling interval; you can modify the number of
seconds. This can also be set in the Media Flow Controller CLI with the server-map
command; the CLI setting overrides the XML file setting:
•
MissingFile Path—A file to use in the case of a missing file path; only needed if you will
be handling streaming of Windows Media content:
•
InvalidPublishingPoint Path—A file to use in the case of an invalid publishing point; only
needed if you will be handling streaming of Windows Media content:
•
PublishingPoint Name—The NFS mount point for that file path. Example:
<PUBLISHINGPOINT NAME="<name>"
PATH="\\<name>.<name>.<name>.com\<mount_point>" />
Important!
incoming URI request. For example, if you define a Publishing Point Name "p12s34"
(<PUBLISHINGPOINT NAME="p12s34">), then incoming URI requests must include that
name in the first part of the URI for the mapping of that publishing point to be successful; for
example, http://p12s34.example.com/path/filename.

Configuring Server Maps (CLI)

In the Media Flow Controller CLI, after you have created the necessary XML file, you define
the server map with the server-map command, and then assign it to a defined namespace.
To define a server map:
1. First, create the server-map with a <name>.
2. Next, set the format-type.
• If this server-map will be assigned to a namespace with an NFS origin-server, set
format-type to nfs-map.
• If this server-map will be assigned to a namespace with HTTP origin-servers without
consistent hashing, set the format-type to host-origin-map, this is the only allowed
value for format-type and applies only to HTTP origin-servers.
• If this server-map will be assigned to a namespace with an HTTP origin-server, and
you want consistent hashing for a cluster configuration, set the format-type to
cluster-map.
• If this server-map will be assigned to a namespace with an HTTP origin-server, and
you want to configure origin escalation, set the format-type to origin-escalation-
map.
server-map <name> [format-type <type>]
3. If you are using a cluster-map or origin-esc-map, optionally set additional allowed-fails
and node-monitoring options:
•
allowed-fails
declared down. Default is 3, minimum allowed value is 0 (zero); maximum value is 32.
The defined Publishing Point Names are expected to be the first component in the
—Specify how many request failures are allowed before the node is
Server Map Configuration
Configuring Server Maps (CLI) 249