cfp261-module2

2005 Brocade Communications Systems, Incorporated.Revision CFP261-02-2005

Chapter 2 - 1


Chapter 2 - 1

1

Brocade SilkWorm

Fibre Channel Review

Brocade

Product Training

Brocade Education Services 2005 Brocade Communications Systems,

Incorporated.


Chapter 2 - 2


Chapter 2 - 2

2

Discuss the Fibre Channel networking model

Describe the Fibre Channel frame format

List the steps for port initialization

List port types and node types

Break down the format of a WWN

Identify Fabric addressing nomenclature

Learning Objectives


Chapter 2 - 3


Chapter 2 - 3

3Fibre Channel Networking Model

FC - 0 and 1 layers specify physical and data link functions needed to physically send from one port to another.

FC - 0 specifications include information about feeds and speeds.

FC - 1 layer contains specifications for 8b/10b encoding, ordered set and link control communication functions.

FC - 2 specifies content and structure of information along with how to control and manage information delivery. This layer contains basic rules needed for sending data across network. This includes: (1) how to divide the data into smaller frames, (2) how much data should be sent at one time before sending more (flow control), and (3) where the frame should go. It also includes Classes of Services, which define different implementations that can be selected depending on the application.

FC - 3 defines advanced features such as striping (to transmit one data unit across multiple links) and multicast (to transmit a single transmission to multiple destinations) and hunt group (mapping multiple ports to a single node). So, while FC-2 level concerns itself with the definition of functions with a single port. The FC-3 level deals with functions that span multiple ports.

FC - 4 provides mapping of Fibre Channel capabilities to pre-existing protocols, such as IP or SCSI, or ATM, etc.


Chapter 2 - 4


Chapter 2 - 4

4Fibre Channel Frame Format

FRAMESOF

4

PAYLOAD

Up to 2112

EOF

4

CRC

4

HEADER

24

2148Bytes

Note: Inside the payload is an optional header used by HBA drivers

A frame has a header and may have a payload. The header contains control and addressing information associated with the frame. The payload contains the information being transported by the frame on behalf of the higher level service or FC-4 upper level protocol. There are many different payload formats, based on the protocol. The TYPE field (Word 2, bit 31- 24) tells which format to use. The routing control INFO bit (bit 27-24) determines how to interpret the payload.Field DefinitionsRouting Control bits (R_CTL) are the first 8 bits of the header. They define the type of frame and its content or function. The first 4 bits (Bit 31-28) identifies the frame type. The 2nd four bits INFO bit (Bit 27-24) defines the contents of the frame or identify the function of the frame.Destination_ID (D_ID)- Port Identifier (PID) or 24 bit address of the recipient. It could also be a a well-known address like the Name Server FFFFFC. Class specific Control Field (CS_CTL) The control necessary for different classes of service. This field is always zero for classes 2 and 3 per the standards. Classes 1 and 4 use it. Brocade switches currently only use Classes 2,3, and F. If CS_CTL is something other than zero in a Brocade port log (a running log extracted from portions of the FC frame displayed with the portLogDump command), then it is a Brocade internal code called IU_Status Values. Source_ID (S_ID) - Port identifier (PID) or 24 bit address of the source. It could be a a well-known address like the Name Server FFFFFC. Type identifies the protocol of the frame content for Data Frames (i.e FC_CT, FCP, IPFC)Frame Control (F_CTL) -This field contains miscellaneous control information regarding the frame such as who owns initiative, first frame of the Exchange, last frame of the Exchange, etc. Sequence ID (SEQ_ID) used to identify and track all of the frames within a sequence between a source and destination port pair. Data Field Control (DF_CTL) this field indicates if any optional headers are present at the beginning of the data field of the frame. Optional headers are used for information that may be required by some applications or protocol mappings. Sequence Count (SEQ_CNT) used to indicate the sequential order of frame transmission within a sequence or multiple consecutive sequences within the same exchange. This is a counter that increments as sequences of frames are transmitted. Originator_ID (OX_ID) Exchange ID assigned by the originator port Responder_ID (RX_ID) - Responder_ID, optionally assigned by the responder to the Exchange. Data Field/Payload The standards limit the size. The maximum size is 2112 bytes.


Chapter 2 - 5


Chapter 2 - 5

5Node WWN Name Format - NWWN

10:00:00:60:69:00:60:02

Single hexadecimal digit selected by the vendor

(Brocade uses a 1)

FC Standard reserved

Assigned by IEEE

