using arista switch as a tor switch with scvmm

In my experience once you get above 50 tenants you run into all sorts of scaling issues. However the small/medum sized business that I've talked to and/or interviewed at in the past have had pleasant experiences with it from what's been said. I ask because working at two major healthcare companies that operate like service providers we have run into scaling issues left and right and ACI has been a shit show. What they want automated is anyones guess!Īre you a service provider? Or are you more in the small/medium sized business? Support for multicast, IPv6 and vrf route leaking (mp-bgp). Requirements will be 40/100 leaf spine, 12 leaf switch (2x5 ToR) + (2x1) single. My issue is handing the implementation to NetOps so need to think of complexity (opex) vs business benefit. So question is, should the transition to leaf spine Bgp evpn be done using standalone boxes/firmware -nx-os/cx/eos with CLI/Rest or go for SDN solution (ACI).

Ive tested Aruba CX but feel they are playing catch up at the moment with regards to the big 3. To be frank, id much rather NX-OS with DCNM as i think the integration/migration from multivendor to ACI will be a nightmare even with the best intentions. Whenever i talk to vendors such as Cisco they push ACI only. Looking at transitioning to leaf spine with BGP evpn. I’ll just be focusing on the DC as it falls under my remit. Not had a lot of physical access to kit since the lockdown.

I joined around 15 months ago to make up a design team. No real standards adhered to or documentation, with different teams having shoehorned in devices over the years. A Sh** show of brocade, extreme, netgear, aruba and mellanox (separate team/site). Our current environment is - how shall i put it. Its that time where the network refresh is getting underway.

Using arista switch as a tor switch with scvmm