Ive been reading the https://documentation.meraki.com/MX/Networks_and_Routing/BGP article, and it got me thinking about using an MX to replace an ageing IOS based Cisco setup we have in production. I also see this post : https://community.meraki.com/t5/Security-SD-WAN/MX84-with-BGP-Protocol/m-p/14120#M3431 which maybe the only solution as we are almost exactly the same scenario as them. So at the moment we have 2 x IOS Routers with their own ethernet to different carriers, then each router runs BGP (in HSRP mode) using our own public AS to advertise our own portable public IP ranges in the event of a carrier or router failure. for example, I currently have configured on our Primary IOS Router: router bgp <ASnumber> no synchronization bgp router-id <LocalRouterIP> bgp log-neighbor-changes network <IP range> neighbor <LocalRouterIP> remote-as <ASnumber> neighbor <LocalRouterIP> send-community both neighbor <LocalRouterIP> soft-reconfiguration inbound neighbor <RemoteRouterIP> remote-as <ProviderAS> neighbor <RemoteRouterIP> password <password> neighbor <RemoteRouterIP> next-hop-self neighbor <RemoteRouterIP> send-community both neighbor <RemoteRouterIP> soft-reconfiguration inbound neighbor <RemoteRouterIP> route-map BGP-IN in neighbor <RemoteRouterIP> route-map BGP-OUT out no auto-summary we have them configured to pull in only regional routing tables then forward all other requests upstream so table size shouldnt be a problem. Has anything changed enough since 2018 to allow us to do this on an MX84 or MX100 without having to have an IOS router in front of them?
... View more
