Forbes, just be careful, here. ALL equipment exhibits some sort of
goofiness when it hits its limit. If the processor can not handle the
load, bad things happen. If it runs out of memory, it does goofy
things. Whether it is an MT or Cisco, it will fail at some level of
loading. The Ubiquiti will, too, at some point.
I don't think your problem is MT, per se, It also is not bridging as
many like to make it out. It looks to me that the problem is MT doesn't
handle large amounts of data or high packet rates over bridged ports.
While I don't have a direct answer for your question, I do have a
long-term recommendation:
Determine what the traffic load is now and what you anticipate it to be
in 1, 3 and 5 years. Determine what you want the network topology to be
in 1, 3, and 5 years. Do some research and find the equipment that
will handle the load in the topology you want in 5 years. That is the
gear to use. I understand your current feeling and I do not disagree
with your approach. Just be aware that anything you do today without
the planning is very likely to also be a "throw-away" purchase. Use it
to get over the current hump, but expect to throw it away when you get
to the configuration you want.
On 10/14/2010 7:56 PM, Forbes Mercy wrote:
I also haven't been in my core router in ages, my template IS by Butch
as I stated before, I HAVE had Dennis look at the outages, everyone is
stumped, if I can't depend on it I don't want it. THEN I'll have time
to route the network. I've used Mikrotik for years and until the load
got to high things ran fine, I wish I could make it work but its down
just too much.
On 10/14/2010 4:18 PM, Josh Luthman wrote:
I agree with Travis.
Also the thread is about a bandwidth manager, which just like Travis,
you would do at the edge between you and your upstream. Your APs,
backhauls and other radios can be Ubnt/Canopy/Linksys/etc
I would suggest spending the minimal amount of money for the MT
router, Butch's template and forget about it. If you do have an
issue (IMO it will be something a person did to the network if no one
logs into it making changes all the time) you have Butch, Dennis, the
list, etc.
I can't remember the last time I logged into the core router. When I
did, it was to copy some rules to share on a list or ##mikrotik.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Thu, Oct 14, 2010 at 6:53 PM, Travis Johnson <t...@ida.net
<mailto:t...@ida.net>> wrote:
Hi,
You need to fix your network, not the hardware/software you are
running. I have over 60 Mikrotik backhaul links, with over 1,000
Mikrotik customer radios (plus thousands more Trango and Canopy)
and have NONE of the issues you describe.
Our main edge router is a Mikrotik box (x86 with Quad core) and
it has thousands of rules and NAT translations, moving 450Mbps x
150Mbps on a daily basis, and has been up for over 6 months right
now (due only to firmware upgrades).
Having your network bridged is the problem. Take time out and fix
that, or you will continue to have more and more problems...
Travis
Microserv
On 10/14/2010 4:45 PM, Forbes Mercy wrote:
Really Josh, you want me to rehash this? To be simple I'm not a
true geek, I barely speak linux and Router OS not at all. Our
network of 700 over 12 towers is bridged, a big no-no but I
can't keep radios up long enough to make us routed along with
the growth sprut we've had this year (we 're averaging 3
installs a day with one installer/field tech). We've found that
if you get over 50 on Mikrotik you start getting latency issues,
four of our towers have over that. When I was all Mikrotik
(well 90% that 10% Moto) it worked great for about a year and a
half, then the packet storms started, then radios started doing
weird intermittent things like turning off. Sure we did the
obvious, change passwords, isolate the radios from the rest of
the network but it just started to get worse, probably traffic
driven from our ongoing growth that the greater demand for more
bandwidth (we are 90% residential so Netflix type stuff).
To solve this we started replacing backhauls with Ubiquiti
radios. Ubiquiti allows more traffic so the added pressure
really started to take down the Mikrotik AP's, ports and bridges
now drop with undiagnoisable (new word) regularity. Then the
bandwidth manager failed, Butch rebuilt it but for some reason
the upgrade to 4.11 made failures happen more often that were
like the AP's, dropped ports and bridges. We compensated by
making a path on the Ethernet side and in-network side so we
could maybe ... (fix the disabled port/bridge) from either end.
We are spending all of our time building redundant this and
redundant that until we realized one thing, on every outage
Mikrotik's had cascading failures shutting down ports or turning
off radios (disabling) meanwhile Ubiquiti never went down,
ever. So we started pulling all Mikrotik backhauls, now we only
lose AP's and the bandwidth manager. Since the bandwidth
manager takes the entire network down we want replace it. Now
you're up to speed on where we are, I call Mikrotik my
'backwards momentum' mover, we have to stop our forward motion
on building and installing so we can restore service, it takes
the fun out of this business thats for sure.
Forbes
On 10/14/2010 3:17 PM, Josh Luthman wrote:
Hrm why doesn't Mikrotik work?
On Oct 14, 2010 6:15 PM, "Forbes Mercy"
<forbes.me...@wabroadband.com
<mailto:forbes.me...@wabroadband.com>> wrote:
> In my mission to rid our network of Mikrotik I need to shop
for a new
> bandwidth manager since mine likes to randomly drop one of
the ports or
> bridge, and reset the route gateway (twice already this
week). I'm
> looking for a more friendly windows type based unit, any
suggestions.
>
> Thanks,
> Forbes
>
>
>
--------------------------------------------------------------------------------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
>
--------------------------------------------------------------------------------
>
> WISPA Wireless List: wireless@wispa.org
<mailto:wireless@wispa.org>
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List:wireless@wispa.org <mailto:wireless@wispa.org>
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives:http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List:wireless@wispa.org <mailto:wireless@wispa.org>
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives:http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: wireless@wispa.org <mailto:wireless@wispa.org>
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List:wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives:http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--
Scott Reed
Sr. Systems Engineer
GAB Midwest
1-800-363-1544 x2241
1-260-827-2241
Cell: 260-273-7239
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
