mu 5.7.10 → 5.7.12

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,20 @@
1
+ Copyright (c) 2010 tlichtenberg
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining
4
+ a copy of this software and associated documentation files (the
5
+ "Software"), to deal in the Software without restriction, including
6
+ without limitation the rights to use, copy, modify, merge, publish,
7
+ distribute, sublicense, and/or sell copies of the Software, and to
8
+ permit persons to whom the Software is furnished to do so, subject to
9
+ the following conditions:
10
+
11
+ The above copyright notice and this permission notice shall be
12
+ included in all copies or substantial portions of the Software.
13
+
14
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
15
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
16
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
17
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
18
+ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
19
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
20
+ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
@@ -0,0 +1,1617 @@
1
+ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
+ <html>
3
+ <head>
4
+ <meta content="text/html; charset=ISO-8859-1"
5
+ http-equiv="content-type" />
6
+ <title>Using the Mu Gem</title>
7
+ <style type="text/css">
8
+
9
+
10
+ #masthead{
11
+ margin: 0;
12
+ border-bottom: 1px solid #cccccc;
13
+ width: 600px;
14
+ padding-top: 10px;
15
+ padding-right: 0px;
16
+ padding-bottom: 5px;
17
+ padding-left: 0px;
18
+ }
19
+
20
+ #content{
21
+ float: left;
22
+ width: 600px;
23
+ margin: 0;
24
+ padding: 0 3% 0 0;
25
+ line-height: 16px;
26
+ }
27
+
28
+ #siteInfo{
29
+ clear: both;
30
+ border: 1px solid #cccccc;
31
+ font-size: 75%;
32
+ color: #cccccc;
33
+ background-color:inherit;
34
+ padding: 10px 10px 10px 10px;
35
+ margin-top: 0px;
36
+ width: 100%;
37
+ }
38
+
39
+ body {
40
+ background-color: #FFFFFF;
41
+ font-family: Arial, sans-serif;
42
+ font-size: 9pt;
43
+ color: #333333;
44
+ left:auto;
45
+ top: auto;
46
+ bottom: auto;
47
+ margin: 10 0 0 10px;
48
+ right: auto;
49
+ width: 95%;
50
+ }
51
+
52
+ p {
53
+ font-family: Arial, sans-serif;
54
+ font-size: 9pt;
55
+ text-align: left;
56
+ line-height: 16px;
57
+ width: auto;
58
+ margin-top: 10px;
59
+ margin-left: 10px;
60
+ padding: 0px;
61
+ }
62
+
63
+ a:link, a:visited {
64
+ color: #3B6EBF;
65
+ background-color: transparent;
66
+ text-decoration: none;
67
+ }
68
+
69
+ a:hover {
70
+ color: #3B6EBF;
71
+ text-decoration: underline;
72
+ }
73
+
74
+ .note {
75
+ font-style: italic;
76
+ font-size: 9pt;
77
+ font-family: Helvetica, Arial, sans-serif;
78
+ margin-top: 10px;
79
+ margin-right: 0;
80
+ margin-bottom: 5px;
81
+ margin-left: 10px;
82
+ width: 85%;
83
+ }
84
+
85
+ li {
86
+ font-family: Arial, sans-serif;
87
+ font-size: 9pt;
88
+ font-weight: normal;
89
+ line-height: 16px;
90
+ width: auto;
91
+ margin-top: 0px;
92
+ margin-right: 0px;
93
+ margin-bottom: 10px;
94
+ margin-left: 6px;
95
+ padding-top: 0px;
96
+ padding-right: 2%;
97
+ padding-bottom: 0px;
98
+ padding-left: 0px;
99
+ }
100
+
101
+ ul {
102
+ list-style-type: disc;
103
+ list-style-position: outside;
104
+ margin-top: 8px;
105
+ }
106
+
107
+
108
+ h1{
109
+ font-family: Arial, Helvetica, sans-serif;
110
+ font-size: 12pt;
111
+ color: #E95D20;
112
+ background-color: inherit;
113
+ padding-top: 10px;
114
+ background-image: none;
115
+ font-weight: bold;
116
+ margin: 0px;
117
+ width: 100%;
118
+ text-align: center;
119
+ }
120
+ .subhead {
121
+ font-family: Arial, Helvetica, sans-serif;
122
+ font-size: 9pt;
123
+ font-style: italic;
124
+ line-height: 16px;
125
+ text-align: center;
126
+ margin-right: 120px;
127
+ margin-left: 120px;
128
+ }
129
+
130
+ h2{
131
+ -moz-border-radius-bottomleft:0;
132
+ -moz-border-radius-bottomright:0;
133
+ -moz-border-radius-topleft:8px;
134
+ -moz-border-radius-topright:8px;
135
+ color:#E95D20;
136
+ font-family:Arial, sans-serif;
137
+ font-size:10pt;
138
+ font-style:oblique;
139
+ margin:25 0 0 8px;
140
+ padding: 4 2 1 0px;
141
+ }
142
+
143
+ h3{
144
+ -moz-border-radius-bottomleft:0;
145
+ -moz-border-radius-bottomright:0;
146
+ -moz-border-radius-topleft:8px;
147
+ -moz-border-radius-topright:8px;
148
+ border:1px solid silver;
149
+ font-size: 9pt;
150
+ color: #333333;
151
+ background-color: #E7E7E7;
152
+ font-weight: bold;
153
+ width: 600px;
154
+ padding-top: 4px;
155
+ padding-bottom: 1px;
156
+ padding-left: 6px;
157
+ margin-top: 20px;
158
+ margin-left: 6px;
159
+ }
160
+
161
+ h4{
162
+ font-size: 9pt;
163
+ font-weight: bold;
164
+ vertical-align: top;
165
+ text-align: left;
166
+ margin-top: 0px;
167
+ margin-right: 15px;
168
+ margin-bottom: 5px;
169
+ margin-left: 10px;
170
+ color: #333333;
171
+ font-style: normal;
172
+ font-variant: normal;
173
+ text-transform: none;
174
+ border: #DFDFDF; }
175
+
176
+
177
+ h5{
178
+ font-size: 9pt;
179
+ color: #333333;
180
+ font-style: italic;
181
+ font-weight: normal;
182
+ margin: 6px 2px 4px 2px;
183
+ padding: 0px;
184
+ }
185
+
186
+ h6 {
187
+ border:1px solid silver;
188
+ font-size: 9pt;
189
+ color: #333333;
190
+ font-weight: normal;
191
+ background-color: #E7E7E7;
192
+ width: 96%;
193
+ padding-top: 4px;
194
+ padding-bottom: 1px;
195
+ padding-left: 4px;
196
+ margin-top: 15px;
197
+ margin-left: 4px;
198
+ margin-right:2px;
199
+ margin-bottom:1px;
200
+ }
201
+
202
+ .copyright {
203
+ font-size: 9pt;
204
+ font-style: italic;
205
+ }
206
+
207
+ /*********** begin wide tables ***********/
208
+ table.wide {
209
+ background: #FFFFFF;
210
+ border-collapse: collapse;
211
+ align: left;
212
+ width: 98%;
213
+ margin-top: 3%;
214
+ margin-right: 1%;
215
+ margin-bottom: 3%;
216
+ margin-left: 15px;
217
+ }
218
+ table.wide th, table.wide td {
219
+ border: 1px silver solid;
220
+ padding: 0.2em;
221
+ }
222
+
223
+ table.wide td {
224
+ width:auto;
225
+ font-family: Arial, Helvetica, sans-serif;
226
+ font-size: 9pt;
227
+ height: auto;
228
+ line-height:16px;
229
+ padding:6px 2px 2px 4px;
230
+ }
231
+
232
+ table.wide th {
233
+ background: #E7E7E7;
234
+ text-align: left;
235
+ vertical-align: middle;
236
+ font: Arial, Helvetica, sans-serif;
237
+ font-size: 9pt;
238
+ font-weight: bold;
239
+ color: #333333;
240
+ padding-top: 4px;
241
+ padding-right: 4px;
242
+ padding-bottom: 2px;
243
+ padding-left: 6px;
244
+ }
245
+
246
+ #important{
247
+ float: clear;
248
+ color: #333333;
249
+ background-color: #e7eedc;
250
+ -moz-border-radius-bottomleft:0;
251
+ -moz-border-radius-bottomright:0;
252
+ -moz-border-radius-topleft:8px;
253
+ -moz-border-radius-topright:8px;
254
+ border:1px solid silver;
255
+ font-size: 9pt;
256
+ padding-top: 2px;
257
+ padding-bottom: 0px;
258
+ padding-left: 2px;
259
+ margin-top: 15px;
260
+ margin-left: 15px;
261
+ margin-right: 35px;
262
+ margin-bottom: 15px;
263
+ }
264
+
265
+ .code{
266
+ font-family: Courier, monospace;
267
+ font-size: 9pt
268
+ }
269
+
270
+
271
+ /*********** end wide tables ***********/
272
+
273
+ -->
274
+ </style>
275
+ </head>
276
+ <body>
277
+ <div id="masthead">
278
+ <h1>Mu Ruby Gem</h1>
279
+ <p align="center" class="subhead">API Commands for the Mu System</p>
280
+ </div>
281
+
282
+ <div id="content">
283
+ <p><font class="body"><a name="top" id="cmd_runscale4"></a></font>The Mu.gem contains command line application (executables) designed to help you work with Scenarios, Test Sets, Scale tests and all results generated from those tests. In addition, the Mu.gem also supports older REST API commands that you can use to configure the Mu network, get system status, or even access the Mu CLI. Finally, the Mu. gem exposes API library classes that you can use in your own custom gems. </p>
284
+ <div id="important">
285
+ <p><strong>Before Using This Gem</strong>:</p>
286
+ <ul>
287
+ <li><strong><em>Ensure that you have installed the necessary software</strong></em>
288
+ You must have installed ruby 1.8.6 and the following gems. (type <strong>sudo gem install</strong><em>&lt;gem&gt;</em>):
289
+ <ul>
290
+ <li><em>json_pure</em>. Don't confuse this with the json gem (that won't work).</li>
291
+ <li><em>nokogiri</em>. See http://nokogiri.org/tutorials/installing_nokogiri.html for help.</li>
292
+ <li><em>rest-client</em>. Used for HTTP calls. </li>
293
+ <li><em>mime-types</em>. Required by REST-client.</li>
294
+ </ul>
295
+ </li>
296
+ <li><strong><em>Set the Mu environment variables</em></strong>.
297
+ <ul>
298
+ <li><em><span class="MsoNormal1">MU_IP</span></em><span class="MsoNormal1">. Set the default IP addr</span>ess of the Mu management interface.</li>
299
+ <li><em>MU_ADMIN_USER</em>. Set the default name of the admin user.</li>
300
+ <li><em>MU_ADMIN_PASS</em>. Set the default <span class="MsoNormal1">admin user password</span>(do not use the ':' or '@' characters in the password).</li>
301
+ </ul></li></ul></div>
302
+ <p>The following table lists each API section and the associated commands:</p>
303
+ <table width="500" border="1" cellpadding="1" cellspacing="1" class="wide">
304
+ <tr>
305
+ <th width="68%" scope="col">&nbsp;</th>
306
+ <th width="32%" scope="col">&nbsp;</th>
307
+ </tr>
308
+ <tr>
309
+ <td><p class="MsoNormal"><strong>Executables</strong>&nbsp;&nbsp;&nbsp;<a href="#executables">&nbsp;&nbsp;&nbsp;go to section &raquo;</a></p>
310
+ <p class="MsoNormal">These command-line applications are used for loading and verifying Scenarios, creating and running Test Sets, and configuring and running Scale tests.</p></td>
311
+ <td><ul>
312
+ <li><a href="#cmd_appid">cmd_appid</a><span
313
+ style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span></li>
314
+ <li><a href="#cmd_runscale">cmd_runscale</a></li>
315
+ <li><a href="#cmd_runverify">cmd_runverify</a></li>
316
+ <li><a href="#cmd_runscenario">cmd_runscenario</a></li>
317
+ </ul></td>
318
+ </tr>
319
+ <tr>
320
+ <td><p class=MsoNormal><strong>Legacy REST API Commands</strong> &nbsp;<a href="#executables"></a>&nbsp;<a href="#executables"></a>&nbsp;<a href="#executables"></a><a href="#api-methods">go to section &raquo;</a>
321
+ </p>
322
+ <p> These commands provide access to legacy REST API commands supported by the Mu system. </p></td>
323
+ <td><ul>
324
+ <li><a href="#cmd_ddt">cmd_ddt</a></li>
325
+ <li><a href="#cmd_scale">cmd_scale</a></li>
326
+ <li><a href="#cmd_netconfig">cmd_netconfig</a></li>
327
+ <li><a href="#cmd_muapi">cmd_muapi</a></li>
328
+ <li><a href="#cmd_homepage">cmd_homepage</a></li>
329
+ <li><a href="#cmd_system">cmd_system</a></li>
330
+ <li><a href="#cmd_cli">cmd_cli</a></li>
331
+ </ul></td>
332
+ </tr>
333
+ <tr>
334
+ <td><p><strong>API Library Classes</strong> &nbsp;<a href="#library-classes">&nbsp;&nbsp;&nbsp;go to section &raquo;</a>
335
+ </p>
336
+ <p>These API library classes can be &lsquo;required&rsquo; and used within Ruby scripts (
337
+ like most ruby gems).</p></td>
338
+ <td><ul>
339
+ <li><a href="#ddt">ddt</a></li>
340
+ <li><a href="#scale">scale</a></li>
341
+ <li><a href="#netconfig">netconfig</a></li>
342
+ <li><a href="#muapi">muapi</a></li>
343
+ </ul></td>
344
+ </tr>
345
+ </table>
346
+ <h3><a name="executables" id="features3"></a>Executables </h3>
347
+ <p>The following command-line applications are used for loading and verifying Scenarios, creating and running Test Sets, and configuring and running Scale tests.</p>
348
+ <ul>
349
+ <li><a href="#cmd_appid">cmd_appid</a><span
350
+ style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span></li>
351
+ <li><a href="#cmd_runscale">cmd_runscale</a></li>
352
+ <li><a href="#cmd_runverify">cmd_runverify</a></li>
353
+ <li><a href="#cmd_runscenario">cmd_runscenario</a> </li>
354
+ </ul>
355
+ <h2><a name="cmd_appid" id="features4"></a>cmd_appid</h2>
356
+ <p>Use to run Scale tests for a multi-host App-ID .msl file or a directory of .msl files. Supports command-line options for setting test parameters (such as concurrency and pattern) and for configuring a client/server &quot;passthrough&quot; Test Bed. Mu Studio automatically collapses all hosts in the App-ID Scenario to just two hosts, which must be set to two Mu interfaces. </p>
357
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
358
+ <tr>
359
+ <th>Command</th>
360
+ <th>Description &amp; Examples</th>
361
+ </tr>
362
+ <tr>
363
+ <td><em>help</em></td>
364
+ <td><p>Gets help for all cmd_appid commands: <strong>help</strong></p>
365
+ <h6 class="code">mu cmd_appid:help</h6></td>
366
+ </tr>
367
+ <tr>
368
+ <td><h5>run_file</h5></td>
369
+ <td><p> Runs the specified .msl file: <strong>run_file -s</strong> <em>msl-filename</em></p>
370
+ <h6><span class="code">mu cmd_appid:run_file -s msl_file -i a1,a2 -m
371
+ admin:admin@10.10.2.2 -p 1-10000:60</span></h6></td>
372
+ </tr>
373
+ <tr>
374
+ <td><em>run_dir</em></td>
375
+ <td><p>Runs all .msl files in the specified directory: <strong>run_dir -d</strong> <em>msl-directory</em></p>
376
+ <h6><span class="code">mu cmd_appid:run_dir -d msl_file_directory -i a1-10000,a2
377
+ -m admin:admin@10.10.2.2 -p 1-100000:360</span></h6>
378
+ <p></p></td>
379
+ </tr>
380
+ <tr>
381
+ <td><em>running?</em></td>
382
+ <td><p>Gets status of the scale player: <strong>running?</strong></p>
383
+ <h6><span class="code">mu cmd_appid:running?</span></h6></td>
384
+ </tr>
385
+ </table>
386
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
387
+ <tr>
388
+ <th colspan="2">Options (short &amp; long form)</th>
389
+ <th width="60%">Description</th>
390
+ </tr>
391
+ <tr>
392
+ <td width="4%">-a</td>
393
+ <td width="36%"><strong>--vector_address_pairing</strong></td>
394
+ <td>Sets vectorAddressPairing to true, which limits and maps concurrencies to the rows in the testset.</td>
395
+ </tr>
396
+ <tr>
397
+ <td width="4%">-c</td>
398
+ <td width="36%"><strong>--csv</strong> <em>csv-filename</em></td>
399
+ <td>Specify the filename of the .csv file that contains the test cases to run.</td>
400
+ </tr>
401
+ <tr>
402
+ <td>-d</td>
403
+ <td><strong>--dir</strong> <em>directory</em></td>
404
+ <td>Specify the directory that contains .msl files to run(required for run_dir).</td>
405
+ </tr>
406
+ <tr>
407
+ <td>-h</td>
408
+ <td><strong>--help</strong></td>
409
+ <td>Get help on command line options.</td>
410
+ </tr>
411
+ <tr>
412
+ <td>-i</td>
413
+ <td><strong>--interfaces</strong> <em>interfaces</em></td>
414
+ <td>Specify Mu interfaces as a comma-separated list. Example: <span class="code">b1, b2</span>. When using an IP range, specify range and offset. Example: <span class="code">b1-1000:0,b2</span></td>
415
+ </tr>
416
+ <tr>
417
+ <td>-l</td>
418
+ <td><strong>--delay</strong> <em>delay_value</em></td>
419
+ <td>Intra-scenario delay value, in milliseconds. Default is 0.</td>
420
+ </tr>
421
+ <tr>
422
+ <td>-m</td>
423
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
424
+ <td>Specify the user, password, and mgmt IP of the Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
425
+ </tr>
426
+ <tr>
427
+ <td>-n</td>
428
+ <td><strong>--no_verify</strong> </td>
429
+ <td>Option to not call verify before start.</td>
430
+ </tr>
431
+ <tr>
432
+ <td>-o</td>
433
+ <td><strong>--output</strong> <em>filename</em></td>
434
+ <td>Specify the filename to which you want to output logs.</td>
435
+ </tr>
436
+ <tr>
437
+ <td>-p</td>
438
+ <td><strong>--pattern</strong> <em>con-start</em>:<em>dur</em>,<em>con-end</em>:<em>dur</em></td>
439
+ <td>Specify pattern as concurrency_start:duration,concurrency-end:duration. Duration is in seconds. Example:
440
+ <span class="code">1-10000:60,10000-1:30</span>. </td>
441
+ </tr>
442
+ <tr>
443
+ <td>-r</td>
444
+ <td><strong>--recursive</strong> </td>
445
+ <td>for run_dir command, recurse through the specified directory </td>
446
+ </tr>
447
+ <tr>
448
+ <td>-s</td>
449
+ <td><strong>--scenario</strong> <em>msl-filename</em></td>
450
+ <td>Specify the .msl filename (required for
451
+ run_msl)</td>
452
+ </tr>
453
+ <tr>
454
+ <td>-t</td>
455
+ <td><strong>--test</strong></td>
456
+ <td>Run a verification check only.</td>
457
+ </tr>
458
+ <tr>
459
+ <td>-v</td>
460
+ <td><strong>--verbose</strong></td>
461
+ <td>Set
462
+ the Logger::DEBUG level.</td>
463
+ </tr>
464
+ </table>
465
+ <p><a href="#top">back to top &uarr;</a></p>
466
+ <h2><a name="cmd_runscale" id="cmd_runscale"></a>cmd_runscale</h2>
467
+ <p>Use to run Scale tests by specifying a Scenario .msl file or a directory of .msl files. Supports command-line options for setting test parameters (such as concurrency and pattern) and for configuring the Test Bed with Mu interfaces and/or network hosts. </p>
468
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
469
+ <tr>
470
+ <th>Command</th>
471
+ <th>Commands &amp; Examples</th>
472
+ </tr>
473
+ <tr>
474
+ <td><em>help</em></td>
475
+ <td><p>Gets help for all cmd_runscale commands: <strong>help</strong></p>
476
+ <h6 class="code">mu cmd_runscale:help</h6></td>
477
+ </tr>
478
+ <tr>
479
+ <td><h5>run_file</h5></td>
480
+ <td><p>Runs the specified .msl file: <strong>run_file -s</strong> <em>msl-filename</em><strong>&nbsp; -i </strong><em>interfaces/hosts</em> <strong>-p</strong> <em>pattern</em></p>
481
+ <h6 class="code">mu cmd_runscale:run_file -s msl_file -i a1,dell-9 -p 1-10000:30</h6></td>
482
+ </tr>
483
+ <tr>
484
+ <td><em>run_dir</em></td>
485
+ <td><p>Runs all .msl files in the specified directory: <strong>run_dir -d </strong><em>msl_directory</em></p>
486
+ <h6 class="code">mu cmd_runscale:run_dir -d msl_file_directory</h6>
487
+ <p></p></td>
488
+ </tr>
489
+ <tr>
490
+ <td><em>running?</em></td>
491
+ <td><p>Gets status of the scale player: <strong>running?</strong></p>
492
+ <h6><span class="code">mu cmd_runscale:running?</span></h6></td>
493
+ </tr>
494
+ </table>
495
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
496
+ <tr>
497
+ <th colspan="2">Options (short &amp; long form)</th>
498
+ <th width="60%">Description</th>
499
+ </tr>
500
+ <tr>
501
+ <td width="4%">-c</td>
502
+ <td width="36%"><strong>--csv</strong> <em>csv-filename</em></td>
503
+ <td>Specify the filename of the .csv file that contains the test cases to run.</td>
504
+ </tr>
505
+ <tr>
506
+ <td>-d</td>
507
+ <td><strong>--dir</strong> <em>directory</em></td>
508
+ <td>Specify the directory that contains .msl files to run(required for run_dir).</td>
509
+ </tr>
510
+ <tr>
511
+ <td>-f</td>
512
+ <td><strong>--default_host</strong> <em>default-host</em></td>
513
+ <td>Specify the default host. This host is used for all hosts in the scenario which have not been explicitly assigned</td>
514
+ </tr>
515
+ <tr>
516
+ <td>-h</td>
517
+ <td><strong>--help</strong></td>
518
+ <td>Get help on command line options.</td>
519
+ </tr>
520
+ <tr>
521
+ <td>-i</td>
522
+ <td><strong>--interfaces</strong> <em>interfaces</em></td>
523
+ <td>Specify Mu interfaces as a comma-separated list. Example: <span class="code">b1, b2</span>. When using an IP range, specify range and offset. Example: <span class="code">b1-1000:0,b2</span></td>
524
+ </tr>
525
+ <tr>
526
+ <td>-l</td>
527
+ <td><strong>--delay</strong> <em>delay_value</em></td>
528
+ <td>Intra-scenario delay value, in milliseconds. Default is 0.</td>
529
+ </tr>
530
+ <tr>
531
+ <td>-m</td>
532
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
533
+ <td>Specify the user, password, and mgmt IP of the Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
534
+ </tr>
535
+ <tr>
536
+ <td>-n</td>
537
+ <td><strong>--no_verify</strong> </td>
538
+ <td>Option to not call verify before start.</td>
539
+ </tr>
540
+ <tr>
541
+ <td>-o</td>
542
+ <td><strong>--output</strong> <em>filename</em></td>
543
+ <td>Specify the filename to which you want to output logs.</td>
544
+ </tr>
545
+ <tr>
546
+ <td>-p</td>
547
+ <td><strong>--pattern</strong> <em>con-start</em>:<em>dur</em>,<em>con-end</em>:<em>dur</em></td>
548
+ <td>Specify pattern as concurrency_start:duration,concurrency-end:duration. Duration is in seconds. Example:
549
+ <span class="code">1-10000:60,10000-1:30</span>. </td>
550
+ </tr>
551
+ <tr>
552
+ <td>-r</td>
553
+ <td><strong>--recursive</strong> </td>
554
+ <td>for run_dir command, recurse through the specified directory </td>
555
+ </tr>
556
+ <tr>
557
+ <td>-s</td>
558
+ <td><strong>--scenario</strong> <em>msl-filename</em></td>
559
+ <td>Specify the .msl filename (required for
560
+ run_msl)</td>
561
+ </tr>
562
+ <tr>
563
+ <td>-t</td>
564
+ <td><strong>--test</strong></td>
565
+ <td>Run a verification check only.</td>
566
+ </tr>
567
+ <tr>
568
+ <td>-v</td>
569
+ <td><strong>--verbose</strong></td>
570
+ <td>Set
571
+ the Logger::DEBUG level.</td>
572
+ </tr>
573
+ </table>
574
+ <p><a href="#top">back to top &uarr;</a></p>
575
+ <h2><a name="cmd_runverify" id="cmd_runscale2"></a>cmd_runverify</h2>
576
+ <p>Use to load a Scenario and Test Set template (.xml files) and run a Test Set in Studio Verify. Supports command-line options for setting option values and for configuring the Test Bed with Mu interfaces and/or network hosts.</p>
577
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
578
+ <tr>
579
+ <th>Command</th>
580
+ <th>Commands &amp; Examples</th>
581
+ </tr>
582
+ <tr>
583
+ <td><em>help</em></td>
584
+ <td><p>Gets help for all cmd_runverify commands: <strong>help</strong></p>
585
+ <h6 class="code">mu cmd_runverify:help</h6></td>
586
+ </tr>
587
+ <tr>
588
+ <td><h5>run</h5></td>
589
+ <td><p>Runs the specified Test Set template for the specified Scenario: <strong>run -s</strong> <em>scenario.xml</em><strong> -t </strong><em>test-set.xml</em> <strong>-i</strong><em> interfaces/hosts</em></p>
590
+ <h6 class="code">mu cmd_runverify:run -s my_scenario -t my_testset -i a1,my-server</h6></td>
591
+ </tr>
592
+ </table>
593
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
594
+ <tr>
595
+ <th colspan="2">Options (short &amp; long form)</th>
596
+ <th width="60%">Description</th>
597
+ </tr>
598
+ <tr>
599
+ <td width="4%">-c</td>
600
+ <td width="36%"><strong>--channels</strong> <em>hosts</em></td>
601
+ <td>Specify channel hosts as a comma-separated list. </td>
602
+ </tr>
603
+ <tr>
604
+ <td>-d</td>
605
+ <td><strong>--dir</strong> <em>directory</em></td>
606
+ <td>Specify the directory with Scenario templates to run.</td>
607
+ </tr>
608
+ <tr>
609
+ <td>-h</td>
610
+ <td><strong>--help</strong></td>
611
+ <td>Get help on command line options.</td>
612
+ </tr>
613
+ <tr>
614
+ <td>-i</td>
615
+ <td><strong>--interfaces</strong> <em>interfaces</em></td>
616
+ <td>Specify Mu interfaces and network hosts as a comma-separated list. Example: <span class="code">b1, b2</span>. When using an IP range, specify range/offset. Example: <span class="code">b1-1000:0,web-server</span></td>
617
+ </tr>
618
+ <tr>
619
+ <td>-m</td>
620
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
621
+ <td>Specify the user, password, and mgmt IP of the Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
622
+ </tr>
623
+ <tr>
624
+ <td>-o</td>
625
+ <td><strong>--output</strong> <em>filename</em></td>
626
+ <td>Specify the filename to which you want to output logs.</td>
627
+ </tr>
628
+ <tr>
629
+ <td>-p</td>
630
+ <td><strong>--options</strong><em> option:value</em></td>
631
+ <td>Specify option/value pairs as a comma-separated list. Example: <span class="code">user:jane,email:jsmith@itemp.com</span></td>
632
+ </tr>
633
+ <tr>
634
+ <td>-s</td>
635
+ <td><strong>--scenario</strong> <em>scenario-template</em></td>
636
+ <td>Specify the Scenario template to run (must be xml).</td>
637
+ </tr>
638
+ <tr>
639
+ <td>-t</td>
640
+ <td><strong>--testset </strong><em>testset-template</em></td>
641
+ <td>Specify the Test Set template to run (must be xml).</td>
642
+ </tr>
643
+ <tr>
644
+ <td>-v</td>
645
+ <td><strong>--verbose</strong></td>
646
+ <td>Set
647
+ the Logger::DEBUG level.</td>
648
+ </tr>
649
+ </table>
650
+ <p><a href="#top">back to top &uarr;</a></p>
651
+ <h2><a name="cmd_runscenario" id="cmd_runscale3"></a>cmd_runscenario</h2>
652
+ <p>Use to load and verify a Scenario template (.xml file). Supports command-line options for configuring the Test Bed with Mu interfaces and/or network hosts.</p>
653
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
654
+ <tr>
655
+ <th>Command</th>
656
+ <th>Commands &amp; Examples</th>
657
+ </tr>
658
+ <tr>
659
+ <td><em>help</em></td>
660
+ <td><p>Gets help for all cmd_runscenario commands: <strong>help</strong></p>
661
+ <h6 class="code">mu cmd_runscenario:help</h6></td>
662
+ </tr>
663
+ <tr>
664
+ <td><h5>run</h5></td>
665
+ <td><p>Runs the specified Scenario template: <strong>run -s</strong> <em>scenario.xml</em><strong> -i</strong><em> interfaces/hosts</em></p>
666
+ <h6 class="code">mu cmd_runscenario:run -s my_scenario -i a1,my-server</h6></td>
667
+ </tr>
668
+ </table>
669
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
670
+ <tr>
671
+ <th colspan="2">Options (short &amp; long form)</th>
672
+ <th width="60%">Description</th>
673
+ </tr>
674
+ <tr>
675
+ <td width="4%">-c</td>
676
+ <td width="36%"><strong>--channels</strong> <em>hosts</em></td>
677
+ <td>Specify channel hosts as a comma-separated list. </td>
678
+ </tr>
679
+ <tr>
680
+ <td>-d</td>
681
+ <td><strong>--dir</strong> <em>directory</em></td>
682
+ <td>Specify the directory with Scenario templates to run.</td>
683
+ </tr>
684
+ <tr>
685
+ <td>-h</td>
686
+ <td><strong>--help</strong></td>
687
+ <td>Get help on command line options.</td>
688
+ </tr>
689
+ <tr>
690
+ <td>-i</td>
691
+ <td><strong>--interfaces</strong> <em>interfaces</em></td>
692
+ <td>Specify Mu interfaces and network hosts as a comma-separated list. Example: <span class="code">b1, b2</span>. When using an IP range, specify range/offset. Example: <span class="code">b1-1000:0,web-server</span></td>
693
+ </tr>
694
+ <tr>
695
+ <td>-m</td>
696
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
697
+ <td>Specify the user, password, and mgmt IP of the Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
698
+ </tr>
699
+ <tr>
700
+ <td>-o</td>
701
+ <td><strong>--output</strong> <em>filename</em></td>
702
+ <td>Specify the filename to which you want to output logs.</td>
703
+ </tr>
704
+ <tr>
705
+ <td>-s</td>
706
+ <td><strong>--scenario</strong> <em>scenario-template</em></td>
707
+ <td>Specify the Scenario template to run (must be xml).</td>
708
+ </tr>
709
+ <tr>
710
+ <td>-v</td>
711
+ <td><strong>--verbose</strong></td>
712
+ <td>Set
713
+ the Logger::DEBUG level.</td>
714
+ </tr>
715
+ </table>
716
+ <p><a href="#top">back to top &uarr;</a></p>
717
+ <p>&nbsp;</p>
718
+ <h3><a name="api-methods" id="features"></a>API Methods</h3>
719
+ <p>These commands provide access to legacy REST API commands supported by the Mu system. </p>
720
+ <ul>
721
+ <li><a href="#cmd_muapi">cmd_muapi</a></li>
722
+ <li><a href="#cmd_netconfig">cmd_netconfig</a></li>
723
+ <li><a href="#cmd_ddt">cmd_ddt</a></li>
724
+ <li><a href="#cmd_scale">cmd_scale</a></li>
725
+ <li><a href="#cmd_homepage">cmd_homepage</a></li>
726
+ <li><a href="#cmd_system">cmd_system</a></li>
727
+ <li><a href="#cmd_cli">cmd_cli</a> </li>
728
+ </ul>
729
+ <h2><a name="cmd_muapi" id="cmd_runscale5"></a>cmd_muapi</h2>
730
+ <p>Use to access the legacy REST API for Test Runs (Protocol Mutation, Scenario Mutation, DoS, and PV tests). </p>
731
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
732
+ <tr>
733
+ <th>Command</th>
734
+ <th>Description &amp; Examples</th>
735
+ </tr>
736
+ <tr>
737
+ <td><em>help</em></td>
738
+ <td>Gets help for all cmd_muapi commands: <strong>help</strong>
739
+ <h6 class="code">mu cmd_muapi:help</h6></td>
740
+ </tr>
741
+ <tr>
742
+ <td><em>archive</em></td>
743
+ <td>Manage archives (reports) for Test Runs. The status and get commands require the job_id returned by the run command. <strong>archive</strong> <strong>-c</strong><em> command </em><strong>-u</strong><em> uuid/job-id</em><br>
744
+ <br>
745
+ <h6 class="code">mu cmd_muapi:archive -c run -u 52add3cf-9040-42ce-b263-8233039931d5</h6>
746
+ <p>Get the status of the archive report:</p>
747
+ <h6><span class="code">mu cmd_muapi:archive -c status -u 1296064526931</span></h6>
748
+ <p>Download the archive report:
749
+ </p>
750
+ <h6><span class="code">mu cmd_muapi:archive -c get -u 1296064526931</span></h6></td>
751
+ </tr>
752
+ <tr>
753
+ <td><em>backup</em></td>
754
+ <td>Manage system backup files. <strong>backup</strong> <strong>-c</strong><em> command</em>
755
+ <p>Generate system backup:</p>
756
+ <h6 class="code">mu cmd_muapi:backup -c run</h6>
757
+ <p>Get the status of the backup job:</p>
758
+ <h6><span class="code">mu cmd_muapi:backup -c status</span></h6>
759
+ <p>Download the backup file (requires a name): <strong>backup</strong> <strong>-c</strong> <strong>get -n</strong><em> filename</em></p>
760
+ <h6><span class="code">mu cmd_muapi:backup -c get -n my-backup</span></h6>
761
+ <p>The Mu system automatically appends the .dat extension to all backup files.</p></td>
762
+ </tr>
763
+ <tr>
764
+ <td><em>capture</em></td>
765
+ <td>Manage pcaps recorded by the Mu system. The <strong>status</strong> and <strong>get</strong> commands require the job-id returned by the run command: <strong>capture</strong> <strong>-c</strong><em> command </em><strong>-p</strong><em> port-number</em><strong> -u</strong><em> job-id</em>
766
+ <p>Start recording packets (this command returns the job-id):</p>
767
+ <h6 class="code">mu cmd_muapi:capture -c run -p a1</h6>
768
+ <p>Get the status of the packet recording job:</p>
769
+ <h6><span class="code">mu cmd_muapi:capture -c status -p a1 -u 1296064526931</span></h6>
770
+ <p>Download the recorded packet capture: </p>
771
+ <h6><span class="code">mu cmd_muapi:capture -c get -p a1 -u 1296064526931</span></h6></td>
772
+ </tr>
773
+ <tr>
774
+ <td><em>delete</em></td>
775
+ <td>Delete the specified Test Run or template: <strong>delete -u</strong> <em>uuid</em>
776
+ <h6 class="code">mu cmd_muapi:delete -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
777
+ </tr>
778
+ <tr>
779
+ <td><em>export_by_name</em></td>
780
+ <td>Export the specified template: <strong>export_by_name -n</strong> <em>name</em>
781
+ <strong>-t</strong> <em>type</em>
782
+ <h6 class="code">mu cmd_muapi:export_by_name -n my_monitor -t monitor</h6></td>
783
+ </tr>
784
+ <tr>
785
+ <td><em>get_faults</em></td>
786
+ <td>Get a list of faults (xml format) from a Test Run: <strong>get_faults -u</strong> <em>uuid</em> <strong>-v</strong>
787
+ <h6 class="code">mu cmd_muapi:get_faults -u 52add3cf-9040-42ce-b263-8233039931d5 -v</h6></td>
788
+ </tr>
789
+ <tr>
790
+ <td><em>get_name</em></td>
791
+ <td>Get details for the specified Test Run or template: <strong>get_name -u</strong> <em>uuid</em>
792
+ <h6><span class="code">mu cmd_muapi:get_name -u 52add3cf-9040-42ce-b263-8233039931d5</span></h6></td>
793
+ </tr>
794
+ <tr>
795
+ <td><em>list</em></td>
796
+ <td>&nbsp;Get a list of templates by type: <strong>list -t</strong> <em>template-type</em> <h6 class="code">mu cmd_muapi:list -t monitor</h6></td>
797
+ </tr>
798
+ <tr>
799
+ <td><em>list_by_status</em></td>
800
+ <td>Get a list of Test Runs by status: <strong>list_by_status -s</strong><em> status</em>
801
+ <h6 class="code">mu cmd_muapi:list_by_status -s finished</h6></td>
802
+ </tr>
803
+ <tr>
804
+ <td><em>pause</em></td>
805
+ <td>Pause a Test Run: <strong>pause -u</strong> <em>uuid</em>
806
+ <h6 class="code">mu cmd_muapi:pause -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
807
+ </tr>
808
+ <tr>
809
+ <td><em>resume</em></td>
810
+ <td>Resume a Test Run: <strong>resume -u</strong> <em>uuid</em>
811
+ <h6 class="code">mu cmd_muapi:pause -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
812
+ </tr>
813
+ <tr>
814
+ <td><em>run</em></td>
815
+ <td>Start a Test Run (to rename, use the -b argument): <strong>run -u</strong> <em>uuid</em> [<strong>-b</strong> <em>new-name</em>]
816
+ <h6 class="code">mu cmd_muapi:run -u 52add3cf-9040-42ce-b263-8233039931d5 -b true</h6></td>
817
+ </tr>
818
+ <tr>
819
+ <td><em>status</em></td>
820
+ <td>Get the status of a Test Run: <strong>status -u</strong> <em>uuid</em>
821
+ <h6 class="code">mu cmd_muapi:status -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
822
+ </tr>
823
+ <tr>
824
+ <td><em>stop</em></td>
825
+ <td>Stop a Test Run: <strong>stop -u</strong> <em>uuid</em>
826
+ <h6 class="code">mu cmd_muapi:stop -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
827
+ </tr>
828
+ <tr>
829
+ <td><em>types</em></td>
830
+ <td>Get a list of all template types: <strong>types</strong><em></em>
831
+ <h6 class="code">mu cmd_muapi:types</h6></td>
832
+ </tr>
833
+ </table>
834
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
835
+ <tr>
836
+ <th colspan="2">Options (short &amp; long form)</th>
837
+ <th width="60%">Description</th>
838
+ </tr>
839
+ <tr>
840
+ <td width="4%">-b</td>
841
+ <td width="36%"><strong>--boolean</strong> <em>value</em></td>
842
+ <td>Specify a boolean value (<span class="code">true</span> or <span class="code">false</span>). </td>
843
+ </tr>
844
+ <tr>
845
+ <td>-c</td>
846
+ <td><strong>--command</strong><em> command</em></td>
847
+ <td>Specify the command to run (run, get, status, etc.)</td>
848
+ </tr>
849
+ <tr>
850
+ <td>-m</td>
851
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
852
+ <td>Specify the user, password, and mgmt IP of the Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
853
+ </tr>
854
+ <tr>
855
+ <td>-n</td>
856
+ <td><strong>--name</strong> <em>name</em></td>
857
+ <td>Specify a Test Run or template name.</td>
858
+ </tr>
859
+ <tr>
860
+ <td>-o</td>
861
+ <td><strong>--output</strong> <em>filename</em></td>
862
+ <td>Specify the filename to which you want to output logs.</td>
863
+ </tr>
864
+ <tr>
865
+ <td>-p</td>
866
+ <td><strong>--port</strong> <em>port-number</em></td>
867
+ <td>Specify the port number.</td>
868
+ </tr>
869
+ <tr>
870
+ <td>-s</td>
871
+ <td><strong>--status</strong> <em>status</em></td>
872
+ <td>Specify the status filter (<span class="code">running</span>, <span class="code">finished</span>, <span class="code">aborted</span> <span class="code">queued</span>, or <span class="code">failed</span>)</td>
873
+ </tr>
874
+ <tr>
875
+ <td>-t</td>
876
+ <td><strong>--type</strong><em> template-type</em></td>
877
+ <td>Specify the type of template.</td>
878
+ </tr>
879
+ <tr>
880
+ <td>-u</td>
881
+ <td><strong>--uuid</strong><em> uuid/job-id</em></td>
882
+ <td>Specify the UUID of the template to run. For archive, backup, and capture commands, this option takes a job-id value.</td>
883
+ </tr>
884
+ <tr>
885
+ <td>-v</td>
886
+ <td><strong>--verbose</strong></td>
887
+ <td>Set
888
+ the Logger::DEBUG level.</td>
889
+ </tr>
890
+ </table>
891
+ <p><a href="#top">back to top &uarr;</a></p>
892
+ <h2><a name="cmd_netconfig" id="cmd_runscale6"></a>cmd_netconfig</h2>
893
+ <p>Use to access the legacy REST API for configuring Mu interfaces, network hosts, and routes.</p>
894
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
895
+ <tr>
896
+ <th>Command</th>
897
+ <th>Description &amp; Examples</th>
898
+ </tr>
899
+ <tr>
900
+ <td><em>help</em></td>
901
+ <td>Gets help for all cmd_netconfig commands: <strong>help</strong>
902
+ <h6 class="code">mu cmd_netconfig:help</h6></td>
903
+ </tr>
904
+ <tr>
905
+ <td><em>clear_hosts</em></td>
906
+ <td><p>Remove all network hosts configured in the Mu system: <strong>clear_hosts</strong></p>
907
+ <h6><span class="code">mu cmd_netconfig:clear_hosts</span></h6></td>
908
+ </tr>
909
+ <tr>
910
+ <td><em>clear_interfaces</em></td>
911
+ <td><p>Clear settings for specified Mu interfaces: <strong>clear_interfaces -i</strong> <em>interfaces</em></p>
912
+ <h6><span class="code">mu cmd_netconfig:clear_interfaces -i b1,b2</span></h6></td>
913
+ </tr>
914
+ <tr>
915
+ <td><em>clear_routes</em></td>
916
+ <td><p>Remove all user-configured routes in the Mu system: <strong>clear_routes</strong></p>
917
+ <h6><span class="code">mu cmd_netconfig:clear_routes</span></h6></td>
918
+ </tr>
919
+ <tr>
920
+ <td><em>clear_vlans</em></td>
921
+ <td><p>Remove all vlans for all Mu interfaces: <strong>clear_vlans</strong></p>
922
+ <h6><span class="code">mu cmd_netconfig:clear_vlans</span></h6></td>
923
+ </tr>
924
+ <tr>
925
+ <td><em>create</em></td>
926
+ <td><p>Create a network object such as a host or route: <strong>create -j </strong><em>object</em><strong> -e </strong><em>value</em> </p>
927
+ <h6><span class="code">mu cmd_netconfig:create -j {&quot;default&quot;: false,&quot;direct&quot;: false,&quot;dst&quot;: &quot;10.0.0.0&quot;,&quot;dst_pfx_len&quot;: 8,&quot;gateway&quot;: &quot;192.168.100.1&quot;,&quot;interface&quot;: &quot;a1&quot;,&quot;interface_display_name&quot;: &quot;A1&quot;,&quot;metric&quot;: 1,&quot;readonly&quot;: false} -e route</span></h6></td>
928
+ </tr>
929
+ <tr>
930
+ <td><em>delete</em></td>
931
+ <td><p>Delete a network object such as host or route: <strong>delete </strong><strong>-e </strong><em>value</em> </p>
932
+ <h6><span class="code">mu cmd_netconfig:delete -e Web-Server</span></h6></td>
933
+ </tr>
934
+ <tr>
935
+ <td><em>get</em></td>
936
+ <td><p>Get details for a network object: <strong>get </strong><strong>-e </strong><em>value</em></p>
937
+ <h6><span class="code">mu cmd_netconfig:get -e a1</span></h6></td>
938
+ </tr>
939
+ <tr>
940
+ <td><em>modify</em></td>
941
+ <td><p>Modify a network object such as a host or route:<strong>modify -j </strong><em>object </em><strong>-e </strong><em>value</em></p>
942
+ <h6><span class="code">mu cmd_netconfig:modify -j {&quot;mac&quot;: &quot;&quot;,&quot;name&quot;: &quot;Web-Server&quot;,&quot;notes&quot;: &quot;&quot;,&quot;v4_addr&quot;: &quot;192.168.112.205&quot;,&quot;v6_global_addr&quot;: &quot;&quot;,&quot;v6_local_addr&quot;: &quot;&quot;} -e host</span></h6></td>
943
+ </tr>
944
+ <tr>
945
+ <td><em>resolve_hosts</em></td>
946
+ <td><p>Get IP address for specified network host: <strong>resolve_hosts </strong><em>host</em></p>
947
+ <h6><span class="code">mu cmd_netconfig:resolve_hosts Web-Server</span></h6></td>
948
+ </tr>
949
+ <tr>
950
+ <td><em>restore</em></td>
951
+ <td><p>Restore from specified file (to overwrite existing object, use the -b argument): <strong>restore -f </strong><em>filepath </em>[<strong>-b</strong> <em>clear-existing</em>]</p>
952
+ <h6><span class="code">mu cmd_netconfig:restore -f my_muhosts/web-server.json true</span></h6></td>
953
+ </tr>
954
+ <tr>
955
+ <td><em>save</em></td>
956
+ <td><p>Save changes to the Mu system: <strong>save</strong></p>
957
+ <h6><span class="code">mu cmd_netconfig:save</span></h6></td>
958
+ </tr>
959
+ </table>
960
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
961
+ <tr>
962
+ <th colspan="2">Options (short &amp; long form)</th>
963
+ <th width="60%">Description</th>
964
+ </tr>
965
+ <tr>
966
+ <td width="4%">-b</td>
967
+ <td width="36%"><strong>--boolean</strong> <em>value</em></td>
968
+ <td>Specify a boolean value (true or false). </td>
969
+ </tr>
970
+ <tr>
971
+ <td>-e</td>
972
+ <td><strong>--element</strong><em> value</em></td>
973
+ <td>Specify a value for the associated command. Example: <span class="code">interfaces</span> or <span class="code">interfaces/a1</span></td>
974
+ </tr>
975
+ <tr>
976
+ <td>-f</td>
977
+ <td><strong>--filepath</strong><em> filepath</em></td>
978
+ <td>Specify the path to a file. </td>
979
+ </tr>
980
+ <tr>
981
+ <td>-h</td>
982
+ <td><strong>--help</strong></td>
983
+ <td>Get help on command line options.</td>
984
+ </tr>
985
+ <tr>
986
+ <td>-i</td>
987
+ <td><strong>--interfaces</strong> <em>interface-or-host</em></td>
988
+ <td>Specify Mu interfaces or network hosts as a comma-separated list. Example: <span class="code">b1, web-server</span>. </td>
989
+ </tr>
990
+ <tr>
991
+ <td>-j</td>
992
+ <td><strong>--json</strong> <em>object</em></td>
993
+ <td>Specify a json object as a text string.</td>
994
+ </tr>
995
+ <tr>
996
+ <td>-m</td>
997
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
998
+ <td>Specify a user, password, and mgmt IP of a Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
999
+ </tr>
1000
+ <tr>
1001
+ <td>-o</td>
1002
+ <td><strong>--output</strong> <em>filename</em></td>
1003
+ <td>Specify the filename to which you want to output logs.</td>
1004
+ </tr>
1005
+ <tr>
1006
+ <td>-v</td>
1007
+ <td><strong>--verbose</strong></td>
1008
+ <td>Set
1009
+ the Logger::DEBUG level.</td>
1010
+ </tr>
1011
+ </table>
1012
+ <p><a href="#top">back to top &uarr;</a></p>
1013
+ <h2><a name="cmd_ddt" id="cmd_runscale7"></a>cmd_ddt</h2>
1014
+ <p>Use to access the legacy REST API for Test Sets (Studio Verify).</p>
1015
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1016
+ <tr>
1017
+ <th>Command</th>
1018
+ <th>Description &amp; Examples</th>
1019
+ </tr>
1020
+ <tr>
1021
+ <td><em>display_results</em></td>
1022
+ <td>Displays results for the current Test Set:
1023
+ <strong>display_results</strong> <h6 class="code">mu cmd_ddt:display_results</h6></td>
1024
+ </tr>
1025
+ <tr>
1026
+ <td><em>new_session</em></td>
1027
+ <td>Create a new session: <strong>new_session</strong>
1028
+ <h6 class="code">mu cmd_ddt:new_session</h6></td>
1029
+ </tr>
1030
+ <tr>
1031
+ <td><em>load_scenario</em></td>
1032
+ <td>Load the specified Scenario template:
1033
+ <strong>load_scenario -u </strong><em>uuid</em> <h6 class="code">mu cmd_ddt:load_scenario -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
1034
+ </tr>
1035
+ <tr>
1036
+ <td><em>get_hosts</em></td>
1037
+ <td>Get a list of hosts in the Test Bed:
1038
+ <strong>get_hosts</strong> <h6 class="code">mu cmd_ddt:get_hosts</h6></td>
1039
+ </tr>
1040
+ <tr>
1041
+ <td><em>set_hosts</em></td>
1042
+ <td>Configure the hosts in the Test Bed: <strong>set_hosts</strong>
1043
+ <strong>-r</strong> <em>role</em> <strong>-n</strong> <em>name</em> <strong>-y</strong> <em>type</em> <h6 class="code">mu cmd_ddt:set_hosts -r HTTP_Client,HTTP_Server -n a1,Web-Server -y v4</h6></td>
1044
+ </tr>
1045
+ <tr>
1046
+ <td><em>get_channels</em></td>
1047
+ <td>Get a list of channels in the Test Bed: <strong>get_channels</strong>
1048
+ <h6 class="code">mu cmd_ddt:get_channels</h6></td>
1049
+ </tr>
1050
+ <tr>
1051
+ <td><em>set_channels</em></td>
1052
+ <td>Configure the channels in the Test Bed: <strong>set_channels</strong> <strong>-r</strong> <em>role</em> <strong>-n</strong> <em>name</em>
1053
+ <h6 class="code">mu cmd_ddt:set_channels -r SSH_Channel -n Web-Server</h6></td>
1054
+ </tr>
1055
+ <tr>
1056
+ <td><em>get_options</em></td>
1057
+ <td>Get a list of options in the Test Set: <strong>get_options</strong>
1058
+ <h6 class="code">mu cmd_ddt:get_options</h6></td>
1059
+ </tr>
1060
+ <tr>
1061
+ <td><em>set_options</em></td>
1062
+ <td>Configure the option values for the Test Set: <strong>set_options</strong> <strong>-n</strong> <em>name</em> <strong>-p</strong> <em>value</em>
1063
+ <h6 class="code">mu cmd_ddt:set_options -n username -p jsmith</h6></td>
1064
+ </tr>
1065
+ <tr>
1066
+ <td><em>get_sessions</em></td>
1067
+ <td>Get a list of all sessions: <strong>get_sessions</strong>
1068
+ <h6 class="code">mu cmd_ddt:get_sessions</h6></td>
1069
+ </tr>
1070
+ <tr>
1071
+ <td><em>setup_test</em></td>
1072
+ <td>Setup the Test Bed, reserving the Mu interfaces:
1073
+ <strong>setup_test</strong> <h6 class="code">mu cmd_ddt:setup_test</h6></td>
1074
+ </tr>
1075
+ <tr>
1076
+ <td><em>run</em></td>
1077
+ <td>Run a Test Set: <strong>run</strong>
1078
+ <h6 class="code">mu cmd_ddt:run</h6></td>
1079
+ </tr>
1080
+ <tr>
1081
+ <td><em>run_testset</em></td>
1082
+ <td>Run the specified Test Set: <strong>run_testset -u</strong> <em>uuid</em> <h6 class="code">mu cmd_ddt:run_testset -u 04aa248a-0b9b-4bf6-97e1-aab691d0acf1</h6></td>
1083
+ </tr>
1084
+ <tr>
1085
+ <td><em>get_testset_results</em></td>
1086
+ <td>Get results for the current Test Set: <strong>get_testset_results</strong>
1087
+ <h6 class="code">mu cmd_ddt:get_testset_results</h6></td>
1088
+ </tr>
1089
+ <tr>
1090
+ <td><em>get_testset_status</em></td>
1091
+ <td>Get status for the current Test Set: <strong>get_testset_status</strong>
1092
+ <h6 class="code">mu cmd_ddt:get_testset_status</h6></td>
1093
+ </tr>
1094
+ <tr>
1095
+ <td><em>teardown_test</em></td>
1096
+ <td>Unsets the Test Bed selections, releasing the Mu interfaces: <strong>teardown_test</strong>
1097
+ <h6 class="code">mu cmd_ddt:teardown_test</h6></td>
1098
+ </tr>
1099
+ <tr>
1100
+ <td><em>close_session</em></td>
1101
+ <td>Closes the current session: <strong>close_session</strong>
1102
+ <h6 class="code">mu cmd_ddt:close_session</h6></td>
1103
+ </tr>
1104
+ <tr>
1105
+ <td><em>close_all_sessions</em></td>
1106
+ <td>Closes all existing sessions: <strong>close_all_sessions</strong>
1107
+ <h6 class="code">mu cmd_ddt:close_all_sessions</h6></td>
1108
+ </tr>
1109
+ tr>
1110
+ <td><em>csv_export</em></td>
1111
+ <td>Exports a Test Set from the Mu system to a. csv file: <strong>csv_export</strong>
1112
+ <strong>-u</strong> <em>uuid</em> <h6 class="code">mu cmd_ddt:csv_export -u 52add3cf-9040-42ce-b263-8233039931d5</h6></td>
1113
+ </tr>
1114
+ tr>
1115
+ <td><em>csv_import</em></td>
1116
+ <td>Imports a .csv file to create a Test Set on the Mu system: <strong>csv_import</strong>
1117
+ <strong>-t</strong><em> filename.csv</em>
1118
+ <h6 class="code">mu cmd_ddt:csv_import -t my-testset.csv</h6></td>
1119
+ </tr>
1120
+ </table>
1121
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1122
+ <tr>
1123
+ <th colspan="2">Options (short &amp; long form)</th>
1124
+ <th width="60%">Description</th>
1125
+ </tr>
1126
+ <tr>
1127
+ <td width="4%">-f</td>
1128
+ <td width="36%"><strong>--filename</strong><em> filename</em></td>
1129
+ <td>Specify the template name for saving an imported Test Set.</td>
1130
+ </tr>
1131
+ <tr>
1132
+ <td>-h</td>
1133
+ <td><strong>--help</strong></td>
1134
+ <td>Get help on command line options.</td>
1135
+ </tr>
1136
+ <tr>
1137
+ <td>-m</td>
1138
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
1139
+ <td>Specify a user, password, and mgmt IP of a Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
1140
+ </tr>
1141
+ <tr>
1142
+ <td>-n</td>
1143
+ <td><strong>--names</strong> <em>name-array</em></td>
1144
+ <td>Specify host names or channel names in a comma-separated array. Example: <span class="code">a1,Web-Serve</span>r</td>
1145
+ </tr>
1146
+ <tr>
1147
+ <td>-o</td>
1148
+ <td><strong>--output</strong> <em>filename</em></td>
1149
+ <td>Specify the filename to which you want to output logs.</td>
1150
+ </tr>
1151
+ <tr>
1152
+ <td>-p</td>
1153
+ <td><strong>--option_values</strong> <em>value-array</em></td>
1154
+ <td>Specify values for Test Set options in a comma-separated array. Example: <span class="code">bob,jane,mary,tom</span></td>
1155
+ </tr>
1156
+ <tr>
1157
+ <td>-r</td>
1158
+ <td><strong>--roles</strong> <em>role-array</em></td>
1159
+ <td>Specify host roles in a comma-separated array. Example: <span class="code">HTTP_Client,HTTP_Server</span></td>
1160
+ </tr>
1161
+ <tr>
1162
+ <td>-t</td>
1163
+ <td><strong>--testset</strong> <em>filename.csv</em></td>
1164
+ <td>Specify the name of the .csv file to import. </td>
1165
+ </tr>
1166
+ <tr>
1167
+ <td>-u</td>
1168
+ <td><strong>--uuid</strong> <em>uuid</em></td>
1169
+ <td>Specify the UUID of the Scenario or Test Set.</td>
1170
+ </tr>
1171
+ <tr>
1172
+ <td>-v</td>
1173
+ <td><strong>--verbose</strong></td>
1174
+ <td>Set
1175
+ the Logger::DEBUG level.</td>
1176
+ </tr>
1177
+ <tr>
1178
+ <td>-y</td>
1179
+ <td><strong>--type</strong> <em>type</em></td>
1180
+ <td>Specify network layer (v4, v6, l2) for all hosts in the Test Bed. Example: <span class="code">v4</span></td>
1181
+ </tr>
1182
+ </table>
1183
+ <p><a href="#top">back to top &uarr;</a></p>
1184
+ <h2><a name="cmd_scale" id="cmd_runscale8"></a>cmd_scale</h2>
1185
+ <p>Use to access the legacy REST API for Scale tests (Studio Scale). </p>
1186
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1187
+ <tr>
1188
+ <th>Command</th>
1189
+ <th>Description &amp; Examples</th>
1190
+ </tr>
1191
+ <tr>
1192
+ <td><em>about</em></td>
1193
+ <td>Lists information for the Scale Player and all active and inactive Scale Engines: <strong>about</strong>
1194
+ <h6 class="code">mu cmd_scale:about</h6></td>
1195
+ </tr>
1196
+ <tr>
1197
+ <td><em>configure</em></td>
1198
+ <td>Configure any element of the scale json object : <strong>configure -p </strong><em>parameter</em><strong> -pv </strong><em>value
1199
+ </em>
1200
+ <h6 class="code">mu cmd_scale:configure -p json_element -pv json_element_value</h6></td>
1201
+ </tr>
1202
+ <tr>
1203
+ <td><em>data</em></td>
1204
+ <td>Gets chart data for the Scale test: <strong>data -w</strong> <em>view</em> <strong> -z</strong> <em>zoom</em> <strong>-ps</strong> <em>position</em> <strong>-b</strong> <em>bot_id</em> <h6 class="code">mu cmd_scale:data -w TIMELINE -z 1 -ps 0 -b bots_10.10.6.200:1</h6></td>
1205
+ </tr>
1206
+ <tr>
1207
+ <td><em>delete_scale_engine </em></td>
1208
+ <td>Delete the specified Scale Engine:<strong>delete_scale_engine -b</strong> <em>bot_id</em> <h6 class="code">mu cmd_scale:delete_scale_engine -b bots_10.10.6.200:1</h6></td>
1209
+ </tr>
1210
+ <tr>
1211
+ <td><em>help</em></td>
1212
+ <td>Gets help for all cmd_scale commands: <strong>help</strong>
1213
+ <h6 class="code">mu cmd_scale:help</h6></td>
1214
+ </tr>
1215
+ <tr>
1216
+ <td><em>list</em></td>
1217
+ <td>Returns the current Scale Player's UUID: <strong>list</strong>
1218
+ <h6 class="code">mu cmd_scale:list</h6></td>
1219
+ </tr>
1220
+ <tr>
1221
+ <td><em>pattern</em></td>
1222
+ <td>Gets the pattern for the Scale test: <strong>pattern </strong><strong>-z</strong> <em>zoom</em> <strong>-ps</strong> <em>position</em>
1223
+ <h6 class="code">mu cmd_scale:pattern -z 1 -ps 0</h6></td>
1224
+ </tr>
1225
+ <tr>
1226
+ <td><em>pcap</em></td>
1227
+ <td>Gets a pcap from a specific Scale Engine: <strong>pcap </strong> <strong>-b</strong> <em>bot_id</em> <strong>-f</strong> <em>filename</em> <h6 class="code">mu cmd_scale:pcap -b bots_10.10.6.200:1 -f bot_1_pcap</h6></td>
1228
+ </tr>
1229
+ <tr>
1230
+ <td><em>release</em></td>
1231
+ <td>Release the Scale Player:
1232
+ <strong>release</strong> <h6 class="code">mu cmd_scale:release</h6></td>
1233
+ </tr>
1234
+ <tr>
1235
+ <td><em>release_scale_engine </em></td>
1236
+ <td>Releases the specified Scale Engine:<strong>release_scale_engine -b</strong> <em>bot_id</em>
1237
+ <h6 class="code">mu cmd_scale:release_scale_engine -b bots_10.10.6.200:1</h6></td>
1238
+ </tr>
1239
+ <tr>
1240
+ <td><em>reserve_scale_engine </em></td>
1241
+ <td>Reserves the specified Scale Engine:<strong>reserve_scale_engine -b</strong> <em>bot_id</em>
1242
+ <h6 class="code">mu cmd_scale:reserve_scale_engine -b bots_10.10.6.200:1</h6></td>
1243
+ </tr>
1244
+ <tr>
1245
+ <td><em>session</em></td>
1246
+ <td>Create a new Scale Player session:
1247
+ <strong>session</strong> <h6 class="code">mu cmd_scale:session</h6></td>
1248
+ </tr>
1249
+ <tr>
1250
+ <td><em>start</em></td>
1251
+ <td>Start the Scale test: <strong>start</strong>
1252
+ <strong>-c</strong> <em>scale-test</em> <strong>-m</strong> <em>user:pass@mu-ip</em> <h6 class="code">mu cmd_scale:start -c scale.json -m admin:admin@10.10.2.2</h6></td>
1253
+ </tr>
1254
+ <tr>
1255
+ <td><em>status</em></td>
1256
+ <td>Gets information about the currently running Scale test: <strong>status</strong>
1257
+ <h6 class="code">mu cmd_scale:status</h6></td>
1258
+ </tr>
1259
+ <tr>
1260
+ <td><em>statuses</em></td>
1261
+ <td>Gets the status of all active and inactive Scale engines: <strong>statuses</strong>
1262
+ <h6 class="code">mu cmd_scale:statuses</h6></td>
1263
+ </tr>
1264
+ <tr>
1265
+ <td><em>stop</em></td>
1266
+ <td>Stops the Scale test: <strong>stop</strong>
1267
+ <h6 class="code">mu cmd_scale:stop</h6></td>
1268
+ </tr>
1269
+ <tr>
1270
+ <td><em>update</em></td>
1271
+ <td>Update the pattern dynamically (while the Scale test is running):
1272
+ <strong>update -p </strong><em>parameter</em> <strong>-pv</strong> <em>parameter-value</em> <h6 class="code">mu cmd_scale:update -p delay -pv 250 -p volume -pv 100000</h6></td>
1273
+ </tr>
1274
+ <tr>
1275
+ <td><em>verify</em></td>
1276
+ <td>Verifies a Scale test: <strong>verify</strong>
1277
+ <h6 class="code">mu cmd_scale:verify</h6></td>
1278
+ </tr>
1279
+ </table>
1280
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1281
+ <tr>
1282
+ <th colspan="2">Options (short &amp; long form)</th>
1283
+ <th width="57%">Description</th>
1284
+ </tr>
1285
+ <tr>
1286
+ <td>-b</td>
1287
+ <td><strong>--bot-id</strong> <em>scale-engine-id</em></td>
1288
+ <td>Specify a Scale Engine using its bot-id value.</td>
1289
+ </tr>
1290
+ <tr>
1291
+ <td>-c</td>
1292
+ <td><strong>--config-file</strong> <em>json-filename</em></td>
1293
+ <td>Specify a .json file that contains the configuration data.</td>
1294
+ </tr>
1295
+ <tr>
1296
+ <td width="5%">-f</td>
1297
+ <td width="38%"><strong>--filename</strong><em> pcap-filename</em></td>
1298
+ <td>Specify a name for the .pcap file.</td>
1299
+ </tr>
1300
+ <tr>
1301
+ <td>-h</td>
1302
+ <td><strong>--help</strong></td>
1303
+ <td>Get help on command line options.</td>
1304
+ </tr>
1305
+ <tr>
1306
+ <td>-m</td>
1307
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
1308
+ <td>Specify a user, password, and mgmt IP of a Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
1309
+ </tr>
1310
+ <tr>
1311
+ <td>-o</td>
1312
+ <td><strong>--output</strong> <em>filename</em></td>
1313
+ <td>Specify the filename to which you want to output logs.</td>
1314
+ </tr>
1315
+ <tr>
1316
+ <td>-p</td>
1317
+ <td><strong>--params</strong><em> parameters</em></td>
1318
+ <td>Specify parameters for initial configuration or for update. Supports <span class="code">delay</span> and <span class="code">volume</span> parameters.</td>
1319
+ </tr>
1320
+ <tr>
1321
+ <td>-ps</td>
1322
+ <td><strong>--view_position</strong><em> value</em></td>
1323
+ <td>Specify the position in the timeline view for which to return data. At this time, only position <span class="code">0</span> is supported.</td>
1324
+ </tr>
1325
+ <tr>
1326
+ <td>-pv</td>
1327
+ <td><strong>--param_value</strong> <em>value</em></td>
1328
+ <td>Specify a value for a parameter.</td>
1329
+ </tr>
1330
+ <tr>
1331
+ <td>-v</td>
1332
+ <td><strong>--verbose</strong></td>
1333
+ <td>Set
1334
+ the Logger::DEBUG level.</td>
1335
+ </tr>
1336
+ <tr>
1337
+ <td>-w</td>
1338
+ <td><strong>--view</strong> <em>view</em></td>
1339
+ <td>Specify the view (<span class="code">RUNTIME</span> or <span class="code">CALLGRAPH</span>) for which to return data.</td>
1340
+ </tr>
1341
+ <tr>
1342
+ <td>-z</td>
1343
+ <td><strong>--zoom</strong> <em>zoom-level</em></td>
1344
+ <td>Specify the zoom level (<span class="code">0</span>, <span class="code">.5</span>, or <span class="code">1</span>) in the timeline view for which to return data. 1 returns data for 100% of the time range, 0.5 returns data for 50% of the time range, and 0 returns only the last minute of data. </td>
1345
+ </tr>
1346
+ </table>
1347
+ <p><a href="#top">back to top &uarr;</a></p>
1348
+ <h2><a name="cmd_homepage" id="cmd_runscale9"></a>cmd_homepage</h2>
1349
+ <p>Use to access information displayed on the Mu UI homepage, such as recent updates, backup status, or a list of latest test results.</p>
1350
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1351
+ <tr>
1352
+ <th>Command</th>
1353
+ <th>Description &amp; Examples</th>
1354
+ </tr>
1355
+ <tr>
1356
+ <td><em>all</em></td>
1357
+ <td>Gets the complete set of information displayed on the Mu home page: <strong>all</strong>
1358
+ <h6 class="code">mu cmd_homepage:all</h6></td>
1359
+ </tr>
1360
+ <tr>
1361
+ <td><em>help</em></td>
1362
+ <td>Gets help for all cmd_homepage commands:
1363
+ <strong>help</strong> <h6 class="code">mu cmd_homepage:help</h6></td>
1364
+ </tr>
1365
+ <tr>
1366
+ <td><em>latest_test</em></td>
1367
+ <td>Gets an array of the latest test results:
1368
+ <strong>latest_test</strong> <h6 class="code">mu cmd_homepage:latest_test</h6></td>
1369
+ </tr>
1370
+ <tr>
1371
+ <td><em>queue_test</em></td>
1372
+ <td>Gets an array of tests in the Test Queue: <strong>queue_test</strong>
1373
+ <h6 class="code">mu cmd_homepage:queue_test</h6></td>
1374
+ </tr>
1375
+ <tr>
1376
+ <td><em>recent</em></td>
1377
+ <td>Gets the "What's New" section from the Mu homepage:
1378
+ <strong>recent</strong> <h6 class="code">mu cmd_homepage:recent</h6></td>
1379
+ </tr>
1380
+ <tr>
1381
+ <td><em>status</em></td>
1382
+ <td>Gets system status for licenses, backup, and updates: <strong>status</strong>
1383
+ <h6 class="code">mu cmd_homepage:status</h6></td>
1384
+ </tr>
1385
+ </table>
1386
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1387
+ <tr>
1388
+ <th colspan="2">Options (short &amp; long form)</th>
1389
+ <th width="57%">Description</th>
1390
+ </tr>
1391
+ <tr>
1392
+ <td>-h</td>
1393
+ <td><strong>--help</strong></td>
1394
+ <td>Get help on command line options.</td>
1395
+ </tr>
1396
+ <tr>
1397
+ <td>-m</td>
1398
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
1399
+ <td>Specify a user, password, and mgmt IP of a Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
1400
+ </tr>
1401
+ <tr>
1402
+ <td>-o</td>
1403
+ <td><strong>--output</strong> <em>filename</em></td>
1404
+ <td>Specify the filename to which you want to output logs.</td>
1405
+ </tr>
1406
+ <tr>
1407
+ <td>-v</td>
1408
+ <td><strong>--verbose</strong></td>
1409
+ <td>Set
1410
+ the Logger::DEBUG level.</td>
1411
+ </tr>
1412
+ </table>
1413
+ <p><a href="#top">back to top &uarr;</a></p>
1414
+ <h2><a name="cmd_system" id="cmd_runscale10"></a>cmd_system</h2>
1415
+ <p>Use to restart system services or to get status details for the Mu system. </p>
1416
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1417
+ <tr>
1418
+ <th>Command</th>
1419
+ <th>Description &amp; Examples</th>
1420
+ </tr>
1421
+ <tr>
1422
+ <td><em>restart</em></td>
1423
+ <td>Restart Mu system services (this does not reboot the appliance):
1424
+ <strong>restart</strong> <h6 class="code">mu cmd_system:restart</h6></td>
1425
+ </tr>
1426
+ <tr>
1427
+ <td><em>status</em></td>
1428
+ <td>Gets all information from the system status page: <strong>status</strong><em></em>
1429
+ <h6 class="code">mu cmd_system:status</h6></td>
1430
+ </tr>
1431
+ <tr>
1432
+ <td><em>status2</em></td>
1433
+ <td>Gets additional system information such as hard drive status, platform model, serial number: <strong>status2</strong> <h6 class="code">mu cmd_system:status2</h6></td>
1434
+ </tr>
1435
+ </table>
1436
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1437
+ <tr>
1438
+ <th colspan="2">Options (short &amp; long form)</th>
1439
+ <th width="57%">Description</th>
1440
+ </tr>
1441
+ <tr>
1442
+ <td width="5%">-h</td>
1443
+ <td width="38%"><strong>--help</strong></td>
1444
+ <td>Get help on command line options.</td>
1445
+ </tr>
1446
+ <tr>
1447
+ <td>-m</td>
1448
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
1449
+ <td>Specify a user, password, and mgmt IP of a Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
1450
+ </tr>
1451
+ <tr>
1452
+ <td>-o</td>
1453
+ <td><strong>--output</strong> <em>filename</em></td>
1454
+ <td>Specify the filename to which you want to output logs.</td>
1455
+ </tr>
1456
+ <tr>
1457
+ <td>-v</td>
1458
+ <td><strong>--verbose</strong></td>
1459
+ <td>Set
1460
+ the Logger::DEBUG level.</td>
1461
+ </tr>
1462
+ </table>
1463
+ <p><a href="#top">back to top &uarr;</a></p>
1464
+ <h2><a name="cmd_cli" id="cmd_runscale11"></a>cmd_cli</h2>
1465
+ <p>Use to access the Mu CLI. </p>
1466
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1467
+ <tr>
1468
+ <th>Command</th>
1469
+ <th>Description &amp; Examples</th>
1470
+ </tr>
1471
+ <tr>
1472
+ <td><em>cli_help</em></td>
1473
+ <td>Get help for all cmd_cli commands: <strong>cli_help</strong>
1474
+ <h6 class="code">mu cmd_cli:cli_help</h6></td>
1475
+ </tr>
1476
+ <tr>
1477
+ <td><em>cli_history</em></td>
1478
+ <td>Display the command line history for the current session: <strong>cli_help</strong>
1479
+ <h6 class="code">mu cmd_cli:history</h6></td>
1480
+ </tr>
1481
+ <tr>
1482
+ <td><em>ping</em></td>
1483
+ <td>Ping the specified IP address from the Mu system: <strong>ping -a </strong><em>ip-address
1484
+ </em>
1485
+ <h6 class="code">mu cmd_cli:ping -a 10.10.10.1</h6></td>
1486
+ </tr>
1487
+ <tr>
1488
+ <td><em>question</em></td>
1489
+ <td>Show the available CLI commands:
1490
+ <strong>question</strong> <h6 class="code">mu cmd_cli:question</h6></td>
1491
+ </tr>
1492
+ <tr>
1493
+ <td><em>traceroute</em></td>
1494
+ <td>Get the network route to a specified IP address from the Mu system: <strong>traceroute -a </strong><em>ip-address </em>
1495
+ <h6 class="code">mu cmd_cli:traceroute -a 10.10.10.1</h6></td>
1496
+ </tr>
1497
+ </table>
1498
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1499
+ <tr>
1500
+ <th colspan="2">Options (short &amp; long form)</th>
1501
+ <th width="57%">Description</th>
1502
+ </tr>
1503
+ <tr>
1504
+ <td width="5%">-h</td>
1505
+ <td width="38%"><strong>--help</strong></td>
1506
+ <td>Get help on command line options.</td>
1507
+ </tr>
1508
+ <tr>
1509
+ <td>-m</td>
1510
+ <td><strong>--mu_string</strong> <em>user</em>:<em>password</em>@<em>mu-ip</em></td>
1511
+ <td>Specify a user, password, and mgmt IP of a Mu system. Example: <span class="code">admin:admin@10.9.8.7</span></td>
1512
+ </tr>
1513
+ <tr>
1514
+ <td>-o</td>
1515
+ <td><strong>--output</strong> <em>filename</em></td>
1516
+ <td>Specify the filename to which you want to output logs.</td>
1517
+ </tr>
1518
+ <tr>
1519
+ <td>-v</td>
1520
+ <td><strong>--verbose</strong></td>
1521
+ <td>Set
1522
+ the Logger::DEBUG level.</td>
1523
+ </tr>
1524
+ </table>
1525
+ <p><a href="#top">back to top &uarr;</a></p>
1526
+ <p>&nbsp;</p>
1527
+ <h3><a name="library-classes" id="features2"></a>Library Classes</h3>
1528
+ <p>The following API library classes can be &lsquo;required&rsquo; and used within Ruby scripts(
1529
+ like most ruby gems).</p>
1530
+
1531
+ <table border="1" cellpadding="1" cellspacing="1" class=wide>
1532
+ <tr>
1533
+ <th>Command</th>
1534
+ <th>Description &amp; Examples</th>
1535
+ </tr>
1536
+ <tr>
1537
+ <td valign=top><p><a name=muapi>muapi</a></p></td>
1538
+ <td valign=top><p>require 'rubygems'</p>
1539
+ <p>require 'mu'</p>
1540
+ <p>api = Mu::Muapi.new(&ldquo;10.10.2.2&rdquo;, &ldquo;admin&rdquo;, &ldquo;admin&rdquo;)</p>
1541
+ <p>$log.level = Logger::INFO</p>
1542
+ <p>Example: <span class="code">api.list_by_status(&quot;running&quot;)</span></p></td>
1543
+ </tr>
1544
+ <tr>
1545
+ <td valign=top><p><a name=ddt>ddt</a></p></td>
1546
+ <td valign=top><p>require 'rubygems'</p>
1547
+ <p>require 'mu'</p>
1548
+ <p>api = Mu::Ddt.new(&ldquo;10.10.2.2&rdquo;, &ldquo;admin&rdquo;, &ldquo;admin&rdquo;)</p>
1549
+ <p>$log.level = Logger::INFO</p>
1550
+ <p>Example: <span class="code">api.new_session</span></p></td>
1551
+ </tr>
1552
+ <tr>
1553
+ <td valign=top><p><a name=scale>scale</a></p></td>
1554
+ <td valign=top><p>require 'rubygems'</p>
1555
+ <p>require 'mu'</p>
1556
+ <p>api = Mu::Scale.new(&ldquo;10.10.2.2&rdquo;, &ldquo;admin&rdquo;, &ldquo;admin&rdquo;)</p>
1557
+ <p>$log.level = Logger::INFO</p>
1558
+ <p>Examples: </p>
1559
+ <h6 class="code">api.configure -p musl -pv &lt;scenario.msl&gt;</h6>
1560
+ <h6 class="code">api.configure -p csv -pv &lt;testset.csv&gt;</h6>
1561
+ <h6 class="code">api.configure -p pattern -pv &lt;pattern.json&gt;</h6>
1562
+ <h6 class="code">api.start</h6>
1563
+ <h6 class="code">api.status</h6>
1564
+ <h6 class="code">api.stop</h6>
1565
+ <h6 class="code">api.release</h6></td>
1566
+ </tr>
1567
+ <tr>
1568
+ <td valign=top><a name=netconfig>netconfig</a></td>
1569
+ <td valign=top><p>require 'rubygems'</p>
1570
+ <p>require 'mu'</p>
1571
+ <p>api = Mu::Netconfig.new(&ldquo;10.10.2.2&rdquo;, &ldquo;admin&rdquo;, &ldquo;admin&rdquo;)</p>
1572
+ <p>$log.level = Logger::INFO</p>
1573
+ <p>Example: <span class="code">api.get(&quot;hosts&quot;)</span></p></td>
1574
+ </tr>
1575
+ </table>
1576
+ <p>&nbsp;</p>
1577
+ <p><a href="#top">back to top &uarr;</a></p>
1578
+ <hr />
1579
+ <h2>Mu
1580
+ Dynamics Information</h2>
1581
+ <p>Mu
1582
+ Dynamics Customer Care is available 9am to 5pm PST, Monday to Friday at the
1583
+ toll-free support line at 1-866-276-4640; international customers can
1584
+ also use 1-408-329-6330. For online communication, visit the Mu
1585
+ Dynamics Customer Care Center at <a
1586
+ title="https://forms.netsuite.com/app/crm/marketing/campaignlistener.nl?__lstr=__cl&amp;c=590487&amp;__r=-2147483648&amp;__h=895f7f7a297d1138ee45&amp;url=https://owa.musecurity.com/exchweb/bin/redir.asp?URL=https://forms.netsuite.com/app/crm/marketing/campaignlistener.nl?__lstr=__cl%26c=590487%26__r=-2147483648%26__h=895f7f7a297d1138ee45%26url=http://www.mudynamics.com/support/overview.html"
1587
+ href="https://forms.netsuite.com/app/crm/marketing/campaignlistener.nl?__lstr=__cl&amp;c=590487&amp;__r=-2147483648&amp;__h=895f7f7a297d1138ee45&amp;url=https://owa.musecurity.com/exchweb/bin/redir.asp?URL=https://forms.netsuite.com/app/crm/marketing/campaignlistener.nl?__lstr=__cl%26c=590487%26__r=-2147483648%26__h=895f7f7a297d1138ee45%26url=http://www.mudynamics.com/support/overview.html"
1588
+ target="_blank">http://www.mudynamics.com/support/overview.html</a>. </p>
1589
+ <p>In addition to Mu UI Help and the Mu
1590
+ product documentation, you can also get continuous updates on Mu system
1591
+ capabilities using the following resources: </p>
1592
+ <table width="640" border="1" cellpadding="1" cellspacing="1" class="wide">
1593
+ <tr>
1594
+ <th width="16%" scope="row">Corporate</th>
1595
+ <td width="84%"><a href="http://www.mudynamics.com" target="_blank">Home </a>&#8226;<a href="http://www.mudynamics.com/news/inthenews.html" target="_blank"> Press </a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://www.mudynamics.com/news/events.html" target="_blank">Webinars,
1596
+ Seminars, &amp; Podcasts </a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://www.mudynamics.com/products/demo.html" target="_blank"> Product </a><a href="http://www.mudynamics.com/products/demo.html">Demos</a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://www.mudynamics.com/news/rss.html" target="_blank"> RSS
1597
+ Feed</a></td>
1598
+ </tr>
1599
+ <tr>
1600
+ <th scope="row">Social</th>
1601
+ <td><a href="http://bit.ly/mu-twitter" target="_blank"> Twitter</a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://bit.ly/mu-on-facebook" target="_blank"> Facebook</a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://bit.ly/mu-youtube" target="_blank"> YouTube</a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://www.mudynamics.com/news/inthenews.html"> </a><a href="http://community.mudynamics.com/main/authorization/signIn?" target="_blank"> Mu
1602
+ Community</a> <a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://bit.ly/pcapr" target="_blank"> Pcapr</a></td>
1603
+ </tr>
1604
+ <tr>
1605
+ <th scope="row">Blogs</th>
1606
+ <td><a href="http://bit.ly/mu-line-blog" target="_blank"> Mu
1607
+ Line</a><a href="http://www.mudynamics.com"> </a>&#8226;<a href="http://bit.ly/mu-labs-blog" target="_blank"> </a><a href="http://bit.ly/mu-labs-blog" target="_blank">Mu
1608
+ Labs </a>(with<a href="http://labs.mudynamics.com/category/research/rss2" target="_blank"> RSS
1609
+ Feed</a>) </td>
1610
+ </tr>
1611
+ </table>
1612
+ </div>
1613
+ <div id="siteInfo">
1614
+ Copyright
1615
+ 2011 Mu Dynamics Inc., All Rights Reserved.</div>
1616
+ </body>
1617
+ </html>