Using Server-Map For Origin Escalation; Configuring Media Flow Controller Server Maps (Cli) - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Configuration Tasks (CLI)
"Server Map Configuration,"
map.
Consistent hash cluster requirements:
•
A cluster is one Level 1 node and >= one Level 2 nodes.
•
Level 1 node must be a Media Flow Controller operating as a reverse proxy.
Example server-map cluster-map configuration:
server-map sm2
format-type cluster-map
file-url http://mapfile.nokeena.com/nfs/path/cluster.xml

Using server-map for Origin Escalation

The server-map format-type origin-escalation-map allows you to specify a set of origin-
servers that are sequentially (in the order defined in the XML server map file) tried until a
request is fulfilled or all defined origins have been tried; if no origin can fulfill the request a 404
(file not found) error is given. See
on page 48
map XML File
for origin-escalation-map.
Origin escalation requirements:
•
All origin servers are viewed as a single entity where any origin server is capable of
resolving a miss or handling a validate request.
•
All origin servers are monitored via a periodic heartbeat (HTTP request) insuring that
escalation only occurs to currently online members.
•
Origin server HTTP response codes resulting in escalation are configurable on a per origin
server basis.
•
Applicable only to a Media Flow Controller reverse proxy configuration.
Example server-map origin-escalation-map configuration:
server-map sm3
format-type
file-url http://mapfile.nokeena.com/nfs/path/originescalation.xml
interval 60

Configuring Media Flow Controller Server Maps (CLI)

Use server maps to configure multiple origin servers for a namespace.
To configure a server-map for either HTTP or NFS origin server:
1. First, create the server-map with a <name> and format-type. To map the incoming
(target origin) HOST header value to a specified origin server, set format-type host-
origin-map. To use consistent hashing to determine the origin server, set format-type
cluster-map. To allow origin escalation (try another defined origin if the first fails), set
format-type origin-escalation-map. To use NFS publishing points for origin, set format-
type nfs-map. For cluster-map and origin-escalation-map only, you can define and add
80 Creating and Configuring Server-Maps (CLI)
for details on clustering and creating the XML file for cluster-
for an overview, server-map
in Chapter 7, "Server Map Configuration,"
origin-escalation-map
Media Flow Controller Administrator's Guide
"Consistent Hash-Based Clustering and Origin Escalation"
for CLI details, and
Copyright © 2010, Juniper Networks, Inc.
refresh-interval 60
Creating the origin-escalation-
for details on creating the XML file
refresh-