There is no CLI command that displays SRDF latency. There is a small baseline overhead for and SRDF write, along with the distance penalty. At 20KM you are looking at ballpark 0.7ms.
Have you used SRDF/S previously? Please be aware of the SRDF/S outstanding writes rule...
(up to) one outstanding write per device per path (up to 8 paths).
For example, a host is presented a 4-way striped meta device and is presented down 4 FA paths. This device may have a maximum of 4X4=16 outstanding SRDF/S writes. If concurrent write demands are higher than that, you will see elongated response time.
If you have a UNIX management host, a crude way to measure the Link latency between the sites would be to use the UNIX "time" command on a symdev show to query the R2 device replicated using SRDF/S (There should be a Windows equivalent too.)
For example, if you've got device 111 on Symmetrix 123 replicating to device 112 on Symmetrix 456, this is what you could use, on the SYMCLI host that has the boxes discovered ..
# time symdev show 111 -sid 123
# time symdev show 112 -sid 456 -- look for the 'real' time - this is the total time it took for the process to complete the call.
PedalHarder
3 Apprentice
•
465 Posts
0
February 2nd, 2014 13:00
There is no CLI command that displays SRDF latency. There is a small baseline overhead for and SRDF write, along with the distance penalty. At 20KM you are looking at ballpark 0.7ms.
Have you used SRDF/S previously? Please be aware of the SRDF/S outstanding writes rule...
(up to) one outstanding write per device per path (up to 8 paths).
For example, a host is presented a 4-way striped meta device and is presented down 4 FA paths. This device may have a maximum of 4X4=16 outstanding SRDF/S writes. If concurrent write demands are higher than that, you will see elongated response time.
Anonymous User
67 Posts
0
February 3rd, 2014 00:00
Hello chinmay,
If you have a UNIX management host, a crude way to measure the Link latency between the sites would be to use the UNIX "time" command on a symdev show to query the R2 device replicated using SRDF/S (There should be a Windows equivalent too.)
For example, if you've got device 111 on Symmetrix 123 replicating to device 112 on Symmetrix 456, this is what you could use, on the SYMCLI host that has the boxes discovered ..
# time symdev show 111 -sid 123
# time symdev show 112 -sid 456 -- look for the 'real' time - this is the total time it took for the process to complete the call.
thanks.