new name, same syntax: ssacli ctrl slot=0 pd all showĪrray A physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS HDD, 300 GB, OK) Physicaldrive 2I:1:7 (port 2I:box 1:bay 7, SAS, 600 GB, OK) Physicaldrive 2I:1:6 (port 2I:box 1:bay 6, SAS, 600 GB, OK) Physicaldrive 2I:1:5 (port 2I:box 1:bay 5, SAS, 600 GB, OK) Physicaldrive 1I:1:4 (port 1I:box 1:bay 4, SAS, 600 GB, OK) Physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 600 GB, OK)
Physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 600 GB, OK) on older installs: hpacucli ctrl slot=2 pd all showĪrray A physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 600 GB, OK) What's wrong with the CLI (API) that's freely available? (Monitoring with Check_MK/Nagios is working)Į.g. In either case (automatic or manual iLO reboot), the SSL connection for the web GUI should be back to functional at this point.What do you mean by ". But sometimes, I got an error with no info available, and in that scenario, I rebooted the iLO (repeat step 4) and found that the config seemed to have imported successfully. In my experience, if the error gave me info, I would modify the config XML and try again. The CLI will tell you this unless an error is returned. When this step completes, the iLO should reboot automatically. *remove ALERTMAIL_% values (presumably because the utility does more validation against the e-mail address than it should, so our format was rejected) *remove USER_INFO section (because this doesn't provide as much permission as you can provide from the web GUI) However, I had to make the following changes: While you can use the GUI, the CLI is more helpful once again, especially as this step may require some troubleshooting.
0 kommentar(er)
