In this topology a small test is elaborated where in the customer is forwarding the ip packets with ip precedence of 3 and service provider which is offering the mplsvpn sevrvices is not using any qos in the cloud but still the precedence sent by the customer is delivered to the remote locations. If means the service provider cloud preserves the ip precedence bits during the forwarding of vpn traffic.
Test Setup
TEST Policy is created on CE2 with precence value of 3 which is set to all the outgoing traffic from fa0/0. The marking of packets can be checked by enabling ip accounting.
CE2#
policy-map TEST
class class-default
set ip precedence 3
interface FastEthernet0/0
ip address 172.16.1.2 255.255.255.252
ip accounting output-packets
ip accounting precedence input
duplex auto
speed auto
service-policy output TEST
!
CE2#ping 10.1.1.2 repeat 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
!!
Success rate is 100 percent (2/2), round-trip min/avg/max = 1040/1110/1180 ms
CE2#
CE2#
CE2#sh interfaces fastEthernet 0/0 precedence
FastEthernet0/0
Input
Precedence 3: 2 packets, 228 bytes
2 packets sent from CE2 with ip precedence 3. Now the packets reached to the PE2 where in Fa0/1 is the receiving interface which is setting the class of service 3 with label 19. Label 19 is used for vpnv4 route.
PE2#
*Nov 7 00:45:09.999: MPLS: Fa0/1: recvd: CoS=3, TTL=253, Label(s)=19
*Nov 7 00:45:10.867: MPLS: Fa0/1: recvd: CoS=3, TTL=253, Label(s)=19
From PE2 the packet reached to P router whith COS 3 and because of PHP the transport label removed and packet forwarded with label 18 to PE1 with exit interface Fa0/0.
P#
*Nov 7 00:45:06.359: MPLS: Fa0/1: recvd: CoS=3, TTL=254, Label(s)=16/18
*Nov 7 00:45:06.363: MPLS: Fa0/0: xmit: CoS=3, TTL=253, Label(s)=18
*Nov 7 00:45:07.487: MPLS: Fa0/1: recvd: CoS=3, TTL=254, Label(s)=16/18
*Nov 7 00:45:07.491: MPLS: Fa0/0: xmit: CoS=3, TTL=253, Label(s)=18
PE1 received the packet with COS 3 and forward the packet towards fa0/0 interface which is the vrf interface and attached with customer.
PE1#
*Nov 7 00:43:38.591: MPLS: Fa0/1: recvd: CoS=3, TTL=253, Label(s)=18
*Nov 7 00:43:38.595: MPLS: Fa0/0: xmit: (no label)
*Nov 7 00:43:39.779: MPLS: Fa0/1: recvd: CoS=3, TTL=253, Label(s)=18
*Nov 7 00:43:39.783: MPLS: Fa0/0: xmit: (no label)
CE1 received the packets with the ip precedence 3.
CE1#sh interfaces fastEthernet 0/0 precedence
FastEthernet0/0
Input
Precedence 3: 2 packets, 228 bytes
SDN and NFV is the next phase of technology change which will help service provider to launch the services in single click. This is all about the programmability of the networks by using open source software defined network controller.
Monday, November 9, 2009
End To End CPE QOS Marking Delivery Without Enabling QOS In Backhaul
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment