Академический Документы
Профессиональный Документы
Культура Документы
Contents
Contents
About This Course........................................................................................................................ 1 Test Instructions....................................................................................................................... 1 Version Introduction................................................................................................................. 1 Test Objectives........................................................................................................................ 1 Test Tasks............................................................................................................................... 1 Relevant Materials................................................................................................................... 1 Chapter 1 Configuration Guide to CCC Local Connection.......................................................2 1.1 Networking and Service Description.................................................................................2 1.2 Command Line List........................................................................................................... 2 1.3 Configuration Flow............................................................................................................ 3 1.4 Configuration Procedure................................................................................................... 3 1.5 Result Verification............................................................................................................. 4 1.6 FAQ................................................................................................................................... 4 1.7 Configuration Reference................................................................................................... 4 1.7.1 Configure the Port.................................................................................................. 4 1.7.2 Service configuration............................................................................................. 5 Chapter 2 Configuration Guide to CCC Remote Connection....................................................6 2.1 Networking and Service Description.................................................................................6 2.2 Command Line List........................................................................................................... 6 2.3 Configuration Flow............................................................................................................ 7 2.4 Configuration Procedure................................................................................................... 8 2.5 Result Verification............................................................................................................. 9 2.6 FAQ................................................................................................................................... 9 2.7 Configuration Reference................................................................................................. 10 2.7.1 Configure the Port................................................................................................ 10 2.7.2 Service configuration...........................................................................................10 Chapter 3 Martini Configuration Guide.....................................................................................12 3.1 Networking and Service Description...............................................................................12 3.2 Command Line List......................................................................................................... 12 3.3 Configuration Flow.......................................................................................................... 13 3.4 Configuration Procedure................................................................................................. 13 3.5 Result Verification........................................................................................................... 14 3.6 FAQ................................................................................................................................. 15 3.7 Additional Task................................................................................................................ 15 3.8 Configuration Reference................................................................................................. 15 3.8.1 Configure the Port................................................................................................ 15 3.8.2 Service configuration...........................................................................................16 Chapter 4 Kompella Configuration Guide................................................................................18 4.1 Networking and Service Description...............................................................................18 4.2 Command Line List......................................................................................................... 18 4.3 Configuration Flow.......................................................................................................... 19 4.4 Configuration Procedure................................................................................................. 20 4.5 Result Verification........................................................................................................... 21 4.6 FAQ................................................................................................................................. 22 4.7 Configuration Reference................................................................................................. 22 4.7.1 Configure the Port................................................................................................ 22 4.7.2 Service configuration...........................................................................................23
Version Introduction
This Guide is applicable to VRP versions 3.30 and 5.10.
Test Objectives
To understand the basic principles of MPLS L2 VPN To grasp the configuration process for MPLS L2 VPN. To get familiar with the configuration commands for MPLS L2 VPN
Test Tasks
Configure the local VPN for CCC Configure the remote VPN for CCC Configure the VLAN-based Martini Configure the Ethernet-based Kompella
Relevant Materials
Figure 1.1
RTA, RTC and RTD are connected among them through Serial interfaces, and PPP is encapsulated at the link layer. A CCC local connection is established between RTC and RTD. It unnecessary to configure IP addresses for RTAs interfaces connected to RTC and RTD.
Operation Configure LSR ID Enable MPLS and enter the MPLS view Enable MPLS L2VPN
2
Version VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 mpls lsr-id X.X.X.X mpls lsr-id X.X.X.X mpls mpls mpls l2vpn
Command
Operation
Command mpls l2vpn ccc ccc-connection-name interface inteface-number out-interface inteface-number ccc ccc-connection-name interface inteface-number out-interface inteface-number interface-type interface-type interface-type interface-type
From the system view, run the MPLS. 3) Run the MPLS L2VPN
From the system view, run the MPLS L2VPN. 4) Create a CCC local connection
Create a CCC local connection, whose interfaces are the ports connected to RTC and RTD respectively.
name: CEA-CEB, type: local, state: up, intf1: Serial2/0 (up), intf2: Serial3/0:0 (up)
Note: Local connection is a connection established between two local CEs. Switching can be completed directly on the PE, and no static LSP needs to be configured. 2) Detect the connectivity between RTC and RTD through the Ping command.
press CTRL_C to break Sequence=1 ttl=255 time=31 Sequence=2 ttl=255 time=29 Sequence=3 ttl=255 time=29 Sequence=4 ttl=255 time=30 Sequence=5 ttl=255 time=30 ms ms ms ms ms
[RTD] ping 172.1.1.2 PING 172.1.1.2: 56 data bytes, Reply from 172.1.1.2: bytes=56 Reply from 172.1.1.2: bytes=56 Reply from 172.1.1.2: bytes=56 Reply from 172.1.1.2: bytes=56 Reply from 172.1.1.2: bytes=56 --172.10.10.2 ping statistics-5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 29/29/3 ms
1.6 FAQ
Q: Whats the full name of CCC? Can a CCC connection bear multi-service? Why? A: CCC is abbreviated from Circuit Cross Connect, and MPLS L2VPN is implemented through static configuration. Unlike the MPLS L2VPN which uses two layers of label, CCC uses one layer of label to transmit user data. Therefore, CCC uses the LSP exclusively.
<RTA>system-view [RTA]int loopback 0 [RTA-LoopBack0]ip address 1.1.1.1 255.255.255.255 [RTA]int serial 3/0 [RTA-Serial 3/0]undo shutdown [RTA]int serial 2/0 [RTA-Serial2/0]undo shutdwon
2.
4
Configure RTC
<RTC>system-view
3.
Configure RTD
<RTD> system-view [RTD] interface serial 2/0 [RTD-Serial2/0] ip add 172.1.1.1 255.255.255.252
[RTA] mpls lsr-id 1.1.1.1 [RTA] mpls [RTA] mpls l2vpn [RTA] ccc RTC-RTD interface Serial2/0 out-interface Serial3/0
Figure 1.1
RTB and RTC are connected through Serial interfaces, and PPP is encapsulated at the link layer. RTA and RTB are connected through Ethernet interfaces, and so are RTC and RTD. RTA and RTD have a CCC remote connection established between them. RTBs interface connected to RTA does not need to have an IP address configured.
Operation Configure LSR ID Enable MPLS and enter the MPLS view Enable MPLS L2VPN
6
Version VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 mpls lsr-id X.X.X.X mpls lsr-id X.X.X.X mpls mpls mpls l2vpn mpls l2vpn
Command
Operation Set the LSR to be an ingress node for the specified LSP
Command static-lsp ingress lsp-name l2vpn { nexthop nexthop-addr | outgoing-interface interface-type interface-num } out-label out-label static-lsp transit lsp-name l2vpn incominginterface interface-type interface-num in-label inlabel { nexthop next-hop-addr | outgoing-interface interface-type interface-num } out-label out-label static-lsp transit lsp-name incoming-interface interface-type interface-number in-label in-label { nexthop next-hop-addr | outgoing-interface interface-type interface-number } out-label out-label static-lsp egress lsp-name l2vpn incominginterface interface-type interface-num in-label inlabel ccc ccc-connection-name interface interface-type interface-num transmit-lsp transmit-lsp-name receive-lsp receive-lsp-name ccc ccc-connection-name interface interface-type inteface-number in-label in-label-value out-label outlabel-value { nexthop ip-address | out-interface interface-type inteface-number }
Set the LSR to be an intermediate node for the specified LSP VRP 5.10
In VRP5.10, each CCC remote connection does not need to have two static LSPs, but only need to have an inbound label and an outbound label configured. The inbound label is used exclusively by the CCC connection. This has the same effect as a configured static LSP. Note: If the egress interface is an Ethernet interface, you must specify the next-hop IP address.
Specify an LSR ID
Create a staticLSP
Run the MPLS from the system view and run the MPLS at the corresponding port. 3) Create a static LSP
Create two static LSPs from the MPLS view. Each LSP is responsible for unidirectional data transmission. To be specific, one LSP transmits data from RTB to RTD, and the other LSP transmits data from RTD to RTB. 4) Run the MPLS L2VPN
From the system view, run the MPLS L2VPN. 5) Create a CCC remote connection
Create a CCC local connection, whose interfaces are the ports connected to RTC and RTD respectively.
name: RTC-RTD, type: remote, state: up, intf: Ethernet0/0 (up), tran-lsp: RTA-RTB (up), rcv-lsp: RTB-RTA (up)) [RTC]display ccc total connections : 1 local connections : 0, remote connections : 1,
0 up 1 up
name: RTC-RTD, type: remote, state: up, intf: Ethernet0/0 (up), tran-lsp: RTB-RTA (up), rcv-lsp: RTA-RTB (up)
Note: If you view the CCC connection information on RTB and RTC, you will see an established CCC remote connection in UP status. 2) On the other hand, you may view the status information of the LSP and static LSP through the display mpls lsp and display mpls static-lsp commands.
[RTB] display mpls lsp ----------------------------------------------------------------------LSP Information: Static Lsp ----------------------------------------------------------------------TOTAL: 2 Record(s) Found. NO FEC 1 0.0.0.0/0 2 -------/-NEXTHOP 192.2.2.1 ------I/O-LABEL -----/100 200/----OUT-INTERFACE S2/0 -------
[RTC] display mpls lsp ----------------------------------------------------------------------LSP Information: Static Lsp ----------------------------------------------------------------------TOTAL: 2 Record(s) Found. NO FEC 1 0.0.0.0/0 2 -------/-NEXTHOP 192.2.2.2 ------I/O-LABEL -----/200 100/----OUT-INTERFACE S2/0 -------
2.6 FAQ
Q: Whats the full name of CCC? Can a CCC connection bear multi-service? Why? A: CCC is abbreviated from Circuit Cross Connect, and MPLS L2VPN is implemented through static configuration. Unlike the MPLS L2VPN which uses two layers of label,
Confidential Information of Huawei. No Spreading without Permission 9
CCC uses one layer of label to transmit user data. Therefore, CCC uses the LSP exclusively.
<RTA> system-view [RTA] interface ethernet 0/0 [RTA-Ethernet0/0] ip address 10.1.1.1 255.255.255.252
2.
Configure RTB
<RTB> system-view [RTB] interface loopback 0 [RTB-LoopBack0] ip address 2.2.2.2 255.255.255.255 [RTB] interface serial 2/0 [RTB-Serial2/0] ip address 192.2.2.2 255.255.255.252
3.
Configure RTC
<RTC> system-view [RTC] interface loopback 0 [RTC-LoopBack0] ip address 3.3.3.3 255.255.255.255 [RTC] int serial 2/0 [RTC-Serial2/0] ip address 192.2.2.1 255.255.255.252
4.
Configure RTD
<RTD> system-view [RTD] interface ethernet 0/0 [RTD-Ethernet0/0] ip address 10.1.1.2 255.255.255.252
2)
3)
Configure Static RP
[RTB-mpls] static-lsp ingress RTA-RTB l2vpn nexthop 192.2.2.1 out-label 100 [RTB-mpls] static-lsp egress RTB-RTA l2vpn incoming-interface Serial2/0 in-label 200
4)
5)
10
Note: In VRP 5.10, the following information will be displayed: [RTB] ccc RTC-RTD interface ethernet 0/0 in-label 200 out-label 100 next-hop 192.2.2.1 2. 1) Configure RTC Specify an LSR ID
2)
3)
Configure Static RP
[RTC-mpls] static-lsp ingress RTB-RTA l2vpn nexthop 192.2.2.2 out-label 200 [RTC-mpls] static-lsp egress RTA-RTB l2vpn incoming-interface Serial2/0 in-label 100
Note: This command is unavailable in VRP 5.10. 1) 2) Run the MPLS L2VPN Create a CCC remote connection
[RTC] mpls l2vpn [RTC] ccc RTC-RTD interface Ethernet0/0 transmit-lsp RTB-RTA receive-lsp RTA-RTB
Note: VRP 5.10: [RTC] ccc RTC-RTD interface ethernet 0/0 in-label 100 out-label 200 next-hop 192.2.2.2
11
Figure 1.1
RTA accesses RTB in the VLAN mode, and RTD accesses RTC in the VLAN mode. A Martini MPLS L2VPN is established between RTA and RTD.
Operation Configure LSR ID Enable MPLS and enter the MPLS view Enable the MPLS capability for an interface Enable LDP and enter LDP view Activate the LDP function for an interface Enable MPLS L2VPN
12
Version VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 mpls lsr-id X.X.X.X mpls lsr-id X.X.X.X mpls mpls mpls mpls mpls ldp mpls ldp mpls ldp enable mpls ldp enable mpls l2vpn mpls l2vpn
Command
Operation Enter the MPLS-LDP remote peer view Create a Martini MPLS L2VPN connection Configure address for the remote peer
Version VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10
Command mpls ldp remote-peer index mpls ldp remote-peer index mpls l2vc destination vc-id mpls l2vc destination vc-id remote-ip ip-address remote-ip ip-address
Run the MPLS from the system view and run the MPLS at the corresponding port.
Confidential Information of Huawei. No Spreading without Permission 13
3)
Run the MPLS LDP from the system view and activate the MPLS LDP at the corresponding port. 4)
Create an LDP remote session First, in the MPLS-LDP view, execute the remote-peer index command to enter the MPLS-LDP-Remote view. Then, in the MPLS-LDP-Remote view, execute the remote-ip ip-address command to specify a remote peer entity. Caution:
The precondition for establishing an LDP session is that a TCP connection must be established between the LSR-IDs of both parties. If both the routers take their Loopback addresses as LSR-IDs, each router needs the information of the route to the Loopback address of the other router. 5) Run the MPLS L2VPN
From the system view, run the MPLS L2VPN. 6) Create a Martini MPLS L2VPN connection
[RTB] display mpls l2vc Total l2vc : 1 l2vc : 1 up l2vc : 0 down Interface Ethernet0/0.10, Encapsulation: vlan, Service: VLL VC-ID Destination State Lcl-Label/Rmt-Label Tunnel/Index 100 3.3.3.3 up 1024/1024 LSP/0 [RTC] display mpls l2vc Total l2vc : 1 l2vc : 1 up l2vc : 0 down Interface Ethernet0/0.10, Encapsulation: vlan, Service: VLL VC-ID Destination State Lcl-Label/Rmt-Label Tunnel/Index 100 2.2.2.2 up 1024/1025 LSP/0
2)
From RTA, ping the interface address 10.1.1.2 of RTD. You can ping it successfully.
break time=57 time=35 time=35 time=35 time=34 ms ms ms ms ms
[RTA] ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to Reply from 10.1.1.2 : bytes=56 Sequence=1 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=2 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=3 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=4 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=5 ttl=255 --10.1.1.2 ping statistics-5 packet(s) transmitted 5 packet(s) received 0.00% packet loss
14
3.6 FAQ
Q: What are the main contents of a Virtual Circuit (VC) that is established between two CEs in the Martini mode? A: Martini uses VC-TYPE and VC-ID to identify a VC.
VC-TYPE: To indicate that the VC type is ATM, VLAN, PPP or others. VC-ID: VC-ID is unique in the whole PE for all VCs of the same VC-TYPE.
A PE that connects two CEs switches VC labels through LDP and binds CEs through VC-ID. When an LSP is successfully established to connect two PEs, a VC is established after the two PEs complete label switching and binding. In this case, CEs at both ends may transmit layer-2 data over this VC. In order to switch VC labels between PEs, the Martini draft expands the LDP by adding an FEC type: VC FEC. In addition, it is possible that two PEs that switch VC labels are not connected directly, so the LDP must establish a remote session using remote peer and transmit VC FEC and VC label over the session.
<RTA> system-view [RTA] interface ethernet 0/0.10 [RTA-Ethernet0/0.10] vlan-type dot1q vid 10 [RTA-Ethernet0/0.10] ip address 10.1.1.1 255.255.255.252
2.
Configure RTB
<RTB> system-view [RTB] interface loopback 0 [RTB-LoopBack0] ip address 2.2.2.2 255.255.255.255 [RTB] interface ethernet 0/0.10 [RTB-Ethernet0/0.10] vlan-type dot1q vid 10 [RTB] interface serial 2/0 [RTB-Serial2/0] ip address 192.2.2.2 255.255.255.252
3.
Configure RTC
<RTC> system-view [RTC] interface loopback 0 [RTC-LoopBack0] ip address 3.3.3.3 255.255.255.255 [RTC] interface ethernet 0/0.10 [RTC-Ethernet0/0.10] vlan-type dot1q vid 10 [RTC] interface serial 2/0 [RTC-Serial2/0] ip add 192.2.2.1 255.255.255.252
15
4.
Configure RTD
<RTD> system-view [RTD] interface ethernet 0/0.10 [RTD-Ethernet0/0.10] vlan-type dot1q vid 10 [RTD-Ethernet0/0.10] ip address 10.1.1.2 255.255.255.252
2)
[RTB] mpls
3)
[RTB-Serial2/0] mpls
4)
5)
6)
7)
8)
9)
Enable OSPF
[RTB] router id 2.2.2.2 [RTB] ospf [RTB-ospf-1] area 0 [RTB-ospf-1-area-0.0.0.0] network 192.2.2.0 0.0.0.3 [RTB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
2. 1)
2)
[RTC] mpls
3)
[RTC-Serial2/0] mpls
16
4)
5)
6)
7)
8)
9)
Enable OSPF
[RTC] router id 3.3.3.3 [RTC] ospf [RTC-ospf-1] area 0 [RTC-ospf-1-area-0.0.0.0] network 192.2.2.0 0.0.0.3 [RTC-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
17
Figure 1.1 RTA and RTB are connected through Ethernet interfaces, so are RTD and RTC. A Kompella MPLS L2VPN is established between RTA and RTD. RTBs interface for connecting RTA does not need to have an IP address configured. RTCs interface for connecting RTD does not need to have an IP address configured.
Operation Enable BGP and enter the BGP view Create a peer group Specify an AS number for the EBGP peer group Specify an AS number for the IBGP
18
Version VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30
Command bgp as-number bgp as-number group group-name [ internal | external ] group group-name [ internal | external ] peer group-name as-number as-number peer group-name as-number as-number peer group-name as-number
Operation peer group Enter MBGP vpn-instance address family view Enable the specified peer group Create a VPN instance and specify the encapsulation mode Configure RD for MPLS L2VPN Configure VPN-target for MPLS L2VPN Create a CE/modify the CE range Creating connection
Version VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10 VRP 3.30 VRP 5.10
Command peer group-name as-number l2vpn-family l2vpn-family peer group-name enable peer group-name enable mpls l2vpn vpn-name encapsulation { atm-aal5 | ethernet | fr | hdlc | ppp | vlan } mpls l2vpn vpn-name encapsulation { atm-aal5 | ethernet | fr | hdlc | ppp | vlan } route-distinguisher route-distinguisher route-distinguisher route-distinguisher vpn-target vpn-target-ext-community [ importextcommunity | export-extcommunity | both ] vpn-target vpn-target-ext-community [ importextcommunity | export-extcommunity | both ] ce name id id [ range range ] ce name id id [ range range ] connection interface-type interface-num [ ce-offset offset ] connection interface-type interface-num [ ce-offset offset ]
19
Specify an LSR ID
Configure RD and RT
Run the MPLS from the system view and run the MPLS at the corresponding port. 3) Run the MPLS LDP
Run the MPLS LDP from the system view and activate the MPLS LDP at the corresponding port. Caution: The precondition for establishing an LDP session is that a TCP connection must be established between the LSR-IDs of both parties. If both the routers take their Loopback addresses as LSR-IDs, each router needs the information of the route to the Loopback address of the other router. 4) Run the BGP routing protocol and establish the IBGP neighborhood
From the system view, run the BGP to enter the BGP view and establish the IBGP neighborhood. 5) Activate the IBGP neighbor under L2VPN-Family
Enter the L2VPN-Family address familiar from the BGP view and activate the IBGP neighbor. 6) Run the MPLS L2VPN
From the system view, run the MPLS L2VPN. 7) Create an L2VPN instance
From the system view, create an MPLS L2VPN instance. 8) Configure the RD and RT attributes
Configure the RD and RT attributes from the MPLS L2VPN instance view. 9) Create a Kompella MPLS L2VPN connection
Create a Kompella MPLS L2VPN connection from the MPLS L2VPN instance view. Caution: While modifying a CE range, you can only make the CE range larger, but not smaller. For example, you can change a CE range from 10 to 20, but cannot change it to 5. To make a CE range smaller, you can only first delete the CE and then re-create it.
[RTB] display mpls l2vpn connection total connections: 1, connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown VPN-Instance Name: vpna, total connections: 1, connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown CE Name RTA, id: 0, Rid type status peer-id route-distinguisher intf 1 rmt up 3.3.3.3 100:2 Ethernet0/0 [RTC] display mpls l2vpn connection
21
total connections: 1, connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown VPN-Instance Name: vpna, total connections: 1, connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown CE Name RTD, id: 1, Rid type status peer-id route-distinguisher intf 0 rmt up 2.2.2.2 100:1 Ethernet0/0
2)
From RTA, ping the interface address 10.1.1.2 of RTD. You can ping it successfully.
break time=57 time=35 time=35 time=35 time=34 ms ms ms ms ms
[RTA] ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to Reply from 10.1.1.2 : bytes=56 Sequence=1 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=2 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=3 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=4 ttl=255 Reply from 10.1.1.2 : bytes=56 Sequence=5 ttl=255 --10.1.1.2 ping statistics-5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 34/39/3 ms
4.6 FAQ
Q: Why is Kompella applied extensively in practice? A: Because the Kompella MPLS L2VPN also uses VPN Target to manage VPN routes. As a result, this networking mode is much flexible. Q: Why should you assign a reasonable CE-ID range in configuring Kompella. A: Because the CE range can only be made larger, but not smaller. To make a CE range smaller, you should first delete the CE and then re-create it.
<RTA> system-view [RTA] interface ethernet 0/0 [RTA-Ethernet0/0] ip address 10.1.1.1 255.255.255.252
2.
Configure RTB
<RTB> system-view [RTB] interface loopback 0 [RTB-LoopBack0] ip address 2.2.2.2 255.255.255.255 [RTB] interface serial 2/0 [RTB-Serial2/0] ip address 192.2.2.2 255.255.255.252
3.
Configure RTC
<RTC> system-view [RTC] interface loopback 0 [RTC-LoopBack0] ip address 3.3.3.3 255.255.255.255 [RTC] interface serial 2/0
22
4.
Configure RTD
<RTD> system-view [RTD] interface ethernet 0/0 [RTD-Ethernet0/0] ip address 10.1.1.2 255.255.255.252
[RTB] router id 2.2.2.2 [RTB] ospf [RTB-ospf-1] area 0 [RTB-ospf-1-area-0.0.0.0] network 192.2.2.0 0.0.0.3 [RTB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
2)
Specify an LSR ID
3)
[RTB] mpls
4)
[RTB-Serial2/0] mpls
5)
6)
7)
8)
9)
23
2. 1)
[RTC] router id 3.3.3.3 [RTC] ospf [RTC-ospf-1] area 0 [RTC-ospf-1-area-0.0.0.0] network 192.2.2.0 0.0.0.3 [RTC-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
2)
Specify an LSR ID
3)
[RTC] mpls
4)
[RTC-Serial2/0] mpls
5)
6)
7)
8)
9)
24