Dc Ccna Fc Intro

8/10/2019 Dc Ccna Fc Intro

1/66


2/66

2013 Cisco and/or its affiliates. All rights reserved.

Data Center Techno

1.0 Cisco data center fundamental concepts

Describe network architectures for the data center (LAN, SAN)

Describe the modular approach in network design

Describe the data center core layer

Describe the data center aggregation layer

Describe the data center access layer

Describe the collapse core model

Describe Cisco FabricPath

Identify key differentiator between DCI and network interconnectivity

Describe, configure, and verify vPC

Describe the functionality ofand configure port channels

Describe and configureVDC

Describe the edge and core layers of the SAN

Describe the Cisco Nexus product family

Configureand verify network connectivity

Identify control and data plane traffic

Perform initial setup

2.0 Data center unified fabric

Describe FCoE

Describe FCoE multihop

Describe VIFs

Describe FEX products


3.0 Storage networking

Describe the initiator target

Verify SAN switch operations

Describe basic SAN connectivity

Describe the different types of storage array connectivity

Verify name server login

Describe, configure, and verify zoning


Describe, configure, and verify VSAN

4.0 Data center virtualization

Describe device virtualization

Describe server virtualization

Describe the Cisco Nexus 1000V Switch

Verify initial setup and operation for the Cisco Nexus 1000

5.0 Unified computing

Describe the Cisco UCS product family

Describe the Cisco UCS Manager

Describe, configure, and verify cluster configurationDescribe and verify discovery operation

Describe, configure, and verify connectivity


Describe the key features of the Cisco UCS Manager

6.0 Data center network services

Describe standard Cisco ACE features for load balancing

Describe server load-balancing virtual context and high av

Describe server load-balancing management options

Describe the benefits of the Cisco Global Load Balancing

Describe how the Cisco Global Load Balancing Solution inCisco load balancers

Describe the Cisco WAAS need and advantages in the da


3/66


Discussion of the FC layers and what each layer is comprised of

Understand various Fiber Channel Topologies

Understanding VSANs and the different port types on a Fiber channel switch

Discuss Fiber Channel Addressing

Understand class of service and Flow control mechanisms

Discuss Fiber channel Login process

Basic Zoning concepts

Understanding NPV-NPIV

Discuss the switched fabric and how switches interconnect


4/66



5/66


Fibre Channel!What Is It?

Fibre Channel

! Circuit & packet switched

! Reliable transfers

! High data integrity

! High data rates

! Low latency

! High connectivity

! Long distance

Blends characteristics ofI/O channels & networks

! Connection service

! Physical circuits

! Reliable transfers

! High speed

! Low latency

!

Short distance! Hardware intensive

I/O Channels

! Connectionle

! Logical circui

! Unreliable tra

! High connect

! Higher latenc

! Longer distan

! Software inte


6/66


SStorage

! Disks -TARGETS

! Tapes

! Optical (e.g. DVD) etc.

!!to Servers & Mainframes - INIT

AArea

! In the Data Centre

! Server Room

!Between Data Centres

N Network! Fibre Channel & FICON

! iSCSI

! FCIP (and iFCP)

!And now Fibre Channel over E

Storage Area Networks


7/66


F

F

B

S

IEEE 802.2

Link Encapsulation

(FC-LE)

ULP(Upper Level Protocol)

(SampleThere Are More) SCSI-3

SCSI-3 Mapping

(SCSI-FCP)FC-4

SNMP Mapping

(FC-SNMP)

FC-3 Common Services

FC-0

FC-1

FC-2Fibre Channel Physical and

Signaling Interface

(FC-PH, FC-PH2,

FC-PH3)Physical Interface

Encode/Decode

Framing Protocol FC-AL FC-A

Copper Optic

8B/10B Encoding


8/66


Structure Is Divided into Five Levels of Functionality

FC-0 defines the physical interface characteristics

Signaling rates, cables, connectors, distance capabilities, etc.

FC-1 defines how characters are encoded/decoded for transmission

