Vdbench online test method - Linux
1. Edit the /etc/hosts file on the hosts that require mutual trust, and add the mapping between the IP addresses and host names of all hosts.
xx.xx.xx.xx LinuxA xx.xx.xx.xx LinuxB ...... xx.xx.xx.xx LinuxN
2. Run the following command on each host to add the trust relationship between hosts:
ssh-keygen -f /root/.ssh/id_rsa -t rsa -P'' ssh-copy-id -i /root/.ssh/id_rsa.pub <host1_name> ssh-copy-id -i /root/.ssh/id_rsa.pub <host2_name> ...... ssh-copy-id -i /root/.ssh/id_rsa.pub <hostn_name>
2. vdbench configuration (only on the first host)
hd=default,vdbench=/root/vdbench502,user=root,shell=ssh hd=hd1,system=<host1_name> ...... hd=hd2,system=<host2_name> sd=sd1,host=hd1,lun=/dev/sdb,openflags=o_direct,thread=64 ...... sd=sdn,host=hd1,lun=/dev/sd..,openflags=o_direct,thread=64 sd=sd2,host=hd2,lun=/dev/sdb,openflags=o_direct,thread=64 ...... sd=sd2,host=hd2,lun=/dev/sdb,openflags=o_direct,thread=64 wd=wd1,sd=sd*,seekpct=0,rdpct=100,xfersize=4K rd=rdx1,wd=wd*,iorate=max,elapse=3000,interval=1,warmup=30
Vdbench online test method - Windows
S1. Install JRE on each Windows server.
S2. Place the Vdbench directory in the same directory on each host, for example, c:\vdbench504.
S3. In the CMD window of each slave server, go to the vdbench directory and run vdbench.bat rsh.
S4. Configuration script of the primary server: For details, see.
hd=default,vdbench=c:\vdbench504,shell=vdbench
hd=host1,system=localhost //Primary end hd=host2,system=xx.xx.xx.xx // and earlier versions: slave servers hd=host3,system=xx.xx.xx.xx hd=host4,system=xx.xx.xx.xx hd=host5,system=xx.xx.xx.xx hd=host6,system=xx.xx.xx.xx hd=host7,system=xx.xx.xx.xx hd=host8,system=xx.xx.xx.xx hd=host9,system=xx.xx.xx.xx hd=host10,system=xx.xx.xx.xx hd=host11,system=xx.xx.xx.xx hd=host12,system=xx.xx.xx.xx sd=default,threads=16,size=39g sd=sd1,host=host1,lun=\\.\PhysicalDrive1 sd=sd2,host=host2,lun=\\.\PhysicalDrive1 sd=sd3,host=host3,lun=\\.\PhysicalDrive1 sd=sd4,host=host4,lun=\\.\PhysicalDrive1 sd=sd5,host=host5,lun=\\.\PhysicalDrive1 sd=sd6,host=host6,lun=\\.\PhysicalDrive1 sd=sd7,host=host7,lun=\\.\PhysicalDrive1 sd=sd8,host=host8,lun=\\.\PhysicalDrive1 sd=sd9,host=host9,lun=\\.\PhysicalDrive1 sd=sd10,host=host10,lun=\\.\PhysicalDrive1 sd=sd11,host=host11,lun=\\.\PhysicalDrive1 sd=sd12,host=host12,lun=\\.\PhysicalDrive1 wd=wd1,sd=sd*,rdpct=50,seekpct=50,xfersize=4KB rd=run1,wd=wd1,iorate=max,warmup=30,elapsed=4800,interval=1,openflags=directio
S5. Run the vdbench.bat -f script file in the CMD window on the active end.
[FAQ]
If Waiting for slave connection fails to run on Windows, ping each host name (including the host name) on each host. If IPv6 is used, perform the following steps:
1. Deselect IPv6 for the management network port of each host.
2. Disable unused and connected NICs on each host to prevent communication with the host.
3. C:\Windows\System32\drivers\etc\hosts of each host: Verify that the IP address and host name of each host are correct.
4. Ping each host name from each host. If the IP address is an IPv4 address, the problem is solved.