Assigned by the vendor

This format applies to:

Switches Storage HBAs

Note: Brocade switches may also be identified by 00:05:1e as well

Based on the IEEE Standard format, a typical SilkWorm Node WWN is: 10:00:00:60:69:xx:xx:xx Where:The first 2 bytes are always 10:00The next 3 bytes are vendor specific. Brocade was assigned 00:60:69. Brocade also has 00:05:1e.The last 3 bytes are derived from the Brocade SilkWorm main board.The 3 byte company ID found in the 64 bit IEEE Standard format WWN can be searched at: http://standards.ieee.org/regauth/oui/oui.txt


Chapter 2 - 6


Chapter 2 - 6

6Port WWN Name Format - PWWN

20:00:00:60:69:00:60:02

Single hexadecimal digit selected by the vendor

(Brocade uses a 2)

Three hex digits set by the vendor to uniquely identify a port on a device or switch

Assigned by IEEE

Assigned by the vendor

This format applies to:

Switches Storage HBAs

Fabric Port Name2p:pp:00:60:69:xx:xx:xxThe next 3 nibbles (p:pp) are used by Brocade to show the switch port number.

20:04:00:60:69:1f:25:e6

The 0:04 which means this is port 4 on the switch


Chapter 2 - 7


Chapter 2 - 7

7NWWN and PWWN

Single Drive

Disk Node WWN20:00:00:77:77:00:70:c0

Host BHost A

Port1 WWN21:00:00:77:77:00:70:c0

Port2 WWN22:00:00:77:77:00:70:c0

Example:Dual Ported Disk Drive

HBA

HBA

Note If the last 3 bytes of the WWN are the same then we are talking about the same physical device.

The Node WWN (NWWN) is like an umbrella; that the port WWNs sit under like spokes. Different vendors do different things with the WWNs.The Port WWN (PWWN) sits under the Node WWN. Brocade uses 20:pp in the 1st 2 bytes of the Port WWN. In the Port WWN the IEEE allows these 1st lower 3 nibbles of the 1st 2 bytes to be used as a vendor wishes. Note Seagate uses Node and Port WWNs in a manner that could be confusing focus on the last 3 bytes. If they are the same, then you are looking at the same device. You will need this in zoning. If the last 3 bytes are the same, it will not matter whether you zone using the port or node WWN you will be zoning the same device. Ports on a switch are not zoned using WWNs; the devices attached to them are zoned using WWNs. Ports can be hardware zoned using domain and port numbers.


Chapter 2 - 8


Chapter 2 - 8

8Port Types

Device Ports

N_Port - Node Port, a Fabric device directly attached

NL_Port - Node Loop Port, a device attached to a loop

Switch Ports

U_Port - Universal Port, a port waiting to become some other type of port

F_Port - Fabric Port, a port to which an N_Port attaches

FL_Port Fabric Loop Port, a port to which a loop attaches

E_Port Expansion port used for inter-switch links

G_Port - Generic Port, a port waiting to be an E or F_Port


Chapter 2 - 9


Chapter 2 - 9

9Fabric Initialization Process

What do I want to be when I grow up? (State 1)

y/n Do you want to talk loop? (Transition 2)

G - Port Im waiting for someone to talk to me(State 3)

yes

no

Are you a switch or a Fabric point-to-point device? (Transition 3)F - Port

Fabric pt-to-pt

E - Port

switch

y/n Is something plugged into the port? (Transition 1)no

yes

U - Port

FL - Port(State 2)

(State 4)

(State 5)

Device Initialization into the Fabric from the switchs perspective

1. A switch port is a Universal Port (U_Port) that operates in either E/F_Port (G_Port) mode or FL_Port mode State 1 . This U_Port to G_Port wait state is 500 millisec

2. Is something connected to the port? If yes Transition 1 continue.3. U_Port starts mode detection process by transmitting at least 12 LIP(F7) Primitive Sequences Transition 2

a. If at least 3 consecutive LIP primitive sequences LIP(F7) received then port enters OPEN_INIT state and attempts FC-AL loop initialization State 2

b. If LIP Primitive Sequences are not received U_Port attempts OLD_PORT initialization by taking the link down then transmitting NOS primitives Transition 2. If Link Initialization Protocol fails after 1 retry or LIP received after 1 second go to Transition 2 (FC-AL) initialization

