Tuesday, November 29, 2011

The Evolution of Google Search in Six Minutes

Google has shared the journey started from 1996 till now. How the different milestones has been achieved with different needs. In fact, necessity is the mother of invention...

Click Here To Read Rest Of The Post...

Sunday, November 27, 2011

History Of MPLS-TP (MPLS-Transport Profile)

Most of the operators are using circuit switched technology as transport network. But most of the services are packet based services, so why not to use packet based networks to offer high bandwidth packet based services. The need of high bandwidth hungry application demands to upgrade the infrastructure. But the same time operators want to reduce their per bit infrastructure cost with minimal capex and opex involved. MPLS had already been deployed widely to offer packet based services, then why not to use MPLS as transport too. This was the reason to add T-MPLS (Transport MPLS) for transport services too. T-MPLS was subset of MPLS. T-MPLS discussion was initially started by ITU-T in 2006. At that time, ITU shown their interest to use the existing MPLS framework defined by IETF and incorporate all the MPLS functionalities in T-MPLS.

After some time, the T-MPLS reached the stage where in some vendors started building their product by adding T-MPLS capabilities. But at the same time, IETF was also working on PWE3 to emulate any kind of access service over packet switched network over MPLS. On April 18, 2008 ITU and IETF had formed a joint working team to address all the issues and ceased the T-MPLS implementation. Thereafter, T-MPLS was changed to MPLS-TP.

Click Here To Read Rest Of The Post...

Tuesday, November 22, 2011

Requirements Of MPLS-TP (Transport Profile)

Requirements of MPLS-TP

1. It must be a packet switching technology with MPLS Traffic Engineering capabilities.
2. It must be able to inter operate with existing IETF MPLS [RFC3031] and IETF PWE3 [RFC3985] control and data planes where appropriate.
3. It must support point to point and point to multipoint.
4. MPLS-TP MUST support static provisioning.
5. It must support ping and trace for O&M.
6. It must support loopback for O&M.

For more please refer the MPLS-TP requirements.

Click Here To Read Rest Of The Post...

Monday, November 21, 2011

What is MPLS-TP (Transport Profile)

I have been hearing about MPLS-TP since long but now the time has come to implement MPLS-TP to the access network. The question arises why only in the access network not in the core? The reason for this is that most of the service providers has already built up the MPLS core and not it's time to move towards the access network with MPLS capabilities.
But what does fascinate service providers to adopt MPLS-TP? Legacy SDH network is used to built as transport network. Being costly solution, all the service providers are looking an alternate solution; must be same as of SDH but have the capacity of Ethernet.
MPLS-TP (Transport Profile) is set of protocols which doesn't use any control plane and is defined under IETF. But G-MPLS could be used for the dynamic allocation of labels. MPLS-TP doesn't offer Penultimate Hop Popping and ECMP.

Click Here To Read Rest Of The Post...

Tuesday, November 8, 2011

BGP update caused several Juniper Networks routers to crash

A Border Gateway Protocol update caused several Juniper Networks routers to crash, causing service disruptions for tier 1 network provider Level3 Communications.

Check eweek

Network world Article

Click Here To Read Rest Of The Post...