--> LDP periodically sends hello messages (every 5 seconds).

If the label switch router (LSR) is adjacent or one hop from its neighbor, the LSR sends out LDP li nk hello messages to all the routers on the subnet as User Datagram Protocol (UDP) packets with a multicast destinatio n address of 224.0.0.2 ( all routers on a subnet ) and destination port number of 64 6 (TDP uses destination port 711) . After discovering any LDP neighbor using multicast UDP hello messages, a T CP session must be established for LDP to exchange labels over a reliable connec tion. If the TCP session cannot be established between two routers (for example there is an access-list that denies TCP s essions on the well-known port number 711 TDP), they cannot become neighbors. An d you will see an empty output when using the show mpls ldp neighbor command. LDP periodically sends Hello messages. If the Label switch router is adjecent or one hop from its neighbor, the LSR sends out the LDP link hello messages to all the routers on the subnet as UDP packet with the multicast destination address 224.0.0.2 and destination port number 646 (TDP uses the destination port 711). After discovering any LDP neighbor using multic ast UDP hello message, a TCP session must be established for LDP to exvhange labels over a reliable connection. If the TCP session cannot be established between two routers (whether in case of TDP or LD P) they cannot become neighbors. The empty output us shown when by show mpls ldp neighbors --> In the more conclusive way the neighbors are not formed unle ss the TDP session is not established between the neighbors after the Hello mess age and secondly both LDP and TDP neighbors can be viewed by using the simple "show mpls ldp neighbors" command When running MPLS VPN, there is feature called penultimate hop popping (PHP). Th e penultimate hop is not the last LSR to process the labeled packet.It is the se cond last LSR to process the labeled packet. With this feature, the egress LSR doesnt have to perform 2 lookups. ***** VRF Basics ***** Virtual routing and forwarding is used by SP to provide the services within MPLS cloud with multiple customers. VRF allows the creation of multiple routing tabl es within a single router. This means that overlapping use of IP addresses from different customer is possible. This is due to the fact that may be each in terface is assigned to the routing tables. Routing is done on the basis of the i nterfaces ***** Actual Tests MPLS ***** -->If aggregation (summerization) were to be used on a network with ATM LSRs the LSPs would be broken in two. --> In MPLS TE every LSR needs additional information about links in the network , avlaible resources and constraints --> The major draw back of using tradiotional IP routing over an ATM network whe n connecting multiple site is ATM virtual circutis are needed to be established between the different sites -->In order to be implemented on ATM Switches, the requirements must the ATM swi tch meet is become Layer 3 aware by running a routing protocol and use MPLS LDP or TDP to distribute and receive MPLS label information --> When running basic MPLS in conjunction with VPNs, each packet contains atlea st two labels one label is used for identifying LSP and other label is used for identifying the VPN --> On ingress, a label is imposed to a packet the process responsible for this

is generically a control plane process which is either TDP or LDP process --> MPLS packets are label switch packets so the label is imposed on layer2 ther efore the problem can only be detected by user application and secondly MPLS pac kets are label switched, packets are automtically fragmented and reassembled by the PE routers therefore th ere is no potential MTU issues --> In MPLS VPN the first label in the label stack is hte LDP label used to reac h the egress PE router and the second label in the label stack is the VPN label assigned by teh egress PE router --> MPLS supports the following applications --> Unicast IP Routing --> Multicast IP Routing --> MPLS TE --> QoS --> MPLS VPNs --> AToM --> Two methods to achieve differentiated QoS in MPLS is by using the experiment al bits to identify the different classes and by using the DiffServ Codepoints t o identify the different classes --> Question 22 --> In Cell mode MPLS the label is imposed in VPI/VCI fields --> While configuring MPLS over an ATM virtual path on a cell-mode-router follwi ng things are needed to be done --> An LC-ATM interface must be created --> The ATM VPI value must be set to the virtual path number --> The virtual path number has to match between the peers --> Label Allocation and Distribution in a frame mode MPLS network is accomplish ed by the following actions -->Local tables are generated for the LIB and LFIB --> Routing information is exchanged using IP routing protocols --> Routing information is exchanged using IP routing protocols --> IP routing protocols build IP routing tables --> Next hop labels are inserted into the LIB, FIB and LFIB tables --> LSRs announces their assigned labels to all other LSRs --> MPLS label allocation method whcih is least secure is per-platform label spa ce --> Conditional Label distribution is used to save memory space by not advertisi ng a label for MPLS WAN links --> Multiple sessions can be established between a pair of LSRs if they use mult iple label spaces --> Per platform label space is identified by the label space ID of 0 in the LDP identifier field --> In TDP and LDP neighbors are discovered automatically --> Proper syntax for enabling MPLS on an interface and by using TDP is given be low --> mpls ip --> tag-switching ip --> When running MPLS in the frame mode over an Ethernet, teh recieving device i dentify that the frame contains MPLS information by the Ether type of PID in the layer 2 header whcih identifies that the frame as an MPLS frame ***** VPN Questions ***** --> Since route distinguisher RD cannot identify participation in more than one VPN, to support complex MPLS VPNs route targets are introduced --> CE routers are not aware of MPLS VPN --> In MPLS VPNs the PE routers are aware of the customer routes --> In tradional peer-to-peer VPN implementations the PE routers are aware of cu stomer routes --> Two IP based overlay VPN technologies are --> Frame Relay

--> Generic route Encapsulation (GRE) --> Layer 2 overlay VPN implementation is achieved with the technology such as f rame relay and ATM --> In overlay VPN service provider doesnt participate in customer routing --> Layer 3 overlay VPN use emulated point to point link --> MPLS and traditional peer to peer VPNs require th service provider to partic ipate in customer routing --> Intranet VPN : Connects sites within an organization --> Managed Network : A dedicated VPN is established by service provider to mana ge customer edge routers in which every site can communicate with every other si te --> Overlapping VPN : Some sites can communicate in more than one VPN --> In MPLS implementaiton in whcih selected sites from one VPN can communicate with the selected sites in second VPN is known as overlapping VPN --> A PE has a global routing table and additional routing table for each VRF --> A tunneling technology that provides the network layer authentication and op tional encryption to make data transfer over the internet securely is IPSec --> In MPLS VPN each customer is assigned an independent routing table (Virtual Routing and Forwarding Table) --> In MPLS VPN implementations the second VPN labels in the label stack propaga ted from the egress PE router to the ingress PE router through MP IBGP VPNv4 rou ting updates --> Two VRF route limiting options supported by IOS are --> The neighbor maximum-prefix command limits the number of rotues that an individual BGP peer can send --> The maximum routes command limits the total number of routes ina VRF , regardless of whether they are recieved from CE routers or from other PE route r via MP-IBGP -->