HP Integrity Superdome 2 16-socket HP Integrity Superdome 2 User Service Guide - Page 83

Troubleshooting partitions, Troubleshooting the network

Page 83 highlights

3. Select your product. 4. Select your operating system or Cross operating system (BIOS, Firmware, Diagnostics, etc.). This takes you to the product download page. 5. Select the appropriate download, and follow the instructions. NOTE: If the Superdome 2 system already has firmware bundle 2.2.27 or later installed, then it is possible to update firmware without taking all the partitions down at once. The complex (or management side) firmware can be updated while all the partitions remain online, and then the partition (or system side) firmware can be applied to one nPartition at a time. It is possible that some firmware updates will be released which do not require partition firmware updates, these firmware bundles can be installed without requiring any nPartition downtime. See the detailed instructions provided in the firmware download bundle for more information. Troubleshooting partitions Use the following commands to troubleshoot partitions: • Use the OA commands parstatus and vparstatus -N to determine which resources belong the failing nPar or vPar. • Use the HR> show indict and show deconfig commands to determine if any of the resources belonging to the nPar or vPar of interest are deconfigured, indicted or in any failure state. If any issues are reported, use the show CAE command for more information. • Use the show syslog OA 1 command to check the syslog file for the active OA. For example: oa1> show syslog oa 1 Dec 11 10:26:03 vparboot: vparboot -p 1:9 Dec 11 10:26:03 parcon: Note: nPartition 1: vPar 9: Attempting to Power On Virtual Partition: 9 in nPartition: 1 Dec 11 10:26:03 icapd: Error: Authorization failed for 2 core(s) for vPartition 1 : 9. Only 0 usage rights are available. Dec 11 10:26:03 parcon: Error: nPartition 1: vPar 9: Power On of Virtual Partition failed. Error: iCAP authorization failed. Dec 11 10:26:03 parcon: Error: nPartition 1: vPar 9: Power On of Virtual Partition: 9 in nPartition:1 failed. Error: iCAP authorization failed. Jun 27 09:10:39 parcon: Note: nPartition 1: Attempting Power On of nPartition Jun 27 09:10:39 parcon: Error: nPartition 1: Power On of nPartition failed. Err or: Specified partition is active. Dec 11 10:30:09 vparmodify: vparmodify -p 1:6 -d cpu::2 NOTE: All partition-related messages in OA syslog contain the string "parcon:" and/or parmodify/vparmodify or any other partition commands. Troubleshooting the network An incorrect setup for the enclosure and complex wide internal network can lead to issues with the following tasks: • Powering on/off partitions • Update firmware • Gathering status information Each iLO and OA in the complex must have a unique IP address set up. The IP addresses will be obtained by either using a DHCP server or defining the IP addresses using EBIPA. Use the show ebipa and show OA network all commands to check the network settings for iLO and the OA: SHOW EBIPA Troubleshooting partitions 83

  • 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

3.
Select your product.
4.
Select your operating system or Cross operating system (BIOS, Firmware, Diagnostics, etc.).
This takes you to the product download page.
5.
Select the appropriate download, and follow the instructions.
NOTE:
If the Superdome 2 system already has firmware bundle 2.2.27 or later installed, then
it is possible to update firmware without taking all the partitions down at once.
The complex (or management side) firmware can be updated while all the partitions remain online,
and then the partition (or system side) firmware can be applied to one nPartition at a time.
It is possible that some firmware updates will be released which do not require partition firmware
updates, these firmware bundles can be installed without requiring any nPartition downtime.
See the detailed instructions provided in the firmware download bundle for more information.
Troubleshooting partitions
Use the following commands to troubleshoot partitions:
Use the OA commands
parstatus
and
vparstatus
N <nPar-ID>
to determine which
resources belong the failing nPar or vPar.
Use the
HR> show indict
and
show deconfig
commands to determine if any of the
resources belonging to the nPar or vPar of interest are deconfigured, indicted or in any failure
state.
If any issues are reported, use the
show CAE
command for more information.
Use the
show syslog OA 1
command to check the syslog file for the active OA. For
example:
oa1> show syslog oa 1
Dec 11 10:26:03
vparboot: vparboot -p 1:9
Dec 11 10:26:03
parcon: Note: nPartition 1: vPar 9: Attempting to Power On Virtual Partition: 9 in
nPartition: 1
Dec 11 10:26:03
icapd: Error: Authorization failed for 2 core(s) for vPartition 1 : 9. Only 0 usage rights
are available.
Dec 11 10:26:03
parcon: Error: nPartition 1: vPar 9: Power On of Virtual Partition failed. Error: iCAP
authorization failed.
Dec 11 10:26:03
parcon: Error: nPartition 1: vPar 9: Power On of Virtual Partition: 9 in nPartition:1
failed. Error: iCAP authorization failed.
Jun 27 09:10:39
parcon: Note: nPartition 1: Attempting Power On of nPartition
Jun 27 09:10:39
parcon: Error: nPartition 1: Power On of nPartition failed. Err
or: Specified partition is active.
Dec 11 10:30:09
vparmodify: vparmodify -p 1:6 -d cpu::2
NOTE:
All partition-related messages in OA syslog contain the string ”parcon:“ and/or
parmodify/vparmodify or any other partition commands.
Troubleshooting the network
An incorrect setup for the enclosure and complex wide internal network can lead to issues with
the following tasks:
Powering on/off partitions
Update firmware
Gathering status information
Each iLO and OA in the complex must have a unique IP address set up. The IP addresses will be
obtained by either using a DHCP server or defining the IP addresses using EBIPA.
Use the
show ebipa
and
show OA network all
commands to check the network settings for
iLO and the OA:
SHOW EBIPA
Troubleshooting partitions
83