[Contents] [Prev] [Next] [Index] [Report an Error]

Create an LSP

The second step in configuring signaled LSPs is to create one or more LSPs and define the properties associated with the label-switched path on the ingress router. To configure an LSP, include the label-switched-path statement at the [edit protocols mpls] hierarchy level: 

[edit protocols mpls]

label-switched-path lsp-path-name { 

    to address ;

    from address ; 

    adaptive;

    admin-group { 

        exclude group-names ;

        include group-names ;

    }

    auto-bandwidth {

        adjust-interval seconds;

        adjust-threshold percent;

        maximum-bandwidth bps;

        minimum-bandwidth bps;

        monitor-bandwidth;

    }

    bandwidth bps;

    class-of-service cos-value ; 

    description;

    disable;

    fast-reroute {    

        fast-reroute bps;

        exclude group-names;

        hop-limit number;

        include group-names;

    }

    hop-limit number ; 

    install {

        destination-prefix/prefix-length <active>;

    }

    ldp-tunneling;

    lsp-attributes {

        gpid gpid;

        signal-type signal-type;

        switching-type switching-type;       

    }

    metric number;

    no-cspf; 

    no-decrement-ttl; 

    optimize-timer seconds ; 

    preference preference ;

    priority setup-priority hold-priority ; 

    (random | least-fill | most-fill);

    (record | no-record); 

    retry-limit number ;

    retry-timer seconds ;

    standby;

    traceoptions { 

        file filename <replace> <size size > <files number  > <no-stamp> 

            <(world-readable | no-world-readable)>;

        flag flag <flag-modifier  > <disable>;

    }

    primary path-name { 

        adaptive; 

        admin-group { 

            exclude group-names ;

            include group-names ;

        }

        bandwidth bps ;

        class-of-service cos-value ; 

        hop-limit number ; 

        no-cspf; 

        no-decrement-ttl; 

        optimize-timer seconds ;

        preference preference ;

        priority setup-priority hold-priority ;

        (record | no-record); 

        retry-limit number ;

        retry-timer seconds ;

        standby; 

    }

    secondary path-name { 

        adaptive; 

        admin-group { 

            exclude group-names ;

            include group-names ;

        }

        bandwidth bps ;

        class-of-service cos-value ; 

        hop-limit number ; 

        no-cspf; 

        no-decrement-ttl; 

        optimize-timer seconds ;

        preference preference ;

        priority setup-priority hold-priority ;

        (record | no-record); 

        retry-limit number ;

        retry-timer seconds ;

        standby; 

    }

}

Each LSP must have a name, lsp-path-name, which can be up to 32 characters long and can contain letters, digits, periods (.), and hyphens (-). The name must be unique within the ingress router. For ease of management and identification, configure unique names across the entire domain.

When you configure LSPs, you can specify the following statements either for each LSP or for each path. (You configure LSPs at the [edit protocols mpls label-switched-path lsp-path-name ] hierarchy level, and you configure paths at the [edit protocols mpls label-switched-path lsp-path-name primary] or [edit protocols mpls label-switched-path lsp-path-name secondary] hierarchy level.) For statements that you configure on a per-LSP basis, the value applies to all paths in the LSP. For statements that you configure on a per-path basis, the path value overrides the per-LSP value.

For maintenance purposes, you can also configure the following attributes across all LSPs and any paths within those LSPs. (You can configure all the LSPs and paths at once at the [edit protocols mpls ] hierarchy level.)

For each LSP, you can configure the following properties:

For each LSP and for each primary and secondary path, you can configure the following properties:

[Contents] [Prev] [Next] [Index] [Report an Error]