c. When operating in the FL_Port mode, a U_Port will try the loop initialization procedure three times. If all these tries fail, the port will be marked as faulty. To ensure N_Port, reinitialize the port and the switch port will cut the laser forcing a loss of signal state for at lease 20 s then the switch port will bring back the laser and issue NOSs Transition 2

4. U_Port will attempt the OLD_PORT initialization (Link Initialization Protocol for point to point) by taking the link down and then transmitting NOS Primitive Sequence if LIP timeout or any of the loop initialization phases timeout or only one non-zero AL_PA is claimed in Loop Inititalization Sequences (LOOP_EMPTY=false) or no non-zero AL_PAs is claimed (LOOP_EMPTY=true)

5. If the ACTIVE state is reached, the port will operate in the G_Port mode State 3. The normal E_Port or F_Port mode detection procedure follows Transition 2.a. If ELP succeeds, the U_Port operates in the E_Port mode State 4.b. If a valid FLOGI is received, the U_Port becomes an F_Port State 5.c. If self loopback detected after ELP exchanges and LOOP_EMPTY = false port exits G_Port and

reinitializes as FL_Port State 2Note The firmware will automatically attempt to reinitialize a faulty port every two seconds.


Chapter 2 - 10


Chapter 2 - 10

10

F

F N

N

NL

FL

NL

NL NL

FC-AL FL

1 2 34

765

0

10 9 811

15

121314

Port Types and Node Topologies

Private

Private

Public

Fabric

Fabric

Public

N NodeF Fabric PortNL Node LoopFL Fabric Loop Port

Hub

Nodes that attach to the fabric can either be a N (Node) or NL (Node Loop). NL nodes have two classifications; private or public.

Private NL nodes can only communicate with other nodes that are attached to the same hub or FL port; hence the word private. If the node is a private initiator then all targets it communicates with must be on the same loop. For fabric devices to communicate with a private storage device a phantom address is created for the port that the private devices is located at. An additional software feature can be added called Brocade QuickLoop that allows a private initiator on a FL_Port communicate with private loop targets on remote ports.

Public NL nodes can communicate with any member of the same hub of FL port and have the ability to send a frame to the fabric.

Fabric Nodes (N) can communicate with any Fabric Node and can communicate with private or public NL nodes on a loop.


Chapter 2 - 11


Chapter 2 - 11

11SilkWorm Port Interfaces

N_Port

NL_Port

N_Port

FL_Port

F_Port

N F 1 Port to 1 NodeNL FL 1 Port to 126 AL_PAs

Topologies

PointtoPoint: PointtoPoint is a simple topology that allows bi-directional communication between two nodes, in this case a storage system and a server.

Arbitrated Loops: The arbitrated loop is a ring topology where each node passes data to its adjacent nodes. In an arbitrated loop configuration, the transmitter of each node is connected to the receiver of the next node. In order to send data from one node to another, devices must arbitrate for access on the loop. Arbitrated Loops use an address scheme called Arbitrated Loop Physical Address (AL_PA). In this address scheme, devices are identified on the loop by their address. Devices with a lower AL_PA have a higher priority than devices with a higher number. Initiators will have a lower AL_PA and targets will have a higher AL_PA.

Switched Fabrics: An extensive storage network in which, large number of servers and storage systems are connected using Fibre Channel switches. Switches can be cascaded and combined with loops to create highly interwoven networks as fabrics.


Chapter 2 - 12


Chapter 2 - 12

12Well Known Addresses of Fabric Services

Well Known AddressesBroadcast

Server

FFFFFF

AliasServer

FFFFF8

MgmtServer

FFFFFA

TimeServer

FFFFFB

FabricController

FFFFFD

DirectoryServer

FFFFFC

FabricLogin

FFFFFE

Version 4.1 Version 3.1 Version 2.6.1

Every switch has reserved 24-bit addresses known as Well Known Addresses. The services residing at these addresses provide a service to either nodes or management applications in the fabric.

Fabric Login: Before a fabric node can communicate with services on the switch or other nodes in the fabric an address is assigned by the fabric login server. Fabric addresses assigned to nodes are three bytes long and are a combination of the domain id plus the port area number of the port the node is attached to.Directory Server: The directory server/name server is where fabric/public nodes register themselves and query to discover other devices in the fabric.Fabric Controller: The fabric controller provides state change notifications to registered nodes when a change in the fabric topology occurs.Time Server: The time server sends to the member switches in the fabric the time on either the principal switch or the Primary FCS switch.Management Server: The Management server provides a single point for managing the fabric.Alias Server: The Alias server keeps a group of nodes registered as one name to handle for multicast groupsBroadcast Server: This service is optional and when frames are transmitted to this address are broadcasted to all operational N and NL ports.

