Quantcast
Channel: EdgeRouter topics
Viewing all articles
Browse latest Browse all 20028

Replacing Mikrotik

$
0
0

Lo Folks!

 

I currently have a pretty fun setup at home.  I run ATT FTTH (1GbE Fiber to the Home), and I have xfinity 200+Mbps..  Both of these are currently running via a Mikrotik RB3011.

 

Additionally, I have a CRS125 as my main 'L2/L3 Switch', and am hoping to replace it... but, I want to be sure that my environment will be migratable to Edge before doing so.. soo

 

In my environment, I have numerous vlans (that part should easily be supported on any of the EdgeR/S devices...), but I also use LACP, VRFs (to separate the WAN interfaces, limiting certain vlan traffic to a given route)...  And the last part is the use of Dual G2 AC LR switches running a Single 2.4Ghz and Single 5.0Ghz SSID using Radius VLAN assignment..

 

So, my questions:

1.) Can the ER-8 handle throughput of 1.0GbE + 300Mbps on 2 seperate WAN interfaces

2.) Can the ER-8 handle VRFs delegating primary routes for each of these WAN interfaces when they are both DHCP assigned?

3.) How well is the implementation and support of LACP on the ER/ES devices?

6.) Are the ER and ES devices using 'software chips' to handle routing/switching, or are they implemented by *real* chips/asics ?

4.) Has anyone else attempted to get dynamic vlans assigned by radius working on the ES devices and achieved it?

5.) How easy is it to use the CLI on the ER/ES devices assuming you are already comfortable with interfaces such as Juniper, Mikrotik, etc...

 

I am sure I will be able to find some of these answers as I browse the forums (such as the CLI Primer, which I plan on reading in a moment), but figured that posting here might be a decent start as well, as I will be able to get feedback from users that have actually been using the devices successfully for similar things already.

 

Thanks!

 


Viewing all articles
Browse latest Browse all 20028

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>