<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>BGP Auto FRR Archives - Network Solution</title>
	<atom:link href="https://blog.network-solution.net/tag/bgp-auto-frr/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.network-solution.net/tag/bgp-auto-frr/</link>
	<description></description>
	<lastBuildDate>Wed, 20 Apr 2016 21:18:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.7</generator>

<image>
	<url>https://blog.network-solution.net/wp-content/uploads/2021/06/favicon.ico</url>
	<title>BGP Auto FRR Archives - Network Solution</title>
	<link>https://blog.network-solution.net/tag/bgp-auto-frr/</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">88039135</site>	<item>
		<title>Example for Configuring BGP Auto FRR</title>
		<link>https://blog.network-solution.net/example-for-configuring-bgp-auto-frr/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=example-for-configuring-bgp-auto-frr</link>
					<comments>https://blog.network-solution.net/example-for-configuring-bgp-auto-frr/#comments</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Wed, 20 Apr 2016 21:18:02 +0000</pubDate>
				<category><![CDATA[BGP]]></category>
		<category><![CDATA[BGP Auto FRR]]></category>
		<category><![CDATA[Configuring BGP Auto FRR]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=478</guid>

					<description><![CDATA[<p>As shown in Figure 1, Router A belongs to AS 100; Router B, Router C, and Router D belong to AS 200. BGP Auto FRR needs to be configure so that the route from Router A to Router D can have backup forwarding information. Figure 1 Networking diagram of configuring BGP Auto FRR Configuration Roadmap &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/example-for-configuring-bgp-auto-frr/">Example for Configuring BGP Auto FRR</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/example-for-configuring-bgp-auto-frr/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">478</post-id>	</item>
		<item>
		<title>BGP Auto FRR</title>
		<link>https://blog.network-solution.net/bgp-auto-frr/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=bgp-auto-frr</link>
					<comments>https://blog.network-solution.net/bgp-auto-frr/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Wed, 20 Apr 2016 21:04:55 +0000</pubDate>
				<category><![CDATA[BGP]]></category>
		<category><![CDATA[BGP Auto FRR]]></category>
		<category><![CDATA[IPRAN]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=476</guid>

					<description><![CDATA[<p>As a protection measure against faults over links, BGP Auto Fast Reroute (FRR) is applicable to networks with primary and backup links. With BGP Auto FRR, traffic can be switched between two BGP peers or next hops within sub-seconds. With BGP Auto FRR, if a peer has multiple routes with the same prefix that are &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/bgp-auto-frr/">BGP Auto FRR</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/bgp-auto-frr/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">476</post-id>	</item>
	</channel>
</rss>
