« Connectivity Changes for November 2010 | Main | FIP, FIP Snooping Bridges, and FCFs (Part 2 – FIP Snooping Bridges and Fibre Channel Forwarders) »



Feed You can follow this conversation by subscribing to the comment feed for this post.

Ivan Pepelnjak


This is a fantastic introduction to FCoE login processing. However, the basic question remains: why would you mandate that a DCB-enabled bridge supports FIP snooping?

FIP snooping is a nice security feature, but it's not mandatory to make FCoE work ... and you should always put FCoE traffic in a separate VLAN anyway.

Looking forward to future posts!

Erik Smith

Hi Ivan, thanks! My next post should be ready in a day or so and it will explain exactly why I think FIP Snooping is required.


Streif Vest

Thank you, Erik, for the topic. I read FC-BB-6 at this moment (FCoE) and try to understand FIP procedures. I think that you describe basic routine very well.


Excellent write up on FIP. Thanks very much.
Just one question, why there must be a VLAN associated with every VSAN? Just I could not understand this? regards. Mohan

Erik Smith

Hi Mohan, thanks!

In regards to your question, there can only be one VSAN per VLAN due to a requirement in the FCoE standard (FC-BB-5). Essentially, if you have more than one VSAN per VLAN, it would be possible to have duplicate FPMAs (Fabric Provided MAC Addresses) and this can lead to data corruption under the right circumstances.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)


  • This is not an official EMC blog.
    The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC nor does it constitute any official communication of EMC.