Router ZXR10 GAR Manual 1

ZXR10 GAR
General Access Router
Users Manual (Volume I)

Version 2.6
ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: doc@zte.com.cn
LEGAL INFORMATION Copyright 2005 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 noninfringement. 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. The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support or training are subject to change without notice.
Revision History Date 2006/03/0 1 Revision No. R1.0 Serial No. Sjzl20061117 Description
ZTE CORPORATION Values Your Comments & Suggestions!

Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers. Please fax to: (86) 755-26772236; or mail to Publications R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057. Thank you for your cooperation!
Document Name Product Version ZXR10 GAR (V2. 6) General Access Router Users Manual (Volume I) V2.6 Document Number Revision R1.0
Equipment Installation Date Your Presentation: evaluation of (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, this Appearance) documentation Good Fair Average Poor Bad N/A
Accessibility: (Contents, Index, Headings, Numbering, Glossary) Good Fair Average Poor Bad N/A
Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content) Good Fair Average Poor Bad N/A Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Improve the Contents Improve the organization Include more figures Your suggestions for improvement of this documentation Add more examples Add more detail Other suggestions __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ # Please feel free to write any comments on an attached sheet. If you wish to be contacted regarding your comments, please complete the following: Name Postcode Telephone Company Address E-mail Make it more concise/brief Add more step-by-step procedures/tutorials Add more troubleshooting information Make it less technical Add more/better quick reference aids Improve the index
Contents
About this Users Manual
Purpose of this Users Manual Typographical Conventions Mouse Operation Conventions Safety Signs How to Get in Touch
Customer Support Documentation Support
Chapter
1 2
Safety Instructions
Safety Instructions Safety Signs
Chapter
System Overview
Overview Functions Technical Features and Parameters
Chapter
Structure and Principle

Overall Structure and Working Principles Main Board Line Interface Board
RA-1CE1 RA-1CE1-75 RA-1CT1
RA-1E1V1 RA-1E1V1-75 RA-1FE-E100RJ RA-1FE-M02KSC RA-1FE-S15KSC RA-1FE-S40KSC RA-1GE-GBIC-R RA-1P3-M02KSC RA-1P3-S15KSC RA-1P3-S40KSC RA-2CE1 RA-2CE1-75 RA-2CT1 RA-2FE-R RA-2FXS RA-2GE-GBIC-R RA-4AS-U RA-4CE1 RA-4CE1-75 RA-4CT1 RA-4E1VE RA-4FE-R RA-4FXO RA-4FXS RA-4HS RA-4T1VE RA-8CE1 RA-8CE1-R RA-8FE-R RA-8FXS
Chapter
User Interface Configuration

Basic Configuration Modes
Configuration through Serial Interface Connection TELNET Connection Configuration
Command Mode
Exec Mode Privileged Mode Global Configuration Mode
Interface Configuration Mode Route Configuration Mode Diagnosis Mode
Online Help Command History
Chapter
System Management
File System Management
File System Introduction File System Management
FTP/TFTP Configuration
FTP Configuration TFTP Configuration
Backing up and Recovering Data Software Version Upgrading

Version Upgrading upon Abnormal System Version Upgrade Upon Normal System
System Parameter Configuration Check System Information System Recovery
Chapter
Interface Configuration
Interface Types Interface Naming Rules Checking Interface Information
Ethernet Interface Configuration

Configurations of Ethernet Interfaces Examples for Ethernet Interface Configuration
POS Interface Configuration

Configuration of POS Interface Examples for POS Interface Configuration
E1 Interface Configuration
Configuration of E1 Interfaces Examples for E1 Interface Configuration
T1 Interface Configurations
T1 Interface Configuration Examples for E1 Interface Configuration
Synchronous/Asynchronous Serial Interface Configurations

Synchronous/Asynchronous Serial Interface Configurations Examples for Synchronous/Asynchronous Serial Interface Configuration
Voice Interface Configuration

Voice Interface Configuration Examples for Voice Interface Configuration
TDMoIP Interface Configuration

TDMoIP Interface Configuration Examples for TDMoIP Interface Configuration
VLAN Sub-interface Configuration

Configuration of VLAN Sub-Interfaces Examples for VLAN Sub-Interface Configuration
Multilink Configuration
Basic Multilink Configuration Examples for Multilink Configuration
Chapter
PPP
Configuration of Link Protocols

General Description of PPP Basic PPP Configuration Examples for PPP Configuration Examples for MPPP Configuration
FR
General Description Basic FR Configuration Examples for PPP Configuration
X.25
Overview Basic X.25 Configurations Examples for X.25 Protocol Configuration
HDLC
Overview Basic HDLC Configuration Examples for HDLC Configuration
Chapter
Network Protocol Configuration

IP Address Configuration
Overview Basic IP Address Configuration Examples for IP Address Configuration
ARP Configuration
Overview Basic ARP Configuration ARP Maintenance and Diagnosis Examples for ARP Configuration
Chapter
V-Switch Configuration
Overview Basic V_Switch Configuration V-Switch Maintenance and Diagnosis Examples for V-Switch Configuration
Chapter
10
Static Route Configuration

Overview Basic Static Route Configuration Static Route Maintenance and Diagnosis Examples for Static Route Configuration
Static Route Configuration Static Route Summary Configuration Default Route Configuration
Chapter
11
RIP Configuration
Overview
RIP Background Metric and Administrative Distance Timer Route Update
RIP Configuration
Basic configurations
Enhanced Configuration
RIP Maintenance and Diagnosis Examples for RIP Configuration
Chapter
12
OSPF Configuration
Overview
OSPF Background
OSPF Algorithm
OSPF Network Types HELLO Packet and Timer OSPF Neighbors Adjacency and Designated Router DR Router Priority and DR Election OSPF Area LSA Type and Flooding Stub Area and Totally Stubby Area Not-So-Stubby Area OSPF Authentication
Chapter
13
IS-IS Configuration
Overview
IS-IS Background IS-IS Area IS-IS Network Types DIS and Router Priority
IS-IS Configuration
Basic IS-IS Configuration Global IS-IS Parameters Configuration IS-IS Interface Parameters Configuration Configuring IS-IS Authentication
IS-IS Maintenance and Diagnosis Examples for IS-IS Configuration

Single-Area IS-IS Configuration
Chapter
14
BGP Configuration
BGP Overview BGP Configuration

Basic BGP Configuration BGP Route Advertisement BGP Aggregate Advertisement Multihop Configuration in EBGP Filtering Routes by Router Filtering Routes via NLRI Filtering Route via AS_PATH LOCAL_PREF Attribute MED Attribute Community String Attribute BGP Synchronization BGP Router Reflector BGP Confederation BGP Route Dampening
BGP Maintenance and Diagnosis BGP Configuration Example
Chapter
15
Policy Routing Configuration

Policy Routing Overview Policy Routing Configuration Examples for Policy Routing Configuration
Policy Routing Configuration Example 1 Policy Routing Configuration Example 2
Chapter
16
MPLS Configuration
Overview
Operational Principles of MPLS MPLS Label Header MPLS LDP
MPLS Configuration MPLS Maintenance and Diagnosis Examples for MPLS Configuration
Chapter
17
MPLS VPN Configuration

Overview
Related Terms VPN-IPv4 Address and Route Distinguisher (RD) Operational Principles of MPLS VPN
MPLS VPN Configuration MPLS VPN Maintenance and Diagnosis Examples for MPLS VPN Configuration
Chapter
18
VPWS Configuration
Overview VPWS Configuration VPWS Maintenance and Diagnosis Examples for VPWS Configuration
Abbreviations Figures Tables
About this Users Manual

The ZXR10 GAR (V2.6) General Access Router Users Manual (Volume I), is applicable to ZXR10 GAR (V2.6) (hereinafter referred to as ZXR10 GAR). The following manuals are used together with the ZXR10 GAR: ZXR10 GAR (V2.6) General Access Router Installation Manual ZXR10 GAR (V2.6) General Access Router Users Manual (Volume I) ZXR10 GAR (V2.6) General Access Router Users Manual (Volume II) ZXR10 Router/Ethernet Switch Command ManualCommand Index ZXR10 Router/Ethernet Switch Command ManualSystem Management ZXR10 Router/Ethernet Switch Command ManualFunctional System (Volume I) ZXR10 Router/Ethernet Switch Command ManualFunctional System (Volume I)
ZXR10 Router/Ethernet Switch Command ManualFunctional System (Volume II) ZXR10 Router/Ethernet Switch Command ManualFunctional System (Volume III) ZXR10 Router/Ethernet Switch Command ManualProtocol Stack (Volume I) ZXR10 Router/Ethernet Switch Command ManualProtocol Stack (Volume II) ZXR10 Router/Ethernet Switch Command ManualProtocol Stack (Volume III) ZXR10 Router/Ethernet Switch Information Manual
The commands supported by the ZXR10 GAR (V2.6) general access router are based on the unified platform ZXROS V4.6.02 version.
Purpose of this Users Manual

There are all together 18 chapters in this manual. Chapter 1 Safety Instructions describes safety instructions and safety signs. Chapter 2 System Overview gives an overview of the ZXR10 GAR. Chapter 3 Structure and Principle describes the structure and principles of ZXR10 GAR. Chapter 4 User Interface Configuration describes common command modes and usage of command lines of ZXR10 routers. configurations,
Chapter 5 System Management describes system management of ZXR10 GAR. Chapter 6 Interface Configuration details multiple types of interfaces on a ZXR10 GAR router and their configurations. Chapter 7 Configuration of Link Protocols describes configurations of the PPP, FR, X.25 and HDLC link protocols. Chapter 8 Network Protocol Configuration describes configuration of IP addresses, and ARP protocol. Chapter 9 V-Switch Configuration describes configuration of V-Switch. Chapter 10 Static Route Configuration describes configuration of the static route. Chapter 11 RIP Configuration describes configuration of the BGP4+ protocol. Chapter 12 OSPF Configuration describes configuration of the RIP protocol. Chapter 13 IS-IS Configuration describes configuration of the IS-IS protocol. Chapter 14 BGP Configuration describes configuration of the BGP. Chapter 15 Policy Routing Configuration describes configuration of the BGP policy.
Chapter 16 MPLS Configuration describes configuration of the DHCP protocol. Chapter 17 MPLS VPN Configuration describes configuration of the MPLS technology. Chapter 18 VPWS Configuration describes configuration of the VPWS.
Typographical Conventions
ZTE documents employ with the following typographical conventions.
T A B L E 1 T Y P O G R A P H I C AL C O N V E N T I O N S
Typeface
Meaning References to other guides and documents. Links on screens. Menus, menu options, function names, input fields, radio button names, check boxes, drop-down lists, dialog box names, window names. Keys on the keyboard and buttons on screens and company name. Text that you type, program code, files and directory names, and function names. Optional parameters Mandatory parameters Select one of the parameters that are delimited by it Note: Provides additional information about a certain topic. Checkpoint: Indicates that a particular step needs to be checked before proceeding further. Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.
Italics
Quotes Bold
CAPS Constant width [] {} |
Mouse Operation Conventions

T A B L E 2 M O U S E O P E R AT I O N C O N V E N T I O N S
Typeface Click Double-click Right-click Drag
Meaning Refers to clicking the primary mouse button (usually the left mouse button) once. Refers to quickly clicking the primary mouse button (usually the left mouse button) twice. Refers to clicking the secondary mouse button (usually the right mouse button) once. Refers to pressing and holding a mouse button and moving the mouse.
Safety Signs
TABLE 3 SAFET Y SIGNS
Safety Signs
Meaning Danger: Indicates an imminently hazardous situation, which if not avoided, will result in death or serious injury. This signal word should be limited to only extreme situations. Warning: Indicates a potentially hazardous situation, which if not avoided, could result in death or serious injury. Caution: Indicates a potentially hazardous situation, which if not avoided, could result in minor or moderate injury. It may also be used to alert against unsafe practices.
Erosion: Beware of erosion.
Electric shock: There is a risk of electric shock. Electrostatic: The device may be sensitive to static electricity.
Microwave: Beware of strong electromagnetic field. Laser: Beware of strong laser beam.
No flammables: No flammables can be stored.
No touching: Do not touch.
No smoking: Smoking is forbidden.
How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software.
Customer Support
If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at support@zte.com.cn. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830.
Documentation Support
ZTE welcomes your comments and suggestions on the quality and usefulness of this document. For further questions, comments, or suggestions on the documentation, you can contact us by e-mail at doc@zte.com.cn; or you can fax your comments and suggestions to (86) 755 26772236. You can also explore our website at http://support.zte.com.cn, which contains various interesting subjects like documentation, knowledge base, forum and service request.
Chapter
Safety Instructions
This chapter describes safety instructions and safety signs.
Safety Instructions
This equipment involves high temperature and high voltages and can only be installed, operated and maintained by the qualified professionals. The installation, operation and maintenance of this equipment must comply with local safety specifications and related operating procedures to reduce the risk of personal injury or equipment damage. Safety instructions described in this manual are only supplementary to the local safety specifications. ZTE shall not bear any liabilities incurred by violation of the universal safety operation requirements or violation of the safety standards for designing, manufacturing and using the equipment.
Safety Signs
The safety reminder falls into three severity levels: Danger, Warning, and Caution. The statement for a severity level is on the right of the sign. The detailed safety instructions are given below the sign, as shown below.
Note: Provides additional information about a certain topic.
Chapter
System Overview
In this chapter, you will learn about an overview of the ZXR10 GAR general access router and specific description of functions of the software and hardware provided by the ZXR10 GAR.
Overview
With the explosive growth of the Internet, IP services on the Internet is no more restricted to pure data services, multiple value-added services, such as voice and video services, are also in rapid development. This has brought higher requirements on the traditional routers. The carriers no longer seek just higher line interface rate for the router and bigger data processing capability to keep in step with the growth of broadband services, and routers are required to be able to act as the expansible infrastructure for running value-added services over the Internet so as to satisfy the carriers practical requirements for continuously launching new network services to get business operation profits. For all these requirements, routers should be operable, manageable, customizable and expansible. On the basis of rich experience in R&D and manufacturing of the carrier-class communication products, ZTE has designed and manufactured ZXR10 GAR. The router, in modular structure, can provide multiple types of service interfaces. It combines the high-speed network processing technology with the effective software technology, which realizes the rapid routing policy. As the basic ISP platform providing integrated services, it is the preferred product for building up networks such as convergence, access and enterprise networks. Facing the access layer of enterprise and carrier networks, the ZXR10 GAR separates the main processor baseboard, processor sub-card and line interface module completely for realizing the real modular structure to satisfy various customer requirements. It can be configured to routers of different models according to performance of the processor sub-card, chassis structure and power supply, as shown in Table 4.
TABLE 4 ZXR10 GAR MODELS
Model RA-G2604-AC RA-G2604-DC RA-G2608-AC RA-G2608-DC RA-G3608-AC RA-G3608-DC RA-G7208-AC RA-G7208-DC
Chassis Structure 1U 1U 2U 2U 2U 2U 2U 2U
Power Supply AC DC AC/2AC DC/2DC AC/2AC DC/2DC AC/2AC DC/2DC
Using original hardware devices, customers can replace a processor sub-card to upgrade from RA-G2608-XX to RA-G3608-X/RA-G7208-XX and from RA-G3608-XX to RA-G7208-XX, where XX indicating AC or DC. In this case, customers can obtain more performance and capability as assuring performance expansion and original investment protection. The 2U chassis of ZXR10 GAR supports double power supplies and provides 2DC/2ACaccessing mode as required. These double power supplies can provide the power backup function and working mode switch of power modules according to changes of accessing environment of power supplies. In this way, the ZXR10 GAR can keep and extend high availability of the system to the max. Front panel of ZXR10 GAR (RA-G2604) is shown in Figure 1.
F I G U R E 1 F R O N T P A N E L O F Z X R 1 0 G A R ( R A- G 2 6 0 4 )
Rear panel of ZXR10 GAR (RA-G2604) is shown in Figure 2.
AC Power
F I G U R E 2 R E A R P A N E L O F Z X R 1 0 G A R ( R A- G 2 6 0 4 )
DC Power
Front panel of ZXR10 GAR (RA-G2608/ RA-G3608/ RA-G7208) is shown in Figure 3

F I G U R E 3 F R O N T P A N E L O F Z X R 1 0 G A R ( R A- G 2 6 0 8 / R A- G 3 6 0 8 / R A- G 7 2 0 8 )
Rear panel of ZXR10 GAR (RA-G2608/ RA-G3608/ RA-G7208) is shown in Figure 4.
AC Power
2AC Power
F I G U R E 4 R E A R P A N E L O F Z X R 1 0 G A R ( R A- G 2 6 0 8 / R A- G 3 6 0 8 / R A- G 7 2 0 8 )
DC Power
2DC Power
Functions
There are 8 interface module slots on a 2U chassis and 4 on a 1U chassis. With various types of interfaces, the ZXR10 GAR supports the following interface boards: 1. 2. 3. 4. 5. 6. 7. 8. 9. 2/1-ports GBIC gigabit interface board 1-port POS3 interface board 8/4/2-ports fast Ethernet interface board 1-port fast Ethernet electrical interface board 1-port fast Ethernet optical interface board 8/4/2/1-ports channelized E1 interface board 8-ports channelized LCE1H interface board 4-ports channelized E1 unbalanced coaxial interface board 4-ports synchronous/asynchronous serial interface board
10. 4-ports high-speed synchronous/asynchronous serial interface board 11. 8/4/2-ports Z interface voice interface board 12. 4-ports loop trunk voice interface board 13. 1-port E1 voice interface board (LE1VI) 14. 4-ports E1 VE interface board 15. 4-ports T1 VE interface board With respect to software, a network operation system (ROS) platform, of which the self-proprietary property rights are completely owned by ZTE, is used for ZXR10 GAR. ZXR10 GAR has powerful protocol support functions, supporting the following network protocols and standards: 1. 2. 3. 4. 5. 6. 7. 8. 9. Link layer protocols: PPP, ML-PPP, FrameRelay, HDLC, 802. 1Q and X.25 Network layer protocols: IP, ICMP, ARP and V-SWITCH Transport layer protocols: TCP and UDP Routing protocols: RIP v1/v2, OSPF v2, IS-IS and BGP4 Multicast protocols: IGMP and PIM-SM Supporting three layers MPLS/VPN and two layers VPWS Tunnel protocol: GRE Application layer protocols: Telnet, FTP, TFTP, H. 323 and LFAP Network layer control application: NAT, ACL, URPF, PBR and LOADBALANCE
10. Network management protocols: SNMP v1/v2/v3, RMON v1 and NTP 11. Supporting MPLS-TE 12. Supporting IPV6 basic protocols 13. Supporting IPV6 unicast routing protocols 14. 1Supporting IPV6 NAT-PT 15. Supporting 6 IN 4 and 4 IN 6 tunnel protocols
Technical Features and Parameters

ZXR10 GAR complies with the following standards: Q/SZX 122-2002 ZXR10 middle/low-end routers Detailed system features of ZXR10 GAR routers of different models are listed in Table 5
T A B L E 5 Z X R 1 0 G A R S Y S T E M F E AT U R E S
Item Processor specification SDRAM configuration FLASH configuration BOOT ROM Bus bandwidth Packet processing capability Number routings
RA-G2604-AC (DC)
RA-G2608-AC (DC)
RA-G3608-AC (DC)
RA-G7208-AC (DC) network
250MHz processor 250MHz processor300MHz processor Dedicated processor 128M 32M 512K 1Gbps 30Kpps 128M 32M 512K 1Gbps 30Kpps 256M 64M 512K 2Gbps 50Kpps 256M 64M 1MB 4. 4Gbps 600Kpps
of 16K
16K 8
32K
64K
Number of 4 available slots Basic interface configuration (mm) Dimensions (mm) (WDH) Power supply Ambient temperature Environment humidity 1AUX, 1CON, 1FE
44240049
44240088
220VAC, 50Hz (-48VDC) 0~40 20% ~ 90% (non-condensing)
Chapter
Structure and Principle

This chapter describes the structure and principles of ZXR10 GAR and details individual modules in the system.
Overall Structure and Working Principles

Based on the modular design of the dedicated network processors, ZXR10 GAR can satisfy vary application requirements by carrying out various hardware module configuration combinations. With respect to the structure, it realizes modulization of interfaces a well as of the CPU processing sub-system. It also supports a span of the interface rate from low rate of 1200b/s to high rate of 1000Mb/s to satisfy customer requirements of various bandwidths. The system structure diagram of ZXR10 GAR is shown in Figure 5.
F I G U R E 5 Z X R 1 0 G AR S Y S T E M S T R U C T U R E D I AG R AM
The hardware of ZXR10 GAR General Access router consists of four parts: Power supply module, CPU sub-system module, bottom plate and back plane module, and line interface module. 1. Power supply module
The ZXR10 GAR adopts the 220V AC or 48V DC power supply. The power supply module supplies power for other modules of the system in the mode of +3. 3V, +5. 0V and +12V DC. 2. CPU sub-system module As the core part of ZXR10 GAR, the CPU sub-system module has two main functions: 1. Processes the routing packets and converges network routings.2. Processes IP packets that are resolved from the link layer, implements address filtration and routing searching for IP packet heads, cooperates with the switching fabric for IP packet head editing, packet buffer and queue scheduling management, and sends out the IP packets that are enveloped in proper link layer frames under the sending direction. It adopts the modular design with the network processor as its core and auxiliary interface chip as its expanding part. Therefore, CPU chips of different models and specifications can be flexibly replaced to satisfy vary requirements of system performance. 3. Bottom plate and back plane module The bottom plate and back plane module provides data channel to the CPU subsystem module and interface module. 4. Line interface module The line interface module is the external interface of ZXR10 GAR. Its interface subunit is connected with the high-speed network processing main board via standard industrial bus. It provides the following functions: In the receiving direction, it exchanges the physical line signals to the data frames of the link layer, envelops the data packets transmitted from the CPU sub-system module to the data frames and then sends them via corresponding destination ports. This module provides one or more physical ports, so different modules can satisfy access of interface services of various rates and models. Internal structure of ZXR10 GAR router is shown in Figure 6.
F I G U R E 6 Z X R 1 0 G E R I N T E R N A L S T R U C T U R E D I AG R A M
As shown in Figure 6., hardware of ZXR10 GAR consists of main board, sub-board, power supply, fans and interface boards. Physically adopting the standard 19-inch case, the ZXR10 GAR can be either installed exteriorly or fixed in standard cabinets.
Main Board
As the core part of ZXR10 GAR, a main board is installed in the chassis, so users cannot see it. Its interfaces and indicator lights can be seen in the front panel, as shown in Figure 7 and Figure 8.
F I G U R E 7 M A I N B O A R D I N T E R F AC E S AN D I N D I C AT O R L I G H T S O F Z X R 1 0 G AR ( R A - G 2 6 0 4 )
F I G U R E 8 M A I N B O A R D I N T E R F AC E S AN D I N D I C A T O R L I G H T S O F Z X R 1 0 G AR ( R A - G 2 6 0 8 / RA- G3608/ RA- G7208)
1.
Interfaces
There are three management interfaces on the front panel of ZXR10 GAR: CONSOLE port, AUX port and 10/100Base-TX port. Of them, the AUX port is reserved for higher versions and cannot be supported in V1. 0. ONSOLE port The CONSOLE port is used for connecting the background administration terminal where operations and maintenance of ZXR10 GAR can be implemented by means of tools such as HyperTerminal. It is a RS232 DB9 male serial interface, which is connected with the COM port of the background administration terminal via serial cables. At the two ends of the connection cable are DB9 female connectors, and the cable sequence is shown in Table 6.
TABLE 6 SEQUENCE OF CONSOLE CABLE
BIC Board DB9 1 2 3 4 5 6 7 8 9
Signal Not used GAR_RX GAR_TX GAR_DTR GAR_GND GAR_DSR GAR_RTS GAR_CTS Not used
DB9 of Background Computer
Signal
3 2 6 5 4 8 7
PC_TX PC_RX PC_DSR PC_GND PC_DTR PC_RTS PC_CTS
AUX port A MODEM can be connected at an AUX port to implement functions such as longdistance access to routers and management configuration, same as functions implemented at the local access terminal. They are connected via an AUX cable to configure ZXR10 GAR in the mode of longdistance access. At the two ends of the connection cable are 9-pins serial DB9 female connector and 9-pins serial DB9 male connector or 25-pin serial DB25 male connector, and the cable sequence is shown in Table 7.
T A B L E 7 S E Q U E N C E O F AU X C AB L E
BIC Board DB9 1 2 3 4 5
Signal GAR_DCD GAR_RX GAR_TX GAR_DTR GAR_GND
DB9 of Background Computer 8 3 2 20 7
Signal MODEM_DCD MODEM_RX MODEM_TX MODEM_DTR MODEM_GND
BIC Board DB9
Signal
DB9 of Background Computer
Signal
6 7 8 9
GAR_DSR GAR_RTS GAR_CTS GAR_RI
6 5 4 22
MODEM_DSR MODEM_RTS MODEM_CTS MODEM_RI
10/100Base-TX Ethernet port The 10/100Base-TX Ethernet management port can either be used for out-band NM of the router, or work as common service ports. It has the function of routing transmission same as the fast Ethernet port on the link interface module. Features of this kind of port are listed in Table 8.
T A B L E 8 F E A T U R E S O F F AS T E T H E R N E T M AN AG E M E N T P O R T
Port Type
Specifications In compliance with IEEE 802. 3 RJ45 connector Using category-3, 4 and 5 Unshielded Twisted Pairs (UTP) Maximum transmission distance: 100 m In compliance with IEEE 802. 3u RJ45 connector Using category-5 Unshielded Twisted Pairs (UTP) Maximum transmission distance: 100 m
10Base-T
100Base-TX
Note: When the interface is connected with a host, a straight-through network cable is used; when it is connected with a hub, switch or router, a crossover cable is used.
2.
Indicators There are four indicators on the panel, and their individual functions are listed in Table 9.
T A B L E 9 F U N C T I O N D E S C R I P T I O N O F I N D I C AT O R S O N T H E F R O N T P AN E L O F T H E G AR
Indicator PWR (green) RUN (green) ALM (red) FAN
Functions indicator Power indicator. When it is on, it indicates that the equipment has been powered on and the power supply is in normal condition indicator Running indicator. When it is on, it indicates that the equipment runs normally. It flashes after the system is normally started indicator Alarm indicator: When it is on, it indicates a system fault
indicator Fan indicator: When it is on, it indicates that the fan is working normally
Indicator (green)
Functions
Line Interface Board

