Intermediate and egress routers perform similar functions—they modify the label that has been applied to a packet. An intermediate router can change the label. An egress router removes the label (if the packet still contains a label) and continues forwarding the packet to its destination.
To configure static LSPs on intermediate and egress routers, include the interface statement:
-
interface (interface-name | all) {
-
disable;
-
admin-group [ group-names ];
-
-
label-map in-label {
-
class-of-service cos-value;
-
next-hop (address | interface-name | address/interface-name) | (discard | reject);
- (pop | swap <out-label>);
-
preference preference;
-
swap-push swap-label push-label;
- }
- }
You can include these statements at the following hierarchy levels:
For the label-map statement configuration, the next-hop | (reject | discard) and pop | swap statements are required. The remaining statements are optional.
Each statement within the interface statement consists of the following parts:
Operation to perform on the labeled packet:
Label properties to apply to the packet (all are optional):
You can specify any number of label-map statements at the [edit protocols mpls interface interface-name] hierarchy level.
The static routes are installed in the default MPLS routing table, mpls.0, and the creating protocol is identified as static. To verify that a static route is properly installed, use the command show route table mpls.0 protocol static. The following is an example of the output:
1000123 *[Static/5] 00:00:38 > to 12.2.2.2 via so-5/0/0.0, swap 1000456