This section shows how to build a minimal configuration for MPLS. For MPLS to be activated, it is necessary to add the MPLS protocol family to the interfaces that will bear MPLS traffic. MPLS must also be configured under the [edit protocols] level of hierarchy as shown below. [edit interfaces] lab@Chicago# set fe-0/0/0 unit 0 family mpls [edit interfaces] lab@Chicago# set fe-0/0/1 unit 0 family mpls [edit interfaces] lab@Chicago# show fe-0/0/0 { unit 0 { family inet { address 10.0.24.2/24; } family mpls; } } fe-0/0/1 { unit 0 { family inet { address 10.0.31.1/24; } family mpls; } } } [edit interfaces] lab@Chicago# top [edit] lab@Chicago# edit protocols [edit protocols] lab@Chicago# set mpls interface all [edit protocols] lab@Chicago# show mpls { interface all } [edit protocols] lab@Chicago# commit The example below shows the routing table MPLS information. There are two labels, 0 and 1, created automatically by JUNOS. These are actual MPLS routes in the table. Label 0 is the IPv4 explicit NULL , and 1 is the router alert label (refer back to Section 12.3.1.1 for more information). [edit] lab@Chicago# show route table mpls.0 mpls.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0 *[MPLS/0] 00:09:26, metric 1 Receive 1 *[MPLS/0] 00:09:26, metric 1 Receive This configuration sample showed the minimum number of steps required to enable MPLS on an interface to permit the FPC that the interface resides on to understand MPLS traffic. This sample also showed the steps used to launch the MPLS protocol on the routing engine. Lastly, this configuration sample showed the two labels that are automatically created by JUNOS when the MPLS protocol is launched. |