Home » HP Manuals » Storage Devices » HP Surestore 64 » Manual Viewer

HP Surestore 64 HP Surestore Director FC-64 Product Manager User's Guide - Page 112

Troubleshooting Tips, CRC errors, Delimiter errors, Address ID errors, Frames too short

Add to My Manuals
Save this manual to your list of manuals

Page 112 highlights

incident. If one or more invalid transmission words are detected in 12 separate 1.5second samples within five minutes, a bit-error threshold link incident is generated. • CRC errors A received frame failed a cyclic redundancy check (CRC) validation, indicating the frame arrived at the director's port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection. • Delimiter errors The number of times that the director detected an unrecognized start-of-frame (SOF), an unrecognized end-of-frame (EOF) delimiter, or an invalid class of service. This indicates that the frame arrived at the director's port corrupted. This corruption can be due to plugging/unplugging the link, bad optics at either end of the cable, bad cable, or dirty or poor connections. Moving the connection around or replacing cables can isolate the problem. • Address ID errors A received frame had an unavailable or invalid Fibre Channel destination address, or an invalid Fibre Channel source address. This typically indicates the destination device is unavailable. • Frames too short- A received frame exceeded the Fibre Channel frame maximum size or was less than the Fibre Channel minimum size, indicating the frame arrived at the director's port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection. Troubleshooting Tips As a general rule, you should clear all counts after the system is stabilized. When looking at the Performance View, roughly keep track of the time interval when errors accumulate to judge the presence and severity of a problem. Also, recognize that there is a link recovery hierarchy implemented in Fibre Channel to handle some level of "expected anomalies." In general, only be concerned with error counts that increment very quickly. 96 Performance View

Section	Page
Product Manager Messages	8
Regulatory Statements	9
Glossary	9
Index	10
1 Product Manager Overview	17
Managing the HP Surestore Director FC-64	18
EFC Management Menu Options	19
HP EFC Manager	19
Fabric Manager	20
Product Manager	21
Product Manager Description	23
Using the Product Manager	27
Using Dialog Boxes	27
Keyboard Navigation	27
Logging in to the HP EFC Manager	27
Opening the Product Manager	30
Window Layout and Function	32
Closing the Product Manager	55
User Rights	56
Backing Up and Restoring Product Manager Data	59
Restoring Data to the HP EFC Server	60
Using QuikSync	60
2 Monitoring and Managing the Director	65
Hardware View	66
Identifying FRUs	66
Monitoring Director Operation	66
Monitoring Hardware Operation	69
Obtaining Hardware Information	72
Using Menu Options	75
Using the Port Card View	82
Port List View	94
Menu Options	96
FRU List View	98
Node List View	100
Menu Options	102
Displaying Node Properties	103
Performance View	106
Menu Options	106
Bar Graph Display	107
Port Statistics	108
Troubleshooting Tips	112
Button Functions	113
Port Operational States	114
Link Incident Alerts	117
Threshold Alerts	118
3 Configuring the Director	119
Configure Identification	121
Procedure	121
Configure Operating Mode	123
Introduction	123
Procedure	123
Configure Operating Parameters	126
Procedure	129
Configure Ports	131
Menu Options	134
Procedure	136
Configure SNMP	139
Procedure	139
Configure Open Systems Management Server	142
Procedure	142
Configure Feature Key	143
Procedure	143
Configure Date and Time	146
Procedure	146
Configure Threshold Alerts	149
Procedures	150
Export Configuration Report	158
Procedure	158
Enable Web Server	160
Enable Telnet	161
Backing Up and Restoring Configuration Data	162
4 Using Logs	163
Using Logs	164
Button Function	164
Expanding Columns	165
Audit Log	166
Event Log	169
Hardware Log	172
Link Incident Log	174
Threshold Alert Log	176
5 Using Maintenance Features	179
Run Port Diagnostics	180
Collect Maintenance Data	181
Execute an IPL	182
Set Online State	184
Manage Firmware Versions	186
Enable E-Mail Notification	187
Enable Call-Home Notification	188
Backup and Restore Configuration	189
Reset Configuration	191
Notes	191
Procedure	191
Product Manager Messages	195
A	196
C	197
D	199
E	200
F	200
I	201
L	203
M	203
N	203
P	204
R	204
S	204
T	205
U	207
Y	207
Regulatory Statements	209
FCC EMC Statement (USA)	210
EMC Statement (Canada)	211
EMC Statement (European Union)	212
Spécification ATI Classe A (France)	213
VCCI EMC Statement (Japan)	214
Harmonics Conformance (Japan)	215
RRL EMC Statement (Korea)	216
BSMI EMC Statement (Taiwan)	217
Germany Noise Declaration	218
Laser Safety	219
Declaration of Conformity	220
A	221
B	222
C	223
D	225
E	227
F	228
G	230
H	231
I	232
J	233
L	233
M	235
N	236
O	237
P	238
R	239
S	240
T	242
U	242
V	243
W	243
Z	244
Numerics	245
A	245
B	245
C	245
D	247
E	248
F	248
G	249
H	249
I	250
J	250
K	250
L	250
M	251
N	252
O	252
P	252
Q	254
R	254
S	254
T	255
U	255
V	255
W	256

Match case Limit results 1 per page

Performance View

incident. If one or more invalid transmission words are detected in 12 separate 1.5-

second samples within five minutes, a bit-error threshold link incident is generated.

•

CRC errors

A received frame failed a cyclic redundancy check (CRC) validation, indicating the

frame arrived at the director

’

s port corrupted. Frame corruption may be caused by

device disconnection, an optical transceiver failure at the device, a bad fiber-optic

cable, or a poor cable connection.

•

Delimiter errors

The number of times that the director detected an unrecognized start-of-frame (SOF),

an unrecognized end-of-frame (EOF) delimiter, or an invalid class of service. This

indicates that the frame arrived at the director

’

s port corrupted. This corruption can be

due to plugging/unplugging the link, bad optics at either end of the cable, bad cable, or

dirty or poor connections. Moving the connection around or replacing cables can

isolate the problem.

•

Address ID errors

A received frame had an unavailable or invalid Fibre Channel destination address, or

an invalid Fibre Channel source address. This typically indicates the destination device

is unavailable.

•

Frames too short

A received frame exceeded the Fibre Channel frame maximum size or was less than

the Fibre Channel minimum size, indicating the frame arrived at the director

’

s port

corrupted. Frame corruption may be caused by device disconnection, an optical

transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection.

Troubleshooting Tips

As a general rule, you should clear all counts after the system is stabilized. When looking at

the Performance View, roughly keep track of the time interval when errors accumulate to

judge the presence and severity of a problem. Also, recognize that there is a link recovery

hierarchy implemented in Fibre Channel to handle some level of

“

expected anomalies.

”

general, only be concerned with error counts that increment very quickly.