Transmission characters are given desirable characters

FC-2 defines how information is transported

Frames, sequences, exchanges, login sessions

FC-3 is a place holder for future functions

FC-4 defines how different protocols are mapped to use Fibre Channel

SCSI, IP, virtual interface architecture, others



Fibre Channel Topologies

Switched Fa

Arbitrated Loop (FC-AL)

Point-to-Point

hub



Ethernet!

Is non-deterministic.

Flow control is destination-based

Relies on TCP drop, retransmit and sliding

window mechanisms

Spanning tree for loop avoidance

Key services are an add-on

Fibre-Channel!

Is deterministic.

Flow control is source-basmechanism)

Key services are integrate

No loop issues

In-built routing with FSPF



Standard Fibre Channel Port Types

N_port: Node ports used to connect devices to switched fabric or point topoint configurations.

F_port: Fabric ports residing on switches connecting Nport devices

L_port: Loop ports are used in arbitrated loop configurations to buildnetworks without FC switches.

NL_ports: Loop ports often also have Nport capabilities as well

FL_ports: Switch ports that connect to a set an Arbitrated Loop

E_port: Expansion ports are essentially are used to connect two FibreChannel switches

G_port: A generic port capable of operating as either an Eor Fport. Itsalso capable of acting in an Lport capacity. Uses auto discoveryto select mode.


14/66


Fibre Channel Port Types

TE_port: Trunk Expansion ports are essentially trunk ports which are used toconnect two Fibre Channel switches. They carry multiple vsan traffic.

NP Port: NP ports are N ports connected to an NPV switch in an NPV-NPIVconnections.

TNP Port: TNP ports are trunking enabled NPV port.

TF port: TF ports are trunking enabled F ports on an NPIV core switch.These ports are generally used in NPV-NPIV connections.


15/66


G_Port

G_Port

E_Port

F_Port

F_Port

E_Port

N_Port

N_Port

More on Fibre Channel Port TypesIncluding some newer, vendor specific terms/types

Fibre Channel Switch

NPSwit

F_Port NP_PortFabric Switch

MDS/Brocade

TE_PortFabricSwitch

TE_Port

End No

EndNode


16/66


Typically, a host is known as an initiator, while the storage and tape units are considere

The initiator is the device that initiates the traffic. The target is the device that the commto. For example, a storage device that is SAN attached, will never send data to the hos

(initiator) sends a command to the (target).

Some intelligent storage arrays will act as as both a target, when the host is sending co

