Maipu - Rate Limit

In this section, we will see about Maipu Switching QOS feature, Rate Limit.. This is normally used in Service provider scenario, When service provider is using Maipu 3400 Metro E switch. Service provider will limit the bandwidth of particular port, as agreed with customer for example 25 MB. Will configure some burst also.

Let’s see how rate limit feature is used in Maipu switches-

Rate Limitation

In order to avoid overloading and congestion of information which passes in network, Maipu series switches provide rate limitation based on port input direction. It means that it processes limitation to the total rate of port receiving direction. The flow with exceeding rate will be dropped. Configure the parameter as the bandwidth threshold (Kbit, 64K is the minimal granularity) and the burst flow (byte).

To provide different rate limitations for different time periods, each port can be configured with eight rate limitations of different priorities. Each rate limitation can be bound with the time domain. For the valid items, the priority decides which one takes effect. The priority 0 is highest and the priority 7 is lowest.

Basic Commands

### These are port mode commands

Command	Description
rate-limit  pri rate burst-size [time-rang time-rang name]	Configure the rate limitation of a port; the granularity of the rate is 64K and the unit of the burst­­-size is byte.
no rate-limit pri	Cancel one rate limitation of a port

rate-limit  pri rate burst-size

When users configuring the command, the input parameters may be different with the practical value configured successfully. Because the drive adjusts the value input by users according to the chip. The final verity value of the rate is an integer multiple of 64.

When the input value is not 64, the port adjusts the value as a minimal integer multiple of 64 which are greater than the present value. The revised value of Burst-size is an integer multiple of 4096. The average rate of the command at the port inputting direction is the value of the rate. The bursting flow actually is the depth of the token barrel. It means the allowed biggest flow size of each bursting.

Syntax	Description
Rate	Configure the bandwidth threshold with 64k step length and its value range is among 0~16777152.
burst-size	The range of bursting flow is among 4096~16773120.

Configuration template

Configure the rate limitation for a port, the value of the rate is 250000 and the value of the burst-size is 12176.

Switch(config)#port 0/1

Switch(config-port-0/1)#rate-limit 1 250000 12176 time-rang rate

Switch(config-port-0/1)#exit

### Here you can see we are binding, rate limit with Time based ACL. You can configure normally also without time base ACL, like below example - 

port 0/3

port-type uni

uni-isolate isolated

port access vlan  10

rate-limit 46080 4096

ethernet uni-id UNI-port-0/5

ethernet uni-type bundling

load-interval 30

exit

Monitoring:

Display the configuration of port0/1:

Command: show rate-limit port 0/1

Displayed result:

port 0/1

rate-limit 1 250048 12288 time-rang rate

Hope this post will be helpful for you.. 

For any queries and feedback, Plz put comments with Name/URL option in profile and leave mail id.. 

Maipu and Cisco - MPLS L2VPN and AToM

As discussed in last post about MPLS L2VPN. In this post we will see the configuration for Cisco and Maipu Router both.First of all this technology is known as AToM (Any Traffic over MPLS).

            In this example I tested Maipu 3840 and Cisco 1841. I only taken two routers, simulating that these are acting as PE. Here I shown computers , Both are in same subnet. That means over MPLS cloud we are creating a L2 tunnel.

So that these two laptops can communicate, which are in same subnet.

            In real time this laptops are replaced with Routers and these IP address are assigned to Routers and they can ping each other, It may be /24 or /32. It totally depends on Customer requirement.

For testing and understanding, I feel this is good example. Here you can know how your L2circut is formed from your site to another site.

            In last post, I shown Full setup, This is just for compatibility with Cisco and Maipu. In Cisco little bit more configuration to setup MPLS L2VPN.

Topology :

Configuration -

Cisco 1841 configuration:

pseudowire-class a
 encapsulation mpls

interface Loopback0
 ip address 18.18.18.18 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
 mpls ip 
mpls label protocol ldp
 xconnect 37.37.37.37 100 pw-class a
!
interface FastEthernet0/1
 ip address 9.0.10.18 255.255.255.0
 duplex auto
 speed auto
 mpls ip
mpls label protocol ldp
!

!
router ospf 1
 log-adjacency-changes
  network 9.0.10.0 0.0.0.255 area 0
 network 18.18.18.18 0.0.0.0 area 0

mpls ldp router-id Loopback0

MP3840 configuration:

ip mef

ip load-sharing per-destination

mpls ip

interface loopback0

 ip address 37.37.37.37 255.255.255.255

 exit

interface gigaethernet0

 ip address 9.0.10.19 255.255.255.0

 mpls ip

 mpls ldp

 exit

interface gigaethernet1

 mpls ip

 xconnect 18.18.18.18 100 encapsulation mpls

 mpls ldp

 exit

                                    

router ospf 1

 router-id 37.37.37.37

 network 9.0.10.0 area 0

 network 37.37.37.37 0.0.0.0 area 0

 exit

mpls ldp

 router-id 37.37.37.37

 transport-address 37.37.37.37

 targeted-peer 18.18.18.18

 exit

-- you are done, yes but many of you thinking its very simple. yes its simple the important is reachability with peer ip address (loopback IP). That means if you face any issue in xconnect, First you have to check IGP status and routing. It use IGP routing to reach peer router. 

Here same example with Maipu to Maipu for better understanding.

MAIPU TO MAIPU

Configurations

MP3780 configuration :

ip mef

ip load-sharing per-destination

mpls ip

           

interface loopback0

 ip address 37.37.37.37 255.255.255.255

 exit

interface gigaethernet0

 ip address 1.1.1.2 255.255.255.0

 mpls ip

 mpls ldp

 exit

interface gigaethernet1

 mpls ip

 xconnect 18.18.18.18 100 encapsulation mpls

 mpls ldp

 exit

                                   

router ospf 1

 router-id 37.37.37.37

 network 1.1.1.0 0.0.0.255 area 0

 network 37.37.37.37 0.0.0.0 area 0

 exit

mpls ldp

 router-id 37.37.37.37

 transport-address 37.37.37.37

 targeted-peer 18.18.18.18

 exit

MP3840 configuration :

ip mef

ip load-sharing per-destination

mpls ip

interface loopback0

 ip address 18.18.18.18 255.255.255.255

 exit

interface gigaethernet0

 ip address 1.1.1.1 255.255.255.0

 mpls ip

 mpls ldp

 exit

interface gigaethernet1

 mpls ip

 xconnect 37.37.37.37 100 encapsulation mpls

 mpls ldp

 exit

                                    

router ospf 1

 router-id 18.18.18.18

 network 1.1.1.0 0.0.0.255 area 0

 network 18.18.18.18 0.0.0.0 area 0

 exit

mpls ldp

 router-id 18.18.18.18

 transport-address 18.18.18.18

 targeted-peer 37.37.37.37

 exit

Hope this information will help you for better understanding about Cisco AToM and Maipu MPLS L2VPN.

For more information about AToM - Click here 

For any feedback and queries, Plz put comment with your Name and Mail id..