Media Flow Controller CLI Commands : server-map

server-map
server-map <name>
file-url <URL> refresh-interval <seconds>
format-type <type> {host-origin-map | cluster-map | nfs-map | origin-escalation-map}
node-monitoring heartbeat
allowed-fails <integer>
connect-timeout<ms>
interval<ms>
read-timeout<ms>
refresh-force
Media Flow Controller can use an XML file to resolve incoming client requests to the right origin sever when Media Flow Controller encounters a cache-miss. Create the XML file following the conventions outlined in Appendix A, “Server Map Configuration and save it; then use these commands to name the server map, reference it with a file-url, provide a format-type, and set other parameters. Once configured, assign the server-map to a namespace origin-server. See “Using namespace origin-server <protocol> server-map” on page 83 for task details. See "Appendix A, “Server Map Configuration," for information on creating server-map XML files. Notes:
node-monitoring—Set cluster and origin escalation node monitoring options; only allowed with format-type cluster-map or format-type origin-escalation-map.
allowed-fails—Specify how many request failures are allowed before the node is declared down. Default is 3, minimum allowed value is 0 (zero); maximum value is 32.
connect-timeout—Specify the allowable time in milliseconds for the socket connect to complete.
heartbeat-interval—Specify the time in milliseconds for nodes to wait before sending a “heartbeat” signal to the other nodes indicating availability status.
read-timeout—Specify the allowable time in milliseconds for the socket read to complete after the connection is established.
file-url—Specify the file that contains the table of server maps. The mapping file is 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—Specify the DTD type of XML file defining the server-map. Use no server-map <name> format-type <type> to delete.
cluster-map—Allows use of consistent hashing. This format-type can be used in conjunction with a defined origin-escalation-map.
host-origin-map—Maps the incoming HOST header to a defined origin.
nfs-map—Allows use of NFS publishing points for origin.
origin-escalation-map—Allows multiple, defined origins to be used, sequentially based on defined weight, should an origin fail. This format-type can be used in conjunction with a defined cluster-map.
refresh-force—Force a refresh of the server map pointed to by the specified file-url; 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

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.