lrb wrote: » Let's say a router running MPLS (an LSR) has the prefix 100.100.100.0/24 in it's RIB, a label will be created for this prefix, say label 500. If this LSR is an LDP neighbour with three LSRs out three different interfaces, the local LSR will send the label binding (100.100.100.0/24, 500) to all three neighbours. Now that all three remote LSRs have the label binding from our local LSR, when one of them sends a labelled packet to our local router with label 500, our local LSR will receive the labelled packet and does one of two things depending on whether per-platform or per-interface label space is being used. If the router considers label 500 to have global significance over the router (i.e. the "platform"), it only bases it's forwarding decision based on the incoming label. This is the default for non-ATM interfaces and is what you will mostly see out there. From a certification POV, I don't think Cisco tests on LC-ATM anymore so per-platform label spaces is definately what you will see on the exams. If the router considers label 500 to have significance based on which interface it arrived on, it bases it's forwarding decision based on both the incoming interface and the incoming label. Therefore if one remote router sends a lableled packet using label 500 to our local router on one interface, this can be part of a different FEC than if the labelled packet had arrived on a different interface, even though they had the same label. Make sense now?
