HCIE-R&S Huawei Certified Internetwork Expert-Routing and Switching Training Lab Guide PDF

The privilege of HCNA/HCNP/HCIE:
With any Huawei Career Certification, you have the privilege on http://learning.huawei.com/en to enjoy:
n
 1、e-Learning Courses： Logon http://learning.huawei.com/en and enter Huawei Training/e-Learning
/e

o m
If you have the HCNA/HCNP certificate：You can access Huawei Career Certification and Basic Technology e-Learning
courses.
e i .c
If you have the HCIE certificate: You can access all the e-Learning courses which marked for HCIE Certification Users.
aw

Methods to get the HCIE e-Learning privilege : Please associate HCIE certificate information with your Huawei account, and
hu

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.

g .
 2、 Training Material Download
i n

arn
Content: Huawei product training material and Huawei career certification training material.

//le
Method：Logon http://learning.huawei.com/en and enter Huawei Training/Classroom Training ,then you can download
training material in the specific training introduction page.
p :
 3、 Priority to participate in Huawei Online Open Class (LVC)
t t

s :h
The Huawei career certification training and product training covering all ICT technical domains like R&S, UC&C, Security,
4、Learning Tools: rc e
Storage and so on, which are conducted by Huawei professional instructors.
u

s o
eNSP ：Simulate single Router&Switch device and large network.

R e
WLAN Planner ：Network planning tools for WLAN AP products.

n g
In addition, Huawei has built up Huawei Technical Forum which allows candidates to discuss technical issues with Huawei experts ,
ni
share exam experiences with others or be acquainted with Huawei Products.
a r
 Statement:
L e
r e
This material is for personal use only, and can not be used by any individual or organization for any commercial purposes.
o
M
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 1
RIP Hands-on Exercise Guide Confidentiality Level
HCIE-R&S Exercise Guide
Chapter 1 RIP Hands-on Exercise Guide...................................................................................... 4

Overview ................................................................................................................................... 4
n
Objectives.................................................................................................................................. 4
Tasks .......................................................................................................................................... 4
/ e
Topology .................................................................................................................................... 5
o m
.c
IP Address Table ........................................................................................................................ 5
i
Configuration and Verification .................................................................................................. 6
e
w
Questions ................................................................................................................................ 14
a
Configuration List .................................................................................................................... 14
u
.h
Chapter 2 OSPF Hands-on Exercise Guide ................................................................................ 20
g
Overview ................................................................................................................................. 20
i n
Objectives................................................................................................................................ 21
n
r
Tasks ........................................................................................................................................ 21
lea
Topology .................................................................................................................................. 22
//
IP Address Table ...................................................................................................................... 22
:
t t p
Configuration and Verification ................................................................................................ 23
Questions ................................................................................................................................ 32
:h
s
e
Chapter 3 IS-IS Hands-on Exercise Guide ................................................................................. 42
r c
Overview ................................................................................................................................. 42
ou
Objectives................................................................................................................................ 43
s
Tasks ........................................................................................................................................ 43
e
R
Topology .................................................................................................................................. 44
i n g
IP Address Table ...................................................................................................................... 44
r n
Questions ................................................................................................................................ 53
e a
e L
Chapter 4 BGP Basics Hands-on Exercise Guide ....................................................................... 62
or Overview ................................................................................................................................. 62
Objectives................................................................................................................................ 62
M Tasks ........................................................................................................................................ 62
Topology .................................................................................................................................. 63
IP Address Table ...................................................................................................................... 63
Questions ................................................................................................................................ 70
Chapter 5 BGP Advanced Hands-on Exercise Guide ................................................................ 77
Overview ................................................................................................................................. 77
Objectives................................................................................................................................ 78
2015-8-31 Huawei Confidential Page 1 of 226

Tasks ........................................................................................................................................ 78
Topology .................................................................................................................................. 79
IP Address Table ...................................................................................................................... 79
Questions ................................................................................................................................ 89
Chapter 6 Route Import and Control Hands-on Exercise Guide ........................................... 101
n
Overview ...............................................................................................................................101
Objectives..............................................................................................................................101
/ e
m
Tasks ......................................................................................................................................101
o
.c
Topology ................................................................................................................................102
i
IP Address Table ....................................................................................................................102
e
w
Configuration and Verification ..............................................................................................103
a
Questions ..............................................................................................................................107
u
.h
Configuration List ..................................................................................................................107
g
Chapter 7 VLAN Hands-on Exercise Guide ............................................................................. 117
i n
Overview ...............................................................................................................................117
n
r
Objectives..............................................................................................................................117
lea
Tasks ......................................................................................................................................117
//
Topology ................................................................................................................................119
p :
IP Address Table ....................................................................................................................119
t t
:h
Questions ..............................................................................................................................128
s
e
r c
Chapter 8 LAN Layer 2 Technology Hands-on Exercise Guide ............................................. 135
ou
Overview ...............................................................................................................................135
s
Objectives..............................................................................................................................135
e
R
Tasks ......................................................................................................................................135
i n g
Topology ................................................................................................................................136
IP Address Table ....................................................................................................................136
r n
e a
Questions ..............................................................................................................................141
e L Configuration List ..................................................................................................................141
or Chapter 9 WAN Layer 2 Technology Hands-on Exercise Guide ............................................. 146

Overview ...............................................................................................................................146
M Objectives..............................................................................................................................146
Tasks ......................................................................................................................................146
Topology ................................................................................................................................147
IP Address Table ....................................................................................................................147
Questions ..............................................................................................................................149
Chapter 10 STP Hands-on Exercise Guide ............................................................................... 155
Overview ...............................................................................................................................155

Objectives..............................................................................................................................155
Tasks ......................................................................................................................................155
Topology ................................................................................................................................156
IP Address Table ....................................................................................................................156
Questions ..............................................................................................................................161
n
Chapter 11 Multicast Hands-on Exercise Guide ...................................................................... 168
Overview ...............................................................................................................................168
/ e
Objectives..............................................................................................................................169
o m
.c
Tasks ......................................................................................................................................169
i
Topology ................................................................................................................................170
e
w
IP Address Table ....................................................................................................................170
a
u
.h
Questions ..............................................................................................................................175
i n g
Chapter 12 IPv6 Hands-on Exercise Guide .............................................................................. 185
r n
Overview ...............................................................................................................................185
lea
Objectives..............................................................................................................................186
//
Tasks ......................................................................................................................................186
p :
Topology ................................................................................................................................187
t t
IP Address Table ....................................................................................................................187
:h
s
e
r c
Chapter 13 Hands-on Exercise Guide to Other Features ........................................................ 203
ou
Overview ...............................................................................................................................203
s
Objectives..............................................................................................................................205
e
R
Tasks ......................................................................................................................................205
i n g
Topology ................................................................................................................................206
IP Address Table ....................................................................................................................206
r n
e a
Questions ..............................................................................................................................213
e L Configuration List ..................................................................................................................213
or
M

Chapter 1 RIP Hands-on Exercise Guide

Overview
The Routing Information Protocol (RIP) is a simple Interior Gateway Protocol (IGP). It
is used on small-scale networks such as campus networks and simple regional networks. It is
not suitable for complex and large networks.
As a distance-vector routing protocol, RIP exchanges routing information through User
Datagram Protocol (UDP) packets with port 520.
RIP measures the distance from a source to a destination by a metric known as hop
e n
count. In RIP, by default, the hop count from a device to its directly connected network is 0,
/
and the hop count from a device to a network that is reachable through another device is 1.
o m
.c
That is, the hop count (metric) equals the number of devices along the path from the local
e i
network to the destination network. To restrict the route convergence time, RIP requires that
the hop count be an integer ranging from 0 to 15. A hop count of 16 is defined as infinite.
used in large networks.

aw
That is, the destination network or host is unreachable. Due to this restriction, RIP cannot be
u
.h
To improve performance and prevent routing loops, RIP supports split horizon and
poison reverse.
n g
As one of the earliest forms of IGP, RIP is designed for small and medium-scale
i
n
networks. RIP implementation, configuration, and maintenance are easier than those of OSPF
and IS-IS, and so RIP is widely used on networks.
r
Objectives
// lea
p :
t
Upon completion of this exercise guide, you will be able to:
t
:h
 Configure RIP.
 Learn about application scenarios of route summarization and perform the correct
configuration.
e s
 Modify the metrics of routes.
r c
 Understand the compatibility of RIPv1 and RIPv2.
ou
 Control the advertising and receiving of RIP routes.
es
 Configure advertisement of RIP default routes.
 Optimize a RIP network by adjusting parameters including authentication and timers.
R
 Troubleshoot RIP faults on RIP networks.
i n g
n
Tasks
ar
L e The following topology shows the network of Company A. Deploy the network
according to the following requirements:
r e (1) Run the default RIP version on R1 since R1 is a legacy device, and run RIPv2 on all
o
other devices. Advertise the interfaces identified in the topology, and avoid advertising
service networks 1.0.0.0/24, 2.0.0.0/24, 5.0.X.0/24, and 6.0.X.0/24 into RIP because
M traffic transmitted on these service networks is special.
(2) Import service networks 1.0.0.0/24 and 2.0.0.0/24 into RIP, using the default metric.
Prevent R2 from receiving the RIP packets sent by R1 to ensure security.
(3) Avoid the impact of malicious users connecting to E0/0/1 of R2 on the network, but
enable E0/0/1 to learn current network routes as it may connect to legitimate routers.
(4) Ensure that the metric of routes to service network 1.0.0.0/8 learned on R4 is 4 and
retain the default metric for all other routes. Do not perform the configuration on R4 for
security purposes.
(5) Import only service network segments 6.0.0.0/24 and 6.0.2.0/24 into RIP, and use the
default metric for the imported routes. Use the least number of commands to meet this
requirement.
(6) Import service network 5.0.X.0/24 into RIP, and summarize routes to improve efficiency.
To prevent routing loops, do not use static routes.
(7) Prevent R5 and R6 from directly exchanging routes for security purposes, but allow
their networks to be reachable by one another.
(8) Enable R4 that connects to the Internet as well as all the other devices to access the
Internet.
(9) Adjust RIP timers on the entire network to speed up RIP convergence. For example, set
the update and aging timers to 20s and 100s respectively, and adjust the garbage-collect
timer according to service requirements.
(10) Configure plain-text authentication on some devices to ensure security, and set the
e n
/
password to Huawei.
Topology
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
IP Address Table
arn Default
L e Device Interface IP Address Subnet Mask

Gateway
e
or
R1 E0/0/0 192.168.1.1 255.255.255.0 N/A
E0/0/0 192.168.1.2 255.255.255.0 N/A
M R2
E0/0/1 20.0.0.2 255.255.255.0 N/A
E0/0/0 192.168.1.3 255.255.255.0 N/A
R3
G0/0/0 34.1.1.3 255.255.255.0 N/A
G0/0/0 34.1.1.4 255.255.255.0 N/A
R4 E0/0/0 192.168.2.4 255.255.255.0 N/A
G0/0/1 40.0.0.4 255.255.255.0 N/A
R5 E0/0/0 192.168.2.5 255.255.255.0 N/A

R6 E0/0/0 192.168.2.6 255.255.255.0 N/A
Configuration and Verification
1. Run the default RIP version on R1 since R1 is a legacy device, and run
RIPv2 on all other devices. Advertise the interfaces identified in the topology,
and avoid advertising service networks 1.0.0.0/24, 2.0.0.0/24, 5.0.X.0/24, and
6.0.X.0/24 into RIP because traffic transmitted on these service networks is
special.
e n
/
Perform basic configuration according to the address table, and then run the display rip
1 interface command to check whether RIP is enabled on related interfaces and whether
o m
interface addresses are configured correctly. The following uses the display of R2 as an
example.
e i .c
[R2]display rip 1 interface
aw
u
.h
Interface IP Address State Protocol MTU
Eth0/0/1 20.0.0.2 UP
i
RIPv2 Multicast
n g 500
Eth0/0/0 192.168.1.2 UP
r n
RIPv2 Multicast 500
le a
//
During the configuration, advertise addresses of R2 interface (E0/0/1) and R4 interface
:
(G0/0/1) in RIP to meet the requirement that interfaces identified in the experimental
topology be advertised.
t t p
You can also run the following commands to verify the results:
:h
display ip routing-table
s
display rip 1 neighbor
2.
r c e
Import service networks 1.0.0.0/24 and 2.0.0.0/24 into RIP, using the default
ou
metric. Prevent R2 from receiving the RIP packets sent by R1 to ensure
security.
es
R
RIP can enable the function of silent-interface to limit the packet sending from this
i n g
interface, also we can use the command "undo rip input/output "under interface. What’s more,
filter-policy can be also used in the situation.
r n
After completing this task, run the display ip routing-table protocol rip command to
a
view the RIP routing tables of R1 and R2. The following RIP routing tables show only key
e
L
information, while other information is omitted.
r e [R1]display ip routing-table protocol rip
o RIP routing table status : <Active>
M Destinations : 4 Routes : 4
Destination/Mask Proto Pre Cost Flags NextHop Interface
2.0.0.0/24 RIP 100 1 D 192.168.1.2 Ethernet0/0/0
20.0.0.0/24 RIP 100 1 D 192.168.1.2 Ethernet0/0/0
34.1.1.0/24 RIP 100 1 D 192.168.1.3 Ethernet0/0/0

192.168.2.0/24 RIP 100 2 D 192.168.1.3 Ethernet0/0/0
[R2]display ip routing-table protocol rip
RIP routing table status : <Active>
Destinations : 2 Routes : 2
e n
/
34.1.1.0/24 RIP 100 1 D 192.168.1.3 Ethernet0/0/0
o m
192.168.2.0/24 RIP 100 2 D 192.168.1.3
i
Ethernet0/0/0
e .c
aw
During the configuration, control the routes to be imported to meet the requirement that
only external network routes 1.0.0.0/24 and 2.0.0.0/24 are imported. Therefore, other external
routes must be filtered.
u
g .h
R1 runs the default version, while R2 and R3 run RIPv2. Version compatibility must be
considered. When RIP version is not specified for a Huawei device, the device can receive
both RIPv1 and RIPv2 packets but can send only RIPv1 packets.
ni n
r
To meet the requirement that R2 not receive the RIP packets sent by R1, R1 should
lea
unicast Update packets to R3, but R2 can accept RIPv2 broadcast packets, so R3 must update
//
by RIPv2 broadcast . When RIP version is not specified for a Huawei device, the device
:
broadcasts update packets. You can also run the following command to verify the results:
display rip 1 route
display rip 1 database
t t p
h connecting to E0/0/1 of R2 on the
3. Avoid the impact of malicious: users
e s current network routes as it may connect
c
network, but enable E0/0/1 to learn
to legitimate routers.
ur
s o
After completing this task, run the debugging rip 1 receive Ethernet 0/0/1 command.
R e
The command output is empty.
According to the requirement, R2 interface E0/0/1 has been advertised in RIP. Therefore,
n g
the command output includes RIP information on this interface. How to filter RIP update
i
packets when E0/0/1 is advertised should be considered.
a rnthat the metric of routes to service network 1.0.0.0/8 learned on R4 is

4eand retain the default metric for all other routes. Do not perform the
4. Ensure
L
e configuration on R4 for security purposes.
or After completing this task, run the display ip routing-table command to view the IP
M routing table of R4. The following IP routing table shows only key information, while other
information is omitted.
[R4]display ip routing-table
1.0.0.0/8 RIP 100 4 D 34.1.1.3 GigabitEthernet0/0/0

During the configuration, to meet the requirement that the metric of route to 1.0.0.0/8
learned on R4 be 4, ensure that the cost of other RIP routes learned on R4 remains
unchanged.
You can also run the following command to verify the results:
display rip 1 route
5. Import only service network segments 6.0.0.0/24 and 6.0.2.0/24 into RIP, and
use the default metric for the imported routes. Use the least number of
e n
commands to meet this requirement.
/
After completing this task, run the display ip routing-table protocol rip command to
o m
view the RIP routing table of R4. The following RIP routing table shows only key
e i .c
[R4]display ip routing-table protocol rip
aw
u
.h
RIP routing table status : <Active>
i n g
Destination/Mask Proto Pre Cost
r
Flags NextHop
n Interface
1.0.0.0/8 RIP 100 4 D
// lea
34.1.1.3 GigabitEthernet0/0/0
2.0.0.0/24 RIP 100 2

p
D : 34.1.1.3 GigabitEthernet0/0/0
t t
:h
6.0.0.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0
6.0.2.0/24 RIP
e s
100 1 D 192.168.2.6 Ethernet0/0/0
r c
ou
192.168.1.0/24
es RIP 100 1 D 34.1.1.3 GigabitEthernet0/0/0
R
The default metric of routes imported in RIP on a Huawei device is 1. Additionally,
i n g
ensure that the least number of commands are used.
r n
display acl all
e a display ip ip-prefix
L
e improve efficiency. To prevent routing loops, do not use static routes.
6.
Import service network 5.0.X.0/24 into RIP, and summarize routes to
or
M After completing this task, run the display ip routing-table command to view the RIP
routing table of R4. The following IP routing table shows only key information, while other
information is omitted.

5.0.0.0/8 RIP 100 1 D 192.168.2.5 Ethernet0/0/0
6.0.0.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0
6.0.2.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0
To perform classful route summarization, summarize 5.0.X.0/24 into 5.0.0.0/8.

e n
When a Huawei device performs automatic or manual summarization, the device does
/
not generate routes pointing to Null0. Therefore, consider how to prevent routing loops after
o m
.c
route summarization is performed.
display ip ip-prefix
e i
display route-policy
aw
but allow their networks to be reachable by one another. .h
u
7. Prevent R5 and R6 from directly exchanging routes for security purposes,
i n g
n
After completing this task, run the display rip 1 neighbor and display ip routing-table
ar
commands to view the neighbors and IP routing tables of R5 and R6, and perform ping tests
e
between them. Only key information is displayed, while other information is omitted.
l
[R5]display rip 1 neighbor
: //
t tp
---------------------------------------------------------------------
: h
s
IP Address Interface Type Last-Heard-Time
r c e
---------------------------------------------------------------------
192.168.2.4
o u Ethernet0/0/0 RIP 0:0:15
e s
R
Number of RIP routes : 2
i n g
arn
[R6]display rip 1 neighbor
L e ---------------------------------------------------------------------
e
or
IP Address Interface Type Last-Heard-Time
M ---------------------------------------------------------------------
192.168.2.4 Ethernet0/0/0 RIP 0:0:6
Number of RIP routes : 3

1.0.0.0/8 RIP 100 5 D 192.168.2.4 Ethernet0/0/0
2.0.0.0/8 RIP 100 3 D 192.168.2.4 Ethernet0/0/0
6.0.0.0/8 RIP 100 2 D 192.168.2.4 Ethernet0/0/0
20.0.0.0/8 RIP 100 3 D 192.168.2.4 Ethernet0/0/0
34.0.0.0/8 RIP 100 1 D 192.168.2.4 Ethernet0/0/0
e n
/
192.168.1.0/24 RIP 100 2 D 192.168.2.4 Ethernet0/0/0
o m
e i .c
Destination/Mask Proto Pre Cost Flags NextHop
w
Interface
a
u
.h
1.0.0.0/8 RIP 100 5 D 192.168.2.4 Ethernet0/0/0
2.0.0.0/8 RIP 100 3 D 192.168.2.4
i n g
Ethernet0/0/0
5.0.0.0/8 RIP 100 2 D

r n
192.168.2.4 Ethernet0/0/0
6.0.0.0/8 RIP 100 2 D
// lea
192.168.2.4 Ethernet0/0/0
p :
t
20.0.0.0/8 RIP 100 3 D 192.168.2.4 Ethernet0/0/0
t
:h
34.0.0.0/8 RIP 100 1 D 192.168.2.4 Ethernet0/0/0
192.168.1.0/24 RIP
e s
100 2 D 192.168.2.4 Ethernet0/0/0
r c
s ou
e
[R5]ping 6.0.0.1
R
g
PING 6.0.0.1: 56 data bytes, press CTRL_C to break
n i n
Reply from 6.0.0.1: bytes=56 Sequence=1 ttl=255 time=70 ms
ar
e
e L Reply from 6.0.0.1: bytes=56 Sequence=3 ttl=255 time=80 ms
or Reply from 6.0.0.1: bytes=56 Sequence=4 ttl=255 time=100 ms
M Reply from 6.0.0.1: bytes=56 Sequence=5 ttl=255 time=80 ms
[R6]ping 5.0.0.1

By default, R5 and R6 multicast update packets. That is, R5 and R6 receive update
packets from one another.
When R5 and R6 send RIP update packets only to R4, R4 does not send the update
n
packets back to R5 or R6 via the inbound interface of the update packets due to the loop
prevention mechanism.
/ e
debugging rip 1
o m
8. Enable R4 that connects to the Internet as well as all the other devices cto
access the Internet. e i.
aw
hu
RIP must combine the static default route to advertise dynamic default route.
.
After completing this task, run the display ip routing-table command to view the IP
while other information is omitted.

i n g
routing tables of R1 and R4. The following IP routing table shows only key information,
r n
l e a
//
:
tp
0.0.0.0/0 RIP 100 2 D 192.168.1.3 Ethernet0/0/0
2.0.0.0/24 RIP
ht
100 1 D 192.168.1.2 Ethernet0/0/0
s :
5.0.0.0/8
r
RIP
c e 100 3 D 192.168.1.3 Ethernet0/0/0
6.0.0.0/24
o u RIP 100 3 D 192.168.1.3 Ethernet0/0/0
e s
6.0.2.0/24 RIP 100 3 D 192.168.1.3 Ethernet0/0/0
R
g
20.0.0.0/24 RIP 100 1 D 192.168.1.2 Ethernet0/0/0
i n
rn
34.1.1.0/24 RIP 100 1 D 192.168.1.3 Ethernet0/0/0
e a 40.0.0.0/24 RIP 100 2 D 192.168.1.3 Ethernet0/0/0
e L 192.168.2.0/24 RIP 100 2 D 192.168.1.3 Ethernet0/0/0
or
M [R4]display ip routing-table
0.0.0.0/0 Static 60 0 D 40.0.0.4 GigabitEthernet0/0/1
5.0.0.0/8 RIP 100 1 D 192.168.2.5 Ethernet0/0/0

6.0.0.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0
6.0.2.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0
n
9. Adjust RIP timers on the entire network to speed up RIP convergence. For
example, set the update and aging timers to 20s and 100s respectively, and
adjust the garbage-collect timer according to service requirements. / e
o m
.c
After completing this task, run the display rip 1 command to view the settings of timers.
e
The following uses the display of R1 as an example. Only key information is displayed,
while other information is omitted. i
[R1]display rip 1
aw
u
Public VPN-instance
g .h
RIP process : 1
ni n
r
lea
RIP version : 1
Preference : 100
: //
Checkzero : Enabled
t t p
Default-cost : 0
s :h
Summary
r
: Enabled
c e
Host-route
s ou
: Enabled
Re
Maximum number of balanced paths : 32
ing
Update time : 20 sec Age time : 100 sec
arn Garbage-collect time : 30 sec
L e Actually, there is no direct relationship between the update and garbage-collect timers.
However, the test experience tells us that the update timer value should be smaller than the
r e garbage-collect timer value.
o
M 10. Configure plain-text authentication on some devices to ensure security, and
set the password to Huawei.
After completing this task, run the display rip 1 interface command to view the
authentication settings. The following uses the display of R4 as an example.
[R4]display rip 1 interface verbose
GigabitEthernet0/0/0(34.1.1.4)
State : UP MTU : 500

Metricin : 0
Metricout : 1
Input : Enabled Output : Enabled
Protocol : RIPv2 Multicast
Send version : RIPv2 Multicast Packets
e n
/
Receive version : RIPv2 Multicast and Broadcast Packets
Poison-reverse : Disabled
o m
Split-Horizon : Enabled
e i .c
Authentication type : Simple
aw
u
.h
Replay Protection : Disabled
GigabitEthernet0/0/1(40.0.0.4)
i n g
State : UP MTU : 500
r n
Metricin : 0
// lea
p :
t
Metricout : 1
t
:h
Protocol
e s
: RIPv2 Multicast
r c
ou
es
R
g
n i n
Split-Horizon : Enabled
ar
e
e L Replay Protection : Disabled
or Ethernet0/0/0(192.168.2.4)
M State : UP MTU : 500
Metricin : 0
Metricout : 1
Protocol : RIPv2 Multicast

Split-Horizon : Disabled
Replay Protection : Disabled
The authentication password is case-sensitive. R1 runs the Huawei default version,

e n
which does not support authentication. Therefore, pay more attention when performing
/
configurations on R1, R2, and R3.
o m
Questions
e i .c
aw
In requirement 2, when version compatibility is not considered, can R2 learn routes to
u
1.0.0.0/24 based on the existing configuration?
.h
R2 can’t receive R3’s update about 1.0.0.0/24 even if RIPv1 compatible with RIPv2.
g
RIP has default rule of split-horizon under interface so the segment network 1.0.0.0 will
i n
never send again from the interface E3/0/0 in R3 unless we disable split-horizon.
In requirement 4, why does 1.0.0.0/8 but not 1.0.0.0/24 exist?
n
r
lea
RIP doesn’t support VLSM by using RIPv1. RIPv1 processes packets based on the main
class network segment mask or interface address mask so R3 gets 1.0.0.0/8
//
In requirement 7, does any problem occur when you ping 6.1.1.1 from R5, if so, how to
:
solve the problem, and why are routes to the peer end learned by R5 and R6?
p
t
When R5 tries to ping 6.1.1.1, the request will send to R4, R4 will choose G0/0/1 as
t
:h
output interface via default route. But the route can’t arrive because it’s not real in this
topology so we need to configure a static route with Null0 as next hop to avoid loop.
e s
Because RIPv2 enable the feature of summary by default so R5 and R6 all get /8 routes.
c
If we want to get detail routes we just use command of undo summary.
r
Configuration List
s ou
Re
<R1>display current-configuration
#
i n g
r n
e a
sysname R1
eL
#
or interface Ethernet0/0/0
M ip address 192.168.1.1 255.255.255.0
interface LoopBack0
ip address 1.0.0.1 255.255.255.0
rip 1

peer 192.168.1.3
network 192.168.1.0
silent-interface Ethernet0/0/0
timers rip 20 100 30
import-route direct route-policy DIRECT
e n
/
#
route-policy DIRECT permit node 10
o m
if-match ip-prefix 10
e i .c
#
aw
u
.h
ip ip-prefix 10 index 10 permit 1.0.0.0 24
i n g
return
r n
// lea
p :
t
t
:h
#
sysname R2
e s
r c
ou
#
es
interface Ethernet0/0/0
R
g
ip address 192.168.1.2 255.255.255.0
n i n
ar
e
ip address 20.0.0.2 255.255.255.0
e L undo rip input
or #
M interface LoopBack0
ip address 2.0.0.1 255.255.255.0
rip 1
version 2
network 192.168.1.0

network 20.0.0.0
import-route direct route-policy DIRECT
route-policy DIRECT permit node 10
e n
/
o m
e i .c
#
aw
u
.h
return
i n g
r n
#
// lea
p :
t
sysname R3
t
:h
#
e s
r c
ou
ip address 192.168.1.3 255.255.255.0
es
rip version 2 broadcast
R
g
#
n i n
interface GigabitEthernet0/0/0
ar
e
ip address 34.1.1.3 255.255.255.0
e L rip authentication-mode simple plain Huawei
or rip metricout ip-prefix 10 3
M #
rip 1
version 2
network 192.168.1.0
network 34.0.0.0

return
e n
/
o m
sysname R4
e i .c
#
aw
u
.h
ip address 192.168.2.4 255.255.255.0
i n g
rip authentication-mode simple plain Huawei
r n
#
// lea
p :
t
t
:h
ip address 34.1.1.4 255.255.255.0
e s
r c
ou
#
es
R
g
ip address 40.0.0.4 255.255.255.0
n i n
ar
e
#
e L rip 1
or default-route originate
M version 2
network 192.168.2.0
network 34.0.0.0
network 40.0.0.0

ip route-static 0.0.0.0 0.0.0.0 GigabitEthernet0/0/1
return
e n
/
#
sysname R5
o m
#
e i .c
aw
u
.h
ip address 192.168.2.5 255.255.255.0
i n g
rip summary-address 5.0.0.0 255.0.0.0 avoid-feedback
r n
#
// lea
p :
t
interface LoopBack0
t
:h
ip address 5.0.0.1 255.255.255.0
#
e s
r c
ou
interface LoopBack1
es
ip address 5.0.1.1 255.255.255.0
R
g
#
n i n
interface LoopBack2
ar
e
ip address 5.0.2.1 255.255.255.0
e L #
or interface LoopBack3
M ip address 5.0.3.1 255.255.255.0
rip 1
version 2
peer 192.168.2.4
network 192.168.2.0

import-route direct route-policy FILTER
route-policy FILTER permit node 10
e n
/
o m
ip ip-prefix 10 index 10 permit 5.0.0.0 22 greater-equal 24 less-equal 24
e i .c
#
aw
u
.h
return
i n g
r n
#
// lea
p :
t
sysname R6
t
:h
#
acl number 2000

e s
r c
ou
rule 5 permit source 6.0.0.0 0.0.254.255
#
es
R
g
n i n
ip address 192.168.2.6 255.255.255.0
ar
e
e L #
M ip address 6.0.0.1 255.255.255.0
interface LoopBack1
ip address 6.0.1.1 255.255.255.0
interface LoopBack2

ip address 6.0.2.1 255.255.255.0
interface LoopBack3
ip address 6.0.3.1 255.255.255.0
e n
/
rip 1
version 2
o m
peer 192.168.2.4
e i .c
network 192.168.2.0
aw
u
.h
i n g
import-route direct route-policy FILTER
r n
#
// lea
p :
t
route-policy FILTER permit node 10
t
:h
if-match acl 2000
#
e s
r c
ou
return
es
R 2 OSPF Hands-on Exercise Guide
i n g
Chapter
Overviewn
ar
L e IETF developed Open Shortest Path First (OSPF), a link state Internal Gateway Protocol
e (IGP), as an enhancement to distance-vector routing protocols in the late 1980s.
or
OSPF version 1 (OSPFv1) was first defined in RFC 113 but was soon replaced by OSPF
version 2 (OSPFv2) defined in RFC 1247. OSPFv2 made great improvements in stability and
M functionality, and is used on existing IPv4 networks，but OSPFv3 is mainly used for IPv6
network.
With advantages of fast convergence, no loop, and good scalability, OSPF as a link state
routing protocol is widely applied. A link state routing protocol advertises link state
information. Each router on a network sends its own link state information (including the IP
address and subnet mask of the interface, network type, and link cost) to other routers. After
all routers collect all link state information on the network, they know the entire network
topology and use the shortest path first (SPF) algorithm to calculate the shortest paths to all
network segments.
OSPF allows multiple areas on a network. An area is regarded as a logical group, and
each group is identified by a 32 bit area ID. A network segment or a link belongs to only one
area. That is, you must specific the area to which each OSPF-enabled interface belongs. Area
0 is the OSPF backbone area and is responsible for advertising routing information between
non-backbone areas. There is only one backbone area on an OSPF network.
In a single OSPF area, each router needs to collect link state information from all other
routers. When a large number of routers run OSPF, there is much link state information and
the sizes of link state databases (LSDBs) on routers become large accordingly, increasing
loads on the routers and complicating maintenance and management. To resolve this issue,
OSPF partitions the Autonomous System (AS) into different areas.
Link state information is flooded only within the local area. Routers advertise only the
n
number of routes among areas, greatly reducing loads on routers. A router that belongs to
different areas is called the Area Border Router (ABR). The ABR is used to transmit
inter-area routing information. The way in which inter-area routing information is transmitted
/ e
is similar to the distance-vector algorithm. To prevent loops between areas, ensure that
o m
.c
routing information between non-backbone areas is forwarded through the backbone area.
That is, each non-backbone area is connected to the backbone area, and routers in
non-backbone areas cannot exchange routing information with each other.
e i
aw
Objectives
u
g .h


Configure a single OSPF area and multiple OSPF areas.
ni n
r
Configure Not-So-Stubby Area (NSSA) areas.
lea
 Configure OSPF route filtering.
 Configure OSPF route summarization.


Configure OSPF authentication.
: //
p
Configure OSPF to advertise default routes.
 Adjust OSPF timers.
t t
:h
 Configure virtual links.
 Configure link-state advertisement (LSA) filtering.
e s
Tasks
r c
s ou
The following topology shows the network of Company A. Deploy the network
Re
(1) Configure multiple OSPF areas. Configure Routing Information Protocol Version 2
i n g
(RIPv2) between R3 and R6, and between R4 and R6. Configure Loopback 0 interfaces
on R1, R2, R3, and R4 to advertise routes to Area 0. Configure R5 to advertise routes to
r n
Area 1 and R6’s direct-connected interfaces to advertise routes to RIP.
a
(2) Configure R6 to advertise routes of internal network segments 192.168.10.0/24 and
L e 192.168.20.0/24 to RIP. Configure R5 to import routes of external network segments

172.16.10.0/24 and 172.16.20.0/24 to OSPF.
r e (3) On R3 and R4, configure OSPF and RIP to import routes from each other, and import
o routes of network segments 192.168.10.0/24 and 192.168.20.0/24 to OSPF.
M
(4) Configure Area 2 as an NSSA area to reduce the number of LSAs (including Type 3 and
Type 5 LSAs) in Area 2.
(5) Perform the configurations only on R3 to ensure that R5 accesses network segment
192.168.10.0/24 through R1 and accesses network segment 192.168.20.0/24 through
R2.
(6) Eliminate existing suboptimal paths on the OSPF network.
(7) Improve robustness of the OSPF network to ensure that the physical link between R1
and R2 is stable.
(8) Optimize the OSPF routing table on R5, reduce the number of LSAs to maintain, and
summarize the two network segments on R5.
(9) Adjust OSPF timers based on the status of the link between R2 and R4.
(10) Configure cipher text authentication in OSPF areas to improve security of the OSPF

network.
Topology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
IP Address Table
r c e
Device
s ou
Interface IP Address Subnet Mask
Default
Re Gateway
g
G0/0/0 10.0.12.1 255.255.255.0 N/A
n
R1i n G0/0/1 10.0.13.1 255.255.255.0 N/A
ar G0/0/2 10.0.15.1 255.255.255.0 N/A
L e Loopback 0 10.0.1.1 255.255.255.255 N/A
r e G0/0/1 10.0.12.2 255.255.255.0 N/A
o G0/0/2 10.0.25.2 255.255.255.0 N/A
M
R2
S1/0/0 10.0.24.2 255.255.255.0 N/A
Loopback 0 10.0.2.2 255.255.255.255 N/A
G0/0/0 10.0.13.3 255.255.255.0 N/A
G0/0/1 10.0.34.3 255.255.255.0 N/A
R3
G0/0/2 10.0.36.3 255.255.255.0 N/A
Loopback 0 10.0.3.3 255.255.255.255 N/A
R4 G0/0/0 10.0.34.4 255.255.255.0 N/A

G0/0/2 10.0.46.4 255.255.255.0 N/A

S1/0/0 10.0.24.4 255.255.255.0 N/A
Loopback 0 10.0.4.4 255.255.255.255 N/A
G0/0/0 10.0.15.5 255.255.255.0 N/A
R5 G0/0/1 10.0.25.5 255.255.255.0 N/A
Loopback 0 10.0.5.5 255.255.255.255 N/A
G0/0/0 10.0.36.6 255.255.255.0 N/A
e n
R6 G0/0/1 10.0.46.6 255.255.255.0 N/A
/
Loopback 0 10.0.6.6 255.255.255.255 N/A
o m
Configuration and Verification e i .c
a wR6, and
1. Configure multiple OSPF areas. Configure RIPv2 between R3 and
hu R3, and R4
between R4 and R6. Configure Loopback 0 interfaces on R1, R2,
g .
to advertise routes to Area 0. Configure R5 to advertise routes to Area 1 and
i n
R6’s direct-connected interfaces to advertise routes to RIP.
n
ar
e
Perform basic configurations according to the IP address table, and then check whether
// l
OSPF neighbor relationships are established, whether devices can receive routes from
:
Loopback 0 interfaces on other devices, and whether the RIP routing domain is properly
tp
working. The following uses the display of R3 as an example. (The following table lists only
t
key information, and as such some information is omitted.)
h
s :
c e
Route Flags: R - relay, D - download to fib
r
o u
-------------------------------------------------------------------------
e s
R
Routing Tables: Public
i n g Destinations : 28 Routes : 29
arn
L e 10.0.1.1/32 OSPF 10 1 D 10.0.13.1 GigabitEthernet0/0/0
e
or
10.0.2.2/32 OSPF 10 2 D 10.0.13.1 GigabitEthernet0/0/0
M

