3com 3031 Instruccion De Instalación

Perform the following configuration in MPLS view.

You can manually set an LSR to be a node along an LSP, and place a limit on the 
traffic over the LSP. Depending on the position in an MPLS domain, LSR can be 
ingress, transit node, or an egress. Note that the correct operation of this LSP can 
be ensured only after the LSRs along the specified LSP have been properly 
configured.

The 

 command is used to delete a specified LSP established 

manually.

Perform the following configuration in MPLS view.

Perform the following configuration in MPLS view.

The interval defaults to 0, that is, the statistics is not reported.

Table 765   Configuring a topology-driven LSP setup policy

Configure a topology-driven LSP setup 
policy

lsp-trigger { any | acl acl-number }

Disable the filtering condition specified 
by the arguments and no routes of any 
type can trigger the LSP setup

acl-number }

Table 766   Setting the local LSR to be a node on a specified LSP

Set the current LSR to be the 
ingress of a specified LSP

static-lsp ingress lsp-name destination 

dest-addr addr-mask { { nexthop 

next-hop-addr } | { outgoing-interface 

interface-type interface-num } } } 

out-label out-label-value [ preference 

preference-value ] [ metric metric-value ]

Set the current LSR to be a transit 
node along the specified LSP

static-lsp transit lsp-name 

interface-num } in-label in-label-value { 

{ nexthop next-hop-addr } | { 

outgoing-interface { interface-name | { 

interface-type interface-num } } } } 

Set the current LSR to be the 
egress of the specified LSP

static-lsp egress lsp-name 

incoming-interface interface-type 

interface-num in-label in-label-value

Table 767   Configuring an interval for reporting statistics

Configure an interval for reporting statistics

Restore the default interval