When frames are sent to a Well Known Address a different protocol call service Fibre Channel Common Transport (FC-CT) is used. This simple protocol provides a simple, consistent format and behavior when a service provider is accessed.


Chapter 2 - 13


Chapter 2 - 13

13Device Communication Example

JBOD

Host

1. Fabric Login (FLOGI) from host to switch at FFFFFE2. Switch (FFFFFE) responds with an ACCEPT3. Host does an N_Port Login (PLOGI) to the switch at FFFFFC4. Switch (FFFFFC) accepts5. Host registers (SCR) to receive RSCN at FFFFFD 5. Host can then:

Register attributesQuery for devices

6. Switch (FFFFFC) will respond as appropriate for type of request7. Host may log out (LOGO) of the Name Server - not the Fabric

Automatic registration of essential device information

During initialization, each interface option (for instance, the G_Port Option) that has a connected device registers the associated information with the Name Server. Thereafter, when a device is changed or a new one is added, that information will also be registered automatically. Essential information registered by a switch interface option includes:

Native port identifier Port type Port name Node name Classes of service

FFFFFE is the well-known address for the Fabric Login Server.


Chapter 2 - 14


Chapter 2 - 14

14Fibre Channel Network Addressing

Each switch is responsible for assigning unique addresses Addresses are 24 bits:

First 8 bits: Domain Number 0x01 - 0xEF Second 8 bits: Area Number 0x00 - 0xFF Third 8 bits: Node Address 00 or AL_PA

Native Mode Core PID Mode

DomainID

8 Bits

AreaID

8 Bits

Node Address

8 Bits

1-2390x01-EF

00 or AL_PA1 0-150x0-F

DomainID

8 Bits

AreaID

8 Bits

Node Address

8 Bits

1-2390x01-EF

00 or AL_PA0-2550x00-FF

Three types of addresses: Fabric: DD AA 00 Public Loop: DD AA PP Private Loop: 00 00 PP

Key:

DD= Domain

AA = Area

PP = AL_PA

When a node attaches to the fabric, it must receive a unique 24-bit address. The network address is a three byte address based upon the domain number and the port of where the node attached. This address is the source address and is used for routing data thru the fabric from one device to another. From left to right, byte zero is the domain number. Byte one identifies the port address when Core PID is enabled. If Core PID is disabled, the 2nd nibble represents the port address. The last byte can be used to get the AL_PA if the node is a NL device.

Fabric attached devices use an address format of DD AA 00, where DD AA 00 is the address of any Fabric-attached device that has logged into the fabric. This Fabric assigned address 1 byte represents the domain of the switch. the last byte (2 nibbles) is 00 indicating a Fabric device.The 2nd byte or 3rd nibble is 1 (native mode) for a 2000 series, the 2nd byte 4th nibble is the port, there are 15 possibilities (0-F).Port counts greater than 15 required a change in addressing modes, so Core Pid addressing was developed and the 1 offset (2nd byte, 3rd nibble) was eliminated. Core PID address mode uses an AREA designation to indicate port numbers 0 256.

Public Loop attached devices use an address format of DD AA PP, where DD AA is assigned by the Fabric at login; and PP = the local loop address (AL_PA). This type of address is simply a Fabric assigned address for a device attached to an FL_Port (24 bits). The value of DD AA is the same for all Public Loop devices attached to the same FL_Port and has the same meaning as DD AA Fabric addressing.

Private Loop devices use an address format of 00 00 PP, where PP = the local loop address. A Private Loop device has a 1-byte, 8-bit address, called the arbitrated loop physical address (AL_PA). This type of address is all that a Private device is capable of receiving or sending. Therefore, the Private devices may only communicate with the devices it can see on the local loop.


Chapter 2 - 15


Chapter 2 - 15

15Core Switch Port Identifier Core PID Required for mixed fabrics of v2.x & v3.x with 4.x switches

Enabled on v2.6.0c+ or v3.0.2c+ switches Not required on fabrics with v4.x switches only Best to implement before fabric enters production

AL_PAZZ

Port # 0-FY

Offset value1

Domain # in hexXX

XX1YZZ

RepresentsAddress Format RepresentsAddress Format

AL_PAZZ

Entire 2nd byte represents area #

YY

Domain # in hexXX

XXYYZZ

