1641Description Use the static-cr-lsp ingress command to configure a static CR-LSP at theingress node.Use the undo static-cr-lsp ingress command to remove the static CR-LSP.n The next hop address cannot be a local public address when configuring the staticCR-LSP on the ingress or a transit node.Example # Configure a static CR-LSP on the ingress node, setting its name to Tunnel3,destination IP address to 202.25.38.1, destination address mask length to 24, nexthop IP address to 202.55.25.33, outgoing label to 237, and required bandwidthto 20 kbps. system-view[Sysname] static-cr-lsp ingress Tunnel3 destination 202.25.38.1 nexthop 202.55.25.33 out-label 237 bandwidth 20static-cr-lsp transitSyntax static-cr-lsp transit tunnel-name incoming-interface interface-type interface-numberin-label in-label-value { nexthop next-hop-addr | outgoing-interface interface-typeinterface-number } out-label out-label-value [ bandwidth [ bc0 | bc1 ]bandwidth-value ]undo static-cr-lsp transit tunnel-nameView System viewParameter Tunnel-name: Tunnel name comprising 1 to 15 characters.next-hop-addr: Next hop address.outgoing-interface interface-type interface-number: Specifies an outgoinginterface for the static CR-LSP.in-label-value: Incoming label, in the range 16 to 1023.out-label-value: Outgoing label, in the range 16 to 1023.bc0: Obtains bandwidth from a subpool.bc1: Obtains bandwidth from the global pool.bandwidth-value: Bandwidth assigned to the CR-LSP, in the range 1 to 32000000kbps.Description Use the static-cr-lsp transit command to configure a static CR-LSP on a transitnode.Use the undo static-cr-lsp transit command to remove the static CR-LSP.
