Server-Map Example For Nfs Origin - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller CLI Commands
See "Chapter 7, "Server Map Configuration,"
files.
Notes:
•
node-monitoring
allowed with format-type cluster-map or format-type origin-escalation-map.
•
allowed-fails
declared down. Default is 3, minimum allowed value is 0 (zero); maximum value is 32.
•
connect-timeout
to complete.
•
heartbeat-interval
sending a "heartbeat" signal to the other nodes indicating availability status.
•
read-timeout
complete after the connection is established.
•
file-url
refreshed according to the specified refresh-interval time. Permitted values for time are 0
(no refresh) or 300 seconds (minimum) to 86400 seconds (maximum). Default is 0.
•
format-type
server-map <name> format-type <type> to delete.
•
cluster-map
conjunction with a defined origin-escalation-map.
•
host-origin-map
•
nfs-map
•
origin-escalation-map
based on defined weight, should an origin fail. This format-type can be used in
conjunction with a defined cluster-map.
•
refresh-force
can also be set in the NFS server map XML file (the Media Flow Controller CLI setting
overrides the NFS XML file setting), this feature is not yet available for the HTTP server
map XML file.
show server-map [<name>]
Display the list of, and settings for, all configured server-maps or the specified server-map.
Example:
show server-map
Server-map: smNFS1
Format-Type:
Map File: http://mapfile.example.com/nfs/path/filemapA.xml
Refresh Interval: 60

server-map Example for NFS Origin

For an incoming URL of http://www.example.com/nfs_mnt1/video1.flv, and a server-map
configuration of:
test-vos (config) # server-map smNFS1
test-vos (config server-map smHTTP1) # format-type nfs-map
350 server-map
—Set cluster and origin escalation node monitoring options; only
—Specify how many request failures are allowed before the node is
—Specify the allowable time in milliseconds for the socket connect
—Specify the time in milliseconds for nodes to wait before
—Specify the allowable time in milliseconds for the socket read to
—Specify the file that contains the table of server maps. The mapping file is
—Specify the DTD type of XML file defining the server-map. Use no
—Allows use of consistent hashing. This format-type can be used in
—Maps the incoming HOST header to a defined origin.
—Allows use of NFS publishing points for origin.
—Allows multiple, defined origins to be used, sequentially
—Force a refresh of the server map pointed to by the specified file-url;
Media Flow Controller Administrator's Guide
for information on creating server-map XML
Copyright © 2010, Juniper Networks, Inc.