Brocade Communications Systems StoreFabric SN6500B Reference
  1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Software
  5. StoreFabric SN6500B
  6. Reference

Brocade Communications Systems StoreFabric SN6500B Reference

Brocade fabric os message reference v7.1.0 (53-1002749-01, march 2013)
Hide thumbs Also See for StoreFabric SN6500B:
1
2
3
4
5
6
Table Of Contents
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
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Administrator's Manual
53-1002749-01
®
14 December 2012
Fabric OS
Message Reference
Supporting Fabric OS v7.1.0

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the StoreFabric SN6500B and is the answer not in the manual?

Questions and answers

Related Manuals for Brocade Communications Systems StoreFabric SN6500B

Summary of Contents for Brocade Communications Systems StoreFabric SN6500B

  • Page 1 53-1002749-01 ® 14 December 2012 Fabric OS Message Reference Supporting Fabric OS v7.1.0...
  • Page 2 Copyright © 2002-2012 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron, TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health, OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
  • Page 3 Title Publication Summary of changes Date number Fabric OS System Error Message 53-0000515-09 Updated for v4.4.0, August 2004 Reference Manual First RASLog release Fabric OS System Error Message 53-0000515-10 Added 22 ZONE messages April 2005 Reference Manual Fabric OS System Error Message 53-0000515-11 Added FICU-1010, HAMK-1004, and July 2005...
  • Page 4 Title Publication Summary of changes Date number Fabric OS Message Reference 53-1001157-01 Updated for Fabric OS v6.2.0: November 2008 -Revised and added new messages to FSS, KSWD, CTAP, CNM, CVLM, EM, FABR, FCIP, FW, HIL, FCR, SEC, SWCH, UCST, ZONE. -Added new chapters: CHASSIS, LFM, PMGR, TAPE.
  • Page 5 Title Publication Summary of changes Date number Fabric OS Message Reference 53-1002149-01 Updated for Fabric OS v7.0.0: April 2011 -Added new chapters: C3, CAL, MCAST_SS, RTE, and VS. -Added new messages: AG, AN, ANV, BL, C2, CDR, CCFG, ECC, EM, ESS, FABR, FCOE, FCPH, FICN, FICU, FSPF, FW, HIL, IPAD, IPS, KAC, L2SYS, LACP, LOG, MS, NS, NSM, ONM, PDM, PS, RAS, RCS,...

  • Page 7: Table Of Contents

    Contents About This Document How this document is organized ........xiii Supported hardware and software .
  • Page 8 Configuring system messages and attributes......15 Configuring event auditing ........15 Disabling a RASLog message or module .
  • Page 9 AUTH Messages ..........144 BKSW Messages .
  • Page 10 FW Messages ...........438 HAM Messages .
  • Page 11 PORT Messages ..........657 PS Messages .
  • Page 12 Fabric OS Message Reference 53-1002749-01...

  • Page 13: About This Document

    About This Document In this chapter • How this document is organized ........xiii •...
  • Page 14 The following hardware platforms are supported by this release of Fabric OS: • Brocade 300 • Brocade 5100 • Brocade 5300 • Brocade 5410 • Brocade 5424 • Brocade 5430 • Brocade 5450 • Brocade 5460 • Brocade 5470 • Brocade 5480 •...

  • Page 15: What's New In This Document

    What’s new in this document The following changes have been made since this document was last released: • The lookup lists in Chapter 2 through Chapter 4 provide hyperlinks to messages by type (LOG, Audit, and FFDC). • Information that was added: AG Messages ANV Messages BL Messages...
  • Page 16 • Information that was changed: AN Messages AUTH Messages BL Messages C2 Messages C3 Messages CDR Messages CAL Messages CNM Messages DOT1 Messages FABR Messages FCOE Messages FCPD Messages FCR Messages FICU Messages FSPF Messages FSS Messages HIL Messages HSL Messages HTTP Messages IPS Messages KAC Messages...

  • Page 17: Document Conventions

    • Information that was deleted: BLL System Messages CER System Messages EM Messages FCIP System Messages FCOE Messages HAM Messages IBPD System Messages ICPD System Messages SNMP Messages SYSC Messages UCST Messages ZONE Messages For further information about new features and documentation updates for this release, refer to the release notes.

  • Page 18: Command Examples

    command Commands are printed in bold. option, option Command options are printed in bold. argument, arg Arguments. Optional element. variable Variables are printed in italics. In the help pages, values are underlined or enclosed in angled brackets < >. Repeat the previous element, for example “member[;member...]” value Fixed values following arguments are printed in plain font.

  • Page 19: Key Terms

    Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade. “Brocade resources” on page xix for instructions on accessing MyBrocade. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia.org/education/dictionary Notice to the reader This document may contain references to the trademarks of the following corporations.

  • Page 20: Getting Technical Help

    For information about the Fibre Channel industry, visit the Fibre Channel Industry Association website: http://www.fibrechannel.org Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1.

  • Page 21: Document Feedback

    If you cannot use the licenseIdShow command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX. For the Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo plate at the top of the non-port side of the chassis.
  • Page 22 xxii Fabric OS Message Reference 53-1002749-01...

  • Page 23: Overview Of System Messages

    Chapter Introduction to System Messages In this chapter • Overview of system messages ........1 •...

  • Page 24: Audit Log Messages

    Overview of system messages RASLog messages RASLog messages report significant system events (failure, error, or critical conditions) or information and are also used to show the status of the high-level user-initiated actions. RASLog messages are forwarded to the console, to the configured syslog servers, and to the SNMP management station through the Simple Network Management Protocol (SNMP) traps or informs.

  • Page 25: Message Severity Levels

    Overview of system messages TABLE 1 Event classes (Continued) Operand Event class Description You can audit Fabric Watch (FW)-related changes. You can audit Virtual Fabric (Logical Switch)-related changes. You can audit the CLI commands executed on the switch. Used to audit or track the RASLog messages or modules that are enabled or disabled using the rasAdmin command.

  • Page 26: System Error Message Logging

    Overview of system messages TABLE 2 Severity levels of a message Severity level Description 1 = CRITICAL Critical-level messages indicate that the software has detected serious problems that will cause a partial or complete failure of a subsystem if not corrected immediately; for example, a power supply failure or rise in temperature must receive immediate attention.

  • Page 27: Configuring The Syslog Message Destinations

    Configuring the syslog message destinations Configuring the syslog message destinations You can configure the Fabric OS to send the syslog messages to the following output locations: syslog daemon, system console, and SNMP management station. System logging daemon The system logging daemon (syslogd) is a process on UNIX, Linux, and some Windows systems that reads and logs messages as specified by the system administrator.

  • Page 28: Snmp Trap Recipient

    Configuring the syslog message destinations The system console displays messages only through the serial port. If you log in to a switch through the Ethernet port or modem port, you will not receive system console messages. You can filter messages that display on the system console by severity using the errFilterSet command.
  • Page 29 Configuring the syslog message destinations The SNMP traps are unreliable because the trap recipient does not send any acknowledgment when it receives a trap. Therefore, the SNMP agent cannot determine if the trap was received. Brocade switches send traps out on UDP port 162. To receive traps, the management station IP address must be configured on the switch.
  • Page 30 Configuring the syslog message destinations Trap recipient Severity level: 2 SNMPv1:Enabled Configuring the SNMPv3 trap recipient To configure the SNMPv3 host to receive the trap, perform the following steps. 1. Log in to the switch as admin. 2. Execute the snmpConfig set snmpv3 command to configure the SNMP trap recipient.

  • Page 31: Snmp Inform Recipient

    Configuring the syslog message destinations 3. Execute the snmpConfig show snmpv3 command to verify the SNMP agent configuration. switch:admin> snmpconfig --show snmpv3 SNMP Informs = 0 (OFF) SNMPv3 USM configuration: User 1 (rw): snmpadmin1 Auth Protocol: noAuth Priv Protocol: noPriv User 2 (rw): snmpadmin2 Auth Protocol: MD5 Priv Protocol: noPriv...
  • Page 32 Configuring the syslog message destinations Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2] Engine ID: [0:0:0:0:0:0:0:0:0] User (rw): [snmpadmin2] Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] 1 New Auth Passwd: Verify Auth Passwd: Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (1..6) [2] 1 New Priv Passwd: Verify Priv Passwd: Engine ID: [0:0:0:0:0:0:0:0:0] 80:00:05:23:01:0A:23:34:1B User (rw): [snmpadmin3] Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]...

  • Page 33: Port Logs

    Changing the severity level of swEventTrap Priv Protocol: noPriv Engine ID: 80:00:05:23:01:0a:23:34:21 User 2 (rw): snmpadmin2 Auth Protocol: MD5 Priv Protocol: DES Engine ID: 80:00:05:23:01:0a:23:34:1b User 3 (rw): snmpadmin3 Auth Protocol: noAuth Priv Protocol: noPriv Engine ID: 00:00:00:00:00:00:00:00:00 User 4 (ro): snmpuser1 Auth Protocol: noAuth Priv Protocol: noPriv Engine ID: 00:00:00:00:00:00:00:00:00...
  • Page 34 Changing the severity level of swEventTrap To change the severity level of swEventTrap, perform the following steps. 1. Log in to the switch as admin. 2. Execute the snmpConfig set mibCapability command to configure MIBs interactively. All the supported MIBs and associated traps are displayed. You can change the DesiredSeverity for swEventTrap to 1 (Critical), 2 (Error), 3 (Warning), or 4 (Informational).

  • Page 35: Commands For Displaying And Configuring The System Message Logs

    Commands for displaying and configuring the system message logs IF-MIB: YES BD-MIB: YES SW-TRAP: YES swFault: YES swSensorScn: YES swFCPortScn: YES swEventTrap: YES DesiredSeverity:Informational swFabricWatchTrap: YES DesiredSeverity:Critical swTrackChangesTrap: YES swIPv6ChangeTrap: YES swPmgrEventTrap: YES swFabricReconfigTrap: YES [...] Commands for displaying and configuring the system message logs Table 3 describes commands that you can use to view or configure the system message logs.

  • Page 36: Displaying Message Content On Switch

    Displaying message content on switch TABLE 3 Commands for viewing or configuring the system parameters and message logs (Continued) Command Description portLogResize Resizes the port log to the specified number of entries. portLogShow Displays the port log, with page breaks. portLogShowPort Displays the port log of the specified port, with page breaks.

  • Page 37: Configuring System Messages And Attributes

    Configuring system messages and attributes For example, execute the following command to display the documentation for PS-1007. switch:admin> rasman PS-1007 Log Messages PS-1007(7m) MESSAGE PS-1007 Failed Fabricmode Talker domain=<domain id>. <function name>. MESSAGE TYPE SEVERITY WARNING PROBABLE CAUSE Indicates that FC Routing (FCR) is enabled on the specified fabric.

  • Page 38: Disabling A Raslog Message Or Module

    Configuring system messages and attributes 5. Execute the auditCfg show command to verify the configuration. switch:admin> auditcfg --show Audit filter is enabled. 1-ZONE 2-SECURITY 3-CONFIGURATION 4-FIRMWARE 5-FABRIC 6-FW 7-LS 8-CLI Severity level: ERROR You must configure the syslog daemon to send the Audit events to a configured remote host using the syslogdIpAdd command.

  • Page 39: Enabling A Raslog Message Or Module

    Displaying system message logs and attributes Enabling a RASLog message or module To enable a single RASLog message or all messages in a module that were previously disabled, perform the following steps. 1. Log in to the switch as admin. 2.

  • Page 40: Displaying Raslog Messages

    Displaying system message logs and attributes Displaying RASLog messages To display the system message log on a switch with no page breaks, perform the following steps. You can display the messages in reverse order using the reverse option. To display message logs in all switches (logical switches), use the all option.

  • Page 41: Displaying Audit Messages

    Displaying system message logs and attributes Displaying Audit messages To display the Audit messages, perform the following steps. Beginning with Fabric OS v7.1.0 release, the RAS-3005 message is generated for each CLI command executed on switch and is saved in the Audit message log. 1.

  • Page 42: Displaying Status Of The System Messages

    Displaying system message logs and attributes Displaying status of the system messages To display the status of the system message, perform the following steps. 1. Log in to the switch as admin. 2. Use the following commands to display the status of all messages in the log, a single message, or all messages that belong to a module: •...

  • Page 43: Displaying Raslog Messages By Severity Level

    Displaying system message logs and attributes Displaying RASLog messages by severity level To display the RASLog messages based on the severity level, perform the following steps. 1. Log in to the switch as admin. 2. Execute the errdump --severity [DEFAULT | INFO | WARNING | ERROR | CRITICAL] command. For more information on message severity levels, refer to “Message severity levels”...

  • Page 44: Viewing Raslog Messages From Web Tools

    Clearing the system message logs 2012/06/19-03:26:44, [SULB-1003], 32, SLOT 4 | CHASSIS, INFO, switch, Firmwarecommit has started. 2012/06/19-03:26:44, [IPAD-1001], 33, SLOT 4 | CHASSIS, INFO, switch, CP/1 IPv6 manual fe80::224:38ff:fe1b:4400 DHCP Off. 2012/06/19-03:29:15, [IPAD-1000], 48, SLOT 4 | CHASSIS, INFO, switch, CP/0 Ether/0 IPv6 autoconf fd00:60:69bc:816:205:1eff:fe84:3f49/64 tentative DHCP Off.

  • Page 45: Clearing The Audit Message Log

    Reading the system messages Clearing the Audit message log To clear the Audit message log for a particular switch instance, perform the following steps. 1. Log in to the switch as admin. 2. Execute the auditDump -c command to clear all Audit messages from memory. Reading the system messages This section provides information about reading the RASLog and Audit messages.

  • Page 46: Reading An Audit Message

    Reading the system messages TABLE 4 System message field description (Continued) Variable name Description Sequence Number The error message position in the log. When a new message is added to the log, this number is incremented by 1. The message sequence number starts at 1 after a firmwareDownload and will increase up to a value of 2,147,483,647 (0x7ffffff).
  • Page 47 Reading the system messages The fields in the error message are described in Table TABLE 5 Audit message field description Variable name Description Sequence Number The error message position in the log. Audit flag Identifies the message as an Audit message. Time Stamp The system time (UTC) when the message was generated on the switch.

  • Page 48: Responding To A System Message

    Responding to a system message Responding to a system message This section provides procedures on gathering information on system messages. Looking up a system message Messages in this manual are arranged alphabetically by Module ID, and then numerically within a given module.

  • Page 49: Support

    Responding to a system message • Are serial port (console) logs available? • Which CP was master? • What and when were the last actions or changes made to the system? Common steps to be followed when troubleshooting a system message are as follows: •...

  • Page 50: System Module Descriptions

    System module descriptions System module descriptions Table 6 provides a summary of the system modules for which messages are documented in this guide; the system modules are listed alphabetically by name. A module is a subsystem in the Fabric OS. Each module generates a set of numbered messages. TABLE 6 System module descriptions System...
  • Page 51 System module descriptions TABLE 6 System module descriptions (Continued) System Description module Error Checking and Correction (ECC) error messages indicate single-bit and multiple-bit errors in the Dynamic Random Access Memory (DRAM) devices. ECC is a technology that helps to correct memory errors.
  • Page 52 System module descriptions TABLE 6 System module descriptions (Continued) System Description module The Fabric OS state synchronization framework provides facilities by which the active control processor (CP) can synchronize with the standby CP, enabling the standby CP to take control of the switch nondisruptively during failures and software upgrades.
  • Page 53 System module descriptions TABLE 6 System module descriptions (Continued) System Description module • KSWD Fabric daemon (fabricd) • (continued) Fabric Device Management Interface daemon (fdmid) • Fabric Watch daemon (fwd) • FCoE daemon (fcoed) • Fibre Channel Protocol daemon (fcpd) •...
  • Page 54 System module descriptions TABLE 6 System module descriptions (Continued) System Description module LFM error messages indicate problems with the logical fabric manager module that is responsible for making a logical switch use XISLs. This involves creating and managing LISLs in a logical fabric. RASLog subsystem.
  • Page 55 System module descriptions TABLE 6 System module descriptions (Continued) System Description module PORT PORT error messages refer to the front-end user ports on the switch. Front-end user ports are directly accessible by users to connect end devices or connect to other switches. The performance server daemon measures the amount of traffic between endpoints or traffic with particular frame formats, such as SCSI frames, IP frames, and customer-defined frames.
  • Page 56 System module descriptions TABLE 6 System module descriptions (Continued) System Description module SSMD SSMD error messages indicate problems with the System Services Module of the Fabric OS. SULB The software upgrade library provides the firmwareDownload command capability, which enables firmware upgrades to both CP blades with a single command, as well as nondisruptive code load to all Fabric OS switches.

  • Page 57: Chapter 2 Log Messages

    Chapter Log Messages AG Messages AG-1001 AG-1002 AG-1003 AG-1004 AG-1005 AG-1006 AG-1007 AG-1008 AG-1009 AG-1010 AG-1011 AG-1012 AG-1013 AG-1014 AG-1015 AG-1016 AG-1017 AG-1018 AG-1019 AG-1020 AG-1021 AG-1022 AG-1023 AG-1024 AG-1025 AG-1026 AG-1027 AG-1028 Fabric OS Message Reference 53-1002749-01...

  • Page 58: An Messages

    AN Messages AG-1029 AG-1030 AG-1031 AG-1032 AG-1033 AG-1034 AG-1035 AG-1036 AG-1037 AG-1038 AG-1039 AG-1040 AG-1041 AG-1042 AG-1043 AG-1044 AN Messages AN-1001 AN-1002 AN-1003 AN-1004 AN-1005 AN-1010 AN-1011 AN-1012 AN-1013 ANV Messages ANV-1001 ANV-1002 ANV-1003 ANV-1004 ANV-1005 Fabric OS Message Reference 53-1002749-01...

  • Page 59: Auth Messages

    AUTH Messages ANV-1006 ANV-1007 ANV-1008 ANV-1015 ANV-1016 ANV-1028 AUTH Messages AUTH-1001 AUTH-1002 AUTH-1003 AUTH-1004 AUTH-1005 AUTH-1006 AUTH-1007 AUTH-1008 AUTH-1010 AUTH-1011 AUTH-1012 AUTH-1013 AUTH-1014 AUTH-1016 AUTH-1017 AUTH-1018 AUTH-1020 AUTH-1022 AUTH-1023 AUTH-1025 AUTH-1026 AUTH-1027 AUTH-1028 AUTH-1029 AUTH-1030 AUTH-1031 AUTH-1032 Fabric OS Message Reference 53-1002749-01...

  • Page 60: Bksw Messages

    BKSW Messages AUTH-1033 AUTH-1034 AUTH-1035 AUTH-1036 AUTH-1037 AUTH-1038 AUTH-1039 AUTH-1040 AUTH-1041 AUTH-1042 AUTH-1043 AUTH-1044 AUTH-1045 AUTH-1046 AUTH-1047 BKSW Messages BKSW-1003 BL Messages BL-1000 BL-1001 BL-1002 BL-1003 BL-1004 BL-1006 BL-1007 BL-1008 BL-1009 BL-1010 BL-1011 BL-1012 BL-1013 BL-1014 Fabric OS Message Reference 53-1002749-01...
  • Page 61 BL Messages BL-1015 BL-1016 BL-1017 BL-1018 BL-1019 BL-1020 BL-1021 BL-1022 BL-1023 BL-1024 BL-1025 BL-1026 BL-1027 BL-1028 BL-1029 BL-1030 BL-1031 BL-1032 BL-1033 BL-1034 BL-1035 BL-1036 BL-1037 BL-1038 BL-1039 BL-1041 BL-1045 BL-1046 BL-1047 BL-1048 BL-1049 BL-1050 BL-1051 BL-1052 Fabric OS Message Reference 53-1002749-01...

  • Page 62: Bls Messages

    BLS Messages BLS Messages BLS-1000 BLS-1001 BLS-1002 BLS-1003 BLS-1004 BLS-1005 BM Messages BM-1001 BM-1002 BM-1003 BM-1004 BM-1005 BM-1006 BM-1007 BM-1008 BM-1009 BM-1010 BM-1053 BM-1054 BM-1055 BM-1056 BM-1058 C2 Messages C2-1001 C2-1002 C2-1004 C2-1006 C2-1007 C2-1008 C2-1009 C2-1010 Fabric OS Message Reference 53-1002749-01...

  • Page 63: C3 Messages

    C3 Messages C2-1012 C2-1013 C2-1014 C2-1015 C2-1016 C2-1017 C2-1018 C2-1019 C2-1025 C2-1026 C2-1027 C2-1028 C3 Messages C3-1001 C3-1002 C3-1004 C3-1006 C3-1007 C3-1008 C3-1009 C3-1010 C3-1011 C3-1012 C3-1013 C3-1014 C3-1015 C3-1016 C3-1017 C3-1018 C3-1019 C3-1020 C3-1021 C3-1023 C3-1025 Fabric OS Message Reference 53-1002749-01...

  • Page 64: Cal Messages

    CAL Messages C3-1026 C3-1027 C3-1028 CAL Messages CAL-1001 CCFG Messages CCFG-1001 CCFG-1002 CCFG-1003 CCFG-1004 CCFG-1005 CCFG-1006 CCFG-1007 CCFG-1008 CCFG-1009 CCFG-1010 CCFG-1011 CCFG-1012 CDR Messages CDR-1001 CDR-1002 CDR-1003 CDR-1004 CDR-1005 CDR-1006 CDR-1007 CDR-1008 CDR-1009 CDR-1010 CDR-1011 CDR-1012 Fabric OS Message Reference 53-1002749-01...

  • Page 65: Chs Messages

    CHS Messages CDR-1014 CDR-1015 CDR-1016 CDR-1017 CDR-1018 CDR-1019 CDR-1022 CDR-1028 CHS Messages CHS-1002 CHS-1003 CHS-1004 CHS-1005 CNM Messages CNM-1001 CNM-1002 CNM-1003 CNM-1004 CNM-1005 CNM-1006 CNM-1007 CNM-1008 CNM-1009 CNM-1010 CNM-1011 CNM-1012 CNM-1013 CNM-1014 CNM-1015 CNM-1016 CNM-1017 CNM-1018 Fabric OS Message Reference 53-1002749-01...
  • Page 66 CNM Messages CNM-1019 CNM-1020 CNM-1021 CNM-1022 CNM-1023 CNM-1024 CNM-1025 CNM-1026 CNM-1027 CNM-1028 CNM-1029 CNM-1030 CNM-1031 CNM-1032 CNM-1033 CNM-1034 CNM-1035 CNM-1036 CNM-1037 CNM-1038 CNM-1039 CNM-1040 CNM-1041 CNM-1042 CNM-1043 CNM-1044 CNM-1045 CNM-1046 CNM-1047 CNM-1048 CNM-1049 CNM-1050 CNM-1051 CNM-1052 CNM-1053 Fabric OS Message Reference 53-1002749-01...

  • Page 67: Conf Messages

    CONF Messages CNM-1054 CNM-1055 CNM-1056 CNM-1057 CNM-1058 CNM-1059 CNM-1060 CNM-1061 CNM-1062 CNM-3001 CNM-3002 CNM-3003 CNM-3004 CNM-3005 CNM-3006 CNM-3007 CNM-3008 CNM-3009 CNM-3010 CNM-3011 CNM-3012 CONF Messages CONF-1000 CONF-1001 CONF-1021 CONF-1023 CONF-1024 CONF-1030 CONF-1031 CONF-1032 CONF-1040 CONF-1041 CONF-1042 CONF-1043 Fabric OS Message Reference 53-1002749-01...

  • Page 68: Ctap Messages

    CTAP Messages CONF-1044 CTAP Messages CTAP-1001 CVLC Messages CVLC-1001 CVLC-1002 CVLC-1003 CVLC-1004 CVLC-1005 CVLC-1006 CVLC-1007 CVLC-1008 CVLC-1009 CVLC-1010 CVLC-1011 CVLC-1012 CVLC-1013 CVLC-1014 CVLC-1015 CVLC-1016 CVLC-1017 CVLC-1018 CVLC-1019 CVLC-1020 CVLC-1021 CVLC-1022 CVLC-1023 CVLC-1024 CVLC-1025 CVLC-1026 CVLC-1027 CVLC-1028 Fabric OS Message Reference 53-1002749-01...

  • Page 69: Cvlm Messages

    CVLM Messages CVLC-1029 CVLC-1030 CVLC-1031 CVLC-1032 CVLC-1033 CVLC-1034 CVLC-1035 CVLC-1039 CVLC-1041 CVLM Messages CVLM-1001 CVLM-1002 CVLM-1003 CVLM-1004 CVLM-1005 CVLM-1006 CVLM-1007 CVLM-1008 CVLM-1009 CVLM-1010 CVLM-1011 CVLM-1012 CVLM-1013 CVLM-1014 CVLM-1015 CVLM-1016 CVLM-3001 CVLM-3002 CVLM-3003 CVLM-3004 CVLM-3005 CVLM-3006 CVLM-3007 CVLM-3008 Fabric OS Message Reference 53-1002749-01...

  • Page 70: Dot1 Messages

    DOT1 Messages CVLM-3009 CVLM-3010 CVLM-3011 CVLM-3012 CVLM-3013 CVLM-3014 CVLM-3015 CVLM-3016 CVLM-3017 CVLM-3018 CVLM-3019 CVLM-3020 CVLM-3021 CVLM-3022 CVLM-3023 CVLM-3024 CVLM-3025 CVLM-3026 CVLM-3027 CVLM-3028 DOT1 Messages DOT1-1001 DOT1-1002 DOT1-1003 DOT1-1004 DOT1-1005 DOT1-1006 DOT1-1007 DOT1-1008 DOT1-1009 DOT1-1010 Fabric OS Message Reference 53-1002749-01...

  • Page 71: Ecc Messages

    ECC Messages ECC Messages ECC-1000 ECC-1001 EM Messages EM-1001 EM-1002 EM-1003 EM-1004 EM-1005 EM-1006 EM-1008 EM-1009 EM-1010 EM-1011 EM-1012 EM-1013 EM-1014 EM-1015 EM-1016 EM-1017 EM-1018 EM-1019 EM-1020 EM-1028 EM-1029 EM-1031 EM-1033 EM-1034 EM-1035 EM-1036 EM-1037 EM-1042 EM-1043 Fabric OS Message Reference 53-1002749-01...

  • Page 72: Ess Messages

    ESS Messages EM-1044 EM-1045 EM-1046 EM-1047 EM-1048 EM-1049 EM-1050 EM-1051 EM-1057 EM-1058 EM-1059 EM-1060 EM-1061 EM-1062 EM-1063 EM-1064 EM-1065 EM-1066 EM-1067 EM-1068 EM-1069 EM-1070 EM-1071 EM-1072 EM-2003 ESS Messages ESS-1001 ESS-1002 ESS-1003 ESS-1004 ESS-1005 ESS-1008 ESS-1009 ESS-1010 Fabric OS Message Reference 53-1002749-01...

  • Page 73: Esw Messages

    ESW Messages ESW Messages ESW-1001 ESW-1002 ESW-1003 ESW-1004 ESW-1005 ESW-1006 ESW-1007 ESW-1008 EVMD Messages EVMD-1001 FABR Messages FABR-1001 FABR-1002 FABR-1003 FABR-1004 FABR-1005 FABR-1006 FABR-1007 FABR-1008 FABR-1009 FABR-1010 FABR-1011 FABR-1012 FABR-1013 FABR-1014 FABR-1015 FABR-1016 FABR-1017 FABR-1018 FABR-1019 FABR-1020 Fabric OS Message Reference 53-1002749-01...

  • Page 74: Fabs Messages

    FABS Messages FABR-1021 FABR-1022 FABR-1023 FABR-1024 FABR-1029 FABR-1030 FABR-1031 FABR-1032 FABR-1034 FABR-1035 FABR-1036 FABR-1037 FABR-1038 FABR-1039 FABR-1040 FABR-1041 FABR-1043 FABR-1044 FABR-1045 FABR-1046 FABR-1047 FABR-1048 FABR-1049 FABR-1050 FABR-1051 FABR-1052 FABR-1053 FABR-1054 FABR-1055 FABS Messages FABS-1001 FABS-1002 FABS-1004 FABS-1005 Fabric OS Message Reference 53-1002749-01...

  • Page 75: Fbc Messages

    FBC Messages FABS-1006 FABS-1007 FABS-1008 FABS-1009 FABS-1010 FABS-1011 FABS-1013 FABS-1014 FABS-1015 FBC Messages FBC-1001 FCMC Messages FCMC-1001 FCOE Messages FCOE-1001 FCOE-1002 FCOE-1003 FCOE-1004 FCOE-1005 FCOE-1006 FCOE-1007 FCOE-1009 FCOE-1010 FCOE-1012 FCOE-1014 FCOE-1015 FCOE-1016 FCOE-1017 FCOE-1019 FCOE-1021 FCOE-1022 Fabric OS Message Reference 53-1002749-01...

  • Page 76: Fcpd Messages

    FCPD Messages FCOE-1023 FCOE-1024 FCOE-1025 FCOE-1026 FCOE-1027 FCOE-1028 FCOE-1029 FCOE-1030 FCOE-1031 FCOE-1032 FCOE-1033 FCOE-1034 FCOE-1037 FCOE-1038 FCOE-1039 FCOE-1040 FCOE-1041 FCOE-1042 FCOE-1043 FCOE-1044 FCOE-1045 FCOE-1046 FCOE-1047 FCOE-1048 FCPD Messages FCPD-1001 FCPD-1002 FCPD-1003 FCPH Messages FCPH-1001 FCPH-1002 FCPH-1003 Fabric OS Message Reference 53-1002749-01...

  • Page 77: Fcr Messages

    FCR Messages FCPH-1004 FCPH-1005 FCR Messages FCR-1001 FCR-1002 FCR-1003 FCR-1004 FCR-1005 FCR-1006 FCR-1007 FCR-1008 FCR-1009 FCR-1010 FCR-1011 FCR-1012 FCR-1013 FCR-1015 FCR-1016 FCR-1018 FCR-1019 FCR-1020 FCR-1021 FCR-1022 FCR-1023 FCR-1024 FCR-1025 FCR-1026 FCR-1027 FCR-1028 FCR-1029 FCR-1030 FCR-1031 FCR-1032 FCR-1033 Fabric OS Message Reference 53-1002749-01...
  • Page 78 FCR Messages FCR-1034 FCR-1035 FCR-1036 FCR-1037 FCR-1038 FCR-1039 FCR-1040 FCR-1041 FCR-1042 FCR-1043 FCR-1048 FCR-1049 FCR-1053 FCR-1054 FCR-1055 FCR-1056 FCR-1057 FCR-1058 FCR-1059 FCR-1060 FCR-1061 FCR-1062 FCR-1063 FCR-1064 FCR-1065 FCR-1066 FCR-1067 FCR-1068 FCR-1069 FCR-1070 FCR-1071 FCR-1072 FCR-1073 FCR-1074 FCR-1075 Fabric OS Message Reference 53-1002749-01...

  • Page 79: Ficn Messages

    FICN Messages FCR-1076 FCR-1077 FCR-1078 FCR-1079 FCR-1080 FCR-1081 FCR-1082 FCR-1083 FCR-1084 FCR-1085 FCR-1086 FCR-1087 FCR-1088 FCR-1089 FCR-1091 FCR-1092 FCR-1093 FCR-1094 FCR-1095 FCR-1096 FCR-1097 FCR-1098 FICN Messages FICN-1003 FICN-1004 FICN-1005 FICN-1006 FICN-1007 FICN-1008 FICN-1009 FICN-1010 FICN-1011 FICN-1012 FICN-1013 Fabric OS Message Reference 53-1002749-01...
  • Page 80 FICN Messages FICN-1014 FICN-1015 FICN-1016 FICN-1017 FICN-1018 FICN-1019 FICN-1020 FICN-1021 FICN-1022 FICN-1023 FICN-1024 FICN-1025 FICN-1026 FICN-1027 FICN-1028 FICN-1029 FICN-1030 FICN-1031 FICN-1032 FICN-1033 FICN-1034 FICN-1035 FICN-1036 FICN-1037 FICN-1038 FICN-1039 FICN-1040 FICN-1041 FICN-1042 FICN-1043 FICN-1044 FICN-1045 FICN-1046 FICN-1047 FICN-1048 Fabric OS Message Reference 53-1002749-01...
  • Page 81 FICN Messages FICN-1049 FICN-1050 FICN-1051 FICN-1052 FICN-1053 FICN-1054 FICN-1055 FICN-1056 FICN-1057 FICN-1058 FICN-1059 FICN-1060 FICN-1061 FICN-1062 FICN-1063 FICN-1064 FICN-1065 FICN-1066 FICN-1067 FICN-1068 FICN-1069 FICN-1070 FICN-1071 FICN-1072 FICN-1073 FICN-1074 FICN-1075 FICN-1076 FICN-1077 FICN-1078 FICN-1079 FICN-1080 FICN-1081 FICN-1082 FICN-1083 Fabric OS Message Reference 53-1002749-01...
  • Page 82 FICN Messages FICN-1084 FICN-1085 FICN-1086 FICN-1087 FICN-1088 FICN-1089 FICN-1090 FICN-1091 FICN-1092 FICN-1093 FICN-1094 FICN-1095 FICN-1096 FICN-1097 FICN-1098 FICN-1099 FICN-1100 FICN-1101 FICN-1102 FICN-1103 FICN-1104 FICN-1105 FICN-1106 FICN-1107 FICN-1108 FICN-1109 FICN-1110 FICN-1111 FICN-1112 FICN-1113 FICN-1114 FICN-1115 FICN-1116 FICN-1117 FICN-1118 Fabric OS Message Reference 53-1002749-01...

  • Page 83: Ficu Messages

    FICU Messages FICN-1119 FICN-1120 FICN-1121 FICN-1122 FICN-2005 FICN-2006 FICN-2064 FICN-2065 FICN-2066 FICN-2082 FICN-2083 FICN-2085 FICN-2086 FICN-2087 FICU Messages FICU-1001 FICU-1002 FICU-1003 FICU-1004 FICU-1005 FICU-1006 FICU-1007 FICU-1008 FICU-1009 FICU-1010 FICU-1011 FICU-1012 FICU-1013 FICU-1017 FICU-1018 FICU-1019 FICU-1020 FICU-1021 FICU-1022 Fabric OS Message Reference 53-1002749-01...

  • Page 84: Fklb Messages

    FKLB Messages FICU-1023 FICU-1024 FKLB Messages FKLB-1001 FLOD Messages FLOD-1001 FLOD-1003 FLOD-1004 FLOD-1005 FLOD-1006 FSPF Messages FSPF-1001 FSPF-1002 FSPF-1003 FSPF-1005 FSPF-1006 FSPF-1007 FSPF-1008 FSPF-1009 FSPF-1010 FSPF-1011 FSPF-1012 FSS Messages FSS-1001 FSS-1002 FSS-1003 FSS-1004 FSS-1005 FSS-1006 FSS-1007 Fabric OS Message Reference 53-1002749-01...

  • Page 85: Fssm Messages

    FSSM Messages FSS-1008 FSS-1009 FSS-1010 FSS-1011 FSSM Messages FSSM-1002 FSSM-1003 FSSM-1004 FW Messages FW-1001 FW-1002 FW-1003 FW-1004 FW-1005 FW-1006 FW-1007 FW-1008 FW-1009 FW-1010 FW-1011 FW-1012 FW-1033 FW-1034 FW-1035 FW-1036 FW-1037 FW-1038 FW-1039 FW-1040 FW-1041 FW-1042 FW-1043 Fabric OS Message Reference 53-1002749-01...
  • Page 86 FW Messages FW-1044 FW-1045 FW-1046 FW-1047 FW-1048 FW-1049 FW-1050 FW-1051 FW-1052 FW-1053 FW-1054 FW-1113 FW-1114 FW-1115 FW-1116 FW-1117 FW-1118 FW-1119 FW-1120 FW-1121 FW-1122 FW-1123 FW-1124 FW-1125 FW-1126 FW-1127 FW-1128 FW-1129 FW-1130 FW-1131 FW-1132 FW-1133 FW-1134 FW-1135 FW-1136 Fabric OS Message Reference 53-1002749-01...
  • Page 87 FW Messages FW-1137 FW-1138 FW-1139 FW-1140 FW-1160 FW-1161 FW-1162 FW-1163 FW-1164 FW-1165 FW-1166 FW-1167 FW-1168 FW-1169 FW-1170 FW-1171 FW-1172 FW-1173 FW-1174 FW-1175 FW-1176 FW-1177 FW-1178 FW-1179 FW-1180 FW-1181 FW-1182 FW-1183 FW-1184 FW-1185 FW-1186 FW-1187 FW-1188 FW-1189 FW-1190 Fabric OS Message Reference 53-1002749-01...
  • Page 88 FW Messages FW-1191 FW-1192 FW-1193 FW-1194 FW-1195 FW-1196 FW-1197 FW-1198 FW-1199 FW-1200 FW-1201 FW-1202 FW-1203 FW-1204 FW-1205 FW-1206 FW-1207 FW-1216 FW-1217 FW-1218 FW-1219 FW-1240 FW-1241 FW-1242 FW-1243 FW-1244 FW-1245 FW-1246 FW-1247 FW-1248 FW-1249 FW-1250 FW-1251 FW-1272 FW-1273 Fabric OS Message Reference 53-1002749-01...
  • Page 89 FW Messages FW-1274 FW-1275 FW-1296 FW-1297 FW-1298 FW-1299 FW-1300 FW-1301 FW-1302 FW-1303 FW-1304 FW-1305 FW-1306 FW-1307 FW-1308 FW-1309 FW-1310 FW-1311 FW-1312 FW-1313 FW-1314 FW-1315 FW-1316 FW-1317 FW-1318 FW-1319 FW-1320 FW-1321 FW-1322 FW-1323 FW-1324 FW-1325 FW-1326 FW-1327 FW-1328 Fabric OS Message Reference 53-1002749-01...
  • Page 90 FW Messages FW-1329 FW-1330 FW-1331 FW-1332 FW-1333 FW-1334 FW-1335 FW-1336 FW-1337 FW-1338 FW-1339 FW-1340 FW-1341 FW-1342 FW-1343 FW-1344 FW-1345 FW-1346 FW-1347 FW-1348 FW-1349 FW-1350 FW-1351 FW-1352 FW-1353 FW-1354 FW-1355 FW-1356 FW-1357 FW-1358 FW-1359 FW-1360 FW-1361 FW-1362 FW-1363 Fabric OS Message Reference 53-1002749-01...
  • Page 91 FW Messages FW-1364 FW-1365 FW-1366 FW-1367 FW-1368 FW-1369 FW-1370 FW-1371 FW-1372 FW-1373 FW-1374 FW-1375 FW-1376 FW-1377 FW-1378 FW-1379 FW-1400 FW-1401 FW-1402 FW-1403 FW-1404 FW-1405 FW-1406 FW-1407 FW-1408 FW-1424 FW-1425 FW-1426 FW-1427 FW-1428 FW-1429 FW-1430 FW-1431 FW-1432 FW-1433 Fabric OS Message Reference 53-1002749-01...
  • Page 92 FW Messages FW-1434 FW-1435 FW-1436 FW-1437 FW-1438 FW-1439 FW-1440 FW-1441 FW-1442 FW-1443 FW-1444 FW-1445 FW-1446 FW-1447 FW-1448 FW-1500 FW-1501 FW-1502 FW-1510 FW-1511 FW-1512 FW-1513 FW-1514 FW-1515 FW-1516 FW-1517 FW-1518 FW-1519 FW-1520 FW-1521 FW-1522 FW-1523 FW-1524 FW-1525 FW-1526 Fabric OS Message Reference 53-1002749-01...

  • Page 93: Ham Messages

    HAM Messages FW-1527 FW-1528 FW-1529 FW-1530 FW-1531 FW-1532 FW-1533 FW-1534 FW-1535 FW-2000 FW-3010 FW-3011 FW-3012 FW-3013 FW-3014 FW-3015 FW-3016 FW-3017 FW-3018 FW-3019 FW-3020 FW-3021 FW-3022 HAM Messages HAM-1001 HAM-1002 HAM-1004 HAM-1005 HAM-1006 HAM-1007 HAM-1008 HAM-1009 HAM-1010 HAM-1011 Fabric OS Message Reference 53-1002749-01...

  • Page 94: Hamk Messages

    HAMK Messages HAM-1013 HAM-1014 HAMK Messages HAMK-1001 HAMK-1002 HAMK-1003 HAMK-1004 HIL Messages HIL-1101 HIL-1102 HIL-1103 HIL-1104 HIL-1105 HIL-1106 HIL-1107 HIL-1108 HIL-1201 HIL-1202 HIL-1203 HIL-1204 HIL-1206 HIL-1207 HIL-1208 HIL-1301 HIL-1302 HIL-1303 HIL-1304 HIL-1305 HIL-1306 HIL-1307 HIL-1308 HIL-1309 Fabric OS Message Reference 53-1002749-01...

  • Page 95: Hlo Messages

    HLO Messages HIL-1310 HIL-1311 HIL-1401 HIL-1402 HIL-1403 HIL-1404 HIL-1501 HIL-1502 HIL-1503 HIL-1504 HIL-1505 HIL-1506 HIL-1507 HIL-1508 HIL-1509 HIL-1510 HIL-1511 HIL-1601 HIL-1602 HIL-1603 HIL-1605 HIL-1610 HIL-1611 HIL-1612 HIL-1613 HIL-1650 HLO Messages HLO-1001 HLO-1002 HLO-1003 HMON Messages HMON-1001 Fabric OS Message Reference 53-1002749-01...

  • Page 96: Hsl Messages

    HSL Messages HSL Messages HSL-1000 HSL-1001 HSL-1002 HSL-1003 HSL-1004 HSL-1005 HSL-1006 HSL-1007 HTTP Messages HTTP-1001 HTTP-1002 HTTP-1003 IBD Messages IBD-1000 IPAD Messages IPAD-1000 IPAD-1001 IPAD-1002 IPAD-1003 IPAD-1004 IPS Messages IPS-1001 IPS-1002 IPS-1003 IPS-1004 IPS-1005 IPS-1006 IPS-1007 Fabric OS Message Reference 53-1002749-01...

  • Page 97: Isns Messages

    ISNS Messages ISNS Messages ISNS-1001 ISNS-1002 ISNS-1003 ISNS-1004 ISNS-1005 ISNS-1006 ISNS-1008 ISNS-1009 ISNS-1010 ISNS-1011 ISNS-1013 ISNS-1014 KAC Messages KAC-1002 KAC-1004 KAC-1006 KAC-1007 KAC-1008 KAC-1009 KAC-1010 KAC-1011 KAC-1012 KAC-1013 KAC-1014 KAC-1015 KAC-1016 KAC-1017 KSWD Messages KSWD-1001 KSWD-1002 Fabric OS Message Reference 53-1002749-01...

  • Page 98: Ktrc Messages

    KTRC Messages KTRC Messages KTRC-1001 KTRC-1002 KTRC-1003 KTRC-1004 KTRC-1005 L2SS Messages L2SS-1001 L2SS-1002 L2SS-1003 L2SS-1004 L2SS-1005 L2SS-1006 L2SS-1007 L2SS-1008 L3SS Messages L3SS-1004 LACP Messages LACP-1001 LACP-1002 LANCE Messages LANCE-1000 LFM Messages LFM-1001 LFM-1002 LFM-1003 LFM-1004 LFM-1005 Fabric OS Message Reference 53-1002749-01...

  • Page 99: Log Messages

    LOG Messages LFM-1006 LOG Messages LOG-1000 LOG-1001 LOG-1002 LOG-1003 LOG-1004 LOG-1005 LOG-1006 LOG-1007 LOG-1008 LOG-1009 LOG-1010 LOG-1011 LSDB Messages LSDB-1001 LSDB-1002 LSDB-1003 LSDB-1004 MCAST_SS Messages MCAST_SS-1001 MCAST_SS-1002 MCAST_SS-1003 MCAST_SS-1004 MCAST_SS-1005 MCAST_SS-1006 MCAST_SS-1007 MCAST_SS-1008 MCAST_SS-1009 MCAST_SS-1010 MCAST_SS-1011 Fabric OS Message Reference 53-1002749-01...

  • Page 100: Mfic Messages

    MFIC Messages MCAST_SS-1012 MCAST_SS-1013 MCAST_SS-1014 MCAST_SS-1015 MCAST_SS-1016 MCAST_SS-1017 MCAST_SS-1018 MCAST_SS-1019 MCAST_SS-1020 MFIC Messages MFIC-1001 MFIC-1002 MFIC-1003 MM Messages MM-1001 MPTH Messages MPTH-1001 MPTH-1002 MPTH-1003 MQ Messages MQ-1004 MQ-1005 MQ-1006 MS Messages MS-1001 MS-1002 MS-1003 MS-1004 MS-1005 Fabric OS Message Reference 53-1002749-01...

  • Page 101: Mstp Messages

    MSTP Messages MS-1006 MS-1008 MS-1009 MS-1021 MS-1022 MS-1023 MS-1024 MS-1025 MS-1026 MS-1027 MS-1028 MS-1029 MS-1030 MSTP Messages MSTP-1001 MSTP-1002 MSTP-1003 MSTP-2001 MSTP-2002 MSTP-2003 MSTP-2004 MSTP-2005 MSTP-2006 NBFS Messages NBFS-1001 NBFS-1002 NBFS-1003 NBFS-1004 NS Messages NS-1001 NS-1002 Fabric OS Message Reference 53-1002749-01...

  • Page 102: Nsm Messages

    NSM Messages NS-1003 NS-1004 NS-1005 NS-1006 NS-1007 NS-1008 NS-1009 NS-1010 NS-1011 NS-1012 NSM Messages NSM-1001 NSM-1002 NSM-1003 NSM-1004 NSM-1005 NSM-1006 NSM-1007 NSM-1008 NSM-1009 NSM-1010 NSM-1011 NSM-1012 NSM-1013 NSM-1014 NSM-1015 NSM-1016 NSM-1017 NSM-1018 NSM-1019 NSM-1020 Fabric OS Message Reference 53-1002749-01...

  • Page 103: Onmd Messages

    ONMD Messages ONMD Messages ONMD-1000 ONMD-1001 ONMD-1002 ONMD-1003 ONMD-1004 ONMD-1005 PDM Messages PDM-1001 PDM-1002 PDM-1003 PDM-1004 PDM-1005 PDM-1006 PDM-1007 PDM-1008 PDM-1009 PDM-1010 PDM-1011 PDM-1012 PDM-1013 PDM-1014 PDM-1017 PDM-1019 PDM-1020 PDM-1021 PDM-1022 PDM-1023 PDM-1024 PDM-1025 PDM-1026 Fabric OS Message Reference 53-1002749-01...

  • Page 104: Pdtr Messages

    PDTR Messages PDTR Messages PDTR-1001 PDTR-1002 PLAT Messages PLAT-1000 PLAT-1001 PLAT-1002 PLAT-1003 PLAT-1004 PLAT-1072 PMGR Messages PMGR-1001 PMGR-1002 PMGR-1003 PMGR-1004 PMGR-1005 PMGR-1006 PMGR-1007 PMGR-1008 PMGR-1009 PMGR-1010 PMGR-1011 PORT Messages PORT-1003 PORT-1004 PORT-1005 PORT-1006 PORT-1007 PORT-1008 PORT-1009 PORT-1010 Fabric OS Message Reference 53-1002749-01...

  • Page 105: Ps Messages

    PS Messages PS Messages PS-1000 PS-1001 PS-1002 PS-1003 PS-1004 PS-1005 PS-1006 PS-1007 PS-1008 PS-1009 PS-1010 PSWP Messages PSWP-1001 PSWP-1002 PSWP-1003 PSWP-1004 PSWP-1005 PSWP-1006 PSWP-1007 RAS Messages RAS-1001 RAS-1002 RAS-1004 RAS-1005 RAS-1006 RAS-1007 RAS-2001 RAS-2002 RAS-2003 RAS-3001 RAS-3002 Fabric OS Message Reference 53-1002749-01...

  • Page 106: Rcs Messages

    RCS Messages RAS-3003 RAS-3004 RCS Messages RCS-1001 RCS-1002 RCS-1003 RCS-1004 RCS-1005 RCS-1006 RCS-1007 RCS-1008 RCS-1009 RCS-1010 RCS-1011 RCS-1012 RCS-1013 RKD Messages RKD-1001 RKD-1002 RKD-1003 RKD-1004 RKD-1005 RMON Messages RMON-1001 RMON-1002 RPCD Messages RPCD-1001 RPCD-1002 RPCD-1003 RPCD-1004 Fabric OS Message Reference 53-1002749-01...

  • Page 107: Rte Messages

    RTE Messages RPCD-1005 RPCD-1006 RPCD-1007 RTE Messages RTE-1001 RTWR Messages RTWR-1001 RTWR-1002 RTWR-1003 SCN Messages SCN-1001 SCN-1002 SEC Messages SEC-1001 SEC-1002 SEC-1003 SEC-1005 SEC-1006 SEC-1007 SEC-1008 SEC-1009 SEC-1010 SEC-1016 SEC-1022 SEC-1024 SEC-1025 SEC-1026 SEC-1028 SEC-1029 SEC-1030 Fabric OS Message Reference 53-1002749-01...

  • Page 108: Sec Messages

    SEC Messages SEC-1031 SEC-1032 SEC-1033 SEC-1034 SEC-1035 SEC-1036 SEC-1037 SEC-1038 SEC-1039 SEC-1040 SEC-1041 SEC-1042 SEC-1043 SEC-1044 SEC-1045 SEC-1046 SEC-1049 SEC-1050 SEC-1051 SEC-1052 SEC-1053 SEC-1054 SEC-1055 SEC-1056 SEC-1057 SEC-1059 SEC-1062 SEC-1063 SEC-1064 SEC-1065 SEC-1069 SEC-1071 SEC-1072 SEC-1073 SEC-1074 Fabric OS Message Reference 53-1002749-01...
  • Page 109 SEC Messages SEC-1075 SEC-1076 SEC-1077 SEC-1078 SEC-1079 SEC-1080 SEC-1081 SEC-1082 SEC-1083 SEC-1084 SEC-1085 SEC-1086 SEC-1087 SEC-1088 SEC-1089 SEC-1090 SEC-1091 SEC-1092 SEC-1093 SEC-1094 SEC-1095 SEC-1096 SEC-1097 SEC-1098 SEC-1099 SEC-1100 SEC-1101 SEC-1102 SEC-1104 SEC-1105 SEC-1106 SEC-1107 SEC-1108 SEC-1110 SEC-1111 Fabric OS Message Reference 53-1002749-01...
  • Page 110 SEC Messages SEC-1112 SEC-1113 SEC-1114 SEC-1115 SEC-1116 SEC-1117 SEC-1118 SEC-1119 SEC-1121 SEC-1122 SEC-1123 SEC-1124 SEC-1126 SEC-1130 SEC-1135 SEC-1136 SEC-1137 SEC-1138 SEC-1139 SEC-1142 SEC-1145 SEC-1146 SEC-1153 SEC-1154 SEC-1155 SEC-1156 SEC-1157 SEC-1158 SEC-1159 SEC-1160 SEC-1163 SEC-1164 SEC-1165 SEC-1166 SEC-1167 Fabric OS Message Reference 53-1002749-01...
  • Page 111 SEC Messages SEC-1168 SEC-1170 SEC-1171 SEC-1172 SEC-1173 SEC-1174 SEC-1175 SEC-1176 SEC-1180 SEC-1181 SEC-1182 SEC-1183 SEC-1184 SEC-1185 SEC-1186 SEC-1187 SEC-1188 SEC-1189 SEC-1190 SEC-1191 SEC-1192 SEC-1193 SEC-1194 SEC-1195 SEC-1196 SEC-1197 SEC-1198 SEC-1199 SEC-1200 SEC-1201 SEC-1202 SEC-1203 SEC-1250 SEC-1251 SEC-1253 Fabric OS Message Reference 53-1002749-01...
  • Page 112 SEC Messages SEC-1300 SEC-1301 SEC-1302 SEC-1303 SEC-1304 SEC-1305 SEC-1306 SEC-1307 SEC-1308 SEC-1309 SEC-1310 SEC-1311 SEC-1312 SEC-1313 SEC-1314 SEC-1315 SEC-1316 SEC-1317 SEC-1318 SEC-1319 SEC-1320 SEC-1321 SEC-1322 SEC-1323 SEC-1324 SEC-1325 SEC-1326 SEC-1327 SEC-1328 SEC-1329 SEC-1330 SEC-1331 SEC-1332 SEC-1333 SEC-1334 Fabric OS Message Reference 53-1002749-01...

  • Page 113: Sflo Messages

    SFLO Messages SEC-1335 SEC-1336 SEC-1337 SEC-1338 SEC-1339 SEC-3035 SEC-3036 SEC-3037 SEC-3038 SEC-3039 SEC-3050 SEC-3051 SEC-3061 SEC-3062 SEC-3063 SEC-3064 SEC-3065 SEC-3066 SEC-3067 SEC-4001 SFLO Messages SFLO-1001 SFLO-1002 SFLO-1003 SFLO-1004 SFLO-1005 SFLO-1006 SFLO-1007 SFLO-1008 SNMP Messages SNMP-1001 SNMP-1002 Fabric OS Message Reference 53-1002749-01...

  • Page 114: Spc Messages

    SPC Messages SNMP-1003 SNMP-1004 SNMP-1005 SNMP-1006 SNMP-1009 SPC Messages SPC-1001 SPC-1002 SPC-1003 SPC-2001 SPC-2002 SPC-2003 SPC-2004 SPC-2005 SPC-2006 SPC-2007 SPC-2008 SPC-2009 SPC-2010 SPC-2011 SPC-2012 SPC-2013 SPC-2014 SPC-2040 SPC-2041 SPC-2042 SPC-2043 SPC-2044 SPC-3001 SPC-3002 SPC-3003 SPC-3004 SPC-3005 SPC-3006 Fabric OS Message Reference 53-1002749-01...

  • Page 115: Spm Messages

    SPM Messages SPC-3007 SPC-3008 SPC-3009 SPC-3010 SPC-3011 SPC-3012 SPC-3013 SPC-3014 SPC-3015 SPM Messages SPM-1001 SPM-1002 SPM-1003 SPM-1004 SPM-1005 SPM-1006 SPM-1007 SPM-1008 SPM-1009 SPM-1010 SPM-1011 SPM-1012 SPM-1013 SPM-1014 SPM-1015 SPM-1016 SPM-3001 SPM-3002 SPM-3003 SPM-3004 SPM-3005 SPM-3006 SPM-3007 SPM-3008 Fabric OS Message Reference 53-1002749-01...

  • Page 116: Ss Messages

    SS Messages SPM-3009 SPM-3010 SPM-3011 SPM-3012 SPM-3013 SPM-3014 SPM-3015 SPM-3016 SPM-3017 SPM-3018 SPM-3019 SPM-3020 SPM-3021 SPM-3022 SPM-3023 SPM-3024 SPM-3025 SPM-3026 SPM-3027 SPM-3028 SPM-3029 SS Messages SS-1000 SS-1001 SS-1002 SS-1003 SS-1004 SS-1005 SS-1006 SS-1007 SS-1008 SS-1009 SS-1010 SS-1011 Fabric OS Message Reference 53-1002749-01...

  • Page 117: Ssmd Messages

    SSMD Messages SS-1012 SSMD Messages SSMD-1001 SSMD-1002 SSMD-1003 SSMD-1004 SSMD-1005 SSMD-1006 SSMD-1007 SSMD-1008 SSMD-1200 SSMD-1201 SSMD-1202 SSMD-1203 SSMD-1204 SSMD-1205 SSMD-1206 SSMD-1207 SSMD-1208 SSMD-1209 SSMD-1210 SSMD-1211 SSMD-1212 SSMD-1213 SSMD-1214 SSMD-1215 SSMD-1216 SSMD-1217 SSMD-1300 SSMD-1301 SSMD-1302 SSMD-1303 SSMD-1304 SSMD-1305 Fabric OS Message Reference 53-1002749-01...

  • Page 118: Sulb Messages

    SULB Messages SSMD-1306 SSMD-1307 SSMD-1308 SSMD-1309 SSMD-1310 SSMD-1311 SSMD-1312 SSMD-1313 SSMD-1314 SSMD-1315 SSMD-1316 SSMD-1317 SSMD-1318 SULB Messages SULB-1001 SULB-1002 SULB-1003 SULB-1004 SULB-1005 SULB-1006 SULB-1007 SULB-1008 SULB-1009 SULB-1010 SULB-1011 SULB-1017 SULB-1018 SULB-1020 SULB-1021 SULB-1022 SULB-1023 SULB-1024 SULB-1025 SULB-1026 Fabric OS Message Reference 53-1002749-01...

  • Page 119: Swch Messages

    SWCH Messages SULB-1030 SULB-1031 SULB-1032 SULB-1033 SULB-1034 SULB-1035 SULB-1036 SULB-1037 SULB-1038 SULB-1039 SULB-1040 SULB-1041 SULB-1042 SULB-1043 SULB-1044 SWCH Messages SWCH-1001 SWCH-1002 SWCH-1003 SWCH-1004 SWCH-1005 SWCH-1006 SWCH-1007 SWCH-1008 SWCH-1009 SWCH-1010 SWCH-1011 SWCH-1012 SWCH-1013 SWCH-1014 SWCH-1015 SWCH-1016 SWCH-1017 SWCH-1018 Fabric OS Message Reference 53-1002749-01...

  • Page 120: Sysc Messages

    SYSC Messages SWCH-1019 SWCH-1020 SWCH-1021 SWCH-1022 SWCH-1023 SWCH-1024 SWCH-1025 SWCH-1026 SYSC Messages SYSC-1001 SYSC-1002 SYSC-1004 SYSC-1005 SYSM Messages SYSM-1001 SYSM-1002 SYSM-1003 SYSM-1004 SYSM-1005 SYSM-1006 SYSM-1007 TAPE Messages TAPE-1001 TRCE Messages TRCE-1001 TRCE-1002 TRCE-1003 TRCE-1004 TRCE-1005 TRCE-1006 Fabric OS Message Reference 53-1002749-01...

  • Page 121: Trck Messages

    TRCK Messages TRCE-1007 TRCE-1008 TRCE-1009 TRCE-1010 TRCE-1011 TRCE-1012 TRCE-1013 TRCK Messages TRCK-1001 TRCK-1002 TRCK-1003 TRCK-1004 TRCK-1005 TRCK-1006 TS Messages TS-1001 TS-1002 TS-1006 TS-1007 TS-1008 UCST Messages UCST-1003 UCST-1007 UCST-1020 UCST-1021 UCST-1022 UCST-1023 UCST-1024 UCST-1026 UCST-1027 Fabric OS Message Reference 53-1002749-01...

  • Page 122: Upth Messages

    UPTH Messages UPTH Messages UPTH-1001 UPTH-1002 VDR Messages VDR-2001 VS Messages VS-1001 VS-1002 VS-1003 VS-1004 VS-1005 VS-1006 VS-1007 VS-1008 WEBD Messages WEBD-1001 WEBD-1002 WEBD-1004 WEBD-1005 WEBD-1006 WEBD-1007 WEBD-1008 XTUN Messages XTUN-1000 XTUN-1001 XTUN-1002 XTUN-1003 XTUN-1004 XTUN-1005 Fabric OS Message Reference 53-1002749-01...

  • Page 123: Zeus Messages

    ZEUS Messages XTUN-1006 XTUN-1007 XTUN-1996 XTUN-1997 XTUN-1998 XTUN-1999 XTUN-2000 XTUN-2001 XTUN-2002 XTUN-2003 XTUN-2004 XTUN-2005 XTUN-2006 XTUN-2007 XTUN-2008 XTUN-2009 XTUN-2010 XTUN-2011 XTUN-2020 XTUN-2021 XTUN-2022 XTUN-2023 XTUN-2024 XTUN-2025 ZEUS Messages ZEUS-1001 ZEUS-1002 ZEUS-1003 ZEUS-1004 ZEUS-1005 ZEUS-1015 ZEUS-1016 ZEUS-1028 Fabric OS Message Reference 53-1002749-01...

  • Page 124: Zone Messages

    ZONE Messages ZONE Messages ZONE-1002 ZONE-1003 ZONE-1004 ZONE-1007 ZONE-1010 ZONE-1013 ZONE-1015 ZONE-1017 ZONE-1019 ZONE-1022 ZONE-1023 ZONE-1024 ZONE-1026 ZONE-1027 ZONE-1028 ZONE-1029 ZONE-1034 ZONE-1036 ZONE-1037 ZONE-1038 ZONE-1039 ZONE-1040 ZONE-1041 ZONE-1042 ZONE-1043 ZONE-1044 ZONE-1045 ZONE-1046 ZONE-1048 ZONE-1049 ZONE-1054 ZONE-1057 ZONE-1058 Fabric OS Message Reference 53-1002749-01...
  • Page 125 ZONE Messages ZONE-1059 ZONE-1060 ZONE-1061 ZONE-1062 Fabric OS Message Reference 53-1002749-01...
  • Page 126 ZONE Messages Fabric OS Message Reference 53-1002749-01...
  • Page 127 Chapter Audit Messages AG Messages AG-1033 AG-1034 AG-1035 AG-1036 AG-1037 AN Messages AN-1003 AN-1004 AN-1005 AN-1006 AN-1010 AN-1011 AN-1012 AN-1013 AUTH Messages AUTH-1045 AUTH-1046 AUTH-1047 AUTH-3001 AUTH-3002 AUTH-3003 AUTH-3004 AUTH-3005 AUTH-3006 AUTH-3007 AUTH-3008 Fabric OS Message Reference 53-1002749-01...
  • Page 128 BLS Messages BLS Messages BLS-1002 BLS-1003 CCFG Messages CCFG-1002 CCFG-1003 CCFG-1013 CNM Messages CNM-3001 CNM-3002 CNM-3003 CNM-3004 CNM-3005 CNM-3006 CNM-3007 CNM-3008 CNM-3009 CNM-3010 CNM-3011 CNM-3012 CONF Messages CONF-1000 CONF-1020 CONF-1022 CONF-1042 CONF-1043 CONF-1044 CVLM Messages CVLM-3001 Fabric OS Message Reference 53-1002749-01...
  • Page 129 ESS Messages CVLM-3002 CVLM-3003 CVLM-3004 CVLM-3005 CVLM-3006 CVLM-3007 CVLM-3008 CVLM-3009 CVLM-3010 CVLM-3011 CVLM-3012 CVLM-3013 CVLM-3014 CVLM-3015 CVLM-3016 CVLM-3017 CVLM-3018 CVLM-3019 CVLM-3020 CVLM-3021 CVLM-3022 CVLM-3023 CVLM-3024 CVLM-3025 CVLM-3026 CVLM-3027 CVLM-3028 ESS Messages ESS-1008 ESS-1009 ESS-1010 Fabric OS Message Reference 53-1002749-01...
  • Page 130 FICU Messages FICU Messages FICU-1011 FICU-1012 FICU-1019 FICU-1020 FICU-1021 FW Messages FW-1202 FW-1274 FW-1402 FW-1404 FW-1405 FW-1406 FW-3001 HAM Messages HAM-1015 HTTP Messages HTTP-1002 HTTP-1003 IPAD Messages IPAD-1002 LOG Messages LOG-1005 LOG-1006 LOG-1007 LOG-1008 LOG-1011 Fabric OS Message Reference 53-1002749-01...
  • Page 131 MS Messages MS Messages MS-1027 MS-1028 MS-1029 MS-1030 PMGR Messages PMGR-1001 PMGR-1003 PORT Messages PORT-1006 PORT-1007 PORT-1008 PORT-1009 RAS Messages RAS-2001 RAS-2002 RAS-2003 RAS-3005 SEC Messages SEC-1113 SEC-1114 SEC-1337 SEC-3001 SEC-3002 SEC-3003 SEC-3004 SEC-3005 SEC-3006 SEC-3007 Fabric OS Message Reference 53-1002749-01...
  • Page 132 SEC Messages SEC-3008 SEC-3009 SEC-3010 SEC-3011 SEC-3012 SEC-3013 SEC-3014 SEC-3015 SEC-3016 SEC-3017 SEC-3018 SEC-3019 SEC-3020 SEC-3021 SEC-3022 SEC-3023 SEC-3024 SEC-3025 SEC-3026 SEC-3027 SEC-3028 SEC-3029 SEC-3030 SEC-3031 SEC-3032 SEC-3033 SEC-3034 SEC-3035 SEC-3036 SEC-3037 SEC-3038 SEC-3039 SEC-3044 SEC-3045 SEC-3046 Fabric OS Message Reference 53-1002749-01...
  • Page 133 SNMP Messages SEC-3047 SEC-3048 SEC-3049 SEC-3050 SEC-3051 SEC-3061 SEC-3062 SEC-3063 SEC-3064 SEC-3065 SEC-3066 SEC-3067 SEC-4001 SNMP Messages SNMP-1004 SNMP-1005 SNMP-1006 SNMP-1009 SPM Messages SPM-3001 SPM-3002 SPM-3003 SPM-3004 SPM-3005 SPM-3006 SPM-3007 SPM-3008 SPM-3009 SPM-3010 SPM-3011 SPM-3012 SPM-3013 Fabric OS Message Reference 53-1002749-01...
  • Page 134 SULB Messages SPM-3014 SPM-3015 SPM-3016 SPM-3017 SPM-3018 SPM-3019 SPM-3020 SPM-3021 SPM-3022 SPM-3023 SPM-3024 SPM-3025 SPM-3026 SPM-3027 SPM-3028 SPM-3029 SULB Messages SULB-1001 SULB-1002 SULB-1003 SULB-1004 SULB-1009 SULB-1010 SULB-1017 SULB-1018 SULB-1020 SULB-1021 SULB-1023 SULB-1024 SULB-1026 SULB-1030 SULB-1031 SULB-1032 SULB-1033 Fabric OS Message Reference 53-1002749-01...
  • Page 135 SWCH Messages SULB-1034 SULB-1035 SULB-1037 SULB-1038 SULB-1039 SULB-1040 SULB-1041 SULB-1042 SWCH Messages SWCH-1012 SWCH-1013 SWCH-1014 UCST Messages UCST-1021 UCST-1022 UCST-1023 UCST-1024 UCST-1026 UCST-1027 ZONE Messages ZONE-3001 ZONE-3002 ZONE-3003 ZONE-3004 ZONE-3005 ZONE-3006 ZONE-3007 ZONE-3008 ZONE-3009 ZONE-3010 ZONE-3011 Fabric OS Message Reference 53-1002749-01...
  • Page 136 ZONE Messages ZONE-3012 ZONE-3013 ZONE-3014 ZONE-3015 ZONE-3016 ZONE-3017 ZONE-3018 ZONE-3019 ZONE-3020 ZONE-3021 ZONE-3022 ZONE-3023 ZONE-3024 ZONE-3025 ZONE-3026 Fabric OS Message Reference 53-1002749-01...
  • Page 137 Chapter FFDC Messages ANV Messages ANV-1002 AUTH Messages AUTH-1014 AUTH-1044 BKSW Messages BKSW-1003 BL Messages BL-1002 BL-1003 BL-1004 BL-1008 BL-1009 BL-1011 BL-1016 BL-1020 BLS Messages BLS-1000 BLS-1001 BM Messages BM-1003 BM-1053 Fabric OS Message Reference 53-1002749-01...
  • Page 138 C2 Messages C2 Messages C2-1002 C2-1012 C3 Messages C3-1002 C3-1012 CDR Messages CDR-1002 CHS Messages CHS-1002 EM Messages EM-1001 EM-1002 EM-1003 EM-1004 EM-1005 EM-1006 EM-1008 EM-1009 EM-1010 EM-1011 EM-1012 EM-1018 EM-1020 EM-1028 EM-1068 EM-1071 EM-1072 Fabric OS Message Reference 53-1002749-01...
  • Page 139 FABR Messages FABR Messages FABR-1011 FABR-1013 FABR-1019 FABR-1020 FABR-1021 FABR-1022 FABR-1031 FABR-1054 FABS Messages FABS-1001 FCMC Messages FCMC-1001 FCPH Messages FCPH-1001 FLOD Messages FLOD-1004 HAM Messages HAM-1001 HAM-1006 HAM-1007 HAM-1008 HAM-1009 HAM-1011 HAMK Messages HAMK-1001 Fabric OS Message Reference 53-1002749-01...
  • Page 140 HIL Messages HIL Messages HIL-1107 HIL-1108 HIL-1502 HIL-1503 HIL-1506 HIL-1507 HIL-1508 HIL-1509 HIL-1602 HIL-1603 HIL-1611 HLO Messages HLO-1001 HLO-1002 HMON Messages HMON-1001 KSWD Messages KSWD-1001 KSWD-1002 LFM Messages LFM-1004 LOG Messages LOG-1001 LOG-1002 LSDB Messages LSDB-1003 Fabric OS Message Reference 53-1002749-01...
  • Page 141 MPTH Messages MPTH Messages MPTH-1001 MPTH-1002 NBFS Messages NBFS-1002 PDM Messages PDM-1017 PLAT Messages PLAT-1000 PLAT-1003 PLAT-1004 PLAT-1072 PS Messages PS-1000 RAS Messages RAS-1004 RAS-1005 RCS Messages RCS-1012 RCS-1013 SCN Messages SCN-1001 SCN-1002 Fabric OS Message Reference 53-1002749-01...
  • Page 142 SNMP Messages SNMP Messages SNMP-1004 SYSC Messages SYSC-1001 SYSC-1002 SYSM Messages SYSM-1001 SYSM-1005 SYSM-1006 TRCE Messages TRCE-1008 UCST Messages UCST-1007 WEBD Messages WEBD-1008 ZEUS Messages ZEUS-1002 Fabric OS Message Reference 53-1002749-01...
  • Page 143 Chapter Fabric OS System Messages AG Messages AG-1001 Message N_Port ID virtualization (NPIV) is not supported by fabric port connected to port <port number>. Message Type Severity ERROR Probable Cause Indicates that the N_Port ID virtualization (NPIV) capability is not supported by the fabric port to which the Access Gateway is connected.
  • Page 144 AG-1003 AG-1003 Message Unable to failover N_Port <port number>. Failover across different fabric is not supported. Message Type Severity WARNING Probable Cause Indicates that the failover does not get blocked between two fabrics, although it is not a supported configuration. Recommended Configure two or more N_Ports to connect to the same fabric;...
  • Page 145 AG-1006 AG-1006 Message Access Gateway mode has been <message>. Message Type Severity INFO Probable Cause Indicates that the Access Gateway mode has been enabled or disabled. Recommended Execute the ag --modeshow command to verify the current status of the Access Gateway mode. Action AG-1007 Message...
  • Page 146 AG-1009 AG-1009 Message Sending FLOGI failed on N_Port <port number>. Message Type Severity WARNING Probable Cause Indicates that there was a failure sending a Fabric Login (FLOGI) request from the Access Gateway to the fabric switch. Recommended Check the configuration of the fabric switch connected to the Access Gateway. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 147 AG-1012 AG-1012 Message Sending logout (LOGO) request failed on N_Port <port number>. Message Type Severity WARNING Probable Cause Indicates that there was a failure sending an N_Port logout request from the Access Gateway to the fabric switch. Recommended Check the configuration of the fabric switch connected to the Access Gateway. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 148 AG-1015 AG-1015 Message Unable to find online N_Ports to connect to the fabric. Message Type Severity WARNING Probable Cause Indicates that no other N_Port is configured or all N_Ports are currently offline. Recommended Check whether any other N_Port is configured using the portCfgShow command. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 149 AG-1018 AG-1018 Message Host port should not be connected to port <port number> which is configured as N_Port. Message Type Severity ERROR Probable Cause Indicates that an initiator or target port is erroneously connected to a port configured for N_Port operation.
  • Page 150 AG-1021 AG-1021 Message Unable to do Preferred-Failover of F_Port <port number>. Failover across different fabric is not supported. Message Type Severity WARNING Probable Cause Indicates that failover across N_Ports connected to different fabrics is not supported. Recommended Change the preferred N_Port settings of the specified F_Port using the ag --prefset command. Action Choose the preferred N_Port so that it is in the same fabric as the primary N_Port of this F_Port.
  • Page 151 AG-1024 AG-1024 Message F_Port <f_port> is failed back to its preferred N_Port <n_port>. Message Type Severity INFO Probable Cause Indicates that the specified N_Port is failing back F_Ports, which are failed over to some other N_Port. Recommended Execute the ag --mapshow command to display the updated F_Port-to-N_Port mapping. Action AG-1025 Message...
  • Page 152 AG-1027 AG-1027 Message Unable to handle this login request on port <port number> because NPIV capability is not enabled on this port. Message Type Severity WARNING Probable Cause Indicates that N_Port ID virtualization (NPIV) is not enabled on the specified port. Recommended Execute the portCfgNpivPort command on the Access Gateway switch to enable the NPIV capability on Action...
  • Page 153 AG-1030 AG-1030 Message N_Port (ID: <port number>) has been determined to be unreliable. Message Type Severity WARNING Probable Cause Indicates that the port goes online and offline often and therefore the port is marked as unreliable. Recommended No action is required. The port will automatically be marked as reliable after a certain interval of time, if Action the port toggling remains within the threshold limit.
  • Page 154 AG-1033 AG-1033 Message F_Port to N_Port mapping has been updated for N_Port (<n_port>). Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that the F_Ports mapped to an N_Port have changed and the configuration file has been updated. Recommended No action is required.
  • Page 155 AG-1036 AG-1036 Message Port <port number> is connected to a non-Brocade fabric with Persistent ALPA enabled. Check the admin guide for supported configuration. Message Type AUDIT | LOG Class Severity WARNING Probable Cause Indicates that one of the ports is connected to a non-Brocade fabric. Recommended Refer to the Access Gateway Administrator's Guide for the supported configuration.
  • Page 156 AG-1039 AG-1039 Message F_Port <Port that was reset> was reset because a WWN mapped device using it, through N_Port <Port who's state change caused the reset>, went offline. Message Type Severity INFO Probable Cause Indicates that the specified F_Port was reset because an N_Port went offline and the changes need to be propagated to all involved devices.
  • Page 157 AG-1042 AG-1042 Message Sending ELS_PORT_OPEN failed on N_Port <port number>. Message Type Severity WARNING Probable Cause Indicates there was a failure sending an ELS_PORT_OPEN request from the Access Gateway to the fabric switch. Recommended Check the configuration of the fabric switch connected to the Access Gateway. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 158 AN-1001 AN Messages AN-1001 Message Failed to allocate memory: (<function name>). Message Type Severity ERROR Probable Cause Indicates that the specified function has failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Restart or power cycle the switch. Action AN-1002 Message...
  • Page 159 AN-1004 Recommended If the port is an F_Port, examine the connected device for the source of the latency. If the port is a Action long-distance E_Port, make sure that there are enough buffer credits to service the link distance. AN-1004 Message Congestion bottleneck on port <slot number>/<port number within slot number>.
  • Page 160 AN-1010 AN-1010 Message Severe latency bottleneck detected at slot <slot number> port <port number within slot number>. Message Type LOG | AUDIT Class FABRIC Severity WARNING Probable Cause Indicates credit loss at the specified port, a downstream port, or a very high latency device at the edge of the fabric.
  • Page 161 AN-1013 AN-1013 Message Performed link reset to recover the port credits on slot <slot number> port <port number within slot number>. Message Type LOG | AUDIT Class FABRIC Severity INFO Probable Cause Indicates a credit loss. Recommended The port is recovered. No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 162 ANV-1001 ANV Messages ANV-1001 Message Port <port number> port fault. Change the SFP or check the cable. Message Type Severity ERROR Probable Cause Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver pair, or a faulty cable between the peer ports. Recommended Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not Action...
  • Page 163 ANV-1004 ANV-1004 Message S<slot number>,C<chip index>: Invalid DMA ch pointer, chan:<Channel number>, good_addr:0x<Good address> bad_addr:0x<Bad address>. Message Type Severity ERROR Probable Cause Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade the data traffic. Recommended Restart the system at the next maintenance window.
  • Page 164 ANV-1007 ANV-1007 Message S<slot number>,C<chip index>: ANVIL PASS 1 low buff pool fault: <chip regval field> 0x<chip error type>. Message Type Severity CRITICAL Probable Cause Indicates that Anvil Pass 1 is running out of free buffers, which may cause chip fault. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 165 ANV-1016 ANV-1016 Message Port is faulted due to port reinitialization failure on internal port S<slot number>,P<port number>(<blade port number>) with reason <port fault reason>. Message Type Severity WARNING Probable Cause Indicates that the specified port is faulted due to port re-initialization failure. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 166 AUTH-1001 AUTH Messages AUTH-1001 Message <Operation type> has been successfully completed. Message Type Severity INFO 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 167 AUTH-1004 AUTH-1004 Message Failed to set <data type> type to <setting value>. Message Type Severity ERROR Probable Cause Indicates that the authUtil command has failed to set the authentication configuration value. The data type can be authentication type, DH group type, hash type, or policy type. Recommended Execute the authUtil command again.
  • Page 168 AUTH-1007 AUTH-1007 Message The proposed authentication protocol(s) are not supported: port <port number>. Message Type Severity ERROR Probable Cause Indicates that the proposed authentication protocol types are not supported by the specified local port. Recommended Execute the authUtil command to make sure the local switch supports the Fibre Channel Authentication Action Protocol (FCAP) or Diffie Hellman - Channel Authentication Protocol (DH-CHAP) protocols.
  • Page 169 AUTH-1011 AUTH-1011 Message Failed to register for failover operation: switch <switch number> error <error code>. Message Type Severity WARNING Probable Cause Indicates an internal problem with the Secure Fabric OS. Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands.
  • Page 170 AUTH-1014 AUTH-1014 Message Invalid port value to <operation>: port <port number>. Message Type LOG | FFDC Severity ERROR Probable Cause Indicates an internal problem with the Secure Fabric OS. Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands.
  • Page 171 AUTH-1018 AUTH-1018 Message Invalid value to check protocol type: port <port number>. Message Type Severity ERROR Probable Cause Indicates an internal problem with the Secure Fabric OS. Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands.
  • Page 172 AUTH-1023 AUTH-1023 Message Failed to <operation type> during <authentication phase>: port <port number>. Message Type Severity ERROR Probable Cause Indicates an authentication operation failed for a certain authentication phase. The Operation type varies depending on authentication type: • Some operations for Switch Link Authentication Protocol (SLAP): certificate retrieve, certificate verification, signature verification, or nonce signing.
  • Page 173 AUTH-1026 AUTH-1026 Message Failed to <Device information> during negotiation phase: port <port number>. Message Type Severity WARNING Probable Cause Indicates that the authentication failed to get device or Host Bus Adapter (HBA) information due to an internal failure. Usually this problem is transient. If the authentication failed, retry the login. Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action...
  • Page 174 AUTH-1029 Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. AUTH-1029 Message Failed to get <data type>...
  • Page 175 AUTH-1032 Recommended Reset the secret value using the secAuthSecret command. Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 176 AUTH-1035 Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. AUTH-1035 Message Invalid <data type>...
  • Page 177 AUTH-1037 AUTH-1037 Message Failed to <operation type> response for <authentication message>: init_len <data length>, resp_len <data length>, port <port number>. Message Type Severity ERROR Probable Cause Indicates that a Diffie Hellman - Challenge Handshake Authentication Protocol (DH-CHAP) authentication operation failed on the specified port due to mismatched response values between two entities.
  • Page 178 AUTH-1040 Recommended Correct the switch policy configuration on either of the switches using the authUtil command, and then Action enable the port using the portEnable command. AUTH-1040 Message Reject authentication on port <Port Number>, because switch authentication policy is set to OFF. Message Type Severity INFO...
  • Page 179 AUTH-1043 Recommended Check the connection port for a possible security attack. Action Check the shared secrets using the secAuthSecret command and reinitialize authentication using the portDisable and portEnable commands. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 180 AUTH-1046 Recommended Check the certificate availability using the secCertUtil show -fcapall command. Action Install the certificate and reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 181 AUTH-3001 AUTH-3001 Message Event: <Event Name>, Status: success, Info: <Data type> type has been changed from [<Old value>] to [<New value>]. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates that an authentication configuration value was set to a specified value. The Data type can be authentication type, DH group type, hash type, or policy type.
  • Page 182 AUTH-3004 AUTH-3004 Message Event: <Event Name>, Status: failed, Info: Neighboring switch has a conflicting authentication policy; Port <Port Number> disabled. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates that 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 183 AUTH-3007 Recommended Check the connection port for a possible security attack. Action Check the shared secrets using the secAuthSecret command and reinitialize authentication using the portDisable and portEnable commands. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 184 BKSW-1003 BKSW Messages BKSW-1003 Message kSWD: <Warning message>. Message Type FFDC | LOG Severity WARNING 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 regarding the state of the system.
  • Page 185 BL-1000 BL Messages BL-1000 Message Initializing ports... Message Type Severity INFO Probable Cause Indicates that the switch has started initializing the ports. Recommended No action is required. Action BL-1001 Message Port initialization completed. Message Type Severity INFO Probable Cause Indicates that the switch has completed initializing the ports. Recommended No action is required.
  • Page 186 BL-1003 BL-1003 Message Faulting blade in slot <slot number>. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates a faulty blade in the specified slot. Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled;...
  • Page 187 BL-1007 BL-1007 Message blade #<blade number>: blade state is inconsistent with EM. bl_cflags 0x<blade control flags>, slot_on <slot_on flag>, slot_off <slot_off flag>, faulty <faulty flag>, status <blade status>. Message Type Severity WARNING Probable Cause Indicates that a failover occurred while a blade was initializing on the previously active control processor (CP).
  • Page 188 BL-1010 Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware problems.
  • Page 189 BL-1012 BL-1012 Message bport <port number> port int. is disabled. status=0x<interrupt status> Port <port number> will be re-enabled in 1 minute. Message Type Severity ERROR Probable Cause Indicates that the port generated an excessive number of interrupts that may prove unrecoverable to the switch operation.
  • Page 190 BL-1014 BL-1014 Message bport <port number> port int. is disabled. status=0x<interrupt status>. Message Type Severity ERROR Probable Cause Indicates that the port generated an excessive number of interrupts that may prove fatal to the switch operation. The port is disabled to prevent the control processor (CP) from becoming too busy. The bport number displayed in the message is the blade port;...
  • Page 191 BL-1016 BL-1016 Message Blade port <port number> in slot <slot number> failed to enable. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the specified blade port could not be enabled. Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled;...
  • Page 192 BL-1019 BL-1019 Message Slot <Slot number>, retry <Retry Number>, internal port retry initialization, <List of internal ports retrying initialization>. Message Type Severity INFO Probable Cause Indicates that the slot had internal ports that are not online. Initiated a retry on ports that failed to go online.
  • Page 193 BL-1022 BL-1022 Message Init Failed: Switch DISABLED because internal ports were not ONLINE, <list of internal port number not ONLINE>. Message Type Severity CRITICAL Probable Cause Indicates that the switch initiation failed because one or more of the internal ports was not online. The switch is faulted.
  • Page 194 BL-1025 BL-1025 Message All GigE/FCIP/Virtualization/FC Fastwrite ports on the blade in slot <slot number> will be reset as part of the firmware upgrade. Message Type Severity INFO Probable Cause Indicates that a recent firmware upgrade caused the blade's firmware to be upgraded and resulted in the cold upgrade.
  • Page 195 BL-1028 BL-1028 Message Switch faulted; internal processor was reset before switch init completed. Message Type Severity CRITICAL Probable Cause Indicates that the switch internal processor was reset before the initialization completed. Recommended Reboot or power cycle the switch using the slotPowerOff and slotPowerOn commands. Action If the message persists, replace the switch.
  • Page 196 BL-1031 BL-1031 Message Link timeout in internal port (slot <slot number>, port <port number>) resulted in blade fault. Use slotpoweroff/slotpoweron to recover the blade. Message Type Severity CRITICAL Probable Cause Indicates that link timeout occurred in one of the back-end internal ports. Recommended Power cycle the blade using the slotPowerOff and slotPowerOn commands.
  • Page 197 BL-1034 BL-1034 Message Slot <slot number> FC Initialization completed. Message Type Severity INFO Probable Cause Indicates that the slot has completed initializing the Fibre Channel (FC) ports. Recommended No action is required. Action BL-1035 Message Slot <slot number> iSCSI port <iscsi port number> Initialization completed. Message Type Severity INFO...
  • Page 198 BL-1037 BL-1037 Message Faulting chip in slot = <slot number>, miniS = <miniS number>,port = <port number> due to BE/BI port fault. Message Type Severity CRITICAL Probable Cause Indicates that all ports on the chip have been disabled due to a fault on the chip. Recommended Make sure that the blade is seated correctly.
  • Page 199 BL-1041 BL-1041 Message Dynamic area mode is enabled on default switch, Faulting the blade w/ ID <Blade ID of blade that has the mini SFP+ that does not support it> in slot <slot number> as it does not support this mode. Message Type Severity CRITICAL...
  • Page 200 BL-1047 BL-1047 Message Buffer optimized mode is turned <buffer optimized mode> for slot <slot number>. Message Type Severity INFO Probable Cause Indicates that the buffer optimized mode is changed for the specified slot. Recommended No action is required. Action BL-1048 Message FCoE Blade in slot <Slot>...
  • Page 201 BL-1050 BL-1050 Message Incompatible Blade Processor FPGA version with FOS7.0 firmware in slot=<slot number> on FX8-24. Contact support for upgrade instructions. Message Type Severity WARNING Probable Cause Indicates that the blade processor field-programmable gate array (FPGA) version with Fabric OS v7.0.0 is incompatible on the FX8-24 blade.
  • Page 202 BLS-1000 BLS Messages BLS-1000 Message <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>. Message Type LOG | FFDC Severity ERROR Probable Cause Indicates that the hardware is not responding to a command request, possibly because it is busy. Recommended Retry the command.
  • Page 203 BLS-1003 BLS-1003 Message An IPsec/IKE policy was deleted. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that an Internet Protocol Security (IPsec) or Internet Key Exchange (IKE) policy was deleted and the configuration file was updated. Recommended No action is required.
  • Page 204 BM-1001 BM Messages BM-1001 Message BM protocol version <Protocol version> in slot <Slot number>. Message Type Severity ERROR Probable Cause Indicates that the firmware running on the control processor (CP) cannot communicate with the application processor (AP) blade in the indicated slot and determine the AP blade's firmware version. The reason can be one of the following: •...
  • Page 205 BM-1004 Recommended Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade. Action BM-1004 Message Blade firmware <Blade firmware> on slot <Slot> is not consistent with system firmware <System firmware>. Auto-leveling blade firmware to match system firmware. Message Type Severity INFO Probable Cause...
  • Page 206 BM-1007 Recommended Configure the blade so that it will persistently enable the ports. Action BM-1007 Message If set, clear EX/VEX/FC Fastwrite configuration for all ports for blade in slot <Slot number>. Message Type Severity INFO Probable Cause Indicates the specified blade was detected for the first time after an FR4-18i was previously configured in the same slot.
  • Page 207 BM-1010 BM-1010 Message Resetting port configuration and linkcost for all ports for blade in slot <Slot number>. Message Type Severity INFO Probable Cause Indicates the specified blade was detected for the first time after an FC10-6 was previously configured in the same slot.
  • Page 208 BM-1055 BM-1055 Message Firmwaredownload timed-out for AP. Faulting switch. Message Type Severity WARNING Probable Cause Indicates that firmware download on the application processor (AP) blade has failed. Recommended Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade. Action BM-1056 Message AP is not configured.
  • Page 209 C2-1001 C2 Messages C2-1001 Message Port <port number> port faulted due to SFP validation failure. Check if the SFP is valid for the configuration. Message Type Severity ERROR Probable Cause Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver pair, or a faulty cable between the peer ports.
  • Page 210 C2-1006 C2-1006 Message S<slot number>,C<chip index>: Internal link errors reported, no hardware faults identified, continuing monitoring: fault1:0x<fault1_cnt>, fault2:0x<fault2_cnt> thresh1:0x<threshold_used>. Message Type Severity WARNING Probable Cause Indicates that some internal link errors have been detected. These errors can be normal in an active running system.
  • Page 211 C2-1009 C2-1009 Message S<slot number>,P<port number>(<blade port number>): portcfglongdistance vc_translation_link_init = 1 overwrites fill word IDLE. ARB will be used on the link. Message Type Severity WARNING Probable Cause Indicates that the portcfglongdistance vc_translation_link_init 1 command has overwritten the fill word IDLE.
  • Page 212 C2-1013 C2-1013 Message S<slot number>,P<port number>(<blade port number>): Duplicate rte_tbl_select detected. Message Type Severity WARNING Probable Cause Indicates that the selected table is corrupted. Recommended This message must have a matching message for the other duplicate table. Reset both the specified Action ports.
  • Page 213 C2-1016 C2-1016 Message Port is faulted due to port re-initialization failure on internal Port S<slot number>,P<port number>(<blade port number>) with reason <port fault reason>. Message Type Severity ERROR Probable Cause Indicates that the specified port failed due to port re-initialization failure. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 214 C2-1019 C2-1019 Message S<slot number>,C<chip index>: HW ASIC Chip TXQ FID parity error threshold reached type = 0x<chip error type>. Message Type Severity WARNING Probable Cause Indicates that an internal error is observed in the application-specific integrated circuit (ASIC) hardware that may degrade the data traffic.
  • Page 215 C2-1027 C2-1027 Message Detected credit loss on Peer internal Port of Slot <slot number>, Port <port number>(<blade port number>) vc_no=<vc number> crd(s)lost=<Credit(s) lost> complete_loss:<complete credit loss>. Message Type Severity INFO Probable Cause Indicates that credit loss was detected on the peer port. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 216 C3-1001 C3 Messages C3-1001 Message Port <port number> failed due to SFP validation failure. Check if the SFP is valid for the configuration. Message Type Severity ERROR Probable Cause Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver pair, or a faulty cable between the peer ports.
  • Page 217 C3-1006 C3-1006 Message S<slot number>,C<chip index>: Various non-critical hardware errors were observed: fault1:0x<fault1_cnt>, fault2:0x<fault2_cnt> thresh1:0x<threshold_used>. Message Type Severity WARNING Probable Cause Indicates that some errors were found in hardware that may or may not impact the data traffic. Recommended No action is required. Usually these errors are transient. Action C3-1007 Message...
  • Page 218 C3-1009 C3-1009 Message S<slot number>,P<port number>(<blade port number>): portcfglongdistance vc_translation_link_init = 1 overwrites fill word IDLE. ARB will be used on the link. Message Type Severity WARNING Probable Cause Indicates that the portcfglongdistance vc_translation_link_init 1 command has overwritten the fill word IDLE.
  • Page 219 C3-1012 C3-1012 Message S<slot number>,P<port number>(<blade port number>): Link Timeout on internal port ftx=<frame transmitted> tov=<real timeout value> (><expected timeout value>) vc_no=<vc number> crd(s)lost=<Credit(s) lost> complete_loss:<Compless credit loss>. Message Type LOG | FFDC Severity CRITICAL Probable Cause Indicates that one or more credits have been lost on a back-end port, and there is no traffic on that port for two seconds.
  • Page 220 C3-1015 C3-1015 Message Port re-initialized due to Link Reset failure on internal Port S<slot number>,P<port number>(<blade port number>). Message Type Severity WARNING Probable Cause Indicates that the specified port is re-initialized due to link reset failure. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action slotPowerOn commands.
  • Page 221 C3-1018 C3-1018 Message Link reset threshold value exceeded in the link S<slot number>,P<port number>(<blade port number>). Message Type Severity ERROR Probable Cause Indicates that the specified blade is faulted because the link reset threshold value has exceeded. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action slotPowerOn commands.
  • Page 222 C3-1021 C3-1021 Message S<slot number>,P<port number>(<blade port number>): Port is offline due to Encryption Compression Block error. Message Type Severity WARNING Probable Cause Indicates that an internal error is observed in the application-specific integrated circuit (ASIC) hardware that may degrade the data traffic. Recommended When this error occurs, the software will automatically recover from the error and no action is required.
  • Page 223 C3-1026 C3-1026 Message S<slot number>,P<port number>(<blade port number>): Faulting F_port due to extra credit detected:ftx=<ftx> curr_cred=<current credits> actual_cred=<actual credits>. Message Type Severity WARNING Probable Cause Indicates that the device is returning the wrong number of receiver-ready (R_RDY) frames. Recommended When this error is observed persistently, replace the device. Action C3-1027 Message...
  • Page 224 CAL-1001 CAL Messages CAL-1001 Message Switch offline requested by remote domain <domain number>. Message Type Severity INFO Probable Cause Indicates that the specified remote domain requested the local domain to be disabled. Recommended Check the error message log on the remote domain using the errShow command to find the reason. Action Fabric OS Message Reference 53-1002749-01...
  • Page 225 CCFG-1001 CCFG Messages CCFG-1001 Message Failed to initialize <module>, rc = <error>. Message Type Severity ERROR Probable Cause Indicates that the initialization of a module within the Converged Enhanced Ethernet (CEE) configuration management daemon has failed. Recommended Download a new firmware version using the firmwareDownload command. Action CCFG-1002 Message...
  • Page 226 CCFG-1004 CCFG-1004 Message Configuration replay failed due to missing system startup configuration file. Message Type Severity ERROR Probable Cause Indicates that the startup configuration file has been moved or deleted and therefore replaying the system configuration has failed. Recommended Execute the copy file startup-config command to restore the startup configuration file from any backup Action retrieved on the server.
  • Page 227 CCFG-1008 Recommended No action is required. Action CCFG-1008 Message CMSH init failed: <msg>. Message Type Severity ERROR Probable Cause Indicates that the CEE Management Shell (CMSH) initialization has failed. Recommended No action is required. Action CCFG-1009 Message Successfully copied to <destination>. Message Type Severity INFO...
  • Page 228 CCFG-1011 CCFG-1011 Message Linecard configuration mismatch on slot <slot>. Message Type Severity INFO Probable Cause Indicates that the inserted line card is different from the pre-configured line card on the specified slot. Recommended Execute the no linecard command to remove the line card configuration. Action CCFG-1012 Message...
  • Page 229 CDR-1001 CDR Messages CDR-1001 Message Port <port number> port fault. Change the SFP or check cable. Message Type Severity ERROR Probable Cause Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver pair, a faulty cable between the peer ports, or the port speed configuration does not match the capability of the SFP transceiver.
  • Page 230 CDR-1004 CDR-1004 Message S<slot number>,C<chip index>: Invalid DMA ch pointer, chan:<Channel number>, good_addr:0x<Good address> bad_addr:0x<Bad address>. Message Type Severity ERROR Probable Cause Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade the data traffic. Recommended Restart the system at the next maintenance window.
  • Page 231 CDR-1007 CDR-1007 Message S<slot number>,C<chip index>: Internal link errors have been reported, no hardware faults identified, continuing to monitor for errors: flt1:0x<fault1_cnt>, flt2:0x<fault2_cnt> thresh1:0x<threshold_used>. Message Type Severity WARNING Probable Cause Indicates that some errors were found in hardware that may or may not impact the data traffic. Recommended No action is required.
  • Page 232 CDR-1010 CDR-1010 Message S<slot number>,C<chip index>: Internal monitoring of faults has identified suspect hardware, blade may need to be reset or replaced: fault1:0x<fault1_cnt>, fault2:0x<fault2_cnt> thresh2:0x<threshold_used>. Message Type Severity CRITICAL Probable Cause Indicates that above-normal errors observed in hardware that may or may not impact the data traffic. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 233 CDR-1014 CDR-1014 Message Link Reset on Internal Port S<slot number>,P<port number>(<blade port number>) vc_no=<vc number> crd(s)lost=<Credit(s) lost>. Message Type Severity WARNING Probable Cause Indicates that one or more credits were lost and the link is reset. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action slotPowerOn commands.
  • Page 234 CDR-1017 CDR-1017 Message Blade in Slot <slot number> faulted due to unavailable ports in internal Trunk. Message Type Severity ERROR Probable Cause Indicates that the specified blade is faulted due to unavailable ports in internal trunk. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action slotPowerOn commands.
  • Page 235 CDR-1022 CDR-1022 Message S<slot number>,P<port number>(<blade port number>): Link Timeout on External port, ftx=<frame transmitted> tov=<real timeout value> (><expected timeout value>) vc_no=<vc number> crd(s)lost=<Credit(s) lost>. Message Type Severity WARNING Probable Cause Indicates that above-normal errors are observed in hardware that may or may not impact the data traffic. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 236 CHS-1002 CHS Messages CHS-1002 Message ki_gd_register_action failed with rc = <return val>. Message Type LOG | FFDC Severity ERROR Probable Cause Indicates an internal error. Recommended To recover a bladed system, execute the slotPowerOff and slotPowerOn commands on the blade. To Action recover a non-bladed system, execute the fastBoot command on the switch.
  • Page 237 CHS-1005 CHS-1005 Message Diag attach failed during recovery, disabling slot = <slot number>. Message Type Severity ERROR Probable Cause Indicates that the diagnostic blade attach operation has failed during failover or recovery. Recommended For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade. Action For a non-bladed switch, restart or power cycle the switch.
  • Page 238 CNM-1001 CNM Messages CNM-1001 Message Failed to allocate memory: (<function name>). Message Type Severity ERROR Probable Cause Indicates that the specified function has failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Action Restart or power cycle the switch. CNM-1002 Message Failed to initialize <module>...
  • Page 239 CNM-1004 CNM-1004 Message iSCSI service is <status> on the switch. Message Type Severity INFO Probable Cause Indicates that the crypto service is enabled or disabled on the switch. Recommended No action is required. Action CNM-1005 Message Posting event CNM_EVT_GRP_LEADER_ELECTED Name [<nodeName>], WWN [<WWN>]. Message Type Severity INFO...
  • Page 240 CNM-1008 Recommended No action is required. Action CNM-1008 Message Posting event CNM_EVT_NODE_EJECT nodeName [<nodeName>], WWN [<WWN>]. Message Type Severity INFO Probable Cause Indicates that the specified node is ejected from the Encryption Group (EG). Recommended No action is required. Action CNM-1009 Message Posting event CNM_EVT_STANDALONE_MODE.
  • Page 241 CNM-1011 CNM-1011 Message Posting event CNM_EVT_NODE_JOIN_TIMEOUT nodeName [<nodeName>], WWN [<wwn>], ipaddress [<ipAddr>]. Message Type Severity INFO Probable Cause Indicates the node join timeout. Recommended Take the peer node offline, and rejoin the node to Encryption Group (EG). Action CNM-1012 Message Posting event CNM_EVT_EG_DELETED.
  • Page 242 CNM-1015 Recommended No action is required. Action CNM-1015 Message Posting event Potential Cluster Split condition. Message Type Severity INFO Probable Cause Indicates a Potential Cluster Split condition. Recommended No action is required. Action CNM-1016 Message Posting event Detected a EG degrade condition. Message Type Severity INFO...
  • Page 243 CNM-1018 CNM-1018 Message Got CNM_FSM_EVT_JOIN_REQ when already a member, My assigned name [<nodename>], dropping request. Message Type Severity INFO Probable Cause Indicates the node is already a member of the Encryption Group (EG). Recommended No action is required. Action CNM-1019 Message Join Rejected by GL node, fix certificate and later add member node from GL node, or reboot the member node.
  • Page 244 CNM-1021 CNM-1021 Message Failed to sign the node authentication message, admission control might fail. Message Type Severity INFO Probable Cause Indicates that node admission control has failed. Recommended No action is required. Action CNM-1022 Message Operation not allowed on GL Node. Message Type Severity INFO...
  • Page 245 CNM-1025 Recommended No action is required. Action CNM-1025 Message Operation not allowed, as member is active with the Cluster. Eject member node and retry. Message Type Severity INFO Probable Cause Indicates an operation is not allowed on a member node. Recommended Eject member node and retry the operation.
  • Page 246 CNM-1028 CNM-1028 Message Certfile <certificate file name> already exists. No need to sync up. Message Type Severity INFO Probable Cause Indicates that the certificate file for the node already exists. Recommended No action is required. Action CNM-1029 Message Certfile <certificate file name> content does not match the cert sent by GL. Message Type Severity WARNING...
  • Page 247 CNM-1032 Recommended No action is required. Action CNM-1032 Message Certfile <certificate file name> size <file size> does not match cert file size <length> sent by GL. Message Type Severity WARNING Probable Cause Indicates that there is a size mismatch between a node's certificate file and the certificate file received from the group leader (GL).
  • Page 248 CNM-1035 CNM-1035 Message Cluster is in degraded state. Posting degrade event. Message Type Severity WARNING Probable Cause Indicates an event is being posted to specify the cluster is in a degraded state. Recommended No action is required. Action CNM-1036 Message All the active nodes of the cluster are in ONLINE state.
  • Page 249 CNM-1038 CNM-1038 Message Split-Brain Arbitration won, majority GL Node, remote:local [<remote_count>:<local_gl_ncount>]. Message Type Severity INFO Probable Cause Indicates that split-brain arbitration is won. Recommended No action is required. Action CNM-1039 Message Split-Brain Arbitration lost, Minority WWN/GL Node, remote_WWN:local_WWN <wbuf>. Message Type Severity INFO Probable Cause...
  • Page 250 CNM-1042 Recommended No action is required. Action CNM-1042 Message Completed updating persistent Cluster DB. Message Type Severity INFO Probable Cause Indicates the persistent database update is complete. Recommended No action is required. Action CNM-1043 Message Received HBT from undefined node IpAddress [<ip>], WWN [<wwn>]. Possible configuration error.
  • Page 251 CNM-1045 CNM-1045 Message Member node [<wwn>] is having dual IP stack.Registering member node with dual IP in an EG with only IPv6 is not allowed. Message Type Severity ERROR Probable Cause Indicates that the member node with dual IP stack was registered with the IPv6 Encryption Group (EG). Recommended No action is required.
  • Page 252 CNM-1049 Recommended No action is required. Action CNM-1049 Message Failed to define node, Node Name [<string>]. Message Type Severity ERROR Probable Cause Indicates the failure to define the node object. Recommended No action is required. Action CNM-1050 Message Node Admission Control failed due to mismatch in Access Gateway Daemon (AGD) mode settings, rejecting node [<nodename>].
  • Page 253 CNM-1052 CNM-1052 Message Member node registered with another Encryption Group. To proceed eject the member node [<nodename>] from other EG. Message Type Severity ERROR Probable Cause Indicates that the member node is registered with another Encryption Group (EG). Recommended No action is required. Action CNM-1053 Message...
  • Page 254 CNM-1055 CNM-1055 Message Got CNM_FSM_EVT_JOIN_REQ when already a member from same GL node, rejoining EG with GL [<glname>]. Message Type Severity INFO Probable Cause Indicates the node is rejoining the Encryption Group (EG). Recommended No action is required. Action CNM-1056 Message Posting event CNM_EVT_EE_INITIALIZING Slot [<slot>], WWN [<wwn>], IP [<ip>], flags [<flags>].
  • Page 255 CNM-1058 CNM-1058 Message Posting event CNM_EVT_OFFLINE Slot [<slot>], WWN [<wwn>], IP [<ip>], flags [<flags>]. Message Type Severity INFO Probable Cause Indicates that the encryption engine is removed from the Encryption Group (EG). Recommended No action is required. Action CNM-1059 Message Local Node CP certificate pair mismatch detected, re-initialize the node.
  • Page 256 CNM-1062 Recommended No action is required. Action CNM-1062 Message Copied certificate to [<ofname>] due to change in IP. Message Type Severity INFO Probable Cause Indicates that the certificate was copied to the file with new IP name. Recommended No action is required. Action CNM-3001 Message...
  • Page 257 CNM-3003 CNM-3003 Message Event: cryptocfg Status: success, Info: Membernode \"<member_node_WWN>\" added to encryption group. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified member node was added to an encryption group. Recommended No action is required. Action CNM-3004 Message...
  • Page 258 CNM-3006 CNM-3006 Message Event: cryptocfg Status: success, Info: Heartbeat miss count set to <heartbeat_misses>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the heartbeat miss value was set. Recommended No action is required. Action CNM-3007 Message Event: cryptocfg Status: success, Info: Heartbeat timeout set to <heartbeat_timeout>.
  • Page 259 CNM-3009 CNM-3009 Message Event: cryptocfg Status: success, Info: <nodeType> <nodeWWN> registered. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified member node was registered. Recommended No action is required. Action CNM-3010 Message Event: cryptocfg Status: success, Info: Membernode <membernodeWWN> unregistered. Message Type AUDIT | LOG Class...
  • Page 260 CNM-3012 CNM-3012 Message Deleteing an EG with LUNs setup for encryption can lead to LUNs being disabled if Encryption Group name is not preserved (<egName>). Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the Encryption Group (EG) was deleted. Recreate EG with the same name if LUNs are set up for encryption.
  • Page 261 CONF-1000 CONF Messages CONF-1000 Message configDownload completed successfully <Info about the parameters and AD.>. Message Type LOG | AUDIT Class Severity INFO Probable Cause Indicates that the configDownload operation was initiated and completed successfully. The Info about the parameters and AD variable is the description of the classes of configuration parameters that were downloaded.
  • Page 262 CONF-1021 CONF-1021 Message configUpload not permitted <AD Number if AD is configured on the system>. Message Type Severity INFO Probable Cause Indicates that a configUpload operation is not permitted. There are many possible causes. Recommended Execute the errShow command to view the error log. Correct the error and execute the configUpload Action command again.
  • Page 263 CONF-1024 CONF-1024 Message configUpload failed <Message>. Message Type Severity INFO Probable Cause Indicates a configUpload operation has failed. Recommended Execute the errShow command to view the error log. Correct the error and execute the configUpload Action command again. CONF-1030 Message Configuration database full, data not committed (key: <Key of failed configuration data>).
  • Page 264 CONF-1032 CONF-1032 Message configRemove completed successfully <Message>. Message Type Severity INFO Probable Cause Indicates that the configRemove command was initiated and completed successfully. Recommended No action is required. Action CONF-1040 Message configDefault Failed. <Message>. Message Type Severity INFO Probable Cause Indicates that an error occurred while executing the configDefault command.
  • Page 265 CONF-1042 CONF-1042 Message Fabric Configuration Parameter <Parameter> changed to <Value> Message Type LOG | AUDIT Class Severity INFO Probable Cause Indicates that the fabric configuration parameter value has been changed. Recommended No action is required. Action CONF-1043 Message Fabric Configuration Parameter <Parameter> changed to <Value> Message Type LOG | AUDIT Class...
  • Page 266 CTAP-1001 CTAP Messages CTAP-1001 Message Key acquisition for <Pool or Container> <Begins or Complete>. Message Type Severity INFO Probable Cause Indicates that a change in the tape pool database has triggered the key acquisition process for each pool. Recommended Do not start tape backup or restore operations involving tape pools until the process is complete. Action Fabric OS Message Reference 53-1002749-01...
  • Page 267 CVLC-1001 CVLC Messages CVLC-1001 Message <Re-key type (First time encryption/Key expired/Manual)> re-key <Re-key action (started/completed/failed/cancelled)>, LUN SN: <LUN serial number>. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity INFO Probable Cause Indicates that the first-time encryption, key expired, or manual re-key operation is performed. The operation has been started, completed, failed, or cancelled.
  • Page 268 CVLC-1004 CVLC-1004 Message Forceful encryption LUN removal while re-key session is still active. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity INFO Probable Cause Indicates that the encryption LUN was forcefully removed while a re-key session was still active. Recommended No action is required.
  • Page 269 CVLC-1007 CVLC-1007 Message Removal of encryption LUN is not allowed when decrypt of existing data is enabled. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity ERROR Probable Cause Indicates that there has been an attempt to remove the encryption LUN while decryption of existing data is still enabled.
  • Page 270 CVLC-1010 CVLC-1010 Message Tape license is required for tape container: <Target container name>. Message Type Severity ERROR Probable Cause Indicates that the tape container is configured with non-Brocade mode but there is no valid license. Recommended Obtain a license for non-Brocade mode. Action CVLC-1011 Message...
  • Page 271 CVLC-1013 CVLC-1013 Message Unable to retrieve key record from the key archive. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity ERROR Probable Cause Indicates that the encryption engine is unable to retrieve the key record base on the key ID found in the metadata.
  • Page 272 CVLC-1016 CVLC-1016 Message LUN is out of read only mode. Reason: <Reason for LUN is out of read only mode>. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity INFO Probable Cause Indicates that the LUN is set to read/write mode. Recommended No action is required.
  • Page 273 CVLC-1019 CVLC-1019 Message Metadata exists while data state is clear text. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity ERROR Probable Cause Indicates that the data state in the LUN configuration is cleartext, but metadata exists on the LUN. Recommended Use the cryptoCfg command to confirm the configuration.
  • Page 274 CVLC-1022 CVLC-1022 Message User provided key ID <Key ID provided by the user> is ignored while data state is clear text. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity INFO Probable Cause Indicates that the key ID provided is ignored because the data state is cleartext. Recommended No action is required.
  • Page 275 CVLC-1025 CVLC-1025 Message Secondary Metadata exists for encrypted LUN not configured with -newLUN option. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity ERROR Probable Cause Indicates that the secondary metadata exists on the LUN that is not configured with the -newLUN option. Recommended Use the cryptoCfg command to remove and add the LUN with the -newLUN option.
  • Page 276 CVLC-1028 CVLC-1028 Message Not starting auto rekey on LUN with uncompressible blocks 1-16. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity WARNING Probable Cause Indicates a warning event. Recommended Perform a manual re-key on this LUN. Action CVLC-1029 Message...
  • Page 277 CVLC-1031 CVLC-1031 Message Primary LUN is restored from mirror LUN. LUN in read-only mode. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity WARNING Probable Cause Indicates that a re-keyed primary LUN may have been restored from a mirror LUN without synchronizing. Recommended Perform the following steps.
  • Page 278 CVLC-1034 CVLC-1034 Message Rekey failed on Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID> because <Failure reason>. Message Type Severity INFO Probable Cause Indicates that the first-time encryption, key expired, or manual re-key operation failed. Recommended No action is required.
  • Page 279 CVLC-1041 CVLC-1041 Message <Host IO to secondary meta-data block rejected>. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Message Type Severity WARNING Probable Cause Indicates that the host write operation on secondary metadata block region failed. Recommended Disable the initiator port.
  • Page 280 CVLM-1001 CVLM Messages CVLM-1001 Message Failed to allocate memory: (<function name>). Message Type Severity ERROR Probable Cause Indicates that the specified function has failed to allocate memory. Recommended Check the memory usage on the switch using the memShow command. Action Restart or power cycle the switch.
  • Page 281 CVLM-1004 CVLM-1004 Message Crypto device configuration between local switch (<local switch WWN>) and peer (<peer switch WWN>) is out of sync. New encryption session is not allowed. Message Type Severity WARNING Probable Cause Indicates that encryption engine nodes in the cluster encryption group have different configurations. Recommended Synchronize the configuration in the cluster group using the cryptocfg --commit command.
  • Page 282 CVLM-1008 Recommended Run the cryptocfg --commit command again. Action CVLM-1008 Message The member (<EE node WWN> <EE slot num>) of HAC (<HAC name>) is not in the fabric. Message Type Severity WARNING Probable Cause Indicates that the member of the HA cluster (HAC) is not in the fabric. Recommended Check the inter-switch link (ISL) port connected to the fabric.
  • Page 283 CVLM-1011 CVLM-1011 Message The HAC failover occurs at EE (<EE node WWN> <EE slot num>). Message Type Severity INFO Probable Cause Indicates that the HA cluster (HAC) failover occurs at the encryption engine. Recommended No action is required. Action CVLM-1012 Message The HAC failback occurs at EE (<EE node WWN>...
  • Page 284 CVLM-1014 CVLM-1014 Message RD zone getting deleted for which there is no Host/Target (<HostPortWWN>/<TargetPortWWN>) L2 zone exists in effective configuration. Message Type Severity ERROR Probable Cause Indicates deletion of Frame Redirect (RD) zone and there is no corresponding Layer 2 zone present, but IT pair is in crypto configuration.
  • Page 285 CVLM-3001 CVLM-3001 Message Event: cryptocfg Status: success, Info: Failback mode set to <failbackmode>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the failback mode was set. Recommended No action is required. Action CVLM-3002 Message Event: cryptocfg Status: success, Info: HA cluster \"<HAClusterName>\" created. Message Type AUDIT | LOG Class...
  • Page 286 CVLM-3004 CVLM-3004 Message Event: cryptocfg Status: success, Info: Cluster member added to HA cluster \"<HAClusterName>\". Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that an HA cluster member was added. Recommended No action is required. Action CVLM-3005 Message Event: cryptocfg Status: success, Info: Cluster member removed from HA cluster...
  • Page 287 CVLM-3007 CVLM-3007 Message Event: cryptocfg Status: success, Info: <diskOrTape> container \"<containerName>\" created. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified crypto-target container was created. Recommended No action is required. Action CVLM-3008 Message Event: cryptocfg Status: success, Info: Container \"<containerName>\" deleted. Message Type AUDIT | LOG Class...
  • Page 288 CVLM-3010 CVLM-3010 Message Event: cryptocfg Status: success, Info: Move crypto target container \"<cryptoTargetContainer>\" to EE <newEEWWN>/<newEESlot>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified crypto-target container was moved to another encryption engine. Recommended No action is required.
  • Page 289 CVLM-3013 CVLM-3013 Message Event: cryptocfg Status: success, Info: LUN <LUNSpec>, attached through Initiator \"<Initiator>\", added to crypto target container \"<cryptoTargetContainer>\". Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that a LUN was added to a crypto-target container. Recommended No action is required.
  • Page 290 CVLM-3016 CVLM-3016 Message Event: cryptocfg Status: success, Info: LUN <LUN Number>, attached through Initiator \"<Initiator>\" in crypto target container \"<cryptoTargetContainer>\", enabled. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified LUN in a crypto-target container was enabled. Recommended No action is required.
  • Page 291 CVLM-3019 CVLM-3019 Message Event: cryptocfg Status: success, Info: Tapepool \"<tapepoolLabelOrNum>\" modified. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified tape pool was modified. Recommended No action is required. Action CVLM-3020 Message Event: cryptocfg Status: success, Info: Manual rekey of LUN <LUNSpec> attached through Initiator \"<Initiator>\"...
  • Page 292 CVLM-3022 CVLM-3022 Message Event: cryptocfg Status: success, Info: Resume rekey of LUN <LUNSpec> attached through Initiator \"<Initiator>\" in crypto tgt container \"<cryptoTargetContainer>\". Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that a resume re-key was performed. Recommended No action is required.
  • Page 293 CVLM-3025 CVLM-3025 Message Event: cryptocfg Status: started, Info: Decommission of device (container <cryptoTargetContainer> initiator <Initiator>, LUN <LUN>). Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the decommission operation has started. Recommended No action is required. Action CVLM-3026 Message...
  • Page 294 CVLM-3028 CVLM-3028 Message Event: cryptocfg Status: success, Info: SRDF mode set to <srdfmode>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the Symmetrix Remote Data Facility (SRDF) mode was set. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 295 DOT1-1001 DOT1 Messages DOT1-1001 Message 802.1X is enabled globally. Message Type Severity INFO Probable Cause Indicates that 802.1X is enabled globally. Recommended No action is required. Action DOT1-1002 Message 802.1X is disabled globally. Message Type Severity INFO Probable Cause Indicates that 802.1X is disabled globally. Recommended No action is required.
  • Page 296 DOT1-1004 DOT1-1004 Message Port <port_name> is forcefully unauthorized. Message Type Severity INFO Probable Cause Indicates that the specified port has been unauthorized forcefully using the dot1x port-control force-unauthorized command. Recommended No action is required. Action DOT1-1005 Message 802.1X authentication is successful on port <port_name>. Message Type Severity INFO...
  • Page 297 DOT1-1007 DOT1-1007 Message No RADIUS server available for authentication. Message Type Severity CRITICAL Probable Cause Indicates that there is no remote authentication dial-in user service (RADIUS) server available for authentication. Recommended Execute the aaaConfig --show command to verify that the configured RADIUS servers are reachable Action and functioning.
  • Page 298 DOT1-1010 DOT1-1010 Message Port <port_name> is set in auto mode. Message Type Severity INFO Probable Cause Indicates that the specified port is set to auto mode. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 299 ECC-1000 ECC Messages ECC-1000 Message ECC Error <Multiple or single occurrence of errors of a given type detected> occurrence of <Automatic calibration error detected><Multiple bit error detected><Single bit error detected><Memory select error detected>. Message Type Severity ERROR Probable Cause Indicates that the processor memory controller has detected one of the several types of double data rate (DDR) memory errors.
  • Page 300 EM-1001 EM Messages EM-1001 Message <FRU ID> is overheating: Shutting down. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the specified field-replaceable unit (FRU) is shutting down due to overheating. This event is typically due to a faulty fan and can also be caused by the switch environment. Recommended Verify that the location temperature is within the operational range of the switch.
  • Page 301 EM-1004 EM-1004 Message <FRU ID> failed to power on. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the specified field-replaceable unit (FRU) failed to power on and is not being used. The FRU ID value is composed of a FRU type string and an optional number to identify the unit, slot, or port.
  • Page 302 EM-1008 EM-1008 Message Unit in <Slot number or Switch> with ID <FRU Id> is faulted, it is incompatible with the <type of incompatibility> configuration, check FOS firmware version as a possible cause. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that a blade inserted in the specified slot or the switch (for non-bladed switches) is not compatible with the platform configuration (includes the firmware version) or the switch configuration.
  • Page 303 EM-1011 EM-1011 Message Received unexpected power down for <FRU Id>, but cannot determine if it has power. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the environmental monitor (EM) received an unexpected power-down notification from the specified field-replaceable unit (FRU). However, after four seconds, it cannot be determined if it has powered down or not.
  • Page 304 EM-1014 EM-1014 Message Unable to read sensor on <FRU Id> (<Return code>). Message Type Severity ERROR Probable Cause Indicates that the environmental monitor (EM) was unable to access the sensors on the specified field-replaceable unit (FRU). Recommended Reseat the FRU. If the problem persists, replace the FRU. Action EM-1015 Message...
  • Page 305 EM-1017 EM-1017 Message Uncommitted WWN change detected. Cold reboot required. Message Type Severity WARNING Probable Cause Indicates that a user did not commit a changed World Wide Name (WWN) value before performing a system restart, power cycle, or firmware download operation. Recommended Change and commit the new WWN value.
  • Page 306 EM-1020 EM-1020 Message Unit in <Slot number> with ID <FRU Id> is faulted, it's an FCoE blade and the Ethernet switch service is not enabled. Please run <fosconfig --enable ethsw>. Message Type FFDC | LOG Severity ERROR Probable Cause Indicates that a blade inserted in the specified slot requires the Ethernet switch service, which is not enabled.
  • Page 307 EM-1031 Recommended This is often a transient error. Action Watch for the EM-1048 message, which indicates that the problem has been resolved. If the problem persists, check for loose or dirty connections. Remove all dust and debris before reseating the field-replaceable unit (FRU). If it continues to fail, replace the FRU. EM-1031 Message <FRU Id>...
  • Page 308 EM-1035 Recommended Reseat the FRU. Action Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power cycle the blade by using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware problems. If the problem persists, replace the FRU.
  • Page 309 EM-1037 EM-1037 Message <FRU Id> is no longer faulted. Message Type Severity INFO Probable Cause Indicates that the specified power supply is no longer marked faulty; probably because its AC power supply has been turned on. Recommended No action is required. Action EM-1042 Message...
  • Page 310 EM-1044 EM-1044 Message Can't power on <FRU Id>, its logical switch is shut down. Message Type Severity WARNING Probable Cause Indicates that the specified field-replaceable unit (FRU) cannot be powered on because the associated logical switch is shutdown. Recommended Execute the switchStart command on the associated logical switch. Action EM-1045 Message...
  • Page 311 EM-1047 Recommended If the blade ID listed is incorrect, the field-replaceable unit (FRU) header for the blade is corrupted and Action the blade must be replaced. If the error is due to the platform, the blade ID listed is not supported for that platform (CP) type. Remove the blade from the chassis.
  • Page 312 EM-1050 Recommended No action is required. Action EM-1050 Message FRU <FRU Id> removal detected. Message Type Severity INFO Probable Cause Indicates that a field-replaceable unit (FRU) of the type and location specified by the FRU ID value was removed from the chassis. Recommended Verify that the FRU was intended to be removed.
  • Page 313 EM-1058 EM-1058 Message Switch gets reset:<Fault reason>. Message Type Severity WARNING Probable Cause Indicates that the switch is being automatically reset because of a known resetable transient problem 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 or blade. If the reset Action threshold is reached on the switch or blade, the switch or blade will be faulted and should be replaced.
  • Page 314 EM-1061 EM-1061 Message Synchronization halted. Remove all blades of type <Blade Type Id> or upgrade your standby CP, then reboot or run haSyncStart. Message Type Severity WARNING Probable Cause Indicates that the blade in the system is not supported by the firmware on the standby control processor (CP).
  • Page 315 EM-1064 EM-1064 Message Blade:<Slot Id> is being powered off (based on user configuration) upon receiving a HW ASIC ERROR, reason:<Fault reason>. Message Type Severity CRITICAL Probable Cause Indicates that the blade is being powered off because a hardware (HW) application-specific integrated circuit (ASIC) error was detected, and you have selected to power off the problem blade when such a condition occurred.
  • Page 316 EM-1067 EM-1067 Message Stopping synchronization of the system due to <version> incompatibility with standby CP. Message Type Severity WARNING Probable Cause Indicates that the software version on the standby control processor (CP) is incompatible with this software feature enabled on this Fabric OS firmware version. Recommended Upgrade the software on the standby CP or disable the software feature on this CP.
  • Page 317 EM-1070 EM-1070 Message Slot <FRU slot number> is being powered on. Message Type Severity INFO Probable Cause Indicates that the blade in the specified slot is being intentionally powered on. Recommended No action is required. Action EM-1071 Message Unit in <Slot number> with ID <FRU Id> is faulted, it is incompatible with the following blade id(s): <blade incompatibility list>.
  • Page 318 EM-2003 EM-2003 Message <Slot Id or Switch for pizza boxes> has failed the POST tests. FRU is being faulted. Message Type Severity ERROR Probable Cause Indicates that a field-replaceable unit (FRU) has failed the Power-On Self-Test (POST). Refer to the /tmp/post[1/2].slot#.log file for more information on the faults.
  • Page 319 ESS-1001 ESS Messages ESS-1001 Message A few switches in the fabric do not support the Coordinated HotCode protocol. Message Type Severity WARNING Probable Cause Indicates one or more switches in the fabric do not support the Coordinated HotCode protocol. Continuing with the firmware download may cause data traffic disruption. Recommended Discontinue the firmware download, identify the down-level switch or switches that do not support the Action...
  • Page 320 ESS-1004 ESS-1004 Message The resume message is rejected by the domain <domain id>. Message Type Severity WARNING Probable Cause Indicates that 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 321 ESS-1009 ESS-1009 Message Fabric Name Mismatch - local(<fabric_name>) remote(<r_fabric_name> - received from domain <domain id>). Message Type AUDIT | LOG Class FABRIC Severity WARNING Probable Cause Indicates that the specified fabric name is not unique for this fabric. Recommended Select an appropriate fabric name and set it again from any switch. Action ESS-1010 Message...
  • Page 322 ESW-1001 ESW Messages ESW-1001 Message Switch is not in ready state - Switch enable failed, switch status= 0x<switch status>, c_flags = 0x<switch control flags>. Message Type Severity ERROR Probable Cause Indicates that the switch enable operation has failed. Recommended If the message persists, execute the supportFtp command (as needed) to set up automatic FTP Action transfers;...
  • Page 323 ESW-1004 ESW-1004 Message Blade attach failed during recovery, disabling slot = <slot number>. Message Type Severity ERROR Probable Cause Indicates that the specified blade has failed during failover or recovery. Recommended For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade. Action For a non-bladed switch, restart or power cycle the switch.
  • Page 324 ESW-1007 ESW-1007 Message Switch port <port number> disabled due to \"<disable reason>\". Message Type Severity WARNING Probable Cause Indicates that the switch port is disabled due to the reason displayed in the message. Recommended Based on the disable reason displayed, take appropriate action to restore the port. Action If the disable reason is "Insufficient frame buffers", reduce the distance or speed settings for the port to reduce the buffer requirement of the link.
  • Page 325 EVMD-1001 EVMD Messages EVMD-1001 Message Event could not be sent to remote proxy = <Remote proxy switch id>. Message Type Severity WARNING Probable Cause Indicates that the event could not be sent to remote proxy. This could happen if the remote proxy switch cannot be reached through in-band.
  • Page 326 FABR-1001 FABR Messages FABR-1001 Message port <port number>, <segmentation reason>. Message Type Severity WARNING Probable Cause Indicates that the specified switch port is isolated because of a segmentation resulting from mismatched configuration parameters. Recommended Based on the segmentation reason displayed with the message, look for a possible mismatch of relevant Action configuration parameters in the switches at both ends of the link.
  • Page 327 FABR-1004 Recommended Investigate the neighbor switch for problems. Run the errShow command on the neighbor switch to view Action the error log for additional messages. Check for a faulty cable or deteriorated small form-factor pluggable (SFP). Replace the cable or the SFP if necessary.
  • Page 328 FABR-1006 FABR-1006 Message Node free error, caller: <error description>. Message Type Severity WARNING Probable Cause Indicates that the Fabric OS is trying to free or deallocate memory space that has already been deallocated. This message is rare and usually indicates a problem with the Fabric OS. Recommended In case of severe memory corruption, the system may recover by performing an automatic failover.
  • Page 329 FABR-1009 FABR-1009 Message <error description>. Message Type Severity WARNING Probable Cause Indicates that errors were reported during the exchange fabric parameter state; cannot allocate domain list due to a faulty exchange fabric parameter (EFP) type. This message is rare and usually indicates a problem with the Fabric OS.
  • Page 330 FABR-1012 FABR-1012 Message <function stream>: no such type, <invalid type>. Message Type Severity WARNING Probable Cause Indicates that the fabric is not in the appropriate state for the specified process. This message is rare and usually indicates a problem with the Fabric OS. Recommended The fabric daemon will take proper action to recover from the error.
  • Page 331 FABR-1015 FABR-1015 Message FICON Insistent DID max retry exceeded: All E_Ports will be disabled. Switch is isolated. Message Type Severity ERROR Probable Cause Indicates that the application exceeded request domain ID (RDI) requests for the insistent domain ID. All E_Ports are disabled; isolating the specified switch from the fabric. Recommended Verify that the insistent domain ID is unique in the fabric and then re-enable the E_Ports.
  • Page 332 FABR-1018 FABR-1018 Message PSS principal failed (<reason for not becoming the principal switch>: <WWN of new principal switch>). Message Type Severity WARNING Probable Cause Indicates that a failure occurred when trying to set the principal switch using the fabricPrincipal command. The message notifies you that the switch failed to become the principal switch because of one of the following reasons: •...
  • Page 333 FABR-1021 Recommended Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the Action fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license.
  • Page 334 FABR-1024 FABR-1024 Message Initializing fabric size limit timer <grace period>. Message Type Severity INFO Probable Cause Indicates that the fabric size has exceeded the limit set by your value-line switches. Value-line switches have a limited fabric size (for example, a specified limit on the number of domains). This value is defined by your specific value-line license key.
  • Page 335 FABR-1031 Recommended No action is required. Action FABR-1031 Message Maximum number of retries sending ILS from port <port number> exceeded. Message Type LOG | FFDC Severity WARNING Probable Cause Indicates the fabric exhausted the maximum number of retries sending internal link service (ILS) to the iswitch daemon on the specified E_Port.
  • Page 336 FABR-1035 FABR-1035 Message Slave area <Area that does not match Master port's area> does not match Master port <Master port >. Persistently disabling port <Port that is being disabled>. Message Type Severity INFO Probable Cause Indicates the Slave port's Trunk Area differs from that of the Master port. Recommended Move the cable to a port to match with the same Master Trunk Area, or disable Trunk Area.
  • Page 337 FABR-1038 FABR-1038 Message Trunking license not present with F port trunking enabled. Persistently disabling port <Port that is being disabled>. Message Type Severity INFO Probable Cause Indicates the specified port is being disabled because F_Port trunking is enabled without a trunking license being present.
  • Page 338 FABR-1041 FABR-1041 Message Port <Port that is being disabled> is disabled due to trunk protocol error. Message Type Severity ERROR Probable Cause Indicates a link reset was received before the completion of the trunking protocol on the port. Recommended Enable the port by running the portEnable command. Action The port may recover by re-initialization of the link.
  • Page 339 FABR-1045 FABR-1045 Message Detected Base Switch conflict with remote (not neighbor) switch <Switchname> (domain <Domain ID>), BS <Base Switch Mode>. No local E_Ports disabled. Message Type Severity ERROR Probable Cause Indicates that the remote switch has a Base Switch attribute conflict with the local switch. But no ports are disabled because the remote switch is not an adjacent to the local switch.
  • Page 340 FABR-1048 FABR-1048 Message Detected Fabric ID (FID <InheritedFID> inherited) conflict with switch <Switchname> (domain <Domain ID>, FID <Fabric ID>). Message Type Severity ERROR Probable Cause Indicates that a switch in the fabric has a Fabric ID (FID) conflict with the inherited FID of the local switch. Recommended Make sure that all the switches in the fabric have the same FID or upgrade the switch firmware to a Action...
  • Page 341 FABR-1051 FABR-1051 Message D-Port <Testname> test failed for slot <Slot> and port <Port>. Message Type Severity ERROR Probable Cause Indicates that the D_Port test failed for the given slot and port due to one of the following reasons: • The small form-factor pluggable (SFP) fault detected by electrical loopback test failure. •...
  • Page 342 FABR-1054 FABR-1054 Message Rebooting the standby as it received an update before port [<Port Number>] is expanded. Message Type LOG | FFDC Severity INFO Probable Cause Indicates that the standby control processor (CP) did not have the port because the port expand operation is still in progress and the standby CP has received a port update.
  • Page 343 FABS-1001 FABS Messages FABS-1001 Message <Function name> <Description of memory need>. Message Type FFDC | LOG Severity CRITICAL 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. The Description of memory need variable specifies the memory size that was being requested.
  • Page 344 FABS-1005 FABS-1005 Message <Function name and description of problem> (<ID type>= <ID number>). Message Type Severity WARNING Probable Cause Indicates that an unsupported operation has been requested. This is usually an internal Fabric OS problem or file corruption. The following is a possible value for function name and description of problem variable: fabsys_write: Unsupported write operation: process xxx In this value, xxx is the process ID (PID), which could be any whole number.
  • Page 345 FABS-1007 FABS-1007 Message <Function name>: Media state is invalid - status=<Status value>. Message Type Severity WARNING Probable Cause Indicates that the Fabric OS has detected an invalid value in an object status field. This is usually an internal Fabric OS problem or file corruption. Recommended Reboot or power cycle the switch.
  • Page 346 FABS-1010 FABS-1010 Message <Function name>: Wrong media_event <Event number>. Message Type Severity WARNING 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 347 FABS-1014 FABS-1014 Message <Method name>[<Method tag number>]:Unknown FRU type 0x<FRU Object type>. Message Type Severity ERROR Probable Cause Indicates an unrecognized type of field-replaceable unit (FRU) has been discovered in the system. This may be caused by an incorrect FRU header, inability to read the FRU header, or the FRU may not be supported by this platform or Fabric OS version.
  • Page 348 FBC-1001 FBC Messages FBC-1001 Message Firmware version on AP blade is incompatible with that on the CP. Message Type Severity ERROR Probable Cause Indicates the control processor (CP) blade determined that the firmware version running on the application processor (AP) blade is not compatible with that running on CP. The AP and CP blades cannot communicate.
  • Page 349 FCMC-1001 FCMC Messages FCMC-1001 Message System is low on memory and has failed to allocate new memory. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for an information unit (IU). Recommended A non-bladed switch will automatically reboot.
  • Page 350 FCOE-1001 FCOE Messages FCOE-1001 Message calloc failed for <object>. Message Type Severity ERROR Probable Cause Indicates a memory failure. Recommended Check the memory usage on the switch using the memShow command. Action FCOE-1002 Message Max logingroup limit reached at <limit>. Message Type Severity WARNING...
  • Page 351 FCOE-1004 FCOE-1004 Message <device>: removing member from <lg> failed. Message Type Severity ERROR Probable Cause Indicates that removing a device from the login group has failed. Recommended Execute the supportSave command and restart the system. If the problem persists, contact your switch Action service provider.
  • Page 352 FCOE-1009 Recommended Check the IfIndex limit displayed in the message. Action FCOE-1009 Message Addition of N_Port mapping failed. Max N_Port mapping limit reached: <max n_port>. Message Type Severity INFO Probable Cause Indicates that the N_Port mapping has reached its maximum limit. Recommended Remove unwanted N_Port mappings using the fcoelogingroup --remove command and try adding Action...
  • Page 353 FCOE-1014 FCOE-1014 Message Request to add ports to VLAN <vid> failed. Message Type Severity ERROR Probable Cause Indicates that a request to add ports to the specified VLAN has failed. Recommended Execute the supportSave command and restart the system. If the problem persists, contact your switch Action service provider.
  • Page 354 FCOE-1019 Recommended Disable the active FCoE session on VLAN using the no fcoe command and try adding the FCMAP Action again. FCOE-1019 Message FLOGI ignored as FCMAP is not configured on FCoE VLAN. Message Type Severity WARNING Probable Cause Indicates that FCMAP has not been configured on FCoE VLAN. Recommended Configure FCMAP on the FCoE VLAN using the fcoe --fcmapset command.
  • Page 355 FCOE-1023 FCOE-1023 Message <portindex>, Too many logins on FCoE controller, max allowed = <MAX_DEVS_PER_CTLR>. Message Type Severity WARNING Probable Cause Indicates that the controller has reached its maximum allowed FCoE login limit. Recommended Log out some of the logged-in devices using the fcoe --resetlogin command and then log in a new Action device.
  • Page 356 FCOE-1026 FCOE-1026 Message FDISC/FLOGI mismatch. FDISC addressed to different FCF than base FLOGI. Message Type Severity WARNING Probable Cause Indicates that the base port has sent a fabric login (FLOGI) but the subsequent FDISC frames that were received on the switch do not match the original FLOGI. Recommended It is due to a CNA or target driver issue.
  • Page 357 FCOE-1029 FCOE-1029 Message Version mismatch between FIP FDISC and root VN port. Message Type Severity WARNING Probable Cause Indicates a version mismatch between the fabric login (FLOGI) and FDISC. Recommended It is due to a CNA or target driver issue. Contact CNA or target driver support team for assistance. Action FCOE-1030 Message...
  • Page 358 FCOE-1033 Recommended Wait until the chassis has fully recovered before you perform any operations. Action FCOE-1033 Message FIP v1 FLOGI received - VF port in use. Message Type Severity INFO Probable Cause Indicates that a device is trying to log in to a port that already has a device logged in. Recommended No action is required.
  • Page 359 FCOE-1038 FCOE-1038 Message logingroup#<logingroup number> (<logingroup name>) created. Message Type Severity INFO Probable Cause Indicates that the specified login group is added to the switch login group table. Recommended No action is required. Action FCOE-1039 Message Logingroup <logingroup name> deleted. Message Type Severity INFO...
  • Page 360 FCOE-1042 Recommended No action is required. Action FCOE-1042 Message FCoE login configuration transaction saved fabric-wide. Message Type Severity INFO Probable Cause Indicates that the FCoE login configuration transaction is saved fabric-wide. Recommended No action is required. Action FCOE-1043 Message FCoE login configuration management disabled. Message Type Severity INFO...
  • Page 361 FCOE-1045 FCOE-1045 Message FCoE port <port number> is configured as VE port. Message Type Severity INFO Probable Cause Indicates that the specified FCoE port is configured as a virtual expansion (VE) port. Recommended No action is required. Action FCOE-1046 Message fcoed.conf file is truncated.
  • Page 362 FCOE-1048 Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 363 FCPD-1001 FCPD Messages FCPD-1001 Message Probing failed on <error string>. Message Type Severity WARNING Probable Cause Indicates that a Fibre Channel Protocol (FCP) switch probed devices on a loop port, and probing failed on the L_Port, arbitrated loop physical address (AL_PA), or the F_Port. For ALPA, the valid range is 0x00 through 0xFF.
  • Page 364 FCPD-1003 Recommended The Brocade 4100, 4900, 5000, 7500, and AP 7600 do not support private loop devices. Refer to the Action switch vendor for a list of other port types that support private devices for inclusion into the fabric. Fabric OS Message Reference 53-1002749-01...
  • Page 365 FCPH-1001 FCPH Messages FCPH-1001 Message <function>: <failed function call> failed, out of memory condition. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for a Fibre Channel driver instance.
  • Page 366 FCPH-1004 FCPH-1004 Message NPIV port <Port Number> has same Port WWN as old port <Port Number> with pid 0x<Port PID> as part of duplicate Port WWN detection policy. Message Type Severity WARNING Probable Cause Indicates that the specified N_Port ID virtualization (NPIV) port has the same Port World Wide Name (PWWN) as the old port.
  • Page 367 FCR-1001 FCR Messages FCR-1001 Message FC router proxy device in edge created at port <port number>. Message Type Severity INFO Probable Cause Indicates that a proxy device at a port in the edge fabric has been imported at the specified port. Recommended No action is required.
  • Page 368 FCR-1004 FCR-1004 Message FC router physical devices offline at port <port number>. Message Type Severity INFO Probable Cause Indicates that one or more physical devices connected to the specified port have gone offline. Recommended Verify that the devices were intended to be taken offline. If not, verify that the devices are functioning Action properly.
  • Page 369 FCR-1007 FCR-1007 Message FC router LSAN zone deleted at port <port number>. Message Type Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone attached to the specified port was deleted in the edge fabric. Recommended No action is required. Action FCR-1008 Message...
  • Page 370 FCR-1010 FCR-1010 Message FC router LSAN zone disabled at port <port number>. Message Type Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone is disabled in the edge fabric attached to the specified port. Recommended No action is required. Action FCR-1011 Message...
  • Page 371 FCR-1013 FCR-1013 Message Phantom FSPF database exchange completed on port <port number>. Message Type Severity INFO Probable Cause Indicates that the specified EX_Port has completed the fabric shortest path first (FSFP) database exchange. Recommended No action is required. Action FCR-1015 Message New EX_Port or VEX_Port added on port <port number>...
  • Page 372 FCR-1018 FCR-1018 Message FC router proxy device entries exhausted on port <port number>. Message Type Severity ERROR 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 devices Action exported is within the range allowed by the port resource.
  • Page 373 FCR-1021 3. Use zoning commands on the edge fabrics, to reduce the LSAN zone entries on the edge fabrics. 4. Use the command on each EX_Port, one at a time, and verify that this error is not portEnable reported again. FCR-1021 Message Local LSAN device entries exhausted.
  • Page 374 FCR-1024 FCR-1024 Message Local LSAN zone <zone name> device entries for edge LSAN exhausted. Message Type Severity WARNING Probable Cause Indicates that the number of devices in a logical storage area network (LSAN) defined in the edge fabric is greater than allowed by the local LSAN zone database limitations. Recommended Remove excess device entries from this LSAN zone until the number of devices is within the range of the Action...
  • Page 375 FCR-1027 FCR-1027 Message In slot <slot number>, Port WWN roll over. Message Type Severity INFO Probable Cause Indicates that the port World Wide Name (WWN) pool has rolled over in the specified slot, and WWN entries not detected to 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 in a Action...
  • Page 376 FCR-1030 FCR-1030 Message Physical device <device WWN> came online at fabric <fabric ID>. Message Type Severity INFO Probable Cause Indicates that the physical device World Wide Name (WWN) came online in the specified fabric. Recommended No action is required. Action FCR-1031 Message Physical device <device WWN>...
  • Page 377 FCR-1034 Recommended No action is required. Action FCR-1034 Message LSAN zone added in backbone fabric. Message Type Severity INFO Probable Cause Indicates that a new logical storage area network (LSAN) zone was added to the backbone fabric. Recommended No action is required. Action FCR-1035 Message...
  • Page 378 FCR-1037 FCR-1037 Message LSAN zone disabled in the backbone fabric. Message Type Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone is disabled in the backbone fabric. Recommended No action is required. Action FCR-1038 Message Total zone entries exceeded local fabric limits by <overflow> entries, in zone: <zone name>, zone limit: <LSAN zone limit>.
  • Page 379 FCR-1040 FCR-1040 Message Proxy device deleted in the backbone fabric. Message Type Severity INFO Probable Cause Indicates that a proxy device created in the backbone fabric was deleted. Recommended No action is required. Action FCR-1041 Message LSAN zone device removed in the backbone fabric. Message Type Severity INFO...
  • Page 380 FCR-1048 Recommended No action is required. Action FCR-1048 Message On EX port (<port number>) setting port <credit type> credits failed. Message Type Severity ERROR Probable Cause Indicates that the indicated credit type was not set. Setting port credits failed. Recommended Execute the portEnable command.
  • Page 381 FCR-1054 FCR-1054 Message Port <port number> received ILS <command> of incorrect size (<actual payload size>); valid ILS size is <expected payload size>. Message Type Severity WARNING Probable Cause Indicates that an internal link service (ILS) IU of invalid size was received from the switch on the other end of the link.
  • Page 382 FCR-1057 FCR-1057 Message EX_Port(<port number>) incompatible long distance parameters on link. Message Type Severity ERROR Probable Cause Indicates that the port, which is configured in long distance mode, has incompatible long distance parameters. Recommended Check the port configuration on both sides of the link using the portCfgShow command. Action Investigate the other switch for more details.
  • Page 383 FCR-1060 FCR-1060 Message EX_Port(<port number>) has an incompatible configuration setting. Message Type Severity WARNING Probable Cause Indicates that virtual channel (VC) Link Init is enabled on the local switch and the remote switch is negotiating in R_RDY mode. The fabric might not form properly. Recommended Check the configuration on the local switch using the portCfgShow command to verify that the VC Link Action...
  • Page 384 FCR-1063 FCR-1063 Message Fabric <fabric ID> for switch with domain ID: <domain ID> mismatch with local fabric ID <local fabric ID>. Message Type Severity INFO Probable Cause Indicates that the fabric ID of the switch does not match the local switch. Recommended Run the switchShow command to display the fabric ID.
  • Page 385 FCR-1066 FCR-1066 Message Fabric on port <port number> has the same fabric ID as another fabric. Message Type Severity ERROR Probable Cause Indicates that either the fabric split, or there is another fabric (possibly the backbone) that has the same fabric ID as the fabric connected to the specified port.
  • Page 386 FCR-1069 FCR-1069 Message The FC Routing service is enabled. Message Type Severity INFO Probable Cause Indicates that the FC Routing service is enabled. This is caused by the fosConfig –-enable fcr or the configDownload command with the fcrState set to 1 (enabled). Note that the FC Routing service is disabled by the factory.
  • Page 387 FCR-1072 FCR-1072 Message Port <port number> is changed from FCR port to non FCR port. Message Type Severity INFO Probable Cause Indicates that the port is no longer an EX_Port or VEX_Port. Recommended No action is required. Action FCR-1073 Message Switch with domain ID <domain ID>...
  • Page 388 FCR-1075 FCR-1075 Message Zone Name configuration is larger than <Zone Name Limit> characters in the edge fabric connected to port <port number>. Message Type Severity ERROR Probable Cause Indicates that the zone name configuration size created in the connected fabric exceeds the maximum supported by the FC Router.
  • Page 389 FCR-1078 FCR-1078 Message LSAN name <LSAN name> is too long. It is dropped. Message Type Severity WARNING Probable Cause Indicates the length of the logical storage area network (LSAN) name exceeds the limit of 64 characters. Recommended Change the name and reactivate the zone database. Action FCR-1079 Message...
  • Page 390 FCR-1081 FCR-1081 Message The pause message is rejected by the domain <Domain>. Message Type Severity WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric has rejected the pause message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of the rejected pause message.
  • Page 391 FCR-1084 FCR-1084 Message The resume retry count is exhausted for the domain <Domain>. Message Type Severity WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric did not accept the resume message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of this issue.
  • Page 392 FCR-1087 FCR-1087 Message ExPort <ExPort > connects to fabric <fabric > with capability to use XISL domain <Domain >. Message Type Severity ERROR Probable Cause Indicates that the EX_Port connects to the logical fabric containing a domain that has the capability to use extended ISL (XISL).
  • Page 393 FCR-1091 FCR-1091 Message Backbone Fabric ID changed to <Tag>. Message Type Severity INFO Probable Cause Indicates that the backbone fabric ID has been changed. Recommended No action is required. Action FCR-1092 Message FCR ELS trap entries exhausted. Message Type Severity ERROR Probable Cause Indicates that the FCR ELS trap entries are exhausted.
  • Page 394 FCR-1094 FCR-1094 Message No Integrated Routing license present. EX-Port <ExPort> will not perform device sharing with other Brocade Native mode fabric(s). Message Type Severity WARNING Probable Cause Indicates that an EX_Port has been configured in Brocade Native mode. Device sharing will not occur with other Brocade Native mode fabrics because the Integrated Routing license is not installed.
  • Page 395 FCR-1097 FCR-1097 Message Failed to get <data type> for <message phase> message: port <port number>, retval <error code>. Message Type Severity ERROR Probable Cause Indicates that the authentication process failed to get a particular authentication value at certain phase. Data type is the payload or structure that failed to get memory. Recommended Usually this problem is transient.
  • Page 396 FICN-1003 FICN Messages FICN-1003 Message FICON Tape Emulation License Key is not installed. Message Type Severity WARNING Probable Cause Indicates FICON Tape Emulation requires a License Key. Recommended Use the appropriate License Key. Action FICN-1004 Message FICON XRC Emulation License Key is not installed. Message Type Severity WARNING...
  • Page 397 FICN-1006 FICN-1006 Message FICON GEPort <GE port number> TID <Tunnel number> Feature Change failed Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled>...
  • Page 398 FICN-1009 FICN-1009 Message DevIng:CmdReject Sense Data rcvd:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> LastCmds=0x<the Last 4 commands issued to the device> Sense Data:Bytes0-0xB=0x<bytes 0-3 of sense data from the device><bytes 4-7 of sense data from the device><bytes 8-0x0b of sense data from the device>.
  • Page 399 FICN-1012 FICN-1012 Message DevDiskIng:Device level exception found for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>: Oxid=0x<The OXID that was reported in the Device Level Exception Frame>. Message Type Severity ERROR Probable Cause Indicates a Device Level Exception frame received from the FICON direct attached storage device (DASD) Control Unit.
  • Page 400 FICN-1015 FICN-1015 Message DevEgr:cuPath=0x<VEPortNumber HostDomain HostPort DeviceDomain>******:Discarding Invalid LRCd SOF=0x<The invalid Frame's SOF value (SOFiX or SOFnx)> count=<The total number of frames that have been received from the peer with incorrect FICON LRC values>. Message Type Severity ERROR Probable Cause Indicates a frame was received from the peer emulation processing with an invalid Longitudinal Redundancy Checking (LRC) values.
  • Page 401 FICN-1018 FICN-1018 Message DevIng:FCUB Lookup failed for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR>******. Message Type Severity ERROR Probable Cause Indicates the FICON Control Unit sent a frame that cannot be associated with a FICON Control Unit number (CUADDR). Recommended Contact your vendor's customer support for assistance. Action FICN-1019 Message...
  • Page 402 FICN-1021 FICN-1021 Message DevTapeEgr:FICON Tape Cancel:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> Elapsed Time=<the current SIO time in seconds for the device>.<the current SIO time in milliseconds for the device> seconds. Message Type Severity WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer support Action...
  • Page 403 FICN-1024 FICN-1024 Message DevTapeEgr:FICON Purge received Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity ERROR Probable Cause Indicates the FICON channel issued a Purge Path command sequence for a device. Recommended If there was an unexpected job failure or I/O error associated with this event, contact your vendor's Action customer support for assistance.
  • Page 404 FICN-1027 FICN-1027 Message DevTapeIng:Device level exception found for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>: Oxid=0x<The OXID of the frame that included the Device Level Exception>. Message Type Severity ERROR Probable Cause Indicates an active emulation device delivered a Device Level Exception frame to the emulation processing.
  • Page 405 FICN-1030 FICN-1030 Message HostDiskIng:FICON Purge received:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity ERROR Probable Cause Indicates an active disk emulation device received a FICON Purge Path from the channel. Recommended If there was an unexpected job failure or I/O error associated with this event, contact your vendor's Action customer support for assistance.
  • Page 406 FICN-1033 FICN-1033 Message HostEgr:Logical Path Established on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR><CUADDR>**. Message Type Severity INFO Probable Cause Indicates the peer-side FICON Control Unit has accepted a logical path establishment command sequence with the FICON channel. Recommended No action is required. This is a part of the FICON path initialization. Action FICN-1034 Message...
  • Page 407 FICN-1036 FICN-1036 Message HostIng:FICON RLP Request on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort><LPAR><CUADDR>**. Message Type Severity INFO Probable Cause Indicates 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 FICN-1037 Message...
  • Page 408 FICN-1039 FICN-1039 Message HostIng:FCUB Lookup failed for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR>********. Message Type Severity ERROR Probable Cause Indicates a locally connected FICON channel sent a frame that could not be associated with a FICON Control Unit. Recommended Contact your vendor's customer support for assistance. Action FICN-1040 Message...
  • Page 409 FICN-1042 FICN-1042 Message HostTapeIng:FICON Cancel received Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for this device>. Message Type Severity WARNING Probable Cause Indicates a job was canceled during a Tape Write Pipelining. Recommended If this was an unexpected event (cancel is normally an operator event), contact your vendor's customer Action support for assistance.
  • Page 410 FICN-1045 FICN-1045 Message HostTapeIng:FICON Purge received:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity WARNING Probable Cause Indicates a Purge Path was received from the locally connected FICON channel. This is performed during the path recovery. Recommended If this was an unexpected event, contact your vendor's customer support for assistance. Action FICN-1046 Message...
  • Page 411 FICN-1048 FICN-1048 Message DevDiskEgr:FICON Cancel received Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<Current emulation state of the FICON device> sflags=0x<The current emulation status flags>. Message Type Severity WARNING Probable Cause Indicates the operator has canceled a read or write job. Recommended This is an unexpected event;...
  • Page 412 FICN-1051 FICN-1051 Message XRC Session Established: SessID=<SDM Assigned Session ID>, Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> Message Type Severity INFO Probable Cause Indicates a PSF command has been received to initiate an eXtended Remote Copy (XRC) session with the extended direct attached storage device (DASD) device. Recommended No action is required.
  • Page 413 FICN-1054 FICN-1054 Message XRC Device Suspended: SessID=<SDM Assigned Session ID>, Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity WARNING Probable Cause Indicates a PSF command has been received to suspend an eXtended Remote Copy (XRC) session with the extended direct attached storage device (DASD) device. Recommended If this was an unexpected event, contact your vendor's customer support for assistance.
  • Page 414 FICN-1057 FICN-1057 Message Error return from frame generation processing for a FICON device: Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity ERROR Probable Cause Indicates an internal resource shortage caused an error so that an emulation frame could not be created and sent to a device.
  • Page 415 FICN-1060 FICN-1060 Message Error return from fcFwdPrcEgressFrame: Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity ERROR Probable Cause Indicates an internal resource shortage caused an error so that an emulation frame could not be created and sent to a device. Recommended This is an unexpected event;...
  • Page 416 FICN-1063 FICN-1063 Message Egress Abort:Oxid=0x<the OXID of the aborted exchange>:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>:LastStates=0x<prior emulation state array><previous emulation state><current emulation state>. Message Type Severity ERROR Probable Cause Indicates an abort operation has been received from a peer FC interface for an active emulation exchange.
  • Page 417 FICN-1066 FICN-1066 Message MemAllocFailed for GEPort=<VEPortNumber> VEport=<GE0 or GE1 number> could not create required structure. Message Type Severity WARNING Probable Cause Indicates an internal resource limit has been encountered so that additional control block memory could not be allocated. Recommended This is an unexpected event;...
  • Page 418 FICN-1069 FICN-1069 Message Emulation Configuration Error on TunnelId <Tunnel ID>:. Message Type Severity ERROR Probable Cause Indicates an error has been noted in the FICON configuration. Refer to the string for the nature of the configuration issue. Recommended If resolution of the configuration issue cannot be completed, contact your vendor's customer support for Action assistance.
  • Page 419 FICN-1072 FICN-1072 Message DevTapeEgr:Tape Loaded on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity INFO Probable Cause Indicates the tape I/Os are processed from a locally connected Logical Partition (LPAR), which indicates that a tape is loaded on a device. Recommended No action is required.
  • Page 420 FICN-1075 Recommended No action is required. Action FICN-1075 Message HostTapeIngr:ReadBlkReport:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>: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 421 FICN-1077 FICN-1077 Message DevTapeEgr:Unloaded:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>:states=0x<4 prior emulation states><previous emulation state><current emulation state>:cmds=0x<last 4 commands received from the channel for this device>:status=0x<last 4 status values received from the channel for this device>:flags=0x<tape report bit flags (0x80-Tape Loaded,0x40-WriteEmul,0x20-RdBlkEmul,0x10-RdCpEmul)>. Message Type Severity INFO...
  • Page 422 FICN-1079 FICN-1079 Message DevTapeEgr:ReadBlkReport:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>: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 423 FICN-1082 Recommended This is normally an unexpected event; contact your vendor's customer support for assistance. Action FICN-1082 Message EmulEls:CSWR_RSCN received on GEPort=<GEPortNumber> VEPort=<VEPortNumber> Domain=0x<Domain> Port=0x<Port Host/Device Side>. Message Type Severity WARNING Probable Cause Indicates an attached port which had a FICON emulated path established has logged out from the switch.
  • Page 424 FICN-1085 FICN-1085 Message FICON FCIP Tunnel is Up on GE<Either ge0 or ge1>,tunnel Id=<The configured tunnel ID (0-7)>. Message Type Severity INFO Probable Cause Indicates a FICON FCIP tunnel has been established successfully to the peer switch. Recommended No action is required. Action FICN-1086 Message...
  • Page 425 FICN-1088 FICN-1088 Message DevTeraEgr:FICON Cancel received Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for the device> tflags=0x<the current emulation tera control flags for the device> sflags=0x<the current emulation status control flags for the device>. Message Type Severity WARNING Probable Cause...
  • Page 426 FICN-1091 FICN-1091 Message DevTeraEgr:FICON Selective Reset:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> Elapsed Time=<the current SIO time in seconds for the device>.<the current SIO time in milliseconds for the device> seconds. Message Type Severity ERROR Probable Cause Indicates the FICON channel issued a Selective Reset sequence for a device. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer support Action...
  • Page 427 FICN-1094 FICN-1094 Message DevTeraIng:UnusualStatus:WriteCancelSelr:Generating Final Ending Status Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Message Type Severity INFO Probable Cause Indicates the FICON tera write pipeline is completing an emulated Selective Reset sequence. Recommended If there was an unexpected job failure or I/O error associated with this event, contact your vendor's Action customer support for assistance.
  • Page 428 FICN-1097 FICN-1097 Message HostTeraEgr:AS Link Level Reject (LRJ) from CU Rx Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> LastCmd=0x<Last 4 commands issued to this device from the channel> LastStatus=0x<Last 4 status values sent to the channel from this device>. Message Type Severity ERROR Probable Cause...
  • Page 429 FICN-1100 FICN-1100 Message HostTeraIng:FICON Selective Reset:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> Elapsed Time=<the number of seconds since the last IO started for this device>.<the number of milliseconds since the last IO started for this device> seconds. Message Type Severity ERROR Probable Cause Indicates that protocol errors in emulation in the Control Unit or network errors can cause Selective...
  • Page 430 FICN-1103 FICN-1103 Message DevTeraIngr:Exceptional Status rcvd on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<current emulation state> status=0x<the exceptional status value>. Message Type Severity INFO Probable Cause Indicates that the status (0x0D or 0x05) indicating the device is going down was received from the device or error status (including Unit Check 0x02) is received from an active emulation device.
  • Page 431 FICN-1106 FICN-1106 Message DevPrintEgr:AS Link Level Reject (LRJ) from Chan on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> LastCmd=0x<the Last 4 commands issued to the device> LastStatus=0x<the Last 4 status values received from the device>. Message Type Severity ERROR Probable Cause Indicates the FICON channel indicated in the path issued a Link Level Reject (LRJ) frame for a sequence from the device.
  • Page 432 FICN-1109 FICN-1109 Message DevPrintEgr:FICON Selective Reset:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> State=0x<the current state of the device that received the selective reset> statArray=0x<the last 4 status values received from the device> cmdArray=0x<the last 4 commands that were issued to the device> tflags=0x<the current emulation tera control flags for the device> sflags=0x<the current emulation status control flags for the device>.
  • Page 433 FICN-1112 FICN-1112 Message DevPrintIng:Auto Sense Data received on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> Bytes0-0xB=0x<bytes 0-3 of sense data from the device><bytes 4-7 of sense data from the device><bytes 8-0x0b of sense data from the device>. Message Type Severity WARNING Probable Cause Indicates the FICON Printer write pipelining processed sense data from a FICON device.
  • Page 434 FICN-1115 FICN-1115 Message HostPrintEgr:CmdReject Sense Data Rcvd:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> LastCmds=0x<Last 4 commands received from the channel for this device> SenseData:Bytes0-0xB=0x<Bytes 0-3 of sense data from the device><Bytes 4-7 of sense data from the device><Bytes 8-0x0b of sense data from the device>. Message Type Severity ERROR...
  • Page 435 FICN-1118 FICN-1118 Message HostPrintIng::FICON Selective Reset:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for this device> LastCmds=0x<the last 4 commands received from the channel for this device> LastStatus=0x<the last 4 status values presented to the channel for this device>. Message Type Severity ERROR...
  • Page 436 FICN-1121 FICN-1121 Message HostPrintIng:LRJ received on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> lastCmds=0x<Last 4 commands received from the channel for this device> lastStatus=0x<Last 4 status values presented to the channel for this device> treating as system reset event. Message Type Severity WARNING Probable Cause...
  • Page 437 FICN-2006 FICN-2006 Message FICON VEPort <VE port number> Feature Change failed Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled> TinTir <1 or 0 - FICON TIN/TIR Emulation Enabled or Disabled>...
  • Page 438 FICN-2066 FICN-2066 Message MemAllocFailed for VEport=<VEPortNumber> could not create required structure. Message Type Severity WARNING Probable Cause Indicates an internal resource limit has been encountered so that additional control block memory could not be allocated. Recommended This is an unexpected event; either the maximum number of emulation devices are already in use or Action there is an internal memory leak.
  • Page 439 FICN-2085 FICN-2085 Message FICON or FCP Emulation Enabled FCIP Tunnel is Up on VEPort=<VEPortNumber>. Message Type Severity INFO Probable Cause Indicates a FICON or Fibre Channel Protocol (FCP) emulation-enabled FCIP tunnel has been established successfully to the peer switch. Recommended No action is required.
  • Page 440 FICU-1001 FICU Messages FICU-1001 Message <error message>. Message Type Severity ERROR Probable Cause Indicates that one of the configuration management functions have failed. The key variable is a component of the Fabric OS configuration database and is for support use only. The error variable is an internal error number.
  • Page 441 FICU-1004 FICU-1004 Message <function name>: Failed to set FICON Management Server (FMS) mode: conflicting PID Format:<pid_format>, FMS Mode:<mode>. Message Type Severity WARNING 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 442 FICU-1007 Recommended Check if the FICON channel corresponding to the PID in the message is functioning correctly. Action FICU-1007 Message <function name>: Failed to allocate memory while performing <message>. Message Type Severity WARNING Probable Cause Indicates that memory resources are low. This may be a transient problem. Recommended Check the memory usage on the switch using the memShow command.
  • Page 443 FICU-1010 FICU-1010 Message FMS mode enable failed due to port(s) with areas 0xFE or 0xFF is(are) connected to device(s). Message Type Severity WARNING Probable Cause Indicates that the FICON Management Server (FMS) mode was not enabled because ports with areas 0xFE or 0xFF are connected to devices.
  • Page 444 FICU-1013 FICU-1013 Message Host data file cannot be reset to proper size. Message Type Severity WARNING Probable Cause Indicates that the file system is too full to create the host data file at the proper size. Recommended Execute the switchStatusShow command to check if the flash memory is full. If the flash memory is full, Action execute the supportSave command to clear the core files.
  • Page 445 FICU-1019 FICU-1019 Message Switch has been set offline by LP(<LP ID>). Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that the FICON Management Server (FMS) has disabled the switch. Recommended No action is required. Action FICU-1020 Message Port Addrs (<port mask>) have been Blocked by <source>.
  • Page 446 FICU-1022 FICU-1022 Message Detected FC8-48 and/or FC8-64 that are not manageable when FMS mode is enabled. Message Type Severity INFO Probable Cause Indicates the presence of unmanageable ports such as 48-port blade ports in the virtual fabric-disabled chassis. Recommended No action is required. For more information on the FICON CUP restrictions, refer to the FICON Action Administrator's Guide.
  • Page 447 FKLB-1001 FKLB Messages FKLB-1001 Message exchange <xid> overlapped, pid=<pid>. Message Type Severity WARNING 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 448 FLOD-1001 FLOD Messages FLOD-1001 Message Unknown LSR type: port <port number>, type <LSR header type>. Message Type Severity WARNING Probable Cause Indicates that the link state record (LSR) type is unknown. The following two LSR header types are the only known types: •...
  • Page 449 FLOD-1005 FLOD-1005 Message Invalid received domain ID: <domain number>. Message Type Severity WARNING Probable Cause Indicates that the received link state record (LSR) contained an invalid domain number. Recommended No action is required; the LSR is discarded. Action FLOD-1006 Message Transmitting invalid domain ID: <domain number>.
  • Page 450 FSPF-1001 FSPF Messages FSPF-1001 Message Input Port <port number> out of range. Message Type Severity ERROR Probable Cause Indicates that the specified input port number is out of range because it does not exist on the switch. Recommended No action is required. This is a temporary kernel error that does not affect your system. If the problem Action persists, execute the supportSave command and contact your service provider.
  • Page 451 FSPF-1005 FSPF-1005 Message Wrong Section Id <section number>, should be <section number>, input port = <port number>. Message Type Severity ERROR Probable Cause Indicates that an incorrect section ID was reported from the specified input port. The section ID is part of the fabric shortest path first (FSPF) protocol and is used to identify a set of switches that share an identical topology database.
  • Page 452 FSPF-1008 FSPF-1008 Message ICL triangular topology is formed among the domains: <domain number> (self), <domain number>, and <domain number>. Message Type Severity INFO Probable Cause Indicates that the inter-chassis link (ICL) triangular topology is formed. Recommended No action is required. Action FSPF-1009 Message...
  • Page 453 FSPF-1012 Recommended Investigate current ICL configuration to ensure that all recommendations for cabling are satisfied. Action FSPF-1012 Message All existing ICL topology imbalances have been corrected. Message Type Severity INFO Probable Cause Indicates that the existing inter-chassis link (ICL) configuration that was resulting in an unbalanced topology has been corrected.
  • Page 454 FSS-1001 FSS Messages FSS-1001 Message Component (<component name>) dropping HA data update (<update ID>). Message Type Severity WARNING Probable Cause Indicates that an application has dropped a high availability (HA) data update. Recommended For a dual control processor (CP) system, enable the HA state synchronization using the haSyncStart Action command.
  • Page 455 FSS-1004 FSS-1004 Message Memory shortage. Message Type Severity ERROR Probable Cause Indicates that the system ran out of memory. Recommended Execute the memShow command to view memory usage in the switch. Action For a dual CP system, enable the high availability (HA) state synchronization using the haSyncStart command.
  • Page 456 FSS-1007 FSS-1007 Message <component name>: Faulty Ethernet connection. Message Type Severity CRITICAL Probable Cause Indicates that the Ethernet connection between the active control processor (CP) and the standby CP is not healthy. This error occurs when the standby CP does not respond to a request from the active CP within five seconds.
  • Page 457 FSS-1010 FSS-1010 Message FSS Warning: <Warning Message>. Message Type Severity WARNING Probable Cause Indicates that a Fabric OS state synchronization (FSS) error may have occurred. Recommended Execute the supportSave command and contact your switch service provider. Action FSS-1011 Message FSS Info: <Info Message>. Message Type Severity INFO...
  • Page 458 FSSM-1002 FSSM Messages FSSM-1002 Message HA State is in sync. Message Type Severity INFO Probable Cause Indicates that the high availability (HA) state of the active control processor (CP) is in synchronization with the HA state of the standby CP. If the standby CP is healthy, the failover will be nondisruptive. Recommended No action is required.
  • Page 459 FSSM-1004 Recommended For a dual CP system, execute the firmwareDownload command to load compatible firmware on the Action standby CP. Fabric OS Message Reference 53-1002749-01...
  • Page 460 FW-1001 FW Messages FW-1001 Message <label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 end-user Action installation.
  • Page 461 FW-1004 FW-1004 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the internal temperature of the switch has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 462 FW-1007 FW-1007 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the speed of the fan has risen above the high boundary. Fan problems typically contribute to temperature problems. Recommended Consistently abnormal fan speeds generally indicate that the fan is failing.
  • Page 463 FW-1010 FW-1010 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the power supply is faulty. The power supply is not producing enough power. Recommended Verify that you have installed the power supply correctly and that it is correctly seated in the chassis. If Action the problem persists, replace the faulty power supply.
  • Page 464 FW-1033 FW-1033 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the temperature of the small form-factor pluggable (SFP) has changed. Frequent fluctuations in SFP temperature may indicate a deteriorating SFP. Recommended No action is required.
  • Page 465 FW-1036 FW-1036 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the temperature of the small form-factor pluggable (SFP) has changed from a value outside of the acceptable range to a value within the acceptable range. Frequent fluctuations in temperature may indicate a deteriorating SFP.
  • Page 466 FW-1039 FW-1039 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the receive power value of the small form-factor pluggable (SFP) has risen above the high boundary. The receive performance area measures the amount of incoming laser to help you determine whether the SFP is in good working condition.
  • Page 467 FW-1042 FW-1042 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has fallen below the low boundary. The transmit performance area measures the amount of outgoing laser to help you determine whether the SFP is in good working condition.
  • Page 468 FW-1045 FW-1045 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has changed. If the supplied voltage of the SFP transceiver is outside of the normal range, this may indicate a hardware failure. Recommended No action is required.
  • Page 469 FW-1048 FW-1048 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 470 FW-1051 FW-1051 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has risen above the high boundary. High voltages indicate possible hardware failures. Recommended Frequent voltage fluctuations indicate that the SFP is deteriorating.
  • Page 471 FW-1054 FW-1054 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the value of the small form-factor pluggable (SFP) Power on Hours has risen above the high boundary. The high value indicates the maximum lifetime use of the SFP. Recommended Replace the SFP.
  • Page 472 FW-1115 FW-1115 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of times E_Ports have gone down has risen above the high boundary. 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 473 FW-1118 Recommended Verify that the cable is properly connected at both ends. Verify that the small form-factor pluggables Action (SFPs) have not become faulty. An inexplicable fabric reconfiguration might be a transient error and might not require troubleshooting. FW-1118 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>).
  • Page 474 FW-1120 FW-1120 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 475 FW-1123 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. FW-1123 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of domain ID changes has risen above the high boundary.
  • Page 476 FW-1126 • Incompatible link parameters. During E_Port initialization, ports exchange link parameters. Rarely, incompatible parameters result in segmentation. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. FW-1126 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>).
  • Page 477 FW-1128 FW-1128 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 478 FW-1131 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. FW-1131 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of zone changes has risen above the high boundary.
  • Page 479 FW-1134 FW-1134 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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.
  • Page 480 FW-1137 FW-1137 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 481 FW-1140 FW-1140 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 482 FW-1162 FW-1162 Message <Port Name> <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of link failures that the port experiences has risen above the high boundary. Link loss errors occur when a link experiences a loss of signal and fails.
  • Page 483 FW-1165 Recommended Check both ends of your cable connection. Verify that the cable and SFPs are not faulty. Action If you continue to experience synchronization loss errors, troubleshoot your host bus adapter (HBA) and contact your switch service provider. FW-1165 Message <Port Name>...
  • Page 484 FW-1167 FW-1167 Message <Port Name> <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of synchronization losses that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 485 FW-1170 FW-1170 Message <Port Name> <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of signal losses that the port experiences has risen above the high boundary. Loss of signal generally indicates a physical problem.
  • Page 486 FW-1173 FW-1173 Message <Port Name> <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of protocol errors that the port experiences has fallen below the low boundary. Occasional protocol errors occur due to software glitches.
  • Page 487 FW-1176 FW-1176 Message <Port Name> <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of invalid words that the port experiences has changed. Invalid words usually indicate a hardware problem with a small form-factor pluggable (SFP) or cable. Recommended Verify that both ends of the connections, the SFP, and the cable are not faulty.
  • Page 488 FW-1179 FW-1179 Message <Port Name> <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of invalid words that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 489 FW-1182 FW-1182 Message <Port Name> <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has risen above the high boundary.
  • Page 490 FW-1185 FW-1185 Message <Port Name> <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the percentage of incoming traffic that the port experiences has fallen below the low boundary.
  • Page 491 FW-1188 FW-1188 Message <Port Name> <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the percentage of outgoing traffic that the port experiences has changed. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation.
  • Page 492 FW-1191 FW-1191 Message <Port Name> <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the percentage of outgoing traffic that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 493 FW-1194 FW-1194 Message <Port Name> <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of state changes that the port experiences has risen above the high boundary. 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 494 FW-1197 FW-1197 Message <Port Name> <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of link resets that the port experiences has fallen below the low boundary level. Link resets occur due to link timeout errors that indicate no frame activity.
  • Page 495 FW-1200 FW-1200 Message <Port Name> <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of C3 transmit timeout frames has changed. Recommended Check the target device; it could be slow. Action FW-1201 Message...
  • Page 496 FW-1203 FW-1203 Message <Port Name> <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of C3 transmit timeout frames is between the high and low thresholds. Recommended Check the target device;...
  • Page 497 FW-1206 FW-1206 Message <Port Name> <Label> is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the trunk utilization is above its threshold level. Recommended Increase the bandwidth by adding more links to the trunk. Action FW-1207 Message...
  • Page 498 FW-1217 FW-1217 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of Arbitrated Loop Physical Address (ALPA) cyclic redundancy check (CRC) errors has fallen below the low boundary. This indicates that errors have been detected in the FC frame. 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 499 FW-1219 FW-1219 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of cyclic redundancy check (CRC) errors has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 500 FW-1242 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. A low number of CRC errors means that the fabric is functioning normally. The CRC error area of the end-to-end performance monitor class helps you tune the fabric. To reduce CRC messages, experiment with alternative topologies and cabling schemes.
  • Page 501 FW-1244 FW-1244 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of end-to-end word frames that the switch receives has changed. Receive performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.
  • Page 502 FW-1247 FW-1247 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of end-to-end word frames that the switch receives has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 503 FW-1250 FW-1250 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of end-to-end word frames that the switch transmits has risen above the high 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 504 FW-1273 FW-1273 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of frame types or commands that the port receives has fallen below the low boundary.
  • Page 505 FW-1296 FW-1296 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of Telnet violations has changed. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of IP addresses that are authorized to establish Telnet connections to switches in the fabric.
  • Page 506 FW-1299 FW-1299 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of Telnet violations has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 507 FW-1302 FW-1302 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of Hypertext Transfer Protocol (HTTP) violations has risen above the high boundary. HTTP violations indicate that a browser connection request has been received from an unauthorized IP address.
  • Page 508 FW-1305 Recommended Execute the errShow command to determine the IP address that sent the request. Responses to Action security-class messages depend on user policies. Consult your security administrator for response strategies and policies. FW-1305 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value>...
  • Page 509 FW-1307 FW-1307 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 510 FW-1310 FW-1310 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of read SNMP (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 511 FW-1313 FW-1313 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of write SNMP (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 512 FW-1316 FW-1316 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of SCSI Enclosure Services (SES) violations has changed. SES violations indicate that a Small Computer System Interface (SCSI) Enclosure Services request has been received from an unauthorized World Wide Name (WWN).
  • Page 513 FW-1319 FW-1319 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of SCSI Enclosure Services (SES) violations has changed from a value outside of the acceptable range to a value within the acceptable range. SES violations indicate that a Small Computer System Interface (SCSI) Enclosure Services (SES) request has been received from an unauthorized World Wide Name (WWN).
  • Page 514 FW-1322 FW-1322 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of Management Server (MS) violations has risen above the high boundary. MS violations indicate that an MS access request has been received from an unauthorized World Wide Name (WWN).
  • Page 515 FW-1325 FW-1325 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 516 FW-1328 FW-1328 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 517 FW-1331 FW-1331 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 518 FW-1334 FW-1334 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of Switch Connection Control (SCC) policy 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 Name (WWN) that are allowed to be members of a fabric.
  • Page 519 FW-1337 Recommended Execute the errShow command to determine the device WWN, switch WWN, and switch port. Action Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. FW-1337 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value>...
  • Page 520 FW-1339 FW-1339 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of Device Connection Control (DCC) violations has changed from a value outside of the acceptable range to a value within the acceptable range. DCC violations indicate that an unauthorized device tried to join the fabric.
  • Page 521 FW-1342 FW-1342 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING 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 Execute the errShow command to determine the IP location of the login attempt.
  • Page 522 FW-1345 FW-1345 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 fabric configuration server (FCS).
  • Page 523 FW-1347 FW-1347 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 524 FW-1349 FW-1349 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 525 FW-1351 FW-1351 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 526 FW-1353 FW-1353 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 527 FW-1355 FW-1355 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 528 FW-1358 Recommended No action is required. Action FW-1358 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates that the number of authentication failures has risen above the high boundary. Authentication failures can occur for many reasons.
  • Page 529 FW-1361 Recommended Responses to security-class messages depend on user policies. Consult your security administrator for Action response strategies and policies. FW-1361 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of switch link authentication protocol (SLAP) faulty packets has fallen below the low boundary.
  • Page 530 FW-1364 FW-1364 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 for Action response strategies and policies.
  • Page 531 FW-1367 FW-1367 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO 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 532 FW-1370 Recommended No action is required. Action FW-1370 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING 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 533 FW-1372 FW-1372 Message <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of incompatible security database violations has changed. This violation indicates the number of secure switches with different version stamps have been detected. When a switch is in secure mode, it connects only to another switch that is in secure mode and has a compatible security database.
  • Page 534 FW-1375 Recommended Responses to security-class messages depend on user policies. Consult your security administrator for Action response strategies and policies. FW-1375 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of incompatible security database violations has changed from a value outside...
  • Page 535 FW-1377 FW-1377 Message <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of illegal commands has fallen below the low 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.
  • Page 536 FW-1379 FW-1379 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of illegal commands has changed from a value outside of the acceptable range to a value within the acceptable range.
  • Page 537 FW-1402 FW-1402 Message <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type AUDIT | LOG Class Severity WARNING Probable Cause Indicates that the flash memory usage percentage has risen above the high boundary. Flash memory increases and decreases slightly with normal operation of the switch.
  • Page 538 FW-1405 FW-1405 Message <Label>,is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that the memory usage is below the low memory threshold. Recommended No action is required. Action FW-1406 Message...
  • Page 539 FW-1408 FW-1408 Message <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the memory usage is between the low and high or middle memory thresholds. Recommended No action is required.
  • Page 540 FW-1426 FW-1426 Message Switch status change contributing factor Power supply: <Number Bad> bad, <Number Missing> absent. Message Type Severity WARNING Probable Cause Indicates that the switch is not in a healthy state. This occurred because the number of faulty or missing power supplies is greater than or equal to the policy set by the switchStatusPolicySet command.
  • Page 541 FW-1429 FW-1429 Message Switch status change contributing factor: Power supplies are not redundant. Message Type Severity WARNING Probable Cause Indicates that the switch is not in a healthy state. This occurred because the power supplies are not in the correct slots for redundancy. Recommended Rearrange the power supplies so that one is in an odd slot and another in an even slot to make them Action...
  • Page 542 FW-1432 FW-1432 Message Switch status change contributing factor WWN: <Number Bad> bad. Message Type Severity WARNING Probable Cause Indicates that the switch is not in a healthy state. This occurred because the number of faulty World Wide Name (WWN) cards is greater than or equal to the policy set by the switchStatusPolicySet command. Recommended Replace the faulty WWN card.
  • Page 543 FW-1435 FW-1435 Message Switch status change contributing factor Flash: usage out of range. Message Type Severity WARNING Probable Cause Indicates that the switch is not in a healthy state. This occurred because the flash memory usage is out of range. The policy was set using the switchStatusPolicySet command. Recommended Execute the supportSave command to clear out the kernel flash.
  • Page 544 FW-1438 FW-1438 Message Switch status change contributing factor Missing SFPs: <Number of missing SFPs> missing SFPs out of <Total number of SFPs> SFPs:config(<Percentage configured> percent,<Actual threshold limit>). (Port(s) <port list>). Message Type Severity WARNING Probable Cause Indicates that the switch is not in a healthy state. This occurred because the number of missing small form-factor pluggable (SFPs) is greater than or equal to the policy set by the switchStatusPolicySet command.
  • Page 545 FW-1441 FW-1441 Message <FRU label> state has changed to <FRU state>. Message Type Severity INFO Probable Cause Indicates that the state of the specified field-replaceable unit (FRU) has changed to inserted. This means that a FRU is inserted but not powered on. Recommended Verify that the event was planned.
  • Page 546 FW-1445 Recommended Replace the FRU. Action FW-1445 Message Four power supplies are now required for 2X redundancy, Switch Status Policy values changed. Message Type Severity INFO Probable Cause Indicates that the switch requires four power supplies and the prior Switch Status Policy parameters will be overwritten to reflect this.
  • Page 547 FW-1447 FW-1447 Message Switch status change contributing factor Core Blade: <Number Bad> Core blade failures (<Switch State>). Message Type Severity WARNING Probable Cause Indicates that the switch is not in a healthy state. This occurred because the number of core blade failures is greater than or equal to the policy set by the switchStatusPolicySet command.
  • Page 548 FW-1501 FW-1501 Message Mail overflow cleared - <Mails discarded> alerts discarded. Message Type Severity INFO Probable Cause Indicates that the mail overflow condition has cleared. Recommended No action is required. Action FW-1502 Message Invalid Email address <Invalid address> is configured from pre-7.0.0 config file. Message Type Severity WARNING...
  • Page 549 FW-1511 FW-1511 Message <Port Name> <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of link failures that the port experiences has changed and crossed the lower threshold boundary to a value within the acceptable range.
  • Page 550 FW-1514 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. FW-1514 Message <Port Name> <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO...
  • Page 551 FW-1517 FW-1517 Message <Port Name> <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of protocol errors that the port experiences has changed and crossed the lower threshold boundary to a value within the acceptable range.
  • Page 552 FW-1520 FW-1520 Message <Port Name> <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of invalid words that the port experiences has changed and dropped the below upper threshold boundary to a value within the acceptable range.
  • Page 553 FW-1523 FW-1523 Message <Port Name> <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the percentage of incoming traffic that the port experiences has changed and crossed the lower threshold boundary to a value within the acceptable range.
  • Page 554 FW-1526 FW-1526 Message <Port Name> <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the percentage of outgoing traffic that the port experiences has changed and dropped below the upper threshold boundary to a value within the acceptable range.
  • Page 555 FW-1529 FW-1529 Message <Port Name> <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of link resets that the port experiences has changed and crossed the lower threshold boundary to a value within the acceptable range.
  • Page 556 FW-1532 FW-1532 Message <Port Name> <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the number of C3 transmit timeout frames has dropped below the upper threshold boundary and is in between the low and high thresholds.
  • Page 557 FW-1535 FW-1535 Message Fabric Watch has stopped portfencing feature for <Area String> loss area in <Port Name> class since FOS6.3. Disabling port fencing feature for this. Message Type Severity INFO Probable Cause Indicates that Port Fencing is configured for link loss and synchronization loss in previous versions, but upgrading to a new version resets the bit because Port Fencing is not supported.
  • Page 558 FW-3010 FW-3010 Message <Port Name> <Label> value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the circuit utilization has changed. Recommended Respond to this message as is appropriate to the particular policy of the end-user installation. Action FW-3011 Message...
  • Page 559 FW-3013 FW-3013 Message <Port Name> <Label> is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates that the circuit utilization is between the high and low boundary thresholds. Recommended No action is required.
  • Page 560 FW-3016 FW-3016 Message <Port Name> <Label> is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity WARNING Probable Cause Indicates the packet loss that the circuit experiences is above the high boundary threshold. Recommended No action is required. Action FW-3017 Message...
  • Page 561 FW-3019 FW-3019 Message <Port Name> <Label> is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Message Type Severity INFO Probable Cause Indicates the number of state changes that the circuit experiences is below the low boundary level. The state of the circuit has changed because the circuit has gone offline or the circuit has come online.
  • Page 562 FW-3022 FW-3022 Message Timebase for <Key> is changed to Minute as Seconds is not supported. Message Type Severity INFO Probable Cause Indicates that the timebase for the class is changed implicitly to minutes because a seconds timebase is not supported. Recommended No action is required.
  • Page 563 HAM-1001 HAM Messages HAM-1001 Message Standby CP is not healthy, device <device name> status BAD, Severity = <severity level>. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that a standby control processor (CP) device error is reported by the high availability manager (HAM) health monitor, with the specified device and severity level.
  • Page 564 HAM-1005 • 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 • Reboot:API •...
  • Page 565 HAM-1006 HAM-1006 Message EMAC controller for Active CP is BAD. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the local Ethernet Media Access Controller (EMAC) on the active CP has been marked BAD as determined by the diagnostic test run by the high availability manager (HAM) module. Recommended The standby CP will take over and reset the active CP.
  • Page 566 HAM-1009 HAM-1009 Message Need to MANUALLY REBOOT the system for recovery - auto-reboot is disabled. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the recovery by auto-restart is disabled, therefore the switch needs to be manually restarted for recovery. This message is displayed if the event logged in HAM-1007 has occurred and auto-reboot is disabled.
  • Page 567 HAM-1013 HAM-1013 Message <error message>. Message Type Severity CRITICAL Probable Cause Indicates that the software watchdog has detected termination of a restartable daemon, but could not restart the daemon. Recommended Manually initiate a restart or failover, if needed. Action HAM-1014 Message <error message>.
  • Page 568 HAMK-1001 HAMK Messages HAMK-1001 Message Warm Recovery Failed. Message Type LOG | FFDC Severity CRITICAL Probable Cause Indicates that the switch failed during the warm recovery. Recommended This event triggers the switch restart automatically and attempts a cold recovery. Action Execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 569 HAMK-1004 HAMK-1004 Message Resetting standby CP (double reset may occur). Message Type Severity INFO Probable Cause Indicates that the standby control processor (CP) is being reset due to a loss of heartbeat. Typically, this message is displayed when the standby CP has been restarted. Note that in certain circumstances, a CP may experience a double reset and restart twice.
  • Page 570 HIL-1101 HIL Messages HIL-1101 Message Slot <slot number> faulted, <nominal voltage> (<measured voltage>) is above threshold. Message Type Severity ERROR Probable Cause Indicates that the blade voltage is above threshold. Recommended Replace the faulty blade or switch (for non-bladed switches). Action HIL-1102 Message...
  • Page 571 HIL-1104 HIL-1104 Message Blower <blower number> faulted, <nominal voltage> (<measured voltage>) is below threshold. Message Type Severity ERROR Probable Cause Indicates that the fan voltage is below threshold. Recommended Run the psShow command to verify the power supply status. Action Try to reseat the faulty fan field-replaceable units (FRUs) and power supply FRU to verify that they are seated properly.
  • Page 572 HIL-1107 HIL-1107 Message Switch faulted, <nominal voltage> (<measured voltage>) above threshold. System preparing for reset. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the switch voltage is above threshold. This message is specific to non-bladed switches. Recommended For switches that do not have field-replaceable units (FRUs), replace the entire switch.
  • Page 573 HIL-1202 HIL-1202 Message Blower <blower number> faulted, speed (<measured speed> RPM) below threshold. Message Type Severity ERROR Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. Recommended Replace the fan FRU. Action HIL-1203 Message Fan <fan number>...
  • Page 574 HIL-1206 HIL-1206 Message Fan <fan number> sensor <sensor number> , speed (<measured speed> RPM) below threshold. Message Type Severity ERROR 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 non-bladed switches. Recommended Replace the fan field-replaceable unit (FRU).
  • Page 575 HIL-1301 HIL-1301 Message 1 blower failed or missing. Replace failed or missing blower assembly immediately. Message Type Severity WARNING 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 576 HIL-1304 HIL-1304 Message Two fans failed. Replace failed fan FRUs immediately. Message Type Severity ERROR 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. Action HIL-1305 Message...
  • Page 577 HIL-1307 HIL-1307 Message Four or five fans failed. Replace failed fan FRUs immediately. Message Type Severity ERROR 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 578 HIL-1311 Recommended Because the fans are not field-replaceable, replace the switch if the temperature is high. Action HIL-1311 Message No fans are faulty. Message Type Severity INFO Probable Cause Indicates recovery from an earlier condition of one or more fans having failed. Recommended This can only occur on switches with non-removable fans.
  • Page 579 HIL-1403 HIL-1403 Message All fan FRUs missing. Install fan FRUs immediately. Message Type Severity WARNING Probable Cause Indicates that all fan field-replaceable units (FRUs) have been removed. Recommended Install the missing fan FRUs immediately. Action HIL-1404 Message <count> fan FRUs missing. Install fan FRUs immediately. Message Type Severity WARNING...
  • Page 580 HIL-1502 HIL-1502 Message Slot <slot number>, high temperature (<measured temperature>). Unit will be shut down in 2 minutes if temperature remains high. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the temperature of this blade has risen above the critical threshold. This usually follows a high-temperature message.
  • Page 581 HIL-1505 HIL-1505 Message High temperature (<measured temperature> C), fan speed increasing per environmental specifications. Message Type Severity WARNING Probable Cause Indicates that temperatures in the system have risen above the warning threshold and that the fan speed is being increased. Recommended Run the fanShow command to verify all the fans are working properly.
  • Page 582 HIL-1508 HIL-1508 Message Fan faulty warning time expired. System preparing for shutdown. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that temperatures in the system have remained above the critical threshold too long. Recommended To avoid causing damage to the switch, the system shuts down automatically. To help prevent future Action problems, make sure that all the fans are working properly.
  • Page 583 HIL-1511 HIL-1511 Message Fan speed increasing per environmental specifications. Message Type Severity WARNING Probable Cause Indicates that temperatures in the system have risen above the warning threshold and that the fan speed is being increased. 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 the operational range of your switch.
  • Page 584 HIL-1603 HIL-1603 Message <failure count> fans out of service. System is shutting down immediately. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the total fan failure count is greater than or equal to two. Recommended To avoid causing damage to the switch, the system shuts down automatically. To help prevent future Action problems, make sure that all the fans are working properly.
  • Page 585 HIL-1611 HIL-1611 Message MISMATCH in PSU-FAN Air Flow direction. Replace PSU with fan air flows in same direction. System will be shut down in 2 minutes. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that the airflows of the power supply and fan assemblies are moving in the reverse or opposite direction, which could overheat the system.
  • Page 586 HIL-1650 HIL-1650 Message Unable to detect both WWN cards in chassis. Access to WWN halted. Message Type Severity ERROR Probable Cause Indicates that one or both of the World Wide Name (WWN) cards is missing. Both WWN cards must be present for normal operation.
  • Page 587 HLO-1001 HLO Messages HLO-1001 Message Incompatible Inactivity timeout <dead timeout> from port <port number>, correct value <value>. Message Type LOG | FFDC Severity ERROR Probable Cause Indicates that the hello (HLO) message was incompatible with the value specified in the fabric shortest path first (FSPF) protocol.
  • Page 588 HLO-1003 HLO-1003 Message Invalid Hello received from port <port number>, Domain = <domain ID>, Remote Port = <remote port ID>. Message Type Severity ERROR Probable Cause Indicates that the hello (HLO) message received was invalid and the frame was dropped. The Brocade switch will not accept fabric shortest path first (FSPF) frames from the remote switch.
  • Page 589 HMON-1001 HMON Messages HMON-1001 Message <Failure description>. Message Type FFDC | LOG Severity CRITICAL 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. Recommended Execute the firmwareDownload command to reinstall the firmware to your switch.
  • Page 590 HSL-1000 HSL Messages HSL-1000 Message HSL initialization failed. Message Type Severity CRITICAL Probable Cause Indicates a hardware subsystem layer (HSL) initialization failure. This error is caused by other system errors. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider.
  • Page 591 HSL-1003 HSL-1003 Message SFP for interface <InterfaceName> is removed. Message Type Severity INFO Probable Cause Indicates that a small form-factor pluggable (SFP) transceiver has been removed from the specified interface. Recommended No action is required. Action HSL-1004 Message Incompatible SFP for interface <InterfaceName> is detected. Message Type Severity ERROR...
  • Page 592 HSL-1006 HSL-1006 Message Failed to get kernel page size <PageSize> bytes for mmap. Message Type Severity CRITICAL Probable Cause Indicates that there is not enough contiguous kernel memory. Recommended Install more memory on the board. Action HSL-1007 Message Failed to read SFP for interface <InterfaceName>. Message Type Severity ERROR...
  • Page 593 HTTP-1001 HTTP Messages HTTP-1001 Message Switch PID format has changed to <current PID format>. Message Type Severity INFO Probable Cause Indicates that the port ID (PID) format was changed. Recommended No action is required. For more information on PID format, refer to the Fabric OS Administrator's Guide. Action HTTP-1002 Message...
  • Page 594 IBD-1000 IBD Messages IBD-1000 Message Slot <slot number> Port GE<port number>: Maximum attempts to restart failed. Disabling port. Message Type Severity ERROR Probable Cause Indicates that the specified port has crashed unexpectedly and restarting attempts have failed. Recommended Power cycle the blade using the slotPowerOff and slotPowerOn commands. Action Fabric OS Message Reference 53-1002749-01...
  • Page 595 IPAD-1000 IPAD Messages IPAD-1000 Message <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 <DHCP enabled or not>. Message Type Severity INFO Probable Cause...
  • Page 596 IPAD-1003 IPAD-1003 Message DNS parameters saved successfully. Message Type Severity INFO Probable Cause Indicates that the Domain Name System (DNS) parameters are saved successfully. Recommended No action is required. Action IPAD-1004 Message DNS parameters removed successfully. Message Type Severity INFO Probable Cause Indicates that the Domain Name System (DNS) parameters are removed successfully.
  • Page 597 IPS-1001 IPS Messages IPS-1001 Message <message> FTR_AFA/FTR_AE License Not Installed (<error>). Message Type Severity WARNING Probable Cause Indicates that either Advanced FICON Acceleration (FTR_AFA) or Advanced Extension (FTR_AE) license is not installed or assigned to the slot. Recommended Run the licenseShow command to verify the slot-based licenses are installed on the switch. Contact Action your switch supplier for an appropriate slot-based license.
  • Page 598 IPS-1004 IPS-1004 Message Port Config Mode Mismatch slot (<slot>) port(ge<port>): current mode is (<current mode>). Message Type Severity WARNING Probable Cause Indicates that configured port mode is different from the intended use. Recommended Change the port configuration (by deleting configured FCIP tunnels or iSCSI sessions) to return the port Action mode to neutral before attempting to configure the port for a different mode or use.
  • Page 599 IPS-1007 IPS-1007 Message FX8-24 blade (<slot>) is not at the correct revision. Unable to use IPSec on FCIP Tunnel (<port>). Message Type Severity WARNING Probable Cause Indicates that the tunnel configuration failed because the FX8-24 blade is not at the correct revision to support IPSec enabled tunnels on VEs 22-31.
  • Page 600 ISNS-1001 ISNS Messages ISNS-1001 Message 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>). Message Type Severity INFO Probable Cause Indicates that a user has issued the isnscCfg command.
  • Page 601 ISNS-1004 ISNS-1004 Message Timeout refreshing iSNS database with iSNS server <iSNS server IP address> slot/port <Slot number>/ge<Port number> Reg-Period <Registration-Period in seconds>. Message Type Severity WARNING Probable Cause Indicates that the Internet Storage Name Service (iSNS) client fails to receive a successful response for a DevAttrQry within the specified registration period.
  • Page 602 ISNS-1008 ISNS-1008 Message Peering with external iSNS server <iSNS server IP address> not started because configuration unchanged. Message Type Severity INFO Probable Cause Indicates that peering with the external Internet Storage Name Service (iSNS) server was already started with the same configuration. Recommended No action is required.
  • Page 603 ISNS-1011 ISNS-1011 Message iSNS Client Service is <iSNS client State (enabled/disabled)>. Message Type Severity INFO Probable Cause Indicates the current state of the Internet Storage Name Service (iSNS) client is enabled or disabled. Recommended No action is required. Use the fosConfig command to display, enable, or disable the iSNS client service. Action ISNS-1013 Message...
  • Page 604 KAC-1002 KAC Messages KAC-1002 Message KAC(<Key Vault Type>) communication Error: Error connecting to <Backup or Primary>. Message Type Severity ERROR Probable Cause Indicates that the Key Archive Client (KAC) is unable to communicate with the primary or backup key vault. Recommended Determine whether the configured key vault is operational;...
  • Page 605 KAC-1007 KAC-1007 Message KAC key archival operation to Key Vault failed, LUN=<LUN Number>, keyID=<Key ID Value>, errno=<Error Number>. Message Type Severity WARNING Probable Cause Indicates that the Key Archive Client (KAC) is unable to archive the key to primary or backup key vault. Recommended Determine whether the configured key vault is operational;...
  • Page 606 KAC-1010 KAC-1010 Message Archival for KeyID <KeyID> failed to <Keyvault IP Address>. Error code=<Error code>, string=<Error string>. Message Type Severity WARNING Probable Cause Indicates that archiving of Data Encryption Key (DEK) to the key vault failed. Recommended No action is required. Action KAC-1011 Message...
  • Page 607 KAC-1013 KAC-1013 Message Archival of the Actual DEK to the KV <Keyvault IP Address> failed. Actual Key: <Actual Key Id>. Error code=<Error code>, string=<Error string>. Message Type Severity WARNING Probable Cause Indicates that archiving of actual Data Encryption Key (DEK) to the key vault failed. Recommended No action is required.
  • Page 608 KAC-1016 KAC-1016 Message Error: Key ID mismatched in request/response. Requested key ID <Key ID in response> and key in response <Requested Key Id>. Error code=<Error code>, string=<Error string>. Message Type Severity ERROR Probable Cause Indicates a mismatch between the requested key ID and the key in the response from the key vault. Recommended Determine whether the configured key vault is operational;...
  • Page 609 KSWD-1001 KSWD Messages KSWD-1001 Message <Software component>:<Software component Process ID> failed to refresh (<Current time>:<Refresh time>). Message Type FFDC | LOG Severity WARNING Probable Cause Indicates that one of the critical daemons is found to be unresponsive. An abort signal is sent. Recommended Copy the warning message along with any core file information and contact your switch service provider.
  • Page 610 KTRC-1001 KTRC Messages KTRC-1001 Message Dump memory size exceeds dump file size. Message Type Severity WARNING Probable Cause Indicates that the dump memory size has exceeded the dump file size. Recommended Execute the supportSave command and reload the switch. If the problem persists, contact your switch Action service provider.
  • Page 611 KTRC-1004 KTRC-1004 Message Cannot write to ATA dump device. Message Type Severity ERROR Probable Cause Indicates that the write boundary in the advanced technology attachment (ATA) dump device has exceeded. Recommended Execute the supportSave command and reload the switch. If the problem persists, contact your switch Action service provider.
  • Page 612 L2SS-1001 L2SS Messages L2SS-1001 Message Linux socket error - error reason: <reason>, socket name: <socketname>, error name: <errorname>. Message Type Severity ERROR Probable Cause Indicates that an error has occurred in the Linux socket. Recommended Reboot or power cycle the switch. Action L2SS-1002 Message...
  • Page 613 L2SS-1004 L2SS-1004 Message FDB error: Error in creating AVL tree. Message Type Severity ERROR Probable Cause Indicates that the Layer 2 system (L2SYS) has encountered an error while initializing the AVL tree. Recommended Reboot or power cycle the switch. Action L2SS-1005 Message MAC-address-table hash failed even after two attempts for slot <slot>...
  • Page 614 L2SS-1007 L2SS-1007 Message MAC-address-table on slot <Slot_id> chip <Chip_id> is less than 90 percent full. Message Type Severity INFO Probable Cause Indicates that the media access control (MAC) address table on the specified chip is less than 90 percent full. Recommended No action is required.
  • Page 615 L3SS-1004 L3SS Messages L3SS-1004 Message <Function Name>, <Line No>: HW/Driver Error (possibly the CAM is full): <HW Error Message>, rc=<Error Code>. Message Type Severity ERROR Probable Cause Indicates an error in the hardware or the driver of the Layer 3 subsystem (L3SS). L3SS may have passed invalid parameters or the hardware Content Addressable Memory (CAM) may be full.
  • Page 616 LACP-1001 LACP Messages LACP-1001 Message <module> Error opening socket (<error>). Message Type Severity ERROR Probable Cause Indicates that initialization of the specified module within the Link Aggregation Control Protocol (LACP) daemon has failed. Recommended Download a new firmware using the firmwareDownload command. Action LACP-1002 Message...
  • Page 617 LANCE-1000 LANCE Messages LANCE-1000 Message Slot <slot number> Port GE<port number>: Maximum attempts to restart failed. Disabling port. Message Type Severity ERROR Probable Cause Indicates that the specified port has crashed unexpectedly and restarting attempts have failed. Recommended Power cycle the blade using the slotPowerOff and slotPowerOn commands. Action Fabric OS Message Reference 53-1002749-01...
  • Page 618 LFM-1001 LFM Messages LFM-1001 Message The Logical Fabric Manager service is disabled. Message Type Severity INFO Probable Cause Indicates that the Logical Fabric Manager service is disabled. Note that the Logical Fabric Manager service is enabled by the factory setting and it is not user-configurable. Recommended No action is required.
  • Page 619 LFM-1004 LFM-1004 Message HA is out of sync for opcode <HA OPCODE>, error value <error value>. Message Type LOG | FFDC Severity CRITICAL Probable Cause Indicates loss of high availability (HA) sync with remote control processor (CP). Recommended Collect the supportsave information using the supportsave command and contact the Brocade technical Action support.
  • Page 620 LOG-1000 LOG Messages LOG-1000 Message Previous message repeated <repeat count> time(s). Message Type Severity INFO Probable Cause Indicates that the previous message was repeated the specified number of times. Recommended No action is required. Action LOG-1001 Message A log message was dropped. Message Type LOG | FFDC Severity...
  • Page 621 LOG-1003 LOG-1003 Message The log has been cleared. Message Type Severity INFO Probable Cause Indicates that the persistent error log has been cleared. Recommended No action is required. Action LOG-1004 Message Log message <Log message that has been blocked> flooding detected and blocked. Message Type Severity INFO...
  • Page 622 LOG-1006 LOG-1006 Message Log message <Log message that has been enabled> has been enabled. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that the specified message has been enabled for logging. Recommended No action is required. Action LOG-1007 Message Log Module <Log Module that has been disabled>...
  • Page 623 LOG-1009 LOG-1009 Message Internal Log message <Log message that has been enabled to be sent to syslog server> has been enabled for syslog logging. Message Type Severity INFO Probable Cause Indicates that the specified internal message has been enabled for syslog logging. Recommended No action is required.
  • Page 624 LSDB-1001 LSDB Messages LSDB-1001 Message Link State ID <link state ID> out of range. Message Type Severity ERROR Probable Cause Indicates that the specified link state ID is out of the acceptable range. The valid link state ID is the same as the valid domain ID, with a range from 1 through 239.
  • Page 625 LSDB-1004 Recommended Run the switchDisable and switchEnable commands. A new local LSR is generated during the switch Action enable. LSDB-1004 Message No Link State Record for domain <local domain>. Message Type Severity WARNING Probable Cause Indicates that there is no link state record (LSR) for the specified local domain. Recommended No action is required.
  • Page 626 MCAST_SS-1001 MCAST_SS Messages MCAST_SS-1001 Message Socket Error: <op> (<reason>) for socket <sockname> the error code <errorname>. Message Type Severity ERROR Probable Cause Indicates that an error has occurred in the Linux socket. Recommended Restart the multicast subsystem (MCAST_SS) daemon. Action MCAST_SS-1002 Message Socket Error: <op>...
  • Page 627 MCAST_SS-1004 MCAST_SS-1004 Message NSM error: <op> (<reason>) for VLAN <vid> port <port>. Message Type Severity ERROR Probable Cause Indicates that the multicast subsystem (MCAST_SS) has encountered an error during a network service module (NSM) event. Recommended Restart the MCAST_SS daemon. Action MCAST_SS-1005 Message...
  • Page 628 MCAST_SS-1007 MCAST_SS-1007 Message Initialization error: <op> (<reason>). Message Type Severity ERROR Probable Cause Indicates that the multicast subsystem (MCAST_SS) has encountered an error during initialization. Recommended Restart the MCAST_SS daemon. Action MCAST_SS-1008 Message HAL error: <op> (<reason>) - VLAN <vid> MAC/group <address>. Message Type Severity ERROR...
  • Page 629 MCAST_SS-1010 MCAST_SS-1010 Message Message Queue error: <op> (<reason>). Message Type Severity ERROR Probable Cause Indicates that the multicast subsystem (MCAST_SS) has encountered the message queue errors. Recommended Restart the MCAST_SS daemon. Action MCAST_SS-1011 Message IDB error: <op> (<reason>) port id <portid> not found. Message Type Severity ERROR...
  • Page 630 MCAST_SS-1014 Recommended Restart the MCAST_SS daemon. Action MCAST_SS-1014 Message Snooping DB error: <op> (<reason>) MAC Not found - VLAN <vid> MAC-addr <mac address>. Message Type Severity ERROR Probable Cause Indicates that the media access control (MAC) address lookup for the specified VLAN has failed. Recommended Restart the MCAST_SS daemon.
  • Page 631 MCAST_SS-1017 MCAST_SS-1017 Message Learning error: <op> (<reason>) Invalid number <port> for ifindex <ifindex>. Message Type Severity ERROR Probable Cause Indicates that the multicast subsystem (MCAST_SS) has encountered an error while learning the media access control (MAC) addresses. Recommended Restart the MCAST_SS daemon. Action MCAST_SS-1018 Message...
  • Page 632 MCAST_SS-1020 MCAST_SS-1020 Message List Error: <op> (<reason>) VLAN <vid> MAC <mac address> group <group address>. Message Type Severity ERROR Probable Cause Indicates that the multicast subsystem (MCAST_SS) has encountered an error during the List operation. Recommended Restart the MCAST_SS daemon. Action Fabric OS Message Reference 53-1002749-01...
  • Page 633 MFIC-1001 MFIC Messages MFIC-1001 Message failure at sysmod_scn registry rc= <failure reason>. Message Type Severity ERROR Probable Cause Indicates the system is temporarily out of resources. Recommended No action is required; this message is often transitory. Action If the message persists, run the reboot or the haFailover command (if applicable). If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 634 MFIC-1003 Recommended IDID mode is a fabric-wide mode; make sure that any switches added to the fabric are configured with Action the same IDID mode as the fabric. If you are enabling or disabling IDID mode, this message is for information purposes only, and no action is required.
  • Page 635 MM-1001 MM Messages MM-1001 Message VPD block 0 CRC is bad. Message Type Severity WARNING Probable Cause Indicates that CRC in the VPD block 0 is bad. This could indicate corruption or tampering. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider.
  • Page 636 MPTH-1001 MPTH Messages MPTH-1001 Message Null parent, lsId = <number>. Message Type LOG | FFDC Severity ERROR Probable Cause Indicates that a null parent was reported. The minimum cost path (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 637 MQ-1004 MQ Messages MQ-1004 Message mqRead, queue = <queue name>, queue ID = <queue ID>, type = <message type>. Message Type Severity ERROR Probable Cause Indicates an unexpected message has been received in the specified message queue. The queue name value is always fspf_q.
  • Page 638 MQ-1006 MQ-1006 Message queue <queue name>: msg too long (<number of bytes>:<message queue size>). Message Type Severity WARNING Probable Cause Indicates the incoming message size is larger than the message queue size. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 639 MS-1001 MS Messages MS-1001 Message MS Platform Segmented port=<port number> (0x<port number (hex)>) (<reason for segmentation> <domain> (0x<domain (hex)>)). Message Type Severity WARNING Probable Cause Indicates that the Management Server (MS) has segmented from another switch domain at the specified port because of errors or inconsistencies defined in the MS platform service.
  • Page 640 MS-1003 MS-1003 Message MS detected Unstable Fabric(<message string><domain number>). Message Type Severity INFO Probable Cause Indicates that the Management Server (MS) detected an unstable fabric; the command or operation may not be successfully completed. This message is often transitory. The message string value can be one of the following: •...
  • Page 641 MS-1005 MS-1005 Message MS Invalid CT Response from d=<domain>. Message Type Severity ERROR Probable Cause Indicates that the Management Server (MS) received an invalid common transport (CT) response from the switch domain. MS expects either a CT accept IU or a reject IU; the MS received neither response, which violates the Fibre Channel - Generic Services (FS-GS) specification.
  • Page 642 MS-1009 MS-1009 Message RLIR event. Slot/Port <slot number>/<port number> (0x<PID (hex)>). Device Port Tag is 0x<port tag>. <message text>. Message Type Severity ERROR Probable Cause Indicates a registered link incident record (RLIR) has been generated for one of the actions indicated by the message value.
  • Page 643 MS-1023 MS-1023 Message Management Server Topology Discovery Service <Enabled or Disabled>. Message Type Severity INFO Probable Cause Indicates that the Management Server (MS) topology discovery service is being enabled or disabled. Recommended No action is required. Action MS-1024 Message Management Server Access Control List is Updated. Message Type Severity INFO...
  • Page 644 MS-1026 MS-1026 Message MS Platform disabled port <port number> domain <domain> to block enabling Platform service through merge operation. Message Type Severity WARNING Probable Cause Indicates that the Management Server (MS) has disabled the specified E_Port connected to the specified domain because an implicit enable operation of the MS platform service has been blocked.
  • Page 645 MS-1029 MS-1029 Message Duplicate Fabric Name - <fabric_name> matching with FID <Fabric ID>. Message Type AUDIT | LOG Class FABRIC Severity ERROR Probable Cause Indicates that the configured fabric name is already used for another partition. Recommended Select a different fabric name and reconfigure. Action MS-1030 Message...
  • Page 646 MSTP-1001 MSTP Messages MSTP-1001 Message <message>: <message>. Message Type Severity ERROR Probable Cause Indicates that the system has failed to allocate memory. Recommended Check the memory usage on the switch using the memShow command. Action Restart or power cycle the switch. MSTP-1002 Message <message>: <message>.
  • Page 647 MSTP-2001 MSTP-2001 Message <message>. Message Type Severity INFO Probable Cause Indicates that the multiple spanning tree protocol (MSTP) bridge mode has changed. Recommended No action is required. Action MSTP-2002 Message <Bridge mode information>. My Bridge ID: <Bridge ID> Old Root: <Old Root ID> New Root: <New Root ID>.
  • Page 648 MSTP-2004 MSTP-2004 Message MSTP instance <instance> is deleted. Message Type Severity INFO Probable Cause Indicates that the specified multiple spanning tree protocol (MSTP) instance has been deleted. Recommended No action is required. Action MSTP-2005 Message VLAN <vlan_ids> is <action> on MSTP instance <instance>. Message Type Severity INFO...
  • Page 649 NBFS-1001 NBFS Messages NBFS-1001 Message Duplicate E_Port SCN from port <portnumber> in state <state change name> (<state change number>). Message Type Severity INFO Probable Cause Indicates a duplicate E_Port state change notification (SCN) was reported. The neighbor finite state machine (NBFSM) states are as follows: •...
  • Page 650 NBFS-1003 NBFS-1003 Message DB_XMIT_SET flag not set in state <current state name>, input <state name>, port <portnumber>. Message Type Severity WARNING Probable Cause Indicates the database transmit set flag was not set for the specified input state on the specified port. Neighbor finite state machine (NBFSM) states are as follows: •...
  • Page 651 NS-1001 NS Messages NS-1001 Message 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. Message Type Severity WARNING Probable Cause Indicates that the response payload exceeds the maximum frame size the remote switch can handle. Recommended Execute the firmwareDownload command to upgrade the remote switch with Fabric OS v4.3 or later, or Action...
  • Page 652 NS-1004 Recommended To avoid disruption of traffic in the event of an unplanned failover, schedule a firmware download so that Action the active and standby CPs have the same firmware version. Reduce the local device count to follow the capability of the earliest version of firmware. NS-1004 Message Number of local devices <Current local device count>, exceeds the standby can...
  • Page 653 NS-1007 Recommended The switch will process the new process ID (PID) and leave the existing PID intact. Subsequent switch Action operations will clean up the obsolete PID. However, it is recommended that administrators remove devices with a duplicate WWN. NS-1007 Message NS has detected a logical ISL port <LISL port number>...
  • Page 654 NS-1010 NS-1010 Message CSCTL mode enabled on port <csctlport> QoS zoning will be ignored for devices on this port. Message Type Severity WARNING Probable Cause Indicates that class-specific control (CS_CTL) mode has been enabled on the specified port that has devices as members of a quality of service (QoS) zone.
  • Page 655 NSM-1001 NSM Messages NSM-1001 Message Interface <InterfaceName> is online. Message Type Severity INFO Probable Cause Indicates that the specified interface has come online after the protocol dependencies are resolved. Recommended No action is required. Action NSM-1002 Message Interface <InterfaceName> is protocol down. Message Type Severity INFO...
  • Page 656 NSM-1003 NSM-1003 Message Interface <InterfaceName> is link down. Message Type Severity INFO Probable Cause Indicates that the specified interface has gone offline because the link is down. Recommended Check whether the connectivity between the peer ports is proper, and the remote link is up using the Action show interface command.
  • Page 657 NSM-1007 Recommended No action is required. Action NSM-1007 Message Chassis is <status>. Message Type Severity INFO Probable Cause Indicates that the chassis has been enabled or disabled. Recommended No action is required. Action NSM-1008 Message Blade (<slot number>) is <status>. Message Type Severity INFO...
  • Page 658 NSM-1010 NSM-1010 Message InterfaceMode changed from <Mode_old> to <Mode_new> for interface <InterfaceName>. Message Type Severity INFO Probable Cause Indicates that the interface mode has been changed. Recommended No action is required. Action NSM-1011 Message OperationalEndpointMode changed from <Mode_old> to <Mode_new> for interface <InterfaceName>.
  • Page 659 NSM-1013 NSM-1013 Message VLAN classifier group <group_id> is deleted. Message Type Severity INFO Probable Cause Indicates that the specified VLAN classifier group has been deleted. Recommended No action is required. Action NSM-1014 Message VLAN classifier rule <rule_id> is created. Message Type Severity INFO Probable Cause...
  • Page 660 NSM-1017 Recommended No action is required. Action NSM-1017 Message Interface <InterfaceName> is <action> on interface <Logical_InterfaceName>. Message Type Severity INFO Probable Cause Indicates that the logical interface member list has been changed. Recommended No action is required. Action NSM-1018 Message <count>...
  • Page 661 NSM-1020 NSM-1020 Message Interface <InterfaceName> is administratively down. Message Type Severity INFO Probable Cause Indicates that the administrative status of the specified interface has changed to down. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 662 ONMD-1000 ONMD Messages ONMD-1000 Message LLDP is enabled. Message Type Severity INFO Probable Cause Indicates that the link layer discovery protocol (LLDP) is enabled globally. Recommended No action is required. Action ONMD-1001 Message LLDP is disabled. Message Type Severity INFO Probable Cause Indicates that the link layer discovery protocol (LLDP) is disabled globally.
  • Page 663 ONMD-1003 ONMD-1003 Message LLDP is enabled on interface <InterfaceName>. Message Type Severity INFO Probable Cause Indicates that the link layer discovery protocol (LLDP) is enabled on the specified interface. Recommended No action is required. Action ONMD-1004 Message LLDP is disabled on interface <InterfaceName>. Message Type Severity INFO...
  • Page 664 PDM-1001 PDM Messages PDM-1001 Message Failed to parse the pdm config. Message Type Severity WARNING Probable Cause Indicates that the Parity Data Manager (PDM) process could not parse the configuration file. This may be caused by a missing configuration file during the installation. Recommended Execute the firmwareDownload command to reinstall the firmware.
  • Page 665 PDM-1004 PDM-1004 Message PDM memory shortage. Message Type Severity WARNING 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, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 666 PDM-1007 PDM-1007 Message File not created: <file name>. errno=<errno>. Message Type Severity WARNING Probable Cause Indicates that the Parity Data Manager (PDM) process failed to create the specified file. Recommended Execute the firmwareDownload command to reinstall the firmware. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 667 PDM-1010 PDM-1010 Message File open failed: <file name>, errno=<errno>. Message Type Severity WARNING Probable Cause Indicates that the Parity Data Manager (PDM) process could not open the specified file. Recommended Execute the firmwareDownload command to reinstall the firmware. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 668 PDM-1013 PDM-1013 Message File empty: <File Name>. Message Type Severity WARNING Probable Cause Indicates that the switch configuration file /etc/fabos/fabos.[0|1].conf is empty. Recommended Execute the firmwareDownload command to reinstall the firmware. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 669 PDM-1019 PDM-1019 Message File path or trigger too long. Message Type Severity WARNING Probable Cause Indicates that one line of the pdm.conf file is too long. Recommended Execute the firmwareDownload command to reinstall the firmware. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 670 PDM-1022 PDM-1022 Message The switch is configured only with IPv6 addresses. Message Type Severity WARNING Probable Cause Indicates that the Parity Data Manager (PDM) cannot synchronize with its peer because the firmware does not support IPv6. Recommended Configure the local switch with IPv4 addresses. Action PDM-1023 Message...
  • Page 671 PDM-1025 PDM-1025 Message LDAP is configured with IPv6 addresses. Message Type Severity WARNING Probable Cause Indicates that the Parity Data Manager (PDM) cannot synchronize with its peer because the Lightweight Directory Access Protocol (LDAP) server is configured with IPv6 addresses. IPv6 is not supported by older firmware.
  • Page 672 PDTR-1001 PDTR Messages PDTR-1001 Message <informational message>. Message Type Severity INFO Probable Cause Indicates that information has been written to the panic dump files. The watchdog register codes are as follows: • 0x10000000 - The watchdog timer (WDT) forced a core reset. •...
  • Page 673 PLAT-1000 PLAT Messages PLAT-1000 Message <Function name> <Error string>. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that nonrecoverable peripheral component interconnect (PCI) errors have been detected. Recommended The system will be faulted and may automatically reboot. Action If the system does not reboot automatically, reboot the system manually using the reboot command.
  • Page 674 PLAT-1003 PLAT-1003 Message <Info message> Slot <Blade Slot number> C/BE: 0x<Captured Command/Byte-Enables data> ADBUS: 0x<Captured AD bus data> misc_intr 0x<Bridge reset interrupts>. Message Type LOG | FFDC Severity CRITICAL Probable Cause Indicates that peripheral component interconnect (PCI) bus hang was detected. Recommended Replace the field-replaceable unit (FRU).
  • Page 675 PMGR-1001 PMGR Messages PMGR-1001 Message Attempt to create switch <FID> succeeded. Message Type LOG | AUDIT Class Severity INFO Probable Cause Indicates that the switch with the specified fabric ID (FID) was successfully created. Recommended No action is required. Action PMGR-1002 Message Attempt to create switch <FID>...
  • Page 676 PMGR-1004 PMGR-1004 Message Attempt to delete switch <FID> failed. Error message: <Error Message>. Message Type Severity WARNING Probable Cause Indicates that the switch with the specified fabric ID (FID) was not deleted. Recommended Refer to the Error Message string displayed in the message for possible action. Action PMGR-1005 Message...
  • Page 677 PMGR-1008 Recommended No action is required. Action PMGR-1008 Message Attempt to change switch <FID> to switch <New FID> failed. Error message: <Error Message>. Message Type Severity WARNING Probable Cause Indicates a failed attempt to change the switch fabric ID (FID). Recommended Refer to the Error Message string displayed in the message for possible action.
  • Page 678 PMGR-1011 PMGR-1011 Message Attempt to move port(s) to switch <FID> succeeded. Message Type Severity INFO Probable Cause Indicates a successful attempt to move the ports to the specified switch. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 679 PORT-1003 PORT Messages PORT-1003 Message Port <port number> Faulted because of many Link Failures. Message Type Severity WARNING Probable Cause Indicates the specified port is now disabled because the link on this port had multiple failures that exceeded 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 680 PORT-1005 PORT-1005 Message Slot <slot number> port <port on slot> does not support configured L_Port. Issue portCfgLport to clear configuration. Message Type Severity WARNING Probable Cause Indicates the specified port is configured to be an L_Port, but the port does not support L_Port. If an L_Port is connected, then the port will be disabled because the port does not support L_Port.
  • Page 681 PORT-1008 PORT-1008 Message GigE Port (ID: <port number>) has been enabled. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates a Gigabit Ethernet port has been enabled. Recommended No action is required. Action PORT-1009 Message GigE Port (ID: <port number>) has been disabled. Message Type AUDIT | LOG Class...
  • Page 682 PS-1000 PS Messages PS-1000 Message Failed to initialize Advanced Performance Monitoring. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that an unexpected software error has occurred in Advanced Performance Monitoring. The Performance Monitor has failed to initialize. Recommended The control processor (CP) will reboot or failover automatically.
  • Page 683 PS-1003 PS-1003 Message Failed to set end-to-end monitoring mask on ISL ports. Message Type Severity WARNING Probable Cause Indicates that the restoring configuration has attempted to set the end-to-end monitoring mask on at least one inter-switch link (ISL) port. Recommended No action is required.
  • Page 684 PS-1006 PS-1006 Message Failed to add fabricmode toptalker monitors on domain=<domain id>, because end-to-end monitors are configured on this switch. Message Type Severity WARNING Probable Cause Indicates that end-to-end monitors are configured on the switch. Recommended Delete end-to-end monitors on the switch and re-install the fabric mode Top Talker monitor. End-to-end Action monitors and fabric mode Top Talker monitors are mutually exclusive.
  • Page 685 PS-1009 PS-1009 Message Failed to add the device updates in condb database. Message Type Severity WARNING Probable Cause Indicates that the fabric has more than the allowed number of devices. Recommended Reduce the number of devices configured in the fabric to be within the allowed limit. The maximum Action number of devices that can be configured in a fabric is 940.
  • Page 686 PSWP-1001 PSWP Messages PSWP-1001 Message PID for port <wwn name corresponding to source port> and port <wwn name corresponding to destination port> are swapped. New PID for port <wwn name corresponding to source port> is 0x<wwn name corresponding to destination port> and port <new area corresponding to source wwn>...
  • Page 687 PSWP-1004 PSWP-1004 Message Blade Swap complete for slots <slot number corresponding to the source blade> and <slot number corresponding to the destination blade>. Message Type Severity INFO Probable Cause Indicates the bladeSwap command has been issued. Recommended No action is required. Action PSWP-1005 Message...
  • Page 688 PSWP-1007 PSWP-1007 Message Blade Swap failed on fabosInit with error code <error code from fabosInit> in switch number <current switch number>. Message Type Severity WARNING Probable Cause Indicates the bladeSwap command failed on access to switch context. Recommended Retry the command. If the failure persists, contact your switch service provider. Action Fabric OS Message Reference 53-1002749-01...
  • Page 689 RAS-1001 RAS Messages RAS-1001 Message First failure data capture (FFDC) event occurred. Message Type Severity INFO Probable Cause Indicates that a first failure data capture (FFDC) event occurred and the failure data has been captured. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider.
  • Page 690 RAS-1005 RAS-1005 Message Software 'assert' error detected. Message Type LOG | FFDC Severity WARNING Probable Cause Indicates an internal software error. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider. RAS-1006 Message Support data file (<Uploaded file name>) automatically transferred to remote...
  • Page 691 RAS-2001 RAS-2001 Message Audit message log is enabled. Message Type LOG | AUDIT Class Severity INFO Probable Cause Indicates that the audit message log has been enabled. Recommended No action is required. Action RAS-2002 Message Audit message log is disabled. Message Type LOG | AUDIT Class...
  • Page 692 RAS-3001 RAS-3001 Message USB storage device plug-in detected. Message Type Severity INFO Probable Cause Indicates that the USB storage device plug-in has been detected. Recommended No action is required. Action RAS-3002 Message USB storage device enabled. Message Type Severity INFO Probable Cause Indicates that the USB storage device has been enabled.
  • Page 693 RAS-3005 Recommended No action is required. Action RAS-3005 Message CLI: <CLI command>. Message Type AUDIT Class Severity INFO Probable Cause Indicates that the specified command was executed on console. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 694 RCS-1001 RCS Messages RCS-1001 Message RCS has been disabled. Some switches in the fabric do not support this feature. Message Type Severity INFO Probable Cause Indicates that the reliable commit service (RCS) feature has been disabled on the local switch because not all switches in the fabric support RCS or the switch is in non-native mode.
  • Page 695 RCS-1004 RCS-1004 Message Application(<application name>) not registered.(<error string>). Message Type Severity ERROR Probable Cause Indicates that the specified application did not register with reliable commit service (RCS). Recommended Run the haShow command to view the HA state. Action Run the haDisable and haEnable commands. Run the rcsInfoShow command to view RCS capability on the fabric.
  • Page 696 RCS-1007 Recommended If the reject is in the ACA phase, wait for several minutes and then retry the operation. Action If the reject is in the SFC phase, check if the application license exists for the remote domain and if the application data is compatible.
  • Page 697 RCS-1010 RCS-1010 Message Domain <domain number> is RCS-incapable. Disabled <Number of E_ports disabled> E_Port(s) connected to this domain. Message Type Severity ERROR Probable Cause Indicates that the specified remote domain is RCS-incapable, or the RCS-capable information could not be retrieved for the specified remote domain due to some potential routing issues. Recommended Run the rcsInfoShow command to view RCS capability of the switch.
  • Page 698 RCS-1013 RCS-1013 Message Remote domain <domain number> is RCS incapable. Message Type LOG | FFDC Severity WARNING Probable Cause Indicates that the specified remote domain is RCS-incapable. Recommended Execute the supportSave command and contact your switch service provider. Action Fabric OS Message Reference 53-1002749-01...
  • Page 699 RKD-1001 RKD Messages RKD-1001 Message <Re-key type (First time encryption/Rekey/Write Metadata)> operation <Re-key action (started/completed/cancelled)>. Target: <Target physial WWN>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. SessionId:<Session ID>/<Session MN>. Message Type Severity INFO Probable Cause Indicates that a first-time encryption, re-key, or write metadata operation was started, completed, or canceled.
  • Page 700 RKD-1004 RKD-1004 Message Message: <Generic re-key message>. Message Type Severity INFO Probable Cause Indicates the generic re-key message. Recommended No action is required. Action RKD-1005 Message LUN with LSN: <LUN LSN> does no have metadata. Make note of key ID <Key ID for encrypt/decrypt>...
  • Page 701 RMON-1001 RMON Messages RMON-1001 Message RMON rising threshold alarm from SNMP OID <oid>. Message Type Severity INFO Probable Cause Indicates that the threshold level was exceeded for the sample type of the remote monitoring (RMON) alarm. Recommended Check the traffic on the interface using the show interface command. Action Note that you can use the show interface command to check the traffic on the interface, provided the statistics on the interface are not cleared using the clear counters command.
  • Page 702 RPCD-1001 RPCD Messages RPCD-1001 Message Authentication Error: client \"<IP address>\" has bad credentials: <bad user name and password pair>. Message Type Severity WARNING Probable Cause Indicates an authentication error was reported. The specified client IP address has faulty credentials. Recommended Enter the correct user name and password from the Fabric Access API host.
  • Page 703 RPCD-1004 RPCD-1004 Message Invalid certificate file. Secure RPCd is disabled. Message Type Severity WARNING Probable Cause Indicates the Secure Sockets Layer (SSL) certificate file has been corrupted. Recommended To enable remote procedure call daemon (RPCD) in secure mode, install a valid SSL certificate on the Action switch.
  • Page 704 RPCD-1007 Recommended Run the secCertUtil command to install a valid private key file. Action Fabric OS Message Reference 53-1002749-01...
  • Page 705 RTE-1001 RTE Messages RTE-1001 Message Detected route inconsistency. It may cause connectivity issues. If such issues arise, bounce all ISLs and ICLs on this chassis. Message Type Severity WARNING Probable Cause Indicates that the constraints that are used to determine the paths for Dynamic Path Selection (DPS) are not synchronized from active control processor (CP) to standby CP during the failover.
  • Page 706 RTWR-1001 RTWR Messages RTWR-1001 Message RTWR <routine: error message> 0x<detail 1>, 0x<detail 2>, 0x<detail 3>, 0x<detail 4>, 0x<detail 5>. Message Type Severity ERROR Probable Cause Indicates that an error occurred in Reliable Transport With Response (RTWR) due to one of the following reasons: •...
  • Page 707 RTWR-1003 RTWR-1003 Message <module name>: RTWR retry <number of times retried> to domain <domain ID>, iu_data <first word of iu_data>. Message Type Severity INFO Probable Cause Indicates the number of times Reliable Transport With Response (RTWR) has failed to get a response and retried.
  • Page 708 SCN-1001 SCN Messages SCN-1001 Message SCN queue overflow for process <daemon name>. Message Type FFDC | LOG Severity CRITICAL 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 is full. This may be caused by the daemon hanging or the system being busy.
  • Page 709 SCN-1002 SCN-1002 Message SCN queue overflow for process <daemon name>. Message Type FFDC | LOG Severity WARNING 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 is full. This may be caused by the daemon hanging or the system being busy.
  • Page 710 SEC-1001 SEC Messages SEC-1001 Message RCS process fails: <reason code>. Message Type Severity ERROR Probable Cause Indicates that the reliable commit service (RCS) process failed 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 711 SEC-1003 SEC-1003 Message Fail to download security data to domain <Domain number> after <Number of retires> retries. Message Type Severity WARNING Probable Cause Indicates 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 712 SEC-1007 SEC-1007 Message Security violation: Unauthorized host with IP address <IP address of the violating host> tries to establish API connection. Message Type Severity INFO Probable Cause Indicates a security violation was reported. The IP address of the unauthorized host is displayed in the message.
  • Page 713 SEC-1010 SEC-1010 Message RCS rejected: <Reason String>. Message Type Severity ERROR Probable Cause Trying to distribute the database from a non-primary switch. Recommended Resolve the specified error by executing the command only from the primary FCS. Action SEC-1016 Message Security violation: Unauthorized host with IP address <IP address of the violating host>...
  • Page 714 SEC-1024 SEC-1024 Message The <DB name> security database is too large to fit in flash. Message Type Severity INFO Probable Cause Indicates the size of the security database is too large for the flash memory. The size of the security database increases with the number of entries in each policy.
  • Page 715 SEC-1028 SEC-1028 Message No name is specified. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 716 SEC-1031 SEC-1031 Message Current security policy DB cannot be supported by standby. CPs will go out of sync. Message Type Severity WARNING Probable Cause Indicates the security database size is not supported by the standby control processor (CP). Recommended Reduce the security policy size by deleting entries within a policy or by deleting some policies. Action SEC-1032 Message...
  • Page 717 SEC-1034 SEC-1034 Message Invalid member <policy member>. Message Type Severity ERROR Probable Cause Indicates the input list has an invalid member. Recommended Verify the member names, and input the correct information. Action SEC-1035 Message Invalid device WWN <device WWN>. Message Type Severity ERROR Probable Cause...
  • Page 718 SEC-1038 Recommended Run the command again using the standard WWN format; 16 hexadecimal digits grouped as 8 Action colon-separated pairs, for example, 50:06:04:81:D6:F3:45:42. SEC-1038 Message Invalid domain <domain ID>. Message Type Severity ERROR Probable Cause Indicates an invalid domain ID was entered. Recommended Verify that the domain ID is correct.
  • Page 719 SEC-1041 SEC-1041 Message Invalid port member <port member> in portlist (<port list>). <Reason>. Message Type Severity ERROR Probable Cause Indicates the port member is invalid for one of the following reasons: • The value is not a number. • The value is too long. Valid numbers must be between one and three characters long. •...
  • Page 720 SEC-1044 SEC-1044 Message Duplicate member <member ID> in (<List>). Message Type Severity ERROR Probable Cause Indicates the specified member is a duplicate in the input list. The list can be a policy list or a switch member list. Recommended Do not specify any duplicates. Action SEC-1045 Message...
  • Page 721 SEC-1049 SEC-1049 Message Invalid switch name <switch name>. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 722 SEC-1052 SEC-1052 Message Invalid input. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 723 SEC-1055 SEC-1055 Message Invalid FCS list <WWN list>. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 724 SEC-1059 SEC-1059 Message Fail to <operation, e.g., save, delete, etc.,> <named item> to flash. Message Type Severity ERROR Probable Cause Indicates the operation failed when writing to flash memory. Recommended Run the supportFtp - e command to FTP files from the switch and remove them from the flash memory. Action SEC-1062 Message...
  • Page 725 SEC-1065 Recommended Run the secCertUtil show -fcapall command to verify that all PKI objects are valid. If PKI objects are not Action valid, generate the PKI objects and install the certificate by following the field upgrade process. SEC-1065 Message Invalid character in list. Message Type Severity ERROR...
  • Page 726 SEC-1072 SEC-1072 Message <Policy type> Policy List is Empty. Message Type Severity ERROR Probable Cause Indicates the specific policy type is empty. The security database is corrupted for unknown reasons. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider.
  • Page 727 SEC-1075 SEC-1075 Message Fail to <operation> new policy set on all switches. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 728 SEC-1078 SEC-1078 Message No new data to abort. Message Type Severity ERROR Probable Cause Indicates there are no new changes in the defined security policy database that can be aborted. Recommended Verify the security event was planned. Verify if there were really any changes to the defined policy Action database that can be aborted.
  • Page 729 SEC-1081 SEC-1081 Message Entered a name for a DCC policy ID that was not unique. Message Type Severity ERROR Probable Cause Indicates the Device Connection Control (DCC) policy name given in the secPolicyCreate command was the same as another DCC policy. Recommended Make sure that the DCC policy name has a unique alphanumeric string, and run the secPolicyCreate Action...
  • Page 730 SEC-1084 SEC-1084 Message Name exists for different type <Policy name>. Message Type Severity ERROR Probable Cause Indicates the specified policy already exists. Recommended No action is required. Action SEC-1085 Message Failed to create <policy name>. Message Type Severity ERROR Probable Cause Indicates the security policy was not created.
  • Page 731 SEC-1087 SEC-1087 Message The security database is larger than the data distribution limit of fabric <fabric data distribution limit> bytes. Message Type Severity ERROR Probable Cause Indicates the security database has more data than can be distributed to some of the switches in the fabric.
  • Page 732 SEC-1090 SEC-1090 Message SCC list contains FCS member. Please remove member from the FCS policy first. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 733 SEC-1093 SEC-1093 Message New FCS list must have at least one member in common with current FCS list. Message Type Severity ERROR Probable Cause Indicates the new fabric configuration server (FCS) list does not have a common member with the existing FCS list.
  • Page 734 SEC-1096 SEC-1096 Message Failed to delete <policy name> because <reason text>. Message Type Severity ERROR Probable Cause Indicates a policy cannot be removed because deleting it would result in an invalid security policy configuration. Recommended Verify the security policy configuration requirements and remove any policies that require the policy you Action want to be removed first.
  • Page 735 SEC-1099 SEC-1099 Message Please enable your switch before running secModeEnable. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 736 SEC-1102 SEC-1102 Message Fail to download <security data>. Message Type Severity ERROR Probable Cause Indicates the switch failed to download a certificate, security database, or policies. This can happen when the switch does not get enough resources to complete the operation, the fabric has not stabilized, or the policy database is an invalid format.
  • Page 737 SEC-1106 SEC-1106 Message Failed to sign message data. Message Type Severity ERROR Probable Cause Indicates that some public key infrastructure (PKI) objects on the switch are not in a valid state, and a signature operation failed. Recommended Run the secCertUtil show -fcapall command and verify that all PKI objects exist on the switch. If a Action failure to validate PKI objects occurs, follow the steps for re-creating PKI objects outlined in the Fabric OS Administrator's Guide.
  • Page 738 SEC-1110 SEC-1110 Message FCS list must be the first entry in the [Defined Security policies] section. Fail to download defined database. Message Type Severity ERROR Probable Cause Indicates that a security policy download was attempted with a defined policy that does not have the fabric configuration server (FCS) policy as the first policy.
  • Page 739 SEC-1113 SEC-1113 Message <Key> [ <Feature> license ] going to expire in <Expiry_days> day(s). Message Type LOG | AUDIT Class SECURITY Severity WARNING Probable Cause Indicates the license period will expire soon. Recommended Get a new license for this feature. Action SEC-1114 Message...
  • Page 740 SEC-1116 SEC-1116 Message Fail to commit failover. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 741 SEC-1119 SEC-1119 Message Secure mode has been enabled. Message Type Severity INFO Probable Cause Indicates the secure Fabric OS was enabled by the secModeEnable command. Recommended Verify the security event was planned. If the security event was planned, there is no action required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 742 SEC-1123 SEC-1123 Message Security database downloaded by Primary FCS. Message Type Severity INFO Probable Cause Indicates the security database was successfully downloaded from the primary fabric configuration server (FCS). Recommended No action is required. Action SEC-1124 Message Secure Mode is off. Message Type Severity INFO...
  • Page 743 SEC-1135 Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. SEC-1135 Message Secure fabric version stamp has been reset. Message Type Severity INFO...
  • Page 744 SEC-1138 SEC-1138 Message Security database download received from Primary FCS. Message Type Severity INFO Probable Cause Indicates that a non-primary fabric configuration server (FCS) switch received a security database download. Recommended Verify that the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 745 SEC-1145 SEC-1145 Message A security admin event has occurred. This message is for information purpose only. The message for individual event is: <Event specific data>. Message Type Severity INFO Probable Cause Indicates one of the following has occurred: • The names for the specified policies have changed. •...
  • Page 746 SEC-1154 SEC-1154 Message PID change failed: <Reason> <defined status> <active status>. Message Type Severity INFO Probable Cause Indicates that either the defined or the active policy could not be updated. If the policy database is very large, it might not be able to change the index/area because the new policy database exceeds the maximum size.
  • Page 747 SEC-1157 SEC-1157 Message PID Change failed: <Reason> <defined status> <active status>. Message Type Severity INFO Probable Cause Indicates the provisioning resources for a security policy failed because of low memory or internal error. The status values can be defined, active, or both. A negative value means that a policy set was failed by the daemon.
  • Page 748 SEC-1160 SEC-1160 Message Duplicate port <port ID> in port list (<port list>). Message Type Severity INFO Probable Cause Indicates a duplicate port member exists in the specified port list. Recommended Verify that there is no duplicate port member in the port list. Action SEC-1163 Message...
  • Page 749 SEC-1166 Recommended Wait a few minutes and try the command again. Action SEC-1166 Message Non FCS tries to commit failover. Message Type Severity ERROR Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 750 SEC-1170 SEC-1170 Message This command must be executed on the Primary FCS switch, the first reachable switch in the FCS list. Message Type Severity INFO Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 751 SEC-1173 SEC-1173 Message Lost contact with Primary FCS switch. Message Type Severity ERROR Probable Cause Indicates the switch has lost contact with the primary fabric configuration server (FCS) switch in the secure fabric. This could result from the primary FCS being disabled. Recommended If the primary FCS was disabled intentionally, no action is required;...
  • Page 752 SEC-1176 SEC-1176 Message Failed to generate new version stamp. Message Type Severity ERROR Probable Cause Indicates the primary fabric configuration server (FCS) failed to generate a new version stamp because the fabric was not stable. Recommended Verify all switches in the fabric are in time synchronization with the primary FCS and that no external Action entity is trying to access the fabric.
  • Page 753 SEC-1183 Recommended No action is required. Action SEC-1183 Message Policy to binary conversion error: Port <port number> is out range. Message Type Severity ERROR Probable Cause Indicates a security database conversion has failed because of an invalid value. Recommended Retry the command with a valid value. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 754 SEC-1186 SEC-1186 Message <Security server (RADIUS/LDAP/TACACS+)> <action> Configuration. Message Type Severity INFO Probable Cause Indicates the RADIUS, LDAP, or TACACS+ configuration was enabled or disabled as the primary authentication, accounting, and authorization (AAA) mechanism. Recommended No action is required. Action SEC-1187 Message Security violation: Unauthorized switch <switch WWN>...
  • Page 755 SEC-1189 SEC-1189 Message Security violation: Unauthorized host with IP address <IP address> tries to do SNMP write operation. Message Type Severity INFO Probable Cause Indicates an SNMP security violation was reported. The specified unauthorized host attempted to perform a write SNMP operation. Recommended Check the WSNMP policy and verify which hosts are allowed access to the fabric through SNMP.
  • Page 756 SEC-1192 SEC-1192 Message Security violation: Login failure attempt via <connection method>. Message Type Severity INFO Probable Cause Indicates a serial or modem login security violation was reported. The wrong password was used while trying to log in through a serial or modem connection; the login failed. Recommended Use the correct password.
  • Page 757 SEC-1195 SEC-1195 Message This switch has no <component> license. Message Type Severity WARNING Probable Cause Indicates a corruption occurred during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, and then local validation finds the error in the security database.
  • Page 758 SEC-1198 SEC-1198 Message Security violation: Unauthorized host with IP address <IP address> tries to establish API connection. Message Type Severity INFO Probable Cause Indicates an API security violation was reported. The specified unauthorized host attempted to establish an API connection. Recommended Check to see if the host IP address specified in the message can be used to manage the fabric through Action...
  • Page 759 SEC-1201 SEC-1201 Message Security violation: MS device <device WWN> operates on non-primary FCS switch. Message Type Severity INFO Probable Cause Indicates a management server (MS) operation security violation was reported. An MS device operation occurred on a non-primary fabric configuration server (FCS) switch. Recommended Check the management server policy and verify the connection is allowed.
  • Page 760 SEC-1250 SEC-1250 Message DCC enforcement API failed: <failed action> err=<status>, key=<data> Message Type Severity WARNING Probable Cause Indicates an internal error caused the Device Connection Control (DCC) policy enforcement to fail. Recommended Retry the failed security command. 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 761 SEC-1300 SEC-1300 Message This switch is in VcEncode mode. Security is not supported. Message Type Severity INFO Probable Cause Indicates the switch is set up with VC-encoded mode. Recommended Turn off VC-encoded mode before enabling security. Action SEC-1301 Message This switch is in interop mode. Security is not supported. Message Type Severity INFO...
  • Page 762 SEC-1303 SEC-1303 Message This software version does not support security. Message Type Severity INFO Probable Cause Indicates the currently installed software version does not support the Brocade Secure Fabric OS feature. Recommended Run the firmwareDownload command to update the firmware to the latest version for your specific Action switch.
  • Page 763 SEC-1306 SEC-1306 Message Failed to verify certificate with root CA. Message Type Severity INFO Probable Cause Indicates the certificate could not be verified with root certificate authority (CA). This could happen if an unauthorized switch tries to access the fabric that is not certified by a trusted root CA or a root CA certificate does not exist on the switch.
  • Page 764 SEC-1309 SEC-1309 Message Waiting for RCS transaction to complete: <Wait time in seconds> secs Message Type Severity INFO Probable Cause Indicates that Fabric OS is still waiting for the reliable commit service (RCS) transaction to complete. Recommended Verify if there are any reliable commit service (RCS) or Reliable Transport With Response (RTWR) Action errors.
  • Page 765 SEC-1312 SEC-1312 Message <MESG Message>. Message Type Severity INFO Probable Cause Indicates the password configuration parameters changed. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. SEC-1313 Message The passwdcfg parameters were set to default values.
  • Page 766 SEC-1315 SEC-1315 Message <Name of command> command failed -<List of databases rejecting distribution> db(s) configured for rejection on this switch. Message Type Severity ERROR Probable Cause Indicates there was an attempt to distribute databases to a switch that was configured not to accept distributions from the fabric.
  • Page 767 SEC-1318 SEC-1318 Message Transaction rejected due to inconsistent fabric. Message Type Severity INFO Probable Cause Indicates that some domains detected an inconsistent fabric. Recommended Resolve the policy conflict, if there is one, and then wait for the fabric to stabilize. Retry the distribution. Action SEC-1319 Message...
  • Page 768 SEC-1321 SEC-1321 Message Failed secure mode enable command. Reason: <Reason>. Message Type Severity ERROR Probable Cause Indicates the security enable failed on the fabric because the switch has a conflicting configuration such as fabric-wide consistency configuration or AD configuration. Recommended Verify the security event was planned.
  • Page 769 SEC-1324 SEC-1324 Message Fabric transaction failure. RCS error: <Error code>. Message Type Severity INFO Probable Cause Indicates the reliable commit service (RCS) transaction failed with the specified reason code. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy.
  • Page 770 SEC-1327 SEC-1327 Message Strict <Policy Name> policy WWN List is conflicting with domain <Domain Number>. Message Type Severity WARNING Probable Cause Indicates the policy is conflicting with the domain. Recommended No action is required. The domain is denied by disallowing all its E_Ports connected to the fabric. If the Action domain should be allowed to merge with the fabric, then resolve the issue by making the conflicting policies the same.
  • Page 771 SEC-1330 SEC-1330 Message <Name of command> command failed -<List of databases rejecting distribution> db(s) are coming from a non-Primary switch. Message Type Severity ERROR Probable Cause Indicates an attempt was made to distribute databases either from a backup fabric configuration server (FCS) switch or a non-FCS switch.
  • Page 772 SEC-1333 SEC-1333 Message <Name of command> command failed. There are VF enabled switch(s) in fabric. <List of databases rejecting distribution> db(s) distribution is blocked. Message Type Severity ERROR Probable Cause Indicates there was an attempt to distribute PWD or IPFILTER databases from the fabric to a switch that is VF-enabled Recommended Disable VF on all the switches that have VF-enabled if PWD or IPFILTER databases need to be...
  • Page 773 SEC-1336 SEC-1336 Message <Policy Name> policy is conflicting with domain <Domain Number>. Message Type Severity WARNING Probable Cause Indicates the newly added switches to the fabric, as specified by domain number, have a conflicting policy with the local switch. Recommended Check the conflicting policy and make the new switches and the local switch policies the same.
  • Page 774 SEC-1339 SEC-1339 Message Distribute command failed. There are Inflight encryption enabled switch(s) in fabric. Auth db(s) distribution is blocked Message Type Severity ERROR Probable Cause Indicates there was an attempt to distribute AUTH databases with switch policy (Off/Passive) from the fabric to a switch that has Inflight Encryption enabled Recommended Disable or enable Inflight encryption in all the switches in the fabric...
  • Page 775 SEC-3003 Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. SEC-3003 Message Event: <Event Name>, Status: success, Info: Created <Policy Name> policy, with member(s) <Member List>...
  • Page 776 SEC-3006 Recommended Verify the addition of members to the policy was planned. If the addition of members was planned, no Action action is required. If the addition of members was not planned, take appropriate action as defined by your enterprise security policy. SEC-3006 Message Event: <Event Name>, Status: success, Info: Removed member(s) <Members removed>...
  • Page 777 SEC-3009 Recommended Verify the modification was planned. If the modification was planned, no action is required. If the Action modification was not planned, take appropriate action as defined by your enterprise security policy. SEC-3009 Message Event: <Event Name>, Status: success, Info: Security Transaction aborted. Message Type AUDIT Class...
  • Page 778 SEC-3012 Recommended Verify the security statistics were intentionally reset. If the security statistics were intentionally reset, no Action action is required. If the security statistics were not intentionally reset, take appropriate action as defined by your enterprise security policy. SEC-3012 Message Event: <Event Name>, Status: success, Info: Temp Passwd <Password Set or Reset>...
  • Page 779 SEC-3015 Recommended Verify the RADIUS configuration was changed intentionally. If the RADIUS configuration was changed Action intentionally, no action is required. If the RADIUS configuration was not changed intentionally, take appropriate action as defined by your enterprise security policy. SEC-3015 Message Event: <Event Name>, Status: success, Info: Moved <Event option>...
  • Page 780 SEC-3018 Recommended Verify the RADIUS/LDAP/TACACS+ configuration was intentionally changed. If the Action RADIUS/LDAP/TACACS+ configuration was intentionally changed, no action is required. If the RADIUS/LDAP/TACACS+ configuration was not intentionally changed, take appropriate action as defined by your enterprise security policy. SEC-3018 Message Event: <Event Name>, Status: success, Info: Parameter [<Parameter Name>] changed from [<Old Value>] to [<New Value>].
  • Page 781 SEC-3020 SEC-3020 Message Event: <Event Name>, Status: success, Info: Successful login attempt via <connection method and IP Address>. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates a successful login occurred. An IP address is displayed when the login occurs over a remote connection.
  • Page 782 SEC-3023 SEC-3023 Message Event: <Event Name>, Status: failed, Info: Account [<User>] locked, failed password attempts exceeded. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates that failed password attempts exceeded the allowed limit; the account has been locked. Recommended The account may automatically unlock after the lockout duration has expired or an administrator may Action manually unlock the account.
  • Page 783 SEC-3026 SEC-3026 Message Event: <Event Name>, Status: success, Info: User account [<User Name>], role changed from [<Old Role Type>] to [<New Role Type>]. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates a user account role was changed. Recommended Verify the security event was planned.
  • Page 784 SEC-3029 SEC-3029 Message Event: <Event Name>, Status: success, Info: Backup user account \"<User Account Name>\" recovered. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates that backup user accounts were recovered. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 785 SEC-3032 SEC-3032 Message Event: <Event Name>, Status: success, Info: Switch is configured to <accept or reject> <Database name> database. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates the specified event has occurred to accept or reject a certain database. Recommended Verify the event was planned.
  • Page 786 SEC-3035 SEC-3035 Message Event: ipfilter, Status: success, Info: <IP Filter Policy> ipfilter policy(ies) saved. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates the specified IP filter policies has been saved. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 787 SEC-3038 SEC-3038 Message Event: ipfilter, Status: failed, Info: Failed to activate <IP Filter Policy> ipfilter policy. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates the specified IP filter policy failed to activate. Recommended Verify the security event was planned. If the event was planned, no action is required. If the security Action event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 788 SEC-3045 SEC-3045 Message Zeroization has been executed on the system. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates the system has been zeroized. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 789 SEC-3048 SEC-3048 Message FIPS mode has been enabled in the system using force option. Message Type AUDIT Class SECURITY Severity INFO Probable Cause Indicates the system has been forced to Federal Information Processing Standards (FIPS) mode. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
  • Page 790 SEC-3051 SEC-3051 Message The license key <Key> is <Action>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that a license key is added or removed. Recommended No action is required. Action SEC-3061 Message Role '<Role Name>' is created. Message Type AUDIT | LOG Class...
  • Page 791 SEC-3063 SEC-3063 Message Role '<Role Name>' is copied from '<Source Role>'. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates that the specified role name has been copied from the source role. Recommended No action is required. Action SEC-3064 Message...
  • Page 792 SEC-3066 SEC-3066 Message Configuration of user-defined roles is downloaded. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates the configuration of user-defined roles has been downloaded. Recommended No action is required. Action SEC-3067 Message Invalid Cipher list <Cipher List>. Message Type AUDIT | LOG Class...
  • Page 793 SFLO-1001 SFLO Messages SFLO-1001 Message sFlow is <state> globally. Message Type Severity INFO Probable Cause Indicates that sFlow is globally enabled or disabled. Recommended No action is required. Action SFLO-1002 Message sFlow is <state> for port <name>. Message Type Severity INFO Probable Cause Indicates that sFlow is enabled or disabled on the specified port.
  • Page 794 SFLO-1004 SFLO-1004 Message Global sFlow polling interval is changed to <polling_intvl>. Message Type Severity INFO Probable Cause Indicates that the global counter sampling interval has been changed to the specified value. Recommended No action is required. Action SFLO-1005 Message sFlow sampling rate on port <name> is changed to <sample_rate>. Message Type Severity INFO...
  • Page 795 SFLO-1008 Recommended No action is required. Action SFLO-1008 Message All the sFlow collectors are unconfigured. Message Type Severity INFO Probable Cause Indicates that none of the sFlow collectors are configured. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 796 SNMP-1001 SNMP Messages SNMP-1001 Message SNMP service is not available <Reason>. Message Type Severity ERROR Probable Cause Indicates that the Simple Network Management Protocol (SNMP) service could not be started because of the specified reason. Therefore, 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 797 SNMP-1004 SNMP-1004 Message Incorrect SNMP configuration. Message Type AUDIT | FFDC | LOG Class Severity ERROR Probable Cause Indicates that the SNMP configuration is incorrect and therefore the SNMP service will not work correctly. Recommended Change the SNMP configuration to the default using the snmpConfig --default command. Action SNMP-1005 Message...
  • Page 798 SNMP-1009 SNMP-1009 Message Port traps are <blocked state> on port <port>. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates the blocked or unblocked status of the port traps on the specified port. Recommended Execute the snmpTraps --show command to view the current status of the port. Action Fabric OS Message Reference 53-1002749-01...
  • Page 799 SPC-1001 SPC Messages SPC-1001 Message S<slot number containing Encryption Engine>, Cryptographic operation enabled. Message Type Severity INFO Probable Cause Indicates that the cryptographic operation is enabled on an encryption engine. Recommended No action is required. Action SPC-1002 Message S<slot number containing Encryption Engine>, Cryptographic operation disabled. Message Type Severity INFO...
  • Page 800 SPC-2001 SPC-2001 Message S<slot number containing Encryption Engine>, <module name>: Crypto error asserted by Vader/OB1 0x<Reason>. Message Type Severity ERROR Probable Cause Indicates that Crypto error is asserted by the Field-Programmable Gate Array (FPGA). Recommended No action is required. Action SPC-2002 Message S<slot number containing Encryption Engine>, <module name>: Tamper Event: Crypto...
  • Page 801 SPC-2004 SPC-2004 Message S<slot number containing Encryption Engine>, <module name>: FPGA firmware download failed: 0x<Reason>. Message Type Severity ERROR Probable Cause Indicates that FPGA download has failed. Recommended No action is required. Action SPC-2005 Message S<slot number containing Encryption Engine>, <module name>: FPGA firmware download success.
  • Page 802 SPC-2007 SPC-2007 Message S<slot number containing Encryption Engine>, <module name>: Crypto post tests success: 0x<Reason>. Message Type Severity INFO Probable Cause Indicates that Crypto Power-On Self-Test (POST) has passed successfully. Recommended No action is required. Action SPC-2008 Message S<slot number containing Encryption Engine>, <module name>: Vader/OB1 recovered from error.
  • Page 803 SPC-2010 SPC-2010 Message S<slot number containing Encryption Engine>, <module name>: Crypto subsystem cover is open. Message Type Severity CRITICAL Probable Cause Indicates that the Crypto subsystem cover is open. Recommended Close the Crypto subsystem cover properly. Action SPC-2011 Message S<slot number containing Encryption Engine>, <module name>: OB1 crypto BIST success.
  • Page 804 SPC-2013 SPC-2013 Message S<slot number containing Encryption Engine>, <module name>: Oscillator Failure Detected. Message Type Severity WARNING Probable Cause Indicates hardware failure. Recommended The shelf life of the system may be reduced. Contact the vendor for further instructions. Action SPC-2014 Message S<slot number containing Encryption Engine>, <module name>: Low Battery Level Detected.
  • Page 805 SPC-2041 SPC-2041 Message S<slot number containing Encryption Engine>, <module name>: Alloc freemsg block failed. Message Type Severity ERROR Probable Cause Indicates an allocation failure for the pool of SB message. Recommended No action is required. Action SPC-2042 Message S<slot number containing Encryption Engine>, <module name>: Alloc msg - no free sbmsgs.
  • Page 806 SPC-2044 SPC-2044 Message S<slot number containing Encryption Engine>, <module name>: Read - device not open <Device minor number>. Message Type Severity WARNING Probable Cause Indicates that the SPD device is not opened. Recommended No action is required. Action SPC-3001 Message S<slot number containing Encryption Engine>, <module name>: No input KEK for DEK inject, DEK: <DEK octet 1>...
  • Page 807 SPC-3003 SPC-3003 Message S<slot number containing Encryption Engine>, <module name>: No output KEK for DEK rewrap, DEK: <DEK octet 1> <DEK octet 2> <DEK octet 3> <DEK octet 4>, KEK: <KEK octet 1> <KEK octet 2> <KEK octet 3> <KEK octet 4>. Message Type Severity ERROR...
  • Page 808 SPC-3006 SPC-3006 Message S<slot number containing Encryption Engine>, <module name>: DEK rewrap error: <SP status code>, DEK: <DEK octet 1 or other info> <DEK octet 2> <DEK octet 3> <DEK octet 4>. Message Type Severity ERROR Probable Cause Indicates data encryption key (DEK) rewrap error. The SP status code variable specifies the cause of the error: •...
  • Page 809 SPC-3008 SPC-3008 Message S<slot number containing Encryption Engine>, <module name>: SP crypto got READY notification. Message Type Severity INFO Probable Cause Indicates that the key application (KPD) within the CryptoModule of the encryption engine has been started. Recommended No action is required. Action SPC-3009 Message...
  • Page 810 SPC-3011 SPC-3011 Message S<slot number containing Encryption Engine>, <module name>: Persistent data storage error: <SP status code>, KEK: <KEK octet 1> <KEK octet 2> <KEK octet 3> <KEK octet 4>. Message Type Severity ERROR Probable Cause Indicates that an attempt to store CryptoModule internal data using the Secret Encryption Key failed; most likely, the encryption engine has been zeroized or tampered with.
  • Page 811 SPC-3014 SPC-3014 Message S<slot number containing Encryption Engine>, <module name>: RNG compare failure: successive values match. Message Type Severity ERROR Probable Cause Indicates that the CryptoModule internal random number generator has failed. Recommended Contact your switch service provider for assistance. Action SPC-3015 Message...
  • Page 812 SPM-1001 SPM Messages SPM-1001 Message Init fails: <Reason>. Message Type Severity ERROR Probable Cause Indicates that the security processor management (SPM) failed to initialize. Recommended Check the system resources and restart the switch. Action SPM-1002 Message Generic SPM Warning: <Reason>. Message Type Severity WARNING...
  • Page 813 SPM-1004 SPM-1004 Message Initialize Node. Message Type Severity INFO Probable Cause Indicates a node initialization. Recommended No action is required. Action SPM-1005 Message Set EE Control slot <slot> action <action>. Message Type Severity INFO Probable Cause Indicates specified control action is taken on encryption engine in specified slot. Recommended No action is required.
  • Page 814 SPM-1008 Recommended No action is required. Action SPM-1008 Message Dergistered SP Certificate in slot <slot>. Message Type Severity INFO Probable Cause Indicates an security processor (SP) certificate de-registration. Recommended No action is required. Action SPM-1009 Message <cert> Certificate is missing. Message Type Severity ERROR...
  • Page 815 SPM-1011 SPM-1011 Message Group Cfg Changed Quorum Size <qc_size>. Message Type Severity INFO Probable Cause Indicates that a group configuration has changed the quorum size. Recommended No action is required. Action SPM-1012 Message Authentication Context: <established>. Message Type Severity INFO Probable Cause Indicates an authentication context.
  • Page 816 SPM-1014 SPM-1014 Message Warning: Configdownload may change key vault configuration and result in EE going to Operational; Need Valid KEK state. Message Type Severity WARNING Probable Cause Indicates the master keys downloaded will not be effective unless imported because the encryption engine may have different master key configured.
  • Page 817 SPM-3001 SPM-3001 Message Event: cryptocfg Status: success, Info: Node [<wwnstr>] initialized. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates a node was initialized. Recommended No action is required. Action SPM-3002 Message Event: cryptocfg Status: success, Info: EE in slot <slot> initialized. Message Type AUDIT | LOG Class...
  • Page 818 SPM-3004 SPM-3004 Message Event: cryptocfg Status: success, Info: EE in slot <slot> enabled. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates an encryption engine was enabled. Recommended No action is required. Action SPM-3005 Message Event: cryptocfg Status: success, Info: EE in slot <slot> disabled. Message Type AUDIT | LOG Class...
  • Page 819 SPM-3007 SPM-3007 Message Event: cryptocfg Status: success, Info: File imported via scp: <hostUsername>[<hostIP>]:<hostPath>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates a file was imported through SCP protocol Recommended No action is required. Action SPM-3008 Message Event: cryptocfg Status: success, Info: DH challenge generated for vault IP <vaultIP>.
  • Page 820 SPM-3010 SPM-3010 Message Event: cryptocfg Status: success, Info: EE in slot <slot> zeroized. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates an encryption engine was zeroized. Recommended No action is required. Action SPM-3011 Message Event: cryptocfg Status: success, Info: Local file \"<filename>\" deleted. Message Type AUDIT | LOG Class...
  • Page 821 SPM-3013 SPM-3013 Message Event: cryptocfg Status: success, Info: Key vault with certificate label \"<certLabel>\" deregistered. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates a key vault was deregistered. Recommended No action is required. Action SPM-3014 Message Event: cryptocfg Status: success, Info: Key archive client registered with certificate file \"<certFilename>\".
  • Page 822 SPM-3016 SPM-3016 Message Event: cryptocfg Status: success, Info: Master key generated. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates a master key was generated Recommended No action is required. Action SPM-3017 Message Event: cryptocfg Status: success, Info: Master key exported. Message Type AUDIT | LOG Class...
  • Page 823 SPM-3019 SPM-3019 Message Event: cryptocfg Status: success, Info: System card registered. Certificate label: \"<certLabel>\" Certificate file: \"<certFilename>\". Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates a system card was registered. Recommended No action is required. Action SPM-3020 Message Event: cryptocfg Status: success, Info: System card with certificate label...
  • Page 824 SPM-3022 SPM-3022 Message Event: cryptocfg Status: success, Info: Authentication card with certificate label \"<certLabel>\" deregistered. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates an authentication card was deregistered. Recommended No action is required. Action SPM-3023 Message Event: cryptocfg Status: success, Info: System card <enabledOrDisabled>.
  • Page 825 SPM-3025 SPM-3025 Message Event: cryptocfg Status: success, Info: File imported via USB: Source: <sourcePath> Destination: <destinationFilename>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates a file was imported through a USB device. Recommended No action is required. Action SPM-3026 Message...
  • Page 826 SPM-3028 SPM-3028 Message Event: SPM-EE state changed, Info: EE State: <EE Status>. Message Type AUDIT | LOG Class SECURITY Severity INFO Probable Cause Indicates an encryption engine state has changed. Recommended No action is required. Action SPM-3029 Message Event: KeyVault Connection Status: <status>, Info: KAC_Connect: <kac status>. Message Type AUDIT | LOG Class...
  • Page 827 SS-1000 SS Messages SS-1000 Message supportSave has uploaded support information to the host with IP address <host ip>. Message Type Severity INFO Probable Cause Indicates that the supportSave command was used to transfer support information to a remote location. Recommended No action is required.
  • Page 828 SS-1003 SS-1003 Message supportSave's operation to USB storage device aborted. Message Type Severity WARNING 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 because of possible errors in subcommands being executed by the supportSave command.
  • Page 829 SS-1006 SS-1006 Message supportsave not collected for slot <Slot Number>. Reason: blade was not available to accept a supportsave request. Message Type Severity WARNING Probable Cause Indicates that the supportsave request was not sent to the blade in the specified slot. Recommended Restart the switch using the reboot command and then execute the supportSave command.
  • Page 830 SS-1009 SS-1009 Message <slot number and its node name(BP/DP)> supportsave failed. Reason:No ISC connection for <slot number and its node name(BP/DP)>. Message Type Severity WARNING Probable Cause Indicates that there is no Inter-Subsystem Communication (ISC) connection for the specified node slot. Recommended Restart the switch using the reboot command and then execute the supportSave command.
  • Page 831 SS-1012 SS-1012 Message BP supportsave failed. The /mnt of Active CP does not have enough disk space to collect BP supportsave files. Message Type Severity INFO Probable Cause Indicates that a chassis with the blade processor (BP) does not have enough disk space in the secondary partition of the active CP to save the supportsave files, before uploading them to the remote host.
  • Page 832 SSMD-1001 SSMD Messages SSMD-1001 Message Failed to allocate memory: (<function name>). Message Type Severity ERROR Probable Cause Indicates that the specified function has failed to allocate memory. Recommended Check the memory usage on the switch using the memShow command. Action Restart or power cycle the switch.
  • Page 833 SSMD-1004 SSMD-1004 Message Failed to unlock semaphore mutex: (<function name>). Message Type Severity ERROR Probable Cause Indicates that the specified function failed to unlock the mutex (semaphore). Recommended Restart or power cycle the switch. Action SSMD-1005 Message SSM start up failed. Message Type Severity ERROR...
  • Page 834 SSMD-1007 SSMD-1007 Message Error while removing ACL <ACL name> from interface <Interface name>. Message Type Severity ERROR Probable Cause Indicates that an error occurred while programming a TCAM entry on the specified interface. Recommended Try again after some time. If the problem persists, execute the supportSave command and then restart Action or power cycle the switch.
  • Page 835 SSMD-1201 SSMD-1201 Message QoS failed programming ASIC <ASIC slot number>/<ASIC chip number> Multicast Tail Drop. Message Type Severity WARNING Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the Multicast Tail Drop feature. Recommended Delete and reapply the QoS Multicast Tail Drop policy using the qos rcv-queue multicast threshold Action...
  • Page 836 SSMD-1204 SSMD-1204 Message QoS failed initializing ASIC <ASIC slot number>/<ASIC chip number>. Message Type Severity WARNING Probable Cause Indicates that DCE SSM encountered an unexpected error in initializing the dataplane ASIC QoS infrastructure. Recommended Restart or power cycle the switch. Action SSMD-1205 Message...
  • Page 837 SSMD-1207 SSMD-1207 Message QoS failed programming interface 0x<Interface ID> Default CoS. Message Type Severity WARNING Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the interface Default CoS feature. Recommended Delete and reapply the QoS interface Default CoS policy using the qos cos command. Action If the problem persists, restart or power cycle the switch.
  • Page 838 SSMD-1210 SSMD-1210 Message QoS failed programming interface 0x<Interface ID> CoS to Traffic Class map. Message Type Severity WARNING Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the CoS to Traffic Class mapping feature. Recommended Delete and reapply the QoS interface CoS to Traffic Class policy using the qos cos-traffic-class Action...
  • Page 839 SSMD-1213 SSMD-1213 Message QoS failed programming interface 0x<Interface ID> CoS Tail Drop Threshold. Message Type Severity WARNING Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the interface CoS Tail Drop Threshold feature. Recommended Delete and reapply the QoS CoS Tail Drop Threshold policy using the qos rcv-queue command.
  • Page 840 SSMD-1216 SSMD-1216 Message QoS failed programming interface 0x<Interface ID> Pause. Message Type Severity WARNING Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the interface Pause feature. Recommended Delete and reapply the QoS Pause policy. Action If the message persists, restart or power cycle the switch.
  • Page 841 SSMD-1301 SSMD-1301 Message CEE Map <ceemap> is deleted. Message Type Severity INFO Probable Cause Indicates that the specified CEE Map has been deleted. Recommended No action is required. Action SSMD-1302 Message CEE Map <ceemap> priority table <pg_ids> are <action>. Message Type Severity INFO Probable Cause...
  • Page 842 SSMD-1305 Recommended No action is required. Action SSMD-1305 Message CEE Map <ceemap> priority group <pg_id> weight is changed from <PGID_weight_new> to <PGID_weight_old>. Message Type Severity INFO Probable Cause Indicates that the specified priority group weight has been changed. Recommended No action is required. Action SSMD-1306 Message...
  • Page 843 SSMD-1308 SSMD-1308 Message <acl_type> access list <acl_name> is deleted. Message Type Severity INFO Probable Cause Indicates that the specified access list has been deleted. Recommended No action is required. Action SSMD-1309 Message <acl_type> access list <acl_name> rule sequence number <rule_sq_no> is <action>. Message Type Severity INFO...
  • Page 844 SSMD-1312 Recommended No action is required. Action SSMD-1312 Message <map_type> <map_name> assigned to interface <InterfaceName>. Message Type Severity INFO Probable Cause Indicates that the specified user profile map has been assigned to the interface. Recommended No action is required. Action SSMD-1313 Message <map_type>...
  • Page 845 SSMD-1315 SSMD-1315 Message CEE Map <ceemap> is incompatible with current firmware. Resetting it to default. Message Type Severity INFO Probable Cause Indicates that the specified CEE Map is incompatible with the current firmware and therefore it is reset to the default. Recommended No action is required.
  • Page 846 SSMD-1318 SSMD-1318 Message ACL <acl_name> is being removed from interface <InterfaceName>. This operation could take a long time. Message Type Severity INFO Probable Cause Indicates that the specified access list is being removed from the interface. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 847 SULB-1001 SULB Messages SULB-1001 Message Firmwaredownload command has started. Message Type AUDIT | LOG Class FIRMWARE Severity WARNING 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 848 SULB-1004 Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action SULB-1004 Message Firmwarecommit has completed. Message Type AUDIT | LOG Class FIRMWARE Severity INFO Probable Cause Indicates that the firmwareCommit command has completed successfully. Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action SULB-1005 Message...
  • Page 849 SULB-1007 SULB-1007 Message Standby CP reboots. Message Type Severity INFO Probable Cause Indicates that the standby control processor (CP) is rebooting with new firmware. Recommended No action is required. The firmwareDownload command is progressing as expected. Action Run the firmwareDownloadStatus command for more information. SULB-1008 Message Standby CP booted successfully with new firmware.
  • Page 850 SULB-1009 TABLE 7 Status messages and status codes (Continued) Status message Status code "Sanity check failed because HAMD is disabled on active CP." 0x34 "Sanity check failed because firmware download process is already in progress." 0x35 "Sanity check failed because Fabric OS is disabled on standby CP." 0x36 "Sanity check failed because HAMD is disabled on standby CP."...
  • Page 851 SULB-1009 TABLE 7 Status messages and status codes (Continued) Status message Status code "Standby CP failed to boot up." 0x6f "Standby CP booted up with new firmware." 0x70 "Standby CP failed to boot up with new firmware." 0x71 "Firmware download has completed successfully on standby CP." 0x72 "Firmware download has started on standby CP.
  • Page 852 SULB-1009 TABLE 7 Status messages and status codes (Continued) Status message Status code "Remote CP is restoring its secondary partition." 0x8e "Firmware download has started." 0x8f "Firmware commit has started." 0x90 "Firmware download has completed successfully." 0x91 "Firmware commit has completed successfully." 0x92 "Firmware commit has started to restore the secondary partition."...
  • Page 853 SULB-1009 TABLE 8 Error messages and error codes (Continued) Error message Error code "Out of memory." 0x14 "Failed to download RPM package." 0x15 "Unable to create firmware version file." 0x16 "Unexpected system error." 0x17 "Error in getting lock device for firmware download." 0x18 "Error in releasing lock device for firmware download."...
  • Page 854 SULB-1009 The following descriptions explain the causes of some common error messages: • 0x15 - "Failed to download RPM package." If this error occurs immediately after firmware download is started, the firmware on the switch may be two releases older than the requested firmware.
  • Page 855 SULB-1010 TABLE 9 Upgrade state and code value (Continued) Upgrade state Code SUS_ACT_FWC_BEGIN 0x2f SUS_PEER_RESTORE_BEGIN 0x30 SUS_SBY_RESTORE_BEGIN 0x31 SUS_PEER_FWC_BEGIN 0x32 SUS_PEER_FS_CHECK1 0x33 SUS_FINISH 0x34 SUS_COMMIT 0x35 Recommended Run the firmwareDownloadStatus command for more information. Action In a modular switch, when the firmwareDownload command fails, the command will synchronize the firmware on the two partitions of each CP by starting a firmware commit operation.
  • Page 856 SULB-1017 Recommended Run the firmwareDownloadStatus command for more information. Action Refer to the Fabric OS Troubleshooting Guide for troubleshooting information. SULB-1017 Message Firmwaredownload failed in slot <Slot number>. Message Type AUDIT | LOG Class FIRMWARE Severity ERROR Probable Cause Indicates that the firmwareDownload command failed on the specified blade. The error may be caused by the inconsistent application processor (AP) blade firmware stored on the active CP.
  • Page 857 SULB-1020 SULB-1020 Message New firmware failed to boot in slot <Slot number>. Message Type AUDIT | LOG Class FIRMWARE Severity ERROR Probable Cause Indicates that the BP blade is still running the old image even though it should reboot with the new image. This error may indicate that the new image has not been loaded correctly to the specified blade.
  • Page 858 SULB-1023 SULB-1023 Message The blade in slot <Slot number> has rebooted during firmwaredownload. Message Type AUDIT | LOG Class FIRMWARE Severity WARNING Probable Cause Indicates that there may be an error caused by an unexpected disruption of the firmwareDownload command; for example, powering off and on of the indicated BP blade in the middle of a firmware download.
  • Page 859 SULB-1026 Recommended Wait for the blade to reboot. Action SULB-1026 Message Firmware commit operation started on the blade in slot <Slot number>. Message Type AUDIT | LOG Class FIRMWARE Severity WARNING Probable Cause Indicates that the firmwareCommit command has started on the specified blade. The operation may be a normal part of firmware download, or it may have started to repair the secondary partition of the blade if the secondary partition is corrupted.
  • Page 860 SULB-1032 Recommended Wait for the operation to complete. Action SULB-1032 Message Relocating an internal firmware image on the CP. Message Type AUDIT | LOG Class FIRMWARE Severity WARNING Probable Cause Indicates that the switch has started firmware download to the co-CPU. Recommended Wait for the operation to complete.
  • Page 861 SULB-1035 SULB-1035 Message An error has occurred during relocation of the internal image. Message Type AUDIT | LOG Class FIRMWARE Severity ERROR Probable Cause Indicates that an error has occurred during the relocation of the internal image. The error may be caused by inconsistent internal firmware image.
  • Page 862 SULB-1038 SULB-1038 Message Co-CPU has not booted up properly. Skip the firmwaredownload command on the co-CPU. Message Type AUDIT | LOG Class FIRMWARE Severity WARNING Probable Cause Indicates that the main CPU cannot access the co-CPU to update the firmware on the co-CPU or run any other firmware download command on the co-CPU.
  • Page 863 SULB-1041 SULB-1041 Message Firmware has been activated successfully on standby CP. Message Type AUDIT | LOG Class FIRMWARE Severity INFO Probable Cause Indicates that the firmwareActivate command has completed successfully on the standby control processor (CP). Recommended No action is required. The firmwareActivate command has completed on the standby CP as expected. Action Run the firmwareShow command to verify the firmware versions.
  • Page 864 SULB-1044 SULB-1044 Message Firmwaredownload to secondary partition has completed successfully. Message Type Severity INFO Probable Cause Indicates that the firmwareDownload command to the secondary partition has completed successfully and the switch will come up with the updated firmware on reboot. Recommended No action is required.
  • Page 865 SWCH-1001 SWCH Messages SWCH-1001 Message Switch is not in ready state - Switch enable failed, switch status= 0x<switch status>, c_flags = 0x<switch control flags>. Message Type Severity ERROR Probable Cause Indicates that the switch is enabled before it is ready. Recommended If the message persists, execute the supportFtp command (as needed) to set up automatic FTP Action...
  • Page 866 SWCH-1004 SWCH-1004 Message Blade attach failed during recovery, disabling slot = <slot number>. Message Type Severity ERROR Probable Cause Indicates that the specified blade has failed during failover or recovery. Recommended For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade. Action For a non-bladed switch, reboot or power cycle the switch.
  • Page 867 SWCH-1007 SWCH-1007 Message Switch port <port number> disabled due to \"<disable reason>\". Message Type Severity WARNING Probable Cause Indicates that the switch port is disabled due to the reason displayed in the message. Recommended Based on the disable reason displayed, take appropriate action to restore the port. Action If the disable reason is "Insufficient frame buffers", reduce the distance or speed settings for the port to reduce the buffer requirement of the link.
  • Page 868 SWCH-1010 SWCH-1010 Message Trunk Area (TA) enabled on slot <slot number> with switch not in PID format 1. TA enabled ports will be persistently disabled. Message Type Severity WARNING Probable Cause Indicates that the blade is enabled with the port configuration that had Trunk Area enabled previously. Recommended Disable Trunk Area on ports that had Trunk Area enabled previously.
  • Page 869 SWCH-1013 SWCH-1013 Message Trunk Area has been disabled for one or more ports. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that a Trunk Area assignment has been disabled for one or more ports and the configuration file has been updated.
  • Page 870 SWCH-1016 SWCH-1016 Message Device <wwn name of device> FDISC to port <port number>. Static persistent PID set and area requested not assigned to the device. Reject FDISC. Message Type Severity INFO Probable Cause Indicates that the static persistent port ID (PID) is set and the area requested is not assigned to the device.
  • Page 871 SWCH-1019 SWCH-1019 Message Device <wwn name of device> tries to FLOGI, reject FLOGI as persistent PID is set on device and port <port number> has user area <area> bound to it. Message Type Severity INFO Probable Cause Indicates a WWN-PID and port address binding collision. Recommended The persistent PID is set on the device and the requested area cannot be assigned because the port it is Action...
  • Page 872 SWCH-1022 SWCH-1022 Message Port:<port number> has been disabled due to port address conflict while enabling FMS mode. Message Type Severity WARNING Probable Cause Indicates that the switch has ports with FICON Management Server (FMS) reserved areas (0xFE, 0xFF) that are not supported in FMS mode. Recommended No action required.
  • Page 873 SWCH-1025 SWCH-1025 Message This Logical Switch has ports other than 16 Gbps-capable FC ports. Edge Hold Time for these ports is unchanged and is <Edge Hold Time>. Message Type Severity WARNING Probable Cause Indicates that the edge hold time for the non 16 Gbps-capable FC ports is not the same as 16 Gbps-capable FC ports in the logical switch.
  • Page 874 SYSC-1001 SYSC Messages SYSC-1001 Message Failed to run <Name of program that could not be run (string)>:<System internal error message (string)>. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates that one of the programs would not run on the system during the boot sequence. Recommended If the message is reported during a reboot after new firmware has been loaded, try reloading the Action...
  • Page 875 SYSC-1005 SYSC-1005 Message Daemon <Daemon name to restart> is not restarted (Reason: <Restart failure reason>). Message Type Severity WARNING Probable Cause Indicates that a terminated daemon is not restarted, either because a restart limit is reached or a restart action fails. Recommended Execute the supportSave command to gather troubleshooting data.
  • Page 876 SYSM-1001 SYSM Messages SYSM-1001 Message No memory. Message Type FFDC | LOG Severity CRITICAL Probable Cause Indicates 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 the supportFtp command (as needed) to set up automatic FTP transfers;...
  • Page 877 SYSM-1004 SYSM-1004 Message Failed to retrieve current chassis configuration option, ret=<Unknown>. Message Type Severity ERROR Probable Cause Indicates there was a failure to read configuration data from the World Wide Name (WWN) card. Recommended Verify that the WWN card is present and operational and the affected control processor (CP) is properly Action seated in its slot.
  • Page 878 SYSM-1007 SYSM-1007 Message PERMITTING USE OF INCOMPATIBLE CHASSIS FOR CP IN SLOT <Slot number>. DATA ERRORS MAY RESULT. Message Type Severity WARNING Probable Cause Indicates an override of the incompatible control processor (CP) or chassis check. This message is for engineering use only.
  • Page 879 TAPE-1001 TAPE Messages TAPE-1001 Message Key acquisition for <Pool or Container> <Begins or Complete>. Message Type Severity INFO Probable Cause Indicates that the key acquisition for the pool or the container has begun or is complete. Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 880 TRCE-1001 TRCE Messages TRCE-1001 Message Trace dump available<slot on which the trace dump occurs>! (reason: <cause of trace dump: PANIC DUMP, WATCHDOG EXPIRED, MANUAL, TRIGGER>). Message Type Severity WARNING Probable Cause Indicates that trace dump files have been generated on the switch or the specified slot. The cause for the dump can be one of the following: •...
  • Page 881 TRCE-1004 Recommended If the message persists, execute the supportFtp command (as needed) to set up automatic FTP Action transfers; then execute the supportSave command and contact your switch service provider. TRCE-1004 Message Trace dump<slot on which the trace dump occurs> was not transferred because trace auto-FTP disabled.
  • Page 882 TRCE-1007 TRCE-1007 Message Notification of this CP has failed. Parameters temporarily out of synch with other Message Type Severity INFO Probable Cause Indicates that the active control processor (CP) is unable to alert the standby CP of a change in trace status.
  • Page 883 TRCE-1010 TRCE-1010 Message Traced fails to start. Message Type Severity ERROR Probable Cause Indicates that the trace daemon (traced), which is used for transferring trace files has failed to start. The trace capability within the switch is unaffected. The system automatically restarts the traced facility after a brief delay.
  • Page 884 TRCE-1013 TRCE-1013 Message Trace dump <slot on which the trace dump occurs> was not transferred as FIPS mode is enabled. Message Type Severity WARNING Probable Cause Indicates that a trace dump has occurred on the switch or the specified slot, but the trace dump files were not automatically transferred from the switch because FIPS mode is enabled on the switch.
  • Page 885 TRCK-1001 TRCK Messages TRCK-1001 Message Successful login by user <User>. Message Type Severity INFO Probable Cause Indicates the track change feature recorded a successful login. Recommended No action is required. Action TRCK-1002 Message Unsuccessful login by user <User> after <login_fail_cnt> overall login failure attempts.
  • Page 886 TRCK-1004 TRCK-1004 Message Config file change from task:<task> Message Type Severity INFO Probable Cause Indicates 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 configuration download.
  • Page 887 TS-1001 TS Messages TS-1001 Message NTP Query failed: <error code>. Message Type Severity WARNING 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 888 TS-1006 TS-1006 Message <message>. Message Type Severity INFO Probable Cause Indicates that a time service event is occurring or has failed. The message can be one of the following: • Init failed. Time Service exiting - Initialization error, but the time server exits. •...
  • Page 889 TS-1008 Recommended No action is required. Action Fabric OS Message Reference 53-1002749-01...
  • Page 890 UCST-1003 UCST Messages UCST-1003 Message Duplicate Path to Domain <domain ID>, Output Port = <port number>, PDB pointer = 0x<value>. Message Type Severity INFO Probable Cause Indicates that duplicate paths were reported to the specified domain from the specified output port. The PDB pointer value displayed in the message is the address of the path database and provides debugging information.
  • Page 891 UCST-1021 UCST-1021 Message In-order delivery option has been enabled. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that in-order delivery (IOD) option has been enabled on the switch. This option guarantees in-order delivery of frames during fabric topology changes. Recommended No action is required.
  • Page 892 UCST-1024 UCST-1024 Message Dynamic Load Sharing option has been disabled. Message Type AUDIT | LOG Class Severity INFO Probable Cause Indicates that Dynamic Load Sharing (DLS) option has been disabled on the switch. Recommended No action is required. Action UCST-1026 Message LossLess-DLS option has been enabled.
  • Page 893 UPTH-1001 UPTH Messages UPTH-1001 Message No minimum cost path in candidate list. Message Type Severity WARNING Probable Cause Indicates that the switch is unreachable because no minimum cost path (MPATH) exists in the candidate list (domain ID list). Recommended No action is required. This error will end the current shortest path first (SPF) computation. Action UPTH-1002 Message...
  • Page 894 VDR-2001 VDR Messages VDR-2001 Message <message>. Message Type Severity WARNING Probable Cause Indicates that the Field-Programmable Gate Array (FPGA) parity error threshold exceeded. Recommended Power cycle the switch. Action Fabric OS Message Reference 53-1002749-01...
  • Page 895 VS-1001 VS Messages VS-1001 Message No virtual PWWN assignment for the device <Login device PWWN>, port <Switch port> or (AG <AG NWWN> port <AG port>). Message Type Severity INFO Probable Cause Indicates that the device with the virtual Port World Wide Name (PWWN) feature enabled tried to log in but there is no mapping for the device, port, or Access Gateway (AG) port.
  • Page 896 VS-1004 VS-1004 Message Could not find Virtual PWWN config file for the switch. Message Type Severity INFO Probable Cause Indicates that the virtual Port World Wide Name (PWWN) feature has been enabled for the first time on the switch or the configuration file was corrupted or accidently removed. Recommended Creating a new default configuration file.
  • Page 897 VS-1007 VS-1007 Message FSS Registration failed for virtualization services. Message Type Severity INFO Probable Cause Indicates failure in the virtualization service daemon (vsd) startup because vsd has failed to register with Fabric OS State Synchronization (FSS). Recommended No action is required. Action VS-1008 Message...
  • Page 898 WEBD-1001 WEBD Messages WEBD-1001 Message Missing or Invalid Certificate file -- HTTPS is configured but could not be started. Message Type Severity WARNING Probable Cause Indicates the Secure Sockets Layer (SSL) certificate file is either invalid or absent. Recommended Install a valid certificate file. Action WEBD-1002 Message...
  • Page 899 WEBD-1005 WEBD-1005 Message HTTP server and weblinker process will be restarted for logfile truncation. Message Type Severity WARNING Probable Cause Indicates the size of the Hypertext Transfer Protocol (HTTP) log file exceeded the maximum limit. Recommended No action is required. Action WEBD-1006 Message...
  • Page 900 WEBD-1008 WEBD-1008 Message HTTP server and weblinker process cannot be started. Message Type LOG | FFDC Severity WARNING Probable Cause Indicates a rare error condition in which the built-in recovery process has failed to restore Hypertext Transfer Protocol (HTTP) services. The problem often results from invalid configuration of Secure Sockets Layer (SSL) certificates, but there can be more than one reason for such a failure.
  • Page 901 XTUN-1000 XTUN Messages XTUN-1000 Message FCIP Tunnel <VE Port (Tunnel) Number> Missed Data frame:I/T/L:<FC Initiator ID>/<FC Target ID>/<FCP Logical Unit Number>. Message Type Severity ERROR Probable Cause Indicates a missed frame with one or more Fibre Channel Protocol (FCP) data information units during a SCSI write or read operation.
  • Page 902 XTUN-1003 XTUN-1003 Message FCIP Tunnel <VE Port (Tunnel) Number> Message Transmission failed:I/T/L/E:<FC Initiator ID>/<FC Target ID>/<FCP Logical Unit Number>/<Error return value>. Message Type Severity ERROR Probable Cause Indicates a message transmission failure. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer support Action for assistance.
  • Page 903 XTUN-1006 XTUN-1006 Message FCIP FC frame drop due to transmit timeout on slot=<FX8-24 Slot number (or 0 if 7800)> DP=<FX8-24 DP number (or 0 if 7800)> BLS=<Blaster Image Number (0 or 1)> DR=<FC Descriptor Ring Number> Frames Dropped=<Number of FC frames that were dropped>.
  • Page 904 XTUN-1997 XTUN-1997 Message FTRACE buffer <FTRACE Trace Buffer Number> on slot <FX8-24 Slot Number> dp <FX8-24 DP Number> has been triggered. Message Type Severity WARNING Probable Cause Indicates that a programmed trigger event has been detected. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer support Action for assistance.
  • Page 905 XTUN-2000 XTUN-2000 Message FCIP Tunnel <VE Port (Tunnel) Number> UP. Message Type Severity INFO Probable Cause Indicates that the specified Fibre Channel over IP (FCIP) tunnel is up. Recommended No action is required. Action XTUN-2001 Message FCIP Tunnel <VE Port (Tunnel) Number> DOWN (<Reason>). Message Type Severity ERROR...
  • Page 906 XTUN-2004 Recommended If the tunnel or circuit has not been administratively disabled or deleted, a possible network error or Action disruption has occurred. XTUN-2004 Message FCIP Tunnel <VE Port (Tunnel) Number> <Priority Class>-Pri QoS UP. Message Type Severity INFO Probable Cause Indicates that the specified quality of service (QoS) for this tunnel is up.
  • Page 907 XTUN-2007 XTUN-2007 Message FCIP Tunnel <VE Port (Tunnel) Number> Circuit <Circuit Number> CREATED (<Originator>). Message Type Severity INFO Probable Cause Indicates that the specified circuit has been successfully created. Recommended No action is required. Action XTUN-2008 Message IKEv2: <Reason>. Message Type Severity INFO Probable Cause...
  • Page 908 XTUN-2011 Recommended No action is required. Action XTUN-2011 Message FIPS: <Reason>. Message Type Severity INFO Probable Cause Indicates that the status of the module FIPS compliance has changed. Recommended No action is required. Action XTUN-2020 Message FCIP Tunnel <VE Port (Tunnel) Number> DELETED (<Originator>). Message Type Severity INFO...
  • Page 909 XTUN-2022 XTUN-2022 Message FCIP Tunnel <VE Port (Tunnel) Number> MODIFIED (<Originator>). Message Type Severity INFO Probable Cause Indicates that the specified Fibre Channel over IP (FCIP) tunnel has been administratively modified. Recommended No action is required. Action XTUN-2023 Message FCIP Tunnel <VE Port (Tunnel) Number> MODATTR (<Attribute change description>). Message Type Severity INFO...
  • Page 910 XTUN-2025 XTUN-2025 Message FCIP Tunnel <VE Port (Tunnel) Number> Circuit <Circuit Number> MODATTR (<Attribute change description>). Message Type Severity INFO Probable Cause Indicates that the attribute is modified. In most cases, the attribute value is modified within the specified circuit. Recommended No action is required.
  • Page 911 ZEUS-1001 ZEUS Messages ZEUS-1001 Message Port <port number> port fault. Change the SFP or check cable. Message Type Severity ERROR Probable Cause Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver pair, or a faulty cable between the peer ports. Recommended Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not Action...
  • Page 912 ZEUS-1004 ZEUS-1004 Message S<slot number>,C<chip index>: Invalid DMA ch pointer, chan:<Channel number>, good_addr:0x<Good address> bad_addr:0x<Bad address>. Message Type Severity ERROR Probable Cause Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade the data traffic. Recommended Reboot the system at the next maintenance window.
  • Page 913 ZEUS-1016 ZEUS-1016 Message Port is faulted due to port re-initialization failure on internal Port S<slot number>,P<port number>(<blade port number>) with reason <port fault reason>. Message Type Severity WARNING Probable Cause Indicates that the specified port failed due to port re-initialization failure. Recommended When this error is observed persistently, power cycle the specified blade using the slotPowerOff and Action...
  • Page 914 ZONE-1002 ZONE Messages ZONE-1002 Message WWN zoneTypeCheck or zoneGroupCheck warning(<warning string>) at port(<port number>). Message Type Severity WARNING Probable Cause Indicates that a zone filter or zone group check failure occurred. The frame filter logic reported a failure when creating or adding the zone groups during port login (PLOGI) trap processing. This message usually indicates problems when adding the content-addressable memory (CAM) entries before the filter setup.
  • Page 915 ZONE-1007 Recommended No action is required. Action ZONE-1007 Message Ioctl (<function>) in (<error message>) at port (<port number>) returns code (<error string>) and reason string (<reason string>). Message Type Severity INFO Probable Cause Indicates that frame filter logic reported a failure during the specified I/O Control (IOCTL) call. This is usually a programming error when adding CAM entries before the filter setup.
  • Page 916 ZONE-1015 ZONE-1015 Message Not owner of the current transaction <transaction ID>. Message Type Severity WARNING Probable Cause Indicates that a zoning change operation is not allowed because the zoning transaction is opened by another task. Indicates concurrent modification of the zone database by multiple administrators. Recommended Wait until the previous transaction is completed.
  • Page 917 ZONE-1022 ZONE-1022 Message The effective configuration has changed to <Effective configuration name>. <AD Id>. Message Type Severity INFO Probable Cause Indicates that the effective zone configuration has changed to the specified zone name. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy.
  • Page 918 ZONE-1026 ZONE-1026 Message port <port number> Out of CAM entries. Message Type Severity INFO Probable Cause Indicates that the total number of entries of S_ID CAM is above the limit while creating or adding a zone group. The maximum number of CAM entries allowed depends on the application-specific integrated circuit (ASIC).
  • Page 919 ZONE-1028 ZONE-1028 Message Commit zone DB larger than supported - <zone db size> greater than <max zone db size>. Message Type Severity WARNING 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 920 ZONE-1036 ZONE-1036 Message Unable to create <config file name>: error message <System Error Message>. Message Type Severity ERROR Probable Cause Indicates that the Fabric OS cannot create 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 921 ZONE-1039 ZONE-1039 Message Unable to read contents of <config file name>: error message <System Error Message>. Message Type Severity ERROR Probable Cause Indicates that the Fabric OS cannot read 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 922 ZONE-1042 ZONE-1042 Message The effective configuration has been disabled. <AD Id>. Message Type Severity INFO Probable Cause Indicates that the effective zone configuration has been disabled. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy.
  • Page 923 ZONE-1046 Recommended No action is required. Action ZONE-1046 Message The Default Zone access mode is already set to All Access. Message Type Severity INFO Probable Cause Indicates that the Default Zone access mode is already set to All Access. Recommended No action is required.
  • Page 924 ZONE-1054 ZONE-1054 Message Default Zone All Access mode is set with Frame Redirection zones. Message Type Severity WARNING Probable Cause Indicates that the Default Zone All Access mode will not grant all access behavior when the frame redirection zones are defined. Recommended Remove frame redirection zones or set the Default Zone access mode to No Access using the defzone Action...
  • Page 925 ZONE-1059 ZONE-1059 Message Unexpected TI routing behavior or a potentially unroutable TI configuration has been detected on local domain <Domain ID of the local Logical Switch where the error was detected>. Message Type Severity WARNING Probable Cause Indicates that the current fabric topology and TI zone configuration may result in an unroutable condition or an unexpected routing behavior.
  • Page 926 ZONE-1062 ZONE-1062 Message Defined and Effective zone configurations are inconsistent. Message Type Severity WARNING Probable Cause Indicates that the defined and effective configurations are different. Recommended Execute the cfgEnable command to make both the configurations consistent. Action ZONE-3001 Message Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object member list>\"...
  • Page 927 ZONE-3003 ZONE-3003 Message Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object name>\" deleted. Message Type AUDIT Class ZONE Severity INFO Probable Cause Indicates that the specified zone object has been deleted. The zone object type variable can be an alias, zone member, zone, or zone configuration. Recommended Verify that the event was planned.
  • Page 928 ZONE-3006 Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. ZONE-3006 Message Event: <Event Name>, Status: success, Info: Current zone configuration disabled. <AD Id>.
  • Page 929 ZONE-3009 Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. ZONE-3009 Message Event: <Event Name>, Status: success, Info: <Event Description>. Message Type AUDIT Class...
  • Page 930 ZONE-3012 ZONE-3012 Message Event: <Event Name>, Status: success, Info: Zone object \"<Zone object name>\" renamed to \"<New Zone object name>\". Message Type AUDIT Class ZONE Severity INFO Probable Cause Indicates that the specified zone object has been renamed. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy.
  • Page 931 ZONE-3015 ZONE-3015 Message Event: <Event Name>, Status: success, Info: AD configurations applied. Message Type AUDIT Class FABRIC Severity INFO Probable Cause Indicates that the saved Admin Domain (AD) configurations are enforced. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy.
  • Page 932 ZONE-3018 ZONE-3018 Message Event: <Event Name>, Status: success, Info:<AD object type> <AD object name> has been deactivated. Message Type AUDIT Class FABRIC Severity INFO 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 not Action planned, take appropriate action as defined by your enterprise security policy.
  • Page 933 ZONE-3021 ZONE-3021 Message Event: <Event Name>, Status: success, Info: AD object \"<AD object name>\" renamed to \"<New AD object name>\". Message Type AUDIT Class FABRIC Severity INFO Probable Cause Indicates that the specified Admin Domain (AD) has been renamed. Recommended Verify that the event was planned.
  • Page 934 ZONE-3024 ZONE-3024 Message Command: <Command Name>, Status: success, Info: executed. <AD Id>. Message Type AUDIT Class FABRIC Severity INFO Probable Cause Indicates that the ad --transabort command has completed successfully in the specified Admin Domain (AD). Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy.

This manual is also suitable for:

Fabric os v7.1.0

Table of Contents