These tasks are performed at the major interface over which you want to run MPLS. Creating or accessing an interface places the CLI in Interface Configuration mode. You can then configure MPLS options on that interface. The following sequence is arbitrary; you can perform these tasks in any order.
![]() |
Note: Loop detection is always enabled in the JUNOSe MPLS implementation. |
Your choice of label distribution protocol determines whether the LDP or RSVP-TE interface configuration tasks are appropriate for your network design.
MPLS interface configuration tasks include the following sets of tasks:
To configure MPLS on the interface:
- host1(config-if)#mpls
or
- host1(config-if)#no mpls disable
- host1(config-if)#mpls atm vpi range 10 200
- host1(config-if)#mpls atm vci range 33 4000
Only ATM AAL5 interfaces support the interface label space. For MPLS interfaces using the interface label space, you must configure the both the VPI and VCI range. If you do not, the interface will remain operationally down.
- host1(config-if)#mpls signaling-interface
atm 4/0.5
To configure LDP on the interface:
- host1(config-if)#mpls ldp link-hello disable
To configure RSVP-TE on the interface:
- host1(config-if)#mpls rsvp
- host1(config-if)#mpls rsvp profile rsvp4
To disable RSVP-TE on the interface:
- host1(config-if)#mpls rsvp disable
- host1(config-if)#bandwidth 262144
- host1(config-if)#mpls bandwidth 4096
- host1(config-if)#mpls traffic-eng flood thresholds
up 15
- host1(config-if)#mpls traffic-eng flood thresholds
down 15
- host1(config-if)#mpls traffic-eng attribute-flags
0x000001f9
- host1(config-if)#mpls traffic-eng administrative-weight
25