Line interface boards in ZXR10 GAR are detailed in Table 10.
T A B L E 1 0 D E S C R I P T I O N S O F Z X R 1 0 G A R L I N E I N T E R F AC E B O AR D S O F V A R I O U S M O D E L S
Line Interface Board Type
Board Model RA-1FE-E100RJ RA-1FE-M02KSC RA-1FE-S15KSC
Functions 1-port fast Ethernet electrical interface board 1-port 100Base-FX optical interface board (2kilometers multimode) 1-port 100Base-FX optical interface board (15-kilometers single-mode) 1-port 100Base-FX optical interface board (40-kilometers single-mode) 2-ports fast Ethernet electrical interface board 4-ports fast Ethernet electrical interface board 8-ports fast Ethernet electrical interface board 1-port Gigabit Ethernet optical interface board 2-ports Gigabit Ethernet optical interface board 1-port POS3 optical interface board (2kilometers multimode) 1-port POS3 optical interface board (15kilometers single-mode) 1-port POS3 optical interface board (40kilometers single-mode) 1-port channelized 120 ohm E1 interface board 2-ports channelized 120 ohm E1 interface board 4-ports channelized 120 ohm E1 interface board 8-ports channelized 120 ohm E1 interface board 1-port channelized 75 ohm E1 unbalanced micro coaxial interface board 2-ports channelized 75 ohm E1 unbalanced micro coaxial interface board
Fast Ethernet board
interface RA-1FE-S40KSC RA-2FE-R RA-4FE-R RA-8FE-R
Gigabit Ethernet interface board
RA-1GE-GBIC-R RA-2GE-GBIC-R RA-1P3-M02KSC
POS optical interface board
RA-1P3-S15KSC RA-1P3-S40KSC
Channelized E1 interface RA-1CE1 board RA-2CE1 RA-4CE1 RA-8CE1 RA-1CE1-75 RA-2CE1-75
Line Interface Board Type
Board Model
Functions 4-ports channelized 75 ohm E1 unbalanced micro coaxial interface board 1r-port channelized T1 interface board 2-ports channelized T1 interface board 4-ports channelized T1 interface board 2-ports Z interface voice interface board 4-ports Z interface voice interface board 4-ports Z interface voice interface board 1-port 120 ohm E1 voice interface board 1-port 75 ohm E1 voice interface board 8-ports channelized LCE1H interface board 4-ports synchronous/asynchronous interface board 4-ports high-speed serial interface board 4-ports loop trunk voice interface board 4-ports E1VE interface board 4-ports T1VE interface board serial
RA-4CE1-75 RA-1CT1 Channelized T1 interface board RA-2CT1 RA-4CT1 RA-2FXS Z interface voice interface board RA-4FXS RA-8FXS E1 voice interface board LCE1H interface board RA-1E1V1 RA-1E1V1-75 RA-8CE1-R
Synchronous/asynchronous RA-4AS-U serial interface board High-speed serial interface RA-4HS board Loop trunk voice interface RA-4FXO board E1VE interface board T1VE interface board RA-4E1VE RA-4T1VE
The line interface board of ZXR10 GAR provides multiple types of port connectors that can be used for different transmission medium and distance. Detailed descriptions about these boards are given in the sequence of letters.
RA-1CE1
The RA-1CE1, 1-port channelized 120 ohm E1 interface board of ZXR10 GAR, provides an E1 interface in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements functions such as data receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines. 1. Panel Panel of the RA-1CE1 board is shown in Figure 9.
F I G U R E 9 R A - 1 C E 1 B O A R D P AN E L
2.
Interfaces Features of interfaces on the RA-1CE1 board are shown in Table 11.
T A B L E 1 1 F E AT U R E S O F I N T E R F A C E S O N R A- 1 C E 1 B O AR D
Port Type
Specifications In compliance with ITU-T G. 703 and G. 704 Recommendations Supporting G. 704 framing
Channelized E1
RJ48 connector and 120 ohm twisted pair Line code of HDB3 A channelized E1 controller has 31 valid timeslots
3.
Indicators There are two indicators on the top of interfaces on RA-1CE1 board. Their functions are listed in Table 12.
T A B L E 1 2 D E S C R I P T I O N O F I N D I C AT O R S O N T H E R A- 1 C E 1 B O A R D
Indicator Left indicator (Yellow) Right indicator (green)
Functions Alarm indicator: On indicates port/line fault Line status indicator: On indicates the line and line signals are normal
4.
Interconnection Table 13 shows the interconnection method of RJ48 connectors at E1 port.
TABLE 13 INTERCONNECTION OF RJ48 CONNECTORS AT E1 PORT
RJ48 of GAR CE1 Board 1 2 3 4 5 6 7 8
Signal RX_RING RX_TIP Not connected TX_RING TX_TIP Not connected Not connected Not connected
E1 RJ48 Connector of Mating Device 4 5 3 1 2 6 7 8
Signal TX_RING TX_TIP Not connected RX_RING RX_TIP Not connected Not connected Not connected
As shown in Table 13, when two routers are connected via E1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. The connection method is shown in Figure 10.
FIGURE 10 INTERCONNECTION VIA E1 RJ48 CONNECTORS
In the case of interconnection of E1 RJ48 connector with E1 BNC connector, a connector converter is needed to convert RJ48 to BNC connector. The E1 RJ48 connector is connected with the RJ48/BNC converter via an E1 crossover cable and the E1 BNC connector connected with the converter via a coaxial cable. The connection mode is shown in Figure 11.
FIGURE 11 CONNECTION OF E1 RJ48 CONNECTOR WITH E1 BNC CONNECTOR
RA-1CE1-75
The RA-1CE1-75 (1-port channelized 75 ohm E1 unbalanced micro coaxial interface board) provides an E1 interface in compliance with ITU-T G.703 and G.704 Recommendations. Each port supports the sending and receiving functions. The receiving end implements functions such as data receiving and framing, and the sending end is to send the data to lines. 1. Panel Panel of the RA-1CE1-75 board is shown in Figure 12.
F I G U R E 1 2 R A- 1 C E 1 - 7 5 B O A R D P AN E L
2.
Interfaces Features of interfaces on the RA-1CE1-75 board are shown in Table 14.
T A B L E 1 4 F E AT U R E S O F I N T E R F A C E S O N R A- 1 C E 1 - 7 5 B O A R D
Port Type
E1Channelized E1
75 ohm micro coaxial (CC4) connector Line code of HDB3 A channelized E1 controller has 31 valid timeslots
3.
Indicators There are two indicators on the top of interfaces on RA-1CE1-75 board. Their functions are listed in Table 15.
T A B L E 1 5 F U N C T I O N S D E S C R I P T I O N S O F C H AN N E L I Z E D R A- 1 C E 1 - 7 5 B O AR D I N D I C A T O R S
Indicator RUN indicator LINE indicator
Functions Running indicator. Green indicator indicates normal running of the port Line indicator: Indicates that the physical line is connected well when it is on
RA-1CT1
The RA-1CT1 (1-port channelized T1 interface board) provides a T1 interface in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements the function of data receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines. 1. Panel Panel of the RA-1CT1 board is shown in Figure 13.
F I G U R E 1 3 R A- 1 C T 1 B O A R D P AN E L
2.
Interfaces Features of interfaces on the RA-1CT1 board are shown in Table 16.
T A B L E 1 6 F E AT U R E S O F I N T E R F A C E S O N T H E R A - 1 C T 1 B O AR D
Port Type
Specifications
In compliance with ITU-T G. 703 and G. 704 Recommendations Supporting G. 704 framing Channelized T1 RJ48 connector and 100 ohm twisted pair Line code of B8ZS/AMI A channelized E1 controller has 24 valid timeslots
3.
Indicators There are two indicators on the top of interfaces on RA-1CT1 board. Their functions are listed in Table 17.
T A B L E 1 7 D E S C R I P T I O N O F I N D I C AT O R S O N T H E R A- 1 C T 1 B O AR D
Indicator Left indicator (Yellow) Right indicator (green)
Functions Alarm indicator: On indicates port/line fault Line indicator: Indicates that the line and line signals are in normal condition when it is on
4.
Interconnection Table 18 shows the interconnection method of RJ48 connectors at T1 port.
TABLE 18 INTERCONNECTION OF RJ48 CONNECTORS AT T1 PORT
RJ48 of GAR CE1 Board 1 2 3 4 5 6 7 8
E1 RJ48 Connector of Mating Device 4 5 3 1 2 6 7 8
Signal TX_RING TX_TIP Not connected RX_RING RX_TIP Not connected Not connected Not connected
As shown in Table 18, when two routers are connected via T1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. The connection method is shown in Figure 14.
F I G U R E 1 4 C AB L E C O N N E C T I O N A T T 1 P O R T
RA-1E1V1
The RA-1E1V1 (1-port 120 ohm E1 voice interface board) provides the 120 ohm interface mode, implements VoIP function on the E1 line, and processes 30-routes voice signals. 1. Panel The panel of the RA-1E1V1 board is shown in Figure 15.
F I G U R E 1 5 R A- 1 E 1 V 1 B O AR D P A N E L
2.
Interfaces Features of interfaces on the RA-1E1V1 board are shown in Table 19
T A B L E 1 9 F E AT U R E S O F I N T E R F A C E S O N T H E R A - 1 E 1 V 1 B O AR D
Port Type
Specifications One RJ45 connector Supporting R2 signaling (similar as Chinese No.1 signaling)
E1 interfaces
Supporting voice coding modes such as G.722 A-law, G.711 u-law, G.723.1, G.723.1A, G.729 A and G.729 B Supporting H. 323
3.
Indicators There are two indicators on the top of interfaces on RA-1E1V1 board. Their functions are listed in Table 20.
T A B L E 2 0 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 E 1 V 1 B O AR D
Indicator
Functions
Yellow indicator with the Link indicator RJ45 socket
Green indicator with the Channel occupation indicator RJ45 socket
RA-1E1V1-75
The RA-1E1V1-75 (1-port 75 ohm E1 voice interface board) provides the 75 ohm interface mode, implements VoIP function on the E1 line, and processes 30-routes of voice signals. 1. Panel The panel of the RA-1E1V1-75 board is shown in Figure 16.
F I G U R E 1 6 R A- 1 E 1 V 1 - 7 5 B O A R D P AN E L
2.
Interfaces Features of interfaces on RA-1E1V1-75 are listed in Table 21.
T A B L E 2 1 F E AT U R E S O F I N T E R F A C E S O N R A- 1 E 1 V 1 - 7 5 B O A R D
Port Type
Specifications 2 CC4 connectors Supporting R2 signaling (similar as Chinese No.1 signaling)
E1E1 interfaces
Supporting voice-coding modes such as G. 711 A-law, G. 711 ulaw, G. 723. 1, G. 723. 1 A, G. 729 A and G. 729 B Supporting H. 323
3.
Indicators There are two indicators on the top of interfaces on RA-1E1V1-75 board. Their functions are listed in Table 22.
T A B L E 2 2 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 E 1 V 1 - 7 5 B O AR D
Indicator RUN LINE
Functions Link indicator Channel occupation indicator
RA-1FE-E100RJ
RA-1FE-E100RJ (1-port fast Ethernet electrical interface board) provides a routing of fast Ethernet uplink interface module and downlink user module. 1. Panel Panel of RA-1FE-E100RJ is shown in Figure 17.
F I G U R E 1 7 P AN E L O F R A- 1 F E - E 1 0 0 R J
2.
Interfaces Features of interfaces on RA-1FE-E100RJ are shown in Table 23.
T A B L E 2 3 F E AT U R E S O F I N T E R F A C E S O N R A- 1 F E - E 1 0 0 R J
Port Type
10Base-T
100Base-TX
Note: When the10Base-T/100Base-TX port is interconnected with a hub, switch or router, a crossover cable should be used; when it is interconnected with a host, a straight-through cable should be used.
3.
Indicators There are two indicators on the top of interfaces on RA-1FE-E100RJ board. Their functions are listed in Table 24.
T A B L E 2 4 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 F E - E 1 0 0 R J B O A R D
Functions Run indicator: Green indicator indicates normal running of the port and flashing indicates data being received/sent Line indicator: Indicates normal line connection when it is on
RA-1FE-M02KSC
RA-1FE-M02KSC (1-port 100Base-FX optical interface board) provides a routing of fast Ethernet uplink interface module and downlink user module. It is based on the circuit design same as that of RA-1FE-E100RJ, but the line interface part differs. 1. Panel Panel of RA-1FE-M02KSC is shown in Figure 18.
F I G U R E 1 8 P AN E L O F R A- 1 F E - M 0 2 K S C
2.
Interfaces Features of interfaces on RA-1FE-M02KSC is shown in Table 25.
T A B L E 2 5 F E AT U R E S O F I N T E R F A C E S O N R A- 1 F E - M 0 2 K S C
Port Type 100Base-FX (MMF 2K)
Specifications In compliance with IEEE 802. 3u SC connector, multimode fiber, with the wavelength of 1310nm and the maximum transmission distance of 2 km
3.
Indicators There are two indicators on the top of interfaces on RA-1FE-M02KSC board. Their functions are listed in Table 26.
T A B L E 2 6 I N D I C A T O R D E S C R I P T I O N S O F R A- 1 F E - M 0 2 K S C
RA-1FE-S15KSC
RA-1FE-M02KSC (1-port 100Base-FX optical interface board) provides a routing of fast Ethernet uplink interface module and downlink user module. It is based on the circuit design same as that of RA-1FE-E100RJ, but the line interface part differs. 1. Panel Panel of RA-1FE-S15KSC is shown in Figure 19.
F I G U R E 1 9 P AN E L O F R A- 1 F E - S 1 5 K S C
2.
Interfaces Features of interfaces on RA-1FE-S15KSC are shown in Table 27.
T A B L E 2 7 F E AT U R E S O F I N T E R F A C E S O N R A- 1 F E - S 1 5 K S C
Port Type 100Base-FX (SMF 15K)
Specifications In compliance with IEEE 802. 3u SC connector, single-mode fiber, with the wavelength of 1310nm and the maximum transmission distance of 15 km
3.
Indicators There are two indicators on the top of interfaces on RA-1FE-S15KSC board. Their functions are listed in Table 28.
T A B L E 2 8 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 F E - S 1 5 K S C B O A R D
RA-1FE-S40KSC
RA-1FE-S40KSC (1-port 100Base-FX optical interface board) provides a routing of fast Ethernet uplink interface module and downlink user module. It is based on the circuit design same as that of RA-1FE-E100RJ, but the line interface part differs. 1. Panel Panel of RA-1FE-S40KSC is shown in Figure 20.
F I G U R E 2 0 P AN E L O F R A- 1 F E - S 4 0 K S C
2.
Interfaces Features of interfaces on RA-1FE-S40KSC are shown in Table 29.
T A B L E 2 9 F E AT U R E S O F I N T E R F A C E S O N R A- 1 F E - S 4 0 K S C B O AR D
Port Type 100Base-FX (SMF 40K)
Specifications In compliance with IEEE 802. 3u SC connector, single-mode fiber, with the wavelength of 1310nm and the maximum transmission distance of 40 km
3.
Indicators There are two indicators on the top of interfaces on RA-1FE-S40KSC board. Their functions are listed in Table 30.
T A B L E 3 0 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 F E - S 4 0 K S C B O A R D
RA-1GE-GBIC-R
Same as the 2-ports Gigabit Ethernet optical interface board, RA-1GE-GBIC-R (1-port Gigabit Ethernet optical interface board) provides gigabit uplink interface module and downlink user module. It can provide a routing of gigabit optical interfaces by configuring GBIC components of different specifications. 1. Panel Panel of RA-1GE-GBIC-R is shown in Figure 21.
F I G U R E 2 1 R A- 1 G E - G B I C - R B O AR D P A N E L
2.
Interfaces Panel of RA-1GE-GBIC-R is shown in Table 31.
T A B L E 3 1 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 G E - G B I C - R B O AR D
Port Type SX (GBIC-M500)
Specifications SC connector, multi-mode fiber, with the wavelength of 850nm and the maximum transmission distance of 500 m
LX (GBIC-S10K) LH (GBIC-S70K)
SC connector, single-mode fiber, with the wavelength of 1310nm and the maximum transmission distance of 10 km SC connector, single-mode fiber, with the wavelength of 1550nm and the maximum transmission distance of 70 km
3.
Indicators There are two indicators on the top of interfaces on RA-1GE-GBIC-R board. Their functions are listed in Table 32.
Functions Run indicator: Green indicator indicates normal running of the port and flashing indicates data being received/sent Line indicator: On indicates the physical line is normal
Note: RA-2GE-GBIC-R can only be adopted in ZXR10 GAR routers with the specification of RA-G7208-XX, avoiding routers of RA-G2608-XX, RA-G2604-XX and RA-G3608-XX.
RA-1P3-M02KSC
RA-1P3-M02KSC (1-port POS3 optical interface board) provides POS 155M uplink interface module and downlink user module. 1. Panel Panel of RA-1P3-M02KSC board is shown in the Figure 22.
F I G U R E 2 2 P AN E L O F R A- 1 P 3 - M 0 2 K S C
2.
Interfaces Features of interfaces on RA-1P3-M02KSC are shown in Table 33.
T A B L E 3 3 F E AT U R E S O F I N T E R F A C E S O N R A- 1 P 3 - M 0 2 K S C B O AR D
Port Type MMF (2K)
Specifications SC connector, multi-mode fiber, with the wavelength of 1310nm and the
maximum transmission distance of 2 km
3.
Indicators There are two indicators on the top of interfaces on RA-1P3-M02KSC board. Their functions are listed in Table 34.
T A B L E 3 4 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 P 3 - M 0 2 K S C B O A R D
RA-1P3-S15KSC
RA-1P3-S15KSC (1-port POS3 optical interface board) provides POS 155M uplink interface module and downlink user module. 1. Panel Panel of v is shown in Figure 23.
F I G U R E 2 3 P AN E L O F R A- 1 P 3 - S 1 5 K S C
2.
Interfaces Features of interfaces on RA-1P3-S15KSC are shown in Table 35.
T A B L E 3 5 F E AT U R E S O F I N T E R F A C E S O N R A- 1 P 3 - S 1 5 K S C B O AR D
Port Type SMF (15K)
Specifications SC connector, single-mode fiber, with the wavelength of 1310nm and the maximum transmission distance of 15 km
3.
Indicators There are two indicators on the top of interfaces on RA-1P3-M02KSC board. Their functions are listed in Table 36.
T A B L E 3 6 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 P 3 - S 1 5 K S C B O AR D
Indicator
Functions
RUN indicator LINE indicator
Run indicator: Green indicator indicates normal running of the port and flashing indicates data being received/sent Line indicator: On indicates the physical line is normal
RA-1P3-S40KSC
RA-1P3-S40KSC (1-port POS3 optical interface board) provides POS 155M uplink interface module and downlink user module. 1. Panel Panel of RA-1P3-S40KSC is shown in Figure 24.
F I G U R E 2 4 P AN E L O F R A- 1 P 3 - S 4 0 K S C B O A R D
2.
Interfaces Features of interfaces on RA-1P3-S40KSC are shown in Table 37.
T A B L E 3 7 F E AT U R E S O F I N T E R F A C E S O N R A- 1 P 3 - S 4 0 K S C B O AR D
Port Type SMF (40K)
Specifications SC connector, single-mode fiber, with the wavelength of 1310nm and the maximum transmission distance of 40 km
3.
Indicators There are two indicators on the top of interfaces on RA-1P3-S40KSC board. Their functions are listed in Table 38.
T A B L E 3 8 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 1 P 3 - S 4 0 K S C B O AR D
RA-2CE1
The RA-2CE1 (2-port channelized 120 ohm E1 interface board) provides two E1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port
supports the sending and receiving functions. The receiving end implements the function of data receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines. 1. Panel Panel of RA-2CE1 board is shown in Figure 25.
F I G U R E 2 5 R A- 2 C E 1 B O AR D P A N E L
2.
Interfaces Features of interfaces on RA-2CE1 board are shown in Table 39.
Port Type
Channelized E1
3.
Indicators There are two indicators on each interface of RA-2CE1 board. Their functions are listed in Table 40.
T A B L E 4 0 O F T H E D E S C R I P T I O N O F I N D I C A T O R S O N R A- 2 C E 1 B O AR D
Indicator
Functions
Upper left indicator on Alarm indicator: On indicates port/line fault each port (yellow) Upper right indicator on Line indicator: On indicates the line and line signals are normal each port (green)
4.
Interconnection Table 41 shows the interconnection method of RJ48 connectors at E1 port.
TABLE 41 INTERCONNECTION OF RJ48 CONNECTORS AT E1 PORT.
RJ48 of GAR CE1
Signal
E1 RJ48 Connector of
Signal
Board 1 2 3 4 5 6 7 8 RX_RING RX_TIP Not connected TX_RING TX_TIP Not connected Not connected Not connected
Mating Device 4 5 3 1 2 6 7 8 TX_RING TX_TIP Not connected RX_RING RX_TIP Not connected Not connected Not connected
As shown in Table 41, when two routers are connected via E1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. Its connection method is displayed in Table 40.
FIGURE 26 INTERCONNECTION OF E1 RJ48 CONNECTORS
F I G U R E 2 7 I N T E R C O N N E C T I O N O F E 1 J R 4 8 AN D E 1 B N C C O N N E C T O R S
RA-2CE1-75
The RA-2CE1-75 (2-port channelized 75 ohm E1 unbalanced micro coaxial interface board) provides two E1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements functions such as data receiving and framing, and the sending end is to send the data to lines. 1. Panel Panel of RA-2CE1-75 board is shown in Figure 28.
2.
Interfaces Features of interfaces on RA-2CE1-75 board are shown in Table 42.
Port Type
E1Channelized E1
75 ohm micro coaxial (CC4) connectors Line code of HDB3 A channelized E1 controller has 31 valid timeslots
3.
Indicators There are two indicators on each interface of RA-2CE1-75 board. Their functions are listed in Table 43.
T A B L E 4 3 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 2 C E 1 - 7 5 B O AR D
Functions Running indicator: Green indicator indicates the port runs properly Line indicator: On indicates the physical line is normal
RA-2CT1
The RA-2CT1 (2-ports channelized T1 interface board) provides two T1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements the function of data receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines.
1.
Panel Panel of RA-2CT1 board is shown in Figure 29.
2.
Interfaces Features of interfaces on RA-2CT1 board are shown in Table 44.
T A B L E 4 4 F E AT U R E S O F I N T E R F A C E S O N R A- 2 C T 1 B O A R D
Port Type
T1Channelized T1
RJ48 connector and 100 ohm twisted pair Line code of B8ZS/AMI A channelized E1 controller has 24 valid timeslots
3.
Indicators There are two indicators on each interface of RA-2CT1 board. Their functions are listed in Table 45.
T A B L E 4 5 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 2 C T 1 B O AR D
Indicator
Functions
Upper left indicator on Alarm indicator: On indicates port/line fault each port (yellow) Upper right indicator on Line indicator: On indicates the line and line signals are normal each port (green)
4.
Interconnection Table 46 shows interconnection of RJ48 connectors at T1 port.
TABLE 46 INTERCONNECTION OF RJ48 CONNECTORS AT T1 PORT
RJ48 of GAR CE1 Board 1 2 3
Signal RX_RING RX_TIP Not connected
E1 RJ48 Connector of Mating Device 4 5 3
Signal TX_RING TX_TIP Not connected
4 5 6 7 8
TX_RING TX_TIP Not connected Not connected Not connected
1 2 6 7 8
RX_RING RX_TIP Not connected Not connected Not connected
As shown in Table 46, when two routers are connected via T1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. Its connection method is displayed in Figure 30.
F I G U R E 3 0 C AB L E C O N N E C T I O N A T T 1 P O R T
RA-2FE-R
RA-2FE-R (2-ports fast Ethernet electrical interface board) provides fast Ethernet uplink interface module and downlink user module. Each board has two 10Base-T / 100Base-TX adaptive ports. 1. Panel Panel of RA-2FE-R board is shown in Figure 31.
F I G U R E 3 1 R A- 2 F E - R B O AR D P A N E L
2.
Interfaces Features of interfaces on RA-1GE-GBIC-R are shown in Table 47.
T A B L E 4 7 F E AT U R E S O F I N T E R F A C E S O N R A- 1 G E - G B I C - R B O AR D
Port Type 10Base-T
Specifications In compliance with IEEE 802. 3
RJ45 connector Using category-3, 4 and 5 Unshielded Twisted Pairs (UTP) Maximum transmission distance: 100 m In compliance with IEEE 802. 3u 100Base-TX RJ45 connector Using category-5 Unshielded Twisted Pairs (UTP) Maximum transmission distance: 100 m
Note: When the10Base-T /100Base-TX port is interconnected with a hub, switch or router, a crossover cable should be used; when it is interconnected with a host, a straight-through cable should be used.
3.
Indicators There are two indicators on each interface of RA-2FE-R board. Their functions are listed in Table 48.
T A B L E 4 8 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 2 F E - R B O AR D
Indicator
Functions
Upper left indicator Run indicator: Green indicator indicates normal running of the port and on each port flashing indicates data being received/sent (yellow) Upper right indicator on each Line indicator: On indicates the physical line is normal port (green)
Note: RA-2FE-R can only be adopted in ZXR10 GAR routers with the specification of RAG7208-XX, avoiding routers of RA-G2608-XX, RA-G2604-XX and RA-G3608-XX.
RA-2FXS
RA-2FXS (2-ports Z interface voice interface board) can be used for direct connection with analog telephones. It provides BORSCHT (Battery, Overvoltage, Ringing, Supervision, Coding, Hybrid, Test) functions at two ports. 1. Panel Panel of RA-2FXS board is shown in Figure 32.
F I G U R E 3 2 R A- 2 F X S B O A R D P A N E L
2.
Interfaces Features of interfaces on RA-2FXS board are shown in Table 49.
T A B L E 4 9 F E AT U R E S O F I N T E R F A C E S O N R A- 2 F X S B O A R D
Port Type
Specifications RJ45 connector Bandwidth: 300Hz~3400Hz Circuit at the user interface complies with ITU Q.512 recommendation Overvoltage and recommendation overcurrent protection comply with ITU K.20
Voice interface
Supporting DTMF dialing and complying with GB3378 Not supporting pulse dialing Supporting voice coding modes such as g711a, g711u, g7231, g729a Recommendation: Telephone line should be less than 500 m
3.
Indicators There are two indicators for each interface on RA-2FXS board. Their functions are listed in Table 50.
T A B L E 5 0 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 2 F X S B O AR D
Indicator
Functions
Upper left indicator On indicates the caller hooks off or the called telephone rings. Off on each port indicates hanging up (yellow) Upper right On indicates in conversation indicator on each port (green)
RA-2GE-GBIC-R
RA-2GE-GBIC-R (2-ports Gigabit Ethernet optical interface board) provides Gigabit uplink interface module and downlink user module. It can provide two Gigabit optical interfaces with different driving distances by configuring GBIC components of different specifications. 1. Panel Panel of RA-2GE-GBIC-R is shown in Figure 33
F I G U R E 3 3 R A- 2 G E - G B I C - R B O AR D P A N E L
2.
Interfaces Features of interfaces on RA-2GE-GBIC-R are shown in Table 51.
T A B L E 5 1 F E AT U R E S O F I N T E R F A C E S O N R A- 2 G E - G B I C - R B O AR D
Port Type SX (GBIC-M500) LX (GBIC-S10K) LH (GBIC-S70K)
Specifications SC connector, multi-mode fiber, with the wavelength of 850nm and the maximum transmission distance of 500 m SC connector, single-mode fiber, with the wavelength of 1310nm and the maximum transmission distance of 10 km SC connector, single-mode fiber, with the wavelength of 1550nm and the maximum transmission distance of 70 km
3.
Indicators There are two indicators for each interface on RA-2GE-GBIC-R board. Their functions are listed in Table 52.
Note: RA-2GE-GBIC-R can only be adopted in ZXR10 GAR routers with the specification of RA-G7208-XX, avoiding routers of RA-G2608-XX, RA-G2604-XX and RA-G3608-XX.
RA-4AS-U
RA-4AS-U (4-ports synchronous/asynchronous serial interface board) provides four serial interfaces with each of them independently configured in the mode of V.35, V.24 (synchronous), and V.24 (asynchronous). It can work in the DTE or DCE mode, supporting the rate from 300bps to 640kbps. 1. Panel Panel of RA-4AS-U board is shown in Figure 34.
F I G U R E 3 4 R A- 4 A S - U B O AR D P A N E L
2.
Interfaces Features of interfaces on RA-4AS-U are shown in Table 53
T A B L E 5 3 F E AT U R E S O F I N T E R F A C E S O N R A- 4 A S - U B O AR D
Port Type
Specifications In compliance with V.35, V.24 (synchronous), and V.24 (asynchronous) standards Recommendation: WAN cable is less than 3 m Optional software: DTE and DCE
Dual interface
serial DB36 plug
3.
Indicators There are two indicators for each interface on RA-4AS-U board. Their functions are listed in Table 54.
T A B L E 5 4 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 AS - U B O AR D
Functions Run indicator: On after board initialization Line indicator: On indicates the line and line signals are normal
4.
Interconnection External cables are adopted in accordance with vary application requirements. Cable codes and features are listed in Table 55.
T A B L E 5 5 E X T E R N AL C AB L E S AT D U AL S E R I AL I N T E R F A C E
Cable Code V.24A V.24B V. 35C V. 35D
CSU/DSU Port Type Two V.24 DB25 connectors Two V.24 DB25 female connectors Two V.35 34-pin male connectors Two V.35 34-pin female connectors
Note: V.24A cables should be used for connecting MODEM.
RA-4CE1
RA-4CE1 (4-ports channelized 120 ohm E1 interface board) provides four E1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements the function of data
receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines. 1. Panel Panel of RA-4CE1 board is shown in Figure 35.
2.
Interfaces Features of interfaces on RA-4CE1 board are shown in Table 56.
Port Type
E1Channelized E1
3.
T A B L E 5 7 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 C E 1 B O AR D
Indicator
Functions
Upper left indicator Alarm indicator: On indicates port/line fault on each port (yellow) Upper right Line indicator: On indicates the line and line signals are normal indicator on each port (green)
4.
Interconnection Table 58 shows interconnection method of RJ48 connectors at E1 port.
TABLE 58 INTERCONNECTION METHOD OF RJ48 CONNECTORS AT E1 PORT
RJ48 of GAR CE1 Board 1 2 3 4 5 6 7 8
As shown in Table 58, when two routers are connected via E1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. Its connection method is displayed in Figure 36.
FIGURE 36 INTERCONNECTION OF E1 RJ48 CONNECTORS
F I G U R E 3 7 I N T E R C O N N E C T I O N O F E 1 J R 4 8 AN D E 1 B N C C O N N E C T O R S
RA-4CE1-75
The RA-4CE1-75 (4-ports channelized 75 ohm E1 unbalanced micro coaxial interface board) provides four E1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements functions such as data receiving and framing, and the sending end is to send the data to lines. 1. Panel Panel of RA-4CE1-75 board is shown in Figure 38.
2.
Interfaces Features of interfaces on RA-4CE1-75 board are shown in Table 59.
Port Type
E1Channelized E1
75 ohm micro coaxial (CC4) connector Line code of HDB3 A channelized E1 controller has 31 valid timeslots
3.
Indicators There are two indicators on each interface of RA-4CE1-75 board. Their functions are listed in Table 60.
T A B L E 6 0 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 C E 1 - 7 5 B O AR D
Functions Running indicator: Green indicator indicates the port runs properly Line indicator: On indicates the physical line is normal
RA-4CT1
RA-4CT1 (4-ports channelized T1 interface board) provides four T1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements the function of data receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines. 1. Panel Panel of RA-4CT1 board is shown in Figure 39.
2.
Interfaces Features of interfaces on RA-4CT1 board are shown in Table 61.
T A B L E 6 1 F E AT U R E S O F I N T E R F A C E S O N R A- 4 C T 1 B O A R D
Port Type
T1Channelized T1
RJ48 connector and 100 ohm twisted pair Line code of A channelized E1 controller has 24 valid timeslots
3.
Indicators There are two indicators on each interface of RA-4CT1 board. Their functions are listed in Table 62.
T A B L E 6 2 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 C T 1 B O AR D
Indicator
Functions
Upper left indicator on each Alarm indicator: On indicates port/line fault port (yellow) Upper right indicator on each Line indicator: On indicates the line and line signals are port (green) normal
4.
Interconnection Table 63 shows interconnection method of RJ48 connectors at E1 port.
TABLE 63 INTERCONNECTION METHOD OF RJ48 CONNECTORS AT E1 PORT
RJ48 of GAR CE1 Board 1 2 3 4 5 6 7 8
As shown in Table 63, when two routers are connected via T1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. The connection mode is shown in Figure 40.
F I G U R E 4 0 C AB L E C O N N E C T I O N A T T 1 I N T E R F AC E
RA-4E1VE
RA-4E1VE (4-ports E1VE interface board) implements transparent transmission of TDM frames over IP networks. Each board provides four E1 interfaces and a routing of 10/100Base-TX adaptive ports. TDM frame signals transmitted via E1 interfaces at the receiving end are directly packed into IP packets without any process, and then the packets are sent to IP networks via external/internal 10/100Base-TX ports. At the sending end, data from IP network are converted to TDM signals after packet head process and are sent via E1 interfaces. 1. Panel Panel of RA-4E1VE board is shown in Figure 41.
F I G U R E 4 1 R A- 4 E 1 V E B O AR D P A N E L
2.
Interfaces Features of interfaces on RA-4E1VE board are shown in Table 64.
T A B L E 6 4 F E AT U R E S O F I N T E R F A C E S O N R A- 4 E 1 V E B O A R D
Port Type
Specifications In compliance with recommendations ITU G.703, G.704 or T1.102 and T1.107
Channelized/non- Adopting RJ45 connector and 120 ohm E1 crossover cable channelized E1 Line code of B8ZS or AMI Transparent transmission of data at E1 interface In compliance with IEEE 802.3 or IEEE 802.3u recommendations RJ45 connector 10M/100M 10BaseT/100Base-TX Semi-duplex/full-duplex automatic negotiation Using category-5 unshielded twist pair Maximum transmission distance: 100 M
3.
Indicators Indicator functions of RA-4E1VE board are listed in Table 65.
T A B L E 6 5 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 E 1 V E B O AR D
Indicator
Functions
Upper right indicator on each On indicates the physical line is normal port (green)
RA-4FE-R
RA-4FE-R (4-ports fast Ethernet electrical interface board) provides fast Ethernet uplink interface module and downlink user module. Each board has four 10Base-T / 100Base-TX adaptive ports. 1. Panel Panel of RA-4FE-R is shown in Figure 42.
2.
Interfaces Features of interfaces on RA-4FE-R are shown in Table 66.
T A B L E 6 6 F E AT U R E S O F I N T E R F A C E S O N R A- 4 F E - R B O AR D
Port Type
Specifications In compliance with EE 802. 3 RJ45 connector Using category-3, 4 and 5 Unshielded Twisted Pairs (UTP) Maximum transmission distance: 100 m In compliance with IEEE 802. 3u RJ45 connector Using category-5 Unshielded Twisted Pairs (UTP) Maximum transmission distance: 100 m
10Base-T
100Base-TX
Note: When the10Base-T /100Base-TX port is interconnected with a hub, switch or router, a crossover cable should be used; when it is interconnected with a host, a straight-through cable should be used.
3.
Indicators
There are two indicators on each interface of RA-4FE-R board. Their functions are listed in Table 67.
Indicator
Functions
Upper left indicator Run indicator: Green indicator indicates normal running of the port and on each port flashing indicates data being received/sent (yellow) Upper right indicator on each Line indicator: On indicates the physical line is normal port (green)
RA-4FXO
RA-4FXO (4-ports loop trunk voice interface board) adopts the VoIP technology to provide four routes of trunk voice access. It implements exchanging digital signals with the voice processing circuit through TDM bus. The voice processing circuit will then implement receiving and sending relative data packets. 1. Panel Panel of RA-4FXO board is shown in Figure 43.
F I G U R E 4 3 R A- 4 F X O B O AR D P A N E L
2.
Interfaces Features of interfaces on RA-4FXO board are shown in Table 68.
T A B L E 6 8 F E AT U R E S O F I N T E R F A C E S O N R A- 4 F X O B O A R D
Port Type
Specifications RJ45 connector Circuit at the recommendation user interface complies with ITU Q.512
Voice interface
Supporting voice coding modes such as g711a, g711u, g723. 1 and g729a Supporting DTMF dialing and complying with GB3378
3.
Indicators
Indicator functions of RA-4FXO board are listed in Table 69.

T A B L E 6 9 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 F X O B O AR D
Indicator
Functions
RA-4FXS
RA-4FXS (4-ports Z interface voice interface board) can be used for direct connection with analogue telephones. It provides BORSCHT (Battery, Overvoltage, Ringing, Supervision, Coding, Hybrid, Test) functions at four ports. 1. Panel Panel of RA-4FXS board is shown in Figure 44.
2.
Interfaces Features of interfaces on RA-4FXS board are shown in Table 70
T A B L E 7 0 F E AT U R E S O F I N T E R F A C E S O N R A- 4 F X S B O A R D
Port Type
Specifications RJ45 connector Bandwidth: 300Hz~3400Hz Circuit interfaces on user interface module complies with ITU Q.512 recommendation
Voice interface
Overvoltage and recommendation
overcurrent
protection
comply
with
ITU
K.20
Supporting DTMF dialing and complying with GB3378 Not supporting pulse dialing Supporting voice coding modes such as g711a, g711u, g7231, g729a Recommendation: Telephone line should be less than 500 m
3.
Indicators
There are two indicators for each interface on RA-4FXS board. Their functions are listed in Table 71.
Indicator
Functions
RA-4HS
RA-4HS (4-ports high-speed serial interface board) provides four serial interfaces each of which can be independently configured in the mode of V.35, V.24 (synchronous), and V.24 (asynchronous). It can work in the DTE or DCE mode, supporting the rate from 300bps to 2Mbps. 1. Panel Panel of RA-4HS board is shown in Figure 45.
F I G U R E 4 5 R A- 4 H S B O A R D P AN E L
2.
Interfaces Interface features of RA-4HS board are shown in Table 72
T A B L E 7 2 I N T E R F A C E F E AT U R E S O F R A - 4 H S B O A R D
Port Type
Specifications In compliance with V.35, V.24 (synchronous), and V.24 (asynchronous) standards Recommendation: WAN cable is less than 3 m Optional software: DTE and DCE
Dual interface
serial DB36 connector
3.
Indicators There are two indicators for each interface on RA-4HS board. Their functions are listed in Table 73.
T A B L E 7 3 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 4 H S B O A R D
Functions Run indicator: On after board initialization Line indicator: On indicates the line and line signals are normal
4.
Interconnection External cables are adopted in accordance with vary application requirements. Cable codes and features are listed in Table 74.
T A B L E 7 4 E X T E R N AL C AB L E S AT D U AL S E R I AL I N T E R F A C E
Cable Code V.24A V.24B V. 35C V. 35D
CSU/DSU Port Type Two V.24 DB25 male connectors Two V.24 DB25 female connectors Two V.35 34-pin male connectors Two V.35 34-pin female connectors
Note: V.24A cables should be used for connecting MODEM.
RA-4T1VE
RA-4T1VE (4-ports T1VE interface board) implements transparent transmission of TDM frames over IP networks. Each board provides four T1 interfaces and a routing of 10/100Base-TX adaptive ports. TDM frame signals transmitted via T1 interfaces at the receiving end are directly packed into IP packets without any process, and then the packets are sent to IP networks via external/internal 10/100Base-TX ports. At the sending end, data from IP network are converted to TDM signals after packet head process and are sent via T1 interfaces. 1. Panel Panel of RA-4T1VE board is shown in Figure 46.
F I G U R E 4 6 R A- 4 T 1 V E B O A R D P AN E L
2.
Interfaces Interface features of RA-4T1VE board are shown in Table 75.
T A B L E 7 5 I N T E R F A C E F E AT U R E S O F R A - 4 T 1 V E B O AR D
Port Type
Specifications In compliance with ITU G.703, G.704 or T1.102 and T1.107 recommendations
Channelized/non-channelized Adopting RJ45 connector 100 ohm T1 crossover cable T1 Line code of AMI Transparent transmission of data at T1 interface
10Base-T/100Base-TX
In compliance with IEEE 802.3 or IEEE 802.3u recommendations; RJ45 connector 10M/100M; Semiduplex/full-duplex automatic negotiation; Using category-5 unshielded twist pair; Maximum transmission distance: 100 M
3.
Indicators Functions of indicators on RA-4T1VE board are shown in Table 76
T A B L E 7 6 D E S C R I P T I O N S O F I N D I C AT O R S O N R A- 4 T 1 V E B O AR D
Indicator
Functions
Upper right On indicates the physical line is normal indicator on each port (green)
RA-8CE1
RA-8CE1 (8-ports channelized 120 ohm E1 interface board) provides eight E1 interfaces in conformity with the ITU-T G. 703 and G. 704 recommendations. Each port supports the sending and receiving functions. The receiving end implements the function of data receiving, framing and HDLC link control, and the sending end is to organize the data into HDB3 codes and send them to lines. 1. Panel Panel of RA-8CE1 board is shown in Figure 47.
2.
Interfaces Interface features of RA-8CE1 are shown in Table 77.
T A B L E 7 7 I N T E R F A C E F E AT U R E S O F R A - 8 C E 1 B O AR D
Port Type
E1Channelized E1
Adopting RJ48 connector and 120 ohm E1 crossover cable Line code of HDB3 A channelized E1 controller has 31 valid timeslots
3.
T A B L E 7 8 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 8 C E 1 B O AR D
Indicator
Functions
Upper left indicator Alarm indicator: On indicates port/line fault on each port (yellow) Upper right Line status indicator: On indicates the line and line signals are normal indicator on each port (green)
4.
Interconnection Table 79 shows the interconnection method of RJ48 connectors at E1 ports.
TABLE 79 INTERCONNECTION METHOD OF RJ48 CONNECTORS AT E1 PORTS
RJ48 of GAR CE1 Board 1 2 3 4 5
Signal RX_RING RX_TIP Not connected TX_RING TX_TIP
6 7 8
Not connected Not connected Not connected
As shown in Table 79, when two routers are connected via T1 RJ48 connectors, special crossover cables of 1 and 4 or 2 and 5 in the mode of interchange are used for connection. The connection method is shown in Figure 48.
FIGURE 48 INTERCONNECTION VIA E1 RJ48 CONNECTORS
FIGURE 49 INTERCONNECTION OF E1 RJ48 WITH E1 BNC CONNECTORS
RA-8CE1-R
The RA-8CE1-R (8-ports channelized LCE1H interface board) provides eight E1 interfaces. Each port supports the sending and receiving functions. The receiving end implements functions such as data receiving and framing, and the sending end is to send the data to lines. 1. Panel Panel of RA-8CE1-R board is shown in Figure 50.
F I G U R E 5 0 R A- 8 C E 1 - R B O AR D P AN E L
2.
Interfaces Interface features of RA-8CE1-R board is shown in Table 80
T A B L E 8 0 I N T E R F A C E F E AT U R E S O F R A - 8 C E 1 - R B O A R D
Port Type
Specifications Providing four E1 ports in compliance with ITU-T G. 703 and G. 704 recommendations
E1Channelized E1
Available line impedance configuration: 75 ohm and 120 ohm. External interfaces are applicable for flat cables and in compliance with G. 703 and G. 704 recommendations. Line code of HDB3
3.
Indicators There are two indicators on each interface of RA-8CE1-R board. Their functions are listed in Table 81.
T A B L E 8 1 D E S C R I P T I O N O F I N D I C AT O R S O N R A - 8 C E 1 - R B O A R D
Indicator LINE (green)
Functions indicator On indicates the physical line is normal
Note: The RA-8CE1-R board supports only G72 serial racks.
RA-8FE-R
RA-8FE-R (8-ports fast Ethernet electrical interface board) provides high-density fast Ethernet uplink interface module and downlink user module. Each board has eight 10Base-T/100Base-TX adaptive ports. 1. Panel Panel of RA-8FE-R board is shown in Figure 51.
2.
Interfaces Interface features of RA-8FE-R board are shown in Table 82.
T A B L E 8 2 I N T E R F A C E F E AT U R E S O F R A - 8 F E - R B O AR D
Port Type
10Base-T
100Base-TX
Note: When the10/100Base-TX port is interconnected with a hub, switch or router, a crossover cable should be used; when it is interconnected with a host, a straight-through cable should be used.
3.
Indicators There are two indicators on each interface of RA-8FE-R board. Their functions are listed in Table 83.
Indicator
Functions
Upper left indicator Run indicator: Indicates normal running of the port when it is on and on each port receiving/sending of data packet when it flashes (yellow) Upper right Line indicator: On when the physical link is connected well indicator on each port (green)
RA-8FXS
RA-8FXS (8-ports Z interface voice interface board) can be used for direct connection with analogue telephones. It provides BORSCHT (Battery, Overvoltage, Ringing, Supervision, Coding, Hybrid, Test) functions at eight ports. 1. Panel Panel of RA-8FXS board is shown in Figure 52.
2.
Interfaces Interface features of RA-8FXS board are shown in Table 84.
T A B L E 8 4 I N T E R F A C E F E AT U R E S O F R A - 8 F X S B O AR D
Port Type
Specifications RJ45 connector Bandwidth: 300Hz~3400Hz Circuit interfaces on user interface module are in compliance with ITU Q.512
Voice interface
Overvoltage and recommendation
overcurrent
protection
comply
with
ITU
K.20
Supporting DTMF dialing instead of pulse dialing and complying GB3378 Supporting voice coding modes of g711a, g711u, g7231, g729a Recommendation: Telephone line should be less than 500 m
3.
Indicators There are two indicators on each interface of RA-8FXS board. Their functions are listed in Table 85.
Indicator
Functions
Chapter
User Interface Configuration

The chapter describes common configurations, command modes and usage of command lines of ZXR10 routers.
Basic Configuration Modes

In order to provide the most flexible operations for users, multiple configuration modes are available for ZXR10 routers. A user can select a proper one according to the connected network. The configuration modes will be described as follows: 1. 2. 3. 4. 5. Configuration through COM ports: This is the main mode for a user to configure a router. Configuration in Telnet mode: In this mode, a user can configure a router in any position on a network. Configuration through NM workstation: Corresponding NM software supporting the SNMP protocol is needed in this mode. Downloading router configuration files via the TFTP/FTP Server Configuration on the NM interface through the Telnet host.
F I G U R E 5 3 C O N F I G U R AT I O N M O D E S O F Z X R 1 0 R O U T E R S
Configuration through Serial Interface Connection
Upon delivery, a ZXR10 router is configured with a serial interface configuration cable with DB9 serial interfaces on both ends. Upon connection, one end of the cable is connected to the COM port of the ZXR10 router, and the other end to the serial interface of a computer. The configuration by means of serial interface connection is in VT100 terminal mode. The HyperTerminal tools provided in the Windows operating system can be used. Before configuration, proper configuration of the serial interface is needed. Detailed procedures are as follows: 1. Open the HyperTerminal, as shown in Figure 54. Enter the connection name, such as ZXR10, and select an icon.
F I G U R E 5 4 Z X R 1 0 S E R I A L I N T E R F AC E C O N F I G U R A T I O N 1
2.
Click OK, the interface shown in Figure 55 will pop up. As selecting a connection, use a COM port, such as COM1.
FIGURE 55 ZXR10 SERIAL INTERFACE CONFIGURATI ON 2
3.
Click OK, the Port Settings interface of the COM port will pop up, as shown in Figure 56.
F I G U R E 5 6 Z X R 1 0 S E R I A L I N T E R F AC E C O N F I G U R A T I O N 3
Configure the properties of the COM port as follows: Set Bits per second (baud rate) to 115200, Data bits to 8, Parity to None, Stop bits to 1 and Flow control to None. 4. Click OK to complete the setting.
TELNET Connection Configuration

