Its that time where the network refresh is getting underway.
Our current environment is - how shall i put it. A Sh** show of brocade, extreme, netgear, aruba and mellanox (separate team/site). No real standards adhered to or documentation, with different teams having shoehorned in devices over the years. I joined around 15 months ago to make up a design team. Not had a lot of physical access to kit since the lockdown.
I’ll just be focusing on the DC as it falls under my remit. Looking at transitioning to leaf spine with BGP evpn.
whenever i talk to vendors such as Cisco they push ACI only. 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.
Ive tested Aruba CX but feel they are playing catch up at the moment with regards to the big 3.
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). My issue is handing the implementation to NetOps so need to think of complexity (opex) vs business benefit.
Requirements will be 40/100 leaf spine, 12 leaf switch (2x5 ToR) + (2x1) single. - manageable size.
Support for multicast, IPv6 and vrf route leaking (mp-bgp). Automation is hot topic at mgt level. What they want automated is anyones guess!
No comments:
Post a Comment