Sj-20130205142913-019-zxr10 M6000 (v1.00.60) Carrier-class Router Configuration Guide (reliability).pdf
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Sj-20130205142913-019-zxr10 M6000 (v1.00.60) Carrier-class Router Configuration Guide (reliability).pdf as PDF for free.
More details
- Words: 33,861
- Pages: 147
ZXR10 M6000 Carrier-Class Router
Configuration Guide (Reliability) Version: 1.00.60
ZTE CORPORATION No. 55, Hi-tech Road South, ShenZhen, P.R.China Postcode: 518057 Tel: +86-755-26771900 Fax: +86-755-26770801 URL: http://ensupport.zte.com.cn E-mail: [email protected]
LEGAL INFORMATION Copyright © 2013 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History Revision No.
Revision Date
Revision Reason
R2.2
2013-02-28
Fourth edition, adding the "Cooperation Configuration Example Between a Directly Connected Route and the Ping Detect" topic.
R2.0
2012-07-20
Third edition
R1.1
2012-03-30
Second edition
R1.0
2011-12-10
First edition
Serial Number: SJ-20130205142913-019 Publishing Date: 2013-02-28 (R2.2)
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Contents About This Manual ......................................................................................... I Chapter 1 Reliability Overview .................................................................. 1-1 Chapter 2 Service Availability Manager Configuration ........................... 2-1 2.1 SAMGR Overview .............................................................................................. 2-1 2.2 SAMGR Configuration ........................................................................................ 2-4 2.3 Maintaining SAMGR ........................................................................................... 2-6 2.4 SAMGR Configuration Instances ......................................................................... 2-9 2.4.1 Linkage between EFM and VRRP ............................................................. 2-9 2.4.2 Linkage between CFM and VRRP ........................................................... 2-12
Chapter 3 VRRP Configuration ................................................................. 3-1 3.1 VRRP Overview ................................................................................................. 3-1 3.2 VRRP Network Application ................................................................................. 3-4 3.3 Configuring VRRP .............................................................................................. 3-8 3.4 Maintaining VRRP .............................................................................................3-11 3.5 VRRP Configuration Instances .......................................................................... 3-13 3.5.1 Basic VRRP Configuration Example ........................................................ 3-13 3.5.2 Symmetrical VRRP Configuration Example .............................................. 3-15 3.5.3 VRRP Heartbeat Configuration Example.................................................. 3-18 3.5.4 VRRP BFD Configuration Example.......................................................... 3-20
Chapter 4 Ping Detect Configuration........................................................ 4-1 4.1 Ping Detect Overview ......................................................................................... 4-1 4.2 Configuring Ping Detect ...................................................................................... 4-2 4.3 Maintaining Ping Detect ...................................................................................... 4-3 4.4 Ping Detect Configuration Instances .................................................................... 4-4 4.4.1 Basic Ping Detect Configuration Examples................................................. 4-4 4.4.2 Cooperation Configuration Example Between a Directly Connected Route and the Ping Detect....................................................................... 4-6
Chapter 5 EFM Configuration.................................................................... 5-1 5.1 EFM Overview ................................................................................................... 5-1 5.2 Configuring EFM ................................................................................................ 5-2 5.3 Maintaining EFM ................................................................................................ 5-4 5.4 EFM Configuration Instances .............................................................................. 5-6 5.4.1 EFM Connection Establishment ................................................................ 5-6 I SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
5.4.2 EFM Remote Loopback .......................................................................... 5-10
Chapter 6 CFM Configuration.................................................................... 6-1 6.1 CFM Overview ................................................................................................... 6-1 6.2 Configuring CFM ................................................................................................ 6-3 6.3 CFM Maintenance .............................................................................................. 6-5 6.4 CFM Configuration Instances .............................................................................. 6-6 6.4.1 CFM Fast Connectivity Detection .............................................................. 6-6 6.4.2 Cross-L2 VPN Connectivity Detection...................................................... 6-10
Chapter 7 BFD Configuration .................................................................... 7-1 7.1 BFD Overview.................................................................................................... 7-1 7.2 BFD Configuration.............................................................................................. 7-2 7.3 BFD Maintenance .............................................................................................. 7-6 7.4 BFD Configuration Instances............................................................................... 7-7 7.4.1 Configuring IS-IS BFD .............................................................................. 7-7 7.4.2 Configuring OSPF BFD ............................................................................ 7-9 7.4.3 Configuring BGP Single-Hop BFD ........................................................... 7-10 7.4.4 Configuring BGP Multi-Hop BFD ............................................................. 7-12 7.4.5 Configuring Static Route BFD ................................................................. 7-14 7.4.6 Configuring LDP BFD ............................................................................. 7-16 7.4.7 Configuring Static Single-Hop BFD.......................................................... 7-18 7.4.8 Configuring Static Multi-Hop BFD ............................................................ 7-20 7.4.9 Configuring BFD on RSVP Interface ........................................................ 7-23 7.4.10 Configuring RSVP LSP BFD ................................................................. 7-26
Chapter 8 FRR Configuration .................................................................... 8-1 8.1 IP FRR Configuration ......................................................................................... 8-1 8.1.1 IP FRR Overview ..................................................................................... 8-1 8.1.2 Nested FRR Overview .............................................................................. 8-3 8.1.3 Configuring IP FRR .................................................................................. 8-4 8.2 Static Route FRR Configuration .......................................................................... 8-4 8.3 L2 VPN FRR Configuration ................................................................................. 8-5 8.3.1 L2 VPN FRR Overview ............................................................................. 8-5 8.3.2 Configuring L2 VPN FRR .......................................................................... 8-6 8.4 L3VPN FRR Configuation ................................................................................... 8-6 8.4.1 Brief Introduction to L3VPN FRR ............................................................... 8-6 8.4.2 Configuring L3 VPN FRR .......................................................................... 8-7 8.5 TE FRR Configuration ........................................................................................ 8-7 8.5.1 TE FRR Overview .................................................................................... 8-7 II SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
8.5.2 TE FRR Work Flow .................................................................................. 8-9 8.5.3 Configuring TE FRR ............................................................................... 8-14
Chapter 9 Graceful Restart Configuration ............................................... 9-1 9.1 IP Graceful Restart Configuration ........................................................................ 9-1 9.2 LDP Graceful Restart Configuration..................................................................... 9-3
Chapter 10 Master/Slave Main Control Handover ................................. 10-1 10.1 Master/Slave Plane Handover Overview .......................................................... 10-1 10.2 Configuring Master/Slave Main-control Handover ............................................. 10-2 10.3 Maintaining Master/Slave Main-control Handover ............................................. 10-2 10.4 Master/Slave Main-control Handover Configuration Example............................. 10-6
Chapter 11 Load Sharing Configuration................................................. 11-1 11.1 Load Sharing Overview ....................................................................................11-1 11.2 Configuring the Load Sharing ...........................................................................11-1 11.3 Configuring Multicast Load Sharing...................................................................11-2 11.4 Configuring MPLS VPN Load Sharing ...............................................................11-2
Figures............................................................................................................. I Glossary ........................................................................................................ III
III SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
IV SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
About This Manual Purpose This manual describes the principle, configuration commands, maintenance commands and configuration examples about the reliability function of the ZXR10 M6000.
Intended Audience This manual is intended for: l l l
Network planning engineers Commissioning engineers On-duty personnel
What Is in This Manual This manual contains the following chapters: Chapter
Summary
1, Reliability Overview
Describes the meaning and requirements of the reliability, and the relationship of various functions related to the reliability.
2, Service Availability
Describes the principle, configuration commands, maintenance
Manager Configuration
commands, and configuration examples of the SAMGR.
3, VRRP Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the VRRP.
4, Ping Detect Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the ping detect.
5, EFM Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the EFM.
6, CFM Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the CFM.
7, BFD Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the BFD.
8, FRR Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the FRR.
9, Graceful Restart
Describes the principle, configuration commands, maintenance
Configuration
commands, and configuration examples of the GR.
I SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter
Summary
10, Master/Slave Main Control
Describes the principle, configuration commands, maintenance
Handover
commands, and configuration examples of the master/slave main-control handover.
11, Load Sharing
Describes the principle, configuration commands, maintenance
Configuration
commands, and configuration examples of the load sharing.
Conventions This manual uses the following typographical conventions: Typeface
Meaning
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.
|
Separates individual parameter in series of parameters. Danger: indicates an imminently hazardous situation. Failure to comply can result in death or serious injury, equipment damage, or site breakdown. Warning: indicates a potentially hazardous situation. Failure to comply can result in serious injury, equipment damage, or interruption of major services. Caution: indicates a potentially hazardous situation. Failure to comply can result in moderate injury, equipment damage, or interruption of minor services. Note: provides additional information about a certain topic.
II SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 1
Reliability Overview Reliability Introduction With the rapid development of IP technology, various value-added services are widely used on the Internet. Some important carrier-class services, such as Next Generation Network (NGN), the 3rd Generation Mobile Communications (3G), Internet Protocol Television (IPTV) stream media, special line, and Virtual Private Network (VPN), have high requirement for reliability on the Internet Protocol (IP) network. The reliability requirements of the carrier-class services on the IP network include: l l l
Device reliability Link reliability Network reliability
On the bearer network, the availability of a network device is required to reach 99.999%. In this case, the duration of service shutdown during continuous operation in a whole year must be less than 5 minutes. High reliability is a basic requirement of a carrier-class device, and it is a basic requirement for telecom operators to construct networks. As a basic network for bearer services, the reliability of the bearer network becomes an important part. On a router or a Packet Transport Network (PTN), reliability technology includes device hardware redundancy and network reliability technology. In this manual, the network reliability technology is described. Network reliability technology includes network fault detection technology and protection switching technology.
Network Fault Detection Technology The network fault detection technology includes the following detection mechanisms in accordance with network layers: l l
l l
Transport layer and physical layer: Automatic Protection Switching (APS). Link layer: Bidirectional Forwarding Detection (BFD), Multiprotocol Label Switching (MPLS) Operations, Administration and Maintenance (OAM) and Ethernet Operations, Administration and Maintenance (Eth-OAM). Network layer: HELLO mechanism of various protocols, LLO mechanism, Virtual Router Redundancy Protocol (VRRP), and BFD. Application layer: heartbeats of various application protocols.
Protection Switching Technology The protection switching technologies includes the following types: 1-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
l l
End-to-end protection: APS 1:1 linear protection, APS 1+1 linear protection and hot standby. Local protection: FRR, including IP FRR, LDP FRR, TE FRR, and PW FRR.
1-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2
Service Availability Manager Configuration Table of Contents SAMGR Overview ......................................................................................................2-1 SAMGR Configuration ................................................................................................2-4 Maintaining SAMGR...................................................................................................2-6 SAMGR Configuration Instances ................................................................................2-9
2.1 SAMGR Overview Introduction Service Availability Manager (SAMGR) is used to manage the relationship between services and the availability. The SAMGR has the following functions: l l l l
Track object management Track group management Operation, Administration and Maintenance (OAM) binding management OAM mapping management
The SAMGR implements the linkage between various detection technologies and services. It ensures the quick switch of services when the network link is faulty. In practical applications, a router provides multiple detection technologies. At the same time, there are also many protection switching applications that need to monitor detection results on a real-time basis to meet the requirements for availability in different network structures. Therefore, the SAMGR is used 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: 1. The SAMGR abstracts a detection example to a track object. It associates the track object with the detection example by configuring a trackname for the track object. The trackname is called directly in the service where the detection result needs to be monitored. 2. When detecting that the link state changes, the detection technology advertises the state change to the SAMGR directly.
2-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
3. The SAMGR informs the application service associated with the track object. The application service performs state switching in accordance with the state change to protect the link. 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.
Linkage Among VRRP, SAMGR, EOAM and BFD Figure 2-1 displays the linkage among VRRP, SAMGR, EOAM, and BFD. Figure 2-1 Linkage Among VRRP, SAMGR, EOAM and BFD
The network structure descriptions are as follows: 1. The EOAM is configured between the routers and the switches to keep links alive. BFD is configured between router A and router B. 2. Router A and router B operate in active/standby mode. The routers monitor the states of EOAM and BFD separately. 3. The VRRP runs on the directly connected interfaces between router A/router B and the switches to form a VRRP group. 4. The SAMGR monitors the results of EOAM and BFD in VRRP service in real time, thus ensuring the reliability for VRRP. When EOAM detects a fault, it reports the fault to the SAMGR. The SAMGR informs the service to switch the state directly in accordance with the relation between the track object and the service. When a fault of the pee-type BFD occurs on the router, the SAMGR advertises the state to the service, and then the service performs switching in accordance with its policy on the basis of the EOAM state and the BFD state.
Linkage of Symmetrical Dual-Connection Between CE and PE A CE connects to two PEs symmetrically to perform linkage of states between detections, see Figure 2-2.
2-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration
Figure 2-2 Linkage of Symmetrical Dual-Connection Between CE and PE
The network structure descriptions are as follows: 1. A PW is established between PE-1 and PE-3, and a PW is established between PE-2 and PE-4. 2. The CE1 connects to PE-1 and PE-2. 3. The CE2 connects to PE-3 and PE-4. 4. The OAM detection (Ethernet in the First Mile (EFM)/Connectivity Fault Management (CFM)/link keepalive) is enabled between CEs and PEs. 5. The BFD is enabled between PEs to detect PWs. MPLS OAM is enabled between PEs to detect TE Label Switched Paths (LSPs). 6. The OAM mapping/binding is associated between the Access Circuit (AC)-side link detection and PW link detection (or between LDPs) to transmit a fault. The principle of fault detection and switching is as follows: If a fault occurs on the AC between CE1 and PE–1, 1. The AC EOAM of PE–1 detects the AC fault and informs the SAMGR. 2. The SAMGR of PE–1 maps the detection track object of PW corresponding to the AC in accordance with the OAM mapping/binding configuration. 3. If BFP or MPLS-OAM is configured between PEs, PE-1 transmits the OAM fault to PE-2 transparently. 4. When PE–3 receives the BFD/MPLS OAM/LDP fault, if there is a standby PW on the remote PE, PE–3 switches the traffic. Otherwise, PE–3 performs OAM mapping/binding to map the corresponding AC and advertises the fault to CE–2. If a fault occurs on a PW, 1. BFD/MPLS OAM on a PE detects the PW/LSP fault. 2. The PE performs OAM mapping/binding to map the corresponding local AC. 3. If there is a standby PW on the PE, the PE switches traffic. Otherwise, the PE performs OAM mapping/binding to map the corresponding AC and advertises the fault to the local CE.
2-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
2.2 SAMGR Configuration Configuring a Track Object To configure a track object on the ZXR10 M6000, perform the following commands: Step
Command
Function
1
ZXR10(config)#samgr
Enters SAMGR configuration mode.
2
ZXR10(config-samgr)#track efm interface
Configures a track object with detection type
"efm".
ZXR10(config-samgr)#track cfm md
Configures a track object with detection type
<1-65535> ma <1-65535> local-mep <1-8191>
"cfm".
3
remote-mep <1-8191> 4
ZXR10(config-samgr)#track ping-detect
Configures a track object with detection type
group <1-10>
"ping-detect". The range of the Ping-detection group is 1-10.
5
6
7
ZXR10(config-samgr)#track sqa instance
Configures a track object with detection type
<1-150>
"sqa". The range of the SQA example is : 1-150.
ZXR10(config-samgr)#track mpls-oam
Configures a track object with detection type
tunnel-id <1-4000> ingress-id
"mpls-oam". The range of the mpls-oam tunnel
egress-id <egress-value>
is 1-4000.
ZXR10(config-samgr)#track link-bfd { ipv4
Configures a track object with detection type
< remote-ipv4-address >| ipv6 <
"link-bfd".
local-ipv6-address >< remote-ipv6-address >} interface[vrf ] 8
ZXR10(config-samgr)#track peer-bfd { ipv4
Configures a track object with detection type
| ipv6 <
"peer-bfd".
local-ipv6-address>}[vrf ] 9
ZXR10(config-samgr)#track ldp-bfd
Configures a track object with detection type
fec-address < fec-address > mask-length <1-32>
"ldp-bfd". interval <10-990> indicates the
interval <10-990> min-rx <10-990> multiplier <3-50>
minimum interval for sending BFD packets, and min-rx <10-990> indicates the minimum interval for receiving BFD packets.
10
ZXR10(config-samgr)#track rsvp-bfd
Configures a track object with detection type
tunnel-id <1-4000> interval <10-990> min-rx <10-990>
"rsvp-bfd".
multiplier <3-50>
2-4 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration
Step
Command
Function
11
ZXR10(config-samgr)#track pw-bfd vcid
Configures a track object with detection type
<1-4294967295> peerid{aal1 | aal2 | atm-aal5
"pw-bfd".
| atm-cell | atm-vcc | atm-vpc | cem | ceop | cesopsn-basic | cesopsn-cas | hdlc | e1 | e3 | ehter | ether-vlan | fr-dlci-martini | fr-dlci | fr-port | ip | ppp | t1 | t3}[interval <10-990> min_rx <10-990> multiplier <3-50>] 12
ZXR10(config-samgr)#track pw vcid
Configures a track object with detection type
<1-4294967295> peerid{aal1|aal2|atm-aa
"pw".
l5|atm-cell|atm-vcc|atm-vpc|cem|ceop| cesopsn-basic | cesopsn-cas | dhlc | e1 |e3| ether | ether-vlan | fr-dhci-martini | fr-dlci | fr-port | ip | ppp | t1 |t3} 13
14
ZXR10(config-samgr)#track vrrp interface
Configures a track object with detection type
vrid <1-255>
"vrrp".
ZXR10(config-samgr)#track l2-bfd session
Configures a track object with detection type
<session-name>
“l2-bfd”. <session-name> indicates the l2-bfd name (Length: 1-32 characters)
Configuring a Track Group To configure a track group on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#samgr
Enters SAMGR configuration mode.
2
ZXR10(config-samgr)#track-group
Configures a track group and enters track group configuration
mode.
ZXR10(config-samgr-track-group)#tr
Adds a track object to the track group.
3
ack 4
ZXR10(config-samgr-track-group)#inac
tive-number <1-10>
Configures the policy for a track group. inactive-number indicates the number of invalid track objects resulting in invalidity of the track group.
Configuring Binding Relation To configure the binding relationship on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#samgr
Enters SAMGR configuration mode.
ZXR10(config-samgr)#sa-bind track to {track |
Configures the binding relationship
track-group}
between track objects or between
2
track groups.
Parameter descriptions in Step 2 are as follows: 2-5 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Parameter
Description
track
Name of the passive track object, that is, the name of the track object that receives state transmission.
{track | track-group}
Name of an active track object or track group, that is, the name of the track object or track group that starts state transmission.
2.3 Maintaining SAMGR To maintain SAMGR on the ZXR10 M6000 , run the following commands: Command
Function
ZXR10#show samgr brief
Displays the brief information related to a track object.
ZXR10#show samgr track [[verbose]]
Displays the detailed information of a track object, for example, the state change information.
ZXR10#show samgr track-group [[verbose]]
Displays the detailed information of a track group, for example, the state change information.
The following is sample output from the show samgr brief command: ZXR10#show samgr brief The total of track at this Router is 7 ====================================================== Track-name
Detect-type
App-num
State
vrrp2
vrrp
0
up
oam1
mpls-oam
1
up
ping1
ping-detect
0
L-down
vrrp1
vrrp
0
up
efm1
efm
1
T-down
ping2
ping-detect
0
up
vrrp2
vrrp
0
up
Parameter descriptions are as follows: Command Output
Description
Track-name
Name of a configured track object.
Detect-type
Detection type of a track object.
App-num
Number of times that the track object is used.
State
State of the track object.
The following is sample output from the show samgr track command: ZXR10#show samgr track Track name is xx
2-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration Detect type
: peer-bfd
Track parameter Local IP: 1.1.1.1 App number
Remote IP: 1.1.1.3
Vrf name: zte
: 0
Active track : none Passive track: none Oam-mapping
: no
Track state
: unknow
State change : 0 state changes, last state change 00-00-00 00:00:00
Track name is bfd1 Detect type
: link-bfd
Track parameter Local IP: 1.1.1.1 App number
Remote IP: 1.1.1.2
Interface: fei-0/1/0/1
: 0
Active track : none Passive track: none Oam-mapping
: no
Track state
: unknow
State change : 0 state changes, last state change 00-00-00 00:00:00
Track name is tcp Detect type
: sqa
Track parameter Instance number: 4 App number
: 0
Active track : none Passive track: none Oam-mapping
: no
Track state
: local down
State change : 1 state changes, last state change 2010-07-15 17:25:43
Track name is oam1 Detect type
: mpls-oam
Track parameter Tunnel Id: 1 App number
Ingress Id: 1.2.3.4
: 1
Active track : none Passive track: none Oam-mapping
: no
Track state
: up
State change : 1 state changes, last state change 2010-07-15 17:26:14
ZXR10(config)#show samgr track sqa verbose Track name is sqa
2-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) State change record:
1
old state
new state
change time
unknown
local down
2010-07-19 02:57:28
2
local down
up
2010-07-19 03:05:16
3
up
local down
2010-07-19 03:06:24
4
local down
up
2010-07-19 03:08:00
5
up
local down
2010-07-19 03:08:13
Parameter descriptions are as follows: Command Output
Description
Track name
Name of a track object.
Detect type
Detection type of track object.
Track parameter
Parameters of a track object.
App number
Number of times that the track object is used.
Active track
Whether to act as a passive track to receive state information from the active track.
Passive track
Whether to act as an active track to send the state information to the passive track.
Oam-mapping
Whether the track has the OAM mapping ID.
Track state
The state of the track object.
State change
The state change information of the track object.
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.
change time
The state change time of the track object.
The following is sample output from the show samgr track-group command: ZXR10#show samgr track-group Track-group name: aaa Set inactive number: all App number: 0 Track-group state: up Track-group member: 0 ------------------------------Track-group name: group1 Set inactive number: 1 App number: 0 Track-group state: local down Track-group member: 3 Track name: ping3
State: up
Track name: ping2
State: up
Track name: ping1
State: local down
ZXR10(config)#show samgr track-group 1 verbose
2-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration Track name is 1 State change record: old state
new state
change time
1
up
local down
2010-07-19 03:14:43
2
local down
up
2010-07-19 03:14:50
3
up
local down
2010-07-19 03:14:56
4
local down
up
2010-07-19 03:15:01
Parameter descriptions are as follows: Command Output
Description
Track-group name
Name of a track group.
Set inactive number
Policy for a track group.
App number
Number of times that the track object is used.
Track-group member
Members in a track group .
Track name
Name of track objects that are bound to the track group.
State
State of the track object.
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.
change time
The state change time of the track group.
2.4 SAMGR Configuration Instances 2.4.1 Linkage between EFM and VRRP Configuration Description The VRRP protocol is used between R2 and R3. The VRRP virtual address is the interface address 10.0.0.1. The R2 operates as a master router, see Figure 2-3. Figure 2-3 Linkage between EFM and VRRP
2-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Configuration Flow 1. Configure the EFM connection for the directly-connected interfaces between S1 and R2. 2. Configure an EFM track object for the directly-connected interface of R2 in SAMGR configuration mode. 3. Configure the same VRRP group number and virtual address for R2 and R3. To set R2 as a master router, bind the VRRP of R2 to the EFM track object. 4. When the EFM function is disabled on S1, the VRRP group on R2 is changed to the Init status, and the VRRP group on R3 is changed to the Master status. When the EFM function is enabled, the VRRP group on R2 is changed to the Master status, and the VRRP group of R3 is changed to the Backup status.
Configuration Command Run the following commands on S1: S1(config)#set ethernet-oam enable S1(config)#interface gei_4/1 S1(config-gei_4/1)#set ethernet-oam
enable
Run the following commands on R2: R2(config)#interface gei-0/2/0/1 R2(config-if)#ip address 10.0.0.1 255.255.0.0 R2(config-if)#exit R2(config)#interface gei-0/3/0/2 R2(config-if)#ip address 192.168.0.1 255.255.0.0 R2(config-if)#exit
R2(config)#efm R2(config-efm)#set ethernet-oam function enable R2(config-efm)#interface gei-0/2/0/1 R2(config-efm-if)#set ethernet-oam function enable R2(config-efm-if)#exit R2(config-efm)#exit
R2(config)#samgr R2(config-samgr)#track efm efm interface gei-0/2/0/1 R2(config-samgr)#exit
R2(config)#vrrp R2(config-vrrp)#interface gei-0/2/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 1 out-interface gei-0/3/0/2 R2(config-vrrp-if)#vrrp 1 track object efm link-type R2(config-vrrp-if)#exit
Run the following commands on R3: 2-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration R3(config)#interface gei-0/5/0/1 R3(config-if)#ip address 10.0.0.2 255.255.0.0 R3(config-if)#exit R3(config)#interface gei-0/6/0/2 R3(config-if)#ip address 192.168.0.2 255.255.0.0 R3(config-if)#exit
R3(config)#vrrp R3(config-vrrp)#interface gei-0/5/0/1 R3(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R3(config-vrrp-if)#vrrp 1 out-interface gei-0/6/0/2 R3(config-vrrp-if)#end
Configuration Verification Check the VRRP configuration results on R2 and R3. The results show that R2 is a master router and R3 is a backup router. The output of the show samgr command on R2 shows that the EFM track object is in up state. R2#show vrrp ipv4 brief Interface
vrID
Pri
Time
A P L State
Master addr
VRouter addr
gei-0/2/0/1
1
255
1000
A P
10.0.0.1
10.0.0.1
Master
R2#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
efm
efm
App-num
State
1
up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
A P L State
100 1000
P
Backup
Master addr
VRouter addr
10.0.0.1
10.0.0.1
When the EFM function on S1 is disabled , the status of the VRRP group on R2 is changed from Master to Init, and that of R3 is changed to Master. The output of the show samgr command on R2 shows that the EFM track object is in local down status. S1(config)#set ethernet-oam enable S1(config-efm)#set ethernet-oam
function disable
S1(config-efm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
gei-0/2/0/1
1
A P
255 1000
Init
Master addr 0.0.0.0
VRouter addr 10.0.0.1
R2#show samgr brief The total of track at this Router is 1.
2-11 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) ============================================================================ Track-name
Detect-type
App-num
State
efm
efm
1
L-down
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
A P L State
100 1000
P
Master addr
Master 10.0.0.2
VRouter addr 10.0.0.1
When the EFM function on S1 is enabled, the status of the VRRP group on R2 is changed to Master, and that of R3 is changed to Backup. The EFM track object on R2 is in up status. S1(config)#set ethernet-oam enable S1(config-efm)#set ethernet-oam
function enable
S1(config-efm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/2/0/1
1
100 1000
A P L State P
Master
Master addr
VRouter addr
10.0.0.1
10.0.0.1
R2#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
App-num
State
efm
efm
1
up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Backup
Master addr
VRouter addr
10.0.0.1
10.0.0.1
2.4.2 Linkage between CFM and VRRP Configuration Description The VRRP protocol is used between R2 and R3. The VRRP virtual address is the interface address 10.0.0.1 of R2 that operates as a master router. For the network structure, see Figure 2-4.
2-12 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration
Figure 2-4 Link between CFM and VRRP
Configuration Flow 1. Configure the CFM continuous detection for the directly-connected interfaces between S1 and R2. 2. Configure a CFM track object for the directly-connected interface of R2 in SAMGR configuration mode. 3. Configure the same VRRP group number and virtual address for R2 and R3. To set R2 as a master router, bind VRRP of R2 to the track object with the detection type "CFM". 4. When the CFM function on S1 is disabled, the status of the VRRP group onR2 is changed to the Init status, and that of R3 is changed to the Master status. When the CFM function on S1 is enabled, the status of the VRRP group on R2 is changed to Master, and that of R3 is changed to Backup.
Configuration Command Run the following commands on S1: S1(config)#cfm enable S1(config)#cfm ccm-format 1 S1(config)#cfm create md session 1 name md2 level 7 S1(config-md)#ma create session 1 name a4 S1(config-md-ma)#create mep session 1 8 direction down S1(config-md-ma)#create rmep session 1 16 remote-mac 00d0.d011.3377 S1(config-md-ma)#assign mep 8 to interface gei_4/1 S1(config-md-ma)#mep 8 state enable S1(config-md-ma)#mep 8 ccm-send enable S1(config-md-ma)#mep 16 state enable
Run the following commands on R2: R2(config)#interface gei-0/2/0/1 R2(config-if)#ip address 10.0.0.1 255.255.0.0 R2(config-if)#exit R2(config)#interface gei-0/3/0/2 R2(config-if)#ip address 192.168.0.1 255.255.0.0 R2(config-if)#exit
2-13 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
R2(config)#cfm R2(config-cfm)#set cfm enable R2(config-cfm)#create md index 2 name-format 2 name md2 level 7 R2(config-cfm)#md index 2 R2(config-cfm-md)#create ma index 4 name-format 2 name a4 R2(config-cfm-md)#ma index 4 R2(config-cfm-ma)#create mep mepid 16 direction down interface gei-0/2/0/1 R2(config-cfm-ma)#create rmep mepid 8 remote-mac 00a1.1122.0011 lmep 16 R2(config-cfm-ma)#set mep 16 state enable R2(config-cfm-ma)#set mep 16 ccm-send enable R2(config-cfm-ma)#set mep 8 state enable R2(config-cfm-ma)#exit R2(config-cfm-md)#exit R2(config-cfm)#exit
R2(config)#samgr R2(config-samgr)#track cfm cfm md 2 ma 4 local-mep 16 remote-mep 8 R2(config-samgr)#exit
R2(config)#vrrp R2(config-vrrp)#interface gei-0/2/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 1 out-interface gei-0/3/0/2 R2(config-vrrp-if)#vrrp 1 track object cfm link-type R2(config-vrrp-if)#exit
Run the following commands on R3: R3(config)#interface gei-0/5/0/1 R3(config-if)#ip address 10.0.0.2 255.255.0.0 R3(config-if)#exit R3(config)#interface gei-0/6/0/2 R3(config-if)#ip address 192.168.0.2 255.255.0.0 R3(config-if)#exit
R3(config)#vrrp R3(config-vrrp)#interface gei-0/5/0/1 R3(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R3(config-vrrp-if)#vrrp 1 out-interface gei-0/6/0/2 R3(config-vrrp-if)#end
Configuration Verification Check the VRRP configuration results on R2 and R3. The results show that R2 is a Master router and R3 is a Backup router. The output of the show samgr command shows that the CFM track object is in up status. 2-14 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
gei-0/2/0/1
1
A P
255 1000
Master addr
VRouter addr
Master 10.0.0.1
10.0.0.1
R2(config)#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
cfm
cfm
App-num
State
1
up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Master addr
Backup 10.0.0.1
VRouter addr 10.0.0.1
When the CFM function on S1 is disabled, the status of the VRRP group on R2 is changed from Master to Init, and that of R3 is changed to Master. The CFM track object of R2 is in local down status. S1(config)#cfm disable S1(config-cfm)#set cfm disable S1(config-cfm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
Master addr
VRouter addr
gei-0/2/0/1
1
A P
0.0.0.0
10.0.0.1
255 1000
Init
R2#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
cfm
cfm
App-num 1
State L-down
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Master
Master addr
VRouter addr
10.0.0.2
10.0.0.1
When the CFM function on S1 is enabled, the status of the VRRP group on R2 is changed to Master, and that of R3 is changed to Backup. The CFM track object of R2 is in up status. S1(config)#cfm enable S1(config-cfm)#set cfm enable S1(config-cfm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
Master addr
VRouter addr
gei-0/2/0/1
1
A P
10.0.0.1
10.0.0.1
255 1000
Master
R2#show samgr brief
2-15 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
cfm
cfm
App-num 1
State up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Backup
Master addr
VRouter addr
10.0.0.2
10.0.0.1
2-16 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3
VRRP Configuration Table of Contents VRRP Overview .........................................................................................................3-1 VRRP Network Application .........................................................................................3-4 Configuring VRRP ......................................................................................................3-8 Maintaining VRRP ....................................................................................................3-11 VRRP Configuration Instances .................................................................................3-13
3.1 VRRP Overview Introduction With the development of Internet, the requirements for network reliability is ever increasing. For Local Area Network (LAN) users, it is important to keep communications with external networks. The same default route is set for all hosts in the internal network to the egress network gateway (router A in Figure 3-1). With the default route, hosts in the internal network communicate with external network. If a fault occurs on the egress network gateway, the communication between the hosts and the external network will be interrupted. Figure 3-1 Default Network Gateway in LAN
A common method to improve system reliability is to configure multiple egress network gateways. Because hosts in LANs normally do not support dynamic routing protocols, it is a problem to select a route among multiple egress network gateways.
3-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
The Virtual Router Redundancy Protocol (VRRP) is a fault-tolerant protocol. The VRRP can implement routing among multiple egress network gateways by isolating physical devices from logical devices. After that, the problem is solved. In LANs with multicasting or broadcasting ability (such as Ethernet), the VRRP provides a logical network gateway to ensure that transmission links are used fully. This not only avoids service interruption due to faults on a network gateway device, but also avoids modification of routing protocol configuration.
VRRP Election Flow The VRRP forms a virtual router with the router A and router B in a LAN, see Figure 3-2. Figure 3-2 VRRP Election Flow
The virtual router has its own IP address 10.100.10.1 (this IP address can be the same with an interface address on a router). Route A and router B also have their own IP addresses (IP address of router A is 10.100.10.2 and IP address of router B is 10.100.10.3). Hosts in the LAN only knows the IP address 10.100.10.1 of the virtual router. Hosts do not know the IP addresses of router A and Router B. Router A and router B set the IP address 10.100.10.1 of the virtual router as their default routes. Therefore, hosts in the LAN communicate with other networks through this virtual router. The virtual router needs to perform the following operations: 1. The virtual router selects a master router in accordance with the priority. The router with the highest priority becomes the master router and its state is Master. If the priorities are the same, the master IP addresses on interfaces are compared. The router with the greater master IP address on an interface becomes the master router. The master router provides routing service. 2. The other router operates as a backup router. It detects the state of the master router at any time. 3-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
l
l l
When the master router works properly, it sends a VRRP multicasting message at a certain interval to inform the backup router in the group that the master router works properly. If the backup router in the group does not receive messages from the master router for a long time, the backup router changes its state to Master. When there are several backup routers in the group, there might be several master routers at this time. In this situation, each master router 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 router changes its state to Backup. Otherwise, the master keeps its state.
In this way, the router with the highest priority becomes the new master router. The VRRP backup function is completed.
VRRP Router States The routers that form the virtual router have three states, Initialize, Master, and Backup. The states descriptions are as follows: l
Initialize A router enters this state after the system is started. When an interface receives a startup message, the router becomes Backup state (when the priority is not 255) or Master state (when the priority is 255). In Initialize state, the router does not handle VRRP messages.
l
Master When a router is in Master state, it performs the following operations: 1. It sends VRRP multicasting messages periodically. 2. It sends free Address Resolution Protocol (ARP) messages to make virtual Medium Access Control (MAC) address that corresponds to the virtual IP address known by all hosts in the network. 3. It replies to the ARP request for the virtual IP address with the virtual MAC address instead of the real MAC address on the interface. 4. It forwards IP messages of which the destination MAC address is the virtual MAC address. In Master state, when the router receives a VRRP message in which the priority is higher than the priority of the router, the router enters the Backup state. When it receives a Shutdown event, the router enters the Initialize state.
l
Backup When a router is in Backup state, it performs the following operations: 1. It receives VRRP multicasting messages from the master router to know the state of the master router. 2. It does reply to the ARP requests for the virtual IP address. 3. It drops IP messages of which the destination IP address is the virtual IP address. For the state conversion, see Figure 3-3. 3-3
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Figure 3-3 State Conversion in VRRP
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 router.
3.2 VRRP Network Application VRRP Monitoring Interface State The VRRP provides a function to monitor interface states. That is, the VRRP not only provides the backup function if a fault occurs on an interface in the backup group, but also for a fault occurring on another interface on routers. When the monitored interface state is down, the priority of the router decreases by a certain value automatically, which makes the priorities of other routers in the backup group be higher than the priority of this router. This urges master/slave router changeover. The router with the highest priority becomes the master router and the changeover is completed. For an application of VRRP monitoring interface, see Figure 3-4. Figure 3-4 Application of VRRP Monitoring Interface
3-4 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
In Figure 3-4, the VRRP Group 1 monitors the interface marked with a red point on router A. When the interface works properly, router A acts as the master router. When the interface is down, the priority of router A is decreased. As a result, the priority of router A is lower than that of router B. In this way, master/backup changeover is completed.
VRRP Load Sharing Load sharing means that several routers bear services at the same time to avoid occurrence of idle routers. Therefore, it is necessary to create two or more backup groups to implement load sharing, see Figure 3-5. Figure 3-5 Application of VRRP Load Sharing
The load sharing function has the following features: l l l
Each backup group contains a Master device and several Backup devices. The Master devices in the backup groups can be different. A router can be added into different backup groups, and the router has different priorities in these backup groups. 1. Application scene descriptions of VRRP load sharing l In Figure 3-5, the VRRP Group 1 (with virtual IP address 10.0.0.1) and the VRRP Group 2 (with virtual IP address 10.0.0.100) are configured on the same interfaces on router A and router B. l The real IP address of physical router A is 10.0.0.2, and the real IP address of physical router B is 10.0.0.3. l The default gateway of a part of hosts in the LAN is 10.0.0.1, and the default gateway of the other part of hosts in the LAN is 10.0.0.100. 2. Working mechanism Router A and router B have the following agreements during the VRRP negotiation through priority configuration of the backup groups on router A and router B: l l l
Router A operates as the master router in Group 1 and operates as a backup router in Group 2. Router B operates as the master router in Group 2 and operates as a backup router in Group 1. A part of the hosts uses the backup group 1 as the gateway and the traffic is sent through router A. The other part of the hosts uses the backup group 2 as the gateway and the traffic is sent through router B. 3-5
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
In this way, the data flows are shared and backed up.
VRRP Heartbeat Configuration In some applications, there is no layer 2 forwarding device under the routers and the protocol packet cannot be sent through the interface on which a VRRP group is configured. In this case, the VRRP heartbeat must be configured. If a heartbeat is configured in the VRRP group, the VRRP protocol packet is sent through the heartbeat interface. If a heartbeat is not configured in the VRRP group, the out-interface is the interface on which a VRRP is configured.
VRRP Track Configuration There are three applications of VRRP link detection. l
Application one The VRRP protocol is used between router A and router B. These two routers are used for master/backup selection. The 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. Figure 3-6 EOAM for VRRP Application One
For the state transfer of EOAM for VRRP, see Figure 3-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, the VRRP transfers to the initialize state directly. When all VRRP interfaces are in up state and VRRP is in initialize state, the 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.
3-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Figure 3-7 VRRP and EOAM State Transfer
l
Application two The VRRP protocol is used between router A and router B, and these two routers are used for master/backup selection, see Figure 3-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. Figure 3-8 EOAM for VRRP Application Two
For the state transfer of EOAM (or link BFD) + peer BFD for VRRP, see Figure 3-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, the VRRP is in initialize state, the 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 the VRRP is in backup state, and the VRRP receives the link fault notified by peer BFD, the VRRP will transfer to the master state.
3-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Figure 3-9 VRRP and EOAM + Peer BFD State Transfer
l
Application three The VRRP protocol is used between router A and router B, see Figure 3-10. These two routers are used for master/backup selection. The EOAM (including EFM and CFM) is used to detect the link states between router A and router C, and between router B and router C. The state of EOAM for VRRP transfers in accordance with the VRRP protocol negotiation. When receiving the link fault notified by EOAM, the VRRP decreases the priority based on configuration and triggers master/slave router changeover. Figure 3-10 EOAM for VRRP Application Three
3.3 Configuring VRRP To configure VRRP on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#vrrp
Enters VRRP configuration mode.
2
ZXR10(config-vrrp)#interface
Enters VRRP interface configuration mode.
3-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Step
Command
Function
3
ZXR10(config-vrrp-if)#vrrpipv4
Configures VRRP virtual IPv4 address in VRRP
>[secondary]
interface configuration mode. indicates the virtual router ID. Range: 1-255.
4
ZXR10(config-vrrp-if)#vrrp priority
Configures VRRP priority in VRRP interface configuration mode. Range: 1-254, default: 100.
5
ZXR10(config-vrrp-if)#vrrp preempt [delay
Configures VRRP group pre-emption in VRRP
<seconds>]
interface configuration mode.<seconds> indicates pre-emption delay. Range: 0-3600 seconds, default: 0.
6
ZXR10(config-vrrp-if)#vrrp timers advertise
Configures the interval to send VRRP
{<1-40>|[msec <50-40000>]}
advertisements in VRRP interface configuration mode. The default value of interval is 1 second. Unit for <1-40> is second, and unit for <50-40000> is millisecond. The parameter msec is optional and it changes the unit of the interval to millisecond from second.
7
ZXR10(config-vrrp-if)#vrrp timers learn
Configures whether sending interval is learnt from the notification packets. The default configuration is not learning.
8
ZXR10(config-vrrp-if)#vrrp track interface
Configures a VRRP track interface in VRRP
[priority-decrement <1-254>|
interface configuration mode. When the priority
rapid-down]
decrement is not specified, the default priority is decreased by 10. Any link state is not traced by default.
9
ZXR10(config-vrrp-if)#vrrp out-interface
Configures VRRP heartbeat in VRRP interface
configuration mode, that is to configure a out-interface for VRRP packets.
10
ZXR10(config-vrrp-if)#vrrp text-authenticat
Configures a VRRP authentication string in
ion <string>
VRRP interface configuration mode. The string consists of 1-8 characters. (This configuration is only available for version 2 of the VRRP.)
11
12
ZXR10(config-vrrp-if)#vrrp track {
Configures VRRP detection group, detection
group | object}<string>{ link-type | peer-type |
object, or policy type in VRRP interface
priority-decrement <1-254>}
configuration mode.
ZXR10(config-vrrp-if)#vrrp version {2|3}
Configures VRRP version in VRRP interface configuration mode. v2 supports IPv4 configuration, and v3 supports IPv4 and IPv6 configuration.
3-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Step
Command
Function
13
ZXR10(config-vrrp-if)#vrrp accept
Enables the accept function in VRRP interface configuration mode. This function is enabled by default.
14
ZXR10(config-vrrp-if)#vrrp check-ttl
Enables tje check-ttl function in VRRP interface configuration mode, default: enabled.
15
16
ZXR10(config-vrrp-if)#vrrp admin-group {
Configures VRRP administration group function
owner | interface vrid <1-255>}
in VRRP interface configuration mode.
ZXR10(config-vrrp-if)#vrrp send-mode {all |
Configures the mode to send packets on an
rotation}
egress interface (heartbeat line) of VRRP. l
All: All heartbeat lines send packages at the same time.
l
Rotation: The heartbeat line sends packages in polling mode.
Parameter descriptions in Step 3 are as follows: Parameter
Description
ID of the virtual router. Range: 1-255.
ipv4
VRRP IPv4 virtual address.
IP address of the virtual router.
secondary
A secondary IP address supported by the virtual router.
Parameter descriptions in Step 8 are as follows: Parameter
Description
priority-decrement
Decreases the priority for a specified tracing link. By default, the priority is decreased by 10.
rapid-down
The priority is switched to 1 immediately. If this command is run on VRRP master router, a special message will be sent to a Backup router. In this case, the backup router will be switched to a master router immediately.
Parameter descriptions in Step 11 are as follows: Parameter
Description
ID of the virtual router. Range: 1-255.
group
Track group.
object
Track object.
string
Name of a track group or track object.
3-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Parameter
Description
link-type
Link-type.
peer-type
Peer-type.
priority-decrement <1-254>
Priority decrement.
Parameter descriptions in Step 15 are as follows: Parameter
Description
ID of the virtual router. Range: 1-255.
owner
The current group is the administration group that receives packets and manages link states.
Interface name of the administration group.
vrid <1-255>
Virtual router ID of the administration group. Range: 1-255.
3.4 Maintaining VRRP To maintain VRRP on the ZXR10 M6000, run the following commands: Command
Function
ZXR10#show vrrp ipv4 brief
Displays the brief information of all IPv4 VRRP groups on a router.
ZXR10#show vrrp ipv4 brief interface
Displays the brief information of all IPv4 VRRP groups on a specific interface.
ZXR10#show vrrp interface[vrid <1-255>]
Displays the detailed information of all VRRP groups or a specified group on a specified interface.
The following is sample output from the show vrrp ipv4 brief command: ZXR10#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
Master addr
fei-0/1/0/2
255
254 999
P
Master 192.168.1.10
15.15.15.1
fei-0/1/0/1
100
200 10000
P
Master 35.35.35.1
1.1.1.1
fei-0/1/0/1
120
255 157
A P L Master 35.35.35.1
VRouter addr
35.35.35.1
Parameter descriptions are as follows: Command Output
Description
Interface
Interface on which VRRP is used.
vrID
ID of the VRRP group. Range: 1-255. 3-11
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Command Output
Description
Pri
VRRP priority.
Time
The local notification time (millisecond).
A
Whether it is a owner of the virtual address, which means whether the VRRP virtual IP address is the same as the IP address of the interface.
P
Whether the preemption mode is used.
L
Whether the learning mode is used.
State
VRRP state.
Master addr
Interface address of the master router in a virtual router group.
VRouter addr
IP address of a virtual router.
The following is sample output from the show vrrp ipv4 brief interface command: ZXR10#show vrrp ipv4 brief interface fei-0/1/0/1 The total of vrrp group on this Interface is 2. ====================================================================== Interface
vrID Pri Time
A P L State
fei-0/1/0/1
100
200 10000
fei-0/1/0/1
120
255 157
P
Master addr
Master 35.35.35.1
A P L Master 35.35.35.1
VRouter addr 1.1.1.1 35.35.35.1
The following is sample output from the show vrrp interface command: ZXR10(config)#show vrrp interface smartgroup4 smartgroup4 - vrID 5 Vrrp configure info: IP version 4, VRRP version 3 Virtual IP address is 0.0.0.0 Virtual MAC address is 0000.5e00.0105 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 0 Admin-group is None Vrrp run info: State is Init 0 state changes, last state change 00:00:00 Current priority is 100 Master router is unknown
3-12 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration 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.609 sec, no learn
Parameter descriptions are as follows: Command Output
Description
Decrement-Priority
The decreased priority after the tracked interface is shut down.
Tracked interface
The tracked interface.
Track name
The name of tracked group or object.
Track type
The track type, including detection group and detection object.
Detect type
The link detection type, which is configured in SAMGR configuration.
Master router is local
This router is the master router is the virtual router group.
3.5 VRRP Configuration Instances 3.5.1 Basic VRRP Configuration Example Configuration Description The VRRP protocol is used between the R1 and the R2. The interface address of the R1 is set to 10.0.0.1 and that of the R2 is set to 10.0.0.2. The VRRP virtual address is the interface address 10.0.0.1 on the R1. In this case, the R1 is the IP address owner and has the highest priority 255. The R1 operates as the master router. The VRRP virtual address can also be set to another address. When the R1 is configured with the highest priority, the R1 is the master router. For the network structure, see Figure 3-11. Figure 3-11 Basic VRRP Configuration (IPv4)
3-13 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Configuration Flow 1. Enter the interfaces on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode and then enter the interface on which the VRRP is to be configured. 3. Configure the same VRRP group ID and virtual address for the R1 and the R2. To make the R1 the master router or specify a higher priority for the R1, configure related commands on the R1 first. If the priorities (the default priority is 100) of two routers are the same, the router becomes the master router in the group, on which VRRP is enabled and messages are advertised first.
Configuration Command Run the following commands on the R1: R1(config)#interface fei-0/1/0/1 R1(config-if)#ip address 10.0.0.1 255.255.0.0 R1(config)#vrrp R1(config-vrrp)#interface fei-0/1/0/1 R1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
Run the following commands on the R2: R2(config)#interface fei-0/1/0/1 R2(config-if)#ip address 10.0.0.2 255.255.0.0 R2(config)#vrrp R2(config-vrrp)#interface fei-0/1/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
Configuration Verification View the VRRP information and configuration result on the R1, which is displayed as follows: R1#show vrrp ipv4 brief Interface fei-0/1/0/1
vrID Pri Time A P L State 1
255 1000 A P
Master addr VRouter addr
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.*/
R1#sho vrrp interface fei-0/1/0/1 vrid 1 fei-0/1/0/1 - vrID 1 Vrrp configure info:
/*VRRP configuration information*/
IP version 4, VRRP version 3 Virtual IP address is 10.0.0.1 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec
3-14 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 0 Admin-group is None Vrrp run info: State is Master
/*Running information of VRRP on current interface*/ /*VRRP running state*/
1 state changes, last state change 22:50:03 6 day(s) /*Number of state changes and the time for how long the system has been running until the last change. If there is no change, the value is 0.*/ Current priority is 255 /*Current priority, the largest priority of the Owner is 255*/ Master router is local Master router address is 10.0.0.1 Master router priority is 255 Master Advertisement interval is 1.000 sec Master Down interval is 3.003 sec, no learn R1#
3.5.2 Symmetrical VRRP Configuration Example Configuration Description Symmetrical VRRP means load sharing is supported. In this example, two VRRP groups are configured. PC1 and PC2 use the virtual router in Group 1 as the default network gateway, and the address is 10.0.0.1. PC3 and PC4 use the virtual router in Group 2 as the default network gateway, and the address is 10.0.0.2. The R1 and R2 provide backups for each other. When both R1 and R2 become invalid, the communications between the hosts and external network will be interrupted. For the network structure, see Figure 3-12.
3-15 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Figure 3-12 Symmetrical VRRP Configuration (IPv4)
Configuration Flow 1. Enter the interfaces on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode and then enter the interface on which the VRRP is to be configured. 3. Configure VRRP Group 1 and corresponding virtual address on R1, and configure VRRP Group 2 and corresponding virtual address on R2. Specify a higher priority for VRRP Group 1 on R1 and VRRP Group 2 on R2. After that, R1 is the master router in Group 1 and the backup router in Group 2, and R2 is the master router in Group 2 and the backup router in Group 1. The R1 and R2 provide backups for each other.
Configuration Command Run the following commands on the R1: R1(config)#interface fei-0/1/0/1 R1(config-if)#ip address 10.0.0.1 255.255.0.0 R1(config)#vrrp R1(config-vrrp)#interface fei-0/1/0/1 R1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R1(config-vrrp-if)#vrrp 2 ipv4 10.0.0.2
Run the following commands on the R2: R2(config)#interface fei-0/1/0/1 R2(config-if)#ip address 10.0.0.2 255.255.0.0 R2(config)#vrrp R2(config-vrrp)#interface fei-0/1/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 2 ipv4 10.0.0.2
3-16 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Configuration Verification Check the VRRP information and configuration result on R1, as shown below. R1#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
fei-0/1/0/1
1
255 1000
A P
Master 10.0.0.1
Master addr
VRouter addr 10.0.0.1
fei-0/1/0/1
2
100 1000
P
Backup 10.0.0.2
10.0.0.2
/*A: whether the router is the address owner. P: whether preemption is configured. L: whether to learn the interval for sending VRRP messages from the master.*/
R1#show vrrp interface fei-0/1/0/1 vrid 1 fei-0/1/0/1 - vrID 1 Vrrp configure info:
/*VRRP configuration information*/
IP version 4, VRRP version 3 Virtual IP address is 10.0.0.1 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 0 Admin-group is None Vrrp run info: State is Master
/*Operation information of VRRP on current interface*/ /*VRRP operation state*/
1 state changes, last state change 22:50:03 6 day(s) /*Number of state changes and the time for how long the system has been operated until the last change. If there is no change, the value is 0.*/ Current priority is 255 /*current priority, the largest priority of the Owner is 255*/ Master router is local Master router address is 10.0.0.1 Master router priority is 255 Master Advertisement interval is 1.000 sec Master Down interval is 3.003 sec, no learn R1#
3-17 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
3.5.3 VRRP Heartbeat Configuration Example Configuration Description The VRRP protocol is used between R1 and R2. The VRRP virtual address is the interface address 10.0.0.1 of R1. R1 operates as the master router. For the network structure, see Figure 3-13. Figure 3-13 VRRP Heartbeat Configuration (IPv4)
Configuration Flow 1. Enter the interfaces on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode and then enter the interface on which the VRRP is to be configured. 3. Configure the same VRRP group ID and virtual address for R1 and R2. To make R1 as the master router, specify a higher priority for R1, or set it to be the IP address owner (The interface address of R1 is set as the virtual address and R1 has the highest priority 255). 4. In VRRP interface configuration mode of R1 and R2, configure egress interfaces for packets in the VRRP group to ensure that packets can be sent and received through these two egresses.
Configuration Command Run the following commands on R1: R1(config)#interface fei-0/1/0/1 R1(config-if)#ip address 10.0.0.1 255.255.0.0 R1(config)#vrrp R1(config-vrrp)#interface fei-0/1/0/1 R1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R1(config-vrrp-if)#vrrp 1 out-interface fei-0/1/0/2
Run the following commands on R2: 3-18 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration R2(config)#interface fei-0/1/0/1 R2(config-if)#ip address 10.0.0.2 255.255.0.0 R2(config)#vrrp R2(config-vrrp)#interface fei-0/1/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 1 out-interface fei-0/1/0/2
Configuration Verification Check the VRRP information and configuration results on R1, which are displayed as follows: R1#show vrrp ipv4 brief Interface
vrID
fei-0/1/0/1
1
Pri
Time
A
P
255
1000
A
P
L State Master
Master addr
VRouter addr
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.*/
R1#show vrrp interface fei-0/1/0/1 vrid 1 fei-0/1/0/1 - vrID 1 Vrrp configure info: /*VRRP configuration information*/ IP version 4, VRRP version 3 Virtual IP address is 10.0.0.1 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Out-interface(heartbeat line) is fei-0/1/0/2 Tracked interface items: 0 Interface
State
Policy
Reduce-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*/ 2 state changes, last state change 00:00:00 /*Number of state changes and the time for how long the system has been running until the last change. If there is no change, the value is 0.*/ Current priority is 255 /*Current priority, the largest priority of the Owner is 255*/
3-19 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Master router is local Master router address is 10.0.0.1 Master router priority is 255 Master Advertisement interval is 1.000 sec Master Down interval is 3.003 sec, no learn
3.5.4 VRRP BFD Configuration Example Configuration Description The VRRP protocol is used between Router A and Router B. The VRRP virtual IP address is 10.0.0.3. For the network structure, see Figure 3-14. Figure 3-14 VRRP Track Configuration (IPv4)
Configuration Flow 1. Enter the interface on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode, and then enter the interface on which the VRRP is to be configured. 3. Configure the same VRRP group ID and virtual IP addre for Router A and Router B. To set Router A as the master router, specify a higher priority for Router A, or set it to be the IP address owner (The interface address of Router A is set as the virtual address and Router A has the highest priority 255). 4. Enter SAMGR configuration mode of Router A and Router B to configure a detection object respectively. Configure the Ethernet Operation, Administration and Maintenance (EOAM) object for Router A and Router B, and then configure the Bidirectional Forwarding Detection (BFD) object. 5. Enter VRRP interface configuration mode of Router A and Router B, enable VRRP track function to track the objects configured in Step 4 respectively.
Configuration Command Run the following commands on Router A: 3-20 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration RA(config)#interface fei-0/1/0/1 RA(config-if)#ip address 10.0.0.1 255.255.0.0 RA(config-if)#exit RA(config)#vrrp RA(config-vrrp)#interface fei-0/1/0/1 RA(config-vrrp-if)#vrrp 1 ipv4 10.0.0.3 RA(config-vrrp-if)#vrrp 1 track object zte1 link-type RA(config-vrrp-if)#vrrp 1 track object zte2 peer-type
The tracked object named zte1 and zte2 should be configured in the SAMGR module in advance. For the detailed configuration, refer to the “SAMGR Configuration” chapter. Run the following commands on Router B: RB(config)#interface fei-0/1/0/1 RB(config-if)#ip address 10.0.0.2 255.255.0.0 RB(config-if)#exit RB(config)#vrrp RB(config-vrrp)#interface fei-0/1/0/1 RB(config-vrrp-if)#vrrp 1 ipv4 10.0.0.3 RB(config-vrrp-if)#vrrp 1 track object zte1 link-type RB(config-vrrp-if)#vrrp 1 track object zte2 peer-type
The tracked object named zte1 and zte2 should be configured in the SAMGR module in advance. For the detailed configuration, refer to the “SAMGR Configuration” chapter.
Configuration Verification Check the VRRP track information and configuration results on Router A, which is displayed as follows: RA#show vrrp ipv4 brief Interface
vrID
Pri
Time
A
P
fei-0/1/0/1
1
100
1000
A
P
L State Master
Master addr
VRouter addr
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.*/
RA#show vrrp interface fei-0/1/0/1 fei-0/1/0/1 - vrID 1 Vrrp configure info: IP version 4, VRRP version 3 Virtual IP address is 10.0.0.3 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs
3-21 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 1 Track name: zte2
Track type: object
Detect type: peer-bfd
Policy type: peer Track state: unknown Track name: zte1
Track type: object
Detect type: cfm
Policy type: link Track state: unknown Admin-group is None Vrrp run info: State is Master 155 state changes, last state change 01:12:08 Current priority is 255 Master router is local Master router address is 10.0.0.3 Master router priority is 100 Master Advertisement interval is 1.000 sec Master Down interval is 3.609 sec, no learn
3-22 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4
Ping Detect Configuration Table of Contents Ping Detect Overview .................................................................................................4-1 Configuring Ping Detect..............................................................................................4-2 Maintaining Ping Detect..............................................................................................4-3 Ping Detect Configuration Instances...........................................................................4-4
4.1 Ping Detect Overview Introduction The Ping Detect function is also called the automatic detection function. It detects the reachability of the destination through request/response messages of the ICMP. After the detection, it feeds back the detection results to the related backup functional module to trigger the active/standby switchover function based on the application of the network layer. The external router for branch router is configured with interface backup on the Ethernet interface, see Figure 4-1. Figure 4-1 Application Overview of Ping Detect
If the destination is unreachable because the Ethernet interface of the peer gateway 1 corresponding to the main link is not configured with an IP address, the backup mode that depends on the protocol status of the detection interface cannot implement the active/standby switchover function. 4-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
In the same way, if the destination of (non-direct) the main link is faulty, for example, the external dedicated line of gateway 1 is faulty, the traditional backup mechanism also cannot implement the active/standby switchover function. The detection results ( the destination ICMP is reachable or unreachable) will be fed back to the related modules, such as static route backup module, dialing backup module, and the VRRP module, to trigger the active/standby switchover operation. After that, the above faults are solved.
Ping Detect Operating Flow The whole operating flow of the Ping detection group is as follows: 1. Configure a global Ping detection group, including the address and the nexthop for the group to be detected. You can define some detection policies flexibly, such as the detection period, maximum retry times, and time-out time. You can configure the "and” or "or" relationship among multiple detection objects of a detection group. l
If the relationship among multiple objects to be detected is "and", and one IP address cannot be pinged successfully, it means that the detection group is unreachable, and it does not detect other addresses any more. l If the relationship among multiple objects to be detected is " or", and one IP address can be pinged successfully, it means that the detection group is reachable, and it does not detect other addresses any more. 2. In SAMGR configuration mode, run the track test ping-detect group command to enable the Ping Detect function. The Ping Detect group sends ICMP detection messages to the objects to be detected continuously, and confirms that the objects to be detected are reachable in accordance with the detection policies (detection times, time-out duration) defined before.
l l
Note: You can check the Ping Detect result by running the show samgr brief command. To use the Ping Detect function, the ICMP service of the firewall corresponding to the objects to be detected should be enabled.
4.2 Configuring Ping Detect To configure the Ping Detect function on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#detect-group
Configures a detection group. The range of the group number is 1-10. 4-2
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration
Step
Command
Function
2
ZXR10(config-detect)#option {And | Or}
Configures the logical relationship "and" or "or" for objects to be detected. And: It indicates that this group is connected when all items in the group are connected. Or: It indicates that this group is connected when any item in the group is connected.
3
ZXR10(config-detect)#detect-list <list-number>[vrf
Configures detection items for the detection group,
]<des-ip-address>[]
and the destination address for a detection item, and specifies the next hop address.
4
ZXR10(config-detect)#retry-times
Configures the maximum number of times that the detection group re-transmits detection results to the Ping module. Range: 1-10, default: 2.
5
ZXR10(config-detect)#loop-time <seconds>
Configures the loop detection interval for the detection results. Range: 2-86400s, default: 15s.
6
ZXR10(config-detect)#time-out <seconds>
Configures the time-out time that the detection group transmits detection results to the PING module. Range: 1-20s, default: 2s.
7
ZXR10(config-samgr)#track ping-detect
Enables the Ping Detect function in SAMGR
group
configuration mode.
4.3 Maintaining Ping Detect To maintain the ping detect function on the ZXR10 M6000, run the following commands: Command
Function
ZXR10#show running-config ping-detect
Displays the configuration of the Ping Detect function. The default value is not displayed.
ZXR10#show running-config ping-detect all
Displays the configuration of the Ping Detect function. The default value is displayed. Displays the information of the Samgr Track Ping Detect
ZXR10#show samgr track
function. Displays the Ping Detect results.
ZXR10#show samgr brief
The following is sample output from the show samgr track command: ZXR10#show samgr track Track name is test Detect type
: ping-detect
4-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Track parameter Group: 1 App-sub count
: 0
Dyn-creat count: 0 Active track
: none
Passive track
: none
Track state
: up
State change
: 3 state changes, last state change 2010-01-01 01:11:05
Parameter descriptions are as follows: Command Output
Description
Detect type
Displays the track type.
Track parameter
Displays track parameters.
Track state
Displays the track state.
4.4 Ping Detect Configuration Instances 4.4.1 Basic Ping Detect Configuration Examples Configuration Description There are three interfaces between R1 and R2. A detection group between R1 and R2 must be configured. For the network structure, see Figure 4-2. Figure 4-2 Network Structure of Basic Ping Detect Configuration Example
Addresses of the interfaces on R1 and R2 are as follows: Interface
R1
R2
IP Address
Mask
fei-0/1/0/5
100.0.0.15
255.255.255.0
fei-0/1/0/6
101.0.0.15
255.255.255.0
fei-0/1/0/7
102.0.0.15
255.255.255.0
fei-0/1/0/5
100.0.0.20
255.255.255.0
fei-0/1/0/6
101.0.0.20
255.255.255.0
fei-0/1/0/7
102.0.0.20
255.255.255.0
4-4 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration
Configuration Flow 1. 2. 3. 4.
Configure a detection group. Configure detection items for the detection group on R1. Set parameters for the detection group as required. Enable the Ping Detect function in Samgr configuration mode, and check the result by running the show command. 5. Set the logical relationship among objects to be detected to And, add a detection item that cannot be pinged successfully, and then check the detection result. Set the logical relationship among objects to be detected to Or, and then check the detection result.
Configuration Command Run the following commands to configure R1: ZXR10(config)#detect-group 1 ZXR10(config-detect)#detect-list 1 100.0.0.20 ZXR10(config-detect)#detect-list 2 101.0.0.20 ZXR10(config-detect)#detect-list 3 102.0.0.20 ZXR10(config-detect)#exit ZXR10(config)#samgr ZXR10(config-samgr)#track test ping-detect group 1 ZXR10(config-samgr)#exit
Configuration Verification Check the Ping Detect configuration results on R1: ZXR10(config)#show samgr brief The total of track at this Router is 1. ====================================================================== Track-name
Detect-type
test
ping-detect
App-num 0
State up
Set the logical relationship among objects to be detected to And, and then add a detection item that cannot be pinged successfully. ZXR10(config-detect)#option And /*Set the logical relationship for the detect object to "And"*/ ZXR10(config-detect)#detect-list 4 1.2.3.4 ZXR10(config-detect)#exit ZXR10(config)#show samgr brief The total of track at this Router is 1. ====================================================================== Track-name test
Detect-type ping-detect
App-num 0
State L-down
Set the logical relationship among objects to be detected to Or, and then check the detect result: ZXR10(config-detect)#option Or
4-5 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) /*Set the logical relationship for the detect object to "Or"*/ ZXR10(config-detect)#exit ZXR10(config)#show samgr brief The total of track at this Router is 1. ====================================================================== Track-name
Detect-type
test
ping-detect
App-num 0
State up
4.4.2 Cooperation Configuration Example Between a Directly Connected Route and the Ping Detect Configuration Description This section describes the basic functions of the cooperation between a directly connected route and the Ping Detect, see Figure 4-3. Figure 4-3 Cooperation Configuration Between a Directly-Connected Route and the Ping Detect
Configuration Flow 1. Set the IP addresses for R1, R2 and R4, enable the OSPF protocol, and create OSPF neighbor relations between routers. 2. Configure the ping detect group on R2, configure the tracing object(s) of samgr, and bind the tracing object(s) on the interface gei-0/7/1/8.
Configuration Commands Run the following commands on R1: 4-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration R1(config)#interface gei-0/0/0/8 R1(config-if)#no shutdown R1(config-if)#ip address 71.88.1.2 255.255.255.0 R1(config-if)#exit
R1(config)#router ospf 19 R1(config-ospfv2)#router-id 22.22.22.22 R1(config-ospfv2)#network 71.88.1.0 0.0.0.255 area 0 R1(config-ospfv2)#exit
Run the following commands on R2: R2(config)#interface gei-0/7/1/8 R2(config-if)#no shutdown R2(config-if)#ip address 71.88.1.1 255.255.255.0 R2(config-if)#exit R2(config)#interface gei-0/2/1/7 R2(config-if)#no shutdown R2(config-if)#exit R2(config)#interface gei-0/2/1/7.1 R2(config-subif)#ip address 41.52.17.2 255.255.255.0 R2(config-subif)#exit
R2(config)#vlan R2(config-vlan)#interface gei-0/2/1/7.1 R2(config-subvlan-if)#encapsulation-dot1q 1 R2(config-subvlan-if)#exit
R2(config)#router ospf 19 R2(config-ospfv2)#router-id 22.11.11.22 R2(config-ospfv2)#network 71.88.1.0 0.0.0.255 area 0 R2(config-ospfv2)#network 41.52.17.0 0.0.0.255 area 0 R2(config-ospfv2)#exit
R2(config)#detect-group 10 R2(config-detect)#option or R2(config-detect)#retry-times 3 R2(config-detect)#loop-time 12 R2(config-detect)#time-out 3 R2(config-detect)#detect-list 9 41.52.17.3 41.52.17.2 R2(config-detect)#detect-list 3 19.19.19.1 R2(config-detect)#detect-list 6 200.11.12.101 R2(config-detect)#detect-list 7 30.0.12.3 R2(config-detect)#detect-list 8 100.10.11.201 R2(config-detect)#detect-list 4 1.1.50.1 R2(config-detect)#exit
4-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
R2(config)#samgr R2(config-samgr)#track abc ping-detect group 10 R2(config-samgr)#exit R2(config)#interface gei-0/7/1/8 R2(config-if)#track abc R2(config-if)#exit
Run the following commands on R4: R4(config)#interface gei-0/0/0/8 R4(config-if)#no shutdown R4(config-if)#exit R4(config)#interface gei-0/0/0/8.1 R4(config-subif)#ip address 1.2.3.4 255.255.255.0 R4(config-subif)#ip address 41.52.17.3 255.255.255.0 secondary R4(config-subif)#interface mac-address offset 23 R4(config-subif)#exit
R4(config)#vlan R4(config-vlan)#interface gei-0/0/0/8.1 R4(config-subvlan-if)#encapsulation-dot1q 1 R4(config-subvlan-if)#exit
R4(config)#router ospf 19 R4(config-ospfv2)#router-id 33.33.33.33 R4(config-ospfv2)#network 41.52.17.0 0.0.0.255 area 0 R4(config-ospfv2)#exit
Configuration Verification Query the status of the tracing object(s) on R2, and you can find that the status of the tracing object is up. Run the show samgr brief command to check whether there is a new IP address for a direct routing of the interface gei-0/7/1/8 added in the protocol table, which is displayed as follows: R2(config)#show samgr brief The total of track at this Router is 1. Track-name
Detect-type
abc
ping-detect
App-num
State
1
up
R2#show ip protocol routing network 71.88.1.0 Protocol routes: status codes: *valid, >best, i-internal, s-stale
*>
Dest
NextHop
71.88.1.0/24
71.88.1.1
RoutePrf 0
RouteMetric 0
Protocol direct
4-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration *
71.88.1.0/24
71.88.1.0
110
1
ospf
*>
71.88.1.1/32
71.88.1.1
0
0
address
After disabling the gei-0/2/1/7.1 interfaces using the shutdown command, check whether the tracing state is down on R2. The direct routes of the gei-0/7/1/8 interfaces will be removed. R2#show samgr brief The total of track at this Router is 1. Track-name
Detect-type
abc
ping-detect
App-num 1
State L-down
R2#show ip protocol routing network 71.88.1.0 IPv4 Routing Table: status codes: *valid, >best Dest
Gw
Interface
Owner
Pri Metric
4-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
This page intentionally left blank.
4-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5
EFM Configuration Table of Contents EFM Overview............................................................................................................5-1 Configuring EFM ........................................................................................................5-2 Maintaining EFM ........................................................................................................5-4 EFM Configuration Instances .....................................................................................5-6
5.1 EFM Overview Introduction EFM is a standard defined by Institute of Electrical and Electronics Engineers (IEEE), and is used to detect, monitor, and maintain directly connected links. It is mainly used for monitoring and detecting the links at the access side. On the ZXR10 M6000, EFM monitors the operation state statistics of point-to-point links directly connected in physical. The EFM monitors the link operation information as much as possible, such as error rate of frame transmission, comparison of sending rate and receiving rate on the link, and loss statistics. At the same time, the EFM also detects and advertises the emergency failure and events of the system, such as system unrecoverable fault. This ensures the transmission quality on Layer 2 links to some extent, and monitors the operation state in real time. This is helpful for network administrators to maintain the network, and reduces the maintenance cost. The ZXR10 M6000 supports the following EMF functions: l l l l l
Supporting automatic negotiation with other devices Supporting remote loopback statistics detection on the links Supporting detection of link error frames and symbols Supporting emergency event advertisement Supporting linkage function handling selectively
EFM Features The EFM features are as follows: 1. The EFM detects whether the EFM function on the peer device is enabled through its protocol packets. It interacts with packets to know whether the negotiation procedure is completed in accordance with the related configurations on two devices. 2. After the negotiation, the EFM collects statistics of link operation information (such as error frames or symbols) in accordance with the link monitoring in a cycle. 5-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
3. When the number of error frames or symbols exceeds the threshold, the EFM triggers related event notification to inform the local device and the remote device. In this way, the network administrators know the operation information of the link. 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, the EFM can only be applied on the directly connected device, see Figure 5-1. Figure 5-1 EFM Principle
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.
5.2 Configuring EFM To configure EFM on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#efm
Enters EFM configuration mode
2
ZXR10(config-efm)#set ethernet-oam function <state>
Sets the switch to enable EFM globally.
3
ZXR10(config-efm)#set ethernet-oam oui <word>
Sets the Organizationally Unique Identifier (OUI) field for the EFM vendor. By default, it is set to ZTE.
4
ZXR10(config-efm)#set ethernet-oam remote-timeout
Configures the time-out time for the EFM overall loopback control. Range: 1-10, unit: second, default: 3.
5
ZXR10(config-efm)#interface
Enters EFM interface configuration mode.
5-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Step
Command
Function
6
ZXR10(config-efm-if)#set ethernet-oam function <state>
Enables the EFM function for a specific interface.
7
8
ZXR10(config-efm-if)#set ethernet-oam link-monitor function
Enables the link monitoring function
<state>
for a specific interface.
ZXR10(config-efm-if)#set ethernet-oam link-monitor frame
Configures the window value and
threshold window <win-value>
threshold value for the error frames during the link monitoring.
9
ZXR10(config-efm-if)#set ethernet-oam link-monitor
Configures the window value and
symbol-period threshold window <win-value>
threshold for the error symbols during the link monitoring.
10
ZXR10(config-efm-if)#set ethernet-oam link-monitor frame-period
Configures the window value and
threshold window <win-value>
threshold for error frames during the link monitoring.
11
ZXR10(config-efm-if)#set ethernet-oam link-monitor frame-second
Configures the window value and
threshold window <win-value>
threshold for the error frames per second during the link monitoring.
12
ZXR10(config-efm-if)#set ethernet-oam link-timeout
: Sets link time-out
{| fast {[period ]}}
time. Range: 3-20 seconds, default: 5 seconds.: Sets link time-out time. Range: 3-200 (100 millisecond), default: 50 (100 millisecond). : Sets the period that the link sends packets. Range: 1-10 (100 millisecond), default :10 (100 millisecond).
13
ZXR10(config-efm-if)#set ethernet-oam mode <mode>
Configures EFM configuration mode, including active or passive. The default mode is active.
14
ZXR10(config-efm-if)#set ethernet-oam rmt-loopback
Enables or disables the EFM link loopback function manually.
Parameter descriptions in Step 8 are as follows: Parameter
Description
Threshold of error frames. Range: 1-65535, default: 1.
<win-value>
Window value of error frame. Range: 1-60 seconds, default: 1 second.
Parameter descriptions in Step 9 are as follows: 5-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Parameter
Description
Threshold of error symbols. Range: 1-65535, default: 1.
<win-value>
Window value of error symbol. Range: 1-65535 millions, default: 1 million.
Parameter descriptions in Step 10 are as follows: Parameter
Description
Threshold of error frame cycle. Range: 1-65535 millions, default: 1 million.
<win-value>
Window value of error frame cycle. Range: 1-65535 millions, default: 1 million.
Parameter descriptions in Step 11 are as follows: Parameter
Description
Threshold of error frames per second. Range: 1-900 frames per second, default: 1 frame per second.
<win-value>
Window value of error frames per second. Range: 1-900 seconds, default: 1 second.
5.3 Maintaining EFM To maintain EFM on the ZXR10 M6000, run the following commands: Command
Function
ZXR10#debug ethernet-oam {interface < interface-name>| packet interface
Sends or receives EFM packets. Run
{dual | in | out} type {all | information| lpbk-ctrl | notify |
the no command to disable all enabled
org-spec | reqst-varb | respst-varb} mode {all-time | number}}
functions.
ZXR10#show ethernet-oam [{discovery | link-monitor
Displays the global EFM configuration,
| statistics}]
or the interface EFM configuration and state.
Parameter descriptions of the debug command are as follows: Parameter
Description
Interface name
dual
Displays the information of sent and received packets.
in
Displays the information of received packets.
out
Displays the information of sent packets.
all
Displays information of all types of EFM packets.
information
Displays the information of EFM information packets. 5-4
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Parameter
Description
lpbk-ctrl
Displays the information of EFM loopback control packets.
notify
Displays the information of EFM notification packets.
org-spec
Displays the information of packets defined by vendors.
reqst-varb
Displays the information of EFM variable-request packets.
respst-varb
Displays the information of EFM variable-response packets.
all-time
Always displays packet debugging information.
Specifies the number of packets of which the information will be displayed. Range: 10-500, default: 200.
Parameter descriptions are as follows: Parameter
Description
Interface name.
discovery
The parameter after the interface name used to display the related state information of the EFM negotiation. The parameter after the interface name used to display the related
link-monitor
information of the EFM link monitoring. The parameter after the interface name used to display the related
statistics
information of the EFM packet statistics, including sent and received packet statistics of the loopback.
The following is sample output from the show ethernet-oam command: ZXR10#show ethernet-oam fei-0/1/0/1 discovery PortId 2: Ethernet Oam enable Local DTE ---------Config: Mode
:active
Period Time
:10*(100ms)
Link time out
:50*(100ms)
Status: Parse
:forward
Multiplexer
:forward
Stable
:no
Discovery
:undone
Loopback
:off
PDU Revision
:0
Unidirection
:nonsupport
5-5 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Remote DTE ----------Config: Mode
:passive
Link Monitor
:nonsupport
Unidirection
:nonsupport
Remote Loopback
:nonsupport
Mib Retrieval
:nonsupport
PDU max size
:1518
Status: Parse
:forward
Multiplexer
:forward
Stable
:no
Mac Address
:0000.0000.0000
PDU Revision
:0
Command Output
Description
Mode
EFM working mode.
Link time out
Link time-out.
Parse
Parser state.
Multiplexer
Multiplexer state.
Stable
Local and remote stable bit.
Discovery
Identifier of discovery complete.
Loopback
Identifier of loopback enabling.
PDU Revision
Revision in the packet.
5.4 EFM Configuration Instances 5.4.1 EFM Connection Establishment Configuration Description R1 and R2 are connected directly. The EFM on the directly-connected interfaces of R1 and R2 need to be configured. For the network structure, see Figure 5-2. Figure 5-2 Network Architecture of EFM Connection Establishment
5-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Configuration Flow 1. Configure the EFM function for the interface of R1 connecting to R2 directly, enable the EFM and link-monitor switch for a specified interface, and then enable the EFM function globally. 2. Configure the EFM function for the interface of R2 connecting to R1 directly, enable the EFM and link-monitor switch for a specified interface, and then enable the EFM function globally. 3. Run the show ethernet-oam discovery command on R1 and R2 to check the EFM connection establishment. 4. Run the show ethernet-oam link-monitor command on R1 and R2 to check the count of link errors between R1 and R2.
Configuration Command Run the following commands on R1: R1#configure terminal R1(config)#efm R1(config-efm)#interface gei-0/0/1/1 R1(config-efm-if)#set ethernet-oam function enable R1(config-efm-if)#set ethernet-oam link-monitor function enable R1(config-efm-if)#exit R1(config-efm)#set ethernet-oam oui R1 R1(config-efm)#set ethernet-oam function enable R1(config-efm)#exit
Run the following commands on R2: R2#configure terminal R2(config)#efm R2(config-efm)#interface gei-0/0/0/1 R2(config-efm-if)#set ethernet-oam function enable R2(config-efm-if)# set ethernet-oam link-monitor function enable R2(config-efm-if)#exit R2(config-efm)#set ethernet-oam oui R2 R2(config-efm)#set ethernet-oam function enable R2(config-efm)#exit
Configuration Verification 1. Run the show ethernet-oam discovery command on R1 to check the link EFM negotiation, which is displayed as follows: R1(config-efm)#show ethernet-oam gei-0/0/1/1 discovery PortId 32: Ethernet Oam enable Local DTE ---------Config: Mode
:active
5-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Period Time
:10*(100ms)
Link time out
:50*(100ms)
Status:
/*local state*/
Parse
:forward
/*forwarding state of receiver*/
Multiplexer
:forward
/*forwarding state of sender*/
Stable
:yes
/*Locl link state is "stable".*/
Discovery
:done
/*Link discovery is done.*/
Loopback
:off
/*Loopback is off.*/
PDU Revision
:1
Unidirection
:nonsupport
/*Local configuration is modified once.*/
Remote DTE ----------Config: Mode
:active
Link Monitor
:support
Unidirection
:nonsupport
Remote Loopback
:support
Mib Retrieval
:nonsupport
PDU max size
:1518
Status:
/*remote state*/
Parse
:forward
/*forwarding mode*/
Multiplexer
:forward
/*forwarding mode*/
Stable
:yes
/*Remote link state is "stable".*/
Mac Address
:0001.12ac.121a
/*MAC of remote device*/
PDU Revision
:0
/*Remote configuration is modified for 0 time.*/
2. Run the show ethernet-oam link-monitor command on R1 to check the number of link errors, which is displayed as follows: R1(config-efm)#show ethernet-oam gei-0/0/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
Total Error Symbols
:0
Local Total Error Events
:0
Remote Total Error Events :0 Error Frame Event: Period Window
: 1(s)
Error Frame Threshold
: 1
Total Error Frames
: 0
Local Total Error Events
: 0
Remote Total Error Events : 0
5-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration Error Frame Period Event: Frame Window
: 1(ten thousand frames)
Error Frame Threshold
: 1
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)
Total Error Frame Seconds : 0(s) Local Total Error Frame Seconds Events
: 0
Remote Total Error Frame Seconds Events : 0
3. Run the show ethernet-oam discovery command on R2 to check the link EFM negotiation, which is displayed as follows: R2(config)#show ethernet-oam gei-0/0/0/1 discovery PortId 66: Ethernet Oam enable Local DTE ---------Config: Mode
:active
Period Time
:10*(100ms)
Link time out
:50*(100ms)
Status: Parse
:forward
Multiplexer
:forward
Stable
:yes
Discovery
:done
Loopback
:off
PDU Revision
:0
Unidirection
:nonsupport
Remote DTE ----------Config: Mode
:active
Link Monitor
:support
Unidirection
:nonsupport
Remote Loopback
:support
Mib Retrieval
:nonsupport
PDU max size
:1518
Status: Parse
:forward
Multiplexer
:forward
5-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Stable
:yes
Mac Address
: 0020.231d.0e0e
PDU Revision
:1
4. Run the show ethernet-oam link-monitor command on R2 to check the number of link errors, which is displayed as follows: R2(config)#show ethernet-oam gei-0/0/0/1 link-monitor Link Monitoring of Port: 66 Link Monitoring enable Error Symbol Period Event: Symbol Window
:1(million symbols)
Error Symbol Threshold
:1
Total Error Symbols
:0
Local Total Error Events
:0
Remote Total Error Events :0 Error Frame Event: Period Window
: 1(s)
Error Frame Threshold
: 1
Total Error Frames
: 0
Local Total Error Events
: 0
Remote Total Error Events : 0 Error Frame Period Event: Frame Window
: 1(ten thousand frames)
Error Frame Threshold
: 1
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)
Total Error Frame Seconds : 0(s) Local Total Error Frame Seconds Events
: 0
Remote Total Error Frame Seconds Events : 0
5.4.2 EFM Remote Loopback Configuration Description R1 and R2 are connected directly. The EFM function is configured for the directly-connected interfaces of R1 and R2, and the remote loopback function is enabled for R1. R2 loops back the packets. For the network structure, see Figure 5-3.
5-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Figure 5-3 EFM Remote Loopback
Configuration Flow 1. Configure the EFM function for the interface of R1 connecting to R2 directly, and enable the EFM function globally. 2. Configure the EFM function for the interface of R2 connecting to R1 directly, and enable the EFM function globally. 3. After the EFM connection is established on R1 and R2, enable remote loopback for R1. 4. Run the show ethernet-oam discovery command on R1 and R2 to check the EFM connection establishment.
Configuration Command Run the following commands on R1: R1#configure terminal R1(config)#efm R1(config-efm)#interface gei-0/0/1/1 R1(config-efm-if)#set ethernet-oam function enable R1(config-efm-if)#set ethernet-oam link-monitor function enable R1(config-efm-if)#exit R1(config-efm)#set ethernet-oam oui R1 R1(config-efm)#set ethernet-oam function enable R1(config-efm)#exit
Run the following commands R2: R2#configure terminal R2(config)#efm R2(config-efm)#interface gei-0/0/0/1 R2(config-efm-if)#set ethernet-oam function enable R2(config-efm-if)#set ethernet-oam link-monitor function enable R2(config-efm-if)#exit R2(config-efm)#set ethernet-oam oui R2 R2(config-efm)#set ethernet-oam function enable R2(config-efm)#exit
After the EFM connection is established, enable remote loopback for R1: R1#configure terminal R1(config)#efm R1(config-efm)#interface gei-0/0/1/1 R1(config-efm-if)#set ethernet-oam rmt-loopback start
5-11 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) R1(config-efm-if)#exit R1(config-efm)#exit
Configuration Verification On the link where the EFM connection is established, R1 sends packets to R2 except OAM Protocol Data Units (OAMPDUs). When R2 receives these packets, it will loop them back to R1 directly.
5-12 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 6
CFM Configuration Table of Contents CFM Overview ...........................................................................................................6-1 Configuring CFM ........................................................................................................6-3 CFM Maintenance ......................................................................................................6-5 CFM Configuration Instances .....................................................................................6-6
6.1 CFM Overview Introduction Ethernet technology becomes the leading technology gradually due to its simplicity and low cost since it was born. In recent years, with the applications of gigabit and 10–gigabit Ethernet technology, Ethernet has been extended towards Metropolitan Area Network (MAN) and Wide Area Network (WAN). Ethernet was mainly applied in LAN in early times. Compared with MAN and WAN, LAN has lower requirements for reliability and stability. As a result, Ethernet was lacking of OAM mechanism, which became a serious obstruction to use Ethernet as operator networks. Therefore, implementing OAM in Ethernet became an inevitable development trend. In this case, a series of standard technologies were generated, such as IEEE 802.3ah (Operations, Administration, and Maintenance - OAM), IEEE 802.1ag (Connectivity Fault Management) and International Telecommunications Union (ITU) - T Y.1731 (OAM functions and mechanisms for Ethernet based networks). IEEE 802.1ag (CFM) provides connectivity detection logically on point-to-point links. It detects the connectivity between two logical points, supporting functions such as loopback, link trace and ITU-T Y1731. CFM can check, isolate, and report connectivity faults in Virtual Local Area Networks (VLANs) effectively. The CFM is the main protocol used for link monitoring, detection, and troubleshooting at the data link layer. It can implement link detection of Ethernet data link layer on most full-duplex point-to-point links and analogical point-to-point links, without depending on specific system interfaces. The CFM mainly has three functions: l
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). 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. 6-1
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
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 Features The 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 6-1. Figure 6-1 Maintenance Domain
A series of ports are defined for the edge devices and the internal device, see Figure 6-1. l l
The gray points on the edge devices are the services ports connecting to devices outside the domain. These points are defined as MEPs. 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. 6-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 6 CFM Configuration
IEEE 802.1ag standard defines the following mechanisms: 1. Several nesting MDs configured through a bridge network or a network of a bridge network. The domains may be managed by different management organizations. 2. An Maintenance Association (MA) identified by an individual MD in a specific bridge and a group of VLANs. 3. The protocol, flow, and formats of CFM protocol packets that are used to detect and isolate connectivity faults. 4. Configuration ability to configure and manage Maintenance Points (MPs) in an MA. An MP is used to generate and receive CFM packets. 5. MPs ordered to execute isolation and result inspection for confirmed faults.
6.2 Configuring CFM To configure CFM on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#cfm
Enters CFM configuration mode.
2
ZXR10(config-cfm)#set cfm enable
Enables the CFM function globally.
3
ZXR10(config-cfm)#create md index name-format
Creates an maintenance domain
[name <md-name>] level
(MD). refers to the level of the maintenance domain. Range: 0-7. The bigger the value, the higher the level.
4
ZXR10(config-cfm)#md index < index >
Enters MD configuration mode.
5
ZXR10(config-cfm-md)#create ma index name-format
Creates a maintenance association
name < ma-name>[vid ]
(MA)
6
ZXR10(config-cfm-md)#ma index
Enters MA configuration mode.
7
ZXR10(config-cfm-ma)#set ccminterval
Configures the CCM interval for an MA. Range: 1-7. The range corresponds to 3.3 ms, 10 ms, 100 ms, 1 s, 10 s, 60 s, and 600 s.
8
ZXR10(config-cfm-ma)#create mep mep-id <mepid> direction {down
Creates an MEP.
| up} interface 9
10
ZXR10(config-cfm-ma)#create rmep mepid <mepid > remote-mac
Creates an Remote Maintenance
<mac-address> lmep
association End Point (RMEP).
ZXR10(config-cfm-ma)#create mip session-id <session-id> interface
Creates an MIP.
6-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Step
Command
Function
11
ZXR10(config-cfm-ma)#set mep <mepid> state {enable|disable}
Enables or disables local management function in an MEP. For an RMEP, it enables or disables CCM detection.
12
ZXR10(config-cfm-ma)#set mep <mepid> ccm-send {enable|disable}
Enables or disables tthe CCM packet sending function in an MEP. It is only effective in the local MEP.
13
ZXR10(config-cfm-ma)#set mep <mepid> alarm-lowest-pri
Configures the lowest fault class that
<priority>
can trigger alarms in an MEP. Range: 1-5, default: 2.
14
ZXR10#cfm loopback md <md-index> ma <ma-index> local-mep
Sends LBMs.
<mepid> type unicast <mac-address>[repeat
Configuration Guide (Reliability) Version: 1.00.60
ZTE CORPORATION No. 55, Hi-tech Road South, ShenZhen, P.R.China Postcode: 518057 Tel: +86-755-26771900 Fax: +86-755-26770801 URL: http://ensupport.zte.com.cn E-mail: [email protected]
LEGAL INFORMATION Copyright © 2013 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History Revision No.
Revision Date
Revision Reason
R2.2
2013-02-28
Fourth edition, adding the "Cooperation Configuration Example Between a Directly Connected Route and the Ping Detect" topic.
R2.0
2012-07-20
Third edition
R1.1
2012-03-30
Second edition
R1.0
2011-12-10
First edition
Serial Number: SJ-20130205142913-019 Publishing Date: 2013-02-28 (R2.2)
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Contents About This Manual ......................................................................................... I Chapter 1 Reliability Overview .................................................................. 1-1 Chapter 2 Service Availability Manager Configuration ........................... 2-1 2.1 SAMGR Overview .............................................................................................. 2-1 2.2 SAMGR Configuration ........................................................................................ 2-4 2.3 Maintaining SAMGR ........................................................................................... 2-6 2.4 SAMGR Configuration Instances ......................................................................... 2-9 2.4.1 Linkage between EFM and VRRP ............................................................. 2-9 2.4.2 Linkage between CFM and VRRP ........................................................... 2-12
Chapter 3 VRRP Configuration ................................................................. 3-1 3.1 VRRP Overview ................................................................................................. 3-1 3.2 VRRP Network Application ................................................................................. 3-4 3.3 Configuring VRRP .............................................................................................. 3-8 3.4 Maintaining VRRP .............................................................................................3-11 3.5 VRRP Configuration Instances .......................................................................... 3-13 3.5.1 Basic VRRP Configuration Example ........................................................ 3-13 3.5.2 Symmetrical VRRP Configuration Example .............................................. 3-15 3.5.3 VRRP Heartbeat Configuration Example.................................................. 3-18 3.5.4 VRRP BFD Configuration Example.......................................................... 3-20
Chapter 4 Ping Detect Configuration........................................................ 4-1 4.1 Ping Detect Overview ......................................................................................... 4-1 4.2 Configuring Ping Detect ...................................................................................... 4-2 4.3 Maintaining Ping Detect ...................................................................................... 4-3 4.4 Ping Detect Configuration Instances .................................................................... 4-4 4.4.1 Basic Ping Detect Configuration Examples................................................. 4-4 4.4.2 Cooperation Configuration Example Between a Directly Connected Route and the Ping Detect....................................................................... 4-6
Chapter 5 EFM Configuration.................................................................... 5-1 5.1 EFM Overview ................................................................................................... 5-1 5.2 Configuring EFM ................................................................................................ 5-2 5.3 Maintaining EFM ................................................................................................ 5-4 5.4 EFM Configuration Instances .............................................................................. 5-6 5.4.1 EFM Connection Establishment ................................................................ 5-6 I SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
5.4.2 EFM Remote Loopback .......................................................................... 5-10
Chapter 6 CFM Configuration.................................................................... 6-1 6.1 CFM Overview ................................................................................................... 6-1 6.2 Configuring CFM ................................................................................................ 6-3 6.3 CFM Maintenance .............................................................................................. 6-5 6.4 CFM Configuration Instances .............................................................................. 6-6 6.4.1 CFM Fast Connectivity Detection .............................................................. 6-6 6.4.2 Cross-L2 VPN Connectivity Detection...................................................... 6-10
Chapter 7 BFD Configuration .................................................................... 7-1 7.1 BFD Overview.................................................................................................... 7-1 7.2 BFD Configuration.............................................................................................. 7-2 7.3 BFD Maintenance .............................................................................................. 7-6 7.4 BFD Configuration Instances............................................................................... 7-7 7.4.1 Configuring IS-IS BFD .............................................................................. 7-7 7.4.2 Configuring OSPF BFD ............................................................................ 7-9 7.4.3 Configuring BGP Single-Hop BFD ........................................................... 7-10 7.4.4 Configuring BGP Multi-Hop BFD ............................................................. 7-12 7.4.5 Configuring Static Route BFD ................................................................. 7-14 7.4.6 Configuring LDP BFD ............................................................................. 7-16 7.4.7 Configuring Static Single-Hop BFD.......................................................... 7-18 7.4.8 Configuring Static Multi-Hop BFD ............................................................ 7-20 7.4.9 Configuring BFD on RSVP Interface ........................................................ 7-23 7.4.10 Configuring RSVP LSP BFD ................................................................. 7-26
Chapter 8 FRR Configuration .................................................................... 8-1 8.1 IP FRR Configuration ......................................................................................... 8-1 8.1.1 IP FRR Overview ..................................................................................... 8-1 8.1.2 Nested FRR Overview .............................................................................. 8-3 8.1.3 Configuring IP FRR .................................................................................. 8-4 8.2 Static Route FRR Configuration .......................................................................... 8-4 8.3 L2 VPN FRR Configuration ................................................................................. 8-5 8.3.1 L2 VPN FRR Overview ............................................................................. 8-5 8.3.2 Configuring L2 VPN FRR .......................................................................... 8-6 8.4 L3VPN FRR Configuation ................................................................................... 8-6 8.4.1 Brief Introduction to L3VPN FRR ............................................................... 8-6 8.4.2 Configuring L3 VPN FRR .......................................................................... 8-7 8.5 TE FRR Configuration ........................................................................................ 8-7 8.5.1 TE FRR Overview .................................................................................... 8-7 II SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
8.5.2 TE FRR Work Flow .................................................................................. 8-9 8.5.3 Configuring TE FRR ............................................................................... 8-14
Chapter 9 Graceful Restart Configuration ............................................... 9-1 9.1 IP Graceful Restart Configuration ........................................................................ 9-1 9.2 LDP Graceful Restart Configuration..................................................................... 9-3
Chapter 10 Master/Slave Main Control Handover ................................. 10-1 10.1 Master/Slave Plane Handover Overview .......................................................... 10-1 10.2 Configuring Master/Slave Main-control Handover ............................................. 10-2 10.3 Maintaining Master/Slave Main-control Handover ............................................. 10-2 10.4 Master/Slave Main-control Handover Configuration Example............................. 10-6
Chapter 11 Load Sharing Configuration................................................. 11-1 11.1 Load Sharing Overview ....................................................................................11-1 11.2 Configuring the Load Sharing ...........................................................................11-1 11.3 Configuring Multicast Load Sharing...................................................................11-2 11.4 Configuring MPLS VPN Load Sharing ...............................................................11-2
Figures............................................................................................................. I Glossary ........................................................................................................ III
III SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
IV SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
About This Manual Purpose This manual describes the principle, configuration commands, maintenance commands and configuration examples about the reliability function of the ZXR10 M6000.
Intended Audience This manual is intended for: l l l
Network planning engineers Commissioning engineers On-duty personnel
What Is in This Manual This manual contains the following chapters: Chapter
Summary
1, Reliability Overview
Describes the meaning and requirements of the reliability, and the relationship of various functions related to the reliability.
2, Service Availability
Describes the principle, configuration commands, maintenance
Manager Configuration
commands, and configuration examples of the SAMGR.
3, VRRP Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the VRRP.
4, Ping Detect Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the ping detect.
5, EFM Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the EFM.
6, CFM Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the CFM.
7, BFD Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the BFD.
8, FRR Configuration
Describes the principle, configuration commands, maintenance commands, and configuration examples of the FRR.
9, Graceful Restart
Describes the principle, configuration commands, maintenance
Configuration
commands, and configuration examples of the GR.
I SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter
Summary
10, Master/Slave Main Control
Describes the principle, configuration commands, maintenance
Handover
commands, and configuration examples of the master/slave main-control handover.
11, Load Sharing
Describes the principle, configuration commands, maintenance
Configuration
commands, and configuration examples of the load sharing.
Conventions This manual uses the following typographical conventions: Typeface
Meaning
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.
|
Separates individual parameter in series of parameters. Danger: indicates an imminently hazardous situation. Failure to comply can result in death or serious injury, equipment damage, or site breakdown. Warning: indicates a potentially hazardous situation. Failure to comply can result in serious injury, equipment damage, or interruption of major services. Caution: indicates a potentially hazardous situation. Failure to comply can result in moderate injury, equipment damage, or interruption of minor services. Note: provides additional information about a certain topic.
II SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 1
Reliability Overview Reliability Introduction With the rapid development of IP technology, various value-added services are widely used on the Internet. Some important carrier-class services, such as Next Generation Network (NGN), the 3rd Generation Mobile Communications (3G), Internet Protocol Television (IPTV) stream media, special line, and Virtual Private Network (VPN), have high requirement for reliability on the Internet Protocol (IP) network. The reliability requirements of the carrier-class services on the IP network include: l l l
Device reliability Link reliability Network reliability
On the bearer network, the availability of a network device is required to reach 99.999%. In this case, the duration of service shutdown during continuous operation in a whole year must be less than 5 minutes. High reliability is a basic requirement of a carrier-class device, and it is a basic requirement for telecom operators to construct networks. As a basic network for bearer services, the reliability of the bearer network becomes an important part. On a router or a Packet Transport Network (PTN), reliability technology includes device hardware redundancy and network reliability technology. In this manual, the network reliability technology is described. Network reliability technology includes network fault detection technology and protection switching technology.
Network Fault Detection Technology The network fault detection technology includes the following detection mechanisms in accordance with network layers: l l
l l
Transport layer and physical layer: Automatic Protection Switching (APS). Link layer: Bidirectional Forwarding Detection (BFD), Multiprotocol Label Switching (MPLS) Operations, Administration and Maintenance (OAM) and Ethernet Operations, Administration and Maintenance (Eth-OAM). Network layer: HELLO mechanism of various protocols, LLO mechanism, Virtual Router Redundancy Protocol (VRRP), and BFD. Application layer: heartbeats of various application protocols.
Protection Switching Technology The protection switching technologies includes the following types: 1-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
l l
End-to-end protection: APS 1:1 linear protection, APS 1+1 linear protection and hot standby. Local protection: FRR, including IP FRR, LDP FRR, TE FRR, and PW FRR.
1-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2
Service Availability Manager Configuration Table of Contents SAMGR Overview ......................................................................................................2-1 SAMGR Configuration ................................................................................................2-4 Maintaining SAMGR...................................................................................................2-6 SAMGR Configuration Instances ................................................................................2-9
2.1 SAMGR Overview Introduction Service Availability Manager (SAMGR) is used to manage the relationship between services and the availability. The SAMGR has the following functions: l l l l
Track object management Track group management Operation, Administration and Maintenance (OAM) binding management OAM mapping management
The SAMGR implements the linkage between various detection technologies and services. It ensures the quick switch of services when the network link is faulty. In practical applications, a router provides multiple detection technologies. At the same time, there are also many protection switching applications that need to monitor detection results on a real-time basis to meet the requirements for availability in different network structures. Therefore, the SAMGR is used 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: 1. The SAMGR abstracts a detection example to a track object. It associates the track object with the detection example by configuring a trackname for the track object. The trackname is called directly in the service where the detection result needs to be monitored. 2. When detecting that the link state changes, the detection technology advertises the state change to the SAMGR directly.
2-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
3. The SAMGR informs the application service associated with the track object. The application service performs state switching in accordance with the state change to protect the link. 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.
Linkage Among VRRP, SAMGR, EOAM and BFD Figure 2-1 displays the linkage among VRRP, SAMGR, EOAM, and BFD. Figure 2-1 Linkage Among VRRP, SAMGR, EOAM and BFD
The network structure descriptions are as follows: 1. The EOAM is configured between the routers and the switches to keep links alive. BFD is configured between router A and router B. 2. Router A and router B operate in active/standby mode. The routers monitor the states of EOAM and BFD separately. 3. The VRRP runs on the directly connected interfaces between router A/router B and the switches to form a VRRP group. 4. The SAMGR monitors the results of EOAM and BFD in VRRP service in real time, thus ensuring the reliability for VRRP. When EOAM detects a fault, it reports the fault to the SAMGR. The SAMGR informs the service to switch the state directly in accordance with the relation between the track object and the service. When a fault of the pee-type BFD occurs on the router, the SAMGR advertises the state to the service, and then the service performs switching in accordance with its policy on the basis of the EOAM state and the BFD state.
Linkage of Symmetrical Dual-Connection Between CE and PE A CE connects to two PEs symmetrically to perform linkage of states between detections, see Figure 2-2.
2-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration
Figure 2-2 Linkage of Symmetrical Dual-Connection Between CE and PE
The network structure descriptions are as follows: 1. A PW is established between PE-1 and PE-3, and a PW is established between PE-2 and PE-4. 2. The CE1 connects to PE-1 and PE-2. 3. The CE2 connects to PE-3 and PE-4. 4. The OAM detection (Ethernet in the First Mile (EFM)/Connectivity Fault Management (CFM)/link keepalive) is enabled between CEs and PEs. 5. The BFD is enabled between PEs to detect PWs. MPLS OAM is enabled between PEs to detect TE Label Switched Paths (LSPs). 6. The OAM mapping/binding is associated between the Access Circuit (AC)-side link detection and PW link detection (or between LDPs) to transmit a fault. The principle of fault detection and switching is as follows: If a fault occurs on the AC between CE1 and PE–1, 1. The AC EOAM of PE–1 detects the AC fault and informs the SAMGR. 2. The SAMGR of PE–1 maps the detection track object of PW corresponding to the AC in accordance with the OAM mapping/binding configuration. 3. If BFP or MPLS-OAM is configured between PEs, PE-1 transmits the OAM fault to PE-2 transparently. 4. When PE–3 receives the BFD/MPLS OAM/LDP fault, if there is a standby PW on the remote PE, PE–3 switches the traffic. Otherwise, PE–3 performs OAM mapping/binding to map the corresponding AC and advertises the fault to CE–2. If a fault occurs on a PW, 1. BFD/MPLS OAM on a PE detects the PW/LSP fault. 2. The PE performs OAM mapping/binding to map the corresponding local AC. 3. If there is a standby PW on the PE, the PE switches traffic. Otherwise, the PE performs OAM mapping/binding to map the corresponding AC and advertises the fault to the local CE.
2-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
2.2 SAMGR Configuration Configuring a Track Object To configure a track object on the ZXR10 M6000, perform the following commands: Step
Command
Function
1
ZXR10(config)#samgr
Enters SAMGR configuration mode.
2
ZXR10(config-samgr)#track
Configures a track object with detection type
"efm".
ZXR10(config-samgr)#track
Configures a track object with detection type
<1-65535> ma <1-65535> local-mep <1-8191>
"cfm".
3
remote-mep <1-8191> 4
ZXR10(config-samgr)#track
Configures a track object with detection type
group <1-10>
"ping-detect". The range of the Ping-detection group is 1-10.
5
6
7
ZXR10(config-samgr)#track
Configures a track object with detection type
<1-150>
"sqa". The range of the SQA example is : 1-150.
ZXR10(config-samgr)#track
Configures a track object with detection type
tunnel-id <1-4000> ingress-id
"mpls-oam". The range of the mpls-oam tunnel
egress-id <egress-value>
is 1-4000.
ZXR10(config-samgr)#track
Configures a track object with detection type
"link-bfd".
local-ipv6-address >< remote-ipv6-address >} interface
ZXR10(config-samgr)#track
Configures a track object with detection type
"peer-bfd".
local-ipv6-address>
ZXR10(config-samgr)#track
Configures a track object with detection type
fec-address < fec-address > mask-length <1-32>
"ldp-bfd". interval <10-990> indicates the
interval <10-990> min-rx <10-990> multiplier <3-50>
minimum interval for sending BFD packets, and min-rx <10-990> indicates the minimum interval for receiving BFD packets.
10
ZXR10(config-samgr)#track
Configures a track object with detection type
tunnel-id <1-4000> interval <10-990> min-rx <10-990>
"rsvp-bfd".
multiplier <3-50>
2-4 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration
Step
Command
Function
11
ZXR10(config-samgr)#track
Configures a track object with detection type
<1-4294967295> peerid
"pw-bfd".
| atm-cell | atm-vcc | atm-vpc | cem | ceop | cesopsn-basic | cesopsn-cas | hdlc | e1 | e3 | ehter | ether-vlan | fr-dlci-martini | fr-dlci | fr-port | ip | ppp | t1 | t3}[interval <10-990> min_rx <10-990> multiplier <3-50>] 12
ZXR10(config-samgr)#track
Configures a track object with detection type
<1-4294967295> peerid
"pw".
l5|atm-cell|atm-vcc|atm-vpc|cem|ceop| cesopsn-basic | cesopsn-cas | dhlc | e1 |e3| ether | ether-vlan | fr-dhci-martini | fr-dlci | fr-port | ip | ppp | t1 |t3} 13
14
ZXR10(config-samgr)#track
Configures a track object with detection type
"vrrp".
ZXR10(config-samgr)#track
Configures a track object with detection type
<session-name>
“l2-bfd”. <session-name> indicates the l2-bfd name (Length: 1-32 characters)
Configuring a Track Group To configure a track group on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#samgr
Enters SAMGR configuration mode.
2
ZXR10(config-samgr)#track-group
Configures a track group and enters track group configuration
mode.
ZXR10(config-samgr-track-group)#tr
Adds a track object to the track group.
3
ack
ZXR10(config-samgr-track-group)#inac
tive-number <1-10>
Configures the policy for a track group. inactive-number indicates the number of invalid track objects resulting in invalidity of the track group.
Configuring Binding Relation To configure the binding relationship on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#samgr
Enters SAMGR configuration mode.
ZXR10(config-samgr)#sa-bind track
Configures the binding relationship
track-group}
between track objects or between
2
track groups.
Parameter descriptions in Step 2 are as follows: 2-5 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Parameter
Description
track
Name of the passive track object, that is, the name of the track object that receives state transmission.
{track | track-group}
Name of an active track object or track group, that is, the name of the track object or track group that starts state transmission.
2.3 Maintaining SAMGR To maintain SAMGR on the ZXR10 M6000 , run the following commands: Command
Function
ZXR10#show samgr brief
Displays the brief information related to a track object.
ZXR10#show samgr track [
Displays the detailed information of a track object, for example, the state change information.
ZXR10#show samgr track-group [
Displays the detailed information of a track group, for example, the state change information.
The following is sample output from the show samgr brief command: ZXR10#show samgr brief The total of track at this Router is 7 ====================================================== Track-name
Detect-type
App-num
State
vrrp2
vrrp
0
up
oam1
mpls-oam
1
up
ping1
ping-detect
0
L-down
vrrp1
vrrp
0
up
efm1
efm
1
T-down
ping2
ping-detect
0
up
vrrp2
vrrp
0
up
Parameter descriptions are as follows: Command Output
Description
Track-name
Name of a configured track object.
Detect-type
Detection type of a track object.
App-num
Number of times that the track object is used.
State
State of the track object.
The following is sample output from the show samgr track command: ZXR10#show samgr track Track name is xx
2-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration Detect type
: peer-bfd
Track parameter Local IP: 1.1.1.1 App number
Remote IP: 1.1.1.3
Vrf name: zte
: 0
Active track : none Passive track: none Oam-mapping
: no
Track state
: unknow
State change : 0 state changes, last state change 00-00-00 00:00:00
Track name is bfd1 Detect type
: link-bfd
Track parameter Local IP: 1.1.1.1 App number
Remote IP: 1.1.1.2
Interface: fei-0/1/0/1
: 0
Active track : none Passive track: none Oam-mapping
: no
Track state
: unknow
State change : 0 state changes, last state change 00-00-00 00:00:00
Track name is tcp Detect type
: sqa
Track parameter Instance number: 4 App number
: 0
Active track : none Passive track: none Oam-mapping
: no
Track state
: local down
State change : 1 state changes, last state change 2010-07-15 17:25:43
Track name is oam1 Detect type
: mpls-oam
Track parameter Tunnel Id: 1 App number
Ingress Id: 1.2.3.4
: 1
Active track : none Passive track: none Oam-mapping
: no
Track state
: up
State change : 1 state changes, last state change 2010-07-15 17:26:14
ZXR10(config)#show samgr track sqa verbose Track name is sqa
2-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) State change record:
1
old state
new state
change time
unknown
local down
2010-07-19 02:57:28
2
local down
up
2010-07-19 03:05:16
3
up
local down
2010-07-19 03:06:24
4
local down
up
2010-07-19 03:08:00
5
up
local down
2010-07-19 03:08:13
Parameter descriptions are as follows: Command Output
Description
Track name
Name of a track object.
Detect type
Detection type of track object.
Track parameter
Parameters of a track object.
App number
Number of times that the track object is used.
Active track
Whether to act as a passive track to receive state information from the active track.
Passive track
Whether to act as an active track to send the state information to the passive track.
Oam-mapping
Whether the track has the OAM mapping ID.
Track state
The state of the track object.
State change
The state change information of the track object.
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.
change time
The state change time of the track object.
The following is sample output from the show samgr track-group command: ZXR10#show samgr track-group Track-group name: aaa Set inactive number: all App number: 0 Track-group state: up Track-group member: 0 ------------------------------Track-group name: group1 Set inactive number: 1 App number: 0 Track-group state: local down Track-group member: 3 Track name: ping3
State: up
Track name: ping2
State: up
Track name: ping1
State: local down
ZXR10(config)#show samgr track-group 1 verbose
2-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration Track name is 1 State change record: old state
new state
change time
1
up
local down
2010-07-19 03:14:43
2
local down
up
2010-07-19 03:14:50
3
up
local down
2010-07-19 03:14:56
4
local down
up
2010-07-19 03:15:01
Parameter descriptions are as follows: Command Output
Description
Track-group name
Name of a track group.
Set inactive number
Policy for a track group.
App number
Number of times that the track object is used.
Track-group member
Members in a track group .
Track name
Name of track objects that are bound to the track group.
State
State of the track object.
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.
change time
The state change time of the track group.
2.4 SAMGR Configuration Instances 2.4.1 Linkage between EFM and VRRP Configuration Description The VRRP protocol is used between R2 and R3. The VRRP virtual address is the interface address 10.0.0.1. The R2 operates as a master router, see Figure 2-3. Figure 2-3 Linkage between EFM and VRRP
2-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Configuration Flow 1. Configure the EFM connection for the directly-connected interfaces between S1 and R2. 2. Configure an EFM track object for the directly-connected interface of R2 in SAMGR configuration mode. 3. Configure the same VRRP group number and virtual address for R2 and R3. To set R2 as a master router, bind the VRRP of R2 to the EFM track object. 4. When the EFM function is disabled on S1, the VRRP group on R2 is changed to the Init status, and the VRRP group on R3 is changed to the Master status. When the EFM function is enabled, the VRRP group on R2 is changed to the Master status, and the VRRP group of R3 is changed to the Backup status.
Configuration Command Run the following commands on S1: S1(config)#set ethernet-oam enable S1(config)#interface gei_4/1 S1(config-gei_4/1)#set ethernet-oam
enable
Run the following commands on R2: R2(config)#interface gei-0/2/0/1 R2(config-if)#ip address 10.0.0.1 255.255.0.0 R2(config-if)#exit R2(config)#interface gei-0/3/0/2 R2(config-if)#ip address 192.168.0.1 255.255.0.0 R2(config-if)#exit
R2(config)#efm R2(config-efm)#set ethernet-oam function enable R2(config-efm)#interface gei-0/2/0/1 R2(config-efm-if)#set ethernet-oam function enable R2(config-efm-if)#exit R2(config-efm)#exit
R2(config)#samgr R2(config-samgr)#track efm efm interface gei-0/2/0/1 R2(config-samgr)#exit
R2(config)#vrrp R2(config-vrrp)#interface gei-0/2/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 1 out-interface gei-0/3/0/2 R2(config-vrrp-if)#vrrp 1 track object efm link-type R2(config-vrrp-if)#exit
Run the following commands on R3: 2-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration R3(config)#interface gei-0/5/0/1 R3(config-if)#ip address 10.0.0.2 255.255.0.0 R3(config-if)#exit R3(config)#interface gei-0/6/0/2 R3(config-if)#ip address 192.168.0.2 255.255.0.0 R3(config-if)#exit
R3(config)#vrrp R3(config-vrrp)#interface gei-0/5/0/1 R3(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R3(config-vrrp-if)#vrrp 1 out-interface gei-0/6/0/2 R3(config-vrrp-if)#end
Configuration Verification Check the VRRP configuration results on R2 and R3. The results show that R2 is a master router and R3 is a backup router. The output of the show samgr command on R2 shows that the EFM track object is in up state. R2#show vrrp ipv4 brief Interface
vrID
Pri
Time
A P L State
Master addr
VRouter addr
gei-0/2/0/1
1
255
1000
A P
10.0.0.1
10.0.0.1
Master
R2#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
efm
efm
App-num
State
1
up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
A P L State
100 1000
P
Backup
Master addr
VRouter addr
10.0.0.1
10.0.0.1
When the EFM function on S1 is disabled , the status of the VRRP group on R2 is changed from Master to Init, and that of R3 is changed to Master. The output of the show samgr command on R2 shows that the EFM track object is in local down status. S1(config)#set ethernet-oam enable S1(config-efm)#set ethernet-oam
function disable
S1(config-efm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
gei-0/2/0/1
1
A P
255 1000
Init
Master addr 0.0.0.0
VRouter addr 10.0.0.1
R2#show samgr brief The total of track at this Router is 1.
2-11 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) ============================================================================ Track-name
Detect-type
App-num
State
efm
efm
1
L-down
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
A P L State
100 1000
P
Master addr
Master 10.0.0.2
VRouter addr 10.0.0.1
When the EFM function on S1 is enabled, the status of the VRRP group on R2 is changed to Master, and that of R3 is changed to Backup. The EFM track object on R2 is in up status. S1(config)#set ethernet-oam enable S1(config-efm)#set ethernet-oam
function enable
S1(config-efm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/2/0/1
1
100 1000
A P L State P
Master
Master addr
VRouter addr
10.0.0.1
10.0.0.1
R2#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
App-num
State
efm
efm
1
up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Backup
Master addr
VRouter addr
10.0.0.1
10.0.0.1
2.4.2 Linkage between CFM and VRRP Configuration Description The VRRP protocol is used between R2 and R3. The VRRP virtual address is the interface address 10.0.0.1 of R2 that operates as a master router. For the network structure, see Figure 2-4.
2-12 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration
Figure 2-4 Link between CFM and VRRP
Configuration Flow 1. Configure the CFM continuous detection for the directly-connected interfaces between S1 and R2. 2. Configure a CFM track object for the directly-connected interface of R2 in SAMGR configuration mode. 3. Configure the same VRRP group number and virtual address for R2 and R3. To set R2 as a master router, bind VRRP of R2 to the track object with the detection type "CFM". 4. When the CFM function on S1 is disabled, the status of the VRRP group onR2 is changed to the Init status, and that of R3 is changed to the Master status. When the CFM function on S1 is enabled, the status of the VRRP group on R2 is changed to Master, and that of R3 is changed to Backup.
Configuration Command Run the following commands on S1: S1(config)#cfm enable S1(config)#cfm ccm-format 1 S1(config)#cfm create md session 1 name md2 level 7 S1(config-md)#ma create session 1 name a4 S1(config-md-ma)#create mep session 1 8 direction down S1(config-md-ma)#create rmep session 1 16 remote-mac 00d0.d011.3377 S1(config-md-ma)#assign mep 8 to interface gei_4/1 S1(config-md-ma)#mep 8 state enable S1(config-md-ma)#mep 8 ccm-send enable S1(config-md-ma)#mep 16 state enable
Run the following commands on R2: R2(config)#interface gei-0/2/0/1 R2(config-if)#ip address 10.0.0.1 255.255.0.0 R2(config-if)#exit R2(config)#interface gei-0/3/0/2 R2(config-if)#ip address 192.168.0.1 255.255.0.0 R2(config-if)#exit
2-13 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
R2(config)#cfm R2(config-cfm)#set cfm enable R2(config-cfm)#create md index 2 name-format 2 name md2 level 7 R2(config-cfm)#md index 2 R2(config-cfm-md)#create ma index 4 name-format 2 name a4 R2(config-cfm-md)#ma index 4 R2(config-cfm-ma)#create mep mepid 16 direction down interface gei-0/2/0/1 R2(config-cfm-ma)#create rmep mepid 8 remote-mac 00a1.1122.0011 lmep 16 R2(config-cfm-ma)#set mep 16 state enable R2(config-cfm-ma)#set mep 16 ccm-send enable R2(config-cfm-ma)#set mep 8 state enable R2(config-cfm-ma)#exit R2(config-cfm-md)#exit R2(config-cfm)#exit
R2(config)#samgr R2(config-samgr)#track cfm cfm md 2 ma 4 local-mep 16 remote-mep 8 R2(config-samgr)#exit
R2(config)#vrrp R2(config-vrrp)#interface gei-0/2/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 1 out-interface gei-0/3/0/2 R2(config-vrrp-if)#vrrp 1 track object cfm link-type R2(config-vrrp-if)#exit
Run the following commands on R3: R3(config)#interface gei-0/5/0/1 R3(config-if)#ip address 10.0.0.2 255.255.0.0 R3(config-if)#exit R3(config)#interface gei-0/6/0/2 R3(config-if)#ip address 192.168.0.2 255.255.0.0 R3(config-if)#exit
R3(config)#vrrp R3(config-vrrp)#interface gei-0/5/0/1 R3(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R3(config-vrrp-if)#vrrp 1 out-interface gei-0/6/0/2 R3(config-vrrp-if)#end
Configuration Verification Check the VRRP configuration results on R2 and R3. The results show that R2 is a Master router and R3 is a Backup router. The output of the show samgr command shows that the CFM track object is in up status. 2-14 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 2 Service Availability Manager Configuration R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
gei-0/2/0/1
1
A P
255 1000
Master addr
VRouter addr
Master 10.0.0.1
10.0.0.1
R2(config)#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
cfm
cfm
App-num
State
1
up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Master addr
Backup 10.0.0.1
VRouter addr 10.0.0.1
When the CFM function on S1 is disabled, the status of the VRRP group on R2 is changed from Master to Init, and that of R3 is changed to Master. The CFM track object of R2 is in local down status. S1(config)#cfm disable S1(config-cfm)#set cfm disable S1(config-cfm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
Master addr
VRouter addr
gei-0/2/0/1
1
A P
0.0.0.0
10.0.0.1
255 1000
Init
R2#show samgr brief The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
cfm
cfm
App-num 1
State L-down
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Master
Master addr
VRouter addr
10.0.0.2
10.0.0.1
When the CFM function on S1 is enabled, the status of the VRRP group on R2 is changed to Master, and that of R3 is changed to Backup. The CFM track object of R2 is in up status. S1(config)#cfm enable S1(config-cfm)#set cfm enable S1(config-cfm)#exit
R2#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
Master addr
VRouter addr
gei-0/2/0/1
1
A P
10.0.0.1
10.0.0.1
255 1000
Master
R2#show samgr brief
2-15 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) The total of track at this Router is 1. ============================================================================ Track-name
Detect-type
cfm
cfm
App-num 1
State up
R3#show vrrp ipv4 brief Interface
vrID Pri Time
gei-0/5/0/1
1
100 1000
A P L State P
Backup
Master addr
VRouter addr
10.0.0.2
10.0.0.1
2-16 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3
VRRP Configuration Table of Contents VRRP Overview .........................................................................................................3-1 VRRP Network Application .........................................................................................3-4 Configuring VRRP ......................................................................................................3-8 Maintaining VRRP ....................................................................................................3-11 VRRP Configuration Instances .................................................................................3-13
3.1 VRRP Overview Introduction With the development of Internet, the requirements for network reliability is ever increasing. For Local Area Network (LAN) users, it is important to keep communications with external networks. The same default route is set for all hosts in the internal network to the egress network gateway (router A in Figure 3-1). With the default route, hosts in the internal network communicate with external network. If a fault occurs on the egress network gateway, the communication between the hosts and the external network will be interrupted. Figure 3-1 Default Network Gateway in LAN
A common method to improve system reliability is to configure multiple egress network gateways. Because hosts in LANs normally do not support dynamic routing protocols, it is a problem to select a route among multiple egress network gateways.
3-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
The Virtual Router Redundancy Protocol (VRRP) is a fault-tolerant protocol. The VRRP can implement routing among multiple egress network gateways by isolating physical devices from logical devices. After that, the problem is solved. In LANs with multicasting or broadcasting ability (such as Ethernet), the VRRP provides a logical network gateway to ensure that transmission links are used fully. This not only avoids service interruption due to faults on a network gateway device, but also avoids modification of routing protocol configuration.
VRRP Election Flow The VRRP forms a virtual router with the router A and router B in a LAN, see Figure 3-2. Figure 3-2 VRRP Election Flow
The virtual router has its own IP address 10.100.10.1 (this IP address can be the same with an interface address on a router). Route A and router B also have their own IP addresses (IP address of router A is 10.100.10.2 and IP address of router B is 10.100.10.3). Hosts in the LAN only knows the IP address 10.100.10.1 of the virtual router. Hosts do not know the IP addresses of router A and Router B. Router A and router B set the IP address 10.100.10.1 of the virtual router as their default routes. Therefore, hosts in the LAN communicate with other networks through this virtual router. The virtual router needs to perform the following operations: 1. The virtual router selects a master router in accordance with the priority. The router with the highest priority becomes the master router and its state is Master. If the priorities are the same, the master IP addresses on interfaces are compared. The router with the greater master IP address on an interface becomes the master router. The master router provides routing service. 2. The other router operates as a backup router. It detects the state of the master router at any time. 3-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
l
l l
When the master router works properly, it sends a VRRP multicasting message at a certain interval to inform the backup router in the group that the master router works properly. If the backup router in the group does not receive messages from the master router for a long time, the backup router changes its state to Master. When there are several backup routers in the group, there might be several master routers at this time. In this situation, each master router 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 router changes its state to Backup. Otherwise, the master keeps its state.
In this way, the router with the highest priority becomes the new master router. The VRRP backup function is completed.
VRRP Router States The routers that form the virtual router have three states, Initialize, Master, and Backup. The states descriptions are as follows: l
Initialize A router enters this state after the system is started. When an interface receives a startup message, the router becomes Backup state (when the priority is not 255) or Master state (when the priority is 255). In Initialize state, the router does not handle VRRP messages.
l
Master When a router is in Master state, it performs the following operations: 1. It sends VRRP multicasting messages periodically. 2. It sends free Address Resolution Protocol (ARP) messages to make virtual Medium Access Control (MAC) address that corresponds to the virtual IP address known by all hosts in the network. 3. It replies to the ARP request for the virtual IP address with the virtual MAC address instead of the real MAC address on the interface. 4. It forwards IP messages of which the destination MAC address is the virtual MAC address. In Master state, when the router receives a VRRP message in which the priority is higher than the priority of the router, the router enters the Backup state. When it receives a Shutdown event, the router enters the Initialize state.
l
Backup When a router is in Backup state, it performs the following operations: 1. It receives VRRP multicasting messages from the master router to know the state of the master router. 2. It does reply to the ARP requests for the virtual IP address. 3. It drops IP messages of which the destination IP address is the virtual IP address. For the state conversion, see Figure 3-3. 3-3
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Figure 3-3 State Conversion in VRRP
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 router.
3.2 VRRP Network Application VRRP Monitoring Interface State The VRRP provides a function to monitor interface states. That is, the VRRP not only provides the backup function if a fault occurs on an interface in the backup group, but also for a fault occurring on another interface on routers. When the monitored interface state is down, the priority of the router decreases by a certain value automatically, which makes the priorities of other routers in the backup group be higher than the priority of this router. This urges master/slave router changeover. The router with the highest priority becomes the master router and the changeover is completed. For an application of VRRP monitoring interface, see Figure 3-4. Figure 3-4 Application of VRRP Monitoring Interface
3-4 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
In Figure 3-4, the VRRP Group 1 monitors the interface marked with a red point on router A. When the interface works properly, router A acts as the master router. When the interface is down, the priority of router A is decreased. As a result, the priority of router A is lower than that of router B. In this way, master/backup changeover is completed.
VRRP Load Sharing Load sharing means that several routers bear services at the same time to avoid occurrence of idle routers. Therefore, it is necessary to create two or more backup groups to implement load sharing, see Figure 3-5. Figure 3-5 Application of VRRP Load Sharing
The load sharing function has the following features: l l l
Each backup group contains a Master device and several Backup devices. The Master devices in the backup groups can be different. A router can be added into different backup groups, and the router has different priorities in these backup groups. 1. Application scene descriptions of VRRP load sharing l In Figure 3-5, the VRRP Group 1 (with virtual IP address 10.0.0.1) and the VRRP Group 2 (with virtual IP address 10.0.0.100) are configured on the same interfaces on router A and router B. l The real IP address of physical router A is 10.0.0.2, and the real IP address of physical router B is 10.0.0.3. l The default gateway of a part of hosts in the LAN is 10.0.0.1, and the default gateway of the other part of hosts in the LAN is 10.0.0.100. 2. Working mechanism Router A and router B have the following agreements during the VRRP negotiation through priority configuration of the backup groups on router A and router B: l l l
Router A operates as the master router in Group 1 and operates as a backup router in Group 2. Router B operates as the master router in Group 2 and operates as a backup router in Group 1. A part of the hosts uses the backup group 1 as the gateway and the traffic is sent through router A. The other part of the hosts uses the backup group 2 as the gateway and the traffic is sent through router B. 3-5
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
In this way, the data flows are shared and backed up.
VRRP Heartbeat Configuration In some applications, there is no layer 2 forwarding device under the routers and the protocol packet cannot be sent through the interface on which a VRRP group is configured. In this case, the VRRP heartbeat must be configured. If a heartbeat is configured in the VRRP group, the VRRP protocol packet is sent through the heartbeat interface. If a heartbeat is not configured in the VRRP group, the out-interface is the interface on which a VRRP is configured.
VRRP Track Configuration There are three applications of VRRP link detection. l
Application one The VRRP protocol is used between router A and router B. These two routers are used for master/backup selection. The 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. Figure 3-6 EOAM for VRRP Application One
For the state transfer of EOAM for VRRP, see Figure 3-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, the VRRP transfers to the initialize state directly. When all VRRP interfaces are in up state and VRRP is in initialize state, the 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.
3-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Figure 3-7 VRRP and EOAM State Transfer
l
Application two The VRRP protocol is used between router A and router B, and these two routers are used for master/backup selection, see Figure 3-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. Figure 3-8 EOAM for VRRP Application Two
For the state transfer of EOAM (or link BFD) + peer BFD for VRRP, see Figure 3-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, the VRRP is in initialize state, the 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 the VRRP is in backup state, and the VRRP receives the link fault notified by peer BFD, the VRRP will transfer to the master state.
3-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Figure 3-9 VRRP and EOAM + Peer BFD State Transfer
l
Application three The VRRP protocol is used between router A and router B, see Figure 3-10. These two routers are used for master/backup selection. The EOAM (including EFM and CFM) is used to detect the link states between router A and router C, and between router B and router C. The state of EOAM for VRRP transfers in accordance with the VRRP protocol negotiation. When receiving the link fault notified by EOAM, the VRRP decreases the priority based on configuration and triggers master/slave router changeover. Figure 3-10 EOAM for VRRP Application Three
3.3 Configuring VRRP To configure VRRP on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#vrrp
Enters VRRP configuration mode.
2
ZXR10(config-vrrp)#interface
Enters VRRP interface configuration mode.
3-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Step
Command
Function
3
ZXR10(config-vrrp-if)#vrrp
Configures VRRP virtual IPv4 address in VRRP
>[secondary]
interface configuration mode.
4
ZXR10(config-vrrp-if)#vrrp
Configures VRRP priority in VRRP interface configuration mode. Range: 1-254, default: 100.
5
ZXR10(config-vrrp-if)#vrrp
Configures VRRP group pre-emption in VRRP
<seconds>]
interface configuration mode.<seconds> indicates pre-emption delay. Range: 0-3600 seconds, default: 0.
6
ZXR10(config-vrrp-if)#vrrp
Configures the interval to send VRRP
{<1-40>|[msec <50-40000>]}
advertisements in VRRP interface configuration mode. The default value of interval is 1 second. Unit for <1-40> is second, and unit for <50-40000> is millisecond. The parameter msec is optional and it changes the unit of the interval to millisecond from second.
7
ZXR10(config-vrrp-if)#vrrp
Configures whether sending interval is learnt from the notification packets. The default configuration is not learning.
8
ZXR10(config-vrrp-if)#vrrp
Configures a VRRP track interface in VRRP
interface configuration mode. When the priority
rapid-down]
decrement is not specified, the default priority is decreased by 10. Any link state is not traced by default.
9
ZXR10(config-vrrp-if)#vrrp
Configures VRRP heartbeat in VRRP interface
configuration mode, that is to configure a out-interface for VRRP packets.
10
ZXR10(config-vrrp-if)#vrrp
Configures a VRRP authentication string in
ion <string>
VRRP interface configuration mode. The string consists of 1-8 characters. (This configuration is only available for version 2 of the VRRP.)
11
12
ZXR10(config-vrrp-if)#vrrp
Configures VRRP detection group, detection
group | object}<string>{ link-type | peer-type |
object, or policy type in VRRP interface
priority-decrement <1-254>}
configuration mode.
ZXR10(config-vrrp-if)#vrrp
Configures VRRP version in VRRP interface configuration mode. v2 supports IPv4 configuration, and v3 supports IPv4 and IPv6 configuration.
3-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Step
Command
Function
13
ZXR10(config-vrrp-if)#vrrp
Enables the accept function in VRRP interface configuration mode. This function is enabled by default.
14
ZXR10(config-vrrp-if)#vrrp
Enables tje check-ttl function in VRRP interface configuration mode, default: enabled.
15
16
ZXR10(config-vrrp-if)#vrrp
Configures VRRP administration group function
owner | interface
in VRRP interface configuration mode.
ZXR10(config-vrrp-if)#vrrp
Configures the mode to send packets on an
rotation}
egress interface (heartbeat line) of VRRP. l
All: All heartbeat lines send packages at the same time.
l
Rotation: The heartbeat line sends packages in polling mode.
Parameter descriptions in Step 3 are as follows: Parameter
Description
ID of the virtual router. Range: 1-255.
ipv4
VRRP IPv4 virtual address.
IP address of the virtual router.
secondary
A secondary IP address supported by the virtual router.
Parameter descriptions in Step 8 are as follows: Parameter
Description
priority-decrement
Decreases the priority for a specified tracing link. By default, the priority is decreased by 10.
rapid-down
The priority is switched to 1 immediately. If this command is run on VRRP master router, a special message will be sent to a Backup router. In this case, the backup router will be switched to a master router immediately.
Parameter descriptions in Step 11 are as follows: Parameter
Description
ID of the virtual router. Range: 1-255.
group
Track group.
object
Track object.
string
Name of a track group or track object.
3-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Parameter
Description
link-type
Link-type.
peer-type
Peer-type.
priority-decrement <1-254>
Priority decrement.
Parameter descriptions in Step 15 are as follows: Parameter
Description
ID of the virtual router. Range: 1-255.
owner
The current group is the administration group that receives packets and manages link states.
Interface name of the administration group.
vrid <1-255>
Virtual router ID of the administration group. Range: 1-255.
3.4 Maintaining VRRP To maintain VRRP on the ZXR10 M6000, run the following commands: Command
Function
ZXR10#show vrrp ipv4 brief
Displays the brief information of all IPv4 VRRP groups on a router.
ZXR10#show vrrp ipv4 brief interface
Displays the brief information of all IPv4 VRRP groups on a specific interface.
ZXR10#show vrrp interface
Displays the detailed information of all VRRP groups or a specified group on a specified interface.
The following is sample output from the show vrrp ipv4 brief command: ZXR10#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
Master addr
fei-0/1/0/2
255
254 999
P
Master 192.168.1.10
15.15.15.1
fei-0/1/0/1
100
200 10000
P
Master 35.35.35.1
1.1.1.1
fei-0/1/0/1
120
255 157
A P L Master 35.35.35.1
VRouter addr
35.35.35.1
Parameter descriptions are as follows: Command Output
Description
Interface
Interface on which VRRP is used.
vrID
ID of the VRRP group. Range: 1-255. 3-11
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Command Output
Description
Pri
VRRP priority.
Time
The local notification time (millisecond).
A
Whether it is a owner of the virtual address, which means whether the VRRP virtual IP address is the same as the IP address of the interface.
P
Whether the preemption mode is used.
L
Whether the learning mode is used.
State
VRRP state.
Master addr
Interface address of the master router in a virtual router group.
VRouter addr
IP address of a virtual router.
The following is sample output from the show vrrp ipv4 brief interface command: ZXR10#show vrrp ipv4 brief interface fei-0/1/0/1 The total of vrrp group on this Interface is 2. ====================================================================== Interface
vrID Pri Time
A P L State
fei-0/1/0/1
100
200 10000
fei-0/1/0/1
120
255 157
P
Master addr
Master 35.35.35.1
A P L Master 35.35.35.1
VRouter addr 1.1.1.1 35.35.35.1
The following is sample output from the show vrrp interface command: ZXR10(config)#show vrrp interface smartgroup4 smartgroup4 - vrID 5 Vrrp configure info: IP version 4, VRRP version 3 Virtual IP address is 0.0.0.0 Virtual MAC address is 0000.5e00.0105 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 0 Admin-group is None Vrrp run info: State is Init 0 state changes, last state change 00:00:00 Current priority is 100 Master router is unknown
3-12 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration 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.609 sec, no learn
Parameter descriptions are as follows: Command Output
Description
Decrement-Priority
The decreased priority after the tracked interface is shut down.
Tracked interface
The tracked interface.
Track name
The name of tracked group or object.
Track type
The track type, including detection group and detection object.
Detect type
The link detection type, which is configured in SAMGR configuration.
Master router is local
This router is the master router is the virtual router group.
3.5 VRRP Configuration Instances 3.5.1 Basic VRRP Configuration Example Configuration Description The VRRP protocol is used between the R1 and the R2. The interface address of the R1 is set to 10.0.0.1 and that of the R2 is set to 10.0.0.2. The VRRP virtual address is the interface address 10.0.0.1 on the R1. In this case, the R1 is the IP address owner and has the highest priority 255. The R1 operates as the master router. The VRRP virtual address can also be set to another address. When the R1 is configured with the highest priority, the R1 is the master router. For the network structure, see Figure 3-11. Figure 3-11 Basic VRRP Configuration (IPv4)
3-13 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Configuration Flow 1. Enter the interfaces on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode and then enter the interface on which the VRRP is to be configured. 3. Configure the same VRRP group ID and virtual address for the R1 and the R2. To make the R1 the master router or specify a higher priority for the R1, configure related commands on the R1 first. If the priorities (the default priority is 100) of two routers are the same, the router becomes the master router in the group, on which VRRP is enabled and messages are advertised first.
Configuration Command Run the following commands on the R1: R1(config)#interface fei-0/1/0/1 R1(config-if)#ip address 10.0.0.1 255.255.0.0 R1(config)#vrrp R1(config-vrrp)#interface fei-0/1/0/1 R1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
Run the following commands on the R2: R2(config)#interface fei-0/1/0/1 R2(config-if)#ip address 10.0.0.2 255.255.0.0 R2(config)#vrrp R2(config-vrrp)#interface fei-0/1/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1
Configuration Verification View the VRRP information and configuration result on the R1, which is displayed as follows: R1#show vrrp ipv4 brief Interface fei-0/1/0/1
vrID Pri Time A P L State 1
255 1000 A P
Master addr VRouter addr
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.*/
R1#sho vrrp interface fei-0/1/0/1 vrid 1 fei-0/1/0/1 - vrID 1 Vrrp configure info:
/*VRRP configuration information*/
IP version 4, VRRP version 3 Virtual IP address is 10.0.0.1 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec
3-14 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 0 Admin-group is None Vrrp run info: State is Master
/*Running information of VRRP on current interface*/ /*VRRP running state*/
1 state changes, last state change 22:50:03 6 day(s) /*Number of state changes and the time for how long the system has been running until the last change. If there is no change, the value is 0.*/ Current priority is 255 /*Current priority, the largest priority of the Owner is 255*/ Master router is local Master router address is 10.0.0.1 Master router priority is 255 Master Advertisement interval is 1.000 sec Master Down interval is 3.003 sec, no learn R1#
3.5.2 Symmetrical VRRP Configuration Example Configuration Description Symmetrical VRRP means load sharing is supported. In this example, two VRRP groups are configured. PC1 and PC2 use the virtual router in Group 1 as the default network gateway, and the address is 10.0.0.1. PC3 and PC4 use the virtual router in Group 2 as the default network gateway, and the address is 10.0.0.2. The R1 and R2 provide backups for each other. When both R1 and R2 become invalid, the communications between the hosts and external network will be interrupted. For the network structure, see Figure 3-12.
3-15 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Figure 3-12 Symmetrical VRRP Configuration (IPv4)
Configuration Flow 1. Enter the interfaces on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode and then enter the interface on which the VRRP is to be configured. 3. Configure VRRP Group 1 and corresponding virtual address on R1, and configure VRRP Group 2 and corresponding virtual address on R2. Specify a higher priority for VRRP Group 1 on R1 and VRRP Group 2 on R2. After that, R1 is the master router in Group 1 and the backup router in Group 2, and R2 is the master router in Group 2 and the backup router in Group 1. The R1 and R2 provide backups for each other.
Configuration Command Run the following commands on the R1: R1(config)#interface fei-0/1/0/1 R1(config-if)#ip address 10.0.0.1 255.255.0.0 R1(config)#vrrp R1(config-vrrp)#interface fei-0/1/0/1 R1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R1(config-vrrp-if)#vrrp 2 ipv4 10.0.0.2
Run the following commands on the R2: R2(config)#interface fei-0/1/0/1 R2(config-if)#ip address 10.0.0.2 255.255.0.0 R2(config)#vrrp R2(config-vrrp)#interface fei-0/1/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 2 ipv4 10.0.0.2
3-16 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration
Configuration Verification Check the VRRP information and configuration result on R1, as shown below. R1#show vrrp ipv4 brief Interface
vrID Pri Time
A P L State
fei-0/1/0/1
1
255 1000
A P
Master 10.0.0.1
Master addr
VRouter addr 10.0.0.1
fei-0/1/0/1
2
100 1000
P
Backup 10.0.0.2
10.0.0.2
/*A: whether the router is the address owner. P: whether preemption is configured. L: whether to learn the interval for sending VRRP messages from the master.*/
R1#show vrrp interface fei-0/1/0/1 vrid 1 fei-0/1/0/1 - vrID 1 Vrrp configure info:
/*VRRP configuration information*/
IP version 4, VRRP version 3 Virtual IP address is 10.0.0.1 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 0 Admin-group is None Vrrp run info: State is Master
/*Operation information of VRRP on current interface*/ /*VRRP operation state*/
1 state changes, last state change 22:50:03 6 day(s) /*Number of state changes and the time for how long the system has been operated until the last change. If there is no change, the value is 0.*/ Current priority is 255 /*current priority, the largest priority of the Owner is 255*/ Master router is local Master router address is 10.0.0.1 Master router priority is 255 Master Advertisement interval is 1.000 sec Master Down interval is 3.003 sec, no learn R1#
3-17 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
3.5.3 VRRP Heartbeat Configuration Example Configuration Description The VRRP protocol is used between R1 and R2. The VRRP virtual address is the interface address 10.0.0.1 of R1. R1 operates as the master router. For the network structure, see Figure 3-13. Figure 3-13 VRRP Heartbeat Configuration (IPv4)
Configuration Flow 1. Enter the interfaces on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode and then enter the interface on which the VRRP is to be configured. 3. Configure the same VRRP group ID and virtual address for R1 and R2. To make R1 as the master router, specify a higher priority for R1, or set it to be the IP address owner (The interface address of R1 is set as the virtual address and R1 has the highest priority 255). 4. In VRRP interface configuration mode of R1 and R2, configure egress interfaces for packets in the VRRP group to ensure that packets can be sent and received through these two egresses.
Configuration Command Run the following commands on R1: R1(config)#interface fei-0/1/0/1 R1(config-if)#ip address 10.0.0.1 255.255.0.0 R1(config)#vrrp R1(config-vrrp)#interface fei-0/1/0/1 R1(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R1(config-vrrp-if)#vrrp 1 out-interface fei-0/1/0/2
Run the following commands on R2: 3-18 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration R2(config)#interface fei-0/1/0/1 R2(config-if)#ip address 10.0.0.2 255.255.0.0 R2(config)#vrrp R2(config-vrrp)#interface fei-0/1/0/1 R2(config-vrrp-if)#vrrp 1 ipv4 10.0.0.1 R2(config-vrrp-if)#vrrp 1 out-interface fei-0/1/0/2
Configuration Verification Check the VRRP information and configuration results on R1, which are displayed as follows: R1#show vrrp ipv4 brief Interface
vrID
fei-0/1/0/1
1
Pri
Time
A
P
255
1000
A
P
L State Master
Master addr
VRouter addr
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.*/
R1#show vrrp interface fei-0/1/0/1 vrid 1 fei-0/1/0/1 - vrID 1 Vrrp configure info: /*VRRP configuration information*/ IP version 4, VRRP version 3 Virtual IP address is 10.0.0.1 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Out-interface(heartbeat line) is fei-0/1/0/2 Tracked interface items: 0 Interface
State
Policy
Reduce-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*/ 2 state changes, last state change 00:00:00 /*Number of state changes and the time for how long the system has been running until the last change. If there is no change, the value is 0.*/ Current priority is 255 /*Current priority, the largest priority of the Owner is 255*/
3-19 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Master router is local Master router address is 10.0.0.1 Master router priority is 255 Master Advertisement interval is 1.000 sec Master Down interval is 3.003 sec, no learn
3.5.4 VRRP BFD Configuration Example Configuration Description The VRRP protocol is used between Router A and Router B. The VRRP virtual IP address is 10.0.0.3. For the network structure, see Figure 3-14. Figure 3-14 VRRP Track Configuration (IPv4)
Configuration Flow 1. Enter the interface on which VRRP will be configured and configure an IP address for it. 2. Enter VRRP configuration mode from global configuration mode, and then enter the interface on which the VRRP is to be configured. 3. Configure the same VRRP group ID and virtual IP addre for Router A and Router B. To set Router A as the master router, specify a higher priority for Router A, or set it to be the IP address owner (The interface address of Router A is set as the virtual address and Router A has the highest priority 255). 4. Enter SAMGR configuration mode of Router A and Router B to configure a detection object respectively. Configure the Ethernet Operation, Administration and Maintenance (EOAM) object for Router A and Router B, and then configure the Bidirectional Forwarding Detection (BFD) object. 5. Enter VRRP interface configuration mode of Router A and Router B, enable VRRP track function to track the objects configured in Step 4 respectively.
Configuration Command Run the following commands on Router A: 3-20 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 3 VRRP Configuration RA(config)#interface fei-0/1/0/1 RA(config-if)#ip address 10.0.0.1 255.255.0.0 RA(config-if)#exit RA(config)#vrrp RA(config-vrrp)#interface fei-0/1/0/1 RA(config-vrrp-if)#vrrp 1 ipv4 10.0.0.3 RA(config-vrrp-if)#vrrp 1 track object zte1 link-type RA(config-vrrp-if)#vrrp 1 track object zte2 peer-type
The tracked object named zte1 and zte2 should be configured in the SAMGR module in advance. For the detailed configuration, refer to the “SAMGR Configuration” chapter. Run the following commands on Router B: RB(config)#interface fei-0/1/0/1 RB(config-if)#ip address 10.0.0.2 255.255.0.0 RB(config-if)#exit RB(config)#vrrp RB(config-vrrp)#interface fei-0/1/0/1 RB(config-vrrp-if)#vrrp 1 ipv4 10.0.0.3 RB(config-vrrp-if)#vrrp 1 track object zte1 link-type RB(config-vrrp-if)#vrrp 1 track object zte2 peer-type
The tracked object named zte1 and zte2 should be configured in the SAMGR module in advance. For the detailed configuration, refer to the “SAMGR Configuration” chapter.
Configuration Verification Check the VRRP track information and configuration results on Router A, which is displayed as follows: RA#show vrrp ipv4 brief Interface
vrID
Pri
Time
A
P
fei-0/1/0/1
1
100
1000
A
P
L State Master
Master addr
VRouter addr
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.*/
RA#show vrrp interface fei-0/1/0/1 fei-0/1/0/1 - vrID 1 Vrrp configure info: IP version 4, VRRP version 3 Virtual IP address is 10.0.0.3 Virtual MAC address is 0000.5e00.0101 Advertise time is 1.000 sec Configured priority is 100 Preemption enable, delay 0 secs
3-21 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) No authentication data Check ttl enable Vrrp accept mode enable Out-interface send-mode is all Tracked interface items: 0 Interface
State
Policy
Reduce-Priority
Tracked detect items: 1 Track name: zte2
Track type: object
Detect type: peer-bfd
Policy type: peer Track state: unknown Track name: zte1
Track type: object
Detect type: cfm
Policy type: link Track state: unknown Admin-group is None Vrrp run info: State is Master 155 state changes, last state change 01:12:08 Current priority is 255 Master router is local Master router address is 10.0.0.3 Master router priority is 100 Master Advertisement interval is 1.000 sec Master Down interval is 3.609 sec, no learn
3-22 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4
Ping Detect Configuration Table of Contents Ping Detect Overview .................................................................................................4-1 Configuring Ping Detect..............................................................................................4-2 Maintaining Ping Detect..............................................................................................4-3 Ping Detect Configuration Instances...........................................................................4-4
4.1 Ping Detect Overview Introduction The Ping Detect function is also called the automatic detection function. It detects the reachability of the destination through request/response messages of the ICMP. After the detection, it feeds back the detection results to the related backup functional module to trigger the active/standby switchover function based on the application of the network layer. The external router for branch router is configured with interface backup on the Ethernet interface, see Figure 4-1. Figure 4-1 Application Overview of Ping Detect
If the destination is unreachable because the Ethernet interface of the peer gateway 1 corresponding to the main link is not configured with an IP address, the backup mode that depends on the protocol status of the detection interface cannot implement the active/standby switchover function. 4-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
In the same way, if the destination of (non-direct) the main link is faulty, for example, the external dedicated line of gateway 1 is faulty, the traditional backup mechanism also cannot implement the active/standby switchover function. The detection results ( the destination ICMP is reachable or unreachable) will be fed back to the related modules, such as static route backup module, dialing backup module, and the VRRP module, to trigger the active/standby switchover operation. After that, the above faults are solved.
Ping Detect Operating Flow The whole operating flow of the Ping detection group is as follows: 1. Configure a global Ping detection group, including the address and the nexthop for the group to be detected. You can define some detection policies flexibly, such as the detection period, maximum retry times, and time-out time. You can configure the "and” or "or" relationship among multiple detection objects of a detection group. l
If the relationship among multiple objects to be detected is "and", and one IP address cannot be pinged successfully, it means that the detection group is unreachable, and it does not detect other addresses any more. l If the relationship among multiple objects to be detected is " or", and one IP address can be pinged successfully, it means that the detection group is reachable, and it does not detect other addresses any more. 2. In SAMGR configuration mode, run the track test ping-detect group command to enable the Ping Detect function. The Ping Detect group sends ICMP detection messages to the objects to be detected continuously, and confirms that the objects to be detected are reachable in accordance with the detection policies (detection times, time-out duration) defined before.
l l
Note: You can check the Ping Detect result by running the show samgr brief command. To use the Ping Detect function, the ICMP service of the firewall corresponding to the objects to be detected should be enabled.
4.2 Configuring Ping Detect To configure the Ping Detect function on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#detect-group
Configures a detection group. The range of the group number is 1-10. 4-2
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration
Step
Command
Function
2
ZXR10(config-detect)#option {And | Or}
Configures the logical relationship "and" or "or" for objects to be detected. And: It indicates that this group is connected when all items in the group are connected. Or: It indicates that this group is connected when any item in the group is connected.
3
ZXR10(config-detect)#detect-list <list-number>[vrf
Configures detection items for the detection group,
and the destination address for a detection item, and specifies the next hop address.
4
ZXR10(config-detect)#retry-times
Configures the maximum number of times that the detection group re-transmits detection results to the Ping module. Range: 1-10, default: 2.
5
ZXR10(config-detect)#loop-time <seconds>
Configures the loop detection interval for the detection results. Range: 2-86400s, default: 15s.
6
ZXR10(config-detect)#time-out <seconds>
Configures the time-out time that the detection group transmits detection results to the PING module. Range: 1-20s, default: 2s.
7
ZXR10(config-samgr)#track
Enables the Ping Detect function in SAMGR
group
configuration mode.
4.3 Maintaining Ping Detect To maintain the ping detect function on the ZXR10 M6000, run the following commands: Command
Function
ZXR10#show running-config ping-detect
Displays the configuration of the Ping Detect function. The default value is not displayed.
ZXR10#show running-config ping-detect all
Displays the configuration of the Ping Detect function. The default value is displayed. Displays the information of the Samgr Track Ping Detect
ZXR10#show samgr track
function. Displays the Ping Detect results.
ZXR10#show samgr brief
The following is sample output from the show samgr track command: ZXR10#show samgr track Track name is test Detect type
: ping-detect
4-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Track parameter Group: 1 App-sub count
: 0
Dyn-creat count: 0 Active track
: none
Passive track
: none
Track state
: up
State change
: 3 state changes, last state change 2010-01-01 01:11:05
Parameter descriptions are as follows: Command Output
Description
Detect type
Displays the track type.
Track parameter
Displays track parameters.
Track state
Displays the track state.
4.4 Ping Detect Configuration Instances 4.4.1 Basic Ping Detect Configuration Examples Configuration Description There are three interfaces between R1 and R2. A detection group between R1 and R2 must be configured. For the network structure, see Figure 4-2. Figure 4-2 Network Structure of Basic Ping Detect Configuration Example
Addresses of the interfaces on R1 and R2 are as follows: Interface
R1
R2
IP Address
Mask
fei-0/1/0/5
100.0.0.15
255.255.255.0
fei-0/1/0/6
101.0.0.15
255.255.255.0
fei-0/1/0/7
102.0.0.15
255.255.255.0
fei-0/1/0/5
100.0.0.20
255.255.255.0
fei-0/1/0/6
101.0.0.20
255.255.255.0
fei-0/1/0/7
102.0.0.20
255.255.255.0
4-4 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration
Configuration Flow 1. 2. 3. 4.
Configure a detection group. Configure detection items for the detection group on R1. Set parameters for the detection group as required. Enable the Ping Detect function in Samgr configuration mode, and check the result by running the show command. 5. Set the logical relationship among objects to be detected to And, add a detection item that cannot be pinged successfully, and then check the detection result. Set the logical relationship among objects to be detected to Or, and then check the detection result.
Configuration Command Run the following commands to configure R1: ZXR10(config)#detect-group 1 ZXR10(config-detect)#detect-list 1 100.0.0.20 ZXR10(config-detect)#detect-list 2 101.0.0.20 ZXR10(config-detect)#detect-list 3 102.0.0.20 ZXR10(config-detect)#exit ZXR10(config)#samgr ZXR10(config-samgr)#track test ping-detect group 1 ZXR10(config-samgr)#exit
Configuration Verification Check the Ping Detect configuration results on R1: ZXR10(config)#show samgr brief The total of track at this Router is 1. ====================================================================== Track-name
Detect-type
test
ping-detect
App-num 0
State up
Set the logical relationship among objects to be detected to And, and then add a detection item that cannot be pinged successfully. ZXR10(config-detect)#option And /*Set the logical relationship for the detect object to "And"*/ ZXR10(config-detect)#detect-list 4 1.2.3.4 ZXR10(config-detect)#exit ZXR10(config)#show samgr brief The total of track at this Router is 1. ====================================================================== Track-name test
Detect-type ping-detect
App-num 0
State L-down
Set the logical relationship among objects to be detected to Or, and then check the detect result: ZXR10(config-detect)#option Or
4-5 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) /*Set the logical relationship for the detect object to "Or"*/ ZXR10(config-detect)#exit ZXR10(config)#show samgr brief The total of track at this Router is 1. ====================================================================== Track-name
Detect-type
test
ping-detect
App-num 0
State up
4.4.2 Cooperation Configuration Example Between a Directly Connected Route and the Ping Detect Configuration Description This section describes the basic functions of the cooperation between a directly connected route and the Ping Detect, see Figure 4-3. Figure 4-3 Cooperation Configuration Between a Directly-Connected Route and the Ping Detect
Configuration Flow 1. Set the IP addresses for R1, R2 and R4, enable the OSPF protocol, and create OSPF neighbor relations between routers. 2. Configure the ping detect group on R2, configure the tracing object(s) of samgr, and bind the tracing object(s) on the interface gei-0/7/1/8.
Configuration Commands Run the following commands on R1: 4-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration R1(config)#interface gei-0/0/0/8 R1(config-if)#no shutdown R1(config-if)#ip address 71.88.1.2 255.255.255.0 R1(config-if)#exit
R1(config)#router ospf 19 R1(config-ospfv2)#router-id 22.22.22.22 R1(config-ospfv2)#network 71.88.1.0 0.0.0.255 area 0 R1(config-ospfv2)#exit
Run the following commands on R2: R2(config)#interface gei-0/7/1/8 R2(config-if)#no shutdown R2(config-if)#ip address 71.88.1.1 255.255.255.0 R2(config-if)#exit R2(config)#interface gei-0/2/1/7 R2(config-if)#no shutdown R2(config-if)#exit R2(config)#interface gei-0/2/1/7.1 R2(config-subif)#ip address 41.52.17.2 255.255.255.0 R2(config-subif)#exit
R2(config)#vlan R2(config-vlan)#interface gei-0/2/1/7.1 R2(config-subvlan-if)#encapsulation-dot1q 1 R2(config-subvlan-if)#exit
R2(config)#router ospf 19 R2(config-ospfv2)#router-id 22.11.11.22 R2(config-ospfv2)#network 71.88.1.0 0.0.0.255 area 0 R2(config-ospfv2)#network 41.52.17.0 0.0.0.255 area 0 R2(config-ospfv2)#exit
R2(config)#detect-group 10 R2(config-detect)#option or R2(config-detect)#retry-times 3 R2(config-detect)#loop-time 12 R2(config-detect)#time-out 3 R2(config-detect)#detect-list 9 41.52.17.3 41.52.17.2 R2(config-detect)#detect-list 3 19.19.19.1 R2(config-detect)#detect-list 6 200.11.12.101 R2(config-detect)#detect-list 7 30.0.12.3 R2(config-detect)#detect-list 8 100.10.11.201 R2(config-detect)#detect-list 4 1.1.50.1 R2(config-detect)#exit
4-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
R2(config)#samgr R2(config-samgr)#track abc ping-detect group 10 R2(config-samgr)#exit R2(config)#interface gei-0/7/1/8 R2(config-if)#track abc R2(config-if)#exit
Run the following commands on R4: R4(config)#interface gei-0/0/0/8 R4(config-if)#no shutdown R4(config-if)#exit R4(config)#interface gei-0/0/0/8.1 R4(config-subif)#ip address 1.2.3.4 255.255.255.0 R4(config-subif)#ip address 41.52.17.3 255.255.255.0 secondary R4(config-subif)#interface mac-address offset 23 R4(config-subif)#exit
R4(config)#vlan R4(config-vlan)#interface gei-0/0/0/8.1 R4(config-subvlan-if)#encapsulation-dot1q 1 R4(config-subvlan-if)#exit
R4(config)#router ospf 19 R4(config-ospfv2)#router-id 33.33.33.33 R4(config-ospfv2)#network 41.52.17.0 0.0.0.255 area 0 R4(config-ospfv2)#exit
Configuration Verification Query the status of the tracing object(s) on R2, and you can find that the status of the tracing object is up. Run the show samgr brief command to check whether there is a new IP address for a direct routing of the interface gei-0/7/1/8 added in the protocol table, which is displayed as follows: R2(config)#show samgr brief The total of track at this Router is 1. Track-name
Detect-type
abc
ping-detect
App-num
State
1
up
R2#show ip protocol routing network 71.88.1.0 Protocol routes: status codes: *valid, >best, i-internal, s-stale
*>
Dest
NextHop
71.88.1.0/24
71.88.1.1
RoutePrf 0
RouteMetric 0
Protocol direct
4-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 4 Ping Detect Configuration *
71.88.1.0/24
71.88.1.0
110
1
ospf
*>
71.88.1.1/32
71.88.1.1
0
0
address
After disabling the gei-0/2/1/7.1 interfaces using the shutdown command, check whether the tracing state is down on R2. The direct routes of the gei-0/7/1/8 interfaces will be removed. R2#show samgr brief The total of track at this Router is 1. Track-name
Detect-type
abc
ping-detect
App-num 1
State L-down
R2#show ip protocol routing network 71.88.1.0 IPv4 Routing Table: status codes: *valid, >best Dest
Gw
Interface
Owner
Pri Metric
4-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
This page intentionally left blank.
4-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5
EFM Configuration Table of Contents EFM Overview............................................................................................................5-1 Configuring EFM ........................................................................................................5-2 Maintaining EFM ........................................................................................................5-4 EFM Configuration Instances .....................................................................................5-6
5.1 EFM Overview Introduction EFM is a standard defined by Institute of Electrical and Electronics Engineers (IEEE), and is used to detect, monitor, and maintain directly connected links. It is mainly used for monitoring and detecting the links at the access side. On the ZXR10 M6000, EFM monitors the operation state statistics of point-to-point links directly connected in physical. The EFM monitors the link operation information as much as possible, such as error rate of frame transmission, comparison of sending rate and receiving rate on the link, and loss statistics. At the same time, the EFM also detects and advertises the emergency failure and events of the system, such as system unrecoverable fault. This ensures the transmission quality on Layer 2 links to some extent, and monitors the operation state in real time. This is helpful for network administrators to maintain the network, and reduces the maintenance cost. The ZXR10 M6000 supports the following EMF functions: l l l l l
Supporting automatic negotiation with other devices Supporting remote loopback statistics detection on the links Supporting detection of link error frames and symbols Supporting emergency event advertisement Supporting linkage function handling selectively
EFM Features The EFM features are as follows: 1. The EFM detects whether the EFM function on the peer device is enabled through its protocol packets. It interacts with packets to know whether the negotiation procedure is completed in accordance with the related configurations on two devices. 2. After the negotiation, the EFM collects statistics of link operation information (such as error frames or symbols) in accordance with the link monitoring in a cycle. 5-1 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
3. When the number of error frames or symbols exceeds the threshold, the EFM triggers related event notification to inform the local device and the remote device. In this way, the network administrators know the operation information of the link. 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, the EFM can only be applied on the directly connected device, see Figure 5-1. Figure 5-1 EFM Principle
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.
5.2 Configuring EFM To configure EFM on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#efm
Enters EFM configuration mode
2
ZXR10(config-efm)#set ethernet-oam function <state>
Sets the switch to enable EFM globally.
3
ZXR10(config-efm)#set ethernet-oam oui <word>
Sets the Organizationally Unique Identifier (OUI) field for the EFM vendor. By default, it is set to ZTE.
4
ZXR10(config-efm)#set ethernet-oam remote-timeout
Configures the time-out time for the EFM overall loopback control. Range: 1-10, unit: second, default: 3.
5
ZXR10(config-efm)#interface
Enters EFM interface configuration mode.
5-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Step
Command
Function
6
ZXR10(config-efm-if)#set ethernet-oam function <state>
Enables the EFM function for a specific interface.
7
8
ZXR10(config-efm-if)#set ethernet-oam link-monitor function
Enables the link monitoring function
<state>
for a specific interface.
ZXR10(config-efm-if)#set ethernet-oam link-monitor frame
Configures the window value and
threshold
threshold value for the error frames during the link monitoring.
9
ZXR10(config-efm-if)#set ethernet-oam link-monitor
Configures the window value and
symbol-period threshold
threshold for the error symbols during the link monitoring.
10
ZXR10(config-efm-if)#set ethernet-oam link-monitor frame-period
Configures the window value and
threshold
threshold for error frames during the link monitoring.
11
ZXR10(config-efm-if)#set ethernet-oam link-monitor frame-second
Configures the window value and
threshold
threshold for the error frames per second during the link monitoring.
12
ZXR10(config-efm-if)#set ethernet-oam link-timeout
{
time. Range: 3-20 seconds, default: 5 seconds.
13
ZXR10(config-efm-if)#set ethernet-oam mode <mode>
Configures EFM configuration mode, including active or passive. The default mode is active.
14
ZXR10(config-efm-if)#set ethernet-oam rmt-loopback
Enables or disables the EFM link loopback function manually.
Parameter descriptions in Step 8 are as follows: Parameter
Description
Threshold of error frames. Range: 1-65535, default: 1.
<win-value>
Window value of error frame. Range: 1-60 seconds, default: 1 second.
Parameter descriptions in Step 9 are as follows: 5-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Parameter
Description
Threshold of error symbols. Range: 1-65535, default: 1.
<win-value>
Window value of error symbol. Range: 1-65535 millions, default: 1 million.
Parameter descriptions in Step 10 are as follows: Parameter
Description
Threshold of error frame cycle. Range: 1-65535 millions, default: 1 million.
<win-value>
Window value of error frame cycle. Range: 1-65535 millions, default: 1 million.
Parameter descriptions in Step 11 are as follows: Parameter
Description
Threshold of error frames per second. Range: 1-900 frames per second, default: 1 frame per second.
<win-value>
Window value of error frames per second. Range: 1-900 seconds, default: 1 second.
5.3 Maintaining EFM To maintain EFM on the ZXR10 M6000, run the following commands: Command
Function
ZXR10#debug ethernet-oam {interface < interface-name>| packet interface
Sends or receives EFM packets. Run
the no command to disable all enabled
org-spec | reqst-varb | respst-varb} mode {all-time | number
functions.
ZXR10#show ethernet-oam [
Displays the global EFM configuration,
| statistics}]
or the interface EFM configuration and state.
Parameter descriptions of the debug command are as follows: Parameter
Description
Interface name
dual
Displays the information of sent and received packets.
in
Displays the information of received packets.
out
Displays the information of sent packets.
all
Displays information of all types of EFM packets.
information
Displays the information of EFM information packets. 5-4
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Parameter
Description
lpbk-ctrl
Displays the information of EFM loopback control packets.
notify
Displays the information of EFM notification packets.
org-spec
Displays the information of packets defined by vendors.
reqst-varb
Displays the information of EFM variable-request packets.
respst-varb
Displays the information of EFM variable-response packets.
all-time
Always displays packet debugging information.
Specifies the number of packets of which the information will be displayed. Range: 10-500, default: 200.
Parameter descriptions are as follows: Parameter
Description
Interface name.
discovery
The parameter after the interface name used to display the related state information of the EFM negotiation. The parameter after the interface name used to display the related
link-monitor
information of the EFM link monitoring. The parameter after the interface name used to display the related
statistics
information of the EFM packet statistics, including sent and received packet statistics of the loopback.
The following is sample output from the show ethernet-oam command: ZXR10#show ethernet-oam fei-0/1/0/1 discovery PortId 2: Ethernet Oam enable Local DTE ---------Config: Mode
:active
Period Time
:10*(100ms)
Link time out
:50*(100ms)
Status: Parse
:forward
Multiplexer
:forward
Stable
:no
Discovery
:undone
Loopback
:off
PDU Revision
:0
Unidirection
:nonsupport
5-5 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Remote DTE ----------Config: Mode
:passive
Link Monitor
:nonsupport
Unidirection
:nonsupport
Remote Loopback
:nonsupport
Mib Retrieval
:nonsupport
PDU max size
:1518
Status: Parse
:forward
Multiplexer
:forward
Stable
:no
Mac Address
:0000.0000.0000
PDU Revision
:0
Command Output
Description
Mode
EFM working mode.
Link time out
Link time-out.
Parse
Parser state.
Multiplexer
Multiplexer state.
Stable
Local and remote stable bit.
Discovery
Identifier of discovery complete.
Loopback
Identifier of loopback enabling.
PDU Revision
Revision in the packet.
5.4 EFM Configuration Instances 5.4.1 EFM Connection Establishment Configuration Description R1 and R2 are connected directly. The EFM on the directly-connected interfaces of R1 and R2 need to be configured. For the network structure, see Figure 5-2. Figure 5-2 Network Architecture of EFM Connection Establishment
5-6 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Configuration Flow 1. Configure the EFM function for the interface of R1 connecting to R2 directly, enable the EFM and link-monitor switch for a specified interface, and then enable the EFM function globally. 2. Configure the EFM function for the interface of R2 connecting to R1 directly, enable the EFM and link-monitor switch for a specified interface, and then enable the EFM function globally. 3. Run the show ethernet-oam discovery command on R1 and R2 to check the EFM connection establishment. 4. Run the show ethernet-oam link-monitor command on R1 and R2 to check the count of link errors between R1 and R2.
Configuration Command Run the following commands on R1: R1#configure terminal R1(config)#efm R1(config-efm)#interface gei-0/0/1/1 R1(config-efm-if)#set ethernet-oam function enable R1(config-efm-if)#set ethernet-oam link-monitor function enable R1(config-efm-if)#exit R1(config-efm)#set ethernet-oam oui R1 R1(config-efm)#set ethernet-oam function enable R1(config-efm)#exit
Run the following commands on R2: R2#configure terminal R2(config)#efm R2(config-efm)#interface gei-0/0/0/1 R2(config-efm-if)#set ethernet-oam function enable R2(config-efm-if)# set ethernet-oam link-monitor function enable R2(config-efm-if)#exit R2(config-efm)#set ethernet-oam oui R2 R2(config-efm)#set ethernet-oam function enable R2(config-efm)#exit
Configuration Verification 1. Run the show ethernet-oam discovery command on R1 to check the link EFM negotiation, which is displayed as follows: R1(config-efm)#show ethernet-oam gei-0/0/1/1 discovery PortId 32: Ethernet Oam enable Local DTE ---------Config: Mode
:active
5-7 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Period Time
:10*(100ms)
Link time out
:50*(100ms)
Status:
/*local state*/
Parse
:forward
/*forwarding state of receiver*/
Multiplexer
:forward
/*forwarding state of sender*/
Stable
:yes
/*Locl link state is "stable".*/
Discovery
:done
/*Link discovery is done.*/
Loopback
:off
/*Loopback is off.*/
PDU Revision
:1
Unidirection
:nonsupport
/*Local configuration is modified once.*/
Remote DTE ----------Config: Mode
:active
Link Monitor
:support
Unidirection
:nonsupport
Remote Loopback
:support
Mib Retrieval
:nonsupport
PDU max size
:1518
Status:
/*remote state*/
Parse
:forward
/*forwarding mode*/
Multiplexer
:forward
/*forwarding mode*/
Stable
:yes
/*Remote link state is "stable".*/
Mac Address
:0001.12ac.121a
/*MAC of remote device*/
PDU Revision
:0
/*Remote configuration is modified for 0 time.*/
2. Run the show ethernet-oam link-monitor command on R1 to check the number of link errors, which is displayed as follows: R1(config-efm)#show ethernet-oam gei-0/0/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
Total Error Symbols
:0
Local Total Error Events
:0
Remote Total Error Events :0 Error Frame Event: Period Window
: 1(s)
Error Frame Threshold
: 1
Total Error Frames
: 0
Local Total Error Events
: 0
Remote Total Error Events : 0
5-8 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration Error Frame Period Event: Frame Window
: 1(ten thousand frames)
Error Frame Threshold
: 1
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)
Total Error Frame Seconds : 0(s) Local Total Error Frame Seconds Events
: 0
Remote Total Error Frame Seconds Events : 0
3. Run the show ethernet-oam discovery command on R2 to check the link EFM negotiation, which is displayed as follows: R2(config)#show ethernet-oam gei-0/0/0/1 discovery PortId 66: Ethernet Oam enable Local DTE ---------Config: Mode
:active
Period Time
:10*(100ms)
Link time out
:50*(100ms)
Status: Parse
:forward
Multiplexer
:forward
Stable
:yes
Discovery
:done
Loopback
:off
PDU Revision
:0
Unidirection
:nonsupport
Remote DTE ----------Config: Mode
:active
Link Monitor
:support
Unidirection
:nonsupport
Remote Loopback
:support
Mib Retrieval
:nonsupport
PDU max size
:1518
Status: Parse
:forward
Multiplexer
:forward
5-9 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) Stable
:yes
Mac Address
: 0020.231d.0e0e
PDU Revision
:1
4. Run the show ethernet-oam link-monitor command on R2 to check the number of link errors, which is displayed as follows: R2(config)#show ethernet-oam gei-0/0/0/1 link-monitor Link Monitoring of Port: 66 Link Monitoring enable Error Symbol Period Event: Symbol Window
:1(million symbols)
Error Symbol Threshold
:1
Total Error Symbols
:0
Local Total Error Events
:0
Remote Total Error Events :0 Error Frame Event: Period Window
: 1(s)
Error Frame Threshold
: 1
Total Error Frames
: 0
Local Total Error Events
: 0
Remote Total Error Events : 0 Error Frame Period Event: Frame Window
: 1(ten thousand frames)
Error Frame Threshold
: 1
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)
Total Error Frame Seconds : 0(s) Local Total Error Frame Seconds Events
: 0
Remote Total Error Frame Seconds Events : 0
5.4.2 EFM Remote Loopback Configuration Description R1 and R2 are connected directly. The EFM function is configured for the directly-connected interfaces of R1 and R2, and the remote loopback function is enabled for R1. R2 loops back the packets. For the network structure, see Figure 5-3.
5-10 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 5 EFM Configuration
Figure 5-3 EFM Remote Loopback
Configuration Flow 1. Configure the EFM function for the interface of R1 connecting to R2 directly, and enable the EFM function globally. 2. Configure the EFM function for the interface of R2 connecting to R1 directly, and enable the EFM function globally. 3. After the EFM connection is established on R1 and R2, enable remote loopback for R1. 4. Run the show ethernet-oam discovery command on R1 and R2 to check the EFM connection establishment.
Configuration Command Run the following commands on R1: R1#configure terminal R1(config)#efm R1(config-efm)#interface gei-0/0/1/1 R1(config-efm-if)#set ethernet-oam function enable R1(config-efm-if)#set ethernet-oam link-monitor function enable R1(config-efm-if)#exit R1(config-efm)#set ethernet-oam oui R1 R1(config-efm)#set ethernet-oam function enable R1(config-efm)#exit
Run the following commands R2: R2#configure terminal R2(config)#efm R2(config-efm)#interface gei-0/0/0/1 R2(config-efm-if)#set ethernet-oam function enable R2(config-efm-if)#set ethernet-oam link-monitor function enable R2(config-efm-if)#exit R2(config-efm)#set ethernet-oam oui R2 R2(config-efm)#set ethernet-oam function enable R2(config-efm)#exit
After the EFM connection is established, enable remote loopback for R1: R1#configure terminal R1(config)#efm R1(config-efm)#interface gei-0/0/1/1 R1(config-efm-if)#set ethernet-oam rmt-loopback start
5-11 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability) R1(config-efm-if)#exit R1(config-efm)#exit
Configuration Verification On the link where the EFM connection is established, R1 sends packets to R2 except OAM Protocol Data Units (OAMPDUs). When R2 receives these packets, it will loop them back to R1 directly.
5-12 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 6
CFM Configuration Table of Contents CFM Overview ...........................................................................................................6-1 Configuring CFM ........................................................................................................6-3 CFM Maintenance ......................................................................................................6-5 CFM Configuration Instances .....................................................................................6-6
6.1 CFM Overview Introduction Ethernet technology becomes the leading technology gradually due to its simplicity and low cost since it was born. In recent years, with the applications of gigabit and 10–gigabit Ethernet technology, Ethernet has been extended towards Metropolitan Area Network (MAN) and Wide Area Network (WAN). Ethernet was mainly applied in LAN in early times. Compared with MAN and WAN, LAN has lower requirements for reliability and stability. As a result, Ethernet was lacking of OAM mechanism, which became a serious obstruction to use Ethernet as operator networks. Therefore, implementing OAM in Ethernet became an inevitable development trend. In this case, a series of standard technologies were generated, such as IEEE 802.3ah (Operations, Administration, and Maintenance - OAM), IEEE 802.1ag (Connectivity Fault Management) and International Telecommunications Union (ITU) - T Y.1731 (OAM functions and mechanisms for Ethernet based networks). IEEE 802.1ag (CFM) provides connectivity detection logically on point-to-point links. It detects the connectivity between two logical points, supporting functions such as loopback, link trace and ITU-T Y1731. CFM can check, isolate, and report connectivity faults in Virtual Local Area Networks (VLANs) effectively. The CFM is the main protocol used for link monitoring, detection, and troubleshooting at the data link layer. It can implement link detection of Ethernet data link layer on most full-duplex point-to-point links and analogical point-to-point links, without depending on specific system interfaces. The CFM mainly has three functions: l
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). 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. 6-1
SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
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 Features The 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 6-1. Figure 6-1 Maintenance Domain
A series of ports are defined for the edge devices and the internal device, see Figure 6-1. l l
The gray points on the edge devices are the services ports connecting to devices outside the domain. These points are defined as MEPs. 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. 6-2 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
Chapter 6 CFM Configuration
IEEE 802.1ag standard defines the following mechanisms: 1. Several nesting MDs configured through a bridge network or a network of a bridge network. The domains may be managed by different management organizations. 2. An Maintenance Association (MA) identified by an individual MD in a specific bridge and a group of VLANs. 3. The protocol, flow, and formats of CFM protocol packets that are used to detect and isolate connectivity faults. 4. Configuration ability to configure and manage Maintenance Points (MPs) in an MA. An MP is used to generate and receive CFM packets. 5. MPs ordered to execute isolation and result inspection for confirmed faults.
6.2 Configuring CFM To configure CFM on the ZXR10 M6000, perform the following steps: Step
Command
Function
1
ZXR10(config)#cfm
Enters CFM configuration mode.
2
ZXR10(config-cfm)#set cfm enable
Enables the CFM function globally.
3
ZXR10(config-cfm)#create md index
Creates an maintenance domain
(MD).
4
ZXR10(config-cfm)#md index < index >
Enters MD configuration mode.
5
ZXR10(config-cfm-md)#create ma index
Creates a maintenance association
(MA)
6
ZXR10(config-cfm-md)#ma index
Enters MA configuration mode.
7
ZXR10(config-cfm-ma)#set ccminterval
Configures the CCM interval for an MA. Range: 1-7. The range corresponds to 3.3 ms, 10 ms, 100 ms, 1 s, 10 s, 60 s, and 600 s.
8
ZXR10(config-cfm-ma)#create mep mep-id <mepid> direction {down
Creates an MEP.
| up} interface
10
ZXR10(config-cfm-ma)#create rmep mepid <mepid > remote-mac
Creates an Remote Maintenance
<mac-address> lmep
association End Point (RMEP).
ZXR10(config-cfm-ma)#create mip session-id <session-id> interface
Creates an MIP.
6-3 SJ-20130205142913-019|2013-02-28 (R2.2)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (Reliability)
Step
Command
Function
11
ZXR10(config-cfm-ma)#set mep <mepid> state {enable|disable}
Enables or disables local management function in an MEP. For an RMEP, it enables or disables CCM detection.
12
ZXR10(config-cfm-ma)#set mep <mepid> ccm-send {enable|disable}
Enables or disables tthe CCM packet sending function in an MEP. It is only effective in the local MEP.
13
ZXR10(config-cfm-ma)#set mep <mepid> alarm-lowest-pri
Configures the lowest fault class that
<priority>
can trigger alarms in an MEP. Range: 1-5, default: 2.
14
ZXR10#cfm loopback md <md-index> ma <ma-index> local-mep
Sends LBMs.
<mepid> type unicast <mac-address>[repeat
Related Documents
Wireless Router Configuration
July 2020 8
Router Configuration Commands
November 2019 15
Basic Router Configuration
November 2019 13
03 Router Configuration
November 2019 7
Cisco Router Configuration Commands
May 2020 10
Cisco Router Configuration Commands
June 2020 8More Documents from "Marco Vignaroli"
Diskusi 1 Adhita S Putri 041211385.docx
November 2019 18
Program Kerja Pas Ganjil.docx
May 2020 12
Tindakan.xlsx
May 2020 11
