Professional Documents
Culture Documents
SJ-20150114102049-010-ZXR10 5900E Series (V3.00.11) Configuration Guide (Reliablity)
SJ-20150114102049-010-ZXR10 5900E Series (V3.00.11) Configuration Guide (Reliablity)
Version: 3.00.11
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
Figures............................................................................................................. I
Glossary ........................................................................................................ III
III
IV
Intended Audience
This manual is intended for:
Chapter 1, VRRP Describes the VRRP principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Chapter 2, MAC Ping/MAC Describes the MAC Ping/MAC Trace principle, and the configuration
Trace Configuration commands, maintenance commands, configuration examples of the
ZXR10 5900E.
Chapter 3, EFM Describes the EFM principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Chapter 4, CFM Describes the CFM principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Chapter 5, SAMGR Describes the SAMGR principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Chapter 6, BFD Describes the BFD principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Chapter 7, IP FRR Describes the IP FRR principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Chapter 8, Route Load Describes the principle of route load sharing, and the configuration
Sharing Configuration commands, maintenance commands, configuration examples, and fault
troubleshooting of the ZXR10 5900E.
Chapter 9, Multicast Load Describes the principle of multicast load sharing, and the configuration
Sharing Configuration commands, maintenance commands, configuration examples of the
ZXR10 5900E.
Chapter 11, UDLD Describes the UDLD principle, and the configuration commands,
Configuration maintenance commands, configuration examples of the ZXR10 5900E.
Conventions
This manual uses the following typographical conventions:
Italics Variables in commands. It may also refer to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
Constant Text that you type, program codes, filenames, directory names, and function names.
width
[] Optional parameters.
{} Mandatory parameters.
II
The same default route is set for all hosts in the internal network to the egress network
gateway (switch A in Figure 1-1). With the default route, hosts in the internal network
communicate with external network. If a fault occurs on the egress network gateway, the
communications between the hosts and the external network will be interrupted.
1-1
VRRP Principle
Working Principle
VRRP forms a virtual switch with the Switch A and Switch B in a LAN, see Figure 1-2.
The virtual switch has its own IP address 10.100.10.1 (this IP address can be the same
with an interface address on a switch). Physical route A and switch B also have their
own IP addresses (IP address of switch A is 10.100.10.2 and IP address of switch B is
10.100.10.3). Hosts in the LAN only knows the IP address 10.100.10.1 of the virtual switch.
Hosts do not know the IP addresses of switch A and switch B. Switch A and switch B set
the IP address 10.100.10.1 of the virtual switch as their default routes. Therefore, hosts in
the LAN communicates with other networks through this virtual switch. The virtual switch
need to do the following operations:
1. The virtual switch selects a master switch in accordance with the priority. The switch
with the highest priority becomes the master switch and its state is Master. If the
priorities are the same, the master IP addresses on interfaces are compared. The
switch with the greater master IP address on an interface becomes the master switch.
The master switch provides routing service.
2. The other switch operates as a backup switch. It detects the state of the master switch
at any time.
1-2
l When the master switch works properly, it sends a VRRP multicasting message
at a certain interval to inform the backup switch in the group that the master switch
works properly.
l If the backup switch in the group does not receive messages from the master
switch for a long time, the backup switch changes its state to Master.
l When there are several backup switches in the group, there might be several
master switches at this time. In this situation, each master switch compares the
priorities in the VRRP messages with its local priority. If its local priority is smaller
than the priorities in the VRRP messages, the master switch changes its state to
Backup. Otherwise, the master keeps its state.
In this way, the switch with the highest priority becomes the new master switch. The
VRRP backup function is finished.
The switches that form the virtual switch has three states, Initialize, Master and Backup.
The states descriptions are as follows:
l Initialize
A switch enters this state after the system is started. When an interface receives a
startup message, the switch becomes Backup state (when the priority is not 255) or
Master state (when the priority is 255). In Initialize state, the switch does not handle
VRRP messages.
l Master
When a switch is in Master state, it performs the following operations:
l Backup
1-3
When a switch in Backup state receives an event indicating that the MASTER_DOWN
timer expires, the switch state becomes Master. When the switch receives VRRP
messages in which the priorities are smaller than its own priority, it will drop the
messages, so it does not reset the timer. After several times, the timer expires, and
the switch state becomes Master. When the switch receives a Shutdown event, the
Switch Becomes Initialize state.
The state conversion is shown in Figure 1-3.
In accordance with the above analysis, the hosts in the network do not have any extra
operations, and the communications with external network will not be affected due to the
faults on a switch.
Practical Network Application
1. VRRP monitoring interface state
VRRP provides a function to monitor interface states. That is, VRRP provides the
backup function not only if a fault occurs on an interface in the backup group, but also
if a fault occurs on another interface on switches.
When the monitored interface state is down, the priority of the switch decreases by
a certain value automatically, which makes the priorities of other switches in the
backup group be higher than the priority of this switch. This urges master/slave
switch changeover.
The switch with the highest priority becomes the master switch and the changeover is
finished.
1-4
In Figure 1-4, VRRP Group 1 monitors the interface marked with a red point on switch
A. When the interface works properly, switch A acts as the master switch. When the
interface is down, the priority of switch A is decreased. As a result, the priority of switch
A is lower than that of switch B. In this way, master/backup changeover is finished.
2. VRRP load sharing
Load sharing means that several switches bear services at the same time to avoid
occurrence of idle switches. Therefore, it is necessary to create two or more backup
groups to implement load sharing, see Figure 1-5.
1-5
b. Working mechanism
Switch A and switch B have the following agreements during VRRP negotiation
through priority configuration of the backup groups on switch A and switch B:
l Switch A operates as the master switch in Group 1 and operates as a backup
switch in Group 2.
l Switch B operates as the master switch in Group 2 and operates as a backup
switch in Group 1.
l A part of hosts uses the backup group 1 as the gateway and the traffic is sent
through switch A. The other part of hosts uses the backup group 2 as the
gateway and the traffic is sent through switch B.
In this way, the data flows are shared and backed up.
3. VRRP heartbeat configuration
VRRP protocol messages can be transmitted through heartbeat, so the messages are
not necessarily transmitted by the interface configured with a VRRP group. If heartbeat
is configured in a VRRP group, designate the out-interface sending messages as the
heartbeat interface. If heartbeat is not configured in a VRRP group, the out-interface
is the interface configured VRRP.
4. VRRP track configuration
There are three applications of VRRP link detection.
l Application one
As shown in Figure 1-6, the VRRP protocol is used between switch A and switch
B. These two routers are used for master/backup selection. EOAM (including
Ethernet in the First Mile (EFM) and Connectivity Fault Management (CFM)) is
used to detect the link state between the switch and the router.
For the state transfer of EOAM for VRRP, see Figure 1-7. EOAM monitors the
link state between the router and the switch. When receiving the link fault notified
by EOAM in the master or backup state, VRRP transfers to the initialize state
directly. When all VRRP interfaces are in up state and VRRP is in initialize state,
VRRP receives link recovery notified by EOAM, and the backup group is the IP
Owner, the state will transfer to the master state, otherwise, the state will transfer
to the backup state.
1-6
l Application two
The VRRP protocol is used between switch A and switch B, and these two routers
are used for master/backup selection, see Figure 1-8. The EOAM (including EFM
and CFM) is used to detect the link state between the switches and the routers.
BFD is used to detect the link state between routers. In this application, the EOAM
can be replaced by the link BFD.
For the state transfer of EOAM (or link BFD) + peer BFD for VRRP, see Figure
1-9. When receiving the link fault notified by EOAM in the master or backup state,
VRRP transfers to the initialize state directly. When all VRRP interfaces are up,
VRRP is in initialize state, VRRP receives link recovery notified by EOAM, and
the group is the IP Owner, the state will transfer to the master state, otherwise,
the state will transfer to the backup state. If VRRP is in backup state, and VRRP
receives the link fault notified by peer BFD, the VRRP will transfer to the master
state.
1-7
l Application three
The VRRP protocol is used between switch A and switch B, see Figure 1-10.
These two routers are used for master/backup selection. The EOAM (including
EFM and CFM) is used to detect the link states between switch A and switch C,
and between switch B and switch C. The state of EOAM for VRRP transfers in
accordance with the VRRP protocol negotiation. When receiving the link fault
notified by EOAM, VRRP decreases the priority based on configuration and
triggers master/slave router changeover.
1-8
1-9
1-10
Parameter Description
Parameter Description
Parameter Description
Parameter Description
1-11
Parameter Description
link-type Link-type
peer-type Peer-type
Parameter Description
Parameter Description
Parameter Description
Parameter Description
vrid <1-255> The virtual switch ID number of the administration group owner, in
the range of 1-255
1-12
Command Function
ZXR10#show vrrp {ipv4|ipv6} brief interface <interface-name> This views the brief information of
all IPv4 or IPv6 VRRP groups on a
specific interface.
ZXR10#show vrrp interface <interface-name>[vrid <1-255>] This views the detailed information
of all VRRP groups or a specified
group on a specified interface.
An example of the show vrrp ipv4 brief command output is shown below.
ZXR10#show vrrp ipv4 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 255 254 999 P Master 192.168.1.10 15.15.15.1
supervlan1 100 200 10000 P Master 35.35.35.1 1.1.1.1
supervlan2 120 255 157 A P L Master 35.35.35.1 35.35.35.1
An example of the show vrrp ipv6 brief command output is shown below.
ZXR10#show vrrp ipv6 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
supervlan5 5 100 1000 P Init 0:0:0:0:0:0:0:0 FE80:0:0:0:0:0:0:1
supervlan4 4 100 1000 P Init 0:0:0:0:0:0:0:0 FE80:0:0:0:0:1:2:3
supervlan2 2 100 1000 P Init 0:0:0:0:0:0:0:0 FE80:0:0:0:0:1:2:3
Output descriptions:
P Preemption mode
L Learning mode
An example of the show vrrp ipv4 brief interface command output is shown below.
An example of the show vrrp ipv6 brief interface command output is shown below.
1-13
Output descriptions:
1-14
supervlan4 - vrID 8
Vrrp configure info:
IP version 4, VRRP version 3
Virtual IP address is 8.9.7.1
Virtual MAC address is 0000.5e00.0108
Advertise time is 1.000 sec
Configured priority is 100
Preemption enable, delay 0 secs
Authentication data is None
Check ttl enable
Vrrp accept mode enable
Out-interface(heartbeat line) is supervlan5
Tracked interface items: 1
Interface State Decrement-Priority
supervlan2 DOWN 25
Tracked detect items: 1
Track name: zte1 Track type: object Detect type: vrrp
Policy type: link
Track state: local-down
Admin-group is None
Vrrp run info:
State is Init
0 state changes, last state change 00:00:00
Current priority is 75
Master router is unknown
Master router address is 0.0.0.0
Master router priority is 0
Master Advertisement interval is 0.000 sec
Master Down interval is 3.707 sec, no learn
Output descriptions:
Decrement-Priority The priority decrement after the track interface is shut down
An example of the show vrrp interface vrid command output is shown below.
1-15
1-16
Configuration Thought
1. Enter the interfaces on which VRRP should be enabled and configure IP addresses.
2. Enter VRRP configuration mode from global configuration mode and then enter the
interfaces to configure VRRP.
3. Configure the same VRRP group ID and virtual addresses for S1 and S2. To make
S1 as the master switch, configure related commands on S1 first. When the priorities
(the default priority is 100) are the same, the switch on which VRRP is enabled first
and messages are advertised first will become the master switch in the group.
Configuration Commands
Configuration of S1:
S1(config)#interface vlan30
S1(config-if)#ip address 10.0.0.1 255.255.0.0
S1(config)#vrrp
S1(config-vrrp)#interface vlan30
S1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
Configuration of S2:
S2(config)#interface vlan30
S2(config-if)#ip address 10.0.0.2 255.255.0.0
S2(config)#vrrp
S2(config-vrrp)#interface vlan30
S2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
Configuration Verification
View the VRRP information and configuration result on S1, as shown below.
S1#show vrrp ipv4 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 1 255 1000 A P Master 10.0.0.1 10.0.0.1
1-17
1-18
Configuration Thought
1. Enter the interfaces on which VRRP should be enabled and configure IP addresses.
2. Enter VRRP configuration mode from global configuration mode and then enter the
interfaces to configure VRRP.
3. Configure VRRP Group 1 and corresponding virtual address on S1. Configure VRRP
Group 2 and corresponding virtual address on S2. Therefore, S1 becomes the master
switch in Group 1, and S2 becomes the master switch in Group 2. Add S1 to Group
2, and add S2 to Group 1, so S1 and S2 become the backup switches.
Configuration Commands
Configuration of S1,
S1(config)#interface vlan30
S1(config-if)#ip address 10.0.0.1 255.255.0.0
S1(config)#vrrp
S1(config-vrrp)#interface vlan30
S1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
S1(config-vrrp-if)#vrrp 2 ipv4 10.0.0.2
S1(config-vrrp-if)end
Configuration of S2,
S2(config)#interface vlan30
S2(config-if)#ip address 10.0.0.2 255.255.0.0
S2(config)#vrrp
S2(config-vrrp)#interface vlan30
S2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
S2(config-vrrp-if)#vrrp 2 ipv4 10.0.0.2
S2(config-vrrp-if)#end
Configuration Verification
View the VRRP information and configuration result on S1, as shown below.
1-19
1-20
Configuration Thought
1. Enter the interfaces on which VRRP should be enabled and configure IP addresses.
2. Enter VRRP configuration mode from global configuration mode and then enter the
interfaces to configure VRRP.
3. Configure the same VRRP group ID and virtual addresses for S1 and S2. To make S1
as the master router, configure related commands on S1 first. When the priorities (the
default priority is 100) are the same, the switch on which VRRP is enabled first and
messages are advertised first will become the master switch in the group.
4. In VRRP interface configuration mode, configure the same out-interface of the
heartbeat link in the VRRP group on S1 and S2.
Configuration Commands
Configuration of S1,
S1(config)#interface vlan30
S1(config-if)#ip address 10.0.0.1 255.255.0.0
S1(config)#vrrp
S1(config-vrrp)#interface vlan30
S1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
S1(config-vrrp-if)#vrrp 1 out-interface vlan40
S1(config-vrrp-if)#end
Configuration of S2,
S2(config)#interface vlan30
S2(config-if)#ip address 10.0.0.2 255.255.0.0
1-21
S2(config)#vrrp
S2(config-vrrp)#interface vlan30
S2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
S2(config-vrrp-if)#vrrp 1 out-interface vlan40
S2(config-vrrp-if)#end
Configuration Verification
View the VRRP information and configuration result on S1, as shown below.
S1#show vrrp ipv4 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 1 255 1000 A P Master 10.0.0.1 10.0.0.1
/*A: whether the router is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
1-22
Configuration Thought
1. Enter the interfaces on which VRRP will be configured and configure IP addresses on
the interfaces.
2. Enter VRRP configuration mode from global configuration mode, and then enter the
interface on which VRRP will be configured.
3. Configure the same VRRP group ID and virtual IP address for switch A and switch B.
To set switch A as the active switch, execute the above steps on switch A first. When
priorities (by default, the priority is 100) are the same, the switch on which VRRP is
configured first and advertise packets first will work as the active switch in the VRRP
group.
4. Enter VRRP configuration mode on switch A and switch B to configure tracks with the
same object name. And then enter VRRP interface configuration mode to enable track
of VRRP.
Configuration Commands
The configuration of switch A:
SA(config)#interface vlan30
SA(config-if)#ip address 10.0.0.1 255.255.0.0
SA(config)#vrrp
SA(config-vrrp)#interface vlan30
SA(config-vrrp-if)#vrrp 1 ipv4 10.0.0.3
1-23
The object named zte of the track should be configured in the SAMGR module in advance.
For the detailed configuration, please refer to the SAMGR Configuration chapter.
The configuration of switch B:
SB(config)#interface vlan30
SB(config-if)#ip address 10.0.0.2 255.255.0.0
SB(config)#vrrp
SB(config-vrrp)#interface vlan30
SB(config-vrrp-if)#vrrp 1 ipv4 10.0.0.3
SB(config-vrrp-if)#vrrp 1 track object zte peer-type
The object named zte of the track should be configured in the SAMGR module. For the
detailed configuration, please refer to the SAMGR Configuration chapter.
Configuration Verification
View the VRRP track information on switch A, as shown below.
SA#show vrrp ipv4 brief
Interface vrID Pri Time A P L State Master addr Vswitch addr
vlan30 1 100 1000 A P Master 10.0.0.1 10.0.0.3
/*A: whether the router is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
1-24
Configuration Thought
1. Enter the interfaces on which VRRP should be enabled. Enable IPv6 and configure
IPv6 addresses.
2. Enter VRRP configuration mode from global configuration mode and then enter the
interfaces to configure VRRP.
1-25
3. Configure the same VRRP group ID and virtual addresses for S1 and S2. To make
S1 as the master router, configure related commands on S1 first. When the priorities
(the default priority is 100) are the same, the router on which VRRP is enabled first
and messages are advertised first will become the master switch in the group.
Configuration Commands
Configuration of S1:
S1(config)#interface vlan30
S1(config-if)#ipv6 enable
S1(config-if)#ipv6 address link-local fe80::1:1
S1(config)#vrrp
S1(config-vrrp)#interface vlan30
S1(config-vrrp-if)#vrrp 1 ipv6 fe80::1:1
Configuration of S2:
S2(config)#interface vlan30
S2(config-if)#ipv6 enable
S2(config-if)#ipv6 address link-local fe80::1:2
S2(config)#vrrp
S2(config-vrrp)#interface vlan30
S2(config-vrrp-if)#vrrp 1 ipv6 fe80::1:1
Configuration Verification
View the VRRP information and configuration result on S1, as shown below.
S1(config-if)#show vrrp ipv6 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 1 255 1000 A P Master FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:1 :1
/*A: whether the switch is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
1-26
1-27
Configuration Thought
1. Enter the interfaces on which VRRP should be enabled. Enable IPv6 and configure
IPv6 addresses.
2. Enter VRRP configuration mode from global configuration mode and then enter the
interfaces to configure VRRP.
3. Configure VRRP Group 1 and corresponding virtual address on S1. Configure VRRP
Group 2 and corresponding virtual address on S2. Therefore, S1 becomes the master
switch in Group 1, and S2 becomes the master switch in Group 2 (note that use the
link-local address as the virtual address that uses FE80:: as prefix). Add S1 to Group
2, and add S2 to Group 1, so S1 and S2 become the backup switches.
Configuration Commands
Configuration of S1:
S1(config)#interface vlan30
S1(config-if)#ipv6 enable
S1(config-if)#ipv6 address link-local fe80::1:1
S1(config)#vrrp
S1(config-vrrp)#interface vlan30
S1(config-vrrp-if)#vrrp 1 ipv6 fe80::1:1
S1(config-vrrp-if)#vrrp 2 ipv6 fe80::1:2
Configuration of S2:
S2(config)#interface vlan30
S2(config-if)#ipv6 enable
S2(config-if)#ipv6 address link-local fe80::1:2
S2(config)#vrrp
S2(config-vrrp)#interface vlan30
S2(config-vrrp-if)#vrrp 1 ipv6 fe80::1:1
S2(config-vrrp-if)#vrrp 2 ipv6 fe80::1:2
Configuration Verification
View the VRRP information and configuration result on S1, as shown below.
S1#show vrrp ipv6 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 1 255 1000 A P Master FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:1 :1
vlan30 2 100 1000 P Backup FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:2 :2
/*A: whether the switch is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
S1#show vrrp interface vlan30
1-28
vlan30 - vrID 1
Vrrp configure info: /*VRRP configuration information*/
IP version 6, VRRP version 3
Virtual IP address is FE80:0:0:0:0:0:1:1
Virtual MAC address is 0000.5e00.0201
Advertise time is 1.000 sec
Configured priority is 100
Preemption enable, delay 0 secs
Authentication data is None
Check ttl enable
Vrrp accept mode enable
Out-interface(heartbeat line) is None
Tracked interface items: 0
Interface State Decrement-Priority
Tracked detect items: 0
Admin-group is None
Vrrp run info:
/*Running information of VRRP on current interface*/
State is Master /*VRRP running state*/
1 state changes, last state change 03:12:14
/*Number of state changes and time*/
Current priority is 255
/*current priority, the largest priority of the Owner is 255*/
Master router is local
Master router address is FE80:0:0:0:0:0:1:1
Master router priority is 255
Master Advertisement interval is 1.000 sec
Master Down interval is 3.003 sec, no learn
1-29
Configuration Thought
1. Enter the interfaces on which VRRP should be enabled. Enable IPv6 and configure
IPv6 addresses.
2. Enter VRRP configuration mode from global configuration mode and then enter the
interfaces to configure VRRP.
3. Configure the same VRRP group ID and virtual addresses for S1 and S2. To make
S1 as the master switch, configure related commands on S1 first. When the priorities
(the default priority is 100) are the same, the switch on which VRRP is enabled first
and messages are advertised first will become the master router in the group.
4. In VRRP interface configuration mode, configure the same out-interface of the
heartbeat link in the VRRP group on S1 and S2, and enable IPv6 on the heartbeat
link interface.
Configuration Commands
Configuration of S1:
S1(config)#interface vlan30
S1(config-if)#ipv6 enable
S1(config-if)#ipv6 address link-local fe80::1:1
S1(config)#interface vlan40
S1(config-if)#ipv6 enable
S1(config)#vrrp
S1(config-vrrp)#interface vlan30
S1(config-vrrp-if)#vrrp 1 ipv6 fe80::1:1
S1(config-vrrp-if)#vrrp 1 out-interface vlan40
Configuration of S2:
S2(config)#interface vlan30
S2(config-if)#ipv6 enable
S2(config-if)#ipv6 address link-local fe80::1:2
S2(config)#interface vlan40
1-30
S2(config-if)#ipv6 enable
S2(config)#vrrp
S2(config-vrrp)#interface vlan30
S2(config-vrrp-if)#vrrp 1 ipv6 fe80::1:1
S2(config-vrrp-if)#vrrp 1 out-interface vlan40
Configuration Verification
View the VRRP information and configuration result on S1, as shown below.
S1#show vrrp ipv6 b
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 1 255 1000 A P Master FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:1 :1
/*A: whether the switch is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
1-31
Configuration Commands
1. Enter the interfaces on which VRRP will be configured. Enable IPv6 and configure
IPv6 addresses on the interfaces.
2. Enter VRRP configuration mode from global configuration mode, and then enter the
interfaces on which VRRP will be configured.
3. Configure the same VRRP group ID and virtual IP address for switch A and switch B.
To set switch A as the active router, execute the above steps on switch A first. When
priorities (by default, the priority is 100) are the same, the router on which VRRP is
configured first and advertise packets first will work as the active router in the VRRP
group.
4. Enter VRRP configuration mode on switch A and switch B to configure tracks with the
same object name. And then enter VRRP interface configuration mode to enable track
of VRRP.
Configuration Commands
The configuration of switch A:
SA(config)#interface vlan30
SA(config-if)#ipv6 enable
SA(config-if)#ipv6 address link-local fe80::1:1
SA(config)#vrrp
SA(config-vrrp)#interface vlan30
1-32
Note:
The object named zte of the track should be configured in the SAMGR module in advance.
For the detailed configuration, please refer to the SAMGR Configuration.
Note:
The object named zte of the track should be configured in the SAMGR module. For the
detailed configuration, please refer to the SAMGR Configuration.
Configuration Verification
View the VRRP track information on switch A, as shown below.
SA#show vrrp ipv6 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan30 1 255 1000 A P Master FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:1 :1
/*A: whether the switch is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
ZXR10_R1#show bfd neighbors ip-brief
OurAddr NeighAddr LD RD Hold State Interface
FE80:0:0:0:0:0: 1234:0:0:0:0:0: 1 0 0 UP
1:1 1:2
/*OurAddr: local IP, NeighAddr: remote IP, LD: BFD local identifier
RD: BFD remote identifier
Hold: session holding period, in the unit of ms
State: BFD session state, Interface: BFD session interface*/
1-33
1-34
2-1
At present, MAC Ping supports CE1 ping CE2, PE1 ping PE2 and PE1 ping CE2. The
parameters of ping command used on CE devices and PE devices are different.
Take the examples of CE1 pinging CE2 and PE1 pinging PE2 to explain the procedure.
l CE1 pinging CE2
CE1 sends a ping request of MAC layer. The request contains the out-interface and
destination MAC of the ping request message. When CE2 receives this request
message, it will send a reply message. If CE1 can receive the reply message within
a period, the link layer is through.
l PE1 pinging PE2
PE1 sends a ping request of MAC layer. The request contains the destination MAC of
the ping request message, VPLS name and peer ID. When PE2 receives this request
message, it will send a reply message. If CE1 can receive the reply message within
a period, the link layer is through.
At present, MAC Trace supports track from CE1 to CE2, from PE1 to PE2 and from PE1
to CE2.
l CE1 to CE2
CE1 sends a trace request of MAC layer. If the link is through, corresponding MAC
addresses on interfaces of CE1, PE1, PE2 and CE2 will be recorded.
l PE1 to PE2
PE1 sends a trace request of MAC layer. If the link is through, corresponding MAC
addresses on interfaces of PE1 and PE2 will be recorded.
l PE1 to CE2
2-2
PE1 sends a trace request of MAC layer. If the link is through, corresponding MAC
addresses on interfaces of PE1, PE2 and CE2 will be recorded.
Command Function
ZXR10#mac-ping <destination-mac>{interface <out-port>| vpls <v This uses a private protocol to test
pls-name> peer <peer-address>}{summary | detail}{[external-vlan the connectivity to the destination
<external-vlan id> internal-vlan <internal-vlan id>]|[vlan <vlan on an Ethernet link.
id>]}[repeat <repeat-count>][timeout <timeout seconds>]
Parameter descriptions:
Parameter Description
repeat <repeat-count> Repeating times, in the range of 1-65535, with the default value 5
timeout <timeout seconds> The interval of timeout, in the range of 1-20, with the default value
2 seconds
Command Function
Parameter descriptions:
2-3
Parameter Description
Figure 2-2 MAC PING and MAC PING TRACE Configuration Example
Configuration Commands
1. Use MAC Ping on CE1 to test the connectivity of the link to CE2, as shown below.
CE1#mac-ping 00d0.d0c2.7d81 interface gei-0/1/1/1 detail
2-4
Or:
CE1#mac-ping 00d0.d0c2.7d81 interface gei-0/1/1/1 summary
sending 5,100-byte EOAM echos to 00d0.d0c2.7d81,timeout is
2 seconds.
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 0/8/40 ms.
2. Use MAC Ping on PE1 to test the connectivity of the link to CE2, as shown below.
PE1#mac-ping 00d0.d0c2.7d81 vpls zte peer 10.9.9.9 detail
sending 5,100-byte EOAM echos to 00d0.d0c2.7d81,timeout is
2 seconds.
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 0/0/0 ms.
Or:
PE1#mac-ping 00d0.d0c2.7d81 vpls zte peer 10.9.9.9 summary
sending 5,100-byte EOAM echos to 00d0.d0c2.7d81,timeout is
2 seconds.
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 0/0/0 ms.
3. Use MAC Trace on CE1 to test the connectivity of the link to CE2, as shown below.
CE1#l2trace 00d0.d0c2.7d81 interface gei_0/1/1/8
Starting L2 Trace to 00d0.d0c2.7d81
Codes: '!' - success, 'Q' - request not transmitted,
'*' - timeout, 'U' - unreachable,
'R' - downstream router but not target
2-5
2-6
3-1
The EFM can also enable remote loopback function to detect the packet loss caused by
the difference between the local receiving rate and the remote receiving rate or the link
fault.
EFM packets are low-speed protocol packets. The packets cannot be forwarded by
devices. Therefore, th EFM can only be applied on the direct connected device, see
Figure 3-1.
The packets cannot be forwarded across devices. The application environment is simple.
The EFM has accuracy requirements for detection. Two devices send keepalive packets
periodically to each other to keep successful protocol negotiation. Other functions of EFM
can be enabled after the successful negotiation.
When detecting an event, the EFM notifies the peer device through specific packets.
3-2
Parameter Description
Parameter Description
Parameter Description
<value> Timeout time for the loopback control, range: 1-10, default: 3 s.
3-3
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
For a description of the parameters in Step 10, refer to the following table:
Parameter Description
<win-value> Window value of error frame cycles, range: 1-65535, unit: million
frames, default: 1.
For a description of the parameters in Step 11, refer to the following table:
Parameter Description
For a description of the parameters in Step 12, refer to the following table:
3-4
Parameter Description
<fast-value> Time-out time of a link when the EFM supports the EFM supports
the quick detection, range: 3-200, unit: 100 ms, default: 50.
<fast-period> Interval of sending packets when the EFM supports the quick
detection, range: 1-10, unit: 100ms, default: 10.
For a description of the parameter in Step 13, refer to the following table:
Parameter Description
Parameter Description
Command Function
For a description of the parameters in the show command, refer to the following table:
Parameter Description
3-5
Status:
Parser :forward
Multiplexer :forward
Stable :no
Discovery :undone
Loopback :off
PDU max size :1518
PDU Revision :0
Unidirection :nonsupport
Remote DTE
-----------
Remote DTE does not exist.
For a description of the parameters in the execution result, refer to the following table:
PDU max size Maximum number of OAMPDU bytes supported by the DTE.
3-6
Configuration Flow
1. Configure the EFM function for the interface directly connecting to S2 on S1. To be
specific, enable the EFM switch and the link-monitor switch for the specified interface,
and enable the EFM function globally.
2. Configure the EFM function for the interface directly connecting to S1 on S2. To be
specific, enable the EFM switch and the link-monitor switch for the specified interface,
and enable the EFM function globally.
3. Run the show ethernet-oam discovery command on S1 and S2 to check the EFM
connection establishment between S1 and S2.
4. Run the show ethernet-oam link-monitor command on S1 and S2 to check the number
of link errors between S1 and S2.
Configuration Commands
Run the following commands on S1:
S1#configure terminal
S1(config)#efm
S1(config-efm)#interface gei-0/1/1/1
S1(config-efm-if-gei-0/1/1/1)#set ethernet-oam function enable
S1(config-efm-if-gei-0/1/1/1)#set ethernet-oam link-monitor function enable
S1(config-efm-if-gei-0/1/1/1)#exit
S1(config-efm)#set ethernet-oam oui S1
S1(config-efm)#set ethernet-oam function enable
S1(config-efm)#exit
3-7
Configuration Verification
1. Run the show ethernet-oam discovery command on S1 to check the negotiation result
of the EFM connection. The execution result is displayed as follows:
S1(config-efm)#show ethernet-oam gei-0/1/1/1 discovery
PortId 32: Ethernet Oam enable
Local DTE
----------
Config:
Mode :active
Period Time :10*(100ms)
Link time out :50*(100ms)
Remote DTE
-----------
Config:
Mode :active
Link Monitor :support
Unidirection :nonsupport
Remote Loopback :support
Mib Retrieval :nonsupport
PDU max size :1518
Remote OUI(hex) :5a-54-45 /*Remote OUI.*/
3-8
3-9
----------
Config:
Mode :active
Period Time :10*(100ms)
Link time out :50*(100ms)
Status:
Parser :forward
Multiplexer :forward
Stable :yes
Discovery :done
Loopback :off
PDU max size :1518
PDU Revision :2
Unidirection :nonsupport
Remote DTE
-----------
Config:
Mode :active
Link Monitor :support
Unidirection :nonsupport
Remote Loopback :support
Mib Retrieval :nonsupport
PDU max size :1518
Remote OUI(hex) :5a-54-45
Status:
Parser :forward
Multiplexer :forward
Stable :yes
Mac Address :1210.1210.1211
PDU Revision :1
4. Run the show ethernet-oam link-monitor command on S2 to check the number of link
errors. The execution result is displayed as follows:
S2(config)#show ethernet-oam gei-0/1/1/1 link-monitor
Link Monitoring of Port: 66
Link Monitoring enable
Error Symbol Period Event:
Symbol Window : 1(million symbols)
Error Symbol Threshold : 1
Error Symbols : 0
Local Total Error Symbols : 0
Remote Total Error Symbols : 0
Local Total Error Events : 0
3-10
Configuration Flow
1. Configure EFM for the interface of S1 connecting to S2 directly and enable EFM
globally.
3-11
2. Configure EFM for the interface of S2 connecting to S1 directly and enable EFM
globally.
3. After the EFM connection is established on S1 and S2, enable remote loopback on
S1.
4. Run the show ethernet-oam discovery command on S1 and S2 to check the EFM
connection establishment.
Configuration Commands
Run the following commands on S1:
S1#configure terminal
S1(config-efm)#interface gei-0/1/1/1
S1(config-efm-if-gei-0/1/1/1)#set ethernet-oam function enable
S1(config-efm-if-gei-0/1/1/1)#set ethernet-oam link-monitor function enable
S1(config-efm-if-gei-0/1/1/1)#exit
S1(config-efm)#set ethernet-oam oui S1
S1(config-efm)#set ethernet-oam function enable
S1(config-efm)#exit
Configuration Verification
On the link where the EFM connection is established, S1 sends packets (except OAMPDU)
to S2. When S2 receives the packets, it loops them back to S1 directly.
3-12
Configuration Flow
1. Complete the configuration in accordance with the description in the "EFM Connection
Establishment" section.
2. Configure the maximum value and window value for the link monitor event on the in-
terface to be monitored.
The monitor events include the error symbol period event, error frame event, error
frame period event, and error frame second event. This section uses the error frame
event as an example.
Configuration Commands
Run the following commands on R1:
R1#configure terminal
R1(config)#efm
R1(config-efm)#interface gei-0/1/1/1
R1(config-efm-if-gei-0/1/1/1)#set ethernet-oam link-monitor frame threshold 2 window 30
R1(config-efm-if-gei-0/1/1/1)#exit
R1(config-efm)#
Configuration Verification
Run the show ethernet-oam link-monitor command on R1 to check the number of error
frames on the link. The execution result is displayed as follows:
R1(config)#show ethernet-oam gei-0/1/1/1 link-monitor
Link Monitoring of Port: 32
Link Monitoring enable
Error Symbol Period Event:
Symbol Window : 1(million symbols)
Error Symbol Threshold : 1
Error Symbols : 1
Local Total Error Symbols : 0
Remote Total Error Symbols : 0
Local Total Error Events : 0
Remote Total Error Events : 0
Error Frame Event:
Frame Window : 30(s)
Error Frame Threshold : 2
3-13
Error Frames : 1
Local Total Error Frames : 0
Remote Total Error Frames : 0
Local Total Error Events : 0
Remote Total Error Events : 0
Error Frame Period Event:
Period Window : 1(ten thousand frames)
Error Frame Threshold : 1
Error Frames : 1
Local Total Error Frames : 0
Remote Total Error Frames : 0
Local Total Error Events : 0
Remote Total Error Events : 0
Error Frame Seconds Event:
Error Seconds Window : 1(s)
Error Seconds Threshold : 1(s)
Error Frame Seconds : 1(s)
Local Total Error Frame Seconds : 0(s)
Remote Total Error Frame Seconds : 0(s)
Local Total Error Frame Seconds Events : 0
Remote Total Error Frame Seconds Events : 0
3-14
l Fault detection: An MEP sends and receives Continuity Check Messages (CCMs)
periodically to detect the connectivity of the network. It can discover connectivity
failures and non-consensual connectivity (situations of wrong connections).
l Fault confirmation and isolation: This function belongs to the management behavior.
Network administrators confirm the faults through Loopback Messages (LBMs) or
Loopback Replies (LBRs), and then isolate the faults.
4-1
l Path discovery: An MEP uses Linktrace Messages (LTMs) or Linktrace Replies (LTRs)
to discover paths and trace the path from an MEP to another MEP or the path between
Maintenance domain Intermediate Points (MIPs).
CFM Principle
CFM can check, isolate, and report connectivity faults in VLANs effectively.
To manage and maintain the network, network administrators make a plan for the network
services and levels, and divide the entire network into several MDs. For the sketch map
of an MD, see Figure 4-1.
A series of ports are defined for the edge devices and the internal device, see Figure 4-1.
l The gray points on the edge devices are the services ports connecting to devices
outside the domain. These points are defined as MEPs.
l The black points on the devices (including the internal device) are ports connecting to
devices inside the domain. These points are defined as MIPs.
The management function is implemented through the MEPs and MIPs.
A network can be divided into user domain, provider domain, and operator domain. Each
domain is specified to a level. There are levels from 0 to 7. The level of a domain decides
the inclusion relation of domains. A domain of a higher level may include domains of lower
levels. However, a domain of a lower level cannot include a domain of a higher level. The
domains of the same level cannot include each other. Therefore, the domain of the largest
range has the highest level. The inclusion relation of domains can be tangent (internally
tangent or externally tangent) and inclusive, but it cannot be intersecting.
The main target of CMF is the networks of service operators. CFM is also effective for
Customer VLANs (C-VLANs). IEEE 802.1ag standard defines the following mechanism:
4-2
4-3
Parameter Description
Parameter Description
Parameter Description
4-4
Parameter Description
<ma-name> Integer. The MA name should be the bound vlan during the MA
configuration.
<vlan-id> Primary VID bound to the MA, default: 0, identifying that the MA
does not include any VLAN.
When a switch creates an MA, the vlan-id must be included.
Parameter Description
Parameter Description
Parameter Description
4-5
Parameter Description
<mepid > MEP ID, range: 1-8191. The MEP ID in the MA should be unique,
including the local MEP and the remote MEP.
For a description of the parameters in Step 10, refer to the following table:
Parameter Description
For a description of the parameters in Step 11, refer to the following table:
Parameter Description
<mepid > MEP ID, range: 1-8191, used for local MEP and remote MEP.
For a description of the parameters in Step 12, refer to the following table:
Parameter Description
<enable> Enables the CCM packet sending function of the local MEP.
<disable> Disables the CCM packet sending function of the local MEP.
For a description of the parameters in Step 13, refer to the following table:
Parameter Description
For a description of the parameter in Step 14, refer to the following table:
Parameter Description
For a description of the parameters in Step 15, refer to the following table:
Parameter Description
md MD.
4-6
Parameter Description
ma MA.
<tlv-length> Length of the Data TLV field carried by the LBM, optional, range:
1–400. If this parameter is not configured, it means that the LBM
does not carry the Data TLV field.
<timeout> Time of waiting for an LBR after an LBM is sent, range: 1–10,
default: 5 s.
For a description of the parameters in Step 16, refer to the following table:
Parameter Description
md MD.
ma MA.
<timeout> Times of each hop waiting for an LTR after an LTM is sent, range:
5–10, default: 5 s.
4-7
Command Function
Parameter Description
The following is sample output from the show cfm status command (checking the CFM
global state):
ZXR10#show cfm status
CFM enabled
CFM version:0
For a description of the parameters in the execution result, refer to the following table:
The following is sample output from the show cfm md all command:
ZXR10#show cfm md all
MD index 1
name format/name: 2(Base string)/md8
level: 7
contain MA numbers:1
4-8
For a description of the parameters in the execution result, refer to the following table:
The following is sample output from the show cfm ma all md 1 command:
For a description of the parameters in the execution result, refer to the following table:
Contained MEP numbers Number of MEPs (including local MEP and RMEP) created in
an MA.
4-9
Configuration Flow
1. Create MDs and MAs on S1 and S2. The MDs have the same ID and name, and the
MAs have the same ID and name. Enable the CFM function globally.
2. Create local MEPs for the directly connected interfaces of S1 and S2. The MEPs are
of the same level. Use the peer MAC and MEP ID to create RMEPs on S1 and S2.
Enable the local MEP, CCM sending and RMEP.
3. Run the show cfm mp command on S1 and S2 to check the MEP identification bit to
check the CFM connection establishment of S1 and S2.
Configuration Commands
Run the following commands on S1:
S1#configure terminal
S1(config)#cfm
S1(config-cfm)#set cfm enable
S1(config-cfm)#create md index 1 name-format 2 name md1 level 1
S1(config-cfm)#md index 1
S1(config-cfm-md)#create ma index 1 name-format 2 name ma1 vid 100
S1(config-cfm-md)#ma index 1
S1(config-cfm-ma)#create mep mepid 1 direction down interface gei-0/1/1/1
S1(config-cfm-ma)#set ccminterval 1 /*fast detection*/
S1(config-cfm-ma)#set mep 1 state enable
S1(config-cfm-ma)#set mep 1 ccm-send enable
S1(config-cfm-ma)#create rmep mepid 2 remote-mac 00ee.ff10.2000
S1(config-cfm-ma)#set mep 2 state enable
S1(config-cfm-ma)#end
4-10
S2(config)#cfm
S2(config-cfm)#set cfm enable
S2(config-cfm)#create md index 1 name-format 2 name md1 level 1
S2(config-cfm)#md index 1
S2(config-cfm-md)#create ma index 1 name-format 2 name ma1 vid 100
S2(config-cfm-md)#ma index 1
S2(config-cfm-ma)#create mep mepid 2 direction down interface gei-0/1/1/1
S2(config-cfm-ma)#set ccminterval 1
S2(config-cfm-ma)#set mep 2 state enable
S2(config-cfm-ma)#set mep 2 ccm-send enable
S2(config-cfm-ma)#create rmep mepid 1 remote-mac 00ee.ff10.1000
S2(config-cfm-ma)#set mep 1 state enable
S2(config-cfm-ma)#end
Configuration Verification
1. Run the show cfm mp all md 1 ma 1 command on S1 to check the link information. The
execution result is displayed as follows:
RP1(config)#show cfm mp all md 1 ma 1
MP type : Local MEP
Direction : down
MEPID : 1
MEPIndex : 1
Level : 1
Primary VID : 100
Assign port : gei-0/1/1/1
Priority : 7
LowestAlarmPriority : 1
Client level : 7
Admin state : enable
CCM state/interval : enable/3.3ms
AIS state/interval : disable/1s
LCK state/interval : disable/1s
DM state : disable
LM state : disable
-------------------------------------------------------------------
PresentRDI : 0 MADefectIndication : 0
SomeRDIDefect : 0 SomeRMEPCCMDefect : 0
ErrorCCMDefect : 0 UnexpectedLevelDefect : 0
UnexpectedPeriodDefect : 0 UnexpectedMACDefect : 0
UnexpectedMEPIDDefect : 0 XconCCMDefect : 0
AISRcvdFlag : 0 LCKRcvdFlag : 0
--------------------------------------------------------------------
TotalSendCCMs : 0 TotalRcvdCCMs : 0
RightRcvdCCMs : 0 DefErrorCCMs : 0
4-11
DiscardCCMs : 0 DefXconCCMs : 0
TotalSendLBMs : 0 TotalRcvdLBRs : 0
TotalRcvdLBMs : 0 TotalSendLBRs : 0
---------------------------------------------------------------------
4-12
Client level : 7
Admin state : enable
CCM state/interval : enable/3.3ms
AIS state/interval : disable/1s
LCK state/interval : disable/1s
DM state : disable
LM state : disable
------------------------------------------------------------------
PresentRDI : 0 MADefectIndication : 0
SomeRDIDefect : 0 SomeRMEPCCMDefect : 0
ErrorCCMDefect : 0 UnexpectedLevelDefect : 0
UnexpectedPeriodDefect : 0 UnexpectedMACDefect : 0
UnexpectedMEPIDDefect : 0 XconCCMDefect : 0
AISRcvdFlag : 0 LCKRcvdFlag : 0
-------------------------------------------------------------------
TotalSendCCMs : 0 TotalRcvdCCMs : 0
RightRcvdCCMs : 0 DefErrorCCMs : 0
DiscardCCMs : 0 DefXconCCMs : 0
TotalSendLBMs : 0 TotalRcvdLBRs : 0
TotalRcvdLBMs : 0 TotalSendLBRs : 0
-------------------------------------------------------------------
4-13
LMMTotalFrameLossRemote : 0 DLMTotalFrameLossRemote : 0
LMMTotalFrameLossLocal : 0 DLMTotalFrameLossLocal : 0
LMMFrameLossRatioRemote : 0.000000 DLMFrameLossRatioRemote : 0.000000
LMMFrameLossRatioLocal : 0.000000 DLMFrameLossRatioLocal : 0.000000
------------------------------------------------------------------------
Configuration Flow
1. Create MDs and MAs on PE1 and PE2. The MDs have the same ID and name, and
the MAs have the same ID and name.
2. Configure the UP MEP for the interfaces on the AC side of PE1 and PE2 separately,
and the MIP for the interfaces on the public network side of PE1 and PE2.
3. PE1 performs the cfm linktrace and cfm loopback operations on MIP and MEP of PE2
to check the link connection.
Configuration Commands
Run the following commands on PE1:
PE1#configure terminal
PE1(config)#cfm
PE1(config-cfm)#set cfm enable
PE1(config-cfm)#create md index 1 name-format 2 name MD1 level 4
PE1(config-cfm)#md index 1
PE1(config-cfm-md)#create ma index 1 name-format 2 name MA1
PE1(config-cfm-md)#ma index 1
PE1(config-cfm-ma)#create mep mepid 1 direction up interface gei-0/1/1/3
PE1(config-cfm-ma)#set mep 1 stat en
PE1(config-cfm-ma)#set mep 1 ccm en
PE1(config-cfm-ma)#create rmep mepid 2 remote 00ee.efab.ede3
4-14
Configuration Verification
PE1 performs the cfm linktrace and cfm loopback operations on PE2. If the link is normal,
the response to the trace and ping operations are correct. If the link status changes from
abnormal to normal, the corresponding alarms are generated on both PE1 and PE2.
4-15
4-16
l Device reliability
l Link reliability
l Network reliability
On the bearer network, the requirement for network device availability is 99.999%, that is,
the time for maintenance of a stop-running device due to faults caused by various reasons
during continuous running in a whole year is only about 5 minutes. High reliability is a
basic requirement of a carrier class device, and it is a basic requirement of operators to
construct networks. The basic network works as the bearer body of various services, so
its reliability is becoming a focus.
On a switch or a Packet Transport Network (PTN) device, reliability technology includes
device hardware redundancy and network reliability technology. Here introduces network
reliability technology.
Network reliability technology includes network fault detection technology and protection
switching technology.
On different network layers, network fault detection technology has the following detection
mechanisms.
5-1
SAMGR Principle
l SAMGR Working Principle
In practical applications, switches support several detection technologies. The
protection switching applications also need to monitor the real-time detection state
to meet the reliability requirements in different network structures. Therefore,
the SAMGR is introduced to implement the linkage between various detection
technologies and services.
The SAMGR isolates detection technologies from services, and reduces the coupling
between modules. The working principles are as follows:
At the same time, the SAMGR also can manage the binding relation between racks
and send the local state to the remote end. In this way, fault transmission and recovery
is accomplished.
5-2
5-3
5-4
5-5
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
5-6
Parameter Description
Parameter Description
Parameter Description
{aal1|aal2|atm-aal5|atm-cell PW type
|atm-vcc|atm-vpc|cem|ceop|
cesopsn-basic | cesopsn-cas |
hdlc | e1 |e3| ether | ether-vlan |
fr-dlci-martini | fr-dlci | fr-port |
ip | ppp | t1 |t3}
Parameter Description
<ifname> The name of the interface on which the VRRP group is configured
Parameter Description
5-7
Parameter Description
Parameter Description
<trackname> The name of the track object added to the track group
Parameter Description
<1-10> Track group policy that describes the number of down tracks that
will results in the track group down
Parameter Description
track<name> The name of the passive track object, that is, the name of the
track object that receives state transmission
5-8
Parameter Description
{track | track-group}<name> The name of the active track object or track group, that is,
the name of the track object or track group that starts state
transmission
Command Function
Output descriptions:
5-9
5-10
Output descriptions:
Active track Whether to work as an active track to send state to the passive
track
Passive track Whether to work as a passive track to receive the state sent by
the active track
old state The original state of the track object before the state is changed.
new state The current state of the track object after the state is changed.
5-11
Output descriptions:
Track name Name of track objects that are bound to the track group
old state The original state of the track group before the state is changed.
new state The current state of the track group after the state is changed.
5-12
Configuration Thought
1. Configure an EFM connection on the direct-connected interfaces of the link between
S1 and S2.
2. Configure a track object of which the detection type is EFM on the direct-connected
interface of S2 in SAMGR configuration mode.
3. Configure the same VRRP group number and virtual address on S2 and S3. To make
S2 work as a master switch, bind VRRP on S2 to the track object of EFM.
4. Disable EFM on S1, the VRRP on S2 becomes Init state, and the VRRP on S3
becomes Backup state. Enable EFM on S1, the VRRP on S2 becomes Master state,
and the VRRP on S3 becomes Backup state.
Configuration Commands
The configuration of S1:
S1(config)#efm
S1(config-efm)#set ethernet-oam function enable
S1(config-efm)#interface gei-0/1/1/1
S1(config-efm-if)#set ethernet-oam function enable
S1(config-efm-if)#exit
5-13
S2(config-swvlan)#exit
S2(config)#interface vlan10
S2(config-if)#ip address 192.168.0.1 255.255.0.0
S2(config-if)#exit
S2(config)#efm
S2(config-efm)#set ethernet-oam function enable
S2(config-efm)#interface gei-0/1/1/1
S2(config-efm-if)#set ethernet-oam function enable
S2(config-efm-if)#exit
S2(config-efm)#exit
S2(config)#samgr
S2(config-samgr)#track efm efm interface gei-0/1/1/1
S2(config-samgr)#exit
S2(config)#vrrp
S2(config-vrrp)#interface vlan20
S2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
S2(config-vrrp-if)#vrrp 1 out-interface vlan10
S2(config-vrrp-if)#vrrp 1 track object efm link-type
S2(config-vrrp-if)#exit
S3(config)#switchvlan-configuration
S3(config -swvlan)#interface gei-0/1/1/1
S3(config-swvlan-intf)#sw trunk vlan 20
S3(config-swvlan-intf)#exit
S3(config-swvlan)#exit
S3(config)#interface vlan20
S3(config-if)#ip address 10.0.0.2 255.255.0.0
S3(config-if)#exit
S3(config)#switchvlan-configuration
S3(config -swvlan)#interface gei-0/1/1/2
S3(config-swvlan-intf)#sw trunk vlan 10
S3(config-swvlan-intf)#exit
S3(config-swvlan)#exit
S3(config)#interface vlan10
S3(config-if)#ip address 192.168.0.2 255.255.0.0
S3(config-if)#exit
S3(config)#vrrp
S3(config-vrrp)#interface vlan20
S3(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
S3(config-vrrp-if)#vrrp 1 out-interface vlan10
S3(config-vrrp-if)#end
5-14
Configuration Verification
Check the VRRP configuration results on S2 and S3. The results show that S2 is a master
router and S3 is a bBackup router. The output of the show samgr command on S2 shows
that the EFM track object is in up state.
S2#show vrrp ipv4 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan20 1 100 1000 P Master 10.0.0.1 10.0.0.1
S2#show samgr brief
The total of track at this Router is 1.
============================================================================
Track-name Detect-type App-num State
efm efm 1 up
When EFM is disabled on S1, the VRRP becomes Init from Master on S2, and the VRRP
becomes Master on S3. The output of the show samgr command on S2 shows that the
EFM track object is in loacl down state.
S1(config)#efm
S1(config-efm)#set ethernet-oam function disable
When EFM is enabled on S1 again, the VRRP on S2 becomes Master, and the VRRP on
S3 becomes Backup. The EFM track object is in up state on S2.
S1(config)#efm
S1(config-efm)#set ethernet-oam function enable
5-15
Configuration Thought
1. Configure CFM on the direct-connected interfaces of the link between S1 and S2.
2. Configure a track object of which the detection type is CFM on the direct-connected
interface of S2 in SAMGR configuration mode.
3. Configure the same VRRP group number and virtual address on S2 and S3. To make
S2 work as a master router, bind VRRP on S2 to the track object of CFM.
4. Disable CFM on S1, the VRRP on S2 becomes Init state, and the VRRP on S3
becomes Backup state. Enable CFM on S1, the VRRP on S2 becomes Master state,
and the VRRP on S3 becomes Backup state.
Configuration Commands
The configuration of S1:
S1(config)#cfm
S1(config-cfm)#set cfm enable
S1(config-cfm)#create md index 2 name-format 2 name md2 level 7
S1(config-cfm)#md index 2
5-16
5-17
Configuration Verification
Check the VRRP configuration results on S2 and S3. The results show that S2 is a master
router and S3 is a bBackup router. The output of the show samgr command on S2 shows
that the CFM track object is in up state.
S2#show vrrp ipv4 brief
Interface vrID Pri Time A P L State Master addr VRouter addr
vlan20 1 100 1000 P Master 10.0.0.1 10.0.0.1
S2(config-samgr)#show samgr brief
The total of track at this Router is 1.
============================================================================
Track-name Detect-type App-num State
cfm cfm 1 up
5-18
When CFM is disabled on S1, the VRRP becomes Init from Master on S2, and the VRRP
becomes Master on S3. The output of the show samgr command on S2 shows that the
CFM track object is in loacl down state.
S1(config)#cfm
S1(config-cfm)#set cfm disable
When CFM is enabled on S1 again, the VRRP on S2 becomes Master, and the VRRP on
S3 becomes Backup. The CFM track object is in up state on S2.
S1(config)#cfm
S1(config-cfm)#set cfm enable
5-19
5-20
BFD provides a solution to the above problem. BFD protocol can detect failures on any
types of paths between adjacent systems, including direct-connected physical link, virtual
circuit, tunnel, MPLS LSP, multi-hop routing channel, and indirect-connected tunnel.
Because of its simpleness and unitary, BFD can focus on fast detection of forwarding
failures. It helps networks to implement transmission of voice, video, and other services
with good Quality of Service (QoS), thus helps service providers to provide real-time
services (such as Voice over Internet Protocol (VoIP) on the base of IP network.
BFD Principle
BFD is a simple Hello protocol. It is similar to the Hello mechanisms of routing protocols.
BFD is simpler and universal. The two systems that establish a BFD session send packets
to each other periodically. If one system does not receive any packet from the peer in a
specific period, it considers that there is a failure on the communication path. The BFD
session will be down, and BFD will inform the upper layer protocol to select another path.
To reduce the loads of devices, some special application modes are designed in BFD. In
these modes, devices can reduce the number of BFD packets sent to the peers; or it is
unnecessary for the devices to send BFD packets periodically. The devices can send the
packets only when it is necessary.
BFD protocol aims at fast failure detection (including failures on interfaces, data links, and
even forwarding engines) on a bidirectional tunnel between forwarding engines. Another
aim is to provide a single detection mechanism that can be applied to any type of medium
and any protocol layer. BFD detects failures in the forwarding engines between a device
and the next hop. It is likely to work in some parts of a system forwarding engine. The
6-1
forwarding engine and the control engine are isolated. This not only binds the protocol to
the forwarding plane, but also isolates the protocol from the routing protocol engine (control
plane). Therefore, BFD can take effect in non-interrupt forwarding and run in the control
engine.
BFD provides failure detection between systems, including direct connected physical links,
virtual links, tunnels, MPLS LSPs, and multi-hop routing paths.
Parameter Description
<src-ip-address> Source IP address used for establishing the BFD session. The
source IP address must be a local IP address.
6-2
Parameter Description
Command Function
Parameter Description
During the static route configuration, you need to confirm the unique link to the destination
and enable BFD for this link by running the bfd enable command.
6-3
You can enable BFD for the interface that uses the IS-IS protocol. When the IS-IS neighbor
relationship is established between this interface and the peer interface, a BFD session
based on the IS-SI protocol is generated on the link that connects these two interfaces
directly.
If the BGP neighbor is directly connected, configure a single-hop BFD detection mode; If
the BFP neighbor is not directly connected, configure a multihop BFD detection mode.
6-4
2 ZXR10(config-ldp)#bfd <FEC address><mask Configures the BFD function for the LSP
length> interval <interval> min-rx < min-rx> generated by the LDP protocol, and
multiplier <multiplier>[ source <ip-address>] creates a BFD session for the LSP.
The LDP BFD session only needs to be configured locally. During the configuration, a
reverse LDP BFD session is established automatically after you specify the address of the
remote LSP.
For a description of the parameters in Step 2, refer to the following table:
Parameter Description
<FEC address> Specifies the LSP address that is used to establish a BFD session.
In general, it is a remote IP address.
<mask length> Specifies the length of the sub-net mask of the remote IP address,
range: 0-32.
Command Function
Command Function
6-5
Parameter Description
Command Function
Parameter Description
<ld> Configures the local identifier for the BFD session, range: 1-2048.
<rd> Configures the remote identifier for the BFD session, range:
1-2048.
Command Function
Command Function
6-6
Command Function
Command Function
ZXR10#debug bfd byte Displays the information about sent and received
link establishment packets when a BFD session
is established (packets in the UDP data area).
ZXR10#show bfd neighbors ip detail Displays the detailed information about a BFD
session whose type is IP.
ZXR10#show bfd neighbors ip brief Displays the brief information about a BFD
session whose type is IP.
ZXR10#show bfd neighbors ldp brief Displays the brief information about a BFD
session whose type is LDP.
ZXR10#show bfd neighbors ldp detail Displays the detailed information about a BFD
session whose type is LDP.
ZXR10#show bfd neighbors rsvp {lsp | passive } brief Displays the brief information about a BFD
session whose type is LDP.
ZXR10#show bfd neighbors rsvp {lsp | passive } Displays the detailed information about a BFD
detail session whose type is RSVP.
ZXR10#show bfd neighbors pw brief Displays the brief information about a BFD
session whose type is PW.
6-7
Command Function
ZXR10#show bfd neighbors pw detail Displays the detailed information about a BFD
session whose type is PW.
ZXR10#show bfd neighbors local-disc Displays the detailed information about a BFD
session in accordance with the local disc.
Configuration Flow
1. Establish the IS-IS neighbor relationship between S1 and S2.
2. Enable BFD for interfaces of S1 and S2.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#router isis
S1(config-isis-0)#area 49.0172
S1(config-isis-0)#system-id 0020.0096.0001
S1(config-isis-0)#interface vlan1
S1(config-isis-0-if-vlan1)#ip router isis
S1(config-isis-0-if-vlan1)#bfd-enable
S1(config-isis-0-if-vlan1)#end
6-8
S2(config)#interface vlan2
S2(config-if-vlan2)#ip address 172.20.130.214 255.255.255.0
S2(config-if-vlan2)#exit
S2(config)#router isis
S2(config-isis-0)#area 49.0172
S2(config-isis-0)#system-id 0020.0096.0002
S2(config-isis-0)#interface vlan2
S2(config-isis-0-if-vlan2)#ip router isis
S2(config-isis-0-if-vlan2)#bfd-enable
S2(config-isis-0-if-vlan2)#end
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the ISIS-BFD
session is established successfully on S1. The execution result is displayed as follows:
S1(config)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State interface
172.20.130.213 172.20.130.214 1 3 150 UP vlan1
Registered Protocols:ISIS
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
6-9
Configuration Flow
1. Establish the OSPF neighbor relationship between S1 and S2.
2. Enable the BFD function for interfaces of S1 and S2.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#router ospf 1
S1(config-ospf-1)#network 172.20.130.0 0.0.0.255 area 0.0.0.0
S1(config-ospf-1)#bfd area 0
S1(config-ospf-1)#end
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the OSPF BFD
session is established successfully on S1. The execution result is displayed as follows:
S1(config)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
172.20.130.213 172.20.130.214 3 3 150 UP vlan1
6-10
Registered Protocols:OSPF
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
Configuration Flow
1. Configure the IP address for the interfaces of S1 and S2.
2. Configure the RIP protocol
3. Enable the configuration related to the RIP protocol for the interfaces.
4. Test the configuration result to confirm that the neighbor relationship is established
between two devices and the notify route can be learnt from each other.
5. Enable the BFD function in RIP mode.
6-11
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 192.168.1.1 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface vlan2
S1(config-if-vlan2)#ip address 10.1.0.1 255.255.255.0
S1(config-if-vlan2)#exit
S1(config)#router rip
S1(config-rip)#network 192.168.1.0 0.0.0.255
S1(config-rip)#network 10.1.0.0 0.0.0.255
S1(config-rip)#bfd
S1(config-rip)#exit
Configuration Verification
After the above configuration, when the following information is displayed on both ends
of the device, it means that the neighbor relationship is successfully established between
two parties, and the route of the peer end can be successfully learnt and pinged.
Run the show running-config rip command to check whether the RIP configuration is
correct on S1. The execution result is displayed as follows:
S1(config-rip)#show running-config rip
!<rip>
router rip
bfd
network 192.168.1.0 0.0.0.255
network 10.1.0.0 0.0.0.255
$
!</rip>
6-12
Registered Protocols:RIP
Uptime:0 day(s),0 hour(s),3 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
Run the show running-config rip command to check whether the RIP configuration is
correct on S2. The execution result is displayed as follows:
S2(config)#show running-config rip
!<rip>
router rip
bfd
6-13
Registered Protocols:RIP
Uptime:0 day(s),0 hour(s),5 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
6-14
Configuration Flow
1. Establish the BGP neighbor relationship between S1 and S2.
2. Enable the BFD function for interfaces of S1 and S2.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.0
S1(config-if-vlan1)#exit
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the BGP BFD
session is established successfully on S1. The execution result is displayed as follows:
S1(config-bgp)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
6-15
Registered Protocols:BGP
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
Configuration Flow
1. Configure the protocol for each route.
2. Enable the BFD function in protocol interface mode or for the specific destination route.
6-16
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 100.1.1.1 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 1.1.1.211 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#router ospf 1
S1(config-ospf-1)#network 100.1.1.0 0.0.0.255 area 0
S1(config-ospf-1)#network 1.1.1.211 0.0.0.0 area 0
S1(config-ospf-1)#exit
S2(config)#router ospf 1
S2(config-ospf-1)#network 100.1.1.0 0.0.0.255 area 0
S2(config-ospf-1)#network 200.1.1.0 0.0.0.255 area 0
S3(config)#router ospf 1
6-17
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail ] command to check whether the BFD session
is established successfully on S1. The execution result is displayed as follows:
S1#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
1.1.1.211 1.1.1.213 56 57 150 UP vlan1
LocalAddr:1.1.1.211
PeerAddr :1.1.1.213
Local Discr: 56 Remote Discr:57 State:UP
Holdown(ms):150 Interface:---
Vpnid:0 VRF Name:---
BFD Type:MultiHop
Instance Name:1
----------------------------------------------------------------------------
Version:1 Dest UDP Port:4784 Final Bit:1
Local Diag:0 Demand Mode:0 Poll Bit:1
MinTxInt:50 MinRxInt:50 Multiplier:3
Received MinTxInt:50 Received MinRxInt:50 Received Multiplier:3
Length:24 Min Echo Interval:0
Min BFD Length:24 Max BFD Length:24
6-18
Configuration Flow
1. Run the static route protocol between S1 and S2.
2. Configure the BFD function for the static route of S1 and S2.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 172.20.96.1 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#ip route 172.20.108.1 255.255.255.255 172.20.130.214 bfd enable
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the static route
BFD session is establish successfully on S1. The execution result is displayed as follows:
S1(config)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
172.20.130.213 172.20.130.214 5 32 150 UP vlan1
6-19
Holdown(ms):150 Interface:---
Vpnid:0 VRF Name:---
BFD Type:SingleHop
Instance Name:
----------------------------------------------------------------------------
Version:1 Dest UDP Port:4784 Final Bit:1
Local Diag:0 Demand Mode:0 Poll Bit:1
MinTxInt:50 MinRxInt:50 Multiplier:3
Received MinTxInt:50 Received MinRxInt:50 Received Multiplier:3
Length:24 Min Echo Interval:0
Min BFD Length:24 Max BFD Length:24
Configuration Flow
1. Configure the IP address for the corresponding interfaces.
2. Enter multicast configuration mode.
3. Enter PIM configuration mode.
4. Set the loopback5 interface of S2 to CRP and BSR.
5. Enter PIM-SM interface configuration mode.
6. Enable the BFD function in PIM-SM interface configuration mode.
6-20
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 199.1.1.1 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface vlan2
S1(config-if-vlan2)#ip address 33.1.1.1 255.255.255.0
S1(config-if-vlan2)#exit
S1(config)#ip multicast-routing
S1(config-mcast)#router pim
S1(config-mcast-pim)#interface vlan1
S1(config-mcast-pim-if-vlan1)#pimsm
S1(config-mcast-pim-if-vlan1)#bfd-enable
S1(config-mcast-pim-if-vlan1)#exit
S1(config-mcast-pim)#interface vlan2
S1(config-mcast-pim-if-vlan2)#pimsm
S1(config-mcast-pim-if-vlan2)#dr-priority 20
S1(config-mcast-pim-if-vlan2)#exit
S2(config)#ip multicast-routing
S2(config-mcast)#router pim
S2(config-mcast-pim)#interface vlan1
S2(config-mcast-pim-if-vlan1)#pimsm
S2(config-mcast-pim-if-vlan1)#bfd-enable
S2(config-mcast-pim-if-vlan1)#exit
S2(config-mcast-pim)#interface vlan2
S2(config-mcast-pim-if-vlan2)#pimsm
S2(config-mcast-pim-if-vlan2)#dr-priority 20
S2(config-mcast-pim-if-vlan2)#exit
6-21
Configuration Verification
Run the show ip pim interface command to check the interface status on S1. The execution
result is displayed as follows:
S1(config)#show ip pim interface
Address Interface State Nbr Hello DR DR PIM Mode
Count Period Priority Silent
33.1.1.1 vlan2 Up 0 30 20 33.1.1.1 Disabled S
199.1.1.1 vlan1 Up 1 30 1 199.1.1.2 Disabled D
Run the show ip pim neighbor command to check the neighbor status on S1. The execution
result is displayed as follows:
S1(config)#show ip pim neighbor
Neighbor Address Interface DR Priority Uptime Expires Ver
199.1.1.2 vlan1 1 00:07:48 00:01:23 V2
Run the show bfd neighbor ip brief command to check the BFD status on S1. The execution
result is displayed as follows:
S1(config)#show bfd neighbor ip brief
LocalAddr PeerAddr LD RD Hold State Interface
199.1.1.1 199.1.1.2 2053 2054 150 UP vlan1
Registered Protocols:PIM
Uptime:0 day(s),0 hour(s),6 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
Run the show ip pim neighbor command to check the neighbor status on S2. The execution
result is displayed as follows:
S2(config)#show ip pim neighbor
6-22
Run the show bfd neighbor ip brief command to check the BFD status on S2. The execution
result is displayed as follows:
S2(config)#show bfd neighbor ip brief
LocalAddr PeerAddr LD RD Hold State Interface
199.1.1.2 199.1.1.1 2055 2054 150 UP vlan1
Registered Protocols:PIM
Uptime:0 day(s),0 hour(s),1 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
6-23
Configuration Flow
1. Enable the LDP function for S1 and S2.
2. Set the IP address of the loopback interface as the ID of the LSR.
3. Enable the MPLS hop-by-hop forwarding function for the link between S1 and S2.
4. The LDP BFD configuration is performed on one end. Set S1 as the active party, and
configure the LDP BFD session for S1.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 172.20.96.1 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#router ospf 1
S1(config-ospf-1)#network 172.20.130.0 0.0.0.255 area 0.0.0.0
S1(config-ospf-1)#network 172.20.96.1 0.0.0.0 area 0.0.0.0
S1(config-ospf-1)#end
S2(config)#router ospf 1
S2(config-ospf-1)#network 172.20.130.0 0.0.0.255 area 0.0.0.0
S2(config-ospf-1)#network 172.20.108.1 0.0.0.0 area 0.0.0.0
S2(config-ospf-1)#end
6-24
Configuration Verification
Run the show bfd neighbors [ldp brief | ldp detail] command on S1 to check whether the
LDP BFD session is established successfully. The execution result is displayed as follows:
S1(config)#show bfd neighbors ldp brief
PeerAddr PrefixLen LD RD Hold State
172.20.108.1 32 6 34 150 UP
Configuration Flow
1. Configure the IGP function for S1 and S2 in loopback interface mode.
2. Enable the MPLS function for the interfaces that connect S1 and S2 directly.
6-25
Configuration Commands
Run the following commands on S1:
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 1.1.1.34 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 100.100.100.1 255.255.255.0
S1(config-if-vlan10/7)#exit
S1(config)#router isis 1
S1(config-isis-1)#area 00.0001
S1(config-isis-1)#system-id 0001.0002.0034
S1(config-isis-1)#interface vlan1
S1(config-isis-1-if-vlan1)#ip router isis
S1(config-isis-1-if-vlan1)#exit
S1(config-isis-1)#interface loopback1
S1(config-isis-1-if-loopback1)#ip router isis
S1(config-isis-1-if-loopback1)#exit
S1(config-isis-1)#exit
S1(config)#bfd
S1(config-bfd)#session 1 peer-bfd ipv4 1.1.1.34 1.1.1.35
S1(config-bfd)#exit
S2(config)#router isis
6-26
S2(config-isis-1)#area 00.0002
S2(config-isis-1)#system-id 0002.0002.0035
S2(config-isis-1)#interface vlan1
S2(config-isis-1-if-vlan1)#ip router isis
S2(config-isis-1-if-vlan1)#exit
S2(config-isis-1)#interface loopback1
S2(config-isis-1-if-loopbck1)#ip router isis
S2(config-isis-1-if-loopbck1)#exit
S2(config-isis-1)#exit
S2(config)#bfd
S2(config-bfd)#session 1 peer-bfd ipv4 1.1.1.35 1.1.1.34
S2(config-bfd)#exit
Note:
In the above configuration, the purpose of running the IS-IS dynamic route protocol is to
notify the Route-id, that is the route of the Loopback interface, of each LSR.
When the address of the loopback interface is set as the route-id of the LDP instance, it is
good for the steady operation of the LDP ID because the address status of the loopback
interface cannot change (except that you disable this interface manually).
Configuration Verification
Run the following commands to check the establishment of the LDP neighbor on S2:
S2(config)#show mpls ldp neighbor detail instance 1
Peer LDP Ident: 1.1.1.34:0; Local LDP Ident 1.1.1.35:0
TCP connection: 1.1.1.34.646 - 1.1.1.35.1069
state: Oper; Msgs sent/rcvd: 47/48; Downstream
Up Time: 00:00:30
LDP discovery sources:
vlan1; Src IP addr: 100.100.100.1
holdtime: 15000 ms, hello interval: 5000 ms
Addresses bound to peer LDP Ident:
2.2.2.34 3.3.3.34 1.1.1.34 10.1.1.2
40.1.1.1 192.12.1.1 192.11.1.1 100.1.1.1
6-27
If the session is in Oper (state: Oper) status, it means that the parameter negotiation is
correct and the neighbor relationship with S1 (1.1.1.34) is established successfully.
Run the following commands to check the PEER BFD neighbor on S1. The execution
result is displayed as follows:
S1(config-ldp-1)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
1.1.1.34 1.1.1.35 2087 2085 150 UP --
Holdown(ms):150 Interface:---
Vpnid:0 VRF Name:---
BFD Type:MultiHop
Instance Name:1
----------------------------------------------------------------------------
Version:1 Dest UDP Port:4784 Final Bit:1
Local Diag:0 Demand Mode:0 Poll Bit:0
MinTxInt:50 MinRxInt:50 Multiplier:3
Received MinTxInt:50 Received MinRxInt:50 Received Multiplier:3
Length:24 Min Echo Interval:0
Min BFD Length:24 Max BFD Length:24
6-28
Configuration Flow
1. Configure the static single-hop BFD for S1.
2. Configure the static single-hop BFD for S2.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#no shutdown
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 172.20.96.1 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#bfd
S1(config-bfd)#session test link-bfd ipv4 172.20.130.213 172.20.130.214
interface vlan1
S1(config-bfd-link-test)#!
6-29
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the static
single-hop BFD configuration on S1 takes effect. The execution result is displayed as
follows:
S1#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
172.20.130.213 172.20.130.214 1 58 150 UP vlan1
Registered Protocols:INSTANCE
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
Run the show bfd neighbors ip brief command to check whether the single-hop BFD
function is configured for the static route of S2. The execution result is displayed as
follows:
S2#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State interface
172.20.130.214 172.20.130.213 58 1 150 UP vlan2
6-30
BFD Type:SingleHop
Instance Name:
----------------------------------------------------------------------------
Version:1 Dest UDP Port:3784 Final Bit:1
Local Diag:0 Demand Mode:0 Poll Bit:1
MinTxInt:50 MinRxInt:50 Multiplier:3
Received MinTxInt:50 Received MinRxInt:50 Received Multiplier:3
Length:24 Min Echo Interval:0
Min BFD Length:24 Max BFD Length:24
Registered Protocols:STATIC
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name: vlan2
==========================================================================
Configuration Flow
1. Configure the static multihop BFD for S1.
2. Configure the multihop BFD for the BGP route of S3.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan 1)#no shutdown
S1(config-if-vlan 1)#ip address 172.20.130.18 255.255.255.0
S1(config-if-vlan 1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 172.20.96.1 255.255.255.255
6-31
S1(config-if-loopback1)#exit
S1(config)#router ospf 1
S1(config-ospf-1)#network 172.20.130.0 0.0.0.255 area 0.0.0.0
S1(config-ospf-1)#network 172.20.96.1 0.0.0.0 area 0.0.0.0
S1(config-ospf-1)#exit
S1(config)#bfd
S1(config-bfd)#session test peer-bfd ipv4 172.20.96.1 172.20.108.2
S1(config-bfd-session-test)#end
S2(config)#router ospf 1
S2(config-ospf-1)#network 172.20.130.0 0.0.0.255 area 0.0.0.0
S2(config-ospf-1)#network 172.20.140.0 0.0.0.255 area 0.0.0.0
S2(config-ospf-1)#network 172.20.96.2 0.0.0.0 area 0.0.0.0
S2(config-ospf-1)#exit
S3(config)#router ospf 1
6-32
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the static
multihop BFD is configured for S1. The execution result is displayed as follows:
S1(config)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
172.20.96.1 172.20.108.2 6 1 150 UP ---
Holdown(ms):150 Interface:---
Vpnid:0 VRF Name:
BFD Type:MultiHop
Instance Name:test
----------------------------------------------------------------------------
Version:1 Dest UDP Port:3784 Final Bit:1
Local Diag:0 Demand Mode:0 Poll Bit:1
MinTxInt:50 MinRxInt:50 Multiplier:3
Received MinTxInt:50 Received MinRxInt:50 Received Multiplier:3
Length:24 Min Echo Interval:0
Min BFD Length:24 Max BFD Length:24
Registered Protocols:INSTANCE
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name:
==========================================================================
Run the show bfd neighbors ip brief command to check whether the multihop BFD function
is configured for the BGP route of S3. The execution result is displayed as follows:
6-33
Holdown(ms):150 Interface:---
Vpnid:0 VRF Name:---
BFD Type:MultiHop
Instance Name: test
----------------------------------------------------------------------------
Version:1 Dest UDP Port:4784 Final Bit:1
Local Diag:0 Demand Mode:0 Poll Bit:1
MinTxInt:50 MinRxInt:50 Multiplier:3
Received MinTxInt:50 Received MinRxInt:50 Received Multiplier:3
Length:24 Min Echo Interval:0
Min BFD Length:24 Max BFD Length:24
Figure 6-12 Configuring the BFD Function for the RSVP Interface
Configuration Flow
1. Establish the ISIS-TE tunnel between S1 and S2.
2. Enable the BFD function for interfaces of S1 and S2 in TE mode.
6-34
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 172.20.130.213 255.255.255.252
S1(config-if-vlan1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 172.20.96.1 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#router isis
S1(config-isis-0)#area 49.0172
S1(config-isis-0)#system-id 0020.0096.0001
S1(config-isis-0)#metric-style wide
S1(config-isis-0)#mpls traffic-eng level-2
S1(config-isis-0)#interface vlan1
S1(config-isis-0-if-vlan1)#ip router isis
S1(config-isis-0-if-vlan1)#end
S1(config)#interface te_tunnel1
S1(config-if-te_tunnel1)#ip unnumbered loopback1
S1(config-if-te_tunnel1)#exit
S1(config)#mpls traffic-eng
S1(config-mpls-te)#interface loopback1
S1(config-mpls-te-if-loopback1)#exit
S1(config-mpls-te)#router-id 172.20.96.1
S1(config-mpls-te)#tunnel te_tunnel 1
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel destination ipv4 172.20.108.1
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel mpls traffic-eng
path-option 1 dynamic
S1(config-mpls-te-tunnel-te_tunnel1)#exit
S1(config-mpls-te)#interface vlan1
S1(config-mpls-te-if-vlan1)#bfd
S2(config)#router isis
S2(config-isis-0)#area 49.0172
6-35
S2(config-isis-0)#system-id 0020.0096.0002
S2(config-isis-0)#metric-style wide
S2(config-isis-0)#mpls traffic-eng level-2
S2(config-isis-0)#interface vlan2
S2(config-isis-0-if-vlan2)#ip router isis
S2(config-isis-0-if-vlan2)#end
S2(config)#mpls traffic-eng
S2(config-mpls-te)#interface loopback1
S2(config-mpls-te-if-loopback1)#exit
S2(config-mpls-te)#router-id 172.20.108.1
S2(config-mpls-te)#interface vlan2
S2(config-mpls-te-if-vlan2)#bfd
Configuration Verification
Run the show bfd neighbors [ip brief | ip detail] command to check whether the BFD function
is configured for the RSVP interface of S1. The execution result is displayed as follows:
S1(config)#show bfd neighbors ip brief
LocalAddr PeerAddr LD RD Hold State Interface
172.20.130.213 172.20.130.214 8 1 150 UP vlan1
Registered Protocols:RSVP
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name: vlan1
==========================================================================
6-36
Configuration Flow
1. Enable the OSPF-TE function among S1, S2, and S3.
2. Configure the hotstandby tunnel (S1-S3-S2) on S1, and then enable the BFD function
for this tunnel.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan3
S1(config-if-vlan3)#ip address 54.1.1.1 255.255.255.0
S1(config-if-vlan3)#exit
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 57.1.1.1 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface loopback10
S1(config-if-loopback10)#ip address 10.10.10.1 255.255.255.255
S1(config-if-loopback10)#exit
6-37
S1(config)#interface te_tunnel1
S1(config-if-te_tunnel1)#ip unnumbered loopback10
S1(config-if-te_tunnel1)#exit
S1(config)#mpls traffic-eng
S1(config-mpls-te)#interface loopback10
S1(config-mpls-te-if-loopback10)#exit
S1(config-mpls-te)#router-id 10.10.10.1
S1(config-mpls-te)#interface vlan3
S1(config-mpls-te-if-vlan3)#exit
S1(config-mpls-te)#interface vlan1
S1(config-mpls-te-if-vlan1)#exit
S1(config-mpls-te)#tunnel te_tunnel1
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel destination ipv4 10.10.10.2
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel mpls traffic-eng path-option 1
explicit-path identifier 1
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel mpls traffic-eng record-route
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel mpls traffic-eng hot-standby
protect 1 dynamic
S1(config-mpls-te-tunnel-te_tunnel1)#tunnel mpls traffic-eng bfd interval 30
min-rx 30 multiplier 5
S1(config-mpls-te-tunnel-te_tunnel1)#exit
S1(config-mpls-te)#explicit-path identifier 1
S1(config-mpls-te-expl-path-id-1)#next-address strict 54.1.1.3
S1(config-mpls-te-expl-path-id-1)#next-address strict 115.1.1.2
6-38
S2(config)#mpls traffic-eng
S2(config-mpls-te)#interface loopback10
S2(config-mpls-te-if-loopback10)#exit
S2(config-mpls-te)#router-id 10.10.10.2
S2(config-mpls-te)#interface vlan1
S2(config-mpls-te-if-vlan1)#exit
S2(config-mpls-te)#interface vlan2
S2(config-mpls-te-if-vlan2)#exit
S3(config)#mpls traffic-eng
S3(config-mpls-te)#interface loopback10
S3(config-mpls-te-if-loopback10)#exit
S3(config-mpls-te)#router-id 10.10.10.3
S3(config-mpls-te)#interface vlan2
S3(config-mpls-te-if-vlan2)#exit
S3(config-mpls-te)#interface vlan3
S3(config-mpls-te-if-vlan2)#exit
Configuration Verification
After the above configuration, the tunnel1 of S1 is in up status, and a hotstandby tunnel is
generated. The hotstandby relationship is ready, and the RSVP LSP BFD session on S1
should be established successfully. When the link between S2 and S3 becomes invalid,
6-39
the status of the LSP BFD session becomes down and then up again, and the traffic is
switched to the hotstandby tunnel.
Run the show bfd neighbors [rsvp lsp brief | rsvp lsp detail] command to check whether the
BFD function is configured for the RSVP interface.
The tunnel1 of S1 is in up status.
S1(config)#show mpls traffic-eng tunnels brief
Signalling Summary:
LSP Tunnels Process: running
RSVP Process: running
Forwarding: enabled
TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROT
tunnel_1 10.10.10.2 - vlan3 up/up
tunnel_1(hot) 10.10.10.2 - vlan1 up/up
InLabel: -
OutLabel: vlan1, 3
RSVP Signalling Info :
Src 10.10.10.1, Dst 10.10.10.2, Tun_Id 1, Tun_Instance 10
RSVP Path Info:
Explicit Route: 57.1.1.1 57.1.1.2 10.10.10.2
Exclude Route: 10.10.10.3 115.1.1.2
Record Route: NULL
Tspec: ave rate= 0 kbits, burst= 1000 bytes, peak rate= 0 kbits
RSVP Resv Info:
Record Route: 10.10.10.2 57.1.1.2
Fspec: ave rate= 0 kbits, burst= 1000 bytes, peak rate= 0 kbits
Run the show bfd neighbors rsvp lsp brief command to check whether the BFD function is
configured for the RSVP interface of S1. The execution result is displayed as follows:
6-40
/*When the link between S3 and S2 becomes invalid, the hotstandby relationship of
the tunnel is in active status and the RSVP LSP BFD is in down status.*/
S1#show mpls traffic-eng fast-reroute
Tunnel head end item information
Protected Tunnel LspID In-label Out intf/label FRR intf/label Status
Tunnel1 9 Tun hd vlan2:14745 Tu1:3 active
6
LSP midpoint frr information:
LSP identifier In-label Out intf/label FRR intf/label Status
S1#show mpls traffic-eng tunnels hot-standby
Name: tunnel_1 (Tunnel1) Destination: 10.10.10.2
Status:
Admin: up Oper: up Path: valid Signalling: connected
Fast Reroute Protection: None
Hot-standby Protection: Backup lsp in use
6-41
Configuration Flow
1. Configure the track object for S1 and S2 in SAMGR mode.
2. Relate this object on S1 and S2 in VRRP configuration mode.
Configuration Commands
Run the following commands on S1:
S1(config)#samgr
S1(config-samgr)#track 1 bfd session bfd
S1(config-samgr)#exit
S1(config)#vrrp
S1(config-vrrp)#interface vlan1
S1(config-vrrp-if-vlan1)#vrrp 1 track object 1 link-type
S1(config-vrrp-if-vlan1)#exit
S1(config-vrrp)#exit
Configuration Verification
Run the show vrrp interface command to check whether the link BFD is configured on S1.
The execution result is displayed as follows:
S1(config)#show vrrp interface vlan1
vlan1 - vrID 1
Vrrp configure info:
6-42
Run the show vrrp interface command to check whether the link BFD is configured on S2.
The execution result is displayed as follows:
S2(config)#show vrrp interface vlan2
vlan2 - vrID 1
Vrrp configure info:
IP version 4, VRRP version 3
Virtual IP address is 0.0.0.0
Virtual MAC address is 0000.5e00.0101
Advertise time is 1.000 (s)
Configured priority is 100
Preemption enable, delay 0 (s)
Reload delay 0 (s)
No authentication data
6-43
Configuration Flow
1. Configure the VPWS instance for S1 and S2.
2. Enable the BFD function for S1 and S2 in VPWS configuration mode.
Configuration Commands
Run the following commands on S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 201.2.3.2 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 100.1.1.2 255.255.255.255
S1(config-if-loopback1)#exit
6-44
S1(config)#router ospf 1
S1(config-ospf-1)#network 201.2.3.0 0.0.0.255 area 0
S1(config-ospf-1)#network 100.1.1.2 0.0.0.0 area 0
S1(config-ospf-1)#exit
S1(config)#pw pw1
S1(config)#vpws vpws-bfd
S1(config-vpws-vpws-bfd)#access-point vlan2
S1(config-vpws-vpws-bfd-ac-vlan2)#access-params ethernet
S1(config-vpws-vpws-bfd-ac-vlan2-eth)#exit
S1(config-vpws-vpws-bfd-ac-vlan2)#exit
S1(config-vpws-vpws-bfd)#pseudo-wire pw1
S1(config-vpws-vpws-bfd-pw-pw1)#neighbour 100.1.1.3 vcid 1
S1(config-vpws-vpws-bfd-pw-pw1-neighbour-100.1.1.3)#vccv bfd capability
basicencapsulation ip
S1(config-vpws-vpws-bfd-pw-pw1-neighbour-100.1.1.3)#exit
S1(config-vpws-vpws-bfd-pw-pw1)#exit
S1(config-vpws-vpws-bfd)#exit
S1(config)#bfd
S1(config-bfd)#session pw-bfd pw-bfd pw-name pw1
S1(config-bfd-pw-pw-bfd)#exit
S1(config-bfd)#exit
S2(config)#router ospf 1
S2(config-ospf-1)#network 201.2.3.0 0.0.0.255 area 0
S2(config-ospf-1)#network 100.1.1.3 0.0.0.0 area 0
S2(config-ospf-1)#exit
6-45
S2(config-ldp-1)#interface vlan2
S2(config-ldp-1)#exit
S2(config)#pw pw1
S2(config)#vpws vpws-bfd
S2(config-vpws-vpws-bfd)#access-point vlan4
S2(config-vpws-vpws-bfd-ac-vlan4)#access-params ethernet
S2(config-vpws-vpws-bfd-ac-vlan4-eth)#exit
S2(config-vpws-vpws-bfd-ac-vlan4)#exit
S2(config-vpws-vpws-bfd)#pseudo-wire pw1
S2(config-vpws-vpws-bfd-pw-pw1)#neighbour 100.1.1.2 vcid 1
S2(config-vpws-vpws-bfd-pw-pw1-neighbour-100.1.1.2)#vccv bfd capability basic
encapsulation ip
S2(config-vpws-vpws-bfd-pw-pw1-neighbour-100.1.1.2)#exit
S2(config-vpws-vpws-bfd-pw-pw1)#exit
S2(config-vpws-vpws-bfd)#exit
S2(config)#bfd
S2(config-bfd)#session pw-bfd pw-bfd pw-name pw1
S2(config-bfd-pw-pw-bfd)#exit
S2(config-bfd)#exit
Configuration Verification
Run the show l2vpn forwardinfo vpnname command to check whether the VPWS instance
is configured and the show bfd neighbors pw brief command to check whether the VPWS
BFD function is configured on S1. The execution result is displayed as follows:
S1(config)#show l2vpn forwardinfo vpnname vpws-bfd
Headers: PWType - Pseudowire type and Pseudowire connection mode
Llabel - Local label, Rlabel - Remote label
VPNowner - owner type and instance name
Codes : H - HUB mode, S - SPOKE mode, L - VPLS, W - VPWS, M - MSPW
$pw - auto_pw
PWName PeerIP FEC PWType State Llabel Rlabel VPNowner
pw1 100.1.1.3 128 Ethernet UP 81922 81921 W:vpws-bfd
Run the show l2vpn forwardinfo vpnname command to check whether the VPWS instance
is configured and the show bfd neighbors pw brief command to check whether the VPWS
BFD function is configured on S2. The execution result is displayed as follows:
S2(config)#show l2vpn forwardinfo vpnname vpws-bfd
Headers: PWType - Pseudowire type and Pseudowire connection mode
Llabel - Local label, Rlabel - Remote label
6-46
6-47
6-48
7-1
5. The time that is used to recalculate the triggering route. For Interior Gateway Protocol
(IGP) protocols that use Dijkstra algorithm, the time is tens of milliseconds.
6. The time that is used to interact with line interface cards to calculate the new routing
information and form the new forwarding table. The time varies in accordance with the
number of routing entries. Usually it is several hundred milliseconds.
7. The time that is used to load the new forwarding route entries into hardware. Usually
it is tens of milliseconds.
The traffic loss may occur in the above mentioned steps. The traffic loss can be divided
into two stages, including:
1. Stage 1: The switch fails to discover the invalid link immediately, and it still forwards
the traffic to the invalid link.
2. Stage 2: The route discovers the invalid link, but the network is in convergence
process. The local forwarding table is different with that of other switches, which
causes "micro-loop" in forwarding plane.
To shorten the traffic interruption duration, a mechanism must be provided to implement
the following functions:
1. Discover the invalid link quickly.
2. When the link is invalid, provide a recovery path quickly.
3. Prevent forwarding "micro-loop" during the further recovery process.
This mechanism is the IP Fast-Reroute (FRR).
IP FRR Principle
The working procedure of IP FRR is as follows:
1. Detect faults quickly: The common technologies include BFD, and physical signal test.
2. Modify the forwarding plane: Hand over the traffic to the recalculated backup path.
3. Perform route re-convergence.
4. After finishing the re-convergence, hand over the route to the optimal path.
Obviously, the backup path is to fill the FRR gap up, which hands over the traffic to the
backup next hop, to guarantee that the service will not be interrupted.
There are some conditions to form the OSPF FRR or IS-IS FRR relationship. To form
the FRR relationship of default LFAs test mode, the algorithm should meet the condition
Distance_opt (Ni, D) < Distance_opt (Ni, S) + Distance (S, D). That is, the distance from
the next hop on the backup link to the destination should be shorter than the sum of the
distance from the next hop on the backup link to the source node and the distance from
the source node on the primary link to the destination node.
To form the FRR relationship of down-stream-path mode, the algorithm should meet the
condition Distance_opt (Ni, D) < Distance (S, D). That is, the distance from the next hop
on the backup link to the destination should be shorter than that from the source node on
the primary link to the destination node.
The establishment of BGP FRR relationship is relatively simpler. It only needs two different
next hops to the same destination.
7-2
7-3
Command Function
ZXR10#show ip ospf border-lsfas [ process < process-id>] Displays the routes on the backup
switch for the OSPF primary
switch.
ZXR10#show ip forwarding backup route {<network>} Displays the backup routing table.
The following is sample output from the show isis fast-reroute-topology command:
ZXR10(config)#show isis fast-reroute-topology level-1
IS-IS ipfrr paths to Level-1 routers
System id Interface Ipfrr interface Ipfrr type metric
AAAA.AAAA.AAAA vlan1 valn2 Link/ECMP 10
AAAA.AAAA.AAAA vlan3 vlan4 Link/ECMP 10
AAAA.AAAA.AAAA vlan5 vlan6 Link/ECMP 10
For a description of the parameters in the execution result, refer to the following table:
The following is sample output from the show ip ospf border-lsfas command:
ZXR10#show ip ospf border-lfas
Protect Type: link-protect 0x80000001, ecmp-protect 0x80000004
node-protect 0x80000002, stat-protect 0x80000008
7-4
For a description of the parameters in the execution result, refer to the following table:
Area Area.
The following is sample output from the show ip forwarding backup route command:
For a description of the parameters in the execution result, refer to the following table:
7-5
2. The typical network structure of link protection is shown in Figure 7-2. IS-IS neighbor
topology is established on the two links. One of the link has high priority and the other
link has lower priority.
7-6
Configuration Thought
1. Configure routing protocols.
2. On the nodes forming FRR relationship, there are more than two next hops reachable
to the same route.
3. Enable FRR function in related routing protocol on corresponding devices.
Configuration Commands
The detailed configuration is described below.
1. Configuration of FRR node protection
Take BGP in Figure 7-1 as an example. First, establish EBGP neighbor relationship
between the routers through real interfaces. Enable FRR function on S1. Set the
routes advertised by S3 that go through the path S1—S2—S3 as the optimal routes.
Configuration of S1:
S1(config)#router bgp 1
S1(config-bgp)#neighbor 172.16.1.2 remote-as 2
S1(config-bgp)#neighbor 172.16.20.2 remote-as 3
S1(config-bgp)#bgp frr
S1(config-bgp)#exit
S1(config)#route-map lt
S1(config-route-map)#set local-preference 200
S1(config-router)#exit
S1(config)#router bgp 1
S1(config-bgp)#neighbor 172.16.1.2 route-map lt in
S1(config-bgp)#exit
Configuration of S2:
S2(config)#router bgp 2
S2(config-bgp)#neighbor 172.16.1.1 remote-as 1
S2(config-bgp)#neighbor 183.16.20.2 remote-as 3
S2(config-bgp)#exit
Configuration of S3:
S3(config)#router bgp 3
S3(config-bgp)#neighbor 172.16.20.1 remote-as 1
S3(config-bgp)#neighbor 183.16.20.1 remote-as 2
S3(config-bgp)#exit
2. Configuration of FRR link protection
Take IS-IS protocol in Figure 7-2 as an example.
Configuration of S1:
S1(config)#router isis
S1(config-isis)#area 01
S1(config-isis-1)#system-id 00D0.D0C7.5460
7-7
S1(config-isis-1)#fast-reroute enable
S1(config-isis-1)#interface vlan24
S1(config-isis-1-if-vlan24)#ip router isis
S1(config-isis-1-if-vlan24)#exit
S1(config-isis-1)#interface vlan47
S1(config-isis-1-if-vlan47)#ip router isis
S1(config-isis-1-if-vlan47)#metric 20
S1(config-isis-1-if-vlan47)#exit
Configuration of S2:
S2(config)#router isis
S2(config-isis)#area 01
S2(config-isis-1)#system-id 00D0.D0C7.6788
S2(config-isis-1)#interface vlan24
S2(config-isis-1-if-vlan24)#ip router isis
S2(config-isis-1-if-vlan24)#exit
S2(config-isis-1)#interface vlan47
S2(config-isis-1-if-vlan47)#ip router isis
S2(config-isis-1-if-vlan47)#end
Configuration Verification
Use the show ip forwarding backup route command to check whether the FRR
configuration takes effect.
7-8
l Improving bandwidth
Route load sharing function makes it possible for routers to share traffic on several
paths, thus to make full use of the bandwidth resources. Through routing protocols
or static configuration, multiple route entities to the same destination are allowed to
exist in the forwarding table.
The forwarding mechanism of load sharing only supports per-destination method. The
advantages and disadvantages of the per-destination method are listed below.
Per-destination
Advantages In this mode, the packets to the same destination go through the
same path. That is, when there are several paths available, packets
to different destinations can go through different paths.
Disadvantages When there are few destinations, the traffic may gather on few
paths. Therefore, the loads are not balanced. When there are more
destinations, load sharing in this mode is more effective.
8-1
1 ZXR10(config)#router ospf < process-id>[ vrf < vrf-name>] Enters OSPF route
configuration mode.
8-2
8-3
8-4
ZXR10#show ip forwarding route {[vrf <vrf-name>]<network>[<net This shows the forwarding routing
work-mask>]|<protocol>} table.
ZXR10#show ip protocol routing {[vrf <vrf-name>]<network>[<netw This shows the protocol routing
ork-mask>]|<protocol>} table.
8-5
Output descriptions:
Pri and RoutePrf Management distance of the information source, that is, the priority
Output descriptions:
8-6
Configuration Thought
1. Configure an interface and set the load sharing of per-packet mode (By default, it is
per-destination).
2. Enable and configure OSPF
3. Configure OSPF load sharing on S1
Configuration Commands
The configuration of S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ip address 101.2.1.100 255.255.255.0
S1(config-if-vlan1)#exit
S1(config)#interface vlan2
S1(config-if-vlan2)#ip address 102.2.1.100 255.255.255.0
S1(config-if-vlan2)#exit
S1(config)#router ospf 1
S1(config-ospfv2)#network 101.2.1.0 0.0.0.255 area 0
S1(config-ospfv2)#network 102.2.1.0 0.0.0.255 area 0
S1(config-ospfv2)#maximum-paths 2
Configuration Verification
Use the show command to check the configuration result, as shown below.
S1#show ip forwarding route ospf
8-7
Configuration Thought
1. Configure an interface and set the load sharing of per-packet mode (By default, it is
per-destination).
2. Enable and configure BGP4+
3. Configure BGP4+ load sharing on S1
Configuration Commands
The configuration of S1:
S1(config)#interface vlan1
S1(config-if-vlan1)#ipv6 enable
S1(config-if-vlan1)#ipv6 address 2000::1/64
S1(config-if-vlan1)#exit
S1(config)#interface vlan2
S1(config-if-vlan2)#ipv6 enable
S1(config-if-vlan2)#ipv6 address 2001::1/64
S1(config-if-vlan2)#exit
S1(config)#router bgp 100
S1(config-bgp)#neighbor 2000::2 remote-as 100
S1(config-bgp)#neighbor 2001::2 remote-as 100
S1(config-bgp)#address-family ipv6
S1(config-bgp-af)#maximum-paths ibgp 16
S1(config-bgp-af)#neighbor 2000::2 activate
8-8
Configuration Verification
Advertise EBGP routes on S2. Use the show command to check the configuration result,
as shown below.
S1#show ipv6 forwarding route bgp
IPv6 Routing Table:
Dest Owner Metric
Interface Gw
2000:0:0:1::/64 bgp 0
vlan1 fe80:12::1
vlan2 fe80:16::1
8-9
8-10
9-1
To solve the problem described above, L3 multicast load sharing solution is introduced.
Command Function
Command Function
Parameter descriptions:
Parameter Description
9-2
Output descriptions:
Assume that the two routes are equal-cost for S2, that is, the two routes are ECMP between
S2 and the source. Multicast load sharing can be configured on S2 to make the multicast
traffic of different groups be shared on the two paths.
9-3
Configuration Thought
1. Configure PIM-SM, BSR and RP on the switches to make the user can receive the
multicast traffic sent by the source properly.
2. Configure multicast load sharing on the downstream switch.
Configuration Commands
Configure multicast protocol on R and S2 to create a multicast tree. Here take PIM-SM as
an example.
The configuration of S1 (enable PIM-SM on the interfaces, and configure BSR and RP on
loopback63 interface):
S1(config)#ip multicast-routing
S1(config-mcast)#router pimsm
S1(config-pimsm)#interface vlan1
S1(config-pimsm-if)#pimsm
S1(config-pimsm-if)#exit
S1(config-pimsm)#interface vlan2
S1(config-pimsm-if)#pimsm
S1(config-pimsm-if)#exit
S1(config-pimsm)#interface vlan3
S1(config-pimsm-if)#pimsm
S1(config-pimsm-if)#exit
S1(config-pimsm)#bsr-candidate loopback63
S1(config-pimsm)#rp-candidate loopback63
9-4
S2(config-pimsm-if)#pimsm
S2(config-pimsm-if)#exit
S2(config-pimsm)#interface vlan6
S2(config-pimsm-if)#pimsm
S2(config-pimsm-if)#exit
S2(config)#ip route 44.63.1.1 255.255.255.255 172.1.7.44
S2(config)#ip route 172.1.3.0 255.255.255.0 172.1.7.44
S2(config)#ip route 172.1.3.0 255.255.255.0 172.1.13.44
Configuration Verification
When the user starts to receive the multicast traffic sent from the source, check the routing
tables on S1 and S2. Pay attention to the ingress and egress of the routes.
The multicast routing table on S1 is shown below:
S1#show ip mroute
(*, 238.255.255.0), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS:
Incoming interface: NULL, flags:
Outgoing interface list:
vlan2, flags: F
(172.1.3.49, 238.255.255.0), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS:
Incoming interface: vlan1, flags:
Outgoing interface list:
vlan3, flags: F
(*, 238.255.255.1), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS:
Incoming interface: NULL, flags:
Outgoing interface list:
vlan2, flags: F
(172.1.3.49, 238.255.255.1), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS:
Incoming interface: vlan1, flags:
Outgoing interface list:
vlan2, flags: F
......
S2#show ip mroute
IP Multicast Routing Table
(*, 238.255.255.0), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS: NS
Incoming interface: vlan6, flags: NS
Outgoing interface list:
vlan5, flags: F
(172.1.3.49, 238.255.255.0), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS:
9-5
9-6
For example, on a mobile IP bearer network, when the quality of phone calls declines
seriously, it is necessary to check whether there is serious voice packet loss, delay and
oscillation at the wireless network side and IP bearer network side at the same time. At
the IP bearer network side, it is necessary to check whether there is any serious network
fault for the transmission of IP packets between CEs. Meanwhile, it is also necessary to
use the parameters (such as UDP packet oscillation and delay ) of SLA to judge whether
the fault is on the bearer network side.
SQA can also be used to detect the network qualities of operators periodically to reflect the
network qualities in real time, so that operators can master the overall network qualities.
SQA is not used very frequently, so it should not be too difficult. Meanwhile, SQA has strict
security limit requirement for the packets forwarded by SLA for handling.
10-1
Parameter Description
Parameter Description
10-2
Parameter Description
<destination-address> For the ICMP, UDP, and TCP detection, it refers to the destination
IP address. For the FTP detection, it refers to the IP address of
the FTP server.
root <local-path>/<file-name> The destination path and name of the destination FTP file. Range:
1-151.
10-3
Parameter Description
Parameter Description
enable <percent> Enables the trap alarm. The range of the alarm threshold is 1-100.
Parameter Description
Command Function
ZXR10(config)#show sqa-test <number> Displays the sqa test configuration information in other
configuration modes except user configuration mode.
Range: 1-150.
10-4
sqa-test 40
type-icmp 192.168.1.100 repeat 10 source 1.1.1.1
!
sqa-test 10
type-udp 192.168.1.98 10000 repeat 10
send-trap enable 80
!
sqa-test 35
type-tcp 192.168.1.98 10000 repeat 10
!
sqa-test 39
!
! </SQA>
Output descriptions:
type-icmp 192.168.1.1 repeat 10 The test type is ICMP. The number of retry attempts for the test to
the destination address 192.168.1.1 is 10.
Output descriptions:
10-5
Configuration Thought
1. Create an SQA test instance.
2. Configure the destination address for the ICMP test, and set the ICMP test attribute.
3. Set the beginning time for the SQA test.
4. Check the test result.
Configuration Commands
The configuration of S1:
S1(config)#sqa-test 1
S1(config-sqa)#type-icmp 10.1.0.2
S1(config-sqa)#sqa-begin now
The sqa test is starting now, please wait a moment for test result......
S1(config-sqa)#
10-6
Configuration Verification
The configuration and test result are shown below.
S1(config)#show sqa-test 1
test type: ICMP
destination IP: 10.1.0.2
repeat:1
tos: 0
interval time:100
send trap:disable
S1(config)#show sqa-result icmp
icmp test[1] result
SendPackets:20 ResponsePackets:20
Completion:success Destination IP Address:192.0.0.100
Min/Max/Avg/Sum RTT:29/99/39/787ms
Min/Max/Avg/Sum Positive Jitter:1/7/3/9ms
Min/Max/Avg/Sum Negative Jitter:1/70/35/71ms
Min/Max/Avg/Sum Jitter:1/70/16/80ms
Packet loss rate:0%
Last Probe Time:2011-11-18 01:57:38
Configuration Thought
1. Create an SQA test instance.
2. Configure the FTP test attribute, including the address of the FTP server, user name,
password, source file name, destination path, and the name of the destination file.
3. Set the beginning time for the SQA test.
4. Check the test result.
Configuration Commands
The configuration of S3:
10-7
S3(config)#ftp-server en
S3(config)#ftp-server top-directory /sysdisk0/
S3(config)#ip ftp username who
S3(config)#ip ftp password who
Configuration Verification
The configuration and test result are shown below.
S1(config)#show sqa-test 2
test type: FTP
ftp IP:10.1.0.2
username:who
password:who
filename:abc.txt
path:/sysdisk0/abc.txt
S1(config)#show sqa-result ftp
ftp test[2] result is finished
Last RTT:127..Bytes read:4817497
Last Probe Time:2010-07-29 09:22:58
Configuration Thought
1. Create an SQA test instance.
2. Configure the destination address and the port for the TCP test, and set the TCP test
attribute.
10-8
Configuration Commands
The configuration of S3:
S3(config)#sqa-tcp-server 10.1.0.2 10000
Configuration Verification
The configuration and test result are shown below.
S1(config)#show sqa-test 3
test type: TCP
destination IP:10.1.0.2
desitnation port:10000
inteinterval time:1000
repeat:1
send trap:disable
S1(config)#show sqa-result tcp
tcp test[3] result is finished
SendPackets:1..ResponsePackets:1
Completion:success....Destination ip IP Aaddress:10.1.0.2
Min/Max/Avg/Sum RTT:5/5/5/5ms
Last Probe Time:2010-07-29 09:45:49
10-9
Configuration Thought
1. Create an SQA test instance.
2. Configure the destination address and the port number for the UDP test, and set the
UDP test attribute.
3. Set the beginning time for the SQA test.
4. Check the test result.
Configuration Commands
The configuration of S3:
S3(config)#sqa-udp-server 10.1.0.2 10000
Configuration Verification
The configuration and test result are shown below.
S1(config)#show sqa-test 4
test type: UDP
destination IP:10.1.0.2
desitnation port:10000
interval time:100
repeat:1
send trap:disable
S1(config)#show sqa-result udp
ZXR10(config)#show sqa-result udp
udp test[2] result
SendPackets:10 ResponsePackets:10
Completion:success Destination IP Address:192.0.0.111
Min/Max/Avg/Sum RTT:61/63/62/622ms
Min/Max/Avg/Sum Positive Jitter:0/0/0/0ms
Min/Max/Avg/Sum Negative Jitter:1/1/1/2ms
Min/Max/Avg/Sum Jitter:1/1/1/2ms
Packet loss rate:0%
Last Probe Time:2011-09-01 23:52:35
10-10
Configuration Thought
1. Create an SQA test instance.
2. Configure the name for the domain to be analysed for the DNS test and the IP address
for the DNS server, and set the times for domain analysis.
3. Set the beginning time for the SQA test.
4. Check the test result.
Configuration Commands
The configuration of S1:
S1(config)#ip domain lookup
S1(config)#ip domain name-server ipv4-address 10.1.0.1
S1(config)#sqa-test 5
S1(config-sqa)#type-dns destination-url abc.cn dns-ip 10.1.0.1
S1(config-sqa)#sqa-begin now
The sqa test is starting now, please wait a moment for test result......
S1(config-sqa)#
Configuration Verification
The configuration and test result are shown below.
S1(config)#show sqa-test 5
test type: DNS
destination-url:abc.cn
dns-ip:10.1.0.1
repeat:1
send trap:disable
S1(config)#show sqa-result dns
dns test[5] result
SendPackets:1 ResponsePackets:1
10-11
Completion:success
Destination-url:abc.cn
DNS Interpret IP Address:192.0.0.100
Min/Max/Avg/Sum RTT:1010/1010/1010/1010ms
Last Probe Time:2011-07-29 09:49:36
10-12
11-1
normally, it indicates that Ethernet link of this interface is reachable bidirectionally. If the
Echo packet fails to be received or the link is reachable unidirectionally according to the
received packet, the UDLD takes measures according to the configured working mode.
The UDLD supports two working modes: normal mode and aggressive mode. In the
normal mode, the UDLD makes an interface down after the interface receives the Echo
packet and confirms that the link is reachable unidirectionally. The UDLD does not perform
any operation when the interface cannot receive the Echo packet or fails to confirm that the
link is reachable unidirectionally. In the aggressive mode, the UDLD makes an interface
down if the interface cannot confirm that the link is reachable bidirectionally. The common
point of the two modes is that the system generates an alarm if the interface fails to confirm
that the link works normally.
When the interface is down or cannot be used due to other reasons, the device will send
a flush packet to notify the adjacent L2 device to delete the information of this device.
11-2
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
11-3
Parameter Description
Parameter Description
Command Function
ZXR10#show udld <interface-name> This shows the UDLD neighbor information of an interface.
Interface gei-0/1/1/1
Administrative configuration: Enable
Port mode: Normal
Current state: Bidirection
Recovery configuration: Disable
Auto-recovery time: 30s
Message interval: 15s
Entry 1
--------------------
Device ID: ZTE0000.0100.9902
Device name: ZTE
Port ID: gei-0/1/1/1
Expiration time: 31s
Message interval: 15s
Timeout interval: 5s
11-4
Configuration Thought
1. Enter the UDLD config mode.
2. Enter the config mode of an interface.
3. Enable the UDLD function.
Configuration Commands
Method 1: In the UDLD config mode, enter the config mode of an interface to enable the
UDLD function.
ZXR10(config)#udld
ZXR10(config-udld)#interface gei-0/1/1/1
ZXR10(config-udld-if)#udld enable
Method 2: In the UDLD config mode, enable the UDLD function of an interface.
ZXR10(config-udld)#udld enable interface gei-0/1/1/1
Configuration Verification
Use the show udld neighbor command to view the configuration result.
ZXR10(config-udld)#show udld gei-0/1/1/1
Interface gei-0/1/1/1
Administrative configuration: Enable
Port mode: Normal
Current state: Bidirection
Recovery configuration: Disable
Auto-recovery time: 30s
Message interval: 15s
Entry 1
11-5
--------------------
Device ID: ZTE0000.0100.9902
Device name: ZTE
Port ID: gei-0/1/1/1
Expiration time: 44s
Message interval: 15s
Timeout interval: 5s
Configuration Thought
1. Enter the UDLD config mode.
2. Enter the config mode of an interface.
3. Configure the properties of UDLD.
Configuration Commands
ZXR10(config)#udld
ZXR10(config-udld)#interface gei-0/1/1/1
/*Enter the interface config mode of UDLD*/
ZXR10(config-udld-if)#udld message timer 10
/*Configure the interval of sending Hello packets in the case of bidirectional
UDLD communication*/
ZXR10(config-udld-if)#udld mode aggressive
/*Configure the interface protocol mode of UDLD*/
ZXR10(config-udld-if)#udld recovery timer 100
/*Configure the interval of automatic recovery in the case of unidirectional
UDLD communication*/
ZXR10(config-udld-if)#udld recovery enable
/*Enable automatic recovery function of UDLD*/
Configuration Verification
Use the show running-config udld command to view the configuration result.
ZXR10(config-udld-if)#show running-config udld
! <UDLD>
udld
interface gei-0/1/1/1
11-6
udld enable
udld mode aggressive
udld message timer 10
udld recovery enable
udld recovery timer 100
$
!
! </UDLD>
11-7
11-8
II
ECMP
- Equal-Cost Multi-Path routing
EFM
- Ethernet in the First Mile
ERO
- Explicit Route Object
FIB
- Forwarding Information Base
FRR
- Fast Reroute
IBGP
- Interior Border Gateway Protocol
IEEE
- Institute of Electrical and Electronics Engineers
IGP
- Interior Gateway Protocol
IPTV
- Internet Protocol Television
III
ITU
- International Telecommunications Union
LAN
- Local Area Network
LBM
- Loopback Message
LDP
- Label Distribution Protocol
LSP
- Label Switched Path
LTM
- Link Trace Message
LTR
- Link Trace Reply
MAC
- Media Access Control
MAN
- Metropolitan Area Network
MIP
- Maintenance domain Intermediate Point
MP
- Merge Point
NGN
- Next Generation Network
OAM
- Operation, Administration and Maintenance
PDU
- Protocol Data Unit
PLR
- Point of Local Repair
PTN
- Packet Transport Network
PWE3
- Pseudo Wire Emulation Edge-to-Edge
QoS
- Quality of Service
RFC
- Request For Comments
IV
RIPng
- Routing Information Protocol next generation
RSVP
- Resource Reservation Protocol
SLA
- Service Level Agreement
TTL
- Time To Live
VLAN
- Virtual Local Area Network
VoIP
- Voice over Internet Protocol
VPWS
- Virtual Private Wire Service
VRRP
- Virtual Router Redundancy Protocol
WAN
- Wide Area Network