Just checked with Cisco SE 4.1.3 software of Nexus5k support FCoE natively
now. no need of putting MDS naymore.
FCoE vlan has 47% of bandwidth reservation for FC traffic.
On Mon, Jan 31, 2011 at 11:26 PM, Radioactive Frog <pbhatkoti_at_gmail.com>wrote:
> Muhammad,
>
> On Mon, Jan 31, 2011 at 8:18 PM, Muhammad Anser Khan <manserkhan_at_gmail.com
> > wrote:
>
>> Dear Experts,
>>
>> I have a scenario:
>>
>> Servers (CNA-FCoE) ----> (FCoE) N5K (FCIP) ----> Layer 3 ---- <<WAN>>
>> ------
>> Layer 3 ------> (FCIP) N5K (FC) ---------> Server (HBA - FC only)
>>
>> FCoE will be on the new DR site whereas FC is currently working on the
>> Main
>> Site.
>>
>> Following are the questions:
>>
>> 1- Can Nexus do FCIP? Please explain and give some example
>>
>
> Nope, i guess u mean FCoIP only IP at the moment.. but there are plan to
> introduce in may be next year.
> You will need MDS or brocade switches at this stage for FC storage
> connectivity.
>
>
>>
>> 2- Can we easily connect traditional FC to Nexus directly on the existing
>> Main Site and forward traffic through FCIP?
>>
>> Nope....same as above..
>
>
>> 3- Will this solution work properly (from servers prospective) where we
>> have
>> one site is using FC and other will be on FCoE?
>>
>>
> FC or FCoE - it doesn't matter - it just included /excludes number of
> devices needed for storage connectivity. As long as solutin is design
> correctly it will have no issue.
> I think looking ahead, FCoE is the way to go and use VSANS on MDS/Brocade
> to separate SAN traffic (infra vs customer's traffic).
>
>
> Regards,
>> Anser
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Mon Jan 31 2011 - 23:42:41 ART
This archive was generated by hypermail 2.2.0 : Tue Feb 01 2011 - 07:39:17 ART