How should I implement this I do not know yet.Īll additional IP addresses, that I had to assign to the VRRP work perfectly. R1 has 254 priority and R2 is 1, plus preemption-mode enabled (to always use R1 as Master if it is available, I like it more)įortunately it works, now the second part left, start using two switches. Here is the simple schema, I've created to illustrate everything (R1, R2 and VR are in VRRP). Now, routing from the network is made by cisco, nat by mikrotiks.Created all needed IP addresses on the VRRP interface.Routed all traffic from Mikrotiks to CPE, but through VRRP interface.Created VRRP on both Mikrotiks (they are also using public IP addresses).Created vlan and placed it in the public IP-address range.Changed the teamplate of cisco switch to lanbase-routing.In order to achieve requirements with minimum costs (working with existing cisco 2960s, two Mikrotik routers and one CPE from ISP, where this CPE is covered with SLA) and avoid using single Mikrotik (I trust a bit more to cisco switch than to Mikrotik) I made following: How does usually configuration of a such network topology looks? Or do I need to create two VRRPs, inside and outside the network? But can't yet make a proper picture of the implementation. I was thinking about making VRRP inside our public range. While on both Mikrotiks I have to mirror the configuration, thus both will have the same IP addresses in the public range (I had to configure all the list of IPs in order to implement dst-nat).Īnd from here I can't imagine how should I implement this. This part is easy and clear.īut then, how to make NAT. VRRP will be inside the network (private). It is obvious that both Mikrotiks have to have the IPs from our public range to use the CPE as gateway. Unfortunately I can't understand how I can establish NAT after. Redundancy between two routers will be achieved through VRRP. And here are the problems I faced.Īs routers we use Mikrotik. Now I would like to implement redundancy. In the previous question I have been trying to optimize switching topology.
0 kommentar(er)