The Telnet mode is normally used in the case of remote router configuration that is completed by the access of a host (connected to the Ethernet port of a local router) to a remote router. A user name and password should be set for Telnet access on the remote router. Furthermore, the local host should be able to ping the remote router successfully. Provided that the IP address of the remote router is 192. 168. 3. 1 and the local host can ping the address successfully, operations of remote configuration are as follows: 1. Run the T e l n e t command on the host, as shown in Figure 57.
FIGURE 57 RUN TELNET
2.
Click OK. The Telnet window will pop up, as shown in Figure 58.
FIGURE 58 ZXR10 REMOTE LOGIN
3.
Input the user name and password according to the prompt to enter the configuration status of the remote router. To prevent an unauthorized user from access to the router in Telnet mode, the user name and password for Telnet access must be configured on the router. To log on to the router, the configured user name and password must be input. Use the following command to configure the user name and password for remote login.
username <username> password <password>
Command Mode
For users to configure and manage routers conveniently, ZXR10 routers assign commands to different modes according to different functions and rights. A command can only be carried out in a special mode. In any command mode, just enter a question mark ?, and the commands that can be used in the mode can be viewed. The command modes of ZXR10 routers are as follows: 1. 2. 3. 4. 5. 6. Exec mode Privileged mode Global configuration mode Interface configuration mode Route configuration mode Diagnosis mode
Exec Mode
When using the HyperTerminal mode to log on to the system, the system will enter the user EXEC mode automatically. As using the Telnet mode to log on, a user will enter the user EXEC mode after entering the user name and password. The prompt of the EXEC mode is the host name of the router followed by a symbol of >, as shown in the following figure (the default host name is ZXR10):
ZXR10>
In the user EXEC mode, a user can run commands, such as p i n g and t e l n e t , and also can view parts of the system information.
Privileged Mode
In the user EXEC mode, enter the e n a b l e command and the corresponding password to enter the Privileged mode, as follows:
ZXR10>enable Password: (The password will not be displayed) ZXR10#
In the Privileged mode, a user can view more detailed configuration information and also can enter the configuration mode to configure the entire router. Therefore, a password should be used to prevent illegal use of unauthorized users. To return from the Privileged mode to the EXEC mode, use the d i s a b l e command.
Global Configuration Mode

In the Privileged mode, input the c o n f i g t e r m i n a l command to enter the Global Configuration mode, as follows:
ZXR10# configure terminal Enter configuration commands,one par line,End with Ctrl-Z ZXR10(config)#
Commands in the Global Configuration mode act on the entire system, not merely on a protocol or an interface. To return from the Global Configuration mode to the Privileged mode, input the e x i t or e n d command or press CTRL+Z.
Interface Configuration Mode

In the Global Configuration mode, use the i n t e r f a c e command to enter the Interface Configuration mode, as shown in the following figure:
ZXR10(config)# interface name, interface indicating fei_2/1 the first (fei_2/1 interface is of the the
Ethernet interface module in Slot 2) ZXR10(config-if)#
A user can modify interface parameters in the Interface Configuration mode. For details, refer to Chapter 6. To return from the Interface Configuration mode to the Global Configuration mode, input the e x i t command; and to return from the Interface Configuration mode to the Privileged mode directly, input the e n d command or press CTRL+Z.
Route Configuration Mode

In the Global Configuration mode, use the r o u t e r command to enter the Route Configuration mode, as shown in the following example:
ZXR10(config)# router ospf 1 ZXR10(config-router)#
Routing protocols used are RIP, OSPF, IS-IS and BGP. In the above example, the routing protocol OSPF will be configured. To return from the Route Configuration mode to the Global Configuration mode, input the e x i t command; and to return from the Route Configuration mode to the Privileged mode directly, input the e n d command or press CTRL+Z.
Diagnosis Mode
In the Privileged mode, use the d i a g n o s e command to enter the Diagnosis mode with an example as follows:
ZXR10#diagnose Test commands: ZXR10(diag)#
Diagnosis test commands are provided in the Diagnosis mode. These commands can be used to test boards used in a router, including bus and connectivity tests. In a diagnosis test, it is much better not to conduct router configurations. To return from the Diagnosis mode to the Privileged mode, input the e x i t or e n d command or press CTRL+Z.
Online Help
In any command mode, enter a question mark ? after the system prompt and then a list of available commands in the command mode will be displayed. With the contextsensitive help function, keywords and parameter lists of any commands can be obtained.
1.
In any command mode, enter a question mark ? after the system prompt and then a list of all commands in the selected mode and the brief description of the commands will be displayed. Here is an example:
ZXR10>? Exec commands: enable Turn on privileged commands exit login ping quit show trace who ZXR10> Exit from the EXEC Login as a particular user Send echo messages Quit from the EXEC Show running system information Trace route to destination List users who is logining on
logout Exit from the EXEC
telnet Open a telnet connection
2.
Input the question mark behind a character or character string to view the list of commands or keywords beginning with this character or character string. Note that there should be no space between the character (string) and the question mark. Here is an example:
ZXR10#co? configure copy ZXR10#co
3.
Press TAB behind the character string. If the command or keyword beginning with this character string is unique, it shall be completed with a space at the end. Note that there is no space between the character string and the TAB. Here is an example:
ZXR10#con<Tab> ZXR10#configure (a space between configure and cursor)
4.
Input a question mark after a command, a keyword or a parameter, the next keyword or parameter to be input will be listed, and also a brief explanation will be given. Note that a space must be entered before the question mark. Here is an example:
ZXR10#configure ? terminal Enter configuration mode ZXR10#configure
If an incorrect command, keyword or parameter is input, the error isolation is offered with ^ in the user interface after you press ENTER. The ^ is below the first
character of the input incorrect command, keyword or parameter. Here is an example:

ZXR10#von ter ^ % Invalid input detected at '^' marker. ZXR10#
In the following example, suppose that a clock is to be set and the contextsensitive help is used to check the syntax for setting the clock.
ZXR10#cl? clear clock ZXR10#clock ? set Set the time and date ZXR10#clock set ? hh:mm:ss Current Time ZXR10#clock set 13:32:00 % Incomplete command. ZXR10#
At the end of the above example, the system prompts that the command is incomplete and other keywords or parameters should be input. The ZXR10 router also allows abbreviation of a command or keyword into characters or a string that uniquely identifies the command or keyword. For example, the s h o w command can be abbreviated s h or s h o .
Command History
The user interface supports the function of recording input commands. A maximum of ten history commands can be recorded. The function is very useful in re-invocation of a long or complicated command or ingress. To re-invoke a command from the record buffer, conduct one of the following operations.
Command Function
Press Ctrl-P or the up Re-invokes the latest command in the record buffer. Repeat these arrow key keys to invoke old commands forwards Roll the commands downward. When the last command line is Press Ctrl-N or the down reached, one more operation will roll the commands from the arrow key begging of the buffer cyclically.
Use the s h o w h i s t o r y command in the Privileged mode, the latest several commands in the mode will be listed.
Chapter
System Management
The chapter describes system management of ZXR10 GAR routers, details the file system and its operations of routers, and also gives a detailed description of version upgrading.

File System Introduction
In a ZXR10 GAR router, the main storage device is a FLASH. Version and configuration files of the router are stored in it. Operations, such as version upgrading and configuration saving, should be conducted in the FLASH. The FLASH consists of three directories: IMG, CFG and DATA. IMG: System mapping files (version files) are stored under this directory. The extended name of version files is .zar. These version files are dedicated compression files. Version upgrading means the change of the corresponding version files under the directory. CFG: Configuration files are stored under this directory. As modifying router configurations using a command, the files are stored in the memory to prevent information loss in the case of restarting the router. Command w r i t e should be used for writing the memory information into s t a r t r u n . d a t . To clear original configurations in the router for data reconfiguration, use the d e l e t e command to delete the s t a r t r u n . d a t file and then reboot the router. DATA: This directory is used to store the ***. zte file that records the abnormity information, where *** stands for characters from 001 to 050.

The ZXR10 GAR provides many file operation commands in a format similar to those under the DOS operating system. Some of them are as follows:
1. 2. 3. 4. 5. 6. 7. 8. 9.
Copy files between the FLASH device and the FTP or TFTP Servers
copy source-device source-file destination-device destination-file
View the path of current directory:

pwd
View files and subdirectories of a specified device or under a specified directory:

dir [<directory>]
Delete files under the specified directory of the device:

delete filename
Enter a file directory of designated file equipment or the current equipment

cd directory
Return to the superior directory:

cd. .
Create a file directory under the current directory:

mkdir directory
Delete the specified file directory:

rmdir <directory>
Modify the specified file name or directory name:

rename source-filename destination-filename
The following instances will be given to illustrate file operation commands: 1. View current files in the Flash.
ZXR10#dir Directory of flash:/ Attribute name 1 2 3 drwx drwx drwx 512 512 512 JUN-27-2002 JUN-27-2002 JUL-08-2002 15:28:56 15:28:56 07:51:56 CFG DATA IMG size date time
65007616 bytes total (15863808 bytes free) ZXR10#cd img ZXR10#dir /*Enter the version directory img*/ /*Show the current directory information*/ size 512 512 16364919 date time name
Directory of flash:/img attribute 1 . 2 . . 3 -rwx MAY-11-2005 11:37:06 zxr10gar.zar 65007616 bytes total (15863808 bytes free) drwx JUL-08-2002 07:51:56 drwx JUL-08-2002 07:51:56
ZXR10#
2.
Create directory ABC in the Flash and then delete it.

ABC /*Add /*Check and the directory a subdirectory the ABC ABC under the
ZXR10#mkdir ZXR10#dir information added*/
current directory*/ current can be directory successfully
Directory of flash:/ attribute 1 15:28:56 2 3 4 drwx drwx drwx drwx CFG 512 512 512 JUN-27-2002 15:28:56 JUL-08-2002 07:51:56 AUG-06-2003 14:58:04 DATA IMG ABC size date 512 time name JUN-27-2002
65007616 bytes total (15863808 bytes free) ZXR10#rmdir ABC ZXR10#dir information successfully) Directory of flash:/ attribute 1 15:28:56 2 3 drwx drwx drwx CFG 512 512 JUN-27-2002 15:28:56 JUL-08-2002 07:51:56 DATA IMG size date 512 time name JUN-27-2002 and /*Delete the subdirectory ABC*/ /*Check the the ABC current has been directory deleted directory
65007616 bytes total (15863808 bytes free) ZXR10#
FTP/TFTP Configuration
Version files and configuration files of a router can be backed up or restored by using FTP or TFTP.
FTP Configuration
Enable FTP, server application software, on the background, and access the router as a client. Take the FTP Server software W F T P D as an example to describe configurations of the background FTP Server. 1. Execute w f t p d 3 2 . e x e and the interface shown in Figure 59. will pop up.
FIGURE 59 WFTPD INTERFACE
2.
Click menu item Security on the interface as shown in Figure 59, select User/Rights and the dialog box shown in Figure 60 will pop up.
FIGURE 60 USER/RIGHTS SECURITY SETTING
3.
Perform the following operations in the User/Rights Security Dialog box: Click New User to create a user, target for example, and set a password for it. Select target from the User Name drop-down list. Type the directory of the version/configuration file in the Home Directory text box, such as D : \ I M G . After the configuration is completed, the dialog box is as follows:
FIGURE 61 USER/RIGHTS SECURITY SETTING
4.
Click Done in Figure 61 to start the FTP Server.
TFTP Configuration
Start TFTP server on the background host, and access the switch as a client. The following describes the background TFTP server configuration taking the t f t p d as an example. 1. Run the t f t p d software at the background host. The interface as shown in Figure 62 is displayed.
FIGURE 62 TFTPD INTERFACE
2.
Select Tftpd > Configure. In the pop-up dialog box, click Browse and select the directory for the version file or configuration file, for example, D:\IMG. Figure 63 shows the dialog box after the setting is finished.
FIGURE 63 CONFIGURE DIALOG BOX
3.
Click OK to complete the setting.
Backing up and Recovering Data

The data backup and recovery here means the backup and recovery of version and configuration files in the FLASH. 1. Saving Configuration Files When a command is used to modify the configuration of a router, the information is running in the memory in real time. If the router reboots, all the new configurations will get lost. Therefore, the w r i t e command should be used to write the memory information into NVRAM and FLASH to prevent loss of the configuration information upon power-off and reboot. The operation of the w r i t e command is as follows:
ZXR10#write ? flash imgfile logging nvram Write to FLASH memory Write running system file to M&S UPC Write the alarm logging into file Write to NVRAM memory <cr>
ZXR10#write
Enter the w r i t e command, directly press ENTER, and the system will write the information into the FLASH and NVRAM. 2. Back up Configuration File
To prevent damage to the configuration information, the configuration information can be backed up. The backup operation can be implemented with the c o p y command.
ZXR10#copy ? flash: Copy from flash: file system ftp: tftp: Copy from ftp: file system Copy from tftp: file system
ZXR10#copy
The following command can be used to back up a configuration file in the FLASH to the backup TFTP Server:
ZXR10#copy flash: /cfg/startrun. dat tftp: //168. 1. 1.
1/startrun. dat
3.
Recover Configuration File The following command can be used to recover a configuration file in the FLASH from the background TFTP Server:
ZXR10#copy
tftp:
//168.
1.
1.
1/startrun.
dat
flash:
/cfg/startrun. dat
4.
Version Backup Version backup is similar to configuration file backup. Use the copy command to copy the foreground version to the background server. Here is an example:
ZXR10#copy
flash:
/img/zxr10gar.zar
tftp:
//168.
1.
1.
1/zxr10gar.zar
5.
Version Recovery Version recovery is used to retransmit the background backup version to the foreground in FTP or TFTP mode. In the operation upon upgrading failure, this step is very necessary. Procedures of version recovery are basically the same as version upgrade (refer to Software Version Upgrading).
Software Version Upgrading

Normally, version upgrading is needed only when the original version fails to support some functions or the equipment cannot run normally due to some special reasons. If version-upgrading operations are not performed properly, upgrading failure may occur or the system may even break down. Therefore, before version upgrading, the maintenance personnel should be familiar with the principles and operations of the ZXR10 GAR and learn the upgrading procedures strictly.
Version Upgrading upon Abnormal System

When a router fails to start or run normally, detailed version upgrading procedures are as follows. 1. Connect the ZXR10 GARs console port (COM port on BIC board) to the serial interface of the background host with a console cable attached to the router; connect the management Ethernet port (10/100M Ethernet port on the BIC) to the background hosts network port with a straight through Ethernet cable. Set the IP address of the background host for upgrade to be in the network segment same as the routers management Ethernet port. Start the background FTP server (refer to FTP/TFTP Configuration). Reboot the ZXR10 GAR, and press any key according to the prompt in a HyperTerminal session to enter the Boot state. The result is displayed as below:
2. 3. 4.
ZXR10 GAR BOOT 2. 6b Copyright (c) 2003 by nanjing institute of ZTE, Inc. Compiled Sep 6 2005, 16:37:16 NPM12 processor with 262114/8192K bytes of memory Serial number 1073 2 [GAR Boot]:
Type C in the Boot state, and press ENTER to enter the parameter modification state. Change the boot mode to booting from the background FTP, change the FTP server address to that of the background host, change the client and gateway addresses to that of the management Ethernet port of the router, and then set the subnet mask and FTP user name and password. After the modification, the prompt ZXR10 Boot: appears.
[ZXR10 Boot]:c '. ' = clear field; '-' = go to previous field; ^D = quit Boot Location [0:Net,1:Flash]: 0 FLASH/* Client IP [0:bootp]: 168. 4.168. 168 to the management Ethernet address/* Netmask: 255.255. 0. 0 Server Gateway IP [0:bootp]: 168. 168. 4.168. 89 /*Corresponding /*The to the address of the background FTP Server/* IP: 4.168. 168 gateway address is the management Ethernet interface address/* /*Corresponding /*0 indicates booting from the background FTP, and 1 indicates booting from the
FTP FTP
User:
target Password:
/*Corresponding
to the FTP user name target/* /*Corresponding to the user password of target/* FTP Password Confirm: Boot Enable Enable Path: zxr10gar.zar */Use */Use Confirm: */Use the the the default value/* Password: Password default value/* default value/* [ZXR10 Boot]:
5.
Type @, and press ENTER. Then the system automatically boot from the background FTP server. Take the 72 router for example:
ZXR10 GAR BOOT 2. 6b Copyright (c) 2003 by nanjing institute of ZTE, Inc. Compiled Sep 6 2005, 16:37:16
NPM12 processor with 262114/8192K bytes of memory Serial number 1073
0 Boot Location [0:Net,1:Flash] : 0 Client IP [0:bootp] Netmask Server IP [0:bootp] Gateway IP FTP User FTP Password Boot Path Enable Password Serial Number : 168. 1. 86. 86 : 255.255. 0. 0 : 168. 1. 153. 153 : 168. 1. 86. 86 : debug1200 : : zxr10gar.zar : : 1073
Wait a while for loading the image: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . - Inflation: 11901 322 ===> 45952065 Maxium Memory : 42276 . . . . \[OK] Attached TCP/IP interface to lnPci unit 0 Attaching interface lo0. . . done -> slave not send Ack Inflation: 304222 ===> 2483177 Maxium Memory : 42448 Inflation: 694 ===> 1899 Maxium Memory : 42448 Inflation: 1096936 ===> 2660712 Maxium Memory : 42448 slave not send Ack Inflation: 491572 ===> 503028 Maxium Memory : 42448 slave not send Ack Inflation: 23820 ===> 41748 Maxium Memory : 42448 Inflation: 11510 ===> 22828 Maxium Memory : 42448 slave not send Ack slave not send Ack Inflation: 90902 ===> 90885 Maxium Memory : 42448 ZXR10 slave not send Ack fixed-tree. SUCCESS! Extract files in the destfile! Stop it (OK) Connect pseudoln97xInt,result = 0 clear TxBuffer clear RxBuffer Install New RxBuffer Apply the changes (OK)! Restart (OK) 0x3fa14a4 (tZxr10Main): Cn847x Hardware Revision: 0c driver module open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [ success ] driver . . . . . . . [ success ] initialize the profile. . . . . . . . . . . . . . . . . . module start. . . . . . . . . . . . . . . . . . . . . . . . . . IMG files merger . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . [ success ] fistElementIndex=0 SlotNo Device PortNums 2 4 6 8 LFEE LFET NONE LP3 8 2 0 1 State ------ ------ -------- --------------DEVICE_POWER_ON DEVICE_POWER_ON DEVICE_POWER_OFF DEVICE_POWER_ON
LFEE interface slotNo 2 initializing. . . . done LFET interface slotNo 4 initializing. . . . done LP3 interface slotNo 8 initializing. . . . done add Suni1x155 device slotNo 8. . . . . . . . [ success ] Ueng 0. . . . . . . . . . . . . . . LFEE. . . . . Mac:0 Port:1--4 Ueng 1. . . . . . . . . . . . . . . LFEE. . . . . Mac:0 Port:5--8 Ueng 2. . . . . . . . . . . . . . . LFET. . . . . Mac:1 Port:1--2 Ueng 3. . . . . . . . . . . . . . . LP3. . . . . . Mac:3 Port:1 <ixp1200_Init>loading success! <ixp1200_Init>loading success! <ixp1200_Init>loading MCode into uEngines . . . . . . . . . . . success! <ixp1200_Init>starting . . . . . . . . . . . success! [ROS10]:shell restarted. Start ZXR10 GAR Version V4. 6. 02. a Build at Sep 27 2005, 19:06:57 ********************************************************* Welcome Corporation ********************************************************* ZXR10> to ZXR10 General Access Router of ZTE uEngines MCode file2 from FLASH . . . . . MCode file1 from FLASH . . . . .
6.
If the system is booted successfully, you can use the s h o w v e r s i o n command to check whether the new version is running in the memory. If not, booting from the background server failed, then you must repeat steps 1 to 5.
7.
Delete the old version file (zxr10gar.zar) from the FLASH>IMG directory with the
d e l e t e command. If the FLASH has sufficient space, change the name of the old
version file and keep it in the FLASH. 8.
Copy the new version file on the background FTP server to the FLASH>IMG directory with the file name as zxr10gar.zar.
ftp: //168. 4.168.
ZXR10#copy
89/zxr10gar.zar@target:target flash: /img/zxr10gar.zar Starting copying file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . file copying successful. ZXR10#
9.
Check for the new version file in the FLASH. If not found, the copying failed, then you must repeat step 8 to copy the version again.
10. Restart GAR following Step 4, and change the start mode to FLASH start. In this case, Boot path will change to / f l a s h / i m g / z x r 1 0 g a r . z a r automatically. If the actual file name is not z x r 1 0 g a r . z a r , change the filename to z x r 1 0 g a r . z a r .
Note: You can also change the boot mode to booting form FLASH with the n v r a m i m g f i l e - l o c a t i o n l o c a l command in the Global Configuration mode.
11. Type @ at the prompt ZXR10 Boot: and press ENTER to boot the system with the new version in the FLASH. 12. When the system is booted successfully, check the running version to confirm the success of upgrade.
Version Upgrade Upon Normal System

If the router runs normally before upgrading, multiple version upgrading methods can be used. For example, use the router as the FTP/TFTP Client to copy the version file or implement remote upgrading via FTP. The local upgrade procedure is as follows when the router serve as an FTP client. 1. Connect the ZXR10 GARs console port (COM port on BIC board) to the serial interface of the background host with a console cable attached to the router; connect the management Ethernet port (10/100 M Ethernet port on BIC board) to the background hosts network port with a straight through network cable.
2.
Set the IP address of the background host for upgrade to be in the network segment same as that of the management Ethernet port on the router, so that the background host can ping the management Ethernet port. Start the background FTP server (refer to FTP/TFTP Configuration). View the running version. Delete the old version file from the FLASH>IMG directory with the d e l e t e command. If the FLASH has sufficient space, change the name of the old version file and keep it in the FLASH. Copy the new version file on the background FTP server to the FLASH>IMG directory with the file name of zxr10.zar.
ftp: //168. 4.168.
3. 4. 5.
6.
ZXR10#copy
89/zxr10gar.zar@target:target flash: /img/zxr10gar.zar Starting copying file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . file copying successful. ZXR10#
7. 8.
Check the new version file in the FLASH>IMG directory. If it is not found, indicating a copy failure, you need to repeat step 5 to copy the version again. When the system is rebooted successfully, check the running version to confirm the success of upgrade.
System Parameter Configuration

The section describes the configuration of system parameters of the ZXR10 GAR router, involving the configuration of host name and password used in the Privileged mode. 1. Set System Host Name
hostname network-name
By default, the host name of the system is ZXR10. The h o s t n a m e command can be used to change the host name in the Global Configuration mode. After the host name is changed, log on to the router again, and the new host name will be used in the system prompt. 2. Set the Greeting at Startup
Set the greeting with the b a n n e r i n c o m i n g command. The greeting begins and ends with a custom character. For example:
ZXR10(config)#banner incoming # Enter TEXT message. End with the character '#'. *********************************** Welcome to ZXR10 Router World *********************************** # ZXR10(config)#
3.
Set Password in Privileged Mode

enable secret 0 password|5 password|password
Users can set operation parameters in the Privileged mode, and enter the Configuration mode from the Privileged mode. To prevent an unauthorized user from modifying the configuration at will, users must configure a password used in the Privileged mode. 4. 5. Set Telnet User Name and Password
username <username> password <password>
Set System Time

clock set <current-time> <month> <day> <year>
Check System Information

On the ZXR10 GAR router, the s h o w command is used to check information. Here, how to check version information and configuration information will be described. 1. Show the software and hardware versions of the system
show version
Run the s h o w v e r s i o n command, and the following information is displayed:

ZXR10#show version ZXR10 Router Operating System Software, ZTE Corporation ZXR10 ROS Version V4. 6. 02. a ZXR10_GAR SOFTWARE Copyright (c) 2000-2005 by ZTE Corporation Compiled Sep 27 2005, 19:06:57 System image files from net <ftp://168. 1. 153. 153/zxr10gar.zar> System uptime is 0 days, 0 hours, 2 minutes [MP] Software, Version V2. 6. 02. a, RELEASE
Main
processor:
StrongArm
Processor
with
256M
bytes
of
memory 8K bytes of non-volatile configuration memory 64M bytes of processor board System flash (Read/Write) ROM: System Bootstrap, Version: ZXR10 GAR BOOT 2. 6b ,RELEASE SOFTWARE System serial: 1073 FPGA Version :V16 CPLD Version :V17 (SLOT 2) FPGA Version :V23 CPLD Version :V17 (SLOT 3) CPLD Version :V18 (SLOT 4) FPGA Version :V23 CPLD Version :V16 (SLOT 8) FPGA Version :V17 CPLD Version :V17
2.
Display the running configuration

show running-config
System Recovery
Implement r e l o a d to recover and reboot the whole rack. This command can automatically run in the Privileged mode, in which case the system will prompt whether to restart. After the user confirmation of restart, the system recovers.
Chapter
The chapter details multiple types of interfaces on a ZXR10 GAR router and their configurations, and also provides examples for interconnection of the routers with other equipment.
Interface Types
There are two kinds of interfaces on the router: Physical and logic interfaces. The physical interface is a kind of real interface, such as LAN Ethernet interfaces , WAN POS, ATM and E1 interfaces. The logic interface is created through configuration, therefore it is the virtual interface, such as E1 sub-interfaces and Loopback interfaces.
Interface Naming Rules

The ZXR10 GAR names ports as follows: 1. Naming the physical interface: <Interface type>_<Slot ID>/<Port ID>. <Subinterface or channel ID>
< I n t e r f a c e t y p e > covers the following types: <Interface type> Fei Gei pos3 Serial hserial fxs, fxo, e1vi, e1ve ce1 ct1 Corresponding Physical Interfaces Fast Ethernet Interface Gigabit Ethernet interface 155M POS interface Synchronous or asynchronous serial interface High-speed synchronous or asynchronous serial interface Voice interface E1 interface T1 interface
fei gei pos3 ce1 ct1
Fast Ethernet Interface Gigabit Ethernet interface 155M POS interface E1 interface T1 interface
serial hserial fei_0 loopback multilink
Synchronous or asynchronous serial interface High-speed synchronous or asynchronous serial interface Voice interface Main control board management Ethernet interface Loopback interface Multi E1 link bundling interface
fxs, fxo, e1vi, e1ve
< S l o t I D > : Depends upon physical slots where the line interface modules are installed, ranging from 1 to 8. < P o r t I D > : Refers to numbers allocated to the line interface module connectors. The value range and assignment of port IDs vary depending upon different types of line interface modules. <Sub-interface or channel channelized E1 interfaces I D > : Sub-interface IDs or channel IDs o f
2.
Logic interface naming mode: < I n t e r f a c e t y p e > < S u b - i n t e r f a c e >

< I n t e r f a c e t y p e > covers the following types:
<Interface type> loopback fei_0 multilink
Corresponding Logic Interface Loopback interface Main control interface board management Ethernet
Multi-link interface
< S u b - i n t e r f a c e I D > : IDs of sub-interfaces
Examples of naming interfaces: gei_1/1 board at slot 1 pos3_4/1 slot 4 fei_2/8 2 Indicates the first interface on the Gigabit Ethernet interface Indicates the first interface on the 155M POS interface board at Indicates the eighth interface on the fast Ethernet interface board at slot
ce1_1/1.2 Indicates the second channel on the first interface on the E1 interface board at slot 1 fei_0/1 loopback2 of 2. Indicates 100/100M Ethernet interfaces on the front panel Indicates interfaces with the interface type of loopback and the number
Checking Interface Information

The ZXR10 router supports commands of checking interface status and information.
show ip interface [brief] [<interface-number>]
Ethernet Interface Configuration

Ethernet interfaces of the ZXR10 router are divided into fast Ethernet interfaces and Gigabit Ethernet interfaces. Fast Ethernet interfaces can work at a rate of 10M or 100M, which support full duplex and semi-duplex modes and auto negotiation. The auto negotiation mode is applied by default. The operational mode of Gigabit Ethernet interfaces is set to auto negotiation mode by default. The working speed is 1000M and the duplex mode is full duplex.
Configurations of Ethernet Interfaces

The configuration of Ethernet interfaces covers the following contents. 1. 2. 3. 4. 5. Enter the Interface Configuration Mode
interface <interface-name>
Configure the IP Address

ip address <ip-addr> <net-mask> [<broadcast-addr>] [<secondary>]
Configure working speed of interfaces in the non-automatic negotiation mode

speed {10 | 100 }
Configure the duplex mode of interfaces in the non-automatic negotiation mode

duplex { half | full}
Configure the automatic negotiation mode of interfaces

negotiation auto
Note: Configurations of working speed and duplex mode are only applicable to fast Ethernet interfaces, and the negotiation mode is only applicable to Gigabit Ethernet interfaces.
Examples for Ethernet Interface Configuration

1. Example 1 for fast Ethernet interfaces As shown in Figure 64, the fei_1/2 interface on ZXR10 router has been connected to the et.2. 1 interface on ZXR10 routing switch.
F I G U R E 6 4 E X AM P L E 1 F O R E T H E R N E T I N T E R F A C E C O N F I G U R AT I O N
Configuration of ZXR10 router:

ZXR10(config)#interface fei_1/2 ZXR10(config-if)#ip address 10. 1. 1.2 255.255.255.252 ZXR10(config-if)# no negotiation auto ZXR10(config-if)#duplex full ZXR10(config-if)#speed 100
Configuration of ZXR10 routing switch:

ZXR10(config)#interface create ip to-router address-
netmask 10. 1. 1. 1/30 port et.2. 1 ZXR10(config)#port set et.2. 1 speed 100mbps duplex full
2.
Example 2 for fast Ethernet interface interconnection As shown in Figure 65, the fei_1/2 interface of a ZXR10 router is connected to the fast Ethernet 0/26 interface of a piece of CISCO equipment.
F I G U R E 6 5 E T H E R N E T I N T E R F A C E I N T E R C O N N E C T I O N E X AM P L E 2
ZXR10 configuration:
ZXR10(config)#interface fei_1/2 ZXR10(config-if)#ip address 10. 1. 1.2 255.255.255.252 ZXR10(config-if)# no negotiation auto ZXR10(config-if)#duplex full
Configuration of CISCO equipment:

CISCO(config)#interface fastethern 0/1 CISCO(config-if)#ip address 10. 1. 1. 1 255.255.255.252 CISCO(config-if)#duplex full
POS Interface Configuration

POS refers to Packet Over SONET, and is also called IP Over SONET (SDH). POS directly transfers IP sub-packets on high-speed transmission paths provided by SDH. Normally, a POS network consists of high-end routers and high-speed fibers. SONET/SDH is a physical layer protocol, which transfers bit streams over channels. Normally, PPP serves as the L2 encapsulation protocol. The POS interface of ZXR10 GAR is POS 155M interface. As configuring it, the default encapsulation type is set to PPP.
Configuration of POS Interface

The configuration of POS 155M interface covers the following contents: 1. 2. 3. 4. Enter the Interface Configuration mode
Configure the IP address of the interface

Configure crc mode

crc {16 | 32}
Configure clock extraction mode clock source { internal | line }
Examples for POS Interface Configuration

1. Examples for POS interface configuration As shown in Figure 66 oc3_4/4 interface of the router is connected with so. 13. 1 interface of the routing switch.
F I G U R E 6 6 P O S C O N F I G U R AT I O N E X AM P L E 1

ZXR10(config)#interface oc3_4/4 ZXR10(config-if)#ip 255.255.255.252 ZXR10(config-if)#crc 32 address 192. 168. 1. 1
Configuration of ZXR10 routing switch:

ZXR10(config)#sonet set so. 13. 1 framing sdh ZXR10(config)#port set so. 13. 1 mtu 1500 ZXR10(config)#interface create ip pos1 address-netmask 192. 168. 1.2/30 port so. 13. 1 ZXR10(config)#sonet set so. 13. 1 s1s0 2 ZXR10(config)#sonet set so. 13. 1 c2 22 ZXR10(config)#sonet set so. 13. 1 payload-scramble on
2.
Example 2 for POS interface interconnection As shown in Figure 67, the oc3_4/4 interface of a ZXR10 router is connected to the pos1/0 interface of a piece of CISCO equipment.
F I G U R E 6 7 P O S C O N F I G U R AT I O N E X A M P L E 2
ZXR10(config)#interface oc3_4/4 ZXR10(config-if)#ip 255.255.255.252 ZXR10(config-if)#crc 32 ZXR10(config-if)#clock source line address 192. 168. 1. 1

CISCO(config)#interface pos1/0 CISCO(config-if)#pos framing sdh CISCO(config-if)#clock source line CISCO(config-if)#ip address 20. 11. 11.21 255.255.255. 0 CISCO(config-if)#no ip directed-broadcast CISCO(config-if)#encapsulation ppp CISCO(config-if)#crc 32 CISCO(config-if)#mtu 1500 CISCO(config-if)#pos scramble-atm CISCO(config-if)#pos flag c2 22 s1s0 2 CISCO(config-if)#no shutdown
E1 Interface Configuration
Being broadly adopted by European countries and China, the E1 interface works in two modes: Non-channelized working mode and channelized working mode. When an E1 interface works in the non-channelized mode, it is equivalent to an interface with a data bandwidth of 2. 048Mbps without timeslot division. Its logic features are similar to those of a synchronous serial interface. It supports data link layer protocols (such as PPP, frame relay, LAPB and X.25) and network protocols (such as IP and IPX). When an E1 interface works in the channelized mode, it is physically divided into 32 timeslots (corresponding to numbers 0 to 31). The bandwidth of each timeslot is 64Kbps. Where, Timeslot 0 is used to transmit synchronous information. Except Timeslot 0, all the other timeslots can be bound into groups. Each group of timeslots can serve as a sub-interface whose logic features are also equivalent to those of a synchronous serial interface. An E1 interface can be divided into a maximum of 31 sub-interfaces.
Configuration of E1 Interfaces
The E1 interface configuration covers the following contents. 1. 2. 3. Enter the E1 controller configuration mode
controller <interface-name>
Configure the framing mode

framing {unframe | frame}
Configure E1 channel (for channelized E1)

channel-group <channel-number> timeslots <timeslots>
4. 5. 6.
Enter the Interface Configuration mode

Configure Layer-2 protocol encapsulation of the interface

encapsulation {ppp | hdlc | frame-relay }
Configure the IP address of interface

Note: When two routers are connected via E1 interfaces, parameters of these interfaces must keep in consistence: Timeslot, framing, line code (HDB3 by default), CRC (32 by default), Layer-2 encapsulation protocol, and synchronous clock.
Examples for E1 Interface Configuration

1. Examples for E1 configuration under the framing format
As shown in Figure 68, the E1 interface of a ZXR10 router is interconnected with the E1 interface of a remote CISCO router. The channelized configuration and timeslots 1 to 10 are used in this case. The L2 WAN encapsulation protocol is PPP, the default linecode is HDB3, the framing format is crc32, and the clock mode is internal.
FIGURE 68 CHANNELIZED E1 CONFIGURATION EXAMP LE
ZXR10(config)# controller ce1_1/2 ZXR10(config-control)# channel-group 1 timeslots 1-10 ZXR10(config-control)# exit ZXR10(config)# interface ce1_1/2. 1 ZXR10(config-if)# encapsulation ppp ZXR10(config-if)# 255.255.255.252 ip address 192. 168.2. 1
Note: To implement synchronization on the entire network, a clock can be extracted from one of the E1 interfaces to serve as the reference clock of the local rack. Carry out the r e f e r e n c e c l o c k command in the Global Configuration mode.

CISCO(config)#controller e1 1/0 CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config-controller)#channel-group 0 timeslots 1-10 CISCO(config)#interface serial 1/0:0 CISCO(config-if)#encapsulation ppp CISCO(config-if)#ip address 192. 168.2.2 255.255.255.252
2.
Examples for E1 configuration under the non-framing format As shown in, the E1 interface of a ZXR10 router is interconnected with the E1 interface of a remote CISCO router. The non-channelized configuration is used, and PPP serves as the L2 WAN encapsulation protocol.
F I G U R E 6 9 E X AM P L E F O R N O N - C H AN N E L I Z E D E 1 C O N F I G U R A T I O N
ZXR10(config)#controller ce1_1/1 ZXR10(config-control)#framing unframe ZXR10(config-control)#exit ZXR10(config)#interface ce1_1/1. 1 ZXR10(config-if)#encapsulation ppp ZXR10(config-if)#ip 255.255.255.252 address 192. 168. 1. 1
Note: When an E1 interface is set to the non-channelized mode, its interface name is e1_slot ID/interface ID. 1, such as e1_1/1. 1.

CISCO(config)#controller E1 2/0/0 CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config-controller)#channel-group 0 unframed CISCO(config)#interface serial 2/0/0:0 CISCO(config-if)#encapsulation ppp CISCO(config-if)#ip address 192. 168. 1.2 255.255.255.252
T1 Interface Configurations
Being a kind of interface available for channelization, the T1 interface multiplexes 24 timeslots with each of them divided into 8 bits and frame length of 193 bits. There are 8 K frame data on a T1 channel in a second; therefore, its baud rate is 1.544Mbps. The baud rate of a timeslot is 64Kbps. Thus, 24 channels at the most can be divided on a T1 interface. Each of these channels acts as an interface that can be configured with an IP address and encapsulate multiple protocols such as peer-to-peer protocol, HDLC, X.25 or frame trunk protocol. As for customer requirements for bandwidth larger than 1.544M, a logic link can be created through the multi-link PPP protocol, bundling multiple T1 interfaces.
T1 Interface Configuration
The E1 interface configuration covers the following contents. 1. Enter the T1 controller configuration mode
2. 3. 4. 5. 6. 7. 8.
Configure the framing mode

Configure T1 channel (for channelized T1s)

Configure the cable-length type

cable-length {long| short}
Configure the linecode type

linecode {ami|b8zs}
Enter the interface configuration mode

Configure layer-2 protocol encapsulation of the interface

Configure the IP address of interface

Note: When two routers are connected via T1 interfaces, parameters of these interfaces must keep in consistence: Timeslot, framing, line code (B8ZS by default), CRC (32 by default), Layer-2 encapsulation protocol, and synchronous clock.
Examples for E1 Interface Configuration

1. Examples for channelized T1 configuration As shown in Figure 70, two GAR routers are connected via T1 interfaces. In this case, it uses the channelized configuration mode with 1 to 10 timeslots, PPP protocol as its L2 WAN encapsulation protocol, line code of b8zs, and clock mode of line by default.
F I G U R E 7 0 E X AM P L E F O R N O N - C H AN N E L I Z E D T 1 C O N F I G U R A T I O N
GAR1 configuration (same as GAR2 configuration):

ZXR10(config)# controller ct1_1/1 ZXR10(config-control)# frame frame ZXR10(config-control)# channel-group 1 timeslots 1-10 ZXR10(config-control)# exit
ZXR10(config)# interface ct1_1/1. 1 ZXR10(config-if)# encapsulation ppp ZXR10(config-if)# 0 ip address 192. 168. 1. 1 255.255.255.
Note: To implement synchronization on the entire network, a clock can be extracted from one of the T1 interfaces to serve as the reference clock of the local rack. Carry out the r e f e r e n c e c l o c k command in the Global Configuration mode.
2.
Example for non-channelized T1 configuration As shown in Figure 71, two GAR routers are connected via T1 interfaces. In this case, it uses the channelized configuration mode with 1 to 10 timeslots and PPP protocol as its L2 WAN encapsulation protocol.
F I G U R E 7 1 E X AM P L E F O R N O N - C H AN N E L I Z E D T 1 C O N F I G U R A T I O N

ZXR10(config)#controller ct1_1/1 ZXR10(config-control)#framing unframe ZXR10(config-control)#exit ZXR10(config)#interface ct1_1/1. 1 ZXR10(config-if)#encapsulation ppp ZXR10(config-if)#ip address 192. 168. 1. 1 255.255.255. 0
Note: When a T1 interface is set to non-channelized mode, its interface name is ct1_slot ID/interface ID. 1, such as ct1_1/1. 1.

CISCO(config)#controller E1 2/0/0 CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config-controller)#channel-group 0 unframed CISCO(config)#interface serial 2/0/0:0 CISCO(config-if)#encapsulation ppp CISCO(config-if)#ip address 192. 168. 1.2 255.255.255.252

Synchronous/asynchronous serial interfaces on ZXR10 routers support two physical layer protocols: V35 and V24. Proper hardware jumpers can be used to change the working mode of the interface. Jumpers corresponding to each interface are listed as follows: Interface 1 corresponds to X6, X7, X8, X28, X29, X30 Interface 2 corresponds to X9, X10, X11, X12, X13, X14 Interface 3 corresponds to X15, X16, X17, X18, X19, X20 Interface 4 corresponds to X21, X22, X23, X24, X25, X26 In case the interface works in the mode of V24, all the jumpers corresponding to this interface should be shorted with 1 to 2 pins, but 2 to 3 pins in the case of V35 mode. The digital switch of interfaces in the mode of V24 is OFF but is ON in the mode of V35. Synchronous/asynchronous serial interfaces support encapsulation of PPP, frame-relay and HDLC protocols and running of dynamic routing protocols. Parameters of the interfaces are listed in Table 86.
T A B L E 8 6 P AR A M E T E R S O F S Y N C H R O N O U S / A S Y N C H R O N O U S S E R I AL I N T E R F A C E S
Parameter Encapsulation protocol
Scope ppp, hdlc, frame-relay
Default PPP
Baud rate of V24 asynchronous 300, 1200, 2400, 4800, 9600, 19200, 9600bps serial interfaces 38400, 57600 Baud rate of low-speed synchronous serial interfaces Baud rate of low-speed synchronous serial interfaces Baud rate of high-speed synchronous serial interfaces V24 1200, 2400, 4800, 9600, 19200, 9600bps 38400 V35 Rate: N*64kbps (N=1~10) V35 Rate: N*64kbps (N=1~32) 64kbps 64kbps
There are two kinds of asynchronous serial interfaces: Synchronous/asynchronous serial interfaces in the mode of asynchronous serial interface mode and specific interfaces called as Async. The asynchronous serial interfaces support both private line and dialling modes, and SLIP or PPP link layer protocol. An ISDN TA or Modem needs to be externally installed in the case of dialling mode.

The configuration of synchronous/asynchronous serial interfaces covers the following contents. 1. 2. Enter the interface mode of synchronous/asynchronous serial interfaces
Configure the working mode of synchronous/asynchronous serial interfaces (for V24 interfaces)
physical-layer mode {sync | async}
3. 4. 5.
Configure the working mode of synchronous serial interfaces Set the working mode of synchronous serial interface as DCE
dce enable
Set the working mode of synchronous serial interface as DTE

dte enable
Set baud rate

baudrate <baudrate>
Configure L2 protocol encapsulation

Examples for Synchronous/Asynchronous Serial Interface Configuration

Example 1: Configure a 640kbps high-speed V35 synchronous serial interface with its working mode as dte and L2 encapsulation protocol as PPP.
ZXR10(config)# interface hserial_4/1 ZXR10(config-if)# dte enable ZXR10(config-if)# baudrate 640000 ZXR10(config-if)# encapsulation ppp
Example 2: Configure a 38400bps low-speed V24 synchronous serial interface with its working mode as dte and L2 encapsulation protocol as FR.
ZXR10(config)# interface serial_4/1 ZXR10(config-if)# physical-layer mode sync ZXR10(config-if)# dte enable ZXR10(config-if)# baudrate 38400 ZXR10(config-if)# encapsulation frame-relay
Example 3: Configure a 57600bps high-speed V24 asynchronous serial interface with the L2 encapsulation protocol of PPP.
ZXR10(config)#interface hserial_4/1 ZXR10(config-if)#physical-layer mode async ZXR10(config-if)#baudrate 57600 ZXR10(config-if)#encapsulation ppp

Voice interfaces on the ZXR10 router implement conversion from analogue telephone voice signals to the PCM digital signals. And the TDM bus implements the following functions: Digital signal conversion of VoIP circuits, ringing, ring interception, creating hang-up signals and providing feeder of client telephone sets. These voice interfaces comply with the ITU Q.512 recommendation and provide protections from overvoltage, overcurrent and lightning. Voice interfaces supported by the general access routers are FXS, FXO and E1VI. 1. FXS (Foreign eXchange Station) interfaces support standard RJ-11 telephone cables for direct connection with common telephone sets, fax machines, and Private Branch Exchange (PBX). In this mode, signaling interchange, ringing, voltage and dialing tones are provided through level changes of Tip and Ring cables. FXO (Foreign eXchange Office) is the 2-wire loop trunk. It supports RJ-11 telephone cables for connection of local calls with PSTN central office or PBX. In this mode, signalling interchange is provided through level changes of Tip and Ring cables. Devices connected to the FXO interfaces can only connect devices with FXS interfaces. E1VI (E1 Voice Interface) module acts as the E1 trunk for connecting the switch. It is to process dense signals in the VoIP system. It implements the VoIP functions on E1 lines, realizes voice transmission mode compatible with data transmission mode. This module provide an E1 interface for users to process 30 routes of voice signals.
2.
3.

The voice interface configuration covers the following contents. 1. 2. 3. 4. Create or enter the dial-up peer configuration mode
dial-peer voice <peer-num> <voip-type>
Configure the dial-up peer target mode

destination-pattern <phone-num>
Associate a dial-up peer of POTS type to a designated voice interface

port <voiceport-num>
Enter E1VI controller configuration mode
5.
Configure ds0 group first to implement R2 signalling configuration

ds0-group <group-number> timeslots digital ][r2-compelled ][ani] <timeslots-list >[type r2-
6. 7. 8.
Configure the VoIP dial-up peer of RAS type

session target ras
Configure the VoIP dial-up peer of the designated network address

session target ipv4: destination-address
Configure the voice coding mode of a dial-up peer

codec {g711alaw|g711ulaw|g7231|g729}
Examples for Voice Interface Configuration

1. Configuration examples of the pots-type interfaces Set the first interface on the FXS voice interface board in Slot 5 to 5001. The detailed configuration is as follows:
ZXR10(config)#dial-peer voice 1 pots ZXR10(config-pots5001)# destination-pattern 5001 ZXR10(config-pots5001)#port fxs_5/1
Set the first interface on the FXO voice interface board in Slot 5 to 5002. The detailed configuration is as follows:
ZXR10(config)#dial-peer voice 2 pots ZXR10(config-pots5001)# destination-pattern 5002 ZXR10(config-pots5001)#port fxo_5/1
Set the E1V1 voice interface board in Slot 5 to 5001. The detailed configuration is as follows:
ZXR10(config)#dial-peer voice 10 pots ZXR10(config-pots5001)# destination-pattern 5003 ZXR10(config-pots5001)#port e1vi_5/1. 1
2.
Examples for configuration of VoIP type interfaces Configure the dial-up peer of VoIP type. As shown in Figure 72, check if the peer end satisfies the following conditions: Office direction of 020, IP address of 168. 1. 1. 10, line code of g7231, and the router connecting the local PBX via the E1 trunk.
F I G U R E 7 2 E X AM P L E 1 F O R V O I P I N T E R F A C E C O N F I G U R AT I O N
If yes, configuration of the local router is:

ZXR10(config)# dial-peer voice 20 voip ZXR10(config-voip20)# destination-pattern 020. . . . ZXR10(config-voip20)#codec g7231 ZXR10(config-voip20)# session target ipv4: 168. 1. 1. 10
Configuration of the remote router is:

ZXR10(config)# dial-peer voice 10 voip ZXR10(config-voip20)# destination-pattern 020. . . . ZXR10(config-voip20)#port e1vi_1/1. 1 ZXR10(config)# dial-peer voice 20 voip ZXR10(config-voip20)# destination-pattern 025. . . . ZXR10(config-voip20)#codec g7231 ZXR10(config-voip20)# session target ipv4: 168. 1. 1. 9 ZXR10(config)# dial-peer voice 10 voip
Configure the dial-up peer of VoIP type. As shown in Figure 73, check if the peer end satisfies the following conditions: Office direction of 025, IP calling type of this dial-up peer as RAS, line code of g7231, address of gatekeeper zte-gk as168. 1. 1. 1, and the router connecting the local PBX via the FOX analog trunk.
F I G U R E 7 3 E X AM P L E 2 F O R V O I P I N T E R F A C E C O N F I G U R AT I O N
If yes, configuration of the local router is:

ZXR10(config)#intface fei_1/1 ZXR10 ZXR10 ZXR10 168. ZXR10 (config-if)# (config-if)# (config-if)# 1. 1. 1 h323-gateway h323-gateway h323-gateway name voip voip id IP gw-id ztegw1 /*Configure alias of gateway*/ interface ztegk address ipaddr of GK /*Configure interface as H. 323 gateway interface */ voip and voip /*Configure
Server*/ (config-if)# h323-gateway techprefix /*Configure 010 to /*Configure technical prefix of gateway*/ ZXR10(config)# gateway entable GK Client*/ ZXR10(config)# dial-peer voice 20 voip ZXR10(config-voip20)# destination-pattern 025. . . . ZXR10(config-voip20)#codec g7231 ZXR10(config-voip20)# session target ras
Configuration of the remote router is:

