Testing Nfs Origin Fetch - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
HTTP request sent, awaiting response... 200 OK
Length: 165 [text/plain]
Saving to: `test.txt.3'
100%[=======================================>] 165
16:17:55 (13.1 MB/s) - `test.txt.3' saved [165/165]
[joe@sv05 joe]$
test-vos-cl11 (config) # show counters
Total number of Active Connections
Total Bytes served from RAM cache
Total Bytes served from Origin Server : 0 Bytes
Total Bytes served from Disk cache
Total Bytes served
Total number of HTTP Connections
Total number of HTTP Transactions
Total number of HTTP 200 responses
Total HTTP Well finished count

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 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. The request must include the configured uri-prefix. Prepare for the test by
doing the following, then follow the given steps as illustrated in
change for the NFS test).
•
Login to the client/origin machine and go to a test directory; for example, testresults/joe;
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/joe
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:
[joe@sv05 joe]$ wget http://172.16.254.1/testresults/joe/test.txt
--13:12:58--
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
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,
Total Bytes served from HTTP Origin Server : 0 Bytes
Total Bytes served from NFS Origin Server : 0 Bytes
http://172.16.254.1/testresults/joe/test.txt
Media Flow Controller Troubleshooting
: 0
: 0 Bytes
: 165 Bytes
: 495 Bytes
: 3
: 3
: 3
: 3
Figure 69
Testing Media Flow Controller Delivery Functions
--.-K/s in 0s
(note the wget path
--.-K/s in 0s
279