as an initiator, when it is sending commands to a remote array (as in a replication enviro


17/66


Virtual SANs (VSANs)Fabric Separation Building Virtual Fabrics

VSANs

Provides a method to allocate ports within a Physical Fabricand create Virtual Fabrics

Analogous to VLANs in Ethernet

Virtual fabrics created from larger physical fabric

Reduces wasted ports of a SAN island approach

Fabric events are isolated per VSANwhich gives furtherisolation for High Availability

Statistics can be gathered per VSAN

VSANs supported on M

UCS Produ


18/66


VSAN is a Virtual Storage Area Network. Each MDS can be part of multiple VSANs. Dethe same VSAN to be capable of communication. MDS switch ports are assigned to VSA

result is that the devices that attach to the MDS are placed into that VSAN. VSANs are cinterfaces assigned to the VSANs.

VSAN 323

VSAN 323Domain 0x16

TSI-9710# config tEnter configuration commands, one per line. End TSI-9710(config)# vsan database

TSI-9710(config-vsan-db)# vsan 323

TSI-9710(config-vsan-db)# vsan 323 interface fc 2

TSI-9710(config-vsan-db)#

TSI-9710# show flogi database--------------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME

--------------------------------------------------------------------------------fc2/3 323 0x160000 10:00:00:00:00:11:00:00 10:00:00:00:00:00:11:00

fc4/3 344 0xe20000 10:00:00:00:00:12:00:00 10:00:00:00:00:00:12:00

Total number of flogi = 2.

FC 2/3

VSAN 344Domain 0xe2


19/66


When an ISL link comes up, the MDS/N5K will try to merge the VSAN on each end, into a sThere are rules that govern if the merge can successful or not.

- VSAN must be configured on each side

- VSAN must be permitted to cross the link- Domain ID for the VSAN must be unique in the 2 switches

-

No zoning conflicts can exist.

VSAN 323Domain 0x16

FC 2/3

MDS-1-95# sh int fc 1/17fc1/17 is trunkingAdmin port mode is auto, tru

Port mode is TEPort vsan is 1

Speed is 4 Gbps

Rate mode is dedicatedTransmit B2B Credit is 16

Receive B2B Credit is 16Receive data field Size is

Trunk vsans (admin allowedTrunk vsans (up) Trunk vsans (isolated)

Trunk vsans (initializing)

FC1/17

VSAN 323Domain 0x44


20/66



21/66


How do we identify devices in a SAN?

Can I use the MAC address as an identity?

What do I need to start communication?

Can IP address be used to send FC frames?


22/66


Fibre Channel NamingFor unique device identification, Fibre Channel uses 64-bit Node Names

20:01:00:05:30:01:97:43

If it uses an IEEE OUI ranges, its a World Wide Name (WWN)

Device with N_Portshave World Wide Node Name Cisco refer to this as a nWWN (others use WWNN o

N_Portsassociated with a WWN are assigned a unique World Wide Port Name Cisco refer to this a theWWPN or WWpN)

pWWNs are the same format as nWWN and derived from it.

It is the pWWN that is used as the unique identifier in the fabric mapped to FC addresses

Switches have Node Names (sWWN);

Switch ports have fabric port names (fWWN)

nWWNpWWN1

pWWN2

pWWN1

pWWN2

fWWN1 fWWN2

WWN is not the

It is not used in forwar

sWWN2


23/66


Switch Topology Model

SwitchDomain Area

P

Fabric Channel ID (FCID)

Fibre Channel Addressing Scheme

24-bit FCIDassigned to every WWN correspondingto an N_Port

FCIDis assigned when a device joins the fabric(see FLOGI later)

FCID made up of switch domain, area and port(device)

! Domain ID represent a single FC switch

!Limit of Domain IDs in a single fabric theoretical max of239

Frame forwarding decisions are based on Domain ID- the first 8 bits of FCID

FC Fabric

Domain ID10

Domain ID11

FC10.0


24/66


Idles* SOF Frame Header Data Field CRC E

General FC-2 Frame Format

Frame Content

0-528 Transmission Word

(4)(0-2112)(24)(4)

Fibre Channel Frame Format

All FC frames follow the general frame format as shown below

Idles are Ordered Sets used for synchronization and basic signaling

SOF Start-of-Frame, EOF End-of-Frame

* 6 Idle words (24 bytes) requires by TX

2 Idle words (8 bytes) guaranteed to RX


25/66


R_CTL Routing D_ID 24bits Destination

78

15

16

23

24

31Word

0

1

2

3

4

5

S_ID 24 bits SourceCS_CTL 8 bits ClassSpec

TYPE 8 bitsData structure

SEQ_ID 8 bitsDF_CTL 8 bitsData field

F_CTL 24 bits Frame Control

SEQ_CNT 16 bits Sequence Count

OX_ID 16 bits Originator Exch ID RX_ID 16 bits Responder Exch ID

Parameter Specific to frame type


26/66


27/66


Sequence 2

Sequence 3

Sequence 1

Cnt 1

Cnt 2

Cnt 1

Cnt 1

Cnt 3

TSI

TSI

TSI = Transfer Sequence Initiative


28/66



29/66



30/66


31/66


32/66


Sequence Initiator SequenceRecipient

Fabric

R_RDYR_RDY

BB_C BB_C

TX Buf

T

TX Buf

TX Buf

RX Buf

RX BufRX

RX Buf

SOFi3


33/66


Sequence Initiator SequenceRecipient

Fabric

ACK

R_RDYR_RDY

R_RDY

R_RDYACK

EE_Credit

BB_C BB_C

TX Buf

T

TX Buf

TX Buf

RX Buf

RX Buf

RX

RX Buf

SOFi2


34/66


Switch Switch

SOFiF

ACK

R_RDY

R_RDY


35/66



36/66


FFFFFEWell-known address of login serverBasic responsibility to assign FCID

FFFFFCWell-known address of fabric directory name server

Basic responsibility registration of devices and distribution of database

FFFFFDWell-known address of fabric controller

Basic duties responsible for managing fabric, initialization, FSPF routing, responsible for Rfor SCNs

FC Standards T11-http://www.t11.org/t11/docreg.nsf/draftlr


37/66


My Port is up... Lets TalkFLOGIs & PLOGIs

Step 1: Fabric Login (FLOGI)

!

Exchanges Service Parameters with the Fabric

! Switch identifies the WWNin the service parameters of the acceptframe and assigns a Fibre Channel ID (FCID)

! Initializes the buffer-to-buffercredits

Step 2: Port Login (PLOGI)

! Required between node and the name server database of the switch to

register itself.! Similar to FLOGI transports a PLOGI frame to the designation N_Port

! In p2p topology (no fabric present), initializes buffer-to-buffer credits

Step 3: Process Login (PRLI)

! Required between two nodes to communicate to each other.

FC Fabric

FCID


38/66


FLOGI - Fabric Login

Issued by N_Port to destination FF FF FEto

Determine if Fabric is Present Establish a session with the Fabric

Exchange Service Parameters with the Fabric

FLOGI ACCEPT assigns N_Ports 24 bit address to N_Port .


39/66


Fibre Channel

R_CTL: 0x22

Dest Addr: ff.ff.fe

CS_CTL: 0x00

Src Addr: 00.00.00

Type: Ext Link Svc (0x01)

F_CTL: 0x290000 (Exchange Originator,

Seq Initiator,Exchg First, Seq Last,

Transfer Seq Initiative,

Last Data Frame - No Info, ABTS - Abort/MS, )

SEQ_ID: 0x00

DF_CTL: 0x00

SEQ_CNT: 0

OX_ID: 0x008e

RX_ID: 0xffff

Parameter: 0x00000000

FC ELS

Cmd Code: FLOGI (0x04)

Common Svc Parameters

B2B Credit: 4

Common Svc Parameters: 0x0 (Alt B2B Credit Mgm0000 .... = BB_SC Number: 0

.... 1000 0000 0000 = Receive Size: 2048

Max Concurrent Seq: 18

Relative Offset By Info Cat: 20352

E_D_TOV: 0

N_Port Port_Name: 10:00:00:01:73:00:94:84 (00

Fabric/Node Name: 10:00:00:01:73:00:94:84 (00Class 1 Svc Parameters

Service Options: 0x0(Class Not Supported)

Class 2 Svc Parameters



Service Options: 0x8800(Seq Delivery Requeste

Initiator Control: 0x0(Seq Delivery RequestedRecipient Control: 0x0(Seq Delivery RequestedClass Recv Size: 0

Total Concurrent Seq: 0

End2End Credit: 0

Open Seq Per Exchg: 0



Vendor Version: 00000000000000000000000000000000

Notice SID

F_CTL bits

Class 3

only

My receive

credit


40/66


Fibre Channel

R_CTL: 0x23

Dest Addr: 7e.00.00

CS_CTL: 0x00

Src Addr: ff.ff.fe


F_CTL: 0x980000 (Exchange Responder,Seq Initiator, Exchg Last,Seq Last,CS_CTL, Last Data Frame - No Info, ABTS - Abort/MS, )

SEQ_ID: 0x00

DF_CTL: 0x00

SEQ_CNT: 0

OX_ID: 0x008e

RX_ID: 0x3d32


FC ELS

Cmd Code: ACC (0x02)


B2B Credit: 12

Common Svc Parameters: 0x1300 (Alt B2B Credit 0000 .... = BB_SC Number: 0

.... 1000 0100 0000 = Receive Size: 2112

Max Concurrent Seq: 0Relative Offset By Info Cat: 10000

E_D_TOV: 2000

N_Port Port_Name: 20:41:00:05:30:00:51:1e (00

Fabric/Node Name: 20:01:00:05:30:00:51:1f (00Class 1 Svc Parameters



Service Options: 0x8800(Seq Delivery RequesteInitiator Control: 0x0(Seq Delivery Requested

Recipient Control: 0x0(Seq Delivery RequestedClass Recv Size: 0


End2End Credit: 0

Open Seq Per Exchg: 0Class 3 Svc Parameters

Service Options: 0x8800(Seq Delivery RequesteInitiator Control: 0x0(Seq Delivery Requested

Recipient Control: 0x0(Seq Delivery RequestedClass Recv Size: 0


End2End Credit: 0




Vendor Version: 00000000000000000000000000000000

Notice DID

This is

your FCID

F_CTL bits

Class 2 & 3

supported

My receive

credit


41/66


PLOGI N_Port Login

Established sessions between two N-Ports

Required before Upper Level protocol operations can begin

N_Port will register to the Name Server FF FF FCin Fabric with all required log

N_Port will then query Name Server for other N_Ports on the Fabric.


42/66


Fibre Channel

R_CTL: 0x22

Dest Addr: ff.ff.fc

CS_CTL: 0x00

Src Addr: 7e.00.00


F_CTL: 0x290000 (Exchange Originator, Seq Initiator, ExchgFirst, Seq Last, CS_CTL, Transfer Seq Initiative, Last DataFrame - No Info, ABTS - Abort/MS, )

SEQ_ID: 0x00

DF_CTL: 0x00

SEQ_CNT: 0

OX_ID: 0x0095

RX_ID: 0xffff


Notice

D_ID

Notice much of the service

parameters exchanged are the

same

FC ELS

Cmd Code: PLOGI (0x03)


B2B Credit: 4

Common Svc Parameters: 0x8000 (Cont. Incr. OSupported, Alt B2B Credit Mgmt, E_D_TOV ResoNormal SEQCNT rules, Payload Len=116 bytes)

0000 .... = BB_SC Number: 0

.... 1000 0000 0000 = Receive Size: 2048

Max Concurrent Seq: 255

Relative Offset By Info Cat: 0

E_D_TOV: 500

N_Port Port_Name: 10:00:00:01:73:00:94:84 (0Fabric/Node Name: 10:00:00:01:73:00:94:84 (0





Class 3 Svc ParametersService Options: 0x8000(Non-zero CS_CTL Mayb

Initiator Control: 0x0(Initial P_A Not Suppo

Recipient Control: 0x0(ACK_0 Not Supported, Policy: Discard Policy only)

Class Recv Size: 2048


End2End Credit: 0




Vendor Version: 00000000000000000000000000000000


43/66


Fibre Channel

R_CTL: 0x23

Dest Addr: 7e.00.00

CS_CTL: 0x00

Src Addr: ff.ff.fc


F_CTL: 0x980000 (Exchange Responder, Seq Initiator, Exchg Last,Seq Last, CS_CTL, Last Data Frame - No Info, ABTS - Abort/MS, )

SEQ_ID: 0x00

DF_CTL: 0x00

SEQ_CNT: 0

OX_ID: 0x0095

RX_ID: 0x3d37


FC ELS

Cmd Code: ACC (0x02)


B2B Credit: 0

Common Svc Parameters: 0xc800 (Cont. Incr. OffsSupported, RRO Supported, Normal B2B Credit

E_D_TOV Resolution in ms, Normal SEQCNT rul

Payload Len=116 bytes)

0000 .... = BB_SC Number: 0

.... 1000 0100 0000 = Receive Size: 2112

Max Concurrent Seq: 128Relative Offset By Info Cat: 255

E_D_TOV: 2000

N_Port Port_Name: 24:8d:00:05:30:00:51:1e (00:0

Fabric/Node Name: 20:01:00:05:30:00:51:1f (00:0




Service Options: 0x8000(Non-zero CS_CTL Maybe T

Initiator Control: 0x0(Initial P_A Not Supporte

Recipient Control: 0x0(ACK_0 Not Supported, ErrDiscard Policy only)


Total Concurrent Seq: 64End2End Credit: 8

Open Seq Per Exchg: 1Class 3 Svc Parameters

Service Options: 0x8000(Non-zero CS_CTL Maybe T

Initiator Control: 0x0(Initial P_A Not Supporte

Recipient Control: 0x0(ACK_0 Not Supported, ErrDiscard Policy only)



End2End Credit: 0




Vendor Version: 00000000000000000000000000000000


44/66


Fabric F_PortLogin ServerX

FF FF FE

64-Bit Node WWN64-Bit Port WWN

FLOGI

Accept

RegistrationInformation

PLOGI

Accept

Registrationfor State Changes

SCRFabric ControllerX

FF FF FD

Accept

Name Server Query

Accept

Address Discovery forSCSI Storage Devices

Host System N_Node

By Registering for State-Change Notifications the Port or Domain Controller Can

Then Notify the Connected Ports with RSCNs When a Port Changes; State-Change Notifications W

Zone

Name ServerX

FF FF FC

Name ServerX

FF FF FC

24-Bit Port ID


45/66


46/66



47/66


What is Zoning

Fabric Zoning Access Control for the Fabric

Zonesdefine who can talk to who in a Fabric

Only members of the same Zone can exchange PLOGIs and thuscommunicate

! Devices can be members of more than one zone

! Default zoning is policy is deny No communications possibleunless in a zone

Zones belong to a zoneset

Zoneset must be active to enforce zoning

Only one active zoneset per fabric or per VSAN

zone name EXAMPLE_Zonefcid 0x10.00.01 [pwwn 10:00:00:00:c9:76:fd:31] [initiator]fcid 0x11.00.01 [pwwn 50:06:01:61:3c:e0:1a:f6] [target] pWWN = 10:00:00:00

pWWN= 50

Domain ID10

Domain ID11

FC10.0


48/66


Disk port is a member of both zones

Hosts are members of a single zone


49/66


Switch

interface

FCFCFC

FCFC

Domain

0x06

7/16

2/1

FCID = 0x060100

PWWN = 20:0d:12:55:26:8f:34:cb FCID = 0x060600

PWWN = 20:0d:67:fc:3d:67:10

FWWN = 20:21:00:0d:ec:0f:b4:c0 FWWN = 20:91:00:0d:ec:0f:b

FWWN = fabric port

WWN

FCID that is

assigned during

FLOGI

PWWN = Device port

WWN


50/66


TSI-9710# show zoneset active

zoneset name zs21 vsan 21

zone name zone_one vsan 21* fcid 0x1d0000 [pwwn 10:00:00:00:00:11:00:00]

* fcid 0xe80000 [pwwn 10:00:00:00:00:13:00:00]

zone name zone_two vsan 21

* fcid 0x1d0001 [pwwn 20:00:00:00:00:11:00:00]

pwwn 20:00:00:00:00:13:00:00

zoneset name zs22 vsan 22

zone name zone_two vsan 22* fcid 0x540000 [pwwn 10:00:00:00:00:14:00:00]

* fcid 0xe20000 [pwwn 10:00:00:00:00:12:00:00]

One active zonese

Zones are membe

Devices are mem All switches in the

same view of zoni The * indicates tha

active in the fabric


51/66


52/66


What is NPIV?N-Port ID Virtualization (NPIV)

Provides a means to assign multiple FCIDsto a single N_Port

Allows multiple applications to share the same FC adapter port

Provides a means to assign multiple Server Logins to a single physical interface

One HBA = many virtual WWNs "VM awareness inside the SAN Fabric

Different pWWNallows access control, zoning, and port security to be implemented at the application level

Usage applies to applications such as VMWare, MS Virtual Server and Citrix

!""#$%&'() +,-.,- /0 1234 0(-, +5$6%7

89&$#

:,;

/$#, +,-.$%,

1?2(-6?3@ A

:,; 3=>

1?2(-6?3@ B

/$#, +,-.$%,< 3=>

1?2(-6?3@ C

/?2(-6

F_Port

N_Port


53/66


What explosion??

One domain ID per switch inside blade enclosure

Theoreticalmaximum number of Domain IDs is 239per VSAN

Supportednumber of domains is quite smaller:

EMC: 40 domains

Cisco Tested: 75

HP: 40 domains

Manageability

Lots of switches to manage

Possible domain-ID overlap

Possible FSPF reconfiguration

Domain-id0x0A

0x0C 0x0D


54/66


What is NPV?

NPV enables the switch to act as a proxy for connected hosts

NPV switch does not use a Domain ID

Inherits Domain ID from upstream fabric switch

No longer limited to Domain ID boundaries

Manageability

Far less switches to manage NPV very much plug and play

NPV-enabled switch is managed much like a host

Reduces SAN management complexity

NPV-switch: no zoning, name server, etc.


55/66

N-Port Virtualizer (NPV)

Uses NPIV functionality to allow a switch to act like a server performing multiple logins through

Servers connected to the NPVswitch login to the upstream NPIV core switch

! Uplink from NPVswitch to NPIV core switch performs FLOGI

! Server logins are converted (proxy) to FDISC to login NPIV Core switch

No local switching is done on an FC switch in NPVmode

FC edge switch in NPVmode does not consume a Domain ID

Scalability will be dependent on FC login limitation (MDS is ~10K per fabric)

1,DE< FGGGH I@+ JADDH I@+ ;#&K,


56/66


57/66



58/66


Each VSAN on a Trunking E portwill establish a logical ISL


59/66


A point to point frame sent from the fabric controller of one (VSAN) switch (Fthe fabric controller of the other switch.

This frame is used to setup and govern the communication between the two Supported classes of service, fibre channel timers, buffer to buffer credits, another things are exchanged using the ELP frame and the subsequent SW_Aaccept) to the ELP.

This is also where isolation can occur due to a mismatch in fibre channel timeID conflicts!


60/66


The ESC (Exchange Switch Capabilities) frame allows switches to exchangeabout the routing protocols supported and agree on a common routing protoc

The vendor ID field is used by the MDS to determine that the switch on the oanother MDS switch. This is indication that Trunking E_Ports (TE) and VSANsupported.

Only the ELP winner, the port that receives the SW_ACC to its ELP, sends


61/66


62/66


FCSwitch

DID 4FCSwitch

DID 5

FCSwitch

DID 6

FCSwitch

DID 8

EFP domain list 8

EFP domain list 4, 5, 6

EFP domain list 4, 5, 6, 8

Link being initialized

SWWN 111

SWWN 444

SWWN 333

SWWN 222Principle

Principle switch does

though the SWWN 11

SWWN in the existing

the EFP from DID 5 co

overrides the lower SW


63/66


64/66


T11- http://www.t11.org/t11/docreg.nsf/draftlr

Where to start?

FC-PI-4 Fibre Channel Physical Interfaces

FC-FS-3 - Framing and Signaling 2

FC-LS-2 - Link Services

FC-GS-6 - Generic Services 6

FC-SW-5 - Switch Fabric Generation 5

FC-BB-5 Fibre Channel Backbone (FCoE, FIP)

There are others depending on the situation, but the ones above are a good starting point

Robert Kembels Comprehensive Introduction to Fibre Channel & Fibre Channel Switched

http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=00533918


65/66


66/66

Dc Ccna Fc Intro

Documents

Transcript of Dc Ccna Fc Intro