What's new in 6.0rc7 (2013-Jan-18 13:04):
*) dhcp relay - possibility to add relay agent information option;
*) lcd - options current-interface, time-interval and all-interface-mode
no longer get reset after reboot;
*) fix reboot in virtualized enviroment;
*) lcd - improve slideshow screen;
*) console - file print now shows file size as small number with suffix;
*) dhcp v4 - fix problem when sometimes client or server failed to send packets
most likely it happened on vlan interfaces;
*) ipv6 - added setting to disable forwarding;
*) added "/ip neighbor discovery settings" menu with "default=yes/no" setting;
We have tons of MikroTik Routers at ISP Supplies.
Friday, January 18, 2013
Wednesday, January 16, 2013
MikroTik CloudCore Test Results
After a few minutes of beating me head against the wall to figure out how to use the traffic generator tool, I was finally able to get a good test of the new MikroTik Cloudcore CCR-1036, 36 core routers. Here is my test setup:
Here are the results with small packets, the important line here is the TOT line:

And standard packets, again look at the TOT line:
As you can see, with small packets it runs out of steam at 17 million packets per second without totally filling the 12 Gig interfaces but with standard 1500 byte packets, it is able to run wire speed (well almost, 11.8 is close enough to 12!) with 12 Gig interfaces connected.
Tomorrow I will try the same test with 16 interfaces as I have some SFP modules and patch cables being sent to my hotel.
Overall, I am quite impressed with this piece of hardware and I can't imagine having an ISP application that will use all of its resources.
Here are the results with small packets, the important line here is the TOT line:

And standard packets, again look at the TOT line:
As you can see, with small packets it runs out of steam at 17 million packets per second without totally filling the 12 Gig interfaces but with standard 1500 byte packets, it is able to run wire speed (well almost, 11.8 is close enough to 12!) with 12 Gig interfaces connected.
Tomorrow I will try the same test with 16 interfaces as I have some SFP modules and patch cables being sent to my hotel.
Overall, I am quite impressed with this piece of hardware and I can't imagine having an ISP application that will use all of its resources.
Wednesday, January 9, 2013
CloudCore CCR Router Tests
Look what's on my desk!
Check back for my tests with the MikroTik CCR1036-12G-4S routers, coming soon.
Friday, January 4, 2013
ISP Supplies now seventh largest US MikroTik distributor
ISP Supplies is now the seventh largest US distributor of MikroTik products. Thank you to our customers! http://www.mikrotik.com/buy/northamerica/usa
Thursday, December 20, 2012
MikroTik Cloud Core Router's Shipping!
The new MikroTik Cloud Core Routers are finally shipping and will be here next week!
Place your orders now to reserve Your Cloud Core Router Today at ISP Supplies!!
- 16 core networking CPU, 1.2GHz clock per core
- 12 Mbytes total on-chip cache
- State of the art TILE GX architecture
- 12x Gigabit ports, all directly connected to CPU
- 1U rackmount case option
- Color touchscreen LCD display
- Up to 1.5 mpps throughput in regular mode
- Up to 17.8 mpps throughput in fastpath mode (wire speed)
- Up to 12 Gbps throughput with common RouterOS configurations
Thursday, November 29, 2012
First SAF Freemile Deployment
We completed our own deployment of the SAF Tehnika FREEMILE-24-2 system today after selling several units to customers with good acceptance. I have been certified on the SAF proeucts for a year or so and this was an opportunity for me to see it perform in the real world.
The quality of the workmanship is excellent. Pieces are well machined and well finished. The Arkivator dish antennas are also well made and have an extremely tight pattern and good front to back ratio. At 24 GHz, the fresnel zone is small and the beam width of the antennas is very tight so proper alignment is a must.
The link was a bit over a mile, not too far and we were able to align it perfectly resulting in a -59 dBm receive strength, 32 QAM modulation and 100 mbps throughput both directions. Latency was about 1 ms. We used 2 ft dish antennas because we were concerned about rain fade and wanted sufficient link margin for 99.999% up-time.
The setup script was easy and only 4 steps long and I had a working link, very intuitive. You don't have to be SAF certified to understand the interface, again, very intuitive. You have a choice of three channels and the ability to do a frequency scan. Also, changes made to the config can be copied to the remote end with a single button click.
The quality of the workmanship is excellent. Pieces are well machined and well finished. The Arkivator dish antennas are also well made and have an extremely tight pattern and good front to back ratio. At 24 GHz, the fresnel zone is small and the beam width of the antennas is very tight so proper alignment is a must.
The link was a bit over a mile, not too far and we were able to align it perfectly resulting in a -59 dBm receive strength, 32 QAM modulation and 100 mbps throughput both directions. Latency was about 1 ms. We used 2 ft dish antennas because we were concerned about rain fade and wanted sufficient link margin for 99.999% up-time.
The setup script was easy and only 4 steps long and I had a working link, very intuitive. You don't have to be SAF certified to understand the interface, again, very intuitive. You have a choice of three channels and the ability to do a frequency scan. Also, changes made to the config can be copied to the remote end with a single button click.
While there are other 24 GHz products out there like the Ubiquiti airFiber that may give more throughput, this one is simple, robust, has the ability to use different antennas. I will definitely push this product to our customers.
Wednesday, November 28, 2012
Trunk two RB250GS Switches Together
Scenario: You have one MikroTik RB250GS switch running 802.1Q vlans and you
want to extend all or some of those vlans to a second switch. The
following diagram borrowed from a post by Ozelo explains:
The configuration of the first switch (192.168.88.1) is explained in a previous example 802.1Q Router on a Stick Example. The main change to that example is the configuration of port ether5 since we want it to pass all the vlans to the second switch. The two pales you need to make changes are the VLAN tab and the VLANs tab. Confusing, yes but note the "s" on VLAN on one tab.
Configure the first switch as follows:
Switch 1 - VLAN Tab
Switch 1 - VLANs Tab
Then configure the second switch as follows. Please note we have set the IP address of the second switch to 192.168.88.10 so as not to duplicate the witch 1 IP address. This is done on the System tab. In case you ever wonder why there is no setting for netmask or default gateway, that is because the switch does a little magic in determining the source of the packet and returning it to the host without the need for those two pieces of information.
Switch 2 - VLAN Tab
Switch 2 - VLANs Tab
All that remains is to create the vlan interfaces on the router and assign IP addresses, DHCP server, etc. to them. Here is a screen shot of the router used for this example, interfaces and IP addresses. The IP here is the one being used to manage the switches:
That is it, you should now have two switches trunked together passing vlans to the second switch.
The configuration of the first switch (192.168.88.1) is explained in a previous example 802.1Q Router on a Stick Example. The main change to that example is the configuration of port ether5 since we want it to pass all the vlans to the second switch. The two pales you need to make changes are the VLAN tab and the VLANs tab. Confusing, yes but note the "s" on VLAN on one tab.
Configure the first switch as follows:
Switch 1 - VLAN Tab
Switch 1 - VLANs Tab
Then configure the second switch as follows. Please note we have set the IP address of the second switch to 192.168.88.10 so as not to duplicate the witch 1 IP address. This is done on the System tab. In case you ever wonder why there is no setting for netmask or default gateway, that is because the switch does a little magic in determining the source of the packet and returning it to the host without the need for those two pieces of information.
Switch 2 - VLAN Tab
Switch 2 - VLANs Tab
All that remains is to create the vlan interfaces on the router and assign IP addresses, DHCP server, etc. to them. Here is a screen shot of the router used for this example, interfaces and IP addresses. The IP here is the one being used to manage the switches:
That is it, you should now have two switches trunked together passing vlans to the second switch.
Subscribe to:
Posts (Atom)


