<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>XISP tips,news, &#38; technology &#187; POP. AP</title>
	<atom:link href="http://www.mtin.net/blog/tag/pop-ap/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mtin.net/blog</link>
	<description>Technology relating to networking and the XISP world</description>
	<lastBuildDate>Fri, 23 Jul 2010 17:43:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
		<item>
		<title>POP Redundancy</title>
		<link>http://www.mtin.net/blog/2009/11/20/pop-redundancy/</link>
		<comments>http://www.mtin.net/blog/2009/11/20/pop-redundancy/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 18:33:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Wireless]]></category>
		<category><![CDATA[Access Point]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[POP. AP]]></category>
		<category><![CDATA[redundancy]]></category>
		<category><![CDATA[tower]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=29</guid>
		<description><![CDATA[<p>Access point redundancy is one of the hardest things to achieve. This is because fixed wireless customers do not roam between access points.  You have a couple of tricks you can do to minimize downtime in the event of an AP failure.</p>
<p>The first thing to do is implement the same SSID across your network or even [...]]]></description>
			<content:encoded><![CDATA[<p>Access point redundancy is one of the hardest things to achieve. This is because fixed wireless customers do not roam between access points.  You have a couple of tricks you can do to minimize downtime in the event of an AP failure.</p>
<p>The first thing to do is implement the same SSID across your network or even per tower. If you are using Mikrotik you can implement connect lists to tell your clients to not connect unless it meets an acceptable signal level.  This way if one sector fails some of your clients might “jump” to another sector if they can connect to that sector at a good enough level.</p>
<p>Another tactic you can employ is putting an omni up with a Mikrotik added to it. Should one or more sectors fail you can add virtual SSIDS to the omni and bring up some customers.  These customers won’t be as good as if they were connected to a sector. However, they will be functional.  A good practice is to mount this omni, on a standoff,  at a different level than your sectors.  Also, if possible, run the cable for the omni down a different leg of the tower.  While this is not always possible, it does isolate the components somewhat from the others.  You could put a redundant omni with any vendor, not just Mikrotik.  You just might not be able to simulate multiple sectors like the Mikrotik does.</p>
<p>Yet another tactic with mikrotik is to add multiple connect lists to your CPE.  This can be cumbersome if you ever decide to change your network.  You have to edit those customer CPE, which can be time consuming.</p>
<p>Stay tuned for more in this continuing series.</p>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.mtin.net/blog/2009/11/20/pop-redundancy/&amp;n=POP+Redundancy&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.mtin.net/blog/2009/11/20/pop-redundancy/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-delicious">
			<a href="http://delicious.com/post?url=http://www.mtin.net/blog/2009/11/20/pop-redundancy/&amp;title=POP+Redundancy" rel="nofollow" class="external" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.mtin.net/blog/2009/11/20/pop-redundancy/&amp;t=POP+Redundancy" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-gmail">
			<a href="https://mail.google.com/mail/?ui=2&amp;view=cm&amp;fs=1&amp;tf=1&amp;su=POP+Redundancy&amp;body=Link: http://www.mtin.net/blog/2009/11/20/pop-redundancy/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Access%20point%20redundancy%20is%20one%20of%20the%20hardest%20things%20to%20achieve.%20This%20is%20because%20fixed%20wireless%20customers%20do%20not%20roam%20between%20access%20points.%C2%A0%20You%20have%20a%20couple%20of%20tricks%20you%20can%20do%20to%20minimize%20downtime%20in%20the%20event%20of%20an%20AP%20failure.%0D%0A%0D%0AThe%20first%20thing%20to%20do%20is%20implement%20the%20same%20SSID%20across%20your%20ne" rel="nofollow" class="external" title="Email this via Gmail">Email this via Gmail</a>
		</li>
		<li class="shr-googlebookmarks">
			<a href="http://www.google.com/bookmarks/mark?op=add&amp;bkmk=http://www.mtin.net/blog/2009/11/20/pop-redundancy/&amp;title=POP+Redundancy" rel="nofollow" class="external" title="Add this to Google Bookmarks">Add this to Google Bookmarks</a>
		</li>
		<li class="shr-hotmail">
			<a href="http://mail.live.com/?rru=compose?subject=POP+Redundancy&amp;body=Link: http://www.mtin.net/blog/2009/11/20/pop-redundancy/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Access%20point%20redundancy%20is%20one%20of%20the%20hardest%20things%20to%20achieve.%20This%20is%20because%20fixed%20wireless%20customers%20do%20not%20roam%20between%20access%20points.%C2%A0%20You%20have%20a%20couple%20of%20tricks%20you%20can%20do%20to%20minimize%20downtime%20in%20the%20event%20of%20an%20AP%20failure.%0D%0A%0D%0AThe%20first%20thing%20to%20do%20is%20implement%20the%20same%20SSID%20across%20your%20ne" rel="nofollow" class="external" title="Email this via Hotmail">Email this via Hotmail</a>
		</li>
		<li class="shr-linkedin">
			<a href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http://www.mtin.net/blog/2009/11/20/pop-redundancy/&amp;title=POP+Redundancy&amp;summary=Access%20point%20redundancy%20is%20one%20of%20the%20hardest%20things%20to%20achieve.%20This%20is%20because%20fixed%20wireless%20customers%20do%20not%20roam%20between%20access%20points.%C2%A0%20You%20have%20a%20couple%20of%20tricks%20you%20can%20do%20to%20minimize%20downtime%20in%20the%20event%20of%20an%20AP%20failure.%0D%0A%0D%0AThe%20first%20thing%20to%20do%20is%20implement%20the%20same%20SSID%20across%20your%20ne&amp;source=XISP tips,news, &amp; technology" rel="nofollow" class="external" title="Share this on LinkedIn">Share this on LinkedIn</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.mtin.net/blog/2009/11/20/pop-redundancy/&amp;t=POP+Redundancy" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=POP+Redundancy+-+http://tinyurl.com/354hv57&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-twittley">
			<a href="http://twittley.com/submit/?title=POP+Redundancy&amp;url=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;desc=Access%20point%20redundancy%20is%20one%20of%20the%20hardest%20things%20to%20achieve.%20This%20is%20because%20fixed%20wireless%20customers%20do%20not%20roam%20between%20access%20points.%C2%A0%20You%20have%20a%20couple%20of%20tricks%20you%20can%20do%20to%20minimize%20downtime%20in%20the%20event%20of%20an%20AP%20failure.%0D%0A%0D%0AThe%20first%20thing%20to%20do%20is%20implement%20the%20same%20SSID%20across%20your%20ne&amp;pcat=Technology&amp;tags=" rel="nofollow" class="external" title="Submit this to Twittley">Submit this to Twittley</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=POP+Redundancy&amp;body=Link: http://www.mtin.net/blog/2009/11/20/pop-redundancy/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Access%20point%20redundancy%20is%20one%20of%20the%20hardest%20things%20to%20achieve.%20This%20is%20because%20fixed%20wireless%20customers%20do%20not%20roam%20between%20access%20points.%C2%A0%20You%20have%20a%20couple%20of%20tricks%20you%20can%20do%20to%20minimize%20downtime%20in%20the%20event%20of%20an%20AP%20failure.%0D%0A%0D%0AThe%20first%20thing%20to%20do%20is%20implement%20the%20same%20SSID%20across%20your%20ne" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><a href="http://www.addtoany.com/add_to/digg?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy" title="Digg" rel="nofollow" target="_blank"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/icons/digg.png" width="16" height="16" alt="Digg"/></a> <a href="http://www.addtoany.com/add_to/linkedin?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy" title="LinkedIn" rel="nofollow" target="_blank"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/icons/linkedin.png" width="16" height="16" alt="LinkedIn"/></a> <a href="http://www.addtoany.com/add_to/stumbleupon?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy" title="StumbleUpon" rel="nofollow" target="_blank"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/icons/stumbleupon.png" width="16" height="16" alt="StumbleUpon"/></a> <a href="http://www.addtoany.com/add_to/twitter?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy" title="Twitter" rel="nofollow" target="_blank"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/icons/twitter.png" width="16" height="16" alt="Twitter"/></a> <a href="http://www.addtoany.com/add_to/wordpress?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy" title="WordPress" rel="nofollow" target="_blank"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/icons/wordpress.png" width="16" height="16" alt="WordPress"/></a> <a href="http://www.addtoany.com/add_to/facebook?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy" title="Facebook" rel="nofollow" target="_blank"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/icons/facebook.png" width="16" height="16" alt="Facebook"/></a> <a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.mtin.net%2Fblog%2F2009%2F11%2F20%2Fpop-redundancy%2F&amp;linkname=POP%20Redundancy"><img src="http://www.mtin.net/blog/wp-content/plugins/add-to-any/share_save_120_16.png" width="120" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/2009/11/20/pop-redundancy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
