I hope the new subject is descriptive enough. I also pulled out the thread references so as to not hijack the original thread.
On Wed, Feb 26, 2014 at 12:58:46PM -0600, Ty Featherling wrote: > "Mikrotik will happily speak OSPF PTP on multiple networks on one > interface. That is something I've taken advantage of when changing > routers at key locations. It would not work with a Cisco in the mix." > > THANK YOU for saying this. I just discovered this limitation on Cisco > the other day. I am just now implementing OSPF on my network and > was having trouble getting the Cisco to talk to a Mikrotik until I > realized that Cisco will ONLY speak OSPF from it's primary IP on an > interface. I have many Mikrotiks with link-nets back to this Cisco > at the edge so I am no trying to solve this problem. Not to hijack > the thread, but could I use a single Mikrotik connected to the same > interface on the Cisco as an OSPF agent of sorts? Have it share with > the Cisco and also share with the other Mikrotiks? I think there were some typos up there that are making it harder for me to figure out exactly what you were saying. If I answer the wrong question, I appologize. I think you have a central Cisco box talking to several MikroTiks, probably across wireless links? Maybe all those links come into the same interface on the Cisco? So that the Cisco has multiple "ip address ... secondary" statements on the interface? That's my assumption. You can always insert another hop in the LAN were your Cisco live. I imagine there is a switch between the Cisco and the various links. You could VLAN the switch to put all those links in one or more VLANs. Or, just use a different switch for the links to the other sites. You can then insert a MikroTik to talk with one interface connected to your switch with the various links and one interface connected to your Cisco, through another VLAN on the switch or a crossover cable. It doesn't really matter. It just adds a hop to the traceroute, a small amount of latency, and another point of failure. That 'Tik can talk OSPF to the other sites and the Cisco. Easy peasy. Or, you could setup VLAN trunking on the port talking to the Cisco and move links into individual VLANs. You can create sub-interfaces on the Cisco for each VLAN allowing each subnet to be the primary IP on each sub-interface. Then you don't need the extra MikroTik, just a VLANable switch. While you're doing that, you can actually create another trunk port. Hook that to a MikroTik. Configure VRRP, or just multiple subnets to each edge site, and have failover capabilities. That's how I've done things here while trying to move from our 7200 to a MikroTik, first try was with an 1100AHx2. That thing fell over several times, but I had two subnets running to each remote site. One terminates on the vlan interface on the Cisco, one on the MikroTik. I used a 10.x.x.x/29 for the secondary, purportedly temporary, subnet. When the 1100 fell down, the traffic still flowed over the Cisco. Until one failure mode of the 1100 spun the CIsco's CPU at 100% taking down both routers. I thought I was being DDoS'd. The network came back up as soon as I powered off the 1100. The 1100 came out of the rack with extreme prejudice at that point. I am now trying with a CCR. It's behaving better, but there are still nervous making things and I can't make everything stable beyond RouterOS 6.4. VLAN switches and multiple devices are the way to go. ;-) Even cheap VLAN capable switches. -- Scott Lambert KC5MLE Unix SysAdmin [email protected] _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
