<?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>All_about_network &#187; Huawei</title>
	<atom:link href="http://www.kuncar.net/blog/category/vendors/huawei/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kuncar.net/blog</link>
	<description></description>
	<lastBuildDate>Wed, 12 May 2010 00:09:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>From Huawei to HP&#8230;</title>
		<link>http://www.kuncar.net/blog/from-huawei-to-hp/2010/</link>
		<comments>http://www.kuncar.net/blog/from-huawei-to-hp/2010/#comments</comments>
		<pubDate>Wed, 12 May 2010 00:09:53 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[3com]]></category>
		<category><![CDATA[H3C]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Huawei]]></category>
		<category><![CDATA[commware]]></category>
		<category><![CDATA[vrp]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=523</guid>
		<description><![CDATA[This post will be slightly atypical for this blog, but I think it is rather important to sum up what happened in last approximately three years. I&#8217;ll try summarize some history behind the Huawei/H3C/3Com/HP products. The reason for this &#8220;history&#8221; lesson is that quite a lot of people is confused of what was/is/will be and [...]]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/from-huawei-to-hp/2010/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>QoS on Huawei equipment &#8211; Custom Queunig</title>
		<link>http://www.kuncar.net/blog/qos-on-huawei-equipment-custom-queunig/2009/</link>
		<comments>http://www.kuncar.net/blog/qos-on-huawei-equipment-custom-queunig/2009/#comments</comments>
		<pubDate>Thu, 26 Nov 2009 07:30:33 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[QoS]]></category>
		<category><![CDATA[ar-46]]></category>
		<category><![CDATA[classyfing]]></category>
		<category><![CDATA[Cusom Queuing]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[traffic behavior]]></category>
		<category><![CDATA[vrp 3.40]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=443</guid>
		<description><![CDATA[After some time I have finally some energy to publish a bit more of some stuff about Huawei QoS. The following article will be concentrating on Custom Queuing as it is seen on VRP 3.40 on AR series routers (namely AR46 and AR28). The first important thing to know is what the Custom Queuing actually [...]]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/qos-on-huawei-equipment-custom-queunig/2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>QoS operation on AR28 and AR46 with VRP 3.40</title>
		<link>http://www.kuncar.net/blog/qos-operation-on-ar28-and-ar46-with-vrp-3-40/2009/</link>
		<comments>http://www.kuncar.net/blog/qos-operation-on-ar28-and-ar46-with-vrp-3-40/2009/#comments</comments>
		<pubDate>Tue, 30 Jun 2009 22:59:00 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[QoS]]></category>
		<category><![CDATA[ACL]]></category>
		<category><![CDATA[classyfing]]></category>
		<category><![CDATA[qo]]></category>
		<category><![CDATA[vrp]]></category>
		<category><![CDATA[vrp 3.40]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=312</guid>
		<description><![CDATA[As one of the previous posts was about configuration of AR46 and 28 series routers this one will be kind of a follow-up article about the QoS on these devices or rather some real example. But as usually first things first &#8211; the dry theory of QoS.  As you probably know QoS is abbreviation for [...]]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/qos-operation-on-ar28-and-ar46-with-vrp-3-40/2009/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Frame-relay multilink and VRF on AR46 platform with VRP 3.40</title>
		<link>http://www.kuncar.net/blog/frame-relay-multilink-and-vrf-on-ar46-platform-with-vrp-340/2009/</link>
		<comments>http://www.kuncar.net/blog/frame-relay-multilink-and-vrf-on-ar46-platform-with-vrp-340/2009/#comments</comments>
		<pubDate>Sun, 17 May 2009 23:10:14 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[ar-46]]></category>
		<category><![CDATA[frame relay]]></category>
		<category><![CDATA[multilink]]></category>
		<category><![CDATA[vrf]]></category>
		<category><![CDATA[vrp]]></category>
		<category><![CDATA[vrp 3.40]]></category>
		<category><![CDATA[vrrp]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=58</guid>
		<description><![CDATA[So time had come to (finally) leave the IPSec and move on to some other stuff. This scenario will show how to configure Frame Relay multilink, some QoS and all of that in combination with VRF and VRRP technology. As this topic is rather more extensive than the previous ones it will be divided into [...]]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/frame-relay-multilink-and-vrf-on-ar46-platform-with-vrp-340/2009/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>l2tp over IPSec scenario</title>
		<link>http://www.kuncar.net/blog/l2tp-over-ipsec-scenario/2009/</link>
		<comments>http://www.kuncar.net/blog/l2tp-over-ipsec-scenario/2009/#comments</comments>
		<pubDate>Sat, 09 May 2009 23:59:14 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Security Links]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[L2tp]]></category>
		<category><![CDATA[vrp 3.40]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=77</guid>
		<description><![CDATA[So this is the long promised scenario that can be used with windows XP (even though it is not really user friendly). If you need a &#8220;PC-client &#8211; VPN-concentrator&#8221; scenario. Huawei does offer only one-way ticket for you and it is l2tp over IPSec. Unless you want to use some MPLS over IPSec which is [...]]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/l2tp-over-ipsec-scenario/2009/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Port isolate vs. Mac Forced Forwarding</title>
		<link>http://www.kuncar.net/blog/mac-forced-forwarding/2009/</link>
		<comments>http://www.kuncar.net/blog/mac-forced-forwarding/2009/#comments</comments>
		<pubDate>Thu, 09 Apr 2009 16:28:10 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[mac-forced-forwarding]]></category>
		<category><![CDATA[port isolate]]></category>
		<category><![CDATA[S3900]]></category>
		<category><![CDATA[S5600]]></category>
		<category><![CDATA[S6500]]></category>
		<category><![CDATA[VRP 3.10]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=211</guid>
		<description><![CDATA[<img class="alignleft size-thumbnail wp-image-118" title="Huawei Logo" src="http://www.kuncar.net/blog/wp-content/uploads/2009/03/huawei_logo_001-150x150.jpg" alt="Huawei Logo" width="120" height="120" />Let me first say that these two features are supposed to do very similar things - they are designed to separate access users so their traffic cannot go directly between them without any control. This is a must as most of the attacks are actually executed from inside your own network and specifically in the same subnet where the]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/mac-forced-forwarding/2009/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Huawei&#8217;s send command</title>
		<link>http://www.kuncar.net/blog/huaweis-send-command/2009/</link>
		<comments>http://www.kuncar.net/blog/huaweis-send-command/2009/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 22:21:28 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[vrp]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=177</guid>
		<description><![CDATA[<img class="alignleft size-thumbnail wp-image-118" title="Huawei Logo" src="http://www.kuncar.net/blog/wp-content/uploads/2009/03/huawei_logo_001-150x150.jpg" alt="Huawei Logo" width="120" height="120" />This article is just about small, handy and not-so-widely known command in all Huawei's equipment. The command is in user-view and is called send.

If you are wandering what exactly does this do the answer is quite simple - it is sort of instant messaging built into every VRP I have seen. It enables to send message to any console/terminal]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/huaweis-send-command/2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NAT NAPT PAT on AR routers (all sw series)</title>
		<link>http://www.kuncar.net/blog/nat-napt-pat-on-ar-routers-all-sw-series/2009/</link>
		<comments>http://www.kuncar.net/blog/nat-napt-pat-on-ar-routers-all-sw-series/2009/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 17:48:26 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[NAPT]]></category>
		<category><![CDATA[NAT]]></category>
		<category><![CDATA[PAT]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=60</guid>
		<description><![CDATA[<img class="alignleft size-thumbnail wp-image-118" title="Huawei Logo" src="http://www.kuncar.net/blog/wp-content/uploads/2009/03/huawei_logo_001-150x150.jpg" alt="Huawei Logo" width="120" height="120" />So this is an article I was not really thinking to write but after certain experience I decided to put some light into this topic. Even though this is explained in the documentation (even though very chaotically) I put here some simple and easily adjustable examples of NAT/NAPT or if you want PAT.

So first thing you need to know]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/nat-napt-pat-on-ar-routers-all-sw-series/2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some GRE/IPSec and basic QoS scenarios on AR 19-X and VRP 5.20 Part II.</title>
		<link>http://www.kuncar.net/blog/some-greipsec-and-basic-qos-scenarios-on-ar-19-x-and-vrp-520-part-ii/2009/</link>
		<comments>http://www.kuncar.net/blog/some-greipsec-and-basic-qos-scenarios-on-ar-19-x-and-vrp-520-part-ii/2009/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 16:51:17 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[ACL]]></category>
		<category><![CDATA[adsl]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[marking]]></category>
		<category><![CDATA[pppoe]]></category>
		<category><![CDATA[QoS]]></category>
		<category><![CDATA[shaping]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=52</guid>
		<description><![CDATA[<img class="alignleft size-thumbnail wp-image-118" title="Huawei Logo" src="http://www.kuncar.net/blog/wp-content/uploads/2009/03/huawei_logo_001-150x150.jpg" alt="Huawei Logo" width="120" height="120" />

So after previous post the whole setup should be working. But there are some things to be done yet. The heading says that the missing part is the QoS. So let's have a closer look.

Step one is easy - just create some ACLs to match the traffic in our case it is goes like this:
#
acl number 3001 name black
rule]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/some-greipsec-and-basic-qos-scenarios-on-ar-19-x-and-vrp-520-part-ii/2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Troubleshooting IPSec on Huawei routers</title>
		<link>http://www.kuncar.net/blog/troubleshooting-ipsec-on-huawei-routers/2009/</link>
		<comments>http://www.kuncar.net/blog/troubleshooting-ipsec-on-huawei-routers/2009/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 00:23:07 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[ike]]></category>
		<category><![CDATA[IPSec]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[troubleshooting]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=62</guid>
		<description><![CDATA[<img class="alignleft size-thumbnail wp-image-118" title="Huawei Logo" src="http://www.kuncar.net/blog/wp-content/uploads/2009/03/huawei_logo_001-150x150.jpg" alt="Huawei Logo" width="120" height="120" />Ok so in my previous posts I described the most common config of IPsec with IKE. For troubleshooting this config there are few simple things one should check for basic troubleshoot.

No. 1 Check display IKE sa command in user view

Output of this command should show you two IKE entries. It is necessary to be two because if there is]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/troubleshooting-ipsec-on-huawei-routers/2009/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
