Media Flow Controller Fault Management : Testing Media Flow Controller Delivery Functions : Testing NFS Origin Fetch

Testing NFS Origin Fetch
NFS origin fetch is very similar to HTTP origin fetch, but the namespace configuration differs slightly. NFS has much more functionality than HTTP. When you configure the namespace, you’ll give the uri origin-server NFS IP address (or hostname) and full path; the uri-prefix can be anything (for example nfs1) and NFS automatically creates that directory when the first request comes in. Note the request must include the configured uri-prefix. Prepare for the test by doing the following, then follow the given steps as illustrated in Figure 7 (note the wget path change for the NFS test).
Login to the client/origin machine and go to a test directory, i.e., testresults/maria; create a simple text file, test.txt, and add some content to give the file some weight.
On the Media Flow Controller, create a new namespace, testNfs, and specify a uri-prefix with a domain, delivery protocol, and origin server; then make the namespace active. Example:
test-vos (config) # namespace testNfs
test-vos (config namespace testNfs) # domain any
test-vos (config namespace testNfs) # match uri /nfs1
test-vos (config namespace testNfs) # origin-server nfs sv05:home/maria
test-vos (config namespace testNfs) # status active
test-vos (config namespace testNfs) # exit
1.
From the client/origin machine, use wget to fetch the file locally (verify Wget). Example:
[maria@sv05 maria]$ wget http://172.16.254.1/testresults/maria/test.txt
--13:12:58-- http://172.16.254.1/testresults/maria/test.txt
Connecting to 172.16.254.1:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165 [text/plain]
Saving to: `test.txt.2'
100%[=======================================>] 165 --.-K/s in 0s
13:12:58 (15.7 MB/s) - `test.txt.2' saved [165/165]
2.
From the client/origin machine, use wget to fetch the file via Media Flow Controller. When Media Flow Controller receives the first request for that namespace, it begins logging it. Media Flow Controller receives the request, matches the uri-prefix to the namespace, and uses that namespace’s defined origin server to retrieve the content. Use show counters on the Media Flow Controller to see what happened. Example (output truncated):
[maria@sv05 maria]$ wget -O newtest http://172.16.254.2/nfs1/test.txt --17:34:26-- http://172.16.254.2/nfs1/test.txt
Connecting to 172.16.254.2:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165 [text/html]
Saving to: `newtest'
100%[=======================================>] 165 --.-K/s in 0s
17:34:26 (26.2 MB/s) - `newtest' saved [165/165]
[maria@sv05 maria]$
test-vos (config) # show counters
Total number of Active Connections : 0
Total Bytes served from RAM cache : 0 Bytes
Total Bytes served from Origin Server : 165 Bytes
Total Bytes served from HTTP Origin Server : 0 Bytes
Total Bytes served from NFS Origin Server : 165 Bytes
Total Bytes served from Disk cache : 0 Bytes
Total Bytes served : 165 Bytes
Total number of HTTP Connections : 1
Total number of HTTP Transactions : 1
Total number of HTTP 200 responses : 1
Total HTTP Well finished count : 1
test-vos (config) #
3.
[maria@sv05 maria]$ wget -O newtest http://172.16.254.2/nfs1/test.txt
--14:07:21-- http://172.16.254.2/nfs1/test.txt
Connecting to 172.16.254.2:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165 [text/plain]
Saving to: `newtest'
100%[=======================================>] 165 --.-K/s in 0.002s
14:07:21 (83.4 KB/s) - `newtest' saved [165/165]
[maria@sv05 maria]$
test-vos (config) # show counters
Total number of Active Connections : 0
Total Bytes served from RAM cache : 165 Bytes
Total Bytes served from Origin Server : 165 Bytes
Total Bytes served from HTTP Origin Server : 0 Bytes
Total Bytes served from NFS Origin Server : 165 Bytes
Total Bytes served from Disk cache : 0 Bytes
Total Bytes served : 330 Bytes
Total number of HTTP Connections : 2
Total number of HTTP Transactions : 2
Total number of HTTP 200 responses : 2
Total HTTP Well finished count : 2
test-vos (config) #
4.
Run the test once more to see Media Flow Controller serve the content from Disk; first restart the delivery service so everything in RAM is moved to disk. Example:
test-vos (config) # service restart mod-delivery
[maria@sv05 maria]$ wget -O newtest http://172.16.254.2/nfs1/test.txt
--16:17:55-- http://172.16.254.2/nfs1/test.txt
Connecting to 172.16.254.2:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165 [text/plain]
Saving to: `newtest'
100%[=======================================>] 165 --.-K/s in 0s
16:17:55 (13.1 MB/s) - `newtest' saved [165/165]
[maria@sv05 maria]$
test-vos-cl11 (config) # show counters
Total number of Active Connections : 0
Total Bytes served from RAM cache : 0 Bytes
Total Bytes served from Origin Server : 0 Bytes
Total Bytes served from HTTP Origin Server : 0 Bytes
Total Bytes served from NFS Origin Server : 165 Bytes
Total Bytes served from Disk cache : 165 Bytes
Total Bytes served : 495 Bytes
Total number of HTTP Connections : 3
Total number of HTTP Transactions : 3
Total number of HTTP 200 responses : 3
Total HTTP Well finished count : 3

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