Repository navigation
Expand file tree
/
Copy pathnetapp-tutorial16.html
More file actions
1035 lines (927 loc) · 66.6 KB
/
Copy pathnetapp-tutorial16.html
File metadata and controls
1035 lines (927 loc) · 66.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
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
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Brocade SAN Switch — Management, CLI Operations & Troubleshooting</title>
<script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
<style>
@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;600&family=Sora:wght@300;400;600;700;800&family=Inter:wght@300;400;500;600&display=swap');
:root {
--bg-primary:#0d1117;--bg-secondary:#161b22;--bg-card:#1c2333;
--accent-blue:#58a6ff;--accent-green:#3fb950;--accent-orange:#f78166;
--accent-purple:#bc8cff;--accent-yellow:#e3b341;--accent-teal:#39d3c3;
--text-primary:#e6edf3;--text-secondary:#8b949e;--text-muted:#6e7681;
--border:#30363d;--border-bright:#484f58;--sidebar-width:290px;
}
*{margin:0;padding:0;box-sizing:border-box}html{scroll-behavior:smooth}
body{font-family:'Inter',sans-serif;background:var(--bg-primary);color:var(--text-primary);display:flex;min-height:100vh}
#reading-progress{position:fixed;top:0;left:var(--sidebar-width);right:0;height:3px;background:linear-gradient(90deg,var(--accent-teal),var(--accent-blue),var(--accent-purple));transform-origin:left;transform:scaleX(0);z-index:999;transition:transform .1s linear}
.sidebar{width:var(--sidebar-width);background:var(--bg-secondary);border-right:1px solid var(--border);position:fixed;top:0;left:0;height:100vh;overflow-y:auto;z-index:100;display:flex;flex-direction:column}
.sidebar-header{padding:20px 16px;border-bottom:1px solid var(--border);background:var(--bg-secondary);position:sticky;top:0;z-index:10}
.sidebar-logo{display:flex;align-items:center;gap:10px;margin-bottom:4px}
.sidebar-logo .logo-icon{width:32px;height:32px;background:linear-gradient(135deg,var(--accent-teal),var(--accent-blue));border-radius:8px;display:flex;align-items:center;justify-content:center;font-size:16px}
.sidebar-logo span{font-family:'Sora',sans-serif;font-weight:700;font-size:14px;color:var(--text-primary);letter-spacing:.5px}
.sidebar-subtitle{font-size:11px;color:var(--text-muted);padding-left:42px}
.toc-nav{padding:12px 0;flex:1}
.toc-section-label{font-size:10px;font-weight:600;text-transform:uppercase;letter-spacing:1.2px;color:var(--text-muted);padding:12px 16px 6px}
.toc-link{display:flex;align-items:center;gap:8px;padding:7px 16px;font-size:12.5px;color:var(--text-secondary);text-decoration:none;transition:all .2s ease;border-left:2px solid transparent;line-height:1.4}
.toc-link:hover{background:var(--bg-card);color:var(--text-primary);border-left-color:var(--accent-teal)}
.toc-link.active{background:rgba(57,211,195,.1);color:var(--accent-teal);border-left-color:var(--accent-teal);font-weight:500}
.toc-link .toc-num{font-size:10px;font-weight:700;color:var(--text-muted);min-width:18px;font-family:'JetBrains Mono',monospace}
.toc-link.sub{padding-left:32px;font-size:12px}
.series-nav{padding:12px 16px;border-top:1px solid var(--border)}
.series-nav-title{font-size:10px;font-weight:600;text-transform:uppercase;letter-spacing:1px;color:var(--text-muted);margin-bottom:8px}
.series-link{display:block;padding:5px 8px;font-size:11.5px;color:var(--text-secondary);text-decoration:none;border-radius:5px;transition:all .2s;margin-bottom:2px}
.series-link:hover{background:var(--bg-card);color:var(--accent-teal)}
.series-link.current{color:var(--accent-teal);font-weight:600}
.main-content{margin-left:var(--sidebar-width);flex:1;max-width:calc(100vw - var(--sidebar-width))}
.top-header{background:linear-gradient(135deg,#0d1117 0%,#0d1a1f 50%,#0d1117 100%);border-bottom:1px solid var(--border);padding:60px 60px 50px;position:relative;overflow:hidden}
.top-header::before{content:'';position:absolute;inset:0;background:radial-gradient(ellipse at 70% 50%,rgba(57,211,195,.07) 0%,transparent 60%),radial-gradient(ellipse at 20% 80%,rgba(88,166,255,.06) 0%,transparent 50%)}
.header-badge{display:inline-flex;align-items:center;gap:6px;background:rgba(57,211,195,.12);border:1px solid rgba(57,211,195,.3);border-radius:20px;padding:4px 14px;font-size:12px;color:var(--accent-teal);font-weight:500;margin-bottom:18px;font-family:'JetBrains Mono',monospace}
.main-title{font-family:'Sora',sans-serif;font-size:36px;font-weight:800;line-height:1.15;margin-bottom:16px;background:linear-gradient(135deg,#e6edf3 20%,#39d3c3 55%,#58a6ff 100%);-webkit-background-clip:text;-webkit-text-fill-color:transparent;background-clip:text;position:relative}
.header-desc{font-size:15px;color:var(--text-secondary);line-height:1.7;max-width:700px;position:relative}
.header-meta{display:flex;gap:24px;flex-wrap:wrap;margin-top:20px;position:relative}
.meta-chip{display:flex;align-items:center;gap:6px;font-size:12.5px;color:var(--text-secondary)}
.meta-chip .dot{width:8px;height:8px;border-radius:50%}
.prog-chips{display:flex;gap:8px;flex-wrap:wrap;margin-top:18px;position:relative}
.prog-chip{background:rgba(255,255,255,.04);border:1px solid var(--border);border-radius:6px;padding:3px 10px;font-size:11px;color:var(--text-muted);font-family:'JetBrains Mono',monospace}
.content-area{padding:40px 60px 80px;max-width:1020px}
.section{margin-bottom:64px;scroll-margin-top:30px}
.section-header{display:flex;align-items:flex-start;gap:16px;margin-bottom:24px;padding-bottom:16px;border-bottom:1px solid var(--border)}
.section-icon{width:44px;height:44px;border-radius:10px;display:flex;align-items:center;justify-content:center;font-size:20px;flex-shrink:0;margin-top:2px}
.icon-teal{background:rgba(57,211,195,.15);border:1px solid rgba(57,211,195,.3)}
.icon-blue{background:rgba(88,166,255,.15);border:1px solid rgba(88,166,255,.3)}
.icon-green{background:rgba(63,185,80,.15);border:1px solid rgba(63,185,80,.3)}
.icon-orange{background:rgba(247,129,102,.15);border:1px solid rgba(247,129,102,.3)}
.icon-purple{background:rgba(188,140,255,.15);border:1px solid rgba(188,140,255,.3)}
.icon-yellow{background:rgba(227,179,65,.15);border:1px solid rgba(227,179,65,.3)}
.section-title-wrap h2{font-family:'Sora',sans-serif;font-size:24px;font-weight:700;color:var(--text-primary);line-height:1.2}
.section-title-wrap .section-num{font-size:11px;font-family:'JetBrains Mono',monospace;color:var(--text-muted);font-weight:400;margin-bottom:4px}
.card{background:var(--bg-card);border:1px solid var(--border);border-radius:12px;padding:24px;margin-bottom:20px;transition:border-color .2s}
.card:hover{border-color:var(--border-bright)}
.card-title{font-family:'Sora',sans-serif;font-weight:600;font-size:15px;color:var(--text-primary);margin-bottom:12px;display:flex;align-items:center;gap:8px}
p{font-size:14.5px;line-height:1.8;color:var(--text-secondary);margin-bottom:14px}
.callout{border-radius:10px;padding:16px 20px;margin:20px 0;display:flex;gap:14px;align-items:flex-start}
.callout-icon{font-size:18px;margin-top:1px;flex-shrink:0}
.callout-content{flex:1}
.callout-title{font-weight:600;font-size:13px;text-transform:uppercase;letter-spacing:.5px;margin-bottom:6px}
.callout-text{font-size:13.5px;line-height:1.7;color:var(--text-secondary)}
.callout.info{background:rgba(88,166,255,.08);border:1px solid rgba(88,166,255,.25)}.callout.info .callout-title{color:var(--accent-blue)}
.callout.success{background:rgba(63,185,80,.08);border:1px solid rgba(63,185,80,.25)}.callout.success .callout-title{color:var(--accent-green)}
.callout.warning{background:rgba(227,179,65,.08);border:1px solid rgba(227,179,65,.3)}.callout.warning .callout-title{color:var(--accent-yellow)}
.callout.danger{background:rgba(247,129,102,.08);border:1px solid rgba(247,129,102,.3)}.callout.danger .callout-title{color:var(--accent-orange)}
.callout.tip{background:rgba(188,140,255,.08);border:1px solid rgba(188,140,255,.25)}.callout.tip .callout-title{color:var(--accent-purple)}
.callout.teal{background:rgba(57,211,195,.08);border:1px solid rgba(57,211,195,.25)}.callout.teal .callout-title{color:var(--accent-teal)}
.code-block{background:#080c10;border:1px solid var(--border);border-radius:10px;overflow:hidden;margin:16px 0}
.code-header{background:var(--bg-secondary);border-bottom:1px solid var(--border);padding:8px 16px;display:flex;align-items:center;justify-content:space-between}
.code-lang{font-size:11px;color:var(--text-muted);text-transform:uppercase;letter-spacing:.8px;font-family:'JetBrains Mono',monospace}
.code-dots{display:flex;gap:5px}.code-dots span{width:10px;height:10px;border-radius:50%}
.dot-red{background:#ff5f56}.dot-ylw{background:#ffbd2e}.dot-grn{background:#27c93f}
.code-body{padding:20px;font-size:12.5px;line-height:1.85;color:#79c0ff;overflow-x:auto;white-space:pre;font-family:'JetBrains Mono',monospace}
.code-body .cmd{color:#3fb950}.code-body .comment{color:#6e7681;font-style:italic}
.code-body .param{color:#ffa657}.code-body .value{color:#a5d6ff}
.code-body .output{color:#8b949e}.code-body .prompt{color:#e3b341}.code-body .hl{color:#39d3c3}
.spec-table{width:100%;border-collapse:collapse;margin:16px 0;font-size:13.5px}
.spec-table th{background:var(--bg-secondary);color:var(--text-secondary);font-weight:600;font-size:12px;text-transform:uppercase;letter-spacing:.5px;padding:10px 16px;text-align:left;border-bottom:2px solid var(--border)}
.spec-table td{padding:11px 16px;border-bottom:1px solid var(--border);color:var(--text-secondary);vertical-align:middle}
.spec-table tr:hover td{background:rgba(255,255,255,.02)}
.badge{display:inline-block;padding:2px 10px;border-radius:20px;font-size:11.5px;font-weight:600;font-family:'JetBrains Mono',monospace}
.badge-blue{background:rgba(88,166,255,.15);color:var(--accent-blue);border:1px solid rgba(88,166,255,.3)}
.badge-green{background:rgba(63,185,80,.15);color:var(--accent-green);border:1px solid rgba(63,185,80,.3)}
.badge-orange{background:rgba(247,129,102,.15);color:var(--accent-orange);border:1px solid rgba(247,129,102,.3)}
.badge-yellow{background:rgba(227,179,65,.15);color:var(--accent-yellow);border:1px solid rgba(227,179,65,.3)}
.badge-teal{background:rgba(57,211,195,.15);color:var(--accent-teal);border:1px solid rgba(57,211,195,.3)}
.badge-purple{background:rgba(188,140,255,.15);color:var(--accent-purple);border:1px solid rgba(188,140,255,.3)}
.grid-2{display:grid;grid-template-columns:1fr 1fr;gap:16px;margin:16px 0}
.grid-3{display:grid;grid-template-columns:repeat(3,1fr);gap:16px;margin:16px 0}
.stat-card{background:var(--bg-card);border:1px solid var(--border);border-radius:10px;padding:20px;text-align:center}
.stat-num{font-family:'Sora',sans-serif;font-size:28px;font-weight:800;margin-bottom:4px}
.stat-label{font-size:12px;color:var(--text-muted);text-transform:uppercase;letter-spacing:.5px}
.step-list{list-style:none;margin:12px 0}
.step-list li{display:flex;gap:12px;padding:10px 0;border-bottom:1px solid rgba(48,54,61,.5);font-size:13.5px;color:var(--text-secondary);line-height:1.6;align-items:flex-start}
.step-list li:last-child{border-bottom:none}
.step-num{width:22px;height:22px;border-radius:6px;background:rgba(57,211,195,.15);border:1px solid rgba(57,211,195,.3);color:var(--accent-teal);font-size:11px;font-weight:700;display:flex;align-items:center;justify-content:center;flex-shrink:0;margin-top:1px;font-family:'JetBrains Mono',monospace}
.bullet-list{list-style:none;margin:10px 0}
.bullet-list li{padding:6px 0 6px 20px;position:relative;font-size:13.5px;color:var(--text-secondary);line-height:1.6}
.bullet-list li::before{content:'▸';position:absolute;left:0;color:var(--accent-teal);font-size:11px;top:8px}
h3{font-family:'Sora',sans-serif;font-size:17px;font-weight:600;color:var(--text-primary);margin:24px 0 12px}
h4{font-family:'Sora',sans-serif;font-size:14px;font-weight:600;color:var(--accent-teal);margin:18px 0 8px;text-transform:uppercase;letter-spacing:.5px}
.diagram-wrap{background:var(--bg-card);border:1px solid var(--border);border-radius:12px;padding:24px;margin:20px 0;overflow-x:auto}
.diagram-caption{text-align:center;font-size:12px;color:var(--text-muted);margin-top:12px;font-style:italic}
.mermaid{display:flex;justify-content:center}
.svg-wrap{background:var(--bg-card);border:1px solid var(--border);border-radius:12px;padding:24px;margin:20px 0;overflow-x:auto}
.quiz-card{background:var(--bg-card);border:1px solid var(--border);border-radius:12px;padding:22px;margin-bottom:16px}
.quiz-q{font-size:14px;font-weight:600;color:var(--text-primary);margin-bottom:12px}
.quiz-a{display:none;background:rgba(57,211,195,.06);border:1px solid rgba(57,211,195,.2);border-radius:8px;padding:14px 16px;margin-top:10px;font-size:13.5px;color:var(--text-secondary);line-height:1.7}
.quiz-btn{background:rgba(57,211,195,.1);border:1px solid rgba(57,211,195,.3);color:var(--accent-teal);border-radius:6px;padding:6px 14px;font-size:12px;cursor:pointer;font-family:'JetBrains Mono',monospace;transition:all .2s}
.quiz-btn:hover{background:rgba(57,211,195,.2)}
.author-card{background:linear-gradient(135deg,#161b22,#1c2333);border:1px solid var(--border);border-radius:16px;padding:32px;margin-top:40px;position:relative;overflow:hidden}
.author-card::before{content:'';position:absolute;top:-40px;right:-40px;width:180px;height:180px;background:radial-gradient(circle,rgba(57,211,195,.08),transparent 70%);border-radius:50%}
.author-avatar{font-size:48px;margin-bottom:12px}
.author-name{font-family:'Sora',sans-serif;font-size:22px;font-weight:700;color:var(--text-primary);margin-bottom:4px}
.author-title{font-size:13px;color:var(--accent-teal);margin-bottom:16px;font-family:'JetBrains Mono',monospace}
.author-bio{font-size:14px;color:var(--text-secondary);line-height:1.7;margin-bottom:20px}
.tech-badges{display:flex;flex-wrap:wrap;gap:8px;margin-bottom:20px}
.tech-badge{background:rgba(57,211,195,.1);border:1px solid rgba(57,211,195,.25);color:var(--accent-teal);border-radius:20px;padding:3px 12px;font-size:12px;font-family:'JetBrains Mono',monospace}
.contact-link{display:inline-flex;align-items:center;gap:8px;background:rgba(57,211,195,.1);border:1px solid rgba(57,211,195,.3);color:var(--accent-teal);border-radius:8px;padding:8px 16px;font-size:13px;text-decoration:none;transition:all .2s;margin-bottom:20px}
.contact-link:hover{background:rgba(57,211,195,.2)}
/* Port error viz */
.error-meter{display:flex;align-items:center;gap:12px;margin:8px 0}
.error-bar-wrap{flex:1;background:rgba(255,255,255,.05);border-radius:4px;height:10px;overflow:hidden}
.error-bar{height:100%;border-radius:4px}
.err-ok{background:var(--accent-green)}
.err-warn{background:var(--accent-yellow)}
.err-crit{background:var(--accent-orange)}
.error-label{font-size:12px;font-family:'JetBrains Mono',monospace;min-width:90px;color:var(--text-secondary)}
.error-val{font-size:12px;font-family:'JetBrains Mono',monospace;min-width:80px;text-align:right}
@media(max-width:900px){.sidebar{transform:translateX(-100%)}.main-content{margin-left:0;max-width:100vw}.top-header{padding:30px 20px}.content-area{padding:20px}.grid-2,.grid-3{grid-template-columns:1fr}#reading-progress{left:0}}
</style>
</head>
<body>
<div id="reading-progress"></div>
<!-- SIDEBAR -->
<nav class="sidebar">
<div class="sidebar-header">
<div class="sidebar-logo">
<div class="logo-icon">🔀</div>
<span>SAN Fundamentals</span>
</div>
<div class="sidebar-subtitle">Brocade Switch · CLI · Troubleshooting</div>
</div>
<div class="toc-nav">
<div class="toc-section-label">Management Interfaces</div>
<a class="toc-link" href="#s1"><span class="toc-num">01</span>CLI vs Web Tools (WebTools)</a>
<a class="toc-link" href="#s2"><span class="toc-num">02</span>Switch Info & Version Check</a>
<a class="toc-section-label">Switch Configuration</div>
<a class="toc-link" href="#s3"><span class="toc-num">03</span>Session & Environment Settings</a>
<a class="toc-link sub" href="#s3"><span class="toc-num">↳</span>Timeout & Quiet Mode</a>
<a class="toc-link" href="#s4"><span class="toc-num">04</span>Port Management & Types</a>
<a class="toc-link sub" href="#s4"><span class="toc-num">↳</span>F-Port, E-Port, Trunk</a>
<a class="toc-link sub" href="#s4"><span class="toc-num">↳</span>Speed Configuration</a>
<a class="toc-link" href="#s5"><span class="toc-num">05</span>Switch Enable / Disable Flow</a>
<div class="toc-section-label">Backup & Recovery</div>
<a class="toc-link" href="#s6"><span class="toc-num">06</span>Config Backup & Restore</a>
<a class="toc-link sub" href="#s6"><span class="toc-num">↳</span>configupload</a>
<a class="toc-link sub" href="#s6"><span class="toc-num">↳</span>configdownload</a>
<div class="toc-section-label">Availability & High Availability</div>
<a class="toc-link" href="#s7"><span class="toc-num">07</span>Service Processors & HA</a>
<a class="toc-link sub" href="#s7"><span class="toc-num">↳</span>hashow / hafailover</a>
<div class="toc-section-label">Troubleshooting</div>
<a class="toc-link" href="#s8"><span class="toc-num">08</span>Port Error Analysis</a>
<a class="toc-link sub" href="#s8"><span class="toc-num">↳</span>porterrshow / Clear Errors</a>
<a class="toc-link sub" href="#s8"><span class="toc-num">↳</span>SFP Health Checks</a>
<a class="toc-link" href="#s9"><span class="toc-num">09</span>Fabric Topology & Logs</a>
<a class="toc-link" href="#s10"><span class="toc-num">10</span>Command Quick Reference</a>
<a class="toc-link" href="#s11"><span class="toc-num">11</span>Interview Q&A</a>
<a class="toc-link" href="#author"><span class="toc-num">★</span>About</a>
</div>
<div class="series-nav">
<div class="series-nav-title">SAN Tutorial Series</div>
<a class="series-link" href="#" target="_blank">📋 Series Index</a>
<a class="series-link current" href="#">Tutorial — Brocade Management</a>
</div>
</nav>
<!-- MAIN -->
<div class="main-content">
<header class="top-header">
<div class="header-badge">🔀 SAN Tutorial · Brocade Switch Administration</div>
<h1 class="main-title">Brocade SAN Switch Management —<br>CLI Operations, Port Config & Troubleshooting</h1>
<p class="header-desc">A hands-on guide to managing Brocade Fibre Channel switches using the CLI and WebTools GUI. Covers FOS version checks, port configuration, session controls, configuration backup and restore, high-availability concepts, and a systematic approach to port error analysis.</p>
<div class="header-meta">
<div class="meta-chip"><span class="dot" style="background:var(--accent-teal)"></span>CLI Management</div>
<div class="meta-chip"><span class="dot" style="background:var(--accent-blue)"></span>Port Configuration</div>
<div class="meta-chip"><span class="dot" style="background:var(--accent-purple)"></span>Backup & Restore</div>
<div class="meta-chip"><span class="dot" style="background:var(--accent-orange)"></span>Troubleshooting</div>
</div>
<div class="prog-chips">
<span class="prog-chip">FOS</span>
<span class="prog-chip">WebTools</span>
<span class="prog-chip">portcfgshow</span>
<span class="prog-chip">porterrshow</span>
<span class="prog-chip">hashow</span>
<span class="prog-chip">configupload</span>
<span class="prog-chip">switchbeacon</span>
<span class="prog-chip">F-Port / E-Port</span>
<span class="prog-chip">Trunk Port</span>
<span class="prog-chip">SFP Health</span>
</div>
</header>
<div class="content-area">
<!-- ═══ SECTION 1 ═══ -->
<section class="section" id="s1">
<div class="section-header">
<div class="section-icon icon-teal">🖥️</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 01</div>
<h2>Management Interfaces — CLI vs WebTools</h2>
</div>
</div>
<p>Brocade SAN switches support two primary management interfaces: a powerful <strong style="color:var(--accent-teal)">command-line interface (CLI)</strong> accessible via SSH or console, and a browser-based <strong style="color:var(--accent-blue)">WebTools GUI</strong> that lets administrators manage the switch without memorizing commands.</p>
<p>WebTools is accessed simply by pointing a web browser at the switch's management IP address. Once authenticated, the full switch management experience — port states, zoning, fabric topology — is available graphically. However, older FOS versions may not render WebTools reliably in modern browsers, making CLI proficiency essential for any SAN administrator.</p>
<div class="grid-2">
<div class="card">
<div class="card-title">🖥️ CLI (Command Line)</div>
<ul class="bullet-list">
<li>Access via SSH or serial console</li>
<li>Full configuration and troubleshooting capability</li>
<li>Works across all FOS versions</li>
<li>Preferred for scripting and automation</li>
<li>Mandatory for console-only recovery</li>
</ul>
</div>
<div class="card">
<div class="card-title">🌐 WebTools GUI</div>
<ul class="bullet-list">
<li>Browser-based — enter switch IP in address bar</li>
<li>Graphical port and zone management</li>
<li>Visual fabric topology view</li>
<li>Requires FOS version compatibility with browser</li>
<li>Best for day-to-day operational visibility</li>
</ul>
</div>
</div>
<div class="diagram-wrap">
<div class="mermaid">
graph TD
Admin["👤 SAN Administrator"]
Admin -->|"SSH / Console"| CLI["🖥️ CLI\n(Fabric OS Shell)"]
Admin -->|"Browser → http://192.168.10.50"| WT["🌐 WebTools GUI"]
CLI --> SW["🔀 Brocade FC Switch\n(Fabric OS)"]
WT --> SW
SW --> Fabric["🕸️ SAN Fabric\n(Zoning · Ports · ISLs)"]
</div>
<div class="diagram-caption">Figure 1 — Two management paths to a Brocade switch: CLI over SSH/console or WebTools via browser</div>
</div>
<div class="callout info">
<div class="callout-icon">💡</div>
<div class="callout-content">
<div class="callout-title">Tip — When WebTools Won't Load</div>
<div class="callout-text">If WebTools fails to render in a modern browser, it almost always points to a FOS version compatibility mismatch. In such cases, fall back to CLI. All operations achievable in WebTools have an equivalent CLI command in FOS.</div>
</div>
</div>
</section>
<!-- ═══ SECTION 2 ═══ -->
<section class="section" id="s2">
<div class="section-header">
<div class="section-icon icon-blue">📋</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 02</div>
<h2>Switch Information & FOS Version Verification</h2>
</div>
</div>
<p>Before performing any configuration or maintenance activity on a Brocade switch, it is good practice to confirm the current FOS (Fabric Operating System) version, kernel version, and hardware details. The <code style="color:var(--accent-teal);background:rgba(57,211,195,.1);padding:2px 6px;border-radius:4px">version</code> command provides all of this in one output.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Switch Identification</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="prompt">sw-core-01:admin></span> <span class="cmd">version</span>
<span class="output">Kernel: 2.6.14.2
Fabric OS: v8.2.3b
Made on: Tue Mar 12 14:22:09 2024
Flash: Wed Apr 10 09:15:00 2024
BootProm: 1.0.9</span>
<span class="comment"># Check power supply status</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">psshow</span>
<span class="comment"># Check temperature sensors</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">tempshow</span>
<span class="comment"># Check fan status</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">fanshow</span></div>
</div>
<div class="callout teal">
<div class="callout-icon">📌</div>
<div class="callout-content">
<div class="callout-title">What the Version Output Tells You</div>
<div class="callout-text">
<strong style="color:var(--text-primary)">Fabric OS version</strong> — the switch operating system version (e.g. v8.2.3b). This determines feature availability and compatibility with management tools.<br><br>
<strong style="color:var(--text-primary)">Kernel</strong> — the underlying Linux kernel that Fabric OS runs on. Useful for deep-level diagnostics.<br><br>
<strong style="color:var(--text-primary)">Flash / BootProm</strong> — firmware dates, helpful when validating post-upgrade states.
</div>
</div>
</div>
<div class="diagram-wrap">
<div class="mermaid">
graph LR
V["version command"]
V --> FOS["Fabric OS Version\n(e.g. v8.2.3b)"]
V --> KRN["Linux Kernel Version\n(background OS layer)"]
V --> FLH["Flash / BootProm Dates\n(firmware build info)"]
</div>
<div class="diagram-caption">Figure 2 — Fields returned by the <code>version</code> command on a Brocade switch</div>
</div>
</section>
<!-- ═══ SECTION 3 ═══ -->
<section class="section" id="s3">
<div class="section-header">
<div class="section-icon icon-purple">⚙️</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 03</div>
<h2>Session Controls & Environment Settings</h2>
</div>
</div>
<p>Fabric OS provides several session-level commands that control how the CLI behaves during your management session. These are lightweight but important for operational hygiene — especially in shared environments or during maintenance windows where background alerts could interfere with active work.</p>
<h3>Idle Session Timeout</h3>
<p>To prevent unauthorized access via forgotten open sessions, you can configure an automatic logout after a defined idle period using the <code style="color:var(--accent-teal);background:rgba(57,211,195,.1);padding:2px 6px;border-radius:4px">timeout</code> command.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Session Timeout</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Set idle timeout to 15 minutes</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">timeout</span> <span class="param">15</span>
<span class="comment"># Value 0 disables timeout (not recommended in production)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">timeout</span> <span class="param">0</span></div>
</div>
<h3>Quiet Mode</h3>
<p>During active CLI sessions, the switch can push background alert messages directly to your terminal — interrupting command output mid-flow. Enabling <strong>Quiet Mode</strong> suppresses these in-session alert messages so your working output stays clean and readable.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Quiet Mode</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Enable quiet mode — suppress background alerts in session</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">setquietmode</span> <span class="param">1</span>
<span class="comment"># Disable quiet mode — resume alert display</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">setquietmode</span> <span class="param">0</span></div>
</div>
<h3>Switch Beacon — Remote Port Identification</h3>
<p>In large data centers, physically identifying a specific port on a switch can be challenging. The Switch Beacon feature toggles the LED on a target port so on-site personnel can visually locate and verify it without confusion.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Switch Beacon</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Enable beacon on port 4 (LED starts blinking)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchbeacon</span> <span class="param">--port 4 --enable</span>
<span class="comment"># Disable beacon on port 4</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchbeacon</span> <span class="param">--port 4 --disable</span></div>
</div>
<div class="callout success">
<div class="callout-icon">✅</div>
<div class="callout-content">
<div class="callout-title">Best Practice — Beacon Before Cabling</div>
<div class="callout-text">Always enable the beacon on a target port before instructing on-site staff to connect a cable. This eliminates wrong-port cabling mistakes that can disrupt live fabric traffic on neighboring ports.</div>
</div>
</div>
<div class="diagram-wrap">
<div class="mermaid">
sequenceDiagram
participant Ops as Remote Admin
participant CLI as Switch CLI
participant DC as On-Site Tech
Ops->>CLI: switchbeacon --port 4 --enable
CLI-->>DC: Port 4 LED begins blinking 🔵
DC->>DC: Locates correct port visually
DC->>DC: Connects FC cable to Port 4
Ops->>CLI: switchbeacon --port 4 --disable
CLI-->>DC: LED returns to normal state
</div>
<div class="diagram-caption">Figure 3 — Switch Beacon workflow for remote-guided port identification</div>
</div>
<h3>License Management</h3>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — License Info</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># List installed licenses</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">licenseshow</span>
<span class="comment"># Add a new license key</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">licenseadd</span> <span class="value">"XXXXXXXXXXXXXXXXXXX"</span></div>
</div>
</section>
<!-- ═══ SECTION 4 ═══ -->
<section class="section" id="s4">
<div class="section-header">
<div class="section-icon icon-green">🔌</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 04</div>
<h2>Port Management — Types, Configuration & Speed</h2>
</div>
</div>
<p>Port management is at the heart of day-to-day SAN switch operations. Fabric OS allows per-port configuration of mode (F-Port, E-Port, Trunk), speed, and operational state. Any configuration change must follow the mandatory <strong style="color:var(--accent-orange)">disable → configure → enable</strong> sequence to avoid traffic disruption.</p>
<h3>Port Types Overview</h3>
<table class="spec-table">
<thead>
<tr><th>Port Type</th><th>Purpose</th><th>Connected To</th><th>Command</th></tr>
</thead>
<tbody>
<tr><td><span class="badge badge-blue">F-Port</span></td><td>Fabric Port — connects end devices</td><td>Server HBA / Storage FCA</td><td><code>portcfgfport</code></td></tr>
<tr><td><span class="badge badge-purple">E-Port</span></td><td>Expansion Port — inter-switch link</td><td>Another FC Switch (ISL)</td><td><code>portcfgeport</code></td></tr>
<tr><td><span class="badge badge-teal">Trunk Port</span></td><td>Link aggregation of physical ports</td><td>ISL trunking between switches</td><td><code>portcfgtrunkport</code></td></tr>
</tbody>
</table>
<div class="diagram-wrap">
<svg viewBox="0 0 700 220" xmlns="http://www.w3.org/2000/svg" style="width:100%;max-width:700px;display:block;margin:0 auto">
<defs>
<marker id="arr" markerWidth="8" markerHeight="6" refX="8" refY="3" orient="auto">
<polygon points="0 0,8 3,0 6" fill="#39d3c3"/>
</marker>
<marker id="arr2" markerWidth="8" markerHeight="6" refX="8" refY="3" orient="auto">
<polygon points="0 0,8 3,0 6" fill="#bc8cff"/>
</marker>
</defs>
<!-- Switch box -->
<rect x="260" y="60" width="180" height="100" rx="10" fill="#1c2333" stroke="#30363d" stroke-width="1.5"/>
<text x="350" y="78" text-anchor="middle" fill="#e6edf3" font-size="12" font-weight="700" font-family="Sora,sans-serif">Brocade Switch</text>
<!-- F-Port -->
<rect x="274" y="88" width="40" height="20" rx="4" fill="rgba(88,166,255,.2)" stroke="rgba(88,166,255,.5)" stroke-width="1"/>
<text x="294" y="102" text-anchor="middle" fill="#58a6ff" font-size="10" font-weight="700" font-family="JetBrains Mono,monospace">F-Port</text>
<!-- E-Port -->
<rect x="386" y="88" width="40" height="20" rx="4" fill="rgba(188,140,255,.2)" stroke="rgba(188,140,255,.5)" stroke-width="1"/>
<text x="406" y="102" text-anchor="middle" fill="#bc8cff" font-size="10" font-weight="700" font-family="JetBrains Mono,monospace">E-Port</text>
<!-- Trunk -->
<rect x="274" y="120" width="152" height="20" rx="4" fill="rgba(57,211,195,.15)" stroke="rgba(57,211,195,.4)" stroke-width="1"/>
<text x="350" y="134" text-anchor="middle" fill="#39d3c3" font-size="10" font-weight="700" font-family="JetBrains Mono,monospace">Trunk Port (aggregated)</text>
<!-- Server -->
<rect x="60" y="80" width="100" height="60" rx="8" fill="#161b22" stroke="#30363d" stroke-width="1.5"/>
<text x="110" y="107" text-anchor="middle" fill="#e6edf3" font-size="11" font-family="Sora,sans-serif">Server</text>
<text x="110" y="124" text-anchor="middle" fill="#58a6ff" font-size="10" font-family="JetBrains Mono,monospace">HBA</text>
<!-- Storage -->
<rect x="540" y="40" width="100" height="60" rx="8" fill="#161b22" stroke="#30363d" stroke-width="1.5"/>
<text x="590" y="67" text-anchor="middle" fill="#e6edf3" font-size="11" font-family="Sora,sans-serif">Storage</text>
<text x="590" y="84" text-anchor="middle" fill="#58a6ff" font-size="10" font-family="JetBrains Mono,monospace">FCA</text>
<!-- Other Switch -->
<rect x="540" y="120" width="100" height="60" rx="8" fill="#161b22" stroke="#30363d" stroke-width="1.5"/>
<text x="590" y="150" text-anchor="middle" fill="#e6edf3" font-size="11" font-family="Sora,sans-serif">Switch B</text>
<text x="590" y="167" text-anchor="middle" fill="#bc8cff" font-size="10" font-family="JetBrains Mono,monospace">ISL</text>
<!-- Lines -->
<line x1="160" y1="110" x2="272" y2="98" stroke="#58a6ff" stroke-width="1.5" marker-end="url(#arr)"/>
<text x="200" y="96" fill="#58a6ff" font-size="9" font-family="JetBrains Mono,monospace">F-Port</text>
<line x1="428" y1="98" x2="538" y2="70" stroke="#58a6ff" stroke-width="1.5" marker-end="url(#arr)"/>
<text x="468" y="78" fill="#58a6ff" font-size="9" font-family="JetBrains Mono,monospace">F-Port</text>
<line x1="428" y1="105" x2="538" y2="148" stroke="#bc8cff" stroke-width="1.5" marker-end="url(#arr2)"/>
<text x="468" y="140" fill="#bc8cff" font-size="9" font-family="JetBrains Mono,monospace">E-Port (ISL)</text>
</svg>
<div class="diagram-caption">Figure 4 — F-Ports connect hosts and storage; E-Ports form Inter-Switch Links (ISLs); Trunk aggregates multiple E-Ports</div>
</div>
<h3>Port Configuration Commands</h3>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Port Type & Speed Configuration</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># MANDATORY: disable port before changing configuration</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portdisable</span> <span class="param">6</span>
<span class="comment"># Set port 6 as F-Port (connects host/storage)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgfport</span> <span class="param">6</span>
<span class="comment"># Set port 7 as E-Port (inter-switch link)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgeport</span> <span class="param">7</span>
<span class="comment"># Configure trunk port (logical aggregation of ports 8 and 9)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgtrunkport</span> <span class="param">8</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgtrunkport</span> <span class="param">9</span>
<span class="comment"># Set port speed (e.g. 16Gbps auto-negotiate)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgspeed</span> <span class="param">6 0</span> <span class="comment"> # 0 = auto</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgspeed</span> <span class="param">6 16</span> <span class="comment"> # force 16Gbps</span>
<span class="comment"># Re-enable port after configuration</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portenable</span> <span class="param">6</span>
<span class="comment"># View full port configuration</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portcfgshow</span> <span class="param">6</span>
<span class="comment"># Detailed port status</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portshow</span> <span class="param">6</span></div>
</div>
<div class="callout danger">
<div class="callout-icon">⚠️</div>
<div class="callout-content">
<div class="callout-title">Warning — Never Configure a Live Port</div>
<div class="callout-text">Changing port type or speed on an active port without first disabling it can cause fabric reconfiguration events (RSCNs), disrupting I/O across all devices zoned to that port. Always follow: <strong>portdisable → configure → portenable</strong>.</div>
</div>
</div>
</section>
<!-- ═══ SECTION 5 ═══ -->
<section class="section" id="s5">
<div class="section-header">
<div class="section-icon icon-orange">🔄</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 05</div>
<h2>Switch Enable / Disable — Initial Setup Flow</h2>
</div>
</div>
<p>When a new Brocade switch arrives in the data center, it must be initialized through a specific sequence before being introduced into a live SAN fabric. Skipping this order — particularly forgetting to disable the switch before setting Domain ID — is a common mistake that can cause fabric segmentation.</p>
<div class="diagram-wrap">
<div class="mermaid">
flowchart TD
A["📦 New Switch Received"] --> B["Connect to Console Port"]
B --> C["Log in via CLI\n(default credentials)"]
C --> D["switchdisable\n(take switch offline)"]
D --> E["Configure Domain ID\n(must be unique in fabric)"]
E --> F["Configure other parameters\n(IP, timezone, DNS)"]
F --> G["switchenable\n(bring switch online)"]
G --> H["Verify fabric join\nfabricshow / switchshow"]
H --> I["✅ Switch Active in Fabric"]
</div>
<div class="diagram-caption">Figure 5 — Mandatory initialization sequence for a new Brocade SAN switch</div>
</div>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Switch Enable / Disable</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Disable the switch (required before initial domain configuration)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchdisable</span>
<span class="comment"># Set domain ID (must be unique within the fabric, range 1-239)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">configure</span>
<span class="output"> Fabric parameters (yes, y, no, n): [no] y
Domain: (1..239) [1] 12</span>
<span class="comment"># Enable the switch to join the fabric</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchenable</span>
<span class="comment"># Verify switch state</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchshow</span></div>
</div>
<div class="callout warning">
<div class="callout-icon">🔔</div>
<div class="callout-content">
<div class="callout-title">Domain ID Conflicts</div>
<div class="callout-text">If two switches in the same fabric share a Domain ID, a fabric segmentation event occurs — the fabric splits into isolated segments and I/O halts. Always audit existing Domain IDs in the fabric using <code>fabricshow</code> before configuring a new switch.</div>
</div>
</div>
</section>
<!-- ═══ SECTION 6 ═══ -->
<section class="section" id="s6">
<div class="section-header">
<div class="section-icon icon-yellow">💾</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 06</div>
<h2>Configuration Backup & Restore</h2>
</div>
</div>
<p>Configuration backup is a non-negotiable step before any firmware upgrade or major maintenance activity. If a FOS upgrade goes wrong and the switch configuration is lost, the entire fabric dependent on that switch goes down — affecting all hosts and storage in that fabric. A pre-saved configuration snapshot allows full recovery.</p>
<h3>configupload — Backup Switch Configuration</h3>
<p>The <code style="color:var(--accent-teal);background:rgba(57,211,195,.1);padding:2px 6px;border-radius:4px">configupload</code> command transfers the current switch configuration to a remote server using SCP, FTP, or SFTP.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Configuration Backup</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="prompt">sw-core-01:admin></span> <span class="cmd">configupload</span>
<span class="output">Protocol (scp, ftp, sftp): [ftp] scp
Server Name or IP Address [host]: </span><span class="value">172.16.50.20</span>
<span class="output">User Name [user]: </span><span class="value">backupadmin</span>
<span class="output">Path/Filename [<home dir>/config.txt]: </span><span class="value">/backups/san/sw-core-01-2025-08-01.txt</span>
<span class="output">Password: ****
configUpload complete: All config parameters are uploaded</span></div>
</div>
<h3>configdownload — Restore Switch Configuration</h3>
<p>To restore from a backup, first disable the switch, run <code style="color:var(--accent-teal);background:rgba(57,211,195,.1);padding:2px 6px;border-radius:4px">configdownload</code> pointing to the saved file, then re-enable. The switch returns to the exact configuration captured at backup time.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Configuration Restore</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Step 1: Disable switch before restore</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchdisable</span>
<span class="comment"># Step 2: Download and apply saved configuration</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">configdownload</span>
<span class="output">Protocol (scp, ftp, sftp): [ftp] scp
Server Name or IP Address [host]: </span><span class="value">172.16.50.20</span>
<span class="output">User Name [user]: </span><span class="value">backupadmin</span>
<span class="output">Path/Filename [<home dir>/config.txt]: </span><span class="value">/backups/san/sw-core-01-2025-08-01.txt</span>
<span class="output">Password: ****
configDownload complete: All config parameters are downloaded</span>
<span class="comment"># Step 3: Re-enable the switch</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">switchenable</span></div>
</div>
<div class="diagram-wrap">
<div class="mermaid">
flowchart LR
SW["🔀 Brocade Switch"] -->|"configupload\n(SCP/SFTP)"| BS["📁 Backup Server\n172.16.50.20\n/backups/san/"]
BS -->|"configdownload\n(after switchdisable)"| SW2["🔀 Switch\n(restored state)"]
</div>
<div class="diagram-caption">Figure 6 — Configuration backup flows from switch to remote server; restore flows in reverse</div>
</div>
<div class="callout danger">
<div class="callout-icon">🚨</div>
<div class="callout-content">
<div class="callout-title">Critical — Always Backup Before Firmware Upgrade</div>
<div class="callout-text">A FOS firmware upgrade can corrupt switch configuration in rare failure scenarios. Without a valid backup, you would need to manually reconfigure the switch from scratch — including all zoning, domain settings, and port configurations. Schedule backups before every planned change window.</div>
</div>
</div>
</section>
<!-- ═══ SECTION 7 ═══ -->
<section class="section" id="s7">
<div class="section-header">
<div class="section-icon icon-purple">🔁</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 07</div>
<h2>Service Processors & High Availability</h2>
</div>
</div>
<p>Brocade SAN switches come in two major form factors with different high-availability characteristics. Understanding which type you are working with determines your maintenance strategy — particularly for firmware upgrades.</p>
<div class="grid-2">
<div class="card">
<div class="card-title" style="color:var(--accent-blue)">🏢 Department-Class Switches</div>
<ul class="bullet-list">
<li>Single Control Processor (CP) blade</li>
<li>No redundant service processor</li>
<li>Firmware upgrades require switch downtime</li>
<li>Suitable for smaller SAN environments</li>
<li>Examples: Brocade 300, 5100, G610</li>
</ul>
</div>
<div class="card">
<div class="card-title" style="color:var(--accent-teal)">🏭 Director-Class Switches</div>
<ul class="bullet-list">
<li>Dual Control Processor blades (active + standby)</li>
<li>Non-disruptive firmware upgrades (ISSU)</li>
<li>Upgrade CP-A first, then CP-B without outage</li>
<li>High port density with hot-swappable blades</li>
<li>Examples: Brocade DCX 8510, X7 Director</li>
</ul>
</div>
</div>
<div class="diagram-wrap">
<div class="mermaid">
graph TD
subgraph DIR["Director-Class Switch — Dual CP"]
CPA["CP-A\n(Active)"] <-->|"sync"| CPB["CP-B\n(Standby)"]
CPA --> P1["Port Blades\n(16/32/64 ports each)"]
CPB --> P1
end
subgraph DEPT["Department-Class Switch — Single CP"]
SCP["CP\n(Active Only)"] --> SP["Port Array\n(fixed port count)"]
end
</div>
<div class="diagram-caption">Figure 7 — Director-class switches have dual redundant CPs; department-class have a single CP</div>
</div>
<h3>HA Commands — Checking & Triggering Failover</h3>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — High Availability Commands</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Check HA status — shows active/standby CP state</span>
<span class="prompt">sw-dir-01:admin></span> <span class="cmd">hashow</span>
<span class="output">Local CP (CP0): Active, Warm Recovered
Remote CP (CP1): Standby, Healthy
HA enabled, Heartbeat Up, HA State synchronized</span>
<span class="comment"># Manually trigger failover (promote standby to active)</span>
<span class="prompt">sw-dir-01:admin></span> <span class="cmd">hafailover</span>
<span class="comment"># Sync HA state between both CPs</span>
<span class="prompt">sw-dir-01:admin></span> <span class="cmd">hasyncconfiguration</span></div>
</div>
<div class="callout tip">
<div class="callout-icon">🎯</div>
<div class="callout-content">
<div class="callout-title">Interview Tip — ISSU vs Disruptive Upgrade</div>
<div class="callout-text"><strong>ISSU (In-Service Software Upgrade)</strong> is only available on director-class switches with dual CPs. The upgrade proceeds on the standby CP first, then failover happens, then the originally-active CP upgrades — all without dropping fabric traffic. Department-class switches require a maintenance window and planned downtime for firmware upgrades.</div>
</div>
</div>
</section>
<!-- ═══ SECTION 8 ═══ -->
<section class="section" id="s8">
<div class="section-header">
<div class="section-icon icon-orange">🔍</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 08</div>
<h2>Port Error Analysis & Troubleshooting</h2>
</div>
</div>
<p>Port errors are one of the most common triggers for SAN performance issues. Fabric OS tracks multiple error counters per port. Knowing how to read, interpret, and act on these errors is a core SAN administration skill.</p>
<h3>Reading Port Errors</h3>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Port Error Display & Clear</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Display error statistics for all ports</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">porterrshow</span>
<span class="output"> frames enc crc crc too too bad enc disc link loss loss frjt fbsy
ports tx in g_eof err shrt long eof out c3 fail sync sig
0: 123456 0 0 0 0 0 0 0 0 0 0 0 0 0
4: 4281000 0 38000 0 0 0 0 2 0 1 12 15 0 0</span>
<span class="comment"># Clear error counters on port 4</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">portstatscclear</span> <span class="param">4</span>
<span class="comment"># Wait, then re-check to see if errors accumulate again</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">porterrshow</span></div>
</div>
<h3>Error Severity Interpretation</h3>
<div class="card">
<div class="card-title">📊 Port Error Thresholds</div>
<div class="error-meter">
<span class="error-label">Hundreds</span>
<div class="error-bar-wrap"><div class="error-bar err-ok" style="width:15%"></div></div>
<span class="error-val" style="color:var(--accent-green)">✅ Normal — Monitor only</span>
</div>
<div class="error-meter">
<span class="error-label">Thousands</span>
<div class="error-bar-wrap"><div class="error-bar err-warn" style="width:50%"></div></div>
<span class="error-val" style="color:var(--accent-yellow)">⚠️ Investigate now</span>
</div>
<div class="error-meter">
<span class="error-label">10K+ / Lakhs</span>
<div class="error-bar-wrap"><div class="error-bar err-crit" style="width:100%"></div></div>
<span class="error-val" style="color:var(--accent-orange)">🚨 Critical action</span>
</div>
</div>
<h3>Systematic Error Investigation Workflow</h3>
<div class="diagram-wrap">
<div class="mermaid">
flowchart TD
A["🚨 High Port Errors Detected\n(porterrshow)"] --> B["Clear port error counters\nportstatscclear <port>"]
B --> C["Wait 15-30 minutes"]
C --> D["Re-run porterrshow"]
D --> E{Errors accumulating?}
E -->|No| F["✅ Was transient\nContinue monitoring"]
E -->|Yes| G["Check SFP health\nsfpshow <port>"]
G --> H{SFP Rx/Tx values OK?}
H -->|No| I["🔄 Replace SFP module"]
H -->|Yes| J["Inspect physical FC cable\n(check for bends, damage)"]
J --> K{Cable OK?}
K -->|No| L["🔄 Replace FC cable"]
K -->|Yes| M["Check connected HBA / FCA\non server or storage side"]
</div>
<div class="diagram-caption">Figure 8 — Systematic port error investigation workflow for SAN troubleshooting</div>
</div>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — SFP Diagnostics</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># View SFP optical data including Tx/Rx power levels</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">sfpshow</span> <span class="param">4</span>
<span class="output">Identifier: SFP+
Connector: LC
Transceiver: 4,8,16_Gig-FC
Baud Rate: 14025 MBd
Temperature: 42 Celsius
Voltage: 3.29 Volts
Current: 6.3 mAmps
RX Power: -4.3 dBm (0.3715 mWatts)
TX Power: -3.1 dBm (0.4898 mWatts)</span>
<span class="comment"># Healthy SFP: Rx/Tx values should be within vendor spec</span>
<span class="comment"># Degraded SFP: abnormally low Rx power, or large Rx/Tx gap</span></div>
</div>
<div class="callout info">
<div class="callout-icon">💡</div>
<div class="callout-content">
<div class="callout-title">Tip — Error Persistence is the Key Indicator</div>
<div class="callout-text">Errors that appear in the hundreds and do not grow over time after clearing can often be ignored — they may be historic counts from a cable swap or previous event. Errors that immediately re-accumulate after clearing point to an active underlying problem requiring hardware inspection.</div>
</div>
</div>
</section>
<!-- ═══ SECTION 9 ═══ -->
<section class="section" id="s9">
<div class="section-header">
<div class="section-icon icon-teal">🕸️</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 09</div>
<h2>Fabric Topology & Log Collection</h2>
</div>
</div>
<p>Understanding how switches are interconnected within the fabric is essential for capacity planning, troubleshooting, and change management. Fabric OS provides dedicated commands to view topology, collect diagnostic logs, and inspect inter-switch link health.</p>
<div class="code-block">
<div class="code-header">
<span class="code-lang">FOS CLI — Fabric & Diagnostic Commands</span>
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
</div>
<div class="code-body"><span class="comment"># Display all switches in the fabric with domain IDs</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">fabricshow</span>
<span class="output"> Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
1: fffc01 10:00:00:27:f8:5a:2e:01 192.168.10.50 0.0.0.0 "sw-core-01"
12: fffc0c 10:00:00:27:f8:5a:2e:02 192.168.10.51 0.0.0.0 "sw-core-02"</span>
<span class="comment"># Show physical topology — how switches interconnect</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">topologyshow</span>
<span class="comment"># Show ISL (E-Port) connections between switches</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">islshow</span>
<span class="comment"># Save support bundle (logs, configs, diagnostics)</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">supportsave</span>
<span class="output">Protocol (scp, ftp, sftp): [ftp] scp
Server Name or IP Address: </span><span class="value">172.16.50.20</span>
<span class="output">User Name: </span><span class="value">backupadmin</span>
<span class="output">Path/Filename: </span><span class="value">/logs/san/</span>
<span class="output">Password: ****
supportSave: switch support data saved</span></div>
</div>
<div class="diagram-wrap">
<div class="mermaid">
graph TD
subgraph Fabric["SAN Fabric — Multi-Switch"]
SW1["🔀 sw-core-01\nDomain 1\n192.168.10.50"]
SW2["🔀 sw-core-02\nDomain 12\n192.168.10.51"]
SW1 <-->|"ISL (E-Port trunk)"| SW2
SRV1["💻 App Server 1\nHBA"] --> SW1
SRV2["💻 App Server 2\nHBA"] --> SW1
STG1["🗄️ Storage Array A\nFCA"] --> SW2
STG2["🗄️ Storage Array B\nFCA"] --> SW2
end
</div>
<div class="diagram-caption">Figure 9 — A two-switch SAN fabric: servers connect to sw-core-01, storage to sw-core-02, linked via ISL E-Ports</div>
</div>
</section>
<!-- ═══ SECTION 10 ═══ -->
<section class="section" id="s10">
<div class="section-header">
<div class="section-icon icon-blue">📋</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 10</div>
<h2>Command Quick Reference</h2>
</div>
</div>
<table class="spec-table">
<thead>
<tr><th>Category</th><th>Command</th><th>Purpose</th></tr>
</thead>
<tbody>
<tr><td><span class="badge badge-blue">Info</span></td><td><code>version</code></td><td>FOS version, kernel, firmware dates</td></tr>
<tr><td><span class="badge badge-blue">Info</span></td><td><code>switchshow</code></td><td>Switch status, port summary, fabric membership</td></tr>
<tr><td><span class="badge badge-blue">Info</span></td><td><code>fabricshow</code></td><td>All switches in fabric with domain IDs and IPs</td></tr>
<tr><td><span class="badge badge-blue">Info</span></td><td><code>topologyshow</code></td><td>Physical interconnect topology between switches</td></tr>
<tr><td><span class="badge badge-green">Port</span></td><td><code>portshow <n></code></td><td>Detailed status of a specific port</td></tr>
<tr><td><span class="badge badge-green">Port</span></td><td><code>portcfgshow <n></code></td><td>Configuration of a specific port</td></tr>
<tr><td><span class="badge badge-green">Port</span></td><td><code>portdisable / portenable</code></td><td>Take a port offline / bring it online</td></tr>
<tr><td><span class="badge badge-green">Port</span></td><td><code>portcfgfport / eport / trunkport</code></td><td>Set port type (F, E, or Trunk)</td></tr>
<tr><td><span class="badge badge-green">Port</span></td><td><code>portcfgspeed <n> <speed></code></td><td>Set port speed (0=auto, 8, 16, 32)</td></tr>
<tr><td><span class="badge badge-orange">Health</span></td><td><code>porterrshow</code></td><td>Error counters across all ports</td></tr>
<tr><td><span class="badge badge-orange">Health</span></td><td><code>portstatscclear <n></code></td><td>Clear error counters on a port</td></tr>
<tr><td><span class="badge badge-orange">Health</span></td><td><code>sfpshow <n></code></td><td>SFP optical Tx/Rx levels and health</td></tr>
<tr><td><span class="badge badge-orange">Health</span></td><td><code>psshow / fanshow / tempshow</code></td><td>Power supply, fan, temperature status</td></tr>
<tr><td><span class="badge badge-purple">HA</span></td><td><code>hashow</code></td><td>Active/standby CP status (director class)</td></tr>
<tr><td><span class="badge badge-purple">HA</span></td><td><code>hafailover</code></td><td>Manually promote standby CP to active</td></tr>
<tr><td><span class="badge badge-yellow">Config</span></td><td><code>configupload</code></td><td>Back up switch configuration to remote server</td></tr>
<tr><td><span class="badge badge-yellow">Config</span></td><td><code>configdownload</code></td><td>Restore switch configuration from remote file</td></tr>
<tr><td><span class="badge badge-teal">Session</span></td><td><code>timeout <minutes></code></td><td>Set CLI idle session auto-logout timer</td></tr>
<tr><td><span class="badge badge-teal">Session</span></td><td><code>setquietmode 1 / 0</code></td><td>Suppress / allow background alerts in session</td></tr>
<tr><td><span class="badge badge-teal">Session</span></td><td><code>switchbeacon --port <n></code></td><td>Blink port LED for physical identification</td></tr>
<tr><td><span class="badge badge-teal">Session</span></td><td><code>supportsave</code></td><td>Collect and export full diagnostic support bundle</td></tr>
</tbody>
</table>
</section>
<!-- ═══ SECTION 11 ═══ -->
<section class="section" id="s11">
<div class="section-header">
<div class="section-icon icon-purple">🎯</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 11</div>
<h2>Scenario-Based Interview Q&A</h2>
</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q1. A junior admin accidentally configured a Domain ID on a live switch without disabling it first. What are the potential consequences and how would you recover?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Show Answer</button>
<div class="quiz-a">Configuring a Domain ID on a live switch without running <code>switchdisable</code> first can trigger a fabric reconfiguration (fabric rebuild). If the new Domain ID conflicts with an existing switch in the fabric, the switch will be isolated (segmented) from the fabric. Recovery steps: run <code>switchdisable</code>, correct the Domain ID to a unique value via <code>configure</code>, then run <code>switchenable</code>. Verify fabric membership with <code>fabricshow</code>.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q2. You observe CRC errors growing on port 8 of a Brocade switch after clearing them. What is your systematic troubleshooting approach?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Show Answer</button>
<div class="quiz-a">Growing CRC errors after clearing indicate an active physical layer problem. The investigation order is: (1) Run <code>sfpshow 8</code> — check Tx/Rx optical power levels against the vendor specification. Abnormal values suggest a degraded SFP. (2) If SFP values are within spec, inspect the FC cable for physical damage, sharp bends, dirty connectors, or excessive length. Replace suspect cables. (3) If cable checks out, move to the connected endpoint — check HBA or FCA on the server or storage side. CRC errors at the FC layer almost always originate from a physical layer issue.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q3. Explain the difference between a department-class and director-class Brocade switch for firmware upgrade planning purposes.</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Show Answer</button>
<div class="quiz-a">Department-class switches (e.g. Brocade 300, G610) have a single Control Processor (CP). A firmware upgrade requires taking the entire switch offline — all connected hosts and storage lose path access through that switch. Director-class switches (e.g. DCX 8510, X7 Director) have dual CPs (active + standby). ISSU (In-Service Software Upgrade) upgrades the standby CP first, fails over traffic to it, then upgrades the originally-active CP — the entire process is non-disruptive. This is the primary reason enterprises use director-class switches for mission-critical fabric links.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q4. What is Switch Beacon and in what operational scenario would you use it?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Show Answer</button>
<div class="quiz-a">Switch Beacon is a FOS feature that activates a blinking LED on a specific port, allowing on-site data center staff to visually identify the exact physical port without risk of connecting to the wrong one. A practical scenario: you need a technician in a remote data center to connect a new server HBA cable to port 6 on a 48-port switch. Instead of risking a wrong port connection (which could disrupt live fabric traffic on adjacent ports), you enable the beacon on port 6 via CLI, the LED blinks, the technician locates it visually, connects the cable, and you then disable the beacon.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q5. Why is it important to take a configupload backup before a FOS firmware upgrade, and what does the backup contain?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Show Answer</button>
<div class="quiz-a">A configupload backup captures the complete switch configuration — including Domain ID, zoning database, port configurations, IP settings, user accounts, and fabric parameters — in a single text file stored on a remote server. If a firmware upgrade fails or causes configuration corruption, you can restore the switch to a known-good state using configdownload without manually re-entering all parameters. Without this backup, a failed upgrade on a large fabric could require hours of manual reconfiguration and extended SAN downtime.</div>
</div>
</section>
<!-- AUTHOR -->
<div class="author-card" id="author">
<div class="author-avatar">🔀</div>
<div class="author-name">SAN Administration Series</div>
<div class="author-title">// Brocade Fabric OS · SAN Infrastructure · Enterprise Storage</div>
<div class="author-bio">This tutorial is part of an ongoing SAN administration series covering Fibre Channel fundamentals, switch management, zoning design, storage protocols, and troubleshooting methodology. The series is designed for storage administrators, infrastructure engineers, and those preparing for SAN-related roles.</div>
<div class="tech-badges">
<span class="tech-badge">Brocade FOS</span>
<span class="tech-badge">Fibre Channel</span>
<span class="tech-badge">SAN Fabric</span>
<span class="tech-badge">FC Zoning</span>
<span class="tech-badge">ISSU</span>