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

Creating 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:

label-switched-path lsp-path-name {

    disable;

    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 text;

    fast-reroute {

        bandwidth bps;

        (exclude group-names | no-exclude);

        hop-limit number;

        (include group-names | no-include);

    }

    from address; 

    hop-limit number; 

    install {

        destination-prefix/prefix-length <active>;

    }

    ldp-tunneling;

    link-protection;

    lsp-attributes {

         gpid (ethernet | hdlc | ipv4 | ppp);

        signal-bandwidth type;

         switching-type type;

    }

    metric number;

    no-cspf; 

    no-decrement-ttl; 

    node-link-protection;

    optimize-timer seconds;

    p2mp path-name;

    policing filter-name;

    preference preference;

    priority setup-priority hold-priority;

    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; 

    }

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

    (record | no-record); 

    retry-limit number;

    retry-timer seconds;

    secondary path-name { 

        adaptive; 

        admin-group { 

            exclude group-names;

            include group-names;

        }

        bandwidth bps;

        class-of-service 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; 

    }

    soft-preemption {

        cleanup-timer seconds;

    }

    standby; 

    to address;

    traceoptions {

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

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

        flag flag <flag-modifier> <disable>; 

    }

}

You can include this statement at the following hierarchy levels:

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. 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:

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]