Repository navigation
Expand file tree
/
Copy pathnetapp-tutorial15.html
More file actions
1009 lines (917 loc) · 65.8 KB
/
Copy pathnetapp-tutorial15.html
File metadata and controls
1009 lines (917 loc) · 65.8 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>Fibre Channel Port Types — Switched Fabric Deep Dive</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%,#0d1a1a 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(88,166,255,.1);border:1px solid rgba(88,166,255,.25);color:var(--accent-blue);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 type pill grid */
.port-pill-grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(200px,1fr));gap:12px;margin:20px 0}
.port-pill{background:var(--bg-card);border:1px solid var(--border);border-radius:10px;padding:16px 18px;transition:all .2s}
.port-pill:hover{border-color:var(--border-bright);transform:translateY(-2px)}
.port-pill-label{font-family:'JetBrains Mono',monospace;font-size:18px;font-weight:700;margin-bottom:4px}
.port-pill-name{font-size:12px;color:var(--text-secondary);margin-bottom:6px}
.port-pill-desc{font-size:11.5px;color:var(--text-muted);line-height:1.5}
.pp-n{border-color:rgba(88,166,255,.4)}.pp-n .port-pill-label{color:var(--accent-blue)}
.pp-nl{border-color:rgba(227,179,65,.4)}.pp-nl .port-pill-label{color:var(--accent-yellow)}
.pp-f{border-color:rgba(63,185,80,.4)}.pp-f .port-pill-label{color:var(--accent-green)}
.pp-fl{border-color:rgba(188,140,255,.4)}.pp-fl .port-pill-label{color:var(--accent-purple)}
.pp-e{border-color:rgba(247,129,102,.4)}.pp-e .port-pill-label{color:var(--accent-orange)}
.pp-u{border-color:rgba(57,211,195,.4)}.pp-u .port-pill-label{color:var(--accent-teal)}
.pp-g{border-color:rgba(139,148,158,.4)}.pp-g .port-pill-label{color:var(--text-secondary)}
.pp-ve{border-color:rgba(188,140,255,.4)}.pp-ve .port-pill-label{color:var(--accent-purple)}
.pp-ex{border-color:rgba(247,129,102,.4)}.pp-ex .port-pill-label{color:var(--accent-orange)}
/* ISL viz */
.isl-box{background:var(--bg-card);border:1px solid var(--border);border-radius:12px;padding:20px;margin:16px 0}
@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}.port-pill-grid{grid-template-columns:1fr 1fr}}
</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">FC Port Types · Switched Fabric</div>
</div>
<div class="toc-nav">
<div class="toc-section-label">Foundation</div>
<a class="toc-link" href="#s1"><span class="toc-num">01</span>Intelligent Switched Fabric</a>
<a class="toc-link" href="#s2"><span class="toc-num">02</span>Port Type Overview</a>
<div class="toc-section-label">Device-Side Ports</div>
<a class="toc-link" href="#s3"><span class="toc-num">03</span>N Port — Node Port</a>
<a class="toc-link" href="#s4"><span class="toc-num">04</span>NL Port — Node Loop Port</a>
<div class="toc-section-label">Switch-Side Ports</div>
<a class="toc-link" href="#s5"><span class="toc-num">05</span>U Port — Universal Port</a>
<a class="toc-link" href="#s6"><span class="toc-num">06</span>F Port — Fabric Port</a>
<a class="toc-link" href="#s7"><span class="toc-num">07</span>FL Port — Fabric Loop Port</a>
<a class="toc-link" href="#s8"><span class="toc-num">08</span>G Port — Generic Port</a>
<a class="toc-link" href="#s9"><span class="toc-num">09</span>E Port — Expansion Port</a>
<div class="toc-section-label">Advanced Ports</div>
<a class="toc-link" href="#s10"><span class="toc-num">10</span>VE, EX & VEX Ports</a>
<a class="toc-link" href="#s11"><span class="toc-num">11</span>Port Discovery Workflow</a>
<a class="toc-link" href="#s12"><span class="toc-num">12</span>Quick Reference Table</a>
<a class="toc-link" href="#s13"><span class="toc-num">13</span>Interview Q&A</a>
</div>
<div class="series-nav">
<div class="series-nav-title">Tutorial Series</div>
<a class="series-link" href="#">Session 28 — FC Topologies</a>
<a class="series-link" href="#">Session 29 — FC Protocol Stack</a>
<a class="series-link current" href="#">Session 30 — FC Port Types ✦</a>
<a class="series-link" href="#">Session 31 — FC Storage Presentation</a>
</div>
</nav>
<!-- ══════════════════════ MAIN ══════════════════════ -->
<div class="main-content">
<div class="top-header">
<div class="header-badge">📡 Switched Fabric</div>
<div class="main-title">Fibre Channel Port Types<br>in a Switched Fabric Environment</div>
<p class="header-desc">Every port in a Fibre Channel switched fabric has a role — and the fabric is intelligent enough to auto-configure them. This guide walks through each port type, when it applies, and how the switch decides what a port becomes.</p>
<div class="header-meta">
<div class="meta-chip"><div class="dot" style="background:var(--accent-teal)"></div>FC SAN</div>
<div class="meta-chip"><div class="dot" style="background:var(--accent-blue)"></div>Switched Fabric</div>
<div class="meta-chip"><div class="dot" style="background:var(--accent-purple)"></div>Port Architecture</div>
<div class="meta-chip"><div class="dot" style="background:var(--accent-orange)"></div>ISL / FCIP</div>
</div>
<div class="prog-chips">
<span class="prog-chip">N-Port</span>
<span class="prog-chip">NL-Port</span>
<span class="prog-chip">F-Port</span>
<span class="prog-chip">FL-Port</span>
<span class="prog-chip">E-Port</span>
<span class="prog-chip">U-Port</span>
<span class="prog-chip">G-Port</span>
<span class="prog-chip">VE-Port</span>
<span class="prog-chip">EX-Port</span>
<span class="prog-chip">FCIP</span>
</div>
</div>
<div class="content-area">
<!-- ═══ S1: Intelligent Fabric ═══ -->
<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>The Intelligent Switched Fabric</h2>
</div>
</div>
<p>One of the defining characteristics of modern Fibre Channel switched fabric environments is that the switch infrastructure is inherently self-aware. Unlike legacy networking gear that requires explicit manual configuration for every port role, FC switches can examine each connected device and automatically assign an appropriate port type based on what is detected at the far end of the cable.</p>
<p>This self-configuration capability means that administrators do not have to pre-configure each switch port before plugging in a device. Once a device is connected, the switch moves through a discovery process and converges on the correct port type automatically. That said, manual override is always available — the switch will respect any explicit port-type configuration that an administrator applies.</p>
<div class="callout teal">
<div class="callout-icon">💡</div>
<div class="callout-content">
<div class="callout-title">Key Concept — Auto-Negotiation of Port Type</div>
<div class="callout-text">FC switches detect what is attached to each physical port — whether it is a host, a storage array, a hub, or another switch — and configure the port type accordingly. Manual configuration is an option but not a requirement in most deployments.</div>
</div>
</div>
<div class="grid-3">
<div class="stat-card">
<div class="stat-num" style="color:var(--accent-teal)">9+</div>
<div class="stat-label">Distinct Port Types</div>
</div>
<div class="stat-card">
<div class="stat-num" style="color:var(--accent-blue)">2</div>
<div class="stat-label">Configuration Modes<br><small style="color:var(--text-muted);font-size:10px">Auto / Manual</small></div>
</div>
<div class="stat-card">
<div class="stat-num" style="color:var(--accent-orange)">1</div>
<div class="stat-label">Default State<br><small style="color:var(--text-muted);font-size:10px">G-Port on powerup</small></div>
</div>
</div>
</section>
<!-- ═══ S2: Overview ═══ -->
<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>Port Type Overview — At a Glance</h2>
</div>
</div>
<p>FC port types fall into two broad families: <strong>device-side ports</strong> (ports that live on hosts or storage arrays) and <strong>switch-side ports</strong> (ports that live on the FC switch itself). Understanding which side of the cable each port type belongs to is the first step to mastering FC fabric design.</p>
<div class="port-pill-grid">
<div class="port-pill pp-n">
<div class="port-pill-label">N</div>
<div class="port-pill-name">Node Port</div>
<div class="port-pill-desc">Device directly attached to fabric (host or storage HBA/FCA)</div>
</div>
<div class="port-pill pp-nl">
<div class="port-pill-label">NL</div>
<div class="port-pill-name">Node Loop Port</div>
<div class="port-pill-desc">Device attached via FC Arbitrated Loop (hub-based)</div>
</div>
<div class="port-pill pp-u">
<div class="port-pill-label">U</div>
<div class="port-pill-name">Universal Port</div>
<div class="port-pill-desc">Transitional state — switch discovering the connected device</div>
</div>
<div class="port-pill pp-f">
<div class="port-pill-label">F</div>
<div class="port-pill-name">Fabric Port</div>
<div class="port-pill-desc">Switch port facing a directly-connected device</div>
</div>
<div class="port-pill pp-fl">
<div class="port-pill-label">FL</div>
<div class="port-pill-name">Fabric Loop Port</div>
<div class="port-pill-desc">Switch port facing a hub or FCAL loop segment</div>
</div>
<div class="port-pill pp-g">
<div class="port-pill-label">G</div>
<div class="port-pill-name">Generic Port</div>
<div class="port-pill-desc">Default state before any device is connected</div>
</div>
<div class="port-pill pp-e">
<div class="port-pill-label">E</div>
<div class="port-pill-name">Expansion Port</div>
<div class="port-pill-desc">Inter-Switch Link (ISL) between two FC switches</div>
</div>
<div class="port-pill pp-ve">
<div class="port-pill-label">VE</div>
<div class="port-pill-name">Virtual E Port</div>
<div class="port-pill-desc">E-port over IP tunnel — FCIP-based fabric extension</div>
</div>
<div class="port-pill pp-ex">
<div class="port-pill-label">EX</div>
<div class="port-pill-name">FC Router E Port</div>
<div class="port-pill-desc">Connects to an FC router fabric boundary</div>
</div>
</div>
<div class="callout info">
<div class="callout-icon">📋</div>
<div class="callout-content">
<div class="callout-title">Two Families of Port Types</div>
<div class="callout-text"><strong>Device-side:</strong> N, NL — these exist on servers, storage arrays, or tape libraries (the endpoints).<br><strong>Switch-side:</strong> U, F, FL, G, E, VE, EX — these exist on the FC switch or director chassis itself.</div>
</div>
</div>
</section>
<!-- ═══ S3: N Port ═══ -->
<section class="section" id="s3">
<div class="section-header">
<div class="section-icon icon-blue">🖥️</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 03</div>
<h2>N Port — Node Port</h2>
</div>
</div>
<p>An N Port (Node Port) is the port type assigned to any end-device — a server, storage controller, or tape system — that connects <em>directly</em> to an FC switch without any intermediate device in the path. The term "node" refers to any participant in the fabric that is not a switch itself.</p>
<p>The key criterion is the direct connection: if a physical FC cable runs straight from the device's HBA or FCA port into a switch port, that device-side port is classified as an N Port. This applies equally to compute nodes and storage nodes.</p>
<div class="svg-wrap">
<svg viewBox="0 0 720 200" xmlns="http://www.w3.org/2000/svg" style="width:100%;max-width:720px;display:block;margin:0 auto">
<!-- Server -->
<rect x="20" y="60" width="150" height="80" rx="10" fill="#1c2333" stroke="#58a6ff" stroke-width="1.5"/>
<text x="95" y="92" text-anchor="middle" font-family="Sora,sans-serif" font-size="12" font-weight="700" fill="#e6edf3">Compute Node</text>
<text x="95" y="110" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">HBA Port</text>
<rect x="168" y="88" width="12" height="14" rx="2" fill="#58a6ff" opacity="0.8"/>
<text x="95" y="128" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="11" font-weight="700" fill="#58a6ff">N Port</text>
<!-- FC Switch -->
<rect x="280" y="40" width="160" height="120" rx="10" fill="#1c2333" stroke="#39d3c3" stroke-width="1.5"/>
<text x="360" y="72" text-anchor="middle" font-family="Sora,sans-serif" font-size="12" font-weight="700" fill="#e6edf3">FC Switch</text>
<rect x="280" y="84" width="14" height="14" rx="2" fill="#58a6ff" opacity="0.7"/>
<text x="300" y="114" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">F Port</text>
<rect x="446" y="84" width="14" height="14" rx="2" fill="#3fb950" opacity="0.7"/>
<text x="390" y="114" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">F Port</text>
<text x="360" y="145" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#39d3c3">Domain: sw-core-01</text>
<!-- Storage -->
<rect x="550" y="60" width="150" height="80" rx="10" fill="#1c2333" stroke="#3fb950" stroke-width="1.5"/>
<text x="625" y="92" text-anchor="middle" font-family="Sora,sans-serif" font-size="12" font-weight="700" fill="#e6edf3">Storage Array</text>
<text x="625" y="110" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">FCA Port</text>
<rect x="550" y="88" width="12" height="14" rx="2" fill="#3fb950" opacity="0.8"/>
<text x="625" y="128" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="11" font-weight="700" fill="#3fb950">N Port</text>
<!-- Lines -->
<line x1="180" y1="95" x2="280" y2="95" stroke="#58a6ff" stroke-width="2" stroke-dasharray="6,3"/>
<line x1="460" y1="95" x2="550" y2="95" stroke="#3fb950" stroke-width="2" stroke-dasharray="6,3"/>
<polygon points="276,91 286,95 276,99" fill="#58a6ff"/>
<polygon points="546,91 556,95 546,99" fill="#3fb950"/>
<!-- Labels -->
<text x="360" y="185" text-anchor="middle" font-family="Inter,sans-serif" font-size="11" fill="#6e7681" font-style="italic">Both HBA and FCA are N Ports — direct connections with no intermediary</text>
</svg>
<div class="diagram-caption">Figure 1 — N Port: device port on any endpoint connected directly to an FC switch</div>
</div>
<div class="card">
<div class="card-title">📌 N Port — Key Facts</div>
<ul class="bullet-list">
<li>Exists on the <strong>device side</strong> — not on the switch</li>
<li>Assigned when a host or storage system connects <em>directly</em> to a switch port</li>
<li>The matching switch-side port becomes an <strong>F Port</strong></li>
<li>Applies to both hosts and storage arrays equally</li>
<li>Part of Switched Fabric (point-to-point signaling at the physical link)</li>
</ul>
</div>
</section>
<!-- ═══ S4: NL Port ═══ -->
<section class="section" id="s4">
<div class="section-header">
<div class="section-icon icon-yellow">🔁</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 04</div>
<h2>NL Port — Node Loop Port</h2>
</div>
</div>
<p>The NL Port (Node Loop Port) is the device-side port type used when a host or storage system participates in an FC Arbitrated Loop (FCAL) topology — typically via an FC hub — rather than connecting directly to a switch. The "L" in NL explicitly denotes loop participation.</p>
<p>In practice, FCAL was a common deployment pattern in older data centers where cost efficiency was prioritized over performance. When a device joins through a loop segment, its port is designated NL, and the corresponding switch-side port becomes an FL Port.</p>
<div class="svg-wrap">
<svg viewBox="0 0 720 230" xmlns="http://www.w3.org/2000/svg" style="width:100%;max-width:720px;display:block;margin:0 auto">
<!-- Device 1 -->
<rect x="20" y="30" width="130" height="60" rx="8" fill="#1c2333" stroke="#e3b341" stroke-width="1.5"/>
<text x="85" y="55" text-anchor="middle" font-family="Sora,sans-serif" font-size="11" font-weight="700" fill="#e6edf3">Host alpha-01</text>
<text x="85" y="72" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" font-weight="700" fill="#e3b341">NL Port</text>
<!-- Device 2 -->
<rect x="20" y="140" width="130" height="60" rx="8" fill="#1c2333" stroke="#e3b341" stroke-width="1.5"/>
<text x="85" y="165" text-anchor="middle" font-family="Sora,sans-serif" font-size="11" font-weight="700" fill="#e6edf3">Host beta-02</text>
<text x="85" y="182" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" font-weight="700" fill="#e3b341">NL Port</text>
<!-- Hub -->
<rect x="240" y="80" width="120" height="70" rx="8" fill="#1c2333" stroke="#e3b341" stroke-width="2"/>
<text x="300" y="108" text-anchor="middle" font-family="Sora,sans-serif" font-size="12" font-weight="700" fill="#e6edf3">FC Hub</text>
<text x="300" y="126" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">FCAL Loop</text>
<text x="300" y="142" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#e3b341">hub-01</text>
<!-- Switch -->
<rect x="490" y="70" width="140" height="90" rx="8" fill="#1c2333" stroke="#39d3c3" stroke-width="1.5"/>
<text x="560" y="102" text-anchor="middle" font-family="Sora,sans-serif" font-size="12" font-weight="700" fill="#e6edf3">FC Switch</text>
<text x="560" y="122" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="11" font-weight="700" fill="#bc8cff">FL Port</text>
<text x="560" y="140" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">sw-edge-02</text>
<!-- Lines: devices to hub -->
<line x1="150" y1="60" x2="240" y2="100" stroke="#e3b341" stroke-width="1.5" stroke-dasharray="5,3"/>
<line x1="150" y1="170" x2="240" y2="130" stroke="#e3b341" stroke-width="1.5" stroke-dasharray="5,3"/>
<!-- Hub to switch -->
<line x1="360" y1="115" x2="490" y2="115" stroke="#bc8cff" stroke-width="2.5" stroke-dasharray="7,3"/>
<polygon points="486,111 496,115 486,119" fill="#bc8cff"/>
<!-- Annotations -->
<text x="420" y="105" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#bc8cff">Loop → Fabric</text>
<text x="360" y="215" text-anchor="middle" font-family="Inter,sans-serif" font-size="11" fill="#6e7681" font-style="italic">NL Ports join a loop segment; the switch-side port auto-configures as FL Port</text>
</svg>
<div class="diagram-caption">Figure 2 — NL Port: device participates in an FC Arbitrated Loop via a hub before reaching the switch</div>
</div>
<div class="callout warning">
<div class="callout-icon">⚠️</div>
<div class="callout-content">
<div class="callout-title">Legacy Topology</div>
<div class="callout-text">FCAL and NL Ports are considered legacy in modern SAN designs. Switched Fabric with N Ports and F Ports has replaced loop-based topologies in virtually all new deployments. You will encounter NL Ports primarily in environments that have older hardware not yet refreshed.</div>
</div>
</div>
</section>
<!-- ═══ S5: U Port ═══ -->
<section class="section" id="s5">
<div class="section-header">
<div class="section-icon icon-teal">⏳</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 05</div>
<h2>U Port — Universal Port</h2>
</div>
</div>
<p>The U Port (Universal Port) is a transient state, not a final port type. When a device is physically connected to a switch port but the switch has not yet completed device identification, the port enters the U Port state. Think of it as "pending classification."</p>
<p>During U Port status, the switch actively runs the FC login negotiation sequence (FLOGI and PLOGI) to identify what kind of device is on the far end. Once identification completes, the port transitions out of U Port to its final type — F Port, FL Port, or E Port.</p>
<div class="diagram-wrap">
<div class="mermaid">
flowchart LR
A["🔌 Cable Connected"] --> B["U Port\n(Discovery)"]
B --> C{Device Type\nIdentified?}
C -->|"Direct Host/Storage"| D["F Port"]
C -->|"Hub / FCAL Loop"| E["FL Port"]
C -->|"Another FC Switch"| F["E Port"]
C -->|"Timeout / Unknown"| G["U Port\n(stays pending)"]
style A fill:#161b22,stroke:#484f58,color:#8b949e
style B fill:#1c2333,stroke:#39d3c3,color:#39d3c3
style C fill:#1c2333,stroke:#e3b341,color:#e3b341
style D fill:#1c2333,stroke:#3fb950,color:#3fb950
style E fill:#1c2333,stroke:#bc8cff,color:#bc8cff
style F fill:#1c2333,stroke:#f78166,color:#f78166
style G fill:#1c2333,stroke:#484f58,color:#8b949e
</div>
<div class="diagram-caption">Figure 3 — U Port transition flow: the switch discovers the connected device and moves to the appropriate final port type</div>
</div>
<div class="callout info">
<div class="callout-icon">🔍</div>
<div class="callout-content">
<div class="callout-title">Exam Tip — U Port is Transient</div>
<div class="callout-text">U Port is not an operational state — no data flows while a port is in U Port mode. If you observe a port stuck in U Port, it typically means the device discovery failed due to a misconfiguration, an unsupported SFP, or a physical layer issue.</div>
</div>
</div>
</section>
<!-- ═══ S6: F Port ═══ -->
<section class="section" id="s6">
<div class="section-header">
<div class="section-icon icon-green">🔌</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 06</div>
<h2>F Port — Fabric Port</h2>
</div>
</div>
<p>The F Port (Fabric Port) is the most common switch-side port type in modern Fibre Channel environments. An F Port forms whenever a device — host or storage — connects directly to a switch port. It is the switch's side of the N-Port-to-F-Port link pair.</p>
<p>Every standard server-to-switch and storage-to-switch connection in a Switched Fabric environment produces this pairing: the device carries an N Port; the switch carries an F Port. The two negotiate connectivity through the FLOGI (Fabric Login) process during initialization.</p>
<div class="card">
<div class="card-title">🔑 N Port ↔ F Port Pairing</div>
<table class="spec-table">
<thead><tr><th>Endpoint</th><th>Port Type</th><th>Role</th></tr></thead>
<tbody>
<tr><td>Host HBA (e.g., <code>hba-host-vm01</code>)</td><td><span class="badge badge-blue">N Port</span></td><td>Initiates FLOGI to join fabric</td></tr>
<tr><td>Switch Port (e.g., port <code>3/4</code> on <code>sw-core-01</code>)</td><td><span class="badge badge-green">F Port</span></td><td>Accepts FLOGI, assigns FCID address</td></tr>
<tr><td>Storage FCA (e.g., <code>fca-stor-array02</code>)</td><td><span class="badge badge-blue">N Port</span></td><td>Initiates FLOGI as target device</td></tr>
<tr><td>Switch Port (e.g., port <code>5/2</code> on <code>sw-edge-01</code>)</td><td><span class="badge badge-green">F Port</span></td><td>Accepts FLOGI, assigns FCID address</td></tr>
</tbody>
</table>
</div>
<div class="callout success">
<div class="callout-icon">✅</div>
<div class="callout-content">
<div class="callout-title">Best Practice</div>
<div class="callout-text">In new SAN deployments, all device connections should use N Port + F Port pairings. Avoid introducing loop segments unless the legacy hardware absolutely requires it. This gives you the best performance, predictability, and troubleshooting visibility.</div>
</div>
</div>
</section>
<!-- ═══ S7: FL Port ═══ -->
<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>FL Port — Fabric Loop Port</h2>
</div>
</div>
<p>When an FC hub or an FC Arbitrated Loop segment connects to a switch port, the switch-side port transitions to FL Port (Fabric Loop Port) rather than a standard F Port. The "L" suffix consistently marks loop involvement on both sides of the connection: NL Port on the device side, FL Port on the switch side.</p>
<p>FL Ports act as the gateway between the loop topology and the switched fabric. All devices in the attached loop share this single FL Port connection to the switch, which means they also share its bandwidth — a key limitation compared to dedicated F Port connections.</p>
<div class="diagram-wrap">
<div class="mermaid">
flowchart LR
subgraph Loop["FCAL Loop Segment"]
D1["🖥️ Host gamma-03\nNL Port"] <--> HUB["FC Hub\nhub-02"]
D2["💾 Storage delta-04\nNL Port"] <--> HUB
end
HUB <-->|"FL Port"| SW["FC Switch\nsw-edge-02\n(FL Port)"]
SW <-->|"ISL / E Port"| CORE["Core Fabric\nsw-core-01"]
style D1 fill:#1c2333,stroke:#bc8cff,color:#e6edf3
style D2 fill:#1c2333,stroke:#bc8cff,color:#e6edf3
style HUB fill:#1c2333,stroke:#e3b341,color:#e3b341
style SW fill:#1c2333,stroke:#39d3c3,color:#39d3c3
style CORE fill:#1c2333,stroke:#58a6ff,color:#58a6ff
</div>
<div class="diagram-caption">Figure 4 — FL Port: the switch-side counterpart to a loop segment — one FL Port connects an entire FCAL segment to the fabric</div>
</div>
<div class="callout warning">
<div class="callout-icon">⚠️</div>
<div class="callout-content">
<div class="callout-title">Bandwidth Sharing on FL Port</div>
<div class="callout-text">All devices sharing an FL Port segment compete for the same bandwidth. In a high-I/O environment, this creates contention and performance bottlenecks. Modern designs eliminate this by giving every device its own direct F Port connection.</div>
</div>
</div>
</section>
<!-- ═══ S8: G Port ═══ -->
<section class="section" id="s8">
<div class="section-header">
<div class="section-icon icon-teal">⚡</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 08</div>
<h2>G Port — Generic Port</h2>
</div>
</div>
<p>The G Port (Generic Port) is the factory-default state of every physical port on an FC switch. When a new switch is powered on for the first time — before anything is connected to it — all its ports are in G Port mode. It is the blank slate from which all other switch-side port types emerge.</p>
<p>The moment a cable is connected and the discovery process starts, the port leaves G Port status and enters U Port (discovery phase), then transitions to its final type. If the switch is ever reset to factory defaults, all ports return to G Port state.</p>
<div class="callout tip">
<div class="callout-icon">🎓</div>
<div class="callout-content">
<div class="callout-title">Interview Tip — G Port vs U Port</div>
<div class="callout-text">G Port is the pre-connection default (nothing plugged in). U Port is the post-connection discovery state (cable inserted, device being identified). Both are transitional — neither carries active I/O traffic.</div>
</div>
</div>
<div class="grid-2">
<div class="card">
<div class="card-title">G Port</div>
<ul class="bullet-list">
<li>Switch powered on, no cable connected</li>
<li>Factory reset state</li>
<li>Waiting for a physical connection</li>
<li>No discovery process running</li>
</ul>
</div>
<div class="card">
<div class="card-title">U Port</div>
<ul class="bullet-list">
<li>Cable connected, device discovery running</li>
<li>FLOGI exchange in progress</li>
<li>Short-lived under normal conditions</li>
<li>Transitions to F, FL, or E Port when done</li>
</ul>
</div>
</div>
</section>
<!-- ═══ S9: E Port ═══ -->
<section class="section" id="s9">
<div class="section-header">
<div class="section-icon icon-orange">🔗</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 09</div>
<h2>E Port — Expansion Port (ISL)</h2>
</div>
</div>
<p>The E Port (Expansion Port) is the switch-side port type used to build Inter-Switch Links (ISLs) — the backbone connections that link multiple FC switches into a single logical fabric. Without E Ports and ISLs, each FC switch would be an isolated island.</p>
<p>When two physical switch ports — one from each switch — are connected by a cable and both are configured or detected as switch-to-switch connections, both ports become E Ports. The ISL they form carries fabric management traffic (RSCNs, routing tables) as well as data I/O between devices on different switches.</p>
<div class="svg-wrap">
<svg viewBox="0 0 720 260" xmlns="http://www.w3.org/2000/svg" style="width:100%;max-width:720px;display:block;margin:0 auto">
<!-- Switch A -->
<rect x="30" y="40" width="200" height="180" rx="12" fill="#1c2333" stroke="#f78166" stroke-width="2"/>
<text x="130" y="68" text-anchor="middle" font-family="Sora,sans-serif" font-size="13" font-weight="700" fill="#e6edf3">sw-core-01</text>
<text x="130" y="86" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">Domain ID: 1</text>
<!-- Ports on switch A -->
<rect x="50" y="100" width="70" height="28" rx="5" fill="#1c2333" stroke="#58a6ff" stroke-width="1"/>
<text x="85" y="118" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#58a6ff">F Port 1/1</text>
<rect x="50" y="140" width="70" height="28" rx="5" fill="#1c2333" stroke="#58a6ff" stroke-width="1"/>
<text x="85" y="158" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#58a6ff">F Port 1/2</text>
<!-- E Port on A -->
<rect x="196" y="110" width="16" height="30" rx="3" fill="#f78166" opacity="0.85"/>
<text x="180" y="195" font-family="JetBrains Mono,monospace" font-size="11" font-weight="700" fill="#f78166">E Port</text>
<!-- Switch B -->
<rect x="490" y="40" width="200" height="180" rx="12" fill="#1c2333" stroke="#f78166" stroke-width="2"/>
<text x="590" y="68" text-anchor="middle" font-family="Sora,sans-serif" font-size="13" font-weight="700" fill="#e6edf3">sw-core-02</text>
<text x="590" y="86" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#8b949e">Domain ID: 2</text>
<!-- Ports on switch B -->
<rect x="600" y="100" width="70" height="28" rx="5" fill="#1c2333" stroke="#3fb950" stroke-width="1"/>
<text x="635" y="118" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#3fb950">F Port 2/5</text>
<rect x="600" y="140" width="70" height="28" rx="5" fill="#1c2333" stroke="#3fb950" stroke-width="1"/>
<text x="635" y="158" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="10" fill="#3fb950">F Port 2/6</text>
<!-- E Port on B -->
<rect x="490" y="110" width="16" height="30" rx="3" fill="#f78166" opacity="0.85"/>
<text x="493" y="195" font-family="JetBrains Mono,monospace" font-size="11" font-weight="700" fill="#f78166">E Port</text>
<!-- ISL cable -->
<line x1="212" y1="125" x2="490" y2="125" stroke="#f78166" stroke-width="3" stroke-dasharray="8,4"/>
<polygon points="486,119 498,125 486,131" fill="#f78166"/>
<polygon points="216,119 204,125 216,131" fill="#f78166"/>
<text x="351" y="112" text-anchor="middle" font-family="JetBrains Mono,monospace" font-size="11" font-weight="700" fill="#f78166">ISL — Inter-Switch Link</text>
<!-- Label -->
<text x="360" y="250" text-anchor="middle" font-family="Inter,sans-serif" font-size="11" fill="#6e7681" font-style="italic">E Ports on both ends form the ISL — merging two switches into one logical fabric</text>
</svg>
<div class="diagram-caption">Figure 5 — E Port ISL: two switches exchange fabric-wide routing and RSCN data over an expansion port link</div>
</div>
<h3>ISL Design Considerations</h3>
<div class="callout success">
<div class="callout-icon">✅</div>
<div class="callout-content">
<div class="callout-title">Best Practice — ISL Oversubscription</div>
<div class="callout-text">Plan ISL bandwidth carefully. As a general rule, avoid oversubscribing ISLs beyond 7:1 (device ports to ISL ports). High-performance environments often use trunk groups (multiple parallel E Ports) to aggregate ISL bandwidth and provide redundancy.</div>
</div>
</div>
<div class="code-block">
<div class="code-header">
<div class="code-dots"><span class="dot-red"></span><span class="dot-ylw"></span><span class="dot-grn"></span></div>
<div class="code-lang">Brocade FOS — ISL Verification</div>
</div>
<div class="code-body"><span class="prompt">sw-core-01:admin></span> <span class="cmd">switchshow</span>
<span class="output">Index Slot Port Speed State Proto
----- ---- ---- ----- ----- -----</span>
<span class="hl"> 24 3 4 16G Online FC E-Port 10:00:00:27:f8:9a:1b:2c "sw-core-02" (downstream)</span>
<span class="output"> 25 3 5 16G Online FC F-Port 10:00:00:c0:dd:10:44:7e</span>
<span class="prompt">sw-core-01:admin></span> <span class="cmd">islshow</span>
<span class="output"> 1: 3/4-> 3/4 10:00:00:27:f8:9a:1b:2c "sw-core-02", 1 jumbo frame capable
sw-core-02 (fabric id=2)</span></div>
</div>
</section>
<!-- ═══ S10: VE / EX / VEX ═══ -->
<section class="section" id="s10">
<div class="section-header">
<div class="section-icon icon-purple">🌐</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 10</div>
<h2>VE Port, EX Port & VEX Port</h2>
</div>
</div>
<p>Beyond the core port types, three advanced variants extend the FC fabric across IP networks and FC router boundaries. These are encountered in multi-site storage replication, disaster recovery architectures, and metro-area SAN extension scenarios.</p>
<h3>VE Port — Virtual E Port (FCIP)</h3>
<p>A VE Port behaves functionally like an E Port but tunnels FC traffic across an IP network using the FCIP (Fibre Channel over IP) protocol. This allows two geographically separated FC fabrics to appear as a single logical fabric without requiring a dedicated dark fiber connection between sites.</p>
<div class="diagram-wrap">
<div class="mermaid">
flowchart LR
subgraph SiteA["Site A — Primary DC"]
SWA["FC Switch\nsw-dc1-01"] -->|"VE Port"| GWA["FCIP Gateway\ngw-dc1-01"]
end
GWA <-->|"IP WAN / MPLS\n10.74.20.0/30"| GWB
subgraph SiteB["Site B — DR DC"]
GWB["FCIP Gateway\ngw-dc2-01"] -->|"VE Port"| SWB["FC Switch\nsw-dc2-01"]
end
style SWA fill:#1c2333,stroke:#39d3c3,color:#e6edf3
style GWA fill:#1c2333,stroke:#bc8cff,color:#bc8cff
style GWB fill:#1c2333,stroke:#bc8cff,color:#bc8cff
style SWB fill:#1c2333,stroke:#39d3c3,color:#e6edf3
</div>
<div class="diagram-caption">Figure 6 — VE Port: FC traffic tunneled across an IP WAN using FCIP — fabric extension to a DR site</div>
</div>
<h3>EX Port — FC Router Expansion Port</h3>
<p>EX Ports connect a standard FC switch to an FC Router. Unlike E Ports — which merge two switches into the same fabric — EX Ports maintain fabric isolation while selectively routing traffic between separate fabrics. This is critical for environments where fabric separation must be preserved for isolation or compliance reasons.</p>
<h3>VEX Port — Virtual EX Port</h3>
<p>VEX Ports combine the characteristics of EX Ports with the IP-based transport of VE Ports. They connect two isolated FC fabrics across an IP network through an FC router, with the transport layer being IP rather than native FC.</p>
<div class="card">
<div class="card-title">📊 Advanced Port Type Comparison</div>
<table class="spec-table">
<thead><tr><th>Port Type</th><th>Transport</th><th>Fabric Scope</th><th>Primary Use Case</th></tr></thead>
<tbody>
<tr><td><span class="badge badge-orange">E Port</span></td><td>Native FC</td><td>Merges fabrics (same domain space)</td><td>Switch-to-switch within same site</td></tr>
<tr><td><span class="badge badge-purple">VE Port</span></td><td>IP / FCIP</td><td>Merges fabrics over WAN</td><td>Multi-site fabric extension</td></tr>
<tr><td><span class="badge badge-orange">EX Port</span></td><td>Native FC</td><td>Isolated fabrics (no merge)</td><td>FC router fabric boundary</td></tr>
<tr><td><span class="badge badge-purple">VEX Port</span></td><td>IP / FCIP</td><td>Isolated fabrics over WAN</td><td>Remote FC router via IP</td></tr>
</tbody>
</table>
</div>
<div class="callout tip">
<div class="callout-icon">🎓</div>
<div class="callout-content">
<div class="callout-title">Who Deals With These?</div>
<div class="callout-text">VE, EX, and VEX ports are primarily the domain of SAN architects who design multi-site replication and disaster recovery networks. Day-to-day SAN administrators rarely configure these directly. Understanding their purpose conceptually is sufficient for most operational and interview contexts.</div>
</div>
</div>
</section>
<!-- ═══ S11: Discovery Workflow ═══ -->
<section class="section" id="s11">
<div class="section-header">
<div class="section-icon icon-blue">🔄</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 11</div>
<h2>Port Discovery Workflow — End to End</h2>
</div>
</div>
<p>Understanding how a switch auto-configures its port type helps demystify what happens every time a cable is connected. The following sequence describes the full discovery lifecycle from physical connection to operational state.</p>
<div class="diagram-wrap">
<div class="mermaid">
sequenceDiagram
participant Admin as 👤 Admin
participant Port as Switch Port
participant SW as FC Switch
participant Dev as Connected Device
Admin->>Port: Connect cable
Port->>SW: Signal detected on port
SW->>Port: Set port → G Port (if idle) then U Port (discovery)
SW->>Dev: Send FLOGI (Fabric Login)
Dev-->>SW: FLOGI response with N_Port_ID
SW->>SW: Identify device class
alt Direct Host or Storage
SW->>Port: Classify as F Port
SW-->>Dev: Assign 24-bit FCID address
else Hub / Loop Segment
SW->>Port: Classify as FL Port
SW-->>Dev: Assign ALPA within loop
else Another FC Switch
SW->>Port: Classify as E Port
SW-->>Dev: Exchange RSCNs and routing tables
end
Port-->>Admin: Port online — operational
</div>
<div class="diagram-caption">Figure 7 — Full port discovery sequence: from cable insertion to operational port type assignment</div>
</div>
<ul class="step-list">
<li><div class="step-num">1</div>Cable connected → switch detects physical signal on the port.</li>
<li><div class="step-num">2</div>Port enters <strong>G Port</strong> → <strong>U Port</strong> transition; discovery process begins.</li>
<li><div class="step-num">3</div>Switch transmits a FLOGI (Fabric Login) to the far-end device.</li>
<li><div class="step-num">4</div>Device responds with its N_Port identifier and capability set.</li>
<li><div class="step-num">5</div>Switch evaluates the response and classifies the port as F, FL, or E.</li>
<li><div class="step-num">6</div>Port becomes operational; the device receives its fabric address (FCID or ALPA).</li>
</ul>
</section>
<!-- ═══ S12: Quick Reference ═══ -->
<section class="section" id="s12">
<div class="section-header">
<div class="section-icon icon-green">📊</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 12</div>
<h2>Quick Reference — All Port Types</h2>
</div>
</div>
<table class="spec-table">
<thead>
<tr><th>Port</th><th>Full Name</th><th>Where It Lives</th><th>Condition</th><th>Paired With</th></tr>
</thead>
<tbody>
<tr>
<td><span class="badge badge-blue">N</span></td>
<td>Node Port</td>
<td>Host / Storage HBA or FCA</td>
<td>Direct connection to switch</td>
<td><span class="badge badge-green">F Port</span></td>
</tr>
<tr>
<td><span class="badge badge-yellow">NL</span></td>
<td>Node Loop Port</td>
<td>Host / Storage HBA or FCA</td>
<td>Connected via hub / FCAL loop</td>
<td><span class="badge badge-purple">FL Port</span></td>
</tr>
<tr>
<td><span class="badge badge-teal">U</span></td>
<td>Universal Port</td>
<td>FC Switch</td>
<td>Transient — device being discovered</td>
<td>Transitions to F, FL, or E</td>
</tr>
<tr>
<td><span class="badge badge-green">F</span></td>
<td>Fabric Port</td>
<td>FC Switch</td>
<td>Device directly connected</td>
<td><span class="badge badge-blue">N Port</span></td>
</tr>
<tr>
<td><span class="badge badge-purple">FL</span></td>
<td>Fabric Loop Port</td>
<td>FC Switch</td>
<td>Hub or FCAL segment connected</td>
<td><span class="badge badge-yellow">NL Port</span></td>
</tr>
<tr>
<td><span class="badge badge-teal">G</span></td>
<td>Generic Port</td>
<td>FC Switch</td>
<td>Default — no device connected yet</td>
<td>None (becomes U, then other)</td>
</tr>
<tr>
<td><span class="badge badge-orange">E</span></td>
<td>Expansion Port</td>
<td>FC Switch</td>
<td>Another FC switch connected (ISL)</td>
<td><span class="badge badge-orange">E Port</span> (other switch)</td>
</tr>
<tr>
<td><span class="badge badge-purple">VE</span></td>
<td>Virtual E Port</td>
<td>FC Switch / FCIP Gateway</td>
<td>FCIP tunnel to remote fabric</td>
<td><span class="badge badge-purple">VE Port</span> (remote)</td>
</tr>
<tr>
<td><span class="badge badge-orange">EX</span></td>
<td>FC Router E Port</td>
<td>FC Switch / Router</td>
<td>Connected to FC router boundary</td>
<td>FC Router</td>
</tr>
<tr>
<td><span class="badge badge-purple">VEX</span></td>
<td>Virtual EX Port</td>
<td>FC Switch / FCIP Gateway</td>
<td>FCIP tunnel + FC router boundary</td>
<td>Remote FC Router</td>
</tr>
</tbody>
</table>
<div class="callout teal">
<div class="callout-icon">🧩</div>
<div class="callout-content">
<div class="callout-title">Memory Trick — N vs NL & F vs FL</div>
<div class="callout-text">The "L" suffix always means <strong>Loop</strong>. NL = Node on a Loop. FL = Fabric port facing a Loop. If there is no "L" in the port name, the connection is direct with no loop topology involved. This single rule eliminates confusion between the N/NL and F/FL pairs.</div>
</div>
</div>
</section>
<!-- ═══ S13: Interview Q&A ═══ -->
<section class="section" id="s13">
<div class="section-header">
<div class="section-icon icon-purple">🧠</div>
<div class="section-title-wrap">
<div class="section-num">SECTION 13</div>
<h2>Interview Q&A — Scenario-Based</h2>
</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q1. A storage administrator connects a new host to an FC switch. After a few seconds, the port shows as "F Port — Online." What happened during those few seconds?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Reveal Answer</button>
<div class="quiz-a">When the cable was connected, the switch detected a physical signal and transitioned the port from G Port (default idle) to U Port (universal/discovery state). The switch then initiated a FLOGI (Fabric Login) exchange with the host HBA. The HBA responded with its N_Port_ID and capability parameters, identifying itself as a direct-attached device rather than a switch or a loop hub. The switch completed the identification and classified the switch-side port as an F Port, assigned the host a 24-bit FCID address, and the port transitioned to Online. The host-side port became an N Port simultaneously.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q2. What is the functional difference between an E Port and a VE Port, and when would you use one versus the other?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Reveal Answer</button>
<div class="quiz-a">Both E Port and VE Port serve the same logical purpose — connecting two FC switches so they function as a single fabric. The difference is the transport layer. An E Port uses native Fibre Channel signaling over dedicated FC cable or optics. A VE Port uses FCIP (Fibre Channel over IP), tunneling FC frames inside IP packets over a standard IP network such as Ethernet, MPLS, or a WAN link. E Ports are used within a single data center or campus where direct FC cabling is practical. VE Ports are used when the two switches are in different geographic locations (separate buildings or cities) and a dedicated FC fiber connection is not available or cost-effective.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q3. A port on your FC switch is stuck in U Port state and will not progress to F Port. What are the likely causes?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Reveal Answer</button>
<div class="quiz-a">A port stuck in U Port means the FLOGI exchange did not complete successfully. Common causes include: (1) Incompatible SFP — the transceiver type or speed may not match between the switch and HBA; (2) Physical layer problem — a bent fiber connector, a dirty/contaminated SFP, or an incorrect cable type (multimode vs single-mode) causes the optical signal to be too weak for login; (3) HBA driver issue — the host HBA driver may have crashed or failed to initialize, preventing it from responding to FLOGI; (4) Speed mismatch — if both ends are set to fixed speed and are set to different values, negotiation fails; (5) Port buffer misconfiguration — insufficient port buffers assigned for the expected distance. Start troubleshooting with physical inspection, then check switch logs and HBA driver status on the host.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q4. Why does an NL Port share bandwidth with other devices, but an N Port does not?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Reveal Answer</button>
<div class="quiz-a">An N Port has a dedicated point-to-point link directly to its matching F Port on the switch. The full bandwidth of that link is exclusively available to that single device — no other device competes for it. An NL Port is part of an FC Arbitrated Loop (FCAL), where multiple devices share a single ring of cable and a single FL Port connection to the switch. Because only one device can transmit on the loop at a time (they must arbitrate for loop access), all attached devices compete for the same aggregate bandwidth of the single FL Port uplink. Adding more NL Port devices to the same loop segment degrades per-device throughput proportionally.</div>
</div>
<div class="quiz-card">
<div class="quiz-q">Q5. How does EX Port differ from E Port in terms of fabric isolation?</div>
<button class="quiz-btn" onclick="this.nextElementSibling.style.display='block';this.style.display='none'">Reveal Answer</button>
<div class="quiz-a">An E Port merges two FC switches into the same fabric — they share a common Domain ID space, the same RSCN propagation, and devices on either switch can see and communicate with each other directly. An EX Port, by contrast, connects a switch to an FC Router while keeping the two fabrics logically isolated. The FC Router selectively forwards traffic between fabrics using proxy N_Port IDs without merging the fabric address spaces. This isolation is valuable in environments where storage resources must be shared across fabrics (for example, in a service provider or multi-tenant environment) without allowing unrestricted cross-fabric visibility.</div>
</div>
</section>
<!-- ═══ AUTHOR ═══ -->
<section class="section" id="author">
<div class="author-card">
<div class="author-avatar">👨💻</div>
<div class="author-name">Mohammed Abdul</div>
<div class="author-title">Data Protection Architect · 10+ Years Experience</div>
<p class="author-bio">Mohammed Abdul is a Data Protection Architect with more than a decade of experience in Hybrid Cloud and enterprise storage infrastructure, having worked with global clients across financial services, healthcare, and manufacturing sectors. He specializes in designing and implementing SAN fabrics, data replication, and backup ecosystems for mission-critical workloads.</p>
<div class="tech-badges">
<span class="tech-badge">Fibre Channel</span>
<span class="tech-badge">NetApp ONTAP</span>
<span class="tech-badge">Brocade FOS</span>
<span class="tech-badge">AWS</span>
<span class="tech-badge">Azure</span>
<span class="tech-badge">Commvault</span>
<span class="tech-badge">Veeam</span>
<span class="tech-badge">NetBackup</span>
</div>
<a class="contact-link" href="mailto:abdul.md.20000102@gmail.com">✉️ abdul.md.20000102@gmail.com</a>
<div class="callout warning" style="margin-top:24px;margin-bottom:0">
<div class="callout-icon">📌</div>
<div class="callout-content">
<div class="callout-title">Disclaimer</div>
<div class="callout-text">This article is published for knowledge-sharing and educational purposes only. All IP addresses, hostnames, switch names, and domain identifiers referenced in examples are entirely fictional and used solely for illustration. Always consult official vendor documentation and your organization's change management process before implementing changes in any production environment. The author is not affiliated with or endorsed by Broadcom, Cisco, or any switch or storage vendor referenced. All product names are trademarks of their respective owners.</div>
</div>
</div>
</div>
</section>
</div><!-- /content-area -->
</div><!-- /main-content -->
<script>
window.addEventListener('scroll', () => {
const el = document.getElementById('reading-progress');
const h = document.documentElement.scrollHeight - window.innerHeight;
el.style.transform = `scaleX(${Math.min(window.scrollY / h, 1)})`;
});
const sections = document.querySelectorAll('.section');
const links = document.querySelectorAll('.toc-link');
const obs = new IntersectionObserver(entries => {
entries.forEach(e => {
if (e.isIntersecting) {
links.forEach(l => l.classList.remove('active'));
const a = document.querySelector(`.toc-link[href="#${e.target.id}"]`);
if (a) a.classList.add('active');
}
});
}, { threshold: 0.2 });
sections.forEach(s => obs.observe(s));
mermaid.initialize({
startOnLoad: true, theme: 'dark',
themeVariables: {