RIP 100 1 D 10.0.34.4 GigabitEthernet0/0/1
172.16.10.0/24 O_ASE 150 1 D 10.0.13.1 GigabitEthernet0/0/0
e n
/
o m
You can also run the following commands to verify the result:
display ospf peer brief
e i .c
display ip routing-table protocol ospf
aw
display rip 1 route
u
display ospf routingdisplay ip routing-table protocol rip
g .h
2. Configure R6 to advertise routes of internal network segments
ni n
r
lea
192.168.10.0/24 and 192.168.20.0/24 to RIP. Configure R5 to import routes of
external network segments 172.16.10.0/24 and 172.16.20.0/24 to OSPF.
: //
p
RIP only supports advertise routes in classful format, but it can be identified in RIPv2
by using VLSM.
t t
:h
Note that only network segments 172.16.10.0/24 and 172.16.20.0/24 on R5 need to be
added.
e s
After completing this task, run the display ip routing-table command to view the
r c
routing table of R1. (The following table lists only key information, and as such some
ou
information is omitted.)
s
Re
i n g
-------------------------------------------------------------------------
r n
a
e
eL
or
M 172.16.10.0/24 O_ASE 150 1 D 10.0.15.5 GigabitEthernet0/0/2
3. On R3 and R4, configure OSPF and RIP to import routes from each other,
and import routes of network segments 192.168.10.0/24 and 192.168.20.0/24
to OSPF.
After completing this task, run the display ospf routing command to view the OSPF
routing table of R3 & R4. (The following table lists only key information, and as such some
[R3]display ospf routing
OSPF Process 1 with Router ID 10.0.3.3
Routing Tables
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
e n
/
172.16.0.0/16 2 Type2 1 10.0.13.1 10.0.5.5
192.168.10.0/24 1 Type2 1 202.101.34.4 10.0.4.4
o m
192.168.20.0/24 1 Type2 1 202.101.34.4 10.0.4.4
e i .c
Routing for NSSAs
aw
u
.h
192.168.10.0/24 1 Type2 1
n
10.0.34.4
i g 10.0.4.4
192.168.20.0/24 1 Type2 1
r n
10.0.34.4 10.0.4.4
// lea
p :
t
<R4>display ospf routing
t
:h
Routing Tables
e s
r c
ou
Routing for ASEs
Destination
es Cost Type Tag NextHop AdvRouter
R
g
172.16.0.0/16 2 Type2 1 202.101.34.3 10.0.5.5
n i n
192.168.10.0/24 1 Type2 1 202.101.34.3 10.0.3.3
ar
e
192.168.20.0/24 1 Type2 1 202.101.34.3 10.0.3.3
e L Routing for NSSAs
or Destination Cost Type Tag NextHop AdvRouter
M 192.168.10.0/24 1 Type2 1 10.0.34.3 10.0.3.3
192.168.20.0/24 1 Type2 1 10.0.34.3 10.0.3.3
Only network segments 192.168.10.0/24 and 192.168.20.0/24 need to be added to

OSPF.
[R5]display ip routing-

-------------------------------------------------------------------------
Destination/Mas Proto Pre Cost Flags NextHop Interface
e n
/
o m
4. Configure Area 2 as an NSSA area to reduce the number of LSAs (including
e i .c
Type 3 and Type 5 LSAs) in Area 2.
aw
u
.h
Totally Stub and totally NSSA can achieve this.
g
NSSA achieves this task here, only the owner of the biggest Router-ID ABR can carry
n
out LSA-7 into LSA-5, but it can be modified by command then more than one ABR can
ni
execute this operation. Because R4’s Router-ID is bigger than R3, R4 carries out this
transform by default.
r
lea
R3 and R4 in Area 2 function as Autonomous System Boundary Routers (ASBRs).
//
Therefore, the task can be completed after Area 2 is configured as an NSSA area.
:
After completing this task, run the display ospf lsdb command to view the routing table
p
t
of R3. (The following table lists only key information, and as such some information is
t
:h
omitted.)
s
[R3]display ospf lsdb
r c e
ou
Link State Database
s
Re Area: 0.0.0.2
ing
Type LinkState ID AdvRouter Age Len Sequence Metric
arn
Router 10.0.3.3 10.0.3.3 162 36 80000005 1
L e Router 10.0.4.4 10.0.4.4 159 36 80000005 1
r e Network 10.0.34.4 10.0.4.4 159 32 80000002 0
o
M Sum-Net
Sum-Net
0.0.0.0
0.0.0.0
10.0.3.3
10.0.4.4
233
215
28
28
80000001
80000001
1
NSSA 0.0.0.0 10.0.3.3 233 36 80000001 1
NSSA 192.168.10.0 10.0.3.3 233 36 80000001 1
NSSA 192.168.20.0 10.0.3.3 233 36 80000001 1
NSSA 0.0.0.0 10.0.4.4 215 36 80000001 1

NSSA 192.168.10.0 10.0.4.4 216 36 80000001 1
NSSA 192.168.20.0 10.0.4.4 216 36 80000001 1
5. Perform the configurations only on R3 to ensure that R5 accesses network

segment 192.168.10.0/24 through R1 and accesses network segment
192.168.20.0/24 through R2.
OSPF imports external routes with Type-2 format by default and they keep metric 1 in
e n
the whole process, but the type and metric can be changed. Type-1 is higher than Type-2.
/
m
OSPF needs to choice the nearest path to arrive the ASBR as next-hop by using LSA-4 when
receive many same external routes.
Based on the configuration result in the default situation and the requirement for the
.c o
configuration only on R3, adjust costs of default routes on R3 to perform the task.
e i
w
After completing this task, run the display ip routing-table & display ospf routing
command to view the routing table of R5. (The following table lists only key information,
and as such some information is omitted.)
u a
[R5]display ip routing-
g .h
ni n
r
lea
-------------------------------------------------------------------------

: //
Destinations : 27
t t
Routes : 28 p
Destination/Mas Proto Pre
s
Cost
:hFlags NextHop Interface
192.168.10.0/24 O_ASE
r c e
150 1 D 10.0.15.1 GigabitEthernet0/0/0
192.168.20.0/24
s
O_ASE
ou 150 1 D 10.0.25.2 GigabitEthernet0/0/1
Re
i n g
r n OSPF Process 1 with Router ID 10.0.5.5
e a
eL
Routing Tables
or
Routing for Network
M Destination
10.0.5.5/32
Cost
0
Type
Stub
NextHop
10.0.5.5
AdvRouter
10.0.5.5
Area
0.0.0.1
10.0.15.0/24 1 Transit 10.0.15.5 10.0.5.5 0.0.0.1
10.0.25.0/24 1 Transit 10.0.25.5 10.0.5.5 0.0.0.1
10.0.1.1/32 1 Inter-area 10.0.15.1 10.0.1.1 0.0.0.1
10.0.2.2/32 1 Inter-area 10.0.25.2 10.0.2.2 0.0.0.1

10.0.3.3/32 2 Inter-area 10.0.15.1 10.0.1.1 0.0.0.1
10.0.4.4/32 1563 Inter-area 10.0.25.2 10.0.2.2 0.0.0.1
Routing for ASEs
192.168.10.0/24 1 Type2 1 10.0.15.1 10.0.3.3
e n
/
192.168.20.0/24 1 Type2 1 10.0.25.2 10.0.4.4
Total Nets: 9
o m
Intra Area: 3 Inter Area: 4 ASE: 2 NSSA: 0
e i .c
aw
u
.h
<R5>tracert -a 172.16.10.1 192.168.10.1
traceroute to
n g
192.168.10.1(192.168.10.1), max hops: 30 ,packet length: 40,press
i
CTRL_C to break
r n
1 10.0.15.1 50 ms 10 ms 50 ms
// lea
p :
t
2 10.0.13.3 50 ms 60 ms 90 ms
t
:h
3 10.0.36.6 140 ms 70 ms 120 ms
e s
r c
ou
<R5>tracert -a 172.16.10.1 192.168.20.1
traceroute to
es
R
g
CTRL_C to break
n i n
1 10.0.25.2 20 ms 20 ms 40 ms
ar
e
2 10.0.24.4 60 ms 80 ms 70 ms
e L 3 10.0.46.6 120 ms 110 ms 90 ms
or
M 6. Eliminate existing suboptimal paths on the OSPF network.
R2 and R4 are connected through a serial link which bandwidth is much smaller than
that of an Ethernet link. Test loopback 0 as an example so that routes mapping network
segments where loopback 0 interfaces of other devices reside are optimal.
R3’s Loopback0 and R4’s Loopback0 all stay on Area 0 and inter route better than intra
route, so R4’s Loopback0 wants to access R3’s Loopback0 must be transferred by R2. Here
must set up a virtual link to connect R3 and R4 and GRE tunnel can be used to finish them
with suitable cost.
routing table of R5 and R3. (The following table lists only key information, and as such some
[R5]display ip routing-table protocol ospf
-------------------------------------------------------------------------
Public routing table : OSPF
e n
/
OSPF routing table status : <Active>
o m
e i .c
10.0.1.1/32 OSPF 10 1 D 10.0.15.1
w
GigabitEthernet0/0/0
a
u
.h
10.0.3.3/32 OSPF 10 2 D 10.0.15.1

n g
i
10.0.4.4/32 OSPF 10 3 D 10.0.15.1
r nGigabitEthernet0/0/0
// lea
p :
t
<R3>tracert -a 10.0.3.3 10.0.4.4
t
:h
traceroute to 10.0.4.4(10.0.4.4), max hops: 30 ,packet length: 40,press CTRL_C to
break
e s
r c
ou
1 202.101.34.4 20 ms 50 ms 40 ms
es
R
g
<R3>display ip routing-table
n i n
ar
e
e L 10.0.1.1/32 OSPF 10 1 D 10.0.13.1 GigabitEthernet0/0/0
or 10.0.2.2/32 OSPF 10 2 D 10.0.13.1 GigabitEthernet0/0/0
M 10.0.3.3/32 Direct 0 0 D 127.0.0.1 LoopBack0
10.0.4.4/32 OSPF 10 1 D 202.101.34.4 Tunnel0/0/0
7. Improve robustness of the OSPF network to ensure that the physical link
between R1 and R2 is stable.
OSPF rules backbone area can’t be divided, Area 0 will be divided into two isolated
areas when the physical link between R1 and R2 has a breakdown.
Virtual-link is a virtual link used to fix a divided backbone area to keep it complete and
resolve discontinuous area; it also can be used as a backup link.
Analyze the result of the physical link disconnection between R1 and R2. Perform OSPF
configurations to improve network robustness based on the analysis result.
After completing this task, run the display ospf vlink command to view the OSPF vlink
of R1. (The following table lists only key information, and as such some information is
omitted.)
<R1>display ospf vlink
e n
/
m
Virtual Links
.c o
Virtual-link Neighbor-id -> 10.0.2.2, Neighbor-State: Full
e i
aw
Interface: 10.0.15.1 (GigabitEthernet0/0/2)
u
Cost: 2 State: P-2-P Type: Virtual
g .h
Transit Area: 0.0.0.1
ni n
r
lea
Timers: Hello 10 , Dead 40 , Retransmit 5 , Transmit Delay 1
: //
8.
t p
Optimize the OSPF routing table on R5, reduce the number of LSAs to
t
maintain, and summarize the two network segments on R5.
s :h
OSPF and ISIS are all link-state protocols so they transfer route by LSA and LSP and
c e
the real route information can’t see. But OSPF transfers real routes in flooding LSA-3,
r
LSA-5 and LSA-7. R1 and R2 all need to filter LSA-3 with filter-policy in area 1.
ou
Know differences between route filtering and LSA filtering. Run proper commands to
perform the task.
es
R
i n g
n
[R5]display ip routing-table protocol ospf
ar
e
e L -------------------------------------------------------------------------
or Public routing table : OSPF
M Destinations : 6 Routes : 6
OSPF routing table status : <Active>

e n
/
OSPF routing table status : <Inactive>
o m
9. Adjust OSPF timers based on the status of the link between R2 and R4.
e i .c
Understand rules for setting up OSPF neighbor relationships and adjust OSPF timers
aw
u
.h
based on the actual situation.
Serial link is a low-speed line, OSPF keep the default Hello and Dead interval as 10s
and 40s by default.
i n g
n
After completing this task, run the display ospf interface all command to view the
r
Hello interval of R2. (The following table lists only key information, and as such some
lea
//
<R2>display ospf interface all
p :
t
t
Interfaces
s :h
Area: 0.0.0.0
c e
(MPLS TE not enabled)
r
ou
Interface: 10.0.24.2 (Serial0/0/1) --> 10.0.24.4
es
R
Cost: 1562 State: P-2-P Type: P2P MTU: 1500
ing
Timers: Hello 60 , Dead 240 , Poll 120 , Retransmit 5 , Transmit Delay 1
arn
10. Configure cipher text authentication in OSPF areas to improve security of
L e
the OSPF network.
r e Configure cipher text authentication in the three OSPF areas and set the key to huawei.
o After completing this task, run the display ospf peer GigabitEthernet 0/0/1 command
M
to view the authentication of R2. (The following table lists only key information, and as such
some information is omitted.)
<R2>display ospf peer GigabitEthernet 0/0/1
Neighbors
Area 0.0.0.0 interface 10.0.12.2(GigabitEthernet0/0/1)'s neighbors
Router ID: 10.0.1.1 Address: 10.0.12.1

State: Full Mode:Nbr is Slave Priority: 1
DR: 10.0.12.2 BDR: 10.0.12.1 MTU: 0
Dead timer due in 37 sec
Retrans timer interval: 5
Neighbor is up for 00:14:13
e n
/
Authentication Sequence: [ 95]
o m
.c
Questions
e i
After requirement 6 is met, is requirement 5 still met? If not, analyze the reason and
work out a solution.
aw
u
When request 6 is met, R5 will refer to LSA-4 to choose the best route to ASBR-R4.
.h
Now, we can compare the OSPF routing-table before and after creating the tunnel0/0/0.
g
After completing this task, run the display ospf routing command to view the OSPF
i n
routing of R5. (The following table lists only key information, and as such some information
is omitted.)
n
r
lea
Tunnel unestablished：
: //
t
t p
Routing Tables
s :h
Routing for Network
r c e
Destination
s
Cost
ou Type NextHop AdvRouter Area
10.0.4.4/32
Re 1563 Inter-area 10.0.25.2 10.0.2.2 0.0.0.1
n g
Routing for ASEs
i
r n
e a
L
192.168.10.0/24 1 Type2 1 10.0.15.1 10.0.3.3
r e 192.168.20.0/24 1 Type2 1 10.0.25.2 10.0.4.4
o
M Tunnel established：
Routing Tables
Routing for Network

Destination Cost Type NextHop AdvRouter Area
10.0.4.4/32 3 Inter-area 10.0.15.1 10.0.1.1 0.0.0.1
Routing for ASEs
192.168.10.0/24 1 Type2 1 10.0.15.1 10.0.3.3
e n
/
192.168.20.0/24 1 Type2 1 10.0.15.1 10.0.4.4
Path can be chosen by setting policy-based-route on R5 and modifying output interface
o m
.c
or next hop.
Configuration List
e i
aw
u
#
g .h
ni n
r
sysname R1
lea
#
: //
p
acl number 2000
t t
:h
e s
r c
ou
s
e
R
#
i n g
r n
e a
eL
ip address 10.0.12.1 255.255.255.0
or #
M interface GigabitEthernet0/0/1
ip address 10.0.13.1 255.255.255.0
ip address 10.0.15.1 255.255.255.0

interface LoopBack0
ip address 10.0.1.1 255.255.255.255
ospf 1 router-id 10.0.1.1
area 0.0.0.0
e n
/
authentication-mode md5 1 plain huawei
network 10.0.1.1 0.0.0.0
o m
network 10.0.12.1 0.0.0.0
e i .c
network 10.0.13.1 0.0.0.0
aw
u
.h
area 0.0.0.1
i n g
filter route-policy R1 import
r n
network 10.0.15.1 0.0.0.0
// lea
p :
t
vlink-peer 10.0.2.2 md5 1 plain huawei
t
:h
#
route-policy R1 deny node 10

e s
r c
ou
if-match acl 2000
#
es
R
g
route-policy R1 permit node 20
#
n i n
ar
e
return
e L
or <R2>display current-configuration
M #
sysname R2
acl number 2000

interface Serial1/0/0
e n
/
link-protocol ppp
ip address 10.0.24.2 255.255.255.0
o m
ospf timer hello 60
e i .c
#
aw
u
.h
ip address 10.0.12.2 255.255.255.0
i n g
#
r n
// lea
p :
t
ip address 10.0.25.2 255.255.255.0
t
:h
#
interface LoopBack0
e s
r c
ou
ip address 10.0.2.2 255.255.255.255
#
es
R
g
n i n
area 0.0.0.0
ar
e
e L network 10.0.2.2 0.0.0.0
or network 10.0.12.2 0.0.0.0
M network 10.0.24.2 0.0.0.0
area 0.0.0.1
filter route-policy R2 import
network 10.0.25.2 0.0.0.0
vlink-peer 10.0.1.1 md5 1 plain huawei

route-policy R2 deny node 10
if-match acl 2000
route-policy R2 permit node 20
e n
/
#
user-interface con 0
o m
authentication-mode password
e i .c
idle-timeout 0 0
aw
u
.h
user-interface vty 0 4
user-interface vty 16 20
i n g
#
r n
return
// lea
p :
t t
:h
#
e s
r c
ou
sysname R3
#
es
R
g
acl number 2000
n i n
ar
e
acl number 2001
e L rule 5 permit source 192.168.20.0 0.0.0.255
or #
ip address 10.0.13.3 255.255.255.0
ip address 10.0.34.3 255.255.255.0

ip address 10.0.36.3 255.255.255.0
interface LoopBack0
ip address 10.0.3.3 255.255.255.255
e n
/
#
interface Tunnel0/0/0
o m
ip address 202.101.34.3 255.255.255.0
e i .c
tunnel-protocol gre
aw
u
.h
source 10.0.34.3
destination 10.0.34.4
i n g
ospf cost 1
r n
ospf network-type broadcast
// lea
p :
t
#
t
:h
e s
import-route rip 1 route-policy R2O
r c
ou
area 0.0.0.0
es
R
g
network 10.0.3.3 0.0.0.0
n i n
network 10.0.13.3 0.0.0.0
ar
e
network 202.101.34.3 0.0.0.0
e L area 0.0.0.2
or authentication-mode md5 1 plain huawei
M network 10.0.34.3 0.0.0.0
nssa no-summary
rip 1
version 2
network 10.0.0.0

import-route ospf 1
route-policy R2O permit node 10
if-match acl 2000
e n
/
if-match acl 2001
o m
apply cost 50
e i .c
#
aw
u
.h
return
i n g
r n
#
// lea
p :
t
sysname R4
t
:h
#
acl number 2000

e s
r c
ou
es
R
g
#
n i n
ar
e
link-protocol ppp
e L ip address 10.0.24.4 255.255.255.0
or ospf timer hello 60
M #
ip address 10.0.34.4 255.255.255.0
ip address 10.0.46.4 255.255.255.0

interface LoopBack0
ip address 10.0.4.4 255.255.255.255
e n
/
ip address 202.101.34.4 255.255.255.0
tunnel-protocol gre
o m
source 10.0.34.4
e i .c
aw
u
.h
ospf cost 1
ospf network-type broadcast
i n g
#
r n
// lea
p :
t
import-route rip 1 route-policy R2O
t
:h
area 0.0.0.0
e s
r c
ou
network 10.0.4.4 0.0.0.0
es
network 10.0.24.4 0.0.0.0
R
g
network 202.101.34.4 0.0.0.0
n i n
area 0.0.0.2
ar
e
e L network 10.0.34.4 0.0.0.0
or nssa no-summary
M #
rip 1
version 2
network 10.0.0.0
import-route ospf 1

if-match acl 2000
return
e n
/
o m
sysname R5
e i .c
#
aw
u
.h
ip local policy-based-route R5
#acl number 2000
i n g
r n
// lea
p :
t
#
t
:h
acl number 3001
e s
rule 5 permit ip source 172.16.0.0 0.0.255.255 destination 192.168.20.0 0.0.0.2 55
r c
ou
#
es
R
g
ip address 10.0.15.5 255.255.255.0
#
n i n
ar
e
e L ip address 10.0.25.5 255.255.255.0
or #
ip address 10.0.5.5 255.255.255.255
interface LoopBack1
ip address 172.16.10.1 255.255.255.0

interface LoopBack2
ip address 172.16.20.1 255.255.255.0
asbr-summary 172.16.0.0 255.255.0.0
e n
/
import-route direct route-policy D2O
area 0.0.0.1
o m
e i .c
network 10.0.5.5 0.0.0.0
aw
u
.h
network 10.0.15.5 0.0.0.0
network 10.0.25.5 0.0.0.0
i n g
#
r n
route-policy D2O permit node 10
// lea
p :
t
if-match acl 2000
t
:h
#
e s
policy-based-route R5 permit node 10
r c
ou
if-match acl 3001
es
apply ip-address next-hop 10.0.25.2
R
g
policy-based-route R5 permit node 20
#
n i n
ar
e
return
e L
M #
sysname R6
ip address 10.0.36.6 255.255.255.0

ip address 10.0.46.6 255.255.255.0
interface LoopBack0
ip address 10.0.6.6 255.255.255.255
e n
/
#
interface LoopBack1
o m
ip address 192.168.10.1 255.255.255.0
e i .c
#
aw
u
.h
interface LoopBack2
ip address 192.168.20.1 255.255.255.0
i n g
#
r n
rip 1
// lea
p :
t
version 2
t
:h
network 10.0.0.0
network 192.168.10.0
e s
r c
ou
network 192.168.20.0
#
es
R
g
return
n i n
ar
Le Chapter 3 IS-IS Hands-on Exercise Guide
r e
Overview
o
M Intermediate System to Intermediate System (IS-IS) is a dynamic routing protocol
initially designed by the International Organization for Standardization (ISO) for its
Connectionless Network Protocol (CLNP).
To support IP routing, the Internet Engineering Task Force (IETF) extended and
modified IS-IS in RFC 1195. This modification enables IS-IS to apply to TCP/IP and OSI
environments. This version of IS-IS is called Integrated IS-IS or Dual IS-IS.
IS-IS is an Interior Gateway Protocol (IGP) that runs within an autonomous system (AS).
IS-IS is a link state protocol and uses the shortest path first (SPF) algorithm to calculate
routes. It is similar to OSPF in many aspects.
IS-IS uses a two-level hierarchy in a routing domain to support large-scale routing
networks. A large routing domain is divided into one or more areas. Level-1 routers manage
intra-area routes. Level-2 routers manage inter-area routes.
The topology of an IS-IS network is similar to the multi-area topology of an OSPF

network. Generally, all devices in the backbone area are Level-2 routers. Non-backbone areas
contain Level-1 routers and connect to the backbone area through Level-1-2 routers. The
backbone area in IS-IS is not a fixed area, that is, the area ID varies.
The networking is one of the differences between IS-IS and OSPF. In OSPF, inter-area
routes must be forwarded through the backbone area, and only routers in the same area use
the SPF algorithm. In IS-IS, both Level-1 and Level-2 routes are calculated using the SPF
algorithm to generate the shortest path tree (SPT).
Objectives
e n
/
m
o
 Configure IS-IS.
.c
 Use IS-IS in different network environments.


Change the IS-IS cost.
e i
w
Configure IS-IS authentication modes.
a
 Configure IS-IS route aggregation.
 Configure route leaking in different areas.
u
.h
 Configure a router to advertise default routes.
Tasks
i n g
r n
lea
//
:
(1) Add R1 to area 49.0001, add R2, R3, R4, and R5 to area 49.0002, and add R6 to area
(2)
t p
49.0006. Set the system ID of each router to 0000.0000.000X.
t
Configure IS-IS on interfaces according to the topology. Run IS-IS on E1/0/0 of R6 and
:h
disable E1/0/0 from sending any IS-IS packets to its directly connected network segment.
s
Enable routers in the IS-IS area to learn addresses of the network segment directly connected
(3)
to E1/0/0.
r c e
Configure R1 as a Level-2 router, R2 and R3 as Level-1-2 routers, R4 and R5 as Level-1
ou
routers, and interfaces on R6 as Level-2 interfaces.
s
(4) Run proper commands to configure the names (such as R1, R2, and R3) of the routers
(5)
Re
because routers are difficult to maintain when identified using only system IDs.
Ensure that no DIS exists between R4 and R5, and establish a neighbor relationship between
(6)
them.
i n g
Configure IS-IS to automatically calculate the cost.
(7)
r n
Use a proper authentication mode to authenticate LSPs and SNPs in area 49.0002. Set the
a
authentication password to HUAWEI and authentication type to MD5.
(8)
L e
Disable R4 and R5 from sending Hello packets with the padding field to each other to
improve bandwidth usage between them.
r e(9) Only configure R4 to import directly connected network segment 4.0.X.0/24 to the IS-IS area
o and do not summary, configure R1 to import directly connected network segment 1.0.X.0/24
M
to the IS-IS area, and perform optimal aggregation. Use as few commands as possible.
(10) Disable R2 and R3 from advertising 4.0.0.0/24 and 4.0.2.0/24 to area 49.0001, configure
ACLs and disable routing policies on R2 and R3. Ensure that R4 and R5 can learn the
aggregated network segment 1.0.X.0/24, and disable routing policies on R4 and R5.
(11) Disable R6 from adding aggregated routes generated by R1 to the routing table. Enable R6 to
advertise a default route when routing information for network segment 1.0.X.0/24 exists on
R1.

Topology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
IP Address Table
// lea
p :
t
Default
t
Device Interface IP Address Subnet Mask
:h
Gateway
es
S2/0/0.2 12.1.1.1 255.255.255.0 N/A
r c
S2/0/0.3 13.1.1.1 255.255.255.0 N/A
ou
R1
G0/0/0 16.1.1.1 255.255.255.0 N/A
es Loopback 0 10.1.1.1 255.255.255.255 N/A
R S2/0/0.2 12.1.1.2 255.255.255.0 N/A

R2
i n g S2/0/1 24.1.1.2 255.255.255.0 N/A
r n Loopback 0 10.2.2.2 255.255.255.255 N/A
e a S2/0/0.3 13.1.1.3 255.255.255.0 N/A
eL
R3 S2/0/1 35.1.1.3 255.255.255.0 N/A
or Loopback 0 10.3.3.3 255.255.255.255 N/A
M R4
S2/0/1
E1/0/0
24.1.1.4
45.1.1.4
255.255.255.0
255.255.255.0
N/A
N/A
Loopback 0 10.4.4.4 255.255.255.255 N/A
S2/0/1 35.1.1.5 255.255.255.0 N/A
R5 E1/0/0 45.1.1.5 255.255.255.255 N/A
Loopback 0 10.5.5.5 255.255.255.255 N/A
R6 G0/0/0 16.1.1.6 255.255.255.0 N/A

E1/0/0 6.0.0.1 255.255.255.0 N/A

Loopback 0 10.6.6.6 255.255.255.255 N/A
1. Add R1 to area 49.0001, add R2, R3, R4, and R5 to area 49.0002, and add R6
to area 49.0006. Set the system ID of each router to 0000.0000.000X.
e n
Perform basic configuration according to the "IP Address Table", and then run the
/
display isis 1 brief command to view brief IS-IS information. The following uses the display
o m
.c
of R1 as an example. The table shows only key information, while other information is
i
omitted.
[R1]display isis 1 brief
we
ISIS Protocol Information for ISIS(1)
u a
-------------------------------------
g .h
SystemId: 0000.0000.0001 System Level: L12
ni n
r
lea
Area-Authentication-mode: NULL
Domain-Authentication-mode: NULL
: //
Ipv6 is not enabled
t t p
ISIS is in invalid restart status
s :h
r c e
ISIS is in protocol hot standby state: Real-Time Backup
ou
During the configuration, view and understand the requirements to avoid incorrect
s
e
configuration.
of R6 and g
R
2. Configure IS-IS on interfaces according to the topology. Run IS-IS on E1/0/0
i n disable E1/0/0 from sending any IS-IS packets to its directly
rn of the network segment directly connected to E1/0/0.

connected network segment. Enable routers in the IS-IS area to learn
a
addresses
e
e L After completing this task, run the display isis interface command to view interfaces
or
that have IS-IS enabled, run the display isis peer command to view IS-IS neighbors, and run
the display ip routing-table protocol isis command to view the IS-IS routing table. The
M following uses the display of R1 as an example. The table shows only key information, while
other information is omitted.
[R1]display isis interface
Interface information for ISIS(1)
Interface Id IPV4.State IPV6.State MTU Type DIS
GE0/0/0 001 Up Down 1497 L1/L2 No/No
Loop0 001 Up Down 1500 L1/L2 --

S2/0/0.2 002 Up Down 1500 L1/L2 --
S2/0/0.3 003 Up Down 1500 L1/L2 –
[R1]display isis peer
Peer information for ISIS(1)
e n
/
System Id Interface Circuit Id State HoldTime Type PRI
-------------------------------------------------------------------------------
o m
0000.0000.0006 GE0/0/0 0000.0000.0006.01 Up 8s
i
L2(L1L2) 64
e .c
0000.0000.0002 S2/0/0.2 0000000002 Up 22s L2
aw --
u
.h
0000.0000.0003 S2/0/0.3 0000000001 Up 23s L2 --
i n g
[R1]display ip routing-table protocol isis
r n
// lea
Flags NextHop Interface
p :
t
6.0.0.0/24 ISIS-L2 15 74 D 16.1.1.6 GigabitEthernet0/0/0
t
:h
10.2.2.2/32 ISIS-L2 15 10 D 12.1.1.2 Serial2/0/0.2
10.3.3.3/32
e
ISIS-L2 15s 10 D 13.1.1.3 Serial2/0/0.3
r c
ou
10.4.4.4/32 ISIS-L2 15 20 D 12.1.1.2 Serial2/0/0.2
10.5.5.5/32
es ISIS-L2 15 20 D 13.1.1.3 Serial2/0/0.3
R
g
n i n
24.1.1.0/24 ISIS-L2 15 20 D 12.1.1.2 Serial2/0/0.2
ar
e
35.1.1.0/24 ISIS-L2 15 20 D 13.1.1.3 Serial2/0/0.3
e L 45.1.1.0/24 ISIS-L2 15 30 D 13.1.1.3 Serial2/0/0.3
or ISIS-L2 15 30 D 12.1.1.2 Serial2/0/0.2
M When IS-IS runs in a frame relay (FR) network, you need to configure FR interfaces as
sub-interfaces that work in P2P mode, otherwise, IS-IS neighbor relationships cannot be
established even if the network type is changed.
IS-IS only support broadcast and P2P network type by default.
In addition, you should understand IS-IS features when configuring IS-IS on E1/0/0 of
R6. IS-IS can disable a certain interface to receive and send data, so the build of the IS-IS
neighbor and transfer of route information can be controlled. You can also run the following
command to verify the results:
display isis lsdb
display isis route
display isis peer
3. Configure R1 as a Level-2 router, R2 and R3 as Level-1-2 routers, R4 and R5

as Level-1 routers, and interfaces on R6 as Level-2 interfaces.
After completing this task, run the display isis brief command to view the level at
which a device works. The following uses the display of R1 as an example. The table shows
only key information, while other information is omitted.
[R1]display isis 1 brief
ISIS Protocol Information for ISIS(1)
e n
-------------------------------------
/
SystemId: 0000.0000.0001 System Level: L2
o m
Area-Authentication-mode: NULL
e i .c
Domain-Authentication-mode: NULL
aw
u
Ipv6 is not enabled
g .h
ISIS is in invalid restart status
ni n
r
lea
ISIS is in protocol hot standby state: Real-Time Backup
//
According to the requirement, interfaces on R6 should be configured as Level-2
:
interfaces. You cannot run the is-level command to configure R6 as a Level-2 router.
p
t
display isis peer
t
h the names (such as R1, R2, and R3) of
:
s difficult to maintain when identified using
4. Run proper commands to configure
the routers because routers e
r c are
u
only system IDs.
s o
e
After completing this task, run the display isis name-table command to view the
R
mapping between the host name and system ID of local and remote IS-IS routers. The
g
following uses the display of R1 as an example. The table shows only key information, while
n
i
rn
[R1]display isis name-table
e a Name table information for ISIS(1)
e L
or
System ID Hostname Type
M
-------------------------------------------------------------------------------
0000.0000.0001 R1 DYNAMIC
0000.0000.0002 R2 DYNAMIC
0000.0000.0003 R3 DYNAMIC
0000.0000.0006 R6 DYNAMIC
The host name is delivered to each router running IS-IS through LSPs. Note that the
length of a specified dynamic host name is limited within 64 bits
IS-IS can name the remote device by the command “is-name 0001.0001.0001 R1”, so
that it is easy to check the LSDB.

display isis peerdisplay isis lsdb
5. Ensure that no DIS exists between R4 and R5, and establish a neighbor
relationship between them.
After completing this task, view the network type of connected interfaces on R4 and R5.
The following uses the display of R5 as an example. The table shows only key information,
e n
[R5]display isis interface Ethernet 1/0/0 verbose
/
o m
---------------------------------
e i .c
Interface Id IPV4.State IPV6.State MTU Type
aw DIS
u
Eth1/0/0 003 Up Down
.h
1497 L1/L2 --
g
Circuit MT State : Standard
ni n
r
lea
Circuit Parameters : p2p
Description
//
: HUAWEI, AR Series, Ethernet1/0/0 Interface
:
SNPA Address
t t
: 00e0-fc04-31d5
p
IP Address
:h
: 45.1.1.5
s
c e
In a P2P network, a three-way handshake is forcibly performed when an IS-IS neighbor
r
relationship is established. The three-way handshake ensures that the neighbor relationship is
ou
established successfully and prevents unidirectional communication.
es
ISIS provides default support for Ethernet and P2P, but here we need to adjust it to
reliable 3-way handshake P2P network.
R
i n g
display isis peer
display isis interface
r n
6.
a
Configure IS-IS to automatically calculate the cost.
e
eL
After completing this task, run the display isis cost interface command to view the cost
or
of each interface. The following uses the display of R1 as an example. The table shows only
key information, while other information is omitted.
M [R1]display isis cost interface GigabitEthernet 0/0/0
Interface: GE0/0/0
Level-2 interface cost
Topology base(0):
Link effective cost: 1(A) enabled by auto cost
IP prefix effective cost:

16.1.1.0/24 cost: 1 enabled by auto cost
Flags: R-Relative cost A-Absolute cost
By default, the IS-IS link cost is 10.

To enable automatic link cost calculation, the cost style must be Wide or
Wide-Compatible.
display isis interface GigabitEthernet 0/0/0 verbose | include cost
e n
/
7. Use a proper authentication mode to authenticate LSPs and SNPs in area
49.0002. Set the authentication password to HUAWEI and authentication
type to MD5.
o m
e i
After completing this task, run the display isis error command to verify whether the .c
w
configuration succeeds. The following uses the display of R5 as an example. The table shows
only key information, while other information is omitted.
u a
.h
[R5]display isis error | include Authentication
Statistics of error packets for ISIS(1)
i n g
---------------------------------------
r n
LSP packet errors:
// lea
Bad Authentication : 0
p :
Bad Auth Count : 0
t t
:h
Hello packet errors:
Mismatched Max Area Addr: 0

e s Bad Authentication : 0
r c
ou
During the configuration, note that there are three IS-IS authentication modes that have
different functions.
s
Default packet of ISIS has 3 formats: IHH、SNP、LSP, among which SNP includes
e
R
CSNP and PSNP of Level-1 and Level-2. Domain authentication is used to encrypt Level-2
g
packet ,area authentication is used to encrypt Level-1 packet and interface authentication is
n
used to encrypt Hello packet.
n i
a r display isis brief
L e R4 and R5 from sending Hello packets with the padding field to each
8. Disable
e
or
other to improve bandwidth usage between them.
M
Default Hello packet carries huge number of useless padding field, as shown below:

e n
/
o m
e i .c
aw
u
.h
After completing this task, view detailed information about E1/0/0 on R4 and R5. The

i n g
following uses the display of R5 as an example. The table shows only key information, while
[R5]display isis interface Ethernet 1/0/0 verbose

r n
//
lea
p :
t
---------------------------------
t
:h
Interface Id IPV4.State IPV6.State MTU Type DIS
Eth1/0/0 003
e s
Up Down 1497 L1/L2 --
r c
ou
Circuit MT State : Standard
Circuit Parameters
es : small-hello p2p
R
g
Description : HUAWEI, AR Series, Ethernet1/0/0 Interface
n i n
SNPA Address : 00e0-fc04-31d5
ar
e
IP Address : 45.1.1.5
eL
Different types of networks process Hello packets in different ways.
or 9. Only configure R4 to import directly connected network segment 4.0.X.0/24
M to the IS-IS area and do not summary, configure R1 to import directly

connected network segment 1.0.X.0/24 to the IS-IS area, and perform
optimal aggregation. Use as few commands as possible.
After completing this task, run the display ip routing-table protocol isis command to
view IS-IS routes. The following uses the display of R6 as an example. The table shows only
[R6]display ip routing-table protocol isis -

During the configuration, note that only required network segments can be imported to
e n
the IS-IS Area. Do not import irrelevant network segments. During IS-IS route aggregation, a
/
route to the Null0 interface is not generated by default.
o m
10. Disable R2 and R3 from advertising 4.0.0.0/24 and 4.0.2.0/24 to area 49.0001,
configure ACLs and disable routing policies on R2 and R3. Ensure that R4
e i .c
and R5 can learn the aggregated network segment 1.0.X.0/24, and disable
aw
routing policies on R4 and R5.
u
g .h
i n
view IS-IS routes. The following table shows information of R1 and R4. Only key
n
r
information is displayed, while other information is omitted.
lea

: //
4.0.1.0/24 ISIS-L2 15 976

t t p
D 12.1.1.2 Serial2/0/0.2
:h
es
4.0.3.0/24 ISIS-L2 15 976 D 12.1.1.2 Serial2/0/0.2
6.0.0.0/24
r c
ISIS-L2 15 11 D 16.1.1.6 GigabitEthernet0/0/0
10.2.2.2/32
s ou
ISIS-L2 15 488 D 12.1.1.2 Serial2/0/0.2
10.3.3.3/32
Re ISIS-L2 15 488 D 13.1.1.3 Serial2/0/0.3
i n g
10.4.4.4/32 ISIS-L2 15 976 D 12.1.1.2 Serial2/0/0.2
r n
a
10.5.5.5/32 ISIS-L2 15 976 D 13.1.1.3 Serial2/0/0.3
e
eL
or
24.1.1.0/24 ISIS-L2 15 976 D 12.1.1.2 Serial2/0/0.2
M 35.1.1.0/24
45.1.1.0/24
ISIS-L2 15
ISIS-L2 15
976
986
D
D
13.1.1.3
12.1.1.2
Serial2/0/0.3
Serial2/0/0.2
ISIS-L2 15 986 D 13.1.1.3 Serial2/0/0.3

0.0.0.0/0 ISIS-L1 15 488 D 24.1.1.2 Serial2/0/1
1.0.0.0/22 ISIS-L1 15 976 D 24.1.1.2 Serial2/0/1
10.2.2.2/32 ISIS-L1 15 488 D 24.1.1.2 Serial2/0/1
10.3.3.3/32 ISIS-L1 15 498 D 45.1.1.5 Ethernet1/0/0
10.5.5.5/32 ISIS-L1 15 10 D 45.1.1.5 Ethernet1/0/0
e n
/
12.1.1.0/24 ISIS-L1 15 976 D 24.1.1.2 Serial2/0/1
13.1.1.0/24 ISIS-L1 15 986 D 45.1.1.5 Ethernet1/0/0
o m
35.1.1.0/24 ISIS-L1 15 498 D 45.1.1.5
i
Ethernet1/0/0
e .c
routes according to the requirement.
a w
This task requires bidirectional route leaking between Level-1 and Level-2 areas. Filter
h uto the routing

11. Disable R6 from adding aggregated routes generated by R1
g .
in
table. Enable R6 to advertise a default route when routing information for
n
network segment 1.0.X.0/24 exists on R1.
ar
e
// l
view IS-IS routes. The following uses the display of R6 as an example. The table shows only
:
t tp
: h
s
0.0.0.0/0
r c e
ISIS-L2 15 1 D 16.1.1.1 GigabitEthernet0/0/0
o
4.0.1.0/24u ISIS-L2 15 977 D 16.1.1.1 GigabitEthernet0/0/0
e s
R
i n g
a rn 10.2.2.2/32 ISIS-L2 15 489 D 16.1.1.1 GigabitEthernet0/0/0
L e 10.3.3.3/32 ISIS-L2 15 489 D 16.1.1.1 GigabitEthernet0/0/0
e
or
M 10.5.5.5/32
12.1.1.0/24
ISIS-L2 15
ISIS-L2 15
977
489
D
D
16.1.1.1
16.1.1.1

Questions
In requirement 1, if the interfaces are not FR sub-interfaces or the sub-interface type is

not P2MP, can IS-IS neighbor relationships be established?
Yes, IS-IS support P2P network type, but doesn’t support NBMA and P2MP network.
In requirement 2, why do R2 and R3 not use the default routes they advertise?
R4 and R5 will generate default route after receive the LSP-level-1 of ATT bit is set and
they will choose the nearest Level-1-2 router as next hop. R2 and R3 as Level-1-2 routers,
they will ignore this LSP.
In requirement 11, are corresponding LSPs filtered when route filtering is implemented
e n
on R6, and what are the considerations that should be taken for advertising default routes?
/
m
Because ISIS and OSPF are Link-state protocol, R6 can’t use filter-policy to filter LSP
o
in inbound direction. The filter-policy will effect in the process of LSP into routing-table, but
.c
can’t deny LSP into LSDB.
e i
When advertising routes under a certain condition, it is required detailed routes and the
summary route to avoid the unknown loop. When the edge device’s routing table contains the
aw
external route to meet route policy, R4 released a default route to ISIS domain, avoid due to
u
link failures and other reasons caused the equipment to do not exist already some important
.h
external routing, still advertise default route resulting in routing loop. The routing strategy
here does not affect the introduction of external ISIS routing.
i n g
Configuration List
r n
// lea
p :
#
t t
:h
sysname R1
e s
c
#
r
ou
acl number 2010
es
R
#
i n g
r
isis 1
n
e a
is-level level-2
e L
r
cost-style wide
o auto-cost enable
M network-entity 49.0001.0000.0000.0001.00
is-name R1
import-route direct route-policy SUMM
default-route-advertise route-policy OTHERROUTE
summary 1.0.0.0 255.255.252.0

link-protocol fr
undo fr inarp
e n
/
interface Serial2/0/0.2
fr dlci 102
o m
ip address 12.1.1.1 255.255.255.0
e i .c
fr map ip 12.1.1.2 102 broadcast
aw
u
.h
isis enable 1
i n g
r n
fr dlci 103
// lea
p :
t
ip address 13.1.1.1 255.255.255.0
t
:h
isis enable 1
e s
r c
ou
#
es
R
g
ip address 16.1.1.1 255.255.255.0
n i n
isis enable 1
ar
e
#
e L interface LoopBack0
or ip address 10.1.1.1 255.255.255.255
M isis enable 1
interface LoopBack10
ip address 1.0.0.1 255.255.255.0

ip address 1.0.1.1 255.255.255.0
ip address 1.0.2.1 255.255.255.0
e n
/
ip address 1.0.3.1 255.255.255.0
o m
#
e i .c
route-policy SUMM permit node 10
aw
u
.h
if-match ip-prefix SUMM
i n g
route-policy OTHERROUTE permit node 10
r n
if-match acl 2010
// lea
p :
t
#
t
:h
ip ip-prefix SUMM index 10 permit 1.0.0.0 22 greater-equal 24 less-equal 24
#
e s
r c
ou
return
es
R
g
#
n i n
ar
e
sysname R2
e L #
or acl number 2000
M rule 5 deny source 4.0.0.0 0.0.254.255
rule 10 permit
isis 1
cost-style wide
auto-cost enable

network-entity 49.0002.0000.0000.0002.00
is-name R2
import-route isis level-2 into level-1 filter-policy ip-prefix LEAKSUMM
import-route isis level-1 into level-2 filter-policy 2000
area-authentication-mode md5 plain HUAWEI
e n
/
#
o m
link-protocol fr
e i .c
undo fr inarp
aw
u
.h
#
i n g
fr dlci 201
r n
ip address 12.1.1.2 255.255.255.0
// lea
p :
t
t
:h
isis enable 1
#
e s
r c
ou
link-protocol ppp
es
R
g
ip address 24.1.1.2 255.255.255.0
n i n
isis enable 1
ar
e
#
e L interface LoopBack0
or ip address 10.2.2.2 255.255.255.255
M isis enable 1
ip ip-prefix LEAKSUMM index 10 permit 1.0.0.0 22
return

sysname R3
acl number 2000
e n
/
rule 5 deny source 4.0.0.0 0.0.254.255
rule 10 permit
o m
#
e i .c
isis 1
aw
u
.h
cost-style wide
auto-cost enable
i n g
network-entity 49.0002.0000.0000.0003.00
r n
is-name R3
// lea
p :
t
import-route isis level-2 into level-1 filter-policy ip-prefix LEAKSUMM
t
:h
import-route isis level-1 into level-2 filter-policy 2000
e s
r c
ou
#
es
R
g
link-protocol fr
n i n
undo fr inarp
ar
e
#
e L interface Serial2/0/0.3
or fr dlci 301
M ip address 13.1.1.3 255.255.255.0
isis enable 1
link-protocol ppp

ip address 35.1.1.3 255.255.255.0
isis enable 1
interface LoopBack0
ip address 10.3.3.3 255.255.255.255
e n
/
isis enable 1
o m
ip ip-prefix LEAKSUMM index 10 permit 1.0.0.0 22
e i .c
#
aw
u
.h
return
i n g
r n
#
// lea
p :
t
sysname R4
t
:h
#
isis 1
e s
r c
ou
is-level level-1
cost-style wide
es
R
g
auto-cost enable
n i n
network-entity 49.0002.0000.0000.0004.00
ar
e
is-name R4
e L import-route direct level-1 route-policy SUMM
or area-authentication-mode md5 plain HUAWEI
M #
ip address 45.1.1.4 255.255.255.0
isis enable 1
isis circuit-type p2p
isis small-hello

link-protocol ppp
ip address 24.1.1.4 255.255.255.0
isis enable 1
e n
/
#
interface LoopBack0
o m
ip address 10.4.4.4 255.255.255.255
e i .c
isis enable 1
aw
u
.h
#
i n g
ip address 4.0.0.1 255.255.255.0
r n
#
// lea
p :
t
t
:h
ip address 4.0.1.1 255.255.255.0
#
e s
r c
ou
es
ip address 4.0.2.1 255.255.255.0
R
g
#
n i n
ar
e
ip address 4.0.3.1 255.255.255.0
e L #
or route-policy SUMM permit node 10
M if-match ip-prefix SUMM
ip ip-prefix SUMM index 10 permit 4.0.0.0 22 greater-equal 24 less-equal 24
return

sysname R5
isis 1
e n
/
is-level level-1
cost-style wide
o m
auto-cost enable
e i .c
network-entity 49.0002.0000.0000.0005.00
aw
u
.h
is-name R5
i n g
summary 1.0.0.0 255.255.252.0
r n
#
// lea
p :
t
t
:h
ip address 45.1.1.5 255.255.255.0
isis enable 1
e s
r c
ou
isis circuit-type p2p
isis small-hello
es
R
g
#
n i n
ar
e
link-protocol ppp
e L ip address 35.1.1.5 255.255.255.0
or isis enable 1
M #
interface LoopBack0
ip address 10.5.5.5 255.255.255.255
isis enable 1
return

sysname R6
e n
/
isis 1
cost-style wide
o m
auto-cost enable
e i .c
network-entity 49.0006.0000.0000.0006.00
aw
u
.h
is-name R6
filter-policy ip-prefix FILTERR1SUMM import
i n g
#
r n
// lea
p :
t
ip address 6.0.0.1 255.255.255.0
t
:h
isis enable 1
isis silent
e s
r c
ou
#
es
R
g
ip address 16.1.1.6 255.255.255.0
n i n
isis enable 1
ar
e
isis circuit-level level-2
e L #
M ip address 10.6.6.6 255.255.255.255
isis enable 1
ip ip-prefix FILTERR1SUMM index 5 deny 1.0.0.0 22
ip ip-prefix FILTERR1SUMM index 10 permit 0.0.0.0 0 less-equal 32

return
Chapter 4 BGP Basics Hands-on Exercise Guide

Overview
n
The Border Gateway Protocol (BGP) is a dynamic routing protocol used between
Autonomous Systems (ASs). Three earlier BGP versions are BGP-1 defined in RFC 1105,
BGP-2 defined in RFC 1163, and BGP-3 defined in RFC 1267, and the currently used BGP / e
version is BGP-4 defined in RFC 4271. As an external routing protocol on the Internet,
o m
.c
BGP-4 is widely used among Internet Service Providers (ISPs).
e i
BGP is an EGP. Different from Interior Gateway Protocols (IGPs) such as Open Shortest
Path First (OSPF) and Routing Information Protocol (RIP), BGP controls route advertisement
aw
and selects optimal routes between ASs rather than discover or calculate routes. BGP uses the
u
Transport Control Protocol (TCP) with listening port 179 as the transport layer protocol. TCP
.h
ensures high reliability and efficiency when BGP advertises, and improves the capability to
g
manage, a large number of routes.
i n
BGP supports Classless Inter-Domain Routing (CIDR) and uses triggered incremental
n
updates, greatly reducing the bandwidth consumed by route propagation. Therefore, BGP can
r
lea
be used on the Internet to propagate a large amount of routing information. BGP routes carry
the AS-Path attribute to prevent routing loops between ASs.
//
BGP provides rich route attributes and uses these attributes to flexibly filter and control
routes.
p :
t t
BGP supports a variety of protocols, including IPv4, IPv6, multicast, and VPNv4, has
:h
good scalability, and applies to network development.
There are two types of BGP peer relationships: Internal BGP (IBGP) and External BGP
e s
(EBGP). BGP routers with the same AS number are IBGP peers, while BGP routers with
c
different AS numbers are EBGP peers. BGP peer relationships are established on TCP
r
ou
sessions and must be manually specified.
Objectives
es
R
g

 i n
Configure IBGP and EBGP peer relationships.
n
Change the origin and next hop and configure EBGP multi-hop.

arConfigure BGP authentication.
L

e Configure BGP route summarization.
Filter BGP routes.
r e  Modify the BGP Community attribute.
o
 Configure BGP suppression.
M Tasks
(1) Build the network according to the topology, establish an IBGP peer relationship between R1
and R2 through loopback interfaces, and deploy OSPF. Establish an IBGP peer relationship
between R3 and R4 through physical interfaces, establish an EBGP peer relationship between
R2 and R5 through loopback interfaces using static routes, and establish an EBGP peer
relationship between R1 and R3.
(2) Advertise or import the loopback interface of each device into BGP processes, and enable
loopback interfaces of all the devices to communicate with each other.
(3) Advertise service network segments of R4 and R5 into BGP, and enable these network
segments to communicate normally.
(4) Optimize BGP routing tables on all the devices so that devices only need to maintain routing
entries of service network segments and network segments where loopback interfaces reside.
(5) Summarize two service network segments 192.168.20.0/24 and 192.168.30.0/24, and suppress
the advertisement of specific routes of service network segment 192.168.30.0/24. The service
network segment 192.168.10.0/24 should be advertised.
(6) Summarize two service network segments 172.16.10.0/24 and 172.16.20.0/24 on R3, and
suppress the advertisement of all the specific routes.
n
(7) Observe communication between service network segments, and solve the sub-optimal route
problem on the network.
(8) Configure the Community attribute to prevent AS 200 from receiving the routes to service
/ e
network segment 192.168.20.0/24.
o m
.c
(9) Assume that service network segment 172.16.10.0/24 is unstable and often interrupted.
network.
e i
Perform the correct configuration to reduce the impact of such interruptions on the entire
(10) Configure authentication between EBGP peers to improve BGP network security.
aw
u
(11) Change the BGP Keepalive timer to 30 seconds and adjust the BGP Holdtime accordingly on
.h
R2.
Topology
i n g
r n
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M IP Address Table
Default
Gateway
G 0/0/0 10.0.12.1 255.255.255.0 N/A
R1 G 0/0/1 10.0.134.1 255.255.255.0 N/A
Loopback 0 10.0.1.1 255.255.255.255 N/A
R2 G 0/0/0 10.0.25.2 255.255.255.0 N/A

G 0/0/1 10.0.12.2 255.255.255.0 N/A

Loopback 0 10.0.2.2 255.255.255.255 N/A
G 0/0/1 10.0.134.3 255.255.255.0 N/A
R3
Loopback 0 10.0.3.3 255.255.255.255 N/A
G 0/0/1 10.0.134.4 255.255.255.0 N/A
R4
Loopback 0 10.0.4.4 255.255.255.255 N/A
G 0/0/0 10.0.25.5 255.255.255.0 N/A
e n
/
R5
Loopback 0 10.0.5.5 255.255.255.255 N/A
o m
e i .c
1. Build the network according to the topology, establish an IBGP peer
aw
u
relationship between R1 and R2 through loopback interfaces, and deploy
.h
OSPF. Establish an IBGP peer relationship between R3 and R4 through
i n g
physical interfaces, establish an EBGP peer relationship between R2 and R5
through loopback interfaces using static routes, and establish an EBGP peer
relationship between R1 and R3.
r n
// lea
Perform basic configuration according to the address table, and then check the
:
establishment of BGP peer relationships.
t t p
After completing this task, run the display bgp peer command to view the BGP peer
status. The following uses the display of R1 as an example. Only key information is
:h
displayed, while other information is omitted.
<R1>display bgp peer
e s
r c
BGP local router ID : 10.0.1.1
Local AS number : 100

s ou
Re
Total number of peers : 2 Peers in established state : 2
Peer
i n g V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
r n
e a 10.0.2.2 4 100 64 69 0 01:01:52 Established 1
eL
10.0.134.3 4 200 66 67 0 01:02:35 Established 2
or 2. Advertise the loopback interface of each device into BGP processes, and
M enable loopback interfaces of all the devices to communicate with each other.
Default BGP compares routers with IGP when advertising routers. To remind, BGP
doesn’t set the route as the best route since default route preference is 255 if there are same
routes.
Perform configuration to ensure that all of the devices have BGP routes to the loopback
interfaces of the devices.
After completing this task, run the display bgp routing-table command to view the
BGP routing table. The following uses the display of R1 as an example. Only key

<R1>display bgp routing-table
BGP Local router ID is 10.0.1.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
e n
/
Total Number of Routes: 14
Network NextHop MED LocPrf PrefVal Path/Ogn
o m
*> 10.0.1.1/32 0.0.0.0 0 0 i
e i .c
* i 10.0.2.2 1 100 0 ?
aw
u
.h
*> 10.0.2.2/32 0.0.0.0 1 0 ?
i 10.0.2.2 0 100
i
0
n g i
*> 10.0.3.3/32 10.0.134.3 0

r n 0 200i
*> 10.0.4.4/32 10.0.134.4
// lea 0 200i
p :
t
*>i 10.0.5.5/32 10.0.2.2 0 100 0 ?
t
hnormally.
s :
3. Advertise service network segments of R4 and R5 into BGP, and enable these
r c e
network segments to communicate
u
o
s
R e
[R5]display bgp routing-table
i n g
arn Status codes: * - valid, > - best, d - damped,
L e h - history, i - internal, s - suppressed, S - Stale
e
or Origin : i - IGP, e - EGP, ? - incomplete
M Total Number of Routes: 11
*> 172.16.10.0/24 10.0.2.2 0 100 200i
*> 172.16.20.0/24 10.0.2.2 0 100 200i
4. Optimize BGP routing tables on all the devices so that devices only need to
maintain routing entries of service network segments and network segments

where loopback interfaces reside.
e n
/
m

.c o
e i
w

u a
*> 10.0.1.1/32 0.0.0.0 0 0
g
i
.h
* i 10.0.2.2 1 100
ni
0 n ?
r
lea
*> 10.0.2.2/32 0.0.0.0 1 0 ?
i 10.0.2.2 0
: //
100 0 i
t t p
:h
*> 10.0.3.3/32 10.0.134.3 0 0 200i
es
*> 10.0.4.4/32 10.0.134.4 0 200i
*>i 10.0.5.5/32
r c
10.0.2.2 0 100 0 ?
*>
s
172.16.10.0/24
ou 10.0.134.4 0 200i
*>
Re
172.16.20.0/24 10.0.134.4 0 200i
*>i
i n g
192.168.10.0 10.0.2.2 0 100 0 300i
r n
a
*>i 192.168.20.0 10.0.2.2 0 100 0 300i
e
eL
*>i 192.168.30.0 10.0.2.2 0 100 0 300i
or 5. Summarize two service network segments 192.168.20.0/24 and

M 192.168.30.0/24, and suppress the advertisement of specific routes of service
network segment 192.168.30.0/24.The service network segment
192.168.10.0/24 should be advertised.
BGP can use aggregate to filter all the detailed routes which can be released via
suppress-policy. Origin-policy can be used to select and advertise summary route, all of
which can be implanted via aggregate command.
Understand BGP route summarization principles, and configure route summarization
using routing policies according to requirements.

e n
/
o m
.c
*>i 192.168.0.0/16 10.0.134.1 100 0

e i
100 300i
aw
u
*>i 192.168.10.0 10.0.134.1 100 0 100 300i
*>i 192.168.20.0 10.0.134.1
g
100 0
.h100 300i
i n
n routes.
ar
6. Summarize two service network segments 172.16.10.0/24 and 172.16.20.0/24
on R3, and suppress the advertisement of all the specific
l e
: //
tp
t
h
s :
c e
r
o u
e s
R
i n g Origin : i - IGP, e - EGP, ? - incomplete
arn
L e Network NextHop MED LocPrf PrefVal Path/Ogn
e
or 7.
*> 172.16.0.0 10.0.2.2 0 100 200i
M Observe communication between service network segments, and solve the

sub-optimal route problem on the network.
Under a MA and FR environment, BGP will report the real source of the route to its
neighbor if the advertise route and the source route are in the same network.
Since R3 has replaced R4 to aggregate detailed routes, R1 cannot arrive R4 and next hop
must be adjusted to avoid a sub-optimal route.
Check the path along which traffic is transmitted during communication between service
network segments, analyze the physical network topology, and avoid affecting other
requirements during the configuration.

8. Configure the Community attribute to prevent AS 200 from receiving the

routes to service network segment 192.168.20.0/24.
Transfer of route can be limited via set the community, including Internet、No-advertise、
No-export、No-export-subconfed, etc.
After completing this task, run the display bgp routing-table community command to
view the BGP Community attribute. The following uses the display of R1 as an example.
Only key information is displayed, while other information is omitted.
<R1>display bgp routing-table community
e n
/
o m
e i .c
w

u a
g .h
ni n
r
Network NextHop MED LocPrf PrefVal Community
lea
*>i 192.168.20.0 10.0.5.5 0 100 0 no-export
: //
9.
t p
Assume that service network segment 172.16.10.0/24 is unstable and often
t
:h
interrupted. Perform the correct configuration to reduce the impact of such
interruptions on the entire network.
e s
r c
Dampening of BGP can be used to reduce route fluctuation.
ou
Analyze the requirement, add correct configuration, and verify the configuration.
After completing this task, run the display bgp routing-table dampening parameter
es
command to view the BGP dampening. The following uses the display of R4 as an example.
R
Only key information is displayed, while other information is omitted.
i n g
<R4>display bgp routing-table dampening parameter
r n
Maximum Suppress Time(in second) : 3973
e aCeiling Value : 16000
e L
r
Reuse Value : 750
o
M
HalfLife Time(in second) : 900
Suppress-Limit : 2000
Route-policy : damp
10. Configure authentication between EBGP peers to improve BGP network

security.
Configure authentication between two EBGP peers, and set the password to huawei.
After completing this task, run the display bgp peer 10.0.5.5 verbose command to view
the BGP peer. The following uses the display of R2 as an example. Only key information is

[R2]display bgp peer 10.0.5.5 verbose
BGP Peer is 10.0.5.5, remote AS 300
Type: EBGP link
BGP version 4, Remote router ID 10.0.5.5
Update-group ID: 0
e n
BGP current state: Established, Up for 00h08m00s
/
o m
.c
BGP current event: KATimerExpired
BGP last state: OpenConfirm

e i
aw
u
Authentication type configured: MD5
. h
Holdtime accordingly on R2.
i n g
11. Change the BGP Keepalive timer to 30 seconds and adjust the BGP
r n
e a
Learn about the working principles of BGP timers and know how to adjust the timers.
l
//
After completing this task, run the display bgp peer 10.0.2.2 verbose command to view
:
the BGP peer. The following uses the display of R1 as an example. Only key information is
tp
ht
<R1>display bgp peer 10.0.2.2 verbose
s :
e
BGP Peer is 10.0.2.2, remote AS 100
r c
u
Type: IBGP link
s o
BGP version 4, Remote router ID 10.0.2.2
R e
Update-group ID: 1
i n g
BGP current state: Established, Up for 00h03m28s
a rnBGP current event: RecvKeepalive
L e
e
BGP last state: OpenConfirm
or BGP Peer Up count: 1
M Received total routes: 6
Received active routes total: 4
Advertised total routes: 5
Port: Local - 179 Remote - 49184
Configured: Connect-retry Time: 32 sec
Configured: Active Hold Time: 180 sec Keepalive Time:60 sec

Received : Active Hold Time: 90 sec
Negotiated: Active Hold Time: 90 sec Keepalive Time:30 sec
Questions
If the sub-optimal route is found in requirement 7, how many methods are available to
solve this problem? If no such problem occurs, do you know why?
To ensure R3 give priority to aggregate route from R4, R4 must aggregate routes and
e n
/
restrain detailed routes. Because of the default character of BGP, A true next hop from R3 to
m
R1 will ensure the generation of a sub-optimal route.
o
R1 can use route-policy to modify the router’s next hop from R3, but output interface
.c
cannot be used since there is only one.
e i
w
Configuration List
u a
.h
i n g
sysname R1
r n
#
// lea
p :
t
acl number 2000
t
:h
rule 5 permit source 10.0.2.2 0
#
e s
r c
ou
es
ip address 10.0.12.1 255.255.255.0
R
g
#
n i n
ar
e
ip address 10.0.134.1 255.255.255.0
e L #
M ip address 10.0.1.1 255.255.255.255
bgp 100
router-id 10.0.1.1
peer 10.0.2.2 as-number 100

peer 10.0.2.2 connect-interface LoopBack0
peer 10.0.134.3 password simple huawei
ipv4-family unicast
e n
/
undo synchronization
network 10.0.1.1 255.255.255.255
o m
import-route ospf 1 route-policy O2B
e i .c
peer 10.0.2.2 enable
aw
u
.h
peer 10.0.2.2 next-hop-local
i n g
peer 10.0.134.3 advertise-community
r n
#
// lea
p :
t
t
:h
area 0.0.0.0
network 10.0.1.1 0.0.0.0

e s
r c
ou
network 10.0.12.1 0.0.0.0
#
es
R
g
route-policy O2B permit node 10
n i n
if-match acl 2000
ar
e
#
e L return
or
M <R2>display current-configuration
sysname R2
acl number 2000

acl number 2001
ip address 10.0.25.2 255.255.255.0
e n
/
#
o m
ip address 10.0.12.2 255.255.255.0
e i .c
#
aw
u
.h
interface LoopBack0
ip address 10.0.2.2 255.255.255.255
i n g
#
r n
bgp 100
// lea
p :
t
router-id 10.0.2.2
t
:h
timer keepalive 30 hold 90

e s
r c
ou
es
R
g
peer 10.0.5.5 ebgp-max-hop 2
n i n
ar
e
e L #
or ipv4-family unicast
M undo synchronization
network 10.0.2.2 255.255.255.255
import-route static route-policy S2B

area 0.0.0.0
network 10.0.2.2 0.0.0.0
e n
/
network 10.0.12.2 0.0.0.0
o m
route-policy S2B permit node 10
e i .c
if-match acl 2000
aw
u
.h
if-match acl 2001
i n g
#
r n
ip route-static 10.0.5.5 255.255.255.255 10.0.25.5
// lea
p :
t
#
t
:h
return
e s
r c
ou
#
es
R
g
sysname R3
#
n i n
ar
e
e L ip address 10.0.134.3 255.255.255.0
or #
ip address 10.0.3.3 255.255.255.255
bgp 200
router-id 10.0.3.3

ipv4-family unicast
e n
/
aggregate 172.16.0.0 255.255.0.0 detail-suppressed
network 10.0.3.3 255.255.255.255
o m
e i .c
aw
u
.h
i n g
return
r n
// lea
p :
t
t
:h
#
sysname R4
e s
r c
ou
#
acl number 2000

es
R
g
#
n i n
ar
e
e L ip address 10.0.134.4 255.255.255.0
or #
ip address 10.0.4.4 255.255.255.255
interface LoopBack1
ip address 172.16.10.1 255.255.255.0

interface LoopBack2
ip address 172.16.20.1 255.255.255.0
bgp 200
router-id 10.0.4.4
e n
/
o m
ipv4-family unicast
e i .c
aw
u
.h
dampening route-policy damp
aggregate 172.16.0.0 255.255.0.0 detail-suppressed
i n g
network 10.0.4.4 255.255.255.255
r n
network 172.16.10.0 255.255.255.0
// lea
p :
t
network 172.16.20.0 255.255.255.0
t
:h
#
e s
r c
ou
route-policy damp permit node 10
if-match acl 2000

es
R
g
#
return
n i n
ar
Le
e
or #
M sysname R5
acl number 2000
acl number 2001

ip address 10.0.25.5 255.255.255.0
interface LoopBack0
e n
/
ip address 10.0.5.5 255.255.255.255
o m
interface LoopBack1
e i .c
ip address 192.168.10.1 255.255.255.0
aw
u
.h
#
interface LoopBack2
i n g
ip address 192.168.20.1 255.255.255.0
r n
#
// lea
p :
t
interface LoopBack3
t
:h
ip address 192.168.30.1 255.255.255.0
#
e s
r c
ou
bgp 300
router-id 10.0.5.5
es
R
g
n i n
peer 10.0.2.2 ebgp-max-hop 2
ar
e
e L peer 10.0.2.2 password simple huawei
or #
M ipv4-family unicast
aggregate 192.168.0.0 255.255.0.0 suppress-policy sup origin-policy ori
network 10.0.5.5 255.255.255.255
network 192.168.10.0
network 192.168.20.0

network 192.168.30.0
import-route static
peer 10.0.2.2 route-policy comm_r5 export
e n
/
#
route-policy sup permit node 10
o m
if-match acl 2001
e i .c
#
aw
u
.h
route-policy ori deny node 10
if-match acl 2000
i n g
#
r n
route-policy ori permit node 20
// lea
p :
t
#
t
:h
route-policy comm_r5 permit node 10
if-match acl 2000

e s
r c
ou
apply community no-export
#
es
R
g
route-policy comm_r5 permit node 20
#
n i n
ar
e
ip route-static 10.0.2.2 255.255.255.255 10.0.25.2
e L #
or return
M
Chapter 5 BGP Advanced Hands-on Exercise Guide
Overview
Multiple routes to the same destination may exist in a BGP routing table. BGP selects
the optimal route from the multiple routes and sends only the optimal route to peers. To select
the optimal route, BGP compares the BGP attributes of the routes according to BGP route
selection rules. BGP attributes are a set of parameters that describe routes.
BGP attributes are classified into four types:

 Well-known mandatory attributes: This type of attribute can be identified by all the
BGP routers and must be carried in Update messages. Without this type of attribute,
errors occur in routing information. For example, the Origin, AS-Path, and
Next_Hop attributes are well-known mandatory attributes.
 Well-known discretionary attributes: This type of attribute can be identified by all
the BGP routers and is not necessarily carried in Update messages. Errors do not
occur in routing information even if this type of attribute is not available. For
example, the Local_Pref attribute is a well-known discretionary attribute.
 Optional transitive attributes: A BGP router may not recognize this type of attribute,
e n
/
but it still accepts these attributes and advertises them to other peers. For example,
the Community attribute is an optional transitive attribute.
 Optional non-transitive attributes: If a BGP router does not recognize this type of
o m
.c
attribute, it ignores these attributes and does not advertise them to other peers. For
example, the MED attribute is an optional non-transitive attribute.
e i
When there are multiple routes to the same destination, BGP compares the following
attributes in sequence to select the optimal route:
 Prefers the route with the largest PrefVal value.
aw
u
.h
 Prefers the route with the highest Local_Pref.
 Prefers the manually summarized route, automatically summarized route, route
i n g
imported using the network command, route imported using the import-route
n
command, and route learned from peers in sequence.
 Prefers the route with the shortest AS-Path.
r
lea
 Prefers the route with the lowest origin type. IGP is lower than EGP, and EGP is
//
lower than Incomplete.
:
 Prefers the route with the lowest MED among the routes from the same AS.
p
t
 Prefers an EBGP route (the preference of an EBGP route is higher than that of an
t
:h
IBGP route).
 Prefers the route with the lowest IGP metric to the BGP next hop.
s
 Prefers the route with the shortest Cluster_List.
e
r c
 Prefers the route advertised by the router with the smallest router ID.
 Prefers the route learned from the peer with the lowest IP address.
ou
The PrefVal attribute is a Huawei proprietary attribute and is valid only on the device
s
where it is configured. If a route does not have the local preference, BGP calculates its local
e
R
preference as the default value of 100. When there are multiple equal-cost routes to the same
destination, you can perform load balancing among these routes to load balance traffic.
n g
Equal-cost BGP routes can be generated for traffic load balancing only when the first eight
i
attributes described in "BGP Route Selection Rules" are the same.
r n
e a
Objectives
e L Upon completion of this exercise guide, you will be able to:
or 

Understand BGP route advertisement rules.
Understand BGP route selection rules.
M 

Explain BGP route reflector functions.
Modify the AS-Path attribute.
 Modify the MED attribute.
 Modify the Next_Hop attribute.
 Configure a BGP route reflector.
Tasks
The following topology shows the network of a company. In the topology, R4, R5, R6,
and R7 are routers in the headquarters. R1 and R3 are routers in two different branches. R2 is
a carrier's network device. Different service network segments are defined on R1 and R3.

Network segments 192.168.10.0/24 and 172.16.10.0/24 are used by service A, and network
segments 192.168.20.0/24 and 172.16.20.0/24 are used by service B. Leased lines are
deployed between two branches and the headquarters so that service network segments on
devices in two branches can access each other through the carrier's network device or through
the headquarters' devices over leased lines. Deploy the network according to the following
requirements:
(1) Build the network according to the topology, and establish EBGP peer relationships between
devices in different ASs through directly connected interfaces.
(2) Establish IBGP peer relationships between R4 and R5, between R5 and R7, between R7 and
n
R6, and between R6 and R4 through loopback interfaces. Deploy OSPF as an IGP.
(3) Ensure that all service network segments, and the network segments where loopback
interfaces Loopback 0 of all devices reside, access each other through BGP routes.
/ e
(4) Enable traffic of service network segment A to be forwarded by the carrier's network device,
o m
.c
and traffic of service network segment B to be forwarded by leased lines, in order to make full
(5)
use of network resources.
e i
Make the network administrator periodically check lines. After the link costs of IGPs are
w
adjusted, all the traffic that passes through the AS of the headquarters is forwarded along the
a
u
path R4->R5->R7->R6.
.h
(6) Forward traffic of service network segment B along the path R4->R6, because this network
g
segment has a high volume of traffic. Ensure that the optimal route selected by BGP is the
(7)
same as the actual forwarding path.
ni n
Reconstruct the headquarters' network, retain the existing configuration, and add
r
lea
configuration to disable R5 and R7 from participating in BGP route selection.
Topology
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
IP Address Table
Default
Gateway
R1 G 0/0/0 10.0.14.1 255.255.255.0 N/A
G 0/0/1 10.0.12.1 255.255.255.0 N/A

Loopback 0 10.0.1.1 255.255.255.255 N/A
G 0/0/0 10.0.12.2 255.255.255.0 N/A
R2 G 0/0/1 10.0.23.2 255.255.255.0 N/A
Loopback 0 10.0.2.2 255.255.255.255 N/A
G 0/0/0 10.0.23.3 255.255.255.0 N/A
R3 G 0/0/1 10.0.36.3 255.255.255.0 N/A
e n
Loopback 0 10.0.3.3 255.255.255.255 N/A
/
G 0/0/0 10.0.45.4 255.255.255.0 N/A
o m
R4
G 0/0/1 10.0.14.4 255.255.255.0
e i N/A
.c
w
G 0/0/2 10.0.46.4 255.255.255.0 N/A
Loopback 0 10.0.4.4 255.255.255.255
u a N/A
G 0/0/0 10.0.57.5 255.255.255.0
g .h N/A
R5 G 0/0/1 10.0.45.5
i n
255.255.255.0
n
N/A
Loopback 0 10.0.5.5
r
255.255.255.255
a
N/A
le
G 0/0/0 10.0.36.6 255.255.255.0 N/A
G 0/0/1
:
10.0.67.6
// 255.255.255.0 N/A
R6
G 0/0/2
t t p
10.0.46.6 255.255.255.0 N/A
:h
Loopback 0 10.0.6.6 255.255.255.255 N/A
e
G 0/0/0 s 10.0.67.7 255.255.255.0 N/A
R7
r c
G 0/0/1 10.0.57.7 255.255.255.0 N/A
s ou
Loopback 0 10.0.5.5 255.255.255.255 N/A
Configuration and R
e
Verification
i n gnetwork according to the topology, and establish EBGP peer

rn between devices in different ASs through directly connected
1. Build the
a
relationships
L e
interfaces.
ore Perform basic configuration according to the address table, and then check the
establishment of BGP peer relationships.
M
After completing this task, run the display bgp peer command to view BGP peer
information. The following uses the display of R1 as an example. Only key information is

Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
10.0.12.2 4 100 22 23 0 00:15:16 Established 3
10.0.14.4 4 400 17 22 0 00:14:24 Established 1
2. Establish IBGP peer relationships between R4 and R5, between R5 and R7,
between R7 and R6, and between R6 and R4 through loopback interfaces.
Deploy OSPF as an IGP.
e n
/
m
Configuration commands are required when peer relationships are established through
loopback interfaces.
After completing this task, run the display ospf peer brief command to view OSPF peer
.c o
information, run the display bgp peer command to view BGP peer information. The
e i
w
following uses the display of R4 as an example. Only key information is displayed, while
u a
.h
[R4]display ospf peer brief
i n g
Peer Statistic Information
r n
// lea
----------------------------------------------------------------------------
Area Id Interface
p : Neighbor id State
t t
:h
0.0.0.0 GigabitEthernet0/0/0 10.0.5.5 Full
0.0.0.0
e s
GigabitEthernet0/0/2 10.0.6.6 Full
r c
ou
----------------------------------------------------------------------------
es
R
g
[R4]display bgp peer
n i n
ar
e
eL
or Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
M 10.0.5.5 4 400 0 0 0 00:04:19 Established 0
10.0.6.6 4 400 12 13 0 00:03:15 Established 0
10.0.14.1 4 100 18 12 0 00:03:47 Established 0
3. Ensure that all service network segments, and the network segments where
loopback interfaces Loopback 0 of all devices reside, access each other
through BGP routes.

<R1>display bg routing-table
e n
/
m
.c o
Network NextHop MED LocPrf
e
PrefVal Path/Ogn i
aw
u
*> 10.0.1.1/32 0.0.0.0 0 0 i
*> 10.0.2.2/32 10.0.12.2 0 0
g .h
200i
*> 10.0.3.3/32 10.0.12.2
ni n0 200 300i
r
lea
* 10.0.14.4 0 400 300i
*> 10.0.4.4/32 10.0.14.4 0

: // 0 400i
*> 10.0.5.5/32 10.0.14.4

t t1 p 0 400?
:h
es
*> 10.0.6.6/32 10.0.12.2 0 200 300 400i
*> 10.0.7.7/32
r c
10.0.14.4 0 400?
*> 172.16.10.0/24
s ou10.0.12.2 0 200 300i
*
Re 10.0.14.4 0 400 300i
*>
i n g
172.16.20.0/24 10.0.12.2 0 200 300i
r n
a
* 10.0.14.4 0 400 300i
e
eL
*> 192.168.10.0 0.0.0.0 0 0 i
or
*> 192.168.20.0 0.0.0.0 0 0 i
M 4. Enable traffic of service network segment A to be forwarded by the carrier's

network device, and traffic of service network segment B to be forwarded by
leased lines, in order to make full use of network resources.
Understand the AS-Path attribute principles and modify the attribute accordingly.

e n
/
*> 172.16.10.0/24 10.0.12.2 0 200 300i
o m
* 10.0.14.4 0 400 300i
e i .c
*> 172.16.20.0/24 10.0.14.4 0 400 300i
aw
u
.h
* 10.0.12.2 0 200 200 200 300i
i n g
<R1>tracert -a 192.168.10.1 172.16.10.1
r n
traceroute to
// lea
p :
t
CTRL_C to break
t
:h
1 10.0.12.2 90 ms 50 ms 50 ms
2 10.0.23.3 120 ms
e s
60 ms 50 ms
r c
s ou
e
<R1>tracert -a 192.168.20.1 172.16.20.1
R
g
traceroute to 172.16.20.1(172.16.20.1), max hops: 30 ,packet length: 40,press
n i n
CTRL_C to break
ar
e
1 10.0.14.4 40 ms 30 ms 50 ms
e L 2 10.0.46.6 60 ms 80 ms 60 ms
or 3 10.0.36.3 100 ms 120 ms 80 ms
M MED is used to control the channel of inbound traffic from external AS, compare of
MED is limited in only one AS by default, but it can be modified to compare among
different AS. The less MED is, the better. BGP can modify the value of MED.
Understand the MED attribute principles, learn how to configure the attribute, and
modify the attribute accordingly.

e n
/
*> 192.168.10.0 10.0.23.2 0 200 100i
o m
* 10.0.36.6 0 400 100i
e i .c
*> 192.168.20.0 10.0.36.6 0 400 100i
aw
u
.h
* 10.0.23.2 200 0 200 100i
i n g
<R3>tracert -a 172.16.10.1 192.168.10.1
r n
traceroute to
// lea
p :
t
CTRL_C to break
t
:h
1 10.0.23.2 10 ms 40 ms 40 ms
2 10.0.12.1 70 ms
e
60 mss 40 ms
r c
s ou
e
<R3>tracert -a 172.16.20.1 192.168.20.1
R
g
traceroute to 192.168.20.1(192.168.20.1), max hops: 30 ,packet length: 40,press
n i n
CTRL_C to break
ar
e
1 10.0.36.6 10 ms 50 ms 30 ms
e L 2 10.0.46.4 80 ms 60 ms 80 ms
or 3 10.0.14.1 110 ms 80 ms 70 ms
M 5. Make the network administrator periodically check lines. After the link costs
of IGPs are adjusted, all the traffic that passes through the AS of the
headquarters is forwarded along the path R4->R5->R7->R6.
Based on the principle of split-horizon among IBGP neighbors, R5 has no access to the
service network segment 172.16.20.0, R7 has no access to the service network segment
192.168.20.0. We can import BGP routes into OSPF so that R5 and R7 can get access under
IGP.
When OSPF imports BGP as external route, the other OSPF routers will choose the
nearest ASBR by default, during which path can be modified by cost of interface, which is
one by default.
After completing this task, run the display ip routing-table command to view
routing-table information. The following uses the display of R4 and R6 as an example. Only
key information is displayed, while other information is omitted.
-----------------------------------------------------------------------------
e n
/
-

o m
e i .c
aw
Interface
u
.h
172.16.10.0/24 IBGP 255 0 RD 10.0.6.6
i n g
172.16.20.0/24 O_ASE 150 1 D
r n
10.0.45.5
// lea
p :
t t
:h
e s
r c
ou
Routing Tables
es
Routing for ASEs
R
g
n i n
172.16.20.0/24 1 Type2 1 10.0.46.6 10.0.6.6
ar
Le
r e [R4]display ospf interface
o OSPF Process 1 with Router ID 10.0.4.4
M Interfaces
Area: 0.0.0.0 (MPLS TE not enabled)
IP Address Type State Cost Pri DR BDR
10.0.45.4 Broadcast BDR 1 1 10.0.45.5 10.0.45.4
10.0.46.4 Broadcast BDR 100 1 10.0.46.6 10.0.46.4

10.0.4.4 P2P P-2-P 0 1 0.0.0.0 0.0.0.0
Routing Tables
e n
/
Routing for ASEs
o m
192.168.20.0/24 1 Type2 1 10.0.67.7
i
10.0.4.4
e .c
aw
u
.h
<R1>tracert -a 192.168.20.1 172.16.20.1
traceroute to
n g
i
CTRL_C to break
r n
1 10.0.14.4 30 ms 30 ms 30 ms
// lea
p :
t
2 10.0.45.5 80 ms 70 ms 40 ms
t
:h
3 10.0.57.7 130 ms 110 ms 70 ms
4 10.0.67.6 100 ms
e s
120 ms 160 ms
r c
ou
5 10.0.36.3 120 ms 210 ms 110 ms
es
R
6. Forward traffic of service network segment B along the path R4->R6,
g
because this network segment has a high volume of traffic. Ensure that the
i n
optimal route selected by BGP is the same as the actual forwarding path.
n
ar IBGP cannot transfer route because of the principle of split-horizon, so we need to use
L e
full mesh topology or router-reflector to realize.
Since the default route preference of BGP is 255 and OSPF is 150, we must decrease the
r e BGP’s route preference to choose path.
o Understand BGP route selection rules and route-reflectors, analyze the routing table, and
M
perform configuration based on routing policies.
BGP routing table. The following uses the display of R6 and R4as an example. Only key

*>i 172.16.10.0/24 10.0.6.6 0 100 0 300i
* i 10.0.6.6 0 100 0 300i
e n
/
* 10.0.14.1 0 100 200 300i
*>i 172.16.20.0/24 10.0.46.6 0 100 0 300i
o m
* i 10.0.6.6 0 100 0 300i
e i .c
*> 192.168.10.0 10.0.14.1 0 0
w
100i
a
u
.h
*> 192.168.20.0 10.0.14.1 0 0 100i
i n g
r n
// lea
p :
t
-----------------------------------------------------------------------------
t
:h
-

e s
r c
ou
Destination/Mask
es Proto Pre Cost Flags NextHop Interface
R
g
172.16.20.0/24 IBGP 100 0 RD 10.0.46.6 GigabitEthernet0/0/2
n i n
ar
e
e L BGP Local router ID is 10.0.6.6
or Status codes: * - valid, > - best, d - damped,
M h - history, i - internal, s - suppressed, S - Stale
*> 172.16.10.0/24 10.0.36.3 0 0 300i
*> 172.16.20.0/24 10.0.36.3 0 0 300i

*>i 192.168.10.0 10.0.4.4 0 100 0 100i
* i 10.0.4.4 0 100 0 100i
* 10.0.36.3 0 300 200 100i
*>i 192.168.20.0 10.0.46.4 0 100 0 100i
* i 10.0.4.4 0 100 0 100i
e n
/
[R6-ospf-1]display ip routing-table
o m
e i .c
-----------------------------------------------------------------------------
aw
u
.h
-
i n g
r n
// lea
p :
t
192.168.20.0/24 IBGP 100 0 RD 10.0.46.4
t
:h
e s
r c
ou
<R1>tracert -a 192.168.20.1 172.16.20.1
traceroute to
es 172.16.20.1(172.16.20.1), max hops: 30 ,packet length: 40,press
R
g
CTRL_C to break
n i n
1 10.0.14.4 30 ms 50 ms 60 ms
ar
e
2 10.0.46.6 30 ms 80 ms 90 ms
e L 3 10.0.36.3 100 ms 70 ms 70 ms
or
M 7. Reconstruct the headquarters' network, retain the existing configuration,
and add configuration to disable R5 and R7 from participating in BGP route
selection.
BGP can use the command peer ignore to suspend the neighbor relationship with other
BGP routers.
BGP establishes neighbors with three-hands mechanism, one side has to initiate TCP
connection. Otherwise, TCP connection will fail.
Peer listen-only command is passive to TCP connection, so both sides must be enabled
at the same time.
After completing this task, run the display bgp peer command on R4 and R6 to view
BGP peer information. Only key information is displayed, while other information is omitted.
e n
/
10.0.5.5 4 400 0 0 0 00:59:43 Idle(Admin) 0
10.0.6.6 4 400 65 69 0 00:53:18 Established 6
o m
10.0.14.1 4 100 253 206 0 03:00:59 Established
e i 6
.c
aw
u
.h
i n g
r n
Total number of peers : 3
// lea
Peers in established state : 2
p :
t
t
:h
10.0.4.4 4 400 69 66 0 00:53:28 Established 6
10.0.7.7 4 400
e s0 0 0 00:54:00 Idle 0
r c
ou
10.0.36.3 4 300 88 65 0 00:53:29 Established 6
es
Questions
R
i n g
Why BGP routes to service network segments on the devices in AS 400 have two
n
routing entries with the same next hop?
ar Since R5 and R7 in AS400 are both router reflector, they don’t modify the next hop adds
L e
when reflecting routers, that is, the router is all the same.
Are there multiple methods to meet requirement 6 and which method is the best one?
r e Imported from BGP to OSPF can be cancelled, after which BGP will have no need to
o
modify the router preference, and only the next hop adds is needed to modified, so that the
suboptimal route can b avoided. Comparatively, Cancelling importing BGP to OSPF is better.
M What problems occur on the network after requirement 7 is met and why do these
problems occur?
When R5 and R7 are not involved in election, Business B must transfer traffic via
AS200 other than AS200 if the connection between R4 and R6 is broken down.
Configuration List

sysname R1
ip address 10.0.14.1 255.255.255.0
e n
/
ip address 10.0.12.1 255.255.255.0
o m
#
e i .c
interface LoopBack0
aw
u
.h
ip address 10.0.1.1 255.255.255.255
i n g
interface LoopBack1
r n
ip address 192.168.10.1 255.255.255.0
// lea
p :
t
#
t
:h
interface LoopBack2
e s
ip address 192.168.20.1 255.255.255.0
r c
ou
#
bgp 100
es
R
g
router-id 10.0.1.1
n i n
ar
e
e L #
or ipv4-family unicast
M undo synchronization
network 10.0.1.1 255.255.255.255
network 192.168.10.0
network 192.168.20.0

return
e n
/
sysname R2
o m
acl number 2000
e i .c
aw
u
.h
acl number 2001
i n g
#
r n
// lea
p :
t
ip address 10.0.12.2 255.255.255.0
t
:h
#
e s
r c
ou
ip address 10.0.23.2 255.255.255.0
#
es
R
g
interface LoopBack0
n i n
ip address 10.0.2.2 255.255.255.255
ar
e
#
e L bgp 200
or router-id 10.0.2.2
M peer 10.0.12.1 as-number 100
peer 10.0.12.1 timer keepalive 30 hold 90
peer 10.0.23.3 timer keepalive 30 hold 90
ipv4-family unicast

network 10.0.2.2 255.255.255.255
peer 10.0.12.1 route-policy AS export
e n
/
peer 10.0.23.3 route-policy MED export
o m
route-policy AS permit node 10
e i .c
if-match acl 2000
aw
u
.h
apply as-path 200 200 additive
i n g
route-policy AS permit node 20
r n
#
// lea
p :
t
route-policy MED permit node 10
t
:h
if-match acl 2001
apply cost 200

e s
r c
ou
#
es
route-policy MED permit node 20
R
g
#
return
n i n
ar
Le
e
or #
M sysname R3
ip address 10.0.23.3 255.255.255.0

ip address 10.0.36.3 255.255.255.0
interface LoopBack0
ip address 10.0.3.3 255.255.255.255
e n
/
interface LoopBack1
ip address 172.16.10.1 255.255.255.0
o m
#
e i .c
interface LoopBack2
aw
u
.h
ip address 172.16.20.1 255.255.255.0
i n g
bgp 300
r n
router-id 10.0.3.3
// lea
p :
t
t
:h
#
e s
r c
ou
ipv4-family unicast
es
R
g
compare-different-as-med
n i n
network 10.0.3.3 255.255.255.255
ar
e
network 172.16.10.0 255.255.255.0
e L network 172.16.20.0 255.255.255.0
or peer 10.0.23.2 enable
M peer 10.0.36.6 enable
return

sysname R4
acl number 2000
acl number 2001
e n
/
o m
e i .c
ip address 10.0.45.4 255.255.255.0
aw
u
.h
#
i n g
ip address 10.0.14.4 255.255.255.0
r n
#
// lea
p :
t
t
:h
ip address 10.0.46.4 255.255.255.0
ospf cost 100

e s
r c
ou
#
e
interface LoopBack0
s
R
g
ip address 10.0.4.4 255.255.255.255
#
n i n
ar
e
bgp 400
e L router-id 10.0.4.4
or peer 10.0.5.5 as-number 400
M peer 10.0.5.5 ignore

ipv4-family unicast
preference 255 100 255
network 10.0.4.4 255.255.255.255
e n
/
o m
e i .c
peer 10.0.6.6 route-policy local export
aw
u
.h
i n g
#
r n
// lea
p :
t
import-route bgp route-policy B2O
t
:h
area 0.0.0.0
network 10.0.4.4 0.0.0.0

e s
r c
ou
network 10.0.45.4 0.0.0.0
es
network 10.0.46.4 0.0.0.0
R
g
#
n i n
ar
e
if-match acl 2000
e L #
or route-policy local permit node 10
M if-match acl 2001
route-policy local permit node 20
route-policy B2O permit node 10

if-match acl 2001
return
e n
/
#
sysname R5
o m
#
e i .c
aw
u
.h
ip address 10.0.57.5 255.255.255.0
i n g
r n
ip address 10.0.45.5 255.255.255.0
// lea
p :
t
#
t
:h
interface LoopBack0
e s
ip address 10.0.5.5 255.255.255.255
r c
ou
#
bgp 400
es
R
g
router-id 10.0.5.5
n i n
ar
e
e L peer 10.0.7.7 as-number 400
or peer 10.0.7.7 connect-interface LoopBack0
M #
ipv4-family unicast
reflector cluster-id 1
network 10.0.5.5 255.255.255.255

peer 10.0.4.4 reflect-client
e n
/
area 0.0.0.0
network 10.0.5.5 0.0.0.0
o m
network 10.0.45.5 0.0.0.0
e i .c
network 10.0.57.5 0.0.0.0
aw
u
.h
#
return
i n g
r n
// lea
p :
t
#
t
:h
sysname R6
#
e s
r c
ou
acl number 2000
es
R
g
acl number 2001
n i n
ar
e
#
e L interface GigabitEthernet0/0/0
or ip address 10.0.36.6 255.255.255.0
M #
ip address 10.0.67.6 255.255.255.0
ip address 10.0.46.6 255.255.255.0

ospf cost 100
interface LoopBack0
ip address 10.0.6.6 255.255.255.255
e n
/
bgp 400
router-id 10.0.6.6
o m
e i .c
aw
u
.h
i n g
peer 10.0.7.7 listen-only
r n
// lea
p :
t
#
t
:h
ipv4-family unicast
e s
r c
ou
preference 255 100 255
es
network 10.0.6.6 255.255.255.255
R
g
n i n
ar
e
e L peer 10.0.4.4 route-policy local export
or peer 10.0.7.7 enable
M peer 10.0.7.7 next-hop-local
import-route bgp route-policy B2O
area 0.0.0.0

network 10.0.6.6 0.0.0.0
network 10.0.46.6 0.0.0.0
network 10.0.67.6 0.0.0.0
e n
/
if-match acl 2000
o m
route-policy B2O permit node 10
e i .c
if-match acl 2001
aw
u
.h
#
i n g
if-match acl 2001
r n
// lea
p :
t
#
t
:h
#
e s
r c
ou
return
es
R
g
#
n i n
ar
e
sysname R7
e L #
or acl number 2000
M rule 5 permit source 192.168.20.0 0.0.0.255
ip address 10.0.67.7 255.255.255.0

ip address 10.0.57.7 255.255.255.0
interface LoopBack0
ip address 10.0.7.7 255.255.255.255
e n
/
bgp 400
router-id 10.0.7.7
o m
e i .c
aw
u
.h
i n g
peer 10.0.6.6 listen-only
r n
#
// lea
p :
t
ipv4-family unicast
t
:h
reflector cluster-id 2
e s
r c
ou
reflect change-path-attribute
es
network 10.0.7.7 255.255.255.255
R
g
n i n
ar
e
e L peer 10.0.6.6 route-policy next export
or peer 10.0.6.6 reflect-client
M #
area 0.0.0.0
network 10.0.7.7 0.0.0.0
network 10.0.57.7 0.0.0.0
network 10.0.67.7 0.0.0.0

route-policy next permit node 10
if-match acl 2000
e n
/
route-policy next permit node 20
o m
return
e i .c
aw
Chapter 6 Route Import and Control Hands-onuExercise
. h
Guide
i n g
r n
a
Overview
l e
//
You can configure route importing to enable protocols to exchange routing information.
:
tp
Due to ever changing network environments, design defects, or misoperations, routing loops
t
may occur and sub-optimal routes may be generated. In this situation, network resources are
: h
wasted, and communication failures may even occur. To prevent these problems, add some
matching conditions during route importing and use route policies for route control.
e s
Route policies use different matching conditions and matching modes to select routes
r c
and change route attributes. A route policy may consist of multiple nodes. Each node has the
o
and IP prefix list.u
permit or deny action. A route policy can reference other route selection tools such as ACL
es
Objectives
R
i n g
rn
 Configure an ACL and an IP prefix list.
a
 Configure a route policy.
L e


Filter routes in OSPF.
Filter routes in IS-IS.
e
or
 Configure route importing in different scenarios.
 Understand why routing loops occur.

M Tasks
Prevent routing loops.
The topology shows the network of a company. OSPF runs in the company's
headquarters, and IS-IS runs in the company's branch. The headquarters and branch have
some service network segments. Network segments 172.16.1.0/24, 172.16.3.0/24,
192.168.1.0/24, and 192.168.3.0/24 are service A network segments, and network segments
172.16.2.0/24, 172.16.4.0/24, 192.168.2.0/24, and 192.168.43.0/24 are service B network
segments. Deploy the network according to the following requirements:
(1) Build an OSPF network for the headquarters and an IS-IS network for the branch according to
the topology. Minimize the number of routing entries to be maintained by the devices in OSPF
Area 1.
(2) Import IS-IS routes on R1 into OSPF, and import OSPF routes on R2 into IS-IS. Perform
correct commissioning to ensure that service network segments communicate normally.
(3) Deploy bidirectional route importing on R1 and R2 to prevent single-point failures between
the headquarters and branch from resulting in network disconnection. Perform correct
commissioning to ensure that service network segments communicate normally.
(4) Implement load balancing on traffic between the headquarters and branch to ensure that traffic
of service A is forwarded through R1, and traffic of service B is forwarded through R2.
(5) Forward traffic of service A and traffic of service B in OSPF Area 1 of the headquarters using
n
different links to implement load balancing. Do not use any route policy.
Topology / e
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
ou
IP Address Table
es Default
R
Gateway
i n g G 0/0/0 10.0.13.1 255.255.255.0 N/A
r nR1 G 0/0/1 10.0.14.1 255.255.255.0 N/A
e a Loopback 0 10.0.1.1 255.255.255.255 N/A
eL
G 0/0/0 10.0.23.2 255.255.255.0 N/A
or R2 G 0/0/1 10.0.24.2 255.255.255.0 N/A
M Loopback 0
G 0/0/0
10.0.2.2
10.0.13.3
255.255.255.255
255.255.255.0
N/A
N/A
R3 G 0/0/1 10.0.23.3 255.255.255.0 N/A
Loopback 0 10.0.3.3 255.255.255.255 N/A
G 0/0/0 10.0.14.4 255.255.255.0 N/A
R4 G 0/0/1 10.0.24.4 255.255.255.0 N/A
S 1/0/0 10.0.45.4 255.255.255.0 N/A

S 1/0/1 10.0.54.4 255.255.255.0 N/A

Loopback 0 10.0.4.4 255.255.255.255 N/A
S 1/0/0 10.0.45.5 255.255.255.0 N/A
R5 S 1/0/1 10.0.54.5 255.255.255.0 N/A
Loopback 0 10.0.5.5 255.255.255.255 N/A
n
1. Build an OSPF network for the headquarters and an IS-IS network for the / e
branch according to the topology. Minimize the number of routing entries to
o m
be maintained by the devices in OSPF Area 1.
e i .c
w
Perform basic configuration according to the IP address table, and then check the
establishment of OSPF and IS-IS neighbor relationships.
u a
.h
<R1>display ospf peer
i n g
Neighbors
r n
// lea
Area 0.0.0.0 interface 10.0.14.1(GigabitEthernet0/0/1)'s neighbors
p :
t
Router ID: 10.0.4.4 Address: 10.0.14.4
t
:h
State: Full Mode:Nbr is Master Priority: 1
DR: 10.0.14.1
e s
BDR: 10.0.14.4 MTU: 0
r c
ou
Dead timer due in 39 sec
es
Retrans timer interval: 5
R
g
Neighbor is up for 03:13:21
n i n
Authentication Sequence: [ 0 ]
ar
L e
r e <R1>display isis peer
o Peer information for ISIS(1)
M System Id Interface Circuit Id State HoldTime Type PRI
-------------------------------------------------------------------------
0000.0000.0003 GE0/0/0 0000.0000.0003.01 Up 8s L1(L1L2) 64
0000.0000.0003 GE0/0/0 0000.0000.0003.01 Up 7s L2(L1L2) 64
Total Peer(s): 2

2. Import IS-IS routes on R1 into OSPF, and import OSPF routes on R2 into
IS-IS. Perform correct commissioning to ensure that service network
segments communicate normally.
Note: ISIS need wide metric to carry tag with route. Pay attention to the external ospf
route imported by R5.
After configuration, we can see that R1 has imported the ISIS route by check the LSDB
on R4 ; also we can see R2 has imported the OSPF route .
n
<R4>display ospf lsdb

/ e
o m
.c
AS External Database
Type LinkState ID AdvRouter Age Len Sequence

e i
Metric
External 172.16.4.0 10.0.4.4 1558 36 80000001

aw 1
u
External 172.16.2.0 10.0.4.4 1558 36
g
80000001
.h 1
External 172.16.3.0 10.0.4.4 1558

i
36
n n 80000001 1
r
lea
External 172.16.1.0 10.0.4.4 1558 36 80000001 1
://
External 192.168.4.0 10.0.1.1 824 36 80000001 1
External 192.168.2.0
t
10.0.1.1
tp 824 36 80000001 1
External 192.168.3.0
s :h
10.0.1.1 824 36 80000001 1
External
r
192.168.1.0
c e 10.0.1.1 825 36 80000001 1
……
s ou
Re
g
<R3>display isis lsdb level-2
n i n Database information for ISIS(1)
ar
e
Level-2 Link State Database
eL
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
or 0000.0000.0002.00-00 0x0000001b 0x23f 1024 80 0/0/0
M 0000.0000.0002.00-01 0x00000002 0x375f 1024 213 0/0/0
……
<R3>display isis lsdb level-2 0000.0000.0002.00-01 ver
Database information for ISIS(1)
Level-2 Link State Database

LSPID Seq Num Checksum Holdtime Length ATT/P/OL
0000.0000.0002.00-01 0x00000002 0x375f 865 213 0/0/0
SOURCE 0000.0000.0002.00
…….
+IP-Extended 172.16.1.0 255.255.255.0 COST: 0 Tag: 200
e n
/
o m
e i .c
Total LSP(s): 1
aw
u
.h
*(In TLV)-Leaking Route, *(By LSPID)-Self LSP, +-Self LSP(Extended),
ATT-Attached, P-Partition, OL-Overload
i n g
3. Deploy bidirectional route importing on R1 and R2
r n toresulting
prevent single-point
a
le to ensure that service
failures between the headquarters and branch from in network
network segments communicate normally. //

disconnection. Perform correct commissioning
p :
t t
: h between the headquarters and branch
Note: the solution is the same as the before.
4. Implement load balancing on straffic

c e
r R2.
to ensure that traffic of service A is forwarded through R1, and traffic of
u
service B is forwarded through
o
s
Re
Note: we can apply cost to specified routes when import route.
i n g
a rn 172.16.1.0/24 ISIS-L2 15 110 D 10.0.13.1 GigabitEthernet0/0/0
L e
e
or 172.16.3.0/24 ISIS-L2 15 110 D 10.0.13.1 GigabitEthernet0/0/0
M 172.16.4.0/24 ISIS-L2 15 110 D 10.0.23.2 GigabitEthernet0/0/1
……

……
n
5. Forward traffic of service A and traffic of service B in OSPF Area 1 of the
headquarters using different links to implement load balancing. Do not use
any route policy. / e
o m
.c
Note: Use policy route. In this requirement we need to use interface policy route.
<R4>display traffic policy user-defined
e i
User Defined Traffic Policy Information:
aw
u
Policy: loadbalance
g .h
Classifier: serviceA
ni n
r
lea
Operator: OR
Behavior: SAbeh
: //
Redirect:
t t p
s
Redirect ip-nexthop 10.0.45.5
:h
Classifier: serviceB
r c e
Operator: OR
s ou
Re
Behavior: SBbeh
n g
Redirect:
i
r n Redirect ip-nexthop 10.0.54.5
e a
e L
or <R5>display traffic policy user-defined
M User Defined Traffic Policy Information:
Policy: loadbalance
Classifier: serviceA
Operator: OR
Behavior: SAbeh
Redirect:

Classifier: serviceB
Operator: OR
Behavior: SBbeh
Redirect:
e n
/
o m
.c
Questions
e i
Which problems will occur on the network after requirement 2 is met and how many
methods are available to solve the problems?
aw
u
Which problems will occur on the network after requirement 3 is met? Why do these
.h
problems occur? What are the differences between the problems in requirement 2 and
g
requirement 3?
i n
How many methods are available to meet requirement 4 and how to select a correct
method?
n
r
What problem occurs on the network after requirement 5 is met and why do these
lea
problems occur?
Configuration List
: //
t t p
:h
e s
c
#
r
ou
sysname R1
#
es
R
i n g
router id 10.0.1.1
r n
e a
acl number 2000
e L
r
o acl number 2001
acl number 2010
acl number 2011

isis 1
cost-style wide
network-entity 10.0000.0000.0001.00
import-route ospf 1 route-policy OSPF-TO-ISIS
e n
/
#
o m
ip address 10.0.13.1 255.255.255.0
e i .c
isis enable 1
aw
u
.h
#
i n g
ip address 10.0.14.1 255.255.255.0
r n
#
// lea
p :
t
interface LoopBack0
t
:h
ip address 10.0.1.1 255.255.255.255
#
e s
r c
ou
ospf 1
es
import-route isis 1 route-policy ISIS-TO-OSPF
R
g
preference ase route-policy OSPF-PREFERENCE 150
n i n
area 0.0.0.0
ar
e
network 10.0.1.1 0.0.0.0
e L network 10.0.14.0 0.0.0.255
or #
M route-policy ISIS-TO-OSPF deny node 10
if-match tag 200
route-policy ISIS-TO-OSPF permit node 20
if-match acl 2010
apply cost 100

apply tag 100
if-match acl 2011
apply cost 500
e n
/
apply tag 100
o m
e i .c
apply tag 100
aw
u
.h
#
route-policy OSPF-TO-ISIS deny node 10
i n g
if-match tag 400
r n
#
// lea
p :
t
route-policy OSPF-TO-ISIS permit node 20
t
:h
if-match acl 2000
apply cost 100

e s
r c
ou
apply tag 300
#
es
R
g
n i n
if-match acl 2001
ar
e
apply cost 500
e L apply tag 300
or #
M route-policy OSPF-TO-ISIS permit node 40
apply tag 300
route-policy OSPF-PREFERENCE permit node 10
if-match tag 55
apply preference 12

return
e n
/
sysname R2
o m
acl number 2000
e i .c
aw
u
.h
acl number 2001
i n g
acl number 2010
r n
// lea
p :
t
acl number 2011
t
:h
#
e s
r c
ou
isis 1
cost-style wide
es
R
g
network-entity 10.0000.0000.0002.00
n i n
import-route ospf 1 route-policy OSPF-TO-ISIS
ar
e
#
or ip address 10.0.23.2 255.255.255.0
M isis enable 1
ip address 10.0.24.2 255.255.255.0
interface LoopBack0

ip address 10.0.2.2 255.255.255.255
ospf 1
import-route isis 1 route-policy ISIS-TO-OSPF
preference ase route-policy OSPF-PREFERENCE 150
e n
/
area 0.0.0.0
network 10.0.2.2 0.0.0.0
o m
network 10.0.24.0 0.0.0.255
e i .c
#
aw
u
.h
route-policy OSPF-TO-ISIS deny node 10
if-match tag 100
i n g
#
r n
// lea
p :
t
if-match acl 2000
t
:h
apply cost 500
apply tag 200

e s
r c
ou
#
es
R
g
if-match acl 2001
n i n
apply cost 100
ar
e
apply tag 200
e L #
or route-policy OSPF-TO-ISIS permit node 40
M apply tag 200
route-policy ISIS-TO-OSPF deny node 10
if-match tag 300

if-match acl 2010
apply cost 500
apply tag 400
e n
/
if-match acl 2011
apply cost 100
o m
apply tag 400
e i .c
#
aw
u
.h
apply tag 400
i n g
#
r n
route-policy OSPF-PREFERENCE permit node 10
// lea
p :
t
if-match tag 55
t
:h
apply preference 12
return
e s
r c
s ou
e
R
g
#
n i n
sysname R3
ar
e
#
e L isis 1
or cost-style wide
M network-entity 10.0000.0000.0003.00
import-route direct route-policy dirin
ip address 10.0.13.3 255.255.255.0
isis enable 1

ip address 10.0.23.3 255.255.255.0
isis enable 1
e n
/
ip address 192.168.1.1 255.255.255.0
o m
ip address 192.168.2.1 255.255.255.0 sub
e i .c
ip address 192.168.3.1 255.255.255.0 sub
aw
u
.h
ip address 192.168.4.1 255.255.255.0 sub
i n g
interface LoopBack0
r n
ip address 10.0.3.3 255.255.255.255
// lea
p :
t
isis enable 1
t
:h
#
e
route-policy dirin permit node 20s
r c
ou
if-match interface GigabitEthernet0/0/2
#
es
R
g
return
n i n
ar
e
e L #
or sysname R4
M #
acl number 2000
acl number 2001

traffic classifier serviceA operator or
if-match acl 2000
traffic classifier serviceB operator or
if-match acl 2001
e n
/
traffic behavior SAbeh
redirect ip-nexthop 10.0.45.5
o m
traffic behavior SBbeh
e i .c
aw
u
.h
#
traffic policy loadbalance
i n g
classifier serviceA behavior SAbeh
r n
classifier serviceB behavior SBbeh
// lea
p :
t
#
t
:h
link-protocol ppp
e s
r c
ou
ip address 10.0.45.4 255.255.255.0
#
es
R
g
n i n
link-protocol ppp
ar
e
ip address 10.0.54.4 255.255.255.0
e L #
or interface GigabitEthernet0/0/0
M ip address 10.0.14.4 255.255.255.0
traffic-policy loadbalance inbound
ip address 10.0.24.4 255.255.255.0
traffic-policy loadbalance inbound

interface LoopBack0
ip address 10.0.4.4 255.255.255.255
ospf 1
e n
/
area 0.0.0.0
network 10.0.4.4 0.0.0.0
o m
network 10.0.14.0 0.0.0.255
e i .c
network 10.0.24.0 0.0.0.255
aw
u
.h
area 0.0.0.1
network 10.0.45.0 0.0.0.255
i n g
network 10.0.54.0 0.0.0.255
r n
nssa no-summary
// lea
p :
t
#
t
:h
return
e s
r c
ou
#
es
R
g
sysname R5
#
n i n
ar
e
acl number 2000
e L rule 10 permit source 172.16.1.0 0.0.2.255
or acl number 2001
traffic classifier serviceA operator or
if-match acl 2000
traffic classifier serviceB operator or
if-match acl 2001

traffic behavior SAbeh
traffic behavior SBbeh
e n
/
#
traffic policy loadbalance
o m
classifier serviceA behavior SAbeh
e i .c
classifier serviceB behavior SBbeh
aw
u
.h
#
i n g
link-protocol ppp
r n
ip address 10.0.45.5 255.255.255.0
// lea
p :
t
#
t
:h
link-protocol ppp
e s
r c
ou
ip address 10.0.54.5 255.255.255.0
#
es
R
g
n i n
ip address 172.16.1.1 255.255.255.0
ar
e
ip address 172.16.2.1 255.255.255.0 sub
e L ip address 172.16.3.1 255.255.255.0 sub
or ip address 172.16.4.1 255.255.255.0 sub
M traffic-policy loadbalance inbound
interface LoopBack0
ip address 10.0.5.5 255.255.255.255
ospf 1

import-route direct route-policy dirin
area 0.0.0.1
network 10.0.5.5 0.0.0.0
network 10.0.45.0 0.0.0.255
network 10.0.54.0 0.0.0.255
e n
/
nssa no-summary
o m
route-policy dirin permit node 10
e i .c
if-match interface GigabitEthernet0/0/2
aw
u
.h
apply tag 55
i n g
return
r n
// lea
p :
t
Chapter 7 VLAN Hands-on Exercise Guide
t
Overview
s :h
r c e
The Virtual Local Area Network (VLAN) technology divides a physical LAN into
ou
multiple broadcast domains (VLANs). Hosts within a VLAN can communicate with each
s
other, whereas hosts in different VLANs cannot communicate with each other. As a result,
Re
broadcast packets are limited into each VLAN.
VLANs can be assigned based on ports, MAC addresses, IP subnets, network protocols,
g
and policies. Different VLAN packets are encapsulated using 802.1Q, differentiated based on
i n
the tag field, and processed according to port attributes.
n
There are enhanced features such as VLAN aggregation and MUX VLAN.
ar
e
Objectives
L
r e Upon completion of this exercise guide, you will be able to:
o  Explain VLAN assignment modes.
M
 Configure VLAN aggregation.
 Configure MUX VLAN.
 Configure inter-VLAN communication.
 Configure port isolation.
Tasks
The following topology shows the network of company A. Deploy the network
(1) Create VLANs 12, 13, 24, 112, 103, 212, 312, 334, 305, 401, and 402 on SW1, SW2,
SW3, and SW4.
(2) Add E0/0/1 and E0/0/2 on SW1 to VLAN 112 and E0/0/3 to VLAN 103.
(3) Add E0/0/1 and E0/0/2 on SW2 to VLAN 212.

(4) Add E0/0/1 and E0/0/2 on SW3 to VLAN 312, E0/0/3 and E0/0/4 to VLAN 334, and
E0/0/5 to VLAN 305.
(5) On SW4, add PC41 with the MAC address of 5489-98CF-447F and IP address of
4.1.1.1 to VLAN 401, and PC42 with the MAC address of 5489-98CF-E17D and IP
address of 4.2.2.2 to VLAN 402.
(6) On SW1, implement Layer 2 isolation and Layer 3 forwarding between VLAN 112 and
VLAN 103. Create VLAN 104 and assign the IP address of 1.0.0.254/24 to VLANIF
104.
(7) On SW2, implement Layer 2 isolation and Layer 3 connectivity between PC21 and
e n
/
PC22 in VLAN 212. Create VLAN 212 and assign the IP address of 2.0.0.254/24 to
VLANIF 212.
(8) On SW3, enable devices in VLAN 312 and VLAN 334 to communicate with devices in
o m
.c
VLAN 305. Enable isolation between VLAN 312 and VLAN 334, and prevent PC33
and PC34 in VLAN 334 from communicating with one another.
(9) On SW4, implement communication between VLAN 401 and VLAN 402. Assign IP
e i
addresses of 4.1.1.254/24 and 4.2.2.254/24 to VLANIF 401 and VLANIF 402.
aw
u
(10) Enable PCs in VLAN 312, VLAN 334, and VLAN 305 to exchange information with
.h
VLANIF 305 on SW4.
i n g
(11) Create VLANIF interfaces according to the network topology. Configure interface
attributes, and configure interfaces to allow VLANs 12, 13, 24, 112, 103, 212, 312, 334,
305, 、401 and 402.
r n
lea
(12) Run RIPv2 and disable RIP summarization on SW1, SW2, SW3, and SW4. Enable SW1
to advertise routes of VLANIF 12, VLANIF 13, and VLANIF 104 to RIPv2. Enable
: //
SW2 to advertise routes of VLANIF 12, VLANIF 24, and VLANIF 202 to RIPv2.
p
Enable SW3 to advertise routes of VLANIF 13 to RIP, and enable SW4 to advertise
t t
routes of VLANIF 24, VLANIF 305, VLANIF 401, and VLANIF 402 to RIPv2.
:h
Implement communication between the different network segments.
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M

Topology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
e
IP Address Table
r c
ou
Default
es Gateway
R VLANIF 12 12.1.1.1 255.255.255.0 N/A
ing
SW1 VLANIF 13 13.1.1.1 255.255.255.0 N/A
rn
VLANIF 104 1.0.0.254 255.255.255.0 N/A
e a VLANIF 12 12.1.1.2 255.255.255.0 N/A
eL
SW2 VLANIF 24 24.1.1.2 255.255.255.0 N/A
or
VLANIF 212 2.0.0.254 255.255.255.0 N/A
M
SW3 VLANIF 13 13.1.1.3 255.255.255.0 N/A
VLANIF 24 24.1.1.4 255.255.255.0 N/A
VLANIF 305 3.0.0.254 255.255.255.0 N/A
SW4
VLANIF 401 4.1.1.254 255.255.255.0 N/A
VLANIF 402 4.2.2.254 255.255.255.0 N/A
PC11 E0/0/1 1.0.0.1 255.255.255.0 N/A
PC12 E0/0/1 1.0.0.2 255.255.255.0 N/A
PC13 E0/0/1 1.0.0.3 255.255.255.0 N/A

PC21 E0/0/1 2.0.0.1 255.255.255.0 N/A

PC22 E0/0/1 2.0.0.2 255.255.255.0 N/A
PC31 E0/0/1 3.0.0.1 255.255.255.0 N/A
PC32 E0/0/1 3.0.0.2 255.255.255.0 N/A
PC33 E0/0/1 3.0.0.3 255.255.255.0 N/A
PC34 E0/0/1 3.0.0.4 255.255.255.0 N/A
PC35 E0/0/1 3.0.0.5 255.255.255.0 N/A
e n
PC41 E0/0/1 4.1.1.1 255.255.255.0 4.1.1.254
/
PC42 E0/0/1 4.2.2.2 255.255.255.0 4.2.2.254
o m
Configuration and Verification e i .c
awon SW1,
hu
1. Create VLANs 12, 13, 24, 112, 103, 212, 312, 334, 305, 、401 and 402
SW2, SW3, and SW4.
g .
ni n
Configure VLANs and run the display vlan summary command to check the summary
ar
of VLANs. The display on SW1 is used as an example. (The following table lists only key
e
information, and as such some information is omitted.)
l
[SW1]display vlan summary
: //
static vlan:
t tp
: h
s
Total 12 static vlan.
r c e
1 12 to 13 24 103 112 212 305 312 334
401 to 402
o u
e s
R
dynamic vlan:
n g
Total 0 dynamic vlan.
i
arn
reserved vlan:
L e Total 0 reserved vlan.
e
or 2.
Perform the configuration according to the requirements and prevent configuration
errors.
M Add E0/0/1 and E0/0/2 on SW1 to VLAN 112 and E0/0/3 to VLAN 103.
After this operation is performed, run the display vlan command to check information
about interfaces in VLANs. The display on SW1 is used as an example. (The following table
lists only key information, and as such some information is omitted.)
[SW1]display vlan
VID Type Ports
--------------------------------------------------------------------------------

1 common UT:Eth0/0/2(U) Eth0/0/4(D) Eth0/0/5(D) Eth0/0/6(D)
Eth0/0/7(D) Eth0/0/8(D) Eth0/0/9(D) Eth0/0/10(U)
Eth0/0/11(U) Eth0/0/12(D) Eth0/0/13(D) Eth0/0/14(D)
Eth0/0/15(D) Eth0/0/16(D) Eth0/0/17(D) Eth0/0/18(D)
e n
/
GE0/0/1(D) GE0/0/2(D)
12 common
o m
13 common
e i .c
24 common
aw
u
.h
103 common UT:Eth0/0/3(U)
112 common UT:Eth0/0/1(U) Eth0/0/2(U)
i n g
r n
To meet the requirements, use interface-based VLAN assignment.
l e a
Run the display vlan vlan id command to verify the result.
:
3. Add E0/0/1 and E0/0/2 on SW2 to VLAN 212.
//
t tp
h
about interface-based VLAN assignment. The display on SW2 is used as an example.
:
[SW2]display vlan
e s
VID Type Ports
r c
o u
s
--------------------------------------------------------------------------------
e
1
R
common UT:Eth0/0/3(D) Eth0/0/4(D) Eth0/0/5(D) Eth0/0/6(D)
i n g Eth0/0/7(D) Eth0/0/8(D) Eth0/0/9(D) Eth0/0/10(U)
arn Eth0/0/11(U) Eth0/0/12(D) Eth0/0/13(D) Eth0/0/14(D)
L e Eth0/0/15(D) Eth0/0/16(D) Eth0/0/17(D) Eth0/0/18(D)
e
or Eth0/0/19(D) Eth0/0/20(D) Eth0/0/21(D) Eth0/0/22(D)
M GE0/0/1(D) GE0/0/2(D)
12 common
13 common
24 common
103 common
112 common

Run the display vlan vlan id command to verify the result.
4. Add E0/0/1 and E0/0/2 on SW3 to VLAN 312, E0/0/3 and E0/0/4 to VLAN
334, and E0/0/5 to VLAN 305.
about VLAN assignment. The display on SW3 is used as an example.
[SW3]display vlan
e n
/
The total number of vlans is : 12
o m
--------------------------------------------------------------------------------
e i .c
w
U: Up; D: Down; TG: Tagged; UT: Untagged;
MP: Vlan-mapping; ST: Vlan-stacking;

u a
#: ProtocolTransparent-vlan; *: Management-vlan;
g .h
ni n
r
--------------------------------------------------------------------------------
lea
VID Type Ports
: //
p
--------------------------------------------------------------------------------
t t
:h
1 common UT:Eth0/0/6(D) Eth0/0/7(D) Eth0/0/8(D) Eth0/0/9(D)
es
Eth0/0/10(U) Eth0/0/11(U) Eth0/0/12(D) Eth0/0/13(D)
r c
ou
es
R
Eth0/0/22(D) GE0/0/1(D) GE0/0/2(D)
12
i n
commong
r n
e a
13 common
eL
24 common
or 103 common
M 112 common
212 common
5. On SW4, add PC41 with the MAC address of 5489-98CF-447F and IP

address of 4.1.1.1 to VLAN 401, and PC42 with the MAC address of
5489-98CF-E17D and IP address of 4.2.2.2 to VLAN 402.
After this operation is performed, run the display policy-vlan all command on SW4 to
check the current policy-based VLAN assignment.
[SW4]display policy-vlan all
------------------------------------------------------------------------
MacAddress IPAddress Port Vlan Priority
e n
/
------------------------------------------------------------------------
o m
5489-98cf-447f 4.1.1.1 NA 401 0
e i .c
w
5489-98cf-e17d 4.2.2.2 NA 402 0
u
------------------------------------------------------------------------a
g .h
VLANs can be assigned based on ports, MAC addresses, IP subnets, network protocols,
ni n
and policies. Determine the VLAN assignment mode according to the requirements. During
VLAN assignment, pay attention to interface attributes.
r
Run the display vlan command to verify the result.
a
6. On SW1, implement Layer 2 isolation andle
VLAN 112 and VLAN 103. Create VLAN/104
: / and assign the IP address of
Layer 3 forwarding between
1.0.0.254/24 to VLANIF 104.

t tp
: h
s
Note：when we want to forward packet between two separated different vlans, inter-vlan
r c e
arp-proxy need to be enabled.
After this operation is performed, run the display sub-vlan or display super-vlan
u
command on SW4 to check sub-VLANs or super-VLANs.
o
s
[SW1]display sub-vlan
e
VLAN ID
R Super-vlan
i n g
--------------------------------------------------------------------------------
a rn103 104
L e 112 104
e
or
M [SW1]display super-vlan
VLAN ID Sub-vlan
--------------------------------------------------------------------------------
104 103 112
After the configuration is complete, perform connectivity test for VLAN 112 and VLAN
103.
7. On SW2, implement Layer 2 isolation and Layer 3 connectivity between

PC21 and PC22 in VLAN 212. Create VLAN 212 and assign the IP address
of 2.0.0.254/24 to VLANIF 212.
Note：when we want to forward packet between two separated ports inside one vlan,
inner-vlan arp-proxy need to be enabled.
After this operation is performed, run the display port-isolate command to verify the
configuration.
[SW2]display port-isolate group all
The ports in isolate group 1:

e n
/
Ethernet0/0/1 Ethernet0/0/2
o m
.c
According to the requirement, isolation between VLANs needs to be configured. After
e i
this operation is performed, check whether PC21 can communicate with PC22.
devices in VLAN 305. Enable isolation between VLAN 312 and a

8. On SW3, enable devices in VLAN 312 and VLAN 334 to communicatew with
hu 312, and
VLAN 334,
implement communication between PC31 and PC32 in VLAN
g .
in
prevent PC33 and PC34 in VLAN 334 from communicating with one
n
another.
ar
e
After this operation is performed, check the results on SW4.
// l
:
[SW3]display mux-vlan
Principal Subordinate Type

t tp Interface
: h
s
-----------------------------------------------------------------------------
305 -
r c e
principal Ethernet0/0/5
305 334
o u separate Ethernet0/0/3 Ethernet0/0/4
e s
R
305 312 group Ethernet0/0/1 Ethernet0/0/2
n g
-----------------------------------------------------------------------------
i
r n Run the display vlan command to verify the result.
a
e IP addresses of 4.1.1.254/24 and 4.2.2.254/24 to VLANIF 401 and
L
9. On SW4, implement communication between VLAN 401 and VLAN 402.
e VLANIF 402.
Assign
or
M Note: for a PC to send packet to a destination out of the same network, the gateway
address should be configured on the PC.
After this operation is performed, run the ping command to check connectivity between
VLANs.
[PC41]ping 4.2.2.2

--- 4.2.2.2 ping statistics ---
5 packet(s) transmitted
e n
/
5 packet(s) received
0.00% packet loss
o m
round-trip min/avg/max = 16/22/31 ms
e i .c
between VLANs.
aw
You can use the router-on-a-stick and VLANIF interface to implement communication
huto exchange
10. Enable PCs in VLAN 312, VLAN 334, and VLAN 305
g .
n
information with VLANIF 305 on SW4.
ni
r
After this operation is performed, run the ping command to check connectivity between
a
e
VLANs.
// l
:
[PC31]ping 3.0.0.254
PING 3.0.0.254: 32
t tp
data bytes, press CTRL_C to break
: h
e s
c
r
o u
e s
R
n g
i
a rn--- 3.0.0.254 ping statistics ---
L e 5 packet(s) transmitted
e
or
M
0.00% packet loss
S4 becomes the gateway of the MUX VLAN to meet this requirement.
11. Create VLANIF interfaces according to the network topology. Configure

interface attributes, and configure the interfaces to allow VLANs 12, 13, 24,
112, 103, 212, 312, 334, 305, 401 and 402.
After this operation is performed, run the display vlan and display ip interface
commands to check information about VLANs and IP addresses. The display on SW1 is used
as an example. (The following table lists only key information, and as such some information
is omitted.)
[SW1]display vlan
--------------------------------------------------------------------------------
e n
/
o m
--------------------------------------------------------------------------------
e i .c
VID Type Ports
aw
u
.h
--------------------------------------------------------------------------------
1 common UT:Eth0/0/4(D) Eth0/0/5(D) Eth0/0/6(D)
i n g Eth0/0/7(D)
Eth0/0/8(D) Eth0/0/9(D)
r n
Eth0/0/10(U) Eth0/0/11(U)
Eth0/0/12(D) Eth0/0/13(D)
// lea
Eth0/0/14(D) Eth0/0/15(D)
p :
t
t
:h
Eth0/0/20(D) Eth0/0/21(D) Eth0/0/22(D) GE0/0/1(D)
GE0/0/2(D)
e s
r c
ou
12 common TG:Eth0/0/10(U) Eth0/0/11(U)
13 common
es
TG:Eth0/0/10(U) Eth0/0/11(U)
R
g
103
n i
sub n UT:Eth0/0/3(U)
ar
e
TG:Eth0/0/10(U) Eth0/0/11(U)
e L 104 super
or 112 sub UT:Eth0/0/1(U) Eth0/0/2(U)
M TG:Eth0/0/10(U) Eth0/0/11(U)

[SW1]display ip interface brief
Interface IP Address/Mask Physical Protocol
e n
/
Vlanif12 12.1.1.1/24 up up
Vlanif13 13.1.1.1/24 up up
o m
Vlanif104 1.0.0.254/24 up
e i up
.c
12. Run RIPv2 and disable RIP summarization on SW1, SW2, SW3, w
Enable SW1 to advertise routes of VLANIF 12, VLANIF 13, u aandVLANIF
SW4.
104 to RIPv2. Enable SW2 to advertise routes of VLANIF.h

and
g
12, VLANIF 24,
RIP, and enable SW4 to advertise routes of VLANIF

n n
i communication
and VLANIF 202 to RIPv2. Enable SW3 to advertise routes of VLANIF 13 to
24, VLANIF 305,
VLANIF 401, and VLANIF 402 to RIPv2. Implement
ar of
different network segments.
/ l e
: /
tp
After this operation is performed, run the display ip routing-table command to check
ht
information about routes. The display on SW1 is used as an example. (The following table
lists only key information, and as such some information is omitted.) Once verified, perform
the ping operation.
s :
c e
[SW1]display ip routing-table
r
Destination/Mask
o u Proto Pre Cost Flags NextHop Interface
e s
R
1.0.0.0/24 Direct 0 0 D 1.0.0.254 Vlanif104
i n g
2.0.0.0/24 RIP 100 1 D 12.1.1.2 Vlanif12
rn
3.0.0.0/24 RIP 100 2 D 12.1.1.2 Vlanif12
e a
L
4.1.1.0/24 RIP 100 2 D 12.1.1.2 Vlanif12
e
or
4.2.2.0/24 RIP 100 2 D 12.1.1.2 Vlanif12
M
12.1.1.0/24 Direct 0 0 D 12.1.1.1 Vlanif12
13.1.1.0/24 Direct 0 0 D 13.1.1.1 Vlanif13
24.1.1.0/24 RIP 100 1 D 12.1.1.2 Vlanif12
[PC11]ping 3.0.0.2

e n
/
o m
e i .c
0.00% packet loss
aw
u
.h
Questions
i n g
r n
lea
Can multiple MAC addresses and IP addresses be associated with one VLAN for
//
requirement 5?
:
For requirement 10, why is VLANIF 305 on SW4 used as the gateway? Can an IP
p
t
address be configured in the MUX VLAN?
t
:h
Configuration List
e s
r c
<SW1>display current-configuration
s ou
sysname SW1
Re
#
i n g
r n
vlan batch 12 to 13 24 103 to 104 112 212 305 312 334 401 to 402
e a
eL
#
or
vlan 104
M aggregate-vlan
access-vlan 103 112
interface Vlanif12
ip address 12.1.1.1 255.255.255.0

interface Vlanif13
ip address 13.1.1.1 255.255.255.0
interface Vlanif104
ip address 1.0.0.254 255.255.255.0
e n
/
arp-proxy inter-sub-vlan-proxy enable
o m
e i .c
port link-type access
aw
u
.h
port default vlan 112
i n g
r n
// lea
p :
t
t
:h
#
e s
r c
ou
es
R
g
#
n i n
ar
e
port link-type trunk
e L port trunk allow-pass vlan 12 to 13 24 103 112 212 305 312 334 401 to 402
or #
M interface Ethernet0/0/11
port trunk allow-pass vlan 12 to 13 24 103 112 212 305 312 334 401 to 402
rip 1
undo summary

version 2
network 12.0.0.0
network 13.0.0.0
network 1.0.0.0
e n
/
return
o m
e i .c
#
aw
u
.h
sysname SW2
i n g
vlan batch 12 to 13 24 103 112 212 305 312 334 401 to 402
r n
#
// lea
p :
t
interface Vlanif12
t
:h
ip address 12.1.1.2 255.255.255.0
#
e s
r c
ou
interface Vlanif24
es
ip address 24.1.1.2 255.255.255.0
R
g
#
n i n
interface Vlanif212
ar
e
ip address 2.0.0.254 255.255.255.0
e L arp-proxy inner-sub-vlan-proxy enable
or #
port-isolate enable group 1

port-isolate enable group 1
e n
/
o m
#
e i .c
aw
u
.h
n g
i
#
r n
rip 1
// lea
p :
t
undo summary
t
:h
version 2
network 12.0.0.0
e s
r c
ou
network 24.0.0.0
network 2.0.0.0
es
R
g
#
n
return
i n
ar
Le
e
or #
M sysname SW3
vlan batch 12 to 13 24 103 112 212 305 312 334 401 to 402
vlan 305
mux-vlan

subordinate separate 334
subordinate group 312
interface Vlanif13
ip address 13.1.1.3 255.255.255.0
e n
/
#
o m
e i .c
aw
u
.h
port mux-vlan enable
i n g
r n
// lea
p :
t
t
:h
#
e s
r c
ou
es
R
g
n i n
ar
e
#
e L interface Ethernet0/0/4
or port link-type access
M port default vlan 334

e n
/
o m
e i .c
aw
u
.h
i n g
rip 1
r n
undo summary
// lea
p :
t
version 2
t
:h
network 13.0.0.0
#
e s
r c
ou
return
es
R
g
#
n i n
ar
e
sysname SW4
e L #
or vlan batch 12 to 13 24 103 112 212 305 312 334 401 to 402
M #
vlan 401
policy-vlan mac-address 5489-98cf-447f ip 4.1.1.1
vlan 402
policy-vlan mac-address 5489-98cf-e17d ip 4.2.2.2

interface Vlanif24
ip address 24.1.1.4 255.255.255.0
interface Vlanif305
ip address 3.0.0.254 255.255.255.0
e n
/
#
interface Vlanif401
o m
ip address 4.1.1.254 255.255.255.0
e i .c
#
aw
u
.h
interface Vlanif402
ip address 4.2.2.254 255.255.255.0
i n g
#
r n
// lea
p :
t
port hybrid pvid vlan 401
t
:h
port hybrid untagged vlan 401
#
e s
r c
ou
es
port hybrid pvid vlan 402
R
g
port hybrid untagged vlan 402
#
n i n
ar
e
e L port link-type access
or port default vlan 305
M #
rip 1

undo summary
version 2
network 24.0.0.0
network 3.0.0.0
network 4.0.0.0
e n
/
#
return
o m
e i .c
Chapter 8 LAN Layer 2 Technology Hands-on Exercise
aw
hu
Guide
g .
Overview
ni n
ar
LAN Layer 2 technologies include the Address Resolution Protocol (ARP), Media
l e
Access Control (MAC), Ethernet link aggregation, and Generic Attribute Registration
//
Protocol (GARP) VLAN Registration Protocol (GVRP).
:
tp
ARP maps IP addresses to MAC addresses. Proxy ARP solves network connectivity
t
problems. Gratuitous ARP enables a host to send an ARP Request packet using its own IP
: h
address as the destination address.
A MAC address defines the position of a network device. A MAC address consists of 48
e s
bits and is displayed as a 12-digit hexadecimal number. Bits 0 to 23 are assigned by IETF and
r c
other institutions to identify vendors, and bits 24 to 47 are the unique ID assigned by vendors
o u
to identify their network adapters.
Ethernet link aggregation bundles multiple physical links to form a logical link to
es
increase link bandwidth, improve reliability, and implement load balancing.
R
Through GARP, GVRP is used to dynamically maintain VLAN attributes on devices.
g
GVRP propagates VLAN attributes of one device throughout the entire switching network.
i n
GVRP enables network devices to dynamically deliver, register, and propagate VLAN
rn
attributes, thereby reducing workload of the network administrator and ensuring correct
configuration.
e a
L
Objectives
ore 
M
Configure ARP broadcast.
 Configure the MAC address table.
 Configure link aggregation.
 Configure GVRP.
Tasks
The following topology shows the network of company A. Deploy the network
(1) Create VLAN 12 and VLAN 21 on SW1 and SW2, and create VLAN 34 on SW3 and SW4.
(2) On SW2, add E0/0/11 to VLAN 12 and E0/0/12 to VLAN 21; add E0/0/13 on SW3 to VLAN
34; add E0/0/14 on SW4 to VLAN 34.
(3) Configure static LACP between SW1 and SW2, configure SW1 as the Actor and the link
connected to E0/0/2 as the backup link, and set the timeout interval to 3 seconds.
(4) Configure interconnected interfaces of switches as trunk interfaces and configure them to
allow all VLANs.
(5) Enable GVRP on each switch, SW3 never learn the VLAN information carried by GVRP, and
implement communication between PC3 and PC4.
(6) Implement communication between PC1 and PC2 through R1.
(7) Set the maximum number of MAC addresses learned by E0/0/13 on SW3 to 2, and configure
an interface in error-down state and enable the device to generate alarms when the number of
n
learned MAC addresses reaches the limit. There is no need to consider MAC address loss
after device restart.
/ e
Topology
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
IP Address Table Re
i n g Default
r n
a
Gateway
L e R1
G0/0/1.1 12.1.1.254 255.255.255.0 N/A
r e G0/0/1.2 21.1.1.254 255.255.255.0 N/A
o PC1 / 12.1.1.1 255.255.255.0 12.1.1.254
M PC2 / 21.1.1.1 255.255.255.0 21.1.1.254

PC3 / 34.1.1.3 255.255.255.0 N/A
PC4 / 34.1.1.4 255.255.255.0 N/A
1. Create VLAN 12 and VLAN 21 on SW1 and SW2, and create VLAN 34 on
SW3 and SW4.

After this operation is performed, run the display vlan summary command to check the
summary of VLANs. The display on SW2 is used as an example.
[SW2]display vlan summary
static vlan:
Total 3 static vlan.
1 12 21
e n
/
dynamic vlan:
Total 0 dynamic vlan.
o m
reserved vlan:
e i .c
Total 0 reserved vlan.
aw
2. On SW2, add E0/0/11 to VLAN 12 and E0/0/12 to VLAN 21;hadd u E0/0/13 on
g .
n
SW3 to VLAN 34; add E0/0/14 on SW4 to VLAN 34.
ni
r
a
e
about interfaces and VLANs. The display on SW2 is used as an example. (The following
// l
table lists only key information, and as such some information is omitted.)
:
tp
[SW2]display vlan
h
t
s :
e
--------------------------------------------------------------------------------
r c
u
s o
Re
i n g
--------------------------------------------------------------------------------
arn
VID Type Ports
L e
e
--------------------------------------------------------------------------------
or 1 common UT:Eth0/0/1(U) Eth0/0/2(U) Eth0/0/3(U) Eth0/0/4(U)
M Eth0/0/5(D) Eth0/0/6(D) Eth0/0/7(D) Eth0/0/8(D)
GE0/0/1(D) GE0/0/2(D)

3. Configure static LACP between SW1 and SW2, configure SW1 as the Actor
and the link connected to E0/0/2 as the backup link, and set the timeout
interval to 3 seconds.
After this operation is performed, run the display eth-trunk command to check link
aggregation information. The display on SW1 is used as an example.
[SW1]display eth-trunk 12
e n
/
Eth-Trunk12's state information is:
o m
Local:
e i .c
LAG ID: 12 WorkingMode: STATIC
aw
u
.h
Preempt Delay: Disabled Hash arithmetic: According to SIP-XOR-DIP
System Priority: 0 System ID: 4c1f-cc3f-01c3
i n g
Least Active-linknumber: 1 Max Active-linknumber: 1
r n
Operate status: up
lea
Number Of Up Port In Trunk: 1
//
p :
--------------------------------------------------------------------------------
t t
:h
ActorPortName Status PortType PortPri PortNo PortKey PortState Weight
Ethernet0/0/1
e s
Selected 1000TG 32768 2 3217 11111100 1
r c
ou
Ethernet0/0/2 Unselect 1000TG 65535 3 3217 11100000 1
Partner:
es
R
--------------------------------------------------------------------------------
i n g
ActorPortName SysPri SystemID PortPri PortNo PortKey PortState
r n
e a
Ethernet0/0/1 32768 4c1f-cc3b-8582 32768 2 3217 11111100
eL
Ethernet0/0/2 32768 4c1f-cc3b-8582 32768 3 3217 11110000
or When configuring link aggregation, notice that the LACP timeout interval can use fast
M
and slow modes.
Run the display interface eth-trunk and display trunkfwdtbl eth-trunk commands to
verify the result:
4. Configure interconnected interfaces of switches as trunk interfaces and

configure them to allow all VLANs.
After this operation is performed, run the display vlan command to check VLAN
information of SW2.
[SW2]display vlan

--------------------------------------------------------------------------------
e n
/
--------------------------------------------------------------------------------
VID Type Ports
o m
--------------------------------------------------------------------------------
e i .c
1 common UT:Eth0/0/3(U) Eth0/0/4(U) Eth0/0/5(D)
w
Eth0/0/6(D)
a
u
.h
Eth0/0/13(D) Eth0/0/14(D) Eth0/0/15(D)
i n gEth0/0/16(D)
Eth0/0/17(D) Eth0/0/18(D)
r n
Eth0/0/19(D) Eth0/0/20(D)
Eth0/0/21(D) Eth0/0/22(D)
// lea
GE0/0/1(D) GE0/0/2(D)
p :
t
Eth-Trunk12(U)
t
:h
TG:Eth0/0/3(U)
e s Eth0/0/4(U) Eth-Trunk12(U)
r c
ou
e sTG:Eth0/0/3(U) Eth0/0/4(U) Eth-Trunk12(U)
Ron each switch, SW3 never learn the vlan information carried
n
5. Enable GVRP
i g
rn
by GVRP, and implement communication between PC3 and PC4.
e aAfter this operation is performed, run the display gvrp statistics command to check
e L GVRP statistics about SW3.
or
[SW3]display gvrp statistics
M
GVRP statistics on port Ethernet0/0/3
GVRP status : Enabled
GVRP registrations failed : 46
GVRP last PDU origin : 4c1f-cc3b-8582
GVRP registration type : Fixed

[PC4]ping 34.1.1.3
e n
/
o m
e i .c
aw
u
.h
0.00% packet loss
i n g
r n
lea
Notice that GVRP provides three registration modes. GVRP provides different
: //
functions in different modes. Configure a registration mode according to the requirements.
p
Run the following command to verify the result:
display gvrp status
t t
: hPC1 and PC2 through R1.
s
6. Implement communication between
r c e
After this operation is performed, perform the ping operation on PC1.
o u
[PC1]ping 21.1.1.1
es
R
i n g
rn
e a
L
e
or
M
0.00% packet loss
You can use the router-on-a-stick and VLANIF interface to implement communication
between VLANs. Select a technique according to the requirements.
7. Set the maximum number of MAC addresses learned by E0/0/13 on SW3 to

2, and configure an interface in error-down state and enable the device to
generate alarms when the number of learned MAC addresses reaches the
limit. There is no need to consider MAC address loss after device restart.
After this operation is performed, perform the ping operation on PC3.
n
[SW3]display mac-address security vlan 34
MAC address table of slot 0:

/ e
o m
.c
-------------------------------------------------------------------------------
MAC Address VLAN/ PEVLAN CEVLAN Port Type

e i
LSP/LSR-ID
VSI/SI MAC-Tunnel
aw
u
.h
-------------------------------------------------------------------------------
g
5489-98cf-3447 34 - - Eth0/0/13
i n
security
n
-
r
lea
-------------------------------------------------------------------------------
Total matching items on slot 0 displayed = 1

: //
t p
The port security function changes MAC addresses learned on an interface into secure
t
:h
dynamic MAC addresses and sticky MAC addresses. There are differences between secure
dynamic MAC addresses and sticky MAC addresses in terms of aging and MAC address loss
after device restart.
e s
r c
ou
Questions
es
How are packets forwarded when the router-on-a-stick method is used?
Configuration List R
i n g
arn<R1>display current-configuration
L e #
ore sysname R1
M #
interface GigabitEthernet0/0/1.1
dot1q termination vid 12
ip address 12.1.1.254 255.255.255.0

arp broadcast enable
interface GigabitEthernet0/0/1.2
dot1q termination vid 21
ip address 21.1.1.254 255.255.255.0
e n
/
arp broadcast enable
o m
return
e i .c
aw
u
.h
i n g
sysname SW1
r n
#
// lea
p :
t
vlan batch 12 21
t
:h
#
gvrp
e s
r c
ou
#
lacp priority 0
es
R
g
#
n i n
interface Eth-Trunk12
ar
e
e L port trunk allow-pass vlan 2 to 4094
or mode lacp-static
M lacp timeout fast
max active-linknumber 1
gvrp
eth-trunk 12

eth-trunk 12
lacp priority 65535
e n
/
o m
port trunk allow-pass vlan 2 to 4094
e i .c
#
aw
u
.h
return
i n g
r n
#
// lea
p :
t
sysname SW2
t
:h
#
vlan batch 12 21
e s
r c
ou
#
gvrp
es
R
g
#
n i n
interface Eth-Trunk12
ar
e
or mode lacp-static
M lacp timeout fast
gvrp
eth-trunk 12

eth-trunk 12
e n
/
gvrp
o m
#
e i .c
aw
u
.h
i n g
gvrp
r n
#
// lea
p :
t
t
:h

e s
r c
ou
#
es
R
g
n i n
ar
e
#
e L return
or
M <SW3>display current-configuration
sysname SW3
vlan batch 34

gvrp
e n
/
gvrp
gvrp registration fixed
o m
#
e i .c
aw
u
.h
i n g
port-security enable
r n
port-security protect-action shutdown
// lea
p :
t
port-security max-mac-num 2
t
:h
#
return
e s
r c
s ou
e
R
g
#
n i
sysname SW4n
ar
e
#
e L vlan batch 34
or #
M gvrp
gvrp

e n
/
return
o m
Chapter 9 WAN Layer 2 Technology Hands-on Exercisei.c
Guide
we
a
Overview
. hu
i n g
This document introduces Wide Area Network (WAN) Layer 2 technologies, including
r n
Point-to-Point Protocol (PPP), Multilink PPP (MP), PPP over Ethernet (PPPoE), and Frame
Relay (FR).
l e a
PPP is used at the data link layer for point-to-point data transmission over full-duplex
: //
synchronous and asynchronous links. It consists of the Link Control Protocol (LCP),
tp
Network Control Protocol (NCP), Challenge-Handshake Authentication Protocol (CHAP),
t
and Password Authentication Protocol (PAP).
h
MP binds multiple PPP links to increase link bandwidth. MP fragments the packets
:
s
whose length is greater than the minimum packet length and then sends the fragments to the
r c e
peer device over multiple PPP links in the MP-Group. After receiving these fragments, the
peer device assembles these packets and then sends them to the network layer. MP can be
o u
implemented by using virtual template (VT) interfaces or MP-Group interfaces.
PPPoE is a network protocol that encapsulates PPP frames into Ethernet frames. PPPoE
es
enables multiple hosts on an Ethernet to connect to a broadband remote access server
R
(BRAS), implementing access control and charging on a per-host basis.
g
FR is a statistical multiplexing protocol that is applicable to charge burst traffic. In
i n
addition, FR can also dynamically allocate network resources.
a rn
Objectives
L e Upon completion of this exercise guide, you will be able to:

e
or
 Configure MP.
 Configure PPPoE.

M Tasks
Configure FR.
(1) Bind PPP links between R1 and R4, and disable the MP-Group mode. For details
about the interface name and IP address, see the "IP Address Table".
(2) Configure R1 as the PPPoE server and R5 as the PPPoE client. Enable the PPPoE
server to allocate the IP address 15.1.1.5 to the PPPoE client. Configure the PPPoE
server to authenticate the PPPoE client using PAP, with the user name R5 and
password HUAWEI.
(3) Disable InARP on FR links between R1 and R2 and between R1 and R3. R1 and
R2 can communicate over the network segment 12.1.1.0/24, while R1 and R3 can
communicate over the network segment 23.1.1.0/24. Sub-interfaces cannot be
created.
(4) Run Intermediate System to Intermediate System (IS-IS) on R1, R2, R3, and R4,
set the area to 47.0000, the system ID to 0000.0000.000X, and the IS-IS level to
Level-2, implementing interworking between addresses in the "IP Address Table".
Topology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
:h
IP Address Table
e s Default
Device
r c
Interface IP Address Subnet Mask
ou
Gateway
s
VT12 12.1.1.1 255.255.255.0 N/A
Re VT13 13.1.1.1 255.255.255.0 N/A
ing
R1 VT14 14.1.1.1 255.255.255.0 N/A
rn
VT15 15.1.1.1 255.255.255.0 N/A
e a Loopback 0 10.1.1.1 255.255.255.255 N/A
eL
VT12 12.1.1.2 255.255.255.0 N/A
R2
or
Loopback 0 10.2.2.2 255.255.255.255 N/A
VT13 13.1.1.3 255.255.255.0 N/A
M R3
Loopback 0 10.3.3.3 255.255.255.255 N/A
VT14 14.1.1.4 255.255.255.0 N/A
R4
Loopback 0 10.4.4.4 255.255.255.255 N/A
1. Bind PPP links between R1 and R4, and disable the MP-Group mode. For
details about the interface name and IP address, see the "IP Address Table."

After completing this task, run the display ppp mp command to view the MP binding
information. The following uses the display of R1 as an example. The table shows only key
[R1]display ppp mp
Template is Virtual-Template14
Bundle 22645b08be91, 2 members, slot 0, Master link is Virtual-Template14:0
0 lost fragments, 0 reordered, 0 unassigned,
e n
/
m
sequence 0/0 rcvd/sent
The bundled sub channels are:

.c o
Serial2/0/0
e i
aw
Serial2/0/1
u
MP can be implemented by using MP-Group interfaces or VT interfaces.
g .h
n
display interface virtual-template
n i
2. Configure R1 as the PPPoE server and R5 as therPPPoE client. Enable the
l e a to the PPPoE client.
// the PPPoE client using PAP,
PPPoE server to allocate the IP address 15.1.1.5
:
Configure the PPPoE server to authenticate
t tp
with the user name R5 and password HUAWEI.
: h
After completing this task, run the display pppoe-server session/display ip interface
e s
brief command to view information about the PPPoE server and IP address of the client. The
r c
following table shows information of R1 and R5. The table shows only key information,
u
o
e s
[R1]display pppoe-server session all
SID Intf
R State OIntf RemMAC LocMAC
1
i n g
Virtual-Template15:0 UP GE0/0/0 00e0.fc03.b392 00e0.fc03.ab7f
arn
L e [R5]display ip interface brief
e
or
Interface IP Address/Mask Physical Protocol
M Dialer15 15.1.1.5/32 up up(s)
GigabitEthernet0/0/0 unassigned up down
display pppoe-client session
3. Disable InARP on FR links between R1 and R2 and between R1 and R3. R1

and R2 can communicate over the network segment 12.1.1.0/24, while R1
and R3 can communicate over the network segment 23.1.1.0/24.
Sub-interfaces cannot be created.
After completing this task, run the display fr map-info command to view FR address
mapping information. The following table shows information on R1.
[R1]display fr map-info
Map Statistics for interface Serial1/0/0 (DTE)
DLCI = 102, PPP over FR Virtual-Template12, Serial1/0/0
create time = 2013/09/18 19:22:33, status = ACTIVE
e n
/
encapsulation = ietf, vlink = 0
DLCI = 103, PPP over FR Virtual-Template13, Serial1/0/0
o m
create time = 2013/09/18 19:22:41, status = ACTIVE
e i .c
encapsulation = ietf, vlink = 0
aw
u
FR links can transmit multiple types of packets, such as IP packets and PPP packets. As
this task.
g .h
sub-interfaces cannot be created, another method should be used to meet the requirement in
i n
n the interworking
a r
4. Run IS-IS on R1, R2, R3, and R4, set the area to 47.0000, system ID to
between addresses in the "IP Address Table".le

0000.0000.000X, and the IS-IS level to Level-2, implementing
: //
tp
t
h
view IS-IS routing information on R1.
s :
Destination/Mask
r c e
Proto Pre Cost Flags NextHop Interface
o
10.2.2.2/32u ISIS-L2 15 10 D 12.1.1.2 Virtual-Template12
e s
R
10.3.3.3/32 ISIS-L2 15 10 D 13.1.1.3 Virtual-Template13
i n g
10.4.4.4/32 ISIS-L2 15 10 D 14.1.1.4 Virtual-Template14
rn
IS-IS does not apply to FR links. To enable IS-IS on FR links, you need to configure
e a sub-interfaces or PPP over FR (PPPoFR).
e L
Questions
or What are the characteristics of VT interfaces?
M Configuration List
sysname R1

aaa
authentication-scheme default
authorization-scheme default
accounting-scheme default
domain default
e n
/
domain default_admin
local-user r5 password cipher %$%$wgCcG9i@%B0!z/SzyC&,S2fp%$%$
o m
local-user r5 service-type ppp
e i .c
local-user admin password cipher %$%$K8m.Nt84DZ}e#<0`8bmE3Uw}%$%$
aw
u
.h
local-user admin service-type http
i n g
isis 1
r n
is-level level-2
// lea
p :
t
network-entity 47.0000.0000.0000.0001.00
t
:h
#
e s
r c
ou
link-protocol fr
undo fr inarp
es
R
g
fr map ppp interface Virtual-Template12 102
n i n
ar
e
#
e L interface Serial2/0/0
or link-protocol ppp
M ppp mp Virtual-Template 14
link-protocol ppp
ppp mp Virtual-Template 14

interface Virtual-Template12
ip address 12.1.1.1 255.255.255.0
isis enable 1
e n
/
ip address 13.1.1.1 255.255.255.0
isis enable 1
o m
#
e i .c
aw
u
.h
ip address 14.1.1.1 255.255.255.0
isis enable 1
i n g
#
r n
// lea
p :
t
ppp authentication-mode pap
t
:h
remote address 15.1.1.5
e
ip address 15.1.1.1 255.255.255.0s
r c
ou
#
es
R
g
pppoe-server bind Virtual-Template 15
#
n i n
ar
e
interface LoopBack0
e L ip address 10.1.1.1 255.255.255.255
or isis enable 1
M #
return
sysname R2

isis 1
is-level level-2
network-entity 47.0000.0000.0000.0002.00
e n
/
link-protocol fr
o m
undo fr inarp
e i .c
aw
u
.h
#
i n g
ip address 12.1.1.2 255.255.255.0
r n
isis enable 1
// lea
p :
t
#
t
:h
interface LoopBack0
e s
ip address 10.2.2.2 255.255.255.255
r c
ou
isis enable 1
#
es
R
g
return
n i n
ar
e
e L #
or sysname R3
M #
isis 1
is-level level-2
network-entity 47.0000.0000.0000.0003.00

link-protocol fr
undo fr inarp
e n
/
ip address 13.1.1.3 255.255.255.0
isis enable 1
o m
#
e i .c
interface LoopBack0
aw
u
.h
ip address 10.3.3.3 255.255.255.255
isis enable 1
i n g
#
r n
return
// lea
p :
t t
:h
#
e s
r c
ou
sysname R4
#
es
R
g
isis 1
n i n
is-level level-2
ar
e
network-entity 47.0000.0000.0000.0004.00
e L #
or interface Serial2/0/0
M link-protocol ppp
link-protocol ppp

ip address 14.1.1.4 255.255.255.0
isis enable 1
e n
/
interface LoopBack0
ip address 10.4.4.4 255.255.255.255
o m
isis enable 1
e i .c
#
aw
u
.h
return
i n g
r n
#
// lea
p :
t
sysname R5
t
:h
#
firewall zone Local

e s
r c
ou
priority 15
#
es
R
g
interface Dialer15
n i n
link-protocol ppp
ar
e
ppp pap local-user R5 password cipher %$%$>*9p9daA=1eVjFUnm!D9,Q[3%$%$
e L ip address ppp-negotiate
or dialer user R5
M dialer bundle 1
pppoe-client dial-bundle-number 1
return

Chapter 10 STP Hands-on Exercise Guide

Overview
STP prevents loops at the data link layer. It uses BPDUs to transmit STP information,
calculate a loop-free tree network topology and block a specified port. When a network fault
n
occurs, STP can detect the fault and use another path to transmit data. STP exchanges BPDUs
to select the root switch; each non-root-switch selects the root port to communicate with the
root switch; the designated port is selected on each network segment to forward data to the / e
o
root switch; the remaining ports, that is, ports not selected as the root and designated ports,
m
.c
are blocked.
e i
STP can prevent loops, but there are disadvantages. STP does not differentiate port
statuses and roles in a fine-granular manner. It defines five ports statuses and has slow
aw
convergence. For users, there are no differences between ports in Listening, Learning, and
u
Blocking states. Ports in Listening, Learning, and Blocking states do not forward traffic.
.h
RSTP is an extension based on STP, and when compared to STP has two additional port roles.
g
RSTP defines four port rules: root port, designated port, alternate port, and backup port.
i n
RSTP defines the port status based on whether the port forwards user traffic and learns MAC
n
addresses. If a port neither forwards user traffic nor learns MAC addresses, the port is in
r
lea
Discarding state. If a port does not forward user traffic but learns MAC addresses, the port is
in Learning state. If a port forwards user traffic and learns MAC addresses, the port is in
//
Forwarding state. RSTP uses the Proposal/Agreement mechanism, fast switching of the root
port, and edge port to implement fast convergence.
p :
t t
RSTP, an enhancement to STP, implements fast convergence of the network topology.
:h
There is a defect for both RSTP and STP: All VLANs on a LAN use one spanning tree, and
VLAN-based load balancing cannot be performed. Once a link is blocked, it will no longer
e s
transmit traffic, wasting bandwidth and causing the failure in forwarding certain VLAN
c
packets. MSTP can be used to address this issue.
r
ou
MSTP divides a switching network into multiple regions, each of which has multiple
spanning trees that are independent of one another. Each region is called MST region and
s
each spanning tree is called an MSTI. An MSTI can contain multiple VLANs. Binding
e
R
multiple VLANs to one MSTI reduces communication costs and resource usage. The
topology of each MSTI is calculated independently, and traffic can be balanced among
MSTIs.
i n g
Objectivesn
a r
L e Upon completion of this exercise guide, you will be able to:
e  Perform basic configurations of STP, RSTP, and MSTP.
or
 Configure MSTIs.
 Configure multiple MST regions.
M  Configure protection functions.
 Configure BPDU filtering.
 Explain election principles of STP, RSTP, and MSTP.
Tasks
The following topology shows the Layer 2 network of a company. SW1 and SW2 are
core switches. Deploy the network according to the following requirements:
(1) Configure the latest spanning tree protocol on the four switches, configure VLAN 10 and
VLAN 20 for service A, configure VLAN 30 and VLAN 40 for service B, and configure
management VLANs 50 and 60. Configure the four switches to allow the preceding VLANs.
Service A, Service B and management VLANs calculate the path separately.

(2) Optimize the network to implement load balancing. Ensure that different topologies are used
for services A and B:ServiceA use SW1 as root, Service B use SW2 as root, when the root
switch in any topology fails, the new root switch should be the core device (SW1, SW2 works
as the core device, SW3, SW4 works as the access device.)
(3) The spanning tree region configuration on SW1, SW2, and SW3 are different from that on
SW4 due to configuration errors or other causes. Ensure that SW4 can access VLANs on
other switches through SW1 user the link with even number.
(4) Use port priority to Configure SW1 and SW2 to use different links to transmit services A and
n
B, implementing redundancy.
(5) Ensure that SW3 and SW4 will never be the root switch of the network.
(6) Configure the ports eth0/0/7 of SW2 operate in Forwarding state when faulty links recover,
/ e
and provide solutions if there are risks to devices such as rogue switches connected to user
o m
.c
ports.
during one hello interval.

e i
(7) To save the CPU resources, configure the two core switches to respond the TC-BPDU twice
(8) To reduce the convergence time of MSTP, configure the link between switches as
aw
u
point-to-point.
Topology
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M IP Address Table
Default
Gateway
PC1 G 0/0/7 10.0.1.1 255.255.255.0 N/A
PC2 G 0/0/7 10.0.1.2 255.255.255.0 N/A
PC3 G 0/0/7 20.0.1.1 255.255.255.0 N/A

1. Configure the latest spanning tree protocol on the four switches, configure
VLAN 10 and VLAN 20 for service A, configure VLAN 30 and VLAN 40 for
service B, and configure management VLANs 50 and 60. Configure the four
switches to allow the preceding VLANs. Service A, Service B and
management VLANs calculate the path separately.
Note: Latest STP means MSTP, configure links as trunk links, and configure the links to
e n
allow all VLANs. Need to use multi-instance.
/
[SW1] display stp region-configuration
o m
Oper configuration
e i .c
Format selector :0
aw
u
.h
Region name :1
Revision level :0
i n g
Instance VLANs Mapped
r n
0
// lea
1 to 9, 11 to 19, 21 to 29, 31 to 39, 41 to 4094
p :
t
1 10, 20
t
:h
2 30, 40
e s
2.
c
Optimize the network to implement load balancing. Ensure that different
r
ou
topologies are used for services A and B:ServiceA use SW1 as root, Service B
s
use SW2 as root, when the root switch in any topology fails, the new root
Re
switch should be the core device (SW1, SW2 works as the core device, SW3,
SW4 works as the access device.)
i n g
Note: Configure multiple MSTIs and adjust the root switch in different MSTIs.
r n
3.
a
The spanning tree region configuration on SW1, SW2, and SW3 are different
e
e L from that on SW4 due to configuration errors or other causes. Ensure that
SW4 can access VLANs on other switches through SW1 user the link with
or even number.
M Note: Configure multiple MST regions. Use port priority to choose the blocking link.
[SW4]display stp region-configuration
Oper configuration
Format selector :0
Region name :2
Revision level :0

Instance VLANs Mapped
0 1 to 9, 11 to 19, 21 to 29, 31 to 39, 41 to 4094
1 10, 20
2 30, 40
e n
/
<SW4>display stp brief
MSTID Port Role STP State Protection
o m
0 Ethernet0/0/3 ALTE DISCARDING NONE
e i .c
aw
u
.h
0 Ethernet0/0/6 ROOT FORWARDING NONE
i n g
0 Ethernet0/0/7 DESI FORWARDING
r n
NONE
1 Ethernet0/0/3 ALTE
//
DISCARDING
lea NONE
p :
t
t
:h
1 Ethernet0/0/6
e s MAST FORWARDING NONE
r c
ou
2
es
Ethernet0/0/4 ALTE DISCARDING NONE
R
g
2
n i n
Ethernet0/0/6 MAST FORWARDING NONE
ar
L
4. e
Use port priority to Configure SW1 and SW2 to use different links to
r e transmit services A and B, implementing redundancy.
o After the configuration is performed, different services are transmitted using different links.
M [SW1]dis stp brief
0 Ethernet0/0/1 DESI FORWARDING NONE
……

……
……
e n
5. Ensure that SW3 and SW4 will never be the root switch of the network.
/
o m
.c
Note: Adjust the configuration and consider using root protection.
[SW1]dis stp brief
e i
aw
u
.h
0 Ethernet0/0/2 DESI FORWARDING

i
NONE
n g
r n
lea
0 Ethernet0/0/3 DESI FORWARDING ROOT
://
0 Ethernet0/0/5 DESI
t tpFORWARDING ROOT
:h
e s
c
r
ou
1
es
Ethernet0/0/3 DESI FORWARDING ROOT
R
ing
rn
e a 1 Ethernet0/0/6 DESI FORWARDING ROOT
e L
r
o
M
6. Configure the ports eth0/0/7 of SW2 operate in Forwarding state when faulty
links recover, and provide solutions if there are risks to devices such as rogue
switches connected to user ports.
Note: Use the edge port and consider how to prevent risks caused by the edge port.
[SW2]display stp interface Ethernet 0/0/7
-------[CIST Global Info][Mode MSTP]-------
CIST Bridge :32768.4c1f-ccfa-13b8
……
e n
/
m
CIST RootPortId :128.3
BPDU-Protection :Enabled
.c o
TC or TCN received :634
e i
aw
……
u
----[Port7(Ethernet0/0/7)][FORWARDING]----
g .h
Port Protocol :Enabled
ni n
r
lea
…..
Port Edged
: //
:Config=enabled / Active=enabled
BPDU-Protection :Enabled
t t p
Point-to-point
s :h
:Config=auto / Active=true
……
r c e
o u configure the two core switches to respond the
TC-BPDU twice e
s
7. To save the CPU resources,
R during one hello interval.
i n g
Note: Enable TC-BPDU protection and Adjust parameters on switches.
r n the convergence time of MSTP, configure the link between

a
8. To reduce
e
L
switches as point-to-point.
ore After configuration, we can see the following information on the switch.
[SW4]display stp interface Ethernet 0/0/1
M -------[CIST Global Info][Mode MSTP]-------
……
----[Port1(Ethernet0/0/1)][FORWARDING]----
Port Protocol :Enabled
……

Point-to-point :Config=ForceTrue
……
Questions
For requirement 9, why p2p link can accelerate the convergence of STP?
When traffic in VLAN 10/20/30/40/50/60 on SW4 needs to be transmitted in VLANs on
core switches, can the link between SW2 and SW4 be used?
e n
/
m
Configuration List
.c o
e i
#
aw
u
.h
sysname SW1
i n g
vlan batch 10 20 30 40 50 60
r n
#
// lea
p :
t
stp instance 0 root primary
t
:h
stp instance 2 root secondary

e s
r c
ou
stp tc-protection
es
stp tc-protection threshold 2
R
g
#
n i n
stp region-configuration
ar
e
region-name 1
eL
instance 1 vlan 10 20
or instance 2 vlan 30 40
M active region-configuration
stp point-to-point force-true

e n
/
#
o m
e i .c
aw
u
.h
stp root-protection
i n g
#
r n
// lea
p :
t
t
:h
stp root-protection
e s
r c
ou
#
es
R
g
n i n
ar
e
e L stp root-protection
or stp point-to-point force-true
M #
stp root-protection

stp instance 0 port priority 16
return
e n
/
#
sysname SW2
o m
#
e i .c
vlan batch 10 20 30 40 50 60
aw
u
.h
#
i n g
r n
// lea
p :
t
stp bpdu-protection
t
:h
stp tc-protection
stp tc-protection threshold 2

e s
r c
ou
#
es
R
g
region-name 1
n i n
ar
e
e L active region-configuration
or #

stp instance 2 port priority 16
e n
/
o m
e i .c
stp root-protection
aw
u
.h
i n g
r n
// lea
p :
t
t
:h
stp root-protection

e s
r c
ou
#
es
R
g
n i n
ar
e
stp root-protection
e L stp point-to-point force-true
or #
stp root-protection

stp edged-port enable
e n
/
return
o m
e i .c
#
aw
u
.h
sysname SW3
i n g
vlan batch 10 20 30 40 50 60 70
r n
#
// lea
p :
t
t
:h
region-name 1
e s
r c
ou
es
active region-configuration
R
g
#
n i n
ar
e
e L undo port trunk allow-pass vlan 1
or port trunk allow-pass vlan 70
M stp point-to-point force-true
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 70

e n
/
o m
e i .c
aw
u
.h
i n g
#
r n
// lea
p :
t
t
:h

e s
r c
ou
#
es
R
g
n i n
ar
e
e L #
or return
M
sysname SW4
vlan batch 10 20 30 40 50 60 70

region-name 2
e n
/
active region-configuration
o m
e i .c
aw
u
.h
i n g
r n
#
// lea
p :
t
t
:h
e s
r c
ou
es
R
g
#
n i n
ar
e
or stp point-to-point force-true
M #

e n
/
o m
e i .c
aw
u
.h
#
return
i n g
r n
l e a
Chapter 11 Multicast Hands-on
: // Exercise Guide
Overview
t tp
: h
s
As the Internet is developing rapidly, increasing data, voice, and video streams are
r c e
transmitted on networks. Emerging services, such as e-commerce, teleconferencing, online
auction, video on demand (VoD), and distance education are becoming more and more
u
popular. These services often use the multipoint-to-multipoint transmission model and
o
s
require high information security, paid service, and high bandwidth. The IP protocol supports
Re
three transmission modes: IP unicast, IP broadcast, and IP multicast.
A multicast packet uses a multicast address as the destination address, which identifies a
i n g
multicast group. A multicast source sends only one copy of packets to a multicast address.
The multicast routing protocol running on the network establishes a multicast distribution
rn
tree from the multicast source to all members of the multicast group. Multicast data packets
a
are replicated to all group members. Hosts can join a group to receive data sent to the group.
L e In multicast transmission mode, a data flow is transmitted to a group of users along the
multicast distribution tree. Each link transmits only one copy of multicast data packets.
e
or
Compared with the unicast mode, the multicast mode reduces loads on servers and CPUs of
network devices. The increase in the number of users will not significantly increase network
M
loads. Multicast packets can be transmitted across different network segments and will not be
sent to users who do not need the packets. Compared with the broadcast mode, the multicast
mode can transmit data over a long distance. In addition, data is transmitted only to network
segments with receivers, ensuring information security. In a summary, the multicast mode has
advantages over the unicast and broadcast modes in the multipoint-to-multipoint transmission
model.
A multicast group is identified by an IP multicast address. It represents a collection of
systems but not a specific host. If a host joins a multicast group, it means that the host wants
to receive packets destined for the IP multicast address. Multicast addresses are class D IP
addresses in the range of 224.0.0.0 to 239.255.255.255. IP addresses 224.0.0.0 to 224.0.0.255
are reserved as permanent group addresses by the Internet Assigned Numbers Authority
(IANA). In this address range, 224.0.0.0 is not allocated, and the other addresses are used by

routing protocols for topology discovery and maintenance.
Objectives

 Understand multicast application scenarios and working mechanisms.
 Configure multicast sources.
 Configure IGMP.
 Configure PIM-DM.
 Configure PIM-SM.
e n
/
 Configure static and dynamic RP.
 Understand the RPF working mechanism.
 Configure static multicast routes.
o m
Tasks
e i .c
aw
The following topology shows the network of Company A. The network runs the OSPF
u
protocol. Routers R2, R3, R4, and R5 work in area 0. Routers R1, R2, and R3 in area 1 form
g .h
a frame relay (FR) network and adopt a hub-spoke structure. Do not change the default
network type or the link costs unless you are required to. R6/R7 locate in area 2. Ensure that
i n
reachable routes are available among the network devices. The company needs to deploy the
n
r
multicast service on the network. There are three multicast sources on the network. Source 1
lea
and Source 3 connect to R1. Source 2 needs to send multicast data to PC2 in group 239.2.2.2
//
using the PIM-SM mode. PC3-1 and PC3-2 need to join group 239.3.3.3. Multicast data
:
should be transmitted without a rendezvous point tree (RPT). The link between R5 and R7
t t p
and the link between R4 and R6 need to transmit a large amount of multicast data, so PIM
cannot be enabled on the two links. Deploy the network according to the following
:h
requirements:
s
(1) Make R4 and R5 the RPs and ensure that the RP address is 45.45.45.45 on all multicast
r c e
devices. The RPs must be determined through dynamic RP election. Make R2 the bootstrap
router (BSR) and use IP address of loopback 0 (20.1.1.2) as the BSR address. Ensure that
ou
20.1.1.2 is in area 1.
s
(2) R2 is the designated router (DR) on the Ethernet network. For Source 1 (10.1.1.1) connecting
Re
to R1, receiver is PC1. PC1 runs IGMPv2, when R7 receive membership report message, just
join multicast group 239.1.1.1 from S1.
(3)
i n g
The two RPs implement load balancing and back each other up. The RPs run the Multicast
Source Discovery Protocol (MSDP), and only Source-Active (SA) messages with the
r n
(70.0.0.7, 239.2.2.2) mapping are allowed between the RPs.
a
(4) Ensure that Source 2 will not receive multicast data packets from other multicast sources.
(5)
L e
Ensure that the multicast stream sent from Source 2 (70.0.0.7) to the downstream receiver
PC2 is forwarded along the best path.
r e(6) When the IGMP querier on the Ethernet network in area 0 fails, a new querier must be
o available as fast as possible.

Topology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
e
IP Address Table
R
g
Default
n
n i Gateway
ar G 0/0/0 10.1.1.254 255.255.255.0 N/A
L e R1 G 0/0/1 10.3.3.254 255.255.255.0 N/A
r e S 1/0/0 1.1.123.1 255.255.255.0 N/A
o G 0/0/2 192.168.1.2 255.255.255.0 N/A
M R2 S 1/0/0 1.1.123.2 255.255.255.0 N/A

Loopback 0 20.1.1.2 255.255.255.255 N/A
G 0/0/2 192.168.1.3 255.255.255.0 N/A
R3
S 1/0/0 1.1.123.3 255.255.255.0 N/A
G 0/0/0 1.1.45.4 255.255.255.0 N/A
R4 G 1/0/0 1.1.46.4 255.255.255.0 N/A
G 0/0/2 192.168.1.4 255.255.255.0 N/A

G 0/0/1 1.1.47.4 255.255.255.0 N/A

Loopback 1 45.45.45.45 255.255.255.255 N/A
G 0/0/0 1.1.45.5 255.255.255.0 N/A
G 0/0/1 1.1.56.5 255.255.255.0 N/A
R5 G 0/0/2 192.168.1.5 255.255.255.0 N/A
G 1/0/0 1.1.57.5 255.255.255.0 N/A
Loopback 1 45.45.45.45 255.255.255.255 N/A
e n
G1/0/0 1.1.46.6 255.255.255.0 N/A
/
G 0/0/1 1.1.56.6 255.255.255.0 N/A
o m
.c
R6
G 0/0/0 60.0.1.254 255.255.255.0
e i N/A
w
G 0/0/2 60.0.2.254 255.255.255.0 N/A
G 0/0/1 1.1.47.7 255.255.255.0
u a N/A
SW1 G 1/0/0 1.1.57.7 255.255.255.0
g .h N/A
G 0/0/2 70.0.0.254
i n
255.255.255.0
n
N/A
Source 1 E 0/0/1 10.1.1.1
ar
255.255.255.0 10.1.1.254
le
Source 2 E 0/0/1 70.0.0.7 255.255.255.0 70.0.0.254
Source 3 E 0/0/1
:
10.3.3.3
// 255.255.255.0 10.3.3.254
PC 1 E 0/0/1
t t p
70.0.0.1 255.255.255.0 70.0.0.254
:h
PC 2 E 0/0/1 60.0.1.1 255.255.255.0 60.0.1.254
PC 3-1
e
E 0/0/1 s 60.0.2.1 255.255.255.0 60.0.2.254
PC 3-2
r c
E 0/0/1 192.168.1.10 255.255.255.0 192.168.1.2
s ou
e
R the RPs and ensure that the RP address is 45.45.45.45 on all
multicastn
i g The RPs must be determined through dynamic RP election.
1. Make R4 and R5
devices.
Maken
ar R2 the bootstrap router (BSR) and use the IP address of loopback 0
e
(20.1.1.2) as the BSR address. Ensure that 20.1.1.2 is in area 1.
L
re
Bootstrap messages sent from the BSR must be spread throughout the network. Ensure
o
that all multicast devices, especially R3can receive Bootstrap messages.
M
<R3>dis pim rp
VPN-Instance: public net
PIM-SM BSR RP Number:1
Group/MaskLen: 224.0.0.0/4
RP: 45.45.45.45
Priority: 0

Uptime: 00:00:13
Expires: 00:02:17
2. R2 is the DR on the Ethernet network. For Source 1 (10.1.1.1) connecting to

R1, receivers is PC1. PC1 runs IGMPv2, when R7 receive membership
report message, just join multicast group 239.1.1.1 from S1.
Note that if SSM and SSM mapping are used and Join messages with the (S, G)
e n
mapping are transmitted in the FR network, the downstream receiver may receive the first
/
m
multicast data packets but fail to receive the subsequent multicast data packets.
[R2]display pim interface GigabitEthernet 0/0/2
.c o
e i
Interface State NbrCnt HelloInt DR-Pri DR-Address
aw
u
GE0/0/2 up 3 30 100 192.168.1.2
g
(local)
.h
ni n
r
lea
<R7>display igmp ssm-mapping group
IGMP SSM-Mapping conversion table of VPN-Instance: public net
: //
Total 1 entry 1 entry matched
t t p
s
00001. (10.1.1.1, 239.1.1.1/32)
:h
r c e
Total 1 entry matched
o u load balancing and back each other up. The RPs

s SA messages with the (70.0.0.7, 239.2.2.2) mapping are
3. The two RPs implement
e
R the RPs.
run MSDP, and only
g
allowed between
i n
rn
You need to configure MSDP on the RPs. As the anycast-RP mode is used, pay
attention to MSDP peer authentication. Configure SA filtering between the MSDP peers to
e a allow only the specified (S, G) mapping.
e L [R5]display msdp brief
or MSDP Peer Brief Information of VPN-Instance: public net
M Configured Up Listen Connect Shutdown Down
1 1 0 0 0 0
Peer's Address State Up/Down time AS SA Count Reset Count
1.1.45.4 Up 00:01:26 ? 0 0
4. Ensure that Source 2 will not receive multicast data packets from other
multicast sources.

SW1 connects to Source 2 and receiver PC1. PC1 needs to receive multicast data from
Source 1. To prevent Source 2 from receiving multicast data packets from other multicast
sources, configure IGMP snooping.
[Sw1]dis igmp-snooping configuration
IGMP Snooping Configuration for VLAN 1
igmp-snooping enable
5. Ensure that the multicast stream sent from Source 2 (70.0.0.7) to the
e n
downstream receiver PC2 is forwarded along the best path. /
o m
.c
R4 is the RP for the source and R5 is the RP for the receiver. Configure an MSDP
e i
session and enable switchover between the two RPs. There are equal paths from S2 (70.0.0.7)
on R7 to R6. But PIM is not enabled on the link between R7 and R5, R4 and R6. Be sure
RPT and SPT can be established successfully.
aw
u
.h
[R5]dis multicast rpf-info 70.0.0.0
i n g
RPF information about source: 70.0.0.0
r n
lea
RPF interface: GigabitEthernet0/0/0, RPF neighbor: 1.1.45.4
//
Referenced route/mask: 70.0.0.0/24
p :
t t
:h
Referenced route type: mstatic
e s
Route selection rule: preference-preferred
r c
ou
Load splitting rule: disable
es
R
<R5>display pim routing-table
i n g
r n
e a
Total 1 (*, G) entry; 1 (S, G) entry
e L
or (*, 239.2.2.2)
M RP: 45.45.45.45 (local)
Protocol: pim-sm, Flag: WC
UpTime: 00:13:10
Upstream interface: Register
Upstream neighbor: NULL
RPF prime neighbor: NULL

Downstream interface(s) information:
Total number of downstreams: 1
1: GigabitEthernet0/0/1
Protocol: pim-sm, UpTime: 00:13:10, Expires: 00:03:20
e n
/
(70.0.0.7, 239.2.2.2)
RP: 45.45.45.45 (local)
o m
Protocol: pim-sm, Flag: SPT 2MSDP ACT
e i .c
UpTime: 00:03:08
aw
u
.h
Upstream interface: GigabitEthernet0/0/0
Upstream neighbor: 1.1.45.4
i n g
RPF prime neighbor: 1.1.45.4
r n
Downstream interface(s) information:
// lea
p :
t
Total number of downstreams: 1
t
:h
1: GigabitEthernet0/0/1
e s
Protocol: pim-sm, UpTime: 00:03:08, Expires: 00:03:22
r c
o
6. When the IGMP querier u asonfasttheasEthernet network in area 0 fails, a new
e s
querier must be available possible.
R
g
There is a receiver on the backbone network. R2 has the smallest IP address on the backbone
i n
network and should be elected as the querier. If the querier fails, R3 should act as the querier.
rn
However, the default querier re-election interval is a long time. To enable R3 to preempt as
a
the new querier as fast as possible, you can change the Other Querier Present Timer value.
L e
[R4]display igmp interface GigabitEthernet 0/0/2
e
or
Interface information of VPN-Instance: public net
M
GigabitEthernet0/0/2(192.168.1.4):
IGMP is enabled
Current IGMP version is 2
IGMP state: up
IGMP group policy: none
IGMP limit: -

Value of query interval for IGMP (negotiated): -
Value of query interval for IGMP (configured): 20 s
Value of other querier timeout for IGMP: 51 s
Value of maximum query response time for IGMP: 10 s
Querier for IGMP: 192.168.1.2
e n
/
Total 1 IGMP Group reported
o m
.c
Questions
e i
When use anycast to implement load balance between RPs, what will happen and how
to resolve the problem?
aw
u
.h
Configuration List
i n g
r n
lea
#
sysname R1
: //
#
t t p
multicast routing-enable
s :h
#
r c e
s ou
link-protocol fr
Re
n g
ip address 1.1.123.1 255.255.255.0
i
r
pim sm
n
e a
e L #
or interface GigabitEthernet0/0/0
M ip address 10.1.1.254 255.255.255.0
pim sm
ip address 10.3.3.254 255.255.255.0
pim sm

ospf 1
peer 1.1.123.2
peer 1.1.123.3
area 0.0.0.1
e n
/
network 1.1.123.0 0.0.0.255
network 10.1.1.0 0.0.0.255
o m
network 10.3.3.0 0.0.0.255
e i .c
network 10.5.5.0 0.0.0.255
aw
u
.h
#
pim
i n g
#
r n
return
// lea
p :
t t
:h
#
e s
r c
ou
sysname R2
#
es
R
g
#
n i n
ar
e
e L link-protocol fr
or ip address 1.1.123.2 255.255.255.0
M pim sm
ospf dr-priority 0
link-protocol ppp

ip address 192.168.1.2 255.255.255.0
pim hello-option dr-priority 100
pim sm
igmp enable
e n
/
igmp version 3
igmp timer query 20
o m
igmp timer other-querier-present 60
e i .c
#
aw
u
.h
interface LoopBack0
ip address 20.1.1.2 255.255.255.255
i n g
pim sm
r n
#
// lea
p :
t
ospf 1
t
:h
peer 1.1.123.1
area 0.0.0.0
e s
r c
ou
network 192.168.1.0 0.0.0.255
area 0.0.0.1
es
R
g
network 1.1.123.0 0.0.0.255
n i n
network 20.1.1.0 0.0.0.255
ar
e
#
e L
pim
or c-bsr LoopBack0
M #
return
sysname R3

link-protocol fr
e n
/
ip address 1.1.123.3 255.255.255.0
pim sm
o m
ospf dr-priority 0
e i .c
#
aw
u
.h
ip address 192.168.1.3 255.255.255.0
i n g
pim sm
r n
igmp enable
// lea
p :
t
igmp version 3
t
:h
igmp timer query 20
e s
r c
ou
#
ospf 1
es
R
g
peer 1.1.123.1
n i n
area 0.0.0.0
ar
e
network 192.168.1.0 0.0.0.255
e L area 0.0.0.1
or network 1.1.123.0 0.0.0.255
M #
ip rpf-route-static 20.1.1.2 32 1.1.123.1
return

sysname R4
e n
/
acl number 3001
rule 5 permit ip source 70.0.0.7 0 destination 239.2.2.2 0
o m
rule 10 deny ip
e i .c
#
aw
u
.h
ip address 1.1.45.4 255.255.255.0
i n g
pim sm
r n
#
// lea
p :
t
t
:h
ip address 1.1.47.4 255.255.255.0
pim sm
e s
r c
ou
#
es
R
g
ip address 192.168.1.4 255.255.255.0
n i n
pim hello-option dr-priority 20
ar
e
pim sm
e L igmp enable
or igmp version 3
M igmp timer query 20
ip address 1.1.46.4 255.255.255.0

interface LoopBack1
ip address 45.45.45.45 255.255.255.255
pim sm
ospf 1
e n
/
area 0.0.0.0
network 1.1.45.0 0.0.0.255
o m
network 45.45.45.45 0.0.0.0
e i .c
network 192.168.1.0 0.0.0.255
aw
u
.h
area 0.0.0.2
network 1.1.46.0 0.0.0.255
i n g
network 1.1.47.0 0.0.0.255
r n
#
// lea
p :
t
pim
t
:h
c-rp LoopBack1
#
e s
r c
ou
pim
c-rp LoopBack1
es
R
g
anycast-rp 45.45.45.45
n i n
local-address 1.1.45.4
ar
e
peer 1.1.45.5
e L
#
or return
M
sysname R5

acl number 3001
rule 5 permit ip source 70.0.0.7 0 destination 239.2.2.2 0
rule 10 deny ip
e n
/
ip address 1.1.45.5 255.255.255.0
o m
pim sm
e i .c
#
aw
u
.h
ip address 1.1.56.5 255.255.255.0
i n g
pim sm
r n
#
// lea
p :
t
t
:h
ip address 192.168.1.5 255.255.255.0
pim sm
e s
r c
ou
igmp enable
igmp version 3
es
R
g
igmp timer query 20
n i n
ar
e
#
e L
or ip address 1.1.57.5 255.255.255.0
M #
interface LoopBack1
ip address 45.45.45.45 255.255.255.255
pim sm
ospf 1

area 0.0.0.0
network 1.1.45.0 0.0.0.255
network 45.45.45.45 0.0.0.0
network 192.168.1.0 0.0.0.255
area 0.0.0.2
e n
/
network 1.1.56.0 0.0.0.255
network 1.1.57.0 0.0.0.255
o m
#
e i .c
pim
aw
u
.h
c-rp LoopBack1
i n g
pim
r n
c-rp LoopBack1
// lea
p :
t
anycast-rp 45.45.45.45
t
:h
local-address 1.1.45.5
peer 1.1.45.4
e s
r c
ou
#
es
ip rpf-route-static 70.0.0.0 24 1.1.45.4
R
g
#
return
n i n
ar
Le
e
or #
M sysname R6
ip address 60.0.1.254 255.255.255.0

pim sm
igmp enable
ip address 1.1.56.6 255.255.255.0
e n
/
pim sm
o m
e i .c
ip address 60.0.2.254 255.255.255.0
aw
u
.h
pim sm
igmp enable
i n g
igmp version 3
r n
#
// lea
p :
t
t
:h
ip address 1.1.46.6 255.255.255.0
#
e s
r c
ou
ospf 1
area 0.0.0.2
es
R
g
network 1.1.46.0 0.0.0.255
n i n
network 1.1.56.0 0.0.0.255
ar
e
network 60.0.1.0 0.0.0.255
e L network 60.0.2.0 0.0.0.255
or #
M return
sysname R7

ip address 1.1.47.7 255.255.255.0
pim sm
e n
/
#
o m
ip address 70.0.0.254 255.255.255.0
e i .c
pim sm
aw
u
.h
igmp enable
igmp ssm-mapping enable
i n g
#
r n
// lea
p :
t
ip address 1.1.57.7 255.255.255.0
t
:h
#
ospf 1
e s
r c
ou
area 0.0.0.2
es
network 1.1.47.0 0.0.0.255
R
g
network 1.1.57.0 0.0.0.255
n i n
network 70.0.0.0 0.0.0.255
ar
e
#
e L
igmp
or ssm-mapping 239.1.1.1 255.255.255.255 10.1.1.1
M #
pim
return
<Sw1>display current-configuration

sysname Sw1
e n
/
vlan 1
o m
#
e i .c
return
aw
u
g .h
Chapter 12 IPv6 Hands-on Exercise Guide
ni n
r
lea
Overview
: //
Internet Protocol Version 6 (IPv6) is the next-generation IP protocol designed by the
t p
Internet Engineering Task Force (IETF) as an upgraded version of the current Internet
Protocol Version 4 (IPv4).
t
:h
Compared with IPv4, IPv6 has the following advantages:
e s
1. Huge address space: An IPv6 address is 128 bits long. The 128-bit address structure
increases the number of possible addresses by 2 96 times.
r c
2. Flexible IP packet header: IPv6 uses a series of extension headers of fixed formats
ou
to replace the options fields of variable lengths in the IPv4 header.
s
3. Simple IPv6 packet header format: An IPv6 packet header carries only eight fields.
R
throughput.e
The simplified packet header facilitates packet forwarding and improves
i n g
4. Enhanced security: IPv6 supports identity authentication and data encryption.
5. Support for more service types.
r n
6. Continuous protocol evolution: IPv6 adds support for new functions and caters for
e a future technology development requirements.

Due to the large scale of the Internet and large number of IPv4 users and terminals,
e L transition from IPv4 to IPv6 cannot be completed in a short time. In addition, enterprises and
or users become increasingly dependent on the Internet in their daily work and cannot tolerate
service disruption brought by the transition. Therefore, IPv4 needs to gradually transit to
M
IPv6 so that users can experience the advantages brought by IPv6 while still be able to
communicate with IPv4 users. Smooth transition from IPv4 to IPv6 is a key factor
determining IPv6 success.
Many solutions have been proposed in the industry for smooth migration from IPv4 to
IPv6. IETF organized the research team NGTrans focused on IPv4-to-IPv6 transition. The
team has drafted several transition solutions and tried to standardize them. The transition
solutions mainly cover the following technologies:
1. Dual-stack technology
2. Tunneling technology (including manual tunneling and automatic tunneling
technologies)
3. Tunnel proxy
4. NAT-PAT
Objectives
Upon completion of this exercise guide, you will be able to master the method to:
 Use stateless IPv6 address auto configuration.
 Configure OSPFv3.
 Configure IS-ISv6.
 Configure BGPv4+.
 Configure BGPv4+ to advertise default routes.
 Configure BGPv4+ routing policy.
 Configure a manual tunnel and an automatic tunnel (6to4).
e n
/
Tasks
o m
i
The following figure shows the IPv6 network topology. Deploy the network according
to the following requirements:
e .c
w
(1) Run OSPFv3 among R1, R2, and R3, and set the area ID of the three routers to 0 and router
(2)
IDs of R1, R2, and R3 to 10.1.1.1, 10.2.2.2, and 10.3.3.3 respectively.
u a
Run IS-ISv6 among R4, R5, and R6, set the area ID of the three routers to 49.0001, and
(3)
ensure that the three routers are all Level-2 routers.
g .h
Run OSPFv2 on the IPv4 network between R2 and R4 and set the area ID of the two routers
to 0, include loopback interfaces.
ni n
(4)
r
Set up an IS-ISv4 neighbor relationship between R6 and R7 (an IPv4 network is deployed
lea
between R6 and R7) and set the area ID of the two routers to 49.0001.
//
(5) Set up full-mesh IBGP4+ IPv6 neighbor relationships among R1, R2, and R3, set the AS
:
number of the three routers to 100, and configure R2 to advertise default routes to AS100. Set
two routers to 200.

t t p
up an IBGP4+ IPv6 neighbor relationship between R4 and R5 and set the AS number of the
:h
(6) Set up an GRE manual tunnel between R2 and R4 with the tunnel address
s
2001:db8:24::/64 ,Set up an EBGP IPv6 neighbor relationship between R2 and R4 using IPv6
(7)
r e
addresses, and configure R2 to advertise the route 2001:db8:100:00 of AS100 to AS200.
c
Import IS-ISv6 routes to BGP on R4 and R5. Ensure that all IPv6 networks that connect to
ou
AS100 and AS200 can communicate with each other.
s
(8) Configure users connected to GE0/0/1 of R7 to automatically obtain IPv6 addresses, DNS(R1)
terminal.
Re
information in state auto configuration mode. In this example, R8 is used to simulate an IPv6
(9)
AS200.
i n g
Establish a 6to4 tunnel between R6 and R7. Ensure R7 can ping the IPv6 networks inside
r n
e a
e L
or
M

Topology
IPv4 network
Autoconfiguration
e n
/
m
IPv4 network
.c o
e i
aw
u
g .h
ni n
IP Address Table
r
lea
://
Default
tp
Gateway
t
:h
G 0/0/1 2001:db8:100::1 64 N/A
R1
Loopback 0 10.1.1.1 32 N/A
G 0/0/0
e s 192.168.24.2 24 N/A
R2 G 0/0/2
r c 2001:db8:100::2 64 N/A
ou
Loopback 0 10.2.2.2 32 N/A
s
G 0/0/0 2001:db8:100::3 64 N/A
R3
Re
S 4/0/0
Loopback 0
192.168.35.3
10.3.3.3
24
32
N/A
N/A
R4
i n g G 0/0/0
G 0/0/1
192.168.24.4
2002:0A06:0606:46::4
24
64
N/A
N/A
r n Loopback 0 10.4.4.4 32 N/A
e a G 0/0/0 2002:0A06:0606:56::5 64 N/A
L
R5 S 4/0/0 192.168.35.5 24 N/A
Loopback 0 10.5.5.5 32 N/A
r e G 0/0/0 2002:0A06:0606:46::6 64 N/A
o R6
G 0/0/1 2002:0A06:0606:56::6 64 N/A
M G 0/0/2
Loopback 0
G 0/0/0
192.168.67.6
10.6.6.6
192.168.67.7
24
32
24
N/A
N/A
N/A
R7 G 0/0/1 2002:0A07:0707::7 64 N/A
Loopback 0 10.7.7.7 32 N/A
1. Run OSPFv3 among R1, R2, and R3, and set the area ID of the three routers
to 0 and router IDs of R1, R2, and R3 to 10.1.1.1, 10.2.2.2, and 10.3.3.3
respectively.
Perform basic configurations according to the address table, and then run the display
ospfv3 peer command to check information about OSPF neighbor relationships and routes
on network segments where the loopback interfaces 0 reside.
<R1>display ospfv3 peer
OSPFv3 Process (1)
OSPFv3 Area (0.0.0.0)
Neighbor ID Pri State Dead Time Interface Instance ID
e n
/
m
10.2.2.2 1 Full/Backup 00:00:40 GE0/0/1 0
10.3.3.3 1 Full/DROther 00:00:31 GE0/0/1 0
.c o
e i
2. Run IS-ISv6 among R4, R5, and R6, set the area ID of the three routers to
aw
u
49.0001, and ensure that the three routers are all Level-2 routers.
g .h
After completing this task, check information about IS-IS neighbor relationships.
[R6]display isis 1 peer
ni n
r
lea
://
t tp
--------------------------------------------------------------------------------
0000.0000.0004 GE0/0/0
s :h
0000.0000.0004.01 Up 8s L2 64
0000.0000.0005 GE0/0/1
r c e 0000.0000.0006.02 Up 30s L2 64
ou
Total Peer(s): 2
es
3.
R
Run OSPFv2 on the IPv4 network between R2 and R4 and set the area ID of
i n g
the two routers to 0, include loopback interfaces.
r n
After completing this task, check information about the OSPF neighbor relationship.
e a
[R2]display ospf peer brief
e L
r
o Peer Statistic Information
M --------------------------------------------------------------------------------
Area Id Interface Neighbor id State
0.0.0.0 GigabitEthernet0/0/0 10.4.4.4 Full
-------------------------------------------------------------------------------
4. Set up an IS-ISv4 neighbor relationship between R6 and R7 (an IPv4

network is deployed between R6 and R7) and set the area ID of the two
routers to 49.0001.
After completing this task, check information about the IS-IS neighbor relationship.
<R7>display isis peer
-------------------------------------------------------------------------------
e n
/
m
0000.0000.0006 GE0/0/0 0000.0000.0006.03 Up 8s L2 64
Total Peer(s): 1
.c o
e i
tow
5. Set up full-mesh IBGP4+ IPv6 neighbor relationships among R1, R2, and R3,
set the AS number of the three routers to 100, and configure R2 a
htou200.
advertise
.
default routes to AS100. Set up an IBGP4+ IPv6 neighbor relationship
between R4 and R5 and set the AS number of the two routers
i n g
r n
Configure R2 to advertise default routes to AS100.
[R1]display bgp ipv6 peer
l e a
: //
t tp
: h
Total number of peers : 2
e s Peers in established state : 2
Peer
rV
c AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
o u
s
2001:DB8:100::2 4 100 2 2 0 00:00:24 Established 0
R e
2001:DB8:100::3 4 100 2 2 0 00:00:19 Established 0
i n g
a rn
<R1>display bgp ipv6 routing-table
L e BGP Local router ID is 10.1.1.1
e
or
M h - history, i - internal, s - suppressed, S - Stale
*>i Network : :: PrefixLen : 0
NextHop : 2001:DB8:100::2 LocPrf : 100
MED : 0 PrefVal : 0

Label :
Path/Ogn : i
<R4>display bgp ipv6 peer
e n
/
o m
e i .c
2002:A06:606:56::5
aw
u
.h
4 200 2 2 0 00:00:16 Established 0
6. Set up an GRE manual tunnel between R2 and R4 with the tunnel address
i n g
2001:db8:24::/64.Set up an EBGP IPv6 neighbor relationship between R2
r n
lea
and R4 using IPv6 addresses, and configure R2 to advertise the route
//
2001:db8:100:00 of AS100 to AS200.
p :
t
After completing this task, check route learning information.
t
:h
<R4>display bgp ipv6 routing-table

e s
r c
ou
*> Network : 2001:DB8:100:: PrefixLen : 64
NextHop
es
: 2001:DB8:24::2 LocPrf :
R
g
MED : 0 PrefVal : 0
n i n
Label :
ar
e
Path/Ogn : 100 i
e L
or <R5>display bgp ipv6 routing-table
M *>i Network : 2001:DB8:100:: PrefixLen : 64
NextHop : 2002:A06:606:46::4 LocPrf : 100
MED : 0 refVal : 0
Label :
Path/Ogn : 100 i

7. Import IS-ISv6 routes to BGP on R4 and R5. Ensure that all IPv6 networks
that connect to AS100 and AS200 can communicate with each other.
Run the import-route command on R4 and R5 to import IS-IS routes to BGP and
enable communication between AS100 and AS200. Since BGP+ does not run on R6, R6 does
not know the forwarding path of the data packets. It is recommended that you configure IS-IS
on R4 to advertise default IPv6 routes.
[R5]ping ipv6 -c 1 2001:db8:100::1
PING 2001:db8:100::1 : 56 data bytes, press CTRL_C to break
e n
/
Reply from 2001:DB8:100::1
o m
bytes=56 Sequence=1 hop limit=61 time = 60 ms
e i .c
w
--- 2001:db8:100::1 ping statistics ---
u a
g .h
ni n
r
0.00% packet loss
lea
: //
8.
t p
Configure users connected to GE0/0/1 of R7 to automatically obtain IPv6
t
:h
addresses and DNS (R1) information in state auto configuration mode. In
this example, R8 is used to simulate an IPv6 terminal.
e s
r c
It is required that DHCP be deployed together with NDP state auto configuration.
ou
<R8>display dhcpv6 client
es
GigabitEthernet0/0/0 is in stateful DHCPv6 client mode.
R
i n g
State is BOUND.
r n
Preferred server DUID : 0003000100E0FC2902A2
e a Reachable via address : FE80::2E0:FCFF:FE29:2A3
e L
r
IA NA IA ID 0x00000031 T1 43200 T2 69120
o Obtained : 2015-05-20 09:20:14
M Renews : 2015-05-20 21:20:14
Rebinds : 2015-05-21 04:32:14
Address : 2002:A07:707::100
Lifetime valid 172800 seconds, preferred 86400 seconds
Expires at 2015-05-22 09:20:14(171706 seconds left)

DNS server : 2001:DB8:100::1
9. Establish a 6to4 tunnel between R6 and R7. Ensure R7 can ping the IPv6
networks inside AS200.
R2 and R4 communicate through a GRE tunnel, and R6 and R7 communicate through a

6to4 tunnel.
Configuration List
e n
/
o m
#
e i .c
sysname R1
aw
u
.h
#
ipv6
i n g
#
r n
router id 10.1.1.1
// lea
p :
t
#
t
:h
ospfv3 1
router-id 10.1.1.1
e s
r c
ou
#
es
R
g
ipv6 enable
n i n
ipv6 address 2001:DB8:100::1/64
ar
e
ospfv3 1 area 0.0.0.0
eL
#
M ip address 10.1.1.1 255.255.255.255
bgp 100
router-id 10.1.1.1
undo default ipv4-unicast
peer 2001:DB8:100::2 as-number 100

ipv4-family unicast
e n
/
ipv6-family unicast
o m
peer 2001:DB8:100::2 enable
e i .c
aw
u
.h
#
return
i n g
r n
// lea
p :
t
#
t
:h
sysname R2
#
e s
r c
ou
ipv6
#
es
R
g
router id 10.2.2.2
#
n i n
ar
e
ospfv3 1
or #
ip address 192.168.24.2 255.255.255.0
ipv6 enable
ipv6 address 2001:DB8:100::2/64

interface LoopBack0
ip address 10.2.2.2 255.255.255.255
e n
/
ipv6 enable
o m
ipv6 address 2001:DB8:24::2/64
e i .c
tunnel-protocol gre
aw
u
.h
source 10.2.2.2
i n g
#
r n
bgp 100
// lea
p :
t
router-id 10.2.2.2
t
:h
e s
r c
ou
#
es
R
g
ipv4-family unicast
n i n
ar
e
#
e L ipv6-family unicast
or undo synchronization
M network 2001:DB8:100:: 64
peer 2001:DB8:100::1 default-route-advertise
peer 2001:DB8:100::3 default-route-advertise

ospf 1
area 0.0.0.0
network 10.2.2.2 0.0.0.0
network 192.168.24.0 0.0.0.255
e n
/
#
ipv6 route-static :: 0 NULL0
o m
#
e i .c
return
aw
u
g .h
n
ni
#
r
sysname R3
// lea
p :
t
#
t
:h
ipv6
#
e s
r c
ou
router id 10.3.3.3
#
es
R
g
ospfv3 1
n i n
router-id 10.3.3.3
ar
e
#
e L interface Serial4/0/0
or link-protocol ppp
M ip address 192.168.35.3 255.255.255.0
ipv6 enable
ipv6 address 2001:DB8:100::3/64

interface LoopBack0
ip address 10.3.3.3 255.255.255.255
bgp 100
e n
/
router-id 10.3.3.3
o m
e i .c
aw
u
.h
#
ipv4-family unicast
i n g
r n
#
// lea
p :
t
ipv6-family unicast
t
:h

e s
r c
ou
#
es
R
g
return
n i n
ar
e
e L #
or sysname R4
M #
ipv6
router id 10.4.4.4
isis 1

is-level level-2
cost-style wide
network-entity 49.0001.0000.0000.0004.00
ipv6 enable topology standard
e n
/
ipv6 default-route-advertise always
o m
firewall zone Local
e i .c
priority 15
aw
u
.h
#
i n g
ip address 192.168.24.4 255.255.255.0
r n
#
// lea
p :
t
t
:h
ipv6 enable
e s
ipv6 address 2002:A06:606:46::4/64
r c
ou
isis ipv6 enable 1
#
es
R
g
interface LoopBack0
n i n
ip address 10.4.4.4 255.255.255.255
ar
e
#
e L interface Tunnel0/0/0
or ipv6 enable
M ipv6 address 2001:DB8:24::4/64
tunnel-protocol gre
source 10.4.4.4
bgp 200

router-id 10.4.4.4
peer 2002:A06:606:56::5 as-number 200
e n
/
ipv4-family unicast
o m
#
e i .c
ipv6-family unicast
aw
u
.h
import-route isis 1
i n g
r n
peer 2002:A06:606:56::5 enable
// lea
p :
t
peer 2002:A06:606:56::5 next-hop-local
t
:h
#
ospf 1
e s
r c
ou
area 0.0.0.0
es
network 10.4.4.4 0.0.0.0
R
g
network 192.168.24.0 0.0.0.255
#
n i n
ar
e
return
e L
M #
sysname R5
ipv6
router id 10.5.5.5

isis 1
is-level level-2
cost-style wide
network-entity 49.0001.0000.0000.0005.00
e n
/
#
o m
#
e i .c
aw
u
.h
link-protocol ppp
ip address 192.168.35.5 255.255.255.0
i n g
#
r n
// lea
p :
t
ipv6 enable
t
:h
ipv6 address 2002:A06:606:56::5/64
isis ipv6 enable 1

e s
r c
ou
#
e
interface LoopBack0
s
R
g
ip address 10.5.5.5 255.255.255.255
#
n i n
ar
e
bgp 200
or undo default ipv4-unicast
M peer 2002:A06:606:46::4 as-number 200
ipv4-family unicast
ipv6-family unicast

import-route isis 1
peer 2002:A06:606:46::4 enable
return
e n
/
o m
#
e i .c
sysname R6
aw
u
.h
#
ipv6
i n g
#
r n
isis 1
// lea
p :
t
is-level level-2
t
:h
cost-style wide
e s
network-entity 49.0001.0000.0000.0006.00
r c
ou
#
es
R
g
#
n i n
ar
e
ipv6 enable
e L ipv6 address 2002:A06:606:46::6/64
or isis ipv6 enable 1
M #
ipv6 enable
ipv6 address 2002:A06:606:56::6/64
isis ipv6 enable 1

ip address 192.168.67.6 255.255.255.0
isis enable 1
interface LoopBack0
e n
/
ip address 10.6.6.6 255.255.255.255
isis enable 1
o m
#
e i .c
aw
u
.h
ipv6 enable
ipv6 address 2002:A06:606::6/64
i n g
tunnel-protocol ipv6-ipv4 6to4
r n
source GigabitEthernet0/0/2
// lea
p :
t
#
t
:h
ipv6 route-static 2001:DB8:700:: 64 2002:A07:707::7
e s
ipv6 route-static 2002:: 16 Tunnel0/0/0
r c
ou
#
return
es
R
i n g
n
ar
e
#
e L sysname R7
or #
M ipv6
dhcp enable
dhcpv6 pool HCIE
address prefix 2002:A07:707::/64

dns-server 2001:DB8:100::1
isis 1
cost-style wide
is-level level-2
e n
/
network-entity 49.0001.0000.0000.0007.00
o m
e i .c
ip address 192.168.67.7 255.255.255.0
aw
u
.h
isis enable 1
i n g
r n
ipv6 enable
// lea
p :
t
ipv6 address 2002:A07:707::7/64
t
:h
undo ipv6 nd ra halt
ipv6 nd autoconfig other-flag

e s
r c
ou
dhcpv6 server HCIE
#
es
R
g
interface LoopBack0
n i n
ip address 10.7.7.7 255.255.255.255
ar
e
isis enable 1
e L #
or interface Tunnel0/0/0
M ipv6 enable
ipv6 address 2002:A07:707:67::7/64
tunnel-protocol ipv6-ipv4 6to4
source LoopBack 0
ipv6 route-static :: 0 2002:A06:606::6

ipv6 route-static 2002:: 16 Tunnel0/0/0
return
e n
/
#
sysname PC
o m
#
e i .c
ipv6
aw
u
.h
#
dns resolve
i n g
#
r n
dhcp enable
// lea
p :
t
#
t
:h
ipv6 enable
e s
r c
ou
ipv6 address auto link-local
es
ipv6 address auto dhcp
R
g
#
return
n i n
ar
e
LChapter 13 Hands-on Exercise Guide to Other Features
r e
o
M Overview
MPLS
The Multiprotocol Label Switching (MPLS) protocol can be used to deploy an IP
network with low cost. Similar to ATM technology, MPLS uses labels to implement fast
packet forwarding. BGP/MPLS VPN is a technique that implements VPN on MPLS networks
by using the MP-BGP protocol. On a BGP/MPLS VPN, network devices are classified into
Provider Edge (PE), Provider (P), and Customer Edge (CE). P devices are internally located
on the Service Provider's (SP) network and only run IGP and MPLS. PE devices are the edge
devices on the SP's network, and connect to the CE. PE devices run MP-BGP, and VPN
instances for users are configured on PE devices. In addition, PE devices need to run IGP and
MPLS. CE devices are the edge devices connected to customer devices. They connect
customer devices to PE devices. The only requirement on CE devices is that the CE devices
must be able to communicate with PE devices.
The BGP protocol can maintain only a single routing table, so it cannot serve the
customers with overlapping addresses or separate data of different users. To address this
problem, MP-BGP is used on the BGP/MPLS VPN. MP-BGP uses VPNv4 address family to
differentiate the network-layer protocols of different customers and uses VPN instances to
separate the routes and traffic of different customers.
SNMP
n
To cope with fast growing network services, a large number of network devices need to
be deployed. In most situations, there is a long distance between these network devices and
the center equipment room where the network administrator stays. It is very difficult for a
/ e
network administrator to detect, locate and rectify the fault in real time if the devices do not
o m
.c
report the fault. This lowers maintenance efficiency and increases maintenance workload.
e i
Simple Network Management Protocol (SNMP) is introduced to address this problem. Based
on the concept of "network manages network", SNMP effectively manages network devices
w
in batches. In addition, by using the SNMP protocol, the network management system can
a
u
manage the devices of different vendors.
BFD
g .h
i n
A network device must be able to detect a communication fault between adjacent
n
devices quickly so that the network administrator can rectify the fault and prevent service
r
lea
interruption. In practice, hardware detection is used to detect link faults. For example,
Synchronous Digital Hierarchy (SDH) alarms are used to report link faults. However, not all
//
media can provide the hardware detection mechanism. Applications use the Hello mechanism
:
of the upper-layer protocol to detect faults. The detection duration is more than 1 second,
p
t
which is intolerable for some applications. If no routing protocols are deployed on a
t
:h
small-scale Layer 3 network, the Hello mechanism cannot be used. Bidirectional Forwarding
Detection (BFD) provides a fast fault detection mechanism that is independent of media and
protocols.
e s
r c
ou
NTP
As network topologies become increasingly complex, clock synchronization becomes
s
more important for devices on the entire network. If a system clock is manually modified by
e
R
network administrators, the workload is heavy and the modification is error-prone, which
affects clock precision. The Network Time Protocol (NTP) is formulated for clock
n g
synchronization between devices on a network. NTP is an application-layer protocol in the
i
TCP/IP protocol suite. It synchronizes time among a set of distributed time servers and
r n
clients. NTP is implemented based on IP and UDP, and transmits data through UDP. The port
a
number of NTP is 123.
e
e L
NQA
or Network Quality Analysis (NQA) is located at the link layer, and covers the network,
transport, and application layers. It is independent of the bottom-layer hardware. NQA
M monitors network quality indicators in real time, and effectively diagnoses and locates
network faults.
QoS
On traditional IP networks, each network device handles all packets in an
undifferentiated manner and follows the First In First Out (FIFO) rule to transmit packets.
The devices try their best to transmit packets to the destination (Best-Effort). This Best-Effort
mode, however, does not ensure performance such as delay and reliability. Along with the
emergence of new applications on IP networks, new requirements are raised for the Quality
of Service (QoS) of IP networks. For example, voice over IP (VoIP) and video services are
delay-sensitive. A long delay in packet transmission is intolerable by customers (for which
email and FTP services are considered delay-insensitive). To support different services such
as voice, video, and data services, the network is required to distinguish different service
types before providing corresponding QoS. The Best-Effort mode cannot distinguish between
different service types on the network, and so it cannot provide differentiated QoS. The
Best-Effort mode therefore cannot meet the requirements of applications. QoS is introduced
to address this problem. QoS can control network traffic, avoid and manage network
congestion, and reduce packet loss. In addition, QoS provides dedicated bandwidth for
specific users and differentiated quality for different services.
Objectives
e n
/
 Explain what BGP MPLS VPN is.
 Configure LDP.
o m
.c
 Configure MP-BGP.
 Configure SNMP.
 Configure BFD. e i
 Configure QoS.
aw
 Configure NQA.
u
.h
 Configure NTP.
Tasks
i n g
r n
lea
//
:
(1) Run OSPF and LDP on AR1, AR2, and AR3. Configure area 0 between AR1 and
t t p
AR2, and area 2 between AR2 and AR3. To reduce the number of routing entries in
area 0, configure OSPF route aggregation on AR2 to summarize R3’s loopback
:h
address.
s
(2) A backup router AR4 has been added to the SP's network. The links between AR1
r c e
and AR4, between AR3 and AR4 are low-speed links, and run IS-IS. Ensure that
the traffic is preferentially transmitted through AR1-AR2-AR3 and uses
ou
AR1-AR4-AR3 as the backup link.
s
(3) Connect the customer devices AR5 and AR6 to the SP's network as VPN1 to
devices.
Re
implement mutual access, and configure static routes between the CE and PE
i n g
(4) With the growth of services, the customer leases lines from other SPs. The
customer prefers MPLS VPN. If the link between AR1 and AR6 or between AR3
r n and AR5 fails, ensure that the traffic can be switched to the link between R5 and
a
R6. Static routes are still used on the customer's network.
L e (5) With the further growth of company's services, the CE devices on the headquarters
network need to be dual homed to PE devices and run BGP. Tear down the original
r e backup link. Ensure that the traffic is preferentially transmitted through
o AR6-AR1-AR3-AR5, and uses AR6-AR4-AR3-AR5 as the backup path. Configure
M
only on router AR6. Static routes are still used between AR3 and AR5.
(6) Add a new NMS to the VPN and ensure the connectivity between the NMS and
other network devices. Configure LSW3 in the NMS as the NTP server and other
devices as NTP clients; LSW2 use network 11.1.5.0/24 to connect to PE.
(7) Run SNMPv2 on network devices; public as RO community, private as RW
community.
(8) Configure NQA on the link between AR5 and AR6. Ensure that AR5 and AR6 can
send traps to the NMS server when three consecutive ICMP packets are dropped.
The address of NMS is 11.1.5.254.
(9) Configure traffic classifiers on AR6’s interface Ge0/0/1, Mark traffic of http/telnet
as DSCP AF41 and set the CAR for other traffic. Ensure the bandwidth of other
traffic under 2M.

Topology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
IP Address Table
: // Default
Device Interface
t t p
IP Address Subnet Mask
Gateway
:h
G 0/0/0 10.1.1.1 255.255.255.0 N/A
G 0/0/2
e s 11.1.1.1 255.255.255.0 N/A
R1
r c
ou
S 1/0/1 10.2.1.1 255.255.255.0 N/A
s
Loopback 0 1.1.1.1 255.255.255.255 N/A
Re G 0/0/0 10.1.1.2 255.255.255.0 N/A
ing
R2 G 0/0/1 10.1.2.1 255.255.255.0 N/A
rn
Loopback 0 2.2.2.2 255.255.255.255 N/A
e a G 0/0/1 10.1.2.2 255.255.255.0 N/A
eL
G 0/0/2 11.1.2.1 255.255.255.0 N/A
R3
or
S 1/0/1 10.2.2.2 255.255.255.0 N/A
Loopback 0 3.3.3.3 255.255.255.255 N/A
M S 1/0/0 10.2.1.2 255.255.255.0 N/A
R4 S 1/0/1 10.2.2.1 255.255.255.0 N/A
Loopback 0 4.4.4.4 255.255.255.255 N/A
G 0/0/0 11.1.2.2 255.255.255.0 N/A
R5
Loopback 0 5.5.5.5 255.255.255.255 N/A
G 0/0/0 11.1.1.2 255.255.255.0 N/A
R6
G 0/0/1 11.1.3.1 255.255.255.0 N/A

Loopback 0 6.6.6.6 255.255.255.255 N/A
1. Run OSPF and LDP on AR1, AR2, and AR3. Configure area 0 between AR1
and AR2, and area 2 between AR2 and AR3. To reduce the number of
routing entries in area 0, configure OSPF route aggregation on AR2 to
summarize R3’s loopback address.
e n
The Loopback interface address of AR3 is in the routing table on AR1, but does not use
/
m
the 32-bit mask. Therefore, LDP cannot distribute labels. Add static routes.
.c o
e
Interface i
1.1.1.1/32 Direct 0 0 D 127.0.0.1 LoopBack0
aw
u
2.2.2.2/32 OSPF 10 1 D 10.1.1.2
.h
g
3.3.3.0/24 OSPF 10 2 D 10.1.1.2
ni nGigabitEthernet0/0/0
r
lea
3.3.3.3/32 Static 60 0 RD 10.1.1.2 GigabitEthernet0/0/0
://
10.1.1.0/24 Direct 0 0 D 10.1.1.1 GigabitEthernet0/0/0
10.1.1.1/32 Direct 0 0
t tp D 127.0.0. GigabitEthernet0/0/0
10.1.1.255/32 Direct
s
0 0
:h D 127.0.0.1 GigabitEthernet0/0/0
10.1.2.0/24 OSPF
r c e10 2 D 10.1.1.2 GigabitEthernet0/0/0
……
s ou
R
[R1]display mpls lsp
e
n g
-------------------------------------------------------------------------------
i
r n LSP Information: LDP LSP
e a
L
-------------------------------------------------------------------------------
r e FEC In/Out Label In/Out IF Vrf Name
o
M 1.1.1.1/32
2.2.2.2/32
3/NULL
NULL/3
-/-
-/GE0/0/0
2.2.2.2/32 1024/3 -/GE0/0/0
3.3.3.3/32 NULL/1025 -/GE0/0/0
3.3.3.3/32 1025/1025 -/GE0/0/0
2. A backup router AR4 has been added to the SP's network. The links between

AR1 and AR4, between AR3 and AR4 are low-speed links, and run IS-IS.
Ensure that the traffic is preferentially transmitted through AR1-AR2-AR3
and uses AR1-AR4-AR3 as the backup link.
The static routes are configured for the path AR1-AR2-AR3 and IS-IS is configured on
the path AR1-AR4-AR3. IS-IS advertises the specific routes. IS-IS has a higher priority than
static routes and so traffic is transmitted to AR4. To meet the task requirements, change the
priority of static routes to be lower than the IS-IS priority.
n
<R4>dis isis peer

/ e
o m
.c
-------------------------------------------------------------------------------
e i
0000.0000.0001 S1/0/0 0000000002 Up 24s L2
a
--w
u
0000.0000.0003 S1/0/1 0000000001
g
Up 26s L2
.h --
Total Peer(s): 2
i n
nSP's network as VPN1 to
r
aroutes between the CE and
l e
3. Connect the customer devices AR5 and AR6 to the
//
implement mutual access, and configure static
:
tp
PE devices.
ht
After configuration, we can see the route information of VPN1, and CE routers can ping
each other.
s :
c e
<R3>display ip routing-table vpn-instance VPN1
r
o
Routing Tables: VPN1
u
e
Destination/Masks Proto Pre Cost Flags NextHop Interface
R
i n g
5.5.5.5/32 Static 60 0 RD 11.1.2.2 GigabitEthernet0/0/2
rn
e a 11.1.1.0/24 IBGP 255 0 RD 1.1.1.1 GigabitEthernet0/0/1
e L
or
11.1.2.0/24 Direct 0 0 D 11.1.2.1 GigabitEthernet0/0/2
M
255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0
[R5]ping -a 5.5.5.5 6.6.6.6

e n
/
o m
0.00% packet loss
e i .c
a w
hu
g .
4. With the growth of services, the customer leases lines from other SPs. The
customer prefers MPLS VPN. If the link between AR1nand AR6 or between
AR3 and AR5 fails, ensure that the traffic can n
i
ar be switched to the link
e
between R5 and R6. Static routes are still used on the customer's network.
/: /l
t tp
: h
e s
r c
o u
e s
R
i n g
arn
L e
e
or
M Configure a static route on the backup link between R5 and R6 and reduce the priority
of the static route. Create a BFD session between the ISP interfaces of R5 and R6 and
associate the BFD session with the static route. When the BFD session is down, the static
route should be deleted.R5 and R6 use 11.2.1.x/24 to connect together.
[R5]display bfd session all
--------------------------------------------------------------------------------
Local Remote PeerIpAddr State Type InterfaceName
--------------------------------------------------------------------------------

8192 8192 11.1.1.2 Up S_AUTO_PEER -
--------------------------------------------------------------------------------
Total UP/DOWN Session Number : 1/0
5. With the further growth of company's services, the CE devices on the

headquarters network need to be dual homed to PE devices and run BGP.
e n
Tear down the original backup link. Ensure that the traffic is preferentially
/
m
transmitted through AR6-AR1-AR3-AR5, and uses AR6-AR4-AR3-AR5 as
the backup path. Configure only on router AR6.Static routes are still used
.c o
between AR3 and AR5.
e i
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
Add R4 to MPLS VPN. Set up an MP-IBGP peer relationship between R4 and
R3.Establish BGP connection between R6 and PEs. Use network address 11.1.4.0/24 between
n g
R4 and R6, the Headquarter use AS number as 65001.
i
n
r
e a Network NextHop MED LocPrf PrefVal Path/Ogn
e L
r
*> 5.5.5.5/32 11.1.1.1 200 0 100?
o * 11.1.4.1 0 100?
M *> 6.6.6.6/32 0.0.0.0 0 0 i
*> 11.1.1.0/24 0.0.0.0 0 0 i
*> 11.1.2.0/24 11.1.1.1 200 0 100?
* 11.1.4.1 0 100?
*> 11.1.3.0/24 0.0.0.0 0 0 i

*> 11.1.4.0/24 0.0.0.0 0 0 i
<R3>display bgp vpnv4 vpn-instance VPN1 routing-table
VPN-Instance VPN1, Router ID 10.1.2.2:
e n
/
*> 5.5.5.5/32 0.0.0.0 0 0 ?
o m
*>i 6.6.6.6/32 1.1.1.1 0 100 0 65001i
e i .c
* i 4.4.4.4 200 100 0
w
65001i
a
u
.h
*>i 11.1.1.0/24 1.1.1.1 0 100 0 65001i
* i 4.4.4.4 200 100
i n g 0 65001i
*> 11.1.2.0/24 0.0.0.0 0

r n 0 ?
*> 11.1.2.1/32 0.0.0.0 0
// lea 0 ?
p :
t
*>i 11.1.3.0/24 1.1.1.1 0 100 0 65001i
t
:h
* i 4.4.4.4 200 100 0 65001i
*>i 11.1.4.0/24
e s
1.1.1.1 0 100 0 65001i
r c
ou
* i 4.4.4.4 200 100 0 65001i
es
R
6. Add a new NMS to the VPN and ensure the connectivity between the NMS
g
and other network devices. Configure LSW3 in the NMS as the NTP server
i n
and other devices as NTP clients. LSW2 use network 11.1.5.0/24 to connect to
PE.
n
ar
e Add SW2 to the VPN and configure NTP.
eL
[R5]display ntp-service status
or clock status: synchronized
M clock stratum: 3
reference clock ID: 11.1.5.2
nominal frequency: 100.0000 Hz
actual frequency: 100.0000 Hz
clock precision: 2^16
clock offset: -28799419.5995 ms

root delay: 109.89 ms
root dispersion: 0.77 ms
peer dispersion: 0.24 ms
reference time: 15:52:20.935 UTC May 18 2015(D9048934.EF648C71)
Run SNMPv2 on network devices. Use string ‘public’ as RO community,

n
7.
“private” as RW community.
/ e
Configure SNMP on the routers inside VPN1.
o m
8. Configure NQA on the link between AR5 and AR6. Ensure that AR5 .and
i c
we
AR6 can send traps to the NMS server when three consecutive ICMP packets
are dropped. The address of NMS is 11.1.5.254.
a
. hu
Configure NQA. Configure appropriate NQA test instances.
[R6]dis nqa results
i n g
r n
NQA entry(admin, R5R6) :testflag is active ,testtype is icmp
l e a
//
1 . Test 5 result The test is finished
:
tp
Send operation times: 2 Receive response times: 2
ht
:
Completion:no result RTD OverThresholds number: 0
e s
c
Attempts number:1 Drop operation number:0
u r
Disconnect operation number:0 Operation timeout number:0
s o
R e
System busy operation number:0 Connection fail number:0
i n g
Operation sequence errors number:0 RTT Status errors number:0
rn
Destination ip address:5.5.5.5
e a Min/Max/Average Completion Time: 20/30/25
e L
or
Sum/Square-Sum Completion Time: 50/1300
Last Good Probe Time: 2015-05-18 16:58:57.4
M Lost packet ratio: 0 %
9. Configure traffic classifiers on AR6‘s interface Ge0/0/1, Mark traffic of

http/telnet as DSCP AF41 and set the CAR for other traffic. Ensure the
bandwidth of other traffic under 2M.
Configure class-based QoS.

Questions
To implement step 2, which methods can be used? Why?
Configuration List
n
#
sysname R1
/ e
o m
.c
#
ip vpn-instance VPN1
e i
ipv4-family
aw
u
route-distinguisher 100:1
g .h
vpn-target 100:1 export-extcommunity
ni n
r
lea
vpn-target 100:1 import-extcommunity
: //
mpls lsr-id 1.1.1.1
t t p
mpls
s :h
#
r c e
mpls ldp
s ou
#
Re
isis 1
i n g
r n
is-level level-2
e a
L
network-entity 47.0001.0000.0000.0001.00
r e #
o
M interface Serial1/0/1
link-protocol ppp
ip address 10.2.1.1 255.255.255.0
isis enable 1
mpls
mpls ldp

ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
e n
/
#
o m
ip binding vpn-instance VPN1
e i .c
ip address 11.1.5.1 255.255.255.0
aw
u
.h
trust dscp
i n g
r n
// lea
p :
t
ip address 11.1.1.1 255.255.255.0
t
:h
trust dscp
#
e s
r c
ou
interface LoopBack0
es
ip address 1.1.1.1 255.255.255.255
R
g
isis enable 1
#
n i n
ar
e
bgp 100
e L peer 3.3.3.3 as-number 100
or peer 3.3.3.3 connect-interface LoopBack0
M #
ipv4-family unicast
undo peer 3.3.3.3 enable
ipv4-family vpnv4

policy vpn-target
peer 3.3.3.3 enable
ipv4-family vpn-instance VPN1
import-route direct
e n
/
o m
ospf 1
e i .c
area 0.0.0.0
aw
u
.h
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.255
i n g
#
r n
// lea
ip route-static 3.3.3.3 255.255.255.255 10.1.1.2 preference 14
p :
t
#
t
:h
return
e s
r c
ou
#
es
R
g
sysname R2
#
n i n
ar
e
mpls lsr-id 2.2.2.2
e L mpls
or #
M mpls ldp
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp

ip address 10.1.2.1 255.255.255.0
mpls
mpls ldp
e n
/
#
interface LoopBack0
o m
ip address 2.2.2.2 255.255.255.255
e i .c
#
aw
u
.h
ospf 1
area 0.0.0.0
i n g
network 2.2.2.2 0.0.0.0
r n
network 10.1.1.0 0.0.0.255
// lea
p :
t
area 0.0.0.1
t
:h
abr-summary 3.3.3.0 255.255.255.0
network 10.1.2.0 0.0.0.255

e s
r c
ou
#
return
es
R
i n g
n
ar
e
#
e L sysname R3
or #
M ip vpn-instance VPN1
ipv4-family

mpls lsr-id 3.3.3.3
mpls
mpls ldp
e n
/
isis 1
is-level level-2
o m
network-entity 47.0001.0000.0000.0003.00
e i .c
#
aw
u
.h
link-protocol ppp
i n g
ip address 10.2.2.2 255.255.255.0
r n
isis enable 1
// lea
p :
t
mpls
t
:h
mpls ldp
#
e s
r c
ou
es
ip address 10.1.2.2 255.255.255.0
R
g
mpls
n
mpls ldp
i n
ar
e
#
or ip binding vpn-instance VPN1
M ip address 11.1.2.1 255.255.255.0
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
isis enable 1

bgp 100
e n
/
#
ipv4-family unicast
o m
e i .c
aw
u
.h
i n g
ipv4-family vpnv4
r n
policy vpn-target
// lea
p :
t
peer 1.1.1.1 enable
t
:h
peer 4.4.4.4 enable
#
e s
r c
ou
es
import-route direct
R
g
import-route static
#
n i n
ar
e
ospf 1
e L area 0.0.0.1
or network 3.3.3.3 0.0.0.0
M network 10.1.2.0 0.0.0.255
ip route-static vpn-instance VPN1 5.5.5.5 255.255.255.255 11.1.2.2
return

sysname R4
ip vpn-instance VPN1
e n
/
ipv4-family
o m
e i .c
aw
u
.h
#
mpls lsr-id 4.4.4.4
i n g
mpls
r n
#
// lea
p :
t
mpls ldp
t
:h
#
isis 1
e s
r c
ou
is-level level-2
es
network-entity 47.0001.0000.0000.0004.00
R
g
#
n i n
ar
e
link-protocol ppp
e L ip address 10.2.1.4 255.255.255.0
or isis enable 1
M mpls
mpls ldp
link-protocol ppp
ip address 10.2.2.1 255.255.255.0

isis enable 1
mpls
mpls ldp
e n
/
ip address 11.1.4.1 255.255.255.0
o m
trust dscp
e i .c
#
aw
u
.h
interface LoopBack0
ip address 4.4.4.4 255.255.255.255
i n g
isis enable 1
r n
#
// lea
p :
t
bgp 100
t
:h
e s
r c
ou
#
ipv4-family unicast
es
R
g
n i n
ar
e
#
e L ipv4-family vpnv4
or policy vpn-target
return

sysname R5
e n
/
snmp-agent local-engineid 800007DB03000000000000
snmp-agent community read %$%$myajH5!e}TA{{B(PGDg',.Vy%$%$
o m
snmp-agent community write %$%$1\z;+o/>^)PB+`/Y\,\,,.Vy%$%$
e i .c
snmp-agent sys-info version v2c
aw
u
.h
snmp-agent
i n g
ntp-service unicast-server 11.1.5.2
r n
#
// lea
p :
t
t
:h
ip address 11.1.2.2 255.255.255.0
#
e s
r c
ou
interface LoopBack0
es
ip address 5.5.5.5 255.255.255.255
R
g
#
n i n
ip route-static 0.0.0.0 0.0.0.0 11.1.2.1
ar
e
#
e L return
or
M <R6>display current-configuration
sysname R6
snmp-agent local-engineid 800007DB03000000000000
snmp-agent community read %$%$y>=d@L0sHJu!w)XjJSO>,"/t%$%$

snmp-agent community write %$%$Y~~T6i`k&K\A0=RU0U7A,"/t%$%$
snmp-agent sys-info version v2c
snmp-agent target-host trap-hostname NMS address 11.1.5.254 udp-port 162 trap-pa
ramsname TRAPWORD
snmp-agent target-host trap-paramsname TRAPWORD v2c securityname Huawei
e n
/
snmp-agent trap enable
snmp-agent
o m
#
e i .c
aw
u
.h
#
acl number 3001
i n g
r
rule 10 permit tcp source-port eq www destination-port eq www
n
rule 20 permit tcp destination-port eq www
// lea
p :
t
rule 30 permit tcp source-port eq telnet
t
:h
rule 40 permit tcp destination-port eq telnet
#
e s
r c
ou
traffic classifier httptelnet operator or
if-match acl 3001

es
R
g
traffic classifier OTHER operator or
n i n
if-match any
ar
e
#
e L traffic behavior httptelnet
or remark dscp af41
M traffic behavior OTHER
car cir 2000 cbs 376000 pbs 626000 green pass yellow pass red discard
traffic policy POL6
classifier httptelnet behavior httptelnet

ip address 11.1.1.2 255.255.255.0
ip address 11.1.3.1 255.255.255.0
e n
/
traffic-policy POL6 inbound
o m
e i .c
ip address 11.1.4.2 255.255.255.0
aw
u
.h
#
interface LoopBack0
i n g
ip address 6.6.6.6 255.255.255.255
r n
#
// lea
p :
t
bgp 65001
t
:h

e s
r c
ou
#
ipv4-family unicast
es
R
g
n i n
network 6.6.6.6 255.255.255.255
ar
e
network 11.1.1.0 255.255.255.0
e L network 11.1.3.0 255.255.255.0
or network 11.1.4.0 255.255.255.0
peer 11.1.1.1 route-policy setpref import
peer 11.1.4.1 route-policy setmet export
route-policy setpref permit node 10

apply local-preference 200
route-policy setmet permit node 10
apply cost 200
e n
/
nqa test-instance admin R5R6
test-type icmp
o m
destination-address ipv4 5.5.5.5
e i .c
test-failtimes 3
aw
u
.h
send-trap testfailure
frequency 5
i n g
timeout 1
r n
start now
// lea
p :
t
#
t
:h
return
e s
r c
ou
<LSW1>display current-configuration
#
es
R
g
sysname LSW1
#
n i n
ar
e
e L #
or interface Vlanif1
M ip address 11.1.3.2 255.255.255.0
ip route-static 0.0.0.0 0.0.0.0 11.1.3.1
snmp-agent
snmp-agent local-engineid 800007DB034C1FCC8032F5

snmp-agent community read public
snmp-agent community write private
snmp-agent sys-info version v2c v3
return
e n
/
o m
#
e i .c
sysname SW2
aw
u
.h
#
ntp-service refclock-master 2
i n g
#
r n
interface Vlanif1
// lea
p :
t
ip address 11.1.5.2 255.255.255.0
t
:h
#
interface MEth0/0/1
e s
r c
ou
#
es
R
g
#
n i n
ar
e
ip route-static 0.0.0.0 0.0.0.0 11.1.5.1
e L #
or snmp-agent
M snmp-agent local-engineid 800007DB034C1FCCF266EE
snmp-agent community read public
snmp-agent community write private
snmp-agent sys-info version v2c v3
return

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

The privilege of HCNA/HCNP/HCIE:
With any Huawei Career Certification, you have the privilege on http://learning.huawei.com/en to enjoy:
n
 1、e-Learning Courses： Logon http://learning.huawei.com/en and enter Huawei Training/e-Learning
/e

o m
If you have the HCNA/HCNP certificate：You can access Huawei Career Certification and Basic Technology e-Learning
courses.
e i .c
If you have the HCIE certificate: You can access all the e-Learning courses which marked for HCIE Certification Users.
aw

Methods to get the HCIE e-Learning privilege : Please associate HCIE certificate information with your Huawei account, and
hu

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.

g .
 2、 Training Material Download
i n

arn
Content: Huawei product training material and Huawei career certification training material.

//le
Method：Logon http://learning.huawei.com/en and enter Huawei Training/Classroom Training ,then you can download
training material in the specific training introduction page.
p :
 3、 Priority to participate in Huawei Online Open Class (LVC)
t t

s :h
The Huawei career certification training and product training covering all ICT technical domains like R&S, UC&C, Security,
4、Learning Tools: rc e
Storage and so on, which are conducted by Huawei professional instructors.
u

s o
eNSP ：Simulate single Router&Switch device and large network.

R e
WLAN Planner ：Network planning tools for WLAN AP products.

n g
In addition, Huawei has built up Huawei Technical Forum which allows candidates to discuss technical issues with Huawei experts ,
ni
share exam experiences with others or be acquainted with Huawei Products.
a r
 Statement:
L e
r e
This material is for personal use only, and can not be used by any individual or organization for any commercial purposes.
o
M
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 1

HCIE-R&S Huawei Certified Internetwork Expert-Routing and Switching Training Lab Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HCIE-R&S Huawei Certified Internetwork Expert-Routing and Switching Training Lab Guide PDF

Uploaded by

Copyright:

Available Formats

The privilege of HCNA/HCNP/HCIE:

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.

HCIE-R&S Exercise Guide

Chapter 1 RIP Hands-on Exercise Guide...................................................................................... 4

2015-8-31 Huawei Confidential Page 1 of 226

e L Configuration List ..................................................................................................................141

or Chapter 9 WAN Layer 2 Technology Hands-on Exercise Guide ............................................. 146

2015-8-31 Huawei Confidential Page 2 of 226

e L Configuration List ..................................................................................................................213

2015-8-31 Huawei Confidential Page 3 of 226

Chapter 1 RIP Hands-on Exercise Guide

used in large networks.

L e Device Interface IP Address Subnet Mask

2015-8-31 Huawei Confidential Page 5 of 226

R6 E0/0/0 192.168.2.6 255.255.255.0 N/A

Configuration and Verification

r e [R1]display ip routing-table protocol rip

o RIP routing table status : <Active>

Destination/Mask Proto Pre Cost Flags NextHop Interface

2.0.0.0/24 RIP 100 1 D 192.168.1.2 Ethernet0/0/0

20.0.0.0/24 RIP 100 1 D 192.168.1.2 Ethernet0/0/0

34.1.1.0/24 RIP 100 1 D 192.168.1.3 Ethernet0/0/0

2015-8-31 Huawei Confidential Page 6 of 226

192.168.2.0/24 RIP 100 2 D 192.168.1.3 Ethernet0/0/0

[R2]display ip routing-table protocol rip

RIP routing table status : <Active>

34.1.1.0/24 RIP 100 1 D 192.168.1.3 Ethernet0/0/0

a rnthat the metric of routes to service network 1.0.0.0/8 learned on R4 is

Destination/Mask Proto Pre Cost Flags NextHop Interface

1.0.0.0/8 RIP 100 4 D 34.1.1.3 GigabitEthernet0/0/0

2.0.0.0/24 RIP 100 2 D 34.1.1.3 GigabitEthernet0/0/0

20.0.0.0/24 RIP 100 2 D 34.1.1.3 GigabitEthernet0/0/0

2015-8-31 Huawei Confidential Page 7 of 226

192.168.1.0/24 RIP 100 1 D 34.1.1.3 GigabitEthernet0/0/0

1.0.0.0/8 RIP 100 4 D

2.0.0.0/24 RIP 100 2

Destination/Mask Proto Pre Cost Flags NextHop Interface

1.0.0.0/8 RIP 100 4 D 34.1.1.3 GigabitEthernet0/0/0

2.0.0.0/24 RIP 100 2 D 34.1.1.3 GigabitEthernet0/0/0

2015-8-31 Huawei Confidential Page 8 of 226

5.0.0.0/8 RIP 100 1 D 192.168.2.5 Ethernet0/0/0

6.0.0.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0

6.0.2.0/24 RIP 100 1 D 192.168.2.6 Ethernet0/0/0

20.0.0.0/24 RIP 100 2 D 34.1.1.3 GigabitEthernet0/0/0

192.168.1.0/24 RIP 100 1 D 34.1.1.3 GigabitEthernet0/0/0

To perform classful route summarization, summarize 5.0.X.0/24 into 5.0.0.0/8.

192.168.2.4 Ethernet0/0/0 RIP 0:0:6

Number of RIP routes : 3

Destination/Mask Proto Pre Cost Flags NextHop Interface

2015-8-31 Huawei Confidential Page 9 of 226

1.0.0.0/8 RIP 100 5 D 192.168.2.4 Ethernet0/0/0

2.0.0.0/8 RIP 100 3 D 192.168.2.4 Ethernet0/0/0

6.0.0.0/8 RIP 100 2 D 192.168.2.4 Ethernet0/0/0

20.0.0.0/8 RIP 100 3 D 192.168.2.4 Ethernet0/0/0

34.0.0.0/8 RIP 100 1 D 192.168.2.4 Ethernet0/0/0

2.0.0.0/8 RIP 100 3 D 192.168.2.4

5.0.0.0/8 RIP 100 2 D

6.0.0.0/8 RIP 100 2 D

e L Reply from 6.0.0.1: bytes=56 Sequence=3 ttl=255 time=80 ms

or Reply from 6.0.0.1: bytes=56 Sequence=4 ttl=255 time=100 ms

M Reply from 6.0.0.1: bytes=56 Sequence=5 ttl=255 time=80 ms

PING 5.0.0.1: 56 data bytes, press CTRL_C to break

Reply from 5.0.0.1: bytes=56 Sequence=1 ttl=255 time=90 ms