ZXR10(config-voip20)# session target ras ZXR10(config)#dial-peer voice 10 pots ZXR10(config-pots10)# destination-pattern 025. . . . ZXR10(config-pots10)#port fxo_1/1 ZXR10(config)#intface fei_1/1 ZXR10 ZXR10 ZXR10 168. ZXR10 (config-if)# (config-if)# (config-if)# 1. 1. 1 h323-gateway h323-gateway h323-gateway name voip voip id IP gw-id ztegw2 /*Configure alias of gateway*/ interface zte-gk address ipaddr of GK /*Configure interface as H. 323 gateway interface */ voip and voip /*Configure
Server*/ (config-if)# h323-gateway techprefix /*Configure 025 to /*Configure technical prefix of gateway*/ ZXR10(config)# gateway enable GK Client*/ ZXR10(config)# dial-peer voice 30 voip ZXR10(config-voip20)# destination-pattern 010. . . . ZXR10(config-voip20)#codec g7231

TDMoIP interfaces implement transmission of time division multiplexing data via IP networks (networks for packet switching). It considers the IP network as the network inserted into the traditional TDM network and seamlessly connected to existing equipment such as traditional client telephone exchange. The IP network can provide multiple services same as that of traditional telephone and guarantee the service quality in the same way as PSTN. TDMoIP transparently transfers TDM frames without transmission interruption, explanation and translation of data. Even in the case that part of the channels is used for data transmission or that all of the frames are instructed bit streams, TDMoIP supports transmission of any T1 or E1 service. It is very easy for basic TDMoIP concepts to extend to part of T1 system of channelized E1 system. To alleviate traffic flow load, only the information bearing bytes need to obtain IP packets. Methods for TDMoIP processing signaling in the IP and telephone networks: Since the in-band signaling is adopted by TDMoIP, signaling and tones are transferred within the same video segment. The TDMoIP will automatically transfer the calling process of the coding in the TDM timeslot, and it adopts the voice trunk protocol to ensure normal implementation of in-band signalling functions. TDMoIP enables all the voice and data services executed on T1 or E1 lines to be automatically supported by IP networks. These services include PSTN access, primary service, centralized client switching, VoIP voice services, ATM frame trunk and pointto-point protocol (PPP).

The TDMoIP interface configuration covers the following contents. 1. 2. Create or enter the context slot configuration mode
context slot <slot-num> index <index-num>
Configure the IP address and interface

ip <Source IP address>< Source UDP port address>< Destination UDP port number> number>< Destination IP
3. 4. 5. 6. 7.
Configure timeslot of context

time-slots interface <tdmoip-interfacename> <timeslots-num>
Configure ip precedence field in packets

ip precedence <precedence-value>
Configure ip dscp field in packets

ip dscp <dscp-value>
Configure ip tos field in packets

ip tos <tos-value>
Configure the jitter buffer of context

Jitter buffer {enable | disable | size <size> }
8. 9.
Configure the maximum frame length of this context

max-frames <length>
Configure the clock synchronization

cet slot <slot-num> clock { adaptive | local }
10. Configure the clock synchronization function of this context

clock-adaptive { enable| disable }
Examples for TDMoIP Interface Configuration

As shown in Figure 74, two PBXs are connected via GARs in the trunk mode, contexts to the peer ends are created on two GARs, and timeslot and IP addresses are configured.
FIGURE 74 TDMOIP INTERFACE CONFIGURATION EXAMP LE
The detailed configuration of GAR1 is as follows:

Gar1#conf t Gar1(config)#interface tdm-fei_8/5 Gar1(config-if)#ip add 1. 1. 1. 1 255.255.255. 0 Gar1(config-if)#end Gar1(config)#context slot 8 index 1 Gar1(tdm-context_8/1)#ip 1. 1. 1. 1 5000 1. 1. 1.2 5200 Gar1(tdm-context_8/1)#time-slots 32 interface tdm-e1_8/1 1-
The detailed configuration of GAR2 is as follows:

Gar2#conf t Gar2(config)#interface tdm-fei_8/5 Gar2(config-if)#ip add 1. 1. 1.2 255.255.255. 0 Gar2(config-if)#end
Gar2(config)#context slot 8 index 1 Gar2(tdm-context_8/1)#ip 1. 1. 1.2 5200 1. 1. 1. 1 5000 Gar2(tdm-context_8/1)#time-slots 32 interface tdm-e1_8/1 1-
Configure the corresponding E1 trunk on the remote switch with the coding mode of hdb3.
VLAN Sub-interface Configuration

ZXR10 routers can utilize the VLAN trunk and sub-interface technologies to provide inter-VLAN routes. When a router is connected to a switch configured with multiple VLANs through a trunk line, interfaces on the router connected to the switch should be set to the trunk mode, and the corresponding interfaces on the switch should also be set to the trunk mode. To terminate different VLANs on the switch, multiple logic subinterfaces should be created on the physical interface of the router. The sub-interfaces correspond to the VLANs on the switch one by one via VLAN IDs. The ZXR10 router supports standard 802. 1Q VLAN trunk protocol. The Ethernet interfaces of the ZXR10 router support VLAN sub-interface functions.
Configuration of VLAN Sub-Interfaces

The configuration of VLAN sub-interfaces covers the following contents. 1. 2. Create sub-interface configuration and enter the sub-interface configuration mode
Encapsulae VLAN-ID
encapsulation dot1Q <vlan-id>
The function of VLAN-ID encapsulation is to assign the sub-interface to the corresponding VLAN so that each sub-interface corresponds to different VLAN IDs. 3. Assign an IP address to the sub-interface
Examples for VLAN Sub-Interface Configuration

In the following configuration example, the VLAN sub-interface technology is applied to implement the access and routing of different VLAN users on the same physical Ethernet interface. As shown in Figure 75, the fei_1/3 interface of a ZXR10 router is connected to port 10 of a ZXR10 3904 switch. Ports 2 and 3 of the ZXR10 3904 switch belong to VLAN100 and VLAN200 in turn, supporting two PCs.
F I G U R E 7 5 V L AN S U B - I N T E R F A C E C O N F I G U R A T I O N E X A M P L E

ZXR10(config)#interface fei_1/3. 100 ZXR10(config-subif)# encapsulation dot1q 100 ZXR10(config-subif)#ip 255.255.255.192 ZXR10(config)#interface fei_1/3. 101 ZXR10(config-subif)# encapsulation dot1q 200 ZXR10(config-subif)#ip 255.255.255.192 address 10. 40. 50. 65 address 10. 40. 50. 1
Configuration of ZXR10 3904 switch:

ZXR10-3904(bridge)# set vlan create br100 100 ZXR10-3904(bridge)# set vlan create br200 200 ZXR10-3904(bridge)# set vlan del br1 2-3,10 ZXR10-3904(bridge)# set vlan add br100 2 untagged ZXR10-3904(bridge)# set vlan add br100 10 tagged ZXR10-3904(bridge)# set vlan add br200 3 untagged ZXR10-3904(bridge)# set vlan add br200 10 tagged ZXR10-3904(bridge)# set vlan pvid 2 100 ZXR10-3904(bridge)# set vlan pvid 3 200 ZXR10-3904(config)#interface br100 ZXR10-3904(config-if)#no shutdown ZXR10-3904(config)#interface br200 ZXR10-3904(config-if)#no shutdown
Multilink Configuration
To increase the bandwidth, multiple physical links can be bound into a logic link, and the logic interface generated in this way is called multilink interface. In the ZXR10 router, a multilink interface can be bound with a maximum of eight E1 interfaces.
Basic Multilink Configuration

The multilink configuration covers the following contents. 1. 2. 3. 4. 5. Create a multilink interface and enter the Interface Configuration mode
Assign an IP address to the multilink interface

Bind physical links

multilink-group <multilink-num>
Multilink fragmentation
ppp multilink fragmentation
Configure the end point string of the multilink

ppp multilink endpoint string <string>
Examples for Multilink Configuration

As shown in Figure 76, a ZXR10 router is interconnected to non-channelized E1 interfaces of a piece of CISCO equipment in a binding manner. PPP serves as the L2 WAN encapsulation protocol.
F I G U R E 7 6 M U L T I L I N K C O N F I G U R AT I O N E X A M P L E
ZXR10(config)#interface multilink1 ZXR10(config-if)#ip address 192. 168. 255.255.255.252 ZXR10(config)#controller ce1_8/1 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/1. 1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/2 ZXR10(config-controller)#framing unframe
1.
ZXR10(config)#interface ce1_8/2. 1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/3 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/3. 1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/4 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/4.1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/5 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/5.1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/6 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/6. 1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/7 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/7. 1 ZXR10(config-if)#multilink-group multilink1 ZXR10(config)#controller ce1_8/8 ZXR10(config-controller)#framing unframe ZXR10(config)#interface ce1_8/8. 1 ZXR10(config-if)#multilink-group multilink1

CISCO(config)#controller E1 1/0/0 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/1 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/2 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32
CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/3 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/4 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/5 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/6 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#controller E1 1/0/7 CISCO(config-controller)#channel-group 0 unframed CISCO(config-controller)#framing crc32 CISCO(config-controller)#linecode hdb3 CISCO(config)#interface multilink1 CISCO(config-if)#ip address 192. 168. 1.2 255.255.255.252 CISCO(config-if)#ppp multilink CISCO(config-if)#no ppp multilink fragmentation CISCO(config-if)#multi-group 1 CISCO(config)#interface serial 1/0/0:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1 CISCO(config)#interface serial 1/0/1:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1
CISCO(config)#interface serial 1/0/2:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1 CISCO(config)#interface serial 1/0/3:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1 CISCO(config)interface serial 1/0/4:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1 CISCO(config)#interface serial 1/0/5:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1 CISCO(config)#interface serial 1/0/6:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1 CISCO(config)#interface serial 1/0/7:0 CISCO(config-if)#no ip address CISCO(config-if)#ip route-cache distributed
CISCO(config-if)#encapsulation ppp CISCO(config-if)#ppp authentication chap CISCO(config-if)#ppp multilink CISCO(config-if)#multilink-group 1
Note: In the case of default configuration of the end point, that of the E1 interface is the host name. If several multilinks are configured on a PC, E1 interfaces corresponding to different multilink interfaces must be configured with different end points. Otherwise, only the first multilink takes effect.
Chapter
Configuration of Link Protocols

This chapter describes the relative configurations of the PPP, FR, X.25 and HDLC link protocols on the ZXR10 GAR routers.
PPP
General Description of PPP
PPP (Point-to-Point Protocol) is a WAN protocol that has found wide application. The PPP has implemented point-to-point connection of router-to-router and host-tonetwork on different synchronous/asynchronous circuits. It provides a complete set of solutions to solve problems such as link setup, maintenance, clearance, upper-level protocol negotiation and authentication. The PPP covers the following parts: 1. LCP (Link Control Protocol) The LCP is responsible for creating, maintaining and terminating a physical connection. 2. NCP (Network Control Protocol) The NCP is a protocol suite responsible for the running of network protocols on the physical connection and clearing faults occurred to upper-level network protocols. 3. Authentication protocol: The most common authentication protocols are PAP (Password Authentication Protocol) and CHAP (Challenge-Handshake Authentication Protocol).
PAP and CHAP are normally used to provide security authentication on serial lines encapsulated in PPP mode. PAP uses the secondary handshake authentication, and the user name and password are transmitted on links in plain text. The PAP authentication process is as follows:
1. 2.
The authenticated party sends the user name and password to the authenticating party. The authenticating party checks whether this user is available and whether the password is correct according to the user configuration and then returns different responses.
CHAP is more secure than PAP. It uses tertiary handshake to authenticate the identity of the remote node periodically and uses a query message to prevent regenerated attacks. The PAP authentication process is as follows: 1. 2. The authenticating party sends some random reports to the party to be authenticated. The party to be authenticated uses his own password and MD5 algorithm to encrypt the random packets, and sends back the cipher text created to the authenticator. The authenticator uses the password and MD5 algorithm stored to encrypt the original random packets, compares the two cipher texts, and then gives different response according to the comparison result.
3.
Basic PPP Configuration

The PPP configuration covers the following contents. 1. 2. 3. 4. Select an interface to be configured and enter the Interface Configuration mode
Configure the IP address of the interface in the Interface Configuration mode

Configure PPP user authentication protocol

ppp authentication {pap|chap}
Configure user name and password used for authentication (different for PAP and CHAP) i. PAP mode: Configure the sent PAP user name and password when the local router is authenticated by the peer router in the PAP mode
ppp pap sent-username <username> password <password>
ii.
CHAP mode:
Configure the user name when the local router is authenticated by the peer router in the CHAP mode
ppp chap hostname <hostname>
Configure the password when the local router is authenticated by the peer router in the CHAP mode
ppp chap password <password>
5.
Take the initiative in setting up a PPP link with the peer router in the management mode
ppp open
Examples for PPP Configuration

As shown in Figure 77, the pos3_3/1 interface of router R1 is connected to that of router R2. The PPP is encapsulated and the CHAP authentication mode is used. The user name and password configured on each interface are used for local and remote authentication. The user names and passwords at both ends should be consistent with each other.
F I G U R E 7 7 P P P C O N F I G U R AT I O N E X A M P L E
R1 configuration:
ZXR10_R1(config)#interface pos3_3/1 ZXR10_R1(config-if)#ip 255.255.255.252 ZXR10_R1(config-if)#ppp authentication chap ZXR10_R1(config-if)#ppp chap hostname ZXR10 ZXR10_R1(config-if)#ppp chap password hello ZXR10_R1(config-if)#ppp open address 192. 168. 1. 1
R2 configuration:
ZXR10_R2(config)#interface pos3_3/1 ZXR10_R2(config-if)#ip 255.255.255.252 ZXR10_R2(config-if)#ppp authentication chap ZXR10_R2(config-if)#ppp chap hostname ZXR10 ZXR10_R2(config-if)#ppp chap password hello ZXR10_R2(config-if)#ppp open address 192. 168. 1.2
Examples for MPPP Configuration

MPPP (MultiLink-PPP), multilink point-to-point protocol, is an extended protocol of PPP. It is used to bind multiple physical WAN links of two routers into a logic link to increase the link bandwidth. For example, it can bind four physical 2M lines into a 8M logic line by MPPP.
Upon data sending, IP packets are first encapsulated into PPP frame format, and then the encapsulated frame are segmented into certain data fragments. Each data fragment, added with the header of the MPPP, is encapsulated into MPPP frame format. As shown in Figure 78, routers R1 and R2 are bound and interconnected in channelized CE1 timeslot mode. The MPPP is configured.
FIGURE 78 RIP CONFIGURATION EXAMP LES
R1 configuration:
ZXR10_R1(config)#interface multilink1 ZXR10_R1(config-if)#ip 255.255.255.252 ZXR10_R1(config)#controller ce1_7/1 ZXR10_R1(config-control)#channel-group 1 timeslots 1-31 ZXR10_R1(config)#interface ce1_7/1. 1 ZXR10_R1(config-if)#multilink-group multilink1 address 192. 168. 1. 1
R2 configuration:
ZXR10_R2(config)#interface multilink1 ZXR10_R2(config-if)#ip 255.255.255.252 ZXR10_R2(config)#controller ce1_7/1 ZXR10_R2(config-control)#channel-group 1 timeslots 1-31 ZXR10_R2(config)#interface ce1_7/1. 1 ZXR10_R2(config-if)#multilink-group multilink1 address 192. 168. 1.2
Note: In case multiple routers are connected with a certain device through multilinks, the CE1 interfaces corresponding to the multilink interfaces of these routers must be configured with different end point.
The show ppp multilink command can be used to view the information about a multilink.
FR
General Description
The FR (Frame Relay) protocol is a high-performance WAN protocol running in the physical layer and data link layer of the OSI reference model. It is a packet switching technology and is a simplified version of X.25. With the omission of some complicated functions of X.25 (such as window technology and data retransmission technology), FR relies on upper-level protocols to support error correction. Since the frame relay works on a piece of WAN equipment that is better than the WAN equipment where the X.25 works, the equipment has higher reliability. The frame relay strictly corresponds to the bottommost two layers of the OSI reference model, while X.25 also provides L3 services. Therefore, frame relay has higher performance and more efficient transmission efficiency than X.25. The WAN equipment of frame relay is divided into Data Terminal Equipment (DTE) and Data Circuit Equipment (DCE). Normally, routers serve as DTE. The frame relay technology provides communications of connection-oriented data link layer. A defined communication link is available between each pair of equipment, and also the link has a Data Link Connection Identity (DLCI). Such a service is implemented via frame relay circuits. Each frame relay virtual circuit identifies itself with DLCI. Normally, DLCI is designated by the frame relay service provider. Frame relay supports PVC as well as SVC. Frame relay Local Management Interface (LMI) is an extension of the basic frame relay standard. It is the signalling standard between a router and a frame relay switch, supporting the frame relay management mechanism. The frame relay LMI provides many features to manage a complicated internetwork, including functions such as global addressing, virtual circuit status message and multi-destination sending.
Basic FR Configuration
The configuration of the FR protocol covers the following contents. 1. 2. 3. Select an interface to be configured and enter the Interface Configuration mode
Configure frame relay encapsulation for the interface

encapsulation frame-relay

Ip address <ip-addr> <net-mask> [<broadcast-addr>] [secondary]
4.
Configure equipment type

frame-relay intf-type <equip-type>
Note: Equipment type name can be dce, dte or nni (the default name is dte). Both communication ends are dte and dce. If one end is configured with "nni" (network-network interface), the other end also should be configured with "nni". To set the equipment type to dce or nni, use the f r a m e - r e l a y s w i t c h i n g command to configure the frame relay equipment type setting switch in the Global Configuration mode.
5. 6. 7.
Configure LMI signaling format

frame-relay lmi-type <lmi-type>
Configure the frame relay interface mode (Point-to-point and point-to-multipoint)

frame-relay interface-mode <mode>
Configure address mapping Define the dlci mapping of the peer and local ends in the point-to-point mode
frame-relay interface-dlci <dlci>
Define the destination protocol address and the mapping used to connect DLCI of the destination address for the point-to-multipoint mode
frame-relay map ip <ip-addr> <dlci> [<encap>]
Note: Here, the IP address should be configured as the peer IP address. At present, the following two encapsulation modes are supported: ietf and cisco (ietf by default).
8. 9.
Displays frame relay lmi information

show frame-relay lmi [interface <interface-number>]
Displays frame relay ip-dlci mapping table

show frame-relay map
10. Displays frame relay PVC

show frame-relay pvc
Examples for PPP Configuration

As shown in Figure 79, routers R1 and R2 are connected via V35 synchronous serial interface on R2. In this example, it uses the frame relay protocol encapsulation and point-to-multipoint mode. R1 acts as DTE and R2 as DCE.
F I G U R E 7 9 F R AM E R E L AY C O N F I G U R AT I O N E X AM P L E
R1 configuration:
ZXR10_R1(config)# interface serial_2/1 ZXR10_R1(config-if)# encapsulation frame-relay ZXR10_R1(config-if)# multipoint ZXR10_R1(config-if)# ip address 192. 168. 1. 1 frame-relay interface-mode point-to-
255.255.255.252 ZXR10_R1(config-if)# frame-realy map ip 192. 168. 1.2 100
R2 configuration:
ZXR10_R2(config)# frame-relay switching ZXR10_R2(config)# interface serial_2/1 ZXR10_R2(config-if)# multipoint ZXR10_R2(config-if)# 255.255.255.252 ZXR10_R2(config-if)# encapsulation frame-relay ZXR10_R2(config-if)# frame-relay intf-type dce ZXR10_R2(config-if)# 100 frame-realy map ip 192. 168. 1. 1 ip address 192. 168. 1.2 frame-relay interface-mode point-to-
X.25
Overview
As the famous and widely applies protocol standard, X.25 defines functions of three layers, physical, link and packet level. These layers correspond to the lower three layers of OSI. The physical layer processes interfaces on links connecting sites and sites with packet switching termination points. In this standard, the user equipment is the Data Terminal Equipment (DTE) and the packet switching termination point connecting the DTE is the Data Circuit Terminal Equipment (DCE). X.25 adopts the principles of the physical layer defined in X.21 standard, but it may also adopt other principles. Data is transmitted in the link layer in the mode of frame sequence, thus ensuring reliable data transmission on the physical lines. It is the LAPB standard, subset of DHLC, adopted by the link layer. The packet layer provides external virtual circuit services. In the X.25 packet layer, data is transmitted in the packet mode via external virtual circuits. There are two kinds of virtual circuits provided: Switched Virtual Circuit (SVC) and Permanent Virtual Circuit (PVC). Of them, the SVC is dynamically established.
Basic X.25 Configurations

The configuration of the X.25 protocol covers the following contents. 1. 2. Configure the interface encapsulation mode
encapsulation <mode>
Enable X.25 OVER FR

frame-relay x.25-enable
3. 4. 5. 6. 7. 8.
Configure X.25 interface equipment type

x.25 mode {dce|dte}
Configure the working mode of X.25 interfaces

x.25 module {8|128}
Configure X.25 port mode

x.25 port-manner {user|trunk}
Configure related parameters of X.25 LAPB Configure the maximum frame length in lapb layer
x.25 lapb packet-size {1032|136|264|520}
Configure the maximum retransmission times in lapb layer

x.25 lapb retransfer count<count>
Configure the send timer in lapb layer

x.25 lapb timeout t1<second>
Configure the receiving timer in lapb layer

Configure the idle timer in lapb layer

Configure size of lapb window

x.25 lapb window size<size>
Configure parameters related to X.25 packet layer Configure the maximum packet length in packet layer
x.25 packet length-size {1024|128|256|512}
Configure the maximum links in packet layer

x.25 packet max-virtual connect<size>
Configure the restart timer in packet layer

x.25 packet timeout t20<second>
Configure call request timer in packet layer

Configure reset timer in packet layer

Configure clear timer in packet layer

Configure size of packet window

x.25 packet window size<size>
Configure the maximum idle time of links in packet layer

x.25 svc-idletime< second >
Configure the X.25 station addresses, user addresses and trunk routing
9.
Configure the X.25 station addresses

x.25 station<station addr>
Configure the X.25 user addresses

x.25 x. 121-user<user addr>interface <interface-name>Qos<num>
Configure the X.25 trunk routing

x.25 x. 121-trunk<trunk addr>interface <interface-name>Qos<num>
Configure default X.25 trunk routing

x.25 default-trunk <interface-name>
Configure X.25 PVC

x.25 pvc<pvc-num> interface <interface-name> interface <interface-name> lcn <lcn-num> lcn <lcn-num>
10. Configure X.25 local switch

x.25 dte id2>> local-switch ingress <interface id1> egress <interface
11. Configure transparent of X.25 frame relay

x.25 xconnect ingress <interface id1> egress <interface id2> dlci <dlci>
Note: Here the out interface must be the frame relay interface and the dlci must be configured on the frame relay interface.
12. Show PVC

show x.25 pvc
13. Show dynamically generated SVC

show x.25 svc
14. Show configuration of X.25 interfaces

show x.25 operation interface <interface-name>
Examples for X.25 Protocol Configuration

1. Take configuration of GAR as the packet switching equipment for example. As shown in Figure 80, two sets of X.25 terminal equipment are connected with two GARs via encapsulated serial interfaces. The interfaces between two GARs are X.25 OVER FRs. Set the user address of terminal DTE1 to 00001, that of DTE2 to 00002, station address of GAR1 to 11111, and that of GAR2 to 22222. Configure the relay routing of DTE2 on GAR1 and that of DTE1 on GAR2 to enable two DTEs call transmission files.
F I G U R E 8 0 X . 2 5 C O N F I G U R A T I O N E X AM P L E 1
GAR1 configuration:
ZXR10_R1(config)#exit ZXR10_R1(config-if)#interface ce1_1/1. 1 ZXR10_R1(config-if)#encapsulation frame-relay ZXR10_R1(config-if)#frame-relay x.25-enable ZXR10_R1(config-if)#frame-relay intf-type dce ZXR10_R1(config-if)#frame-relay interface-dlci 16 ZXR10_R1(config-if)#x.25 mode dte ZXR10_R1(config-if)#x.25 port-manner trunk ZXR10_R1(config-if)#exit ZXR10_R1(config)#x.25 station 11111 ZXR10_R1(config)#x.25 serial_1/1 Qos 1 ZXR10_R1(config)#x.25 ce1_1/1. 1 Qos 1 x. 121-trunk 2222200002 interface x. 121-user 00001 interface
GAR2 configuration:
ZXR10_R2(config)#interface serial_2/1 ZXR10_R2(config-if)#encapsulation x.25 ZXR10_R2(config-if)#x.25 mode dce ZXR10_R2(config-if)#x.25 port-manner user ZXR10_R2(config)#exit ZXR10_R2(config-if)#interface ce1_2/1. 1 ZXR10_R2(config-if)#encapsulation frame-relay ZXR10_R2(config-if)#frame-relay x.25-enable ZXR10_R2(config-if)#frame-relay intf-type dte ZXR10_R2(config-if)#frame-relay interface-dlci 16 ZXR10_R2(config-if)#x.25 mode dce ZXR10_R2(config-if)#x.25 port-manner trunk ZXR10_R2(config-if)#exit ZXR10_R2(config)#x.25 station 22222 ZXR10_R2(config)#x.25 serial_2/1 Qos 1 ZXR10_R2(config)#x.25 ce1_2/1. 1 Qos 1 x. 121-trunk 1111100001 interface x. 121-user 00002 interface
2.
Here is an example for configuring interconnection of GAR with B10 where the GAR acts as the transparent equipment. As shown in Figure 81, the GAR transparently transmits all the packets between the terminal and B10.
GAR configuration:
ZXR10_R1(config-if)#interface ce1_1/1. 1 ZXR10_R1(config-if)#encapsulation frame-relay ZXR10_R1 (config-if)#frame-relay intf-type nni ZXR10_R1(config-if)# frame-relay interface-dlci 16 ZXR10_R1(config-if)#exit ZXR10_R1(config)# x.25 xconnect ingress serial_1/1 egress ce1_1/1. 1 dlci 16
3.
Configuration of GAR acting as the transparent equipment for self-switching between terminals As shown in Figure 82, the GAR transparently transmits all the packets between the terminal and B10.
GAR configuration:
ZXR10_R1(config-if)#interface serial_1/1 ZXR10_R1(config-if)#encapsulation x.25 ZXR10_R1 (config-if)#exit ZXR10_R1(config-if)#interface serial_2/1 ZXR10_R1(config-if)#encapsulation x.25 ZXR10_R1 (config-if)#exit ZXR10_R1(config)#x.25 dte local-switch ingress serial_1/1 egress serial_2/1
HDLC
Overview
HDLC is a protocol used for data transmission between network termination points. When this protocol is adopted, data are grouped into units (frames) for network transmission and the receiving end will confirm its reception. Furthermore, it manages the data streams and interval between data transmission. HDLC is the most widely adopted protocol in the data link layer.
Basic HDLC Configuration

