HP ProLiant ML310e HP ProLiant Gen8 Troubleshooting Guide Volume I: Troublesho - Page 24

Using the OA CLI

Get HP ProLiant ML310e PDF manuals and user guides View all HP ProLiant ML310e manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

6. If the blade is not displayed in the Insight Display on the enclosure or within the OA GUI, then troubleshoot the issue further using the procedures in the HP BladeSystem c-Class Enclosure Troubleshooting Guide on the HP website (http://www.hp.com/support/BladeSystem_Enclosure_TSG_en). Using the OA CLI 1. For systems using OA firmware 3.60 or later, execute the SHOW HEALTH CLI command and review possible degraded sections to review health status for the entire enclosure. SHOW HEALTH status output is included within the OA SHOW ALL report as well as the first executed SHOW command. 2. Gather the OA SHOW ALL report. The HP Onboard Administrator provides a detailed SHOW ALL report on the full enclosure configuration, status, and inventory available. This report can be generated in two ways: o OA GUI > Enclosure settings > Enclosure configuration scripts > SHOW ALL o OA CLI > Execute the following CLI command: SHOW ALL 3. For systems using OA firmware 3.60 and earlier, review the SHOW ENCLOSURE LCD section of the SHOW ALL report. The flashing Insight Display indicates a warning. Review the data or remotely review messages on the Insight Display through the OA GUI. 4. Review the following sections of the SHOW ALL report for a status overview of the enclosure by searching for the following command output: o SHOW ENCLOSURE STATUS o SHOW SERVER STATUS ALL o SHOW INTERCONNECT STATUS ALL If any status is degraded, then observe the subcomponents one by one to discover the degraded component. Subcomponents that are faulty can be marked as such. For example, health: faulty or Internal Data Failed. 5. Review the OA SHOW ALL syslog section at SHOW SYSLOG OA (1 or 2, depending on which one is active) especially from when the incident happened. The OA SYSLOG can assist you with which section you might expect a failure. If needed, fill in syslog lines from the syslog on the HP website (http://www.hp.com/go/hpsc). If the time frame of the failure is not available within the OA SYSLOG, then review the extended OA SYSLOG using the following CLI command: SHOW SYSLOG HISTORY 0 6. For any low level (transport layer) SAN or network connectivity errors in an interconnect device or network card connection, review the low level FRU firmware update at the section of the SHOW ALL report called SHOW UPDATE. Any newer version available in the New Version column must be updated using the update device command. This causes an interruption in the I/O connectivity, so update the firmware per module and not all together. For more information about the update device command, see the OA CLI Users Guide on the HP website (http://www.hp.com/go/bladesystem/documentation). 7. To review any connectivity issues with 1 or 10 GB pass-thru module, install the latest pass-thru module interconnect firmware. 8. Capture any entry in the OA syslog file referring to "Saving supportdump" by using the OA CLI command upload supportdump, and then send it to HP Support for analysis where needed. For more information, see the HP website (http://www.hp.com/go/OAsupportdump). Remote troubleshooting 24

  • 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
Remote troubleshooting 24
6.
If the blade is not displayed in the Insight Display on the enclosure or within the OA GUI, then
troubleshoot the issue further using the procedures in the
HP BladeSystem c-Class Enclosure
Troubleshooting Guide
on the HP website
(
).
Using the OA CLI
1.
For systems using OA firmware 3.60 or later, execute the
SHOW HEALTH CLI
command and review
possible degraded sections to review health status for the entire enclosure. SHOW HEALTH status
output is included within the OA SHOW ALL report as well as the first executed
SHOW
command.
2.
Gather the OA SHOW ALL report. The HP Onboard Administrator provides a detailed SHOW ALL
report on the full enclosure configuration, status, and inventory available. This report can be generated
in two ways:
o
OA GUI > Enclosure settings > Enclosure configuration scripts >
SHOW ALL
o
OA CLI > Execute the following CLI command:
SHOW ALL
3.
For systems using OA firmware 3.60 and earlier, review the SHOW ENCLOSURE LCD section of the
SHOW ALL report. The flashing Insight Display indicates a warning. Review the data or remotely review
messages on the Insight Display through the OA GUI.
4.
Review the following sections of the SHOW ALL report for a status overview of the enclosure by
searching for the following command output:
o
SHOW ENCLOSURE STATUS
o
SHOW SERVER STATUS ALL
o
SHOW INTERCONNECT STATUS ALL
If any status is degraded, then observe the subcomponents one by one to discover the degraded
component. Subcomponents that are faulty can be marked as such. For example, health: faulty or
Internal Data Failed.
5.
Review the OA SHOW ALL syslog section at SHOW SYSLOG OA (1 or 2, depending on which one is
active) especially from when the incident happened. The OA SYSLOG can assist you with which section
you might expect a failure. If needed, fill in syslog lines from the syslog on the HP website
(
). If the time frame of the failure is not available within the OA SYSLOG,
then review the extended OA SYSLOG using the following CLI command:
SHOW SYSLOG HISTORY 0
6.
For any low level (transport layer) SAN or network connectivity errors in an interconnect device or
network card connection, review the low level FRU firmware update at the section of the SHOW ALL
report called SHOW UPDATE. Any newer version available in the New Version column must be
updated using the update device command. This causes an interruption in the I/O connectivity, so
update the firmware per module and not all together. For more information about the update device
command, see the OA CLI Users Guide on the HP website
(
).
7.
To review any connectivity issues with 1 or 10 GB pass-thru module, install the latest pass-thru module
interconnect firmware.
8.
Capture any entry in the OA syslog file referring to "Saving supportdump" by using the OA CLI
command
upload supportdump
, and then send it to HP Support for analysis where needed. For
more information, see the HP website (
).