Fibre Channel (SAN)

Reply
New Contributor
Posts: 3
Registered: ‎01-01-2011

How Fibre channel protocol finds D_ID(destination address)

Hi iam new to this forum.In fibre channel frame there is source id and destination id . host will get source id through the login process how it will come to know about the destination port  address is there any protocol like arp in fibre channel.

Super Contributor
Posts: 635
Registered: ‎04-12-2010

Re: How Fibre channel protocol finds D_ID(destination address)

Hi,

this is not easy to explain all the details.

From a high level view: All devices can find the fiber channel IDs (D_ID/ S_ID) in the name server. You can query this on the switch with nsshow and nscamshow. The first command displays the details of all devices local on the switch and the second one all remote devices.

Zoning is a kind of isolation. Only zoning members can see each other. No other communication is allow. Changes on the zoning are propagated via RSCN to the zone members. So a servers will be informed if a storage port is not reachable.

Zoning can be  done on WWPN, WWNN and Port ID.

I hope this helps,

Andreas

New Contributor
Posts: 3
Registered: ‎01-01-2011

Re: How Fibre channel protocol finds D_ID(destination address)

thank you andreas for you reply.can you please provide some links or pdf for learning Fibre channel protocol in depth .

After fabric login the node will register its wwn no and port no to name server then is there any specific frame for querying.suppose isame hba wwn is in two zones how will it find where to route packets to be more clear is there any protocol like ARP in tcp/ip to find where the packet to be send for reaching the destination......once again thank you for your response

Super Contributor
Posts: 635
Registered: ‎04-12-2010

Re: How Fibre channel protocol finds D_ID(destination address)

Hi,

currently I have no real good link where you can learn the FC protocol.

Check the FOS Admin Guide and the command reference guide.

To understand how frames are routed throught the fabric you need some more commands.

portRouteShow, topologyShow, urouteShow.

In addition you need to know which switch model you have and which FOS code is running.

The routing policy can be shown with aptpolicy and dlsshow

You need to understand how FSPF is working. The Brocade documentation explains this very good. In addition check how trunking is working.

Frame routing is under normal condition not really important if you have enough ISLs between the switches.

Andreas

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook