HP StorageWorks 2/128 HP StorageWorks Core Switch 2/64 and SAN Director 2/128 - Page 100

Identifying a failed CP Card, Recording critical switch information, slotShow, haShow, Slot unknown

Page 100 highlights

Identifying a failed CP Card The following indicators confirm that a CP card needs to be replaced: • The Status LED on the CP card is yellow, or the Power LED is not ON. • The slotShow command does not show that the CP card is enabled. • The CP card does not respond to telnet commands, or the serial console is not available. • The haShow command indicates that the CP cards have not achieved redundancy (after 30 minutes). • The calendar clock is inaccurate, or the CP card does not boot up or shut down normally. • Any of the following messages appear in the error log: • Slot unknown message relating to a CP slot • CP card errors or I2C timeouts • FRU: FRU_FAULTY messages for a CP card • Configuration loader messages or Sys PCI config messages • Generic system driver messages, FABSYS • Platform system driver messages • EM messages that indicate a problem with a CP card • Function fail messages for the CP master Recording critical switch information Back up the switch configuration before replacing a CP card. To record critical switch information, follow these steps: 1. Create a serial connection to the healthy CP card: a. Disable any serial communication programs running on the workstation (such as synchronization programs). b. Connect a serial cable to the terminal serial port (10101 Console Port). c. Connect the other end of the serial cable to a serial port on the workstation. If necessary, you can remove the adapter on the serial cable to allow for a serial RJ45 connection. 100 Installing FRUs

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166

Installing FRUs
100
Identifying a failed CP Card
The following indicators confirm that a CP card needs to be replaced:
The Status LED on the CP card is yellow, or the Power LED is not ON.
The
slotShow
command does not show that the CP card is enabled.
The CP card does not respond to telnet commands, or the serial console is not available.
The
haShow
command indicates that the CP cards have not achieved redundancy (after 30
minutes).
The calendar clock is inaccurate, or the CP card does not boot up or shut down normally.
Any of the following messages appear in the error log:
Slot unknown
message relating to a CP slot
CP card errors or I
2
C timeouts
FRU:
FRU_FAULTY
messages for a CP card
Configuration loader messages or
Sys PCI config
messages
Generic system driver messages,
FABSYS
Platform
system driver messages
EM
messages that indicate a problem with a CP card
Function fail messages for the CP master
Recording critical switch information
Back up the switch configuration before replacing a CP card.
To record critical switch information, follow these steps:
1.
Create a serial connection to the healthy CP card:
a.
Disable any serial communication programs running on the workstation (such as
synchronization programs).
b.
Connect a serial cable to the terminal serial port (10101 Console Port).
c.
Connect the other end of the serial cable to a serial port on the workstation. If
necessary, you can remove the adapter on the serial cable to allow for a serial RJ45
connection.