The configuration of the FR protocol covers the following contents. 1. 2. 3. Select an interface to be configured and enter the Interface Configuration mode
Configure frame relay encapsulation for the interface

encapsulation hdlc

ip address <ip-addr> <net-mask> [<broadcast-addr>] [secondary]
Examples for HDLC Configuration

Connect GAR1 and GAR2 via E1 interfaces and encapsulate DHLC as shown in Figure 83.
F I G U R E 8 3 H D L C C O N F I G U R AT I O N E X A M P L E

ZXR10_R1(config)# interface ce1_1/1. 1 ZXR10_R1(config-if)# encapsulation hdlc ZXR10_R1(config-if)# 255.255.255. 0 ip address 192. 168. 1. 1
Chapter
Network Protocol Configuration

This chapter describes configuration of IP addresses, and ARP protocol.
IP Address Configuration
Note: This chapter introduces IP addresses of IPV4.
Overview
Here the IP address refers to the network layer address in IP protocol stack. One IP address is mainly composed of two parts: Network bit identifying the network to which this IP address belongs, and host bit identifying a certain host in the network. The IP addresses are divided into five classes: Class A, Class B, Class C, Class D and Class E. Classes A, B and C are the most common ones. Class D is the network multicast address and Class E is reserved for future use. Table 87.lists the range of each class.
T A B L E 8 7 I P AD D R E S S R AN G E O F E A C H C L AS S
Category Class A Class B Class C Class D Class E
Prefix Network Bit Host Bit Characteristic Bit 0 10 110 1110 1111 8 16 24 24 16 8
Scope 0. 0. 0. 0~127.255.255.255 128. 0. 0. 0~191.255.255.255 192. 0. 0. 0~223.255.255.255 224. 0. 0. 0~239.255.255.255 240. 0. 0. 0~255.255.255.255
Multicast address Reserved
Among the three categories (A, B and C) of IP addresses, some addresses are reserved for private networks. It is recommended that private network addresses be used in establishing internal networks. They are: Class A: 10. 0. 0. 0 to 10.255.255.255 Class B: 172. 16. 0. 0 to 172. 31.255.255 Class C: 192. 168. 0. 0 to 192. 168.255.255
This address classification method is to facilitate routing protocol designing. One can know the network type just by the prefix characteristic bit of the IP address. This method, however, cannot make the best of the address space. With the dramatic expansion of the Internet, the problem of address shortage becomes increasingly serious. To make the most of IP addresses, you can divide one network into multiple subnets. Borrow some bits from the highest bit of the host bit as the subnet bit. The remaining part of the host bit still serves as the host bit. Thus, the IP address is composed of three parts: network bit, subnet bit and host bit. The network bit and subnet bit identify a network uniquely. The subnet mask is used to decide which parts of the IP address are the network bit, subnet bit, and host bit. The part with the subnet mask being 1 corresponds to the network bit and subnet bit of the IP address, and the part with the subnet mask being 0 corresponds to the host bit. The division of the subnet greatly improves the utilization of the IP address, and alleviates the problem of IP address shortage. Some conventions for IP addresses: 1. 0. 0. 0. 0 is used when a host without an IP address is started. RARP, BOOTP and DHCP are used to obtain the IP address. The address serves as the default route in the routing table. 255.255.255.255 is used for the destination address of broadcast and cannot be used as a source address. 127. X. X. X is called the loop-back address. When the actual IP address of the host is not known, this address is used to represent this host. The address with only the host bit being 0 indicates the network itself. The address with the host bit being 1 is the broadcast address of the network. The network part or the host part of a valid host IP address cannot be all 0s or 1s.
2. 3. 4. 5.
Basic IP Address Configuration

In the Interface Configuration mode, the IP address is configured as follows: 1. Entering the Interface Configuration Mode
For an inexistent sub-interface, create it and enter the sub-interface configuration mode 2. Configure the IP and secondary addresses of the interface
ip address <ip-addr> <net-mask> [<broadcast-addr>] [secondary]
3.
Check the interface IP address.

show ip interface [brief] [<interface-name>]
Examples for IP Address Configuration

Supposing a Gigabit Ethernet interface board is inserted into Slot 3 of a ZXR10 GAR router, the user wants to configure the IP address of the second interface as 192. 168. 3. 1 and the mask code to 255.255.255. 0. The detailed configuration is as follows:
ZXR10(config)#interface gei_3/2 ZXR10(config-if)#ip address 192. 168. 3. 1 255.255.255. 0
ARP Configuration
Overview
When a set of network equipment sends data to another network equipment, it should know the IP address and physical address (MAC address) of the destination equipment. ARP (Address Resolution Protocol) is to map the IP address to the physical address, so as to ensure smooth communication. At first, the source device broadcasts the ARP request with the IP address of the destination device. Then, all the devices on the network receive this ARP request. If one device finds the IP address in the request matches with its IP address, it sends a reply containing the MAC address to the source device. The source device obtains the MAC address of the destination device through this reply. To reduce ARP packets on the network and send data faster, the mapping between IP address and MAC address is cached in the local ARP table. When a device wants to send data, it looks up the ARP table according to the IP address first. If the MAC address of the destination device is found in the ARP table, it is unnecessary to send the ARP request again. The dynamic entry in the ARP table will be automatically deleted or retransmit an APR requirement of this entry after a period of time, which is called the aging time of the ARP.
Basic ARP Configuration

The ARP configuration includes: 1. 2. 3. Configure the aging time of the ARP entry in the ARP buffer area
arp timeout <timeout>
Bind the IP address with the MAC address

set arp {static|permanent} <ip-address> <hardware-address>
Delete the bound IP address and MAC address of the designated ARP table entry in the Ethernet interface ARP cache
clear arp [<ip-address>|static|permanent]
4. 5. 6. 7. 8. 9.
Delete all dynamic ARP table entries in the Ethernet interface ARP cache
clear arp-cache [<interface-name>]
Configure the agent function of ARP

ip proxy-arp
Filter ARP source address

arp source-filtered
Automatic binding of dynamic ARP entries

arp to-static
Configure APR protection

arp protect{interface|whole}limit-num<number>
Modify the MAC offset of interfaces

interface mac-address offset <mac-offset>
ARP Maintenance and Diagnosis

For the convenience of ARP maintenance and diagnosis, ZXR10 routers provide related view and debug commands. 1. Check ARP configuration
show arp [<interface-name>[mac <mac-addr>]]
The following example shows the ARP table of Ethernet interface fei_1/1.
ZXR10#show arp fei_1/1 Address Interface 10. 1. 1. 1 fei_1/1 10. 1. 100. 100 18 fei_1/1 ZXR10# Age(min) Hardware 000a. 00b0. Addr e2c6 820a
010c. d08f.
2. 3.
Print the ARP debug information on the terminal

debug arp
Check ARP automatic binding

show arp-to-static [<interface-name>]
Examples for ARP Configuration

The following part shows an ARP configuration example.
ZXR10(config)#interface fei_1/1 ZXR10(config-if)#arp timeout 1200 ZXR10(config-if)#set arp static 10. 1. 1. 1 000a. 010c.
e2c6
Chapter
V-Switch Configuration
This chapter describes configuration of V-Switch.
Overview
In the networking mode of router + BAS, a router has two functions: Transfers PPPoE data packets to BAS equipment, implements data convergence, and provides services such as access of large clients (VPN), Qos, NAT and multicast. To implement these functions, the ZXR10 GAR adopts static V-Switch transmission to realize L2 transmission of data packets, and implements transparent transmission between different VLANs.
Basic V_Switch Configuration

The configuration of V-Switch contains the following contents: 1. 2. Configure the transfer mode of the interface in the Interface Configuration mode
ip forwarding-mode {vlan-switch|normal|mix}
Configure the V-Switch forwarding table

vlan-forwarding ingress <interface-name> <vlan-id> <interface-name> <vlan-id> [range <range>] [dual|single] egress
V-Switch Maintenance and Diagnosis

1. Show the configuration information of a specified interface
show running-config interface <interface-name>
2.
Show entries in VLAN forwarding table

show vlan-forwarding [ingress <interface-name>]
Examples for V-Switch Configuration

As shown in Figure 84, interface fei_1/3 of ZXR10 GAR is connected to the user side of BAS and interface fei_1/4 to the network side of BAS. A PPPoE user is attached on interface fei_1/1 and a private user on interface fei_1/2. VLAN ID of PPPoE users ranges from 10 to 19, that of BAS user side ranges from 20 to 29, and that of private users from 30 to 31.
F I G U R E 8 4 V - S W I T C H C O N F I G U R A T I O N E X AM P L E
ZXR10(config-if)#ip forwarding-mode vlan-switch ZXR10(config)#interface fei_1/1 ZXR10(config-if)#ip forwarding-mode vlan-switch ZXR10(config)#vlan-forwarding fei_1/3 20 ZXR10(config)#vlan-forwarding fei_1/3 21 ingress fei_1/1 11 egress ingress fei_1/1 10 egress
ZXR10(config)#vlan-forwarding fei_1/3 22 ZXR10(config)#vlan-forwarding fei_1/3 23 ZXR10(config)#vlan-forwarding fei_1/3 24 ZXR10(config)#vlan-forwarding fei_1/3 25 ZXR10(config)#vlan-forwarding fei_1/3 26 ZXR10(config)#vlan-forwarding fei_1/3 27 ZXR10(config)#vlan-forwarding fei_1/3 28 ZXR10(config)#vlan-forwarding fei_1/3 29
ingress ingress ingress ingress ingress ingress ingress ingress
fei_1/1 fei_1/1 fei_1/1 fei_1/1 fei_1/1 fei_1/1 fei_1/1 fei_1/1
12 13 14 15 16 17 18 19
egress egress egress egress egress egress egress egress
ZXR10(config)#interface fei_1/4 ZXR10(config-if)#ip 255.255.255.252 ZXR10(config)#interface fei_1/2. 30 ZXR10(config-subif)#encapsulation dot1q 30 ZXR10(config-subif)#ip 255.255.255.192 ZXR10(config)#interface fei_1/2. 31 ZXR10(config-subif)#encapsulation dot1q 31 ZXR10(config-subif)#ip 255.255.255.192 address 10. 1. 1. 65 address 10. 1. 1. 1 address 192. 168. 1. 1
Chapter
10

This chapter describes configuration of the static route.
Overview
The static route is the route information designated by the network administrator to the routing table with the configuration commands. Unlike the dynamic route, it does not create the routing table according to the route algorithm. When configuring the dynamic route, sometimes you need to send routing information of the entire Internet to a router, which is hard to bear such great amount of information. In this case, it is necessary to use the static route. Only a few configurations of the static route are needed to avoid the use of the dynamic route. In a routing environment with many routers and paths, however, it is very difficult to configure the static route.
Basic Static Route Configuration