16-Port Count Addressing Larger Port Count Addressing

Updating the Core Switch PID format is required when introducing a larger port-count

switch into a fabric. When a switch with more than 16 ports, such as the Silkworm

3900 or SilkWorm 12000 is introduced into an existing fabric, the parameters needs to be set on all 2.x and 3.x switches in the fabric to

prevent segmentation. If redundant fabrics are not in use, it is necessary to schedule an outage for the fabric. This not available on

the 12000 and 3900.

A PID is a port identifier and is used by the routing and zoning services in the Fibre Channel fabrics to identify ports in the

network. Some device drivers map logical disk drives to Fibre Channel counterparts by PID. An example might be a static DRIVE

E:= PID =011F00 (Domain 1, Port 15, Fabric Device). If Core PID is enabled, the

address would change to 010F00

sw1:admin> switchdisable;configureConfigure...Fabric parameters (yes, y, no, n): [no] yDomain: (1..239) [239] BB credit: (1..27) [16] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] WAN_TOV: (1000..120000) [0] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..1) [0] Suppress Class F Traffic: (0..1) [0] SYNC IO mode: (0..1) [0] VC Encoded Address Mode: (0..1) [0] Core Switch PID Format: (0..1) [1]Per-frame Route Priority: (0..1) [0] Long Distance Fabric: (0..1) [0]


Chapter 2 - 16


Chapter 2 - 16

16

F

F N

N

NL

FL

NL

NL NL

FC-AL FL

00 00 08Private

00 00 CAPrivate 09 1E 04

Public09 11 02Public

09 14 00Fabric

09 1A 00Fabric

SwitchDomain #9

1 2 34

765

0

10 9 811

15

121314

Native Mode Addressing Example


Hub

As described earlier, all public loop and fabric devices will have the 2nd byte with a 1 in the leading field. Fabric Devices located port 1 and port 4 may obtain a phantom address allowing the fabric devices to communicate with the private device.


Chapter 2 - 17


Chapter 2 - 17

17

F

F N

N

NL

FL

NL

NL NL

FC-AL FL

00 00 08Private

00 00 CAPrivate 09 0E 04

Public09 01 02Public

09 04 00Fabric

09 0A 00Fabric

SwitchDomain #9

1 2 34

765

0

10 9 811

15

121314

Core PID Addressing Example


Hub

When a switch has the Core PID format enabled, the entire 2nd byte of the 24-bit network address is used to identify the port on the switch. Fabric Devices located port 1 and port 4 may obtain a phantom address allowing the fabric devices to communicate with the private device.


Chapter 2 - 18


Chapter 2 - 18

1812000 Addressing

Uses Port Addressing For Zoning Security Policies

Port Addressing Logical Blade Number

times 16 plus Port #

Port Addressing per logical switch (domain)

Physical Port 15

Physical Port 0

Logical Blade 0Physical Slot 1 or 7

Logical Blade 3Physical Slot 4 or 10

SilkWorm 12000 PortsSLOT SLOT SLOT SLOT

Port 1/7 2/8 3/9 4/10 ==== ====== ====== ====== ======

15 15 31 47 63 14 14 30 46 62 13 13 29 45 61 12 12 28 44 60 11 11 27 43 59 10 10 26 42 58 9 9 25 41 57 8 8 24 40 56 7 7 23 39 55 6 6 22 38 54 5 5 21 37 53 4 4 20 36 52 3 3 19 35 51 2 2 18 34 50 1 1 17 33 490 0 16 32 48

SilkWorm 12000 Layout:Port Slot 1 Slot 2 Slot 3 Slot 4 Slot 7 Slot 8 Slot 9 Slot 10==== ====== ====== ====== ====== ====== ====== ====== =======

15 15 31 47 63 15 31 47 6314 14 30 46 62 14 30 46 6213 13 29 45 61 13 29 45 6112 12 28 44 60 12 28 44 6011 11 27 43 59 11 27 43 5910 10 26 42 58 10 26 42 589 9 25 41 57 9 25 41 578 8 24 40 56 8 24 40 567 7 23 39 55 7 23 39 556 6 22 38 54 6 22 38 545 5 21 37 53 5 21 37 534 4 20 36 52 4 20 36 523 3 19 35 51 3 19 35 512 2 18 34 50 2 18 34 501 1 17 33 49 1 17 33 490 0 16 32 48 0 16 32 48

An alternative way to determine the area number is to use this formula:Area Number = (Logical Slot Number * 16 + port number)

