This document will show when customer run OSPF with PE in that case the routes advertised from one CE to another CE travelling MPLS backbone should be IA(Inter Area) routes but in some cases the routes could be external. MPLS backbone is working as trasparent to the customer, so for customer every route should be inter area route. But may be a day you get a call from your customer which is getting all its routes as external routes instead of inter area routes. I have tried to explain how the external route constraint can be removed by taking a simple precaution.
Download the Full Document
regards
shivlu jain
Click Here To Read Rest Of The Post...
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.
Friday, November 7, 2008
Thursday, November 6, 2008
What Is PHP (Penultimate Hop Popping)
What is PHP ?
PHP is penultimate hop popping which means remove the label one hop before its destination. In figure 1 LER-1 wants to reach on CPE lan for this it is getting route from LER-2 with its loopback as next-hop address. For loopback it will check the routing table lookup and reverse lookup will be performed. After that packet will be forwarded to the next router and same process will be followed till it reach LER-2. You can see the label exchange on LER-1 which is pushing a label of 17 and forwarding to LSR-1. LSR will swap the label with 20 and forward the packet to LSR-2. LSR-2 will swap the label with 21 and forward to LER-2. Now LER-2 will check this is the directly connected interface and label will be popped off and normail ip packet will be delivered.

Lets see in figure 2 what will happen in case of PHP. The packet will be forwarded to the next router and same process will be followed till it reach LER-2. You can see the label exchange on LER-1 which is pushing a label of 17 and forwarding to LSR-1. LSR will swap the label with 20 and forward the packet to LSR-2. Now LSR-2 will forward the packet by removing the label. When LER-2 will get the packet it has to do perform only ip lookup. This is case of directly connected interface.
But in case of VPN when the CPE routes will be forwarded a vpn label is also forwarded along with MP-BGP. So a packet consists of two labels one is vpn label and another is ip label. The top label of stack is always igp label and inner label is vpn label. So when PHP will perform on LSR-2 it wll remove the IGP label and forward the packet with vpn label. On LER-2 it wil check it is for my directly connected interface and vpn label will popped off and normail ip packet will be delivered to CPE.
Note:- For directly connected interfaces and summary addresses always label 3 will be advertised to adjacent neighbors which is used for PHP.

Author of the post is Shivlu Jain
Click Here To Read Rest Of The Post...
Wednesday, November 5, 2008
Double Traceroute In MPLS
If you are getting double traceroutes in MPLS cloud then definately you are running with cisco bug CSCef16357. From one of the thread Click Here I come to know about that bug.
Cisco has clearly mentioned that this is the hardware issue of sup720 in 6500 chassis.
CSCef16357 Bug Details
MPLS/SUP720 : egress CE appears twice in traceroute
Symptoms
In a MPLS/VPN environment, egress CE is seen twice in traceroute.
Conditions
This problem is seen if both following conditions are met :
- egress PE is a cat6k with sup720
- MPLS core is hidden (no tag-switching ip propagate-ttl
is configured on
ingress PE)
N.B. Same problem is seen in a simple MPLS environment (without VPN)
Workaround
none
Further Problem Description
This is an hardware problem and cannot be fixed by software.
It impacts all software versions
Click Here To Read Rest Of The Post...
Subscribe to:
Posts (Atom)