Author: j2sw
Upgrading EPMP GPS Firmware
Beginning with System Release 2.0, users can upgrade the firmware of the on-board GPS chip present on the Connectorized Radio with Sync.
To upgrade the on-board GPS chip on a Connectorized Radio with Sync:
1. Navigate to Monitor => GPS to check the GPS Firmware Version that is currently present on the radio.
2.If the GPS Firmware Version displays AXN_1.51_2801, navigate to Tools => Software Upgrade
3.Under the G P S F i r m w a r e upgrade section, select the same package used to upgrade the device’s firmware ex: ePMP-GPS_Synced-v2.4.2.tar.gz.
4.Click upgrade
5. The upgrade can take up to 3 minutes. Once the upgrade is done, the radio’s UI prompts for a reboot and the reboot button will be highlighted.
6.Click the Reboot button on the top right corner of the UI.
7.Once the radio has completed its reboot process, check under the Monitor => GPS page to check the firmware version
Helpful Mikrotik BGP route print
/ip route print where received-from=<PEERNAME>
Replace <PEERNAME> with the name of one of your peers to show the routes received from that particular BGP peer.
Open Source Box Design
One of the biggest challenges WISPs and anyone deploying wireless gear is power and distribution. I have put together a checklist for purchasing items to make a standard box MTIN would deploy. This is not designed to be a how-to, but rather a “What to buy” guide.
Link to the PDF (7Meg Download)
Throughout this documents I make notes based upon experience. As with anything, these are not hard rules. They are meant to be guidelines to follow. Please adapt to your uses. For example, if you don’t have any non-cambium radios you don’t need the POE injectors found on page 5.
If you find this document useful please feel free to send your thoughts, beer money, or other admiration. Links to http://www.mtin.net/blog are always appreciated, as well as twitter ( @j2sw ) or facebook follows (http://www.facebook.com/mtinnet )are always appreciated. If you reproduce any parts of this Open Source document please give credit to the original source.
I have been wanting to write this article for awhile. When the topic is fresh in my mind I am usually too tired from a day of climbing. By the time things get around the lessons learned have escaped me. So, after a day of being in the sun on a 150 foot monopole I figured I would share some best practices. These are aimed toward the WISP who wants to maximize their climbs.
1.Tighten sector brackets on the ground and other bolts. If it is holding it to the sector tighten it. The idea is the climber wants to be able to position the antenna against the mounting pole as easily as possible without needing extra hands. Sometimes having both hands free is a challenge. If you want to adjust downtilt on the ground the following links can help speed up the process. This is not necessary nor is it a requirement. It just is one less thing to do in the air. Some helpful Links:
Wisp-Router downtilt calculator
I am planning on another blog article about downtilt calculations and my thoughts. We will go into this in a future post.
2.For Wireless backhaul shots in the 0-7 mile range use google earth. Draw a line between the two points and use two reference points to get in the neighborhood. By looking at the below screenshot I know to align my path over the edge of the building almost at the base of the tower. This helped me determine mounting location and get a pretty close aim. You can get fancy with compasses, GPS alignment devices, and other high-tech toys, but people are typically visual people. Having a reference point is easier on the mind than having a number like 121 degrees off north. Microwave shots are a different beast so don’t lump tight beamwidth licensed links into the above statement.
3.Don’t get too hung up on labels. Instead I like to color code things. If I am putting up 3 sectors I will get some colored tape and label them with a blue piece, a red piece, and a green piece. This way if the client wants to have a sector facing north We have the software labeled blue. I can identify color and tell the ground crew I faced the blue sector north. Makes things easier in the high stress environment of being hundreds of feet in the air. The cellular companies have some standardized labeling of their sectors:
Alpha is the North FACING vertical antenna on the cell tower
Beta is the Southeast FACING vertical antenna on the cell tower
Gamma is the Southwest FACING vertical antenna on the cell tower
I would suggest come up with a SOP for all your tower deployments, but be flexible. Due to the various mounting locations it’s not always prudent to cookie cutter a WISP deployment like the cellular folks do. I have installed gear on towers where you have a small corner of a rooftop or grain facility. Due to other things being up there, the fact you are trading service or paying very little, your mounting options may be limited.
4.On a related note color code everything. If you use colored tape, make sure to match the ethernet cables going to the sectors. This way it is easier to identify the cable going to the sector. This also helps in easier identification of where things are plugged in.
5.There are six phases of the a WISP deployment.
Stage one- assembly and staging
Stage two – Mounting radio equipment and antennas
Stage three – Connecting power and connectivity.
Stage four – Physical adjustment and tuning
Stage five – Testing and tweaking
Stage six – cleanup and zip up
Think about each of these. This will be another future blog post.
6.Have a plan of action. Have a flexible order of doing things. Be able to adjust this on the fly due to various factors. Sometimes is makes sense to mount the sectors, backhauls, and any other boxes at the top. Once you have them mounted then make the connections. Other times it may make sense to run the cable when you mount the device.
7. Have a loadout of specific tools in a bucket or tool pouch. I like to include the following:
Knife – Automatic or assisted opening
Crescent wrench
Super-88 Tape
Zip ties
Phillips Screwdriver
Flat Screwdriver
Slip Joint pliers
Other tools such as ratchet wrenches, different sized tools, power tools, etc. are handy, and can make life easier. However, the above tools will allow you to 90% of what you need to do to install or remove most WISP equipment. The flat screwdriver can be used to pry things loose or for leverage.
8.If you can do it on the ground do it. Terminating and testing cat-5 is easier on the ground than 150 feet in the air.
9. Train the ground crew to think about how this affects someone on the tower. Most of the time folks don’t have the luxury of platforms. So they are hanging off the tower in awkward positions. Doing a pull with 3 sectors attached to a load line might seem like you are saving time, but it might make things complicated for the climber. Sometimes, 3 pulls might make their life easier. They only have to deal with one thing at a time. They aren’t fighting trying to unhook multiple antennas or figuring out what is what. This is where straps come in very handy. A strap allows a climber some extra flexibility to move things around and position them better.
10.Have a checklist of sorts. This can be a running thing as you go along. I routinely tell the ground crew to remind me to do this. If you have someone writing this stuff down they can read it back to you before you come down.
There are a great variety of tools, tricks, and ways of putting stuff on the tower. Many people have their own ways of doing things. These are just some of the best practices I have come up with through experience. We could debate tape vs zip ties and other things for hours. Please leave comments and some tips that make your life easier.
New Software Features
RoMON
another blog post will follow on this.
Need to use Winbox 3
FastTrack
FastPath + Connection Tracking
FastTrack Accelerates packet processing for specific connection tracking entries
Full NAT support
Works with IPv4/TCP and IPv4/UDP
MUM2015: Janis opening Remarks
Recently Introduced
hAP Lite (Home Access Point Lite)
2.4GHZ Dual Chain
5volt USB powered
CCR1009 PC
9 Core Tilera
Passive cooling
* Gigabit, 1SFP, 1SFP+
PowerBox
Outdoor Ethernet router
POE Out
S+2332LC10D
10KM Bidirectional SFP+
New Products:
hAP
951 replacement
regular power input
POE-IN
PoE-out on port 5
hAP ac lite
2.4GHZ dual chain 802.11n
5GHZ single chain 802.11ac
hAP AC
Gigabit
2.4GHZ high power 2 chain 802.11n
5GHZ high power 3 chanin 802.11ac
5Gigabit and 1 SFP cage
CRS112-8G-4S-IN
4 SFP ports
8 Gigabit copper
QRT 5GH
miniPCIe card with 5GHZ triple chain 802.11ac
QRT 5 AC
802.11ac upgrade for QRT5
SXT HG5 AC
802.11ac
RB3011 Series
Upgrade for 2011
Dual core 1.2GHZ ARM CPU
2x performance of 2011
10x Gigabit ethernet
niniPCIe slot and SFP port
QuickMount
Easy way to mount to wall for SXT
Can have back to back setup
Available Q3
DynaDish 5
802.11ac
5GHZ dual chain board integrated into 23DBI dish
8 Degree beamwidth
$179
ePMP 100 version 2.4 released
New Features added:
Release 2.4 adds the following features:
eFortify™ Enhancements:
- New ePTP mode operation: The release introduces a new mode of operation for point-to-point configuration providing significantly lower latency than other modes. Not available for DFS bands.
- Improvements to VoIP performance
- Ability to configure the Max MCS independently in each direction
eCommand™ Enhancements:
- eAlign: The release introduces eAlign (found under the Tools menu), a tool to aid with link alignment
- Session Time per SM on the AP (under Monitor->Wireless)
- Improvements to the throughput chart on the GUI dashboard (under “Home”)
Internet Routing Registries
Routing Registries are a mysterious underpinning of the peering and BGP world. To many they are arcane and complicated. If you have found this article you are at least investigating the use of a registry. Either that or you have ran out of fluffy kittens to watch on YouTube. Either way one of the first questions is “Why use a routing registry”.
As many of us know BGP is a very fragile ecosystem. Many providers edit access lists in order to only announce prefixes they have manually verified someone has the authority to advertise. This is a manual process for many opportunities for error. Any time a config file is edited errors can occur. Either typos, misconfiguration, or software bugs.
Routing registries attempt to solve two major issues. The first is automating the process of knowing who has authority to advertise what. The second is allowing a central repository of this data.
So what is a routing Registry?
From Wikipedia: An Internet Routing Registry (IRR) is a database of Internet route objects for determining, and sharing route and related information used for configuring routers, with a view to avoiding problematic issues between Internet service providers.
The Internet routing registry works by providing an interlinked hierarchy of objects designed to facilitate the organization of IP routing between organizations, and also to provide data in an appropriate format for automatic programming of routers. Network engineers from participating organizations are authorized to modify the Routing Policy Specification Language (RPSL) objects, in the registry, for their own networks. Then, any network engineer, or member of the public, is able to query the route registry for particular information of interest.
What are the downsides of a RR?
Not everyone uses routing registries. So if you only allowed routes from RR’s you would get a very incomplete view of the Internet and not be able to reach a good amount of it.
Okay, so if everyone doesn’t use it why should i go to the trouble?
If you are at a formal Internet Exchange (IX) you are most likely required to use one. Some large upstream providers highly encourage you to use one to automate their process.
What are these objects and attributes?
In order to partipate you have to define objects. The first one you create is the maintainer object. This is what the rest of the objects are referenced to and based from. Think of this as setting up your details in the registry.
From this point you setup “object types”. Object types include:
as-set
aut-num
inet6num
inetnum
inet-rtr
key-cert
mntner
route
route6
route-set
If you want to learn more about each of these as well as templates visit this ARIN site.
So what do I need to do to get started?
The first thing you need to do is setup your mntner object in the registry. I will use ARIN as our example. You can read all about it here:https://www.arin.net/resources/routing/.
You will need a couple of things before setting this up
1.Your ARIN ORGID
2.Your ADMIN POC for that ORGID
3.Your TECH POC for that ORGID
Once you have these you can fill out a basic template and submit to ARIN.
mntner: MNT-YOURORGID
descr: Example, Inc.
admin-c: EXAMPLE123-ARIN
tech-c: EXAMPLE456-ARIN
upd-to: hostmaster@example.net
mnt-nfy: hostmaster@example.net
auth: MD5-PW $1$ucVwrzQH$zyamFnmJ3XsWEnrKn2eQS/
mnt-by: MNT-YOURORGID
referral-by: MNT-YOURORGID
changed: hostmaster@example.net 20150202
source: ARIN
The templates is very specific on what to fill out. The mnt-by and referral-by are key to following instructions. MD5 is another sticking point. The process is documented just in a couple of places. In order to generate your MD5-PW follow these instructions.
1.Go to https://apps.db.ripe.net/crypt/ Enter in a password. Make sure you keep this cleartext password as you will need it when sending future requests to ARIN’s Routing Registry.
2.Submit the password to get the md5 crypt password. Keep this password for your records, as you may need it when interacting with ARIN’s IRR in the future.
3.Add the following line to your mntner object template in the text editor.
auth: MD5-PW
Our example above has a MD5 password already generated.
Once this is done and created you can add objects. The most commonly added objects are your ASN and IP space.
Create your ASN object using the as-num template
aut-num: AS65534
as-name: EXAMPLE-AS
descr: Example, Inc.
descr: 114 Pine Circle
descr: ANYWHERE, IN 12345
descr: US
import: from AS65535 accept ANY
import: from AS65533 accept AS65534
export: to AS65533 announce ANY
export: to AS65535 announce AS2 AS65533
admin-c: EXAMPLE456-ARIN
tech-c: EXAMPLE123-ARIN
mnt-by: MNT-YOURORGID
changed: user@example.com 20150202
source: ARIN
password:
The things to know about the above template are the import and export attributes.
Now on to adding IP space
Suppose you have IP space of 192.0.2.0/24 Your template would look like:
inetnum: 192.0.2.0 – 192.0.2.255
netname: EXAMPLE-NET
descr: Example, Inc.
descr: 115 Oak Circle
descr: ANYWHERE, IN 12345
country: US
admin-c: EXAMPLE123-ARIN
tech-c: EXAMPLE456-ARIN
notify: user@example.com
mnt-by: MNT-YOURORGID
changed: user@example.com 20150202
source: ARIN
password:
The password attribute is the cleartext password for your MD5 key.
Further Reading:
Using RPSL in practice
Case Study from MidWest-IX
http://www.midwest-ix.com/blog/?p=67
Outlines a real world example of how an exchange benefits a network operator
You must be logged in to post a comment.