Configure the static route using the following command:
ip route [vrf <vrf-name>] <prefix> <net-mask> {<forwarding-router'saddress>|<interface-name>} [<distance-metric>] [tag <tag>]
Tag is a route label. Two static routes (with different next hop) to the same destination network cannot have the same tag value.
Static Route Maintenance and Diagnosis

The following command can be used to display the global routing table of a router and view whether a configurable static route is available in the routing table.
show ip route [<ip-address> [<net-mask>]|<protocol>]
This command is very useful and often used in routing protocol diagnosis and maintenance.
Examples for Static Route Configuration

Figure 85 shows a simple network with three routers connected.
F I G U R E 8 5 S T AT I C R O U T E C O N F I G U R A T I O N E X AM P L E
If the R1 needs to access the network on the R3, the static route should be configured as follows: 1. Method 1:
route route 192. 192. 168. 168. 5. 6. 0 0 255.255.255. 255.255.255. 0 0
ZXR10_R1(config)#ip 192. 168. 4.2 ZXR10_R1(config)#ip 192. 168. 4.2
As shown from the above configuration information, the static route is configured in the Global Configuration mode, and only one static route is configured at a time. Following the i p r o u t e command are the remote network, subnet mask, and the next hop IP address to the remote address. If R1 intends to send packets to the network 192. 168. 5. 0/24, it first must send packets to the R2 with the IP address 192. 168. 4.2. R1 and R2 are directly connected. 2. Method 2:
route 192. 168. 5. 0 255.255.255. 0
ZXR10_R1(config)#ip
ce1_2/1. 1 ZXR10_R1(config)#ip ce1_2/1. 1 route 192. 168. 6. 0 255.255.255. 0
This configuration method is similar to the previous method. The sole difference is that the previous method uses the IP address of the next hop, and this method uses the local interface. That is, all packets to 192. 168. 5. 0/24 and 192. 168. 6. 0/24 are sent through CE1 interface ce1_2/1, instead of routing to the logic address of the next hop. The local interface mode is not adaptive for Ethernet interfaces. If there are multiplex paths to the same destination, you can configure different static routes with multiple administrative distances for the router. The routing table only shows information of the route with the minimum administrative distance. The reason is that when the route is notified of many competition sources of a network, the route with the minimum administrative distance prevails. The parameter distance-metric in the static route configuration command ip route is used to change the administrative distance of a static route. Suppose that there are two different routes from R1 to 192. 168. 6. 0/24, which are configured as follows:
ZXR10_R1(config)#ip 192. 168. 4.2 ZXR10_R1(config)#ip route 192. 168. 6. 0 255.255.255. 0 192. 168. 3.2 25 tag 180 route 192. 168. 6. 0 255.255.255. 0
The above two commands configure two different static routes to the same network. The first command does not configure the administrative distance, so it uses the default value 1. The second command sets the administrative distance to 25. Because the administrative distance of the first route is smaller than that of the second one, the routing table will show information of the first route only, that is, the router arrives at the destination address 192. 168. 6. 0/24 only through the next hop address 192. 168. 4.2. Only when the first route is failed and disappears from the routing table will the second one appear in the routing table.
Static Route Summary Configuration

The summary static route is a special static route, which summaries two or more specific route expressions into one expression, thus reducing entries of the routing table while keeping all of the original connections. Figure 86 describes the summary static route in detail.
F I G U R E 8 6 S T AT I C R O U T E S U M M A R Y C O N F I G U R AT I O N E X A M P L E
As shown in Figure 86, R3 has two networks: 10. 1. 0. 0/16 and 10.2. 0. 0/16. To make R1 access these networks, it is necessary to configure the following two static routes for R1:
ZXR10_R1(config)#ip route 10. 1. 0. 0 255.255. 0. 0 192. 168. 4.2 ZXR10_R1(config)#ip 168. 4.2 route 10.2. 0. 0 255.255. 0. 0 192.
Suppose R3 has been configured normally, you can complete IP connection through the above configuration. We can use the summary static route to optimize the routing table of R1, and use the following command to replace the above two commands:
ZXR10_R1(config)#ip 168. 4.2 route 10. 0. 0. 0 255. 0. 0. 0 192.
This command shows that all packet sent to 10. 0. 0. 0/8 have to pass 192. 168. 4.2. That is, packets of subnets (10. 1. 0. 0/16 and 10.2. 0. 0/16) with the destination being 10. 0. 0. 0/8 are sent to 192. 168. 4.2. Through this method, we collect all the subnets of the primary network 10. 0. 0. 0/8 with a static route.
Default Route Configuration

The default route is also a special static route. The default route is used when all the other routes in the routing table fail. It gives the routing table a last destination, thus greatly alleviating the processing load of the router. If a router cannot supply a route for a packet, the packet has to be discarded. To avoid the packet being sent to an unknown destination and to make the route fully connected, there must be a route from the router to a certain network. The default route can keep the router fully connected, and avoid recording each independent route. Through the default route, an independent route can be designated to represent all other routes. The following example explains functions and usage of the static route.
F I G U R E 8 7 D E F AU L T R O U T E C O N F I G U R A T I O N E X AM P L E
As shown in Figure 87 R2 is connected to R3 in the Internet. Because R2 does not record all the network addresses on the Internet, it uses the default route to send
unknown packets to R3 for processing. The default route configuration of R2 is as follows:

ZXR10_R2(config)#ip 211.211.211.2 route 0. 0. 0. 0 0. 0. 0. 0
The configuration of default route is almost the same as that of static route except that its network address and subnet mask are 0. 0. 0. 0. Check the routing table of R2:
ZXR10_R2#show ip route IPv4 Routing Table: Dest 0. 0. 0. 0 ZXR10_R2# Mask Gw 0. 0. 0. 0 Net Owner static 211.211.211.2
As shown in the routing table, the default route with the next hop address being 211.211.211.2 is added to the routing table as the last route. The default route in the routing protocol configuration varies with the routing protocol. If the default route is configured for a router running RIP, RIP will notify the default route 0. 0. 0. 0/0 to its neighbors, without the need of route redistribution in the RIP domain. For OSPF, the router running OSPF will not notify the default route to its neighbors automatically. To make OSPF send the default route to the OSPF domain, command d e f a u l t - i n f o r m a t i o n o r i g i n a t e can be used. If it is necessary to redistribute the default route in the OSPF domain, this notification is usually given by the ASBR in the OSPF domain.
Chapter
11
RIP Configuration
This chapter describes configuration of the RIP protocol.
Overview
RIP Background
RIP is the first routing protocol to implement dynamic routing, based on the distance vector algorithm of the local network. RIPv1 is defined in RFC1058, while RIPv2 is defined in RFC1723. The ZXR10 GAR completely supports RIPv1 and RIPv2. It uses RIPv2 by default. Compared with RIPv1, RIPv2 has the following advantages: Subnet mask contained in the routing update Authentication of the routing update Multicast route update
The following part introduces RIPv2. Unless otherwise specified, RIP refers to RIPv2.
Metric and Administrative Distance

RIP uses the UDP packet (port number 520) to exchange RIP routing information. Routing information in the RIP packet includes the number of routers that a route passes (that is, hops). The router determines the route to the destination network according to hops. RFC stipulates that the maximum hop count cannot go beyond 16, so RIP is only applicable to a small-sized network. The hop count 16 indicates the infinite distance, meaning that the route is unreachable. Besides, this is a method for RIP to identify and avoid route loop. RIP only takes the hop count as the metric, and does not consider the bandwidth, delay or other variable factors during the routing. RIP always takes the path with the
minimum hop count as the optimal path, which sometimes results in that the selected path is not the best. The Administrative Distance (AD) of the RIP is 120 by default. The smaller the AD value, the more reliable the routing source. Therefore, compared with other routing protocols, RIP is not so reliable.
Timer
The router running RIP sends a routing information update packet reflecting all the routing information of the router at intervals (30 seconds by default), which is called the routing information announcement. If a router cannot receive update information from another router within a period of time (180 seconds by default), it will label the route provided by this router as unavailable. If update information still cannot be received within the subsequent period of time (240 seconds by default), the router eliminates the route from the routing table. RIP provides four timers: Update timer Invalid timer Holddown timer Flush timer
Route Update
RIP uses triggered updates to accelerate the dispersion of routing changes in the RIP route domain. When an RIP router detects that an interface is being or has been stopped, a neighboring node collapses, or a new subnet/neighboring node joins, it will send a triggered update. The triggered update packet only involves changed routes. RIP uses the poison reverse to accelerate protocol aggregation. The poison reverse sets the prefix metric of the inaccessible network to 16 (inaccessible). After receiving the route update of the metric, the router discards this route, instead of waiting for the aging time. RIP uses the split horizon function to avoid route loops and reduce the size of route update. The split horizon means not repeatedly sending update information to an interface that has received a route update.
RIP Configuration
RIP configuration includes: Basic configuration, enhancement configuration and version configuration.
Basic configurations
1. 2. Start the RIP route selection process:
router rip
Designate a network table for RIP routing

network <ip-address> <net-mask>
Enhanced Configuration
1. Adjusts RIP network timer
timers basic <update> <invalid> <holddown> <flush>
Many RIP features can be customized to adapt any network environment. Although timers default values need not be changed in most cases, regulating timers could enhance protocol performance in some cases. 2. 3. 4. Change the delay for sending RIP update packets
output-delay <packets> <delay>
Define the neighboring router exchanging routing information with the local router
neighbor <ip-address>
Authentication configuration To add some special security to the routing process in the network, configure RIP authentication on the router. Set a password for the interface. The network neighbors must use the same password on the network. RIPv1 does not support the authentication.
5. 6. 7. 8.
Designate the key for interface simple text authentication

ip rip authentication key <key>
Designate the authentication type for RIP packet

ip rip authentication mode {text|md5}
Enable the split horizon mechanism

ip split-horizon
Enable the poison reverse mechanism

ip poison-reverse
Redistribute routes from one route domain to the RIP route domain
redistribute
Set the default metric when redistributing routes generated by other protocols to RIP routes
default-metric <metric-value>
9.
ZXR10 GAR supports both RIPv1 and RIPv2, and it uses RIPv2 by default. Designate the RIP version received or sent by the router with the following commands: Designate the global RIP version of the router
version {1|2}
Designate the RIP version received by the interface

ip rip receive version {1|2} [1|2]
Designate the RIP version sent by the interface

ip rip send version {1|2 {broadcast|multicast}}
RIP Maintenance and Diagnosis

The following part shows common commands in RIP maintenance and diagnosis. 1. 2. 3. Display the basic RIP running information
show ip rip [vrf <vrf-name>]
Show the current configuration and state of the RIP interface

show ip rip interface [vrf <vrf-name>] <interface-name>
View the route entries generated by the RIP:

show ip rip database [vrf <vrf-name>] [network <ip-address> [mask <net-mask>]]
4.
Show all the RIP interfaces configured by users

show ip rip networks [vrf <vrf-name>]
The ZXR10 GAR also provides the d e b u g command to debug RIP and trace relevant information. Here is an example: 1. 2. 3. 4. 5. Trace packet receiving and sending of RIP
debug ip rip
Open all RIP debug switches.

debug ip rip all
Trace RIP routing table changes

debug ip rip database
Trace RIP-related events

debug ip rip events
Trace RIP-triggered events

debug ip rip trigger
Example for debugging output of the d e b u g i p r i p command:

ZXR10#debug ip rip RIP protocol debugging is on ZXR10# 11:01:28: RIP: building update entries 130. 1. 0. 0/16 via 0. 0. 0. 0, metric 1, tag 0
130. 1. 1. 0/24 via 0. 0. 0. 0, metric 1, tag 0 177. 0. 0. 0/9 via 0. 0. 0. 0, metric 1, tag 0 193. tag 0 197. 1. 0. 0/16 via 0. 0. 0. 0, metric 1, tag 0 199.2. 0. 0/16 via 0. 0. 0. 0, metric 1, tag 0 202. tag 0 11:01:28: RIP: sending v2 periodic update to 224. 0. 0. 9 via pos3_3/1 (193. 1. 1. 111) 130. 1. 0. 0/16 via 0. 0. 0. 0, metric 1, tag 0 130. 1. 1. 0/24 via 0. 0. 0. 0, metric 1, tag 0 177. 0. 0. 0/9 via 0. 0. 0. 0, metric 1, tag 0 193. 1. 1. 0/24 via 0. 0. 0. 0, metric 1, tag 0 11:01:28: RIP: sending v2 periodic update to 193. 1. 168. 95 via fei_1/1 (193. 1. 168. 111) 11:01:28: RIP: sending v2 periodic update to 193. 1. 168. 86 via fei_1/1 (193. 1. 168. 111) 11:01:28: RIP: sending v2 periodic update to 193. 1. 168. 77 via fei_1/1 (193. 1. 168. 111) 11:01:28: RIP: sending v2 periodic update to 193. 1. 168. 68 via fei_1/1 (193. 1. 168. 111) 119. 8. 0/24 via 0. 0. 0. 0, metric 1, 1. 168. 0/24 via 0. 0. 0. 0, metric 1,
Examples for RIP Configuration

As shown in Figure 88, run RIP on both R1 and R2.
FIGURE 88 RIP CONFIGURATION EXAMP LE
R1 configuration:
ZXR10_R1(config)#router rip ZXR10_R1(config-router)#network 10. 1. 0. 0 0. 0.255.255 ZXR10_R1(config-router)#network 0.255 192. 168. 1. 0 0. 0.
R2 configuration:
ZXR10_R2(config)#router rip ZXR10_R2(config-router)#network 10.2. 0. 0 0. 0.255.255 ZXR10_R2(config-router)#network 0.255 192. 168. 1. 0 0. 0.
Chapter
12
OSPF Configuration
This chapter introduces the OSPF protocol and relative configurations on the ZXR10 GAR.
Overview
OSPF Background
The Open Shortest Path First (OSPF) protocol is one of the most popular and widelyused routing protocols. It is a link state protocol without the disadvantages of Routing Information Protocol (RIP) and other distance vector protocols. OSPF is an open standard, allowing devices from different vendors to communicate with each other. OSPF Version 1 is defined by RFC1131. OSPF Version 2, defined by RFC2328, is currently being used. The ZXR10 GAR fully supports OSPF Version 2. OSPF has the following features:
Support rapid convergence, ensure database synchronization by flooding link state update rapidly, and calculate the routing table simultaneously. No routing loop: The shortest path first (SPF) algorithm ensures no loop will be generated. Route aggregation decreases the routing table size. It is completely classless and supports Variable Length Subnet Mask (VLSM) and Classless Inter-Domain Routing (CIDR). Less network bandwidth is needed because the adopted update trigger mechanism sends update information only when the network changes. Packet authentication on ports ensures the security of route calculation. Update information can be multicasted instead of being broadcasted, which reduces the impact on irrelevant network devices.
OSPF Algorithm
As OSPF is a link state protocol, the OSPF router generates the routing table by setting up a link state database, which contains the information of all networks and routers. Routers use this information to establish routing tables. To ensure reliability, all routers must have the completely same link state database. The link state database is built based on Link State Advertisements (LSAs), which are generated by all routers and spread over the whole OSPF network. There are many types of LSAs; a complete LSA set shows an accurate distribution diagram over the whole network. OSPF uses cost as the metric. The cost is distributed to each port of a router. A port calculates the cost based on the 100M benchmark by default. The path cost to a particular destination is the total cost of all links between the router and the destination. To generate a routing table based on the LSA database, a router run the Dijkstra SPF algorithm to construct a cost routing tree, with itself as the root of the routing tree. The Dijkstra algorithm enables a router to calculate the lowest-cost path between itself and any node on the network and the router saves the routes of the paths in the routing table. Different from RIP, OSPF does not simply broadcast all its routing information regularly. An OSPF router sends call messages to its neighbors to let them know it is still alive. If a router does not receive any message from a neighbor within a period of time, the neighbor might not be alive. OSPF routing are incrementally updated and a router sends the update information only when the topology changes. When the age of an LSA reaches 1800 seconds, a new version of the LSA is resent.
OSPF Network Types
The type of the network connecting to a port is used to determine the default OSPF behavior on that port. The network type affects the adjacency relationship and how the router designates a timer to the port. There are five network types in OSPF, and they are as follows: Broadcast Non-broadcast Multi-access (NBMA) Point-to-Point Point-to-Multipoint Virtual Links
HELLO Packet and Timer

An OSPF router exchanges Hello Packets with its neighbors at an interval to let them know it is alive. The Hello Packet can discover OSPF neighbors, establish association and adjacency relationship among neighbors, and select a designated router. On broadcast, point-to-point, and point-to-multipoint networks, Hello Packets are multicasted; on NBMA and virtual links, Hello Packets are unicasted to neighbor routers. OSPF uses three types of timers related to the Hello Packet: 1. Hello-Interval The Hello-interval is an attribute of an interface, defining the length of time between the Hello Packets that the router sends on the interface. The default call interval depends on the network type. On the broadcast and point-to-point networks, the default Hello-interval is 10 seconds; on the NBMA and point-to-multipoint networks, it is 30 seconds. The routers neighbor routers must agree on the Hello-Interval to enable them to become neighbors. 2. Router Dead Interval It is the number of seconds before the routers neighbors will declare it down, when they stop hearing the routers Hello Packets. The default Router-Dead interval is four times as long as the Hello-Interval, which applies to all network types. 3. Poll Interval The Poll interval is only used on the NBMA network.
OSPF Neighbors
OSPF neighbors are a group of routers on the same network, with some of the same configuration parameters. The routers must first be neighbors before they can set up adjacency relationship. The routers analyze the Hello Packets from each other when they are becoming neighbors to make sure the required parameters are stipulated. The parameters
include area ID, area flag, authentication information, Hello-interval, and Router-Dead interval.
Adjacency and Designated Router DR

After two routers set up an adjacency relationship, they can exchange the routing information. Whether two routers can set up an adjacency relationship depends on the type of the network connecting the routers. As there are only two routers on the point-to-point network and virtual links, the routers set up an adjacency relationship automatically. The point-to-multipoint network can be regarded as a set of point-to-point networks, so each pair of routers set up an adjacency relationship automatically. In the broadcast and NBMA networks, the neighbors may not form the adjacency. If all n routers on a network have set up the adjacency relationship, each router has (n-1) adjacency relationships and there are n (n-1)/2 adjacency relationships on the network. Tracking so many adjacency relationships on a large multi-access network will impose a heavy burden on each router, and the routing information between each pair of neighbor routers will waste a great deal of network bandwidth. Therefore, OSPF defines a Designated Router (DR) and a Backup Designated Router (BDR). The DR and BDR must establish an adjacency relationship with each OSPF router on the network, and each OSPF router only establishes adjacency relationships with the DR and BDR. If the DR stops working, the BDR will take its place and become the DR.
Router Priority and DR Election

Each router interface has a priority, which affects the routers capability to become the DR or BDR on its network. The router priority is an 8-bit unsigned integer, ranging from 0 to 255. It is 1 by default. During the DR election, the router with the highest priority will become the DR. If all routers have the same priority, the one with the highest IP address will be elected as the DR. The router with priority of 0 cannot become the DR or BDR.
OSPF Area
A network is divided into several smaller OSPF areas to reduce the information that each router stores and maintains. Each router must have the complete information of its area. Areas can share their information, and the routing information can be filtered out on the area edge to reduce the routing information stored in routers. Each area is identified by a 32-bit unsigned number. Area 0 is used to identify the backbone area. All the other areas must directly connect to Area 0. An OSPF network must have one backbone area. Based on its tasks in the area, a router can be of one or multiple of the following roles, as shown in Figure 89.
FIGURE 89 OSPF ROUTER TYPES
Internal router: Routers interface is in the same area. Backbone router: Router has at least one interface in Area 0. Area Border Router (ABR): Router has at leas one interface in Area 0 and at least one interface in another area. Autonomous System Border Router (ASBR): Router connects an AS that runs OSPF to another AS that runs another protocol, such as RIP and IGRP.
LSA Type and Flooding

OSPF routers use LSAs to exchange information for the link state database, set up an accurate and complete network diagram, and thus generate routes in the routing table. ZXR10 GAR supports six types of LSAs including: Type 1: Router LSA Type 2: Network LSA Type 3: Network summary LSA Type4: ASBR summary LSA Type 5: AS external LSA Type 7: NSSA external LSA
OSPF operations are determined by all routers that share one public link state database in a region. Therefore all LSAs need to be flooded over the region and the processing must be reliable. Each router sends the LSAs that it receives from a particular area to the other interfaces in the area. Instead of being packets, LSAs are contained in Link State Update (LSU) packets, and several LSAs can be included in one LSU. When a router receives an LSU packet, instead of forwarding it directly, the router extracts LSAs from the packet and puts them into its database. In addition, the router constructs its own LSU and forwards the modified LSU to neighbors connecting to it.
OSPF sends Link State Acknowledgements (LSAck) to make sure that each LSA is received by neighbors. An LSAck contains the head of the confirmed LSA, which is sufficient for identifying an LSA uniquely. When a router sends an LSA to an interface, the LSA is recorded in the resend queue of the interface. The router will wait the preset time for the LSAck of the LSA. If it does not receive the LSAck within the preset time, it will resend the LSA. A router can send the original LSU by both unicast and multicast, but can resend the LSU only by unicast.
Stub Area and Totally Stubby Area

When there is no ASBR in a non-backbone area, a router has only one path to the outside of the AS: through the ABR. Routers in the area will send the LSAs destined for unknown hosts outside the AS to the ABR. Therefore, Type 5 LSAs need not be flooded to the area and there is no Type 4 LSA in the area. Such areas are called stub area. In a stub area, all routers must be configured as stub routers. The Hello Packet contains a stub area flag bit, which must be consistent among neighbors. The ABR in a stub area can filter out Type 5 LSAs to prevent them from being advertised to the stub area. In addition, the ABR will generate a Type 3 LSA to advertise a default route to destination addresses outside of the AS. If the ABR also filters out the Type 3 LSAs and advertises a default route to destination addresses outside of the area, this area is called totally stubby area.
Not-So-Stubby Area
Routers in a stub area do not allow Type 5 LSAs, so the ASBR is not part of a stub area. However, we might want to create a stub area with ASBR. Routers in this area receive from the ASBR the routes outside of the AS, but external routing information from other areas is blocked. To achieve this purpose, OSPF defines the Not-So-Stubby Area (NSSA). In an NSSA, the ASBR generates Type 7 LSAs instead of Type 5 LSAs. The ABR cannot introduce Type 7 LSAs to other OSPF areas. On the one hand, it blocks external routes from entering the NSSA; on the other hand, it converts Type 7 LSAs into Type 5 LSAs.
OSPF Authentication
The authentication applies to packet exchange between OSPF neighbors. Neighbors must agree on the authentication type, which is included in all packets. 0: no authentication, 1: simple password authentication, and 2: MD5 password authentication.
Chapter
13
IS-IS Configuration
This chapter describes configuration of the IS-IS protocol.
Overview
Intermediate System-to-Intermediate System (IS-IS) is a routing protocol introduced by the International Organization for Standardization (ISO) for Connectionless Network Service (CLNS). It works on the network layer of the Open Systems Interconnection (OSI). When IS-IS is expanded and added with the function to support IP routing, it becomes the Integrated IS-IS. The IS-IS introduced in this document refers to the Integrated IS-IS.
IS-IS Background
IS-IS is widely used as an Interior Gateway Protocol (IGP) on networks. It has a similar working mechanism as OSPF: a network is divided into areas, and routers in an area only manage the routing information of the area, so that route costs are lowed. This feature especially suits medium to large networks. Based on the CLNS protocol, instead of IP, IS-IS uses the ISO-defined Protocol Data Units (PDUs) in the communication between two routers. PDUs used in IS-IS are mainly of the following types: Hello PDU Link State PDU (LSP) Sequence Num PDU (SNP)
The Hello PDU is similar to the Hello Packet in OSPF, responsible for establishing adjacent relationships, discovering new neighbors, and detecting withdrawal of neighbors. IS-IS routers exchange routing information through link state PDU and create and maintain the link state database. An LSP contains the important information of a
router, including the area and network connecting to it. In addition, SNPs are used to ensure the reliable transmission of LSPs. An SNP contains the summary of an LSP on the network. When a router receives an SNP, it compares the SNP with its link state database. If a router loses the LSP in an SNP, it multicasts an SNP to the other routers on the network to request the LSP it needs. The cooperation between LSP and SNP allows IS-IS to implement route interaction reliably on a large network. IS-IS also uses the Dijkstra (SPF) algorithm to calculate routes. IS-IS uses the SPF algorithm to calculate the optimal route according to the link state database and adds the route to the IP routing table.
IS-IS Area
To facilitate the management of the link state database, the concept of area is introduced into IS-IS. Routers in an area only need to manage the link state database of the local area, which relieves the burden on routers. This is extremely important on large networks. Areas in IS-IS are divided into backbone area and non-backbone area. Routers in the backbone area have the database information of the whole network. Routers in non-backbone areas only have the information of the local areas.
IS-IS defines three types of routers for the areas: L1 router: It is in a non-backbone area and only exchanges routing information with L1 and L1/L2 routers in the area. L2 router: It is in the backbone area and exchanges routing information with L2 and L1/L2 routers. L1/L2 router: It is in a non-backbone area and responsible for exchanging routing information from its area with the backbone area.
Figure 90 shows IS-IS areas division and route types.

F I G U R E 9 0 I S - I S AR E A S
IS-IS Network Types

There are only two types of IS-IS networks: broadcast and point-to-point networks. This makes it easier to configure and implement IS-IS.
DIS and Router Priority

On a broadcast network, similar to OSPF, IS-IS also has a Designate IS (DIS). The DIS advertises information to all routers on the broadcast network and all the other routers only advertise information on a neighbor of the DIS. You can configure priority parameters for routers for DIS election or configure different priorities for L1 and L2 routers respectively. In DIS election, the router with the highest priority is elected as the DIS. If all routers have the same priority, for frame relay interfaces, the router with the highest system ID is elected as the DIS; for Ethernet interfaces, the router whose interface has the highest MAC value is elected as the DIS.
IS-IS Configuration
The IS-IS configuration introduced here is mainly based on IP routing.
Basic IS-IS Configuration

1. 2. 3. Enable the IS-IS routing process:
router isis [vrf <vrf-name>]
Set the address for an IS-IS area:

area <area-address>
Set the IS-IS system-id:

system-id <system-id> [range <range-number>]
In the IS-IS route configuration mode, you need to define an area and designate a router to the area. In addition, you need to configure a system ID for identifying the router in the area. The ID is usually represented by an interfaces MAC address. By default, the router running IS-IS is marked as LEVEL-1-2. To optimize the network, you can change it with the command. 4. Run IS-IS on the designated interface:
ip router isis
When configuring IS-IS, you need to designate the interface on the router to run IS-IS. Enable the interface to run IS-IS after the system enters the interface mode.
Global IS-IS Parameters Configuration

If all the routers running on the network are ZXR10 routers, just use default parameters in IS-IS configuration. However, upon interconnection with routers of other manufacturers, the related interface parameters and timers need adjustment so that the IS-IS protocol can run more efficiently in the network. IS-IS parameter configuration covers global parameters and interface parameters. ISIS global parameters need to be configured in the IS-IS route mode. The configuration of some common global parameters is as follows: 1. Set the IS-IS operation type:
is-type {level-1 | level-1-2 | level-2-only}
This is a basic parameter in IS-IS configuration. It is used to define an operation type for the current router according to actual networking conditions. 2. Set the PSNP interval:
isis psnp-interval <interval> [level-1 | level-2]
PSNP is usually used on a point-to-point network. The parameter is used to set the interval between transmission of two PSNPs, and it defaults to 3. 3. Advertise self-resources shortage
set-overload-bit
Set the IS-IS OL flag bit to enable the current router to send notification to other routers when its processing capability is insufficient. 4. Generate default routes
default-information originate [always] [metric [metric-type <type>] [level-1|level-1-2|level-2] <metric-value>]
When configuring route redistribution, you need to execute this command on the router to redistribute the default route to IS-IS areas. 5. Route aggregation
summary-address <ip-address> level-1-2 | level-2] <net-mask> <metric-value> [level-1 |
IS-IS can aggregate some entries in the routing table and advertise the aggregate route, instead of advertising the all the routes. The smallest metric of the aggregated routes is selected as the aggregate routes metric.
IS-IS Interface Parameters Configuration

Interface IS-IS parameters need to be configured on the interface running IS-IS. The configuration of some typical interface parameters is introduced as follows:
1.
Set the interface operation type:

isis circuit-type {level-1|level-1-2|level-2-only}
This is a basic parameter in IS-IS configuration, used to designate an operation type for an interface. This value should be consistent with the IS-IS global operation type. 2. 3. 4. 5. Configure the interval on the interface to send Hello packets
isis hello-interval <interval> [level-1 | level-2]
Set the multiplier between the hello interval and the saving time of the interface:
isis hello-multiplier <multiplier> [level-1 | level-2]
Set the interval for transmitting LSP packets:

isis lsp-interval <interval> [level-1 | level-2]
Set the interval for repeated transmission of LSP packets, and this command is effective to the interface of the point-to-point network.
isis retrasmit-interval <interval> [level-1 | level-2]
6. 7.
Configure DIS election priority of the interface

isis priority <priority> [level-1 | level-2]
Set the metric for an IS-IS interface:

isis metric <metric-value> [level-1 | level-2]
It is used to set the interface metric for the calculation of the IS-IS shortest path. You can set different metrics for L1 and L2 on one interface. The default metric is 10. 8. Set CSNP intervals
isis csnp-interval <interval> [level-1 | level-2]
Set intervals for transmitting CSNP packets.. It defaults to 10 on the broadcast network and to 3600 on a point-to-point network.
Configuring IS-IS Authentication

ZXR10 GAR supports four types of IS-IS authentication: Inter-neighbor authentication Intra-area authentication Inter-area authentication Inter-SNP authentication
At present ZXR10 GAR supports clear text authentication and MD5 authentication.
1. 2. 3.
Configure the clear text authentication for the hello packet.

isis authentication <key> [level-1|level-2]
Configure the LSP MD5 authentication for the IS-IS. Configure the LSP authentication for the IS-IS.
authentication <key> [level-1|level-2]
Set the authentication mode as hello packet for IS-IS.

isis authentication-type {MD5 | TEXT} [level-1 | level-2]
Set authentication for SNP packet.

enable-snp-authentication
Example 1: Configure SNP clear text authentication, and the authentication character string is welcome.
ZXR10(config)#router isis ZXR10(config-router)#authentication welcome ZXR10(config-router)#enable-snp-authentication
Example 2: Configure L1 LSP MD5 authentication, and the authentication character string is welcome.
ZXR10(config)#router isis ZXR10(config-router)#authentication welcome level-1 ZXR10(config-router)#authentication-type md5 level-1
IS-IS Maintenance and Diagnosis

The ZXR10 GAR provides the s h o w command to help troubleshoot IS-IS. The commands mainly used in IS-IS maintenance and diagnosis are as follows: 1. 2. 3. 4. Check the neighborhood and show the current adjacency:
show isis adjacency [level-1 | level-2] [vrf <vrf-name>]
Show the information of the current IS-IS interface:

show isis circuits [detail] [vrf <vrf-name>]
Show the information of the current IS-IS database:

show isis database [level-1|level-2] [detail] [vrf <vrf-name>]
Show the current IS-IS topology:

show isis topology [level-1|level-2] [vrf <vrf-name>]
Besides the foresaid s h o w command, the ZXR10 GAR also offers some d e b u g commands that can be used in actual operations. Here are examples: 1. Track and show the received and transmitted IS-IS Hello packets:
debug isis adj-packets
2.
Track and show the received and transmitted IS-IS SNP packets and relevant processing events:
debug isis snp-packets
3. 4.
Track and show the debugging information of the IS-IS route calculation event:
debug isis spf-events
Track and show the debugging information of the IS-IS LSP processing event:
debug isis update-packets
Examples for IS-IS Configuration

Single-Area IS-IS Configuration
Before configuring IS-IS, you need to analyze the whole network, plan network topology based on the size of the network, and decide whether it is necessary to divide the network into areas and run multiple routing protocols on the network according to the network size. The basic configuration of IS-IS on a single-area network is as shown in Figure 91.
F I G U R E 9 1 S I N G L E A R E A I S - I S C O N F I G U R AT I O N E X AM P L E
In the above figure, R1 and R2 form Area 1 and they run IS-IS. The detailed configuration is displayed as follows: R1 configuration:
ZXR10_R1(config)#router isis ZXR10_R1(config-router)#area 01 ZXR10_R1(config-router)#system-id 00D0.D0C7.53E0 ZXR10_R1(config-router)#exit ZXR10_R1(config)#interface fei_2/4 ZXR10_R1(config-if)#ip address 192.168.2.1 255.255.255.0 ZXR10_R1(config-if)#ip router isis
ZXR10_R1(config)#interface fei_2/6 ZXR10_R1(config-if)#ip address 192.168.1.1 255.255.255.0 ZXR10_R1(config-if)#ip router isis
R2 configuration:
ZXR10_R2(config)#router isis ZXR10_R2(config-router)#area 01 ZXR10_R2(config-router)#system-id 00D0.D0C7.5460 ZXR10_R2(config-router)#exit ZXR10_R2(config)#interface fei_1/4 ZXR10_R2(config-if)#ip address 192.168.2.2 255.255.255.0 ZXR10_R2(config-if)#ip router isis ZXR10_R2(config)#interface fei_1/3 ZXR10_R2(config-if)#ip address 192.168.6.1 255.255.255.0 ZXR10_R2(config-if)#ip router isis
Chapter
14
BGP Configuration
This chapter describes configuration of the BGP.
BGP Overview
Border Gateway Protocol (BGP) is an inter-area routing protocol, exchanging Network Layer Reachable Information (NLRI) between ASs that run BGP. The information mainly includes the list of the ASs that a route passes through, which can be used to establish an AS connection state diagram. This makes the AS-based routing policy possible and solves the route loop problem. BGP of version 4 (BGP4) is the latest BGP version, which is defined in RFC1771. BGP4 supports the implementation of CIDR, supernet and subnet and the functions such as
route aggregation and route filtering. At present, BGP4 has found wide application on the Internet. A management area that has its own independent routing policy is called an autonomous system (AS). An important feature of an AS is that from the perspective of another AS, it has complete internal routes and shows identical topology for reachable destinations. The AS indicator is a 16-bit value ranging from 1 to 65535, of which the numbers between 1 to 32767 are available for allocation, those from 32768 to 64511 are reserved, and those from 64512 to 65534 are used for private ASs (similar to private network addresses in IP addresses). The session between BGP routers between different ASs is called EBGP session; BGP routers in one AS set up an IBGP session. The BGP runs over reliable transmission protocol, with the TCP as its bottom protocol and the TCP port as 179. The routers running BGP first set up a TCP connection, and then exchange all the routing table information after authentication. After that, when the routing table changes, they send route update messages to all BGP neighbors, who will further spread the routing information until it reaches the whole network. When a router sends a BGP update message regarding the destination network to its peer, the message includes the BGP metric, called path attribute. The path attributes include four independent types: 1. Recognized mandatory attribute: it must appear in the route description. AS-path Next-hop Origin 2. Recognized self-defined attribute: it does not have to appear in the route description. Local preference Atomic aggregate 3. Optional transitional attribute: It does not have to be supported by all BGP implementations. If it is supported, it can be forwarded to BGP neighbors. If it is not supported by the current router, it should be forwarded to other BGP routers. Aggregator Community 4. Optional non-transitional attribute: Routers that do not support it should be deleted. Multi-exit-discriminator (MED) Besides the above attributes, the weight attribute (defined by CISCO) is also a common attribute.
BGP Configuration
Basic BGP Configuration
Normally, the following three steps are used to start the BGP routing protocol on a router. 1. 2. 3. Start BGP process
router bgp <as-number>
Configure BGP neighbor

neighbor <ip-address> remote-as <number>
Use BGP to advertise a network

network <ip-address> <net-mask>
Figure 92 shows a BGP4 configuration example. Where, router R1 belongs to AS 100, while router R2 belongs to AS 200.
F I G U R E 9 2 B AS I C B G P C O N F I G U R A T I O N
R1 configuration:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#neighbor 10.1.1.1 remote-as 200 ZXR10_R1(config-router)#network 182.16.0.0 255.255.0.0
R2 configuration:
ZXR10_R2(config)#router bgp 200 ZXR10_R2(config-router)#neighbor 10.1.1.2 remote-as 100 ZXR10_R3(config-router)#network 182.17.0.0 255.255.0.0
In the above configuration, R1 and R2 mutually define the peer party as the BGP neighbor. As R1 and R2 belong to different ASs, they will set up an EBGP session. R1 advertises network 182.16.0.0/16 and R2 advertises network 182.17.0.0/16.
BGP Route Advertisement
In the above, the n e t w o r k command is used to advertise BGP routers. Generally, after setting up BGP neighbors, you can use three approaches to advertise BGP routes. 1. Use the n e t w o r k command to advertise routes. In BGP, the n e t w o r k command can be used to advertise the networks known to the current router. The known networks can be learnt through direct, static and dynamic routes. The use of the n e t w o r k command in BGP is different from that in IGP. 2. The r e d i s t r i b u t e command can redistribute routes of IGPs (RIP, OSPF and ISIS) into BGP.
redistribute tag>] <protocol> [metric <metric-value>] [route-map <map-
When using the r e d i s t r i b u t e command, you need to avoid redistributing the routes that IGP learns from BGP to BGP again, and use filter commands to prevent loop if necessary.
3. 4.
Distribute static routes to BGP. As for the static routes redistributed to BGP, their source is shown as incomplete in the routing table.
Figure 93 shows an example of advertising routes to BGP by redistribution.

FIGURE 93 BGP ROUTE ADV ERTIS EMENT CONFIGURATI ON
ZXR10_R3(config)#router ospf 1 ZXR10_R3(config-router)#network area 0 ZXR10_R3(config)#router bgp 200 ZXR10_R3(config-router)#neighbor 1.1.1.1 remote-as 300 ZXR10_R3(config-router)#redistribute ospf 175.220.0.0 0.0.0.255
BGP Aggregate Advertisement

BGP can aggregate multiple learnt routes to one route and advertise it via the a g g r e g a t e - a d d r e s s command, so that the entries in a routing table can be significantly reduced.
1. aggregate-address <ip-address> set] [summary-only] [strict] <net-mask> [count <count>] [as-
2.
aggregate-address <ip-address> <net-mask> subnet <subnet-address> <subnet-mask>
The following section shows a route aggregate example: As shown in Figure 94, R1 and R2 advertise routes 170.10.0.0/16 and 170.20.0.0/16 respectively. R3 aggregates the two routes into 170.0.0.0/8 and advertises it to R4. After route aggregate is configured, R4s routing table can only learn the aggregate route 170.0.0.0/8.
FIGURE 94 BGP AGG REG ATE ADV ERTIS EMENT CONFIGURATION
R1 configuration:
ZXR10_R1(config)#interface fei_1/1 ZXR10_R1(config-if)#ip address 2.2.2.2 255.0.0.0 ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#network 170.20.0.0 255.255.0.0 ZXR10_R1(config-router)#neighbor 2.2.2.1 remote-as 300
R2 configuration:
ZXR10_R2(config)#interface fei_1/1 ZXR10_R2(config-if)#ip address 3.3.3.3 255.0.0.0 ZXR10_R2(config)#router bgp 200 ZXR10_R2(config-router)#network 170.10.0.0 255.255.0.0 ZXR10_R2(config-router)#neighbor 3.3.3.1 remote-as 300
R3 configuration:
ZZXR10_R3(config)#interface fei_1/1 ZXR10_R3(config-if)#ip address 2.2.2.1 255.0.0.0 ZXR10_R3(config)#interface fei_1/2 ZXR10_R3(config-if)#ip address 3.3.3.1 255.0.0.0 ZXR10_R3(config)#interface fei_1/3 ZXR10_R3(config-if)#ip address 4.4.4.1 255.0.0.0 ZXR10_R3(config)#router bgp 300 ZXR10_R3(config-router)#neighbor 2.2.2.2 remote-as 100 ZXR10_R3(config-router)#neighbor 3.3.3.3 remote-as 200 ZXR10_R3(config-router)#neighbor 4.4.4.4 remote-as 400 ZXR10_R3(config-router)#aggregate-address 170.0.0.0
255.0.0.0 summary-only
R3 learns both routes 170.20.0.0 and 170.10.0.0, but it only advertises the aggregate route 170.0.0.0/8. Pay attention to the parameter summary-only in the command. Without that parameter, R3 will advertise both routes in addition to the aggregate route. R4 configuration:
ZXR10_R4(config)#interface fei_1/1 ZXR10_R4(config-if)#ip address 4.4.4.4 255.0.0.0 ZXR10_R4(config)#router bgp 400 ZXR10_R4(config-router)#neighbor 4.4.4.1 remote-as 300
Multihop Configuration in EBGP

Usually, EBGP neighbor is established on the interfaces directly connecting two routers. If EBGP neighbor is to be established on indirectly connected interfaces, you need to use the n e i g h b o r ebgp-multihop command to perform EBGP multihop configuration, as well as suitable IGP or static routing configuration to enable indirectly connected neighbors to communicate with each other.
neighbor <ip-address> ebgp-multihop [ttl <value>]
As shown in Figure 95, router R1 needs to set up adjacency on a non-directly connected interface (with the IP address of 180.225.11.1) of R2. Then you need to use the n e i g h b o r e b g p - m u l t i h o p command.
F I G U R E 9 5 C O N F I G U R AT I O N O F B G P M U L T I H O P
R1 configuration:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#neighbor 300 ZXR10_R1(config-router)#neighbor multihop 180.225.11.1 ebgp180.225.11.1 remote-as
R2 configuration:
ZXR10_R2(config)#router bgp 300 ZXR10_R2(config-router)#neighbor 100 129.213.1.2 remote-as
Filtering Routes by Router

Route filtering and attribute configuration are the basis of BGP decision-making. Route filtering allows you to control the attributes of the imported and exported routes based on needs. The route map is used to control the routing information and redistribute routes between areas by defining conditions. The route map usually works with the route attributes to make routing decisions. Follow these two steps to use a route map: 1. 2. Define a route map
route-map <map-tag>[permit|deny][<sequence-number>]
Filter the routes advertised to/from neighbors or configure priorities for them.
neighbor <ip-address> route-map <map-tag> {in|out}
The following example shows how to configure route filtering by routers.

ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#neighbor 200 ZXR10_R1(config-router)#neighbor MAP1 out ZXR10_R1(config-router)#neighbor 182.17.20.1 send-med ZXR10_R1(config)#route-map MAP1 permit 10 ZXR10_R1(config-route-map)#match ip address 1 ZXR10_R1(config-route-map)#set metric 5 ZXR10_R1(config)#access-list 0.0.255.255 1 permit 172.3.0.0 182.17.20.1 route-map 182.17.20.1 remote-as
A route map MAP1 is defined in the above example. This route map allows advertising network 172.3.0.0 to AS 200 and sets its MED as 5. The route map is often used with the m a t c h command and the s e t command. The m a t c h command defines the match conditions, and the s e t command defines the action to be executed when match conditions set by the m a t c h command are met.
Filtering Routes via NLRI

To set limit to a router when it gets or advertise the routing information, we can filter the route updates from or destined for a particular neighbor. The filter has an update list of the neighbors where the route updates are from or destined for.
As shown in Figure 96, R1 and R2 are IBGP peers; R1 and R3 are EBGP peers; R2 and R4 are EBGP peers.
FIGURE 96 FILTERING ROUTES USING NLRI
To avoid AS100 from being a transitional AS, and advertise the network 192.18.10.0/24 from AS300 to AS200, we need to perform filtering on R1. The configuration is as follows:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#no synchronization ZXR10_R1(config-router)#neighbor 182.17.1.2 remote-as 100 ZXR10_R1(config-router)#neighbor 200 ZXR10_R1(config-router)#neighbor MAP1 out ZXR10_R1(config)#route-map MAP1 permit 10 ZXR10_R1(config-route-map)#match ip address 1 ZXR10_R1(config)#access-list 1 deny 192.18.10.0 0.0.0.255 ZXR10_R1(config)#access-list 255.255.255.255 1 permit 0.0.0.0 182.17.20.1 route-map 182.17.20.1 remote-as
In this example, the r o u t e - m a p command and the access list command a c c e s s l i s t are used to prevent R1 from advertising prefix 192.18.10.0/24 to AS200.
Filtering Route via AS_PATH

When all the routes in one or more ASs are to be filtered, we usually use the AS-pathbased route filtering method. It can avoid the complexity caused by prefix filtering. An access list can be specified for input and output updates on the basis of AS path attributes with the following command..
ip as-path access-list regular-expression>
<access-list-number>
{permit|deny}
<as-
As shown in Figure 96, AS path-based route filtering can also be used to prevent R1 from advertising the network 192.18.10.0/24 from AS300 to AS200. The configuration is as follows:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#no synchronization ZXR10_R1(config-router)#neighbor 182.17.1.2 remote-as 100 ZXR10_R1(config-router)#neighbor 200 ZXR10_R1(config-router)#neighbor MAP1 out ZXR10_R1(config)#route-map MAP1 permit 10 ZXR10_R1(config-route-map)#match as-path 1 ZXR10_R1(config)#ip as-path access-list 1 permit ^$ 182.17.20.1 route-map 182.17.20.1 remote-as
In this configuration, the list is accessed through AS paths, which makes R1 advertise only the networks from AS100 to AS200, so that the network 192.18.10.0/24 can be filtered.
LOCAL_PREF Attribute
The value of the Local preference attribute is used for routing between the IBGP peers inside an AS. Configure the local priority of the routes advertised by the BGP with the following command.
bgp default local-preference <value>
When the two IBGP routers synchronously learn the route to the same destination from outside, their Local preference values are compared. The route with the greater value is preferential. The default value of the Local preference is 100. As shown in Figure 97, R3 and R4 synchronously learn the route to 170.10.0.0. Since the Local preference value of R4 is greater, internal AS256 to the destination has the preference to pass R4.
F I G U R E 9 7 L O C AL R E F E R E N C E AT T R I B U T E C O N F I G U R AT I O N
There are two modes used to configure the LOCAL_PREF attribute as follows. 1. Set the LOCAL_PREF attribute with the bgp default local-preference command. R3 configuration:
ZXR10_R3(config)#router bgp 256 ZXR10_R3(config-router)#neighbor 1.1.1.1 remote-as 100 ZXR10_R3(config-router)#neighbor 256 ZXR10_R3(config-router)#bgp default local-preference 150 128.213.11.2 remote-as
R4 configuration:
ZXR10_R4(config)#router bgp 256 ZXR10_R4(config-router)#neighbor 3.3.3.2 remote-as 300 ZXR10_R4(config-router)#neighbor 256 ZXR10_R4(config-router)#bgp default local-preference 200 128.213.11.1 remote-as
2.
Set the LOCAL_PREF attribute with the r o u t e - m a p command. R4 configuration:
ZXR10_R4(config)#router bgp 256 ZXR10_R4(config-router)#neighbor 3.3.3.2 remote-as 300 ZXR10_R4(config-router)#neighbor setlocalin in ZXR10_R4(config-router)#neighbor 256 .... 128.213.11.1 remote-as 3.3.3.2 route-map
ZXR10_R4(config)#ip as-path access-list 7 permit ^300$ ... ZXR10_R4(config)#route-map setlocalin permit 10 ZXR10_R4(config-route-map)#match as-path 7 ZXR10_R4(config-route-map)#set local-preference 200 ZXR10_R4(config)#route-map setlocalin permit 20 ZXR10_R4(config-route-map)#set local-preference 150
MED Attribute
The Metric attribute is also called the Multi_Exit_Discrimination attribute (MED), which is used for the exchanging between ASs to decide the route. The router only compares the adjacent Metric value of the BGP from the same AS by default. If comparing adjacent Metric values of neighbors from different ASs, it is necessary to use b g p a l w a y s - c o m p a r e - m e d command to compare them by force. The Metric value is 0 by default. The smaller Metric value is more preferential. The Metric value is not delivered to the third AS. Namely, when receiving the update with the Metric value, the Metric value by default will be delivered if the update needs to be delivered to the third AS. As shown in Figure 98, the R1 receives the 180.10.0.0 update from the R2, the R3 and the R4 synchronously. Only compare the Metric values of the adjacent R3 and R4 from the same AS by default; the Metric value of the R3 is smaller than that of the R4. Therefore, for the 180.10.0.0 update, the R1 preferentially uses the R3.
F I G U R E 9 8 C O N F I G U R AT I O N O F T H E M E D A T T R I B U T E
The r o u t e - m a p command is used to set the MED value as follows. R1 configuration:

ZXR10_R1(config)#router bgp 100
ZXR10_R1(config-router)#neighbor 2.2.2.1 remote-as 300 ZXR10_R1(config-router)#neighbor 3.3.3.2 remote-as 300 ZXR10_R1(config-router)#neighbor 4.4.4.1 remote-as 400
R3 configuration:
ZXR10_R3(config)#router bgp 300 ZXR10_R3(config-router)#neighbor 2.2.2.2 remote-as 100 ZXR10_R3(config-router)#neighbor setmetricout out ZXR10_R3(config-router)#neighbor 1.1.1.2 remote-as 300 ZXR10_R3(config)#route-map setmetricout permit 10 ZXR10_R3(config-route-map)#set metric 120 2.2.2.2 route-map
R4 configuration:
ZXR10_R4(config)#router bgp 300 ZXR10_R4(config-router)#neighbor 3.3.3.1 remote-as 100 ZXR10_R4(config-router)#neighbor setmetricout out ZXR10_R4(config-router)#neighbor 1.1.1.1 remote-as 300 ZXR10_R4(config)#route-map setmetricout permit 10 ZXR10_R4(config-route-map)#set metric 200 3.3.3.1 route-map
R2 configuration:
ZXR10_R2(config)#router bgp 400 ZXR10_R2(config-router)#neighbor 4.4.4.2 remote-as 100 ZXR10_R2(config-router)#neighbor setmetricout out ZXR10_R2(config)#route-map setmetricout permit 10 ZXR10_R2(config-route-map)#set metric 50 4.4.4.2 route-map
The command b g p a l w a y s - c o m p a r e - m e d is used to compare the metric values of R1 and R2 by force as follows. The Metric value of the R2 is smaller than that of the R3. Therefore, for the 180.10.0.0 update, the R1 selects the R2 rather than the R3.
R1 configuration:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#neighbor 2.2.2.1 remote-as 300 ZXR10_R1(config-router)#neighbor 3.3.3.2 remote-as 300 ZXR10_R1(config-router)#neighbor 4.4.4.1 remote-as 400
ZXR10_R1(config-router)#bgp always-compare-med
Community String Attribute

Community string attribute is an delivered optional attribute which ranges from 1 to 4294967295.According to the Community attribute, decisions can be made on a group of routes. Several recognized definitions of the Community attribute are as follows: no-export: Forbid advertising the neighbors of the EBGP. no-export: Forbid advertising any neighbors of the BGP. no-export-subconfed: Forbid advertising the route with the attribute outside the confederation. In addition, GAR V2.6 supports community attribute of the general value which has two forms of community attribute:
<1~4294967295> Community number
<1~65535>:<0~65535> Community number in < aa:nn > format
Where, the format aa:nn is transformed into a general value of a long integer number with the formula aa * 65536 + nn. set community 1000:1 The equivalence is set community 65536001 Normally, the r o u t e - m a p command is used to define attribute to the community. By default, the community attribute will not be sent to neighbors. The following command needs to be used in conjunction to send community attribute when routes are advertised to neighbors.
neighbor <ip-address> send-community
For example, configure route-map and community attribute is 1000:1 (namely 65536001)
ZXR10(config)#route-map xpzhou ZXR10(config-route-map)#set ZXR10(config-route-map)#set comm ZXR10(config-route-map)#set community ? <1-4294967295> Community number no-advertise no-export community) no-export-subconfed known community) Do not send outside local AS(wellDo not export to Do not advertise to <1-65535>:<0-65535> Community number in aa:nn format any peer(well-known community) next AS(well-known
ZXR10(config-route-map)#set community 1000:1 ZXR10(config-route-map)#show route-map xpzhou route-map xpzhou, permit, sequence 10 Match clauses: Set clauses: community 65536001
In addition, GAR V2.6 supports the filtering of community attribute of the general value which expanding the community attribute-based filtering. In the following configuration, R1 will advertise to its neighbors not to advertise routes of 192.166.1.0/24 to other EBGP neighbors.R1 configuration:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#neighbor 3.3.3.3 remote-as 300 ZXR10_R1(config-router)#neighbor 3.3.3.3 send-community ZXR10_R1(config-router)#neighbor setcommunity out ZXR10_R1(config)#route-map setcommunity permit 10 ZXR10_R1(config-route-map)#match ip address 1 ZXR10_R1(config-route-map)#set community no-export ZXR10_R1(config)#route-map setcommunity permit 20 access-list 1 permit 192.166.1.0.0.0.0.255 3.3.3.3 route-map
BGP Synchronization
As shown in Figure 99, in AS100, R1 and R2 run IBGP, and R5 is a non-BGP router.
F I G U R E 9 9 C O N F I G U R AT I O N O F T H E B G P S Y N C H R O N I Z AT I O N
The R2 learns to the route 170.10.0.0 through the IBGP. The next-hop is 2.2.2.1. From the figure, if the R2 reaches the 170.10.0.0, the actual next-hop is the R5. But without the route 170.10.0.0 the R5 will throw off the packet. At the moment, the R2 is also thrown off in the R5 if the R2 notifies the R4 that it has the route 170.10.0.0 itself. It is necessary to make the R5 have the route to the 170.10.0.0 if the packet with the destination of 170.10.0.0 smoothly passes the R5 and reaches the R3. Therefore, the route redistribution should be used to help the R5 learn the route through the IGP. The R2 must wait for the R2 to learn the route by means of the IGP (through the R5) before it advertises the BGP route to the EBGP neighbor. This is called the route synchronization. Synchronize both the BGP and the IGP with the s y n c h r o n i z a t i o n command. The synchronization function of the ZXR10 GAR is booting by default. For the transitional AS, the route learned from other AS should be advertised to the third party AS. If the non-BGP route exists inside the AS, the route synchronization should be used. Here, the R2 adopts route synchronization. It is unnecessary to use the route synchronization when not advertising the BGP route to the third party AS or when the routers inside the As run the BGP. In the following configuration, close the R2 route synchronization.
ZXR10_R2(config)#router bgp 100 ZXR10_R2(config-router)#network 150.10.0.0 ZXR10_R2(config-router)#neighbor 1.1.1.2 remote-as 400 ZXR10_R2(config-router)#neighbor 3.3.3.1 remote-as 100 ZXR10_R2(config-router)#no synchronization
BGP Router Reflector

For BGP routes in the same AS, an adjacency should be set up between any two routers. Thus, as the number of the IBPG routers increases, the number of neighbors will ascend by n(n-1)/2 (n refers to the number of the IBGP routers). The router reflector and the confederation is used to reduce the workload of maintenance and configuration. For the running IBGP routers inside the AS, one of the preceding routers is selected as the Router Reflector (RR) and other IBGP routers as clients, which only establish the adjacency with the RR. All clients pass the RR to reflect routes. Thus, the number of neighbors decreases to n-1. The following command is used to set a neighbor as the peer entity of route reflector client.
neighbor <ip-address> router-refletor-client
As shown in Figure 100, the AS100 has two router reflectors: the R3 and the R4. Among them, the R4 clients are the R5 and the R6. The R3 clients are the R1 and the R2.
FIGURE 100 CONFIGURATION OF THE BGP ROUTER REFLECTOR
R3 configuration:
ZXR10_R3(config)#router bgp 100 ZXR10_R3(config-router)#neighbor 2.2.2.2 remote-as 100 ZXR10_R3(config-router)#neighbor client ZXR10_R3(config-router)#neighbor 1.1.1.1 remote-as 100 ZXR10_R3(config-router)#neighbor client ZXR10_R3(config-router)#neighbor 7.7.7.7 remote-as 100 ZXR10_R3(config-router)#neighbor 4.4.4.4 remote-as 100 1.1.1.1 route-reflector2.2.2.2 route-reflector-
R2 configuration:
ZXR10_R2(config)#router bgp 100 ZXR10_R2(config-router)#neighbor 3.3.3.3 remote-as 100
When a route is received by the RR, the RR reflects according to types of different peers. 1. 2. 3. If a route comes from non-client peers, it is reflected to all client peers. If a route comes from client peers, it is reflected to all non-client peers and client peers. If a route comes from the EBGP peer, it is reflected to all non-client peers and client peers.
If an AS has multiple RRs inside, the multiple RRs in the internal AS can be incorporated into a cluster. There may be multiple clusters inside one AS. A cluster contains more than one RR.
BGP Confederation
The route confederation has the same function as the router reflector. The purpose is to reduce the number of the IBGP connection neighbors established inside the same AS. The route confederation divides an AS into multiple sub-ASs; multiple IBGP routers inside the AS belongs respectively to sub-ASs; the IBGP is established inside the subAS; the EBGP is established between sub-ASs. The sub-AS number is called confederation number. But for the AS outside, the sub-AS is invisible. 1. 2. Set the confederation ID:
bgp confederation identifier <value>
Set the confederation peer AS number:

bgp confederation peers <value> [<value>]
The following is an example for explaining the application of the router confederation.
As shown in Figure 101, AS200 has five BGP routers, which is divided into two subASs. One is defined as AS65010 (containing routers R3, R5 and R6), and the other is defined as AS65020 (consisting of routers R4 and R7).
FIGURE 101 CONFIGURATION OF THE BGP CONFEDERATI ON
R3 configuration:
ZXR10_R3(config)#router bgp 65010 ZXR10_R3(config-router)#bgp confederation identifier 200 ZXR10_R3(config-router)#bgp confederation peers 65020 ZXR10_R3(config-router)#neighbor 65010 ZXR10_R3(config-router)#neighbor 65010 ZXR10_R3(config-router)#neighbor 65020 ZXR10_R3(config-router)#neighbor 2.2.2.2 remote-as 100 210.61.19.2 remote-as 210.61.20.1 remote-as 210.61.10.1 remote-as
R5 configuration:
ZXR10_R5(config)#router bgp 65010 ZXR10_R5(config-router)#bgp confederation identifier 200 ZXR10_R5(config-router)#neighbor 65010 ZXR10_R5(config-router)#neighbor 65010 210.61.20.1 remote-as 210.61.30.1 remote-as
When establishing the adjacency, the EBGP adjacency between the R3 and the confederation peers is established; the IBGP adjacency in the confederation is established; this adjacency also occurs between the R3 and the AS100. AS100 does not know whether the confederation exists. Therefore, router R1 in AS100 still sets up adjacency with R3 by using AS200. R1 configuration:
ZXR10_R1(config)#router bgp 100 ZXR10_R1(config-router)#neighbor 2.2.2.1 remote-as 200
BGP Route Dampening

The BGP provides the Route dampening mechanism to reduce the stability caused by Route Flap. Each time the flap occurs, the route is given a Penalty 1000. The route will be suppressed to advertise when the Penalty reaches the Suppress-limit. Each time the half-life-time comes, the Penalty exponentially decreases . The suppressed and advertised route will be cancelled when the Penalty decreases to the Reuse-limit. Make the BGP route damping effective or modify the BGP route damping factors with the following command.
bgp dampening [<half-life> route-map <map-tag>] <reuse> <suppress> <max-suppress-time>|
Half-life-time: the range is from 1 to 45min and the default value is 15min. Reuse-value: the range is from 1 to 20000, and the default value is 750. Suppress-value: the range is from 1 to 20000, and the default value is 2000. Max-suppress-time: the range is from 1 to 255, four times as half-life-time by default.
Boot the suppression function in the router:

ZXR10(config)#router bgp 100 ZXR10(config-router)#bgp dampening ZXR10(config-router)#network 203.250.15.0 255.255.255.0 ZXR10(config-router)#neighbor 192.208.10.5 remote-as 300
BGP Maintenance and Diagnosis

When encountering the BGP route problems, faults are located and removed with relevant debugging commands. The s h o w command is most frequently used. View the current BGP neighbor state, the BGP route information, etc, with the s h o w command. 1. Display the configuration information of the BGP module:
show ip bgp protocol
2. 3. 4.
View the BGP adjacency and show the current neighbor state:
show ip bgp neighbor [[vrf <vrf-name>] <ip-address>] show ip bgp neighbor [in|out] <ip-address> show ip bgp neighbor [vrf-in|vrf-out] <ip-address> <vrf-name> show ip bgp neighbor [vpnv4-in|vpnv4-out] <ip-address>
Display the BGP routing table entries:

show ip bgp route [network <ip-address> [mask <net-mask>]]
Display the connection state of all BGP neighbors:

show ip bgp summary
Besides the s h o w command, we also use the d e b u g command to observe the establishment process of the BGP adjacency, route updating process, etc. 1. Trace and show the notification packet sent by the BGP, list the error number and sub-error number:
debug ip bgp in
2.
Trace and show the notification packet sent by the BGP, list the error number and sub-error number:
debug ip bgp out
3.
Trace and display the transition of state machine connected to the BGP:
debug ip bgp events
The next example is to trace the state transition of the BGP with the d e b u g i p b g p e v e n t s command:
ZXR10#debug ip bgp events BGP events debugging is on ZXR10# 04:10:07: BGP: 192.168.1.2 reset due to Erroneous BGP Open received 04:10:07: BGP: 192.168.1.2 went from Connect to Idle 04:10:08: BGP: 192.168.1.2 went from Idle to Connect 04:10:13: BGP: 192.168.1.2 went from Connect to OpenSent 04:10:13: OpenConfirm 04:10:13: Established ZXR10# BGP: 192.168.1.2 went from OpenConfirm to BGP: 192.168.1.2 went from OpenSent to
BGP Configuration Example
The following is a BGP comprehensive example. It involves the actual applications of such BGP functions as route aggregation and static route redistribution. As shown in Figure 102, the R4 establishes the EBGP with the R1; the R1 establishes the IBGP with the R2; the R2 establishes the multi-hop EBGP with the R5. Supposing the R4 has four static routes marked in the top right corner of the Figure. In the R4 configuration, only aggregate and advertise the network segment 192.16.0.0/16, and forbid advertising the network segment 170.16.10.0/24 the outside by the BGP through the route figure. The EBGP multi-hop relationship is established between the R2 and the R5 through the R3. At the moment, ensure that the addresses on which to establish adjacency can be interconnected in the two routers.
F I G U R E 1 0 2 B G P C O N F I G U R AT I O N E X AM P L E
R4 configuration:
ZXR10_R4(config)#route bgp 2 ZXR10_R4(config-router)#redistribute static ZXR10_R4(config-router)#neighbor 172.16.20.2 remote-as 1 ZXR10_R4(config-router)#aggregate-address 255.255.0.0 count 0 as-set summary-only ZXR10_R4(config-router)#neighbor torouter1 out ZXR10_R4(config)#access-list 0.0.0.255 ZXR10_R4(config)#route-map torouter1 deny 10 ZXR10_R4(config-route-map)#match ip address 1 ZXR10_R4(config)#route-map torouter1 permit 20 1 permit 172.16.10.0 172.16.20.2 route-map 192.16.0.0
R1 configuration:
ZXR10_R1(config)#route bgp 1
ZXR10_R1(config-router)#no synchronization ZXR10_R1(config-router)#neighbor 172.16.1.2 remote-as 1 ZXR10_R1(config-router)#neighbor 172.16.1.2 next-hop-self ZXR10_R1(config-router)#neighbor 172.16.20.1 remote-as 2
R2 configuration:
ZXR10_R2(config)#ip route 183.16.0.0 255.255.0.0 fei_1/4 ZXR10_R2(config)#route bgp 1 ZXR10_R2(config-router)#neighbor 172.16.1.1 remote-as 1 ZXR10_R2(config-router)#neighbor 172.16.1.1 next-hop-self ZXR10_R2(config-router)#neighbor 183.16.20.2 remote-as 3 ZXR10_R2(config-router)#neighbor multihop 2 ZXR10_R2(config-router)#neighbor torouter5 in ZXR10_R2(config)#access-list 0.0.0.255 ZXR10_R2(config)#route-map torouter5 deny 10 ZXR10_R2(config-route-map)#match ip address 1 ZXR10_R2(config)#route-map torouter5 permit 20 1 permit 155.16.10.0 183.16.20.2 route-map 183.16.20.2 ebgp-
R5 configuration:
ZXR10_R5(config)#ip route 173.16.0.0 255.255.0.0 gei_1/1 ZXR10_R5(config)#route bgp 3 ZXR10_R5(config-router)#neighbor 173.16.20.2 remote-as 1 ZXR10_R5(config-router)#neighbor multihop 2 173.16.20.2 ebgp-
Chapter
15
This chapter describes configuration of the BGP policy.
Policy Routing Overview

Traditionally, the router searches the routing table to obtain next-hop to forward the packets based on the destination address. The routing table is statically designated by the network administrator or dynamically generated via routing protocols. Compared with traditional routing, policy-based routing is more functional and more flexible. It enables the administrator to select the forwarding route not only by the destination address, but also according to application of the packet (TCP/UDP) or the source IP address. On controlling the packet forwarding, policy-based routing is stronger in the controlling capacity than the traditional routing. Policy routing can implement traffic engineering to a certain extent, thus making traffic of different service quality or different service data (such as voice and FTP) to go to different paths. The user has higher and higher requirements for network performance, therefore it is necessary to select different packet forwarding paths based on the differences between services or user categories. On the ZXR10 GAR, network administrator can define different Route-maps with statement of m a t c h and s e t , then apply the Route-map to the interface for receiving packets to implement route selection. There is series of sequences in each Route-map, and each sequence contains many clauses with m a t c h and s e t . The m a t c h clause defines the matching requirement. When incoming messages meet the requirement, run the policy routing. The s e t clause defines the routing action when the requirements of the Match clause is met. When the m a t c h requirements in one of the sequences are not met, go to next sequence. For the packet received by the router, first judge whether the incoming interface binds the policy route. If not, forward it based on searching routing in the destination address. If the interface is bound with the policy routing, operate according to the sequence of the Route-map in order. The detailed process is as follows: 1. First, use the packet to match the ACL configured in the first sequence. If it fails, then try the ACL in the next sequence, and likewise. If the match is successful, then judge the attribute in that sequence. If the attribute of the sequence is deny, route is normal; if the attribute is permit, then forward it with s e t item according to that sequence. Judge whether there is a valid set ip next-hop item. When there are more than one
s e t i p n e x t - h o p items (direct next-hop), select the first valid next-hop according
2. 3.
to the configured order; if it exists, packet should be sent to the configured nexthop.
4.
If s e t i p n e x t - h o p is not configured or there is no valid one, it is necessary to check if there is a valid outcoming interface (it exists and the status is UP).When there are more than one s e t i n t e r f a c e items, select the first valid outer interface according to the configured order; if it exists, packet should be sent directly from it, otherwise a normal route is taken. When taking a normal route, packet should be forwarded based on it if the corresponding routing can be found in the forwarding table; otherwise forward it according to the valid set ip default next-hop item (direct next-hop) configured in policy routing. When there are more than one s e t i p d e f a u l t n e x t - h o p items, select the first valid next-stop by default according to the configured order. If s e t i p d e f a u l t n e x t - h o p is not configured or there is no valid one, forward it according to the valid s e t d e f a u l t i n t e r f a c e item configured in policy routing. When there are more than one set default interfaces, select the first valid outer interface by default according to the configured order. If s e t d e f a u l t i n t e r f a c e is not configured or there is no valid one, forward it by default routing. If there is no configured routing by default in the system, throw the packet away.
5.
6.
7. 8.
Note: Sequence (from top to the bottom) of the route selection for forwarding data packet is: policy routing, normal routing and default routing.

Policy routing configuration covers the following contents: 1. Create a Route-map for policy routing, and access to mapping configuration mode of routes.
route-map <map-tag> [permit|deny] [<sequence-number>]
2.
Set match and set item under the mode of mapping configuration mode. Policy route the packets matched with the access list.
match ip address <access-list-number> [<access-list-number>]
Route the data packet to the next-hop when the packet can be policy routed.
set ip next-hop <ip-address> [ <ip-address>]
Route the data packet to the designated interface when the packet can be policy routed.
set interface <interface-name> [ <interface-name>]
Route the data packet to the designated next-hop when the data packet can be policy routed while there is no definite route to the destination.
set ip default next-hop <ip-address> [ <ip-address>]
Route the data packet to the designated interface when the data packet can be policy routed while there is no definite route to the destination
set default interface <interface-name> [ <interface-name>]
3.
Configure the policy routing based express forwarding for the port incoming messages.
ip policy route-map <map-tag>
Examples for Policy Routing Configuration

When there are many Internet Service Provider (ISP) egresses on the network, select different ISP egresses for users from different groups via policy routing, or select different ISP egresses based on service types.
Policy Routing Configuration Example 1

As shown in Figure 103 two sub-network users are connected to the router via different interfaces. Two ISP egresses are to be used which are differently selected according to the users IP address. Egress ISP1 is valid for the IP address that belongs to the user service of the sub-network 10.10.0.0/24 and Egress ISP2 is valid for the IP address that belongs to the user service of the sub-network 11.11.0.0/24.
F I G U R E 1 0 3 P O L I C Y R O U T I N G C O N F I G U R A T I O N E X AM P L E 1
interface fei_1/1 description To User1 ip address 10.10.0.254 255.255.255.0 ip policy route-map source-ip ! interface fei_1/2 description To User1 ip address 11.11.0.254 255.255.255.0 ip policy route-map source-ip ! interface fei_2/1
description To ISP1 ip address 100.1.1.2 255.255.255.252 ! interface fei_2/2 description To ISP2 ip address 200.1.1.2 255.255.255.252 ! ip route 0.0.0.0 0.0.0.0 100.1.1.1 ! access-list 10 permit 10.10.0.0 0.0.0.255 access-list 20 permit 11.11.0.0 0.0.0.255 ! Route-map source-ip permit 10 /* Forward the packet matched to the ACL 10 to 100.1.1.1*/ match ip address 10 set ip next-hop 100.1.1.1 ! route-map source-ip permit 20 /* Forward the packet matched to the ACL 20 to 200.1.1.1*/ match ip address 20 set ip next-hop 200.1.1.1
In this example, the service connection is as follows: 1. 2. When egress of ISP1 and ISP2 are normal, users service on sub-network 10.10.0.0/24 and 11.11.0.0/24 routes to ISP1 and ISP2 respectively. When egress of ISP1 is normal and egress of ISP2 is abnormal, users service of the two sub-network routes to egress of ISP1. At that time, users service of network 11.11.0.0/24 uses default routing. When egress of ISP1 is abnormal and egress of ISP2 is normal, users service of sub-network 11.11.0.0/24 is normal, but the service for users in sub-network 10.10.0.0/24 is cut off.
3.
Policy Routing Configuration Example 2

As shown in Figure 104, when different sub-network users are connected via the same interface of the router, the configuration of the policy routing should have corresponding change.
F I G U R E 1 0 4 P O L I C Y R O U T I N G C O N F I G U R A T I O N E X AM P L E 2
interface fei_1/1 description To User ip address 192.168.1.1 255.255.255.252 ip policy route-map source-ip ! interface fei_2/1 description To ISP1 ip address 100.1.1.2 255.255.255.252 ! interface fei_2/2 description To ISP2 ip address 200.1.1.2 255.255.255.252 ! ip route 10.10.0.0 255.255.255.0 192.168.1.2 ip route 11.11.0.0 255.255.255.0 192.168.1.2 ! access-list 10 permit 10.10.0.0 0.0.0.255 access-list 20 permit 11.11.0.0 0.0.0.255 ! route-map source-ip permit 10 /*Forward the packet matched to the ACL 10 to 100.1.1.1 and 200.1.1.1 is a standby egress*/ match ip address 10 set ip next-hop 100.1.1.1 200.1.1.1 ! route-map source-ip permit 20 /*Forward the packet matched to the ACL 20 to 200.1.1.1 and 100.1.1.1 is a standby egress*/ match ip address 20 set ip next-hop 200.1.1.1 100.1.1.1 !
In this example, two ISP egresses are standby for each other. the service connection is as follows: 1. 2. When egress ISP1 and ISP2 are normal, service of users on sub-network 10.10.0.0/24 and 11.11.0.0/24 moves to ISP1 and ISP2 respectively. When one of the egresses is in failure, the corresponding service of the user on the sub-network will route to the standby egress. So, if only two egresses be not abnormal at the same time, service would not be cut off.
Chapter
16
MPLS Configuration
This chapter describes configuration of the MPLS technology.
Overview
Multi-Protocol Label Switching (MPLS) is a multi-layer switching technology, which combines L2 switching technologies with L3 routing technologies and uses labels to aggregate forwarding information. MPLS runs under the routing hierarchy, supports multiple upper-level protocols and can be implemented on multiple physical platforms. Label switching can be visually imagined as postal codes for mails. With the application of postal codes, the destination addresses and some special requirements (such as QoS, CoS and management information) of the mails are coded in a certain method to facilitate rapid and efficient mail processing and speed up the routing of the mails to individual destinations. The basic concept of MPLS is the assignment of labels, that is, labels are bound with network layer routes. The basic routing mode of MPLS is hop-by-hop routing, allowing a forwarding mechanism simpler than that of the data packet, so as to achieve more rapid routing. Since the common label allocation method and generic routing protocols are used in multiple types of media (such as packets, cells and frames), MPLS supports efficient definite routing mode (such as QoS) that can be used to fulfill different purposes, common traffic engineering method and other operation modes.
LDP (Label Distribution Protocol) is the core protocol of MPLS. LDP works in conjunction with standard network layer routing protocols and distributes label information among different pieces of equipment on an MPLS network in the connectionless working mode. In addition, MPLS can employ the working mode that enables resource reservation but establishes connection inexplicitly. That is, it employs the protocols of RSVP and RSVPLSP-TUNNEL, mainly for traffic engineering. In addition, CRLDP (Constrained-based Routing LDP) executes some routes with definite paths. LDP divides Forwarding Equivalence Class (FEC) based on IP prefixes. In an MPLS network, internal gateway protocols are used to discover the information about IP prefixes. When a Label Switch Router (LSR) discovers such information, it will distribute a label to the FEC and advertise the label to all upstream LDP neighbors. The hop-by-hop dynamic label distribution of LDP leads to the generation of a series of labeled paths, called Label Switched Paths (LSPs). Along these LSPs, the label traffic can pass the MPLS backbone to reach a designated destination. With this capability, a service provider can deploy MPLS-based IP VPN, as well as the IP + ATM service over multi-proxy MPLS networks. The propagation process of IP packets via the MPLS backbone is as follows: 1. An ingress border LSR receives a packet, puts the packet into an FEC and then uses the outgoing label corresponding to the FEC to label the packet. For a unicast IP route based on destination address, the FEC corresponds to a destination subnet. A backbone LSR receives the labeled packet, searches the label forwarding table and uses a new outgoing label to replace the label in the input packet. An egress border LSR receives the labeled packet, deletes the label and performs the traditional L3 search for the IP packet.
2. 3.
Operational Principles of MPLS

MPLS is a label-based IP routing method. These labels can be used to stand for hopby-hop mode or explicit routes and also to indicate QoS, VPN and the transmission of special types of traffic (or special users traffic) on a network. MPLS uses a simplified technology to complete conversion between L2 and L3. MPLS can provide a label for each IP packet that can be encapsulated into a new MPLS packet in conjunction with the IP packet, to determine the transmission path and priority sequence of the IP packet. Before forwarding the IP packet according to the corresponding path, an MPLS router will read the header label of the MPLS packet, but will not read the information such as the IP address in each IP packet. Therefore, the switching and routing speed of packets is greatly improved. MPLS can use different types of L2 protocols. Up to now, the MPLS Task Force has standardized labels used in frame relay, ATM, PPP links and IEEE802.3 LANs. The
advantage of the running of MPLS in frame relay and ATM is that it brings the random connectivity of the IP to these connection-oriented technologies. At present, the developing tendency of MPLS is ATM. It is mainly because ATM has strong flow administration and can provide service like QoS. Technical combination of ATM and MPLS can make full use of its function on flow administration and QoS. Labels are used to forward headers of packets, and format of packet headers depends upon network features. In a router network, a label is an independent 32-bit header. In ATM, a label is placed in the cell header of a Virtual Circuit Identifier/Virtual Channel Identifier (VCI/VPI). For the scalability of MPLS, a very key point is that a label is meaningful only between two pieces of equipment in mutual communications. When an IP packet enters the network core, a border router will assign a label to it. Since then, the MPLS equipment will check the label information all the time and switch the labeled packet to the destination. Since route processing is reduced, the waiting time of the network is shortened and the scalability is improved. The border router of MPLS determines the QoS type of an MPLS packet according to the parameters (such as source/destination IP address, port ID and TOS value) in the IP packet. For IP packets to the same destination, different forwarding paths can be set up according to the requirements for TOS values, to meet the requirements for transmission quality. In the meantime, the management of special routes also can solve the problems of load balance and congestion on the network efficiently. If congestion occurs on a network, MPLS can set up new forwarding routes to disperse the traffic to ease network congestion.
MPLS Label Header

An MPLS label is inserted between an L2 header and an L3 packet. Therefore, an MPLS label header is also called a shim header. The length of an MPLS label header is four bytes, containing a 20-bit label, a 3 test bits, a 1-bit stack bottom tag and 8-bit TTL (Time-To Live). A router sending an MPLS packet needs to use a method to notify a router receiving the packet. The transmitted packet is not a pure IP packet, but an MPLS datagram. For Ethernet packets, Ethernet types 8847 and 8848 (in hexadecimal notation) are used to label MPLS packets; while for PPP packets, the protocol field is set to "8281" (in hexadecimal notation) to label MPLS packets.
MPLS LDP
LDP label binding is an association relation between a destination prefix and a label. Labels used for label binding are locked from a label set called label space. LDP supports two types of label spaces:
Label space per interface: The label space per interface uses the label resources of the interface. For example, the LC-ATM interface uses VPI/VCI as a label. Based on different configurations, an LDP instance can support or may not support one or multiple interface label spaces. Label space per platform: The LDP instance supports a label space shared by all interfaces in a platform range. Except the LC-ATM interface, a ZXR10 GAR uses the label space per platform on all the other interfaces.
LDP uses six bytes to name a label space, called LDP identity (LDP Id), which is composed of two parts: the first four bytes indicate the router ID of the router that has the label space, and the last two bytes indicate the internal label space ID of the LSR. For the label space per platform, the last two bytes are always zero. The rules for selecting the router ID of an LDP on a ZXR10 GAR are as follows: 1. If the m p l s l d p r o u t e r - i d command is used to designate the address of an interface as the router ID, and also the interface has an IP address and is in UP status, the interface will serve as the router ID. If there are loopback interfaces configured with an IP address, the maximum IP address among the IP addresses of all the loopback interfaces will serve as the router ID. The maximum one among the IP addresses of interfaces configured with IP addresses in UP status is selected as the router ID.
2.
3.
An LSR sends LDP hello messages periodically, indicating that it hopes to advertise label binding to find LDP peers. A Hello message contains the LDP ID of the label space that the LSR wants to advertise. The LDP uses UDP as a transmission protocol to send the Hello message, with the port ID of 646. When an LSR receives a Hello message from another LSR, it will "think" that it has found an LSR and its special label space. If two LSRs find each other, they will start to set up an LDP session. LDP defines two types of discovery mechanisms. At present, ZXR10 GAR supports the basic discovery mechanism, used to discover directly-connected peers. The Hello message in the basic discovery mechanism is sent on all interfaces configured with LDP, with multicast addresses of all routers on the subnet as the destination addresses. The procedure for setting up an LDP session between two LSRs is as follows. 1. Open a TCP connection used for label distribution On a ZXR10 GAR, by default, the router ID of LDP serves as the transport address of the TCP connection. Alternatively, in the interface configuration mode, the m p l s l d p d i s c o v e r y t r a n s p o r t - a d d r e s s command can be used to designate an IP address or the source IP address for sending Hello messages can serve as the transport address of the TCP connection.
Note: To set up a TCP connection, an LSR should have a route to the TCP transport address of another LSR.
2.
Negotiate LDP session parameters Parameters to be negotiated are label distribution mode (independent downstream label distribution/downstream label distribution on demand) and other parameters.
After the LDP session is set up, the LDP can start label distribution.
MPLS Configuration
The ARP configuration covers the following contents. 1. Enable LDP to set up an LSP along a common hop-by-hop routing path
mpls ip (Global configuration)
The n o format of the command disables the LSP setup along a common hop-by-hop routing path, regardless of LDP enable on the interface. However, labeled packet forwarding along the LSP will not be affected. 2. Enable LDP label switching on the interface
mpls ip (Interface configuration)
After the m p l s i p command is configured on an interface needing label forwarding, the LSR starts to send the Hello message periodically. When the interface obtains an outgoing label to a destination network section, a packet to the destination network section will be tagged with this label and forwarded from the interface. 3. Configures the transport address parameter contained in the Hello message
mpls ldp discovery transport-address {interface|<ip-address>}
By default, a ZXR10 router regards the router ID on an interface in frame mode as the transport address and advertises the address in the Hello message. The above command can change the default behavior of the router on an interface. 4. 5. Designates the IP address of an interface as the router ID of the LDP
mpls ldp router-id <interface-name> [force]
Control the LDP to create the FEC item (that is, FEC filtering policy) for which destination network sections
mpls ldp access-fec {for <prefix-access-list>|host-route-only}
6.
Controls locally distributed labels (incoming labels) to be distributed upstream by means of LDP
mpls ldp advertise-labels access-list>]] [for <prefix-access-list> [to <peer-
7.
Configure the interval for sending the LDP hello discovery message and the timeout time of the discovered LDP neighbor
mpls ldp discovery hello {holdtime <holdtime>|interval <interval>}
8.
Configure the LDP neighbor.

mpls ldp target-session <ip-address>
MPLS Maintenance and Diagnosis

ZXR10 routers provide some commands for viewing the work status of MPLS. The common maintenance commands are as follows. 1. Show interfaces with MPLS enabled
show interface [ interface-name ]
View interfaces with MPLS enabled on R2, "Yes" indicates normal start:
ZXR10_R2#show mpls ldp interface interface of LDP: Interface fei_1/5 fei_1/6 IP Tunnel Operational No No Yes Yes Yes(ldp) Yes(ldp)
2.
Check MPLS LDP parameters, that is, LDP timer parameters

show mpls ldp parameters
Check the LDP parameter information on R2:

ZXR10_R2#show mpls ldp parameters Protocol version: 1 Downstream label pool: min label: 16; max label: 1048575 Session hold time: 180 sec; keep alive interval: 60 sec Discovery hello: holdtime: 15 sec; interval: 5 sec Downstream on Demand max hop count: 255 LDP initial/maximum backoff: 15/120 sec LDP loop detection: off
3.
Show LDP discovery information

show mpls ldp discovery [detail]
Check the detailed LDP discovery information on R2:

ZXR10_R2#show mpls ldp discovery detail Local LDP Identifier: 10.10.2.2:0 Discovery Sources: Interfaces: fei_1/5 (ldp): xmit/recv LDP Id: 10.10.1.1:0 Src 10.10.12.1 fei_1/6 (ldp): xmit/recv LDP Id: 10.10.3.3:0 IP addr: 10.10.12.1; Transport IP addr:
Src 10.10.3.3
IP
addr:
10.10.23.3;
Transport
IP
addr:
The command can be used to view the IP address that is discovered on each interface and is used to set up a TCP connection (that is, the transport IP address) by an LDP neighbor. To set up an LDP session, a router should have a reachable route to the address, that is, the router can ping the address successfully. x m i t / r e c v indicates the interface is transmitting/receiving Hello packets (both are indispensable). 4. Check LDP session information
show mpls ldp neighbor [<neighbor>|<interface-name>] [detail]
Check the LDP session information on R2. Label distribution can be performed only after an LDP session is set up between LSRs:
ZXR10_R2#show mpls ldp neighbor detail Peer LDP Ident: 10.10.1.1:0; Local LDP Ident 10.10.2.2:0 TCP connection: 10.10.12.1.1025 - 10.10.2.2.646 state: Oper; Msgs sent/rcvd: 240/240; Downstream Up Time: 03:52:25 LDP discovery sources: fei_1/5; Src IP addr: 10.10.12.1 holdtime: 15000 ms, hello interval: 5000 ms Addresses bound to peer LDP Ident: 10.10.12.1 10.10.1.1 Peer holdtime: 180000 ms; KA interval: 60000 ms ZXR10_R2#
The above information indicates that a normal TCP connection has been set up between LDPs, including the source/destination address and port ID of the TCP connection. The status is operation. If no normal LDP session is set up, the following contents will be displayed:
ZXR10_R2#show mpls ldp neighbor Peer LDP Ident: 10.10.1.1:0; Local LDP Ident 10.10.2.2:0 No TCP connection state: Non; Msgs sent/rcvd: 0/0; Downstream Up Time: 00:00:45 LDP discovery sources: fei_1/5; Src IP addr: 10.10.12.1 Addresses bound to peer LDP Ident:
5.
After the normal LDP session is set up, check the learned LDP label binding.
show mpls ldp bindings [<ip-address> {<net-mask>|<length>} [longer-prefixes]] [local-label <label> [- <label>]] [remote-label <label> [- <label>]] [neighbor [<ip-address>]] [detail]
Check the learned LDP label binding on R2:

ZXR10_R2#show mpls ldp bindings 10.10.1.1/255.255.255.255 local binding: label: 17 remote binding: lsr: 10.10.3.3:0, label: 18 remote null(inuse) 10.10.2.2/255.255.255.255 local binding: label: imp-null remote binding: lsr: 10.10.3.3:0, label: 17 remote binding: lsr: 10.10.1.1:0, label: 18 10.10.3.3/255.255.255.255 local binding: label: 16 remote null(inuse) remote binding: lsr: 10.10.1.1:0, label: 17 10.10.12.0/255.255.255.0 local binding: label: imp-null remote binding: lsr: 10.10.3.3:0, label: 16 remote binding: lsr: 10.10.1.1:0, label: imp-null 10.10.23.0/255.255.255.0 local binding: label: imp-null remote binding: lsr: 10.10.3.3:0, label: imp-null remote binding: lsr: 10.10.1.1:0, l abel: 16: binding: lsr: 10.10.3.3:0, label: impbinding: lsr: 10.10.1.1:0, label: imp-
Here, l o c a l b i n d i n g refers to local label distribution and advertisement to upstream LSRs, while r e m o t e b i n d i n g refers to labels advertised from downstream LSRS. Where, for a local network section, label distribution is set to i m p - n u l l , and the receiver executes n o t - s o - s t u b b y processing so that a label can pop up. Commands similar to the above commands:
ZXR10_R1#show mpls forwarding-table Mpls Ldp Forwarding-table: InLabel 18 17 16 16 Pop tag OutLabel Dest Pfxlen Interface 32 32 24 fei_1/1 fei_1/1 fei_1/1 NextHop 10.10.12.2 10.10.12.2 10.10.12.2 Pop tag 10.10.2.2 10.10.3.3 10.10.23.0
ZXR10_R2#show mpls forwarding-table Mpls Ldp Forwarding-table: InLabel 17 OutLabel Dest Pfxlen Interface 32 fei_1/5 NextHop 10.10.12.1 Pop tag 10.10.1.1
16
Pop tag
10.10.3.3
32
fei_1/6
10.10.23.3
ZXR10_R3#show mpls forwarding-table Mpls Ldp Forwarding-table: InLabel 18 17 16 17 Pop tag Pop tag OutLabel Dest 32 32 24 Pfxlen Interface fei_3/1 fei_3/1 fei_3/1 NextHop 10.10.23.2 10.10.23.2 10.10.23.2 10.10.1.1 10.10.2.2 10.10.12.0
Here, I n L a b e l refers to a locally bound label, and O u t L a b e l refers to a label learned fro a downstream LSR. If the downstream LSR advertises i m p - n u l l , the P o p t a g action will be executed. For complicated troubleshooting, the following d e b u g commands may be used: 1. 2. 3. 4. 5. Monitor the messages found by LDP:
debug mpls ldp transport {connections|events}
Monitor LDP session activities:

debug mpls ldp session {io|state-machine}
Monitor the messages sent to or received from the LDP neighbors:

debug mpls ldp messages {received|sent}
Monitor the addresses and labels advertised to the LDP neighbors:

debug mpls ldp bindings
Monitor the addresses and labels announced to the LDP neighbors:

debug mpls ldp advertisements
In the following example, events related to the mechanism discovered by LDP on R1 are monitored:
ZXR10_R1#debug mpls ldp transport events LDP transport events debugging is on ZXR10_R1# ldp: ldp: Send Rcvd ldp ldp hello; hello; fei_1/1, fei_1/1, scr/dst from 10.10.12.1(0.0.0.0)/224.0.0.2, intf_id 257 10.10.12.2(10.10.2.2:0), intf_id 257 ZXR10_R1#debug mpls ldp transport connections LDP transport connection debugging is on ZXR10_R1# ldp: Hold timer expired for adj 0, will close adj ldp: Closing ldp conn; 10.10.12.1:1025<-->10.10.2.2:646 ldp: Opening ldp conn; 10.10.12.1<-->10.10.2.2 ldp: Opening ldp conn; 10.10.12.1<-->10.10.2.2
ldp: ldp conn closed; 10.10.12.1:1026<-->10.10.2.2:646 ldp: ldp conn closed; 10.10.12.1:1027<-->10.10.2.2:646 ldp: Opening ldp conn; 10.10.12.1<-->10.10.2.2 ldp: ldp conn is up; 10.10.12.1:1028<-->10.10.2.2:646 ZXR10_R1#
Examples for MPLS Configuration

Figure 105 shows a simple network where frame interfaces are used for MPLS forwarding.
F I G U R E 1 0 5 M P L S C O N F I G U R A T I O N E X AM P L E
Basic configuration tasks of three routers are to: Enable MPLS hop-by-hop forwarding on POS links between R1 and R2 and that between R1 and R3. Configure LDP label distribution between R1 and R2 and that between R1 and R3. Configure the IP address of a loopback interface to serve as the router ID of the LSR.
R1 configuration:
ZXR10_R1(config)#mpls ip ZXR10_R1(config)#interface Loopback1 ZXR10_R1(config-if)#ip address 10.10.1.1 255.255.255.255 ZXR10_R1(config)#interface fei_1/1 ZXR10_R1(config-if)#ip address 10.10.12.1 255.255.255.0 ZXR10_R1(config-if)#mpls ip ZXR10_R1(config)#mpls ldp router-id loopback1 ZXR10_R1(config)#router ospf 1
ZXR10_R1(config-router)#network 10.0.0.0 0.255.255.255
R2 configuration:
ZXR10_R2(config)#mpls ip ZXR10_R2(config)#interface Loopback1 ZXR10_R2(config-if)#ip address 10.10.2.2 255.255.255.255 ZXR10_R2(config)#interface fei_1/5 ZXR10_R2(config-if)#ip address 10.10.12.2 255.255.255.0 ZXR10_R2(config-if)#mpls ip ZXR10_R2(config)#interface fei_1/6 ZXR10_R2(config-if)#ip address 10.10.23.2 255.255.255.0 ZXR10_R2(config-if)#mpls ip ZXR10_R2(config)#mpls ldp router-id loopback1 ZXR10_R2(config)#router ospf 1 ZXR10_R2(config-router)#network 10.0.0.0 0.255.255.255
R3 configuration:
ZXR10_R3(config)#mpls ip ZXR10_R3(config)#interface Loopback1 ZXR10_R3(config-if)#ip address 10.10.3.3 255.255.255.255 ZXR10_R3(config)#interface fei_3/1 ZXR10_R3(config-if)#ip address 10.10.23.3 255.255.255.0 ZXR10_R3(config-if)#mpls ip ZXR10_R3(config)#mpls ldp router-id loopback1 ZXR10_R3(config)#router ospf 1 ZXR10_R3(config-router)#network 10.0.0.0 0.255.255.255
In the above configuration, the OSPF dynamic routing protocol is run to advertise the Route-id of each LSR, that is, the route of the loopback interface address.
Note: The use of the loopback interface address as the router ID facilitates the stability of the LDP id of a router, since the status of the loopback interface address does not change (unless the interface is disabled manually
Chapter
17

This chapter introduces MPLS VPN technology and the relevant configuration of ZXR10 GAR.
Overview
MPLS VPN is an MPLS-based IP VPN, that is Layer 3 VPN, which is a routing method of applying the MPLS technology to networking routing and switching equipment to simplify core routers. MPLS VPN uses the label switching combined with traditional routing technologies to implement IP-based VPN. MPLS VPN can be used to construct broadband Intranet and Extranet and can meet multiple flexible service requirements. MPLS VPN can utilize the powerful transmission capability of a common backbone network, reduce the construction costs of the Intranet, greatly improve the operation and management flexibility of users networks, and meanwhile can meet the requirements of users for secure, realtime, broadband and convenient information transmission. In an IP-based network, MPLS has many advantages. 1. Reduce costs MPLS simplifies the integration technology of ATM and IP, efficiently combines the L2 and L3 technologies, reduces costs and protects users investment at earlier stages. 2. Improve resource utilization Since label switching is used on the network, users LANs at different points can use repeated IP addresses to improve the utilization of IP resources. 3. Improve network speed Since label switching is used, the address searching time in each hop process is shortened, the transmission time of data on a network is reduced, and the network speed is improved. 4. Improve flexibility and scalability Since MPLS uses AnyToAny connection, the network flexibility and scalability is improved. With respect to flexibility, special control policy can be customized to meet special requirements of different users and implement value-added services. The scalability covers the following two aspects: more VPNs on a network and easy user expansion in the same VPN. 5. Make users application convenient
The MPLS technology will find wider application in networks of different carriers, so that an enterprise user can set up a global VPN conveniently. 6. Improve security MPLS serves as a channel mechanism to implement transparent packet transmission. LSPs of MPLS have high reliability and security similar to frame relay and ATMVCC (Virtual Channel Connection). 7. 8. Enhance service integration capability A network can support the integration of data, audio and video services. QoS assurance of MPLS Related standards and drafts drawn by IETF for BGP/MPLS VPN: RFC 2547, BGP/MPLS VPN Draft RFC 2547bis, BGP/MPLS VPN RFC 2283, multi-protocol extension BGP4
Related Terms
A BGP/MPLS VPN network system covers the following types of network equipment. PE (Provider Edge) A PE refers to a router connected to a CE in a client site on a carriers network. A PE router supports VPN and labeling function (the labeling function can be provided by RSVP, LDP or CR-LDP). In a single VPN, a tunnel is used for connecting two PE routers, and the tunnel can be an MPLS LSP tunnel or an LDP tunnel. P (Provider) Here, P refers a router in the core of a carriers network, which is not connected to any router in any customer site, but is a part of the tunnel in a PE pair. P supports MPLS LSP or LDP, but does not need to support VPN. CE (Customer Edge) CE refers to a router or switch connected to a carriers network in a customer site. Normally, CE refers to an IP router. The VPN function is provided by a PE router, while P and CE routers do not have other VPN configuration requirements.
VPN-IPv4 Address and Route Distinguisher (RD)

Since an Layer 3 VPN may be connected to private networks via the Internet, these private networks can use public addresses or private addresses. When the private networks use private addresses, the addresses between different private networks may be repeated. To avoid repetition of private addresses, public addresses can be used in network equipment to replace private addresses. Solutions are provided in RFC2547bis and it uses the present private net ID to create a new definite address.
The new address is one of the components in the VPN-IPv4 address family and is the BGP address family of MP_BGP. In a VPN-IPv4 address, there is a value used to differentiate different VPNs, called Route Distinguisher (RD). The format of a VPN-IPv4 address is an eight-byte Router Distinguisher (RD) plus a four-byte IP address. The RD is the eight-byte value used for VPN differentiation. An RD consists of the following domains: Type domain (two bytes): length of the other two domains depends on it. If the value of the type domain is 0, the administrator (ADM) domain is four bytes and the Assignment Number (AN) domain is two bytes. If the value of the type domain is 1, the administrator (ADM) domain is two bytes and the Assignment Number (AN) domain is four bytes. The administrator (ADM) domain: an administrator assignment number is identified If the value of the type domain is 0, the administrator domain contains an IPv4 address. RFC2547bis recommends that the IP address of a router (this address is normally configured as router ID) be used, and this address is a public address. If the value of the type domain is 1, the administrator domain contains an AS Number.RFC2547bis recommends the public AS Number is distributed by IANA and the number is recommended to be the ISP or the clients number. Assignment value: number assigned by network carrier If the type domain is 0, the length of the AN domain is two bytes. If the type domain is 1, the length of the AN domain is four bytes. An RD is only used between PEs to differentiate IPv4 addresses of different VPNs. The ingress generates an RD and converts the received IPv4 route of the CE into a VPNIPv4 address. Before advertising the route to the CE, the egress PE converts the VPNIPv4 route into an IPv4 route.
Operational Principles of MPLS VPN

The basic operation mode of MPLS VPN is the application of the L3 technologies. Each VPN has an independent VPN-ID, users of each VPN can only communicate with members in the same VPN and only VPN members can enter the VPN. On MPLS-based VPNs, the service provider assigns a distinguisher to each VPN, called Route Distinguisher (RD). The distinguisher is unique in the network of the service provider. The forwarding table contains a unique address, called VPN-IP address, which is formed through the connection of the RD and the IP address of the user. The VPN-IP address is a unique one in the network. The address table is stored in the forwarding table. BGP is a routing information distribution protocol, which uses multi-protocol extension and common attributes to define VPN connectivity. On MPLS-based VPNs, BGP only advertises information to members in the same VPN and provides basic security by means of traffic split.
Data is forwarded by using LSP. The LSP defines a special path that cannot be changed, to guarantee the security. Such a label-based mode can provide confidentiality as frame relay and ATM. The service provider relates a special VPN to an interface, and packet forwarding depends upon ingress labels. The VPN forwarding table contains a label corresponding to the VPN-IP address. The label is used to send the data to the corresponding destination. Since the label is used instead of the IP address, a user can maintain its dedicated address structure, without the need of data transfer by means of Network Address Translation (NAT). According to the data ingress, the corresponding router will select a special VPN forwarding table that only contains a valid destination address in VPN. First, CE provides the routing information of the client in the net to PE router via static routing, default routing or protocols like RIP, OSPF, IS-IS or BGP. Meanwhile, CE transmits information of VPN-IP and the corresponding labels (labels on VPN, shortened into internal-layer label as follows) by adopting BGP between PEs. Traditional IGP is adopted to learn routing information from each other between PE and P routers. LDP is adopted to bind the routing information and labels (labels in the backbone network, shortened as external-layer label as follows). In this case, the basic network topology and routing information of CE, PE and P routers have already been formed. A PE router has the routing information of the backbone network and the routing information of each VPN. When a CE user on a VPN enters the network, the system can identify to which VPN the CE belongs on the interface between the CE and the PE, and will further read the next-hop address information in the routing table of the VPN. In addition, forwarded packets will be marked with a VPN label (internal layer label). In this case, the nexthop address obtained is the address of a PE that is the peer of this PE. To reach the destination PE, the routing information of the backbone network should be read from the source PE to obtain the address of the next P router, and meanwhile, forwarded users packets will be tagged with a backbone network label (external layer label). In the backbone network, all P routers after the source PE read the external layer label to determine the next hop. Therefore, only simple label switching is performed on the backbone network. When a packet reaches the last P router before arriving at the destination PE, the external layer label will be cancelled. After the packet reaches the destination PE, the PE will read the internal layer label, find the next-hop CE in the corresponding VRF, send the packet to the related interface and further transfer the data to the CE network of the VPN.

The MPLS/VPN configuration covers the following contents.
1.
Define a name of a VPN on PE or give a name of the forwarding table of a VPN

ip vrf <vrf-name>
The length of the name lasts one through sixteen characters. The name is only valid locally, which will be used when an interface is bound with the VPN. 2. 3. 4. Defines the RD of the VRF
rd <route-distinguisher>
Creates route-target extension community attribute related to the VRF

route-target [import|export|both] <extended-community>
Defines the association of a designated interface with the VRF

ip vrf forwarding <vrf-name>
If the interface is configured with an IP address in advance, the original IP address will disappear, and address reconfiguration is needed. 5. Define VRF route PE can define static routes or run dynamic routing protocols to implement automatic interaction with CE. i. ii. Static routes configuration needs to use i p r o u t e command to designate the VPR. For different dynamic routing protocols, the configurations on PE are different. At present, the version supports four protocols: RIP, OSPF, IS-IS and BGP.
For RIP, it is necessary to use the n e t w o r k command to define an interface connected to CE and to execute route redistribution from BGP to RIP in the address-family ipv4 vrf address mode of the RIP. Here is an example:
ZXR10(config)#router rip ZXR10(config-router)#address-family ipv4 vrf test1 ZXR10(config-router-af)#network 10.10.1.1 0.0.0.0 ZXR10(config-router-af)#redistribute connected ZXR10(config-router-af)#redistribute bgp-int
For the OSPF, it is necessary to start the process of OSPF in the VPN with the
r o u t e r o s p f command on PE.
In this process, use the n e t w o r k command to define an interface connected to CE, and execute route redistribution from BGP to RIP. Here is an example:
ZXR10(config)#router ospf 1 ZXR10(config-router)#network 0.0.0.0 ZXR10(config)#router ospf 2 vrf test1 ZXR10(config-router)#network 0.0.0.0 ZXR10(config-router)#redistribute bgp_int 10.10.10.1 0.0.0.0 area 10.0.0.0 0.255.255.255 area
For the ISIS, it is necessary to start the process of IS-IS in the VPN with the command r o u t e r i s i s on PE. It is necessary to execute BGP redistribution in this process, for example:
ZXR10(config)#router isis vrf test1 ZXR10(config-router)#system-id 2222.2222.2222 ZXR10(config-router)#area 02 ZXR10(config-router)#redistribute protocol bgp level-2
For the BGP, it is only necessary to designate a CE peer in the address-family ipv4 vrf address of the BGP. Note that EBGP runs between PE and CE that belong to different ASs. In the current version, it is recommended that a directly-connected address be used as the link setup address. Here is an example:
ZXR10(config)#router bgp 100 ZXR10(config-router)#neighbor 10.10.3.3 remote-as 100 ZXR10(config-router)#neighbor loopback1 ZXR10(config-router)#address-family ipv4 vrf test1 ZXR10(config-router-af)#redistribute connected ZXR10(config-router-af)#neighbor 10.1.1.2 remote-as 200 ZXR10(config-router-af)#exit-address-family ZXR10(config-router)#address-family vpnv4 ZXR10(config-router-af)#neighbor 10.10.3.3 activate ZXR10(config-router-af)#exit-address-family 10.10.3.3 update-source
6.
Configure MPBGP After learning a VRF route from CE, the PE should advertise the route to other PEs. In this case, MPBGP should be configured. Here are four steps: i. In BGP route configuration mode, use the neighbor command to designate a PE peer. Enter the BGP access address configuration mode
address-family vpnv4
ii.
Activates PE peer
neighbor <ip-address> activate
iii. For different VRFs, their routes (directly connected routes, static routes, OSPF routes and ISIS routes) should be redistributed into MPBGP and advertised.
redistribute <map-tag>] <protocol> [metric <metric-value>] [route-map
Here is an example:
ZXR10(config)#router bgp 100 ZXR10(config-router)#no synchronization ZXR10(config-router)#no bgp default route-target filter
ZXR10(config-router)#no bgp default ipv4-unicast ZXR10(config-router)#neighbor 192.168.1.250 remote-as 100 ZXR10(config-router)#neighbor loopback1 ZXR10(config-router)#address-family ipv4 vrf t1 ZXR10(config-router-af)#redistribute connected ZXR10(config-router-af)#redistribute isis-2 ZXR10(config-router-af)#redistribute isis-1 ZXR10(config-router-af)#exit-address-family ZXR10(config-router)#address-family vpnv4 ZXR10(config-router-af)#neighbor 192.168.1.250 activate ZXR10(config-router-af)#exit-address-family 192.168.1.250 update-source
MPLS VPN Maintenance and Diagnosis

ZXR10 GAR provides some commands for viewing the work mode of MPLS VPN. The common maintenance commands are as follows. 1. Check network connectivity
ping
Different from the p i n g command used in the VPN environment, the VRF needs to be designated to p i n g the CE1 address as shown in the following example.
PE1#ping vrf test1 10.1.1.2 sending seconds. !!!!! Success PE1# rate is 100 percent(5/5),round-trip min/avg/max= 0/4/20 ms. 5,100-byte ICMP echos to 10.1.1.2,timeout is 2
2.
Check information about VRF

show ip vrf [brief|detail|interfaces] [<vrf-name>]
Check the VRF information on PE1:

PE1#show ip vrf * Being deleted Name test1 PE1# Default RD 100:1 Interfaces fei_1/2
Check the status and information about the VRF interface on PE1:
PE1#show ip vrf interfaces interface fei_1/2 PE1# IP-Address 10.1.1.1 VRF test1 Protocol up
3.
On PE, check the VRF routing table to see whether there is any correct route
show ip mask>]] route vrf <vrf-name> [network <ip-address> [mask <net-
Check the VRF routing table on PE1:
PE1#show ip route vrf test1 IPv4 Routing Table: Dest 10.1.1.0 10.1.1.1 0 100.1.1.1 0 10.10.10.0 4294967295 200.1.1.1 4294967295 PE1# 255.255.255.255 10.10.3.3 fei_1/1 bgp 200 255.255.255.0 10.10.3.3 fei_1/1 bgp 200 255.255.255.255 10.1.1.1 fei_1/2 bgp 20 Mask Gw Interface Owner pri metric 10.1.1.1 10.1.1.1 fei_1/2 fei_1/2 direct 0 0 0 address 255.255.255.0
255.255.255.255
The VRF routing table contains directly connected network sections, routes advertised by CE1 and routes advertised by PE2.
Note: The key to the advertisement of routes in VRF to other PEs is to see whether the routes are redistributed into the MPBGP.
Whether the peer can enter VRF depends upon whether the import/export target route attribute (route-target import/export) of both parties match each other. 4. Check neighbor connection status
show ip ospf neighbor [interface <neighbor>] [process <process-id>] <interface-name>] [neighbor-id
The case whether the PE notifies CE about the VRF route will decide if the CE routing table is complete. Confirm whether the routes are redistributed from MPBGP to the dynamic routing protocol between PE and CE, whether the protocol between PE and CE runs normally, and whether the MPBGP connection between PEs is in Established status.
Check OSPF adjacency between PE2 and CE2. (OSPF process ID should be designated):
PE2#show ip ospf neighbor process 2 Neighbor 200.1.1.1 In the area 0.0.0.0 via interface fei_3/2.10 10.10.10.2 Neighbor is DR State FULL, priority 1, Cost 1 Queue count : Retransmit 0, DD 0, LS Req 0 Dead time : 00:00:37 PE2#
Check the EBGP connection between CE1 and PE1:

CE1#show ip bgp summary BGP router identifier 10.1.1.2, local AS number 200 BGP table version is 8, main routing table version 8 Neighbor V AS MsgRcvd 157 MsgSent 8 0 TblVer 0 InQ OutQ 3 Up/Down State/PfxRcd 10.1.1.1 4 100 156 CE1# 01:16:48
Check the IBGP connection between PE1 and PE2:

PE1#show ip bgp summary Neighbor State 10.10.3.3 Established PE1# 4 100 195 201 01:37:23 Ver As MsgRcvd MsgSend Up/Down(s)
5.
Check whether the internal layer labels of VPN on PEs are correct and consistent
show ip protocol [mask <net-mask>]] routing vrf <vrf-name> [network <ip-address>
Check the internal layer label that PE1 assigns to VPN routes:
PE1#show ip protocol routing vrf test1 Routes of vpn: status codes: *valid, >best Dest *> *> *> *> *> NextHop 10.1.1.0 10.1.1.1 10.1.1.2 10.10.3.3 Intag Outtag 153 152 22 20 21 RtPrf Protocol 0 0 connected connected 20 bgp_ext 200 bgp_int 10.1.1.0/24 10.1.1.1/32 100.1.1.0/24 200.1.1.0/24 notag notag 17 notag 27
10.10.10.0/24 10.10.3.3
200 bgp_int
PE1#
For a local VPN network section, the Intag value is the internal layer VPN label; for a non-local network section, Outtag is an internal layer VPN label advertised from other PEs. Check the internal layer label assignment of VPN routing entries of PE2:
PE2#show ip protocol routing vrf test1 Routes of vpn: status codes: *valid, >best Dest *> *> * *> *> *> PE2# NextHop 10.10.1.1 Intag 26 10.10.10.0 20 Outtag RtPrf Protocol 153 17 notag 16 23 27 20 200 bgp_int 0 ospf 0 notag 110 notag 200 10.1.1.0/24
10.10.10.0/24
connected 10.10.10.0/24 10.10.10.0 10.10.10.1/32 100.1.1.0/24 200.1.1.0/24 10.10.10.1
connected 10.10.1.1 10.10.10.2 bgp_int ospf notag 110
6.
Traces and displays updates packets transmitted/received by a BGP connection and also displays route processing in packets.
debug ip bgp [ <ip-address> ] updates
Trace and display updates packets transmitted/received by a BGP connection and also displays route processing in packets:
ZXR10#debug ip bgp updates ZXR10(config)#reset ip bgp neighbor 10.10.3.3 ZXR10(config)# 1d4h: BGP: 100.1.1.1/32 deleted from BGP routable 1d4h: BGP: 100.1.1.1/32 deleted from IP routable 1d4h: BGP: 10.10.1.1/32 deleted from BGP routable 1d4h: BGP: 10.10.1.1/32 deleted from IP routable ZXR10(config)# 1d4h: path afi:1 BGP: metric 10.10.3.3 0 send UPDATE route w/ attr: nlri origin 100:1 0131 mp i asnlri 100:1 localpref 254 target
safi:128
next-hop:10.10.1.1
10.1.1.0/24 1d4h: BGP: 10.10.3.3 rcv UPDATE w/ attr: origin i as-path metric 0 localpref 144 route target 100:1 mp nlri afi:1 safi:128 next-hop:10.10.3.3 nlri 0181 100:1 100.1.1.1/32
nlri 0171 100:1 10.10.1.1/32 ZXR10(config)#
7.
Resets BGP session by software. The commands has the function of enable for a neighbor already in non-BGP session stop status
reset ip bgp [vrf <vrf-name>] [<ip-address>]
Examples for MPLS VPN Configuration

An MPLS VPN configuration example is given below.
FIGURE 106 MPLS VPN CONFIGURATION EXAMP LE
As shown in Figure 106, CE1 and CE2 belong to the same VPN. The loopback address of CE1 is 100.1.1.1/24, and that of CE2 is 200.1.1.1/24. Proper VPN configuration should be made so that CE1 and CE2 can learn the loopback routes from each other. The BGP runs between CE1 and PE1, while the OSPF runs between CE2 and PE2. Configuration of CE1:
CE1(config)#interface Loopback1 CE1(config-if)#ip address 100.1.1.1 255.255.255.0 CE1(config)#interface FastEthernet0/0 CE1(config-if)#ip address 10.1.1.2 255.255.255.0 CE1(config)#router bgp 200 CE1(config-router)#bgp log-neighbor-changes CE1(config-router)#network 100.1.1.0 mask 255.255.255.0 CE1(config-router)#neighbor 10.1.1.1 remote-as 100 CE1(config-router)#no auto-summary
Configuration of PE1:
PE1(config)#ip vrf test1
PE1(config-vrf)#rd 100:1 PE1(config-vrf)#route-target import 100:1 PE1(config-vrf)#route-target export 100:1 PE1(config)#interface loopback1 PE1(config-if)#ip address 10.10.1.1 255.255.255.255 PE1(config)#interface fei_1/1 PE1(config-if)#ip address 10.10.12.1 255.255.255.0 PE1(config-if)#mpls ip PE1(config-if)#mpls interface PE1(config)#interface fei_1/2 PE1(config-if)#ip vrf forwarding test1 PE1(config-if)#ip address 10.1.1.1 255.255.255.0 PE1(config)#router ospf 1 PE1(config-router)#router-id 10.10.1.1 PE1(config-router)#network 0.0.0.0 PE1(config)#router bgp 100 PE1(config-router)#neighbor 10.10.3.3 remote-as 100 PE1(config-router)#neighbor loopback1 PE1(config-router)#address-family ipv4 vrf test1 PE1(config-router-af)#redistribute connected PE1(config-router-af)#neighbor 10.1.1.2 remote-as 200 PE1(config-router-af)#exit-address-family PE1(config-router)#address-family vpnv4 PE1(config-router-af)#neighbor 10.10.3.3 activate PE1(config-router-af)#exit-address-family PE1(config)#mpls ip PE1(config)#mpls ldp router-id loopback1 force 10.10.3.3 update-source 10.0.0.0 0.255.255.255 area ldp discovery transport-address
An EBGP connection is set up between CE1 and PE1:

CE1#show ip bgp summary BGP router identifier 10.1.1.2, local AS number 200 BGP table version is 8, main routing table version 8 Neighbor V AS MsgRcvd 157 MsgSent 8 0 TblVer 0 InQ OutQ 3 Up/Down State/PfxRcd 10.1.1.1 4 100 156 CE1# 01:16:48
The routing table of CE1 is as follows and two of the BGP routes are VPN routes learned from CE1:
CE1#show ip route Gateway of last resort is not set 100.0.0.0/24 is subnetted, 1 subnets C B B C CE1# 100.1.1.0 is directly connected, Loopback1 200.1.1.0/24 [20/0] via 10.1.1.1, 00:01:17 10.0.0.0/24 is subnetted, 2 subnets 10.10.10.0 [20/0] via 10.1.1.1, 00:02:02 10.1.1.0 is directly connected, FastEthernet0/0
Configuration of P:
P(config)#interface fei_1/5 P(config-if)#ip address 10.10.12.2 255.255.255.0 P(config-if)#mpls ip P(config-if)#mpls interface P(config)#interface fei_1/6 P(config-if)#ip address 10.10.23.2 255.255.255.0 P(config-if)#mpls ip P(config-if)#mpls interface P(config)#interface loopback1 P(config-if)#ip address 10.10.2.2 255.255.255.255 P(config)#router ospf 1 P(config-router)#network 0.0.0.0 P(config)#mpls ip P(config)#mpls ldp router-id loopback1 force 10.0.0.0 0.255.255.255 area ldp discovery transport-address ldp discovery transport-address
Configuration of PE2. Here, an Ethernet sub-interface is used for connection with CE2:
PE2(config)#ip vrf test1 PE2(config-vrf)#rd 100:1 PE2(config-vrf)#route-target import 100:1 PE2(config-vrf)#route-target export 100:1 PE2(config)#interface loopback1 PE2(config-if)#ip address 10.10.3.3 255.255.255.255 PE2(config)#interface fei_3/1 PE2(config-if)#ip address 10.10.23.3 255.255.255.0 PE2(config-if)#mpls ip PE2(config-if)#mpls interface ldp discovery transport-address
PE2(config)#interface fei_3/2.10 PE2(config-if)#ip vrf forwarding test1 PE2(config-if)#encapsulation dot1q 10 PE2(config-if)#ip address 10.10.10.1 255.255.255.0 PE2(config)#router ospf 1 PE2(config-router)#network 0.0.0.0 PE2(config)#router ospf 2 vrf test1 PE2(config-router)#network 0.0.0.0 PE2(config-router)#redistribute bgp_int PE2(config)#router bgp 100 PE2(config-router)#neighbor 10.10.1.1 remote-as 100 PE2(config-router)#neighbor loopback1 PE2(config-router)#address-family ipv4 vrf test1 PE2(config-router-af)#redistribute ospf_int metric 10 PE2(config-router-af)#redistribute connected PE2(config-router-af)#exit-address-family PE2(config-router)#address-family vpnv4 PE2(config-router-af)#neighbor 10.10.1.1 activate PE2(config-router-af)#exit-address-family PE2(config)#mpls ip PE2(config-if)#mpls ldp router-id loopback1 force 10.10.1.1 update-source 10.10.10.1 0.0.0.0 area 10.0.0.0 0.255.255.255 area
Configuration of CE2:
CE2(config)#interface Loopback1 CE2(config-if)#ip address 200.1.1.1 255.255.255.0 CE2(config-if)#ip ospf network point-to-point CE2(config)#interface FastEthernet0/0.10 CE2(config-if)#encapsulation dot1Q 10 CE2(config-if)#ip address 10.10.10.2 255.255.255.0 CE2(config)#router ospf 1 CE2(config-router)#log-adjacency-changes CE2(config-router)#network 10.10.10.2 0.0.0.0 area 0 CE2(config-router)#network 200.1.1.1 0.0.0.0 area 0
Routing table of CE2 and two of the OSPF routes are VPN routes learned from CE2:
CE2#show ip route Gateway of last resort is not set 100.0.0.0/24 is subnetted, 1 subnets
O C O C
E2
100.1.1.0
[110/1]
via
10.10.10.1,
00:07:21,
FastEthernet0/0.10 200.1.1.0/24 is directly connected, Loopback1 10.0.0.0/24 is subnetted, 2 subnets E2 10.1.1.0 [110/1] via 10.10.10.1, 00:07:21, FastEthernet0/0.10 10.10.10.0 is directly connected, FastEthernet0/0.10 CE2#
Chapter
18
VPWS Configuration
This chapter describes configuration of the VPWS.
Overview
VPWS is set up and based on the infrastructure of the MPLS net, providing high-speed Layer 2 transparent transmission between a pair of ports of the two routers. VPWS is mainly composed of PE router, LDP and LSP Tunnel of the MPLS. PE router possesses and maintains the link information of the Layer 2 transparent transmission connected directly to it. PE router is responsible for making and removing labels on the common packet of the VPN clients, so the PE router should be an edge mark switch router. The two ports of the Layer 2 transparent transmission between the two PE routers are of the same type like Ethernet, VLAN, ATMVC, frame-relay VC, HDLC or PPP. Each pair of such ports is represented by the sole VC Label VCID. The LSP tunnel through the MPLS net should be defined between the two PE routers and should provide Tunnel Label transparently transmitting data between the two PE routers. At the same time, the direct process of the LDP label distribution protocol is also defined between the two PE routers to transmit the virtual link information. Among them, distributing the VC Label through matching VCID is the critical.
When data packet enters the PE router at the port of the Layer 2 transparent transmission, PE router finds the corresponding Tunnel Label and VC Label through matching VCID. PE router will put two layers labels on the data packet. The external layer is the Tunnel Label indicating the route from this PE router to the destination PE router. The internal layer is the VC Label indicating which corresponding router port of the VCID belongs to on the destination PE router. PE router should monitor the Layer 2 protocol state at each port, such as the framerelay LMI and the ILMI of the ATM. When a fault occurs, cancel the VC Label through the LDP label distribution protocol process so that the Layer 2 transparent transmission is shut off avoiding producing unidirectional unwanted data stream. Such Layer 2 transparent transmission based on the MPLS changes the traditional confinement that the Layer 2 link should be implemented through net exchange. It essentially forms a pattern of One Net Multi-Service pattern and makes the operator provide Layer 2 and Layer 3 Services simultaneously in a MPLS net.
VPWS Configuration
1. 2. Start the VPWS configuration at the interface.
mpls xconnect <ip-address> <vc-id> [tunnel <tunnel number> ]
Configure the extend LDP neighbor

mpls ldp target-session <ip-address>
VPWS block function is based on the LDP. Setting up PW between the indirect connected PE needs building a LDP neighbor between the indirect connected PE via the mode of TARGET HELLO of the LDP firstly and then distributes the PW label.
VPWS Maintenance and Diagnosis

For easy maintaining VPWS, ZXR10 GAR provides the following commands: 1. Check if VC is set up.
show mpls l2transport vc [ {vcid <vcidmin> [<vcidmax>] | interface <interface-name> [ <loca-lcircuit-id1> [<local-circuit-id2>] ] | destination <ip-addr> } ] [detail]
2.
Check the Binding Information of the VC.

show mpls l2transport binding [<vc-id>|<ip-address>|local-label local-label>| remote-label <remote-label >] <
3. 4.
Monitor the message sending and receiving of the VPWS.

debug mpls ldp l2vpn event
Monitor the state machine of the VPWS.

debug mpls ldp l2vpn fsm
Examples for VPWS Configuration

As shown in Figure 107, implement VC interaction between CE1 and CE2.
F I G U R E 1 0 7 V P W S C O N F I G U R AT I O N E X A M P L E
Configuration method is as follows: 1. 2. 3. 4. 5. 6. Configure interface address on fei_1/2 on PE1, fei_2/1 and fei_2/2 on P, fei_3/1 on PE2. Configure the loopback address on PE1, P and PE2. Run IGP(like OSPF) on PE1, P and PE2 to make interactive between PE1 and PE2, and learned to route to the loopback interface address on the other side. Start MPLS on PE1, P and PE2 and indicate router-id of mpls ldp. Start mpls ip on the interface like fei_2/1 on P, fei_3/1 on PE2; Configure targetsession on PE1 and PE2 to make ldp neighborhood between PE1 and PE2; (the configuration is not needed if there is no P in the networking); Start mpls xconnect on PE1 and PE2 and the interface fei_1/1 and fei_3/2 connected to the CE.
Configuration of the equipment is shown as follows: PE1 configuration:

PE1(config)# interface loopback10 PE1(config-if)# ip address 1.1.1.1 255.255.255.255 PE1(config)# interface fei_1/1 PE1(config-if)# mpls xconnect 1.1.1.3 100 PE1(config)# interface fei_1/2 PE1(config-if)# ip address 175.1.1.1 255.255.255.0 PE1(config-if)# mpls ip PE1(config)# mpls ip PE1(config)# mpls ldp router-id loopback10 force PE1(config)# mpls ldp target-session 1.1.1.3 PE1(config)# router ospf 1
PE1(config-router)# network 1.1.1.1 0.0.0.0 area 0.0.0.0 PE1(config-router)# 0.0.0.0 network 175.1.1.0 0.0.0.255 area
P configuration:
P(config)# interface loopback10 P(config-if)# ip address 1.1.1.2 255.255.255.255 P(config)# interface fei_2/1 P(config-if)# ip address 175.1.1.2 255.255.255.0 P(config-if)# mpls ip P(config)# interface fei_2/2 P(config-if)# ip address 148.1.1.2 255.255.255.0 P(config-if)# mpls ip P(config)# mpls ip P(config)# mpls ldp router-id loopback10 force P(config)# router ospf 1 P(config-router)# network 1.1.1.2 0.0.0.0 area 0.0.0.0 P(config-router)# 0.0.0.0 P(config-router)# 0.0.0.0 network 175.1.1.0 0.0.0.255 area network 148.1.1.0 0.0.0.255 area
PE2 configuration:
PE2(config)# interface loopback10 PE2(config-if)# ip address 1.1.1.3 255.255.255.255 PE2(config)# interface fei_3/1 PE2(config-if)# ip address 148.1.1.3 255.255.255.0 PE2(config-if)# mpls ip PE2(config)# interface fei_3/2 PE2(config-if)# mpls xconnect 1.1.1.1 100 PE2(config)# mpls ip PE2(config)# mpls ldp router-id loopback10 force PE2(config)# mpls ldp target-session 1.1.1.1 PE2(config)# router ospf 1 PE2(config-router)# network 1.1.1.3 0.0.0.0 area 0.0.0.0 PE2(config-router)# 0.0.0.0 network 148.1.1.0 0.0.0.255 area
Abbreviations
Abbreviations ABR ACL AD API ARP AS ASBR ASN ATM BGP BOOTP BRD CHAP CIDR CLNP CLNS COS CRC CRLDP CSN CSU DDN DHCP DIS DNS DR DSU EBGP EGP ES Full name Area Border Router Access Control List Administrative Distance Application Programming Interface Address ResolutionProtocol Autonomous System Autonomous System Border Router Abstract Syntax Notation Asynchronous Transfer Mode Border Gateway Protocol BOOTstrap Protocol Backup Designate Router Challenge Handshake Authentication Protocol Classless Inter-Domain Routing ConnectionLess Network Protocol ConnectionLess Network Sevice Class of Service Cyclic Redundancy Check Constraint based Routing Label Distribution Protocol Cryptographic Sequence Number Channel Service Unit Digit Data Network Dynamic Host Configuration Protocol Designate IS Domain Name System Designate Router Data Service Unit External Border Gateway Protocol External Gateway Protocol End System
Abbreviations FDDI FEC FIFO FPGA FSM FTP GBIC GRE ICMP IETF IGMP IGP IP ISO ISP LAN LAPB LCP LDP LLC LSA LSP LSR MAC MD5 MED MIB MPLS MTU NAT NBMA NCP NIC NLRI NMS
Full name Fiber Distributed Data Interface Forwarding Equivalence Class First In and First Out Field Programmable Gate Array Finite State Machine File Transfer Protocol Gigabit Interface Converter General Routing Encapsulation Internet Control Message Protocol Internet Engineering Task Force Internet Group Management Protocol Interior Gateway Protocol Internet Protocol International Organization for Standardization Internet Service Provider Local Area Network Link Access Procedure Balanced Link Control Protocol Label Distribution Protocol Logical Link Control Link State Advertisement Link State PDU Label Switch Router Media Access Control Message Digest 5 MULTI_EXIT_DISC Management Information Base Multi-Protocol Label Switching Maximum Transmission Unit Network Address Translation Non-Broadcast Multiple Access Network Control Protocol Network Information Center Network Layer Reachable Information Network Management System
Abbreviations NSAP NSP NTP NVT OAM OID OSI OSPF PAP PAT PCB PCM PDU POS PPP PSNP PRT QOS RARP RADIUS RFC RIP RLE RMON ROS RSVP SDH SDLC SMP SMTP SNMP SNP SPF TCP TFTP
Full name Network Service Access Point Network Service Provider Network Time Protocol Network Virtual Terminal Operation And Management Object ID Open Systems Interconnection Open Shortest Path First Password Authentication Protocol Port Address Translation Process Control Block Pulse Code Modulation Protocol Data Unit Packet over SDH Point-to-Point Protocol Partial Sequence Num PDU Process Registry Table Quality of Service Reverse Address Resolution Protocol Remote Authentication Dial In User Service Request For Comments Routing Information Protocol Route lookup engine Remote Monitoring Router Operation System Resource Reservation Protocol Synchronous Digital Hierarchy Synchronous Data Link Control Security Main Processor Simple Mail Transfer Protocol Simple Network Management Protocol Sequence Num PDU Shortest Path First Transmission Control Protocol Trivial File Transfer Protocol
Abbreviations TOS TELNET TTL UDP VLSM VPN VRF VRRP WAN WWW
Full name Type Of Service Telecommunication Network Protocol Time To Live User Datagram Protocol Variable Length Subnet Mask Virtual Private Network Virtual Routing Forwarding Virtual Router Redundancy Protocol Wide Area Network World Wide Web
Figures
Figure 1 Front Panel of ZXR10 GAR (RA-G2604) Figure 2 Rear panel of ZXR10 GAR (RA-G2604) Figure 3 Front Panel of ZXR10 GAR (RA-G2608/ RA-G3608/ RA-G7208) Figure 4 Rear Panel of ZXR10 GAR (RA-G2608/ RA-G3608/ RA-G7208) Figure 5 ZXR10 GAR System Structure Diagram Figure 6 ZXR10 GER Internal Structure Diagram Figure 7 Main Board Interfaces and Indicator Lights of ZXR10 GAR (RA-G2604) Figure 8 Main Board Interfaces and Indicator Lights of ZXR10 GAR (RA-G2608/ RA-G3608/ RAG7208) Figure 9 RA-1CE1 Board Panel Figure 10 Interconnection via E1 RJ48 Connectors Figure 11 Connection of E1 RJ48 Connector with E1 BNC Connector Figure 12 RA-1CE1-75 Board Panel Figure 13 RA-1CT1 Board Panel Figure 14 Cable Connection at T1 Port Figure 15 RA-1E1V1 Board Panel Figure 16 RA-1E1V1-75 Board Panel Figure 17 Panel of RA-1FE-E100RJ Figure 18 Panel of RA-1FE-M02KSC Figure 19 Panel of RA-1FE-S15KSC Figure 20 Panel of RA-1FE-S40KSC Figure 21 RA-1GE-GBIC-R Board Panel Figure 22 Panel of RA-1P3-M02KSC Figure 23 Panel of RA-1P3-S15KSC Figure 24 Panel of RA-1P3-S40KSC board Figure 25 RA-2CE1 Board Panel Figure 26 Interconnection of E1 RJ48 Connectors
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85
Interconnection of E1 JR48 and E1 BNC Connectors RA-2CE1-75 Board Panel RA-2CT1 Board Panel Cable Connection at T1 Port RA-2FE-R Board Panel RA-2FXS Board Panel RA-2GE-GBIC-R Board Panel RA-4AS-U Board Panel RA-4CE1 Board Panel Interconnection of E1 RJ48 Connectors Interconnection of E1 JR48 and E1 BNC Connectors RA-4CE1-75 Board Panel RA-4CT1 Board Panel Cable Connection at T1 Interface RA-4E1VE Board Panel RA-4FE-R Board Panel RA-4FXO Board Panel RA-4FXS Board Panel RA-4HS Board Panel RA-4T1VE Board Panel RA-8CE1 Board Panel Interconnection via E1 RJ48 Connectors Interconnection of E1 RJ48 with E1 BNC Connectors RA-8CE1-R Board Panel RA-8FE-R Board Panel RA-8FXS Board Panel Configuration Modes of ZXR10 Routers ZXR10 Serial Interface Configuration 1 ZXR10 Serial Interface Configuration 2 ZXR10 Serial Interface Configuration 3 Run Telnet ZXR10 Remote Login WFTPD INTERFACE User/Rights Security Setting User/Rights Security Setting TFTPD Interface Configure Dialog Box Example 1 for Ethernet Interface Configuration Ethernet Interface Interconnection Example 2 POS Configuration Example 1 POS Configuration Example 2 Channelized E1 Configuration Example Example for Non-channelized E1 Configuration Example for Non-channelized T1 Configuration Example for Non-channelized T1 Configuration Example 1 for VoIP Interface Configuration Example 2 for VoIP Interface Configuration TDMoIP Interface Configuration Example VLAN Sub-Interface Configuration Example Multilink Configuration Example PPP Configuration Example RIP Configuration Examples Frame relay Configuration Example X.25 Configuration Example 1 X.25 Configuration Example 2 X.25 Configuration Example 3 HDLC Configuration Example V-Switch Configuration Example Static Route Configuration Example
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure
86 Static Route Summary Configuration Example 87 Default Route Configuration Example 88 RIP Configuration Example 89 OSPF Router Types 90 IS-IS Areas 91 Single Area IS-IS Configuration Example 92 Basic BGP Configuration 93 BGP Route Advertisement Configuration 94 BGP Aggregate Advertisement Configuration 95 Configuration of BGP Multihop 96 Filtering Routes Using NLRI 97 Local Reference Attribute Configuration 98 Configuration of the MED Attribute 99 Configuration of the BGP Synchronization 100 Configuration of the BGP Router Reflector 101 Configuration of the BGP Confederation 102 BGP Configuration Example 103 Policy Routing Configuration Example 1 104 Policy Routing Configuration Example 2 105 MPLS Configuration Example 106 MPLS VPN Configuration Example 107 VPWS Configuration Example
Tables
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 1 Typographical Conventions 2 Mouse Operation Conventions 3 Safety Signs 4 ZXR10 GAR Models 5 ZXR10 GAR System Features 6 Sequence of CONSOLE Cable 7 Sequence of AUX cable 8 Features of Fast Ethernet Management Port 9 Function Description of Indicators on the Front Panel of the GAR 10 Descriptions of ZXR10 GAR Line Interface Boards of Various Models 11 Features of Interfaces on RA-1CE1 Board 12 Description of Indicators on the RA-1CE1 Board 13 Interconnection of RJ48 connectors at E1 port 14 Features of Interfaces on RA-1CE1-75 Board 15 Functions Descriptions of Channelized RA-1CE1-75 Board Indicators 16 Features of Interfaces on the RA-1CT1 board 17 Description of Indicators on the RA-1CT1 Board 18 Interconnection of RJ48 Connectors at T1 Port 19 Features of Interfaces on the RA-1E1V1 Board 20 Description of Indicators on RA-1E1V1 Board 21 Features of Interfaces on RA-1E1V1-75 Board 22 Description of Indicators on RA-1E1V1-75 Board 23 Features of Interfaces on RA-1FE-E100RJ 24 Description of Indicators on RA-1FE-E100RJ Board
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83
Features of Interfaces on RA-1FE-M02KSC Indicator Descriptions of RA-1FE-M02KSC Features of Interfaces on RA-1FE-S15KSC Description of Indicators on RA-1FE-S15KSC Board Features of Interfaces on RA-1FE-S40KSC Board Description of Indicators on RA-1FE-S40KSC Board Description of Indicators on RA-1GE-GBIC-R Board Description of Indicators on RA-1GE-GBIC-R Board Features of Interfaces on RA-1P3-M02KSC Board Description of Indicators on RA-1P3-M02KSC Board Features of Interfaces on RA-1P3-S15KSC Board Description of Indicators on RA-1P3-S15KSC Board Features of Interfaces on RA-1P3-S40KSC Board Description of Indicators on RA-1P3-S40KSC Board Features of Interfaces on RA-2CE1 Board of the Description of Indicators on RA-2CE1 Board Interconnection of RJ48 Connectors at E1 Port. Features of Interfaces on RA-2CE1-75 Board Description of Indicators on RA-2CE1-75 Board Features of Interfaces on RA-2CT1 Board Description of Indicators on RA-2CT1 Board Interconnection of RJ48 Connectors at T1 Port Features of Interfaces on RA-1GE-GBIC-R Board Description of Indicators on RA-2FE-R Board Features of Interfaces on RA-2FXS Board Description of Indicators on RA-2FXS Board Features of Interfaces on RA-2GE-GBIC-R Board Description of Indicators on RA-2GE-GBIC-R Board Features of Interfaces on RA-4AS-U Board Description of Indicators on RA-4AS-U Board External Cables at Dual Serial Interface Features of Interfaces on RA-4CE1 Board Description of Indicators on RA-4CE1 Board Interconnection Method of RJ48 Connectors at E1 Port Features of Interfaces on RA-4CE1-75 Board Description of Indicators on RA-4CE1-75 Board Features of Interfaces on RA-4CT1 Board Description of Indicators on RA-4CT1 Board Interconnection Method of RJ48 Connectors at E1 Port Features of Interfaces on RA-4E1VE Board Description of Indicators on RA-4E1VE Board Features of Interfaces on RA-4FE-R Board Description of Indicators on RA-4FE-R Board Features of Interfaces on RA-4FXO Board Description of Indicators on RA-4FXO Board Features of Interfaces on RA-4FXS Board Description of Indicators on RA-4FXS Board Interface Features of RA-4HS Board Description of Indicators on RA-4HS Board External Cables at Dual Serial Interface Interface Features of RA-4T1VE Board Descriptions of Indicators on RA-4T1VE Board Interface Features of RA-8CE1 Board Description of Indicators on RA-8CE1 Board Interconnection Method of RJ48 Connectors at E1 Ports Interface Features of RA-8CE1-R Board Description of Indicators on RA-8CE1-R Board Interface Features of RA-8FE-R Board Description of Indicators on RA-8FE-R Board
Table Table Table Table
84 85 86 87
Interface Features of RA-8FXS Board Description of Indicators on RA-8FXS Board Parameters of Synchronous/Asynchronous Serial Interfaces IP Address Range of Each Class

Router ZXR10 GAR Manual 1

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Router ZXR10 GAR Manual 1

Загружено:

Авторское право:

Доступные форматы

ZXR10 GAR

General Access Router

Users Manual (Volume I)

ZTE CORPORATION Values Your Comments & Suggestions!

Structure and Principle

User Interface Configuration

Interface Configuration Mode Route Configuration Mode Diagnosis Mode

Online Help Command History

Backing up and Recovering Data Software Version Upgrading

System Parameter Configuration Check System Information System Recovery

Ethernet Interface Configuration

POS Interface Configuration

T1 Interface Configuration Examples for E1 Interface Configuration

Synchronous/Asynchronous Serial Interface Configurations

Voice Interface Configuration

TDMoIP Interface Configuration

VLAN Sub-interface Configuration

Configuration of Link Protocols

Network Protocol Configuration

Static Route Configuration

RIP Maintenance and Diagnosis Examples for RIP Configuration

IS-IS Maintenance and Diagnosis Examples for IS-IS Configuration

BGP Overview BGP Configuration

BGP Maintenance and Diagnosis BGP Configuration Example

Policy Routing Configuration

MPLS VPN Configuration

Abbreviations Figures Tables

About this Users Manual

Purpose of this Users Manual

CAPS Constant width [] {} |

Mouse Operation Conventions

Typeface Click Double-click Right-click Drag

Erosion: Beware of erosion.

No flammables: No flammables can be stored.

No touching: Do not touch.

No smoking: Smoking is forbidden.

How to Get in Touch

Note: Provides additional information about a certain topic.

Model RA-G2604-AC RA-G2604-DC RA-G2608-AC RA-G2608-DC RA-G3608-AC RA-G3608-DC RA-G7208-AC RA-G7208-DC

Power Supply AC DC AC/2AC DC/2DC AC/2AC DC/2DC AC/2AC DC/2DC

Rear panel of ZXR10 GAR (RA-G2604) is shown in Figure 2.

Front panel of ZXR10 GAR (RA-G2608/ RA-G3608/ RA-G7208) is shown in Figure 3

Rear panel of ZXR10 GAR (RA-G2608/ RA-G3608/ RA-G7208) is shown in Figure 4.

Technical Features and Parameters

RA-G7208-AC (DC) network

220VAC, 50Hz (-48VDC) 0~40 20% ~ 90% (non-condensing)

Structure and Principle

Overall Structure and Working Principles

F I G U R E 8 M A I N B O A R D I N T E R F AC E S AN D I N D I C A T O R L I G H T S O F Z X R 1 0 G AR ( R A - G 2 6 0 8 / RA- G3608/ RA- G7208)

BIC Board DB9 1 2 3 4 5 6 7 8 9

DB9 of Background Computer

PC_TX PC_RX PC_DSR PC_GND PC_DTR PC_RTS PC_CTS

BIC Board DB9 1 2 3 4 5

Signal GAR_DCD GAR_RX GAR_TX GAR_DTR GAR_GND

DB9 of Background Computer 8 3 2 20 7

Signal MODEM_DCD MODEM_RX MODEM_TX MODEM_DTR MODEM_GND

BIC Board DB9

DB9 of Background Computer

GAR_DSR GAR_RTS GAR_CTS GAR_RI

MODEM_DSR MODEM_RTS MODEM_CTS MODEM_RI

Indicator PWR (green) RUN (green) ALM (red) FAN

Line Interface Board

Line Interface Board Type