Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual
  1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Switch
  5. A7533A - Brocade 4Gb SAN Switch Base
  6. Reference manual
Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual

Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual

Brocade error message reference guide v6.0.0 (53-1000600-01, april 2008)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:
1
2
3
4
Table Of Contents
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
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Reference Manual
53-1000600-01
19 October 2007
Fabric OS
Message Reference
Supporting Fabric OS v6.0.0

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the A7533A - Brocade 4Gb SAN Switch Base and is the answer not in the manual?

Questions and answers

Related Manuals for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base

Summary of Contents for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base

  • Page 1 53-1000600-01 19 October 2007 Fabric OS Message Reference Supporting Fabric OS v6.0.0...
  • Page 2 Copyright © 2007, Brocade Communications Systems, Incorporated. ALL RIGHTS RESERVED. 53-1000600-01 Brocade, the Brocade B weave logo, Secure Fabric OS, and Brocade are registered trademarks and Tapestry is a trademark of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON, IBM BladeCenter are registered trademarks of IBM Corporation in the U.S.
  • Page 3 Document History The following table lists all versions of the Brocade Fabric OS Message Reference. Document Title Publication Summary of Changes Publication Date Number Diagnostic and System Error 53-0000210-02 First release March 2002 Message Reference v3.0, v4.0 Diagnostic and System Error 53-0000511-04 Major content reorganization June 2003...
  • Page 4 Document Title Publication Summary of Changes Publication Date Number Fabric OS System Error Message 53-1000046-02 Minor updates to a few messages. June 2006 Reference Manual Fabric OS Message Reference 53-1000242-01 -Updated for Fabric OS v5.2.0: September 2006 -changed doc title and number -Added the following new modules: IBPD, ICPD, ISCSI, ISNSCD.

  • Page 5: Table Of Contents

    Contents About This Document How This Document Is Organized ........xlvii Supported Hardware and Software .
  • Page 6 System Module Descriptions ........14 Section I RASLog Messages Section II...
  • Page 7 AUTH-1004 ............34 AUTH-1005 .
  • Page 8 Chapter 4 BKSW System Messages BKSW-1003 ............47 Chapter 5 BL System Messages BL-1000 .
  • Page 9 BL-1034 ............60 BL-1035 .
  • Page 10 Chapter 11 CONF System Messages CONF-1000 ............75 CONF-1001 .
  • Page 11 EM-1042 ............87 EM-1043 .
  • Page 12 FABR-1004............100 FABR-1005.
  • Page 13 FABS-1012 ............112 FABS-1013 .
  • Page 14 FICN-1017 ............129 FICN-1018 .
  • Page 15 FICN-1054 ............139 FICN-1055 .
  • Page 16 FICU-1003 ............151 FICU-1004 .
  • Page 17 FSSM-1004 ........... . .166 Chapter 29 FW System Messages FW-1001 .
  • Page 18 FW-1115 ............178 FW-1116 .
  • Page 19 FW-1171............192 FW-1172 .
  • Page 20 FW-1248 ............204 FW-1249 .
  • Page 21 FW-1325 ............217 FW-1326 .
  • Page 22 FW-1362 ............231 FW-1363 .
  • Page 23 FW-1439 ............243 FW-1440 .
  • Page 24 HIL-1207 ............257 HIL-1208 .
  • Page 25 Chapter 34 HMON System Messages HMON-1001........... . .269 Chapter 35 HTTP System Messages HTTP-1001.
  • Page 26 Chapter 41 ISCS System Messages ISCS-1000 ............285 Chapter 42 ISNS System Messages ISNS-1001 .
  • Page 27 FCR-1022............296 FCR-1023.
  • Page 28 FCR-1066............307 FCR-1067.
  • Page 29 MFIC-1002............319 MFIC-1003.
  • Page 30 Chapter 54 PDM System Messages PDM-1001 ............335 PDM-1002 .
  • Page 31 Chapter 58 PS System Messages PS-1000 ............349 PS-1001 .
  • Page 32 Chapter 62 RPCD System Messages RPCD-1001 ........... . .361 RPCD-1002 .
  • Page 33 SEC-1032............375 SEC-1033.
  • Page 34 SEC-1079............386 SEC-1080.
  • Page 35 SEC-1121............399 SEC-1122.
  • Page 36 SEC-1182............410 SEC-1183.
  • Page 37 SEC-1312............422 SEC-1313.
  • Page 38 SULB-1003 ........... . .433 SULB-1004 .
  • Page 39 Chapter 71 SYSC System Messages SYSC-1001............451 SYSC-1002.
  • Page 40 Chapter 75 TS System Messages TS-1001 ............463 TS-1002 .
  • Page 41 ZONE-1013 ........... . .480 ZONE-1014 .
  • Page 42 AUTH-3006 ........... . .492 AUTH-3007.
  • Page 43 SEC-3025 ............507 SEC-3026 .
  • Page 44 SULB-1021 ........... . .525 SULB-1023 .
  • Page 45 ZONE-3025 ........... . .537 Fabric OS Message Reference 53-1000600-01...
  • Page 46 xlvi Fabric OS Message Reference 53-1000600-01...

  • Page 47: About This Document

    About This Document This document is a system message reference manual written to help system administrators and technicians operate, maintain, and troubleshoot SAN products. “About This Document” contains the following sections: • How This Document Is Organized ....xlvii •...

  • Page 48: What's New In This Document

    • Brocade 48000 director • FA4-16 blade • FC10-6 blade In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies exactly which switches are supported and which are not.

  • Page 49: Additional Information

    italic text Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles Identifies class properties text Identifies CLI output code Identifies syntax examples For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow.
  • Page 50 Fabric OS • Fabric OS Administrator’s Guide • Fabric OS Command Reference • Fabric OS iSCSI Gateway Service Administrator’s Guide • Fabric OS MIB Reference • Fabric OS Message Reference • Brocade Glossary Optional Applications • Web Tools Administrator’s Guide •...

  • Page 51: Getting Technical Help

    Gbit/sec switches and directors. When two or more adjacent ISLs are used to connect two switches, the switches automatically group the ISLs into a single logical ISL, or “trunk.” The throughput of the resulting trunk can be anywhere from 4 Gbit/sec to as much as 32 Gbit/sec. Advanced Zoning Automatically groups SAN fabric-connected devices into logical zones that restrict access to “member”...

  • Page 52: Document Feedback

    Detailed description of the problem and specific questions Description of any troubleshooting steps already performed and results Serial console and telnet session logs syslog message logs 2. Switch Serial Number The switch serial number and corresponding bar code are provided on the serial number label, as shown here: *FT00X0054E9* FT00X0054E9...

  • Page 53: Overview Of System Messages

    Chapter Introduction to System Messages This guide supports Fabric OS v6.0.0 and documents system messages that can help you diagnose and fix problems with a switch or fabric. The messages are organized first by event type, reliability, availability, and serviceability log (RASLog) or AUDIT, and then alphabetically by module name. A module is a subsystem in the Fabric OS.

  • Page 54: Event Auditing

    Overview of System Messages • Messages are numbered sequentially from 1 to 2,147,483,647 (0x7ffffff). The sequence number will continue to increase beyond the storage limit of 1024 messages. The sequence number can be reset to 1 using the errClear command. The sequence number is persistent across power cycles and switch reboots.

  • Page 55: System Logging Daemon (Syslogd)

    Overview of System Messages Fabric OS v6.0.0 generates the following component-specific Audit messages: • Authentication messages: AUTH 2001-3008 • Configuration messages: CONF-1000, 1020, 1022 • HTTP configuration messages: HTTP-1002 - 1003 • SNMP related messages: SNMP-1004 - 1006 • Security related messages (SFOS, RADIUS, login/logout, passwords, ACLs): SEC-3001 - 3038 •...

  • Page 56: Port Logs

    Viewing and Configuring System Message Logs The system console displays system messages, Audit messages (if enabled) and panic dump messages. These messages are mirrored to the system console; they are always saved in one of the system logs. You can filter messages that appear on the system console by severity using the errFilterSet command.
  • Page 57 Viewing and Configuring System Message Logs TABLE 2 Commands for Viewing or Configuring the System Parameters and Logs Command Description agtCfgDefault Resets the SNMP recipients to default values. agtCfgSet Modifies the SNMP agent configuration. agtCfgShow Displays the current SNMP agent configuration. auditCfg Configures the audit message log.

  • Page 58: Viewing System Messages From Web Tools

    Viewing and Configuring System Message Logs TABLE 2 Commands for Viewing or Configuring the System Parameters and Logs (Continued) Command Description supportFfdc Enables and disables FFDC (first failure data capture). supportSave Collects RASLog, trace files, and supportShow (active CP only) information for the local CP and then transfers the files to an FTP server.

  • Page 59: Viewing System Messages One Message At A Time

    Viewing and Configuring System Message Logs 2004/07/28-17:04:51, [EM-1055], 3,, WARNING, switch, Media 27: Port media incompatible. Reason: Configured port speed. 2004/07/28-17:04:54, [FABR-1001], 4,, WARNING, switch, port 4, ELP rejected by the other switch 2004/07/28-17:05:06, [FW-1050], 5,, WARNING, switch, Sfp Supply Voltage 0, is below low boundary(High=3600, Low=3150).

  • Page 60: Reading A Ras System Message

    Reading a RAS System Message switch:admin> auditcfg --show Audit filter is enabled. 1-ZONE 2-SECURITY 3-CONFIGURATION 4-FIRMWARE 5-FABRIC 3. Enable the audit feature: switch:admin> auditcfg --enable Audit filter is enabled. 4. Configure up to six syslog servers to receive the audit events that will be generated through syslog (procedure will vary depending on server type).

  • Page 61: Audit Event Messages

    Reading a RAS System Message TABLE 3 System Message Field Description (Continued) Example Variable Name Description Sequence Number Represents the error message position in the log. When a new message is added to the log, this number is incremented by 1. When this message reaches the last position in the error log, and becomes the oldest message in the log, it is deleted when a new message is added.
  • Page 62 Reading a RAS System Message AUDIT, 2005/12/10-09:54:03, [SEC-1000], WARNING, SECURITY, JohnSmith/root/192.168.132.10/Telnet/CLI, Domain A/JohnsSwitch, , Incorrect password during login attempt. The fields in the error message are described in table below. TABLE 4 Audit Message Field Description Example Variable Name Description AUDIT Audit flag Identifies the message as an Audit message.

  • Page 63: Message Severity Levels

    Responding to a System Message MESSAGE SEVERITY LEVELS There are four levels of severity for messages, ranging from Critical (1) to Info (4). In general, the definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all cases, you should look at each specific error message description thoroughly before taking action.

  • Page 64: Gathering Information About The Problem

    Responding to a System Message GATHERING INFORMATION ABOUT THE PROBLEM Common steps and questions to ask yourself when troubleshooting a system message are as follows: 1. What is the current Fabric OS level? 2. What is the switch hardware version? 3.

  • Page 65: Trace Dumps

    Responding to a System Message The software watchdog process (SWD) is responsible for monitoring daemons critical to the function of a healthy switch. The SWD holds a list of critical daemons that ping the SWD periodically at a predetermined interval defined for each daemon. The ping interval is set at 133 seconds, with the exception of the Fabric Watch daemon and the IP storage demon, which ping the SWD every 333 seconds.

  • Page 66: System Module Descriptions

    System Module Descriptions System Module Descriptions Table 5 provides a summary of the system modules for which messages are documented in this reference guide; the system modules are listed alphabetically by name. TABLE 5 System Module Descriptions System Description Module Access Gateway allows multiple hosts (or HBAs) to access the fabric using fewer physical ports.
  • Page 67 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module FICU The FICON-CUP daemon handles communication with fibre connectivity (FICON) on IBM FICON storage devices. Errors to this module are usually initiation errors or indications that FICON-CUP prerequisites have not been met, such as a license key, core process ID (PID), and secure mode on the fabric.
  • Page 68 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module KSWD The kernel software watchdog (KSWD) watches daemons for unexpected terminations and “hang” conditions and informs the HAM module to take corrective actions such as failover or reboot. The following daemons are monitored by KSWD: •...
  • Page 69 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module The Management Service enables the user to obtain information about the Fibre Channel fabric topology and attributes by providing a single management access point. MS provides for both monitoring and control of the following areas: Fabric Configuration Server.
  • Page 70 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module SNMP Simple Network Management Protocol is a universally supported low-level protocol that allows simple get, get next, and set requests to go to the switch (acting as an SNMP agent). It also allows the switch to send traps to the defined and configured management station.
  • Page 71 Section RASLog Messages This section provides the RASLog messages, including: • AG System Messages ......25 •...
  • Page 72 • HMON System Messages ..... 269 • HTTP System Messages ..... . 271 •...
  • Page 73 • TRCK System Messages..... . 461 • TS System Messages ......463 •...
  • Page 75 Section Audit Log Messages This section provides the Audit messages, including: • AUDIT AUTH System Messages ....491 • AUDIT CONF System Messages ....495 •...

  • Page 77: Ag-1001

    Chapter AG System Messages AG-1001 Message <timestamp>, [AG-1001], <sequence-number>,, ERROR, <system-name>, N_Port ID virtualization (NPIV) is not supported by fabric port connected to port <port>. Probable Cause N_Port ID virtualization (NPIV) capability is not supported by the fabric port to which the Access Gateway is connected.

  • Page 78: Ag-1004

    AG-1004 Severity WARNING AG-1004 Message <timestamp>, [AG-1004], <sequence-number>,, ERROR, <system-name>, Invalid response to fabric login (FLOGI) request from the fabric for N_Port <port>. Probable Cause Indicates that the fabric sent an invalid response to the FLOGI Extended Link Service (ELS) for the specified N_Port.

  • Page 79: Ag-1008

    AG-1008 Recommended Check the connectivity between the Access Gateway N_Port and the fabric switch port. Action Severity WARNING AG-1008 Message <timestamp>, [AG-1008], <sequence-number>,, WARNING, <system-name>, Invalid port login (PLOGI) response from the fabric on the N_Port <port>. Probable Cause Indicates that the fabric switch management server did not accept the N_Port Login (PLOGI) request sent by the Access Gateway.

  • Page 80: Ag-1011

    AG-1011 AG-1011 Message <timestamp>, [AG-1011], <sequence-number>,, WARNING, <system-name>, Sending FDISC failed on N_Port <port>. Probable Cause Indicates failure of sending the discover F_Port service parameter request from the Access Gateway to the fabric switch. Recommended Please check the configuration of the fabric switch connected to the Access Gateway. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...

  • Page 81: Ag-1015

    AG-1015 Severity INFO AG-1015 Message <timestamp>, [AG-1015], <sequence-number>,, WARNING, <system-name>, Unable to find online N_Ports to connect to the fabric. Probable Cause Either no other N_Port is configured or all N_Ports are currently offline. Recommended Please check whether or not any other N_Port is configured. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...

  • Page 82: Ag-1019

    AG-1019 Recommended Run switchShow to display the status of all ports in the system. Run portCfgShow to display a list of Action ports currently configured as N_Port(s). Ensure that the host is connected to an F_port. Severity ERROR AG-1019 Message <timestamp>, [AG-1019], <sequence-number>,, WARNING, <system-name>, Unable to failover N_Port <port>.

  • Page 83: Ag-1023

    AG-1023 Probable Cause Indicates that the specified F_Port is failing over to its preferred N_Port. Recommended Please run ag --mapshow to display the updated F_Port to N_Port mapping. Action Severity INFO AG-1023 Message <timestamp>, [AG-1023], <sequence-number>,, INFO, <system-name>, F_Port <fport> mapped to offline N_Port <nport>...
  • Page 84 Fabric OS Message Reference 53-1000600-01...

  • Page 85: Auth-1001

    Chapter AUTH System Messages AUTH-1001 Message <timestamp>, [AUTH-1001], <sequence-number>,, INFO, <system-name>, <Operation type> has been successfully completed. Probable Cause Indicates that the secret database operation has been updated using the secAuthSecret command. The values for Operation type can be “set” or “remove”. Recommended No action is required.

  • Page 86: Auth-1004

    AUTH-1004 AUTH-1004 Message <timestamp>, [AUTH-1004], <sequence-number>,, ERROR, <system-name>, Failed to set <data type> type to <setting value>. Probable Cause Indicates that the authUtil command has failed to set the authentication configuration value. The data type is either “authentication type”, “DH group type”, or “policy type”. Recommended Retry the authUtil command.

  • Page 87: Auth-1008

    AUTH-1008 Recommended Run the authUtil command to make sure the local switch supports the specified protocols: Fibre Action channel authentication protocol (FCAP) or Diffie Hellman - challenge handshake authentication protocol (DH-CHAP). Severity ERROR AUTH-1008 Message <timestamp>, [AUTH-1008], <sequence-number>,, ERROR, <system-name>, No security license, operation failed.

  • Page 88: Auth-1012

    AUTH-1012 AUTH-1012 Message <timestamp>, [AUTH-1012], <sequence-number>,, WARNING, <system-name>, Authentication <code> is rejected: port <port number> explain <explain code> reason <reason code>. Probable Cause Indicates that an authentication is rejected because the remote entity does not support authentication. Recommended Make sure the entity at the other end of the link supports authentication. Action Severity WARNING...

  • Page 89: Auth-1017

    AUTH-1017 Probable Cause This may relate to an internal failure. Recommended Copy the message, collect switch information using the supportShow command, and contact your Action switch service provider. Severity ERROR AUTH-1017 Message <timestamp>, [AUTH-1017], <sequence-number>,, ERROR, <system-name>, Invalid value to start authentication request: port <port number>, operation code <operation code>.

  • Page 90: Auth-1022

    AUTH-1022 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity INFO AUTH-1022 Message <timestamp>, [AUTH-1022], <sequence-number>,, ERROR, <system-name>, Failed to extract <data type> from <message> payload: port <port number>. Probable Cause Indicates that the authentication process failed to extract a particular value from the receiving payload.

  • Page 91: Auth-1025

    AUTH-1025 Severity ERROR AUTH-1025 Message <timestamp>, [AUTH-1025], <sequence-number>,, ERROR, <system-name>, Failed to get <data type> during <authentication phase>: port <port number>. Probable Cause Indicates that the authentication process failed to get the expected information during the specified authentication phase. Recommended Usually this problem is transient.

  • Page 92: Auth-1028

    AUTH-1028 Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1028...

  • Page 93: Auth-1031

    AUTH-1031 Probable Cause Indicates the receiving payload does not have valid message code for a particular authentication phase. Recommended Usually this problem is transient. The authentication might fail. Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.

  • Page 94: Auth-1034

    AUTH-1034 Probable Cause Indicates that an entity was not configured in the switch connection control (SCC) policy and tried to connect to the port. Recommended Add the entity's world-wide name (WWN) to the SCC policy and reinitialize authentication by using Action the portDisable and portEnable commands or the switchDisable and switchEnable commands.

  • Page 95: Auth-1037

    AUTH-1037 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1037 Message <timestamp>, [AUTH-1037], <sequence-number>,, ERROR, <system-name>, Failed to <operation type> response for <authentication message>: init_len <data length>, resp_len <data length>, port <port number>.

  • Page 96: Auth-1040

    AUTH-1040 Recommended Correct the switch policy configuration on either of the switches using the authUtil command, and Action then enable the port using the portEnable command. Severity ERROR AUTH-1040 Message <timestamp>, [AUTH-1040], <sequence-number>,, INFO, <system-name>, Reject authentication on port <Port Number>, because switch authentication policy is set to OFF.

  • Page 97: Auth-1043

    AUTH-1043 Recommended Check the connection port for a possible security attack. Action Check the shared secrets using secAuthSecret and reinitialize authentication using the portDisable and portEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
  • Page 98 AUTH-1044 Fabric OS Message Reference 53-1000600-01...

  • Page 99: Bksw-1003

    Chapter BKSW System Messages BKSW-1003 Message <timestamp>, [BKSW-1003], <sequence-number>,, WARNING, <system-name>, kSWD: <warning message>. Probable Cause Indicates a warning state within the system. A critical application error was reported in the watchdog subsystem. This message is used to convey information that might be of interest to the customer regarding the state of the system. Refer to the string at the end of the error message for specific information.
  • Page 100 BKSW-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 101: Bl-1000

    Chapter BL System Messages BL-1000 Message <timestamp>, [BL-1000], <sequence-number>,, INFO, <system-name>, Initializing ports... Probable Cause Indicates that the switch has started initializing the ports. Recommended No action is required. Action Severity INFO BL-1001 Message <timestamp>, [BL-1001], <sequence-number>,, INFO, <system-name>, Port initialization completed.

  • Page 102: Bl-1003

    BL-1003 Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Additional blade fault messages precede and follow this error, providing more information. See other error messages for recommended action. If the message persists, replace the blade. Severity CRITICAL BL-1003 Message...

  • Page 103: Bl-1007

    BL-1007 Probable Cause Indicates that the errors (mostly synchronization errors) on this blade are harmless. Probably, the standby control processor (CP) blade connected to the active CP blade has experienced transitory problems. Recommended Use the haShow command to verify that the standby CP is healthy. If the standby CP was removed Action or faulted by user intervention, no action is required.

  • Page 104: Bl-1010

    BL-1010 Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, reboot or power cycle the blade. Run the systemVerification command to verify that the blade does not have hardware problems. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these commands.

  • Page 105: Bl-1012

    BL-1012 BL-1012 Message <timestamp>, [BL-1012], <sequence-number>,, ERROR, <system-name>, bport <port number> port int. is disabled. status=0x<interrupt status> Port <port number> will be re-enabled in 1 minute. Probable Cause Indicates that the port generated an excessive number of interrupts that might prove unrecoverable to the switch operation.

  • Page 106: Bl-1015

    BL-1015 Recommended Make sure to capture the console output during this process. Action On a bladed switch, run the slotPowerOff and slotPowerOn commands. On a nonbladed switch, reboot the switch. Run the systemVerification command to determine if there is a hardware error. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled.

  • Page 107: Bl-1017

    BL-1017 Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, reboot or power cycle the blade. Run the systemVerification command to verify that the blade does not have hardware problems. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these commands.

  • Page 108: Bl-1020

    BL-1020 BL-1020 Message <timestamp>, [BL-1020], <sequence-number>,, CRITICAL, <system-name>, Switch timed out initializing the chips. Probable Cause Indicates that the switch has failed to initialize the application-specific integrated circuit (ASIC) chips. Recommended Reboot or power cycle the switch. Action Run the systemVerification command to verify that the switch does not have hardware problems. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled.

  • Page 109: Bl-1023

    BL-1023 BL-1023 Message <timestamp>, [BL-1023], <sequence-number>,, CRITICAL, <system-name>, Blade in <slot number> slot was reset before blade init completed. As a result the blade is faulted. Probable Cause Indicates that the blade was reset before the initialization completed. Recommended Reboot or power cycle the blade. Action If the message persists, replace the blade.

  • Page 110: Bl-1027

    BL-1027 Recommended Collect supportSave information, then reboot switch and run the diagPost command to ensure Action Power-On Self-Test (POST) is enabled. If problem persists, replace switch. Severity CRITICAL BL-1027 Message <timestamp>, [BL-1027], <sequence-number>,, CRITICAL, <system-name>, Blade in slot <slot number> faulted, boot failed; status 0x<boot status> 0x<1250 0 boot status>...

  • Page 111: Bl-1030

    BL-1030 BL-1030 Message <timestamp>, [BL-1030], <sequence-number>,, INFO, <system-name>, All GigE/FCIP Virtualization/FC Fastwrite ports on the switch will be reset as part of the firmware upgrade. Probable Cause Indicates that a recent firmware upgrade caused the switch's internal processor firmware to be upgraded and resulted in the cold upgrade.

  • Page 112: Bl-1034

    BL-1034 Probable Cause Indicates that the system timed out while waiting for disable messages from the user ports after disabling the ports. Recommended Reboot or power cycle the blade. Run the systemVerification command to verify that the blade does Action not have hardware problems.

  • Page 113: Bll-1000

    Chapter BLL System Messages BLL-1000 Message <timestamp>, [BLL-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, ASIC driver detected Slot <slot number> port <port number> as faulty (reason: <reason>) Probable Cause Indicates that a blade regulation problem was reported on the specified slot number. The blade is faulted.
  • Page 114 BLL-1000 If the message persists, replace the blade. Severity CRITICAL Fabric OS Message Reference 53-1000600-01...

  • Page 115: Bm-1001

    Chapter BM System Messages BM-1001 Message <timestamp>, [BM-1001], <sequence-number>,, ERROR, <system-name>, BM protocol version <Protocol version> in slot <Slot number>. Probable Cause Indicates that the software running on the CP cannot communicate with the AP blade in the indicated slot, in order to determine AP blade's firmware version. This can be due to one of the following: •...

  • Page 116: Bm-1004

    BM-1004 Recommended Use the slotPowerOff and slotPowerOn commands or reseat the affected blade. Action Severity WARNING BM-1004 Message <timestamp>, [BM-1004], <sequence-number>,, INFO, <system-name>, Blade firmware <Blade firmware> on slot <Slot> is not consistent with system firmware <System firmware>. Auto-leveling blade firmware to match system firmware. Probable Cause The policy of the specified blade is to auto-level the blade firmware to the system firmware.The inconsistency may be due to either of the following reasons:...

  • Page 117: Bm-1007

    BM-1007 BM-1007 Message <timestamp>, [BM-1007], <sequence-number>,, INFO, <system-name>, Clearing <Slot number>. EX/VEX/FC port configuration for all ports for blade in slot Probable Cause The specified blade was detected for the first time after an FR4-18i was previously configured in the same slot. The new blade requires the specified port configurations to be cleared. Recommended The blade ports are cleared automatically.

  • Page 118: Bm-1053

    BM-1053 Severity INFO BM-1053 Message <timestamp>, [BM-1053], <sequence-number>,, WARNING, <system-name>, Failed to establish connection between CP and Application Processor. Faulting switch. Probable Cause The control processor (CP) could not establish a connection to the application processor to communicate. Recommended On the Brocade 7500 or 7600, switch off and on all primary power to power-cycle the unit. Action Severity WARNING...

  • Page 119: Bm-1058

    BM-1058 Probable Cause The policy of the specified switch is to persistently disable all ports the first time the application processor (AP) blade is detected. This may be cause by one of the following: • The AP was detected for the first time on this switch. •...
  • Page 120 BM-1058 Fabric OS Message Reference 53-1000600-01...

  • Page 121: C2-1001

    Chapter C2 System Messages C2-1001 Message <timestamp>, [C2-1001], <sequence-number>,, ERROR, <system-name>, Port <port number> port fault (the configured speed may not be supported by the SFP). Please change the SFP or check the cable. Probable Cause Indicates a deteriorated SFP, an incompatible SFP pair, or a faulty cable between the peer ports. Recommended Verify that you are using compatible SFPs on the peer ports.

  • Page 122: C2-1005

    C2-1005 C2-1005 Message <timestamp>, [C2-1005], <sequence-number>,, ERROR, <system-name>, Rate limit configuration is not effective on S(<slot number>) user port <port number> because QoS license is not present. Probable Cause Indicates that the switch does not have the QoS license added. Rate Limit is a licensed feature and requires QoS license.

  • Page 123: Cdr-1001

    Chapter CDR System Messages CDR-1001 Message <port <timestamp>, [CDR-1001], <sequence-number>,, ERROR, <system-name>, Port number> port fault. Please change the SFP or check cable Probable Cause Indicates a deteriorated small form-factor pluggable (SFP), an incompatible SFP pair, a faulty cable between peer ports, or the port speed configuration does not match the capability of the SFP. Recommended Verify that you are using compatible SFPs on the peer ports.

  • Page 124: Cdr-1004

    CDR-1004 Severity CRITICAL CDR-1004 Message <timestamp>, [CDR-1004], <sequence-number>, FFDC, ERROR, <system-name>, <slot number>, <chip index>: invalid DMA ch pointer, chan:<Channel number>, good_addr:0x<Good address>, bad_addr:0x<Bad address>. Probable Cause Indicates an internal error in the application specific integrated circuit (ASIC) hardware that may degrade data traffic.

  • Page 125: Cer-1001

    Chapter CER System Messages CER-1001 Message <timestamp>, [CER-1001], <sequence-number>,, ERROR, <system-name>, HA Sync broken, since standby Advanced Performance Tuning module does not support FICON Management Server (FMS). Probable Cause Indicates that the high-availability (HA) synchronization between the active and standby control processors (CPs) is broken, because there is downlevel firmware loaded on the standby CP.
  • Page 126 CER-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 127: Conf-1000

    Chapter CONF System Messages CONF-1000 Message <timestamp>, [CONF-1000], <sequence-number>, AUDIT, INFO, <system-name>, <Info about the parameters and AD> configDownload completed successfully. Probable Cause Indicates that the configDownload operation was initiated and completed successfully. The message string that follows is a description of the class of configuration parameters that were downloaded.

  • Page 128: Conf-1021

    CONF-1021 CONF-1021 Message <timestamp>, [CONF-1021], <sequence-number>,, INFO, <system-name>, configUpload <AD Number if AD is configured on the system> not permitted Probable Cause There are many possible causes. Recommended Check the error log for a possible cause. Please correct the error and upload the configuration Action again.

  • Page 129: Em-1001

    Chapter EM System Messages EM-1001 Message <FRU <timestamp>, [EM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, ID> is over heating: Shutting down. Probable Cause Indicates that a field-replaceable unit (FRU) is shutting down due to overheating. This is typically due to a faulty fan but can also be caused by the switch environment. Recommended Verify that the location temperature is within the operational range of the switch.

  • Page 130: Em-1004

    EM-1004 Run the systemVerification command to verify that the switch does not have hardware problems. Refer to the Fabric OS Command Reference for more information on this command. On the Brocade 24000 and 48000, replace the specified FRU. For the Brocade 3900, replace the motherboard FRU. For the Brocade 200E, 3016, 3250, 3850, 4012, 4016, 4018, 4020, 4024, 4100, 4900, 5000, 7500, and AP7600, replace the switch.

  • Page 131: Em-1006

    EM-1006 EM-1006 Message <FRU <timestamp>, [EM-1006], <sequence-number>, FFDC, CRITICAL, <system-name>, Id> has faulted. Sensor(s) below minimum limits. Probable Cause Indicates that the sensors show the voltage is below minimum limits. The switch or specified blade is being shut down for environmental reasons; the voltage is too low. Recommended If this problem occurs on a blade, it usually indicates a hardware problem on the blade;...

  • Page 132: Em-1009

    EM-1009 EM-1009 Message <FRU <timestamp>, [EM-1009], <sequence-number>, FFDC, CRITICAL, <system-name>, Id> powered down unexpectedly. Probable Cause Indicates that the environmental monitor (EM) received an unexpected power-down notification from the specified field-replaceable unit (FRU). This might indicate a hardware malfunction in the FRU.

  • Page 133: Em-1012

    EM-1012 EM-1012 Message <timestamp>, [EM-1012], <sequence-number>, FFDC, CRITICAL, <system-name>, <FRU Id> failed <state> state transition, FRU faulted. Probable Cause Indicates that a switch blade or nonbladed switch failed to transition from one state to another. It is faulted. The specific failed target state is displayed in the message. There are serious internal Fabric OS configuration or hardware problems on the switch.

  • Page 134: Em-1015

    EM-1015 EM-1015 Message <timestamp>, [EM-1015], <sequence-number>,, WARNING, <system-name>, Warm recovery <Return code> failed ( Probable Cause Indicates that a problem was discovered when performing consistency checks during a warm boot. Recommended Monitor the switch. If the problem persists, a reBoot or power cycle is required to resolve the Action problem.

  • Page 135: Em-1018

    EM-1018 EM-1018 Message <timestamp>, [EM-1018], <sequence-number>, FFDC, CRITICAL, <system-name>, CP blade in slot <slot number> failed to retrieve current chassis type (<detailed fault descriptor>/<PLACE HOLDER>/0x<PLACE HOLDER>). Probable Cause Indicates that there was a failure to read the chassis type from the system. Recommended Verify that the control processor (CP) blade is operational and is properly seated in its slot.

  • Page 136: Em-1029

    EM-1029 EM-1029 Message <timestamp>, [EM-1029], <sequence-number>,, WARNING, <system-name>, <FRU Id>, a problem occurred accessing a device on the I2C bus (<error code>). Operational status (<state of the FRU when the error occurred>) not changed, access is being retried. Probable Cause Indicates that the I2C bus had problems and a timeout occurred.

  • Page 137: Em-1034

    EM-1034 EM-1034 Message <timestamp>, [EM-1034], <sequence-number>,, ERROR, <system-name>, <FRU Id> set to faulty, rc=<return code>. Probable Cause Indicates that the specified field-replaceable unit (FRU) has been marked as faulty for the specified reason. Recommended Try reseating the FRU. Action Run the systemVerification command to verify that the switch does not have hardware problems. Refer to the Fabric OS Command Reference for more information on this command.

  • Page 138: Em-1036

    EM-1036 EM-1036 Message <FRU Id> <timestamp>, [EM-1036], <sequence-number>,, WARNING, <system-name>, not accessible. Probable Cause Indicates that the specified field-replaceable unit (FRU) does not seem to be present on the switch. If the FRU is a world-wide name (WWN) card, then default WWN and IP addresses are used for the switch.

  • Page 139: Em-1042

    EM-1042 EM-1042 Message <timestamp>, [EM-1042], <sequence-number>,, WARNING, <system-name>, Important FRU <FRU Id> header data for is not valid). Probable Cause Indicates that the specified field-replaceable unit (FRU) has an incorrect number of sensors in its FRU header-derived information. This could mean that the FRU header was corrupted or read incorrectly or corrupted in the object database, which contains information about all FRUs.

  • Page 140: Em-1045

    EM-1045 EM-1045 Message <timestamp>, [EM-1045], <sequence-number>,, WARNING, <system-name>, <FRU Id> is being powered <new state>. Probable Cause Indicates that an automatic power adjustment is being made because of the (predicted) failure of a power supply or the insertion or removal of a port blade. If new_state is On, a port blade is being powered on because more power is available (either a power supply was inserted or a port blade was removed or powered down).

  • Page 141: Em-1048

    EM-1048 EM-1048 Message <timestamp>, [EM-1048], <sequence-number>,, INFO, <system-name>, <FRU Id> I2C access recovered: state <current state> Probable Cause Indicates that the I2C bus problems have been resolved and I2C access to the field-replaceable unit (FRU) has become available again. Recommended The EM-1029 error can be a transitory error;...

  • Page 142: Em-1055

    EM-1055 Severity INFO EM-1055 Message <timestamp>, [EM-1055], <sequence-number>,, WARNING, <system-name>, <FRU Id>: Port media incompatible. Reason: <Reason for incompatibility> Probable Cause Indicates that an incompatible port media is detected. The possible causes are: • The port media is not capable of running at the configured port speed. •...

  • Page 143: Em-1058

    EM-1058 EM-1058 Message <timestamp>, [EM-1058], <sequence-number>,, WARNING, <system-name>, Switch gets <Fault reason> reset: Probable Cause The switch is automatically reset due to known resetable transient errors, such as an application-specific integrated circuit.(ASIC) parity. error. Recommended No action is required if the switch does not reach the reset threshold for the switch/blade. If the Action reset threshold is reached on the switch/blade, the switch/blade will be faulted and should be replaced.

  • Page 144: Em-1062

    EM-1062 Recommended Please remove all blades of this type or upgrade your standby CP. Once an appropriate action is Action taken, this CP must be rebooted or haSyncStart must be run successfully. Until this is done, the system will remain out of synchronization. Severity WARNING EM-1062...

  • Page 145: Em-1065

    EM-1065 EM-1065 Message <timestamp>, [EM-1065], <sequence-number>,, CRITICAL, <system-name>, SAS Virtualization Services are not available due to incompatiblity between the FOS and SAS versions <Slot number or blank for single board systems>. Probable Cause The version of either the control processor firmware (CFOS) or the blade processor firmware (BFOS) is not compatible with the Storage Application Services (SAS) or other application firmware version(s).
  • Page 146 EM-2003 Fabric OS Message Reference 53-1000600-01...

  • Page 147: Ess-1001

    Chapter ESS System Messages ESS-1001 Message <timestamp>, [ESS-1001], <sequence-number>,, WARNING, <system-name>, A few switches in the fabric do not support the Coordinated HotCode protocol. Probable Cause One or more switches in the fabric do not support the Coordinated HotCode protocol. Continuing with the firmware download may cause data traffic disruption.

  • Page 148: Ess-1004

    ESS-1004 ESS-1004 Message <timestamp>, [ESS-1004], <sequence-number>,, WARNING, <system-name>, The resume message is rejected by the domain <domain id>. Probable Cause During the Coordinated HotCode protocol, a switch in the fabric has rejected the resume message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been due to the rejected resume message.

  • Page 149: Evmd-1001

    Chapter EVMD System Messages EVMD-1001 Message <timestamp>, [EVMD-1001], <sequence-number>,, WARNING, <system-name>, Event could <Remote proxy switch id.> not be sent to remote proxy. = Probable Cause The event could not be sent to the remote proxy because the remote proxy switch cannot be reached through in-band.
  • Page 150 EVMD-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 151: Fabr-1001

    Chapter FABR System Messages FABR-1001 Message <timestamp>, [FABR-1001], <sequence-number>,, WARNING, <system-name>, port <port number>, <segmentation reason>. Probable Cause Indicates that the specified switch port is isolated because of a segmentation due to mismatched configuration parameters. Recommended Based on the segmentation reason displayed within the message, look for a possible mismatch of Action relevant configuration parameters in the switches at both ends of the link.

  • Page 152: Fabr-1004

    FABR-1004 Run the fabStateShow command on both the receiving and transmitting switches. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1004 Message <timestamp>, [FABR-1004], <sequence-number>,, WARNING, <system-name>, port: <port number>, req iu: 0x<address of IU request sent>, state: 0x<command sent>, resp iu:...

  • Page 153: Fabr-1007

    FABR-1007 Recommended In case of severe memory corruption, the system might recover by performing an automatic Action failover. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1007...

  • Page 154: Fabr-1010

    FABR-1010 Recommended The fabric daemon will discard the EFP. The system will recover through the EFP retrial process. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1010...

  • Page 155: Fabr-1013

    FABR-1013 FABR-1013 Message <timestamp>, [FABR-1013], <sequence-number>, FFDC, CRITICAL, <system-name>, No Memory: pid=<fabric process id> file=<source file name> line=<line number within the source file>. Probable Cause Indicates that there is not enough memory in the switch for the fabric module to allocate. This message is rare and usually indicates a problem with the Fabric OS.

  • Page 156: Fabr-1016

    FABR-1016 FABR-1016 Message <timestamp>, [FABR-1016], <sequence-number>,, WARNING, <system-name>, ficonMode is enabled. Probable Cause Indicates that FICON mode is enabled on the switch through a user interface command. Recommended No action is required. Action Severity WARNING FABR-1017 Message <timestamp>, [FABR-1017], <sequence-number>,, WARNING, <system-name>, ficonMode is disabled.

  • Page 157: Fabr-1019

    FABR-1019 FABR-1019 Message <timestamp>, [FABR-1019], <sequence-number>, FFDC, CRITICAL, <system-name>, Critical fabric size (<current domains>) exceeds supported configuration (<supported domains>). Probable Cause Indicates that this switch is a value-line switch and has exceeded the limited fabric size: that is, a specified limit to the number of domains. This limit is defined by your specific value-line license key. The fabric size has exceeded this specified limit, and the grace period counter has started.

  • Page 158: Fabr-1022

    FABR-1022 FABR-1022 Message <timestamp>, [FABR-1022], <sequence-number>, FFDC, CRITICAL, <system-name>, Fabric size (<actual domains>) exceeds supported configuration (<supported domains>). Fabric limit timer (<type>) started from <grace period in seconds>. Probable Cause Indicates that the fabric size has exceeded the value-line limit, and the grace period counter has started.

  • Page 159: Fabr-1029

    FABR-1029 FABR-1029 Message <timestamp>, [FABR-1029], <sequence-number>,, INFO, <system-name>, Port <port number> negotiated <flow control mode description> (mode = <received flow control mode>). Probable Cause Indicates that a different flow control mode, as described in the message, is negotiated with the port at the other end of the link.

  • Page 160: Fabr-1032

    FABR-1032 FABR-1032 Message <timestamp>, [FABR-1032], <sequence-number>, FFDC, WARNING, <system-name>, Remote switch with domain ID <domain ID>and switchname <switchname>running an unsupported FOS version v2.x has joined the fabric. Probable Cause Indicates that a switch with an unsupported Fabric OS version 2.x has joined the fabric. Recommended Remove the switch with the unsupported Fabric OS version 2.x from the fabric.

  • Page 161: Fabs-1001

    Chapter FABS System Messages FABS-1001 Message <timestamp>, [FABS-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Description of memory need> Probable Cause Indicates that the system is low on memory and cannot allocate more memory for new operations. This is usually an internal Fabric OS problem or file corruption. Description of memory need indicates how much memory was being requested.

  • Page 162: Fabs-1005

    FABS-1005 FABS-1005 Message <timestamp>, [FABS-1005], <sequence-number>,, WARNING, <system-name>, <Function name and description of problem> (<ID type>= <ID number>) Probable Cause Indicates that an unsupported operation has been requested. This is usually an internal Fabric OS problem or file corruption. The possible values for function name and description of problem are: fabsys_write: Unsupported write operation: process xxx where "xxx"...

  • Page 163: Fabs-1007

    FABS-1007 FABS-1007 Message <timestamp>, [FABS-1007], <sequence-number>,, WARNING, <system-name>, <Function name>: Media state is invalid - status=<Status value> Probable Cause Indicates that the Fabric OS has detected an invalid value in an object's status field. This is usually an internal Fabric OS problem or file corruption. Recommended Reboot or power cycle the switch.

  • Page 164: Fabs-1010

    FABS-1010 FABS-1010 Message <timestamp>, [FABS-1010], <sequence-number>,, WARNING, <system-name>, <Function name>: Wrong media_event <Event number> Probable Cause Indicates that the Fabric OS detected an unknown event type. This is usually an internal Fabric OS problem or file corruption. Recommended Reboot or power cycle the switch. Action If the message persists, run the firmwareDownload command to update the firmware.

  • Page 165: Fabs-1013

    FABS-1013 FABS-1013 Message <timestamp>, [FABS-1013], <sequence-number>,, ERROR, <system-name>, <Method name>[<Method tag number>]:Unknown blade type 0x<Blade type> Probable Cause An unrecognized type of blade has been discovered in the system. This may be caused by an incorrect FRU header, inability to read the FRU header, or the blade may not be supported by this platform or Fabric OS version.
  • Page 166 FABS-1015 Fabric OS Message Reference 53-1000600-01...

  • Page 167: Fbc-1001

    Chapter FBC System Messages FBC-1001 Message <timestamp>, [FBC-1001], <sequence-number>,, ERROR, <system-name>, Firmware version on AP blade is incompatible with that on the CP. Probable Cause The CP determined that the version of firmware running on the AP blade is not compatible with the version of firmware running on the CP.
  • Page 168 FBC-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 169: Fcip-1000

    Chapter FCIP System Messages FCIP-1000 Message <timestamp>, [FCIP-1000], <sequence-number>, FFDC, ERROR, <system-name>, <command name> of GE <port number> failed. Please retry the command. Data: inst=<ASIC instance> st=<ASIC initializing state> rsn=<reason code> fn=<message function> oid=<ASIC ID> Probable Cause Indicates that the hardware is not responding to a command request; possibly because it is busy. Recommended Retry the command.
  • Page 170 FCIP-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 171: Fcmc-1001

    Chapter FCMC System Messages FCMC-1001 Message <timestamp>, [FCMC-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, System is low on memory and has failed to allocate new memory. Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for an information unit (IU).
  • Page 172 FCMC-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 173: Fcpd-1001

    Chapter FCPD System Messages FCPD-1001 Message <timestamp>, [FCPD-1001], <sequence-number>,, WARNING, <system-name>, Probing <error string>. failed on Probable Cause Indicates that a fibre channel protocol (FCP) switch probed devices on a loop port, and the probing failed on the either the L_Port, AL_PA address, or the F_Port. For the AL_PA, the valid range is 00 through FF.
  • Page 174 FCPD-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 175: Fcph-1001

    Chapter FCPH System Messages FCPH-1001 Message <timestamp>, [FCPH-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <function>: <failed function call> failed, out of memory condition Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for a Fibre Channel driver instance.
  • Page 176 FCPH-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 177: Ficon System Messages

    Chapter FICON System Messages The FICON messages in this chapter include in many of the messages. The FICON <FICON Path> Path is a string that includes, where: VEHDHPDDDPLPCUDV VE - VE Port Number: This number represents the FCIP Tunnel number through its VE Port number.

  • Page 178: Ficn-1003

    FICN-1003 FICN-1003 Message <timestamp>, [FICN-1003], <sequence-number>,, WARNING, <system-name>, FICON Tape Emulation License Key is not installed. Probable Cause FICON Tape Emulation requires a License Key. Recommended Use the appropriate License Key. Action Severity WARNING FICN-1004 Message <timestamp>, [FICN-1004], <sequence-number>,, WARNING, <system-name>, FICON XRC Emulation License Key is not installed.

  • Page 179: Ficn-1007

    FICN-1007 Probable Cause The FCIP Tunnel ID associated with the FICON tunnel must be down or disabled for a feature change to become effective. Recommended Disable the applicable FCIP tunnel to make the feature change effective. Action Severity WARNING FICN-1007 Message <timestamp>, [FICN-1007], <sequence-number>,, ERROR, <system-name>, DevDiskEgr:FICON Selective Reset:Path=<FICON PATH>...

  • Page 180: Ficn-1010

    FICN-1010 FICN-1010 Message <timestamp>, [FICN-1010], <sequence-number>,, INFO, <system-name>, DevDiskEgr:Device level exception flag found for Path=<FICON PATH>: Oxid=0x<FC OXID value from the received Device Level Exception frame>. Probable Cause A Device Level Exception frame received from the FICON Channel. Recommended If there was a job or IO failure associated with this event, please contact your vendor's customer Action support for assistance.

  • Page 181: Ficn-1014

    FICN-1014 Recommended If there was a job or IO failure associated with this event, please contact your vendor's customer Action support for assistance. Severity INFO FICN-1014 Message <timestamp>, [FICN-1014], <sequence-number>,, INFO, <system-name>, DevEgr:Device level exception flag found for Path=<FICON PATH>: Oxid=0x<The OXID used to deliver the non-AS Device Level Exception>.

  • Page 182: Ficn-1018

    FICN-1018 Probable Cause The FICON Control Unit sent a LPE frame to the FICON channel. Recommended This is an informational message and does not require any action. Action Severity INFO FICN-1018 Message <timestamp>, [FICN-1018], <sequence-number>,, ERROR, <system-name>, DevIng:FCUB Lookup failed for Path=<FICON PATH>. Probable Cause The FICON Control Unit sent a frame that cannot be associated with a FICON Control Unit CUADDR.

  • Page 183: Ficn-1021

    FICN-1021 FICN-1021 Message <timestamp>, [FICN-1021], <sequence-number>,, ERROR, <system-name>, DevTapeEgr:FICON Tape Cancel:Path=<FICON PATH> Elapsed Time=<the current SIO time in seconds for the device>.<the current SIO time in milliseconds for the device> seconds. Probable Cause The FICON channel issued a Cancel sequence for a device in emulation. Recommended If there was an unexpected job failure associated with this event, please contact your vendor's Action...

  • Page 184: Ficn-1025

    FICN-1025 Recommended If there was an unexpected job failure or IO Error associated with this event, please contact your Action vendor's customer support for assistance. Severity ERROR FICN-1025 Message <timestamp>, [FICN-1025], <sequence-number>,, ERROR, <system-name>, DevTapeIng:Auto Sense Data received on Path=<FICON PATH> Bytes0-0xB=0x<FICON device Sense Data bytes 0-11>.

  • Page 185: Ficn-1029

    FICN-1029 Probable Cause An active emulation device received a cancel operation from the FICON channel. Recommended If there was an unexpected job failure or IO Error associated with this event, please contact your Action vendor's customer support for assistance. Severity ERROR FICN-1029 Message...

  • Page 186: Ficn-1033

    FICN-1033 Probable Cause The XRC System Data mover was restarted to discover the capabilities of the channel extension equipment. Recommended No action is required. This is a part of the XRC initialization. Action Severity INFO FICN-1033 Message <timestamp>, [FICN-1033], <sequence-number>,, INFO, <system-name>, HostEgr:Logical Path Established on Path=<FICON PATH>.

  • Page 187: Ficn-1036

    FICN-1036 FICN-1036 Message <timestamp>, [FICN-1036], <sequence-number>,, INFO, <system-name>, HostIng:FICON RLP Request on Path=<FICON PATH>. Probable Cause A locally connected FICON Channel issued a Remove Logical Path sequence to the specified FICON Control Unit. Recommended No action is required. This is a part of the FICON path deactivation. Action Severity INFO...

  • Page 188: Ficn-1040

    FICN-1040 FICN-1040 Message <timestamp>, [FICN-1040], <sequence-number>,, ERROR, <system-name>, HostTapeEgr:Tape:CmdReject Sense Data Rcvd:Path=<FICON PATH> LastCmds=0x<Last 4 commands received from the channel for this device> SenseData:Bytes0-0xB=0x<FICON device Sense Data bytes 0-11>. Probable Cause An active disk emulation device received a FICON Purge Path from the channel. Recommended If there was an unexpected job failure or IO Error associated with this event, please contact your Action...

  • Page 189: Ficn-1044

    FICN-1044 Probable Cause Protocol errors in emulation in the CU or network errors can cause Selective Reset. Recommended If this was an unexpected event, please contact your vendor's customer support for assistance. Action Severity ERROR FICN-1044 Message <timestamp>, [FICN-1044], <sequence-number>,, ERROR, <system-name>, HostTapeIng:FICON Selective Reset:Path=<FICON PATH>...

  • Page 190: Ficn-1047

    FICN-1047 FICN-1047 Message <timestamp>, [FICN-1047], <sequence-number>,, ERROR, <system-name>, fcFicSetEmulation:Path=<FICON PATH> FDCB Not Idle state=0x<Current emulation state of the FICON device> prevState=0x<Previous emulation state of the FICON device> set to state=0x<The new state to which the device is transitioning>. Probable Cause This is an internal emulation error and should not be encountered.

  • Page 191: Ficn-1051

    FICN-1051 Recommended This is an unexpected event, please contact your vendor's customer support for assistance. Action Severity WARNING FICN-1051 Message <timestamp>, [FICN-1051], <sequence-number>,, INFO, <system-name>, XRC Session Established: SessID=<SDM Assigned Session ID>, Path=<FICON PATH>. Probable Cause An establish XRC session PSF command has been received to initiate an XRC session with the extended DASD device.

  • Page 192: Ficn-1055

    FICN-1055 Probable Cause A suspend from XRC session PSF command has been received to break an XRC session with the extended DASD device. Recommended If this was an unexpected event, please contact your vendor's customer support for assistance. Action Severity WARNING FICN-1055 Message...

  • Page 193: Ficn-1058

    FICN-1058 FICN-1058 Message <timestamp>, [FICN-1058], <sequence-number>,, ERROR, <system-name>, Error return from frame generation processing for a FICON control unit: Path=<FICON PATH>. Probable Cause An internal resource shortage caused error such that an emulation frame could not be created and sent to a Control Unit. Recommended This is an unexpected event, please contact your vendor's customer support for assistance.

  • Page 194: Ficn-1062

    FICN-1062 FICN-1062 Message <timestamp>, [FICN-1062], <sequence-number>,, ERROR, <system-name>, Ingress Abort:Oxid=0x<the OXID of the aborted exchange>:Path=<FICON PATH>:LastStates=0x<emulation state>. Probable Cause An abort operation has been received from the local FC interface for an active emulation exchange. Recommended This is an unexpected event, please contact your vendor's customer support for assistance. Action Severity ERROR...

  • Page 195: Ficn-1066

    FICN-1066 Recommended If there were associated IO errors at the same time as this event, please contact your vendor's Action customer support for assistance. Severity INFO FICN-1066 Message <timestamp>, [FICN-1066], <sequence-number>,, WARNING, <system-name>, MemAllocFailed for GEPort=<GE0 or GE1 Number> VEport=<VEPortNumber> could not create required structure.

  • Page 196: Ficn-1070

    FICN-1070 Probable Cause An error has been noted in the FICON configuration. Please refer to the string for the nature of the configuration issue. Recommended If resolution of the configuration issue cannot be completed, please contact your vendor's Action customer support for assistance. Severity ERROR FICN-1070...

  • Page 197: Ficn-1073

    FICN-1073 FICN-1073 Message <timestamp>, [FICN-1073], <sequence-number>,, INFO, <system-name>, HostTapeIngr:Unloaded:Path=<FICON PATH>:states=0x<4 prior emulation states>:cmds=0x<last 4 commands received from the channel for this device>:status=0x<last 4 status values sent to the channel for this device>:flags=0x<tape report bit flags>. Probable Cause A Rewind and Unload IO has been processed from a locally connected LPAR, which indicates that a tape should be unloaded on a device.

  • Page 198: Ficn-1076

    FICN-1076 FICN-1076 Message <timestamp>, [FICN-1076], <sequence-number>,, INFO, <system-name>, HostTapeIngr:ReadCpReport:Path=<FICON PATH>:Emuls=0x<the number of idle state to non-idle state transitions while this tape was loaded>:Cmds=0x<the number of emulated host read commands processed while this tape was loaded>:Chains=0x<the number of emulated host chains processed while this tape was loaded>:MBytes=<the number of emulated read megabytes processed while this tape was loaded>.

  • Page 199: Ficn-1079

    FICN-1079 FICN-1079 Message <timestamp>, [FICN-1079], <sequence-number>,, INFO, <system-name>, DevTapeEgr:WriteReport:Path=<FICON PATH>:Emuls=0x<the number of idle state to non-idle state transitions while this tape was loaded>:Cmds=0x<the number of emulated host read commands processed while this tape was loaded>:Chains=0x<the number of emulated host chains processed while this tape was loaded>:MBytes=<the number of emulated read Kilobytes processed while this tape was loaded>.

  • Page 200: Ficn-1082

    FICN-1082 FICN-1082 Message <timestamp>, [FICN-1082], <sequence-number>,, WARNING, <system-name>, EmulEls:CSWR_RSCN received on GEPort=<GEPortNumber> VEPort=<VEPortNumber> Domain=0x<Domain Port Host> Port=0x<Device Side>. Probable Cause An attached port which had an FICON emulated path established has logged out from the switch. Recommended This may be an unexpected event, please contact your vendor's customer support for assistance. Action Severity WARNING...

  • Page 201: Ficn-1086

    FICN-1086 FICN-1086 Message <timestamp>, [FICN-1086], <sequence-number>,, ERROR, <system-name>, FICON FCIP Tunnel is Down on GE<Either GE0 or GE1>,tunnel Id=<The configured tunnel ID (0-7)>. Probable Cause A FICON FCIP tunnel has been terminated to the peer switch. Recommended If this is an unexpected event, please contact your vendor's customer support for assistance. Action Severity ERROR...
  • Page 202 FICN-1086 Fabric OS Message Reference 53-1000600-01...

  • Page 203: Ficu-1001

    Chapter FICU System Messages FICU-1001 Message <timestamp>, [FICU-1001], <sequence-number>,, ERROR, <system-name>, <function name>: config<config Set(key)|Get(key)| Save> failed rc = <error>. Probable Cause Indicates that one of the configuration management functions failed. The key variable is part of the Fabric OS configuration database and is for support use only. The error variable is an internal error number.

  • Page 204: Ficu-1004

    FICU-1004 Severity WARNING FICU-1004 Message <timestamp>, [FICU-1004], <sequence-number>,, WARNING, <system-name>, <function name>: Failed to set fabric manager server (FMS) mode: conflicting PID Format:<pid_format>, FMS Mode:<mode>. Probable Cause Indicates that a process ID (PID) format conflict was encountered. The core PID format is required for fibre connectivity control unit port (FICON-CUP).

  • Page 205: Ficu-1007

    FICU-1007 Recommended Check if the FICON channel corresponding to the PID in the message is functioning correctly. Action Severity WARNING FICU-1007 Message <timestamp>, [FICU-1007], <sequence-number>,, WARNING, <system-name>, <function name>: Failed to allocate memory while performing <message>. Probable Cause Indicates that memory resources are low. This might be a transient problem. Recommended If the message persists, check the memory usage on the switch, using the memShow command.

  • Page 206: Ficu-1010

    FICU-1010 FICU-1010 Message <timestamp>, [FICU-1010], <sequence-number>,, WARNING, <system-name>, FMS Mode <port number>. enable failed due to address conflict with port Probable Cause Indicates that the fibre connectivity FICON Management Server mode (fmsMode) was not enabled because the specified port has an address conflict with the CUP management port is in use. Recommended Use the portDisable command to disable the specified port to avoid the port address conflict.

  • Page 207: Fklb-1001

    Chapter FKLB System Messages FKLB-1001 Message <timestamp>, [FKLB-1001], <sequence-number>,, WARNING, <system-name>, exchange <xid> overlapped, pid=<pid> Probable Cause Indicates that the FC kernel driver has timed out the exchange while the application is still active. When the FC kernel driver reuses the exchange, the application will overlap. This happens on a timed-out exchange;...
  • Page 208 FKLB-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 209: Flod-1001

    Chapter FLOD System Messages FLOD-1001 Message <timestamp>, [FLOD-1001], <sequence-number>, FFDC, WARNING, <system-name>, Unknown LSR type: port <port number>, type <LSR header type> Probable Cause Indicates that the link state record (LSR) type is unknown. 1-Unicast and 3-Multicast are the only two LSR header types.

  • Page 210: Flod-1005

    FLOD-1005 FLOD-1005 Message <timestamp>, [FLOD-1005], <sequence-number>,, WARNING, <system-name>, Invalid <domain number> received domain ID: Probable Cause Indicates that the received LSR contained an invalid domain number. Recommended No action is required; the LSR is discarded. Action Severity WARNING FLOD-1006 Message <timestamp>, [FLOD-1006], <sequence-number>,, WARNING, <system-name>, <domain number>...

  • Page 211: Fspf-1001

    Chapter FSPF System Messages FSPF-1001 Message <timestamp>, [FSPF-1001], <sequence-number>,, ERROR, <system-name>, Input Port <port number> out of range Probable Cause Indicates that the specified input port number is out of range; it does not exist on the switch. Recommended No action is required. Action Severity ERROR...

  • Page 212: Fspf-1005

    FSPF-1005 FSPF-1005 Message <timestamp>, [FSPF-1005], <sequence-number>,, ERROR, <system-name>, Wrong Section Id <section number>, should be <section number>, input port = <port number> Probable Cause Indicates that an incorrect section ID was reported from the specified input port. The section ID is used to identify a set of switches that share an identical topology database.

  • Page 213: Fss-1001

    Chapter FSS System Messages FSS-1001 Message <timestamp>, [FSS-1001], <sequence-number>,, WARNING, <system-name>, Component (<component name>) dropping HA data update (<update ID>). Probable Cause Indicates that an application has dropped a high availability (HA) data update. Recommended Run the haSyncStart command if this is a dual-CP system, or reboot the switch if it is a nonbladed Action system.

  • Page 214: Fss-1003

    FSS-1003 FSS-1003 Message <timestamp>, [FSS-1003], <sequence-number>,, WARNING, <system-name>, Component (<component name>) misused the update transaction (<transaction ID>) without marking the transaction beginning. Probable Cause Indicates that the Fabric OS state synchronization (FSS) service has dropped the update because an application has not set the transaction flag correctly. Recommended Run the haSyncStart command if this is a dual-CP system, or reboot the switch if it is a nonbladed Action...

  • Page 215: Fss-1006

    FSS-1006 FSS-1006 Message <timestamp>, [FSS-1006], <sequence-number>,, WARNING, <system-name>, No FSS message available Probable Cause Indicates that data is not available on the Fabric OS state synchronization (FSS) device. Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the Action supportSave command and contact your switch service provider.
  • Page 216 FSS-1007 Fabric OS Message Reference 53-1000600-01...

  • Page 217: Fssm-1002

    Chapter FSSM System Messages FSSM-1002 Message <timestamp>, [FSSM-1002], <sequence-number>,, INFO, <system-name>, HA State is in sync. Probable Cause Indicates that the high availability (HA) state for the active control processor (CP) is in synchronization with the HA state of the standby CP. If the standby CP is healthy, then a failover is nondisruptive.

  • Page 218: Fssm-1004

    FSSM-1004 FSSM-1004 Message <timestamp>, [FSSM-1004], <sequence-number>,, INFO, <system-name>, Incompatible software version in HA synchronization. Probable Cause Indicates that the active control processor (CP) and the standby CP in a dual CP system are running firmware that are incompatible with each other. If the active CP fails, the failover will be disruptive. In a non-bladed system, this message is logged when the firmware upgrade/downgrade was invoked.

  • Page 219: Fw-1001

    Chapter FW System Messages FW-1001 Message <timestamp>, [FW-1001], <sequence-number>,, INFO, <system-name>, <label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the internal temperature of the switch has changed. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.

  • Page 220: Fw-1003

    FW-1003 FW-1003 Message <timestamp>, [FW-1003], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the internal temperature of the switch has risen above the high boundary to a value that might damage the switch.

  • Page 221: Fw-1006

    FW-1006 FW-1006 Message <timestamp>, [FW-1006], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the speed of the fan has fallen below the low boundary. Fan problems typically contribute to temperature problems. Recommended Consistently abnormal fan speeds generally indicate that the fan is failing.

  • Page 222: Fw-1009

    FW-1009 FW-1009 Message <timestamp>, [FW-1009], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the state of the power supply has changed from faulty to functional, or from functional to faulty. Recommended If the power supply is functioning correctly, no action is required.

  • Page 223: Fw-1012

    FW-1012 FW-1012 Message <timestamp>, [FW-1012], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the power supply counter changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 224: Fw-1035

    FW-1035 FW-1035 Message <timestamp>, [FW-1035], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the temperature of the small form-factor pluggable (SFP) has risen above the high boundary. Frequent fluctuations in temperature might indicate a deteriorating SFP. Recommended Replace the SFP.

  • Page 225: Fw-1038

    FW-1038 FW-1038 Message <timestamp>, [FW-1038], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the receive power value of the small form-factor pluggable (SFP) has fallen below the low boundary. The receive performance area measures the amount of incoming laser to help you determine if the SFP is in good working condition or not.

  • Page 226: Fw-1041

    FW-1041 FW-1041 Message <timestamp>, [FW-1041], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has changed. The transmit performance area measures the amount of outgoing laser to help you determine if the SFP is in good working condition or not.

  • Page 227: Fw-1044

    FW-1044 FW-1044 Message <timestamp>, [FW-1044], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 228: Fw-1047

    FW-1047 FW-1047 Message <timestamp>, [FW-1047], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has risen above the high boundary. The supplied current of the SFP transceiver is outside of the normal range, indicating possible hardware failure.

  • Page 229: Fw-1050

    FW-1050 FW-1050 Message <timestamp>, [FW-1050], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has fallen below the low boundary. Recommended Configure the low threshold to 1 so that the threshold triggers an alarm when the value falls to 0 Action...

  • Page 230: Fw-1113

    FW-1113 FW-1113 Message <timestamp>, [FW-1113], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of times E_Ports have gone down has changed. E_Ports go down each time you remove a cable or small form-factor pluggable (SFP). SFP failures also cause E_Ports to go down.

  • Page 231: Fw-1116

    FW-1116 FW-1116 Message <timestamp>, [FW-1116], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of times E_Ports have gone down has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 232: Fw-1118

    FW-1118 FW-1118 Message <timestamp>, [FW-1118], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of fabric reconfigurations has fallen below the low boundary. The following occurrences can cause a fabric reconfiguration: •...

  • Page 233: Fw-1120

    FW-1120 FW-1120 Message <timestamp>, [FW-1120], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of fabric reconfigurations has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 234: Fw-1123

    FW-1123 FW-1123 Message <timestamp>, [FW-1123], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of domain ID changes has risen above the high boundary. Domain ID changes occur when there is a conflict of domain IDs in a single fabric and the principal switch has to assign another domain ID to the switch.

  • Page 235: Fw-1126

    FW-1126 FW-1126 Message <timestamp>, [FW-1126], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of segmentations has fallen below the low boundary. Segmentation changes might occur due to: •...

  • Page 236: Fw-1128

    FW-1128 FW-1128 Message <timestamp>, [FW-1128], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of segmentations has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 237: Fw-1131

    FW-1131 FW-1131 Message <timestamp>, [FW-1131], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of zone changes has risen above the high boundary. Zone changes occur when there is a change to the effective zone configuration. Recommended No action is required.

  • Page 238: Fw-1134

    FW-1134 FW-1134 Message <timestamp>, [FW-1134], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of fabric logins has fallen below the low boundary. Fabric logins occur when a port or device initializes with the fabric. The event is called a fabric login or FLOGI. A low number of fabric logins means that the fabric is functioning normally.

  • Page 239: Fw-1137

    FW-1137 FW-1137 Message <timestamp>, [FW-1137], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of small form-factor pluggable (SFP) state changes has changed. SFP state changes occur when the SFP is inserted or removed. Recommended No action is required.

  • Page 240: Fw-1140

    FW-1140 FW-1140 Message <timestamp>, [FW-1140], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of small form-factor pluggable (SFP) state changes has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 241: Fw-1162

    FW-1162 FW-1162 Message <timestamp>, [FW-1162], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of link failures that the port experiences has risen above the high boundary.

  • Page 242: Fw-1165

    FW-1165 Severity INFO FW-1165 Message <timestamp>, [FW-1165], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of synchronization losses that the port experiences has fallen below the low boundary.

  • Page 243: Fw-1168

    FW-1168 FW-1168 Message <timestamp>, [FW-1168], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of signal losses that the port experiences has changed. Loss of signal generally indicates a physical problem.

  • Page 244: Fw-1171

    FW-1171 FW-1171 Message <timestamp>, [FW-1171], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of signal losses that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 245: Fw-1174

    FW-1174 FW-1174 Message <timestamp>, [FW-1174], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of protocol errors that the port experiences has risen above the high boundary.

  • Page 246: Fw-1177

    FW-1177 FW-1177 Message <timestamp>, [FW-1177], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid words that the port experiences has fallen below the low boundary.

  • Page 247: Fw-1180

    FW-1180 FW-1180 Message <timestamp>, [FW-1180], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has changed. Recommended No action is required.

  • Page 248: Fw-1183

    FW-1183 FW-1183 Message <timestamp>, [FW-1183], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 249: Fw-1186

    FW-1186 FW-1186 Message <timestamp>, [FW-1186], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the percentage of incoming traffic that the port experiences has risen above the high boundary.

  • Page 250: Fw-1189

    FW-1189 FW-1189 Message <timestamp>, [FW-1189], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the percentage of outgoing traffic that the port experiences has fallen below the low boundary.

  • Page 251: Fw-1192

    FW-1192 FW-1192 Message <timestamp>, [FW-1192], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of state changes that the port experiences has changed. The state of the port has changed for one of the following reasons: the port has gone offline, has come online, is testing, is faulty, has become an E_Port, has become an F_Port, has segmented, or has become a trunk port.

  • Page 252: Fw-1195

    FW-1195 FW-1195 Message <timestamp>, [FW-1195], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of state changes that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 253: Fw-1218

    FW-1218 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Severity INFO FW-1218 Message <timestamp>, [FW-1218], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.

  • Page 254: Fw-1240

    FW-1240 FW-1240 Message <timestamp>, [FW-1240], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) cyclic redundancy check (CRC) errors has changed. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change.

  • Page 255: Fw-1243

    FW-1243 FW-1243 Message <timestamp>, [FW-1243], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) cyclic redundancy check (CRC) errors has changed from a value outside of the acceptable range to a value within the acceptable range. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change.

  • Page 256: Fw-1246

    FW-1246 FW-1246 Message <timestamp>, [FW-1246], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch receives has risen above the high boundary. Receive performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.

  • Page 257: Fw-1249

    FW-1249 FW-1249 Message <timestamp>, [FW-1249], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch transmits has fallen below the low boundary. Transmit performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.

  • Page 258: Fw-1272

    FW-1272 FW-1272 Message <timestamp>, [FW-1272], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of frame types or commands that the port receives has changed. The port has received small computer system interface (SCSI) Read, SCSI Write, SCSI Read and Write, SCSI Traffic, or IP commands in a frame.

  • Page 259: Fw-1275

    FW-1275 FW-1275 Message <timestamp>, [FW-1275], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of frame types or commands that the port receives has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 260: Fw-1298

    FW-1298 FW-1298 Message <timestamp>, [FW-1298], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of telnet violations has risen above the high boundary. Telnet violations indicate that a telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of internet protocol (IP) addresses that are authorized to establish telnet connections to switches in the fabric.

  • Page 261: Fw-1301

    FW-1301 FW-1301 Message <timestamp>, [FW-1301], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of hypertext transfer protocol (HTTP) violations has fallen below the low boundary. HTTP violations indicate that a browser connection request has been received from an unauthorized IP address.

  • Page 262: Fw-1304

    FW-1304 FW-1304 Message <timestamp>, [FW-1304], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of application programming interface (API) violations has changed. API violations indicate that an API connection request has been received from an unauthorized IP address.

  • Page 263: Fw-1307

    FW-1307 FW-1307 Message <timestamp>, [FW-1307], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of application programming interface (API) violations has changed from a value outside of the acceptable range to a value within the acceptable range. API violations indicate that an API connection request has been received from an unauthorized IP address.

  • Page 264: Fw-1310

    FW-1310 FW-1310 Message <timestamp>, [FW-1310], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of simple network management protocol read (RSNMP) violations has risen above the high boundary. RSNMP violations indicate that an SNMP “get” operation request has been received from an unauthorized IP address.

  • Page 265: Fw-1313

    FW-1313 FW-1313 Message <timestamp>, [FW-1313], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of simple network management protocol write (WSNMP) violations has fallen below the low boundary. WSNMP violations indicate that an SNMP “get/set” operation request has been received from an unauthorized IP address.

  • Page 266: Fw-1316

    FW-1316 FW-1316 Message <timestamp>, [FW-1316], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of SES violations has changed. SES violations indicate that an small computer system interface (SCSI) Enclosure Services (SES) request has been received from an unauthorized world-wide name (WWN).

  • Page 267: Fw-1319

    FW-1319 FW-1319 Message <timestamp>, [FW-1319], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of SES violations has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 268: Fw-1322

    FW-1322 FW-1322 Message <timestamp>, [FW-1322], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of simple network management server (MS) violations has risen above the high boundary. MS violations indicate that a MS access request has been received from an unauthorized world-wide name (WWN).

  • Page 269: Fw-1325

    FW-1325 FW-1325 Message <timestamp>, [FW-1325], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of serial violations has fallen below the low boundary. Serial violations indicate that an unauthorized serial port request has been received. The SERIAL_POLICY contains a list of switch world-wide names (WWNs) for which serial port access is enabled.

  • Page 270: Fw-1328

    FW-1328 FW-1328 Message <timestamp>, [FW-1328], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of front panel violations has changed. Front panel violations indicate that an unauthorized front panel request has been received. The FRONTPANEL_POLICY contains a list of switch world-wide names (WWNs) for which front panel access is enabled.

  • Page 271: Fw-1331

    FW-1331 FW-1331 Message <timestamp>, [FW-1331], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of front panel violations has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 272: Fw-1334

    FW-1334 FW-1334 Message <timestamp>, [FW-1334], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of switch connection control policy (SCC) violations has risen above the high boundary. SCC violations indicate that an unauthorized switch tried to join the fabric. The SCC_POLICY contains a list of switches by world-wide names (WWNs) that are allowed to be members of a fabric.

  • Page 273: Fw-1337

    FW-1337 FW-1337 Message <timestamp>, [FW-1337], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of device cable connection (DCC) violations has fallen below the low boundary. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically host bus adaptor (HBA) ports) to specific switch ports.

  • Page 274: Fw-1339

    FW-1339 FW-1339 Message <timestamp>, [FW-1339], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of device cable connection (DCC) violations has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 275: Fw-1342

    FW-1342 FW-1342 Message <timestamp>, [FW-1342], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of login violations has risen above the high boundary. Login violations indicate that a login failure has been detected. Recommended Run the errShow command to determine the IP location of the login attempt.

  • Page 276: Fw-1345

    FW-1345 FW-1345 Message <timestamp>, [FW-1345], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid timestamps has fallen below the low boundary. Invalid-timestamp violations indicate a packet with an invalid timestamp has been received from the primary world-wide name (WWN).

  • Page 277: Fw-1347

    FW-1347 FW-1347 Message <timestamp>, [FW-1347], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid timestamps has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 278: Fw-1349

    FW-1349 FW-1349 Message <timestamp>, [FW-1349], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid signatures has fallen below the low boundary. Invalid-signature violations indicate that a packet with an invalid signature has been received from the primary fabric configuration server (FCS).

  • Page 279: Fw-1351

    FW-1351 FW-1351 Message <timestamp>, [FW-1351], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid signatures has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 280: Fw-1353

    FW-1353 FW-1353 Message <timestamp>, [FW-1353], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid certificates has fallen below the low boundary. This violation indicates that a packet with an invalid certificate has been received from the primary fabric configuration server (FCS).

  • Page 281: Fw-1355

    FW-1355 FW-1355 Message <timestamp>, [FW-1355], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid certificates has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 282: Fw-1358

    FW-1358 FW-1358 Message <timestamp>, [FW-1358], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of authentication failures has risen above the high boundary. Authentication failures can occur for many reasons. The switch on the other side might not support the protocol, have an invalid certificate, not be signed properly or send unexpected packets.

  • Page 283: Fw-1361

    FW-1361 FW-1361 Message <timestamp>, [FW-1361], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of switch link authentication protocol (SLAP) faulty packets has fallen below the low boundary. This counter keeps track of the number of unexpected SLAP packets and SLAP packets with faulty transmission IDs.

  • Page 284: Fw-1364

    FW-1364 FW-1364 Message <timestamp>, [FW-1364], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of time service (TS) out-of-sync violations has changed. Recommended Responses to security-class messages depend on user policies. Consult your security administrator Action for response strategies and policies.

  • Page 285: Fw-1367

    FW-1367 FW-1367 Message <timestamp>, [FW-1367], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of time service (TS) out-of-sync violations has changed from a value outside of the acceptable range to a value within the acceptable range.

  • Page 286: Fw-1370

    FW-1370 FW-1370 Message <timestamp>, [FW-1370], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of no-FCS violations has risen above the high boundary. This counter records how often the switch loses contact with the primary fabric configuration server (FCS) switch.

  • Page 287: Fw-1373

    FW-1373 Severity INFO FW-1373 Message <timestamp>, [FW-1373], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of incompatible security database violations has fallen below the low boundary. This violation indicates the number of secure switches with different version stamps have been detected.

  • Page 288: Fw-1376

    FW-1376 Recommended No action is required. Action Severity INFO FW-1376 Message <timestamp>, [FW-1376], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of illegal commands has changed. This counter tracks how many times commands allowed only on the primary fabric configuration server (FCS) switch have been executed on a non-primary FCS switch.

  • Page 289: Fw-1379

    FW-1379 Probable Cause Indicates that the number of illegal commands has risen above the high boundary. This counter tracks how many times commands allowed only on the primary fabric configuration server (FCS) switch have been executed on a non-primary FCS switch. There are many commands that can be executed only on the primary FCS switch as well as one security command that can be executed only on a backup FCS switch.

  • Page 290: Fw-1402

    FW-1402 Probable Cause Indicates that the flash usage percentage has fallen below the low boundary. Flash increases and decreases slightly with normal operation of the switch. Excessive permanent increases can lead to future problems. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.

  • Page 291: Fw-1425

    FW-1425 FW-1425 Message <timestamp>, [FW-1425], <sequence-number>,, INFO, <system-name>, Switch status <Bad state> changed from to HEALTHY. Probable Cause Indicates that the switch status has changed to a healthy state. This occurred because a policy is no longer violated. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.

  • Page 292: Fw-1428

    FW-1428 FW-1428 Message <timestamp>, [FW-1428], <sequence-number>,, WARNING, <system-name>, Switch status <Number Missing> change contributing factor Power supply: absent. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of missing power supplies is greater than or equal to the policy set by the switchStatusPolicySet command.

  • Page 293: Fw-1431

    FW-1431 FW-1431 Message <timestamp>, [FW-1431], <sequence-number>,, WARNING, <system-name>, Switch status <Number Bad> change contributing factor Fan: bad. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty fans is greater than or equal to the policy set by the switchStatusPolicySet command. A fan is faulty when sensor value is not in the acceptable range or is faulty.

  • Page 294: Fw-1434

    FW-1434 FW-1434 Message <timestamp>, [FW-1434], <sequence-number>,, WARNING, <system-name>, Switch status <Number Bad> change contributing factor Blade: blade failures. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of blade failures is greater than or equal to the policy set by the switchStatusPolicySet command. Recommended Replace the faulty blade.

  • Page 295: Fw-1437

    FW-1437 FW-1437 Message <timestamp>, [FW-1437], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor faulty ports: <Num of faulty ports>. (Port(s) <unknown>. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty ports is greater than or equal to the policy set by the switchStatusPolicySet command.

  • Page 296: Fw-1440

    FW-1440 FW-1440 Message <timestamp>, [FW-1440], <sequence-number>,, INFO, <system-name>, <FRU label> state has changed to <FRU state>. Probable Cause Indicates that the state of the specified field-replaceable unit (FRU) has changed to “absent”. Recommended No action is required. Verify that the event was planned. Action Severity INFO...

  • Page 297: Fw-1444

    FW-1444 FW-1444 Message <timestamp>, [FW-1444], <sequence-number>,, WARNING, <system-name>, <FRU label> state has changed to <FRU state>. Probable Cause Indicates that the state of the specified field-replaceable unit (FRU) has changed to “faulty”. Recommended Replace the FRU. Action Severity WARNING FW-1445 Message <timestamp>, [FW-1445], <sequence-number>,, INFO, <system-name>, Four power supplies are now required for 2X redundancy, Switch Status Policy values changed.

  • Page 298: Fw-1500

    FW-1500 FW-1500 Message <timestamp>, [FW-1500], <sequence-number>,, WARNING, <system-name>, Mail overflow - Alerts being discarded. Probable Cause Indicates that mail alert overflow condition has occurred. Recommended Resolve or disable the mail alert using the fwMailCfg command. Action Severity WARNING FW-1501 Message <timestamp>, [FW-1501], <sequence-number>,, INFO, <system-name>, Mail overflow <Mails discarded>...

  • Page 299: Ham-1001

    Chapter HAM System Messages HAM-1001 Message <timestamp>, [HAM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Standby CP is not healthy, device <device name> status BAD, Severity = <Log="YES" Class="NONE" Severity> Probable Cause Indicates that a standby control processor (CP) device error is reported by the high-availability manager (HAM) Health Monitor, with a specific device and Log="YES”...

  • Page 300: Ham-1005

    HAM-1005 • Unknown • Fastboot • Giveup Master:SYSM • CP Faulty:SYSM • FirmwareDownload • ConfigDownload:MS • ChangeWWN:EM • Reboot:WebTool • Fastboot:WebTool • Software Fault:Software Watchdog • Software Fault:Kernel Panic • Software Fault:ASSERT • Reboot:SNMP • Fastboot:SNMP • Reboot • Chassis Config •...
  • Page 301 HAM-1006 Recommended The standby CP will take over and reset the active CP.The system will be non-redundant as the Action standby becomes the active CP. Severity CRITICAL Fabric OS Message Reference 53-1000600-01...
  • Page 302 HAM-1006 Fabric OS Message Reference 53-1000600-01...

  • Page 303: Hamk-1001

    Chapter HAMK System Messages HAMK-1001 Message <timestamp>, [HAMK-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Warm recovery failed. Probable Cause The switch failed in the warm recovery. Recommended This message triggers a switch reboot automatically and attempts a cold recovery. RUn supportFtp Action (as needed) to set up automatic FTP transfers;...

  • Page 304: Hamk-1004

    HAMK-1004 HAMK-1004 Message <timestamp>,[HAMK-1004], <sequence-number>,, INFO, <system-name>, Resetting standby CP (double reset may occur). Probable Cause Indicates that the standby control processor (CP) is being reset due to a loss of heartbeat. This message is typically seen when the standby CP has been rebooted. Note that in certain circumstances a CP may experience a double reset and reboot twice in a row.

  • Page 305: Hil-1101

    Chapter HIL System Messages HIL-1101 Message <timestamp>, [HIL-1101], <sequence-number>,, ERROR, <system-name>, Slot <slot number> faulted, <nominal voltage> (<measured voltage>) is above threshold. Probable Cause Indicates that the blade voltage is above the threshold. Recommended Replace the faulty blade or switch (for nonbladed switches). Action Severity ERROR...

  • Page 306: Hil-1104

    HIL-1104 HIL-1104 Message <timestamp>, [HIL-1104], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, <nominal voltage> (<measured voltage>) is below threshold. Probable Cause Indicates that the fan voltage is below the threshold. Recommended Run the psShow command to verify the power supply status. Action Try to reseat the faulty fan field-replaceable unit (FRU) and power supply FRU to verify that they are seated properly.

  • Page 307: Hil-1107

    HIL-1107 HIL-1107 Message <timestamp>, [HIL-1107], <sequence-number>,, ERROR, <system-name>, Switch faulted, <nominal voltage> (<measured voltage>)above threshold. Probable Cause Indicates that the switch voltage is above threshold. This message is specific to nonbladed switches and is not applicable to the Brocade 24000, or 48000. Recommended For the Brocade 200E, 3250, 3850, 4012, 4016, 4018, 4020, and 4024 the entire switch must be Action...

  • Page 308: Hil-1202

    HIL-1202 If the fan continues to generate this message, replace the fan field-replaceable unit (FRU). Severity WARNING HIL-1202 Message <timestamp>, [HIL-1202], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, speed (<measured speed> RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. Recommended Replace the fan field-replaceable unit (FRU).

  • Page 309: Hil-1206

    HIL-1206 HIL-1206 Message <timestamp>, [HIL-1206], <sequence-number>,, ERROR, <system-name>, Fan <fan number> sensor <sensor number> , speed (<measured speed> RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. This problem can quickly cause the switch to overheat. This message is specific to nonbladed switches and is not applicable to the Brocade 24000, or 48000.

  • Page 310: Hil-1301

    HIL-1301 HIL-1301 Message <timestamp>, [HIL-1301], <sequence-number>,, WARNING, <system-name>, 1 blower failed or missing. Replace failed or missing blower assembly immediately. Probable Cause Indicates that a fan field-replaceable unit (FRU) has failed or has been removed. This message is often preceded by a low speed error message. This problem can cause the switch to overheat. Recommended Replace the affected fan FRU immediately.

  • Page 311: Hil-1305

    HIL-1305 Severity ERROR HIL-1305 Message <timestamp>, [HIL-1305], <sequence-number>,, ERROR, <system-name>, One or two fan(s) failed. Replace failed fan FRUs immediately. Probable Cause Indicates that multiple fan field-replaceable units (FRUs) have failed. This message is often preceded by a low fan speed message. Recommended Replace the faulty fan FRUs immediately.

  • Page 312: Hil-1309

    HIL-1309 Recommended Replace the faulty fan field-replaceable units (FRUs) immediately. Action Severity ERROR HIL-1309 Message <count> <timestamp>, [HIL-1309], <sequence-number>,, ERROR, <system-name>, FRUs failed. Replace failed fan FRUs immediately. Probable Cause Indicates that multiple fans have failed. This message is often preceded by a low fan speed message.

  • Page 313: Hil-1402

    HIL-1402 Probable Cause Indicates that one fan field-replaceable unit (FRU) has been removed. Recommended Install the missing fan FRU. Action Severity WARNING HIL-1402 Message <timestamp>, [HIL-1402], <sequence-number>,, WARNING, <system-name>, Two fan FRUs missing. Install fan FRUs immediately. Probable Cause Indicates that two fan field-replaceable units (FRUs) have been removed. Recommended Install the missing fan FRUs immediately.

  • Page 314: Hil-1502

    HIL-1502 Recommended Run the fanShow command to verify all the fans are working properly. Action Make sure that the area is well ventilated and that the room temperature is within operational range of your switch. Refer to the hardware reference manual for your switch for the operational temperature range.

  • Page 315: Hil-1505

    HIL-1505 Recommended No action is required. Action Severity INFO HIL-1505 Message <timestamp>, [HIL-1505], <sequence-number>,, WARNING, <system-name>, High <measured temperature> temperature ( C) exceeds environmental specifications. Probable Cause Indicates that temperatures in the system have risen above the warning threshold. Recommended Run the fanShow command to verify all the fans are working properly.

  • Page 316: Hil-1508

    HIL-1508 HIL-1508 Message <timestamp>, [HIL-1508], <sequence-number>, FFDC, CRITICAL, <system-name>, Fan faulty warning time expired. System preparing for shutdown. Probable Cause Indicates that temperatures in the system have remained above the critical threshold too long. Recommended In order to avoid causing damage to the switch, the system shuts down automatically. To help Action prevent future problems, make sure that all the fans are working properly.

  • Page 317: Hil-1601

    HIL-1601 HIL-1601 Message <timestamp>, [HIL-1601], <sequence-number>,, ERROR, <system-name>, Using backup temperature sensor. Service immediately. Probable Cause Indicates that temperature readings from the primary sensor are out of range. Recommended Run the fanShow command to verify that all fans are operating correctly. Replace any deteriorating Action fan field-replaceable units (FRUs).
  • Page 318 HIL-1650 Severity ERROR Fabric OS Message Reference 53-1000600-01...

  • Page 319: Hlo-1001

    Chapter HLO System Messages HLO-1001 Message <timestamp>, [HLO-1001], <sequence-number>, FFDC, ERROR, <system-name>, Incompatible Inactivity timeout <dead timeout> from port <port number>, correct value <value>. Probable Cause Indicates that the HLO message was incompatible with the value specified in the FSPF protocol. The Brocade switch will not accept FSPF frames from the remote switch.
  • Page 320 HLO-1003 The switch has received an invalid HLO because either the domain or port number in the HLO message has an invalid value. This error can only occur when the Brocade switch is connected to a switch from another manufacturer. Recommended The HLO message of the remote switch must be compatible with the value specified in the FSPF Action...

  • Page 321: Hmon-1001

    Chapter HMON System Messages HMON-1001 Message <timestamp>, [HMON-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Failure description> Probable Cause Indicates that there was a problem reading an essential file containing configuration information from the nonvolatile storage device. This could be the result of a missing file or a corrupt file system.
  • Page 322 HMON-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 323: Http-1001

    Chapter HTTP System Messages HTTP-1001 Message <timestamp>, [HTTP-1001], <sequence-number>,, INFO, <system-name>, Switch <current PID format> PIDformat has changed to Probable Cause Indicates that the PID format was changed by the administrator. Recommended No action is required. For more information on PID, format refer to the Fabric OS Administrator’s Action Guide.
  • Page 324 HTTP-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 325: Ibd-1001

    Chapter IBD System Messages IBD-1001 Message <timestamp>, [FKLB-1001], <sequence-number>,, ERROR, <system-name>, Slot <slot number>, Port GE<port number>: Maximum attempts to restart failed. Disabling port. Probable Cause Indicates that the specified port has crashed unexpectedly and restarting attempts have failed. Recommended Power off and power on the blade using the slotPowerOff and slotPowerOn commands.
  • Page 326 IBD-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 327: Ibpd-1001

    Chapter IBPD System Messages IBPD-1001 Message <timestamp>, [IBPD-1001], <sequence-number>,, WARNING, <system-name>, <Function name>:<Line number> initiator name length exceeds the <Max length limit> character limit [<Initiator name>] Probable Cause Indicates that the initiator name length exceeds the supported limit of characters. Recommended Change the initiator name, keeping the number of characters within the supported limit.
  • Page 328 IBPD-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 329: Icpd-1001

    Chapter ICPD System Messages ICPD-1001 Message <timestamp>, [ICPD-1001], <sequence-number>,, ERROR, <system-name>, Failed to <function name> allocate memory: ( Probable Cause Indicates that the specified function failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Action Reboot or power cycle the switch.

  • Page 330: Icpd-1004

    ICPD-1004 ICPD-1004 Message <timestamp>, [ICPD-1004], <sequence-number>,, WARNING, <system-name>, iSNS Client service is detected on multiple switches in fabric. Probable Cause Indicates that iSNS Client service is enabled on multiple switches in fabric. Recommended Enable the iSNS Client service on a single switch in the fabric using the fosConfig command. Refer Action to the Fabric OS Command Reference for more information on this command.

  • Page 331: Icpd-1008

    ICPD-1008 ICPD-1008 Message <timestamp>, [ICPD-1008], <sequence-number>,, INFO, <system-name>, iSCSI switch (<domain id>) is <status>. Probable Cause Indicates that the iSCSI switch is reachable or unreachable. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-01...
  • Page 332 ICPD-1008 Fabric OS Message Reference 53-1000600-01...

  • Page 333: Ipad-1000

    Chapter IPAD System Messages IPAD-1000 Message <timestamp>, [IPAD-1000], <sequence-number>,, INFO, <system-name> <Type of managed entity> <Instance number of managed entity> <Type of network interface> <Instance number of network interface> <Protocol address family> <Source of address change> <Value of address and prefix> <DHCP enabled or not> Probable Cause Indicates that a change in local IP address has occurred.
  • Page 334 IPAD-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 335: Ips-1001

    Chapter IPS System Messages IPS-1001 Message <timestamp>, [IPS-1001], <sequence-number>,, WARNING, <system-name>, <message> FCIP License Not Installed (<error>) Probable Cause Indicates that the FCIP license is not installed on the switch. Recommended Run the licenseShow command to check the installed licenses on the switch. Contact your switch Action supplier for a FCIP license.

  • Page 336: Ips-1005

    IPS-1005 Probable Cause Indicates that configured Port Mode is different from intended use. Recommended Change the port configuration (by deleting configured FCIP tunnels or iSCSI sessions) to return the Action port mode to neutral before attempting to configure the port for a different mode or use. Severity WARNING IPS-1005...

  • Page 337: Iscs-1000

    Chapter ISCS System Messages ISCS-1000 Message <timestamp>, [ISCS-1000], <sequence-number>,, ERROR, <system-name>, Slot <slot number> Port GE<port number> crashed unexpectedly. Probable Cause Indicates that specified port has crashed. Recommended No action is required; the port will restart automatically. Action Severity ERROR Fabric OS Message Reference 53-1000600-01...
  • Page 338 ISCS-1000 Fabric OS Message Reference 53-1000600-01...

  • Page 339: Isns-1001

    Chapter ISNS System Messages ISNS-1001 Message <timestamp>, [ISNS-1001], <sequence-number>,, INFO, <system-name>, Configuration peering with external iSNS server <New config iSNS server IP address> slot/port <New config Slot number>/ge<New config port number> (current <Current iSNS server IP address> <Current slot number>/ge<Current port number>). Probable Cause Indicates that the user has issued the isnscCfg command.

  • Page 340: Isns-1004

    ISNS-1004 ISNS-1004 Message <timestamp>, [ISNS-1004], <sequence-number>,, WARNING, <system-name>, Timeout refreshing iSNS database with iSNS server <iSNS server IP address> slot/port <Slot number>/ge<Port number> Reg-Period <Registration-Period in seconds>. Probable Cause Indicates that the internet storage name service (iSNS) client failed to receive a successful response for a DevAttrQry within the specified Registration-Period.

  • Page 341: Isns-1008

    ISNS-1008 ISNS-1008 Message <timestamp>, [ISNS-1008], <sequence-number>,, INFO, <system-name>, Peering with external iSNS server <iSNS server IP address> not started because configuration unchanged. Probable Cause Indicates that peering with the external iSNS server was already started with the same configuration. Recommended No action is required.

  • Page 342: Isns-1013

    ISNS-1013 Severity INFO ISNS-1013 Message <timestamp>, [ISNS-1013], <sequence-number>,, WARNING, <system-name>, iSNS server connection failure. Probable Cause Indicates that the internet storage name service (iSNS) client failed to establish a connection with the iSNS server. Recommended Verify the connection of the iSNS server to the slot/port. Use the isnscCfg command to display or Action correct the server IP address.

  • Page 343: Fcr-1001

    Chapter FCR System Messages FCR-1001 Message <timestamp>, [FCR-1001], <sequence-number>,, INFO, <system-name>, FC router proxy <port number> device in edge created at port Probable Cause Indicates that a proxy device in the edge fabric has been imported at the specified port. Recommended No action is required.

  • Page 344: Fcr-1004

    FCR-1004 FCR-1004 Message <timestamp>, [FCR-1004], <sequence-number>,, INFO, <system-name>, FC router <port number> physical devices offline at port Probable Cause Indicates that one or more physical devices connected to the specified port have gone offline. Recommended Verify that the device(s) were intended to be taken offline. Action If not, verify that the devices are functioning properly.

  • Page 345: Fcr-1008

    FCR-1008 Severity INFO FCR-1008 Message <timestamp>, [FCR-1008], <sequence-number>,, INFO, <system-name>, FC router LSAN zone created at port <port number>. Probable Cause Indicates that a logical storage area network (LSAN) zone was created at the specified port in the edge fabric. Recommended No action is required.

  • Page 346: Fcr-1012

    FCR-1012 Recommended No action is required. Action Severity INFO FCR-1012 Message <timestamp>, [FCR-1012], <sequence-number>,, INFO, <system-name>, FC Router fabric build completed on port <port number>. Probable Cause Indicates that the fibre channel router has completed a fabric build at the specified port. Recommended No action is required.

  • Page 347: Fcr-1018

    FCR-1018 Recommended No action is required. Action Severity INFO FCR-1018 Message <timestamp>, [FCR-1018], <sequence-number>,, ERROR, <system-name>, FC router <port number> proxy device entries exhausted on port Probable Cause Indicates that the number of proxy devices is greater than allowed by the port resource. Recommended Remove excess logical storage area network (LSAN) zones or devices until the number of proxy Action...

  • Page 348: Fcr-1021

    FCR-1021 To do that, perform the following steps: 1. Run portDisable to disable all the EX_Ports that got this error message. 2. Run portDisable to disable all the other EX_Ports on that FCR connected to the same edge fabrics the EX_ports disabled in step 1 are connected to. 3.

  • Page 349: Fcr-1024

    FCR-1024 Recommended Limit the number of port WWNs required by limiting the remote edge fabric connectivity (which Action limits the number of translate domains). You can also limit the number of proxy devices for a translate domain (which limits the number of translate domain ports required) by limiting the devices specified in logical storage area network (LSAN) zones.

  • Page 350: Fcr-1027

    FCR-1027 FCR-1027 Message <timestamp>, [FCR-1027], <sequence-number>,, INFO, <system-name>, In slot <slot number> port WWN roll over. Probable Cause Indicates that the port world-wide name (WWN) pool has rolled over in the specified slot, and WWN entries detected to not be in use are reused as needed. Recommended It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed Action...

  • Page 351: Fcr-1030

    FCR-1030 To avoid WWN conflicts, all EX_Ports attached to fabrics with highly dynamic changes to EX_Port connectivity should be disabled then reenabled. Severity INFO FCR-1030 Message <timestamp>, [FCR-1030], <sequence-number>,, INFO, <system-name>, Physical device <device WWN> came online at fabric <fabric ID>. Probable Cause Indicates that the physical device world-wide name (WWN) came online in the specified fabric.

  • Page 352: Fcr-1034

    FCR-1034 Recommended No action is required. Action Severity INFO FCR-1034 Message <timestamp>, [FCR-1034], <sequence-number>,, INFO, <system-name>, LSAN zone added in backbone fabric. Probable Cause Indicates that a new logical storage area network (LSAN) zone was added to the backbone fabric. Recommended No action is required.

  • Page 353: Fcr-1038

    FCR-1038 Recommended No action is required. Action Severity INFO FCR-1038 Message <timestamp>, [FCR-1038], <sequence-number>,, WARNING, <system-name>, Total zone entries exceeded local fabric limits by <overflow> entries, in zone: <zone name>, zone limit: <LSAN zone limit>. Probable Cause Indicates that the number of cfg/zone/alias entries created in a local fabric is greater than the local switch's zone database limitations.

  • Page 354: Fcr-1042

    FCR-1042 Probable Cause Indicates that a logical storage area network (LSAN) zone device within the backbone fabric was removed. Recommended No action is required. Action Severity INFO FCR-1042 Message <timestamp>, [FCR-1042], <sequence-number>,, INFO, <system-name>, LSAN zone removed in the backbone fabric. Probable Cause Indicates that a logical storage area network (LSAN) zone within the backbone fabric was removed.

  • Page 355: Fcr-1049

    FCR-1049 FCR-1049 Message <port <timestamp>, [FCR-1049], <sequence-number>,, ERROR, <system-name>, EX port ( number> ) received an ELP command that is not supported. Probable Cause Indicates an incoming exchange link protocol (ELP) command was issued and it is not supported. Recommended Run the portEnable and portDisable commands to enable and disable the port.

  • Page 356: Fcr-1055

    FCR-1055 FCR-1055 Message <timestamp>, [FCR-1055], <sequence-number>,, INFO, <system-name>, Switch with <domain ID> domain ID does not support backbone to edge imports. Probable Cause Indicates that a switch that does not support backbone-to-edge routing was detected in the backbone. Edge-to-edge routing will work, but backbone-to-edge routing might fail. Recommended No action is required if backbone to edge routing is not required.

  • Page 357: Fcr-1059

    FCR-1059 Recommended Please check the switches on both ends of the link for a possible mismatch in switch or port Action configuration parameters such as Operating Mode, E_D_TOV, R_A_TOV, Domain ID Offset, etc. Run the portCfgExport command to modify the appropriate parameters on the local switch. Run the appropriate configuration command to modify the switch or port parameters on the remote switch.

  • Page 358: Fcr-1062

    FCR-1062 Recommended No action is required. Action Severity INFO FCR-1062 Message <timestamp>, [FCR-1062], <sequence-number>,, INFO, <system-name>, Port <port number> disabled, system only supports <maximum ports> EX/VEX_ports. Probable Cause Indicates that the maximum number of supported EX_ports or VEX_ports was exceeded. To enable the specified port, disable any other operational port then re-enable the port.

  • Page 359: Fcr-1066

    FCR-1066 Probable Cause Indicates that another port on the switch is connected to the same edge fabric with a different fabric ID assignment. Recommended Change the port fabric ID to same value as the other ports connected to the edge fabric using the Action portCfgExport or portCfgVexport commands.

  • Page 360: Fcr-1069

    FCR-1069 Severity INFO FCR-1069 Message <timestamp>, [FCR-1069], <sequence-number>,, INFO, <system-name>, The FC Routing service is enabled. Probable Cause Indicates that the FC Routing service is enabled. This is caused by either fosConfig –-enable fcr, or a configDownload with the fcrState set to 1 (enabled). Note that the FC Routing service is disabled by the factory.

  • Page 361: Fcr-1073

    FCR-1073 Recommended No action is required. Action Severity INFO FCR-1073 Message <timestamp>, [FCR-1073], <sequence-number>,, INFO, <system-name>, Switch with domain ID <domain ID> in fabric <fabric ID> has lower limit of LSAN Zones supported. Probable Cause Indicates that a switch in the backbone/edge that supports different limit of logical storage area network (LSAN) zones was detected.

  • Page 362: Fcr-1076

    FCR-1076 FCR-1076 Message <timestamp>, [FCR-1076], <sequence-number>,, ERROR, <system-name>, Port <port number> disabled, system only supports <maximum fds> front domains. Probable Cause Indicates that the maximum number of supported front domains was exceeded. To enable the specified port, disable any other operational front domain and then re-enable the port. Recommended Make sure to remain within the maximum of supported front domains.

  • Page 363: Kswd-1003

    Chapter KSWD System Messages KSWD-1003 Message <timestamp>, [KSWD-1003], <sequence-number>, FFDC, WARNING, <system-name>, kSWD: <Warning message>. Probable Cause Indicates a warning state within the system. A critical application error was reported in the watchdog subsystem. Refer to the string at the end of the error message for specific information.
  • Page 364 KSWD-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 365: Ktrc-1001

    Chapter KTRC System Messages KTRC-1001 Message <timestamp>, [KTRC-1001], <sequence-number>,, WARNING, <system-name>, Dump memory size exceeds dump file size Probable Cause Indicates that the dump memory size has exceeded the dump file size. Recommended No action is required. Action Severity WARNING KTRC-1002 Message <timestamp>, [KTRC-1002], <sequence-number>,, INFO, <system-name>, Concurrent...

  • Page 366: Ktrc-1005

    KTRC-1005 Recommended No action is required. Action Severity ERROR KTRC-1005 Message <timestamp>, [KTRC-1005], <sequence-number>,, ERROR, <system-name>, Trace initialization failed. <Reason initialization failed>. <Internal error code>. Probable Cause Indicates that Trace was unable to initialize. Recommended No action is required. Action Severity ERROR Fabric OS Message Reference...

  • Page 367: Log-1000

    Chapter LOG System Messages LOG-1000 Message <timestamp>, [LOG-1000], <sequence-number>,, INFO, <system-name>, Previous <repeat count> message repeated time(s) Probable Cause Indicates that the previous message repeated the specified number of times. Recommended No action is required. Action Severity INFO LOG-1001 Message <timestamp>, [LOG-1001], <sequence-number>, FFDC, WARNING, <system-name>, A log message was dropped Probable Cause...

  • Page 368: Log-1003

    LOG-1003 LOG-1003 Message <timestamp>, [LOG-1003], <sequence-number>,, INFO, <system-name>, The log has been cleared. Probable Cause Indicates that the persistent error log has been cleared. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-01...

  • Page 369: Lsdb-1001

    Chapter LSDB System Messages LSDB-1001 Message <timestamp>, [LSDB-1001], <sequence-number>,, ERROR, <system-name>, Link State ID <link state ID> out of range Probable Cause Indicates that the specified link state database ID is out of the acceptable range. The valid link state ID is the same as the valid domain ID, whose range is from 1 through 239. The switch will discard the record because it is not supported.

  • Page 370: Lsdb-1004

    LSDB-1004 Recommended Run the switchDisable and switchEnable commands. A new local link state record is generated Action during the switch enable. Severity CRITICAL LSDB-1004 Message <timestamp>, [LSDB-1004], <sequence-number>,, WARNING, <system-name>, No Link <local domain> State Record for domain Probable Cause Indicates that there is no link state record for the specified local domain.

  • Page 371: Mfic-1001

    Chapter MFIC System Messages MFIC-1001 Message <timestamp>, [MFIC-1001], <sequence-number>,, ERROR, <system-name>, failure at <failure reason> sysmod_scn registry rc= Probable Cause Indicates that the system is temporarily out of resources. Recommended No action is required; this message is often transitory. Action If the message persists, run a switch reboot or an haFailover (if applicable).

  • Page 372: Mfic-1003

    MFIC-1003 MFIC-1003 Message <timestamp>, [MFIC-1003], <sequence-number>,, WARNING, <system-name>, Effective Insistent domain ID for the fabric changed from <state> to <state> Probable Cause Indicates that one or more switches joined the fabric with a different insistent domain ID (IDID) mode setting than the current effective IDID mode for the fabric. This message also occurs when the IDID for the fabric has been turned on or off.

  • Page 373: Mpth-1001

    Chapter MPTH System Messages MPTH-1001 Message <timestamp>, [MPTH-1001], <sequence-number>, FFDC, ERROR, <system-name>, Null <number> parent, lsId = Probable Cause Indicates that a null parent was reported. MPATH uses a tree structure in which the parent is used to connect to the root of the tree. Recommended No action is required.
  • Page 374 MPTH-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 375: Mq-1004

    Chapter MQ System Messages MQ-1004 Message <timestamp>, [MQ-1004], <sequence-number>,, ERROR, <system-name>, mqRead, queue = <queue name>, queue ID = <queue ID>, type = <message type> Probable Cause Indicates that an unexpected message has been received in the specified message queue. The queue name is always fspf_q.
  • Page 376 MQ-1004 Fabric OS Message Reference 53-1000600-01...

  • Page 377: Ms-1001

    Chapter MS System Messages MS-1001 Message <timestamp>, [MS-1001], <sequence-number>,, WARNING, <system-name>, MS Platform Segmented port=<port number>(<reason for segmentation> <domain>) Probable Cause Indicates that the management server (MS) has segmented from another switch domain at the specified port number due to errors or inconsistencies defined in the MS platform service. Recommended Reboot or power cycle the switch.

  • Page 378: Ms-1003

    MS-1003 • <GCAP Rejected (reason =BUSY) by> Run the firmwareDownload command to upgrade the firmware level on the switch to a level that supports RCS. RCS is supported in Fabric OS v2.6, v3.1 and greater, and v4.1 and greater. • <Reject EXGPLDB from>...

  • Page 379: Ms-1005

    MS-1005 Severity INFO MS-1005 Message <timestamp>, [MS-1005], <sequence-number>,, ERROR, <system-name>, MS Invalid CT <domain> Response from d= Probable Cause Indicates that the management server (MS) received an invalid common transport (CT) response from switch domain. MS expects either a CT accept IU or a reject IU; MS received neither response, which violates the Fibre Channel Generic Services (FS-GS) specification.

  • Page 380: Ms-1009

    MS-1009 MS-1009 Message <timestamp>, [MS-1009], <sequence-number>,, ERROR, <system-name>, RLIR event. Switch Port ID is <PID>. Device Port Tag is <port tag>. <message>. Probable Cause A Registered Link Incident Record (RLIR) has been generated for one of the actions clarified by the <message>...

  • Page 381: Ms-1023

    MS-1023 MS-1023 Message <timestamp>, [MS-1023], <sequence-number>,, INFO, <system-name>, Management <Enabled or Disabled> Server Topology Discovery Service Probable Cause Indicates that Management Server Topology Discovery Service is being enabled or disabled. Recommended No action is required. Action Severity INFO MS-1024 Message <timestamp>, [MS-1024], <sequence-number>,, INFO, <system-name>, Management Server Access Control List is Updated Probable Cause...
  • Page 382 MS-1024 Fabric OS Message Reference 53-1000600-01...

  • Page 383: Nbfs-1001

    Chapter NBFS System Messages NBFS-1001 Message <timestamp>, [NBFS-1001], <sequence-number>,, INFO, <system-name>, Duplicate E_Port SCN from port <portnumber> in state <state change name> (<state change number>) Probable Cause Indicates that a duplicate E_Port State Change Number was reported. The neighbor finite state machine (NBFSM) states are as follows: •...

  • Page 384: Nbfs-1003

    NBFS-1003 Severity ERROR NBFS-1003 Message <timestamp>, [NBFS-1003], <sequence-number>,, WARNING, <system-name>, DB_XMIT_SET flag not set in state <current state name>, input <state name>, port <portnumber> Probable Cause Indicates that the database transmit set flag was not set for the specified input state on the specified port.

  • Page 385: Ns-1001

    Chapter NS System Messages NS-1001 Message <timestamp>, [NS-1001], <sequence-number>,, WARNING, <system-name>, The response for request 0x<CT command code> from remote switch 0x<Domain Id> is larger than the max frame size the remote switch can support! Probable Cause Indicates that the response payload exceeds the maximum frame size that the remote switch can handle.

  • Page 386: Ns-1004

    NS-1004 Recommended To avoid disruption of traffic in the event of an unplanned failover, schedule a firmwareDownload Action so that the active and standby CPs have the same firmware version. Reduce the local device count to follow the capability of the lowest version of firmware. Severity INFO NS-1004...

  • Page 387: Pdm-1001

    Chapter PDM System Messages PDM-1001 Message <timestamp>, [PDM-1001], <sequence-number>,, WARNING, <system-name>, Failed to parse the pdm config. Probable Cause Indicates that the parity data manager (PDM) process could not parse the configuration file. This might be caused by a missing configuration file during the installation. Recommended Run the firmwareDownload command to reinstall the firmware.

  • Page 388: Pdm-1004

    PDM-1004 PDM-1004 Message <timestamp>, [PDM-1004], <sequence-number>,, WARNING, <system-name>, PDM memory shortage. Probable Cause Indicates that the parity data manager (PDM) process ran out of memory. Recommended Reboot or power cycle the switch. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.

  • Page 389: Pdm-1008

    PDM-1008 Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1008 Message <timestamp>, [PDM-1008], <sequence-number>,, WARNING, <system-name>, Failed to get the number of U_Ports.

  • Page 390: Pdm-1011

    PDM-1011 PDM-1011 Message <timestamp>, [PDM-1011], <sequence-number>,, WARNING, <system-name>, File read failed: <file name> Probable Cause Indicates that the parity data manager (PDM) process could not read data from the specified file. Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...

  • Page 391: Pdm-1017

    PDM-1017 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1017 Message <timestamp>, [PDM-1017], <sequence-number>, FFDC, CRITICAL, <system-name>, System (<Error Code>): <Command>. Probable Cause Indicates that the specified system call failed.

  • Page 392: Pdm-1022

    PDM-1022 Probable Cause Indicates that a system call failed. Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1022...
  • Page 393 PDM-1024 Fabric OS Message Reference 53-1000600-01...
  • Page 394 PDM-1024 Fabric OS Message Reference 53-1000600-01...

  • Page 395: Pdtr-1001

    Chapter PDTR System Messages PDTR-1001 Message < <timestamp>, [PDTR-1001], <sequence-number>,, INFO, <system-name>, informational message > Probable Cause Indicates that information has been written to the panic dump files. The watchdog register codes are as follows: • 0x10000000 bit set means that the watch dog timer (WDT) forced a core reset. •...
  • Page 396 PDTR-1002 Fabric OS Message Reference 53-1000600-01...

  • Page 397: Plat-1000

    Chapter PLAT System Messages PLAT-1000 Message <timestamp>, [PLAT-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Error string> Probable Cause Indicates that nonrecoverable PCI errors have been detected. Recommended The system will be faulted and might automatically reboot. Action If the system does not reboot, then try issuing the reboot command from a command-line prompt. Run supportFtp (as needed) to set up automatic FTP transfers;...
  • Page 398 PLAT-1002 Severity CRITICAL Fabric OS Message Reference 53-1000600-01...

  • Page 399: Port-1003

    Chapter PORT System Messages PORT-1003 Message <port <timestamp>, [PORT-1003], <sequence-number>,, WARNING, <system-name>, Port number> Faulted because of many Link Failures Probable Cause Indicates that the specified port is now disabled because the link on this port had multiple failures that exceed an internally set threshold on the port. This problem is typically related to hardware. Recommended Check and replace (if necessary) the hardware attached to both ends of the specified port number, Action...

  • Page 400: Port-1005

    PORT-1005 PORT-1005 Message <timestamp>, [PORT-1005], <sequence-number>,, WARNING, <system-name>, Slot <slot number> port <port on slot> does not support configured L_port. Issue portCfgLport to clear configuration. Probable Cause Indicates that the specified port is configured to be an L_port, but that port does not support L_port.

  • Page 401: Ps-1000

    Chapter PS System Messages PS-1000 Message <timestamp>, [PS-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, Failed to initialize Advanced Performance Monitoring. Probable Cause Indicates that an unexpected software error has occurred in Advanced Performance Monitoring. The Performance Monitor has failed to initialize. Recommended The CP should reboot (or fail over) automatically.

  • Page 402: Ps-1003

    PS-1003 PS-1003 Message <timestamp>, [PS-1003], <sequence-number>,, WARNING, <system-name>, Failed to set end-to-end monitoring mask on ISL ports. Probable Cause Indicates that the restoring configuration has attempted to set the end-to-end monitoring mask on at least one ISL port. Recommended No action is required. End-to-end monitoring is not supported on ISL ports when ISL monitoring is Action enabled.

  • Page 403: Pswp-1001

    Chapter PSWP System Messages PSWP-1001 Message <timestamp>, [PSWP-1001], <sequence-number>,, INFO, <system-name>, Areas for port <wwn name corresponding to source port> and port <wwn name corresponding to destination port> are swapped. New area for port <wwn name corresponding to source port> is <wwn name corresponding to destination port> and port <new area corresponding to source wwn>...
  • Page 404 PSWP-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 405: Ras-1001

    Chapter RAS System Messages RAS-1001 Message <timestamp>, [RAS-1001], <sequence-number>,, INFO, <system-name>, First failure data capture (FFDC) event occurred. Probable Cause Indicates that a failure happened and the failure data was captured. Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.

  • Page 406: Ras-1006

    RAS-1006 Probable Cause Indicates an internal software error. Recommended Run the supportSave command and contact your switch service provider. Action Severity WARNING RAS-1006 Message <timestamp>, [RAS-1006], <sequence-number>, INFO, <system-name>, Support data file (<Uploaded file name>) automatically transferred to remote address ' <Remote target designated by user>...

  • Page 407: Ras-3001

    RAS-3001 Probable Cause A user has changed the configured classes of the audit feature. Recommended No action is required. Action Severity INFO RAS-3001 Message <timestamp>, [RAS-3001], <sequence-number>, INFO, <system-name>, USB storage device plug-in detected. Probable Cause Indicates that the USB storage device plug-in is being detected. Recommended No action is required.
  • Page 408 RAS-3004 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-01...

  • Page 409: Rcs-1001

    Chapter RCS System Messages RCS-1001 Message <timestamp>, [RCS-1001], <sequence-number>,, INFO, <system-name>, RCS has been disabled. Some switches in the fabric do not support this feature. Probable Cause Indicates that the RCS feature has been disabled on the local switch because not all switches in the fabric support RCS or the switch is in nonnative mode.

  • Page 410: Rcs-1004

    RCS-1004 RCS-1004 Message <timestamp>, [RCS-1004], <sequence-number>,, ERROR, <system-name>, Application(<application name>) not registered.(<error string>) Probable Cause Indicates that a specified application did not register with RCS. Recommended Run the haShow command to view the HA state. Action Run the haDisable and the haEnable commands. Run the rcsInfoShow command to view RCS capability on the fabric.

  • Page 411: Rcs-1006

    RCS-1006 RCS-1006 Message <timestamp>, [RCS-1006], <sequence-number>,, INFO, <system-name>, State <RCS phase>, Application <Application Name> AD<Administrative Domain>, RCS CM. Domain <Domain ID that sent the reject> returned 0x<Reject code>. Probable Cause Indicates that a remote domain rejected an RCS phase initiated by an application on the local switch.
  • Page 412 RCS-1008 Fabric OS Message Reference 53-1000600-01...

  • Page 413: Rpcd-1001

    Chapter RPCD System Messages RPCD-1001 Message <timestamp>, [RPCD-1001], <sequence-number>,, WARNING, <system-name>, Authentication Error: client \"<IP address>\" has bad credentials: <bad user name and password pair> Probable Cause Indicates that an authentication error was reported. The specified client IP address has faulty credentials.

  • Page 414: Rpcd-1004

    RPCD-1004 RPCD-1004 Message <timestamp>, [RPCD-1004], <sequence-number>,, WARNING, <system-name>, Invalid certificate file. Secure RPCd is disabled. Probable Cause Indicates that the SSL certificate file has been corrupted. Recommended To enable RPCD in Secure mode, install a valid SSL certificate the switch. Action Severity WARNING...

  • Page 415: Rtwr-1001

    Chapter RTWR System Messages RTWR-1001 Message <timestamp>, [RTWR-1001], <sequence-number>,, ERROR, <system-name>, RTWR <routine: error message> 0x<detail 1>, 0x<detail 2>, 0x<detail 3>, 0x<detail 4>, 0x<detail 5> Probable Cause Indicates that an error occurred in the RTWR. The message provides the name of the routine having the error, and more specific error information.

  • Page 416: Rtwr-1003

    RTWR-1003 RTWR-1003 Message <timestamp>, [RTWR-1003], <sequence-number>,, INFO, <system-name>, <module name>: RTWR retry <number of times retried> to domain <domain ID>, iu_data <first word of iu_data> Probable Cause Indicates how many times RTWR failed to get a response and retried. Recommended Run the dom command to verify that the specified domain ID is reachable.

  • Page 417: Sas-1001

    Chapter SAS System Messages SAS-1001 Message <timestamp>, [SAS-1001], <sequence-number>,, ERROR, <system-name>, string description of command which failed> of GE <GE port number which failed> failed. Please retry the command. Data inst=<chip instance> st=<chip init state> rsn=<failure reason> fn=<message function> oid=<chip OID>. Probable Cause The Hardware is not responding to the command request;...
  • Page 418 SAS-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 419: Scn-1001

    Chapter SCN System Messages SCN-1001 Message <timestamp>, [SCN-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, SCN <daemon name> queue overflow for process Probable Cause Indicates that an attempt to write a state change notification (SCN) message to a specific queue has failed because the SCN queue for the specified daemon name is full. This might be caused by the daemon hanging or if the system is busy.
  • Page 420 SCN-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 421: Sec-1001

    Chapter SEC System Messages SEC-1001 Message <timestamp>, [SEC-1001], <sequence-number>,, ERROR, <system-name>, RCS process <reason code> fails: Probable Cause Indicates that the reliable commit service (RCS) process fails to complete. RCS is a mechanism for transferring data from one switch to other switches within the fabric. RCS ensures that either all or none of the switches commit to the database.

  • Page 422: Sec-1003

    SEC-1003 SEC-1003 Message <timestamp>, [SEC-1003], <sequence-number>,, WARNING, <system-name>, Fail to download security data to domain <Domain number> after <Number of retires> retries Probable Cause Indicates that the specified domain failed to download security data after the specified number of attempts, and that the failed switch encountered an error accepting the database download. The primary switch will segment the failed switch after 30 tries.

  • Page 423: Sec-1007

    SEC-1007 SEC-1007 Message <timestamp>, [SEC-1007], <sequence-number>,, INFO, <system-name>, Security <IP address of the violating violation: Unauthorized host with IP address host> tries to establish API connection. Probable Cause Indicates that a security violation was reported. The IP address of the unauthorized host is displayed in the message.

  • Page 424: Sec-1016

    SEC-1016 SEC-1016 Message <timestamp>, [SEC-1016], <sequence-number>,, INFO, <system-name>, Security <IP address of the violating host> violation: Unauthorized host with IP address tries to establish SSH connection. Probable Cause Indicates that a security violation was reported. The IP address of the unauthorized host is displayed in the message.

  • Page 425: Sec-1025

    SEC-1025 SEC-1025 Message <timestamp>, [SEC-1025], <sequence-number>,, ERROR, <system-name>, Invalid IP (<IP address>) address detected. Probable Cause Indicates that a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configurations server (FCS) distributes the security database to the other switches in the fabric, then local validation finds the error in the security database.

  • Page 426: Sec-1029

    SEC-1029 SEC-1029 Message <timestamp>, [SEC-1029], <sequence-number>,, ERROR, <system-name>, Invalid <policy name> character in Probable Cause Indicates that a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configurations server (FCS) distributes the security database to the other switches in the fabric, then local validation finds the error in the security database.

  • Page 427: Sec-1032

    SEC-1032 SEC-1032 Message <timestamp>, [SEC-1032], <sequence-number>,, ERROR, <system-name>, Empty FCS list is not allowed. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 428: Sec-1035

    SEC-1035 SEC-1035 Message <timestamp>, [SEC-1035], <sequence-number>,, ERROR, <system-name>, Invalid device <device WWN> Probable Cause Indicates that the specified world-wide name (WWN) is invalid. Recommended Enter the correct WWN value. Action Severity ERROR SEC-1036 Message <timestamp>, [SEC-1036], <sequence-number>,, ERROR, <system-name>, Device name <device name>...

  • Page 429: Sec-1040

    SEC-1040 SEC-1040 Message <timestamp>, [SEC-1040], <sequence-number>,, ERROR, <system-name>, Invalid <port list> portlist ( ). Cannot combine * with port member in the same portlist. Probable Cause Indicates that the port list contains the wildcard asterisk (*) character. You cannot use the asterisk in a port list.

  • Page 430: Sec-1043

    SEC-1043 SEC-1043 Message <timestamp>, [SEC-1043], <sequence-number>,, ERROR, <system-name>, Invalid port range <Minimum> - <Maximum>. Probable Cause Indicates that the specified port is not within the minimum and maximum range. Recommended Use valid syntax when entering port ranges. Action Severity ERROR SEC-1044 Message <timestamp>, [SEC-1044], <sequence-number>,, ERROR, <system-name>, Duplicate...

  • Page 431: Sec-1046

    SEC-1046 SEC-1046 Message <timestamp>, [SEC-1046], <sequence-number>,, ERROR, <system-name>, Empty list. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 432: Sec-1051

    SEC-1051 SEC-1051 Message <timestamp>, [SEC-1051], <sequence-number>,, ERROR, <system-name>, Missing brace <port list> for port list Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 433: Sec-1054

    SEC-1054 SEC-1054 Message <timestamp>, [SEC-1054], <sequence-number>,, ERROR, <system-name>, Invalid FCS <list length> list length Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 434: Sec-1057

    SEC-1057 SEC-1057 Message <timestamp>, [SEC-1057], <sequence-number>,, ERROR, <system-name>, No change. Both positions are the same. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 435: Sec-1063

    SEC-1063 SEC-1063 Message <timestamp>, [SEC-1063], <sequence-number>,, ERROR, <system-name>, Failed to reset statistics. Probable Cause Indicates that either the type or domains specified are invalid. Recommended Enter valid input. Action Severity ERROR SEC-1064 Message <timestamp>, [SEC-1064], <sequence-number>,, ERROR, <system-name>, Failed to sign message.

  • Page 436: Sec-1071

    SEC-1071 SEC-1071 Message <timestamp>, [SEC-1071], <sequence-number>,, ERROR, <system-name>, No new security policy data to apply. Probable Cause Indicates that no changes in the defined security policy database need to be activated at this time. Recommended Verify that the security event was planned. First change some policy definitions, then run the Action secPolicyActivate command to activate the policies.

  • Page 437: Sec-1074

    SEC-1074 SEC-1074 Message <timestamp>, [SEC-1074], <sequence-number>,, ERROR, <system-name>, Cannot execute the command on this switch. Please check the secure mode and FCS status. Probable Cause Indicates that a security command was run on a switch that is not allowed to run it either because it is in non-secure mode or because it does not have required fabric configurations server (FCS) privilege.

  • Page 438: Sec-1077

    SEC-1077 SEC-1077 Message <timestamp>, [SEC-1077], <sequence-number>,, ERROR, <system-name>, Failed to activate new policy set on all switches. Probable Cause Indicates that the policy could not be activated. Possible reasons that the policy could not be activate include not enough memory or a busy switch. Recommended Run the secFabricShow command to verify that all switches in the fabric are in the ready state.

  • Page 439: Sec-1080

    SEC-1080 SEC-1080 Message <timestamp>, [SEC-1080], <sequence-number>,, ERROR, <system-name>, Operation denied. Please, use secModeEnable command. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 440: Sec-1083

    SEC-1083 SEC-1083 Message <timestamp>, [SEC-1083], <sequence-number>,, ERROR, <system-name>, Name already exists. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 441: Sec-1086

    SEC-1086 SEC-1086 Message <timestamp>, [SEC-1086], <sequence-number>,, ERROR, <system-name>, The security database is too large to fit in flash. Probable Cause Indicates that the security database has more data than the flash can accommodate. Recommended Reduce the number of entries in some policies to decrease the security database size. Action Severity ERROR...

  • Page 442: Sec-1089

    SEC-1089 SEC-1089 Message <timestamp>, [SEC-1089], <sequence-number>,, ERROR, <system-name>, Policy name <policy name> was not found. Probable Cause Indicates that the security policy name in the secPolicyAdd command does not exist. Recommended Create the appropriate security policy first, then use its name in the secPolicyAdd command to add Action new members.

  • Page 443: Sec-1092

    SEC-1092 SEC-1092 Message <Policy <timestamp>, [SEC-1092], <sequence-number>,, ERROR, <system-name>, name> Name not found. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 444: Sec-1095

    SEC-1095 SEC-1095 Message <timestamp>, [SEC-1095], <sequence-number>,, ERROR, <system-name>, Deleting FCS policy is not allowed. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 445: Sec-1098

    SEC-1098 SEC-1098 Message <active or <timestamp>, [SEC-1098], <sequence-number>,, ERROR, <system-name>, No defined> FCS list. Probable Cause Indicates that the specified policy could not be found. Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.

  • Page 446: Sec-1101

    SEC-1101 SEC-1101 Message <timestamp>, [SEC-1101], <sequence-number>,, ERROR, <system-name>, Failed to enable security on all switches. Please retry later. Probable Cause Indicates that the security enable failed on the fabric because one or more switches in the fabric are busy. Recommended Verify that the security event was planned.

  • Page 447: Sec-1105

    SEC-1105 SEC-1105 Message <timestamp>, [SEC-1105], <sequence-number>,, ERROR, <system-name>, Fail to disable secure mode on all switches. Probable Cause Indicates that the switch failed to disable security in the fabric. This could happen if the switch cannot get the required resources to complete the command, and sending to a remote domain fails or the remote domain returns an error.

  • Page 448: Sec-1108

    SEC-1108 SEC-1108 Message <timestamp>, [SEC-1108], <sequence-number>,, ERROR, <system-name>, Fail to reset stamp on all switches. Probable Cause Indicates that a version reset operation failed either because the switch could not get all the required resources to perform the operation or because it failed to send the message to all switches in the fabric.

  • Page 449: Sec-1112

    SEC-1112 SEC-1112 Message <timestamp>, [SEC-1112], <sequence-number>,, ERROR, <system-name>, FCS list must be the first entry in the Active Security policies, and the same as the current active FCS list in the switch. Probable Cause Indicates that either a security policy download is attempted with an active policy that does not have the fabric configurations server (FCS) policy as the first policy or the FCS policy is not same as the current FCS policy on the switch.

  • Page 450: Sec-1117

    SEC-1117 SEC-1117 Message <timestamp>, [SEC-1117], <sequence-number>,, INFO, <system-name>, Fail to set <data> Probable Cause Indicates that the switch failed to save the data received by the primary fabric configurations server (FCS) switch. This data can be an FCS password, a non-FCS password, SNMP data, or multiple user authentication data.

  • Page 451: Sec-1121

    SEC-1121 SEC-1121 Message <timestamp>, [SEC-1121], <sequence-number>,, ERROR, <system-name>, Time is out of <text> range when Probable Cause Indicates that the time on the switch is not synchronized with the primary fabric configurations server (FCS), the data packet is corrupted, or a replay attack is launched on the switch. Recommended Verify that the security event was planned.

  • Page 452: Sec-1126

    SEC-1126 Severity INFO SEC-1126 Message <timestamp>, [SEC-1126], <sequence-number>,, INFO, <system-name>, Secure mode has been disabled. Probable Cause Indicates that a secure mode disable operation completed successfully. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.

  • Page 453: Sec-1136

    SEC-1136 SEC-1136 Message <timestamp>, [SEC-1136], <sequence-number>,, ERROR, <system-name>, Failed to <data type, MUA, policy, etc.,> verify signature Probable Cause Indicates that the receiving switch fails to validate the security database sending from the primary fabric configurations server (FCS) switch. This message usually indicates that the data package is corrupted, the time stamp on the package is out of range as a result of a replay attack or out-of-sync time service, or the signature verification failed.

  • Page 454: Sec-1139

    SEC-1139 SEC-1139 Message <timestamp>, [SEC-1139], <sequence-number>,, ERROR, <system-name>, The RSNMP_POLICY cannot exist without the WSNMP_POLICY. Probable Cause Indicates that the receiving switch fails to validate the security database sending from the primary fabric configurations server (FCS) switch. This message usually indicates that the data package is corrupted, the time stamp on the package is out of range as a result of a replay attack or out-of-sync time service, or the signature verification failed.

  • Page 455: Sec-1146

    SEC-1146 SEC-1146 Message <timestamp>, [SEC-1146], <sequence-number>,, INFO, <system-name>, PID changed: <State> Probable Cause Indicates that the PID format of the switch was changed either to extended-edge PID or from extended-edge PID. If the device connection control (DCC) polices existed, all index/area ID values either increased or decreased by 16.

  • Page 456: Sec-1155

    SEC-1155 SEC-1155 Message <timestamp>, [SEC-1155], <sequence-number>,, INFO, <system-name>, PID change failed: <Reason> <defined status> <active status>. Probable Cause Indicates that either the defined or active policy was too large after modifying the index/area ID. The status values can be either defined, active, or both. A negative value means that a policy set was failed by the daemon.

  • Page 457: Sec-1158

    SEC-1158 SEC-1158 Message <timestamp>, [SEC-1158], <sequence-number>,, INFO, <system-name>, Invalid name <Policy or Switch name> Probable Cause Indicates that the specified name is invalid. The name can be a policy name or a switch name. Recommended Enter a valid name. Action Severity INFO SEC-1159...

  • Page 458: Sec-1163

    SEC-1163 SEC-1163 Message <timestamp>, [SEC-1163], <sequence-number>,, ERROR, <system-name>, System is already in secure mode. Lockdown option cannot be applied. Probable Cause Indicates that the lockdown option was attempted while the fabric is already in secure mode. Recommended Do not use the lockdown option with the secModeEnable command when switch is already in Action secure mode.

  • Page 459: Sec-1166

    SEC-1166 SEC-1166 Message <timestamp>, [SEC-1166], <sequence-number>,, ERROR, <system-name>, Non FCS tries to commit failover. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 460: Sec-1170

    SEC-1170 SEC-1170 Message <timestamp>, [SEC-1170], <sequence-number>,, INFO, <system-name>, This command must be executed on the Primary FCS switch, the first reachable switch in the FCS list. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 461: Sec-1173

    SEC-1173 SEC-1173 Message <timestamp>, [SEC-1173], <sequence-number>,, ERROR, <system-name>, Lost contact with Primary FCS switch. Probable Cause Indicates that the switch has lost contact with the primary fabric configurations server (FCS) switch in the secure fabric. This could be due to the primary FCS being disabled. Recommended If the primary FCS was disabled intentionally, no action is required;...

  • Page 462: Sec-1180

    SEC-1180 SEC-1180 Message <timestamp>, [SEC-1180], <sequence-number>,, INFO, <system-name>, Added account <user name> with <role name> authorization. Probable Cause Indicates that the specified new account has been created. Recommended No action is required. Action Severity INFO SEC-1181 Message <timestamp>, [SEC-1181], <sequence-number>,, INFO, <system-name>, Deleted account <user name>...

  • Page 463: Sec-1184

    SEC-1184 SEC-1184 Message <timestamp>, [SEC-1184], <sequence-number>,, INFO, <system-name>, <server> configuration change, action <action>, server ID <server>. Probable Cause Indicates that the specified action is applied to the specified Remote Authentication Dial-in User Service (RADIUS) / Lightweight Directory Access Protocol (LDAP) server configuration. The possible actions are ADD, REMOVE, CHANGE, and MOVE Recommended No action is required.

  • Page 464: Sec-1187

    SEC-1187 SEC-1187 Message <timestamp>, [SEC-1187], <sequence-number>,, INFO, <system-name>, Security <switch WWN> violation: Unauthorized switch tries to join fabric. Probable Cause Indicates that a switch connection control (SCC) security violation was reported. The specified unauthorized switch attempts to join the fabric. Recommended Check the switch connection control policy (SCC) policy to verify the switches allowed in the fabric.

  • Page 465: Sec-1190

    SEC-1190 SEC-1190 Message <timestamp>, [SEC-1190], <sequence-number>,, INFO, <system-name>, Security <IP address> violation: Unauthorized host with IP address tries to do SNMP read operation. Probable Cause Indicates that an SNMP security violation was reported. The specified unauthorized host attempted to perform a read SNMP operation. Recommended Check the RSNMP policy to verify that hosts allowed access to the fabric through SNMP read Action...

  • Page 466: Sec-1193

    SEC-1193 SEC-1193 Message <timestamp>, [SEC-1193], <sequence-number>,, INFO, <system-name>, Security violation: Login failure attempt via <connection method>. IP Addr: <IP address> Probable Cause Indicates that a specified login security violation was reported. The incorrect password was used while trying to log in through the specified connection method; the login failed. Recommended The error message lists the violating IP address.

  • Page 467: Sec-1196

    SEC-1196 SEC-1196 Message <timestamp>, [SEC-1196], <sequence-number>,, WARNING, <system-name>, Switch does not have all default account names. Probable Cause Indicates that the default switch accounts admin and user do not exist on the switch when enabling security. Recommended Reset the default admin and user account names on the switch that reported the warning and retry Action enabling security.

  • Page 468: Sec-1199

    SEC-1199 SEC-1199 Message <timestamp>, [SEC-1199], <sequence-number>,, INFO, <system-name>, Security <switch instance> violation: Unauthorized access to serial port of switch Probable Cause Indicates that a serial connection policy security violation was reported. An attempt was made to access the serial console on the specified switch instance when it is disabled. Recommended Check to see if an authorized access attempt is being made on the console.

  • Page 469: Sec-1202

    SEC-1202 SEC-1202 Message <timestamp>, [SEC-1202], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized access from MS device node name <device node name>, device port name <device port name>. Probable Cause Indicates that a management server (MS) security violation was reported. The unauthorized device specified in the message attempted to establish a connection.

  • Page 470: Sec-1251

    SEC-1251 SEC-1251 Message <timestamp>, [SEC-1251], <sequence-number>,, ERROR, <system-name>, Policy to binary conversion error: <text message> <value>. Probable Cause Indicates that the security database conversion failed because of invalid values. The reason is specified in the text message variable and faulty value is printed in value variable. Recommended Retry the failed security command.

  • Page 471: Sec-1301

    SEC-1301 SEC-1301 Message <timestamp>, [SEC-1301], <sequence-number>,, INFO, <system-name>, This switch is in interop mode. Security is not supported. Probable Cause Indicates that the switch is interop-mode enabled. Recommended Disable interop-mode using the interopMode command before enabling the Secure Fabric OS Action feature.

  • Page 472: Sec-1304

    SEC-1304 SEC-1304 Message <timestamp>, [SEC-1304], <sequence-number>,, INFO, <system-name>, This switch has no security license. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.

  • Page 473: Sec-1307

    SEC-1307 SEC-1307 Message Got response <timestamp>, [SEC-1307], <sequence-number>,, INFO, <system-name>, from <Radius/LDAP server identity> server <Radius/LDAP server identity>. Probable Cause Indicates that after some servers timed out, the specified remote authentication dial-in user service (RADIUS/LDAP) server responded to a switch request. Recommended If the message appears frequently, move the responding server to the top of the RADIUS/LDAP Action...

  • Page 474: Sec-1311

    SEC-1311 Severity INFO SEC-1311 Message <timestamp>, [SEC-1311], <sequence-number>,, ERROR, <system-name>, Security mode cannot be enabled because one or more of the password policies is not set to default value. Probable Cause Indicates that the security enable failed on the fabric because one or more switches in the fabric have password policies that are not set to the default value.

  • Page 475: Sec-1314

    SEC-1314 SEC-1314 Message <IP <timestamp>, [SEC-1314], <sequence-number>,, ERROR, <system-name>, Reading Address Description > IP address from EM failed. Probable Cause Indicates that the call to the EM module to retrieve the IP address failed. Recommended Please reboot the system to fix this error. If the problem persists contact your switch service Action provider.

  • Page 476: Sec-1317

    SEC-1317 SEC-1317 Message <timestamp>, [SEC-1317], <sequence-number>,, INFO, <system-name>, Inconsistent fabric, rejecting transaction Probable Cause Indicates that either this domain is performing an FDD merge or matched domains are not the same as what the CM sees. Recommended If a policy conflict exists, resolve it, then wait for the fabric to become stable. Retry the distribution. Action Severity INFO...

  • Page 477: Sec-1321

    SEC-1321 SEC-1321 Message <timestamp>, [SEC-1321], <sequence-number>,, ERROR, <system-name>, Failed secure <Reason> mode enable command. Reason: Probable Cause Indicates that the security enable failed on the fabric because switch has conflicting configuration such as fabric wide consistency configuration or AD configuration. Recommended Verify that the security event was planned.

  • Page 478: Sec-1324

    SEC-1324 SEC-1324 Message <timestamp>, [SEC-1324], <sequence-number>,, INFO, <system-name>, Fabric <Error code> transaction failure. RCS error: Probable Cause Indicates that the reliable commit service (RCS) transaction failed with specified reason code. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.

  • Page 479: Sec-1327

    SEC-1327 SEC-1327 Message <timestamp>, [SEC-1327], <sequence-number>,, WARNING, <system-name>, Strict <Policy Name> policy is conflicting with domain <Domain Number> Probable Cause Strict policy is conflicting. Recommended None, the domain is denied by disallowing all its E-ports connected to the fabric. If the domain Action should be allowed to merge with the fabric, then resolve the issue by making the conflicting policies same.

  • Page 480: Sec-1331

    SEC-1331 Recommended Verify that the distribution is initiated by the primary FCS switch. Use the secPolicyShow command Action to verify and correct the configuration if necessary. Severity ERROR SEC-1331 Message <timestamp>, [SEC-1331], <sequence-number>,, ERROR, <system-nam>, Attempt to enable secure mode failed. Reason: <Reason>. Probable Cause Indicates that the secModeEnable command failed on the fabric, because default IP Filter policies are not active on the switch, or an active transaction exists on IP Filter policies.

  • Page 481: Snmp-1001

    Chapter SNMP System Messages SNMP-1001 Message <timestamp>, [SNMP-1001], <sequence-number>,, ERROR, <system-name>, SNMP service <Reason> is not available Probable Cause Indicates that the simple network management protocol (SNMP) service could not be started because of the specified Reason. You will not be able to query the switch through SNMP. Recommended Verify that the IP address for the Ethernet and Fibre Channel interface is set correctly.

  • Page 482: Snmp-1004

    SNMP-1004 SNMP-1004 Message <timestamp>, [SNMP-1004], <sequence-number>, FFDC, ERROR, <system-name>, Incorrect SNMP configuration. Probable Cause Indicates that the simple network management protocol (SNMP) configuration is incorrect and the SNMP service will not work correctly. Recommended Change the SNMP configuration back to the default. Action Severity ERROR...

  • Page 483: Ss-1000

    Chapter SS System Messages SS-1000 Message <timestamp>, [SS-1000], <sequence-number>,, INFO, <system-name>, supportSave has uploaded support information to the host with IP address <host ip>. Probable Cause Indicates that the supportSave command was used to transfer support information to a remote location.

  • Page 484: Ss-1003

    SS-1003 SS-1003 Message <timestamp>, [SS-1003], <sequence-number>,, WARNING, <system-name>, supportSave's operation to USB storage device aborted. Probable Cause Indicates that a USB operation error occurred during execution of the supportSave command. Complete error information cannot always be displayed in this message due to possible errors in subcommands being executed by the supportSave command.

  • Page 485: Sulb-1001

    Chapter SULB System Messages SULB-1001 Message <timestamp>, [SULB-1001], <sequence-number>, AUDIT, WARNING, <system-name>, Firmwaredownload command has started. Probable Cause Indicates that the firmwareDownload command has been entered. This process should take approximately 17 minutes. The process is set to time out after 30 minutes. Recommended Do not fail over or power down the system during firmware upgrade.

  • Page 486: Sulb-1004

    SULB-1004 SULB-1004 Message <timestamp>, [SULB-1004], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwarecommit has completed. Probable Cause Indicates that the FirmwareCommit command is executed. Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action Severity INFO SULB-1005 Message <timestamp>, [SULB-1005], <sequence-number>,, INFO, <system-name>, Current Active CP is preparing to failover.

  • Page 487: Sulb-1008

    SULB-1008 SULB-1008 Message <timestamp>, [SULB-1008], <sequence-number>,, INFO, <system-name>, Standby CP booted successfully with new firmware. Probable Cause Indicates that the standby CP has rebooted successfully. Recommended No action is required. The firmwareDownload command is progressing as expected. Action Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1009...
  • Page 488 SULB-1009 TABLE 6 Status Messages and Status Codes Status Message Status Code “firmwareCommit operation failed due to IPC error.” 0x55 "Unable to check the firmware version on Standby CP due to IPC error." 0x56 “Unable to restore the original firmware due to Standby CP timeout.” 0x57 "Standby CP failed to reboot and was not responding."...
  • Page 489 SULB-1009 TABLE 6 Status Messages and Status Codes Status Message Status Code "The original firmware has been restored successfully on Standby CP." 0x7e "Unable to restore the original firmware on Standby CP." 0x7f "Standby CP reboots." 0x80 "Standby CP failed to reboot." 0x81 "Standby CP booted up with new firmware."...
  • Page 490 SULB-1009 TABLE 6 Status Messages and Status Codes Status Message Status Code “firmwareRestore is entered. System will reboot and a firmwareCommit operation will start 0xa8 upon boot up.” "Switch is relocating the AP image." 0xa9 "The AP image is relocated successfully." 0xaa "Switch reboots during relocating the AP image.
  • Page 491 SULB-1009 TABLE 7 Error Messages and Error Codes Error Message Error Code "Both images are mounted to the same device." 0x20 “Unable to unionist old packages.” 0x21 “firmwareDownload is already in progress.” 0x22 “firmwareDownload timed out.” 0x23 "Our of disk space." 0x24 “Primary filesystem is inconsistent.
  • Page 492 SULB-1009 0x23 - firmwareDownload timed out. This error may occur because firmwareDownload has not completed within the predefined timeout period. It is most often caused by network issues. If the problem persists, contact your system administrator. 0x24 - out of disk space. This error may occur because some coredump files have not been removed from the filesystem and are using up disk space.

  • Page 493: Sulb-1010

    SULB-1010 Recommended Run the firmwareDownloadStatus command for more information. Action In a director-class switch, when firmwareDownload fails, the command will synchronize the firmware on the two partitions of each CP by starting a firmware commit operation. Wait until this operation completes (about 10 minutes) before attempting another firmwareDownload. In a director-class switch, when firmwareDownload fails, the two CPs may end up with different versions of firmware and they may not gain high-availability (HA) sync.

  • Page 494: Sulb-1018

    SULB-1018 Probable Cause Indicates that firmwareDownload failed in the specified blade. The error may be caused by an inconsistent AP blade firmware stored on the active CP. It may also caused by an internal Ethernet issue or by a persistent storage hardware failure. Recommended Run the slotShow command.

  • Page 495: Sulb-1022

    SULB-1022 Recommended Run the firmwareDownloadStatus command to monitor the firmwareDownload progress. After it Action finishes, run the firmwareShow command to verify the firmware versions. Severity WARNING SULB-1022 Message <timestamp>, [SULB-1022], <sequence-number>,, WARNING, <system-name>, The blade <Slot number> in slot has rebooted successfully with new firmware. Probable Cause Indicates that the blade in the specified slot has rebooted with new firmware.

  • Page 496: Sulb-1025

    SULB-1025 Severity WARNING SULB-1025 Message <timestamp>, [SULB-1025], <sequence-number>,, WARNING, <system-name>, The blade <Slot number> in slot will reboot with the new firmware. Probable Cause Indicates that new firmware has been downloaded to the specified AP blade and that the AP blade will reboot to active it.

  • Page 497: Sulb-1033

    SULB-1033 Probable Cause Indicates that the switch has rebooted with the new firmware and is relocating the AP firmware. Recommended Wait for the operation to complete. Action Severity WARNING SULB-1033 Message <timestamp>, [SULB-1033], <sequence-number>, AUDIT, WARNING, <system-name>, Switch has completed relocating the internal firmware image. Probable Cause Indicates that the firmwareDownload process has completed normally on the switch.

  • Page 498: Sulb-1036

    SULB-1036 SULB-1036 Message <The Version <timestamp>, [SULB-1036], <sequence-number>,, INFO, <system-name>, being logged><Version String> Probable Cause Indicates the firmware version running in the system. This is generally logged before download and after download of the firmware to store version information. Recommended No action is required.

  • Page 499: Swch-1001

    Chapter SWCH System Messages SWCH-1001 Message <timestamp>, [SWCH-1001], <sequence-number>,, ERROR, <system-name>, Switch is not in ready state - Switch enable failed switch status= 0x<switch status>, c_flags = 0x<switch control flags>. Probable Cause Indicates that the switch is enabled before it is ready. Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...

  • Page 500: Swch-1004

    SWCH-1004 SWCH-1004 Message <timestamp>, [SWCH-1004], <sequence-number>,, ERROR, <system-name>, Blade attach <slot number>. failed during recovery, disabling slot = Probable Cause Indicates that a blade has failed during failover or recovery. Recommended On a Brocade 24000 or 48000 switch, run the slotPowerOff command and then the slotPowerOn Action command.

  • Page 501: Swch-1007

    SWCH-1007 SWCH-1007 Message <timestamp>, [SWCH-1007], <sequence-number>,, WARNING, <system-name>, Switch port <port number> disabled due to \"<disable reason>\". Probable Cause Indicates that the switch port is disabled due to the reason displayed in the message. Recommended Based on the disable reason displayed, proper corrective action may to be required to restore the Action port.
  • Page 502 SWCH-1008 Fabric OS Message Reference 53-1000600-01...

  • Page 503: Sysc-1001

    Chapter SYSC System Messages SYSC-1001 Message <timestamp>, [SYSC-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Failed to run <Name of program that could not be run (string)>:<System internal error message (string)>. Probable Cause Indicates that during the boot sequence, one of the programs would not run on the system. Recommended If the message is reported during a reboot after new firmware has been loaded, try reloading the Action...

  • Page 504: Sysc-1003

    SYSC-1003 SYSC-1003 Message <timestamp>, [SYSC-1003], <sequence-number>, FFDC, CRITICAL, <system-name>, Chassis config option <Option number read from the chassis option storage device> is not supported by CP Blade with ID <Blade ID (platform) number from the Active CP>. Change the chassis configuration <Steps to change chassis configuration> Probable Cause Indicates that on system startup, the option configuration file corresponding to the chassisConfig option read could not be found.

  • Page 505: Sysm-1001

    Chapter SYSM System Messages SYSM-1001 Message <timestamp>, [SYSM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, No memory. Probable Cause Indicates that the switch has run out of system memory. Recommended Run the memShow command to view the switch memory usage. Action Reboot or power cycle the switch. Run supportFtp as needed) to set up automatic FTP transfers;...

  • Page 506: Sysm-1004

    SYSM-1004 SYSM-1004 Message <timestamp>, [SYSM-1004], <sequence-number>,, ERROR, <system-name>, Failed to <Unknown> retrieve current chassis configuration option, ret= Probable Cause Indicates that there was a failure to read configuration data from the WWN card. Recommended Verify that the world-wide name (WWN) card is present and operational and that the affected Action control processor (CP) is properly seated in its slot.

  • Page 507: Trce-1001

    Chapter TRCE System Messages TRCE-1001 Message <timestamp>, [TRCE-1001], <sequence-number>,, WARNING, <system-name>, Trace dump available< optional slot indicating on which slot the dump occurs >! (reason: <Text explanation of what triggered the dump. (PANIC DUMP, WATCHDOG EXPIRED, MANUAL, TRIGGER)>) Probable Cause Indicates that trace dump files have been generated on the switch or the indicated slot.

  • Page 508: Trce-1003

    TRCE-1003 TRCE-1003 Message < <timestamp>, [TRCE-1003], <sequence-number>,, ERROR, <system-name>, Trace dump optional slot indicating on which slot the dump occurs > was not transferred due to FTP error. Probable Cause Indicates that a trace dump has been created on the switch or the indicated slot but is not automatically transferred from the switch due to an FTP error, such as a wrong FTP address, FTP site down, or network down.

  • Page 509: Trce-1006

    TRCE-1006 TRCE-1006 Message <timestamp>, [TRCE-1006], <sequence-number>,, INFO, <system-name>, FTP <FTP target configured by users.> Connectivity Test succeeded to FTP site ' Probable Cause Indicates that a connectivity test to the FTP host has succeeded. This feature is enabled by the supportFtp -t command.

  • Page 510: Trce-1009

    TRCE-1009 TRCE-1009 Message <timestamp>, [TRCE-1009], <sequence-number>,, ERROR, <system-name>, Unable to alert active CP that a dump has occurred. Probable Cause Indicates that the standby CP is unable to communicate trace information to active CP. This message is only applicable to the Brocade 24000 and 48000. Recommended Run the haShow command to verify that the current CP is standby and the active CP is active.

  • Page 511: Trce-1012

    TRCE-1012 TRCE-1012 Message <timestamp>, [TRCE-1012], <sequence-number>,, WARNING, <system-name>, The system <Slot number of the blade was unable to retrieve trace information from slot the attempt was made on> Probable Cause Indicates that communication between the main system and the indicated slot is unavailable. Recommended Check that the AP blade is enabled and retry the command.
  • Page 512 TRCE-1012 Fabric OS Message Reference 53-1000600-01...

  • Page 513: Trck-1001

    Chapter TRCK System Messages TRCK-1001 Message <timestamp>, [TRCK-1001], <sequence-number>,, INFO, <system-name>, Successful <User> login by user Probable Cause Indicates that the track change feature recorded a successful login. Recommended No action is required. Action Severity INFO TRCK-1002 Message <timestamp>, [TRCK-1002], <sequence-number>,, INFO, <system-name>, Unsuccessful <User>...

  • Page 514: Trck-1004

    TRCK-1004 TRCK-1004 Message <timestamp>, [TRCK-1004], <sequence-number>,, INFO, <system-name>, Config file <task> change from task: Probable Cause Indicates that the track change feature recorded a configuration change for the switch. The track change feature records any change to the configuration file in nonvolatile memory, including a configDownload.

  • Page 515: Ts-1001

    Chapter TS System Messages TS-1001 Message <timestamp>, [TS-1001], <sequence-number>,, WARNING, <system-name>, NTP Query <error code> failed: Probable Cause Indicates that a network time protocol (NTP) query to the configured external clock server failed. Local clock time on the principal or primary fabric configuration server (FCS) switch is used for fabric synchronization.

  • Page 516: Ts-1006

    TS-1006 TS-1006 Message <message> <timestamp>, [TS-1006], <sequence-number>,, INFO, <system-name>, Probable Cause Indicates that a time service event is occurring or has failed. The message might be one of the following: • Init failed. Time Service exiting Probable Cause: Initialization error, Time Server exits. •...

  • Page 517: Ts-1008

    TS-1008 TS-1008 Message <New clock <timestamp>, [TS-1008], <sequence-number>,, WARNING, <system-name>, server used> Clock Server used instead of <Old server configured>. Probable Cause Indicates that there is a change in the source of fabric time synchronization distributed from the principal or primary fabric configuration server (FCS) switch. Another clock server in the list of clock servers configured is being used.
  • Page 518 TS-1008 Fabric OS Message Reference 53-1000600-01...

  • Page 519: Ucst-1003

    Chapter UCST System Messages UCST-1003 Message <timestamp>, [UCST-1003], <sequence-number>,, INFO, <system-name>, Duplicate Path to Domain <domain ID>, Output Port = <port number>, PDB pointer = 0x<value> Probable Cause Indicates that duplicate paths were reported to the specified domain from the specified output port.
  • Page 520 UCST-1020 Fabric OS Message Reference 53-1000600-01...

  • Page 521: Upth-1001

    Chapter UPTH System Messages UPTH-1001 Message <timestamp>, [UPTH-1001], <sequence-number>,, WARNING, <system-name>, No minimum cost path in candidate list Probable Cause Indicates that the specified switch is unreachable because no minimum cost path (FSPF UPATH) exists in the candidate list (domain ID list). Recommended No action is required.
  • Page 522 UPTH-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 523: Webd-1001

    Chapter WEBD System Messages WEBD-1001 Message <timestamp>, [WEBD-1001], <sequence-number>,, WARNING, <system-name>, Missing or Invalid Certificate file -- HTTPS is configured to be enabled but could not be started. Probable Cause Indicates that the SSL certificate file is either invalid or absent. Recommended Run the configure command to disable HTTPS.

  • Page 524: Webd-1004

    WEBD-1004 WEBD-1004 Message <timestamp>, [WEBD-1004], <sequence-number>,, INFO, <system-name>, HTTP server will be restarted due to configuration change Probable Cause Indicates that the HTTP server configuration has changed. Recommended No action is required. Action Severity INFO WEBD-1005 Message <timestamp>, [WEBD-1005], <sequence-number>,, WARNING, <system-name>, HTTP server will be restarted for logfile truncation Probable Cause Indicates that the size of HTTP logfile exceeded the maximum limit.

  • Page 525: Webd-1008

    WEBD-1008 WEBD-1008 Message <timestamp>, [WEBD-1008], <sequence-number>, FFDC, WARNING, <system-name>, HTTP server cannot be started Probable Cause Indicates a rare error condition, where the built-in recovery process has failed to restore http services. The problem often results from invalid configuration of ssl certs., but there can be more than one reason for such failure.
  • Page 526 WEBD-1008 Fabric OS Message Reference 53-1000600-01...

  • Page 527: Zolb-1001

    Chapter ZOLB System Messages ZOLB-1001 Message <timestamp>, [ZOLB-1001], <sequence-number>,, ERROR, <system-name>, ZONELIB <error message> Probable Cause Indicates that there was an internal timeout on the inter process communication (IPC) between the name server (NS) and the zoning modules. This usually indicates that the system was busy. Recommended This message generates core dump files of the related modules (zoned, nsd, rcsd).
  • Page 528 ZOLB-1001 Fabric OS Message Reference 53-1000600-01...

  • Page 529: Zone-1002

    Chapter ZONE System Messages ZONE-1002 Message <timestamp>, [ZONE-1002], <sequence-number>,, WARNING, <system-name>, WWN zoneTypeCheck or zoneGroupCheck warning(<warning string>) at port(<port number>) Probable Cause Indicates that a zone filter or zone group check failure occurred. The frame filter logic reported a failure when creating or adding zone groups during port login (PLOGI) trap processing. This messages usually indicates problems when adding content-addressable memory (CAM) entries before the filter setup.

  • Page 530: Zone-1004

    ZONE-1004 ZONE-1004 Message <port <timestamp>, [ZONE-1004], <sequence-number>,, INFO, <system-name>, port number> enforcement changed to Session Based HARD Zoning. Probable Cause Indicates that the zoning enforcement changed to session-based hard zoning. When a device is zoned using both world-wide name (WWN) in one zone and <domain, portarea> in another, this will cause that port to go session based hard zoning.

  • Page 531: Zone-1006

    ZONE-1006 ZONE-1006 Message <timestamp>, [ZONE-1006], <sequence-number>,, WARNING, <system-name>, WARNING - WWN(<WWN number>) in HARD PORT zone <zone_name>. Probable Cause Indicates that one or more devices are zoned as world-wide name (WWN) devices and also zoned as <domain, portarea> devices. The device(s) are used to specify zone members over separate zones.

  • Page 532: Zone-1010

    ZONE-1010 ZONE-1010 Message <timestamp>, [ZONE-1010], <sequence-number>,, WARNING, <system-name>, WARNING - <zone name> Duplicate entries in zone( ) specification. Probable Cause Indicates that there are duplicate entries in a zone object. A zone object member is specified twice in a given zone object. This message occurs only when enabling a zone configuration. Recommended Check the members of the zone and delete the duplicate member.

  • Page 533: Zone-1014

    ZONE-1014 ZONE-1014 Message <timestamp>, [ZONE-1014], <sequence-number>,, ERROR, <system-name>, Missing <license name> required license - Probable Cause Indicates that the required zoning license is missing. Recommended Install the zoning license using the licenseAdd command. Refer to your switch supplier to obtain a Action Zoning license if you do not have one.

  • Page 534: Zone-1018

    ZONE-1018 ZONE-1018 Message <timestamp>, [ZONE-1018], <sequence-number>,, ERROR, <system-name>, Incorrect zoning enforcement type(<zone type>) at port(<port number>). Probable Cause Indicates that an incorrect zoning enforcement type was reported on the specified port. This is a software error. A QuickLoop zone type (value = 4) or an uninitialized type (value = 0) are invalid. The valid zone type values are: •...

  • Page 535: Zone-1022

    ZONE-1022 ZONE-1022 Message <timestamp>, [ZONE-1022], <sequence-number>,, INFO, <system-name>, The effective configuration has changed to <Effective configuration name>. <AD Id> Probable Cause Indicates that the effective zone configuration has changed to the name displayed. Recommended Verify that this zone configuration change was done on purpose. If the new effective zone Action configuration is correct, no action is necessary.

  • Page 536: Zone-1026

    ZONE-1026 ZONE-1026 Message <port <timestamp>, [ZONE-1026], <sequence-number>,, INFO, <system-name>, port number> Out of CAM entries. Probable Cause Indicates that the total number of S_ID entries while creating or adding a zone group exceeds the limit. Recommended If hardware zoning enforcement is preferred, edit the zoning database to have zoned PIDs for that Action port.

  • Page 537: Zone-1028

    ZONE-1028 ZONE-1028 Message <timestamp>, [ZONE-1028], <sequence-number>,, WARNING, <system-name>, Commit zone DB larger than supported - <zone db size> greater than <max zone db size>. Probable Cause Indicates that the zone database size is greater than the limit allowed by the fabric. The limit of the zone database size depends on the lowest level switch in the fabric.

  • Page 538: Zone-1031

    ZONE-1031 ZONE-1031 Message <timestamp>, [ZONE-1031], <sequence-number>,, ERROR, <system-name>, Switch is in interop mode. (switch, port) members not supported. Probable Cause The switch is set to interop mode using the interopMode command. Interop mode does not allow <domain, portarea> members in the active zone database. Recommended Remove all <domain, portarea>...

  • Page 539: Zone-1034

    ZONE-1034 ZONE-1034 Message <timestamp>, [ZONE-1034], <sequence-number>,, WARNING, <system-name>, Zoning file doesn't exist or Corrupted Zoning files detected before reboot, currently the file <config file name> is saved at Probable Cause Indicates that the zone database is corrupt or zone database is not found. Recommended Use the firmwareDownload command to reinstall the firmware.

  • Page 540: Zone-1037

    ZONE-1037 ZONE-1037 Message <timestamp>, [ZONE-1037], <sequence-number>,, ERROR, <system-name>, Unable to examine <config file name>: error message <System Error Message>. Probable Cause Indicates that the Fabric OS cannot examine the zone configuration file. Typically the zone configuration is too large for the memory available on the switch. Recommended Reduce the size of the zone database and retry the operation.

  • Page 541: Zone-1040

    ZONE-1040 ZONE-1040 Message <timestamp>, [ZONE-1040], <sequence-number>,, INFO, <system-name>, Merged zone database exceeds limit. Probable Cause Indicates that the Fabric OS cannot read the merged zone configuration file. Typically the zone configuration is too large for the memory available on the switch. Recommended Reduce the size of the zone database and retry the operation.

  • Page 542: Zone-1044

    ZONE-1044 ZONE-1044 Message <timestamp>, [ZONE-1044], <sequence-number>,, INFO, <system-name>, The Default Zone access mode is set to All Access. Probable Cause Indicates that the Default Zone access mode is set to All Access. Recommended Verify that this Default Zone access mode change was done intentionally. Action Severity INFO...

  • Page 543: Auth-3001

    Chapter AUDIT AUTH System Messages AUTH-3001 Message AUDIT, <timestamp>, [AUTH-3001], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Data type> type has been changed from [<Old value>] to [<New value>]. Probable Cause Indicates that an authentication configuration value was set to a specified value. The data type is “authentication type”, “DH group type”, “Hash type”, or “policy type”.

  • Page 544: Auth-3004

    AUTH-3004 AUTH-3004 Message AUDIT, <timestamp>, [AUTH-3004], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Neighboring switch has a conflicting authentication policy; Port <Port Number> disabled. Probable Cause The specified E_Port was disabled because the neighboring switch rejected the authentication negotiation, and the local switch has a strict switch authentication policy.

  • Page 545: Auth-3007

    AUTH-3007 AUTH-3007 Message AUDIT, <timestamp>, [AUTH-3007], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Port <port number> disabled due to receiving an authentication reject with code '<Reason String>' and explanation '<Explanation String>'. Probable Cause Indicates that the specified port was disabled due to receiving an authentication reject response from the connected switch/device.
  • Page 546 AUTH-3008 Fabric OS Message Reference 53-1000600-01...

  • Page 547: Conf-1020

    Chapter AUDIT CONF System Messages CONF-1000 Message AUDIT, <timestamp>, [CONF-1000], INFO, CFG, <event-initiator-details>, <Info about the <event-location>, , configDownload completed successfully. parameters and AD> Probable Cause The configDownload process was initiated and completed successfully. The message string describes the class of configuration parameters that were downloaded. If admin domain (AD) is enabled, the AD number is specified in the description.
  • Page 548 CONF-1022 Fabric OS Message Reference 53-1000600-01...

  • Page 549: Http-1002

    Chapter AUDIT HTTP System Messages HTTP-1002 Message AUDIT, <timestamp>, [HTTP-1002], INFO, ZONE, <event-initiator-details>, <event-location>, , Zoning transaction initiated by User: <User Name>, Role: <User Role> completed successfully. Probable Cause Indicates that the zoning database has been changed. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
  • Page 550 HTTP-1003 Fabric OS Message Reference 53-1000600-01...

  • Page 551: Sec-3001

    Chapter AUDIT SEC System Messages SEC-3001 Message AUDIT, <timestamp>, [SEC-3001], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Security mode <State change: Enabled or Disabled> on the fabric. Probable Cause Indicates that the security mode of the fabric was either enabled or disabled. Recommended Verify that the security mode change was planned.

  • Page 552: Sec-3003

    SEC-3003 SEC-3003 Message AUDIT, <timestamp>, [SEC-3003], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Created <Policy Name> policy, with member(s) <Member List> . Probable Cause Indicates that a new security policy was created with entries. Note: If you use a wildcard (for example, an asterisk) in creating a policy, the audit report displays the wildcard in the event info field.

  • Page 553: Sec-3006

    SEC-3006 SEC-3006 Message AUDIT, <timestamp>, [SEC-3006], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Removed member(s) <Members removed> from policy <Policy name>. Probable Cause Indicates that a user has removed the specific members from the specified security policy. Note: If you use a wildcard (for example, an asterisk) in removing members from a policy, the audit report displays the wildcard in the event info field.

  • Page 554: Sec-3009

    SEC-3009 SEC-3009 Message AUDIT, <timestamp>, [SEC-3009], INFO, SECURITY, <event-initiator-details>, <Event Name> <event-location>, , Event: , Status: success, Info: Security Transaction aborted. Probable Cause Indicates that the pending security transaction was aborted. Recommended Verify that the security transaction was intentionally aborted. If the security transaction was Action intentionally aborted, no action is required.

  • Page 555: Sec-3012

    SEC-3012 SEC-3012 Message AUDIT, <timestamp>, [SEC-3012], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Temp Passwd <Password Set or Reset> on domain [<Domain ID>] for account [<Account name>]. Probable Cause Indicates that a user has reset the password for the specified user accounts. Recommended Verify that the password was intentionally reset.

  • Page 556: Sec-3015

    SEC-3015 SEC-3015 Message AUDIT, <timestamp>, [SEC-3015], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Moved RADIUS server <Server name> to position <New position>. Probable Cause Indicates that a user has changed the position of the remote authentication dial-in user service (RADIUS) server.

  • Page 557: Sec-3018

    SEC-3018 SEC-3018 Message AUDIT, <timestamp>, [SEC-3018], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Parameter [<Parameter Name>] changed from [<Old Value>] to [<New Value>]. Probable Cause Indicates that the specified passwdCfg parameter is changed. Recommended Verify that the passwdCfg parameter was intentionally changed. If the passwdCfg parameter was Action intentionally changed, no action is required.

  • Page 558: Sec-3021

    SEC-3021 SEC-3021 Message AUDIT, <timestamp>, [SEC-3021], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Failed login attempt via <connection method and IP Address>. Probable Cause Indicates that a failed login attempt occurred. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.

  • Page 559: Sec-3024

    SEC-3024 SEC-3024 Message AUDIT, <timestamp>, [SEC-3024], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>], password changed. Probable Cause Indicates that the user’s password changed. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.

  • Page 560: Sec-3027

    SEC-3027 SEC-3027 Message AUDIT, <timestamp>, [SEC-3027], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] [<Changed Attributes>]. Probable Cause Indicates that user account properties were changed. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.

  • Page 561: Sec-3030

    SEC-3030 SEC-3030 Message AUDIT, <timestamp>, [SEC-3031], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info:<Event Specific Info> Probable Cause Indicates the specified secCertUtil operation was performed. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.

  • Page 562: Sec-3033

    SEC-3033 SEC-3033 Message AUDIT, <timestamp>, [SEC-3033], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: fddcfg --fabwideset, Status: success, Info: Fabric wide <Fabric-wide configuration set by user> configuration set to Probable Cause Indicates that the specified event has occurred. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.

  • Page 563: Sec-3037

    SEC-3037 Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3037 Message AUDIT, <timestamp>, [SEC-3037], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: ipfilter, Status: success, Info: <IP Filter Policy>...

  • Page 564: Sec-3044

    SEC-3044 SEC-3044 Message AUDIT, <timestamp>, [SEC-3044], INFO, SECURITY, <event-initiator-details>, <event-location>, FIPS mode has been changed to <Fips Mode>. Probable Cause Indicates that there was a change in the FIPS mode. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.

  • Page 565: Sec-3048

    SEC-3048 Severity INFO SEC-3048 Message AUDIT, <timestamp>, [SEC-3048], INFO, SECURITY, <event-initiator-details>, <event-location>, FIPS mode has been enabled in the system using force option. Probable Cause Indicates that the system has been forced to FIPS mode. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 566 SEC-3049 Fabric OS Message Reference 53-1000600-01...

  • Page 567: Snmp-1005

    Chapter AUDIT SNMP System Messages SNMP-1004 Message AUDIT, <timestamp>, [SNMP-1004], ERROR, CONFIGURATION, <event-initiator-details>, <event-location>, , Incorrect SNMP configuration. Probable Cause Indicates that the simple network management protocol (SNMP) configuration s incorrect and the SNMP service will not work correctly. Recommended Reset the SNMP configuration to default.
  • Page 568 SNMP-1006 Fabric OS Message Reference 53-1000600-01...

  • Page 569: Sulb-1002

    Chapter AUDIT SULB System Messages SULB-1001 Message AUDIT, <timestamp>, [SULB-1001], WARNING, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwaredownload command has started. Probable Cause Indicates that the firmwareDownload command has been entered. This process should take approximately 17 minutes. The process is set to time out after 30 minutes. Recommended No action is required.

  • Page 570: Sulb-1009

    SULB-1004 SULB-1004 Message AUDIT, <timestamp>, [SULB-1004], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwarecommit has completed. Probable Cause Indicates that the FirmwareCommit command is executed. Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action Severity INFO SULB-1009 Message AUDIT, <timestamp>, [SULB-1009], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwaredownload command failed.
  • Page 571 SULB-1009 TABLE 9 Status Messages and Status Codes Status Message Status Code “firmwareCommit operation failed due to IPC error.” 0x55 "Unable to check the firmware version on Standby CP due to IPC error." 0x56 “Unable to restore the original firmware due to Standby CP timeout.” 0x57 "Standby CP failed to reboot and was not responding."...
  • Page 572 SULB-1009 TABLE 9 Status Messages and Status Codes Status Message Status Code "The original firmware has been restored successfully on Standby CP." 0x7e "Unable to restore the original firmware on Standby CP." 0x7f "Standby CP reboots." 0x80 "Standby CP failed to reboot." 0x81 "Standby CP booted up with new firmware."...
  • Page 573 SULB-1009 TABLE 9 Status Messages and Status Codes Status Message Status Code “firmwareRestore is entered. System will reboot and a firmwareCommit operation will start 0xa8 upon boot up.” "Switch is relocating the AP image." 0xa9 "The AP image is relocated successfully." 0xaa "Switch reboots during relocating the AP image.
  • Page 574 SULB-1009 TABLE 10 Error Messages and Error Codes Error Message Error Code "Both images are mounted to the same device." 0x20 “Unable to unionist old packages.” 0x21 “firmwareDownload is already in progress.” 0x22 “firmwareDownload timed out.” 0x23 "Our of disk space." 0x24 “Primary filesystem is inconsistent.
  • Page 575 SULB-1009 0x23 - firmwareDownload timed out. This error may occur because firmwareDownload has not completed within the predefined timeout period. It is most often caused by network issues. If the problem persists, contact your system administrator. 0x24 - out of disk space. This error may occur because some coredump files have not been removed from the filesystem and are using up disk space.

  • Page 576: Sulb-1017

    SULB-1010 Recommended Run the firmwareDownloadStatus command for more information. Action In a director-class switch, when firmwareDownload fails, the command will synchronize the firmware on the two partitions of each CP by starting a firmware commit operation. Wait until this operation completes (about 10 minutes) before attempting another firmwareDownload. In a director-class switch, when firmwareDownload fails, the two CPs may end up with different versions of firmware and they may not gain high-availability (HA) sync.

  • Page 577: Sulb-1020

    SULB-1020 Probable Cause The error may be caused by a blade initialization issue after the new firmware is downloaded and the blade is rebooted. The error may also be caused by an internal Ethernet issue or by a persistent storage failure. Recommended Run the slotShow command.

  • Page 578: Sulb-1024

    SULB-1024 Recommended firmwareCommit will be started automatically after the blade boots up to repair the secondary Action partition. If at the end of firmwareCommit, the blade firmware version is still inconsistent with the active CP firmware, firmwareDownload will automatically be restarted on the blade. Run the firmwareDownloadStatus command to monitor the progress.

  • Page 579: Sulb-1031

    SULB-1031 Recommended firmwareDownload will continue after the switch has rebooted. Run the firmwareDownloadStatus Action command to monitor progress. If the problem persists, contact your switch service provider. Severity WARNING SULB-1031 Message AUDIT, <timestamp>, [SULB-1032], WARNING, FIRMWARE, <event-initiator-details>, <event-location>, , Relocating an internal firmware image on the CP. Probable Cause Indicates that the switch has rebooted with the new firmware and is relocating the AP firmware.

  • Page 580: Sulb-1035

    SULB-1035 Recommended Reboot the switch. This will cause the internal image to be relocated again. Use the Action firmwareDownloadStatus to monitor the progress. If the problem persists, contact your switch service provider. Severity ERROR SULB-1035 Message AUDIT, <timestamp>, [SULB-1035], ERROR, FIRMWARE, <event-initiator-details>, <event-location>, , An error has occurred relocation of the internal image.

  • Page 581: Zone-3001

    Chapter AUDIT ZONE System Messages ZONE-3001 Message AUDIT, <timestamp>, [ZONE-3001], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object member list>\" added to <Zone object set type> \"<Zone object set name>\". Probable Cause Indicates that a new zone object member or members have been added to the specified zone object set.

  • Page 582: Zone-3003

    ZONE-3003 ZONE-3003 Message AUDIT, <timestamp>, [ZONE-3003], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object name>\" deleted. Probable Cause Indicates that the specified zone object has been deleted. The zone object type can be “alias”, “zone member”, “zone” or “zone configuration”. The string “...” appears at the end of the zone object member list if the list was truncated in the message.

  • Page 583: Zone-3006

    ZONE-3006 ZONE-3006 Message AUDIT, <timestamp>, [ZONE-3006], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Current zone configuration disabled. <AD Id>. Probable Cause Indicates that the current zone configuration has been disabled. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.

  • Page 584: Zone-3009

    ZONE-3009 ZONE-3009 Message AUDIT, <timestamp>, [ZONE-3009], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Event Description>. Probable Cause Indicates that the specified zone transaction has been aborted. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.

  • Page 585: Zone-3012

    ZONE-3012 ZONE-3012 Message AUDIT, <timestamp>, [ZONE-3012], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Zone object \"<Zone object name>\" renamed to \"<New Zone object name>\". Probable Cause Indicates that the specified zone object has been renamed. Recommended Verify that the event was planned.

  • Page 586: Zone-3015

    ZONE-3015 ZONE-3015 Message AUDIT, <timestamp>, [ZONE-3015], INFO, FABRIC, <event-initiator-details>, <Event Name> <event-location>, , Event: , Status: success, Info: AD configurations applied. Probable Cause Indicates that the current admin domain (AD) configuration has been saved to flash is being enforced. Recommended Verify that the event was planned.

  • Page 587: Zone-3018

    ZONE-3018 ZONE-3018 Message AUDIT, <timestamp>, [ZONE-3018], INFO, FABRIC, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <AD object name> has been deactivated. Probable Cause Indicates that the specified admin domain (AD) object has been deactivated. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.

  • Page 588: Zone-3021

    ZONE-3021 ZONE-3021 Message AUDIT, <timestamp>, [ZONE-3021], INFO, FABRIC, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: AD object \"<AD object name>\" renamed to \"<New AD object name>\". Probable Cause Indicates that the specified admin domain (AD) has been renamed. Recommended Verify that the event was planned.

  • Page 589: Zone-3024

    ZONE-3024 ZONE-3024 Message AUDIT, <timestamp>, [ZONE-3024], INFO, FABRIC, <event-initiator-details>, <event-location>, , Command: <Command Name>, Status: success, Info: executed. <AD Id>. Probable Cause Indicates that the admin domain ad --transabort operation was successful in the specified AD. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
  • Page 590 ZONE-3025 Fabric OS Message Reference 53-1000600-01...

This manual is also suitable for:

Ae370a - brocade 4gb san switch 4/12

Table of Contents