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

Viewing recent service history, Physical Location installation and health history

Get HP Integrity Superdome 2 16-socket PDF manuals and user guides View all HP Integrity Superdome 2 16-socket manuals
Add to My Manuals
Save this manual to your list of manuals

Page 71 highlights

FRU Type: CPU Socket Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0 Timestamp: Mon May 18 16:11:19 2009 Indictment State: Acquitted Requested Deconfig State: Configured Current Deconfig State: Deconfigured --- end report --- 2 records shown NOTE: The requested and current deconfiguration states shown in the examples above are not the same. This can happen when requested deconfiguration changes are not be acted on until the n-Par containing the component in question is rebooted. Viewing recent service history You can view the recent service history using the show acquit command. To view the installation history for the acquitted locations, enter show | Physical Location installation and health history The show | command returns the entire stored installation and health history of a physical location. This includes up to two previous components installed at this location. The history will include previous indictments, with or without acquittals, rather than just the indictments. 2009-11-18 21:50 hpsl18-4 HR> show 0x0B00FFFF01FFFF69 Location Installation/Health History - Sat Nov 18 21:51:04 2009 FRU Type: IO Expander Midplane Location: 0x0B00FFFF01FFFF69 enclosure11/midplane0 Timestamp: Thu Sep 10 18:34:11 2009 Indictment State: Indicted Requested Deconfig State: Configured Current Deconfig State: Configured --- Install History 1 --- Discovery: Startup (| Runtime Insertion | Indictment) Timestamp: Thu Sep 10 18:34:12 2009 Serial Num: MYJ84901ZH Parent Serial: 1Z34AB7890 Part Num: AH342-60003 Spare Part Num: AH342-60003 Manufacturer: HP Product Name: CB900s i2 Board Serial Num: MYJ84901ZH - FRU Data Extension Name: value Name2: Value2 (Detailed info about FRU is provided here if it exists. E.g. For CPUs max freq will be provided here. If no data, entire section omitted.) --- Action - Indict --Event No: 4000 Provider: some_provider_name Reason: Text reason of problem from WS-Man alert. Reason: 3:1 Description: Text description of problem from ws-man Alert. Bundle ID: 0x400000000000010D Alert ID: 7400020091023220043 - Indicted / Acquitted - Type Timestamp Entity Ind Thu Sep 10 18:34:11 2009 CAE Acq Thu Sep 10 18:34:11 2009 User Reason See reason above. User request --- Supporting Symptoms - Reason: Text reason of supporting symptom** (not from ws-man). Health Repository viewer 71

  • 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
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11
enclosure1/blade1/socket0
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Acquitted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured
--- end report --- 2 records shown
NOTE:
The requested and current deconfiguration states shown in the examples above are not
the same. This can happen when requested deconfiguration changes are not be acted on until the
n-Par containing the component in question is rebooted.
Viewing recent service history
You can view the recent service history using the show acquit command. To view the installation
history for the acquitted locations, enter show <physical location>|<resource path>
Physical Location installation and health history
The show <physical location>|<resource path> command returns the entire stored installation and
health history of a physical location. This includes up to two previous components installed at this
location. The history will include previous indictments, with or without acquittals, rather than just
the indictments.
2009-11-18 21:50 hpsl18-4 HR> show 0x0B00FFFF01FFFF69
Location Installation/Health History - Sat Nov 18 21:51:04 2009
--------------------------------------------------
FRU Type: IO Expander Midplane
Location: 0x0B00FFFF01FFFF69
enclosure11/midplane0
Timestamp: Thu Sep 10 18:34:11 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Configured
--- Install History 1 ---
Discovery:
Startup (| Runtime Insertion | Indictment)
Timestamp: Thu Sep 10 18:34:12 2009
Serial Num: MYJ84901ZH
Parent Serial: 1Z34AB7890
Part Num: AH342-60003
Spare Part Num: AH342-60003
Manufacturer: HP
Product Name: CB900s i2
Board Serial Num: MYJ84901ZH
- FRU Data Extension -
Name: value
Name2: Value2
(Detailed info about FRU is provided here if it exists. E.g. For CPUs max freq will be provided here. If no
data, entire section omitted.)
--- Action - Indict ---
Event No: 4000
Provider: some_provider_name
Reason: Text reason of problem from WS-Man alert.
Reason: 3:1
Description: Text description of problem from ws-man Alert.
Bundle ID: 0x400000000000010D
Alert ID: 7400020091023220043
- Indicted / Acquitted -
Type Timestamp
Entity
Reason
Ind Thu Sep 10 18:34:11 2009
CAE
See reason above.
Acq Thu Sep 10 18:34:11 2009
User
User request
---
- Supporting Symptoms -
Reason: Text reason of supporting symptom** (not from ws-man).
Health Repository viewer
71