You can partition the traffic, but would you then lose the properties of NVO3 such as overlapping address space and mobility for storage traffic?
Siamack -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Anoop Ghanwani Sent: Tuesday, August 28, 2012 6:11 PM To: Linda Dunbar Cc: Black, David; [email protected]; [email protected] Subject: Re: [nvo3] Storage (part of: Let's refocus on real world) On Tue, Aug 28, 2012 at 8:37 AM, Linda Dunbar <[email protected]> wrote: > > I agree that the first phase of NVo3 should not consider encapsulating FCoE > traffic. > > That means servers need to have separate physical ports for FCOE traffic so > that NVE won't need any mechanism to recognize the FCoE traffic. Not necessary to have separate physical ports as noted below. > If servers don't have separate physical ports for FCoE traffic, they use some > VLANs for FCoE traffic instead. Then NVEs have to be configured not to > process those VLANs. Is it correct? Yes, FCoE would typically use its own VLAN(s) and those wouldn't be configured for forwarding to any of the tunnels at the NVE. Anoop _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
