Dell DR4000 Command Line Reference Guide - Page 75

diagnostics --collect, reason, diagnostics, collect, force

Get Dell DR4000 PDF manuals and user guides View all Dell DR4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

--collect [--name , --reason , --force, --dset, --all] To generate a new diagnostics log file that represents the current state of a DR4000 system, enter the following command string at the system prompt: administrator@mydr4000 > diagnostics --collect Collecting diagnostics...done. Diagnostics file mydr4000_2011-11-17_17-15-52.lzip created. To define a specific name for the diagnostics file you want to generate, append the --name option to the diagnostics --collect command as shown in this example: administrator@mydr4000 > diagnostics -collect --name diag_mydr4000_11-17-11 Collecting diagnostics...done. Diagnostics file mydr4000_11_17_11.lzip created. To define a specific reason for the diagnostics file you want to generate, append the --reason command option to the diagnostics --collect --name command as shown in this example: administrator@mydr4000 > diagnostics --collect --name mydr4000_11_17_11 --reason check-operations Collecting diagnostics...done. Diagnostics file mydr4000_11_17_11.lzip created. To force the generation of a diagnostics file that collects your current system information, append the --force command option to the diagnostics --collect command as shown in this example: NOTE: Use the diagnostics --force command when you want to override any existing system operations to generate a diagnostics log file immediately because it is a priority. administrator@mydr4000 > diagnostics --collect --force Collecting diagnostics...done. Diagnostics file mydr4000_2011-11-15_13-53-57.lzip created. Maintaining the DR4000 System 65

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
Maintaining the DR4000 System
65
--collect [--name <name>, --reason <reason>, --force, --dset, --all]
To generate a new diagnostics log file that represents the current state of a
DR4000 system, enter the following command string at the system prompt:
administrator@mydr4000 > diagnostics --collect
Collecting diagnostics...done.
Diagnostics file mydr4000_2011-11-17_17-15-52.lzip created.
To define a specific name for the diagnostics file you want to generate,
append the
--name
option to the
diagnostics --collect
command as shown in
this example:
administrator@mydr4000 > diagnostics -collect --name
diag_mydr4000_11-17-11
Collecting diagnostics...done.
Diagnostics file mydr4000_11_17_11.lzip created.
To define a specific reason for the diagnostics file you want to generate,
append the
--reason
command option to the
diagnostics
--collect
--name
command as shown in this example:
administrator@mydr4000 > diagnostics --collect --name
mydr4000_11_17_11 --reason check-operations
Collecting diagnostics...done.
Diagnostics file mydr4000_11_17_11.lzip created.
To force the generation of a diagnostics file that collects your current system
information, append the
--force
command option to the
diagnostics
--collect
command as shown in this example:
NOTE:
Use the
diagnostics --force
command when you want to override any
existing system operations to generate a diagnostics log file immediately because it
is a priority.
administrator@mydr4000 > diagnostics --collect --force
Collecting diagnostics...done.
Diagnostics file mydr4000_2011-11-15_13-53-57.lzip created.