-
-If you are driving obdfilter or obdecho instances over the network, you
-must instantiate the echo_clients yourself using lmc/lconf. Set the shell
-array variable 'client_names' to the names of the echo_client instances and
-leave 'ost_names' undefined.
-
-You can optionally prefix any name in 'ost_names' or 'client_names' with
-the hostname that it is running on (e.g. remote_node:ost4) if your
-obdfilters or echo_clients are running on more than one node. In this
-case, you need to ensure...
-
-(a) 'custom_remote_shell()' works on your cluster
-(b) all pathnames you specify in the script are mounted on the node you
- start the survey from and all the remote nodes.
-(c) obdfilter-survey must be installed on the clients, in the same
- location as on the master node.
-
-- First, bring up obdecho instances on the servers and echo_client instances
-on the clients:
- - run the included create-echoclient on a node that has Lustre installed.
- -shell variables:
- - SERVERS: Set this to a list of server hostnames, or `hostname` of
- the current node will be used. This may be the wrong interface, so
- check it. NOTE: create-echoclient could probably be smarter about this...
-
- - NETS: set this if you are using a network type other than
-tcp.
- - example: SERVERS=oss01-eth2 sh create-echoclient
-
-- On the servers start the obdecho server and verify that it is up:
-
-# lconf --node (hostname) /(path)/echo.xml
-# lctl dl
- 0 UP obdecho ost_oss01.local ost_oss01.local_UUID 3
- 1 UP ost OSS OSS_UUID 3
-
-- On the clients start the other side of the echo connection:
-
-# lconf --node client /(path)/echo.xml
-# lctl dl
- 0 UP osc OSC_xfer01.local_ost_oss01.local_ECHO_client 6bc9b_ECHO_client_2a8a2cb3dd 5
- 1 UP echo_client ECHO_client 6bc9b_ECHO_client_2a8a2cb3dd 3
-
-- verify connectivity from a client:
- - lctl ping SERVER_NID
-
-- Run the script on the master node, specifying the client names in an
-environment variable
-
-Example:
-# client_names_str='xfer01:ECHO_client xfer02:ECHO_client
-xfer03:ECHO_client xfer04:ECHO_client xfer05:ECHO_client
-xfer06:ECHO_client xfer07:ECHO_client xfer08:ECHO_client
-xfer09:ECHO_client xfer10:ECHO_client xfer11:ECHO_client
-xfer12:ECHO_client' ./obdfilter-survey
-
-
-- When done: cleanup echo_client/obdecho instances:
- - on clients: lconf --cleanup --node client /(path)/echo.xml
- - on server(s): lconf --cleanup --node (hostname) /(path)/echo.xml
-
-- When aborting: killall vmstat on clients:
-
-pdsh -w (clients) killall vmstat
-
-Use 'lctl device_list' to verify the obdfilter/echo_client instance names
-e.g...
+For the second case i.e. obdfilter-survey over network, following setup
+is to be done.
+- Install all lustre modules including obdecho.
+- Start lctl and check for the device list. The device list must be empty.
+- It is suggested that there should be passwordless enrty between client
+ and server machine to avoid typing password.
+1. Automated run:
+ To run obdfilter-surevy against network you just need to pass parameter
+ case=netdisk and server_nid="<name/nid_of_server>" to the script.
+
+e.g. $ nobjhi=2 thrhi=2 size=1024 server_nid="<name/nid_of_server>" \
+ case=network sh obdfilter-survey
+
+On server side you can see the stats at :
+ /proc/fs/lustre/obdecho/<ost-testfs>/ststs
+where, 'ost_testfs' is the obdecho server created through script.
+
+NOTE: In network test only automated run is supported.
+
+To run against network-disk:
+----------------------------
+- Create a Lustre configuraton using your normal methods
+
+1. Automated run:
+Setup the lustre with required OST's. Make sure that obdecho.ko module is
+present. Then invoke the obdfilter-survey script with parameter case=netdisk.
+e.g. : $ nobjhi=2 thrhi=2 size=1024 case=netdisk sh -x obdfilter-survey
+
+2. Manual run:
+While running manually you need to tell the script all the names of the
+echo_client instances, which should already be up and running.
+e.g. $ nobjhi=2 thrhi=2 size=1024 ECHO_CLIENTS="ECHO_<osc_name> ..." \
+ sh -x obdfilter-survey
+
+
+Output files:
+-------------