Area 1 - Huawei

Transcription

Area 1 - Huawei

n
e
/
Resource support on website
m
o
c
You can get free E-Learning courses, training materials, product materials, software, cases and so on.

.
i
e
1、40% E-Learning Courses： http://support.huawei.com/learning/NavigationAction!createNavi#navi[id]=_16

w
a
u
Career Certification E-Learning courses: After received any Huawei Career Certification, you will have the
h
.
g
privilege to learn all Huawei Career Certification E-Learning courses.

Partner E-Learning Courses: Any Huawei Partner Engineer have the learning privilege

Free E-Learning Courses: 40% of the total , Any website users have the learning privilege
n
i
n
r
a
e
2、Training Materials： http://support.huawei.com/learning/NavigationAction!createNavi#navi[id]=f2f
l
/ training material are accessible without
Huawei product training material and Huawei career certification
/
:
logon.
p
t
3、 Huawei Online Open Class(LVC)： http://support.huawei.com/ecommunity/bbs/10154479.html
t
h
The Huawei career certification training and product training covering all ICT technical domains like R&S,
:are conducted by Huawei professional instructors
s
UC&C, Security, Storage and so on, which
e
c
4、Product Materials Download: http://support.huawei.com/enterprise/#tabname=productsupport
r
u
5、Software Download: http://support.huawei.com/enterprise/#tabname=softwaredownload
o
s
e
R
For more content, please visit:
g
n
http://learning.huawei.com/en
i
n
r
http://support.huawei.com/enterprise/
a
http://support.huawei.com/ecommunity/
Le
e TECHNOLOGIES CO., LTD.
HUAWEI
1
r
Huawei Confidential
o
PS: to access the resources above you need to logon Huawei website .









n
e
/
m
o
c
.
i
e
NE40E-X Hardware
Description
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
g
n
i
Re
e
L
Copyrig ht © 2011 Hua w ei Technologies Co., Lt d. All right s reserved.
e
r
o
www.huawei.com
Foreword
n
e
/
.
i
e
m
o
c
w
a
u
 HUAWEI NetEngine40E-X Universal Service Router
h
.
g
n a high-end
(hereinafter referred to as the NE40E-X)iis
n
r
a networks. The
router designed for core and backbone
e
l
/
NE40E-X is positioned as the edge
/ or convergence router
:
p
t
on the IP backbone network.
ht
:
s
 Based on the powerful
Versatile
Routing Platform (VRP),
e
c
r
u the following: rich services, large
the NE40E-X features
o
s
e
capacity, highRperformance, high availability.
g
n
i
n
r
a
Le
eht © 2011 Hua w ei Technologies Co., Lt d. All right s reserved.
r
Copyrig
Pa ge2
o
n
e
/
m
o
c
Objectives

.
i
e
w
a
u
Upon completion of this course, you will be h
able to:




e
r
o
.
g
n
i
Describe NE40E-X hardware system architecture
n
r
a
e
Describe NE40E-X boards
l
/
/
:
Describe NE40E-X performance
p parameters
t
t
h
NE40E-X chassis and boards
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Pa ge3
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
1. NE40E-X16/X8/X3 Hardware Introduction
2. NE40E-X2/X1 Hardware Introduction nin
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge4
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge5
n
e
/
m
o
c
Contents
.
i
e
h
.
g
n
i
n
1.1 NE40E-X16 Chassis
w
a
u
r
a
le
/
/
p:
t
t
h
1.4 NE40E-X16/X8/X3 Boards
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
Pa ge6
n
e
/
m
o
Overview-Appearance of NE40E-X16
c
.
i
e
w
①
a
Switching capacity: 12.58T(bidirectional)
u (bidirectional)
Interface capacity：3.2T
h
⑥
.
MPU
1
:
1
redundancy
g
②
n
SFU 3＋1 redundancy
⑦
i
④
n
FAN2＋2 redundancy
r
A Power
aEntry Modules (PEMs)
e
Working
in 4+4 load balancing mode
l
⑧
⑧
/
4＋4
redundancy
⑤
/
:
p
③
t
t
h
⑨ ⑧
⑧
⑤
:
s
e
c
r
④
u
⑦
o
s
Re
g
①
⑥
n
i
n
r
a
e
L
r
Copyrig
Pa ge7
o








No.
Quantity
Module
①
Air intake vent
×2
②
MPU
×2
③
SFU
×4
④
LPU
× 16
⑤
Cabling trough
×2
⑥
Fan module
×4
⑦
Filtering box
×4
⑧
DC power module
×8
⑨
CMU
×1
Overview-Distributed Architecture .
i
m
o
c
1
2
3
17
18
4
5
6
L
P
U
L
P
U
L
P
U
M
P
U
M
P
U
L
P
U
L
P
U
g
n
ni
e
w
7a
u
h
.
SFU
r
a
le
L
P
U
L
P
U
/
/
p:
19
t
t
h
SFU
L
P
U
n
r
a
e
r
o
Le 8
L
P
U
g
n
i
9
u
o
s
:SFU
s
e SFU
c
r
Re
L
P
U
10
20
21
22
L
P
U
L
P
U
L
P
U
L
P
U
L
P
U
L
P
U
11
12
13
14
15
16
Pa ge8
n
e
/
n
e
/
m
o
c
Power Supply System

.
i
e
w
a
u
The NE40E-X16 supports either DC or AC
h
.
g
power supply.

A Power Entry Modules (PEMs) are inserted at the
rear of the chassis, working in 4+4 load balancing
r
a
le
/
/
:
power frames are placed outside the chassis and p
t
t
installed with rectifier modules based on system
h
power. The AC power frames are then :
connected
s
to the input terminals on the DC-PEMs
e to supply
c
power for the system. (In short,
rexternal AC power
u
frames are added to the DC
opower supply system
s
to constitute an AC power
Re supply system).
The NE40E-X16gbackplane is divided into
n
i
four areas, nwith each area having two
r
a
powereinputs. These eight power inputs
L
work
in backup mode.
e
Copyrig
or ht © 2011 Hua w ei Technologies Co., Lt d. All right s reserved.
mode.

n
i
n
In the case of a DC power supply system, eight 70
In the case of an AC power supply system, two AC

Pa ge9
n
e
/
Power Supply System-DC Power Supplyom
c
.
System
ei
Indicator Color
RUN
Green
ALM
Red
:
s
e
c
r
Description
w
a
u
h
.
g power output. If the
Indicates normal
n
iis steady on, it implies the normal
indicator
n
r
output.
a
lePower failure indicator. If the indicator is
/
/
p:
t
t
h
u
o
s
steady on, it indicates the following:

Lightning-proof circuits on the power
module become faulty.

One of the power modules does not
have input power.。
Note : If the NE40E-X16 has a DC power supply system,
n
r
a
e
r
o
Le
g
n
i
Reeight 70 A PEMs work in 4+4 backup mode. Two -48V
power inputs are joined on the board. After the low-
frequency filtering, the two -48 V power inputs for fans
are joined inside the fan module.
Pa ge10
n
e
/
Power Supply System-Architecture of DC
m
o
c
.
Power Supply System
ei
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge11
n
e
/
Power Supply System-AC Power om
c
.
Supply System
ei
w
a
u
Rear view of the AC rectifier module
Front view of the AC rectifier module:
h
.
g
n
i
n
r
a
le
/
/
p:
Name
Color
Status
Power
Green
On
ur
running
Indicator
Protection
Indicator
Yellow
Failure
Indicator
e
r
o
L
i
n
r
Red
a
e
ng
o
s
e
R Off
t
t
h
Error status
:
Off
s
ce
On
Error reasons:
Electricity supply error(no electricity input、lower
voltage )、no output from the power modules.
Temperature Alarm( exceed 65 ℃ to Over-temperature
Shut-down ) ; Dormancy Shut-down (only indication
from the indicator, no report)
Off
On
Overvoltage shutdown、FANs error、Overtemperature Shut-down、errors in power module
n
e
/
Power Supply System-Architecture of AC
m
o
c
.
Power Supply System
ei
w
a
u
Area 1
LPU13
LPU14
LPU1
LPU1
Le
LPU1
n
r
a
g
n
i
SFU
SFU
SFU
SFU
LPU3
DCb4
MPU1
0
1
2
3
LPU15
LPU11
LPU9
LPU10
Re
u
o
s
LPU7
DCa4
t
t
h
area3
DCb3
DCb
MPU0
:
s
e
c
r
DCa3
LPU2
area2
DCb2
LPU1
DCa2
LPU0
DCa
/
/
p:
area1
DCb1
r
a
le
Filter box
LPU12
DCa1
n
i
n
board
System board
e
r
o
h
.
g
AC2
LPU8
AC1
Area 2
area4
board
Filter box
Area 3
Area 4
Pa ge13
n
e
/
m
o
c
Heat Dissipation System-Fan
Rear
NE40E-X16 Air Flow Map
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
t
t
h
e
R
Fan modules locate at the rear of the chassis, and the exhaust design is evenly
g
Fan 2＋2 redundancy
n
i
“ U” shapenair-flow channel, helpful for evenly Heat Dissipation, avoiding dead angle
rair channels for upper and lower frames are independent and dissipate heat separately.
X16: the
a
Le
r
Copyrig
Pa ge14
o




m
o
Heat Dissipation System- Air Filter .c
i
e
w
a
u
h
Air filter ：
.
g
n
i
n filter:
SFU ArearAir
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge15
o
n
e
/
n
e
/
m
o
c
Switching Network
100Gbps Switching Network
B(SFUI-100-B) ：
.
i
e
w
a
u
h
.
g
200Gbps Switching Network B(SFUI-200-B) ：
n
i
n
r
a
le
/
/
p:
LED
RUN
ACT
OFL
e
r
o
t
t
h
: Indictor
s
ethe SFU: If the indicator blinks twice every second (2 Hz),
Before the registration of
c
r state.
u
the system is in the alarm
o
s
After the registration
of the SFU: If the indicator blinks once every two seconds (0.5
e
R
Hz), the system is running normally.
ng is on, it indicates that the SFU is working normally; if the green
If theiindicator
n is off, it indicates that the SFU is faulty.
indicator
r
a
Le When the SFU is working normally, the OFL indicator is off. After the OFL button is
pressed to power off the SFU, the OFL indicator is on.
Switching Network Appearance
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
The NE40E-X16 hass4 SFUs. These 4 SFUs work in 3+1 load
e
R
balancing mode. The 4 SFUs load balance services at the same time.
g
n
When one i
SFU is faulty or being replaced, the other 3 SFUs
n
r take over its tasks to ensure normal delivery of
automatically
a
e
L
services, thus improving system reliability.
r
Copyrig
Pa ge17
o

n
e
/
m
o
c
Control Plane
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
: from the data plane and the
The control plane of the NE40E-X16 is separated
p
t
monitoring plane.
t
h
: and controlling including route calculating,
MPU is responsible for management
s
e
c
monitoring and maintenance.
r
u
o clock module and LAN Switch all use 1:1 hot
Main processing module,
s
e
R
redundancy
g
n
The two MPUs
i work in 1:1 backup mode. Each MPU monitors the status of the
n
r master SRU is faulty, the slave MPU automatically takes over as
other. Ifathe
Le MPU.
the master
r
Copyrig
Pa ge18
o




n
e
/
m
o
c
Contents
.
i
e
h
.
g
n
i
n
w
a
u
r
a
le
/
/
p:
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
Pa ge19
n
e
/
m
o
Overview-Appearance of NE40E-X8
c
.
i
Switching capacity: 7.08T(bidirectional)
e
w
Interface capacity：1.6T (bidirectional)
a
SRU 1：1 redundancy u
h
SFU2＋1 redundancy
.
g
FAN1＋1 redundancy
n
A Power Entry i
Modules (PEMs)
n
①
Working inr2+2 load balancing mode
a
e
l
/
② ②
/
⑥
⑥
:
p
t
⑦ ⑦
ht
③
④
:⑧
s
⑧⑧
⑧
e
c
r
u
⑤
o
⑨ s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge20
o







No.
Quantity
Module
①
Air intake vent
×1
②
SRU
×2
③
SFU
×1
④
LPU
×8
⑤
Cabling trough
×1
⑥
Fan module
×2
⑦
Filtering box
×2
⑧
DC power module
×4
⑨
CMU
×1
n
e
/
m
o
c
Overview-Slot Layout
1
L
P
U
2
L
P
U
3
L
P
U
4
L
P
U
9
S
R
U
:
s
e
c
r
10
11
S
F
U
.
i
e
5
t
t
h
U
L
P
U
11
10
5
8
.h
g
n
ni
r
a
le
S/
/
p: R
6
w
a
u7
L
P
U
L
P
U
L
P
U
6
7
8
u
o
s
Re
1
e
r
o
g3
n
i
2
n
r
a
4
9
Le
Pa ge21
n
e
/
m
o
c
Power Supply System

.
i
e
w
a
u
h
.
g
n
i
n
power supply.

r
a
le
In the case of a DC power supply system, four 70 A
Power Entry Modules (PEMs) are inserted at the
/
/
:
In the case of an AC power supply system, an ACp
t
t
power frame is placed outside the chassis and
h
installed with rectifier modules based on
:system
s
power. The AC power frame is theneconnected to
c to supply
the input terminals on the DC-PEMs
r
u an external AC
power for the system. (In short,
o
s
power frame is addede
to the DC power supply
Ran AC power supply system.)
system to constitute
g
n
i backplane is divided into two
The NE40E-X8
n
areach area having two power inputs.
areas, e
with
L
These four power inputs work in backup mode.
e
r
o
rear of the chassis, working in 2+2 load balancing
mode.


n
e
/
c
.
System
ei
w
a
u
Indicator Color
Description
RUN
Indicates normal power output. If the
Green
h
.
g
n
i
n
indicator is steady on, it implies the
r
a
e failure indicator. If the
lPower
normal output.
/
/
p:
ALM
Red
s:
e
c
r
ou
rn
a
e
L
g
n
i
s
e
R
t
t
h
indicator is steady on, it indicates the
following:

Lightning-proof circuits on the
power module become faulty.

One of the power modules does
not have input power.
Note : If the NE40E-X8 has a DC power supply system,
four 70 A PEMs work in 2+2 backup mode. Two -48V
power inputs are joined on the board. After the low-
frequency filtering, the two -48 V power inputs for fans
e
Copyrig
Lt d. All
right s reserved.
Pa ge23
areCo.,
joined
inside
the fan module.
or ht © 2011 Hua w ei Technologies
n
e
/
Power Supply System-Architecture of DC
m
o
c
.
Power Supply System
ei
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge24
n
e
/
Power Supply System-AC Power Supplyom
c
.
System
ei
Front view of the AC rectifier module
w
a
u
Rear view of the AC rectifier module
h
.
g
n
i
n
r
a
le
/
/
p:
Name
Indictor
:
s
e
c
Off
r
Status
Error
t
t
h Error reason
Status
Power
Green
running
Indicator
Protection
n
r
a
Indicator
e
r
Failure
o
g
n
i
Yellow
On
u
o
s
lower voltage )、no output from the power
Re
Off
Electricity supply error(no electricity input、
modules.
On
Temperature Alarm( exceed 65 ℃ to Overtemperature Shut-down ) ; Dormancy Shut-
Le
down (only indication from the indicator, no
report)
Red
Off
On
Overvoltage shutdown、FANs error、Over-
n
e
/
Power Supply System-Architecture ofom
c
.
AC Power Supply System
ei
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge26
n
e
/
m
o
c
Heat Dissipation System-Fan
.
i
e
NE40E-X8 Air Floww Map
Rear
.
g
n
i
n
a
u
h
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
t
t
h
e
R
Fan modules locate at the rear of the chassis, and the exhaust design is evenly
g
n
“ U” shapeni
air-flow channel, helpful for evenly Heat Dissipation, avoiding dead angle
r
a
e
L
r
Copyrig
Pa ge27
o



n
e
/
m
o
Heat Dissipation System-Air Filter .c
i
e
w
a
Air Filter：
u
h
.
g
n
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
Note:
e
c
urfilter at the air intake vent helps to prevent dust
Placing a black spongeoair
s It is recommended that air filters be removed and
e
from entering the system.
R
cleaned at leastgonce every three months.
n
i
n
r
a
e
L
r
Copyrig
Pa ge28
o


n
e
/
m
o
c
SFU
.
i
e
100Gbps SFUC(SFUI-100-C)
w
a
u
h
.
g
200Gbps SFU C(SFUI-200-C)
n
i
n
r
a
le
/
/
p:
t
t
hDescription
:
s
Before the registration
e of the SFU: If the indicator blinks twice every
c
second (2 Hz), thersystem is in the alarm state.
u of the SFU: If the indicator blinks once every
o
After the registration
s
e
R (0.5 Hz), the system is running normally.
two seconds
g
n
If the
indicator
is on, it indicates that the SFU is working normally; if
i
n green indicator is off, it indicates that the SFU is faulty.
r
the
ea
LED
RUN
ACT
OFL
e
r
o
L
When the SFU is working normally, the OFL indicator is off. After
the OFL button is pressed to power off the SFU, the OFL indicator is
Switching Network Appearance
n
e
/
w
a
u
.
i
e
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge30
m
o
c
n
e
/
m
o
c
Control Plane
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:

t
t
h
The control plane of the NE40E is separated from the data plane and
:
s
e
c
The two SRUs work in 1:1
r backup mode. Each SRU monitors the
u
status of the other.sIfothe master SRU is faulty, the slave SRU
e
R
automatically takes over as the master SRU.
g
n
i
n
r
a
Le
r
Copyrig
Pa ge31
o
the monitoring plane. The SRU is used by the NE40E-X8.

n
e
/
m
o
c
Contents
.
i
e
h
.
g
n
i
n
w
a
u
r
a
le
/
/
p:
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
Pa ge32
n
e
/
m
o
c
Overview-Appearance
.
i
e
w
a
u
Appearance of the NE40E-X3 DC chassis
h
.
g
n
i
n
r
a
Interface
e capacity ：
l
/
240G(bidirectional)
/
p:

t Switching capacity :
t
h 1.08T(bidirectional)
Appearance of the NE40E-X3 AC chassis
:
s
e
MPU 1：1redundency
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge33
o



n
e
/
m
o
c
4
MPU
.
i
e
h
.
g
MPU
LPU
LPU
5
n3
i
n
r
a
le
2
/
/
:
LPUtp
ht
:Slot layout
s
e
c
Slot Number
Quantity Slot
r Width
u
o
s
1～3
3
41mm（1.6 inches)
e
R
g
n
i2
4～5
41mm（1.6 inches)
n
r
a
e
L
r
Copyrig
o
w
a
u
1
Remarks
These slots are used to hold
LPUs.
These slots hold MPUs that
work in 1:1 backup mode.
Pa ge34
n
e
/
m
o
c
Power Supply System

.
i
e
w
a
u
h
.
g
power supply.

n
i
n
Power modules convert the input voltage
r
a
le
into -48 V DC voltage to supply power for
the entire system. The power supply system
/
/
p:
has the following features:

The power supply system consists of
t
t
h
power modules working in 1+1 backup
:
s
mode.
e
c
r
Both AC power modulesuand DC power
ofunctions. DC
s
modules support alarm
e
R
power modules support I2C
g and AC power
n
communications
i
n
modules
support RS485
r
a
e
communications.
L
two AC power modules or two DC


Two
e AC power modules or two DC power
r
omodules work in 1+1 backup mode to
n
e
/
c
.
System
ei
w
a
u
h
.
g
n
i
n
r
a
le

t
t
hU.
The PEM of the NE40E-X3 is
1
:
s
e supply module in NE40E-X3 is located at
The indicator of DC power
c
r
u
the panel of the power
o module.
s
Re module in NE40E-X3 has one input and following
The power supply
g
n
functions:
i
n
r protection, filtering, and short circuit protection
Surge
a
Le
Note：



/
/
p:

Alarm
e
Copyrig

Pa ge36
n
e
/
Power Supply System-AC Power Supplyom
c
.
System
ei
w
a
u
h
.
g
n
i
n

r
a
le
/
/
p:
Note：
t
t
h

The PEM of the NE40E-X3 is 1 U.

The AC power supply module has various protection functions,
:
s
e
c
r
u
o
s
Outgoing overvoltage
protection
e
R
Outgoing
g overvoltage protection
n
i
n
Short
circuit
r
a
e
L Alarm
including:



e
r
o

Pa ge37
Heat Dissipation System -Fan
Air flow in the NE40E-X3 DC chassis(DC)
s:
Air flow in the NE40E-X3 AC chassis
e
c
r
u
o
s
n
r
a
g
n
i
Re
n
e
/
m
o
c
.
i
e
w
a
uair from the
The NE40E-X3 draws in
h
g.from the rear.
left and exhausts nair
i
The air intake n
vent is located at the
r
a
left side of
e the chassis and the air
l
/ vent is located at the rear of
exhaust
/
:chassis.
p
the
t
t
h Fans are back-to-back and two fans in


the frame.

The heat dissipation system consists
of the following components:

One fan module

An air intake vent and an air exhaust
Le
vent
An air filter
e
Copyrig
Fans on power modules


n
e
/
m
o
Heat Dissipation System - Air Filter.c
i
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
/
:
p
t
ht
:
 Note：
s
e
c
r NE40E-X3 is located on the left rear of
The air filter of the
u
o
s
the chassis .Re
g
The airinfilter of the NE40E-X3 can be bent, which facilitates
n
r
amaintenance within a limited space in the rear of the
the
e
L
chassis.
e
Copyrig
Pa ge39


n
e
/
m
o
c
Contents
.
i
e
h
.
g
n
i
n
w
a
u
r
a
le
/
/
p:
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
Pa ge40
n
e
/
m
o
c
NE40E-X16/X8/X3 Boards

.
i
e
w
a
u
NE40E-X16/X8/X3 support boards:
h
.
g
n
i
n

LPU

LPUF-100,4 Sub-slots ,supports L3VPN and MVPN

LPUI-100

LPUF-40,2 Sub-slots

LPUI-40

LPUI-41

LPUS-41

LPUS-20

LPUF-21,2 Sub-slots

LPUF-10,4 Sub-slots
e
r
o
n
r
a
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
g
n
i
Re
Le
Pa ge41
Service Process Unit- Versatile
Service Process Unit C
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
t
t
h
:
s
e
 SPUC Supports NetStream、GRE
and Multicast VPN
c
r
u
o interface and fit for any LPU.
without any physical
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge42
o
n
e
/
Service Process Unit- Flexible Card Versatile
m
o
c
.
Service Unit 10(VSUF-10)
i
e
whas a higha
The VSUF-10 is of a multi-core processing architecture and
u
h
. memory. The
performance multi-core processing engine and a large
g
in
board provides flexible and complicated servicenprocessing
capabilities
r
a
and ensures bandwidth for the user traffic with
e a large throughput.
l
/
/
Software features
:
p
t
FCC
t
h
:
RET
s
e
c
MDI
r
u
o
Hardware featureses
R
Supporting hot
g swap
n
i
n
r
a
Le
r
Copyrig
Pa ge43
o







n
e
/
Service Process Unit- Integrated Versatile
m
o
c
.
Service Unit 20 A(VSUI-20-A)
ei

w
a
The VSUI-20-A, also known as the CR5DVSUI201A, provides
u the
h
.
g
following functions: ：
n
i
n
Encrypts user data to ensure data secrecy.
r
anot modified when being
e
Checks data completeness to ensure that the data is
l
/
transmitted.
/
:
Prevents anti-replay of data by means oftapsequence number and prevents middleman
t
attack by means of authentication. h
:algorithms and keys between devices and provides a
Supports negotiations of security
s
e generation.
c
secure mechanism for online
key
r
u
omodes, that is, transport mode and tunnel mode, to meet
Supports two security
s
requirements of different
Re network structures.
g
n
i
n
r
a
Le
e
r
o





n
e
/
Flexible Card Line Processing Unit(LPUFm
o
c
.
100)
ei

w
The LPUF-100 provides four slots .An FPIC supports the
ua following
functions:
n
i
n
h
.
g
r
a
e
Automatic recovery of configurations/l
/
:
Intermixing with other types of FPICs
p
t
t
h
LPUF-100 Software features:
:
s
e
NSF
c
r
u
o
FRR
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge45
o






Hot swap
n
e
/
m
o
c
LPUF-100 Supporting Subcards
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
48-Port 100/1000Base-CSFP Flexible Card : 24-Port100/1000Base-SFP Flexible Card
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i5-Port10GBase LAN/WAN-XFP Flexible Card A(supporting1588v2)
n
r
a
Le
r
Copyrig
Pa ge46
o
n
e
/
Flexible Card Line Processing Unit(LPUIm
o
c
.
40)(1/2)
ei
w
a
u
 10-Port10GBase LAN/WAN-XFP supports1588v2
h
.
g
n
i
n
r
a
e
l
/
/
:
p
t
 Software features
ht
:
s
IPv4 and IPv6 address e
c
r
u
ICMP
o
s
e
R
L3 routing protocol（
BGPv4、OSPFv2、OSPFv3、IS-IS ）
g
n
Multicast
i protocol（ PIM-SM、Bidir-PIM、PIM SSM、AutoRP ）
n
r
a
Le
r
Copyrig
Pa ge47
o




n
e
/
Flexible Card Line Processing Unit(LPUIm
o
c
.
100)(2/2)
ei
w
a
 16-Port10GBase LAN-SFP + Flexible Card Line Processing
Unit
u
h
.
g
(LPUI-100)
n
i
n
r
a
e
l
/
/
:
p
t
ht
:
 Function
s
e
c
r
IEEE 802.3ae
u
so
IEEE 802.3x FloweControl
R
IEEE802.1q g
Jumbo frames supported by VLAN
n
i Link aggregation
n
IEEE802.3ad
r
a
IEEE
Le 802.1p Label
r
Copyrig
Pa ge48
o





n
e
/
o
c
.
40)
ei
w
a
The Flexible Card Line Processing Unit LPUF-40 providesu two slots,
h
.
g
each of which can hold an FPIC that supports hot n
swapping.
The cards
i
n
support hot swap. The LPUF-40 supports a maximum
of 40-Gbit/s
r
a
e
bandwidth.
l
/
/ and LPUF-40-B.
:
The LPUF-40 has two models: LPUF-40-A
p
t
ht
Software features
:
s
LPUF-40-A supports all software
e features
c
r L3VPN, MVPN, or IPv6., IPv6
LPUF-40-B does not support
u
o
s
Hardware features
Re
g hot swap.
n
LPUF-40 supports
i
n
r of the LPUF-40 supports hot swap.
The a
FPIC
Le
r
Copyrig
Pa ge49
o








n
e
/
m
o
LPUF-40 Supporting Subcards(1/2).c
i
e
w
a
u
h
.
g
n
i
n
r
a
e
l
20-Port100/1000Base-X-SFP
/
20-Port 100/1000Base-X-SFP Flexible Card
/ Card A(supports1588v2)
Flexible
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g Flexible Card B
20-Port10/100/1000Base-RJ45 Flexible Card
n
i
n
r
a
e
L
r
Copyrig
Pa ge50
o
n
e
/
m
o
LPUF-40 Supporting Subcards(2/2).c
i
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
2-Port 10GBase LAN/WAN-XFP Flexible Card
2-Port
/ 10GBase LAN/WAN-XFP
:
p Flexible Card A(supports1588v2)
t
ht
:
s
e
c
r
u
o
s
Re
g Flexible Card B 4-Port 10GBase LAN/WAN-XFP Flexible Card
2-Port 10GBase LAN/WAN-XFP
n
i
n
r
a
Le
r
Copyrig
Pa ge51
o
n
e
/
Integrated Line Processing Unit (LPUI- om
c
.
40)(1/2)
ei
w
a
u
 4-Port 10GBase LAN/WAN-XFP Integrated Line
h
.
g
n
Processing Unit (LPUI-40)
i
n
r
a
 Function
e
l
/
/
:
IEEE 802.3ae
p
t
t
IEEE 802.3x Flow Control h
:
s
e frames supported by VLAN
IEEE802.1q VLAN Jumbo
c
r
u
o aggregation
IEEE802.3ad Link
s
Re
g Label
IEEE 802.1p
n
i
n
r
a
Le
r
Copyrig
Pa ge52
o





n
e
/
Integrated Line Processing Unit (LPUI- om
c
.
40)(2/2)
ei
w
a
u
 40-Port100/1000Base-X-SFP Integrated LinehProcessing
.
g
n
Unit (LPUI-40)
i
n
r
a
 Function
e
l
/
/
:
IEEE 802.3ab
p
t
ht
IEEE 802.3z
:
s
e
IEEE 802.3x Flow Control
c
r
u
o Jumbo frames supported by VLAN
IEEE802.1q VLAN
s
Re
g Link aggregation
IEEE802.3ad
n
i
n
r802.1p Label
IEEE
a
Le
r
Copyrig
Pa ge53
o






n
e
/
m
o
Integrated Line Processing Unit(LPUI-41)(1/3)
c
.
i
e
w feature:
 Integrated Line Processing Unit (LPUI-41) function
a
u
h
.
IPv4 and IPv6 address distribution
g
n
i
n
ICMP
r
a
e
l
/
L3 Route Protocol(BGPv4、OSPFv2、OSPFv3、IS-IS
)
/
:
p
t
Multicast Protocol(PIM-SM、Bidir-PIM、PIM
SSM、AutoRP )
t
h
:
s
e
c
r
u
o
s
Re
g
n
i 8-Port 10GBase LAN/WAN-XFP Integrated Line Processing Unit
n
r
a
Le
r
Copyrig
Pa ge54
o




n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
e
4-Port 10GBase LAN/WAN-XFP
l
/
Integrated Line Processing Unit
/
:
p
t
ht
2-Port 10GBase LAN/WAN-XFP+
:
s
24-Port 100/1000Base-X-SFP
e
c
r
u
o
s
Re
g
n
iProcessing Unit
Integrated Line
n
r
a
Le
r
Copyrig
Pa ge55
o
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
e
4-Port 10GBase LAN/WAN-XFP Integrated Line
l
/
Processing Unit
/
:
(LPUI-41,supports1588v2)
p
t
ht
:
s
2-Port 10GBase LAN/WAN-XFP+
e
c
20-Port 100/1000Base-X-SFP Integrated
r
u
Line Processing Unit（LPUI-41，
o
supports1588v2）
s
e
R
g
n
i
40-Port 100/1000Base-X-SFP
n
r
(LPUI-41，supports1588v2)
a
e
L
r
Copyrig
Pa ge56
o
m
o
c
Line Processing Unit S(LPUS-41) .
i
e
w
a
n
e
/
u
h
.
g
n
ni
r
a
8-Port 10GBase LAN/WAN-XFP Line Processing Unit S(LPUS-41) e
l
/
/
:
p
t
ht
:
s
e
c
r
u
Line Processing Unit S(LPUS-41)
o
s
e
R
g
n
i Line Processing Unit S(LPUS-41)
4-Port10GBase LAN/WAN-XFP
n
r
a
Le
r
Copyrig
Pa ge57
o
m
o
c
Line Processing Unit S(LPUS-20) .
i
e
w
a
n
e
/
u
h
.
g
n
ni
r
a
4-Port10GBase LAN/WAN-XFP Line Processing Unit S(LPUS-20)
e
l
/
/
:
p
t
t
h
:
s
e
c
40-Port100/1000Base-SFP
r
u
o
s
Re
g
n
i
40-Port10/100/1000Base-RJ45
n
r
a
Le
r
Copyrig
Pa ge58
o
n
e
/
o
c
.
21)
ei
w
a
u hold one
 The LPUF-21 provides two slots, each of which can
h
.
g
half-width FPIC.
n
i
n
r
 The LPUF-21 has two models:LPUF-21-A
aand LPUF-21-B.
e
l
/
/
:
p
t
LPUF-21-A supports all software
ht features
: MVPN, IPv6 advanced
LPUF-21-B not support L3VPN,
s
e
c
r
 Hardware features u
o
s
LPUF-21 supports
Re Hot swap
g
n
FPIC ofiLPUF-21 support Hot swap
n
r
a
e
L
r
Copyrig
Pa ge59
o




n
e
/
o
c
.
10)
ei
w
a
ufull-height
 The LPUF-10 provides four slots that can hold
h
.
g
n
FPICs or four half-height FPICs.
i
n
r
a

An FPIC supports the following functions:
e
l
/
/
:
Hot swap
p
t
ht
Automatic recovery of configurations
:
s
e types of FPICs
Intermixing with other
c
r
u
o
s
Re
g
NSF
n
i
n
FRRar
Le
e
r
o





n
e
/
m
o
c
Content
.
i
e
h
.
g
w
a
u
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge61
n
e
/
m
o
c
Content
.
i
e
w
a
u
h
.
g
2. NE40E-X2/X1 Hardware Introduction
n
i
n
2.1 NE40E-X2/X1 Chassis
r
a
le
2.2 NE40E-X2/X1 Board
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge62
Overview-NE40E-X2 System
Structure
n
e
/
.
i
e
m
o
c
w
a
u slots for
 The NE40E-X2 provides two slots for NPUs and eight
h
.
g
PICs. The network process unit on the NE40E-X2
n is NPUI-20.
i
n the NPUI-20. The
r
All the PICs perform data switching through
a
e
l capability of up to
NPUI-20 has a bidirectional processing
/
/
:
p capacity of the NE40E-X2 is
20Gbit/s. The maximum interface
t
t
h
75.2Gbit/s.
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge63
o
Overview-NE40E-X1 System
Structure
n
e
/
.
i
e
m
o
c
w
a
u slots for
 The NE40E-X1 provides one slot for the NPU and four
h
.
g
PICs. The network process unit on the NE40E-X1
n is NPUI-20.
i
rn
All the PICs switch data with each otherathrough
the NPUI-20.
e
l
The NPUI-20 has a bidirectional data/ processing capability of
/
:
p
up to 20Gbit/s. The maximum interface
capacity of the NE40Et
t
h
X1 is 52Gbit/s.
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge64
o
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
Re
Slot layout of the NE40E-X2
n
r
a
e
r
o
g
n
i
t
t
h
Slot layout of the NE40E-X1
Le
Pa ge65
Power Supply System
n
e
/
.
i
e
m
o
c
w
a
uwhich work
 DC Power Supply System is powered by two PSUs,
h
.
g
in 1+1 backup mode. work in 1+1 backup mode.
n
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge66
o
Heat Dissipation System
n
e
/
.
i
e
m
o
c
w
a
u
 The NE40E-X8 draws in air from the left andhexhausts
air
.
g
n
from the right.
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Air flow in
Air flow in the NE40E-X1
Rethe NE40E-X2
g
n
i
n
r
a
Le
r
Copyrig
Pa ge67
o
n
e
/


m
o
Data Plane Architecture of the NE40E-X1
c
.
i
e
NPUs are key parts on the
w
a
u
NE40E-X2/X1 and are responsible
h
.
g
for data processing and data
n
i
switching between PICs (Physical
n
r
a
Interface Card) and
e
l
/
NPUs(Network Processing Unit) .
/
:
p
t
The procedure for data
t
h
processing is as follows:
:
s
The IP packets sent from PICs and e
c
r
2x10G interfaces on an NPU u
o
converge at a convergences
e
R
module. ；
g IP packets.
n
The NP processes
the
i
n
r performs traffic
The TM module
a
management
Le on the IP packets.
eFabric Interface Chip (FIC)
The
r
o




n
e
/


m
o
Data Plane Architecture of the NE40E-X2
c
.
i
e
w
a
NPUs are key parts on the
u
h
NE40E-X2/X1 and are
.
g
n
responsible for data processing
i
n
r
and data switching between
a
e
l
PICs (Physical Interface Card)
/
/
:
and NPUs(Network Processing
p
t
Unit)
ht
:
The procedure for data
s
e
c
processing is as follows:
r
u
The IP packets sent from PICsoand
s
2x10G interfaces on an NPU
e
R
converge at a convergence module.
g IP packets.
n
The NP processes
the
i
n
r performs traffic
The TM module
a
management
Le on the IP packets.
eThe Fabric Interface Chip (FIC)
r
o performs IP packet switching.




n
e
/
m
o
Integrated Line Processing Unit NPUI-20
c
.
i
e
w
a
u
 The NPUI-20 has the bidirectional 20-Gbit/s forwarding
h
.
g
capability, and all subcards switch data through
n the NPUI-20.
i
rn interfaces that
An NPUI-20 provides two 10G Ethernet aoptical
e
l
can work in the WAN or LAN mode /
and can be installed with
/
:
p
XFP optical modules.
t
t
h
 NE40E-X1 chassis can install an NPUI-20.
:
s
e
c
 NE40E-X2 chassis canrinstall an NPUI-20.
u
o
s
e
R
g
n
i
n
r
NPUI-20 panel
a
Le
r
Copyrig
Pa ge70
o
Control Plane
n
e
/
.
i
e
m
o
c
w
a
The function of control plane is implemented by the MPU.
u
h
.
g
MPU can be equipped with a single MPU or double
n MPUs (in backup
i
n
mode).
r
a
e
l works and the slave
In the case of double MPUs, the master MPU
/
/
:
MPU is in the standby state.
p
t
t
h
MPUs support two switchover modes: failover and manual switchover.
:
s
e functional units. By integrating the
The MPU integrates multiple
c
r
u
system control and management
unit, clock unit, and system
o
s
e
maintenance unit,
R the MPU provides the functions of the control plane
g plane.
and maintenance
n
i
n
r
a
MPUG panel
Le
r
Copyrig
Pa ge71
o





n
e
/
m
o
c
Content
.
i
e
w
a
u
h
.
g
2. NE40E-X2/X1 Hardware Introduction
n
i
n
2.1 NE40E-X2/X1 Chassis
r
a
le
2.2 NE40E-X2/X1 Board
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge72
n
e
/
m
o
c
NE40E-X2/X1 Board(1/4)

.
i
e
w
a
u
h
.
g
NE40E-X2/X1 supporting boards:







8-Port 100/1000Base-X-SFP (HIC)
n
i
n
r
a
8-Port 100/1000Base-X-SFP (HIC,supports
1588v2)
e
l
/
/
: 1588v2)
8-Port 100Base-X-SFP(FIC, supports
p
t
t
8-Port 100Base-RJ45(FIC, hsupports 1588v2)
:
s
e
16-Port E1(75ohm)(FIC)
c
r
u
o
16-Port E1(120ohm)(FIC)
s
Re
g
AuxiliarynInterface
and 4-Port 100Base-RJ45 (FIC,
i
n
supports1588v2)
r
a
Le
1-Port Channelized OC-3c/STM-1c POS-SFP (FIC)
e
Copyrig
Pa ge73

n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
8-Port100/1000Base-X-SFP (HIC)
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
8-Port100/1000Base-X-SFP (HIC,supports1588v2)
Pa ge74
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
t
t
h
8-Port100Base-X-SFP (FIC,supports1588v2)
:
s
e
c
r
u
o
s
rn
e
r
o
a
e
L
g
n
i
Re
8-Port100Base-RJ45 (FIC,supports1588v2)
Pa ge75
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
16-Port E1(120ohm) (FIC)
:
s
e
c
r
u
o
s
g
n
i
Re
t
t
h
Auxiliary Interface and 4-Port100Base-RJ45
(FIC, supports1588v2)
n
r
1-Port Channelized
a OC-3c/STM-1c POS-SFP (FIC)
e
L
r
Copyrig
o
Pa ge76
n
e
/
m
o
c
Summary


.
i
e
w
a
u
h
.
g
NE40E-X16/X8/X3 Hardware

NE40E-X16/X8/X3 Chassis

NE40E-X16/X8/X3 Board
NE40E-X2/X1 Hardware


e
r
o
:
s
e
c
NE40E-X2/X1 Board
r
u
o
s
Re
g
n
i
n
r
a
Le
NE40E-X2/X1 Chassis
n
i
n
r
a
le
/
/
p:
t
t
h
Pa ge77
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank :you
//
p
www.huawei.com
t
t
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
h
n
e
/
m
o
c
.
i
e
w
a
u
h
NE40E-X Router
.
g
n
i
n
Products Parts
r
a
e
l
/
/
Replacement tp:
ht
Introductiones:
rc
u
o
s
n
r
a
g
n
i
Re
e
L
e
r
o
www.huawei.com
Objectives
n
e
/
.
i
e
w
a
u to:
 Upon completion of this course, you will be h
able
.
g
Replace parts of NE40E-X series productsin
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge2
o

m
o
c
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. Overview of Parts Replacement
n
i
n
2. Replacing Boards
r
a
le
3. Replacing Other Parts
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge3
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. Overview of Parts Replacement
n
i
n
2. Replacing Boards
r
a
le
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge4
n
e
/
m
o
c
Basic Operation Process
.
i
e
w
a
u
Start
h
.
g
n
i
n
Assess the feasibility of the operation
r
a
e parts
l
Prepare tools and spare
/
/
:
p
t measures
Take protective
t
h
:
s
eReplace parts
c
r
u
so
n
r
a
e
r
o
Le
g
n
i
e the functions of the new parts
RVerify
Return the faulty parts for repair
End
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
2. Replacing Boards
n
i
n
2.1 Overview of Boards
r
a
le
2.2 Replacing Boards
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge6
Mechanical Specifications of
Boards
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
Common LPU
1 Captive screw
2 Ejector lever
3 Connector
4 Bolt
e
r
o
Le
n
r
a
g
n
i
s
e
R
ou
:
s
e
c
r
t
t
h
FPIC LPU
FPIC
1 Captive screw
1 Captive screw
2 Subcard slot 0
2 Connector
3 Subcard slot 1
4 Ejector lever
5 Connector
n
e
/
m
o
c
Installation of Boards
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s LPU
Installing a common
e
R
g
1 Connector
n
i
n
2 Backplane
r
a
Le
r
Copyrig
o
Installing an FPIC
Pa ge8
n
e
/
m
o
c
Slots Layout
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
uSlots layout on the NE40E-X8
o
s
Slots layout on the NE40E-X3
n
r
a
e
r
o
g
n
i
:
s
e
c
r
t
t
h
Re
Le
Slots layout on the NE40E-X16
Pa ge9
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
2. Replacing Boards
n
i
n
2.1 Overview of Boards
r
a
le
2.2 Replacing Boards
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge10
n
e
/
m
o
c
Replacing an MPU/SRU (1)
Step1 Check the version of the running software package.
w
a
u
.
i
e
h
.
Run the display version command to check the version of the g
running software
n
i
package.
n
r
a
Step2 Prepare a new MPU/SRU and check whether
e there is any bent pin in the
l
/bent pin, copy the software
connector. After determining that there is no
/
:Step 1 to the root directory of CF
p
package and configuration file checked in
t
t
card 1 of the new MPU/SRU.
h
:
s
Step3 Save the current configuration.
e
c
Run the save command torsave the current configuration.
u
o
s
Run the compare configuration
command to compare the saved configuration file and
e
R
the current configuration
file.
g
n
Step4 Checkithe location of the MPU/SRU to be replaced.
n
r
Before
a pulling out an MPU/SRU that is to be replaced, you should first determine the
e
L of the MPU/SRU, for example, the cabinet, chassis, and slot where the
location
ehtMPU/SRU
r
Copyrig
w ei Technologies Co., Lt d. All right s reserved.
Pa ge11
o © 2010 Huaresides.












.
i
e
m
o
c
w
a
Step5 Check whether the MPU/SRUto be replaced is the master
MPU/SRU.
u
h
.
Run the display device command to check the slot number of g
the current MPU/SRU. If
n
i the slave switchover
the MPU/SRU to be replaced is the master one, you must run
n
rthe master/slave switchover. If
command on the console interface to forcibly perform
a
e
the output is displayed as follows on the console l
interface, it indicates that the
/ command to check the slot
/
switchover is successful. Then, run the display
device
:
p
number of the MPU/SRU after the master/slave
t switchover.
t
[HUAWEI] slave switchover enable h
: This operation will switch the slave board
s
[HUAWEI] slave switchoverWarning:
e
c
to the master board. Continue?[Y/N]:y
r
u
Switching....................................................................
o has been switched slave successfully, and it will be
s
........OK This board
e
R
reset!
g
n
Step6 Remove
the
cables from the MPU/SRU and label the cables.
i
n
r
a off the MPU/SRU to be replaced.
Step7 Power
e
L
Press and hold the OFL button on the panel of the MPU/SRU for six seconds till the
e OFFLINE indicator is on. It means that the MPU/SRU is powered off.
r
o


n
e
/

n
e
/
m
o
c

Step8 Pull out the MPU/SRU to be replaced from the chassis.



e
r
o
w
a
u
.
i
e
h
.
Wear the ESD-preventive wrist strap and connect the grounding
g terminal to the ESD
n
i
jack on the rack.
n
rthe two captive screws on the
a
Turn the cross screwdriver counter-clockwise to loosen
e
l
board.
/
/
:
Turn the ejector levers on the panel of thepMPU/SRU
outward and upward. When the
t
ejector levers and the panel form a 45-degree
t angle, the MPU/SRU is removed from
h
the backplane.
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le


e
r
o
n
e
/
.
i
e
m
o
c
w
a
Hold the ejector levers on the panel of the MPU/SRU and pull out the
MPU/SRU
u
h
smoothly from the chassis along the guide rail of the slot. When.the MPU/SRU is 40
g
n
cm (15.75 in.) out of the chassis, support the lower edge of the MPU/SRU with one
i
n
hand and hold the panel of the MPU/SRU with the other
hand. Then, pull out the
r
a
e
MPU/SRU smoothly from the slot.
l
/
/
Place the MPU/SRU that is removed in the ESD-preventive
bag.
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Pa ge14
n
e
/
m
o
c

Step9 Insert the new MPU/SRU into the chassis.


e
r
o
.
i
e
h
.
g
w
a
u
n
i
Support the lower edge of the new MPU/SRU with one hand
n and hold the panel with
r
a into the chassis along the
the other hand. Then, insert the new MPU/SRU smoothly
e
l when the ejector levers on
guide rail of the slot. Stop sliding the MPU/SRU/forward
/
the front panel of the MPU/SRU reaches the:chassis.
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Take out the new MPU/SRU from the ESD-preventive bag.


e
r
o
n
e
/
.
i
e
m
o
c
w
a
Turn the ejector levers on the MPU/SRU outward and upward to form
a 45-degree
u
h turn the ejector
angle, and at the same time push the MPU/SRU into the slot. Then,
.
g
n
levers inward and downward till the panel of the MPU/SRU touches the slot.
i
n
r captive screws.
Turn the cross screwdriver clockwise to tighten the two
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Pa ge16
n
e
/
m
o
c

Step10 Check the running status of the new MPU/SRU.
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
w
a
u
Pa ge17
.
i
e
n
e
/
m
o
c
Replacing an SFU (1)
Step1 Check the location of the SFU to be replaced.
w
a
u
.
i
e
h
.
Before pulling out an SFU that is to be replaced, you should first
g determine the
n
i
location of the SFU.
n
ra label to identify the SFU.
a
Locate the SFU to be replaced in the chassis and attach
e
l
/there is any bent pin in the
Step2 Prepare a new SFU and check whether
/
:
p
connector.
t
t
h
Step3 Power off the SFU to be replaced.
:
s
Press and hold the OFL buttoneon the panel of the SFU for six seconds till the OFFLINE
cthe SFU is powered off.
r
indicator is on. It means that
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyrig
Pa ge18
o






n
e
/
m
o
c

Step4 Pull out the SFU to be replaced from the chassis.



e
r
o
w
a
u
.
i
e
h
.
n
i
jack on the rack.
n
ra cross screwdriver.
a
Loosen the two captive screws counter-clockwise with
e
l
Turn the ejector levers on the panel of the SFU /
/
: angle, the SFU is removed from the
p
t
backplane.
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le


e
r
o
n
e
/
.
i
e
m
o
c
w
a
Hold the ejector levers on the panel of the SFU and pull out the SFUusmoothly from
h
the chassis along the guide rail of the slot. When the SFU is 30 .
cm to 40 cm (11.81 in.
g
n
to 15.75 in.) out of the chassis, support the lower edge of the SFU with one hand and
i
n
hold the panel of the SFU with the other hand. Then, pull
out the SFU smoothly from
r
a
e
the slot.
l
/
/
Place the SFU that is pulled out in the ESD-preventative
bag.
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
n
e
/
m
o
c

Step5 Insert the new SFU into the chassis.


e
r
o
.
i
e
h
.
g
w
a
u
n
i
Support the lower edge of the new SFU with one hand and
n hold the panel with the
r
a chassis along the guide rail of
other hand. Then, insert the new SFU smoothly into the
e
l levers on the front panel of
the slot. Stop sliding the SFU forward when the/ejector
/
the SFU reaches the chassis.
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Take out the new SFU from the ESD-preventive bag.


e
r
o
n
e
/
.
i
e
m
o
c
w
a
Turn the ejector levers on the SFU outward and upward to form a 45-degree
angle,
u
h
and at the same time push the SFU into the slot. Then, turn the.ejector levers inward
g
n
and downward till the panel of the SFU touches the slot.
i
n
r captive screws.
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
n
e
/
m
o
c

.
i
e
w
a
u
Step6 Check the running status of the new SFU.
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge23
n
e
/
m
o
c
Replacing an LPU (1)
Step1 Check the location of the LPU to be replaced.
w
a
u
.
i
e
h
.
Before pulling out an LPU that is to be replaced, you should first
g check the location of
n
the LPU, for example, the cabinet, chassis, and slot whereithe LPU resides.
n
r
a a label to identify the LPU.
Locate the LPU to be replaced in the chassis and attach
e
l
/
Step2 Check whether there is any bent pin in
the connector of the new LPU.
/
:
p
Step3 Power off the LPU to be replaced.
t
t
h
Press and hold the OFL button on the panel of the LPU for six seconds till the OFFLINE
:LPU is powered off.
s
indicator is on. It means that the
e
c
r the LPU and label the cables to mark the
Step4 Remove the cablesufrom
onumbers.
s
corresponding interface
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge24
o







n
e
/
m
o
c

Step5 Pull out the LPU to be replaced from the chassis.



e
r
o
w
a
u
.
i
e
h
.
n
i
jack on the rack.
n
ra cross screwdriver.
a
Loosen the two captive screws counter-clockwise with
e
l
Turn the ejector levers on the panel of the LPU /
/
: angle, the LPU is removed from the
p
t
backplane.
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le


e
r
o
n
e
/
.
i
e
m
o
c
w
a
Hold the ejector levers on the panel of the LPU and pull out the LPU
smoothly from
u
h
the chassis along the guide rail of the slot. When the LPU is 40 .
cm (15.75 in.) out of
g
n
the chassis, support the lower edge of the LPU with one hand and hold the panel of
i
n
the LPU with the other hand. Then, pull out the LPU smoothly
from the slot.
r
a
e
Place the LPU that is pulled out in the ESD-preventive
l bag.
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
n
e
/
m
o
c

Step6 Insert the new LPU into the chassis.


e
r
o
.
i
e
h
.
g
w
a
u
n
i
Support the lower edge of the new LPU with one hand and
n hold the panel with the
r
other hand. Then, insert the new LPU smoothly into a
the chassis along the guide rail of
e
l lever on the front panel of the
the slot. Stop sliding the LPU forward when the/ejector
/
LPU reaches the chassis.
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Take out the new LPU from the ESD-preventive bag.


e
r
o
n
e
/
.
i
e
m
o
c
w
a
Turn the ejector levers on the LPU outward and upward to form a 45-degree
angle,
u
h
and at the same time push the LPU into the slot. Then, turn the.ejector levers inward
g
n
and downward till the panel of the LPU touches the frame.
i
n
r captive screws.
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
n
e
/
.
i
e
m
o
c
w
a
Step7 Connect the cables to the corresponding interfaces in the
original
u
h
.
sequence.
g
n
i
Step8 Check the running status of the new LPU.
n
r
a
e
Step9 Check service operations.
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge29
o



n
e
/
m
o
c
Replacing an FPIC (1)
Step1 Check the location of the FPIC to be replaced.
w
a
u
.
i
e
h
.
Before pulling out an FPIC to be replaced, you should first check
g the location of the
n
FPIC, for example, the cabinet, chassis, and slot where theiFPIC resides. Then, locate
n
r
the FPIC to be replaced in the chassis and attach a label
to identify the FPIC.
a
e
l
Step2 Check whether there is any bent pin in/the connector of the new FPIC.
/
:
p label the cables to mark the
Step3 Pull out the cables from the FPICtand
t
corresponding interface numbers. h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge30
o




n
e
/
m
o
c

.
i
e
w
a
u
Step4 Pull out the FPIC to be replaced from the LPU.




e
r
o
h
.
Wear the ESD wrist strap and connect the ground terminal tog
the ESD jack on the rack.
n
i two captive screws.
Turn the Phillips screwdriver counter-clockwise to loosennthe
r
a
Hold the captive screws of the FPIC and pull out the
eFPIC.
l
/
Place the removed FPIC into the ESD bag.
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Pa ge31
n
e
/
m
o
c

Step5 Insert a new FPIC into the LPU.



e
r
o
.
i
e
w
a
u
h
.
g
n
i
Hold the captive screws of the FPIC, and insert the FPIC n
smoothly along the guide rails
r
a
of the slot till the FPIC is completely seated in the slot.
e
lthe two captive screws
/
Turn the Phillips screwdriver clockwise to tighten
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
Take out the new FPIC from the ESD bag.
Pa ge32



n
e
/
.
i
e
m
o
c
w
a
Step6 Connect the cables to the corresponding interfaces in the
original
u
h
.
sequence.
g
n
i
Step7 Check the running status of the new FPIC.
n
r
a
e
Step8 Check whether services are normal.
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
e
r
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
n
i
n
3.1 Replacing a Fan Frame
3.2 Replacing a Power Module
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge34
Introduction to a Fan Module
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
n
r
a
e
r
o
g
n
i
u
o
s
Re
Fan module of the NE40E-X3
t
t
h
Le
Pa ge35
n
e
/
Replacing the Fan Frame of the om
c
.
i
NE40E-X3 (1)
e
w

Step1 Check the location of the fan frame to be replaced.
.
g
n where the fan frame
i
location of the fan frame, for example, the cabinet and chassis
n
r
resides. Then, find the fan frame to be replaced in the
chassis
and attach a label to
a
e
l
the panel to identify the fan frame.
/
/
:and connect the grounding terminal
Step2 Wear the ESD-preventive wrist strap
p
t
t
to the ESD jack on the rack.
h
:to loosen the captive screws on both ends of
Step3 Turn the cross screwdriver
s
e
c
the fan frame.
r
u
o the fan frame and draw out the fan frame by 5 cm
Step4 Hold the handleson
e
R
(1.97 in.). When the fans stop rotating, pull out the fan frame completely.
g
n
i
n
r
a
Le
e
r
o




a
u
h
Before pulling out a fan frame that is to be replaced, you should first check the
n
e
/
Replacing the Fan Frame of the om
c
.
i
NE40E-X3 (2)
e
w

Step5 Insert the backup fan frame into the chassis.
.
g
n and slowly along the
i
frame with the other hand. Then, insert the fan frame smoothly
n
r
guide rail of the slot till the back of the fan frame is connected
properly to the
a
e
l
backplane of the chassis.
/
/
: frame to the chassis by tightening
Step6 Turn the cross driver to fasten thepfan
t
t
the captive screws.
h
:
s
e
c
r
u
o
s
Re
g
n
ithe functions of the new fan frame.
n
Step7 Verify
r
a
Le
e
r
o



a
u
h
Hold the handle of the fan frame with one hand and support the bottom of the fan
n
e
/
Replacing the Fan Module of the om
c
.
i
NE40E-X8/X16 (1)
e
w

Step1 Check the location of the fan frame to be replaced.
.
g
n where the fan frame
i
location of the fan frame, for example, the cabinet and chassis
n
r
resides. Then, find the fan frame to be replaced in the
chassis
and attach a label to
a
e
l
the panel to identify the fan frame.
/
/
:and connect the grounding terminal
Step2 Wear the ESD-preventive wrist strap
p
t
t
to the ESD jack on the rack.
h
:to loosen the captive screws on both ends of
s
e
c
the fan frame.
r
u
o the fan frame and draw out the fan frame by 5 cm
Step4 Hold the handleson
e
R
(1.97 in.). When the fans stop rotating, pull out the fan frame completely.
g
n
i
n
r
a
Le
e
r
o




a
u
h
Before pulling out a fan frame that is to be replaced, you should first check the
n
e
/
Replacing the Fan Module of the om
c
.
i
NE40E-X8/X16 (2)
e
w

a
u
h
Step5 Hold the upper and lower handles of the fan module, and slowly and
.
g
n Turn the cross
i
back of the fan module properly connects to the backplane.
n
r
screwdriver to fasten the fan frame to the chassisaby tightening the captive
e
l
screws.
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Step6 Verify the function
Re of the new fan module.
g
n
i
n
r
a
Le
e
r
o
horizontally insert the fan module along the guide rails in the slot until the

n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
n
i
n
3.1 Replacing a Fan Frame
3.2 Replacing a Power Module
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge40
m
o
c
Introduction to a Power Module i.
e
w
a
n
e
/
u
h
.
g
n
ni
r
a
le
DC power module of NE40E-X3
:
s
e
c
r
t
t
h
/
/
p:
DC power module of NE40E-X8/16
u
o
s
g
n
i
Re
n
r
AC power
AC power module of NE40E-X8/16
a module of NE40E-X3
e
L
r
Copyrig
Pa ge41
o
n
e
/
Replacing an AC Power Module ofom
c
.
i
NE40E-X3 (1)
e
w

Step1 Check the location of the power module to be replaced.
.
g
nresides. Then, locate the
module, for example, the cabinet and chassis where the power module
i
n panel to identify the power
power module to be replaced in the chassis and attach a label to the
r
a
module.
e
lon the power distribution cabinet.
/
Step2 Switch off the corresponding air circuit breaker
/
:
Thus, the power module to be replaced is powered
p off. In addition, the power module to
t
be replaced must be switched off.
ht
Step3 Wear the ESD-preventive wrist :
strap and connect the grounding terminal to the ESD
s
e
jack on the rack.
c
rthe power module to be replaced.
u
Step4 Remove the cables from
o
s
Step5 Loosen the captive
Re screws on the right side of the power module with a cross
screwdriver.
g
n
ihandle on the power module and pull the power module out of the chassis.
Step6 Hold the
n
r
a
Le
e
r
o






a
u
h
Before pulling out a power module that is to be replaced, you should first check the location of the
n
e
/
c
.
i
NE40E-X3 (2)
e
w

a
u
h
Step7 Insert the backup power module into the chassis. Hold the handle of the
.
g
n rail of the slot till
i
Then, insert the module smoothly and slowly along the
guide
n
r
a of the chassis
the back of the module properly connects the backplane
e
l
/
Step8 Fasten the power module to the chassis
by screwing the captive screws
/
:
p
with a cross screwdriver.
t
t
Step9 Connect the cables to the newh power supply module.
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge43
o
power module with one hand and support the bottom with the other hand.


n
e
/
c
.
i
NE40E-X3 (3)
e
w

Step10 Verify the functions of the new power module.
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge44
a
u
h
n
e
/
Replacing a DC Power Module of om
c
.
i
NE40E-X3 (1)
e
w

Step1 Check the location of the power module to be replaced.
.
g
of the module, for example, the cabinet and chassis where the power n
module resides. Then,
i
locate the power module to be replaced in the chassis and attach n
a label to the panel to
r
a
identify the power module.
e
lon the power distribution
/
Step2 Switch off the corresponding air circuit breaker
/
:
cabinet. Thus, the power module to be replaced
p is powered off. In addition, the
t
power module to be replaced must be switched
ht off.
Step3 Wear the ESD-preventive wrist :
strap and connect the grounding terminal to
s
e
the ESD jack on the rack.
c
rthe power module to be replaced.
u
Step4 Remove the cables from
o
s
Step5 Loosen the captive
Re screws on both sides of the power module with a cross
screwdriver.
g
n
i
n
r
a
Le
e
r
o





a
u
h
Before pulling out a power module that is to be replaced, you should first check the location
n
e
/
c
.
i
NE40E-X3 (2)
e
w

a
u
h
Step6 Turn the ejector levers on the panel of the power module outward and
.
g
n
i
n
upward. When the ejector levers and the panel form a 45-degree angle, the
power module is removed from the backplane.
r
a
Step7 Hold both sides of the power module and epull the power module out of
l
/
the chassis.
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge46
o

n
e
/
c
.
i
NE40E-X3 (3)
e
w

Step8 Insert the backup power module into the chassis.
a
u
h
.
g
n
slot. Ensure that the power module is in good contact withithe backplane of the
n
r
chassis.
a
e
l with both hands till the
Step9 Turn the ejector levers inward and downward
/
/
:
power module touches the slot.
p
t
t
Step10 Fasten the power module tohthe chassis by screwing the captive screws
:
with a cross screwdriver.
s
e
c
rcables to the power module in original sequence.
Step11 At last, connect the
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge47
o




Hold both sides of the power module and insert the module into the guide rail of the
n
e
/
c
.
i
NE40E-X3 (4)
e
w

Step12 Verify the functions of the new power module.
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge48
a
u
h
n
e
/
Replacing the DC PEM of the
m
o
c
.
i
NE40E-X8/16 (1)
e
w

Step1 Check the location of the PEM to be replaced.
.
g
n a label to the panel to
PEM resides. Then, find the PEM to be replaced in the chassis and attach
i
n
identify the PEM and avoid misoperation.
r
a
Step2 Wear the ESD-preventive wrist strap and connectethe grounding terminal to the ESD
l
/
jack on the chassis.
/
:
p on the power distribution cabinet.
Step3 Turn off the corresponding air circuit breaker
t
t
Thus, the PEM to be replaced is poweredhoff. In addition, switch off the PEM.
: module to be replaced.
Step4 Remove the cables from the power
s
e
c
r to loosen the captive screws on the PEM.
u
o
Step6 Hold the handle onsthe PEM with one hand and hold the PEM with the other hand.
Re
Then, pull the PEM horizontally
and slowly out of the chassis.
g
n
i
n
r
a
Le
e
r
o






a
u
h
Before removing the old PEM, check its location, for example, the cabinet and chassis where the
n
e
/
m
o
c
.
i
NE40E-X8/16 (2)
e
w

Step7 Insert the new PEM into the chassis.
a
u
h
.
g
nin the slot until the back
i
insert the PEM horizontally and slowly along the guide rails
rncross screwdriver to fasten
of the PEM properly connects to the backplane, Turnathe
e
l
the PEM to the chassis by tightening the captive screws.
/
/
: in original sequence.
Step8 Connect the cables to the power module
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge50
o


Hold the handle on the PEM with one hand and the PEM with the other hand. Then,
n
e
/
m
o
c
.
i
NE40E-X8/16 (3)
e
w

Step9 Verify the function of the new PEM.
.
g
n
i
n
r
a
le
/
/
p:
…………….
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge51
a
u
h
Summary
n
e
/
.
i
e
m
o
c
w
a
u routers
 Procedure of replace boards of NE40E-X series
h
.
g
n of NE40E-X
i
 Procedure of replace fan and power module
n
r
a
series routers
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge52
o
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank :you
//
p
www.huawei.com
t
t
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
h
n
e
/
m
o
c
.
i
e
w
a
u
NE40E-X Router
h
.
g
n
Products Routine arni
e
l
Maintenance p://
t
t
Introduction s: h
e
c
r
u
o
s
n
r
a
g
n
i
Re
e
L
e
r
o
www.huawei.com
Objectives
n
e
/
.
i
e
m
o
c
w
a
u to:
able
.
g
n for the NE40E-X
Perform the routine maintenance operation
i
n
r
a
series products
e
l
/
/troubles of the device and
Discover the defects or possible
:
p
t
remove them on time
ht
:
Guarantee long-term,esstable, and reliable operation of the
c
r
device.
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyrig
o



n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. Overview of Routine Maintenance
n
i
n
2. Routine Maintenance Items
3. Operations Involving Risks
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
n
i
n
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
m
o
c
Objective of Routine Maintenance
.
i
e
w
a
u
 Routine Maintenance is a preventive maintenance
h
.
g
n
measure conducted during the normal operation
of the
i
n
r
a discover the
device. Routine Maintenance helps eto
l
/
defects or possible troubles of :the
/ device and remove
p
t
them, on time. Routine maintenance
guarantees longht
: operation of the device.
term, stable, and reliable
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
n
e
/
n
e
/
m
o
c
Maintenance Rules


.
i
e
w
a
u
Environment of the Equipment Room
h
.
g

Conform to relevant national or industrial standards

Keep the room clean, tidy, dustproof, and moistureproof

Prevent the growth of animalcules such as fungi and mildew

Prevent rodents and insects from entering the room
n
i
n
r
a
le
/
/
:
p
Password management (for the system administrator)
t
t
Keep management-level passwords safely and
h modify them regularly, and assign different
passwords to people with specific operation
: rights to ensure system security
s
e
Key operations
c
roperations such as board switching, system resetting and software
u
Maintain records about all key
o
loading, and analyze thesfeasibility and take backup, emergency and secure measures before such
Re
key operations
g
Data modification
n
i
n
Carry out authorization and control on data modification, back up the data before modification, and
r
a
make
records about modification
Le
Operating Specifications






Anti-static specifications
e
or Wear anti-static wrist strap when operating the device and store the damaged boards in the anti

n
e
/
Classifications of Routine
Maintenance

Daily routine maintenance






.
i
e
h
.
g
w
a
u
Checking the environment of the equipment
in room
n
r
Checking the power supply systemlea
/
/
Checking the alarm system p:
t
t
Checking the operation ofhthe device
:
s
e
c
 Periodic routine maintenance
r
u
so
Checking the ecables
R
g the grounding resistance
Measuring
n
i
n
r
Removing
the dust from the device
a
e
L
r
Copyrig
o

m
o
c
n
e
/
m
o
c
Contents
2.
.
i
e
w
a
u
h
.
g
Routine Maintenance Items
2.1 Maintenance Items and Operations
r
a
2.2 Dustproof Maintenance of the Device
e
l
/
/
:
2.3 Backup and Restoration
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
n
i
n
n
e
/
Introduction to Routine
Maintenance Items (1)
Maintenance period
Maintenance item
u
o
s
e
r
o
.
i
e
h
.
g
w
a
u
n
i
Environment of the
n equipment
r
a
room
e
/l
Alarm and/log
:
Devicetp
temperature and voltage
t
Fanhmodule and power module
:
status
s
e CPU usage and memory usage
c
r
Daily
n
r
a
m
o
c
g
n
i
Re
Le
n
e
/
Maintenance
period
Maintenance item
Monthly
System clock
w
a
u
r
a
le
n
i
n
/
/
:
p
Board running
status
t
t
h neighbor relationship status
OSPF/ISIS/BGP
: information
s
Routing
e
c
r
Administrative
user control
u
o
ng
i
n
r
e
r
o
.
i
e
h
.
g
Traffic on an interface
a
e
L
m
o
c
s
e
R
Telnet login control
Anti-attack detection
FTP password control
Password change
Backup and restoration
n
e
/
.
i
e
w
a
u
Maintenance item
Yearly
Label check
r
a
e
l
Air filter cleaning
/
/
:
p
t
t
h
:
s
e
c
r
n
r
a
g
n
i
Re
Le
h
.
g
n
i
n
Maintenance period
u
o
s
e
r
o
m
o
c
n
e
/
Maintenance Items and Operations
m
o
c
.
i
(1)
e
w
Maintenance Maintenance
item
period
Guidance
Temperature
Observe the
thermometer
and record it
Daily
:
s
e
c
r
Humidity
Daily
n
r
a
e
r
o
Le
g
n
i
Re
u
o
s
Specification
a
u
h
t
t
h
.
g
n
i
•The long-term n
working temperature of the equipment
room should r
range from 0ºC (32ºF) to 45ºC (113ºF)
a
while theeshort-term
one should range from -5ºC (23ºF)
to 55ºCl(131ºF).
/ X1 and X2 models of the NE80E/40E, the long•For
the
/
: working temperature of the equipment room
pterm
should range from -5ºC (23ºF) to 50ºC (122ºF) while the
short-term one should range from -20ºC (-4ºF) to 60ºC
(140ºF).
•If the temperature is not within the normal range for a
long time, overhaul or replace the air conditioning
system.
•The cooling function and the switches of air
conditioners are in good condition.
•The relative humidity for the longterm working
Observe the
hygrometer and environment should range from 5% to 85% while that
of the short-term one should range from 5% to 95%.
record it
•If the relative humidity is too high, install
dehumidifying devices. If the relative humidity of the
equipment room is too low, install humidifying devices.
n
e
/
m
o
c
.
i
(2)
e
w
item
period
Guidance
Alarm
display
trapbuffer
Daily
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
Specification
a
u
h
t
t
h
.
g
n
i
•There is no alarm
normally.
n
•If any alarm r
is displayed, record it. For the alarm
a level is higher than critical, analyze and
whose severity
e
resolvel
it at once.
/
The
bolded information as shown in the following
/
output
p: is severity level:
<HUAWEI> display trapbuffer
Trapping Buffer Configuration and contents:enabled
allowed max buffer size : 1024
actual buffer size : 256
channel number : 3 , channel name : trapbuffer
dropped messages : 0
overwritten messages : 131
current messages : 1 #Nov 16 2009 15:33:06 PE-1
SRM_BASE/1/ENTITYRESUME: OID 1.3.6.1.4.1.2011.5.25
.129.2.1.10 Physical entity is detected resumed
from failure. (EntityPhysicalInd ex=16908289,
BaseTrapSeverity=2, BaseTrapProbableCause=67719,
BaseTrapEventType= 5,
EntPhysicalContainedIn=16908288,
EntPhysicalName="LPU 2", RelativeResource="S FP",
ReasonDescription="LPU 2 is failed, EAGF SFP 0 of
PIC0 is abnormal, Resume")
n
e
/
m
o
c
.
i
(3)
e
w
item
period
Log
Guidance
Specification
a
u
h
Daily
.
g
n should not be displayed in the
i
•Repeated
information
Run the display
n
log.
r
logbuffer
aanalyze and resolve it on time.
•If it occurs,
e
command.
The bolded
information as shown in the following
l
/
output
is repeated information.
/
:
p
t
t
h
:
s
e
c
r
u
o
<HUAWEI> display logbuffer
Logging buffer configuration and contents:enabled
Allowed max buffer size : 1024
Actual buffer size : 512
Channel number : 4 , Channel name : logbuffer
Dropped messages : 0
Overwritten messages : 3
Current messages : 3
n
r
a
e
r
o
Le
g
n
i
R
es
Nov 13 2009 18:12:18 HUAWEI
%%01SRM/3/LPURESET(l):LPU3 reset, the reason is LPU
board LOAMNET init failed and reset lpu. Nov 13
2009 18:10:22 HUAWEI %%01SRM/3/LPURESET(l):LPU3
reset, the reason is LPU board LOAMNET init failed
and reset lpu. Nov 13 2009 18:08:26 HUAWEI
%%01SRM/3/LPURESET(l):LPU3 reset, the reason is LPU
board LOAMNET init failed and reset lpu.
n
e
/
m
o
c
.
i
(4)
e
w
Maintenance Maintenance Guidance
item
period
Configuration
files
Monthly
CF card
Monthly
n
r
a
e
r
o
g
n
i
Specification
a
u
h
.
g
n
i
configurations should be the same
Run the display •The current n
r
as those saved.
currenta
e
•The
configurations
should meet the
configuration
l
requirements.
/
and the display /
:
savedp
t
configuration
t
h
commands
:
s
All the files in the CF card memory should be
Run e
the dir
c
useful; otherwise, delete them using the delete
command
r
/unreserved command.
ou
s
e
R
Le
n
e
/
m
o
c
.
i
(5)
e
w
Maintenance
item
Mainte- Guidance
nance
period
Temperature
Daily
Specification
.
g
n
i
n
a
u
h
r
a
le
Run the display The temperatures of the boards should be in the given range.
Temp(C): indicates the current temperature, In normal situations,
temperature
Temp(C) should be less than Minor.
command to
display the
<HUAWEI> display temperature
:
temperatures of SlotID9
Base-Board, Unit:C, Slot9
Adj_speed Temp
the boards and PCB I2C Addr Chl Status Minor Major Fatal TMin
Tmax (C)
---------------------------------------------------------------record them
/
/
p:
Voltage
:
s
e
c
r
u
o
s
Daily
n
r
a
e
r
o
Le
g
n
i
Run the display
voltage
command to
display the
voltages of the
boards and
record them
Re
t
t
h
SRUA
SRUA
SRUA
SRUA
1
1
1
1
1
2
3
4
0
0
0
0
NORMAL
NORMAL
NORMAL
NORMAL
66
57
55
64
78
69
67
72
90
80
78
80
56
46
44
46
67
57
55
57
40
32
31
33
The voltages of the boards should be in the given range.
Vol: indicates the current voltage. LowAlmThreshold Major: indicates the minor
alarm of low voltage. HighAlmThreshold Major: indicates the minor alarm of high
voltage. In normal situations, Vol should be less than HighAlmThreshold Major
and greater than LowAlmThreshold Major.
n
e
/
m
o
c
.
i
(6)
e
w
Specification
a
u
h
Maintenance
item
Maintenance
period
Guidance
Status of the fan
module
Daily
Run the display •The value of the Present should be Yes.
•The value of the Status field should be AUTO.
fan command
.
g
n
i
n
r
a
le
/
/
p:
If the bolded information as shown in the following output is
displayed, it means that the fan is normal.
:
s
e
c
r
t
t
h
u
o
s
Status of the
power supply
module
e
r
o
ng
Daily
ni
L
r
a
e
RRune the display
power
command
•The value of the Present should be Yes.
•The value of the State field should be Normal.
displayed, it means that the power supply module is normal.
n
e
/
m
o
c
.
i
(7)
e
w
Maintenance
item
Mainte- Guidance
nance
period
System clock
Monthly
Specification
.
g
n
i
n
a
u
h
r
a
le
Run the display •The system date and time are displayed. The time should be
clock command identical with the local time (the deviation is within 5m).
/
/
p:
•If the time is not correct, modify the system time or NTP through
the clock command.
The bolded information as shown in the following output should be
focused.
t
t
h
CPU usage
Daily
n
r
a
e
r
o
Le
g
n
i
:
s
e
c
CPU usage rate should be less than 80%.
Run the display
r •The
u
•If the rate is too high for a long period of time, check the device
cpu-usage
o
and locate the cause.
s
command
e
The bolded information as shown in the following output is the
R
current CPU usage, it should be less than 80%.
n
e
/
m
o
c
.
i
(8)
e
w
Maintenance
item
Mainte- Guidance
nance
period
Memory usage
Daily
Specification
.
g
n
i
n
a
u
h
r
a
le
Run the display •The memory usage rate should be less than 80%.
memory-usage •If the rate is too high for a long period of time, examine the device
and locate the cause.
command
/
/
p:
The bolded information as shown in the following output is the
current memory usage, it should be less than 80%.
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
n
e
/
m
o
c
.
i
(9)
e
w
Maintenance
item
Mainte- Guidance
nance
period
Traffic on an
interface
Monthly
Run the display
interface brief
command
Specification
r
a
le
•Compare the current traffic with the interface bandwidth. If the
usage rate is more than 80%, record and confirm it.
•Check whether incorrect statistics are collected on the inbound and
the outbound interfaces. Focus on the incorrect statistics.
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
.
g
n
i
n
a
u
h
Re
Le
n
e
/
m
o
c
.
i
(10)
e
w
Maintenance
item
Mainte- Guidance
nance
period
Running status of
a board
Monthly
Specification
.
g
n
i
n
a
u
h
r
a
le
Run the display The fields of Online, Register and Status displayed should be
Present, Registered and Normal respectively.
device
command
/
/
p:
displayed, it means that the device is normal.
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
n
e
/
m
o
c
.
i
(11)
e
w
Maintenance
item
Mainte- Guidance
nance
period
Status of OSPF
neighbor
relationship
Monthly
Status of IS-IS
neighbor
relationship
Specification
r
a
le
Run the display The status of neighbor relationship should be 2-Way or Full.
The neighbor relationship is stable and not reestablished repeatedly.
ospf peer
command
/
/
p:
displayed, it means that the status of OSPF neighbor relationship is
normal.
Monthly
ng
:
s
e
c
r
t
t
h
u
o
s
Run the display The status of neighbor relationship should be Up.
isis peer
displayed, it means that the status of IS-IS neighbor relationship is
command
Re
normal.
i
n
r
e
r
o
.
g
n
i
n
a
u
h
a
e
L
n
e
/
m
o
c
.
i
(12)
e
w
Maintenance Mainte- Guidance
item
nance
period
Status of BGP
peer relationship
Monthly
Routing
information
Monthly
n
r
a
e
r
o
Le
g
n
i
Specification
a
u
h
.
g
n
i
n should be Established.
Run the display The status of BGP peer relationship
r
If the bolded information
as shown in the following output is
a
bgp peer
e
displayed, it means that the status of BGP peer relationship is
l
command
normal.
/
/
:
p
t
ht
:
Run the display ips •There should be a default route in the routing table.
routing-table e
•The routing information on a device has little change. For the
c
command. r
devices running the same routing protocol in a network, the routing
u
Compare the
entries on all the devices should be almost the same. Because static
o
routing
information
routing is configured differently, the routing entries may differ.
s
e
currently displayed
R
with that recorded
for the last time to
check whether
obvious changes
exist between
them.
Run the ping or
tracert command
for the routing
n
e
/
m
o
c
.
i
(13)
e
w
Maintenance
item
Mainte- Guidance
nance
period
Administrative
user control
Monthly
Specification
.
g
n
i
n
Run the display currentconfiguration | include
super password level
3command
Monthly
n
r
a
e
r
o
g
n
i
r
a
le
Use the super password command to set the super
password. The super password should be in the encrypted
text mode and its length should not be less than six
characters.
/
/
p:
t
t
h
Telnet logon
control
a
u
h
:
s
e current- •Telnet password cannot be the same as the super
Run the display
c
r include password.
configuration|
u
supero
password level 3 •It must use the encrypted text mode.
s
command
e
R
Le
n
e
/
m
o
c
.
i
(14)
e
w
Maintenance
item
Maintenance
period
FTP password
control
Monthly
Password change Monthly
n
r
a
e
r
o
a
u
h
Guidance
Specification
.
g
n
i
n
r
Run the display current-configurationa •FTP password cannot be the same as the
e super password.
| include include password command
l
/ •It must use the encrypted text mode.
/
:
p
t
t
h
:
s
eusername password •The password should be in cipher text and
Run the user
c
length should be more than six
r in the local-aaa- itscharacters.
cipher command
u
servero
view.
•The password should be changed on a
s
Forethe local user adopting password quarterly basis.
R
authentication,
run the set
g authentication password command.
n
i
Le
n
e
/
m
o
c
Contents
2.
.
i
e
w
a
u
h
.
g
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
n
i
n
n
e
/
Maintaining the Air Filter of the om
c
.
i
NE40E-X3 (1)
e
w
a
u
h
Step1 Remove an air filter from the air intake frame.
•The air filter is located at the rear of the device. Loosen the
captive screws on the panel.
•Hold the panel of the air filter and slowly pull out the air
filter until it leaves the chassis.
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
g
n
i
Re
Step2 Clean air filters.
•Dust off air filters.
•Use a cleaner to draw the dust.
n
r
a
e
r
o
Le
n
e
/
c
.
i
NE40E-X3 (2)
e
w
a
u
Step3 Install a cleaned air filter to the air intake frame.
h
.
g
•Horizontally insert the air filter into the chassis.
n
i air filter.
•Tighten the captive screws on the panel ofnthe
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
n
e
/
c
.
i
NE40E-X8 (1)
e
w
.
g
n
i
n
a
u
h
Step1 Check the location of the air filter to be replaced.
•Before removing the old air filter, check its location, for example,
the cabinet and chassis where the air filter resides. Then, find the air
filter to be replaced in the chassis and attach a label to the panel to
identify the air filter and avoid misoperation.
r
a
le
/
/
p:
t
t
h
Step2 Wear the ESD-preventive wrist strap and connect the grounding
terminal to the ESD jack on the chassis. Or wear the ESD-preventive
gloves.
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
n
e
/
c
.
i
NE40E-X8 (2)
e
w
.
g
n
i
n
a
u
h
Step3 Remove the air filter from the air intake frame.
•Place fingers in the holes on both sides of the panel to press hard
inwards, pull it out of the air intake frame horizontally. In this
manner, the panel is removed
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
Re
Step4 Clean air filters.
•Dust off air filters.
•Use a cleaner to draw the dust.
n
r
a
e
r
o
g
n
i
Le
n
e
/
c
.
i
NE40E-X8 (3)
e
w
.
g
n
i
n
a
u
h
Step5 Install an air filter on the air intake frame.
•Place a clean and dry air filter onto the air intake frame and press
the air filter.
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
n
e
/
c
.
i
NE40E-X16 (1)
e
w
.
g
n
i
n
a
u
h
Step1 Check the location of the air filter to be replaced.
•Before removing the old air filter, check its location, for example,
the cabinet and chassis where the air filter resides. Then, find the air
filter to be replaced in the chassis and attach a label to the panel to
identify the air filter and avoid misoperation.
r
a
le
/
/
p:
t
t
h
Step2 Wear the ESD-preventive wrist strap and connect the grounding
terminal to the ESD jack on the chassis. Or wear the ESD-preventive
gloves.
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
n
e
/
c
.
i
NE40E-X16 (2)
e
w
.
g
n
i
n
a
u
h
Step3 Remove the air filter from the air intake frame.
•Both the upper part and the lower part of the device are installed
with an air intake frame. As shown in the picture, hold the slots in
both sides of the air intake frame, press hard inwards, and pull the
air intake frame horizontally, and the air intake frame is removed.
Then, remove the air filter from the air intake frame.
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
t
t
h
n
e
/
c
.
i
NE40E-X16 (3)
e
w
.
g
n
i
n
a
u
h
Step4 Remove the air filter from the SFU area.
•The air filter is located on the left in the middle of the device. When
removing the air filter, hold the upper handle of the air filter with
one hand and pull the air filter out horizontally.
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
t
t
h
e
R
Step5 Clean air
filters.
g
n air filters.
•Dust off
i
n cleaner to draw the dust.
•Usera
a
e
L
r
Copyrig
o
n
e
/
c
.
i
NE40E-X16 (4)
e
w
.
g
n
i
n
a
u
h
Step6 Install an air filter on the air intake frame.
•Place the clean and dry air filter onto the panel of the air intake
frame.Place fingers in the holes on both sides of the panel to install
the panel back to the original place.
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
t
t
h
n
e
/
c
.
i
NE40E-X16 (5)
e
w
.
g
n
i
n
a
u
h
Step7 Install an air filter in the SFU area.
•Support the bottom of the air filter with one hand and hold the
handle on the air filter with the other hand. Then, insert the clean
and dry air filter in the chassis horizontally.
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
n
e
/
m
o
c
Removing Dust from Fan Modules
.
i
e
w
a
u
 Step1 Remove dust from a spare fan module.
h
.
g
n a spare fan
Remove dust from the fans and the FCB of
i
n
r
a soft brush, or the
module with the clean gauze, antistatic
e
l
/
vacuum cleaner.
/
:
p
t
 Step2 Replace the fan module
ht to be cleaned with the
:
s
spare one.
e
c
r
u
 Step3 Remove dust
o from the replaced fan module.
s
e
R
Remove dust
from the fans and the FCB of the replaced fan
g
n
i
module
n with the clean gauze, antistatic soft brush, or the
r
a cleaner. The fan module cleaned is used as a spare
e
vacuum
L
ehtone.
r
Copyrig
o © 2010 Hua w ei Technologies Co., Lt d. All right s reserved.


n
e
/
m
o
c
Removing Dust from Boards


To clean dust for all boards, you need to prepare a spare board for each board.
h
.
g
Step2 Replace boards.

n
i
n
Replace a board with the spare board first. You cannot remove dust from the board until the spare one is in
r
a
le
position and runs normally.

w
a
u
Step1 Prepare spare boards.

Step3 Remove dust.

.
i
e
/
/
p:
You can carry out dust cleaning in many ways. Two ways for dust cleaning are as follows.
t
t
h

With vacuum cleaner

Brush dust from board surface with a clean and dry antistatic soft brush and align the dust intake of a vacuum
:
s
e
c
r
cleaner with the brush. In this case, dust is absorbed immediately when it is brushed off.

This method features simple operation and low cost. It is hard to remove the dust that is absorbed on board
surface such as harmful gas.
u
o
s

With detergent

Use dedicated anhydrous, erosion-free, non-conductive and highly volatile detergent such as Isopropyl
g
n
i
Re
Alcohol (IPA) to remove dust from boards.

This method helps to remove dust completely, even those harmful gases that are adsorbed on board surface.
n
r
a boards.
Step4 Reuse
e
L
e
r
o
It, however, features complicated operation and high cost.


Due to the amount limit of spare boards, it is not possible to replace all the boards with spare boards
simultaneously.

You can repeatedly use the cleaned board to replace other boards the types of which are the same for secure
Removing Dust from Optical
Interfaces and Connectors
Step1 Pull out an LPU.
n
e
/
m
o
c
w
a
u
.
i
e
h
.
ginterfaces.
Before pulling out an LPU, remove fibers from optical
n
i
n
Performing this step under the guidance of Huawei
r engineers is
a
e be avoided.
recommended so that damages to the LPU lcan
/
/
:connectors with dedicated tools
Step2 Clean the optical interfaces and
p
t
t
and materials.
h
:
The tools and materials cansbe purchased from fiber suppliers.
e
c
rinterfaces and connectors, you must use special
For large-power optical
u
oto clean them.
s
tools and materials
e
R
For small-power
optical interfaces and connectors, you can use clean, dry
g
n
i
antistatic
brushes,
if dedicated tools and materials are unavailable.
n
r
a
Le
r
Copyrig
o







n
e
/
m
o
c
Contents
2.
.
i
e
w
a
u
h
.
g
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
n
i
n
n
e
/
Backing Up the Configuration Fileom
c
.
i
(1)
e
w

Step1 Directly Copying the File
a
u
h
.
g
n
i
interface and copy all command outputs into a .txt
n file. In this manner, the
r
a of the maintenance
configuration file is backed up into the hard e
disk
l
/
terminal.
/
:
pto the CFcard.
Step2 Directly copy the configuration file
t
t
h
You can take the step to copy the current configuration file immediately to
:
s
the CFcard of the router. Run
e the following commands to copy the
c
r CFcard of the router before starting the router:
configuration file to the
u
o
s
<HUAWEI> copy vrpcfg.zip
cfcard:/backup.zip
Re
Copy cfcard:/vrpcfg.zip
to cfcard:/backup.zip?[Y/N]:y
g
n
i
100% complete
n
r
a
Info:Copied
file cfcard:/vrpcfg.zip to cfcard:/backup.zip...Done
Le
r
Copyrig
o



Run the display current-configuration command on the command line
n
e
/
c
.
i
(2)
e
w

Step3 Backing Up the File Through FTP
a
u
h
.
g
n
i
environment. Assign an IP address to the interface
n on the router.
r
a
e
Enable the FTP service.
l
/
/
The router functions as an FTP server.
:
pCreate an FTP user with the username as
t
Enable the functions of the FTP server.
t
h
huawei and password as 123. The user is authorized to access "cfcard:/".
:
s
<HUAWEI> system-view
e
c
r
[HUAWEI] ftp server enable
u
o
s
[HUAWEI] aaa
e
R
[HUAWEI-aaa] g
local-user huawei password simple 123
n local-user huawei service-type ftp
i
[HUAWEI-aaa]
n
r
a ] local-user huawei ftp-directory cfcard:/
[HUAWEI-aaa
e
L
r
Copyrig
o

Connect the router and maintenance terminal to set up a Telnet



n
e
/
c
.
i
(3)
e
w
a
u
h

On the maintenance terminal, initiate an FTP connection to the router.

On the PC, set up an FTP connection with the router through the FTP client. Assume
that the IP address of the router is 10.110.24.254.
r
a
le
.
g
n
i
n
C:\Documents and Setting\Administrator> ftp 10.110.24.254
/
/
p:
Connected to 10.110.24.254.
220 FTP service ready.
t
t
h
331 Password required for huawei.
:
s
Password:
e
c
230 User logged in.
r
u
o
Configure transfer parameters.
s
e
R
ftp> binary
g
200 Type n
set to I.
i
n
ftp>rlcd c:\temp
a directory now C:\temp.
Local
e
L
User (10.110.24.254:(none)): huawei

e
r
o
n
e
/
c
.
i
(4)
e
w
Transfer the configuration file.
a
u
h
.
g
n the
On the PC, run the get command to download
i
n
r
a and save the file as
configuration file to the specified path
e
l
/
backup.zip.
/
:
p
t
ftp> get vrpcfg.zip backup.zip
t
h
200 Port command okay. :
s
e
150 Opening ASCII mode
c data connection for vrpcfg.zip.
r
u
o
226 Transfer complete.
s
e
R received in 0.06Seconds 60.02Kbytes/sec.
ftp: 1021 bytes
g
n
i
ftp>
n
r
a
Le
r
Copyrig
o


n
e
/
Restoring the Configuration Files om
c
.
i
(1)
e
w

a
u
h
Recovering the Configuration Files Saved in the CF Card Memory

router as the configuration files of the current system.

.
g
n
i
n
This action is to restore the configuration files saved in the CF card memory of the
r
a
le
Run the following commands when the router works normally.
/
/
p:
<HUAWEI> copy backup.zip CFcard:/vrpcfg.zip
t
t
h
Copy CFcard:/backup.zip to CFcard:/vrpcfg.zip?[Y/N]:y
:
s
e
Info: Copied file CFcard:/backup.zip
to
c
r
u
CFcard:/vrpcfg.zip...Done
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
100% complete
n
e
/
Restoring the Configuration Files om
c
.
i
(2)
e
w


.
g
n
i
n
This action is to restore the configuration files saved in the PC as the configuration
files of the current system.
r
a
e
l
backing up the configuration files through TFTP.
/ Run the tftp get command to
/
download the configuration files saved in the
: PC to the CF card memory of the router.
p
t in the PC Through FTP
t
Recovering the Configuration Files Saved
h
:
This action is to restore the configuration
files saved in the PC as the configuration
s
e
files of the current system. c
r
u
The router acts as the o
FTP server. The restoration procedure is similar to that for
s
backing up the configuration
files through FTP. Run the ftp put command to upload
Re
the configuration
g files saved in the PC to the CF card memory of the router.
n
i
n
r
a
Le
e
r
o


a
u
h
Recovering the Configuration Files Saved in the PC Through TFTP


The router works as the TFFP client. The restoration procedure is similar to that for
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
n
i
n
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
n
e
/
Hardware Operations Involving om
c
.
i
Risks (1)
e
w
Item
Sub-item
Aftereffects that may be
caused by maloperation
Operation Hot swapping the
s on
master main control
boards
board is prohibited
:
s
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
.
g
n
i
n
a
u
h
r
a
le
•When the standby main control board
runs normally, data backup from the
master board to the standby one
requires a certain period. In this case,
the latest data on the main control
board cannot be backed up entirely to
the standby board. Therefore,
removing the in-service master control
board may result in incorrect statistics
and data loss.
•When the standby main control board
fails to run, removing the in-service
master board may result in interrupt of
partial or even global services.
/
/
p:
t
t
h
Le
n
e
/
c
.
i
Risks (2)
e
w
Item
Sub-item
Operation Pressing the Reset
s on
button on the main
boards
control board is not
allowed, unless
otherwise required.
:
s
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
.
g
n
i
n
a
u
h
r
a
le
•If you press the Reset button on the
panel, the board is forced to reset the
hardware. This operation can be
carried out only by the qualified
personnel in case that fatal faults occur
in the system.
•If the Reset button on the panel is
pressed by mistake, the main control
board will be reset. Its results are the
same as those of removing the inservice master control board.
/
/
p:
t
t
h
Le
n
e
/
c
.
i
Risks (3)
e
w
Item
.
g
n
i
n
Sub-item
a
u
h
r
a
le
Operation Pressing the OFL
If you press the OFL button, the board
s on
button is not
is powered off and the service is
boards
allowed, unless
interrupted.
otherwise required..
Operation Inserting and
s on
removing boards
boards
without wearing
antistatic wrist strap
are prohibited
:
s
e
c
r
u
o
s
Re
Operation Debugging the
s on
Console with the
boards
Console cable is
prohibited
n
r
a
e
r
o
Le
g
n
i
/
/
p:
t
t
h
•Electrostatic on human body does
great harm to electrical parts on the
board.
•If the maintenance personnel insert
and remove boards without wearing
antistatic wrist strap, the board may be
damaged or not run stably.
Only Huawei professional engineers
can use the debugging Console;
otherwise, abnormality of board
running or board resetting may be
caused.
n
e
/
c
.
i
Risks (4)
e
w
Item
.
g
n
i
n
Sub-item
a
u
h
r
a
le
Operation Hot swapping the CF When the CF card is reading or writing
s on the
card is prohibited
data, hot swapping the CF card may
CF card
cause abnormity of the operation
system. That is resetting caused by
infinite loop or loss of heartbreak of
the main control board on which the CF
card is on.
/
/
p:
t
t
h
: •The network cables inside the cabinet
s
e are used for communication between
c
r
Operation Plugging in and
s for cable plugging out the
network cables
inside the cabinet
are not allowed,
unless otherwise
required.
ou
n
r
a
e
r
o
g
n
i
Operation
s for
power
supply
Le
s
e
R
Operating the power
supply in the power
distribution frame of
the cabinet is
prohibited
the host and the terminal.
•Plug-in and plug-out of the cables
inside the cabinet may make the
terminal fail to log on to the router.
•The maintenance personnel can
operate the power supply based on the
guide only in the case of upgrading,
expansion, parts replacement or fatal
faults.
•Operations may cause fatal faults such
n
e
/
Command Executions Involving om
c
.
i
Risks (1)
e
w
Classification
Command Function
Reboot
reboot
Rebooting the
system
Delete
n
r
a
User interface
e
r
o
Le
g
n
i
Aftereffect that may be
r
a
le
/
/
p:
Format
.
g
n
i
n
a
u
h
This command can be used only
in the case of office deployment
or upgrading; otherwise, the
services carried over the device
will be interrupted.
t
t
the Using this command may cause
formatdevice- Formatting
h
name
storage
of all the files on the
: device loss
s
specified storage device and the
e
files cannot be restored.
c
r
Deleting the
This command is used to delete
delete [u
o
/unreserved
s ] { specified files in the specified files in the storage
e
filename
storage
device of the router. If you use
Rcfcard: } | the
device
unreserved when deleting files,
the files cannot be restored.
authenticatio Authenticating When setting user authentication
n-mode
the logon users on the Console and VTY user
interface, if the mode is
password or AAA, you have to
set the password or the user
n
e
/
Command Executions Involving om
c
.
i
Risks (2)
e
w
Classification
Command Function
System maintenance startup
systemsoftware
System maintenance
System maintenance
Setting the
large file for
next startup
Aftereffect that may be
r
a
le
/
/
p:
t
t
h
Upgrading
a
upgrade
:
s
board
e
c
r
u
o
power
s off slot Powering off a
e
board
R
.
g
n
i
n
a
u
h
In the active/standby mode, set
the large files for next startup at
the same time on the active and
standby main control board.
Otherwise, the router will restart
continuously.
Using this command to upgrade
the software or the logical file of
a board will interrupt the
services.
Using this command will power
off a board and interrupt the
services.
g
n
System maintenance
i reset slot Restarting a Using this command will restart
n
board
the specified board.
r
a
e
L
r
Copyrig
o
n
e
/
m
o
c
Summary

Routine maintenance items

Maintenance items and operations
.
i
e
w
a
u
r
a
e
 Dustproof maintenance of the device
l
/
/
:
p
 Backup and restoration
t
t
h
:
 Operations involving risks
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
n
i
n
h
.
g
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank :you
//
p
www.huawei.com
t
t
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
h
n
e
/
m
o
c
.
i
e
w
a
u
NE40E-X Series
h
.
g
n
Products Hardware rni
a
e
l
Introduction
/
/
:
p
t
:
s
e
c
r
ht
u
o
s
n
r
a
g
n
i
Re
e
L
e
r
o
www.huawei.com
Foreword
n
e
/
.
i
e
m
o
c
w
a
u
 NE40E-X3/X8/X16 Series Router are the next generation
high
h
.
g
performance core routers developed by Huawei.
n NE40E-X8/X16
i
n bandwidth,
r
support 400G ready chassis and provides
large
a
e
l types and services.
high processing features and rich interface
/
/
:
p
This course mainly focuses on hardware
architecture, boards
t
t
h
and features comparison.
:
s
e NE40E-X3/X8/X16 hardware and
 This course will introduce
c
r
u
o router products.
compare with other
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge2
o
Objectives
n
e
/
.
i
e
m
o
c
w
a
u to:
able
.
g
n
Understand the hardware structure and features
of NE40Ei
n
r
a
X3/X8/X16 Routers
e
l
/ board
/
Master the functions of each service
:
p
t
t
Describe the features andhhighlights of NE40E-X3/X8/X16
:
s
Routers
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge3
o



n
e
/
m
o
c
Contents
1. Product Overview of NE40E-X3/X8/X16
.
i
e
h
.
g
w
a
u
n
i
2. Hardware Architecture of NE40E-X3/X8/X16
n
r
a
e
3. Board Introduction of NE40E-X8/X16
l
/
/
:
p
4. Features Comparison of NE40E-X3/X8/X16
t
t
h
:
5. Highlights of NE40E-X3/X8/X16
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge4
o
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n
i
n
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge5
o
n
e
/
m
o
c
Evolution of Router
Switched Router based
on NP Chip
Switched Router based
on ASIC Chip
Distributed forwarding
based on CPU
interface
CPU
interface
Modularized interface
CPU
e
r
o
2nd
u
o
s
Re
Interface
ng
i
n
r
a
e
L
Interface
Interface
Interface
Interface
Interface
CPU
1st
CPU
CPU CPU
Interfac
e
centralized forwarding
:
s
e
c
r
Interfac
e
Interfac
e
Centralized forwarding
Fixed interface
ASIC
NP
interface
NP
Switch
Network
ASIC
h
.
g
Switch
Network
n
i
n
r
a
CPU e
l
/
/
:
p
t
t
h
w
a
u
CPU
interface
ASIC
interface
ASIC
interface
.
i
e
NP
interface
NP
interface
In the contemporary era, high
performance and diversified service is
not only the basic requirement of IP
network, but also the duty of the 5th
generation Router.
3rd
4th
5th Generation
Pa ge6
n
e
/
m
o
c
NetEngine Series Router
.
i
e
w
a
u
h
.
g
1600
Mpps
NE40EX8/X16
n
i
n NE80E
Forwarding
Capability
r
a
le
NE5000E
NE40E-8
400
Mpps
200
Mpps
96
Mpps
48
Mpps
:
NE40-8s
e
c
ur
NE20/20E
n
r
a
e
r
o
Le
g
n
i
32G
40G/slot
20G/slot
o
s
e
NE40-4
24
Mpps
/
/
NE80 :
p
t
ht
NE40E-4
R
Switching
Capability
2.5G/slot
64G
128G
1.28T
2.56T and more
Pa ge7
n
e
/
m
o
c
Position of NE40E-X8/X16 routers
.
i
e
w
a
u node of
 NE40E-X8/X16 is usually deployed as the core
h
.
g
nof large-scale
ISP backbone network or the core router
i
n
r
MAN, large enterprise network andeaegress of IDC.
l
/
/ bearer network, multi Support IP Bearer network, IPTV
:
p
t
play IP MAN, IPRAN access
htnetwork applications.
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge8
o
n
e
/
m
o
c
New Hardware of the NE40E （1/3）
.
i
e
w
a
New System of NE40E V6R1
u
h
.
g
n
i
n
 NE40E-X8:
r
a
e
14 U high
l
/
/
:
hardware architecture (chassis/backplane/power
system/heat
p
t G/slot
dispersion system); ready for 400
t
h
:
 NE40E-X16:
s
e
c
32 U high;
r
u
o (chassis/backplane/power system/heat
s
hardware architecture
e
R
dispersion system ); ready for 400 G/slot
g
n
i
n
r
a
Le
r
Copyrig
Pa ge9
o




m
o
c
.
i
e
w
a
New boards of NE40E-X8/X16 V6R1
u
h
.
g
n
Line-card
NE40E/CX600
i
n
r
a
CR5MLPUF402A
e
LPUF40
l
/
CR5MLPUF402B
/
:
p
40 Gbit/s
t
P40-20x100/1000Base-X-SFP
t
platform
h
P40-20x100/1000Base-X-SFP-A with 1588v2
: WAN/LAN-XFP
Subcards
s
P40-2x10GBase
e WAN/LAN-XFP-A with 1588v2
c
P40-2x10GBase
r
u
o
s
20 Gbit/s
e
LPUF21 R LPUF21：2x10GE＋20xGE
platform
g
n
i
10 Gbit/s
n
rSubcards P10-8x100/1000Base-X-SFP-A with 1588v2
platform a
Le
r
Copyrig
Pa ge10
o
n
e
/
n
e
/
m
o
c
.
i
e
w
a
New boards of NE40E-X8/X16 V6R1
u
h
.
g
n
i
n
Line-card
NE40E/CX600
r
a
e
l
/
/ Unit A4 (including 1*2G Memory
CR5D0SRUA4 Switch and Route Processing
:
70
and 1*1G CF Card) p
Main
t
Control
t
h
Board
CR5D0MPUB4 Main Processing Unit B4 (including 1*2G Memory and 1*1G CF
:
Card)
60
s
e
c
r
CR5DSFUI407
u
40Gbps
o Switch Fabric Unit C
C
s
Switching
e
R
Board
CR5DSFUI407
g 40Gbps Switch Fabric Unit B
n
iB
n
r
a
Le
r
Copyrig
Pa ge11
o
n
e
/
m
o
c
Product overview-the system
architecture
Monitorin
g plane
Managemen
t and control
plane
Monitoring
Unit
Data
plane
System
Monitoring
Unit
Management
Unit
:
s
e
c
r
Management
Unit
n
r
a
g
n
i
Forwarding
Unit
LPU
e
r
o
System
Monitoring
Unit
Monitoring
Unit
Forwarding
Unit
Le
LPU
SRU
LPU
Switch Fabric
Control Unit
Monitoring
Unit
/
/
p:
t
t
h
Management
Unit
Management
Unit
Re
u
o
s
h
.
g
The data plane,
management and control
plane are separated

The monitoring plane
and service plane are
separated

Distributed Forwarding

Forwarding
Unit
Switch Fabric
Control Unit
SFU
w
a
u
n
i
n
r
a
le
Monitoring
Unit
.
i
e
Three-level switch fabric

Forwarding
Unit
LPU
Pa ge12
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n
i
n
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge13
o
n
e
/
Basic Specification of NE40E-X3
Router
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
t
t
h
:
s
There are five slots in total, e
including two MPU (two 1+1 backup MPUs)
c
slots and three LPU slots.r
uby each slot is 20 Gbit/s and even 40 Gbit/s after
The capacity supported
o
later expansion. es
The NE40E-X3 is R
compatible with all LPUs of the NE40E and shares the
g with the NE40E.
software platform
n
The MPUnisiintegrated with Stratum-3 clocks and supports the 1588v2
r
features.
a
Power
Le supply modules and fan frames support 1+1 backup.
r
Copyrig
Pa ge14
o





n
e
/
m
o
c
Structure of the NE40E-X3
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge15
Full Mesh Switching Structure
n
e
/
LPU2
.
i
e
w
a
u
LPU1
18 Serdes
m
o
c
h
.
g
n
i
n
r
a
le
/ LPU3
/
p:
t
t
hno switched SFU is required.

With the Fullmesh structure,
:
s
e
c

With an excellent expandability,
the structure supports LPUFr
u
o
10/LPUF-20 link card
s and later mainstream link cards.
e
R
g supports 20G->40G->80G compatibility scheme. At

The structure
n
i
n
present,r the mainstream delivery is 20 Gbit/s line cards.
a
e
L
r
Copyrig
Pa ge16
o
n
e
/
m
o
c
Hardware Description of NE40E-X8
.
i
e
w
a
 Height: 14 U, three chassis in each cabinet
u supports 400 G/Slot
 Backplane capacity: 15 Tbit/s,
h
. Tbit/s
 Switching capacity: 1.44
g
 1:1 backup of SRUs
n
i
 2+1 backup of SFUs
n
①
 1+1 backup r
of fan modules
a by areas (supply power for two areas)
 Power supply
e
 2+2 backup
l architecture: ready for 400G/slot
/
② ②
 Hardware
/
⑥
⑥
:
p
t
⑦ ⑦
ht
③
④
:⑧
s
⑧⑧
⑧
e
c
r
u
⑤
o
⑨ s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge17
o
No.
Quantity
Module
①
Air intake vent
1
②
SRU
2
③
SFU
1 (Total three SFUs, two
of which are integrated
on the SRUs)
④
LPU
8
⑤
Cabling area
1
⑥
Fan module
2
⑦
Low-frequency filtering unit
2
⑧
System power distribution
module
4
⑨
CMU
1
n
e
/
m
o
Hardware Description of NE40E-X16.c
i
e
w
①
a
u
 Height: 32 U
h
 Backplane capacity: 30
Tbit/s, supports 400 G/Slot
.
⑥
g
 Switching capacity: 2.56 Tbit/s
②
n
 1:1 backup of MPUs
i
⑦
④
 3+1 load balancing
among SFUs
n fan modules
r
 2+2 backup
of
a
 Powere
supply by areas (supply power for four areas)
lredundancy
 4+4
⑧
⑧
/
⑤
 Hardware
architecture: ready for 400G/slot
/
:
p
③
t
ht
⑨ ⑧
⑧
⑤
:
s
e
c
r
④
u
o⑦
s
Re
g
①
⑥
n
i
n
r
a
e
L
r
Copyrig
Pa ge18
o
No.
Quantity
Module
①
Air intake vent
2
②
MPU
2
③
SFU
4
④
LPU
16
⑤
Cabling area
2
⑥
Fan module
4
⑦
Low-frequency filtering unit
4
⑧
System power distribution
unit
8
⑨
CMU
1
n
e
/
m
o
c
Backplane of the NE40E-X8/X16
.
i
e
Backplane of the NE40E-X8
Backplane of the NE40E-X16
w
a
u
h
.
g
n
i
Power
supply for the two areas of
n
r
the
backplane of the NE40E-X8, in
a
e2+2 backup mode
l
/ Power supply for the four areas of
/
backplane of the NE40E-X16, in
: the
p
4+4 backup mode
t
The CMU requires an independent
ht
power supply of 5V in 1+1 power
:
supply mode.
s
e
Capacity of the backplane for the
c
r
NE40E-X8: 15 Tbit/s
u
Capacity of the backplane for
o
s
theNE40E-X16: 30 Tbit/s
e
R
g
n
i
n
r
a
Le
r
Copyrig
Pa ge19
o
FAN
P
P
P
FAN
Filter
FAN
Filter
FAN
P
P
P
E
M
P
E
M
200G LPU
200G LPU
200G LPU
200G LPU
200G LPU
200G LPU
200G LPU
200G LPU
P
E
M
P
P
MPU
LPU
M
O
N
P
P
P
P
P
P
P
P
Filter
P
SRU
SFU
SRU
P
P
P
Filter
P
LPU
P
E
M
MPU
LPU
LPU
P
E
M
LPU
P
E
M
P
E
M
LPU
LPU
P
E
M
P
P
P
P
SFU
SFU
SFU
SFU
M P
O E
N M
P
E
M
P
E
M
P
E
M
LPU
LPU
LPU
LPU
LPU
LPU
LPU
LPU
LPU
P
P
P
P
P
P
P
P
P
Filter
Filter
FAN
FAN
n
e
/
m
o
Distributed Architecture Power Supply .-X8
c
i
e
Fan
w Fan
a
PEM
Backplane
u
h
.
g
n
i
n
PEM A0
r
a
e
l
Area 0
/
/
PEM A 1
:
p
t
ht
:
s
e
c
r
u
o
s
Area 1
e
PEM B 0
R
g
n
PEM B 1 ni
r
a
Le
r
Copyrig
Pa ge20
o
Filtering box
Filtering box
-48 V A/RTN A
-48V A/RTN B
LPU7
LPU6
-48V A/RTN A
LPU5
LPU4
SRU1
SFU
SRU0
LPU3
LPU2
LPU1
LPU0
-48 V A/RTN B
n
e
/
m
o
Distributed Architecture Power Supply -X16
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge21
o
Backplane
Fan
Filtering box
PEM A 0
Area 0
PEM A 1
Filtering box
- 48 V A / RTN A
LPU1
LPU1
LPU1
LPU3
MPU1
MPU0
LPU2
LPU1
Area 1
LPU15
- 48 V A / RTN B
LPU0
PEM B 0
Fan
LPU14
PEM
- 48 V A / RTN A
- 48 V A / RTN B
PEM B 1
SFU 2
SFU 3
- 48 V A / RTN A
LPU13
LPU12
LPU11
LPU7
PEM A 3
LPU10
- 48 V A / RTN B
LPU9
Area 2
LPU8
PEM A 2
SFU 0
SFU 1
- 48 V A / RTN A
PEM B 2
PEM B 3
Area 3
- 48 V A / RTN B
Filtering box
Filtering box
Fan
Fan
n
e
/
AC Power Supply System
LPU1
LPU1
e
r
o
Le
LPU1
n
r
a
g
n
i
area2
SFU0
SFU1
SFU2
SFU3
LPU15
LPU14
LPU13
LPU12
LPU10
LPU11
LPU9
area3
LPU7
DCb DCa
4
DCb
4
FAN
LPU3
u
o
s
DCa
3
DCb
3
MPU1
e
c
r
s:
MPU0
AC rectifier module (front view)
LPU2
DCa
DCa
2
DCb
2
area1
LPU1
r
a
le
/
/
p:
t
t
h
g
n
ni
LPU0
DCa
1
DCb
1
Re
h
.Board
AC1AC2
backplan
e
.Area 2
i
e
w
a
u
LPU8
AC rectifier module (rear view)
Area 1
m
o
c
area4
board
FAN
Area 4
Pa ge22
Area 3
n
e
/
m
o
c
Heat Dissipation Unit -X8
Front view
.
i
e
w
a
u
Rear view
Air channel (side view)
Fan
area
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
e
R
 Fan modules at the
back
g
 1+1 backup of n
fan modules
i
 U-shaped air
n channel for effective heat dissipation
r
a
e
L
r
Copyrig
o
Pa ge23
Air
intake
vent
n
e
/
m
o
c
Heat Dissipation Unit -X16
Front
view
Rear
view
Fan
area
n
r
a
e
l
.
i
Air channel (sidee
view)
w
a
u
h
.
g
n
i
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
Re
 Fan modules at the back
 2+2 backup of fans
 U-shaped air channel for effective heat dissipation
 -X16: separate air channels for heat dissipation of the upper and lower
n
r
a
e
r
o
g
n
i
Le
Pa ge24
frames
Air
intake
vent
n
e
/
m
o
c
Heat Dissipation Unit
NE40E-X8
.
i
e
NE40E-X16
h
.
g
n
i
The upper chassis:
draws air from the front
n
U-shape air channel, draws air from
r
top and exhausts air from the rear top;
a chassis: draws air from the front
the front top and exhausts air from
e
The
lower
the rear top
l and exhausts air from the rear
/
bottom
/
bottom;
:
p4
t
2
t
h
When a single fan fails, the
other
When a single fan fails, the other fans
:
s
fans enables the system to work at enables the system to work at normal
e
normal temperature.c
temperature.
r
u
o
supported s
supported
e
R
60W(typical value)
120W(typical value)
g
n
400W(maximum
value)
800W(maximum value)
i
n
U-shape air channel;
Air channel
Fan number
Fan backup
Fan speed
adjustment
Fan power
r NEBS/ETSI
a
e
Noise criteria
e
r
o
L
w
a
u
NEBS/ETSI
Pa ge25
n
e
/
m
o
c
Fan Filtering Unit

.
i
e
w
a
u
Background:

h
.
g
The low-frequency noise (20 Hz to 20 KHz) generated during the running of the fans can be
transmitted through power supply cables, which interferes with the low frequency-sensitive
analog devices sharing power supply with the fans, such as voice switches and the devices
on the access network.
n
i
n

Function:


r
a
le
/
/
p:
The low frequency filtering unit suppresses the low frequency noise through audio filtering
circuits, which prevents the impact of low frequency noise.
Criteria:



e
r
o
:
s
e
c
r
t
t
h
ENSI EN 300 132: is released by the Environment Engineering (EE) division of the ETSI and
provides a series of rules for the features of power input interfaces.
u
o
s
NEBS GR-1089-Core: Section 10.7 of Chapter 10 "Criteria for DC Power Port of
Telecommunications Load Equipment" in the fourth edition of NEBS GR-1089-Core,
published in June 2006, lists the requirements for low frequency interference emission.
These requirements were upgraded to the "R" level requirements, which must be fulfilled, in
June 2007.
n
r
a
g
n
i
Re
ITU-T K.76: lists the requirements of the low frequency emission test in detail, which is
similar to ENSI EN 300 132.
Le
Pa ge26
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n
i
n
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge27
o
n
e
/
m
o
Board function-Main Processing Unit (MPU)
c
.
i
e
w
a
u
MPU/SRU
h
Routing processing board
includes CPU
.
Adapter
g
Route Process
n interface module,
module, the external
Unit
i
netc.
Power
stratum-3
clock,
r
module
a
e
Power
the Routing
l processing board provides
module
/
/
LSW
the following
functions:
:
module
pRoute calculation;
t
CPU
module
ht Outband communication between boards;
:
s
Device management and maintenance;
e
Storage
c
Data configuration;
r
module
u
Clock
o
provide two-channel 2.048-MHz
s
Driver
e
stratum
R
synchronous clock signals for the
-3 clock
g
downstream devices, or receive 2.048-MHz
Switch
n
i
Module
n
or 2.048-Mbit/s external reference clock
r
a
signals.
e
L
r
Copyrig
Pa ge28
o

External Interface




EPLD
Inner-Board connector
FPGA
Backplane connector
Monitori
ng
module


n
e
/
m
o
c
SRU of the NE40E-X8
.
i
e
w
a
u
An SRU consists of the CPU, storage
module, interface module, clock module,
communication module, monitoring module,
and power module.
The SRUs of the NE40E-X8 are integrated
with SFUs.
h
.
g
USB
port
n
i
n
r
a
e of the SRU
l
Highlights
/Two USB ports: supporting version
/
p: downloading through USB devices and
Slot for a
CF card of
up to 1GB
1588 v2 Inside
:
s
e
c
r
RJ-45 connector,
providing clock
information and BITS
clock
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
SMB connector,
providing clock
clock
t
t
h
power supply for USB devices
CF card with mass storage capacity
(up to 1 GB)
Compatible with the design of disks
RJ-45/SMB connector: processing
Stratum-3 clock and 1588 clock;
supporting input and output of
2MHz/2Mbps/1PPS clock signals
High performance multi-core CPU
The bandwidth of the control bus
between the SRU and the LPU is
increased to 1 Gbit/s.
Pa ge29
n
e
/
m
o
c
MPU of the NE40E-X16
w
a
u
An MPU consists of the CPU, storage
module, interface module, clock module,
communication module, monitoring module,
and power module.
Highlights of the MPU
h
.
g
USB port
n
i
n ports: supporting version
Two USB
r
downloading
through USB devices and
a
e
power
supply for USB devices
l
/CF card with mass storage capacity (up
/
1 GB)
p: toCompatible
with the design of disks
Slot for a CF
card of up to
1GB
1588v2 Inside
1G/2.5G SFP connector,
supporting the
architecture of multichassis cascading
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
RJ-45 connector,
providing clock
clock
Re
SMB connector,
providing clock
clock
.
i
e
t
t
h
RJ-45/SMB connector: processing
Stratum-3 clock and 1588 clock;
supporting input and output of
2MHz/2Mbps/1PPS clock signals
High performance multi-core CPU
The bandwidth of the control bus
between the MPU and the LPU is
increased to 1 Gbit/s.
Providing two 1G or 2.5G SFP
interfaces for future expansion into
clusters
The architecture is designed to be
compatible with the SFU function on
future MPUs.
Pa ge30
n
e
/
m
o
c
SFU Boards
.
i
e

w
a
u comprises of
Switching Board
h
. switching
g
CPU module,
n
i
module.
n
r
a responsible for
e
Mainly
l

/
/
p:
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
t
t
h

switching data between LPUs.
-X16 has four SFUs that work
in 3+1 load balancing mode.

X8 support 2+1 load
balancing mode

Le
Indicators on panel include
ACT indicator, RUN indicator
and OFL indicator.
Pa ge31
n
e
/
m
o
c
SFUs of the NE40E-X8
Channels: Each SFU provides 12
pairs of high-speed SerDes links for
each LPU. The rate of each pair of
SerDes links is 3.125 Gbit/s (LPU).
SRU＝MPU＋SFU
.
i
Redundancy: Three SFUsework in load
wone SFU fails,
balancing mode. When
a
u to the other SFUs
the traffic is switched
h
automatically..
g
n
i
n
r
a
LPU
le
Control plane
SRU
SRU
/
/
p:
LPU
s:
Interface
e
c
r
t
t
h
Interface
SFU
u
o
s
g
n
i
Re
Forwarding plane
 Architecture: 2+1 backup of SFUs. Two SFUs are integrated on the SRU.
 Capacity: 480 Gbit/s for each SFU. The capacity of the entire system is 1.44 Tbit/s.
 Features: Large capacity, congestion-free, high reliability, and supporting switching capacity of
n
r
a
Le
40G/slot.
e
r
o
Pa ge32
n
e
/
m
o
c
SFUs of the NE40E-X16
.
i
e
w
a
u
Channels: Each SFU provides 8
pairs of high-speed SerDes links for
each LPU. The rate of each pair of
SerDes links is 3.125 Gbit/s (LPU).
Redundancy: Four SFUs work in
load balancing mode. When one
SFU fails, the traffic is switched
to the other SFUs automatically.
h
.
g
n
i
n
r
a
le
/
/
p:
LPU
Interface
:
s
e
c
r
LPU
t
t
h
Interface
u
o
s
g
n
i
Re
 Architecture: 3+1 backup of SFUs.
n
r
a
 Capacity: 640 Gbit/s for each SFU. The capacity of the entire system is 2.56 Tbit/s.
 Features: Large capacity, congestion-free, high reliability, and supporting switching capacity of 40G/slot
e
r
o
Le
Pa ge33
n
e
/
m
o
CMU of the NE40E New System (optional)
c
.
i
e
 Extensive environment monitoring functions aw
Indicator
Alarm detection of the smoke sensor :Supports u
the connection to the
h
smoke sensor through the panel to detect the alarm
signals from the
.
chassis or equipment room.
g
n
Detection of the ambient temperature :Supports the connection to the
i
temperature sensor through the panel
to detect the temperature of the
n
r
chassis or equipment room.
a
Access control management e
:Detects whether access control is enabled
l
through magnetic inspection and reports the inspection signal to the
RJ-45
/ function is reserved. You can instruct the
device. The remote unlocking
/
connector
: access control through the remote control
CMU to enable or disable
p
function.
t :The CMU provides two-level alarm output signals.
t
Device alarm output
h
Main contact point inspection :The CMU can provide six main contact
: signal input and monitor whether the devices outside
points to detect
s
the chassis
work normally.
e
c
One 232 and 485 serial interface :Provides an RS-232 serial interface,
r is connected to the panel. You can use it to query or locate
which
u
o information about the CMU. In addition, the CMU provides an R-485
s
Panel
port, which is connected to the panel. You can connect an device
connector
Re serial
to this interface. The interface supports full-duplex mode.
g Perform the system environment monitoring and access control
n
functions
i
n
 Not require additional devices, saving customers’ investment.
r
a
e
L
r
Copyrig
Pa ge34
o
n
e
/
Differences Between the Hardware of the NE40E-X8 om
c
.
and NE40E-X16
i
Item
e
w
a
-X8/X16
Remarks
Backplane
Different and cannot be shared
SFU
SRU/MPU
Same and can be shared
Fan
Fan filtering
unit
Power
module
－
－
u
o
s
－
Re
rn
CMU
e
r
o
MPU for NE40E/SRU for NE40E-X8;
/
X16
:
p
t
t
h
LPU
:
s
e
c
r
u
h
Different
. in size
g
n of the SFUs is the
The hardware
i
n connector between the
same.
The
r
a and backplane is different.
SFU
e
l
a
e
L
－
g
n
i Same and can be shared
－
Pa ge35
n
e
/
New Boards and Cards of V6R1m
o
c
.
LPUF40 and PIC
ei
w
a
u
h
.
g
n
i
n
r
a
le
LPUF Mother Card
/
/
p:
NE 40G
platform
P40 half-height
subcard
:
s
e
c
r
t
t
h
2*10GE
NE 20G
platform
u
o
s
g
n
i
P20 full-height subcard
Re
LPUF21：2*10GE＋20*GE
n
P10：8*GE with1588v2
r
P10 half-height a
subcard
Le
r
Copyrig
o
NE 10G platform
20*GE
Pa ge36
n
e
/
m
o
New Boards and Cards of V6R1- LPUF40
c
.
i
e
w
Main function:
a
u
h
Classify, search and forward
. data at a wire
g
speed of 40G; traffic
n management, process
i
link protocol;n
r
a
netstream
e supported by service board SPUC;
l
/ of LPUF40：
/
Highlights
:
p
t Consist of CPU module, switching interface
t
h module, TM module, forwarding module,
:
OAM and netstream module etc;
s
e
c
Support flexible subcard，each LPUF-40 can
r
u
be inserted with 2 subcard;
o
s
e
Support NE80E,NE40E-X8 and NE40E-X16
R
hardware platform, the whole NE80E system
g
n
provides only 8KW，not 5KW.
i
n
r
Support restricted use on NE40E-X3 platform.
a
e
L
r
Copyrig
Pa ge37
o


searchi
ng ,for
wardin
g
module
SI
module

From PIC

TM
module
TO backpland
CPU
module

OAM&
Netstre
am
module
From PIC



n
e
/
New Boards and Cards of V6R1- LPUF40
m
o
c
.
(Cont.)
ei
h
.
g
Item
Specifications
n
i
n
Dimensions (width
x depth x height)
Power consumption
(Typical value)
Heat dissipation
41mm×520mm×400mm
r
a
Aboute280W
l
/
/ BTU/hour
908
:
p
Board weight
type
e
r
o
Le
6.6kg
PowerPC
Frequency
NP
n
r
a
t
t
h
:
s
e
c
bandwidth
r
CPU
Memory
w
a
u
u
o
s
g
n
i
Re
1.3GHz
40Gbit/s
SRAM
288MB
Flash
32MB
SDRAM
1GB
RLDRAM
6.912Gb
EEPROM
64KB
Pa ge38
n
e
/
m
o
New Boards and Cards of V6R1- LPUF40.cPIC
i
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
/
:
p
t
ht10GE optical interface XFP module;
: Support LAN/WAN mode.
s
e
c
r
u
o
s
Re
Optical interface XFP module, providing features of the
g
10GE adaptive;
n
i
Support LAN/WAN mode.
n
r
Support IEEE1588v2.
a
Le
r
Copyrig
Pa ge39
o

GE optical module, providing features of GE optical interfaces.

FE optical module, providing features of FE optical interfaces.


20-port 100/1000Base-X SFP flexible plug-in card

20-port 100/1000Base-X SFP flexible plug-in card A


2-port 10GBase LAN/WAN-XFP flexible plug-in card



2-port 10GBase LAN/WAN-XFP FPIC flexible plug-in card
A
Electrical interface SFP module, providing features of the
10M/100M/1000M adaptive electrical interfaces.
Intermixing of the preceding modules.
2 types of PIC code, have the same appearance, the difference
is that the 20-port 100/1000Base-X-SFP flexible card A
supports IEEE1588v2.
n
e
/
m
oPIC
New Boards and Cards of V6R1- LPUF21/10
c
.
i
e
w
afeatures of GE
GE optical module, providing
u
h
optical interfaces
.
gproviding features of GE
GE optical module,
n
i
optical interfaces
n
r
Electricala
interface SFP module, providing
eof the 10M/100M/1000M adaptive
l
features
/
/
:electrical interfaces
p
t Intermixing of the preceding modules
t
h
:
s
GE optical module, providing features of GE
e
optical interfaces.
c
r
u
FE optical module, providing features of FE
o
s
optical interfaces.
e
R
Electrical interface SFP module, providing features
g
of the 10M/100M/1000M adaptive electrical
n
interfaces.
i
n
r
Intermixing of the preceding modules.
a
Le
r
Copyrig
Pa ge40
o



LPUF21: 2*10GE+20*GE




LPUF10: 8*GE

n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n
i
n
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge41
o
n
e
/
Platform &
performance
Overview of the Previous and New Devicesom
c
.
of V6R1
i
e
w
NE40E/CX600-X3
NE40E/CX600-X8
NE40E/CX600-X16
a
u
h
Available in 2009Q1
Available
in 2009Q3
Available in 2009Q3
.
g
n
i
n
r
a
e
l
/
/
:
p
t
t
400Gh platform
NE40E-4
NE40E/CX600-8
NE80E/CX600-16
:
s
e
c
r
u
o
s
Re
g
n
i
n
20/40G platform
r
a
e
Slot & capacity
L
e
r
o
4 U
Three service slots
100G/Slot
1:1 redundancy of
SRUs
14 U
Eight service slots
400G/Slot
1:1 redundancy of SRUs
2+1 redundancy of SFUs
32 U
16 service slots
400G/Slot
1:1 redundancy of MPUs
3+1 redundancy of SFUs
400G Chassis
Ready
10 U
Four service slots
20G/Slot
SRU
3+1 redundancy of
SFUs
20 U
Eight service slots
20G/Slot
SRUs
SFUs
36 U
16 service slots
40G/Slot
SRUs
SFUs
Pa ge42
n
e
/
Comparison of Key Parameters Between the om
c
.
V6R1 New and Previous Systems
i
NE40E-X16
NE80E
e
w
NE40E-8 a
u
h
.
g
n
i
n
NE40E-X8
NE40E-X3
r
a
le
Parameter
Backplane
442mm*650mm*1420m
m
NE40E-X16
442mm*669mm*1600m
m
NE80E
30Tbps
4Tbps
2.56Tbps
2.56Tbps
1.28Tbps
1.28Tbps
1.44Tbps
640Gbps
1.08Tbps
640Gbps
320Gbps
240Gbps
1600Mpps
800Mpps
400Mpps
300Mpps
40G, 400G in future
40G
40G, 400G in future
20G
40G, 100G in future
22 （16 LPU、 2 MPU、 4
22 （16 LPU、 2 MPU、
11 （8 LPU、2 SRU, 1 SFU） 12（8 LPU、2 SRU, 2
SFU）
4 SFU）
:
s
e
c
r
ou
1600Mpps
capacity
Forwarding
n
r
a
platform
Slots
Le
g
n
i
s
e
R
32U
36U
3 LPU、2 MPU
SFU）
r
Copyrig
o
Height
NE40E-X3
1.35Tbps
capacity
Forwarding
t
t
h
NE40E-8
2Tbps
capacity
Interface
NE40E-X8
442mm*650mm*175m
m
442mm*669mm*975m
m
15Tbps
bandwidth
Switching
/
/
p:
442mm*650mm*620m
m
14U
20U
Pa ge43
4U
n
e
/
m
o
Calculation of the Backplane Capacity .c
i
e
w
a
 NE80E-16: 4 Tbps
u
h
. each of the 16
g
The backplane provides 40 pairs of SerDes links
for
n
i
slots. The bandwidth of a SerDes link is 3.125
n Gbps. Each pair of
r
a
SerDes links provides bidirectional data etransmission.
The 8B/10B
l
/
cost is excluded from the backplane/capacity.
Hence, the
: Gbps x 2 = 4 Tbps.
backplane capacity is: 40 x 16 x 3.125
p
t
t
h
 NE40E-8: 2Tbps
:
s
e slots, and the backplane capacity is 40 x
The device provides eight
c
8 x 3.125 Gbps x 2u=r2 Tbps.
o
s
 NE40E-4: 1 Tbps
Re
gprovides four slots, and the backplane capacity is 40 x
The device
n
i
n
4 x 3.125
x 2 Gbps = 1 Tbps.
r
a
e
L
r
Copyrig
Pa ge44
o



n
e
/
m
o
Calculation of the Backplane Capacity (Cont.)
c
.
i
e
w
a
NE40E-X16: 30 Tbps
u
h
The backplane provides 72 pairs of SerDes links for each of the.
16 service slots and 32
g
pairs of SerDes links for each of the two MPU slot. The raten
of a SerDes link is up to
idata transmission. Hence,
n
12.5 Gbps. Each pair of SerDes links provides bidirectional
r
the backplane capacity is: （72 x 16 x 12.5 G + 32 e
xa
2 x 12.5 G) x 2 = 30.4 Tbps.
l
/
NE40E-X8：15 Tbps
/
:
The backplane provides 72 pairs of SerDesplinks for each of the eight service slots and
t
24 pairs of SerDes links for each of thettwo SRU slots. The rate of a SerDes link is up
h
to 12.5 Gbps. Each pair of SerDes links provides bidirectional data transmission. Hence,
:
the backplane capacity is: (72 xs8 x 12.5 G + 24 x 2 x 12.5 G) x 2 = 15.6 Tbps.
e
c
r
NE40E-X3：1.35 Tbps
u
o 54 pairs of SerDes links for all the three service slots. The rate
The backplane provides
s
e
of a SerDes link isRup to 12.5 Gbps. Each pair of SerDes links provides bidirectional
data transmission.
g Hence, the backplane capacity is: 54 x 12.5 G x 2 = 1.35 Tbps.
n
i
n
r
a
Le
r
Copyrig
Pa ge45
o






n
e
/
m
o
Calculation of the Switching Capacity .c
i
e
w
a
NE80E-16: 2.56Tbps
u
h
.32 pairs of the total
Each of the 16 slots provides 32 pair of SerDes links. At present,
g
n link is 3.125 Gbps. Each
40 pairs of SerDes links are used. The bandwidth of a SerDes
i
n Hence, the switching
pair of SerDes links provides bidirectional data transmission.
r
a
capacity is: 32 x 16 x 3.125 x (8B/10B) x 2 = 2.56 Tbps
e
l
/
NE40E-8: 640Gbps
/
:
Each of the eight slots provides 16 pairs ofpSerDes links. At present, 16 pairs of the
t
t
total 40 pairs of SerDes links are used.
The bandwidth of a SerDes link is 3.125 Gbps.
h
Each pair of SerDes links provides:bidirectional data transmission. Hence, the
s x (8B/10B) x 2 = 640 Gbps
switching capacity is: 16 x 8 xe3.125
c
r
NE40E-4: 320Gbps
u
o
s of the SRUs and SFUs used on the NE40E-4 are the same as
The types and numbers
e
that of the SRUs R
and SFUs used on the NE40E-8. Hence, the capacity of the SFUs on
g be up to 640 Gbps. The NE40E-4 provides only four slots. Hence, the
the NE40E-4 can
n
i is: 16 x 4 x 3.125 x (8B/10B) x 2 = 320 Gbps
witchingncapacity
r
a
Le
r
Copyrig
Pa ge46
o






n
e
/
m
o
Calculation of the Switching Capacity (Cont.)
c
.
i
e
w
a
NE40E-X16: 2.56Tbps
u
h
. 32 pairs of the total
Each of the 16 slots provides 32 pairs of SerDes links. At present,
g
n link is 3.125 Gbps. Each
72 pairs of SerDes links are used. The bandwidth of a SerDes
i
n Hence, the switching
pair of SerDes links provides bidirectional data transmission.
r
a
capacity is: 32 x 16 x 3.125 x (8B/10B) x 2 = 2.56 Tbps
e
l
/
NE40E-X8: 1.44Tbps
/
:
Each of the eight slots provides 36 pairs ofpSerDes links. At present, 36 pairs of the
t
total 72 pairs of SerDes links are used.tThe bandwidth of a SerDes link is 3.125 Gbps.
h
Each pair of SerDes links provides bidirectional data transmission. Hence, the
: x (8B/10B) x 2 = 1.44 Tbps
s
switching capacity is: 36 x 8 x 3.125
e
c
r
NE40E-X3: 1.08Tbps
u
oprovides 36 pairs of SerDes links. The bandwidth of a SerDes
Each of the three slots
s
e
link is up to 12.5 R
Gbps. Each pair of SerDes links provides bidirectional data
transmission. g
The NE40E-X3 adopts the full-mesh connection for the LPUs and
n
backplane;ihence, the switching capacity is: (36 x 3/2) x 12.5 x (8B/10B) x 2 = 1.08
n
Tbps r
a
e
L
r
Copyrig
Pa ge47
o






n
e
/
m
Comparison of Key Hardware Between the V6R1
o
c
New System and Previous System (SRUs)i.
e
w
a
u
h
.
MPU/SRU of the Previous
MPU/SRU of the New System
Improvement in CPUs
Dominant frequency: 1.5 GHz for one core
DDR SDRAM
Improvement
in memory
capacity
r
a
le
4G
Type: Power PC
Dominant frequency : 1 GHz
1 G（ standard configuration,
can be upgraded to 2 G ）
/
/
p:
BOOT ROM
8M
Flash ROM
32M
NVROM
4M
CF card
1G（ standard configuration ）
512M（ standard configuration ）
Supported
Not supported (only supported
1588v2
Increase in the bandwidth of the
control bus
ng
Differences in other key features
ni
ar
Le
g
n
ni
Type: Power PC dual-core
System
R
t
t
h
32M
512K
ou
es
GE
:
s
e
c
r
1M
on special boards)
FE

USB port supported

Hard disk compatible

Providing 1G/2.5G Ethernet SFP interfaces to support
None
the future design of a multi-chassis system
r
Copyrig
o

Architecture supporting the integration of SFUs and
SRUs
Pa ge48
n
e
/
Comparison of Key Hardware Between the om
c
V6R1 New and Previous Systems (SFUs) i.
Item
Improvement
in SFU
capacity
SFU of the New System
-X16/-16
640G/SFU
-X8/-8
480G/SFU
-X16/-16
Improvement
in switching
-X8/-8
chips
Redundancy
i
-X8/-8
n
r
mode of the
a
e
L
SFUs
e
r
o
ng
-X16/-16
e
w
a
u
h
.
SFU of the Previous System
g
n
640G/SFU
i
n
r
160G/SFU
a
le
/
/
:G.
with the capacity of 640
p
t
t
h
:
SFU has onesswitching chip with
e
c
the capacity
r of 480 G.
u
o
s
Re
An SFU has one switching chip
An SFU has four switching chips,
each of which has the capacity
of 160 G.
An SFU has one switching chips
which the capacity of 160 G.
3＋1 redundancy
3＋1 redundancy
2＋1 redundancy
3＋1 redundancy
Pa ge49
n
e
/
Next Generation 400 G Platform—small
m
o
c
.
but powerful
ei
Huawei
Cisco
w
a
Cisco
u
h
.
Huawei
g
n
ni
r
a
le
11 chassis in one cabinet
Four chassis in one cabinet
1320
10U
640
4U
60%
Height
Chassis
n
r
a
e
r
o
Le
NE40E-X3
ASR9006
e
c
r
132
u
so 64
s:
e 50%
50%
R
10GE
GE
g
Interface capacity
in
t
t
h
/
/
p:
Three chassis in a cabinet
Two chassis in a cabinet
NE40E-X8
21U
ASR9010
960
14U
640
96
33%
Height
33%
33%
GE
10GE
Interface capacity
Chassis
• Compact design, saving investment by 40%
64
Pa ge50
n
e
/
m
o
c
Next Generation 400 G Platform
48U
Two
chassis
in one
cabinet
32U
Three
chassis
in one
cabinet
n
i
n
r
a
le
Item
NE40E-X8
:
s
e
c
r
Backplane capacity
400G/Slot
Compatibility
Supporting all previous LPUs,
ou
4U
ASR9006 NE40E-X3
NE40E-X8
7750-12
ASR9010
100G/Slot
400G/Slot（non-carrier class）
——
The LPUs of the 7600 series are
can be expanded to 400 G/slot
Power supply capability per slot
and
energy
saving
e
r
o
ng
ni
Installation Cabinet
r
a
e
depth
R
14 U (three chassis in a cabinet)
Height
Green
es
550 W/Slot
COP of the heat
in one
cabinet
10U
/
/
p:
t
t
h
ASR9010
NE40E-X16
w Eleven
a
u chassis
h
.
g
21U
14U
CRS-1
Four
chassis
in one
cabinet
.
i
e
not supported.
530 W/Slot
700 W/Slot
14 U (three chassis in a
21 U (two chassis in a cabinet)
cabinet)
800
800
1000
30
14
12
Comply with the ETSI standard
Comply with the ETSI
L
dispersion system
Noise
Copyrig ht © 2010 Hua w ei Technologies
Co., Lt d. All right s reserved.
(72dBA)
standard (72dBA)
Comply with the NEBS
Pa ge51 standard (78dBA)
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n
i
n
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge52
o
n
e
/
m
o
c
Highlights of the V6 New System
Compact design: saves space by 40％
 High interface density: supports bandwidth growth
 Greenest platform: lowest power consumption and
highest heat dispersion efficiency
 Uniform software platform
 Uniform NMS
 Reducing OpEx and CapEx
Ready for 400G/slot.
Smooth upgrade does
not need replacement
of basic components:
 Chassis
 Backplane
 Power system
 Heat dispersion
system

Low frequency filtering board
 Suppress the low frequency
interference of the fan
 Suppress the low frequency
interference in case of high power and
current
 Comply with ENSI EN 300 132 and
NEBS GR-1089-Core
 System environment
monitoring and access
management
 Does not need additional
devices, which saves
investment.
P
P
风扇
风扇
滤波盒
滤波盒
P
P
P
200G LPU
200G LPU
P
P
P
P
P
E
M
P
P
SRU
SFU
P
E
M
SRU
200G LPU
200G LPU
200G LPU
P
E
M
200G LPU
200G LPU
监
控
200G LPU
风扇
滤波盒
P
P
P
P
P
E
M
P
MPU
LPU
LPU
P
E
M
P
P
P
P
MPU
LPU
LPU
P
E
M
LPU
P
E
M
LPU
LPU
P
E
M
SFU
SFU
SFU
监 P
控 E
M
LPU
P
P
E
M
P
E
M
P
E
M
LPU
LPU
LPU
LPU
LPU
LPU
P
P
P
P
P
P
滤波盒
风扇
e
r
o
n
r
a
P
P
P
P
SFU
LPU
LPU
P
P
Le
滤波盒
风扇
g
n
i
/
/
p:
t
t
h
Safety
regulation
Environment
monitoring
Re
u
o
s
Power supply by areas
 The power system in the equipment
room needs no modification.
 2＋2 / 4＋4 power redundancy
 Ensures the reliability of power
supply.
 Power supply system Ready for
400G/slot

风扇
滤波盒
:
s
e
c
r
r
a
le
h
.
g
Power
supply and
heat
dispersion
Two USB interfaces
Large capacity CF card
 Compatible with hard disk
 Stratum-3 clock and 1588
clock
 High performance multi-core
CPU
 Bandwidth of the control bus
increased to 1G
 Supporting the future design
of a multi-chassis system
 Support integration of SRU
and SFU

Forward
and
backward
compatible
SRU
function
improved
w
a
u
Can be expanded to 400 Gbit/s.
 Is compatible with previous boards.
 Protects the customer’s investment.
 Expandable: high performance and
large capacity

n
i
n
Smooth
expansion
to 400
Gbit/s
Green,
energy
saving,
reduce TCO
.
i
e

Rear fan frame
1+1 or 2+2 fan redundancy
F
 U-shaped air channel
 Smooth and complete heat
A
dispersion
N
 Quiet fan design
Temperature sense and
intelligent speed adjustment
 Power supply system Ready
for 400G/slot


Pa ge53
Fan
area
Air
inta
ke
Air
intake
n
e
/
m
o
c
Ready for 400 G/slot
.
i
e
w
a
u
h
.
g
Chassis
Ready for 400G/slot
Backplane
Ready for 400G/slot
Power supply system
Ready for 400G/slot
:
s
e
c
r
n
i
n
r
a
le
/
/
p:
upgrade
Smoothly to
400G/slot.
tBasic components
t
h unmodified
u
o
Heat dispersion system
s (fan)
e
Ready for 400G/slot
R
g
n
i
n
r
a
Le
r
Copyrig
o
Pa ge54
n
e
/
Forward and Backward Compatible with
m
o
c
.
All the Previous Boards
ei
w
a
u
。。。
h
.
g
Forward compatible to all the previous boards
Smooth upgrade to 400 G/slot
2010
Meeting future demands and being
expandable
Protecting your investment
2009
:
s
e
c
r
40G LPU
2007
10G LPU
ar
ni
e
r
o
Le
ng
/
/
100G
:LPU
p
t
t
h
u
o
s
20G LPU
2004
n
i
n
400G
LPU
r
a
e
l
Re
10G/20G
Platform
Past
40G
Platform
Now
Futur
e
400G Platform
Pa ge55
n
e
/
m
o
c
Green 400G Platform
.
i
e
w
a
u
Greenest platform
NE40E-X16
h
.
g
Greenest platform: lowest power consumption, highest
efficiency in heat dispersion
n
i
n
Power supply by areas, power supply mode can be
unmodified.
Lowest power consumption: Power consumption of a
10G interface is 30% lower than that of the other supplier.
A device saves power of 10000 kwh each year.
r
a
le
/
/
p:
NE40E-X8
:
s
e
c
r
NE40E-X3
ou
g
n
i
s
e
R
Green platform，unified NMS，unified platform
From 10G to 400G，compatible to all boards
rn
Highest
efficiency in heat dispersion: innovative U-shaped
t
t
h air channel, greatly improves the heat dispersion system.
Compact design, save space by 40％
High performance and great capacity
Most compact design: 14 U/32 U. Three chassis in a cabinet
High interface density: up to 132*10GE
Save OPEX and CAPEX，saves TCO by 40％
e
r
o
a
e
L
400G platform, backplane capacity up to 30 T
Pa ge56
Questions
n
e
/
.
i
e
m
o
c
w
a
u
 Please describe the network position of NE40E-X8/X16
h
.
g
routers.
n
i
n
r
a control planes of
 What is the difference between the
e
l
/
NE40E-X8 and NE40E-X16?
/
:
p
t
 What is the difference between
ht the SFUs of NE40E-X8
:
and NE40E-X16?
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge57
o
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank :you
//
p
www.huawei.com
t
t
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
h
n
e
/
m
o
c
.
i
e
w
a
u
n
i
n
System Architecture
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
e
VRP
e
r
o
h
.
g
L
www.huawei.com
Foreword
n
e
/
.
i
e
m
o
c
w
a
usupport
 VRP is a network operation system which can
h
.
g
n
multiple kinds of network facilities and iwhich
is
n
r
a and application
developed after many years of research
e
l
/
practice in the network domain:/by Huawei Technologies.
p
t
 It provides powerful IP forwarding
engine, flexible
ht
:equipment management
s
network operation and
e
c
r
u
capability.
o
s
e
R
 VRP provides high reliability.
g
n
i
n
r
a
Le
e
Pa g e2
Copyrig ht r
© 2012 Hua w ei Technolog ies Co., Lt d. All right s reserved.
o
Objectives
n
e
/
.
i
e
w
a
u to:
able
.
g
n
Describe the VRP architecture.
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
e
Pa g e3
Copyrig ht r
o

m
o
c
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. VRP Overview
n
i
n
1.1 VRP Background
r
a
le
1.2 VRP Architecture
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Copyrig ht © 2012 Hua w ei Technolog ies Co., Lt d. All right s reserved.
Pa g e4
n
e
/
m
o
c
VRP Background
.
i
e
w
a
u

h
.
g
VRP: Versatile Routing Platform
n
i
n
r
a
le

network operation system

platform to support lots of products
//
:
p
t
Provide TCP/IP routing service
t
h
:
 VRP 5.x
s
e
VRP 3.x c
NE series router
r
u
AR series
router, NE
o
s
VRP
1.x

e router and all
series
R
forepart version
series switch
g
n
i
n
r
a
e
L
e
Copyrig ht r
o

…
Pa g e 5
n
e
/
m
o
VRP Background –Three Layersi.c
e
w
a
u
h
VRP .
core
gconcrete product
Independent to
n
i/ TCP IP stack /
Routing
n
r / MPLS VPN
a
MPLS
e
l
/
/
:
p
t
VRP shell
t
VRP Core
h Independent product partially
:
IFNET / Link layer……
s
e
c
r
u
o
VRP Shells
Product code
e
R
Specific to concrete product
g Code
Product
Driver / Device management /
n
i
forwarding….
n
r
a
e
L
e
Pa g e6
Copyrig ht r
o
VRP
VRP Core
Core
m
o
c
VRP Background—Framework i.
e
w
a
n
e
/
u
VRP is designed with modularization software hframework
.
g
n
i
n
BGP for IPv4
BGP
Module
Ha
r
a
le Modular upgrade
t
t
h
Func
Ha
Shell
:
s
e
c
r Func
BGP Core
Cfg
Interface
Func
g
n
i
u
o
s
Re
BGP for IPv4 VPN
n
r
a
e
r
o
Le
/
/
p:
Cfg
without interrupting
other modules
Easy system
maintenance
Cfg
Ha
Upgrade service
smoothly
BGP for
IPv6
Pa g e7
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. VRP Overview
n
i
n
1.1 VRP Background
r
a
le
1.2 VRP Architecture
:
s
e
c
r
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa g e8
n
e
/
m
o
c
VRP Architecture
.
i
e
w
a
u
General Control Plane(GCP)
Service Control Plane(SCP)
Routing Subsystem
Proto Client
AAA
TE_Ex
URP
4/6
LocalM
Vpn Subsystem
MRP
4/6
VPN_Ex
L2TPv3
r
a
le
MPLS-IFM
IP Stack Subsystem
M
I
P
v
4
Data Forwarding Plane(DFP)
LSPM4/6
CR-LDP
Socket Layer
TCP4/6
UDP4/6
ICMP4/6
MIPv6
IP4/6
FE API
FEC
s:
Net Interface Subsys
e
c
r
IFNET
FE DRV
PPP
FE
ETH
u
o
s
ATM
COMM
ng
INSPECT
ni
PROCESS
ar
Le
THREAD
RSVP-TE
t
t
h
Info Management Subsys
IM
TEDBM
BW-M
QosM
Multi-Chassis
HeartBeat
BoardM
CFG-RS
SwitchOver
SAA
RSVP
Hot Plug
Alarm Proc
System Service Plane(SSP)
RPC
RMDB
MOM
HA/FT
LBM
PATCH
MEM
TIMER
IPC
UTILITY
FS
LOAD
OSAL
Operating System
Stat
Device Management Subsys
QoS Subsystem
TUNN4/6
Trace
a
Multi Language
Security Subsystem
PBR4/6
IPSec4/6
FW
ACL4/6
CA
DevSec
NAT4/6
Link Manager
Re
CMO
LSP-AGENT
TunnelM
FR
WebUI CLI SNMP MML BINA
CSPF
/
/
p:
IP Application4/6
Config Management Subsys
.h
g
n
ni
IPsec
VPN
6PE
Mpls Subsystem
CM
e
r
o
VPDN
L3vpnM4/6
L2vpnM
MRM4/6
RM4/6
System Manage Plane(SMP)
Pa g e9
n
e
/
m
o
c
VRP Architecture –GCP

GCP：General Control Plane

General Control Plane (GCP)
Routing Subsystem
VPN Subsystem
IP Stack Subsystem
e
r
o
s:
e
c
MPLS Subsystemr
u
o
s
Security Subsystem
e
R
Net Interface
g Subsystem
n
i
n
QoS
Subsystem
r
a
e
L
.
i
e
w
a
u
h
.
g
It supports network
protocols,
n
i
n
especiallyr the TCP/IP protocol
a
e
family,
l including IPv4 and
/
/
:
pIPv6 ,IPX in the future.
t
t
h It supports SOCKET, route

management, various kinds
of routing protocols, VPN,
interface management, link
layer, MPLS, security and QoS.
Pa g e10
n
e
/
m
o
c
VRP Architecture –SCP

.
i
e
w
a
u
h
.
g
SCP：Service Control Plane
Service Control Plane (SCP)
:
s
e
c
r
Local M
ng
Re
i
n
r
e
r
o
a
e
l
t
t
h
u
o
s
CM
Basedr on GCP.
Supporting
/
/
p: service:

Proto Client
AAA

n
i
n
a
e
L
value-added

Connection management

User authentication
accounting

User policy management

……
Pa g e11
n
e
/
m
o
c
VRP Architecture –DFP

w
a
u
h
.
g
DFP：Data Forward Plane

Data Forwarding Plane (DFP)

FE API
:
s
e
c
r
FEC
FE DRV
FE
ng
i
n
r
e
r
o
a
e
L
Re
u
o
s
.
i
e
n of the forwarding
It is made i
up
n
r
aand FIB maintenance.
engine
e
l
/
/ functions: forwarding
Main
:
p
t data, QoS, policy
t
h
implementation and
forwarding table maintenance.

Control plane and forwarding
plane interfaces are defined in
VRP, control and forwarding
are separated.
Pa g e12
n
e
/
m
o
c
VRP Architecture –SMP

.
i
e
w
a
u
h
.
g
SMP：System Management Plane
System Manage Plane (SMP)
Config Management Subsys
n
i
n
It providesr system configuration
a
e
l
management
function and
/
/
:
management
interface, manage
p
t
ht the system output information.

:
s
e
It flexibly imports some network
c
r
Device Management Subsystem
u
management mechanisms, such as:
o
s
Re
command line, NMP and Web.
g
n
i
n
r
a
Le
e
Pa g e13
Copyrig ht r
o
Info Management Subsystem

n
e
/
m
o
c
VRP Architecture –SSP

.
i
e
w
a
u
h
.
g
SSP：System Service Plane (SSP)


e
r
o
n
i memory
It supports order system services, such n
as:
r
a
management, timer, IPC, loading and
e so on.
l
/
/
It provides operation system abstract
layer to make the VRP
:
p
t
t
independent to certain operation
system.
h
:Service Plane (SSP)
System
s
e
c
r
u
o
s
Re
OSAL
g
n
i
Operating System
n
r
a
e
L
COMM
INSPECT
RPC
RMDB
MOM
PROCESS
THREAD
MEM
TIMER
IPC
HA/FT
LBM
PATCH
UTILITY
FS
LOAD
Pa g e14
n
e
/
m
o
c
License Mechanism

Reason
w
a
u
.
i
e
VRPv5 will operate on different
.h products.
g
n
i and services.
they provide different functional attributes
n
r
a
ecan control certain
l
 Function
License mechanism
/
/
:
p
characteristic available or unavailable
and restrict the
t
t
h
maximum number of routes
and LSPs the product
:
s
e
supports
.
c
Advantage
r
u
o
s

Clients
only need to pay for the functions
e
R
g
n
and performance
attributes they have bought.
i
n
r
a
e
L
e
Pa g e15
Copyrig ht r
o
n
e
/
m
o
c
Summary
.
i
e
w
a
u

The background of VRP

Basic architecture and functions
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa g e16
n
e
/
m
o
c
Questions

.
i
e
w
a
u
Please describe the functions (roles) of VRP. h
.
g
n
i
n
r
a
e and their functions.
 Please describe the five planes of VRP
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
e
Pa g e17
Copyrig ht r
o
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank :you
//
p
www.huawei.com
t
t
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
h
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
VRP Basic Configuration
rn
a
e
l
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
g
n
i
Re
e
L
e
r
o
www.huawei.com
n
e
/
Foreword
.
i
e
m
o
c
w
a
uoperating
 Versatile Routing Platform (VRP) is the network
h
.
g
n
system used by all Huawei data communication
products.
i
n
r
a other products all
Huawei routers, switches, firewalls, and
e
l
/
use the VRP platform. Therefore,
/learning the basic
:
p
t
configuration of the VRP is the
ht operating basis of Huawei
:
equipment.
s
e
c
r the basic configurations of VRP.
u
 This course describes
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 2
o
n
e
/
Objectives
.
i
e
w
a
uto:
 Upon completion of this course, you will be able
h
.
g
n
Use basic operation commands
i
n
r
a center
Describe the function of VRP information
e
l
/
/
:
Perform VRP operate files
p
t
ht
Operate VRP upgrade software
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 3
o




m
o
c
n
e
/
m
o
c
Contents
.
i
e


Information Center

File Operation

Software Upgrade
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 4
VRP Overview
n
e
/
.
i
e
m
o
c
w
a
As the core engine for Huawei routers, Ethernet switches, uand service
h
.
g
gateways, VRP provides the following functions:
n
i
n
Provides unified CLI and management views,
r including unified
a
e
operating system kernel, software IP forwarding
engine, route
l
/
/
:
processing, and configuration management.
p
t
t
Provides the control plane andhdefines interface standards to
: products' forwarding planes and VRP's
s
implement interaction between
e
c
r
control plane.
u
o
s
Provides network
Re interface layer to shield link layer differences of
products. ng
i
n
r
a
Le
r
Copyrig
Pa ge 5
o




n
e
/
m
o
c
VRP Development

.
i
e
w
a
u
We commonly use the VRP 5.9 software now.h
.
g
n
i
n
Feature
r
a
le
OAM, reliability
/
/
p:
Switching
IPv6 multicast
Metro access
:
s
e
c
r
Multi-chassis
cascade
u
o
s
VRP3.X
Distributed
Centralized
e
r
o
t
t
h
VRP5.1 VRP5.3 VRP5.5 VRP5.6 VRP5.7 VRP5.9
n
r
a
g
n
i
Re
VRP1.X
Le
Time
Pa ge 6
n
e
/
Logging In to the Router Through theom
c
.
Console Port
ei
w
a
uconfigure it
 If you are the first time logging in to the device,
h
.
g
n
using the console port.
i
n
r
a
e
l
/
/
AR2220
:
p
t
ht
:
s
e
c
r
u
o
s
Console cable
e
R
g
n
i
n
r PC
Windows
a
Le
r
Copyrig
Pa ge 7
o
n
e
/
Configuring the Terminal Running onom
c
.
Windows XP
ei
w
a
Start > Program > Accessories > Communication > HyperTerminal
u
h
.
g
Other terminals such as SecureCRT can also be used. The parameter
settings are
n
the same as the parameter settings of HyperTerminal. ni
r
a
e
l
/
/
:
p
t
t
h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 8
o


Command-Line Interface
n
e
/
.
i
e
m
o
c
w
a
u
 After you log in to the router, the displayed command
line
h
.
g
nCLI.
prompt indicates that you have entered the
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 9
o
Command Level
n
e
/
.
i
e
m
o
c
w
a
u of 16 levels.
 The router's commands are classified into a maximum
h
.
g
n levels:
 By default, the commands are classified into four
i
n
r
a
0: Visit level
e
l
/
/
1: Monitoring level
:
p
t
ht
2: Configuration level
:
s
3: Management levelce
r
u
o
 If refined right management
is required, command levels can be
s
e
R
extended to 0gto 15.
n
i
n
r
a
e
L
r
Copyrig
Pa ge 10
o




Command Views
n
e
/
.
i
e
m
o
c
w
a
u views. All
 CLI interfaces are classified into several command line
h
.
g
commands must be executed in command line nviews.
i
n
r its command view.
 You can run a command only after you enter
a
e
l
/
/
:
p
# Connect to the switch. If the switch
t uses default settings, you
t
h
enter the user view.
:
<Huawei>
s
e Enter to enter the system view.
# Enter system-view andcpress
r
<Huawei> system-view
u
o
s
[Huawei]
e
R
# Enter an interface view.
g GigabitEthernet X/Y/Z
[Huawei] interface
n
i
[Huawei-GigabitEthernetX/Y/Z]
n
r
a
Le
r
Copyrig
Pa ge 11
o
Command Line Help: Full Help
n
e
/
.
i
e
m
o
c
w
a
u help
 When inputting a command, you can use the full
h
.
g
function to obtain keywords or parametersinfor the command.
n mark (?) to display
# Enter a character string followed directly by a question
r
all commands that begin with this character string.ea
l
<Huawei>?
/
/separated by a space. All
# Enter a command and a question mark (?)
:
pas well as simple descriptions, are
keywords associated with this command,
t
displayed.
ht
<Huawei>language-mode ?
:
s
Chinese Chinese environment
e
c
English English environment
r
# Enter a command andou
a question mark (?) separated by a space.
sthis command, as well as parameter descriptions, are
Parameter names for
e
R
displayed.
g ?
[Huawei]ftp timeout
n
i
INTEGER<1-35791>
The value of FTP timeout (in minutes)
n
r
[Huawei]ftp
timeout 35 ?
a
<cr>Le
r
Copyrig
Pa ge 12
o
m
o
c
Command Line Help: Partial Help .
i

e
w
a
u
h
.
n
e
/
If you enter only the first or first several characters of a command, partial
g
n
i
n
# Enter a character string followed directly by a question
mark (?) to display all
r
commands that begin with this character string. ea
l
<Huawei>d?
/
/
debugging
delete
:
p
dir
display
t
t followed directly by a question
# Enter a command and a characterhstring
mark (?) to display all key words :
that begin with this character string.
s
<Huawei>display b?
e
c
bfd
bgp
r bulk-stat
u
bootrom
o
s
Enter the first several
Re letters of a key word in the command and then
g a complete key word. A complete keyword is
press Tab to ndisplay
i if the partial string of letters uniquely identifies a specific
displayed n
only
r If they do not identify a specific key work, continuing to press
key word.
a
e display different key words. You can select the needed key word.
Tab Lwill
r
Copyrig
Pa ge 13
o
help provides keywords that begin with this character or character string.

n
e
/
m
o
Command Line Help: Error Messages
c
.
i
e
w
a
If a command is entered and passes the syntax check, the system executes
it. Otherwise, the
u
h
system reports an error message.
.
g
n
Common error messages of the command line
i
n
r
a
Error Messages
Causee of the Error
l
/
Unrecognized command
The command/cannot be found
: cannot be found
The key word
p
t type error
t
Wrong parameter
Parameter
h
Parameter value out of range
:
s
Incomplete command
eIncomplete command entered
c
r Too many parameters entered
Too many parameters
u
o Ambiguous parameters entered
Ambiguous command s
Re
gxyz
<Huawei>display
n
i ^
n
r
Error: Unrecognized
command found at '^' position.
a
Le
r
Copyrig
Pa ge 14
o


n
e
/
m
o
c
CLI Features

.
i
e
w
a
u
Editing

h
.
g
The command line editing function allows you to edit command lines
or obtain help by using certain keys.
n
i
n
r
a
Command lines have a feature to controlle
how they are displayed. You
/ as required.
can set the command line display mode
/
:
p
Regular Expressions
t
t
h a set of strings. You can use regular
A regular expression describes
expressions to filter outputs:
to locate needed information quickly.
e
c
Previously-Used Commands
r
u
o
If you need to runs a command that has been previously executed, you
can use this function
Re to call up the command.
g Execution
Batch Command
n
i
n
Executing
the pre-defined commands in a batch can simplify
r
a
configuration
and improve configuration efficiency.
e
L
r
Copyrig
Pa ge 15
o

Displaying







n
e
/
m
o
c
Common Commands (1)

.
i
e
w
a
u
h
.
g
Change the device name.
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname RTA
[RTA]
n
i
n
r
a
le
/
/
:
p
 Display the current configuration.
t
t
[RTA]display current-configuration h
:
#
s
e
sysname RTA
c
r
#
u
o
……
s
e
#
R
return
g
n
[RTA]
i
n
r
a
Le
r
Copyrig
o
Pa ge 16
n
e
/
m
o
c
Common Commands (2)

.
i
e
w
a
u
h
.
g
Display device version.
n
i
n
<RTA> display version
Huawei Versatile Routing Platform Software
VRP (R) software, Version 5.90 (AR2200 V200R001C00)
Copyright (C) 2011 HUAWEI TECH CO., LTD
Huawei AR2220 Router uptime is 0 week, 4 days, 3 hours, 25 minutes
BKP 0 version information:
1. PCB
Version : AR01BAK2A VER.A
2. If Supporting PoE : No
3. Board Type : AR2220
4. MPU Slot Quantity : 1
5. LPU Slot Quantity : 6
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
……
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 17
n
e
/
m
o
c
Common Commands (3)

.
i
e
w
a
u
Display component type and operating status. h
.
g
n
i
n
r
a
le
<RTA> display device
AR2220's Device status:
Slot Sub Type Online Power
Register
Alarm
Primary
----------------------------------1 - 1E1-F Present PowerOn Registered Normal NA
2 - ADSL-B Present PowerOn Registered Normal NA
3 - 1E1-MFT Present PowerOn Registered Normal NA
4 - 2FE
Present PowerOn Registered Normal NA
6 - 8AS
Present PowerOn Registered Normal NA
0 - AR2220 Present PowerOn Registered Normal Master
PWR1 - Present PowerOn Registered Normal NA
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 18
n
e
/
m
o
c
Common Commands (4)

.
i
e
w
a
u
h
.
g
Change system time.
<RTA>clock datetime 15:48:00 2011-09-27
<RTA>
n
i
n
r
a
euser levels.
 Configure the password for switching
l
/
/
<RTA>system-view
:
p
[RTA]super password level 3 cipher huawei
t
t
h
:
 Configure login using password.
s
e
c
[RTA]user-interface vty 0 4r
u
[RTA-ui-vty0-4]set authentication
password cipher huawei
o
s
[RTA-ui-vty0-4]quit e
R
[RTA]
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 19
o
n
e
/
m
o
c
Common Commands (5)

.
i
e
w
a
u
h
.
g
Enter the interface view.
[RTA]interface GigabitEthernet 0/0/0
[RTA-GigabitEthernet0/0/0]
Configure IP addresses.
r
a
le
n
i
n
/
/
[RTA-GigabitEthernet0/0/0]ip address 10.0.0.1
: 24
p
[RTA-GigabitEthernet0/0/0]
t
t
h
 Display the configuration:in the current view.
s
e
c this
[RTA-GigabitEthernet0/0/0]display
r
u
#
o
s
interface GigabitEthernet0/0/0
e
R
shutdown
g 255.255.255.0
ip address 10.0.0.1
n
i
#
n
r
return
a
Le
r
Copyrig
Pa ge 20
o

n
e
/
m
o
c
Common Commands (6)

w
a
u
h
.
g
Cancel the configuration.
[RTA-GigabitEthernet0/0/0]undo shutdown
[RTA]

Quit the current view.
[RTA-GigabitEthernet0/0/0]quit
[RTA]

.
i
e
Return to the user view.s:
n
i
n
r
a
le
/
/
p:
t
t
h
e
c
[RTA-GigabitEthernet0/0/0]return
r
u
<RTA>
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o
Pa ge 21
n
e
/
m
o
c
Common Commands (7)

.
i
e
w
a
u
h
.
g
Log in to the device through Telnet.
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
Login authentication
u
o
s
t
t
h
e
R
Password: (enter
the password configured for VTY user)
g
Info: The maxin
number of VTY users is 10, and the number
n VTY users on line is 1.
of current
r
<RTA>ea
L
r
Copyrig
Pa ge 22
o
n
e
/
m
o
c
Common Commands (8)

.
i
e
w
a
u
h
.
g
Increase user level.
n
i
n
<RTA> super 3
Password: (enter the super password)
Now user privilege is 3 level, and only those commands whose level is equal to
or less than this level can be used.
Privilege note: 0-VISIT, 1-MONITOR, 2-SYSTEM, 3-MANAGE
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 23
n
e
/
m
o
c
Contents
.
i
e


Information Center

File Operation

Software Upgrade
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 24
Information Center
n
e
/
.
i
e
m
o
c
w
a
The information center works as the information hub of a switch. It
classifies and
u
.h
filters the output of a system. The information center uses a g
debugging
program to
noperation and analyze
i
help network administrator and developers monitor network
n
r
a
network faults.
e
l
/
The information center receives and processes
information of the following types:
/
:
p
logs
t
t
h
Debug information
:
s
e
Traps
c
r
u
o
s
Sep 28 2011 09:29:08
ReRTA %%01PHY/1/PHY(l)[0]: GigabitEthernet0/0/0:
change status togup
n
Sep 28 2011 i
09:29:08
RTA %%01IFNET/4/LINKNO_STATE(l)[1]:The line
nthe interface GigabitEthernet0/0/0 has enter.
protocol on
r
a
e
L
r
Copyrig
Pa ge 25
o





n
e
/
m
o
c
Information Level
Level
Emergency
1
Alert
2
Critical
3
Error
4
Warning
5
Notice
6
7
e
r
o
Re
g
n
i
Informational
n
r
Debugging
a
e
L
w
a
u
h
.
g causes the system
A fatal fault occurs in the device, which
n
to fail to run normally unless theidevice is restarted.
rn which requires
A critical fault occurs in theadevice,
e
immediate action.
l
/
A sever fault occurs /
in the device, which requires that
:
actions be taken p
to analyze or process it.
t
t
Incorrect operation
or an abnormal process occurs in the
h
device, which
does not affect subsequent services but
:
s
requires
e attention and cause analysis.
c
Anrabnormality that may result in a fault occurs in the
u
o
device, which requires full attention.
s
Severity
0
.
i
e
Description
A key operation is performed to keep the device running
normally.
A normal operation is performed.
A normal operation is performed, which requires no
attention.
Pa ge 26
n
e
/
m
o
c
Information Output
Channel
0
Default Channel
Output
Name
Direction
Console
console
1
Monitor
monitor
2
Loghost
loghost
3
trapbuffer
trapbuffer
4
logbuffer
logbuffer
5
6
7
8
9
snmpagent
Unspecified
Unspecified
Unspecified
channel9
snmpagent
Unspecified
Unspecified
Unspecified
logfile
n
r
a
e
r
o
Le
g
n
i
w
a
u
Description
h
.
g
Outputs information to the local console that can receive logs,
traps, and debugging information.
Outputs information to the virtual type terminal (VTY) that can
receive logs, traps, and debugging information.
This is helpful for remote maintenance.
Outputs information to the log host that can receive logs, traps, and
debugging information.
The information is saved to the log host in the file format for
convenient reference.
Outputs information to the trap buffer that can receive traps.
An area is specified inside a device as the trap buffer recording
traps.
Outputs information to the log buffer that can receive logs.
An area is specified inside a device as the log buffer for recording
logs.
Outputs information to the SNMP agent that can receive traps.
Reserved.
Reserved.
Reserved.
Outputs information to log files that can receive logs, traps, and
debugging information. Information is saved to the hard disk or
Flash memory in the file format.
The supported file types vary according to products used. For
details, refer to the configuration guide of each product.
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
Re
.
i
e
t
t
h
Pa ge 27
Information Shield
n
e
/
.
i
e
m
o
c
w
a
To flexibly control information output, the information center
u provides the
h
.
information shield function. You can use commands tog configure the type,
n
i
n to be output.
severity, and originating module of the information
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 28
o

Information Center Configuration .
i
m
o
c

Enable the information center.
u
h
.
e
w
a
g
n
The information center of VRP is enabled by
i default.
n
r
a
<RTA>system-view
e
l
Enter system view, return user view with Ctrl+Z./
/
[RTA]info-center enable
:
p
Info: Information center is enabled.
t
ht
 Disable the information center.
:
s
e
c
No information will rbe output.
u
o
<RTA>system-view es
Enter system view, R
return user view with Ctrl+Z.
g
[RTA]undo info-center
enable
n
i
Info: Information
n center is disabled.
r
a
e
L
r
Copyrig
Pa ge 29
o


n
e
/
n
e
/
m
o
c
Information Output
Operation
.
i
e
w
a
u
h
.
g
Command
n
i
n
Output information to the
console.
info-center console channel { channel-number | channel-name }
Telnet terminal or dumb
terminal.
info-center monitor channel { channel-number | channel-name }
r
a
le
/
/
: { channel-number | channel-name }
p
info-center snmp channel
t
SNMP agent.
t
h
info-center logbuffer [ channel { channel-number | channel-name } |
Set the log buffer size and
: ]*
output information to the log size buffersize
s
e
buffer.
c
r loghost ip-address [ channel { channel-number |
u
info-center
o
s
channel-name
} | facility local-number | language { chinese |
e
log host.
R english } ] *
gand info-center trapbuffer [ channel { channel-number | channel-name }
n
Set the trap buffer size
ito the | size buffersize ] *
output information
n
trap buffer. ar
Le
r
Copyrig
Pa ge 30
o
n
e
/
m
o
c
Control Information Output
Command
w
a
u
h
.
g
Function
Default Value
terminal
debugging
Enables terminal display.
terminal logging
Enables log display on
terminal.
n
i
nDisabled
r
a
le
/
/
p:
t
t
Enables traphdisplay on
:
terminal.
s
e
c
r
u
Enable
log, trap, and
o
s
e debugging information
terminal trapping
terminal monitor
ng
i
n
r
e
r
o
.
i
e
R
display on terminal.
Enabled
Enabled
Enabled for
console and
disabled for
terminal
a
e
L
Pa ge 31
n
e
/
m
o
c
Contents
.
i
e


Information Center

File Operation

Software Upgrade
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 32
File System
n
e
/
.
i
e
m
o
c
w
a
u the storage
 The file system manages files and directories on
h
.
g
n
devices. It can create, delete, modify, or rename
a file or
i
n
r
a
directory, or display the contents of aefile.
l
/
/
 The file system has two functions:
:
p
t
t
Managing storage devices h
:
s
e are stored on those devices
Managing the files that
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 33
o


n
e
/
m
o
c
Storage Device Operation

.
i
e
w
a
u
h
.
g
Format the storage device: format
n
i
n
<RTA>format flash:
All data(include configuration and system startup file) on flash: will be lost ,
proceed with format ? [Y/N]:y
%Format flash: completed.
r
a
le
/
/
: device: fixdisk
p
 Repair the file system on the storage
t
t
h
<RTA>fixdisk flash:
:
Fixdisk flash: will take long time ifsneeded.
e
%Fixdisk flash: completed. c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 35
o
n
e
/
m
o
c
Directory Operation (1)

.
i
e
w
a
u
h
.
g
Display the current directory: pwd
n
i
n
<RTA>pwd
flash:

Change the current directory: cd
/
/
p:
<RTA>pwd
flash:
<RTA>cd temp
<RTA>pwd
flash:/temp

r
a
le
:
s
e
c
r
t
t
h
Display directory orufile: dir
o
s
e
R
<RTA> dir /all
Directory of flash:/
Idx Attr Size(Byte) Date
Time(LMT) FileName
0 -rw- 10117356 Jan 06 2007 19:37:46 ar2220_v200r001c00spc200.cc
1 -rw5024 Jan 09 2007 15:53:26 config.cfg
3 -rw- 5024 Jan 09 2007 16:27:06 [1.txt]
n
r
a
e
r
o
g
n
i
Le
Pa ge 36
n
e
/
m
o
c
Directory Operation (2)

.
i
e
w
a
u
h
.
g
Create a directory: mkdir
n
i
n
<RTA>mkdir test
Info: Create directory flash:/test......Done.
<RTA>dir test
Directory of flash:/
Idx Attr Size(Byte) Date
Time(LMT) FileName
0 drw- Sep 27 2011 17:31:40 test
2,540 KB total (2,520 KB free)
r
a
le
/
/
p:

Delete a directory: rmdirs:
t
t
h
e
c
r
u
o
s
<RTA>rmdir test
Remove directory flash:/test?[Y/N]:y
%Removing directory flash:/test...Done!
<RTA>dir test
Error: File can't be found "test".
<RTA>
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 37
n
e
/
m
o
c
File Operation (1)

.
i
e
w
a
u
h
.
g
Copy a file: copy
n
i
n
<RTA>copy vrpcfg.cfg flash:/test/
Copy flash:/vrpcfg.cfg to flash:/test/vrpcfg.cfg?[Y/N]:y
100% complete
Info: Copied file flash:/vrpcfg.cfg to flash:/test/vrpcfg.cfg...Done.
r
a
le

/
/
p:
Move a file: move
:
s
e
c
r
t
t
h
<RTA>move vrpcfg.cfg flash:/test/vrpcfg.cfg
Move flash:/vrpcfg.cfg to flash:/test/vrpcfg.cfg ?[Y/N]:y
%Moved file flash:/vrpcfg.cfg to flash:/test/vrpcfg.cfg.
u
o
s
 Rename a file: rename
e
R
g
<RTA>rename vrpcfg.cfg
vrpcfg_20110927.cfg
n
i
Rename flash:/vrpcfg.cfg
to flash:/vrpcfg_20110927.cfg ?[Y/N]:y
n
r file flash:/vrpcfg.cfg to flash:/vrpcfg_20110927.cfg ......Done.
Info: Rename
a
Le
r
Copyrig
Pa ge 38
o
n
e
/
m
o
c
File Operation (2)

.
i
e
w
a
u
h
.
g
Delete a file: delete
n
i
n
<RTA>delete vrpcfg.cfg
Delete flash:/vrpcfg.cfg?[Y/N]:y
Info: Deleting file flash:/vrpcfg.cfg...succeeded.

<RTA>undelete vrpcfg.cfg
Undelete flash:/vrpcfg.cfg?[Y/N]:y
%Undeleted file flash:/vrpcfg.cfg.

/
Restore a deleted file: undelete :/
:
s
e
c
r
p
t
ht
r
a
le
Remove files from u
the recycle bin: reset recycle-bin
o
s
e
R
<RTA>reset recycle-bin
Squeeze flash:/vrpcfg.cfg?[Y/N]:y
Clear file from flash will take a long time if needed...Done.
%Cleared file flash:/vrpcfg.cfg.
n
r
a
e
r
o
g
n
i
Le
Pa ge 39
n
e
/
m
o
c
File Operation (3)

.
i
e
w
a
u
h
.
g
Display text file content: more

n
i
n
Only text files are displayed.
r
a
le
<RTA>more vrpcfg.cfg
#
sysname RTA
#
……
#
user-interface con 0
user-interface vty 0 4
set authentication password cipher N`C55QK<`=/Q=^Q`MAF4<1!!
user-interface vty 16 20
#
return
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 40
n
e
/
m
o
c
Saving Configuration File

.
i
e
w
a
u
h
.
g
Save the current configurations: save

n
i
n
By default, the VRP saves the current configurations as vrpcfg.zip.
r
a
le
<RTA>save
The current configuration will be written to the device.
Are you sure to continue?[Y/N]y
Info: Please input the file name(*.cfg,*.zip)[vrpcfg.zip] (press Enter)
Now saving the current configuration to the slot 0 .............
Info: Save the configuration successfully.
/
/
p:
t
t
h
:
s
e using a user-defined name: save xyz.cfg
Save the current configurations
c
r
u
o
<RTA>save rta.cfg es
Are you sure to saveRthe configuration to flash:/rta.cfg?[Y/N]:y
g configuration to the slot 0 ..
Now saving thencurrent
iconfiguration successfully.
Info: Save the
n
r
a
Le
r
Copyrig
Pa ge 41
o

n
e
/
Displaying and Clearing Configuration
m
o
c
.
Files
ei
w
a
Display the saved configurations: display saved-configuration
u
h
.
g
<RTA>display saved-configuration
n
i
#
n
r
sysname RTA
a
e
#
l
/
……
/
:
p
Clear configuration files: reset saved-configuration
t
ht
:
<RTA>reset saved-configuration
s
econfiguration in the device.
The action will delete the saved
c
r
u
oerased to reconfigure. Continue? [Y/N]:y
The configuration will be
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 42
o


n
e
/
Specifying the Configuration File for om
c
.
the Next Startup
ei
w
a
The configuration file name extension must be .cfg or .zip.u
h
.
g of the storage
The system startup file must be stored in the root directory
n
i
n
device.
r
a
e
<RTA>startup saved-configuration rta.cfg
l
/booting system.
Info: Succeeded in setting the configuration for
/
:
<RTA>display startup
p
t
MainBoard:
t
Configured startup system software:h
NULL
:
Startup system software:
s
e
Next startup system software:
NULL
c
r
Startup saved-configuration
file:
NULL
u
o
Next startup saved-configuration
file: flash:/rta.cfg
s
e
…….
R
<RTA>
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 43
o


n
e
/
VRP Functions as the FTP or TFTP om
c
.
Client
ei

w
a
u
h
.
g
FTP Client
<RTA>ftp 10.0.0.2
Trying 10.0.0.2 ...
Press CTRL+K to abort
Connected to 10.0.0.2.
220 FTP service ready.
User(10.0.0.2:(none)):ftp (FTP server user name)
331 Password required for ftp.
Enter password: (password)
230 User logged in.
[ftp]
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
t
t
h
e
R
# Download filesgfrom the server.
n get vrpcfg_0927.cfg flash:/vrpcfg.cfg
<RTA>tftp 10.0.0.2
i
n to the server.
# Upload files
r
a 10.0.0.2 put vrpcfg.cfg vrpcfg_0928.cfg
<RTA>tftp
e
L
r
Copyrig
Pa ge 44
o

TFTP Client
n
e
/
m
o
c
FTP Server

.
i
e
w
a
u
h
.
g
Enable the FTP server.
n
i
n
[RTA]ftp server enable
Info: Succeeded in starting the FTP server.

Configure FTP user attributes.
[RTA]aaa
[RTA-aaa]local-user
[RTA-aaa]local-user
[RTA-aaa]local-user
[RTA-aaa]local-user
[RTA-aaa]quit
n
r
a
e
r
o
g
n
i
r
a
le
/
/
p:
t
t
h
ftp password simple ftp
ftp service-type ftp
ftp level 15
ftp ftp-directory flash:/
:
s
e
c
r
u
o
s
Re
Le
Pa ge 45
n
e
/
m
o
c
Contents
.
i
e


Information Center

File Operation

Software Upgrade
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 46
n
e
/
m
o
c
Why Upgrade?

.
i
e
w
a
u
h
.
g
New version provides new functions.

Newly developed functions

Improved usability

Increased reliability
n
i
n
r
a
le
/
/
p:
t
t
h versions.
 New versions fix the bugs in old
:
s
e
Software always hascbugs.
r
u
oknown bugs.
New versions fix
s
Re
g
n
i
n
r
a
Le
r
Copyrig
o


Pa ge 47
n
e
/
m
o
c
Upgrade Risk

Upgrade risk
.
i
e
h
.
g
w
a
u
If the features provided by the new version are modified compared
n
i
with the old version, services may be affected.n
r
a
eupgrade, the services will
The device needs to be restarted after the
l
/
/
be interrupted.
:
p
t
t
If the upgrade operation is incorrect,
h the device cannot start.
:
s
Risk control
e
c
r
Before the upgrade,uask the qualified personnel whether the device
o
s
can be upgraded.
Re
g
Make an upgrade
plan and prepare upgrade tools and software.
n
i
n
r
Back
a up the configurations and license files for rollback.
e
L
r
Copyrig
Pa ge 48
o







n
e
/
m
o
c
Upgrade Method
Method
Interface
Local
upgrade
i
n
r
e
r
o
a
e
L
Onsite/Remote
w
a
u
h Impact
.
g
n
i
n
r
a
e The device does not
l
Remote or /onCLI
need to be restarted
/
site
:
p
after the upgrade.
t
ht
The device must be
:
s
BootROM ce On-site
restarted after the
r
upgrade.
u
o
s
Re
The device must be
Remote
or
ong
restarted after the
nCLI
In-service
patching
In-service
upgrade
.
i
e
site
upgrade.
Pa ge 49
n
e
/
m
o
c
Upgrade Procedure
.
i
e
w
a
u
h
.
g

Confirm whether the device needs to be upgraded.

Prepare the software, upgrade guide, and tools.

Read the release notes and upgrade guide. Make the upgrade and
rollback plans.





e
r
o
r
a
le
/
/
p:
t
t
h
Back up configurations and:license files.
s
e
c files.
Upload the new version
r
u
o
Set the new version
s files as the next startup files.
e
R
Restart thegdevice.
n
i
n upgrade.
Verifyrthe
a
e
L
Upgrade

n
i
n
Pa ge 50
n
e
/
m
o
c
CLI Upgrade (1)

Prepare for the upgrade.









e
r
o
Documents, such as upgrade guide
.
i
e
w
a
u
h
.
g
n
i
n and network cables
Software and hardware tools, such as FTP server
r
a
e
New version files: provided by Huawei l
/
/
License files: provided by Huawei p:
t
t
h
Configuration file of the new version
:
s
Current version and device
e operating status
c
r can connect to the FTP server as an FTP
u
FTP server: the device
o
s
client
Re
g old configuration file and license files
Data backup:
n
i
n
Newar
version software, configuration file, and license file
Le
Pa ge 51
n
e
/
m
o
c
CLI Upgrade (2)

.
i
e
w
a
u
h
.
g
Specify the system software for next startup.

n
i
n
Configure the loaded system software as the startup program of the
r
a
e
<RTA> startup system-software sd1:/ar2220_v200r001c01.cc
l
/ system.
Info: Succeeded in setting the software for booting
/
:
p
Specify the configuration file for nexttstartup.
ht
If a new configuration file is:used, specify the new configuration file for
s
e
next startup. If you do not
c specify the configuration file, the old
r
ube used after the upgrade.
configuration file will
o
s
e
R
<RTA> startup saved-configuration
vrpcfgnew.cfg
gin setting the configuration for booting system.
Info: Succeeded
n
i
n
r
a
Le
r
Copyrig
Pa ge 52
o
master MPU.


CLI Upgrade (3)
n
e
/
.
i
e
m
o
c
w
a
u
 Check whether the next startup file is the new h
system
file.
.
g
n
i
n
r
a
<RTA> display startup
e
l
MainBoard:
/
/
Startup system software:
sd1:/ar2220_v200r001c00spc200.cc
:
p sd1:/ar2220_v200r001c01.cc
Next startup system software:
t
Backup system software for next startup:
ht null
Startup saved-configuration file: :
sd1:/iascfg.zip
s
Next startup saved-configuration
e file: sd1:/vrpcfgnew.zip
c
Startup license file:
null
r
u
Next startup license file:
null
o
s
Startup patch package:
null
e
Next startup patchRpackage:
null
g
Startup voice-files:
null
n
i
Next startup
null ……
n voice-files:
r
a
e
L
r
Copyrig
Pa ge 53
o
n
e
/
m
o
c
CLI Upgrade (4)

.
i
e
w
a
u
h
.
g
Restart the device.
n
i
n
<RTA> reboot
Info: The system is now comparing the configuration, please wait.
Warning: All the configuration will be saved to the next startup configuration.
Continue ? [y/n]:y # If you want to use the new configuration file, enter N.
It will take several minutes to save configuration file, please wait...
...................
Configuration file had been saved successfully
Note: The configuration file will take effect after being activated
<Huawei>
System will reboot! Continue ? [y/n]:y
Info: system is rebooting ,please wait...
r
a
le
/
/
p:
:
s
e
c
r
u
o
s
t
t
h
e
R
 Activate the license file. (optional)
g license.dat
n
<RTA> license
active
i
n
Info: The License
is being activated. Please wait for a moment.
r
a
Info: Succeeded
in activating the License file on the master board.
e
L
r
Copyrig
Pa ge 54
o
n
e
/
m
o
c
CLI Upgrade (5)

.
i
e
w
a
u
h
.
g
Verify the upgrade.
n
i
n
<RTA> display version
Huawei Versatile Routing Platform Software
VRP (R) software, Version 5.90 (AR2200 V200R001C01)
Copyright (C) 2011 HUAWEI TECH CO., LTD
Huawei AR2220 Router uptime is 0 week, 1 day, 3 hours, 24 minutes
BKP 0 version information:
1. PCB
Version : AR01BAK2A VER.A
2. If Supporting PoE : No
3. Board Type : AR2220
4. MPU Slot Quantity : 1
5. LPU Slot Quantity : 6
......
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 55
Rollback
n
e
/
.
i
e
m
o
c
w
a
u
 You may need to roll back the version if some h
events
occur,
.
g
n be restored
for example, services are affected and cannot
i
n
r
a
after the upgrade.
e
l
/
/ as the upgrade
 The rollback procedure is the same
:
p
t
procedure, except that the startup
file must be the old
ht
:
s
version file.
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 56
o
n
e
/
m
o
c
Summary
.
i
e

VRP basic configuration

Information center

File system operation

Software upgrade
w
a
u
h
.
g
n
i
n
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Pa ge 57
Questions
n
e
/
.
i
e
m
o
c
w
a
u by VRP?
 Which are the default command levels supported
h
.
g
n
 How do you disable information output oniterminals?
n
r
a
e
 How do you delete the configuration
l file on VRP?
/
/
:
p
 Which upgrade methods are supported
by VRP?
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyrig
Pa ge 58
o
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank :you
//
p
www.huawei.com
t
t
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
h
n
e
/
m
o
c
.
i
e
w
a
u
h
.
OSPF Feature and
g
n
i
n
r
Configuration
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
g
n
i
Re
e
L
Copyright ©2012 Huawei Technologies Co., Ltd. All rights reserved.
e
r
o
www.huawei.com
n
e
/
Preface
.
i
e
m
o
c
w
a
u
 Open Shortest Path First (OSPF) is a link state-based
h
.
g
n the Internet
interior gateway protocol (IGP) developediby
n
r
a
Engineering Task Force (IETF).
e
l
/
/
 As a link state-based protocol featuring
fast convergence,
:
p
t
t
loop-free routing, and high scalability,
OSPF has become an
h
: used.
s
excellent IGP that is widely
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
e ©2012 Huawei Technologies Co., Ltd. All rights reserved.
r
Copyright
Page 2
o
n
e
/
Objectives
.
i
e
m
o
c
w
a
uto:
h
.
g
n
Describe the feature of OSPF routing protocol
i
n
r
aof link state algorithm
Describe the route calculation process
e
l
/
/
:
Describe basic concepts of OSPF
p
t
ht packet types
Describe OSPF routing protocol
:
s
e protocol neighbor relationship
Describe OSPF routing
c
r
u
o calculation process of OSPF
Describe the route
s
Re
gOSPF routing protocol
Configure
n
i
n
r
a
Le
r
Copyright
Page 3
o







n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. OSPF Overview
n
i
n
2. Basic OSPF Concepts
r
a
le
3. OSPF Route Calculation
4. OSPF Configuration
/
/
p:
t
t
h
5. OSPF Application Scenarios
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 4
m
o
c
Basic Characteristics of OSPF i.
e
w
a

Supporting Classless Inter-Domain Routing
hu (CIDR)

Free of routing loops

Fast convergence

t
Sending and receiving protocol
data by using IP
t
h

r
a
le
/
/
p:
:
s
e
c
r
multicast

.
g
n
i
n
u
o
Supporting equal-cost
routes
s
Re
Supporting
ng protocol packet authentication
i
n
r
e
r
o
a
e
L
Page 5
n
e
/
n
e
/
m
Route Calculation Using the Link
o
c
.
State Algorithm
ei
w
a
u
h
.
g
LSDB
n
i
n
r
a
le RTB’s LSA
RTA’s LSA
RTA
RTB
/
/
p:
RTC
t
t
h
LSA flooding
RTD
:
s
e
c
r
Destination
Next hop
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
e
r
o
RTD’s LSA
SPF
algorithm
u
o
s...
Re
g
n
i table
IP routing
n
r
a
e
RTC’s LSA
Cost
...
...
...
...
Route calculation
Shortest path tree
L
Page 6
n
e
/
m
o
Self-Test Question About OSPF Overview
c
.
i
e
w
a
u true? (
1.Which of the following statements about OSPFhare
.
g
n
)
i
n
r
a
A.OSPF uses a link state routing algorithm.
e
l
/
/
:
B.OSPF uses a distance vector routing
algorithm.
p
t
t
h
C.OSPF is an Interior Gateway
Protocol (IGP).
:
s
e
c
D.OSPF is an ExteriorurGateway
Protocol (EGP)
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 7
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. OSPF Overview
n
i
n
r
a
le
/
/
p:
t
t
h
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 8
AS（Autonomous System）
n
e
/
.
i
e
m
o
c
w
a
u exchange
 In OSPF, an AS refers to a group of routers that
h
.
g
n protocol.
routing information by running the same routing
i
n
r
a
e
l
/
/
:
p
t
ht
:
s
e
c
r
OSPF
u
o
s
e
R
g
n
i
 In this example,
all the routers run OSPF and belong to the
n
r
a
same
Le AS.
r
Copyright
Page 9
o
Router ID
n
e
/
.
i
e
m
o
c
w
a
 A router ID is a 32-bit integer that uniquely identifies
an
u
h
.
g ID is the same
OSPF router in an AS. The format of a router
n
i
n
r
as that of an IP address.
a
e
l
/
[Quidway]router
id 1.1.1.1
/
:
[Quidway]display
router id
p
t
RouterID:1.1.1.1
ht
:
s
e router id 1.1.1.1 command to
 In this example, run the
c
r
u
o ID of the router as 1.1.1.1. After the
configure the router
s
e
R
router ID is configured, run the display router id command.
g
n
i output information shows that the router ID of
The command
n
r
a
e is 1.1.1.1
the Lrouter
r
Copyright
Page 10
o
Cost
n
e
/
.
i
e
m
o
c
w
a
u from 1 to
 An OSPF cost is a 16-bit unsigned integer ranging
h
.
g
n
65535.
i
n
r
a as 108/BW(bps)
1. By default, the cost of an interface is calculated
e
l
/
2. The cost of an OSPF interface can be/configured manually
:
p
t
t
h[Quidway-Ethernet0/0]ospf cost 100
:
s
e
c
r are configurable. When configuring
3. Bandwidth referenceuvalues
o
s
bandwidth reference
values,
ensure that the bandwidth reference values
e
R
of all the routers
g running the OSPF process are the same.
n
[Quidway]ospf
i
n
[Quidway-ospf-1]bandwidthr
a
reference 1000
Le
r
Copyright
Page 11
o
n
e
/
m
o
c
OSPF Area(1/2)
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Area 1
Area 4
/
/
p:
Area 0 is Backbone area ,
for ABR at least one
interface belongs to Area
0.
Area 0
:
s
e
c
r
t
t
h
u
o
s
rn
e
r
o
a
e
L
g
n
i
e
RArea
2
Area 3
Page 12
n
e
/
m
o
c
OSPF Area(2/2)
.
i
e
w
a
u
h
.
g
n
i
n
Area 1
r
a
le
Area 4
/
/
p:
Area 0
:
s
e
c
r
t
t
h
u
o
s
Area 2
g
n
i
Re
Area 3
[Quidway]ospf
[Quidway-ospf-1]area 2
[Quidway-ospf-1-area-0.0.0.2]network 12.1.1.0 0.0.0.3
n
r
a
e
r
o
Le
Page 13
n
e
/
m
o
c
OSPF Router Roles
.
i
e
w
a
u
BR
h
.
g
n
i
n
ASBR
r
a
le
Area 0
/
/
p:
Import ISIS route
t
t
h Area 2
Area 1
:
s
e ABR
c
ABR
r
u
o
n
r
a
e
r
o
gIR
n
i
s
e
R
Le
Page 14
n
e
/
Self-Test Questions About OSPF Basicom
c
.
Concepts
ei
w
a
u an
1. In the OSPF routing domain, ( ) uniquely identifies
h
.
g
n
OSPF router.
i
n
r
a
A. Area ID
e
l
/
/
:
B. AS ID
p
t
t
h
C. Router ID
:
s
e
c
D. Cost
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 15
o
n
e
/
c
.
Concepts
ei
w
a
u
2.Which of the following statements about the backbone
area
h
.
g
n
are true in an OSPF network? ( )
i
n
r
a
A. The area ID of the backbone area isle0.0.0.0.
/
/
:
B. All non-backbone areas must connect
to the backbone
p
t
ht
area.
:
s
ce
C. No area can directlyrconnect
to another one.
u
o
s
D. At least one backbone
area is required in areas to which
e
R
g
the ABR belongs.
n
i
n
r
a
Le
r
Copyright
Page 16
o
n
e
/
c
.
Concepts
ei
w
a
u external
3. In the OSPF routing domain, the router importing
h
.
g
n
routes is called ( ).
i
n
r
a
A. ABR
e
l
/
/
:
B. BR
p
t
t
h
C. ASBR
:
s
e
c
D. IR
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 17
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. OSPF Overview
n
i
n
r
a
le
/
/
p:
t
t
h
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 18
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
3.1 OSPF Packets
n
i
n
r
a
e
3.2 Establishment of Neighbor Relationship
and
l
/
/
:
Adjacency
p
t
t
h
3.3 Establishment of An: Adjacency and LSDB
s
e
Synchronization rc
u
o
s Calculation
3.4 OSPF Route
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 19
o
n
e
/
m
o
c
OSPF Packet Types
.
i
e
w
a
u
Type
h
Packet function
g.
n
i
n
Discover /maintain
neighbor
r
Hello
a
e
relationships
l
/
/
:
Database DescriptionSummarize
database contents
p
t
t
h
Link State Request
Database download
:
s
e
c
Link State Update
Database update
r
u
o
s Ack
e
Link State
Flooding acknowledgement
R
g
n
i
n
ar
1
2
3
4
5
e
r
o
Packet name
Le
Page 20
n
e
/
OSPF Packet Header Authentication- om
c
.
Interface Authentication
ei
w
a
u
Configure simple password
"huawei"
h
.
g
n
i
n
Area 1
Loopback0
E0/0
10.1.1.1/30
1.1.1.1/32
RTA
e
r
o
:
s
e
c
r
u
o
s
[RTA-Ethernet0/0]ospf
e
R
plain huawei
g
n
i
[RTB-Ethernet0/0]ospf
n
r huawei
a
plain
Le
r
a
le
/
/
p: E0/0
t
t
h
Loopback0
.2
2.2.2.2/32
RTB
authentication-mode simple
authentication-mode simple
Page 21
n
e
/
OSPF Packet Header Authentication- om
c
.
Area Authentication
ei
w
a
u
h
.
g
Configure simple password
"huawei"
n
i
n
Area 1
Loopback0
E0/0
10.1.1.1/30
1.1.1.1/32
RTA
e
r
o
:
s
e
c
r
r
a
le
/
/
p: E0/0
t
t
h
Loopback0
.2
2.2.2.2/32
RTB
u
o
[RTA-ospf-1-area-0.0.0.1]authentication-mode
s
e
R huawei
simple plain
g
n
[RTB-ospf-1-area-0.0.0.1]authentication-mode
i
n
r plain huawei
simple
a
Le
Page 22
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
3.1 OSPF Packets
n
i
n
r
a
e
and
l
/
/
:
Adjacency
p
t
t
h
s
e
Synchronization rc
u
o
s Calculation
3.4 OSPF Route
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 23
o
n
e
/
What Is Neighbor? What Is
Adjacency?
m
o
c
.
i
e
h
.
g
I have 3
neighbors
n
i
n
r
a
le
RTA
/
/
p:
t
t
h
10.1.1.1
10.1.1.2
:
s
e Ethernet
c
10.1.1.3
r
10.1.1.4
u
o
s
n
r
a
e
r
o
g
n
i
w
a
u
Re
Le
Page 24
n
e
/
What Are the OSPF Network Types?-P2Pom
c
.
and Broadcast
ei
w
a
u
h
.
g
n
i
n
10.1.1.
1
PPP
r
a
e
10.1.1.
l
1/
/
p:
20.1.1.
1
:
s
e
c
r
Point to Point Network
u
o
s
n
r
a
e
r
o
g
n
i
Re
t 10.1.1.
t
h 3
10.1.1.
2
Ethernet
10.1.1.
4
Broadcast Network
Le
Page 25
n
e
/
10.1.1.1
m
o
c
What Are the OSPF Network Types?-NBMA
.
i
e
w
a
u
h
.
g
n
i
VPI/VCI=0/102
VPI/VCI=0/103
n
r
a
e
Full l
meshed
/
/ network
ATM
:
p
t
ht
:
ATM s
e
c
r
u
o
s
Re
g
n
i
Non-Broadcast
Multiple Access（NBMA）
n
r
a
e
L
r
Copyright
Page 26
o
n
e
/
10.1.1.1
m
o
c
What Are the OSPF Network Types?-P2MP
.
i
e
w
a
u
h
.
g
n
DLCI = 102
DLCI = 103
i
n
r
a
e
Non-full meshed
l frame
/
/
relay network
:
p
t
ht
:
s
FR ce
r
u
o
s
Re
g
n
i Point-to-MultiPoint
n
r
a
Le
r
Copyright
Page 27
o
n
e
/
Default Network Types Corresponding om
c
.
to Common Link Layer Protocols ei
w
a
u
h
.
g
Common data link
ar layer protocols
Network type
Broadcast
n
r
a
e
r
o
g
n
i
e
l
/
/
:
PPP, LAPB, HDLC
p
t
ht
:
s
Ethernet
e
c
r
u
o
Point-to-point
NBMA
n
i
n
s
e
R
Frame Relay, ATM
Le
Page 28
n
e
/
m
o
c
DR and BDR
.
i
e
w
a
u
h
.
g
n
i
n
I have 3 neighbors, but only
2 adjacencies
RTA
r
a
le
/
/
p:
t
t
h
: 10.1.1.1
s
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
10.1.1.2
Ethernet
10.1.1.3
10.1.1.4
BDR
DR
Le
Page 29
DR Election and BDR Election
n
e
/
.
i
e
m
o
c
w
a
u BDR are
 Instead of being manually specified, the DR and
h
.
g
n
elected among all the routers on the localinetwork
segment.
n
r
a
The DR priority of a router interface determines
the eligibility
e
l
/
of the interface in the DR election
/and BDR election.
:
p with highest Router
Router
t
htPriority may not be DR/BDR
:
s
e
10.1.1.3c
r
120
u
o
s
e
R
Ethernet
90 10.1.1.2
100 10.1.1.1
g
n
i
n BDR
Red numbers indicate
DR
r
a
Router Priority of interface
e
L
r
Copyright
Page 30
o
DR Election and BDR Election
n
e
/
.
i
e
m
o
c
w
a
DR election and BDR election takes time and affects the speed
u of OSPF
h
. the broadcast
g
route convergence. During the actual OSPF application,
n
i
n to the P2P type to
network and NBMA network types are often changed
r
ea command is used to
prevent the election of the DR or BDR. The lfollowing
/ interface:
/
change the network type of an OSPF network
:
p
t
[RTB-Ethernet0/0] ospf t
network-type p2p
h
:
The following figure describess whether adjacencies are established with
e
c
r types:
neighbors for different network
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 31
o


Network Type
Establish Adjacency with Neighbor or not
Point-to-Point
Neighbors always become adjacent
Point-to-MultiPoint
Neighbors always become adjacent
Broadcast
NBMA
DR is always adjacent to all the other routers including BDR;
BDR is always adjacent to all the other routers including DR;
Routers whose interface state is DROther is adjacent to only
DR and BDR.
Establishment of Neighbor
Relationship(1/3)
n
e
/
.
i
e
m
o
c
w
a
 Neighbor relationship establishment on a ubroadcast
h
.
g
network:
n
i
n
r id 2.2.2.2
Router id 1.1.1.1
Router
a
e
l
/
/
:
RTA
RTB
p
t
t
h
Down
Down
:
Hello (one-way)
s
e
Init
c
r
u
o
Hello (two-way)
s
Two-way e
R
g
n
Hello (two-way)
i
n
Two-way
r
a
e
L
r
Copyright
Page 32
o
1
2
3
Relationship(2/3)
n
e
/
.
i
e
m
o
c
w
a
u is as
 The difference between the 1-way and 2-way states
h
.
g
n router ID has
follows: If a Hello packet carrying the router's
i
n
r
ait indicates the 2-way
recently been seen from the neighbor,
e
l
/
state. Otherwise, it indicates the:1-way
state.
/
p
[Quidway]display ospf peer
t
t
h
OSPF Process 1 with Router ID 4.4.4.4
: Neighbors
s
e
c
Area 0.0.0.1 interfacer10.1.1.4(Ethernet0/0)'s neighbor(s)
u Address: 10.1.1.1
RouterID: 1.1.1.1 o
s Mode: None Priority: 1
State: 2 Way
e
R BDR: 10.1.1.3
DR: 10.1.1.2
g expires in 37s
Dead timer
n
Neighbor
i has been up for 00:00:00
n
r
a
Le
r
Copyright
Page 33
o
Relationship(3/3)
n
e
/
.
i
e
m
o
c
w
a
u network:
 Neighbor relationship establishment on a P2P
h
.
g
n id 2.2.2.2
i
Router id 1.1.1.1
Router
n
r
a
e
l
/
RTA
RTB
/
:
p
t
Down
t
Down
h Hello
Init
:
s
e
c
r
Hello
u
Init
o
s
e
R
 No DR or BDR needs to be elected on a P2P link, P2MP
g
n
i link.
link, or virtual
n
r
a
Le
r
Copyright
Page 34
o
1
2
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
3.1 OSPF Packets
n
i
n
r
a
e
and
l
/
/
:
Adjacency
p
t
t
h
s
e
Synchronization rc
u
o
s Calculation
3.4 OSPF Route
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 35
o
n
e
/
Adjacency Establishment
Process(1/2)
Router id
1.1.1.1
Exchange
DD, Seq=552A, I, M, MS
2
DD, Seq=5528, I, M, MS
e
r
o
4
5
Master
h
.
g
RTB
/
/
p:
1
t
t
h
:
s
3 e DD, Seq=5528
c
r
ou
s
e
R
Exchange
g
n
i
Exchange
n
r  Loading
Exchange
a
e
w
a
u
n
i
n
r
a
le
RTA
ExStart  Exchange
.
i
e
Router id
2.2.2.2
Adjacency relationship
ExStart
m
o
c
DD, Seq=5529, MS
DD, Seq=5529
ExStart
ExStart  Exchange
Exchange
Exchange  Full
L
Page 36
n
e
/
Adjacency Establishment
Process(2/2)
Router id
1.1.1.1
Adjacency relationship rn
a
e
l
RTA
7
Loading
Loading  Full
ng
i
n
r
e
r
o
.
i
e
w
a
u
hid
Router
.
g
n
2.2.2.2
i
RTB
/
/
:
p
LS
Request
t
t
h
Full
LS Update
ou
s
e
R
Full
:
s
8e
c
r
m
o
c
9
Full
LS Ack
Full
a
e
L
Page 37
n
e
/
m
Check Neighbor State of OSPF
o
c
.
i
Router
e
w
.
g
n
i
n
[RTA]display ospf peer
r
a
le
a
u
h
/
/
:
p
Area 0.0.0.0 interface 10.1.1.1(Ethernet0/0)'s
neighbor(s)
t
ht 10.1.1.2
RouterID: 2.2.2.2
Address:
:
State: Full Mode:esNbr is Master Priority: 1
rc 10.1.1.2
DR: 10.1.1.1 u
BDR:
so
Dead timer eexpires
in 35s
Rhas been up for 04:35:02
Neighbor
g
n
i
n
r
a
Le
r
Copyright
Page 38
o
Neighbors
LSDB Synchronization
n
e
/
.
i
e
m
o
c
w
a
 Synchronized LSDBs are the basis for proper OSPFuroute
h
.
g OSPF router
calculation. When an adjacency is established,nan
i
n
r adjacent router.
completes the LSDB synchronization withathe
e
l
 After an adjacency is established and /
LSDB synchronization is
/
:
p
completed, LSAs are updated in tthe following ways:
ht
Periodic update: Every 30:minutes, an OSPF router floods the LSAs
s
e
in the LSDB of the current
c area to the adjacent routers in the
r
u
o
corresponding areas.
s
e
R When a network topology change occurs, the
Triggered update:
g
n
router generates
new LSAs and floods them so that the topology
i
n
r about the network remains correct and consistent.
a
information
Le
r
Copyright
Page 39
o


n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
3.1 OSPF Packets
n
i
n
r
a
e
and
l
/
/
:
Adjacency
p
t
t
h
s
e
Synchronization rc
u
o
s Calculation
3.4 OSPF Route
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 40
o
n
e
/
m
o
c
What Is An LSA?
LSA Type
1
2
3
4
5
e
r
o
.
i
e
w
a
u
h
.
Generated by each router. Describing the
g collected states of the
n
Router-LSA router’s interfaces, flooded only within
i the area where this LSA is
n
generated.
r
a
Generated by DR, available linebroadcast and NBMA network.
/ attached to the network. flooded only
Network-LSA Describing the set of routers
/
:this LSA is generated.
within the area where
p
t
t
Generated by ABR.
h Describing routes to networks that are outside
Networkarea but inside
the AS, flooded within the area where this LSA is
:
s
Summary-LSA generated.e
c
r
u by ABR. Describing routes to ASBRs, flooded within the
ASBRGenerated
o
s where this LSA is generated.
Summary-LSA area
e
R
g- Generated by ASBR. Describing routes to destinations external to
AS-external
n
i As, flooded within the whole AS.
n
LSA
r
a
Le
LSA Name
LSA Description
Page 41
Intra-Area Route Calculation
n
e
/
.
i
e
w
a
u
h
.
g
n
i
n
Area 1
r
a
le
/
/
p:
Router-LSA
:
s
e
c
r
Network-LSA
t
t
h
DR
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 42
m
o
c
Inter-Area Route Calculation
n
e
/
.
i
e
w
a
u
h
.
g
n
i
n
r
a
e 0
lArea
Area 1
/
/
p:
N1
:
s
e
c
r
t
t
h
ABR
Router-LSA
n
r
a
e
r
o
g
n
i
u
o
s
Re
Network-Summary-LSA
Le
Page 43
m
o
c
n
e
/
m
o
External Route Calculation(1/2)i.c
e
w
a
u
h
.
g
Area 1
n
Area 0 ni
r
a
e
l
/
/
:
p
ABR tt
ASBR Connected to
h
another AS by
:
s
BGP
e
c
ASBR-externalo
-LSA
AS-external-LSA
ur
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 44
o
n
e
/
m
o
External Route Calculation(2/2)i.c
e
w
a
u
h
Des N1.
, type=1,
cost=100
g
Cost=1
n
i
RTC
n
RTA
r
a
e
l
/
RTB
/
:
p
Des N1, type=2, cost=20
Cost=1
t
ht
:
s
e
c
Destination Type Cost Next
hop
r
u
N1
1
101 soRTA
√
e
R RTB
N1
2
20
g
n
i
n
r
a
Le
r
Copyright
Page 45
o
n
e
/
Route Calculation in Special Areas- om
c
.
Stub Area(1/3)
ei
w
a
u
h
.
g
n
i
n
Stub Area
Flood AS- externalLSA
r
a
le
/
/
p:
Area 0
Area 1
RTB
:
s
e
c
r
t
t
h
Area 2
u
o
s
Re
n
r
a
e
r
o
Le
Flood AS- externalLSA
RTAConnected to another AS by BGP
gFlood a default route by Network
n
i
SummaryLSA ,will not flood AS
external LSA .
Page 46
n
e
/
c
.
Stub Area(2/3)
ei
w
a
u
Area 1
h
.
g
n
i
n
RTC
r
a
10.3.1.0/30
e
l
Area 0
RTA
RTB
10.1.1.0/30
.1
.2
10.2.1.0/30
.1
.2
/
/
p:
Stub Area
:
s
e
c
r
u
o
s
g
n
i
Re
.1
t
t
h
Configure a static to
10.4.1.0/24 on RTC and
import it to OSPF
[RTA-ospf-1-area-0.0.0.1] stub
n
r
a
[RTB-ospf-1-area-0.0.0.1] stub
e
r
o
Le
Page 47
RTD
.2
Loopback0
10.4.1.1/24
n
e
/
c
.
Stub Area(3/3)
ei
w
a
u
h
.
g
[RTA]display ospf lsdb
n
i
n
Link State Database
Type
Router
Router
Network
Sum-Net
Sum-Net
LinkState ID
2.2.2.2
1.1.1.1
10.1.1.2
0.0.0.0
10.2.1.0
Area: 0.0.0.1
AdvRouter
2.2.2.2
1.1.1.1
2.2.2.2
2.2.2.2
2.2.2.2
:
s
e
c
r
r
a
le
/ Age
/
p: 165
t
t
h
165
166
228
228
Len
36
36
32
28
28
Sequence
80000004
80000003
80000001
80000001
80000001
Metric
1
1
0
1
1
u
o
s
e
R
RTB only advertise a default
g an ASn
route not advertise
i
n
External-LSA.
r
a
Le
r
Copyright
o
Inter-area routes are still
advertised to STUB area.
Page 48
n
e
/
c
.
Total Stub Area(1/2)
ei
w
a
u
Area 1
h
.
g
n
i
n
RTC
r
a
10.3.1.0/30
e
l
Area 0
RTA
RTB
10.1.1.0/30
.1
.2
10.2.1.0/30
.1
.2
/
/
p:
Stub Area
:
s
e
c
r
u
o
s
g
n
i
Re
.1
t
t
h
Configure a static to
10.4.1.0/24 on RTC and
import it to OSPF
[RTA-ospf-1-area-0.0.0.1] stub
n
r
a
[RTB-ospf-1-area-0.0.0.1] stub no-summary
e
r
o
Le
Page 49
RTD
.2
Loopback0
10.4.1.1/24
n
e
/
c
.
Total Stub Area(2/2)
ei
w
a
u
h
.
g
n
i
n
[RTA]display ospf lsdb
r
a
le
Link State Database
Type
Router
Router
Network
Sum-Net
LinkState ID
2.2.2.2
1.1.1.1
10.1.1.1
0.0.0.0
Area: 0.0.0.1
AdvRouter
2.2.2.2
1.1.1.1
1.1.1.1
2.2.2.2
:
s
e
c
r
/
/
p: Age
t
t
h
10
10
14
550
Len
36
36
32
28
Sequence
80000008
80000008
80000001
80000001
u
o
s
n
r
a
e
r
o
Re
Only advertise a default route
Not advertise any inter area routing information
Not advertise any AS external LSA
g
n
i
Le
Page 50
Metric
1
1
0
1
n
e
/
c
.
Not So Stubby Area (NSSA)
ei
w
a
u
h
.
g
Transform type 7
LSA into type 5
LSA
Area 0
r
a
le RTC
RTD
/
/
10.1.1.0/24
10.2.1.0/24
10.3.1.0/24
:
p
.1
.2
.1
.1
.2
t .2
t
h
RTB :
s
Loopback0
e
10.4.1.1/24
c
r
u
o
Flood type 7 LSA
Flood type 5 LSAs
Re
g
n
[RTB-ospf-1-area-0.0.0.1]
nssa
i
n[RTC-ospf-1-area-0.0.0.1] nssa
r
a
e
L
RTA
e
r
o
Area 1
NSSA
n
i
n
Configure the static
route to10.4.1.0/24
Page 51
n
e
/
OSPF Route Aggregation-Route
Aggregation on ABR
RouterC
ABR
19.1.0.0/16
/
/
p:
r
a
le
RouterB
Re
[RouterA-ospf-1-area-0.0.0.19]abr-summary
19.1.0.0 255.255.0.0
n
r
a
e
r
o
Le
19.1.1.0/24
19.1.2.0/24
19.1.3.0/24
….
Area 19
u
o
s
g
n
i
w
a
u
n
i
n
t
t
h
ABR
:
s
e
c
r
.
i
e
h
.
g
RouterA
Area 0
m
o
c
Page 52
n
e
/
OSPF Route Aggregation-Route
Aggregation on ASBR
RouterC
ABR
19.1.0.0/16
r
a
le
/
/
p:
:19.1.0.0/16
s
e
c
r
RouterB
ASBR
u
o
s
Re
[RouterB-ospf-1-area-0.0.0.19]asbr-
g
n
i
summary 19.1.0.0 255.255.255.0
n
r
a
e
r
o
Le
w
a
u
n Import route
i
n
t
t
h
ABR
.
i
e
h
.
g
RouterA
Area 0
m
o
c
Page 53
19.1.1.0/24
19.1.2.0/24
19.1.3.0/24
….
Area 19
n
e
/
Self-Test Questions About OSPF Routeom
c
.
Calculation
ei
w
a
u
1. Which of the following OSPF protocol packetshcontains
.
g
n ( )
detailed information about the router link state?
i
n
r
a
A. LSR
e
l
/
/
:
B. LSU
p
t
t
h
C. Router LSA
:
s
e
c
D. AS-External LSA ur
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 54
o
n
e
/
c
.
Calculation
ei
w
a
uadjacency
2. Which of the following two routers can establish
h
.
g
n
relationships? ( )
i
n
r
A. Two routers in a point-to-point link lea
/
/
: in a broadcast network
B. A DR router and a DR-other router
p
t
t
h in a broadcast network
C. A DR router and a BDR router
:
s
e
c
D. Two DR-other routers
r in an NBMA network
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 55
o
n
e
/
c
.
Calculation
ei
w
a
u( )
3. ( ) indicates a stable neighbor relationship and
h
.
g
n neighbor and
indicates a stable adjacency relationship after
i
n
r
a and the LSDB is
adjacency relationships are established
e
l
/
synchronized.
/
:
p
t
A. Exchange
ht
:
s
e
B. Full
c
r
u
o
C. 2-Way
s
Re
g
D. Init
n
i
n
r
a
Le
r
Copyright
Page 56
o
n
e
/
c
.
Calculation
ei
4. OSPF calculates routes in an area based on ( h
w
a
u), calculates
.
g
routes between different areas based on (in ), and calculates
n
r
routes outside an area based on ( ).ea
l
/
/
A. Type 1 LSA
:
p
t
ht
B. Type 2 LSA
:
s
e
c
C. Type 3 LSA
r
u
o
s
D. Type 4 LSA e
R
g
n
E. Type 5 LSA
i
n
r
a
Le
r
Copyright
Page 57
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. OSPF Overview
n
i
n
r
a
le
/
/
p:
t
t
h
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 58
n
e
/
OSPF Configuration
.
i
e
m
o
c
w
a
Basic network Loopback interface (optional)hu
. an interface view
Create and enter
g
configuration
n IP address
Configureian
n the OSPF network type (optional)
Interface Configure
r
a
e
l
/
Router ID (optional)
/
:
p
Configuration roadmap for
t
Enter the
htOSPF view
OSPF on the router
Import
: an external route (optional)
s
e
Advertise
the default route (optional)
OSPF
c
r Enter the OSPF
Stub
u
Configure the area type (optional) NSSA
o area view
s
Enable the network segment
Re
requiring OSPF
g
n
i
n
r
a
Le
r
Copyright
Page 59
o
n
e
/
Configuring a Single OSPF Area
h
.
g
LB0: 2.2.2.2/32
n
i
n
GE1/0/0
10.0.0.1/30
GE1/0/1
192.168.1.1/24
GE1/0/0
10.0.0.2/30
r
a
le
RTB
GE1/0/1
192.168.2.1/24
/
/
p:
Area 0
t
t
h
[RTA]ospf
[RTA-ospf-1]area 0
[RTA-ospf-1-area-0.0.0.0]network 1.1.1.1 0.0.0.0
:
s
e
c
r
u
o
s
n
r
a
g
n
i
Re
Note: RTB configuration is similar to RTA configuration.
e
r
o
.
i
e
w
a
u
LB0: 1.1.1.1/32
RTA
m
o
c
Le
Page 60
m
o
c
Configuring Multiple OSPF Areas (1)
.
i
e
w
a
u
h
LB0: 1.1.1.1/32
LB0: 2.2.2.2/32
.
g
GE1/0/0
GE1/0/0 in
RTA
RTB
n
10.0.0.1/30
10.0.0.2/30
r
a
e
GE1/0/1
l
GE1/0/1
Area 0
192.168.2.1/24
/
192.168.3.1/24
/
:
p
LB0: 3.3.3.3/32
t
t
h
[RTA]ospf :
RTC
s
[RTA-ospf-1]area
0
e
c
[RTA-ospf-1-area-0.0.0.0]network
1.1.1.1 0.0.0.0
GE1/0/1
r
u
[RTA-ospf-1-area-0.0.0.0]network
10.0.0.0 0.0.0.3
192.168.3.1/24
o
s[RTA-ospf-1-area-0.0.0.0]network 192.168.1.0 0.0.0.255
e
R [RTA-ospf-1-area-0.0.0.0]quit
g [RTA-ospf-1]area 1
n
i
n
r
a
Le
r
Copyright
Page 63
o
n
e
/
m
o
c
Configuring Multiple OSPF Areas (2)
.
i
e
w
a
u
h
LB0: 1.1.1.1/32
LB0: 2.2.2.2/32
.
g
GE1/0/0
GE1/0/0 in
RTA
RTB
n
10.0.0.1/30
10.0.0.2/30
r
a
e
GE1/0/1
l
GE1/0/1
Area 0
192.168.2.1/24
/
192.168.3.1/24
/
:
p
LB0: 3.3.3.3/32
t
t
h
:
RTC
s
e
[RTC]ospf
c
GE1/0/1
r
[RTC-ospf-1]area
1
u
192.168.3.1/24
o
[RTC-ospf-1-area-0.0.0.1]network
3.3.3.3 0.0.0.0
s
10.0.0.0 0.0.0.3
Re[RTC-ospf-1-area-0.0.0.1]network
[RTC-ospf-1-area-0.0.0.1]network 192.168.3.0 0.0.0.255
g
n
i
n
r
a
e
L
r
Copyright
Page 64
o
n
e
/
n
e
/
Importing OSPF External Routes .
i
m
o
c
e
w
a
LB0: 2.2.2.2/32
u
h
LB0: 1.1.1.1/32
LB1: 2.0.0.1/32
.
g
n
GE1/0/0
GE1/0/0 i
RTA
RTB
n
10.0.0.1/30
10.0.0.2/30
r
a
e
GE1/0/1
l
GE1/0/1
Area 0
192.168.2.1/24
/
192.168.3.1/24
/
:
p
LB0: 3.3.3.3/32
t
t
h
:
[RTB]ip route-static
0.0.0.0 0.0.0.0 10.0.0.10
RTC
s
e
[RTB]ospf
c
GE1/0/1
r
[RTB-ospf-1]import-route
direct
u
192.168.3.1/24
o
[RTB-ospf-1]area
0
s
2.2.2.2 0.0.0.0
Re[RTB-ospf-1-area-0.0.0.0]network
[RTB-ospf-1-area-0.0.0.0]network 10.0.0.0 0.0.0.3
g
n
i
n
r
a
e
L
r
Copyright
Page 65
o
n
e
/
Configuring OSPF Default Route .
i
m
o
c
e
w
a
LB0: 2.2.2.2/32
u
h
LB0: 1.1.1.1/32
LB1: 2.0.0.1/32
.
g
n
GE1/0/0
GE1/0/0 i
RTA
RTB
n
10.0.0.1/30
10.0.0.2/30
r
a
e
GE1/0/1
l
GE1/0/1
Area 0
192.168.2.1/24
/
192.168.3.1/24
/
:
p
LB0: 3.3.3.3/32
t
t
h
:
[RTB]ip route-static
0.0.0.0 0.0.0.0 10.0.0.10
RTC
s
e
[RTB]ospf
c
GE1/0/1
r
[RTB-ospf-1]default-route-advertise
u
192.168.3.1/24
o
[RTB-ospf-1]area
0
s
2.2.2.2 0.0.0.0
Re[RTB-ospf-1-area-0.0.0.0]network
g
n
i
n
r
a
e
L
r
Copyright
Page 67
o
n
e
/
Configuration Verification: OSPF
m
o
c
.
i
Neighbor
e
w
.
g
n
i
n
a
u
h
<RTA>display ospf peer brief
Peer Statistic Informations
------------------------------------------------------------------Area Id
Interface
Neighbor id
State
0.0.0.0
GigabitEthernet1/0/0
2.2.2.2
Full
0.0.0.1
3.3.3.3
Full
-------------------------------------------------------------------
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
<RTB>display ospf peer brief
------------------------------------------------------------------Area Id
Interface
Neighbor id State
0.0.0.0
GigabitEthernet1/0/0 1.1.1.1
Full
-------------------------------------------------------------------
u
o
s
n
r
a
e
r
o
g
n
i
Re
<RTC>display ospf peer brief
------------------------------------------------------------------Area Id
Interface
Neighbor id
State
0.0.0.1
GigabitEthernet1/0/2 1.1.1.1
Full
-------------------------------------------------------------------
Le
Page 69
n
e
/
Configuration Verification: Routing om
c
.
i
Table (1)
e
w
<RTA>display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 17
Routes : 17
.
g
n
i
n
e
r
o
a
u
h
r
a
e
Destination/Mask Proto Pre Cost
Flags NextHop
Interface
l
/
:/ GigabitEthernet1/0/0
0.0.0.0/0 O_ASE 150 1
D p
10.0.0.2
t
1.0.0.1/32 Direct 0 0
D 127.0.0.1
InLoopBack0
t
1.1.1.1/32 Direct 0 0
Dh 127.0.0.1
InLoopBack0
2.0.0.1/32 O_ASE 150 1 :
D 10.0.0.2
s
2.2.2.2/32 OSPF 10 e
1
D 10.0.0.2
3.3.3.3/32 OSPF 10c1
D 10.0.0.6
r
......
u
o
127.0.0.0/8 Direct
0 0
D 127.0.0.1
InLoopBack0
s
e
127.0.0.1/32RDirect 0 0
D 127.0.0.1
InLoopBack0
192.168.1.0/24 Direct 0 0
D 192.168.1.1 GigabitEthernet1/0/1
g
192.168.1.1/32
Direct 0 0
D 127.0.0.1
InLoopBack0
n
i
192.168.2.0/24
OSPF 10 2
D 10.0.0.2
n
r
192.168.3.0/24 OSPF 10 2
D 10.0.0.6
a
Le
Page 70
n
e
/
c
.
i
Table (2)
e
w
<RTB>display ip routing-table
Destinations : 17
Routes : 17
.
g
n
i
n
e
r
o
a
u
h
r
a
e Interface
Flags NextHop
l
/
/
:
0.0.0.0/0 Static 60 0
RD 10.0.0.10
p
1.1.1.1/32 OSPF 10 1
D t
10.0.0.1
t
2.0.0.1/32 Direct 0 0
D h127.0.0.1
InLoopBack0
2.2.2.2/32 Direct 0 0
D 127.0.0.1
InLoopBack0
:
s
3.3.3.3/32 OSPF 10 2e
D 10.0.0.1
c
......
r
10.0.0.4/30 OSPF u10 2
D 10.0.0.1
o
......
s0 0
e
127.0.0.0/8 Direct
D 127.0.0.1
InLoopBack0
R
127.0.0.1/32 Direct 0 0
D 127.0.0.1
InLoopBack0
g
192.168.1.0/24
OSPF 10 2
D 10.0.0.1
n
i
192.168.2.0/24
Direct 0 0
n
r
192.168.2.1/32 Direct 0 0
D 127.0.0.1
InLoopBack0
a
D 10.0.0.1
Le192.168.3.0/24 OSPF 10 3
Page 71
n
e
/
c
.
i
Table (3)
e
w
<RTC>display ip routing-table
Destinations : 17
Routes : 17
.
g
n
i
n
e
r
o
a
u
h
r
a
e
l
Flags NextHop
Interface
/
/
:
0.0.0.0/0 O_ASE 150 1
D 10.0.0.5
p
t
1.1.1.1/32 OSPF 10 1
Dt 10.0.0.5
h D 10.0.0.5 GigabitEthernet1/0/2
2.0.0.1/32 O_ASE 150 1
2.2.2.2/32 OSPF 10 2 : D 10.0.0.5
s
......
e2
c
10.0.0.0/30 OSPF 10
D 10.0.0.5
r
u
......
o
127.0.0.0/8 Direct
D 127.0.0.1
InLoopBack0
s 0 0
e
127.0.0.1/32RDirect 0 0
D 127.0.0.1
InLoopBack0
192.168.1.0/24
OSPF 10 2
D 10.0.0.5
g
n OSPF 10 3
192.168.2.0/24
D 10.0.0.5
i
192.168.3.0/24
Direct 0 0
n
r
192.168.3.1/32
Direct 0 0
D 127.0.0.1
InLoopBack0
a
e
L
Page 72
n
e
/
Configuring an OSPF Stub Area
.
i
e
m
o
c
w
a
LB0: 2.2.2.2/32
u
h
LB0: 1.1.1.1/32
LB1: 2.0.0.1/32
.
g
GE1/0/0
GE1/0/0 in
RTA
RTB
n
10.0.0.1/30
10.0.0.2/30
r
a
e
GE1/0/1
l
GE1/0/1
Area 0
192.168.2.1/24
/
192.168.3.1/24
/
:
p
LB0: 3.3.3.3/32
t
t
h
:[RTA]ospf
RTC
s
e [RTA-ospf-1]area 1
c
GE1/0/1
r [RTA-ospf-1-area-0.0.0.1]stub
u
192.168.3.1/24
o
s
Re
g
[RTC]ospf
n
i [RTC-ospf-1]area 1
n
r [RTC-ospf-1-area-0.0.0.1]stub
a
Le
r
Copyright
Page 73
o
m
o
c
Configuration Verification: Stub Area
.
i
e
w
a
u
[RTC]display ip routing-table
h
.
g
------------------------------------------------------------------------------ n
i
Routing Tables: Public
n
r
Destinations : 15
Routes : 15
a
e
l
Flags NextHop
Interface
/
/
:
p
0.0.0.0/0 OSPF 10 2
D 10.0.0.5
t
1.1.1.1/32 OSPF 10 1
Dt 10.0.0.5
h
2.2.2.2/32 OSPF 10 2
D 10.0.0.5
:
3.0.0.1/32 Direct 0 0 s D 127.0.0.1
InLoopBack0
e
3.3.3.3/32 Direct 0 0c
D 127.0.0.1
InLoopBack0
r 2
10.0.0.0/30 OSPF 10
D 10.0.0.5
u
......
so 10 2
192.168.1.0/24 e
OSPF
D 10.0.0.5
R OSPF 10 3
192.168.2.0/24
D 10.0.0.5
g Direct 0 0
192.168.3.0/24
n
192.168.3.1/32
Direct 0 0
D 127.0.0.1
InLoopBack0
i
n
r
a
Le
r
Copyright
Page 74
o
n
e
/
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. OSPF Overview
n
i
n
r
a
le
/
/
p:
t
t
h
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 75
n
e
/
Small- and Medium-Sized Enterpriseom
c
.
i
Network
e
w
.
g
n
i
n
a
u
h
r
a
le
OSPF
Area 0
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 76
Internet
n
e
/
m
o
c
Large Enterprise Network
.
i
e
w
a
u
h
.
g
n
i
Area 6 n
r
a
le
Area 5
Area 4
/
/
p:
Extranet
Intranet
t
t
h
Area 0
:
s
e
c
r
Re
Area 1
n
r
a
e
r
o
g
n
i
u
o
s
Area 2
Area 3
Le
Page 77
n
e
/
m
o
c
Summary
.
i
e
w
a
u
h
.
g

OSPF Router ID

OSPF Area

OSPF Neighbor Adjacency

OSPF Packets

OSPF Network Types

OSPF LSA Types
n
i
n
:
s
e
c
r
r
a
le
/
/
p:
t
t
h
u
o
s
e
R
 OSPF Special Area
g
n
i
n
r
a
Le
r
Copyright
o
Page 78
n
e
/
m
o
c
Thank you
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank you
//
:
www.huawei.com
tp
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
ht
n
e
/
m
o
c
.
i
e
BGP Feature and
Configuration
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
g
n
i
Re
e
L
e
r
o
www.huawei.com
n
e
/
Preface
.
i
e
m
o
c
w
a
udivided into
 As network sizes keep increasing, a network is
h
.
g
n (ASs).
multiple interconnected autonomous systems
i
n
r
Uniquely identified by an AS number,eaan AS is an
l
/
internetwork under the control of:/one administrative entity.
p
t
The administrative entity selects
ht an interior gateway
: open shortest path first (OSPF)
protocol (IGP), for example,
s
e
c
r
and intermediate system-to-intermediate
system (IS-IS),
u
o
s
within each AS.
ReRouting information is shared between ASs
gexterior gateway protocol (EGP). In this way,
n
by using an
i
n
r
interconnection
is achieved on the entire internetwork.
a
e
L
r
Copyright
Page 2
o
n
e
/
Objectives
.
i
e
w
a
uto:
h
.
g
n
Describe BGP basic concepts
i
n
r
Describe BGP working principles lea
/
/
: of BGP
Describe the route selection process
p
t
t
Configure BGP protocol h
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 3
o




m
o
c
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. BGP Overview
n
i
n
2. BGP Route Transfer Process
3. BGP Path Control and Selection
r
a
le
/
/
p:
t
t
h
4. BGP Configuration
Networks
5. BGP Applications on Enterprise
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 4
Basic Characteristics of BGP
n
e
/
.
i
e
m
o
c
w
a
BGP is an EGP. Different from IGPs, for example, OSPF and routing
information
u
h route
.
protocol (RIP), BGP focuses on route propagation control and
optimal
g
n
selection, instead of route discovery and calculation. ni
r
a
BGP uses transport control protocol (TCP) as the transport
layer protocol (using
e
l
/
port 179) to improve protocol reliability.
/
:
p
BGP supports classless inter-domain routing
t (CIDR).
t
h
During routing updates, BGP sends only incremental routes. This greatly reduces
:
s
the bandwidths occupied wheneBGP advertises routes. Therefore, BGP is suitable
c
r
for advertising a great dealuof routing information on the Internet.
o
s
As a distance-vector e
Rrouting protocol, BGP is designed to prevent routing loops.
g routing policies for flexible rout filtering and selection.
BGP provides n
diverse
i
n
r
a
Le
r
Copyright
Page 5
o






n
e
/
m
o
c
Basic Concepts of BGP

w
a
u
h
.
g
AS (Autonomous System)

.
i
e
n under the
An AS is a connected group of routers thatiare
n
r
a routing policy. Each
control of an entity and adhere to a single
e
l
/
AS is uniquely identified by an AS/number assigned by the
:
p
t
Internet assigned numbers authority
(IANA).
t
h
AS65000
:
s
AS65001
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
BGP
ISIS
OSPF
e
r
o
Page 6
n
e
/
m
o
Self-Test Questions About BGP Overview
c
.
i
e
w
a
u
1. The range of public AS IDs is ( ) and that of private
AS
h
.
g
n
IDs is ( ).
i
n
r
a
A. 1-65535
e
l
/
/
:
B. 1-64511
p
t
t
h
C. 64512-65535
:
s
e
c
D. 0-65535
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 7
o
n
e
/
m
o
Self-Test Questions About BGP Overview
c
.
i
e
w
a
u ( )
2. Which of the following statements about BGP are true?
h
.
g
n routes in an AS.
A. BGP is a routing protocol that discovers dynamic
i
n
r
Its basic function is to exchange routing information
without loops
a
e
l
/
in an AS.
/
:
p
t
B. BGP carries AS path information
ht to resolve the route loop
:
problem.
s
e
c
rclassless inter-domain routing (CIDR).
C. BGP does not support
u
o
s
D. When routes are
Reupdated, BGP sends only incremental routes,
g the occupied bandwidth when BGP transfers
n
greatly reducing
i
n
r
routes.aTherefore,
BGP can transmit large amount of routing
e
L
information
over the Internet.
e
Copyright
Page 8
or ©2012 Huawei Technologies Co., Ltd. All rights reserved.
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. BGP Overview
n
i
n
r
a
le
/
/
p:
t
t
h
Networks
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 9
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
nProcess
i
2.1 Overview of the BGP Route Transfer
n
2.2 BGP Protocol Packets
r
a
le
/
/
:
p
2.3 Neighbor Relationship Establishment
t
t
h
:
2.4 Route Redistribution
s
e
c
r
2.5 BGP Route Advertisement
Principles
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 10
o
n
e
/
Overview of the BGP Route Transfer om
c
.
Process
ei
w
a
u
Step
Description
n
i
n
r
a
le BGP.
IGP routes are imported /into
/
:
p between BGP neighbors
Routes are transferred
t
according to the
ht BGP route advertisement
:
principles.
s
e
c
r
u
o
s
Re
g
n
i
n
r
1
BGP neighbor relationships are established.
2
3
e
r
o
h
.
g
a
e
L
Page 11
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
nProcess
i
n
r
a
le
/
/
:
p
t
t
h
:
s
e
c
r
Principles
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 12
o
n
e
/
m
o
c
BGP Protocol Packets
Keepalive
Message
Update
Message
Notification
Message
n
r
a
e
r
o
g
n
i
w
a
u
h
.
g
Message
Open Message
.
i
e
Description
n
i
n
As the first message sent after the
establishment of a TCP connection.
r
a
e
l
BGP routers periodically
send the
/
/ that is used to
Keepalive message
:
p of a connection.
check the validity
t
t
h
The Update message is used to
exchanges:routing information between
e
c
BGP peers.
r
u
o a BGP router detects an error,
When
s
Reit sends a Notification message to
its peer.
Le
Page 13
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
nProcess
i
n
r
a
le
/
/
:
p
t
t
h
:
s
e
c
r
Principles
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 14
o
n
e
/
State Machine of Neighbor
Relationship Establishment
m
o
c
.
i
e
w
a
u
Connect-retry
timer expired
h Connect-retry
.
g timer expired
TCP connection fails
Active
TCP connection setup
Correct Open
message received
g
n
i
n
r
a
e
r
o
r
a
le
/
others
/
:
TCP connection setup
p
t
t
h Error
:
s
e
Error
c
r
u
Open-sent
Keepalive timer
expired
n
i
n
Connect
o
s
e
R
Open-confirm
Keepalive message
received
Le
others
BGP start
Idle
Error
Established
1. Keepalive timer expired
2. Keepalive received
3. Update received
Page 15
Neighbor Relationship Types
n
e
/
m
o
c
.
i
e
w
a
u(EBGP)
 BGP neighbor relationship types: External BGP
h
.
g
n
neighbor and Internal BGP (IBGP) neighbor.
i
n
AS 300
AS 100
r
Loopback0
[RTE]bgp 300
a
e
5.5.5.5
[RTE-bgp]peer 20.0.0.1 as-number
200
l
RTA
/
/
RTE
:
p
20.0.0.2
t
t
ASh200
Loopback0 :
Loopback0
20.0.0.1
2.2.2.2 s
e
4.4.4.4
RTB
RTD
c
r
u
o
11.0.0.1
22.0.0.1
s
e
22.0.0.2
R 11.0.0.2
g
RTC
n
i
n [RTD]bgp 200
r
a
[RTD-bgp]peer 2.2.2.2 as-number 200
e
L
r
Copyright
Page 17
o
EBGP
EBGP
IBGP
n
e
/
Specified Update Source and EBGP Multim
o
c
.
Hop
i
e
w
AS 100
RTA
/
/
p: 21.0.0.1
AS 200
RTB
n
r
a
Le
g
n
i
Loopback0
2.2.2.2
.
g
n
i
n
r
a
le
[RTE]ip route-static 4.4.4.4 32 20.0.0.1
EBGP
e
r
o
a
u
h
[RTE]bgp 300
[RTE-bgp]peer 4.4.4.4 as-number 200
[RTE-bgp]peer 4.4.4.4 connect-interface loopback 0
[RTE-bgp]peer 4.4.4.4 ebgp-max-hop 2
tLoopback0
t
h 4.4.4.4
:
s
e
11.0.0.1 c
22.0.0.1
r
u11.0.0.2
22.0.0.2
o
s
RTC
Re
IBGP
Loopback0
5.5.5.5
21.0.0.2
RTE
20.0.0.2
EBGP
20.0.0.1
RTD
[RTD]bgp 200
[RTD-bgp]peer 2.2.2.2 connect-interface loopback 0
AS 300
Page 18
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
nProcess
i
n
r
a
le
/
/
:
p
t
t
h
:
s
e
c
r
Principles
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 19
o
n
e
/
m
o
c
Route Redistribution-Network(1/2)
.
i
e
w
a
u
h
.
g
n
AS200
i
n
r
RT3 AS100
a
18.0.0.1/32
e
l
18.0.0.2/32
/
/
OSPF
:
p
t
t
RT2
h
RT1
:
s
e
c
r
The routing information discovered
by
u
o Imported into
IGP (for example OSPF)sis
e by using the
the BGP routing table
R
“network” command.
g the subnet mask
n
Need to configure
i
n
precisely.
r
a
Le
r
Copyright
Page 20
o


[RT2]display ip routing-table
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/30
Direct
0 NextHop
10.1.1.2 Interface
Serial0
Destination/Mask
Proto
Pre0 Cost
10.1.1.2/32
Direct
0
0
127.0.0.1
InLoopBack0
10.1.1.0/30
Direct 0
0
10.1.1.2
Serial0
10.2.2.0/30
Direct
10.2.2.1
Serial1
10.1.1.2/32
Direct
0 0 0 0 127.0.0.1
InLoopBack0
10.2.2.1/32
Direct
127.0.0.1
InLoopBack0
10.2.2.0/30
Direct
0 0 0 0 10.2.2.1
Serial1
18.0.0.1/32
OSPF
10
1563
10.1.1.1
Serial0
10.2.2.1/32
Direct 0
0
127.0.0.1 InLoopBack0
18.0.0.2/32
OSPF
10
1563
10.1.1.1
Serial0
18.0.0.1/32
OSPF 10 1563 10.1.1.1
Serial0
[RT2]display bgpOSPF
routing-table
18.0.0.2/32
10 1563 10.1.1.1
Serial0
….empty……
[RT2]bgp 200
200
[RT2]bgp
[RT2-bgp]network
18.0.0.1
255.255.255.255
[RT2-bgp]network 18.0.0.1
255.255.255.255
[RT2-bgp]network18.0.0.2
18.0.0.2
255.255.255.255
[RT2-bgp]network
255.255.255.255
n
e
/
m
o
c
Route Redistribution-Network(2/2)
.
i
e
w
a
u
h
.
g
n
[RT2]display bgp routing-table
i
n
r
a
Total Number of Routes: 2
e
l
/
BGP Local router ID is 1.1.1.1
/
:
Status codes: * - valid, > - best, d - damped,
p s - suppressed, S - Stale
h - history, i - internal,
t
t ? - incomplete
Origin : i - IGP, e - h
EGP,
Network
NextHop :
MED
LocPrf
PrefVal Path/Ogn
s
e
*>i 18.0.0.1
0.0.0.0
1
0
i
c
r
*>i 18.0.0.1
0.0.0.0
1
0
i
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 21
o
n
e
/
m
Route Redistribution-Import
o
c
.
i
Route(1/2)
e
aw
u
h
.
AS200
RT3
18.0.0.1/32
18.0.0.2/32
OSPF
RT1
RT2
u
o
s
:
s
e
c
r
The IGP route or static
e route is
R
imported into thegBGP routing
n
table of RT2 nbyi using importroute command.
ar

e
r
o
Le
g
n
AS100
i
n
r
a
e
l
/
/
: ipiprouting-table
[RT2]display
routing-table
[RT2]display
p
t
t
Destination/Mask
Proto Pre Cost NextHop Interface
hDestination/Mask
Proto
Pre Cost
NextHop
Interface
10.1.1.0/30
Direct 0
0
10.1.1.2
Serial0
10.1.1.0/30
10.1.1.2/32
10.1.1.2/32
InLoopBack0
10.2.2.0/30
10.2.2.0/30
10.2.2.1/32
10.2.2.1/32
18.0.0.1/32
InLoopBack0
18.0.0.2/32
18.0.0.1/32
Direct
0 0 0 0 10.1.1.2
Serial0
Direct
127.0.0.1
Direct 0 0
127.0.0.1 InLoopBack0
Direct
0 0 0 0 10.2.2.1
Direct
10.2.2.1Serial1Serial1
Direct
0 0 0 0 127.0.0.1
InLoopBack0
Direct
127.0.0.1
OSPF 10 1563 10.1.1.1
Serial0
OSPF
10 101563
10.1.1.1
OSPF
1563
10.1.1.1 Serial0Serial0
18.0.0.2/32
OSPF 10 1563
[RT2]display
[RT2]bgp
200 bgp routing-table
….empty……
[RT2-bgp]import-route ospf
[RT2]bgp 200
[RT2-bgp]import-route ospf
Page 22
10.1.1.1
Serial0
n
e
/
m
Route Redistribution-Import
o
c
.
i
Route(2/2)
e
aw
u
h
.
g
n
ni
r
a
le
/
/
p:
t
t
h
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Network
:
s
e
c
NextHop
r
u
o
3.3.3.3
s
e 3.3.3.3
*>i
*>i
*>i
*>i
1.1.1.1/32
3.3.3.3/32
20.1.1.0/30
33.33.33.33/32
e
r
o
ng
i
n
r
R
3.3.3.3
3.3.3.3
MED
LocPrf
0
0
0
0
100
100
100
100
a
e
L
Page 23
PrefVal Path/Ogn
0
0
0
0
?
?
?
?
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
nProcess
i
n
r
a
le
/
/
:
p
t
t
h
:
s
e
c
r
Principles
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 24
o
Advertisement Principle 1
n
e
/
m
o
c
.
i
e
w
a
u (route
 BGP advertises only the routes that are the best
h
.
g
n
entries preceded by the > mark) and validi(route
entries
n
r
a routing table.
preceded by the * mark) in the local BGP
e
l
[Quidway]display bgp routing-table
/
/
:
p
t
td - damped,
Status codes: * - valid, > - best,
h
h - history, i -: internal, s - suppressed, S - Stale
s e - EGP, ? - incomplete
Origin : i - IGP,
e
c
Network
NextHop
MED
LocPrf
PrefVal
r
Path/Ogn
u
o
i 3.3.3.3/32
0
100
0
s 3.3.3.3
e
*>i 18.0.0.1/32
3.3.3.3
0
100
0
R
*>i 18.0.0.2/32 g
3.3.3.3
0
100
0
n
*>i 20.1.1.0/30
3.3.3.3
0
100
0
i
n
*>i 33.33.33.33/32
3.3.3.3
0
100
0
r
a
*
20.1.1.2
0
100
0
e
L
r
Copyright
Page 25
o
?
?
?
?
?
?
n
e
/
m
o
Advertisement Principle 2(1/9) i.c
e
w
a
u
 Locally originated routes are the best and valid.
Therefore,
h
.
g
n
these routes are advertised to neighbor routers,
including
i
n
r
iBGP neighbors and eBGP routers. ea
l AS200
/
/
:
p
Loopback1:18.0.0.1/32
OSPF
t
Loopback2:18.0.0.2/32
ht
20.1.1.2/30
RT2
:
20.1.1.1/30
s
Loopback3: 33.33.33.33/32
e
Loopback0: 1.1.1.1/32
c
r21.1.1.1/30
u
o
RT1
s
Loopback0: 3.3.3.3/32
Re
21.1.1.2/30
g
n
i
AS100
n
r
RT3
a
Loopback0: 2.2.2.2/32
Le
r
Copyright
Page 26
o
IBGP
EBGP
n
e
/
m
o
e
w
a
u
 IP routing table of RT1:
h
.
g
n
i
n
-----------------------------------------------------------------------------r
a
e
l
Destinations : 9
Routes : 9
/ NextHop
/
Destination/Mask
Proto Pre Cost
Flags
Interface
:
1.1.1.1/32 OSPF
10
1
D
20.1.1.2
Ethernet0/0/0
p
t
3.3.3.3/32 Direct 0
0
D
127.0.0.1
InLoopBack0
t
h
18.0.0.1/32 Direct 0
0
D
127.0.0.1
InLoopBack0
18.0.0.2/32 Direct 0
0 :
D
127.0.0.1
InLoopBack0
s
20.1.1.0/30 Direct 0
0
D
20.1.1.1
Ethernet0/0/0
e
c
20.1.1.1/32 Direct 0 r 0
D
127.0.0.1
InLoopBack0
u 0
21.1.1.0/30 Direct 0
D
21.1.1.1
Ethernet0/0/1
o
21.1.1.1/32 Direct
D
127.0.0.1
InLoopBack0
s0 0
e
33.33.33.33/32 Direct
0
0
D
127.0.0.1
InLoopBack0
R
127.0.0.0/8 gDirect 0
0
D
127.0.0.1
InLoopBack0
127.0.0.1/32n Direct 0
0
D
127.0.0.1
InLoopBack0
i
n
r
a
e
L
r
Copyright
Page 27
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
-----------------------------------------------------------------------------e
l
/
Destinations : 9
Routes : 9 /
:Flags NextHop
Destination/Mask
Proto Pre Cost
Interface
p
t
1.1.1.1/32 Direct 0
0
D
127.0.0.1
InLoopBack0
t
h
3.3.3.3/32 OSPF
10
1
D
20.1.1.1
Ethernet0/0/0
20.1.1.0/30 Direct 0
0 :
D
20.1.1.2
Ethernet0/0/0
s
20.1.1.2/32 Direct 0
D
127.0.0.1
InLoopBack0
e0
c
33.33.33.33/32 OSPF
10r 1
D
20.1.1.1
Ethernet0/0/0
u
127.0.0.0/8
Directo0
0
D
127.0.0.1
InLoopBack0
s0 0
127.0.0.1/32 Direct
D
127.0.0.1
InLoopBack0
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 28
o
n
e
/
m
Advertisement Principle 2(4/9)-Import
o
c
.
Direct Route
ei
w
a
u
AS200
Loopback1:18.0.0.1/32
Loopback2:18.0.0.2/32
OSPF
n
i
n
h
.
g
r
a
20.1.1.2/30e
l
RT2
20.1.1.1/30
/
/ Loopback0: 1.1.1.1/32
Loopback3: 33.33.33.33/32
:
p
21.1.1.1/30
t
RT1 ht
Loopback0:
: 3.3.3.3/32
21.1.1.2/30
s
e
c
AS100our
RT3
s
e
R
Loopback0: 2.2.2.2/32
g
[RT1]bgp 200
n
i
[RT1-bgp]import-route direct
n
r
a
Le
r
Copyright
Page 29
o
IBGP
EBGP
n
e
/
m
o
e
w
a
u
 BGP routing table of RT1:
h
.
g
n
i
n
r
a
e
l
/
h - history, i - internal, s/ - suppressed, S - Stale
:
Origin : i - IGP, e - EGP,p? - incomplete
tMED
Network
NextHop
LocPrf
PrefVal Path/Ogn
t
h
*>
3.3.3.3/32
0.0.0.0
0
0
?
*>
18.0.0.1/32
0.0.0.0 :
0
0
?
s
*>
18.0.0.2/32
0.0.0.0
0
0
?
e
c
*>
20.1.1.0/30
0.0.0.0
0
0
?
r
u
*>
20.1.1.1/32
0.0.0.0
0
0
?
o
s0.0.0.0
*>
21.1.1.0/30
0
0
?
e
*>
21.1.1.1/32
0.0.0.0
0
0
?
R
*>
33.33.33.33/32
0.0.0.0
0
0
?
g
*>
127.0.0.0 in
0.0.0.0
0
0
?
n
*>
127.0.0.1/32
0.0.0.0
0
0
?
r
a
e
L
r
Copyright
Page 30
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
/
h - history, i - internal, :s - suppressed, S - Stale
p? - incomplete
Origin : i - IGP, e - EGP,
t
t MED
Network
NextHop
LocPrf
PrefVal Path/Ogn
h
i 3.3.3.3/32
3.3.3.3 :
0
100
0
?
s
*>i 18.0.0.1/32
3.3.3.3
0
100
0
?
e
*>i 18.0.0.2/32
3.3.3.3
0
100
0
?
c
r
*>i 20.1.1.0/30
3.3.3.3
0
100
0
?
u
o
*>i 21.1.1.0/30
3.3.3.3
0
100
0
?
s
e
*>i 33.33.33.33/32
0
100
0
?
R 3.3.3.3
g
n
i
n
r
a
Le
r
Copyright
Page 31
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
-----------------------------------------------------------------------------r
a
e
Destinations : 11
Routes : 11 /l
/ NextHop
Destination/Mask
Proto Pre Cost
Flags
Interface
:
1.1.1.1/32 Direct 0
0
D
127.0.0.1
InLoopBack0
p
t
3.3.3.3/32 OSPF
10
1
D
20.1.1.1
Ethernet0/0/0
t
h
10.1.1.0/30 Direct 0
0
D
10.1.1.1
Ethernet0/0/1
10.1.1.1/32 Direct 0
0 :
D
127.0.0.1
InLoopBack0
s
18.0.0.1/32 BGP
255 e0
RD
3.3.3.3
Ethernet0/0/0
c
18.0.0.2/32 BGP
255
0
RD
3.3.3.3
Ethernet0/0/0
r
u 0
20.1.1.0/30 Direct 0
D
20.1.1.2
Ethernet0/0/0
o
20.1.1.2/32 Direct
D
127.0.0.1
InLoopBack0
s0 0
e
21.1.1.0/30 BGP
255 0
RD
3.3.3.3
Ethernet0/0/0
R
33.33.33.33/32 gOSPF
10
1
D
20.1.1.1
Ethernet0/0/0
127.0.0.0/8 n Direct 0
0
D
127.0.0.1
InLoopBack0
i
127.0.0.1/32
D
127.0.0.1
InLoopBack0
n Direct 0 0
r
a
e
L
r
Copyright
Page 32
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
e
Status codes: * - valid, > - best, d - damped,l
/
: - incomplete
Origin : i - IGP, e - EGP,p?
tMED
Network
NextHop
LocPrf
PrefVal Path/Ogn
t
h 0
*>
3.3.3.3/32
21.1.1.1
0
200?
*>
18.0.0.1/32
21.1.1.1 :
0
0
200?
s
*>
18.0.0.2/32
21.1.1.1
0
0
200?
e
c
*>
20.1.1.0/30
21.1.1.1
0
0
200?
r
u
21.1.1.0/30
21.1.1.1
0
0
200?
o
*>
33.33.33.33/32
0
0
200?
s21.1.1.1
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 33
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
-----------------------------------------------------------------------------e
l
/
Destinations : 10
Routes : 10 /
:Flags NextHop
Destination/Mask
Proto Pre Cost
Interface
p
t
2.2.2.2/32 Direct 0
0
D
127.0.0.1
InLoopBack0
t
h
3.3.3.3/32 BGP
255 0
D
21.1.1.1
Ethernet0/0/2
18.0.0.1/32 BGP
255 0 :
D
21.1.1.1
Ethernet0/0/2
s
18.0.0.2/32 BGP
255 e0
D
21.1.1.1
Ethernet0/0/2
c
20.1.1.0/30 BGP
255
0
D
21.1.1.1
Ethernet0/0/2
r
u 0
21.1.1.0/30 Direct 0
D
21.1.1.2
Ethernet0/0/2
o
21.1.1.2/32 Direct
D
127.0.0.1
InLoopBack0
s0 0
e
33.33.33.33/32 BGP
255 0
D
21.1.1.1
Ethernet0/0/2
R
127.0.0.0/8 gDirect 0
0
D
127.0.0.1
InLoopBack0
127.0.0.1/32n Direct 0
0
D
127.0.0.1
InLoopBack0
i
n
r
a
e
L
r
Copyright
Page 34
o
n
e
/
m
o
e
w
The BGP routes received from EBGP peers are advertisedua
to all the BGP
h
.
neighbors other than the router from which the routes gare received,
n
i
including IBGP neighbors and EBGP neighbors.rn
a
e
l AS200
/
/
Loopback1:18.0.0.1/32
:
OSPF
p
Loopback2:18.0.0.2/32
t
20.1.1.2/30
t
AS300
h
RT5
Loopback3: 33.33.33.33/32
RT2
20.1.1.1/30
:
40.1.1.2/30
s
IBGP Loopback0: 1.1.1.1/32
e 21.1.1.1/30
c
r EBGP
RT1
EBGP
u
o
Loopback0: 3.3.3.3/32
s
40.1.1.1/30
AS10
e
R
21.1.1.2/30
31.1.1.1/30
0
g
31.1.1.2/30
n
i IBGP RT3
RT4
n
r 4.4.4.4/32 Loopback0: 2.2.2.2/32
Loopback0:
a
Le
r
Copyright
Page 35
o

n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
/
h - history, i - internal, :s - suppressed, S - Stale
p? - incomplete
Origin : i - IGP, e - EGP,
t
t MED
Network
NextHop
LocPrf
PrefVal Path/Ogn
h
*>
3.3.3.3/32
40.1.1.1 :
0
100 200?
*>
18.0.0.1/32
40.1.1.1s
0
100 200?
e
*>
18.0.0.2/32
40.1.1.1
0
100 200?
c
r
*>
20.1.1.0/30
40.1.1.1
0
100 200?
u
o
*>
33.33.33.33/32
40.1.1.1
0
100 200?
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 36
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
e
Status codes: * - valid, > - best, d - damped,l
h - history, i - internal, s//
- suppressed, S - Stale
: - incomplete
Origin : i - IGP, e - EGP,p?
tMED
Network
NextHop
LocPrf
PrefVal Path/Ogn
t
i 3.3.3.3/32
21.1.1.1
100
0
200?
h 0
i 18.0.0.1/32
21.1.1.1 :
0
100
0
200?
s
i 18.0.0.2/32
21.1.1.1
0
100
0
200?
e
c
i 20.1.1.0/30
21.1.1.1
0
100
0
200?
r
i 33.33.33.33/32
21.1.1.1
0
100
0
200?
u
o
s
e
R are all the BGP routes displayed as invalid
 Question: Why
g
n
on RT4?ni
r
a
Le
r
Copyright
Page 37
o
n
e
/
m
Advertisement Principle 3(4/5)-Modify
o
c
.
the Next Hop
ei
w
a
u
AS200
.h
Loopback1:18.0.0.1/32
Loopback2:18.0.0.2/32
g
n
i
nOSPF
r 20.1.1.2/30
a
AS300
RT5
RT2
le
Loopback3: 33.33.33.33/32 /20.1.1.1/30
/
40.1.1.2/30
:
IBGP Loopback0: 1.1.1.1/32
p
t
21.1.1.1/30
t RT1
h
EBGP
EBGP
:
Loopback0: 3.3.3.3/32
s
40.1.1.1/30
e
AS100
c
21.1.1.2/30
31.1.1.1/30ur
31.1.1.2/30so
e
IBGP
R
RT3
RT4
Loopback0:
2.2.2.2/32
g
Loopback0: 4.4.4.4/32
n
i
[RT3]bgp 200
n
r
[RT3-bgp] peer 4.4.4.4 next-hop-local
a
e
L
r
Copyright
Page 38
o
n
e
/
m
o
e
w
a
u
h
.
g
n
i
n
r
a
e
l
/
:
tMED
Network
NextHop
LocPrf
PrefVal Path/Ogn
t
h
*>i 3.3.3.3/32
2.2.2.2
0
100
0
200?
*>i 18.0.0.1/32
2.2.2.2 :
0
100
0
200?
s
*>i 18.0.0.2/32
2.2.2.2
0
100
0
200?
e
c
*>i 20.1.1.0/30
2.2.2.2
0
100
0
200?
r
u
*>i 33.33.33.33/32
2.2.2.2
0
100
0
200?
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 39
o
n
e
/
m
o
e
w
anot
u
 A BGP route received from an IBGP neighbor is
h
.
advertised to any IBGP neighbor. AS200 ing
n
r
18.0.0.1/32
a
OSPF
10.1.1.1
e
18.0.0.2/32
l
/ 20.1.1.2/30
/
:
p
RT2
20.1.1.1/30
t
33.33.33.33/32 ht
:
21.1.1.1/30
s
e RT1
c
r
u
o
21.1.1.2/30
s
RT5
Re
AS100
g
n
i RT3
n
RT4
r
a
e
 Question:
How can we let RT5 receive the routes from
L
e
r
Copyright
©2012 Huawei Technologies Co., Ltd. All rights reserved.
Page 40
oRT1?
IBGP
IBGP
EBGP
IBGP
IBGP
n
e
/
Advertisement Principle 4(2/2)-IBGP om
c
.
Full Mesh Structure
ei
w
a
u
AS200
18.0.0.1/32
18.0.0.2/32
n
i
n
r
a
le
OSPF
h
.
g
/
/
:
20.1.1.1/30
p
t IBGP
33.33.33.33/32
t
h
IBGP
21.1.1.1/30 :
s
e RT1
EBGP
c
IBGP
IBGP
r
u
21.1.1.2/30
o
s
e
RAS100
IBGP
g
n
i RT3
RT4
n
r
a
10.1.1.1
20.1.1.2/30
e
r
o
RT2
IBGP
Le
Page 41
RT5
Advertisement Principle 5
n
e
/
.
i
e
m
o
c
w
a
u are
 Whether the routes learnt from an IBGP neighbor
h
.
g
n
advertised to its EBGP peer depends on the
i
n
r
a
synchronization between IGP and BGP.
e
l
/
10.1.1.1/24
/
AS300
:
AS100
p
t
t
RTA
RTF
h
:
1.1.1.1/24
s
e AS200
c
EBGP
EBGP
r
u
1.1.1.2/24
o
IBGP
s
e
RTE
2.2.2.2/32
RTB R
5.5.5.5/32
g
n
i
n
r
RTC
a
RTD
e
L
r
Copyright
Page 42
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
nProcess
i
n
r
a
le
/
/
:
p
t
t
h
:
s
e
c
r
Principles
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 44
o
n
e
/
m
o
c
BGP Route Advertisement

.
i
e
Update messages are sent to exchange routing information
aw
g
n
iwith the same attributes or
An Update message can advertise multiple reachable routes
n
r
a
withdraw multiple unreachable routes.
e
l
An Update message can advertise multiple reachable
/ routes with the same route
/
:route attributes. All the route attributes
attributes. These routes can share a group of
p
tapplicable to all the destinations (expressed
contained in a given Update message are
t
hmessage.
using IP prefixes) carried in the Update
:
s
e multiple unreachable routes. The routes previously
An Update message can withdraw
c
r are clearly defined by means of destinations (expressed
advertised between BGP u
routers
o
s
by IP prefixes).
e
R
An Update message can be used to only withdraw routes. In this case, the Update
g
n
message does
not carry any path attribute or network reachability information. Likewise,
i
n message can be used to only advertise reachable routes. In this case, the
an Update
r
a message does not carry the routes to be withdrawn.
e
Update
L
among peers.




e
r
o
u
h
.
Page 45
n
e
/
Self-Test Questions About BGP Route om
c
.
Transfer Process
ei
w
a
u
1. BGP uses ( ) messages to establish adjacency
h
.
g
n information,
relationships, ( ) messages to transmit routing
i
n
r
a information.
and ( ) messages to withdraw routing
e
l
/
/
A. Open
:
p
t
ht
B. Update
:
s
e
c
C. Keepalive
r
u
o
s
D. Notification
Re
g
n
i
n
r
a
Le
r
Copyright
Page 46
o
n
e
/
c
.
Transfer Process
ei
2. A BGP route can be generated after ( ).
w
a
u
h
.
g
nBGP routing
i
A. A route discovered by IGP is added to the
n
table using Import commands.
r
a
le
/
/
: to the BGP routing
B. A route discovered by IGP is added
p
t
t
h
table using Network commands.
:
s
e is added to the BGP routing
C. A route learned fromrcIBGP
u
o
table.
s
e
R
g from EBGP is added to the BGP routing
D. A route learned
n
i
n
table. ar
Le
r
Copyright
Page 47
o
n
e
/
c
.
Transfer Process
ei
3. BGP route advertisement principles include ( ).
w
a
u
h
. and EBGP
A. Locally originated routes are advertised to IBGPgpeers
peers.
n
i
n
r
a
e
B. BGP advertises only the optimal and reachable
route in the local
l
/
/
:
BGP routing table.
p
t
t
h
C. BGP routes originated from EBGP peers can be advertised to
:
s
e peers and EBGP peers, except the
BGP peers, such as thecIBGP
r
u
originating ends. o
s
e
R
D. A BGP route received
from an IBGP peer cannot be advertised to
g
npeers.
i
other IBGP
n
r
a
E. BGPLepeers are synchronized.
r
Copyright
Page 48
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. BGP Overview
n
i
n
r
a
3. BGP Path Control and Selectionle
/
/
:
p
t
t
h
:
Networks
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 49
o
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n Path
3.1 Impacts of BGP Route Attributes onniBGP
Selection and Control
3.2 BGP Route Aggregation
/
/
p:
r
a
le
t
t
h
3.3 BGP Optimal Route:Selection Process
s
e
c
r
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 50
o
n
e
/
m
o
c
BGP Route Attribute Classification
.
i
e
w
a
 BGP route attributes can be classified into four u
categories:
h
.
g
Well-known mandatory: This attribute can be identifiednby all BGP routers and
i
n
must be carried in an Update message. Routing information
without this
r
a
e
attribute goes wrong.
l
/
/ be identified all the BGP routers
Well-known discretionary: This attribute :
can
p message. This attribute can be
t
but does not need to be carried in an
Update
t
h
selected depending on the actual
conditions.
:
s
e
Optional transitive: This attribute
is transitive among ASs. A BGP router does
c
r A BGP router, however, still receives routes carrying
u
not support this attribute.
o
s
this attribute and
Readvertises these routes to its peers.
g
Optional non-transitive:
If a BGP router does not support this attribute, the
n
i
n the Update messages carrying this attribute without advertising
routerrignores
a
theeroutes carrying this attribute.
L
r
Copyright
Page 51
o




Origin Attribute(1/4)
n
e
/
.
i
e
m
o
c
w
a
u
 This attribute defines how a BGP speaker generates
BGP
h
.
g
routes. It can have the following values. in
n
r
If one routes is selectively converted into BGP ,the
a Origin is IGP.
e
l
By running the network command
/
/
:
p EGP(RFC 904), the Origin is EGP.
If the BGP routes are redistributed from
t
t
h
Routes carrying this attribute are learnt from neither an IGP nor EGP and are
:
s
in unknown states.
e
c
r
By running the importucommand
o
s
 The priorities of
Rethe three values of the Original attribute are
g
n
IGP > EGP
> INCOMPLETE in descending order. These
i
n
r
a
threeevalues
control BGP path selection.
L
r
Copyright
Page 52
o





n
e
/
m
o
c
AS200
18.0.0.1/32
18.0.0.2/32
OSPF
.
i
e
w
a
u
h
.
g
n
i
n
r
a
20.1.1.2/30e
l
/
RT2
20.1.1.1/30
/
:
33.33.33.33/32
p
t
t
h
RT1 :
s
e
c
r
u
o
[RT1]bgp 200 s
[RT1-bgp]import-route
direct
Re
[RT1-bgp]network
33.33.33.33 255.255.255.255
g
n
i
n
r
a
Le
IBGP
e
r
o
Page 54
n
e
/
m
o
c

.
i
e
w
a
u
h
.
g
BGP routing table of RT1:
n
i
n
Network
NextHop
MED
LocPrf
PrefVal Path/Ogn
*>
3.3.3.3/32
0.0.0.0
0
0
?
*>
18.0.0.1/32
0.0.0.0
0
0
?
*>
18.0.0.2/32
0.0.0.0
0
0
?
*>
20.1.1.0/30
0.0.0.0
0
0
?
*>
20.1.1.1/32
0.0.0.0
0
0
?
*>
33.33.33.33/32
0.0.0.0
0
0
i
*
0.0.0.0
0
0
?
*>
127.0.0.0
0.0.0.0
0
0
?
*>
127.0.0.1/32
0.0.0.0
0
0
?
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 55
n
e
/
m
o
c

.
i
e
w
a
u
h
.
g
BGP routing table of RT2:
n
i
n
r
a
le
Network
NextHop
MED
LocPrf
PrefVal Path/Ogn
i 3.3.3.3/32
3.3.3.3
0
100
0
?
*>i 18.0.0.1/32
3.3.3.3
0
100
0
?
*>i 18.0.0.2/32
3.3.3.3
0
100
0
?
*>i 20.1.1.0/30
3.3.3.3
0
100
0
?
*>i 33.33.33.33/32
3.3.3.3
0
100
0
i
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 56
n
e
/
m
o
c
AS_Path Attribute(1/3)
AS400
/
/
p:
u
o
s
e
r
o
Le
Re
AS200
t
t
h
18.0.0.0/8
AS_PATH (400 300 200)
n
r
a
n
i
n
r
a
le
RTA
:
s
e
c
r
w
a
u
h
.
g
18.0.0.0/8
AS300
g
n
i
.
i
e
AS500
18.0.0.0/8
AS_PATH (500 200)
AS 100
18.0.0.0/8
AS_PATH (500 200)
Page 57
n
e
/
m
o
c
AS_Path Attribute(2/3)
.
i
e
w
a
u
h
Will RTA accept this route?
.
g
n
i
n
r
a
le
RTA
AS 213
10.0.0.0/8
n
r
a
e
r
o
ou
s
e
R
g
n
i RTB
:
s
e
c
r
10.0.0.0/8
/
/
AS_PATH(387
: 213)
p
t
t
h
AS 387
RTC
10.0.0.0/8
AS_PATH (213)
Le
Page 58
n
e
/
m
AS_Path Attribute(3/3)-Plan
o
c
.
i
AS_Path
e
aw
g
n
ni
10.0.0.0/8
AS_PATH (123)
RTC
RTD
r
a
le
10.0.0.0/8
2 Mbps
:
s
e
c
r
t
t
h
2 Mbps
/
/
p:
2 Mbps
AS 123
u
h
.
AS 462
10.0.0.0/8
AS_PATH (462 123)
u
o
s
10.0.0.0/8
n
r
a
e
r
o
Le
g
n
i
Re
RTA
10.0.0.0/8
AS_PATH (123 123 123)
AS 387
RTB
Page 59
n
e
/
m
o
c
Next Hop Attribute(1/3)

.
i
e
w are
a
Normally, the following Next Hop attribute principles
u
observed:



e
r
o
h
.
g
n
i
n
When advertising a route to EBGP peers,
ar a BGP speaker sets
e
l
the next hop of the route to the IP address
of the interface
/
/
p: peer end.
interconnecting the local end t
and
t
h
When advertising a locally
: originated route to IBGP peers, a
s
enext hop of the route to the IP address
BGP speaker sets the
c
r
u
o that originated the route.
of the router interface
s
Re
When advertising
a route learnt from an EBGP peer to IBGP
g
n
i BGP speaker does not change the Next Hop attribute
n
peers,
a
r
a
of
Lethe route.
Page 60
n
e
/
m
o
c
.
i
e
w
a
u
h
.
g
D=8.0.0.0
Next_Hop=1.1.1.1
D=8.0.0.0
Next_Hop=1.1.3.1
n
i
n
AS200
EBGP 1.1.1.1/24
1.1.2.1/24
RTA
1.1.4.2/24
r IBGP
a
le
/
/
p:
AS100
EBGP
D=8.0.0.0
Next_Hop=1.1.2.1
u
o
s
:
s
e
c
r
rn
e
r
o
a
e
L
g
n
i
Re
RTE
t
t
h
RTB
1.1.3.1/24
8.0.0.0
RTC
IBGP
D=8.0.0.0
Next_Hop=1.1.2.1
RTF
AS300
Page 61
n
e
/
m
o
c

.
i
e
w
a
u
h
.
g
The BGP route 8.0.0.0 of RTA:
n
i
n
r
a
le
<RTA> display bgp routing-table 8.0.0.0
BGP local router ID : 1.1.4.1
Local AS number : 100
Paths:
1 available, 1 best
BGP routing table entry information of 8.0.0.0/8:
From: 1.1.3.1 (8.1.1.1)
Relay Nexthop: 1.1.4.2
Original nexthop: 1.1.3.1
AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal,
best, pre 255
Not advertised to any peer yet
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 62
MED Attribute and Local_Pref
Attribute(1/2)
n
e
/
.
i
e
m
o
c
w
a
u for
 MED attribute: is used to decide the optimal route
h
.
g
n
forwarding traffic into an AS.
i
n
r
athe best route for
 Local_Pref attribute: is used to decide
e
l
/
forwarding traffic out of an AS. :/
p
t
Attribute Application Valueht
Impact on Traffic
Scope
:
s
MED
Between
two e
The smaller Affects the inbound traffic
c
neighboringr the value, to the AS for which this
u the better attribute is set.
o
ASs
s
e
Local_Pref Within
R an AS The larger Affects the outbound traffic
g
the value, from the AS for which this
n
i
the better. attribute is set.
n
r
a
Le
r
Copyright
Page 63
o
n
e
/
MED Attribute and Local_Pref
Attribute(2/2)
/
/
p:
RouterA
8.0.0.0
e
r
o
s:
w
a
u
n
i
n
r
a
le
RouterB
4.1.1.1
IBGP
Local_Pref=100
2.1.1.1
EBGP
.
i
e
h
.
g
MED=0
> D=9.0.0.0
Next_Hop=2.1.1.1
MED=0
m
o
c
D=8.0.0.0
Next_Hop=4.1.1.1
Local_Pref=100
t
t
h
9.0.0.0
RouterD
Local_Pref=200
e
EBGPc
D=9.0.0.0
> D=8.0.0.0
IBGP
r
Next_Hop=3.1.1.1
u
Next_Hop=5.1.1.1
o
MED=100
Local_Pref=200
5.1.1.1
s 3.1.1.1
AS10
e
R
MED=100 RouterC
AS20
g
n
i
n
r
a
Le
Page 64
Community Attribute(1/2)
n
e
/
.
i
e
m
o
c
w
a
The community attribute is used to simplify routing policy application
and
u
h
.is a group of
g
maintenance & management. The Community attribute
n
i
n but no physical
destination addresses that have the same features
r
eaaddresses belong. These
boundary, independent of the ASs to which lthe
/
/
destination addresses share one or more
common
attributes.
:
p
t
A Community attribute is represented
ht by a list in the unit of four bytes.:
:
On VRP 5, the format of a Community
attribute is aa:nn, where aa and nn
s
e
cadministrator can set the values based on the
range from 1 to 65536. An
r
u aa indicates the AS number and nn indicates the
o
actual conditions. Generally,
s
e
R identifier defined by an administrator. For example, if the
Community attribute
gdefines the Community attribute identifier as 1, the Community
administrator
n
i
n
attribute
of a route from AS 100 is 100:1.
r
a
e
L
r
Copyright
Page 65
o



n
e
/
m
o
c
Community Attribute(2/2)

.
i
e
w
The following table describes the acknowledged aCommunity
u
h
.
attributes in BGP:
Community
Name
Internet
No_Export
No_Advertise
n
r
a
No_Export_
Le
Subconfed
e
r
o
Community
Identifier
Remarks
g
n
ni
r
a
0
By default, all routes
belong to the Internet
e
l
community.
Routes
with
this
attribute
can
be
/
(0x00000000)
/ BGP peers.
advertised to all
:
4294967041
A received p route with this attribute is not
toutside the local AS. If a confederation
t
advertised
(0xFFFFFF01)
h
is used, such a route can be advertised to other ASs
:
in sthe confederation, instead of being advertised
e the confederation (Confederation is discussed
outside
c
r in the section describing the problems encountered on
u
o a large BGP network).
s
4294967042
A received route with this attribute is not
Re
advertised to any other BGP peer.
(0xFFFFFF02)
g
in4294967043 A received route with this attribute is neither
(0xFFFFFF03)
advertised outside the local AS nor advertised to any
other AS in a confederation.
Page 66
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n Path
/
/
p:
r
a
le
t
t
h
s
e
c
r
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 67
o
n
e
/
m
BGP Route Aggregation-Automatic
o
c
.
i
Aggregation(1/2)
e
w
.
g
n
i
n
AS200
OSPF
r
a
e
20.1.1.2/30
l
/
20.1.1.1/30
/
:
p
t
t
h
RT1s:
e
c
ur
18.0.0.1/32
18.0.0.2/32
a
u
h
RT2
IBGP
o
s
e
[RT1]bgp 200
[RT1-bgp]import-route direct
[RT1-bgp]summary automatic
n
r
a
e
r
o
g
n
i
R
Le
Page 68
n
e
/
m
BGP Route Aggregation-Automatic
o
c
.
i
Aggregation(2/2)
e
w

a
Display the BGP routing table information on RT2:
hu
.
g
n
i
n
r
a
le
Network
NextHop
MED
LocPrf
PrefVal Path/Ogn
*>i 18.0.0.0
3.3.3.3
100
0
?
*>i 20.1.1.0
3.3.3.3
100
0
?
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 69
BGP Route Aggregation-Manual
Aggregation(1/2)
n
e
/
AS200
OSPF
RT2
o
s
e
[RT1]bgp 200
[RT1-bgp]aggregate 18.0.0.0 24
n
r
a
e
r
o
g
n
i
R
Le
Page 70
.
i
e
w
a
u
h
.
g
n
i
n
r
a
e
20.1.1.2/30
l
/
20.1.1.1/30
/
:
p
tIBGP
t
h
RT1s:
e
c
ur
18.0.0.1/32
18.0.0.2/32
m
o
c
BGP Route Aggregation-Manual
Aggregation(2/2)
n
e
/
.
i
e
m
o
c
w
a
u
 Display the BGP routing table information on RT2:
h
.
g
n
i
n
r
a
e
l
/
h - history, i - internal, :s/ - suppressed, S - Stale
tMED
t
Network
NextHop
LocPrf
PrefVal Path/Ogn
h
*>i 18.0.0.0/24
3.3.3.3
100
0
?
:
*>i 18.0.0.1/32
3.3.3.3 s
0
100
0
?
e
*>i 18.0.0.2/32
3.3.3.3
0
100
0
?
c
*>i 20.1.1.0/30
3.3.3.3
0
100
0
?
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 71
o
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
n Path
/
/
p:
r
a
le
t
t
h
s
e
c
r
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 72
o
n
e
/
BGP Optimal Route Selection
Process(1/4)
m
o
c
.
i
e
1.
Discard routes with an unreachable next hop. uaw
2.
Prefer the route with the largest PrefVal.

Remarks:
h
.
g
r
a
le
n
i
n
/
/
the route is. After receiving multiple routes
: with the same destination address from different
p
neighbors, a BGP router compares t
the preferred-values set for these neighbors on the local
t
h is, the better the route is. For example, the following
router. The higher the preferred-value
: the preferred-value of neighbor 3.3.3.3 to 200.
command can be used to set
s
e preferred-value 200
c
[RT2-bgp]peer 3.3.3.3
r
u
o the largest Local_Pref value.
3.
Prefer the route
with
s
Re
g
4.
Prefer annaggregated
route (an aggregated route has a
i
n
r
higher
priority
than a non-aggregated route).
a
Le
r
Copyright
Page 73
o

PrefVal is the preference value of the specified peer. The larger the PrefVal is , the better
n
e
/
Process(2/4)
5.
6.
m
o
c
.
i
e
w
a
u
h
.
g
Prefer the route with the shortest AS_Path.
n EGP, and
i
Prefer the routes with Origin attributes IGP,
n
r
a
Incomplete in descending order oflpriorities.
e
/
/
: MED value.
7.
Prefer the route with the smallest
p
t
t
h
8.
Prefer the routes learnt :from eBGP neighbors (an eBGP
s
e
c
route has a higher rpriority
than an iBGP route).
u
o
s
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 74
o
Process(3/4)
n
e
/
.
i
e
m
o
c
w
a
u an AS.
9.
Prefer the IGP route with the smallest metric hwithin
.
g
n are equal-cost routes
If all the preceding conditions are the same, the routes
i
n
and can be used for load sharing. If load sharingris configured and multiple
a
e
external routes with identical AS_Paths arelavailable, routes are selected on
/ for load sharing.
/
the basis of the number of routes configured
:
p
t
Notes:
t
h
: the following principles do not apply:
After load sharing is configured,
s
e
c
r the shortest Cluster_List.
10. Prefer the route with
u
o
s
Remarks:
Re
ng related to a route reflector and is not covered in this
This is aiconcept
n
r
course.
a
e
L
r
Copyright
Page 75
o





Process(4/4)
n
e
/
.
i
e
m
o
c
w
a
u
11. Prefer the route with the smallest Originator_ID.
h
.
g
n
Remarks:
i
n
r
This is a concept related to a routelreflector
and is not
ea
/
/
covered in this course.
:
p
t
t
h by the router with the smallest
12. Prefer the routes advertised
:
s
router ID.
e
c
r
u
olearnt from a peer with a smaller IP
13. Prefer the routes
s
e
R
address. g
n
i
n
r
a
e
L
r
Copyright
Page 76
o


n
e
/
c
.
ei
w
a
u
1. Origin defines the origin of a BGP route. Specifically,
Origin
h
.
g
n
specifies a method for a BGP speaker to generate
a BGP
i
n
r
route. The values of Origin are ( ). ea
l
/
/
A. IGP
:
p
t
ht
B. BGP
:
s
e
c
C. EGP
r
u
o
s
D. IBGP
Re
g
E. EBGP in
n
r
a
e
F. INCOMPLETE
L
r
Copyright
Page 77
o
n
e
/
c
.
ei
w
a
u methods
2. In the BGP routing protocol, which of the following
h
.
g
n
can prevent loops? ( )
i
n
r
A. Use Origin to identify the origin of alroute.
ea
/
/
: that a route passes
B. Use AS_PATH to record all ASs
p
t
t
h
through.
:
s
ce
C. Use NEXT_HOP to ridentify
the next hop of a route.
u
o
s selection of the egress PE of the peer
D. Use MED to affect
e
R
g
AS.
n
i
n
r
a
Le
r
Copyright
Page 78
o
n
e
/
c
.
ei
w
a
u
3.Which of the following statements about the comparison
h
.
g
between MED and Local_Pref are true? ( in)
n
r
aof traffic.
A. MED is used on the inbound interface
e
l
/
/
:
B. The greater the MED value, the
p higher the priority of a
t
ht
route.
:
s
e
c
C. Local_Pref can be advertised
together with routing
r
u
o
information to different
ASs.
s
e
R
gthe Local_Pref value, the higher the priority of a
D. The greater
n
i
n
route.ar
Le
r
Copyright
Page 79
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. BGP Overview
n
i
n
r
a
le
/
/
p:
t
t
h
Networks
s:
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 80
n
e
/
BGP Configuration Roadmap
Basic
configuration
Configure interfaces
and IP addresses
Loopback
m
o
c
physical interface
.
i
e
w
a
u
h
.
g
Configure an IGP
n
i
n
Enter the BGP view
/
/
p:
Configure a router ID (optional)
BGP configuration roadmap
t
t
h
Configure a BGP peer
BGP
configuration
:
s
e
c
r
IBGP
EBGP
Configure an interface for the establishment of peer relationship (optional)
u
o
s
n
r
a
e
r
o
g
n
i
Re
r
a
le
Enter the IPv4 unicast address
family view
Disable BGP and IGP synchronization (optional)
Run the network command to advertise routes (optional)
Import external routes (optional)
Enable the peer (by default)
Run the next-hop-local command (optional)
Specify clients of a route reflector (optional)
Le
Page 81
n
e
/
Configuring BGP: Networking
Requirements
Device
LoopBack0
LAN(G1/0/0)
Interconnected
Interface
AS
RTA
1.1.1.1
10.0.0.0/8
x.0.0.1/30(G1/0/X)
10
RTB
2.2.2.2
20.0.0.0/8
1.0.0.2/30(G1/0/1)
10
RTC
3.3.3.3
30.0.0.0/8
2.0.0.2/30(G1/0/1)
10
RTD
4.4.4.4
40.0.0.0/8
3.0.0.2/30(G1/0/1)
20
ng
i
n
r
20.0.0.0/8
e
r
o
a
e
L
ou
es
R
:
s
e
c
r
.
i
e
w
a
u
h
.
g
n
i
n
AS 20
RTD
r
a
le
.2
/
/
p.1:
t
t
h.1
m
o
c
LB0: 4.4.4.4/32
40.0.0.0/8
10.0.0.0/8
.1
RTA
LB0: 1.1.1.1/32
AS 10
.2
.2
RTB
LB0: 2.2.2.2/32
RTC
30.0.0.0/8
LB0: 3.3.3.3.3/32
Page 82
n
e
/
Configuring BGP: RTA
m
o
c
.
i
e
[RTA]bgp 10
[RTA-bgp]router-id 1.1.1.1
[RTA-bgp]peer 2.2.2.2 as-number 10
[RTA-bgp]peer 2.2.2.2 next-hop-local
[RTA-bgp]peer 2.2.2.2 connect-interface LoopBack 0
[RTA-bgp]peer 3.3.3.3 connect-interface LoopBack 0
[RTA-bgp]peer 3.0.0.2 connect-interface GigabitEthernet 1/0/3
[RTA-bgp]network 10.0.0.0 8
w
a
u
h
.
g
n
i
n
RTD
r
a
le
s:
e
c
r
u
o
s
ng
i
n
r
20.0.0.0/8
e
r
o
a
e
L
Re .2
LB0: 4.4.4.4/32
.2
/
/
p:
t
t
h .1
AS 20
40.0.0.0/8
.1
10.0.0.0/8
.1
RTA
LB0: 1.1.1.1/32
AS 10
.2
RTB
LB0: 2.2.2.2/32
RTC
30.0.0.0/8
LB0: 3.3.3.3.3/32
Page 83
n
e
/
m
o
c
Configuring BGP: RTB
.
i
e
w
a
u
[RTB]bgp 10
[RTB-bgp]peer 1.1.1.1 as-number 10
[RTB-bgp]peer 1.1.1.1 connect-interface LoopBack 0
[RTB-bgp]network 20.0.0.0 8
[RTC]bgp 10
[RTC-bgp]peer 1.1.1.1 as-number 10
[RTC-bgp]peer 1.1.1.1 connect-interface LoopBack 0
[RTC-bgp]import-route direct
h
.
g
n
i
n
RTD
r
a
le
s:
e
c
r
u
o
s
ng
i
n
r
20.0.0.0/8
e
r
o
a
e
L
Re .2
LB0: 4.4.4.4/32
.2
/
/
p:
t
t
h .1
AS 20
40.0.0.0/8
.1
10.0.0.0/8
.1
RTA
LB0: 1.1.1.1/32
AS 10
.2
RTB
LB0: 2.2.2.2/32
RTC
30.0.0.0/8
LB0: 3.3.3.3.3/32
Page 86
n
e
/
m
o
c
Configuring BGP: RTD
.
i
e
w
a
u
[RTD]bgp 20
[RTD-bgp]peer 3.0.0.1 connect-interface
GigabitEthernet 1/0/1
[RTD-bgp]network 40.0.0.0 8
s:
e
c
r
i
n
r
20.0.0.0/8
e
r
o
a
e
L
Re .2
AS 20
n
i
n
RTD
r
a
le
LB0: 4.4.4.4/32
.2
/
/
p:
t
t
h .1
u
o
s
ng
h
.
g
40.0.0.0/8
.1
10.0.0.0/8
.1
RTA
LB0: 1.1.1.1/32
AS 10
.2
RTB
LB0: 2.2.2.2/32
RTC
30.0.0.0/8
LB0: 3.3.3.3.3/32
Page 87
n
e
/
Configuring Authentication: BGP Peer
m
o
c
.
<RTA>display bgp peer
i
e
w
a
u
Total number of peers : 3
Peers in established state : .
3h
g State PrefRcv
Peer
V
AS MsgRcvd MsgSent OutQ Up/Down
n
i Established 1
2.2.2.2
4
10
24
25
0 00:15:21
n
r Established 1
3.0.0.2
4
20
6
8
0 00:02:18
a
3.3.3.3
4
10
18
20
0e00:12:15 Established
3
l
/
/
<RTB>display bgp peer
:
p
t
ht
Total number of peers : 1
Peers
: in established state : 1
s
Peer
V
AS MsgRcvd
e MsgSent OutQ Up/Down State PrefRcv
c
1.1.1.1
4
10
33
32
0 00:21:14 Established
2
r
u
<RTD>display bgp peer so
BGP local router IDR: e
4.4.4.4
Local AS numberg : 20
npeers : 1
Total number of
Peers in established state : 1
i
n
Peer
V
AS MsgRcvd MsgSent OutQ Up/Down
State PrefRcv
r
3.0.0.1 ea 4
10
17
14
0 00:10:07 Established
4
L
r
Copyright
Page 88
o
n
e
/
Configuring Authentication:
Routing Table (1/4)
m
o
c
w
a
u
.
i
e
<RTA>display ip routing-table
Destinations : 19
Routes : 19
Flags NextHop
Interface
......
20.0.0.0/8 BGP 255 0
RD 2.2.2.2
30.0.0.0/8 BGP 255 0
RD 3.3.3.3
40.0.0.0/8 BGP 255 0
RD 3.0.0.2
......
<RTA>display bgp routing-table
Origin : i - IGP, e - EGP, ? – incomplete
Network
NextHop
MED
LocPrf PrefVal Path/Ogn
*>i 2.0.0.0/30
3.3.3.3
0
100
0
?
i 3.3.3.3/32
3.3.3.3
0
100
0
?
*> 10.0.0.0
0.0.0.0
0
0
i
*>i 20.0.0.0
2.2.2.2
0
100
0
i
*>i 30.0.0.0
3.3.3.3
0
100
0
?
*> 40.0.0.0
3.0.0.2
0
0
20i
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 89
n
e
/
Routing Table (2/4)
m
o
c
w
a
u
.
i
e
<RTB>display ip routing-table
Destinations : 13
Routes : 13
Flags NextHop
Interface
......
10.0.0.0/8 BGP 255 0
RD 1.1.1.1
40.0.0.0/8 BGP 255 0
RD 1.1.1.1
......
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
<RTB>display bgp routing-table
Origin : i - IGP, e - EGP, ? – incomplete
Network
NextHop
MED
*>i 10.0.0.0
1.1.1.1
0
100
0
i
*> 20.0.0.0
0.0.0.0
0
0
i
*>i 40.0.0.0
1.1.1.1
0
100
0
20i
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 90
n
e
/
Routing Table (3/4)
m
o
c
w
a
u
.
i
e
<RTC>display ip routing-table
Destinations : 12
Routes : 12
Flags NextHop
Interface
......
10.0.0.0/8 BGP 255 0
RD 1.1.1.1
......
<RTC>display bgp routing-table
……
Network
NextHop
MED
*> 2.0.0.0/30
0.0.0.0
0
0
?
*> 2.0.0.1/32
0.0.0.0
0
0
?
*> 2.0.0.2/32
0.0.0.0
0
0
?
*> 3.3.3.3/32
0.0.0.0
0
0
?
*>i 10.0.0.0
1.1.1.1
0
100
0
i
*> 30.0.0.0
0.0.0.0
0
0
?
*> 30.0.0.1/32
0.0.0.0
0
0
?
i 40.0.0.0
3.0.0.2
0
100
0
20i
*> 127.0.0.0
0.0.0.0
0
0
?
*> 127.0.0.1/32
0.0.0.0
0
0
?
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 91
n
e
/
Routing Table (4/4)
m
o
c
w
a
u
.
i
e
<RTD>display ip routing-table
Destinations : 12
Routes : 12
Flags NextHop
Interface
……
2.0.0.0/30 BGP 255 0
RD 3.0.0.1
10.0.0.0/8 BGP 255 0
RD 3.0.0.1
20.0.0.0/8 BGP 255 0
RD 3.0.0.1
30.0.0.0/8 BGP 255 0
RD 3.0.0.1
……
h
.
g
n
i
n
r
a
le
/
/
p:
t
t
h
:
s
<RTD>display bgp routing-table e
Total Number of Routes: 5 rc
u
o
……
s
e
Network
NextHop
MED
R
*> 2.0.0.0/30 g 3.0.0.1
0
10?
*> 10.0.0.0 n
3.0.0.1
0
0
10i
i
*> 20.0.0.0
3.0.0.1
0
10i
n
r
*> 30.0.0.0
3.0.0.1
0
10?
a
e
*>L 40.0.0.0
0.0.0.0
0
0
i
r
Copyright
Page 92
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
1. BGP Overview
n
i
n
r
a
le
/
/
p:
t
t
h
:
5. BGP Applications on sEnterprise
Networks
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 93
n
e
/
m
o
c
Large Enterprise WAN
.
i
e
w
a
ISP2u
h
.
g
n
ni
ISP1
r
a
le
/
/
p:
t
t
h
Headquarters
:
s
e
c
r
u
o
s
n
r
a
g
n
i
Branch 1
e
r
o
Le
Re
Branch 3
Branch 2
Page 94
n
e
/
m
o
c
Summary
.
i
e

BGP basic concepts

Working principle of BGP

BGP route selection
:
s
e
c
r
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 95
n
e
/
m
o
c
Thank you
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank you
//
:
www.huawei.com
tp
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
ht
n
e
/
m
o
c
.
i
e
w
a
u
Route Selection and ng.h
i
n
r
Control Feature
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
g
n
i
Re
e
L
e
r
o
www.huawei.com
n
e
/
Preface
.
i
e
m
o
c
w
a
u
 A routing protocol is used to discover routes tohdifferent
.
g
n thereby guiding
destination network segments on a network,
i
n
r
a
routers in forwarding packets. It is impossible
for a router to
e
l
/
accept all the routes learnt by different
routing protocols
/
:
p
t
running on the network.
ht
s:learn useful routes, filter out

A router must be able eto
c
r
u select optimal routes. This course
unwanted routes, oand
s
e
R describes route control and route
comprehensively
g
n
selection.
i
n
r
a
Le
r
Copyright
Page 2
o
n
e
/
Objectives
.
i
e
w
a
uto:
h
.
g
n
Describe route selection tools
i
n
r
a
Describe routing policy
e
l
/
/
:
Describe policy-based route selection
p
t
t
Compare routing policy andh policy-based route
:
s
e
Configure routing policy
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 3
o





m
o
c
n
e
/
m
o
c
Contents
.
i
e
1. Route Selection and Control Overview
h
.
g
2. Route Selection and Control Tools
3. Route Selection and Control
:
s
e
c
r
n
i
n
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
w
a
u
Page 4
Introduction to Route Selection and m/en
o
c
Control
i.

e
w
a
When advertising, receiving, or redistributing routes, a router needs to
implement certain policies according to the actual networking
requirements for filtering the routes or changing the attributes of the
routes:
u
h
.
g
n
ni

r
a
e
l
Advertise only the routes that meet the specified
/ conditions.
/
:
Controlling route reception
p
t
t
Receive only necessary and legal routes
to control routing table sizes and enhance
h
network security.
:
s
e
Filtering and controlling redistributed
routes
c
urroutes discovered by another routing protocol into the current
When redistributing o
the
s protocol redistributes only the routes that meet the specified
routing table, a routing
e
conditions andRsets certain attributes of the redistributed routes so that the routes
g
meet thenrequirements of the current protocol.
i
n
Settingrthe specified route attributes
a
e
L Set the corresponding attributes for the routes filtered by using a route policy.
Controlling route advertisement






e
r
o

Page 5
n
e
/
m
o
c
Route Selection and Control
AS400
D2 (18.0.0.0/8)
D1 (19.0.0.0/8)
/
/
p:
t
t
h
:
s
e AS100
c
r
EBGP
RTB
ni
ng
e
r
o
r
a
e
r
a
le
EBGP
AS200
RTD
AS300
RTE
EBGP
u
o
s
ReIBGP
h
.
g
n
i
n
RTF
EBGP
w
a
u
RTC
IBGP
RTA
L
Page 6
.
i
e
n
e
/
Basic Process of Route Selection andom
c
.
Control
ei
w
a
u two steps:
 Route policy implementation can be divided into
h
.
g
n
i
n
r
Step
Description a
e
l
/ on which the route policy
Define the characteristics of the routes
/
p: a group of matching rules to
is to be implemented. That is, t
define
t
extract the routes that needhto be processed.
:
1
s
Different attributes, such
e as the destination address and the
c
radverting routes, in the routes can be set as the
router address for
u
so
basis of theematching.
Rmatching rules to the route policies used for route
Apply the
g
n
2
i
advertisement,
reception and redistribution.
n
r
a
Le
r
Copyright
Page 7
o
Self-Test Question About Route
Selection and Control Overview
n
e
/
1. The route control involves (
A. Advertising routes
B. Receiving routes
m
o
c
h
.
g
w
a
u
).
r
a
le
n
i
n
/
/
:
p
C. Filtering and controlling the introduced
routes
t
ht
:
D. Setting attributes of a specified
route
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 8
o
.
i
e
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
:
s
e
c
r
n
i
n
r
a
le
/
/
p:
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 9
Access Control List
n
e
/
.
i
e
m
o
c
w
a
An ACL is a group of sequential rules that consist of the permit
u | deny
h
. address,
statements and are described by source address, destination
g
n
i
and port number.
n
r
a into three types:
e
Based on their functions, ACLs can be classified
l
/
/
Basic ACL
:
tp a basic ACL can be used to match source
With a number ranging from 2000 tot2999,
h
IP addresses.
:
s
Advanced ACL
e
c
rfrom 3000 to 3999, an advanced ACL can be used to match
With a number ranging
u
o destination IP addresses, source port numbers, destination port
source IP addresses,
s
e
numbers, andRprotocol numbers.
g ACL
n
Interface-based
i
n
r a number ranging from 1000 to 1999, an interface-based ACL can be used to
With
a
Lematch interfaces.
r
Copyright
Page 10
o








n
e
/
m
o
c
Access Control List

.
i
e
w
a
u
h
.
g
ACL rule matching process

existent ACLs to be referenced).

r
a
le
/
/
: checked according to the rules, all the
If the ACL exists and packets need to be
p
tof the rules matches the packets, the service is
rules in the ACL are queried. If any
t
h
directly notified of the action:matched by the rule and no subsequent rule continues
s
to be queried.
e
c
r
u only source addresses, destination addresses, type of
If the ACL exists and
o
sby IP, TCP source port number, destination port number, and
protocol carried
e
R in the ICMP types need to be matched, all the ACLs are queried
certain options
g
n
according
i to the service requirements for rule matching. Once a rule is matched,
n
rservice is notified of the match and no subsequent rules continue to be queried.
the
a
e
Based on the ACL configurations:


e
r
o
n
i
n
Check whether the user has configured the ACL (certain services may allow non-
L
Page 11
n
e
/
m
o
c
Access Control List


h
.
g
n
i
n
Configuration Sequence

r
a
le
In configuration sequence mode, matching is performed according to
the sequence in which the ACL rules are configured.
Automatic Sequence

/
/
p:
t
t
h
In automatic sequence mode, the system automatically allocates route
IDs and puts the smallest statement in the specified data packet range
at the beginning according to the "depth first" principle.
:
s
e
c
r

w
a
u
Rule matching sequence:


.
i
e
u rule matching mode is configuration
On VRP 5, the default
o
s
e
sequence.
R
g
n classified into those used for IPv4 routes and those
ACLs can i
be
n routes, namely, ACL6.
r
used for
IPv6
a
e
r
o
Le
Page
Pae12 12
n
e
/
m
o
c
ACL Example (1)
.
i
e
w
a
u
h
.
g
n
i
n
Route
1.1.1.1/32
1.1.1.0/24
1.1.0.0/16
1.0.0.0/8
n
r
a
e
r
o
g
n
i
r
a
le
/
/
:
acl number 2001tp
t
rule 0 permithsource
1.1.0.0
0.0.255.255:
s
e
c
r
u
o
s
e
R
1.1.1.1/32
1.1.1.0/24
1.1.0.0/16
Le
Route
Page 13
n
e
/
m
o
c
ACL Example (2)
.
i
e
w
a
u
h
.
g
n
i
n
Route
r
a
le
/
/
p:
1.1.1.1/32
1.1.1.0/24
n
r
a
e
r
o
g
n
i
t
t
h
acl number 2001
rule 0 permit source 1.1.0.0 0
s:
1.1.0.0/16
e
c
r
1.1.0.0/16
1.0.0.0/8
Route
u
o
s
Re
Le
Page 14
n
e
/
m
o
c
ACL Example (3)
.
i
e
w
a
u
h
.
g
n
i
n
Route
1.1.1.1/32
1.1.2.1/32
1.1.3.1/32
1.1.4.1/32
1.1.5.1/32
ng
/
/
p:
t
t
acl number 2001
h
rule 0 permit
: source
s
e 0.0.254.255
1.1.1.0
c
r
u
o
s
Re
1.1.6.1/32
ni
e
r
o
r
a
e
Route
r
a
le
1.1.1.1/32
1.1.3.1/32
1.1.5.1/32
L
Page 15
n
e
/
m
o
c
ACL Example (4)
.
i
e
w
a
u
h
.
g
n
i
n
Route
1.1.1.1/32
1.1.1.0/24
1.1.0.0/16
1.0.0.0/8
n
r
a
e
r
o
g
n
i
r
a
le
/
/
p:
acl number 2001
rule 1 deny source 1.1.1.0 0
rule 2 permit source 1.1.0.0 0.0.255.0
rule 3 deny
:
s
e
c
r
t
t
h
s
e
R
ou
1.1.1.1/32
1.1.0.0/16
Le
Route
Page 16
n
e
/
m
o
c
ACL Example (5)
.
i
e
w
a
u
h
.
g
n
i
n
Route
r
a
le
/
/
p:
1.1.1.1/32
1.1.1.0/24
g
n
i
1.0.0.0/8
n
r
a
e
r
o
Le
t
t
h
acl number 2001
s:
1.1.1.0/24
e
c
r
1.1.1.0/25
1.1.0.0/16
Route
1.1.1.0/25
u
o
s
Re
How to filter 1.1.1.0/25 ?
Page 17
IP-Prefix
n
e
/
.
i
e
m
o
c
w
a
u prefix of
 Used to filter IP prefix according prefix number and
h
.
g
length
n
i
n
r
a
 Prefix-list has better capability than ACL
e
l
/
/
 Prefix-list can not filter data packets
:
p
t
 Example: ip ip-prefix test index
ht 10 permit 10.0.0.0 16
:
s
greater-equal 24 less-equal
28
e
c
rbe 10.0
u
Prefix number must
o
s
e
R
24<=prefix length <=28
g
n
i
Such as:10.0.1.0/24,
10.0.2.0/25, 10.0.2.192/26
n
r
a
e
L
r
Copyright
Page 18
o



n
e
/
m
o
c
IP-Prefix

IP prefix list matching sequence:
.
i
e
h
.
g
w
a
u
During the matching, the system checks each nentry according to
i
n
the index numbers in ascending order. Therefore,
the specified
r
a
e expected matching
entry index numbers must conform to lthe
/
/
:
sequence.
p
t
t
Once an entry is found to meet
h the condition, the filter list is
: the system does not match any other
considered as passed and
s
e
c
entries.
r
u
o
s
 IP prefix lists canebe classified into IPv4 prefix lists and IPv6 prefix
R
g with ACLs, IP prefix lists can be configured easily
lists. Compared
n
i
n
and applied
flexibly.
r
a
e
L
r
Copyright
Page 19
o


n
e
/
m
o
c
IP-Prefix Example
.
i
e
w
a
u
h
.
g
n
i
n
Route
1.1.1.1/32
1.1.1.0/24
1.1.1.0/25
1.1.0.0/16
g
n
i
1.0.0.0/8
n
r
a
e
r
o
r
a
le
/
/
: 10
p
ip ip-prefix Pref1 index
t
t
permit 1.1.1.0h24
greater-equal
: 24 less-equal 24
s
e
c
r
u
o
s
Re
Le
Page 20
Route
1.1.1.0/24
AS-Path-Filter
n
e
/
.
i
e
m
o
c
w
a
u
 The AS_Path filter is a group of matching conditions
h
.
g
n
specified for the AS_Path field, namely, AS_Path
list.
i
n
r
aa regular expression.
 The AS_Path filter is defined by using
e
l
/
/
:
Example
p
t
ht .* to match all AS_PATH lists.
Run ip as-path-filter 10 permit
:
s
Run ip as-path-filter 10
e permit _100$ to match all the routes
c
ur
originated fromoAS100.
s
e
Run ip as-path-filter
10 permit ^200_ to match all the routes
R
g from AS200.
n
received
i
n
r
a
Le
r
Copyright
Page 21
o




n
e
/
m
o
c
Common Regular Expressions
Regular
Expression
^$
.*
_10_
^10_
e
r
o
g
n
_10$ i
n
r
ea
.
i
e
w
a
u
Meaning
h
.
g
n
i
n
r
a
e from the local AS.
Indicates the routes originated
l
/
/
:
Indicates all the routes.
p
t
t
h routes must pass through
Indicates that the
:
s
AS10. ce
r
u
Indicates
o that only the routes from AS10 are
s
e
Raccepted.
Indicates all the routes originated from AS10.
L
Page 22
Community-Filter
n
e
/
.
i
e
m
o
c
w
a
 A community filter list specifies matching conditions u
for the
h
.
g
community attribute field.
n
i
n
 Community filters can be classified into twortypes: basic and
a
e
l
advanced:
/
/
:
pto match the actual community
Basic community filters are used
t
ht
attributes and constants
:
s
ip community-filter 1 permit
e 100:1 100:2
c
r1 permit 100:1
u
ip community-filter
o
s
ip community-filter
Re 1 permit no-export
ng
Regulariexpressions
can be used for advanced community filters.
n
r
ip community-filter
100 permit ^10
a
Le
r
Copyright
Page 23
o





Route-Policy(1/2)
n
e
/
.
i
e
m
o
c
w
a
 A route policy is used to match the specified routes or
u certain
h
.
attributes, such as the next hop and outbound interface,
of the
g
n
i when conditions
routes, and change the attributes of these routes
n
r
a
are met.
e
l
/
/
 A route policy can consist of multiple
nodes,
among which an OR
:
p
t
relationship exists (The methodtof specifying node numbers is the
h
same as the method of specifying
the index numbers of IP prefix
:
s
eenters the route policy filter, the system
lists). When a route entry
c
r according to the node sequence
u
checks each node in
turn
o
s
numbers. A route
Reis considered to have passed the filter once any
g policy passes the filter, and the system does not
node of the nroute
i
n
match any
other node.
r
a
e
L
r
Copyright
Page 24
o
Route-Policy(2/2)
n
e
/
.
i
e
m
o
c
w
a
All of the nodes has the if-match and apply sub clause,uand the ifh
.
match clauses is “And” relationship.
g
n
ni deny.
There are two node matching modes: permit r
and
ea of the node, the apply
In permit mode, if a route entry passes thelfiltering
/ does not match the route
clause of the node is executed and the /system
: the system matches the route
p
entry against any other node. Otherwise,
t
t
entry against the next node.
h
: is not executed. If a route entry meets all
s
In deny mode, the apply clause
e
c
the if-match clauses ofrthe node, the route entry is prohibited from passing
outhe system does not match the route entry against
through the node s
and
e
the next node. ROtherwise,
the system continues to match the route entry
against theng
next node.
i
n
r
a
Le
r
Copyright
Page 25
o




n
e
/
m
o
c
Route-Policy Example
Network
Cost
1.1.2.0/24 4687
4687
1.1.3.0/24 4687
4687
1.1.3.0/25 1
1
5.5.5.5/32 4687
4687
6.6.6.6/32 4687
4687
Network
Cost
1.1.3.0/24 4687
21
1.1.3.0/25 11
21
6.6.6.6/32 4687
4687
n
r
a
e
r
o
Le
w
a
u
NextHop
34.34.34.2
13.13.13.1
34.34.34.2
13.13.13.1
34.34.34.2
13.13.13.1
34.34.34.2
13.13.13.1
34.34.34.2
13.13.13.1
acl number 2001
rule 0 permit source 1.1.3.0 0.0.0.255
acl number 2002
h
.
g
n
i
n
r
a
le
g
n
i
Re
route-policy RP deny node 10
if-match ip-prefix Pref1
route-policy RP permit node 20
if-match acl 2001
if-match ip next-hop acl 2002
apply cost 21
apply cost 11
#
ip ip-prefix Pref1 index 10 permit
greater-equal 25 less-equal 25
/
/
p:
:
s
e
c
r
u
o
s
NextHop
34.34.34.2
13.13.13.1
34.34.34.2
13.13.13.1
34.34.34.2
13.13.13.1
.
i
e
t
t
h
Page 26
5.5.5.5
1.1.2.0
6.6.6.6
1.1.3.0
32
24
32
24
n
e
/
m
o
c
Comparison of Filters
Filter
ACL
Application
Scope
Dynamic routing
protocols
.
i
e
w
a
u
Matching Condition Remarks
Destination address,
next hop
h
.
g
Often referenced by
filter-policy and routepolicy
n
i
n
r
a
e
Dynamic routing
Destination address,
l
IP prefix list
/
protocols
next hop
/
:
p
Destination
t address,
t
nexthhop, metric,
Dynamic routing
Route-Policy
interface
information,
:
protocols
s
e route type, ACL, IP
c
r prefix list
u
o
s
AS_Path attribute
AS_Path filter BGP
e
R
g
n
i
Community
n
Community attribute
BGP
r
filter
a
e
L
r
Copyright
o
Often referenced by
filter-policy and routepolicy
Often referenced by
import-route
Often referenced by BGPrelated commands
Often referenced by BGPrelated commands
Page 27
n
e
/
m
Self-Test Questions About Route
o
c
.
i
Selection and Control Tool
e
w
1. Which of the following statements about "ip ip-prefix
ua Prefix1
permit 160.0.0.0 8" is true? (
)
n
i
n
h
.
g
A. The first three bits of the prefix must be
ar 101. The mask
e
l
/
length must range from 8 to 32 bits.
/
:
p
t must be 101. The mask
B. The first three bits of the prefix
t
h
length must be 8 bits. s:
e
c
r be 160. The mask length must
u
C. The prefix number
must
o
s
e
R
range from 8 to 32 bits.
g
n
i number must be 160. The mask length must be
D. The prefix
n
r
a
8 bits.
Le
r
Copyright
Page 28
o
n
e
/
m
o
c
.
i
e
w
a
2. Which of the following filters can filter only BGP
huroutes? (
.
g
n
i
n
A. ACL
r
a
le
B. IP-Prefix
/
/
p:
C. AS-PATH-Filter
:
s
e
c
r
D. Community-Filter
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 29
)
n
e
/
m
o
c
.
i
e
w
a
3. What is the difference between the ACL and the
hu IP-Prefix? (
)
.
g
n
i
n
r
a
A. The ACL can be used to match data
eexcept routing
l
/
/
information.
:
p
t
t
h
B. The ACL can be used to differentiate
routes with the same
:
s
e
prefix and different masks.
c
r
u
obe used to match data except routing
C. The IP-Prefix can
s
Re
information.g
n
i
n
r
D. The IP-Prefix
can be used to differentiate routes with the
a
e
L
same
prefix and different masks.
e
Copyright
Page 30
or ©2012 Huawei Technologies Co., Ltd. All rights reserved.
n
e
/
m
o
c
.
i
e
w
a
4. Which of the following statements about the Route-Policy
hu are
true? (
)
.
g
n
i
n
A. The Route-Policy consists of the "If-match"
arand "apply"
e
l
/
statements.
/
:
p
B. The Route-Policy can have multiple
tt nodes. A route can be
h
matched only if all conditions
s: of a node are met.
e
c
C. The Route-Policy canurhave multiple nodes. A route can be
o
s
matched only if one
Re condition of a node is met.
g
D. If a route isindenied
after the first node of the Route-Policy is
nand the route matches the second node, the action
r
matched
a
e
L at the second node is also performed.
defined
r
Copyright
Page 31
o
n
e
/
m
o
c
Contents
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
/
/
p:
:
s
e
c
r
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 32
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
3.1 Selecting and Controlling Routes by Using
inRoute Filtering
n
r
a
3.2 Selecting and Controlling Routes by
Adjusting
Routing
e
l
/
/
Protocol Priorities
:
p
t
t
3.3 Controlling Packet Forwarding
h Paths by Using Policy-based
:
s
Routing
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 33
o
n
e
/
Avoiding Sub-Optimal Routes by Usingom
c
.
Route Filtering(1/2)
ei
w
a
u
h
.
g
2. Import rip
isis 1
import-route rip 1
n
i
n
r
a
le
RTC
RTA
S0
:
s
e
c
r
/
/
p:
t
t
h
Lo0:2.2.2.2
RTD
ou
g
n
i
s
e
R
RTB
[RTB]display ip routing-table
Destination/Mask
Proto Pre
2.0.0.0/8
ISIS
15
n
r
a
e
r
o
Le
Cost
84
NextHop
12.12.12.1
Page 34
Interface
Serial0
n
e
/
Avoiding Sub-Optimal Routes by Usingom
c
.
Route Filtering(2/2)
ei
w
a
u
isis 1
import-route rip 1
h
.
g
n
i
n
r
a
le Lo0:2.2.2.2
RTC
/
/
p:
RTB
t
t
h
e
r
o
RTD
:
s
e
acl number 2001
c
r 2.0.0.0 0.255.255.255
rule 5 deny source
u
o
rule 10 permit
s
isis 1
e
R
filter-policy 2001 import
g
n
i
[RTB]display
ip routing-table
n
Destination/Mask
Pre Cost
NextHop
r 2.0.0.0/8 Proto
a
RIP
100 1
24.24.24.2
Le
Page 35
Interface
Serial1
n
e
/
m
Avoiding Routing Loops by Using Route
o
c
.
i
Filtering(1/2)
e
w
7. Import isis
r
a
le
RTC
/
/
p:
RTB
n
r
a
RTA
Le
2. Dest. ASE 150
1. Import direct cost 2
e
r
o
.
g
n
i
n
a
u
h
g
n
i
:
s
e
c
r
ou
s
e
R
Lo0:2.2.2.2
t
t
h
RTD
RTE
4. Import ospf-ase
Page 36
n
e
/
m
Avoiding Routing Loops by Using Route
o
c
.
i
Filtering(2/2)
e
w
RTC
.
g
n
i
n
a
u
h
r
a
le
acl number 2001
rule 0 deny source 2.0.0.0 0.255.255.255
rule 1 permit
ospf 1
import-route isis 1 route-policy RP1
route-policy RP1 permit node 10
if-match acl 2001
/
/
p:
RTB
t
t
h
:
s
e
ospf 1
c
import-route direct costr2
u
o
s
e
R
g Lo0:2.2.2.2
n
i
n
r
a
Le
r
Copyright
o
RTE
RTA
RTD
isis 1
import-route ospf 1
Page 37
n
Accurately Controlling Route Redistribution
e
/
m
o
and Route Advertisement by Using Route
c
.
i
Filtering
we
[RTB]display bgp routing-table
*>
*>
Network
6.6.6.6/32
201.12.12.0
NextHop
12.12.12.1
12.12.12.1
MED
0
0
LocPrf
.
g
n
i
n
a
PrefVal Path/Ogn
u
h
r
a
le
RTA
0
0
100?
100?
RTB
/
/
:
p
MED
t0
t
h 0
[RTA]display bgp routing-table
Network
NextHop
LocPrf
PrefVal Path/Ogn
*>
6.6.6.6/32
0.0.0.0
0
?
*>
10.1.1.0/24
0.0.0.0
0
?
*>
172.16.1.0/24
0.0.0.0
0
0
?
*>
192.168.1.0
0.0.0.0
0
0
?
*>
192.168.2.0
0.0.0.0
0
0
?
*>
201.12.12.0
0.0.0.0
0
0
?
bgp 100
peer 12.12.12.2 ip-prefix P1 export
ip ip-prefix P1 index 5 deny 10.0.0.0 8 greater-equal 8 less-equal 32
ip ip-prefix P1 index 20 permit 0.0.0.0 0 less-equal 32
:
s
e
c
r
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 38
Route Filtering Rules
n
e
/
.
i
e
m
o
c
w
a
 The route-policy filter can reference an IP prefix list as
u a matching
h
.
g
condition.
n
i
n
r
 In each routing protocol, the filter-policy command
can be run to
a
e
reference an IP prefix list (or reference/lan ACL) to filter received
/
:
and advertised routes so that onlypthe routes that meet the
t
t
condition are received or advertised.
h
:
s
The filter-policy import ecommand is used to filter received routes.
c
r
u command is used to filter advertised
The filter-policy export
o
s
e
routes.
R
g command operation procedure in a distancen
 The filter-policy
i
n
r
vector aprotocol
and that in a link-state protocol are different.
e
L
r
Copyright
Page 39
o


n
e
/
m
o
c
Route Filtering Rules
w
a
u
.
i
e
[RouterC]ip ip-prefix in index 10 permit 172.1.18.0 24
[RouterC]ospf
[RouterC-ospf-1]filter-policy ip-prefix in import
h
.
g
n
i
n
RouterC
r
a
le
OSPF
/
/
p:
RouterA
0
RouterB
:
s
e
c
r
RouterD
t
t
h
Internet
172.1.16.0/24
172.1.17.0/24
172.1.18.0/24
172.1.19.0/24
172.1.20.0/24
u
o
s
Re
[RouterA]ip ip-prefix a2b index 10 permit 172.1.17.0 24
[RouterA]ospf
[RouterA-ospf-1]filter-policy ip-prefix a2b export
n
r
a
e
r
o
g
n
i
Le
Page 40
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
inRoute Filtering
n
r
a
Adjusting
Routing
e
l
/
/
Protocol Priorities
:
p
t
t
:
s
Routing
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 41
o
n
e
/
Selecting and Controlling Routes by om
c
.
Adjusting Routing Protocol Priorities
ei
w
a
u routing
 The following table lists the default priorities ofhthe
.
g
protocols or routing categories on VRP 5:in
n
r
a
Protocol
Preference
e
l
/
/
Direct
0
:
p
t
t
OSPF
10
h
:
s
IS-IS
15
e
c
r
Static u
60
o
s
e
RIP
100
R
g ASE
n
OSPF
150
i
n
r
a
BGP
255
e
L
r
Copyright
Page 42
o
Floating Static Routes are Typical /en
m
o
Application of Routing Protocol .c
i
e
Priorities
w
a
The protocol preference of OSPF is 10 and of static route is 60.
u
h
.

g
When the active link becomes faulty, the OSPFnneighbor
i
n
r learnt from
relationship is interrupted. As a result, thearoutes
e
l
OSPF become invalid and are cleared/from the routing table.
/
:
p
t
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 43
o

STATIC
STATIC
OSPF
Selecting and Controlling Routes by
n
e
/
m
Adjusting Routing Protocol
o
c
Priorities-Floating Static Route ei.
w
a
Configuration
hu
S2
1.1.1.1
.
g
n
S2
i
n
12.12.12.0
r
a
le
/
/
p:
21.21.21.0
RTA S3
2.2.2.2
S1 RTB
t
t
h
ospf 1
area 0.0.0.0
network 12.12.12.0 0.0.0.3
network 1.1.1.1 0.0.0.0
ip route-static 2.2.2.2 255.255.255.255 Serial3
:
s
e
c
r
Destination/Mask
1.1.1.1/32
2.2.2.2/32
n
r
a
e
r
o
g
n
i
u
o
s
e
Pre
RProto
Direct 0
OSPF
10
Cost
0
1563
NextHop
127.0.0.1
12.12.12.2
Le
Page 44
Interface
InLoopBack0
Serial2
Selecting and Controlling Routes by
n
e
/
m
Adjusting Routing Protocol
o
c
Priorities-Floating Static Route ei.
w
a
Verification
hu
1.1.1.1
S2
12.12.12.0
RTA S3
21.21.21.0
/
/
p:
r
a
le
.
g
n
i
S2
n
2.2.2.2
S1 RTB
t
t
h
:
s
e
[RTA]display ip routing-table
c
Destination/Mask
Proto rPre Cost
NextHop
u
1.1.1.1/32 Direct
127.0.0.1
o 0 0
s
2.2.2.2/32 Static
60
0
21.21.21.1
e
R
g
n
i
n
r
a
Le
r
Copyright
Page 45
o
Interface
InLoopBack0
Serial3
n
e
Selecting and Controlling Routes by Adjusting m/
Routing Protocol Priorities- Application of .co
i
e
Routing Protocol Priorities in Routing Protocol
w
a
u
Migration
h
.
g
n
i
n
r
a
e
l
/
/
:
p
t
OSPF
IS-IS
ht
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 46
o
n
e
/
m
o
c
Contents
.
i
e
h
.
g
w
a
u
inRoute Filtering
n
r
a
Adjusting
Routing
e
l
/
/
Protocol Priorities
:
p
t
t
:
s
Routing
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 47
o
n
e
/
Controlling Packet Forwarding Paths om
c
.
by Using Policy-based Routing
ei
w
a
Policy-based routing is mainly used to control packet forwarding.
That
u
h
. table.
is, packets can be forwarded not according to the routing
g
n
i
n on ACLs and packet
Policy-based routing supports information based
r
a forwarding.
lengths to flexibly specify the path of data packet
e
l
/
Policy-based routing can be classified:/into interface policy-based
p
t
routing and local policy-based routing:
t
h
Interface policy-based routing
:
s
e view, interface policy-based routing applies to the
Configured in the interface
c
rinterface. Interface policy-based routing is used to meet
packets bound for the
u
o such as forwarding and security.
common requirements,
s
e
R
Local policy-based routing
g
n
Configured
i in the system view, local policy-based routing applies to the packets
n
r
generated
by the local router.
a
Le
r
Copyright
Page 48
o







n
e
/
Controlling Packet Forwarding Paths omby
c
.
Using Policy-based Routing Example
ei
w
a
u
acl number 2001
acl number 2002
interface Ethernet 1
ip policy-based-route PBR1
h
.
g
n
i
n
r
a
le
/
/
p:
PCB
:
s
e
c
r
1.1.1.2
S2
u
o
s
E1
PCA
e
r
o
Le
n
r
a
g
n
i
Re
policy-based-route PBR1 permit node 10
if-match acl 2001
apply output-interface Serial0
policy-based-route PBR1 permit node 20
if-match acl 2002
apply output-interface Serial2
t
t
h
RTB
5.5.5.5
S0
RTA
RTC
Page 49
n
e
/
m
o
c
.
i
e
w
1. The priority of the OSPF route is ( ).
A. 0
.
g
n
i
n
a
u
h
r
a
le
B. 10
/
/
p:
C. 100
:
s
e
c
r
D. 255
t
t
h
u
o
s
n
r
a
e
r
o
g
n
i
Re
Le
Page 50
n
e
/
m
o
c
.
i
e
w
a
2. Which of the following statements about policy-basedhurouting are true?
( )
.
g
n
i
n
A. In policy-based routing, the "apply" statement
ar can be used to modify
e
l
/ of packet forwarding.
the outbound interface, next hop and priority
/
:
p
t
B. In policy-based routing, multiple "if-match"
statements can be defined.
t
h
: interfaces are specified by using the
C. If multiple next hops or outbound
s
e
c
"apply" statement, loadur
balancing is applied to forwarding.
o
s
D. Policy-based routing
Re can be configured in the interface view or system
g on the scenario.
n
view, depending
i
n
r
a
Le
r
Copyright
Page 51
o
n
e
/
m
o
c
.
i
e
w
a
3. The intranet of a company uses a private class B IP address.
To
hu
.
g
prevent the routing information about the intranetnfrom being leaked to
i
n
r to be configured on
the public network, a route filtering policy needs
a
e
l
the outbound router to filter all routes on/ the network segment from
/
:
pto configure the IP-Prefix? ( )
172.16.0.0 to 172.31.255.255. How
t
t
h
A. ip ip-prefix Prefix1 deny 172.16.0.0
24 greater-equal 12 less-equal 32
:
s
e
c
B. ip ip-prefix Prefix1 denyr172.16.0.0
8 greater-equal 8 less-equal 32
u
o
s
C. ip ip-prefix Prefix1edeny 172.16.0.0 16 greater-equal 16 less-equal 32
R
g deny 172.16.0.0 12 greater-equal 12 less-equal 32
n
D. ip ip-prefix Prefix1
i
n
r
a
Le
r
Copyright
Page 52
o
n
e
/
Summary
.
i
e
m
o
c
w
a
u
 Access control list（ACL） /Prefix-list /AS-path-filter
h
.
g
n
/Community-filter /Route-policy
i
n
r
a
 Importing Route /Filtering Route /Advertisement
of Default
e
l
/
/
Route
:
p
t
t
h
 Policy-based route selection
:
s
e
c
r
u
o
s
Re
g
n
i
n
r
a
Le
r
Copyright
Page 53
o
n
e
/
m
o
c
Thank you
.
i
e
w
a
u
h
.
g
n
i
n
r
a
le
Thank you
//
:
www.huawei.com
tp
:
s
e
c
r
u
o
s
n
r
a
e
r
o
Le
g
n
i
Re
ht

Area 1 - Huawei

Transcription

Similar documents

Proposed Xpress Route 423 Schedule, Fare, and Route:

LPU Batangas vicinity map - Lyceum of the Philippines University

Madrid, Spain

Brochure - Premier Commercial Realty

50000 in free upgrades!

Huawei D51 Discovery Expedition

muttaburrasaurus - Clyde Peeling`s Reptiland

The Killer APP for NFV

AVS24 2.4 GHZ Wireless Audio/Video Sender

c O n TA c T jiM SPEROS