"Dino, > >> Thomas, just be aware that in the physical case, a server is dual >> attached to multiple TORs. If each TOR is going to be an NVE, >> because you want to save state in the data center core layer, then >> you'll have to do multi-homing. > > I suspect we need to dive a bit deeper into this. i.e., what does > "dual attached" mean?
A bare-metal server has 2 physical connections to different boxes (where a box is a swtich or a router). In some cases, the 2 connections are active/active, but mostly active/backup. There is some assumption from the server OSes that the upstream boxes are layer-2 switches. But it doesn't have to be the case, they can be layer-3 routers. > Do you mean the NVE has two physical connections to the ToR? If so, No, that would be the NVE being able to get ECMP support from the underlay. I am talking about the NVE in the TOR, as one example. > than the question presumably is about allowing/supporting multi-homed > NVEs. That is right Thomas. > If the question is about the TS having two attachements to the ToR, > wouldn't that be modeled (architecturally) as two distinct > interfaces/ports, in which case each one can connect to its own NVE, > in which case we are good? The questions is about the return traffic coming to the TS. Do you want it load-split across all the NVEs associated with the TS. The answer is a definite yes, as Joel stated for robustness and to take advantage of all cross-sectional cheap bandwidth in a data center. Dino > > Thomas _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