Address 032400 = Slot 2 * 16 + 4 = Area 36 Address 033500 = Slot 3 * 16 + 5 = Area 53Address 030400 = Slot 0 * 16 + 4 = Area 4 Address 031e00 = Slot 1 * 16 + 14 = Area 30


Chapter 2 - 19


Chapter 2 - 19

19

Translation Table that maps 24-bit fabric addresses to an 8-bit AL_PA address Allows for fabric initiators to communicate with private storage Does not make loop LIP when a phantom is created

PhantomAddress 000004

Fabric Device appears as Phantom in loop

Translative Mode

Phantom Translation Table

00 00 04

Private

02 15 00

Fabric

00 00 E8 02 12 E8

Domain 2

AL_PA E8

Port 2

Port 5

Fabric Address 021500

Private loop devices with an 8-bit AL_PA address can only register and communicate with the members of the local loop. When a FL_port becomes active, the Brocade switch emulate a HBA at ALPA 01 and will probe loop members and register responses to the Name Server. Private devices will be padded with the domain number and port information when added to the name server. This information allows the private device to appear as a public target that a fabric initiators can potentially access.

If a fabric initiator sends a frame to a private device that was added to the name server by the switch, SID and DID field will have a 24bit address. When the frame arrives at the FL_Port, the Brocade switch will perform translative mode operation before. The translation will map the SID 24-bit fabric address to a virtual 8-bit AL_PA device. The FL_Port will replace the SID with the assigned virtual ALPA and place the frame on the loop. Now the private device will reply to a local ALPA and the FL_Port will remove the frame from the loop and put the true 24 bit address DID of the fabric device and route the frame. When the FL_Port completes its initialization it registers with the Fabrics Name Service (in the FCP capable device table) all existing devices on the loop. The format in the Name Service table is 0xLLLLPP where 0xLLLL is the two most significant bytes of the FL_Port and the 0xPP is the device ID. When a Nx_Port device tries to access another Nx_Port device it would PLOGI to it first. Whenever a remote public device sends a PLOGI to a private device, the FL_Port assigns to the host a phantom private address out of the 125available addresses per switch and registers this association in its node mapping table. When a remote public device needs to access a private device on the FL_Port Loop, it looks up the address in the Fabrics Name Service FCP-capable device table. The FL_Port converts this remote public device S_ID (i.e., 0x600226) to a loop port ID (i.e., device it uses the remote public devices phantom loop port ID (i.e., 0x02). The FL_Port, when detecting the use of a phantom ID translates it to a switch port ID (i.e., 0x600226) using its Node Mapping table. When a private device needs to access a remote public device it uses the remote public devices phantom loop port ID (i.e., 0x02). The FL_Port, when detecting the use of phantom ID translate it to a switch port ID (i.e., 0x600226) using its Node Mapping table.

Please note the following: The Translation Table can contain up to 125 entries per switch A single loop can contain up to 126 devices. It can contain up 127 AL_PAs, with 0x00 reserved for the FL_Port.


Chapter 2 - 20


Chapter 2 - 20

20Summary

Fibre Channel Network Model Well Known Addresses Topologies and Node Types Port Initialization Addressing Formats


Chapter 2 - 21


Chapter 2 - 21

21Review Questions

1. What is the area number in this 24-bit address: 062b00?

2. How many entries can the translative table keep?

3. What are the different switch port types?

4. What is the purpose of the well-known address FFFFFE?

5. What is the difference between a node and port worldwide name?


Chapter 2 - 22


Chapter 2 - 22

22Review Answers

1. What is the area number in this 24-bit address: 062b00?

2. How many entries can the translative table keep?

3. What are the different switch port types?

4. What is the purpose of the well-known address FFFFFE?

5. What is the difference between a node and port worldwide name?

1. In the 24-bit address 062b00, 43 is the area number (2 X 16 + 11). When converting to decimal to find the area, from a hex 24-bit address, use the slot number and multiply it by 16, then add the port number. 2 is the slot number, so that gets multiplied by 16, then the specific port number, b (11 decimal) is added. In this case is 32 + 11 = 43.

2.125

3.U_Port, G_Port, E_Port, FL_Port and F_Port

4.FFFFFE is the login server

5.A node worldwide name defines a specific device, while a port worldwide name defines a specific port on a device, be it a server, storage or switch.

cfp261-module2

Documents

brocade communications

revision cfp261

type of frame

frame type

data link functions

single port

flow control

hba driversa frame