"Translation" Configuration rsvp-signaled LSP

Source Address:

Https://www.juniper.net/techpubs/software/junos-security/junos-security10.2/junos-security-swconfig-mpls/topic-47253.html

Body:

This example shows us how to create an LSP in an IP network between routers using RSVP as the signaling protocol. (Translator Press: The so-called signaling protocol that I understand is used to distribute the label to determine which LSR is in which port to use which label's protocol. such as Cisco's Ldp,juniper are commonly used for RSVP. )

Required Conditions:

Before you begin this experiment, delete the security services on your device. Specific reference https://www.juniper.net/techpubs/software/junos-security/junos-security10.2/junos-security-swconfig-mpls/ Topic-47168.html

Overview and Topology:

Typical rsvp-signaled LSP

In an MPLS network, if you want to establish an LSP between routers, you must manually activate the MPLS family yourself, configure RSVP on each transit interface (This example shows how to activate MPLS and configure RSVP on the ge-0/0/0 port). In addition, you must activate MPLS on all the interfaces in this network (the translator presses: that is, either the transit interface activates MPLS).

This case shows how to: on the ingress router (R1), use R7 's loopback port address (10.0.9.7) to define an LSP from R1 to R7. 10Mbps bandwidth is reserved for MPLS in the following configuration. Additionally, this configuration disables the CSPF algorithm to ensure that the rsvp-signaled LSP used by the host C1 and C2 is consistent with the shortest path to the IGP network.

Configuration

CLI Quick Configuration

To quickly configure RSVP, copy the following command into the CLI

[Edit]set interfaces ge-0/0/00  family mplsset Protocols RSVP Interface GE-0/0/0.0set Protocols MPLS label10.0. 9.7 set Protocols MPLS label-switched-path r1-R7 Bandwidth 10mset Protocols MPLS label-switched-path R1-R7 no-cspfset Protocols MPLS interface all

Decomposition steps

The following example requires you to navigate to a different configuration level and then configure it. See https://www.juniper.net/topics/reference/general/cli-editor-configuration-mode-quick-reference-using.html for the CLI hierarchy

To configure RSVP:

1. Activate the MPLS family on all transit interfaces

[Email protected]# Set interfaces ge-0/0/0 Unit 0 family MPLS

2. Activate RSVP on each transit interface

User @host # set Protocols RSVP interface ge-0/0/0

3. Activate the MPLS process for all interfaces. (Translator: This is actually the configuration under Protocol MPLS, and the first step in the unit 0 family MPLS to make a distinction, the first step is to do configuration under interface, this step is configured under Protocol)

[Email protected]# set Protocols MPLS interface all

4. Defining the LSP on the ingress router

[Email protected]# set Label-switched-path r1-r7 to 10.0.9.7

5. Leave 10Mbps bandwidth to the LSP

User @host # set Label-switched-path r1-r7 bandwidth 10m

6. Disabling the CSPF algorithm

[Email protected]# set Label-switched-path r1-r7 NO-CSPF

Results

Verify that your configuration is correct by using the show command in configuration mode. If the output is not the configuration you want, go through the configuration guide in this example again to correct it (Editor's note: Juniper's documentation is really a lot of crap ... ）。

For brevity, the output of the show command below contains only the configuration associated with this example, regardless of the ... Omitted.

[email protected]# show...interfaces {GE-0/0/0  {family MPLS;}}} ... protocols {RSVP {interface ge-0/0/0.0;} MPLS {label-switched-path r1-10.0. 9.7 ; bandwidth 10m;no-CSPF;} interface All;}} ...

Remember to commit when you're done configuring.

Verify

Objective:

Verify that each device establishes a corresponding RSVP neighbor. For example, in a topology diagram, router R1 lists the two RSVP neighbors of R2 R3.

Command:

In the CLI, enter the show RSVP neighbor command.

Output:

[Email protected]>Show RSVP NEIGHBORRSVP neighbor:2learnedaddress Idle up/dn Lastchange Helloint hellotx/Rx10.0.6.2              0  3/2        -: on        3   366/349 10.0.3.3              0  1/0        A: the        3   448/448 

Significance:

The IP address of the neighbor router can be seen in the output. Please verify that the loopback address of each router that established the RSVP neighbor is listed in the results.

Verifying RSVP Sessions

Objective:

Verify that the RSVP session was successfully established between the RSVP neighbors, and verify that the bandwidth reserved value is the same as the setting.

Command:

In the CLI, enter the show RSVP session detail command.

Output:

[Email protected]>Show RSVP session detailingress RSVP:1Sessions10.0.9.7From :10.0.6.1, Lspstate:up, ActiveRoute:0lspname:r1–r7, Lsppath:primary bidirectional, Upstream labelinch: –, Upstream label out:-suggested label received:-, suggested label Sent:–recovery label received:-, Recovery label sent:100000RESV Style:1FF, Labelinch:-, Label out:100000Time left :-, Since:thu Jan -  -: $: $ 2002tspec:rate 10Mbps size 10Mbps peak infbps m -M thePort Number:sender3Receiver -Protocol0path rcvfrom:localclient path Sentto:10.0.4.13(ge-0/0/1.0)1467pkts RESV rcvfrom:10.0.4.13(ge-0/0/1.0)1467pkts Record Route:<self>10.0.4.13  10.0.2.1  10.0.8.10  

Significance:

The details of the output include the session ID, as well as the bandwidth reservation for each session, and the next hop address. Please verify the following information:

• Each RSVP neighbor address is listed in the form of an loopback address.
• The status of each RSVP session is up
• For Tspec (translator presses: TSPEC namely traffic specification), the corresponding bandwidth value is 10Mbps as shown above.

Verifying that the rsvp-signaled LSP does play a role

Objective:

Verify that the routing table on the ingress router already exists with the loopback address of the other routers that you configured. For example, the Inet.3 routing table for R1 in the verification diagram has an LSP that you ration to R7.

Command:

In the CLI, enter the show route table Inet.3 command.

Output:

[Email protected]> Show route table inet.3inet.3:2Destinations,2Routes (2Active0Holddown,0hidden)+ = Active Route,-= last active, * =Both10.0.9.7/ +*[rsvp/7]xx: to: in, metricTen> To10.0.4.17Via ge-0/0/0.0, Label-switched-path R1–R7

Significance:

From the output you can see that the RSVP route exists in the Inet.3 routing table. In the MPLS network, verify that the loopback port of the rsvp-signaled LSP and egress (egress) router R7 is associated.

"Translation" Configuration rsvp-signaled LSP