HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 137

Using FTP to download logs and update firmware, Downloading system logs, ftp 10.1.0.9, get logs - g3 firmware download

Page 137 highlights

B Using FTP to download logs and update firmware Although SMU is the preferred interface for downloading logs, updating firmware, and installing a license, you can also use FTP to do these tasks. IMPORTANT: Do not attempt to do more than one of the operations in this appendix at the same time. They can interfere with each other and the operations may fail. Specifically, do not try to do more than one firmware update at the same time or try to download system logs while doing a firmware update. Downloading system logs To help service personnel diagnose a system problem, you might be asked to provide system log data. You can download this data by accessing the system's FTP interface and running the get logs command. When both controllers are online, regardless of operating mode, get logs will download a single, compressed zip file that includes: • User configuration settings from both controllers • Event logs from both controllers • SC logs from both controllers • SC crash dumps from both controllers • CAPI trace from the controller receiving the command • MC log from the controller receiving the command • Controller environment (including data about attached disks, enclosures, and so forth) It is recommended to use a command-line-based FTP client. A GUI-based FTP client might not work. To download logs to a file 1. In SMU, prepare to use FTP: a. Determine the network-port IP addresses of the system's controllers; see Changing network interface settings on page 46. b. Verify that the system's FTP service is enabled; see Changing management interface settings on page 40. c. Verify that the user you will log in as has permission to use the FTP interface; see Modifying users on page 43. 2. Open a Command Prompt (Windows) or a terminal window (UNIX) and navigate to the destination directory for the log file. 3. Enter: ftp controller-network-address For example: ftp 10.1.0.9 4. Log in as a user that has permission to use the FTP interface. 5. Enter: get logs filename.zip where filename is the file that will contain the logs. It is recommended to choose a filename that identifies the system, controller, and date. For example: get logs Storage2_A_20100124.zip Wait for the message Operation Complete to appear. 6. Quit the FTP session. 7. If the problem to diagnose seems specific to user-interface behavior, repeat step 3 through step 6 on the partner controller to collect its unique MC log data. HP P2000 G3 MSA System SMU Reference Guide 137

  • 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
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

HP P2000 G3 MSA System SMU Reference Guide
137
B
Using FTP to download logs and update firmware
Although SMU is the preferred interface for downloading logs, updating firmware, and installing a license,
you can also use FTP to do these tasks.
IMPORTANT:
Do not attempt to do more than one of the operations in this appendix at the same time.
They can interfere with each other and the operations may fail. Specifically, do not try to do more than one
firmware update at the same time or try to download system logs while doing a firmware update.
Downloading system logs
To help service personnel diagnose a system problem, you might be asked to provide system log data. You
can download this data by accessing the system’s FTP interface and running the
get logs
command.
When both controllers are online, regardless of operating mode,
get logs
will download a single,
compressed zip file that includes:
User configuration settings from both controllers
Event logs from both controllers
SC logs from both controllers
SC crash dumps from both controllers
CAPI trace from the controller receiving the command
MC log from the controller receiving the command
Controller environment (including data about attached disks, enclosures, and so forth)
It is recommended to use a command-line-based FTP client. A GUI-based FTP client might not work.
To download logs to a file
1.
In SMU, prepare to use FTP:
a.
Determine the network-port IP addresses of the system’s controllers; see
Changing network interface
settings
on
page 46
.
b.
Verify that the system’s FTP service is enabled; see
Changing management interface settings
on
page 40
.
c.
Verify that the user you will log in as has permission to use the FTP interface; see
Modifying users
on
page 43
.
2.
Open a Command Prompt (Windows) or a terminal window (UNIX) and navigate to the destination
directory for the log file.
3.
Enter:
ftp
controller-network-address
For example:
ftp 10.1.0.9
4.
Log in as a user that has permission to use the FTP interface.
5.
Enter:
get logs
filename
.zip
where
filename
is the file that will contain the logs. It is recommended to choose a filename that
identifies the system, controller, and date. For example:
get logs Storage2_A_20100124.zip
Wait for the message
Operation Complete
to appear.
6.
Quit the FTP session.
7.
If the problem to diagnose seems specific to user-interface behavior, repeat
step 3
through
step 6
on
the partner controller to collect its unique MC log data.