HP 3PAR User's Guide Page 68

  • Download
  • Add to my manuals
  • Print
  • Page
    / 676
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 67
Specifies the port on which to run the test. If this specifier is not used, the test automatically runs
on port 3492.
RESTRICTIONS
The Remote Copy ports must be configured via the controlport command before this test can
be carried out; however, this test can be performed before links are admitted into the Remote Copy
target system.
EXAMPLES
The following example displays a 60-second latency and throughput check of SystemA to SystemB:
SystemB# checkrclink startserver 0:6:1 10.100.33.63
SystemA# checkrclink startclient 2:5:1 10.100.10.10 60
.
.
.
============================================================
TEST SUMMARY from 0:0:1 -> 10.100.18.164
Test Started: Wed Aug 10 10:34:15 PST 2011
Test Finished: Wed Aug 10 10:34:26 PST 2011
============================================================
Latency: 0.104 ms
Lost pings: 0 %
Through-put: 522 Mbits/second
Max MTU: 1500
Tx TCP Segs: 486675
Rx TCP Segs: 199271
TCP retrans: 0 %
Errored Segs: 0 %
Link 2:5:1 is SUITABLE for Remote Copy Use
SystemB# checkrclink stopserver
NOTES
Do not check the links if CPU usage is already close to 100%. The link check temporarily
increases CPU usage.
This test must be performed in two stages. To run a test between SystemA and SystemB:
Start the system on SystemB, specifying the <N:S:P> for SystemB and the <dest_addr>
for SystemA.
a.
# checkrclink startserver <N:S:P> <dest_addr>
If you are running the checkrclink test on RCFC links, note the IP address displayed in the
output.
b. Start the client on the target system (SystemA), specifying the <N:S:P> for SystemA; the
<dest_addr> for SystemB (as an IP address for both RCIP and RCFC links); and the
duration of the test in seconds.
# checkrclink startclient <N:S:P> <dest_addr> <time>
68 Check Commands
Page view 67
1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 675 676

Comments to this Manuals

No comments