Manual para Referencia R860

CiTRANS R860
Multi-Service Convergence
Router
Product Description
Version: B
Code: MN000001305
FiberHome Telecommunication Technologies Co., Ltd.
March 2013
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +86 27 8769 1549
Fax: +86 27 8769 1755
Website: http://www.fiberhomegroup.com
Legal Notice
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved
No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Related Documentation
Document Description
CiTRANS R860 Multi-Service Introduces functions and features, protection mechanisms,

Convergence Router Product networking applications and technical specifications of the
Description CiTRANS R860.
Gives a detailed introduction to structures, functions, signal
CiTRANS R860 Multi-Service
flow, dimensions and technical specifications of all
Convergence Router Hardware
CiTRANS R860 hardware components, including cabinets,
Description
subracks, cards and cables.
Gives a detailed introduction to the CiTRANS R860
appearance, structures and installation, connection and
Convergence Router Installation
layout of cables and wires as well as installation
Guide
environment requirements.
CiTRANS R860 Multi-Service Gives a detailed introduction to commissioning

Convergence Router precautions, procedures and methods of the CiTRANS
Commissioning Guide R860.
CiTRANS R860 Multi-Service Describes the rules and methods for configuring various
Convergence Router functions and performance parameters of the CiTRANS
Configuration Guide (Subnet- R860 on the OTNM2000 at the subnetwork level, and lists
Level) typical configuration examples and operation procedures.
Gives a detailed description of items and procedures of

CiTRANS R860 Multi-Service routine maintenance on a daily, monthly, quarterly and
Convergence Router Routine yearly basis; introduces routine operation methods and
Maintenance instructs users to perform basic operation based on
hardware and the network management system.
Gives a detailed introduction to troubleshooting

precautions and common location methods as well as
Convergence Router
processing procedures and methods of troubleshooting
Troubleshooting Guide
common faults.
Describes levels, classification and mutual suppression of
alarms and performance events; lists definitions, causes
Convergence Router Alarm and
and troubleshooting methods of all alarms and
Performance Reference
performance events.
I
Document Description

Convergence Router Service Describes the configuration parameters of each card and
Configuration Parameter the parameter meanings.
Reference
Includes five manuals, i.e., product description,
networking, routine maintenance, operation guide and
e-Fim OTNM2000 Element
installation guide, all of which are aimed at introducing
Network Management System
common and fundamental contents of the OTNM2000 for a
Manual Set
better understanding and proficient use of the network
management system.
II
Version
Version Description
A Initial version.
B Adds the SCUR2 card.
Intended Readers
This manual is intended for the following readers:
u Operation and maintenance engineers
u Commissioning engineers
To utilize this manual, these prerequisite skills are necessary:
u Router related technology
u Data communication technology
u Ethernet technology
III
Conventions
Terminology Conventions
Terminology Convention
FiberHome CiTRANS R860 Multi-Service Convergence

CiTRANS R860
Router
FiberHome e-Fim OTNM2000 Element Management
OTNM2000
System
RCUO1 Routing and Control Card
SCUR1 Cross-connect Clock Card

SCUR2 Cross-connect Clock Card
XSR1 2*10GE Ethernet Interface Card
XSR2 10G Ethernet Interface Card
XGR1 Enhanced XGE Interface Card
GSR1 GE Ethernet Interface Card
ESR1 FE Ethernet Interface Card
ESJ1 FE Interface Card with Electrical Switch Function
ESJ2 FE Interface Card with Optical Switch Function
S1J2 STM-1 Optical Interface Card (2 channels)
S1J4 STM-1 Optical Interface Card (8 channels)
E1J2 E1 Interface Card

AIFJ1 Power and Auxiliary Terminal Board 1
AIFJ2 Power and Auxiliary Terminal Board 2
IV
Symbol Conventions
Symbol Refer to Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.
Warning May cause severe bodily injuries.
➔ Jump Jumps to another step.
Cascading
→ Connects multi-level menu options.
menu
Bi-directional
↔ The service signal is bi-directional.
service
Unidirectional
→ The service signal is unidirectional.
service
V
Contents
Preface...................................................................................................................I
Related Documentation ...................................................................................I
Version ..........................................................................................................III
Intended Readers ..........................................................................................III
Conventions ................................................................................................. IV
1 Overview .....................................................................................................1-1
1.1 Architecture ...................................................................................1-2
1.1.1 Overview .........................................................................1-2

1.1.2 Characteristics.................................................................1-2
1.2 Network Application .......................................................................1-5
1.2.1 Product Positioning..........................................................1-5

1.2.2 Network Mode .................................................................1-5
2 Function ......................................................................................................2-1
2.1 Routing and Switching Capability ...................................................2-2
2.2 Service Type and Access Capability...............................................2-2
2.2.1 Service Type....................................................................2-2

2.2.2 Access Capability ............................................................2-2
2.3 Interface Type................................................................................2-3
2.3.1 Service Interface..............................................................2-3

2.3.2 Management and Auxiliary Interface ................................2-4
2.4 Protection Capability ......................................................................2-5
2.4.1 Equipment-Level Protection .............................................2-5

2.4.2 Network-Level Protection .................................................2-6
2.4.3 Protection for Network Management Information ..............2-6
2.5 Carrier-Class Network Management...............................................2-6
2.5.1 Support to Centralized Configuration Management...........2-7

2.5.2 Support to Performance, Alarm, and Security
Management ...................................................................2-7
2.5.3 DCN Construction............................................................2-8
2.6 Monitoring and Maintenance Function ..........................................2-10
2.6.1 Card Self-Booting ..........................................................2-11

2.6.2 Remote Upgrade ...........................................................2-11
2.6.3 Monitoring of the Power Supply and Environment...........2-11
2.6.4 Intelligent Fan Feature ...................................................2-11
3 Feature........................................................................................................3-1
3.1 QoS...............................................................................................3-2
3.1.1 Introduction to QoS ..........................................................3-2

3.1.2 QoS Feature....................................................................3-2
3.2 OAM..............................................................................................3-4
3.2.1 Introduction to OAM .........................................................3-5

3.2.2 OAM Features .................................................................3-6
3.2.3 Introduction to BFD ..........................................................3-7
3.3 Clock Feature ................................................................................3-9
3.3.1 Clock Signal Synchronization...........................................3-9

3.3.2 Introduction to Clock and Time Synchronization..............3-10
3.3.3 Time and Clock Synchronization Function ......................3-16
3.3.4 Reference......................................................................3-18
3.4 VPN Feature................................................................................3-18
3.4.1 Introduction to VPN........................................................3-18

3.4.2 VPN Feature..................................................................3-19
3.4.3 Reference......................................................................3-23
3.5 Applicable EMC / EMI and Safety Standard and Protocol..............3-24
4 Dynamic Routing .........................................................................................4-1
4.1 Overview .......................................................................................4-2
4.2 RIP................................................................................................4-2
4.3 OSPF Protocol...............................................................................4-3
4.4 IS-IS Protocol ................................................................................4-7
4.5 BGPv4.........................................................................................4-11
4.6 IPv6 Dynamic Routing Protocol....................................................4-15
4.7 RSVP ..........................................................................................4-17

4.8 LDP.............................................................................................4-18
5 Product Architecture ....................................................................................5-1
5.1 Logical Structure............................................................................5-2
5.2 Hardware Structure........................................................................5-4
5.2.1 Cabinet............................................................................5-4
5.2.2 PDP ................................................................................5-7
5.2.3 Fiber Passage Unit ..........................................................5-8
5.2.4 Subrack...........................................................................5-9
5.2.5 Overview of Card ...........................................................5-10
5.2.6 The RCUO1 Card ..........................................................5-13
5.2.7 The SCUR1 Card...........................................................5-14
5.2.8 The XSR1 / XSR2 Card .................................................5-15
5.2.9 The XGR1 Card .............................................................5-16
5.2.10 The GSR1 Card .............................................................5-17
5.2.11 The ESJ1 / ESJ2 / ESR1 Card .......................................5-17
5.2.12 The E1J2 Card ..............................................................5-19
5.2.13 The S1J2 / S1J4 Card....................................................5-20
5.2.14 The AIFJ1 / AIFJ2 Card..................................................5-20
5.3 Software Architecture...................................................................5-21
5.3.1 Overview .......................................................................5-21

5.3.2 Communication Protocol and Interface ...........................5-22
5.3.3 BMU ..............................................................................5-23
5.3.4 NMU..............................................................................5-23
5.3.5 Network Management Software .....................................5-24
6 Service and Network....................................................................................6-1
6.1 Ethernet Service ............................................................................6-2
6.1.1 E-Line Service .................................................................6-2

6.1.2 E-LAN Service .................................................................6-4
6.1.3 E-Tree Service.................................................................6-5
6.2 CES Service ..................................................................................6-8
6.2.1 Service Example..............................................................6-8

6.2.2 Emulation Mode...............................................................6-9
6.2.3 Clock Synchronization Mode............................................6-9
6.3 Radio Service ..............................................................................6-12

6.3.1 Service Bearer Solution for the Radio Network ...............6-12
6.3.2 Clock Synchronization Solution for the Radio Network....6-13
6.4 Network Capability.......................................................................6-14
6.4.1 Typical Network for Ethernet Service ..............................6-14

6.4.2 Typical Network for CES Service....................................6-17
6.4.3 Typical Network for Mobile Service.................................6-18
6.4.4 Typical Network for L3VPN ............................................6-19
6.4.5 L2 / L3 Hybrid Network...................................................6-23
6.4.6 MS-PW Network ............................................................6-24
6.4.7 Hierarchical VPLS Network ............................................6-25
7 Protection Mechanism .................................................................................7-1
7.1 Equipment-Level Protection ...........................................................7-2
7.1.1 1+1 Protection for the SCUR1 Card..................................7-2

7.1.2 1+1 Protection for the RCUO1 Card .................................7-3
7.1.3 1+1 Protection for the Power Card....................................7-4
7.2 Network-Level Protection ...............................................................7-4
7.2.1 1:1 Protection for Tunnel ..................................................7-4

7.2.2 PW Redundancy Protection .............................................7-6
7.2.3 Virtual Router Redundancy Protection..............................7-7
7.2.4 Dual-Homing Protection .................................................7-11
7.2.5 MPLS TE FRR Protection ..............................................7-14
7.2.6 VPN FRR Protection ......................................................7-16
7.2.7 IP FRR Protection..........................................................7-18
7.2.8 LDP FRR Protection ......................................................7-20
7.2.9 LAG Protection for the Ethernet......................................7-21
7.3 Protection for Network Management Information ..........................7-23
8 Security Management ..................................................................................8-1
8.1 Network Security Protection ...........................................................8-2
8.1.1 ACL.................................................................................8-2
8.1.2 Traffic Policing .................................................................8-2
8.1.3 Attack Defense ................................................................8-3
8.2 Security Protection for the Network Management System ...............8-6
8.2.1 Access Control ................................................................8-6

8.2.2 User Level and Permission Management .........................8-7
8.2.3 Data Security ...................................................................8-9
8.2.4 Log Management.............................................................8-9
9 Technical Specification.................................................................................9-1
9.1 System Technical Specification ......................................................9-2
9.2 System Performance Specification.................................................9-2
9.3 Mechanical Dimension and Power Consumption ............................9-4
9.4 Performance Specification of Interface ...........................................9-5
9.4.1 Technical Specification of XGE Interface ..........................9-5

9.4.2 Technical Specification of GE Interface.............................9-5
9.4.3 Technical Specification of STM-1 Interface .......................9-6
9.4.4 Technical Specification of E1 Interface .............................9-7
9.4.5 Technical Specification of FE Interface .............................9-8
9.5 Clock Specification ........................................................................9-8
9.6 EMC / EMI Specification ..............................................................9-10
9.7 Applicable Safety Standard ..........................................................9-11
9.8 Environment Requirement ...........................................................9-11
9.8.1 Storage Environment .....................................................9-11

9.8.2 Operating Environment ..................................................9-11
9.8.3 Transport Environment...................................................9-12
Appendix A Abbreviations .......................................................................... A-1

Figures
Figure 1-1 Network Application of the CiTRANS R860 ....................................1-6

Figure 1-2 LTE Service Application of the CiTRANS R860...............................1-7
Figure 2-1 In-band DCN Network for the CiTRANS R860 ...............................2-9
Figure 2-2 Out-of-band DCN Network for the CiTRANS R860 .......................2-10
Figure 3-1 Difference between Time Synchronization and Clock
Synchronization ...........................................................................3-11
Figure 3-2 Principle of the Synchronous Ethernet Technology .......................3-12
Figure 3-3 Implementation Solution of Time Synchronization through 1588v2 3-14
Figure 3-4 Implementation Principle of Time Synchronization through IEEE
1588v2 ........................................................................................3-15
Figure 3-5 Architecture of HoVPN .................................................................3-22
Figure 4-1 Structure of an OSPF Packet .........................................................4-5
Figure 4-2 Typical Application of OSPF...........................................................4-7
Figure 4-3 Typical Application of IS-IS...........................................................4-10
Figure 4-4 Typical Application of BGP ...........................................................4-14
Figure 5-1 Functional Modules of the CiTRANS R860 .....................................5-2
Figure 5-2 Appearance of the 21-inch Cabinet ................................................5-5
Figure 5-3 Equipment Layout (Unit: mm) .........................................................5-6
Figure 5-4 Appearance of the PDP for the 21-inch Cabinet..............................5-7
Figure 5-5 The Fiber Guide Unit......................................................................5-9
Figure 5-6 Layout of the CiTRANS R860’s Slots............................................5-10
Figure 5-7 Locations of Common Cards in the System ..................................5-13
Figure 5-8 System Software Architecture ......................................................5-22
Figure 5-9 Software Architecture of the OTNM2000 ......................................5-24
Figure 6-1 E-Line Service Example.................................................................6-3
Figure 6-2 E-LAN Service Example.................................................................6-5
Figure 6-3 E-Tree Service Example ................................................................6-7
Figure 6-4 CES Example ................................................................................6-8
Figure 6-5 Implementation Principle of System Clock Recovery ....................6-10
Figure 6-6 Implementation Principle of Differential Clock Recovery................6-11
Figure 6-7 Implementation Principle of Adaptive Clock Recovery...................6-11
Figure 6-8 2G/3G RAN Bearer for the CiTRANS R860 ..................................6-12
Figure 6-9 Clock Synchronization through 1588v2 ........................................6-13
Figure 6-10 Typical Networking of the E-Line Service Provided by the CiTRANS
R860 ...........................................................................................6-15
Figure 6-11 Typical Networking in the Ethernet E-LAN Service........................6-16
Figure 6-12 Typical Networking of the E-Tree Service Provided by the CiTRANS
R860 ...........................................................................................6-17
Figure 6-13 Typical Network of the CES Services Provided by the CiTRANS
R860 ...........................................................................................6-18
Figure 6-14 Typical Networking of the Mobile Services Provided by the CiTRANS
R860 ...........................................................................................6-19
Figure 6-15 Ethernet L3VPN Point-to-point Network Diagram..........................6-21
Figure 6-16 Ethernet L3VPN Point-to-multipoint Network Diagram ..................6-22
Figure 6-17 Ethernet L3VPN Hub-Spoke Network Diagram.............................6-22
Figure 6-18 L2 / L3 Hybrid Network.................................................................6-23
Figure 6-19 MS-PW Network ..........................................................................6-24
Figure 6-20 Hierarchical VPLS Network ..........................................................6-25
Figure 7-1 1:1 Protection for Tunnels ..............................................................7-5
Figure 7-2 Master and Backup Redundancy ...................................................7-9
Figure 7-3 Load Sharing ...............................................................................7-10
Figure 7-4 Working Status During Normal Operation .....................................7-11
Figure 7-5 Dual-homing Protection Switching Status – the Network Side is
Faulty ..........................................................................................7-12
Figure 7-6 Dual-homing Protection Switching Status – the AC Side is Faulty .7-12
Figure 7-7 Dual-homing Protection Switching Status – the Network Side and AC
Side are Faulty ............................................................................7-13
Figure 7-8 Dual-homing Protection Switching Status – Node C is Faulty ........7-13
Figure 7-9 FRR in the Bypass Mode .............................................................7-15
Figure 7-10 VPN FRR Protection Principle......................................................7-17
Figure 7-11 IP FRR Protection Principle..........................................................7-19
Figure 7-12 LAG Protection ............................................................................7-22
Figure 7-13 Backup of the Network Management Information Channel on a Ring
Network (When a Transmission Segment Fails)............................7-24
Figure 7-14 Backup of the Network Management Information Channel (During
Normal Operation) .......................................................................7-25
Figure 7-15 Backup of the Network Management Information Channel (When the
Main Channel Fails) .....................................................................7-26
Tables
Table 2-1 Routing and Switching Capability of the CiTRANS R860.................2-2

Table 2-2 Service Types Supported by the CiTRANS R860............................2-2
Table 2-3 The CiTRANS R860's Access Capability........................................2-2
Table 2-4 Service Interfaces of the CiTRANS R860 .......................................2-3
Table 2-5 Management and Auxiliary Interfaces of the CiTRANS R860 ..........2-4
Table 2-6 The Equipment-Level Protection of the CiTRANS R860..................2-5
Table 2-7 Network-Level Protection of the CiTRANS R860 ............................2-6
Table 3-1 Applicable OAM Standards of the CiTRANS R860..........................3-4
Table 3-2 References for Time and Clock Synchronization...........................3-18
Table 3-3 Applicable Standards of the VPN Function ...................................3-23
Table 3-4 Applicable EMC / EMI Standards and Protocols of the CiTRANS
R860 ...........................................................................................3-24
Table 3-5 Applicable Safety Standards ........................................................3-25
Table 4-1 Applicable Standards of RIP ..........................................................4-3
Table 4-2 Applicable Standards of OSPF.......................................................4-7
Table 4-3 Applicable Standards of IS-IS.......................................................4-10
Table 4-4 Applicable Standards of BGP .......................................................4-14
Table 4-5 Applicable Standards of IPv6 Dynamic Routing Protocols.............4-17
Table 4-6 Applicable Standards of RSVP.....................................................4-18
Table 4-7 Applicable Standards of LDP .......................................................4-18
Table 5-1 Subrack Quantities for Cabinets .....................................................5-7
Table 5-2 Appearance and Dimensions of the Cards....................................5-11
Table 5-3 Card Categories ..........................................................................5-12
Table 6-1 Application Scenarios of Ethernet Services Provided by the CiTRANS
R860 ...........................................................................................6-14
Table 6-2 Application Scenarios of CES Services Provided by the CiTRANS
R860 ...........................................................................................6-17
Table 6-3 Application Scenarios of Mobile Services Provided by the CiTRANS
R860 ...........................................................................................6-18
Table 6-4 Application Scenarios of the L3VPN Service.................................6-20
Table 7-1 Protection Parameters ...................................................................7-2
Table 7-2 1+1 Protection Parameters of the RCUO1 Card..............................7-4
Table 7-3 1+1 Protection Parameters of the Power Card ................................7-4
Table 7-4 Protection Parameters ...................................................................7-6
Table 7-5 PW Redundancy Protection Parameters ........................................7-7
Table 7-6 Term Description for VRRP ............................................................7-7
Table 7-7 Dual-homing Protection Parameters.............................................7-14
Table 7-8 Protection Parameters .................................................................7-23
Table 9-1 System Technical Specifications ....................................................9-2
Table 9-2 The CiTRANS R860 System Performance Specification.................9-2
Table 9-3 Dimensions and Weight of the CiTRANS R860 Cabinet..................9-4
Table 9-4 Dimensions and Weight of the CiTRANS R860 Subrack .................9-4
Table 9-5 Dimensions, Weight, and Power Consumption of Cards and Fan Unit
of the CiTRANS R860 ....................................................................9-4
Table 9-6 Technical Specifications of XGE Interfaces.....................................9-5
Table 9-7 Technical Specifications of GE Interfaces .......................................9-6
Table 9-8 Technical Specifications of STM-1 Interfaces..................................9-6
Table 9-9 Technical Specifications of E1 Interfaces........................................9-7
Table 9-10 Technical Specifications of FE Interfaces........................................9-8
Table 9-11 Specifications of Clock Interfaces...................................................9-9
Table 9-12 Wander Generation (MTIE) with Constant Temperature ..................9-9
Table 9-13 Wander Generation (TDEV) with Constant Temperature .................9-9
Table 9-14 Applicable EMC / EMI Standards and Protocols of the CiTRANS
R860 ...........................................................................................9-10
Table 9-15 Safety Standards .........................................................................9-11
1 Overview
The CiTRANS R860 multi-service routing platform (referred to as the CiTRANS

R860 hereinafter) is a high-end IP (Internet Protocol) / MPLS (Multi-Protocol Label
Switching) router developed by FiberHome Telecommunication Technologies Co.,
Ltd. (hereinafter referred to as FiberHome ). The following describes the basic
information about the CiTRANS R860 in these respects:
Architecture
Network Application
Version: B 1-1
CiTRANS R860 Multi-Service Convergence Router Product Description
1.1 Architecture
The following introduces the CiTRANS R860 and its features.
1.1.1 Overview
Data service networks are in the development and transformation stage. With the
trend of the IP telecommunication services, the transport network based services
have changed from TDM (Time Division Multiplex) predomination to IP
predomination. And new types of services emerging in the transmission network
have a higher demand for diversity in data types.
The CiTRANS R860 is a high-end IP / MPLS router that is designed by FiberHome

to meet the high rate, multi-service, and high performance requirements of the next-
generation transport network. The CiTRANS R860 provides line-rate 10GE, GE, FE,
STM-1, and E1 interfaces and can be deployed with the CiTRANS R845 to form a
bearer network solution with a complete structure and a clear hierarchy.
The CiTRANS R860 is based on the distributed hardware forwarding and

nonblocking switching technologies, and features carrier-class reliability, line rate
forwarding performance, a mature QoS mechanism, capability of processing rich
services, and excellent expansion capability.
The CiTRANS R860 works as a backbone convergence router with powerful IP

service processing capability. It integrates Layer 3 Ethernet switching capability and
provides rich IP edge services, including Ethernet switching processing, tunneling,
and flow queues. The can implement smooth migration from IPv4 to IPv6.
1.1.2 Characteristics
The CiTRANS R860 has the following characteristics:
u Capability of providing rich networking services
4 The CiTRANS R860 provides rich Layer 2 services, such as Layer 2 VLAN,
selective QinQ (double VLAN tags: 802.1Q In 802.1Q), and QinQ
termination.
1-2 Version: B
1 Overview
4 The CiTRANS R860 provides rich IPv6 / IPv4 unicast, multicast, and
routing protocols, as well as comprehensive MPLS / MPLS TE support.
4 The CiTRANS R860 provides mature VPN services and complete QoS
capability and supports L2VPN and L3VPN services.
u Multi-service transmission capability
The CiTRANS R860 completes unified service encapsulation through the

PWE3 technology, provides end-to-end transparent transmission paths in the
service forwarding process, and transmits the circuit emulation service (CES)
and Ethernet services.
u Comprehensive carrier-class protection capability
4 1+1 hot standby protection for the RCUO1 card, SCUR1 card, and power
card.
4 GR (Graceful Restart) protection
4 1:1 protection for tunnels
4 Dual-homing Protection
4 Ethernet LAG protection
4 MPLS TE FRR protection
4 VPN FRR protection
4 IP FRR protection
4 LDP FRR protection
4 VRRP protection
u Comprehensive security design
The CiTRANS R860 provides comprehensive security protection measures to

protect network data for carriers and end users. The CiTRANS R860 has the
following security features.
4 The CiTRANS R860 supports ACLs based on the forwarding plane and
control plane.
4 The CiTRANS R860 supports data traffic control and policing.
Version: B 1-3
4 The CiTRANS R860 provides queue buffering management, queue

congestion scheduling, port rate limiting, protection against malformed
packets, suppression of broadcast, multicast, and flooding packets, and
prevention from IP address spoofing.
4 The CiTRANS R860 supports allocation and management of user levels

and rights and user access control.
4 The CiTRANS R860 has multiple security mechanisms to ensure network

management data security, protect data integrity and confidentiality, and
implement database security management.
4 The CiTRANS R860 provides a comprehensive log management function

to allow you to query logs when system security is damaged.
u Carrier-class OAM capability
The CiTRANS R860 supports the high-performance hierarchical OAM

mechanism and locates faults precisely in real time in a complex network
topology.
u Powerful routing capability and service forwarding capability
4 The CiTRANS R860 has powerful routing capability and supports IP /

MPLS distributed forwarding and oversized routing tables.
4 The CiTRANS R860 provides rich routing protocol functions, such as RIP,
OSPF, IS-IS, BGP-4, and multicast routing protocols and the fast
convergence function.
4 The CiTRANS R860 implements full-duplex forwarding at the FE, GE, and
10GE interfaces and integrates the features of Ethernet switches to
support switching on the Ethernet.
u Excellent fast scalability
The CiTRANS R860 supports IPv6 and can quickly implement unpredictable
services in the future to help users improve competitiveness.
u Low transmission cost per bit
Compared with the SDH, the IP-based CiTRANS R860 has the inherent
statistical multiplexing capability and provides connection-oriented flexible
bearer channels with high efficiency, which greatly reduces the transmission
cost per bit.
1-4 Version: B
1 Overview
1.2 Network Application
The following describes the product positioning and network mode of the CiTRANS
R860.
1.2.1 Product Positioning
The CiTRANS R860 focuses on the distribution layer or core layer of the multi-
service metropolitan area network and mobile backhaul network. Together with the
CiTRANS R845 and the CiTRANS R865, the constitutes a network from the access
layer to the distribution layer and forms an IP network solution with a complete
structure and a clear hierarchy to meet the all-service access requirements of
carriers.
The CiTRANS R860 provides access and bearer services for BTSs, which can
connect to the CiTRANS R860 through the E1 interface or FE interface.
The CiTRANS R860 carries TDM mobile services between the BTS and BSC (Base
Station Controller) through the circuit emulation technology, carries Ethernet mobile
services through the MPLS technology, and implements such functions as high-
level QoS for mobile services, protective recovery, time synchronization and clock
synchronization for the bearer network, and end-to-end service configuration and
management.
1.2.2 Network Mode
The CiTRANS R860 focuses on the distribution layer and core layer of the
metropolitan area network and connects to SR devices upstream and to access-
layer devices (for example, the CiTRANS R845) downstream. It aggregates
services to the data backbone network.
Figure 1-1 shows the network application of the CiTRANS R860.
Version: B 1-5
Figure 1-1 Network Application of the CiTRANS R860
In addition to the preceding applications, the CiTRANS R860 supports the Long
Term Evolution (LTE), which is the next version of mobile network evolution.
Compared with 2G and 3G networks, LTE networks have the following advantages:
u Orthogonal frequency division multiplex (OFDM), which is a high speed

transmission technology in dense radio environments, increases frequency
spectrum usage and reduces terminal cost.
u Multiple-input multiple-output (MIMO) increases link capacity and resolves

multipath interference.
u The flattened network structure achieves high throughput and low latency.
The CiTRANS R860's application in the LTE service is shown in Figure 1-2. As the
relay and convergence node, the eNodeB provides the functions of the NodeB and
most functions (including the physical layer, scheduling, access control, bearer
control, and access mobility management) of the radio network controller (RNC).
Original backbone networks are integrated and simplified as mobility management
entities (MMEs) and signal gateways (SGWs). The LTE network structure is
optimized and more reliable.
1-6 Version: B
1 Overview
Figure 1-2 LTE Service Application of the CiTRANS R860
Version: B 1-7
2 Function
As a carrier-class transmission equipment set, the CiTRANS R860 supports

multiple service types and provides a wide variety of functions to ensure service
transmission quality and efficiency. The functions of the CiTRANS R860 are as
described follows:
Routing and Switching Capability
Service Type and Access Capability
Interface Type
Protection Capability
Carrier-Class Network Management
Monitoring and Maintenance Function
Version: B 2-1
2.1 Routing and Switching Capability
The core of the CiTRANS R860 is routing and switching. Table 2-1 shows the
routing and switching capability of the CiTRANS R860.
Table 2-1 Routing and Switching Capability of the CiTRANS R860
Product Code Switching Capacity
CiTRANS R860 The SCUR1 card 320 G
2.2 Service Type and Access Capability
The following describes the service types and access capability of the CiTRANS
R860.
2.2.1 Service Type
The CiTRANS R860 supports L2VPN and L3VPN services, as shown in Table 2-2.
Table 2-2 Service Types Supported by the CiTRANS R860
Service Category Service Type
E-Line
E-LAN
L2VPN services
E-Tree
E-CES
L3VPN services MPLS L3VPN
2.2.2 Access Capability
The CiTRANS R860 supports Ethernet services and CES services. Table 2-3
shows the service types supported by the and the processing capability.
Table 2-3 The CiTRANS R860's Access Capability
Service
Service Type Card Access Capability (Number of Channels)
Category
Ethernet services 10GE 2 (the XSR1 card)
2-2 Version: B
2 Function
Table 2-3 The 's Access Capability (Continued)
Service
Service Type Card Access Capability (Number of Channels)
Category
4 (the XSR2 card)
2 (the XGR1 card)
8 (the GSR1 card)

GE
8 (the XGR1 card)
8 (optical interfaces of the ESR1 card)
FE 12 (optical interfaces of the ESJ1 card)
12 (electrical interfaces of the ESJ2 card)
E1 32 (the E1J2 card)
CES services 2 (the S1J2 card)

STM-1
8 (the S1J4 card)
2.3 Interface Type
The CiTRANS R860 provides external interfaces such as service interfaces and
management and auxiliary interfaces.
2.3.1 Service Interface
The CiTRANS R860 provides a wide variety of service interfaces, as shown in

Table 2-4.
Table 2-4 Service Interfaces of the CiTRANS R860
Interface Type Specification
10GE interface 10GBASE-LR/W

GE interface 1000BASE-LX and 1000BASE-SX
Electrical interface: RJ-45; optical interfaces: 100M-FX and
FE interface
100BASE-TX
E1 interface E1 electrical interface of 75Ω or 120Ω; DE25 socket
Channelized STM-1 interface S-1.1, L-1.1, and L-1.2 based on EOS
Version: B 2-3
2.3.2 Management and Auxiliary Interface
The CiTRANS R860 provides a wide variety of management and auxiliary interfaces,
as shown in Table 2-5.
Table 2-5 Management and Auxiliary Interfaces of the CiTRANS R860
Interface Type Specification Terminal Type
Alarm
ALM interface Alarm output interface
interface
DB-9
Local monitoring interface, which
f interface
connects to the LCT
Control interface for external events
(temperatures and alarms), which
CTR interface
Auxiliary connects to the user's environment
interface monitoring equipment
Monitoring interface for external events

(temperatures and alarms), which
MON interface
connects to the user's equipment to be
monitored
RJ-45
COM1, COM2, Extended interface for intra-NE subrack
COM3 and communication and software debugging
CONS interfaces interface
Network management interfaces 1 and
Management F1 interface and
2, which connect to the network
interface F2 interface
management host
ETH1, ETH2,
Interfaces 1, 2, 3, and 4 of the control
ETH3 and ETH4
plane
interfaces
Used for clock synchronization
External CKIO1 interface
(frequency and phase synchronization).
clock and CKIO2 DB-9
The input and output of clock signals use
interface interface
interfaces 1 and 2.
Used for time synchronization. The input
TOD1 interface
External time and output of time signals use interfaces
and TOD2 RJ-45
interface 1 and 2, which can receive 1PPS & TOD
interface
time signals.
2-4 Version: B
2 Function
2.4 Protection Capability
The CiTRANS R860 provides equipment-level protection, network-level protection,

and protection for network management information.
2.4.1 Equipment-Level Protection
The CiTRANS R860 provides various equipment-level protections, as shown in

Table 2-6.
Table 2-6 The Equipment-Level Protection of the CiTRANS R860
Protected Object Protection Mode

1+1 hot standby
The RCUO1 card
GR protection
The SCUR1 card 1+1 hot standby
The SCUR2 card 1+1 hot standby
Accessed power supply (the AIFJ1, AIFJ2 cards) 1+1 hot standby
1+1 Hot Standby and GR Protection for the RCUO1 Card
Two RCUO1 cards of the CiTRANS R860 are recommended for the to achieve hot
standby. When the active card fails, its services are switched over to the standby
card, thereby implementing the 1+1 protection. In addition, the GR protection of the
routing protocol is configured; when the RCUO1 card performs the active / standby
switching or rebooting operations due to the software upgrade or equipment faults,
the forwarding of services will not be interrupted.
1+1 Protection for the SCUR1 / SCUR2 Card
Two SCUR1 / SCUR2 cards of the CiTRANS R860 are recommended for the to
achieve hot standby. When the active card fails, its services are switched over to the
standby card, thereby implementing the 1+1 protection.
1+1 Protection for Accessed Power Supply
The AIFJ1 and AIFJ2 cards of the CiTRANS R860 are recommended for the for
inputting the -48 V power supply to achieve hot standby.
Version: B 2-5
2.4.2 Network-Level Protection
The CiTRANS R860 provides various network-level protections, as shown in

Table 2-7.
Table 2-7 Network-Level Protection of the CiTRANS R860
Protection Type Protection Mode

Tunnel protection 1:1
Dual-homing protection Dual-homing 1:1
IP FRR, VPN FRR, MPLS TE FRR, and LDP FRR

FRR protection
protection
Redundancy gateway protection VRRP protection
LAG protection for Ethernet access

Port aggregation
links
2.4.3 Protection for Network Management Information
The CiTRANS R860 provides a standby channel for network management

information. It connects the network elements (NEs) that require protection for
network management information to the network management host through the data
communication network (DCN), thereby setting up a standby channel for network
management information.
When the network is normal, network management information is transmitted on the

active channel. When the active channel is faulty, an NE automatically switches to
the standby channel to transmit network management information, which allows the
NMS to monitor and operate the entire network.
2.5 Carrier-Class Network Management
The CiTRANS R860 uses the OTNM2000 EMS (referred to as OTNM2000

hereinafter) to implement network management. The OTNM2000 is the subnetwork
of the telecommunication management network and designed based on the open
systems interconnection (OSI) standard of the ISO.
2-6 Version: B
2 Function
The OTNM2000 is developed by FiberHome and manages the transmission

equipment and access equipment from FiberHome on a platform. This facilitates the
user's operations and reduces the user's maintenance cost.
The CiTRANS R860 supports logging in the OTNM2000 in the PPPoE (Point to
Point Protocol over Ethernet) mode.
2.5.1 Support to Centralized Configuration Management
The CiTRANS R860 uses the OTNM2000 to perform unified configuration

management at the central office, with a large control scope, high management
efficiency, and low maintenance cost.
Configuration management covers network configuration and NE configuration.
u Network configuration: Includes setting up and modifying physical links and

service channels of a network and deleting channels, and reconfiguring
physical links and channels and recovering routes when faults occur on the
network.
u NE configuration: Indicates managing (creating, deleting, and modifying) NEs

that constitute a communication network, including NE initialization and
function configuration (adding or deleting NEs, subracks, or cards).
2.5.2 Support to Performance, Alarm, and Security

Management
The CiTRANS R860 uses the OTNM2000 to perform performance management

and alarm management and implements operations, such as real-time collection,
alert, browsing, filter, confirmation, clearing, and statistics related to performance
data and alarms, as well as alarm correlation analysis and fault diagnosis.
Version: B 2-7
u Performance management: The OTNM2000 provides the performance

management function and generates assessments and reports on the
transmission performance parameters of communication equipment and
networks. It collects quality data and statistics on the actual operation of
equipment on a communication network and monitors the status and
performance of the network and equipment. This provides a theoretical basis
for the maintenance personnel to perform network assessment, analysis,
prediction, and planning.
u Alarm management: The OTNM2000 provides the alarm management function.

It monitors any abnormal operation of equipment and network channels in real
time, completes monitoring, reporting, and storage of alarm signals, and
implements fault diagnosis, locating, and troubleshooting.
2.5.3 DCN Construction
The DCN (Data Communication Network) is part of network management and

transmits network management information.
The CiTRANS R860 supports multiple DCN construction modes and isolation of the
management communication network and the signaling communication network,
and implements both in-band and out-of-band DCN network modes.
2.5.3.1 In-band DCN Network
On an in-band DCN, the service channel provided by the managed equipment is

used to complete network equipment management. Network management
information is transmitted on the service channel of the equipment.
The in-band DCN network mode is flexible and requires no additional equipment.
The CiTRANS R860 supports the following interfaces of an in-band DCN:
u 10GE interface
u GE interface
u FE interface
u STM-1 interface
2-8 Version: B
2 Function
Figure 2-1 shows the in-band DCN network for the CiTRANS R860.
Figure 2-1 In-band DCN Network for the CiTRANS R860
2.5.3.2 Out-of-band DCN Network
On an out-of-band DCN, channels except service channels are used to transmit

network management information to implement network management.
Compared with an in-band DCN, an out-of-band DCN provides management

channels that are more reliable. When service channels of an out-of-band DCN are
faulty, network management information can be obtained in a timely manner and
real-time network monitoring can be implemented.
An out-of-band DCN requires dedicated communication channels independent of

service channels.
In the out-of-band DCN network mode, the network management center can set up
a DCN with the managed equipment in multiple modes. The CiTRANS R860
supports the following out-of-band DCN network modes:
u E1 private line
u Ethernet
Figure 2-2 shows the out-of-band DCN network for the CiTRANS R860.
Version: B 2-9
Figure 2-2 Out-of-band DCN Network for the CiTRANS R860
2.6 Monitoring and Maintenance Function
The CiTRANS R860 provides complete monitoring and maintenance functions,

including card self-booting, monitoring of the power supply and environment, remote
upgrade, and intelligent fan features.
2-10 Version: B
2 Function
2.6.1 Card Self-Booting
The CiTRANS R860 performs the card self-booting function. When the RCUO1 card
of the CiTRANS R860 is present and works properly and a new card is inserted, the
system detects information about the new card, such as the network block and NE
to which the new card belongs and the card name. Then, the system reports the
detected information to the OTNM2000, prompts the user to confirm the information,
and stores the information to the database. This simplifies the management and
configuration procedures and facilitates commissioning for project startup and
subsequent maintenance.
2.6.2 Remote Upgrade
Remote login is a service provided by the Internet to allow users to operate

computers remotely. Remote login is widely used on the transport networks such as
SDH, MSTP and PTN, especially in large-scale project start-up, equipment upgrade,
and network monitoring and maintenance.
The CiTRANS R860 supports remote upgrade of the field programmable gate array
(FPGA) and business manager unit (BMU) of each card from a computer at the
remote end, which facilitates project startup and maintenance and meets system
upgrade requirements in the future.
2.6.3 Monitoring of the Power Supply and Environment
The CiTRANS R860 provides two channels of -48 V power input, monitors the
power supply status and the temperature inside the cabinet through the RCUO1
card, and controls the fan system based on the configured temperature threshold.
The CiTRANS R860 monitors the equipment room environment in real time and
reports the data via the external monitoring interface of the AIFJ1 card.
2.6.4 Intelligent Fan Feature
The fan unit of the CiTRANS R860 can work in intelligent mode or manual mode.
Version: B 2-11
Introduction
u Intelligent mode: The fan unit automatically adjusts the rotational speed of the
fan based on the temperature reported by each card of the CiTRANS R860.
u Manual mode: The fan unit operates based on the rotational speed set by the
NMS. Speed options are full speed, fast speed, slow speed, and low speed in
the manual mode.
Warning:
In the manual mode, the CiTRANS R860 cannot monitor temperature

changes in real time, which may cause faults on the CiTRANS R860. The
fan unit must be in the intelligent mode when the CiTRANS R860 works
properly.
Implementation
The fan unit is started in soft-start mode to reduce the impact of fan startup on the
CiTRANS R860. In intelligent mode, after the fan is started, the fan operates at the
medium speed before being controlled by the routing and control card.
u After controlling the fan, the routing and control card regularly collects the
temperature information reported by each card of the CiTRANS R860 and
compares the collected temperature information with the fan speed adjustment
parameter of each card to determine the speed for fan operations.
u The fan unit controls the fan to operate in the required speed based on the
speed information sent by the routing and control card, thereby ensuring
cooling of the CiTRANS R860.
u When the fan is faulty, the fan unit sends fault information to the routing and
control card and reports a fan fault alarm to the NMS.
2-12 Version: B
3 Feature
The CiTRANS R860 provides the following features to ensure service transmission
quality and efficiency:
QoS
OAM
Clock Feature
VPN Feature
Applicable EMC / EMI and Safety Standard and Protocol
Version: B 3-1
3.1 QoS
The following describes the basic concepts of QoS and the QoS features of the
CiTRANS R860.
3.1.1 Introduction to QoS
QoS (Quality of Service) refers to the performance when data flows pass a network.
QoS is defined for the purpose of guaranteeing E2E service quality for users.
QoS cannot increase the bandwidth. However, it can minimize the delay and jitter
on a network and ensure the quality of principal services by properly allocating
network resources and monitoring the resource usage.
KPIs for measuring the QoS are listed as follows:
u Service availability: normal operation time when service quality is ensured.
u Delay: duration from the time when a packet is sent to the time when the packet
is received.
u Jitter: deviation of time when packets are received. The packets are sent along
the same route.
u Throughput: rate for sending packets. Throughput can be represented as the

average rate or peak rate.
u Packet loss rate: maximum rate of discarded packets during packet

transmission.
3.1.2 QoS Feature
Traffic Bandwidth Control
The CiTRANS R860 supports multiplayer bandwidth control policies for uplink and
downlink traffic.
u Traffic bandwidth control based on tunnels
u Traffic bandwidth control based on PW
u Traffic bandwidth control based on virtual service ports of L2VPNs or L3VPNs
3-2 Version: B
3 Feature
u Traffic bandwidth control based on physical ports
u Traffic bandwidth control based on logical ports
Service Priority Mapping
The CiTRANS R860 supports the Differentiated Service (DiffServ) model. It

completely implements per-hop behavior (PHB) so that carriers can ensure
differentiated QoS levels for users.
During data forwarding, the CiTRANS R860 maps user priorities and VC priorities
carried in received packets to PHBs, and PHBs in forwarded packets to pseudo wire
(PW) or label switched path (LSP) priorities.
The CiTRANS R860 supports setting PHBs for virtual service ports of L2VPNs and
L3VPNs, physical ports, and logical ports. An existing mapping table (mapping
between PHBs and PW priorities) can be used. Also, a PHB service level can be
specified.
Queue Buffering Management
When network congestion occurs, the CiTRANS R860 employs certain queue
buffering management policies to preferentially ensure the QoS of services with
high priorities.
The CiTRANS R860 supports two types of queue buffering management policies.
u Tail drop
When a queue is full, packets that arrive later are discarded.
u Weighted Random Early Detection (WRED)
4 When the number of packets stored in a buffer does not exceed the
threshold specified by START, the system does not discard packets.
4 When the number of packets stored in the buffer exceeds the threshold
specified by END, all packets are discarded.
4 When the number of packets stored in the buffer is between the START
and the END, all packets face a probability of being dropped based on an
average-queue-length function.
Version: B 3-3
Queue Scheduling
When congestion occurs, the CiTRANS R860 employs different queue scheduling
policies to guarantee the QoS of services with high priorities.
The CiTRANS R860 supports the following two queue scheduling modes.
u SP (Strict Priority)
Packets are scheduled in strict accordance with the priorities of queues.

Packets in queues with lower priorities are sent only after all packets in queues
with higher priorities are forwarded.
u Weighted Fair Queuing (WFQ)
Packets are scheduled fairly based on the weights of queues. Queues with
higher priorities are assigned higher weights and therefore occupy more
bandwidth. Similarly, queues with lower priorities are assigned lower weights
and therefore occupy less bandwidth.
3.2 OAM
The CiTRANS R860 supports BFD (Bidirectional Forwarding Detection) - based

OAM, 802.1ag Ethernet OAM, GACh+Y.1731 MPLS-TP OAM, and IEEE 802.3ah
access link OAM to implement OAM functions on the user side and at different
network layers of MPLS-TP. This implements fast fault detection, which then triggers
protection switchover, thereby offering carrier-class QoS on route switching
networks.
Table 3-1 lists the applicable OAM standards of the CiTRANS R860 at different
network layers.
Table 3-1 Applicable OAM Standards of the CiTRANS R860
Network Layer OAM Standard

Access link OAM IEEE 802.3ah
MPLS-TP OAM (VS / VP / VC) GACh+Y.1731
Ethernet OAM 802.1ag
draft-ietf-bfd-base-08, draft-ietf-bfd-v4v6-1hop-08, draft-

BFD
ietf-bfd-multihop-06
3-4 Version: B
3 Feature
3.2.1 Introduction to OAM
Based on network operation requirements of carriers, the management of a network

is usually classified into operation, administration, and maintenance, that is, OAM.
u Operation and administration: routine analysis, prediction, planning, and

configuration for the network and services.
u Maintenance: routine activities such as performing network and service tests

and fault management.
According to ITU-T, OAM is illustrated as follows:
u Conducts performance monitoring and generates maintenance information,

which is used for evaluating network stability.
u Checks for network faults periodically and generates related maintenance and
alarm information.
u Ensures normal network operation by scheduling or switching over to other

entities and bypassing the faulty entity.
u Transmits fault information to the administration entity.
Access Link OAM
Access link OAM is a type of E2E OAM function specific for services. It can check
the quality of an Ethernet link that passes multiple NEs.
MPLS-TP OAM
MPLS-TP OAM can detect and identify defects on an MPLS-TP network, thereby
finishing performance monitoring for the network.
A switchover is triggered based on the detected status. This implements quick fault
detection and service switchover and therefore ensuring carrier-class QoS over
packet switched networks.
MPLS-TP OAM complies with the GACh+Y.1731 standard. This mechanism can
implement features with abundant service overheads as SDH networks do,
automatic multilayer fault detection, protection switchover, performance monitoring,
and fault identification, thereby implementing multilayer OAM monitoring.
Version: B 3-5
Ethernet OAM
Ethernet OAM is a mechanism for monitoring network problems and works at the
data link layer. In the Ethernet OAM mechanism, devices periodically exchange
OAM PDUs to report network status so that the network administrator can
effectively manage the network.
Ethernet OAM complies with the 802.1ag standard and supports both proactive fault
management and on-demand fault management. It can implement functions on the
Ethernet, including connectivity check, loopback detection, message tracing,
alerting, channel maintenance, and remote fault notification.
BFD
BFD is a simple Hello protocol. It resembles the neighbor detection part of a routing
protocol. In BFD, the two devices of a channel periodically exchange detection
packets. If either device does not receive a detection packet within the specified
time, the channel is faulty.
3.2.2 OAM Features
Compared with SDH networks that provide powerful OAM functions, traditional
packet switched networks provide weak management and maintenance functions.
Therefore, it is difficult for traditional packet switched networks to offer E2E service
management, fault detection, and performance monitoring. CiTRANS R860The
provides the functions of traditional IP routers and incorporates partial advantages
of MPLS, thereby offering multilayer OAM functions.
The OAM functions of the CiTRANS R860 are described as follows:
u Multilayer OAM function: The provides a maximum of eight MEG layers (0 to 7).
Each layer performs OAM functions independently to accommodate different
network deployment policies.
u Fault management-related OAM function: implements automatic detection,

verification, identification, and notification of network faults. E2E fault
management can be implemented at the VC layer of an MPLS network.
3-6 Version: B
3 Feature
u Performance monitoring-related OAM function: implements online

measurement and reporting of network performance. E2E performance
measurement can be implemented at the VC layer of an MPLS network.
u Routine maintenance-related OAM function: involves loopback and locking

operations. This type of OAM function helps operators perform routine
maintenance conveniently.
The CiTRANS R860 also supports OAM on the Ethernet.
u Ethernet in the First Mile OAM (EFM OAM)
EFM OAM provides connectivity check, fault monitoring, remote fault

notification, and remote loopback for the link between two directly connected
devices. On a MAN, EFM OAM is typically applied between the CE (Customer
Edge) and the PE (Provider Edge) to ensure connection reliability and stability
between the user network and the carrier network.
u Connectivity Fault Management OAM (CFM OAM)
CFM OAM implements E2E connectivity check, fault advertisement, fault

ascertainment, and fault identification for networks. CFM OAM is typically
applied on access and convergence networks to monitor the connectivity of the
entire network, thereby identifying connectivity faults on the network. It can also
be used together with the protection switchover technology to enhance
reliability.
3.2.3 Introduction to BFD
BFD Operating Mechanism
BFD provides a general and standardized fast fault detection mechanism

independent of media and protocols. It can quickly detect faults on the bidirectional
forwarding path between two routers in upper-layer protocols such as routing
protocols and MPLS.
Version: B 3-7
BFD sets up a session between two routers to monitor the bidirectional forwarding
path between the routers. BFD does not have a discovery mechanism. An upper-
layer protocol of the service detects and finds BFD of the objects for session setup.
After a session is set up, if a system does not receive a BFD control packet from the
peer system within the detection duration, BFD determines that a fault occurs and
notifies the served upper-layer protocol, which performs corresponding processing.
BFD Operating Mode
The BFD operating mode can be active mode or passive mode before session
setup. During session initialization, at least one of the communicating parties must
operate in active mode to ensure that a session can be set up.
u Active mode: A system sends BFD control packets before a session is set up
regardless of whether it receives BFD control packets from the system at the
peer end.
u Passive mode: A system does not send BFD control packets before a session
is set up until it receives BFD control packets from the system at the peer end.
The BFD operating mode can be asynchronization mode or query mode after
session setup.
u Asynchronization mode: A router operating in asynchronization mode

periodically sends BFD control packets. If it does not receive a BFD control
packet within the detection duration, it determines that a fault occurs.
u Query mode: Assume that each system has a method for confirming that it
successfully connects to other systems. The system stops sending BFD control
packets when a BFD session is set up.
BFD Application
The CiTRANS R860 supports the following BFD application types:
u BFD for static routes
u BFD for VRRP
u BFD for OSPF
u BFD for ISIS
u BFD for BGP
3-8 Version: B
3 Feature
u BFD for LSP
u BFD for PW
3.3 Clock Feature
The CiTRANS R860 supports the physical-layer clock synchronization mechanism

and the IEEE 1588v2 time synchronization protocol and uses a clock input / output
interface to implement physical-layer clock synchronization.
3.3.1 Clock Signal Synchronization
The CiTRANS R860 supports physical-layer clock synchronization and IEEE

1588v2 time synchronization.
Physical-layer Clock Synchronization
In physical-layer clock synchronization, clock information is extracted from the

signals transmitted on physical channels for frequency synchronization.
The CiTRANS R860 supports extraction of clock information from the following
transmission links:
u E1 interface
u FE interface
u GE interface for synchronous Ethernet
u STM-1 interface
The CiTRANS R860 supports two channels of external clock source input and
output, can use clock interfaces of 75Ω and 120Ω, and provides stratum 3 clock
sources of 2048 kHz / 2048 kbit/s (HDB3) coding externally.
The CiTRANS R860 supports the clock working modes of locked, holdover and
free-running and can process and transmit Synchronization Status Messages
(SSMs).
Version: B 3-9
IEEE 1588v2 Time Synchronization
IEEE 1588v2 is a time synchronization protocol and its precision reaches

nanoseconds, which meets the requirements of 3G base stations.
The CiTRANS R860 supports the following features of IEEE 1588v2:
u Implementation of clock synchronization and time synchronization through

IEEE 1588v2.
u Two clock modes. The clock mode can be configured for each port as required.
4 Boundary clock mode
4 Ordinary clock mode
u Protection switchover of clock sources.
3.3.2 Introduction to Clock and Time Synchronization
Synchronization covers clock synchronization and time synchronization.
u Frequency synchronization, or clock synchronization, refers to: (1) the attaining

of synchronism between the frequencies or phases of two or more signals; (2)
the obtaining of a desired, fixed relationship among corresponding significant
instants of two or more signal; (3) the valid moment occurs at the same rate.
u Time synchronization indicates that the internal clock and time of a device are
controlled based on the received time. Time synchronization controls both clock
frequency and phase and represents clock phase with a value, that is, time of
the day (ToD).
The synchronization technologies of the IP radio access network (RAN) include:
u Synchronous Ethernet technology (for clock synchronization)
u 1588v2 technology (for time synchronization)
3-10 Version: B
3 Feature
Figure 3-1 Difference between Time Synchronization and Clock Synchronization
Figure 3-1 shows the difference between time synchronization and clock
synchronization.
u Electronic clocks 1 and 2 maintain time consistency at every moment. This

status is called time synchronization.
u Electronic clocks 1 and 2 maintain a constant time difference, for example, one
hour. This status is called clock synchronization.
Note:
The consistency of time difference between electronic clocks 1 and 2
cannot be maintained if electronic clocks 1 and 2 have different
frequencies. Therefore, clock synchronization is the prerequisite for time
synchronization.
Version: B 3-11
3.3.2.1 Synchronous Ethernet Technology
The synchronous Ethernet technology, simplified as SyncE, implements clock

recovery by using Ethernet link code streams. The coding of the Ethernet physical
layer uses the 4B / 5B (FE) and 8B / 10B (GE) technologies. Every four bits are
inserted with a spare bit. In this way, the data code streams transmitted at the
physical layer do not contain four consecutive 1s or 0s, which allows those streams
to carry clock information effectively. On the Ethernet, a high-precision clock is used
to send data on the source interface. The clock is recovered and extracted at the
receive end, which maintains high-precision clock performance.
Figure 3-2 shows the principle of the synchronous Ethernet technology. As a

technology of clock frequency synchronization, it uses physical-layer signals of the
Ethernet to transmit clocks, which is similar to that on the synchronous digital
hierarchy (SDH) network.
Figure 3-2 Principle of the Synchronous Ethernet Technology
u The equipment (Node A) at the transmit end injects a high-precision clock to

the PHY chip of the Ethernet. The PHY chip uses the high-precision clock to
send data.
u The PHY chip of the equipment (Node B) at the receive end extracts the clock
from the data code stream without deteriorating the clock precision, ensuring
precise clock synchronization with the source end.
3-12 Version: B
3 Feature
The synchronous Ethernet technology is mature and easy to implement and hardly
affected by network damages. The clock synchronization quality approximates to
that of SDH. The architecture of the synchronous Ethernet technology is similar to
that of the SDH solution. It is applicable to network frequency synchronization.
3.3.2.2 IEEE 1588v2 Time Synchronization
IEEE 1588v2 enables the most precise time on a distributed network to keep
synchronous with other time. IEEE 1588v2 defines a Precision Time Protocol (PTP)
to implement submicrosecond-level synchronization for clocks of sensors,
performers, and other terminals on standard Ethernets or distributed bus systems
that use multicast technologies. In IEEE 1588, four types of packets, that is, Sync,
Follow_up, Delay-Req, and Delay-Resp, are used for time alignment and delay
compensation.
Figure 3-3 shows the IEEE 1588v2 time synchronization solution.
Version: B 3-13
Figure 3-3 Implementation Solution of Time Synchronization through 1588v2
Figure 3-4 shows the IEEE 1588v2 time synchronization principle.
3-14 Version: B
3 Feature
Figure 3-4 Implementation Principle of Time Synchronization through IEEE 1588v2
According to Figure 3-4, we can get (1) and (2) :
t1 + TSlaveoffset + TDelay(m->s) = t2; (1)
t3 - TSlaveoffset + TDelay(s->m) = t4; (2)
(1) + (2): TDelay(m->s)+ TDelay(s->m) = (t2 - t1) + (t4 - t3)
Assume that TDelay(m->s) = TDelay(s->m) = TDelay. The formula for calculating the delay
between the master and slave ports is as follows:
TDelay = [(t2- t1) + (t4- t3)]/2
The master and slave ports send PTP packets continuously. The slave port
synchronizes its time with TDelay so that its time is synchronous with that of the
master port.
Version: B 3-15
IEEE 1588v2 delivers high synchronization precision, precise to submilliseconds.

IEEE 1588v2 complies with the industrial standard and is applicable to time
synchronization on networks.
3.3.3 Time and Clock Synchronization Function
The following describes the internal clock unit and time and clock synchronization
capability of the CiTRANS R860.
3.3.3.1 Internal Clock Unit
The internal system clock unit of the CiTRANS R860 is embedded into the SCUR1
card and provides clock reference for the entire system.
The clock unit complies with the ITU-T G.8261 standard. The clock unit can provide
a system clock in compliance with the G.8262 standard for synchronous Ethernet
devices. It supports multiple types of clock references and provide stratum-3 clocks.
In this way, the CiTRANS R860 can apply to different environments and support
flexible networking.
The clock unit has the following features:
u Provides stable clock frame positioning pulse and multiframe positioning pulse.
u Automatically selects and traces proper clock reference sources.
u Provides input interfaces for multiple types of clock reference sources.
u Provides 2048 kHz and 2048 kbit/s (HDB3) stratum-3 clock sources.
u Provides automatic protection switchover.
u Provides a superior monitoring and management system.
u Provides the mutual locking function for cards and supports smooth clock
switchover.
3.3.3.2 Time and Clock Synchronization
The CiTRANS R860 supports physical-layer clock synchronization and Ethernet

time synchronization.
3-16 Version: B
3 Feature
Physical-layer Clock Synchronization
In physical-layer clock synchronization, clock information is extracted from the

signals transmitted on physical channels for frequency synchronization.
The CiTRANS R860 supports extraction of clock information from the following
transmission links:
u E1 interfaces
u FE interfaces
u GE interfaces
u STM-1 interfaces
The CiTRANS R860 two channels of external input and output clock sources. 75-
ohm or 120-ohm clock interface can be used. The two external input and output
clock sources work in 1+1 protection mode.
Provides 2048 kHz and 2048 kbit/s (HDB3) stratum-3 clock sources.
The CiTRANS R860 supports three working modes for processing and transmitting
SSM information: locked, holdover, and free-running. The system can process SSM
information of a maximum of 52 directions.
IEEE 1588v2 Time Synchronization
The CiTRANS R860 supports Ethernet time synchronization in accordance with the
IEEE 1588v2 protocol. IEEE 1588v2 is a time synchronization protocol and can
implement time synchronization precise to nanosecond, meeting the requirements
of 3G BTSs.
Supports the following features of IEEE 1588v2:
u Clock and time synchronization.
u Two clock modes. The clock mode can be configured for each port as required.
4 Boundary clock mode
4 Ordinary clock mode
u Protection switchover of clock sources.
Version: B 3-17
3.3.4 Reference
The following describes the reference standards for time and clock synchronization
of the CiTRANS R860.
For details about time and clock synchronization, refer to related standards listed in
Table 3-2.
Table 3-2 References for Time and Clock Synchronization
Standard Number Title

Standard for A Precision Clock Synchronization Protocol for Networked
IEEE 1588v2
Measurement and Control Systems
G.813 Timing characteristics of SDH equipment slave clocks
The control of jitter and wander within digital networks which are based
G.823
on the 2048 kbit/s hierarchy
G.8262 Timing characteristics of a synchronous Ethernet equipment slave clock
G.8264 Timing and Synchronization Aspects in Packet Networks
3.4 VPN Feature
The CiTRANS R860 supports L3VPN and L2VPN.
3.4.1 Introduction to VPN
The following describes the background and characteristics of the VPN.
3.4.1.1 Background of VPN
With the social development, IT technologies are widely applied in service

processes of modern enterprises. IT technologies such as resource planning, IP
network-based voice, IP network-based conference, and IP network-based
education technologies are employed to build an architecture for automated office
and information retrieval.
3-18 Version: B
3 Feature
As the network industry develops, many enterprises are becoming increasingly

large in scale, more cooperators are available, and the mobility of employees
increases. This poses an urgent need to connect the headquarters and branches to
form an independent enterprise network with the help of the telecommunication
network of carriers. As a result, the staff of an enterprise can connect to the
enterprise network in other locations.
To resolve these problems, the VPN solution is introduced.
3.4.1.2 Characteristics of VPNs
The VPN has the following characteristics:
u Private: A VPN is similar to a traditional private network. Resources for VPNs

are independent from the underlying bearer network. That is, resources for a
VPN will not be used by users that do not belong to this VPN. In addition, users
on VPNs are protected against external networks.
u Virtual: Users on a VPN communicate with each other on the public network,
which is also used by non-VPN users. The VPN is a logical private network.
This public network is called the VPN backbone.
The existing IP network can be divided into logically isolated networks based on
these characteristics. This type of logically isolated network (VPN) can be widely
used. A logically isolated network can be used for internal interconnection within an
enterprise or between departments. It can also be used to provide new services. For
example, a VPN can be assigned for the IP telephony service to address problems
such as IP address shortage, QoS guarantee, and new value-added service
provisioning.
VPN is becoming increasingly popular in providing interconnection within

enterprises and providing new services. It is widely used by carriers to provide
value-added services on the IP network.
3.4.2 VPN Feature
The CiTRANS R860 supports L3VPN and L2VPN.
Version: B 3-19
3.4.2.1 L2VPN
L2VPN includes the Virtual Pseudo Wire Service (VPWS) and the Virtual Private
LAN Service (VPLS).
With the development of network technologies, carrier networks become

increasingly complex. This poses a need for new technologies to integrate the
traditional switching network with the IP or MPLS network. L2VPN is introduced to
fulfill this purpose.
VPWS
VPWS is an emulation of the traditional leased line service. In VPWS, the IP

network is used to simulate the leased line to provide asymmetric data transmission
services with low costs. For users at the two ends of the virtual leased line, the
virtual leased line resembles the traditional leased line.
VPWS is compatible with traditional private networks such as the asynchronous

transfer mode (ATM) and frame relay (FR). Carriers can have their traditional
networks upgraded to VPWS smoothly.
VPLS
In VPLS, LANs are interconnected over virtual private network segments. It is the
extension of LANs on the IP public network.
VPLS is also called transparent LAN service. Unlike the P2P service of common
L2VPNs, VPLS enables SPs to provide Ethernet-based P2MP services over the
MPLS backbone.
On the VPLS backbone, full-mesh connection and horizontal split are used to
eliminate loops. Unknown unicast and multicast frames may be discarded, locally
processed, or broadcast. VPLS extends the application of VLANs across the
country or even the world.
3-20 Version: B
3 Feature
3.4.2.2 L3VPN
L3VPN is also called virtual private routing network (VPRN). L3VPN differs from
other types of VPNs in that VPRN packets are forwarded at the network layer. The
VPN node on the public network needs to establish a dedicated routing forwarding
table for each VPN. The routing forwarding table contains routing information about
the network layer. Data flows are forwarded between the VPN node on the public
network and user sites based on the dedicated routing forwarding table.
L3VPN forwards IP packets in a way similar to traditional routing. After a router

receives an IP packet, the router queries the forwarding table for the destination
address of the IP packet and then forwards the IP packet across the backbone of
the carrier along the pre-set-up LSP.
The boundary router of the carrier exchanges routing information with the client
router so that routers on the carrier network can detect routing information about the
user network. The boundary router can exchange routing information with the client
router over a static route, or over dynamic routing protocols such as RIP, OSPF, IS-
IS, and BGP.
HoVPN (Hierarchy of VPN) allocates the PE (Provider Edge) functions to multiple

PE equipment sets. In this mode, multiple equipment sets act as different roles, and
form the hierarchical structure, so as to conduct the functions of one PE.
Version: B 3-21
Figure 3-5 Architecture of HoVPN
As shown in Figure 3-5, the equipment set directly connected to the user is called
the UPE (User-end PE); the inside-network equipment set connected to the UPE is
called the SPE (Service Provider-end PE). Multiple UPEs and SPEs form the
hierarchical PE, and conduct the functions of a traditional PE.
u UPE
4 The UPE performs the user access function.
4 The UPE maintains the routes of the VPN site connected directly with the
UPE itself, but does not maintain the routes of other remote sites in the
VPN, or it only maintains their aggregation routes.
4 The UPE allocates the inner labels for the routes of the sites directly with
itself, and sends these labels to the SPE via the MP-BGP together with the
VPN routes.
4 The route capacity and forwarding capability of the UPE is low, but its
access capability is strong.
u SPE
4 The SPE completes the management and distribution of the VPN routes.
3-22 Version: B
3 Feature
4 The SPE maintains all routes of the VPN connected with the UPE,
including the routes of the local and remote sites. The SPE distributes the
route information to the UPE, together with the label.
4 The route information distributed by the SPE can be the default route (or
aggregation route) of the VPN instance or the route information related to
the routing policy. Via the latter, the users can control of the access
between sites in the same VPN.
4 The SPE has the following features: the routing table with a large capacity,
a strong forwarding capability, but it supports little interface resources.
u SPE-UPE
4 The MP-BGP (Multiprotocol Extensions for BGP-4) runs between the SPE
and the UPE. It can be MP-IBGP or MP-EBGP, depending on whether the
UPE and the SPE belong to the same AS.
4 When the MP-IBGP is used, to notify the route between the IBGP peer
body, the SPE acts as the route reflector, and distributes the VPN routes
from the IBGP peer body to the IBGP peer body SPE. But the SPE does
not act as the route reflector of other PEs.
3.4.3 Reference
The following lists the applicable standards of the VPN function.
Refer to standards in Table 3-3 for more information about the VPN.
Table 3-3 Applicable Standards of the VPN Function

RFC 3985 Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
Requirements for Pseudo-Wire Emulation Edge-to-Edge

RFC 3916
(PWE3)
RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)
Virtual Private LAN Service (VPLS) Using Label Distribution

RFC 4762
Protocol (LDP) Signaling
Encapsulation Methods for Transport of Layer 2 Frames Over

RFC 4905
MPLS
Version: B 3-23
Table 3-3 Applicable Standards of the VPN Function (Continued)

RFC 4906 Transport of Layer 2 Frames Over MPLS
draft-kompella-ppvpn-l2vpn-
Layer 2 VPNs Over Tunnels
04
3.5 Applicable EMC / EMI and Safety Standard

and Protocol
The design of the CiTRANS R860's EMC (Electromagnetic Compatibility) / EMI

(ElectroMagnetic Interference) complies with the standards and protocols listed in
Table 3-4.
Table 3-4 Applicable EMC / EMI Standards and Protocols of the CiTRANS R860
Standard / Protocol
Title
Number
Electromagnetic compatibility and Radio spectrum Matters (ERM);
ETSI EN 300 386 Telecommunication network equipment; Electromagnetic
Compatibility (EMC) requirements
Information technology equipment - Radio Disturbance characteristics

EN 55022
- Limits and methods of measurement
Information technology equipment - Immunity characteristics - Limits
EN55024
and methods of measurement
Electromagnetic compatibility (EMC) - Part 4-2: Electrostatic
EN 61000-4-2
discharge immunity test
Electromagnetic compatibility (EMC) - Part 4-3: Testing and

EN 61000-4-3 measurement techniques-Radiated, radio-frequency, electromagnetic
field immunity test

EN 61000-4-4
measurement techniques-Electrical fast transient/burst immunity test

EN 61000-4-5
measurement techniques-Surge immunity test

EN 61000-4-6 measurement techniques-Immunity to conducted disturbances,
induced by radio-frequency fields

CISPR 22
3-24 Version: B
3 Feature
Table 3-4 Applicable EMC / EMI Standards and Protocols of the (Continued)
Standard / Protocol
Title
Number
CISPR 24
Resistibility of telecommunication equipment installed in a
ITU-T K.20
telecommunications centre to overvoltages and overcurrents
Resistibility of Telecommunication Equipment installed in Customer

ITU-T K.21
Premises to Overvoltages and Overcurrents
ITU-T K.43 Immunity requirements for telecommunication equipment
Resistibility of telecommunication equipment to overvoltages and

ITU-T K.44
overcurrents
The applicable safety standards of the CiTRANS R860 are shown in Table 3-5.
Table 3-5 Applicable Safety Standards

Safety of laser products – Part 1 : Equipment classification and
EN 60825-1
requirements
Safety of laser products – Part 2 : Safety of optical fibre

EN 60825-2
communication
Information technology equipment –Safety – Part 1:General
EN 60950-1
Requirements
Safety of laser products – Part 1 : Equipment classification and

IEC 60825-1
requirements
Safety of laser products – Part 2 : Safety of optical fibre

IEC 60825-2
communication
Safety of Information technology equipment including Electrical
IEC 60950
Business Equipment
Information Technology Equipment – Safety – Part 1: General

UL 60950-1
Requirements
Version: B 3-25
4 Dynamic Routing
The CiTRANS R860 supports a wide range of routing protocols to meet different
network requirements. The following describes the routing protocols that the
CiTRANS R860 supports.
Overview
RIP
OSPF Protocol
IS-IS Protocol
BGPv4
IPv6 Dynamic Routing Protocol
RSVP
LDP
Version: B 4-1
4.1 Overview
The CiTRANS R860 supports the following routing protocols and functions:
u IPv4 routing protocols: RIP, OSPF, IS-IS, and BGPv4.
u IPv6 routing protocols: RIP Next Generation (RIPng), OSPFv3, IS-ISv6, and
MP-BGP.
u Routing signaling and control protocols: Resource Reservation Protocol (RSVP)

and Label Distribution Protocol (LDP).
u A large number of routing entries to effectively support MAN operations.
u A complete set of routing policies for determining the optimal route.
u BGP indirect next hop and group-based packaging.
4.2 RIP
Basic Concept
The Routing Information Protocol (RIP) is used to transmit routing information. Each
router broadcasts its routing table at 30-second intervals to maintain location
information about neighboring routers. Also, each router calculates the routing table
based on received routing information.
RIP has the following features:
u RIP is a distance-vector routing protocol. In RIP, routing information is

exchanged as UDP packets using port 520.
u RIP is applicable to small-scale networks, such as campus networks and

regional networks with a simple structure.
u The distance to the destination is measured based on the number of hops to

the destination. In RIP, there is no hop from a router to a directly connected
network. The number of hop from a router to the other network through a
directly connected router is 1, and so on and so forth. According to RIP, the
number of hops is an integer ranging from 0 to 15 to limit the route convergence
time. If the number of hops exceeds 15, the destination network or host is
unreachable.
4-2 Version: B
4 Dynamic Routing
u RIP supports horizontal split and poison reverse to avoid routing loops.
References
Refer to standards in Table 4-1 for more information about RIP.
Table 4-1 Applicable Standards of RIP

RFC 2082 RIP-2 MD5 Authentication
RFC 2453 RIP Version 2
4.3 OSPF Protocol

Basic Concept
OSPF is an IGP defined by the IETF (Internet Engineering Task Force). It is one of
the most commonly used routing protocols.
There are two OSPF versions: OSPFv1 (RFC 1131) and OSPFv2 (RFC 2328).
OSPF uses the link state route selection technology and the SPF algorithm. Routers
exchange information about direct links and links to other routers. Each OSPF
router maintains the same database that describes the topology of the AS. Each
OSPF router constructs an SPT to calculate the routing table based on the
database.
When the topology changes, OSPF quickly recalculates routes and only a small
amount of routing protocol traffic is generated. Identity authentication is required for
exchanging route selection protocols.
OSPF consists of three subprotocols: Hello protocol, switching protocol, and

diffusion protocol.
u The Hello protocol checks whether links are available and specifies the DR and
BDR.
u The switching protocol specifies the master and slave routers and enables the
routers to exchange the information in their respective routing database.
u The diffusion protocol synchronizes and maintains the routing databases of

routers.
Version: B 4-3
OSPF has the following features:
u Supports variable-length subnet masks.
u Supports area division and applies to large-scale networks.
u Supports load balancing among equivalent routes.
u Supports verification to avoid attacks to routers and routing protocols.
u Supports fast convergence.
u Has no restrictions on the number of hops.
u Supports variable-length subnet masks.
u Applies to the large-scale and complex Internet.
u Overcomes the drawbacks of RIP and other distance-vector routing protocols.
u Triggers route convergence in a very short time to avoid routing loops and
therefore applies to mesh networks and LANs that are connected using
bridges.
u Implements interconnection between devices of different manufacturers as an

open standard.
Route Calculation
The core of OSPF is the SPF (Shortest Path First) algorithm. OSPF generates the
minimum spanning tree using the Dijkstra algorithm.
In OSPF, routes are calculated using the SPF algorithm as follows:
1. Each router advertises its LSA that describes its own link state information.
2. Each router summarizes the received LSAs and generate an LSDB.
3. Each router calculates an SPT based on the costs of links, with itself as the root
node.
4. Each router obtains the route entries based on the minimum spanning tree and
generates a routing table.
Packet Structure
Figure 4-1 shows the structure of OSPF packets.
4-4 Version: B
4 Dynamic Routing
Figure 4-1 Structure of an OSPF Packet
There are five types of OSPF packets.
u Hello packet
4 A Hello packet is an OSPF packet numbered 1.
4 An OSPF router periodically sends Hello packets to discover and maintain

neighbor relationships and elects the DR (Designated Router) and BDR
(Backup Designated Router).
u LSDB description packet
4 An LSDB description packet is an OSPF packet numbered 2.
4 This type of packet is generated when routers exchange information in

their LSDBs. This type of packet is used to:
¡ Determine the master/slave relationships of routers when they

exchange LSDB information.
¡ Determine the initial sequence number when routers exchange LSDB

information.
¡ Exchange headers of all LSAs.
u Link state request packet
4 A link state request packet is an OSPF packet numbered 3.
Version: B 4-5
4 This type of packet is used by a router to request details about LSAs that it
does not have or about outdated LSAs during the process of exchanging
LSDB description packets.
u Link state update packet
4 A link state update packet (LSA-Update) is an OSPF packet numbered 4.
4 This type of packet is used to flood LSAs and respond to received link
state updates. If a flooded LSA is not acknowledged, the link state update
packet is retransmitted at 5-second intervals by default.
u Link state acknowledgment packet
4 A link state acknowledgment packet (LSA-Acknowledgment) is an OSPF

packet numbered 5.
4 This type of packet is used to acknowledge received LSAs. This type of

packet is transmitted in multicast mode. If the router that acknowledges the
received LSAs is a DR or BDR, the acknowledgment packet is sent to the
multicast address 224.0.0.5. If the router that acknowledges the received
LSAs is not the DR or BDR, the acknowledgment packet is sent to the
multicast address 224.0.0.6.
Typical Application
Figure 4-2 shows a typical AS established over OSPF. The AS is divided into three
areas, which are respectively numbered 0, 1, and 2. The router in an area maintains
an LSDB of states of links between routers within this area. The router at the border
of two areas maintains the LSDBs of both areas and sends LSA-Update messages
between the two areas. The router at the border of the AS is responsible for
exchanging routing information between the AS and external systems.
4-6 Version: B
4 Dynamic Routing
Figure 4-2 Typical Application of OSPF
References
Refer to Table 4-2 for more information about OSPF.
Table 4-2 Applicable Standards of OSPF

RFC 2328 OSPF Version 2
RFC 3623 Graceful OSPF Restart
OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP
RFC 4577
Virtual Private Networks (VPNs)
RFC 4915 Multi-Topology (MT) Routing in OSPF
4.4 IS-IS Protocol

Basic Concept
According to the ISO, a router is defined as an intermediate system (IS). ISs

communicate with each other over the IS-IS routing protocol.
Version: B 4-7
IS-IS uses a two-layer structure within routing domains to support large-scale

routing networks. A large routing domain is divided into multiple areas. Routes
within an area are managed by a level-1 router, and routes between areas are
managed by a level-2 router.
u Level-1 router
A level-1 router is responsible for routing within an area. It establishes neighbor

relationships with other level-1 routers or level-1-2 routers in the same area. In
addition, it maintains a level-1 LSDB that contains all routes in the area. The
routes are calculated using the SPF algorithm. Packets bound for devices
outside this area are forwarded by the level-1 router to the nearest level-2
router.
u Level-2 router
A level-2 router is responsible for routing between areas. It establishes

neighbor relationships with other level-2 routers or level-1-2 routers in other
areas. In addition, it maintains a level-2 LSDB that contains routes between
areas. The routes are calculated using the SPF algorithm. All level-2 routers
form the backbone in the routing domain. The level-2 routers in a routing
domain must be contiguous to ensure the continuity of the backbone.
u Level-1-2 router
A level-1-2 router is both a level-1 router and a level-2 router. Each area has at
least one level-1-2 router. An area connects to the backbone through the level-
1-2 router. A level-1-2 router maintains two LSDBs: a level-1 LSDB for intra-
area routing and a level-2 LSDB for inter-area routing.
A router is uniquely identified by a system ID. Routers in the same area have the
same area ID. If a router belongs to multiple areas, it may have different area IDs
but the same system ID.
Packet Structure
IS-IS packets are encapsulated into frames at the data link layer. There are three
types of IS-IS packets.
u Hello packet
4-8 Version: B
4 Dynamic Routing
Hello packets are used for establishing and maintaining neighbor relationships.
On a broadcast LAN, level-1 routers send level-1 LAN Hello packets, and level-
2 routers send level-2 LAN Hello packets. On a non-broadcast network, routers
send P2P Hello packets.
u Link state packet (LSP)
LSPs are used for exchanging link state information. There are two types of
LSPs: level-1 LSP and level-2 LSP. Level-2 LSPs are sent by level-2 routers
and level-1 LSPs are sent by level-1 routers. A level-1-2 router can send both
level-1 and level-2 LSPs.
u Sequence number packet (SNP)
SNPs are used for acknowledging the LSP latest received by neighbors. There
are two types of SNPs: complete SNPs (CSNPs) and partial SNPs (PSNPs).
SNPs can be further classified into level-1 CSNPs, level-2 CSNPs, level-1
PSNPs, and level-2 PSNPs.
4 A PSNP contains only the sequence numbers of the recently received one
or more LSPs. Multiple LSPs can be acknowledged through one PSNP.
When a router finds that its LSDB is not synchronized with that of its
neighbor, it can send a PSNP to request new LSPs from its neighbor.
4 A CSNP contains the summary information about all LSPs in an LSDB and
therefore can be sent to synchronize LSDBs between neighboring routers.
On a broadcast network, the DIS periodically sends CSNPs at 10-second
intervals by default. On a P2P channel, a CSNP is sent only when the two
points establish a neighbor relationship for the first time.
Version: B 4-9
Typical Application
Figure 4-3 Typical Application of IS-IS
Figure 4-3shows an AS set up over IS-IS. The AS is divided into four parts. NEs
within an AS and in different ASs communicate with each other over dynamic
routing protocols. Routes within an area are managed by a level-1 router, and routes
between areas are managed by a level-2 router. A router is uniquely identified by a
system ID.
References
Refer to Table 4-3 for more information about IS-IS.
Table 4-3 Applicable Standards of IS-IS

RFC 1195 Use of OSI IS-IS for Routing in TCP/IP and Dual Environments
RFC 2763 Dynamic Hostname Exchange Mechanism for IS-IS
RFC 2966 Domain-wide Prefix Distribution with Two-Level IS-IS

Intermediate System to Intermediate System (IS-IS) Transient
RFC 3277
Blackhole Avoidance
Three-Way Handshake forIntermediate System to Intermediate System
RFC 3373
(IS-IS)Point-to-Point Adjacencies
4-10 Version: B
4 Dynamic Routing
Table 4-3 Applicable Standards of IS-IS (Continued)

Intermediate System to Intermediate System (IS-IS) Cryptographic
RFC 3567
Authentication
Restart Signaling for Intermediate System to Intermediate System (IS-
RFC 3847
IS)
4.5 BGPv4
Basic Concept
BGP is an exterior gateway protocol. Different from IGPs such as OSPF and RIP,
which focus on discovering and calculating routes, BGP focuses on controlling route
transmission and optimal route selection.
The earliest released three BGP versions are BGPv1 (RFC1105), BGPv2
(RFC1163), and BGPv3 (RFC1267). The currently used version is BGPv4
(RFC4271).
Note:
BGP mentioned in the following refers to BGPv4 unless otherwise

specified.
The ISO defines BGP to maintain the individual interests of ISPs. BGP is
responsible for route transmission among ISPs.
Only qualified personnel that are familiar with the network structure can configure
BGP; otherwise, unexpected consequences may be resulted.
BGP has the following features:
u BGP is a routing protocol applied among ASs.
u BGP transmits routing information among ASs.
u BGP is a distance-vector routing protocol and avoids routing loops in design.
u BGP runs over TCP.
u BGP supports classless inter-domain routing.
Version: B 4-11
u BGP provides abundant route filtering and routing policies.
u BGP delivers powerful routing capacity.
Protocol Packets
Four types of BGP packets are used.
u Open packet: Open packets are used for establishing initial BGP connections,
including the hold time and router ID.
u Keepalive packet: Keepalive packets are periodically exchanged between BGP

peers to keep sessions valid. The default validity period of a session is 60
seconds.
u Update packet: BGP peers exchange routing information about the network
layer by sending Update packets. Update packets carry reachable and
unreachable routes, as well as routing attributes.
u Notification packet: BGP peers notify error information by sending Notification

packets. A Notification packet is sent when a connection fails and the BGP
connection is ended.
Usage Guidelines
The usage guidelines are described as follows:
u When there are multiple routes, the BGP speaker chooses the optimal route.
u The BGP speaker advertises only its currently used route to its peers.
u The BGP speaker does not advertises the routes obtained from IBGPs to its
IBGP peers to avoid intra-domain routes.
u The BGP speaker determines whether to advertise the routes obtained from
IBGPs to its EBGP peers based on the synchronization conditions between
IGP and BGP.
u After establishing a connection with a new peer, the BGP speaker advertises all
its BGP routes to the peer.
4-12 Version: B
4 Dynamic Routing
BGP ECMP
The CiTRANS R860 supports BGP ECMP (Equal-Cost Multi-Path), the ECMP
being used for load balancing. When multiple links in the network can reach the
same destination address, the system will work out the corresponding multiple route
entries, and add them in the routing table. When the fault of a neighbor node leads
to the failure of the path, the BGP ECMP can be used to switch the corresponding
service traffic to other paths.
BGP Next-hop Separation
The CiTRANS R860 supports the BGP next-hop separation. This means separating
the VPN routing table according to the remote next hop of the VPN route. The
divides the original VPN routing table into two parts: the remote next hop and the
connected route of the remote next hop. This reduces the route iteration caused by
the public network faults, so as to lower the route convergence time.
Typical Application
As shown in Figure 4-4, the BGP is an IBGP (Internal BGP) when running within an
AS, and is an EBGP (External BGP) when running between ASs.
Version: B 4-13
Figure 4-4 Typical Application of BGP
Reference Standard
Refer to Table 4-4 for more information about BGPv4.
Table 4-4 Applicable Standards of BGP

RFC 1997 BGP Communities Attribute
RFC 1998 An Application of the BGP Community Attribute in Multi-home Routing
RFC 2439 BGP Route Flap Damping
RFC 2858 Multiprotocol Extensions for BGP-4
RFC 2918 Route Refresh Capability for BGP-4
RFC 3107 Carrying Label Information in BGP-4
RFC 3392 Capabilities Advertisement with BGP-4
RFC 4271 A Border Gateway Protocol 4 (BGP-4)
RFC 4456 BGP Route Reflection:An Alternative to Full Mesh Internal BGP (IBGP)
4-14 Version: B
4 Dynamic Routing
4.6 IPv6 Dynamic Routing Protocol

RIPng
RIP is a distance-vector IGP proposed by the IETF. RIP features simple

configuration, easy management, and easy operation, and is widely used on small-
and medium-scale IPv4 networks.
The IETF customizes RIP specific for IPv6 networks, that is, RIPng, with the
advantages of RIP inherited. RIPng provides routing functions on IPv6 networks
and is an important routing technology for IPv6 networks.
RIPng resembles RIP in the working mechanism. Compared with RIP, RIPng has
the following differences:
u Packet
The length, format, and transmission method of RIPng packets are different
from those of RIPv2.
u Security authentication
RIPng does not provide authentication. The validity of RIPng packets is

ensured by using the security mechanism provided by IPv6. Therefore, the
authentication RTE in RIPv2 packets is revoked in RIPng packets.
u Compatibility with network-layer protocols
RIP can run on both IP and IPX networks whereas RIPng can run only on IPv6
networks.
OSPFv3
The IETF customizes OSPFv2 specific for IPv6 networks, that is, OSPFv3, with the
advantages of OSPFv2 inherited. OSPFv3 provides routing functions on IPv6
networks and is a mainstream routing technology for IPv6 networks.
OSPFv3 is improved so that it can run on IPv6 networks and guide IPv6 packet
forwarding. In this way, OSPFv3 can run independent of network-layer protocols. It
can be compatible with various protocols after being customized and this enhances
the scalability of OSPFv3.
Compared with OSPFv2, OSPFv3 has the following differences:
Version: B 4-15
u Runs based on links.
u Uses link-local addresses.
u Supports multi-instance multiplexing for links.
u Identifies neighbors uniquely with router IDs.
u Uses a different authentication mode.
u Supports stub areas.
u Uses different packets.
u Has the "Option" field modified.
u Uses different LSAs.
IS-IS for IPv6
IS-IS provides strong scalability. It can discover and generate IPv6 routes to support
IPv6 network-layer protocols. The IS-IS protocol that supports IPv6 is also called the
IS-ISv6 dynamic routing protocol.
IS-ISv6 can process IPv6 routing information. Compared with IS-IS, IS-ISv6 has the
following differences:
u Code-length-value (CLV)
4 An IPv6 reachability CLV is added.
4 An IPv6 interface address CLV is added.
4 A protocol support CLV is added.
u Extended Hello packets for supporting IPv6 routing and establishing IPv6
adjacencies
4 An 8-bit NLPID is added to the protocol support CLV. Its value is 0x81,
indicating that the current router supports IS-ISv6.
4 An interface IPv6 address CLV for enabling IS-ISv6 is added to Hello

packets. Setting the "Interface Address" field enables the IPv6 link-local
address of the IS-ISv6 interface.
4-16 Version: B
4 Dynamic Routing
MP-BGP
Traditional BGP manages only IPv4 routing information and does not support
applications that use other network-layer protocols such as IPv6 and multicast
protocols. It has restrictions when transmitting routing information across ASs.
The IETF extends BGP to Multiprotocol Extensions for BGPv4 (MP-BGP) that
supports more network-layer protocols. MP-BGP is defined in RFC 2858.
MP-BGP is forward compatible. That is, routers that support MP-BGP can interwork
with routers that do not support MP-BGP.
References
Refer to Table 4-5 for more information about IPV6.
Table 4-5 Applicable Standards of IPv6 Dynamic Routing Protocols
Standard No. Description
RFC 2080 RIPng for IPv6
RFC 2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
RFC 5308 Routing IPv6 with IS-IS
RFC 5340 Routing IPv6 with IS-IS
4.7 RSVP
Basic Concept
RSVP is a signaling protocol that runs at the network layer. It allows any router to
establish a reserved-bandwidth path. It ensures the QoS (Quality of Service) for
data flows on a network. Dynamic tunnels are established over RSVP.
RSVP has the following features:
u Supports resource reservation. Resource requests are transmitted as RSVP

signaling between network nodes. After a network node receives a resource
request, the network node needs to reserve resources. The network node
checks the available resources and determines whether to accept the request
based on actual conditions. It can reject the request when resources are
insufficient.
Version: B 4-17
u Supports priority setting. Different priorities can be set for requests. When
network resources are insufficient, resource requests with higher priorities can
preempt the resources reserved for resource requests with lower priorities.
References
Refer to standards in Table 4-6 for more information about RSVP.
Table 4-6 Applicable Standards of RSVP

RFC 2205 Resource ReSerVation Protocol (RSVP)
RFC 2209 Resource ReSerVation Protocol (RSVP)
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels

Encoding Long Options in the Dynamic Host Configuration Protocol
RFC 3396
(DHCPv4)
RFC 4090 Fast Reroute Extensions to RSVP-TE for LSP Tunnels
4.8 LDP
Basic Concept
As a control protocol in MPLS, the LDP classifies FECs, distributes labels, transmits
label distribution results, and sets up and maintains LSPs. Dynamic tunnels and
VCs are set up over LDP.
LDP defines the messages required during label distribution and related processing
processes. It is mainly used by LSRs to negotiate label distribution and set up LSPs.
LSRs combine the inbound label, next-hop node, and outbound label that map a
specific FEC to form an LSP that crosses the entire MPLS domain.
References
Refer to standards in Table 4-7 for more information about LDP.
Table 4-7 Applicable Standards of LDP

RFC 3035 MPLS using LDP and ATM VC Switching
RFC 3036 LDP Specification
4-18 Version: B
5 Product Architecture
The following introduces the product architecture of the CiTRANS R860, and
includes these contents.
Logical Structure
Hardware Structure
Software Architecture
Version: B 5-1
5.1 Logical Structure
The CiTRANS R860 consists of the service processing module, management

interface module, clock and time control module, routing control module, heat
dissipation module, and power module. Figure 5-1 shows the logical structure of the
CiTRANS R860.
Figure 5-1 Functional Modules of the CiTRANS R860
Service Processing Module
The service processing module contains the routing forwarding core and interface
cards.
Different interface cards can be used to connect a variety of services.
u Ethernet services: 10GE, GE, FE
u CES services: E1, STM-1
The access signals are processed by the routing forwarding chip, with a switching
capacity of 320 Gbit/s.
5-2 Version: B
Management Interface Module
The management interface module provides various types of management

interfaces and auxiliary interfaces, including Ethernet interfaces, network
management interfaces, commissioning interfaces, and alarm interfaces.
Routing Control Module
The routing control module is responsible for the communication among cards by
using the internal system bus. The routing control module supports cascading of
cards and supports varied routing protocols. In addition, it provides functions
including overhead information transmission, card information management, and
card self-booting.
Clock and Time Control Module
The clock and time control module supports physical-layer clock synchronization
and time synchronization complying with IEEE 1588 or 802.1as. The details are as
follows:
u Supports processing and transmitting synchronization clock status information.

The module receives external input clock sources through the external clock
interface. After selecting the optimal clock source and synchronizing the phase
lock for the optimal clock source, the module provides the system clock to other
modules. It also provides clock signal output.
u Supports time synchronization. The module receives time signals through the
external time interface. It provides synchronous time to system modules and
time signal output.
u Supports extracting and processing synchronization signals and

synchronization clock status information from the customer interface and line
interface, meeting synchronization requirements of carrier-class network
equipment.
Heat Dissipation Module
The heat dissipation module cools and dissipates heat for the system. It consists of
fan units and the intelligent fan control software. The functions are described as
follows:
Version: B 5-3
u It detects the temperature in subracks and generates alarms.
u It changes the fan speed to full speed, high speed, or low speed, and stops
fans.
u The fan speed can be manually set.
u The fan unit has three fans. Each fan works independently and serves as the
hot standby for each other. When a fan stops due to a fault, other fans increase
their speed to ensure that the CiTRANS R860 runs properly.
Power Module
The power module supplies power to other modules of the system.
u It supports two -48 V power inputs in active / standby mode.
u It supports lightning protection and transient power failure protection to prevent

the system from being damaged by lightning.
5.2 Hardware Structure
The CiTRANS R860 consists of a cabinet, a power distribution panel (PDP),

subracks, and cards.
5.2.1 Cabinet
The following describes the appearance and equipment layout of the cabinet.
5.2.1.1 Appearance
Figure 5-2 shows the appearance of a 21-inch cabinet.
5-4 Version: B
Figure 5-2 Appearance of the 21-inch Cabinet
5.2.1.2 Equipment Layout
Figure 5-3 shows the layout of the hardware components of the CiTRANS R860.
Version: B 5-5
Figure 5-3 Equipment Layout (Unit: mm)
Cabinets in different dimensions can house different numbers of subracks. Keep the
following rules when working out a layout plan:
u Reserve a space of 125 mm between subracks and a space of 200 mm

between a subrack and the cabinet bottom to ensure normal heat dissipation.
u Reserve space in the cabinet for expansion.
u In full configuration, cabinets in different dimensions have different subrack

quantities. If a cabinet is not fully configured, install subracks from the bottom
up.
Table 5-1 lists the subrack quantities for cabinets with different dimensions.
5-6 Version: B
Table 5-1 Subrack Quantities for Cabinets
Cabinet Dimension (H x W x D, mm) Subrack Quantity
2000 × 600 × 306 1

2200 × 600 × 306 1
2600 × 600 × 306 1 to 2
5.2.2 PDP
The following describes the appearance and functions of the PDP.
5.2.2.1 Appearance
The PDP is located on the top of the cabinet and its appearance is shown in
Figure 5-4.
Figure 5-4 Appearance of the PDP for the 21-inch Cabinet
Version: B 5-7
5.2.2.2 Function
The PDP connects and distributes external power supplies and processes alarm
signals. It connects external power supplies to the system and distributes power to
other components. It also receives alarm signals from other components in the
cabinet and displays and outputs the alarm signals.
The CiTRANS R860 uses a 2x3 -48 V / 40 A PDP. The PDP provides the following
functions:
u The PDP inducts two channels of DC -48 V power (active and standby) from
the external (e.g. the power cabinet) and provides six branch power rails (active
and standby) for the three subracks.
u Performs the lightning protection function, which can effectively withstands

surge currents of common mode 2 kV (1.2 / 50 us to 8 / 20 us combination wave)
and differential mode 1 kV (1.2 / 50 us to 8 / 20 us combination wave) on the
power line.
u Performs the alarm input and output function: The PDP collects the alarm
information from corresponding equipment in the cabinet, provides audible and
visual alarm display of the alarm signals, and outputs the alarm signals to the
higher-level equipment (such as the head of row cabinet).
u Supports lightning protection, under-voltage protection, transient interruption

protection.
5.2.3 Fiber Passage Unit
The fiber passage unit of CiTRANS R860 is installed above the subrack for
arranging the power cable, the signal wire and the optical fibers in the upper part of
the subrack.
The fiber passage unit is composed of the wire binding rail and the fiber guide slot,
as shown in Figure 5-5. The wire binding rail is used for arranging the power cable
and signal wire of the subrack and the fiber guide slot is used for arranging the
optical fibers in the upper part of the subrack.
5-8 Version: B
(1) A wire binding rail (2) Fiber passage unit
Figure 5-5 The Fiber Guide Unit
5.2.4 Subrack
The following describes the functions and slot layout of subracks.
5.2.4.1 Function
Subracks are used to contain cards. Cards exchange signals with the backplane
through subracks.
5.2.4.2 Slot Layout
The cabinet of the CiTRANS R860 has 32 slots for cards, half in the upper subrack
and half in the lower subrack. Figure 5-6 shows the slot layout.
Version: B 5-9
Figure 5-6 Layout of the CiTRANS R860’s Slots
5.2.5 Overview of Card
The following describes the appearance, classification, and locations-in-the-system

of cards.
5.2.5.1 Card Appearance
The CiTRANS R860 cards are classified into two types according to their
appearance and dimensions.
Table 5-2 shows the appearance and dimensions of the cards.
5-10 Version: B
Table 5-2 Appearance and Dimensions of the Cards
Item Card
Card appearance
RCUO1, SCUR1, XSR1, ESR1, AIFJ1, AIFJ2, S1J2, S1J4, E1J2,

Card name
XSR2, GSR1, XGR1 ESJ1, ESJ2
Dimensions (H x D x
370 × 210 × 30 370 × 150 × 30
W, mm)
5.2.5.2 Card Classification
Table 5-3 lists the card categories of the CiTRANS R860.
Version: B 5-11
Table 5-3 Card Categories
Category Card Function
The XSR1, XSR2, GSR1, XGR1, Connects and processes E1,

Service card ESR1, ESJ1, ESJ2, S1J4, S1J2, STM-1, FE, GE, and 10GE
E1J2 cards signals.
Switches services on the client

Switching and clock side and line side.
The SCUR1 Card
processing unit Provides standard system lock or
time.
Monitoring signal Communicates with the
The RCUO1 card
processing unit OTNM2000 to manage NEs.
Power and auxiliary Connects external power

The AIFJ1, AIFJ2 cards
terminal board supplies to the system.
5.2.5.3 Card Position in System
Figure 5-7 shows the positions of cards of the CiTRANS R860. For more information,
see the descriptions of each card.
5-12 Version: B
Figure 5-7 Locations of Common Cards in the System
5.2.6 The RCUO1 Card
The following descries the number and functions of the RCUO1 card.
5.2.6.1 Card Number
2.200.854
5.2.6.2 Function
u Connects the -48 V power from the AIFJ1 / AIFJ2 card and converts the -48 V
power into the 3.3 V or 1.5 V power.
Version: B 5-13
u Manages NEs, interconnects NEs over embedded communication channels,

and supports 1+1 protection.
u Provides GE channels for transmitting SCC and MCC information to the active
and standby SCUR1 cards respectively, and shows the connection status
through indicator LEDs on the panel.
u Supports fan alarm detection, intelligent fans, and fan temperature and power
reporting.
5.2.7 The SCUR1 Card
The following describes the number and functions of the SCUR1 card.
5.2.7.1 Card Number
u The SCUR1 card number: 2.200.741.
u The SCUR2 card number: 2.200.950.
5.2.7.2 Function
u The SCUR1 card supports a switching capacity of 320 Gbit/s.
u The SCUR2 card supports a switching capacity of 360 Gbit/s.
u Works with the RCUO1 card to implement tunnel 1:1 protection, LAG protection,
IP FRR, VPN FRR, MPLS TE FRR, LDP FRR, and VRRP protections.
u Supports OAM at four layers: link layer, VP layer, VC layer, and Ethernet
service layer.
u Uses the 1+1 protection mode and supports the SCUR1 / SCUR2 card's
automatic active / standby switchover or switchover performed by the network
management system.
u Supports detecting and reporting temperature of sensitive areas of cards.
u Supports the automatic, holdover, and free running modes.
u Supports overvoltage and undervoltage protection and power alarm monitoring.
u Supports cold start of cards.
5-14 Version: B
u Supports remote upgrade of FPGA and BMU.
u Supports hot-insertion of cards.
u Provides the 25.00 MHz system clock (a single TTL) and 8 kHz frame timing
clock for cards.
u Supports synchronization for Ethernet interfaces to implement system-level

tributary timing with the help of the cards including FE, E1, cSTM-1 types.
u Supports mutual frequency synchronization between the active and standby

SCUR1 / SCUR2 card and the hitless switchover.
u Supports the One-step, OC, BC, and BMC functions defined in IEEE 1588v2,
and synchronization of time from the XGE or GE interface.
5.2.8 The XSR1 / XSR2 Card
The following describes the number and functions of the XSR1 / XSR2 card.
5.2.8.1 Card Number
The XSR1 card: 2.200.844.
The XSR2 card: 2.200.829.
5.2.8.2 Function
u The XSR1 card provides two 10GE optical interfaces.
u The XSR2 card provides four 10GE optical interfaces.
u Supports line clock extraction.
u Provides OAM for cards.
u Supports system clock synchronization.
u Supports IEEE 1588v2.
u Supports service classification based on PW, port, VLAN, IP address, MAC

address, or 802.1P priority.
u Supports imposition, swapping and disposition of VPAN and MPLS tags.
Version: B 5-15
u Supports static unicast and multicast.
u Supports MPLS VPWS and VPLS.
u Supports collecting performance such as the card power and alarms.
u Manages XFP optical modules.
u Supports hot-insertion of cards and optical modules.
5.2.9 The XGR1 Card
The following descries the number and functions of the XGR1 card.
5.2.9.1 Card Number
2.200.766
5.2.9.2 Function
u Provides two 10GE optical interfaces and eight GE optical interfaces.
u Provides OAM for cards.
u Supports IEEE 1588v2.
u Supports service classification based on PW, port, VLAN, IP address, MAC

address, or 802.1P priority.
u Supports imposition, swapping and disposition of VPAN and MPLS tags.
u Supports static unicast and multicast.
u Supports MPLS VPWS and VPLS.
u Supports collecting performance indicators such as the card power and alarms.
u Manages XFP optical modules.
5-16 Version: B
5.2.10 The GSR1 Card
The following describes the number and functions of the GSR1 card.
5.2.10.1 Card Number
2.200.843
5.2.10.2 Function
u Provides eight GE optical interfaces.
u Supports active / standby protection for services.
5.2.11 The ESJ1 / ESJ2 / ESR1 Card
The following describes the number and functions of the ESJ1 / ESJ2 / ESR1 card.
The ESJ1 Card
2.115.322
The ESJ2 Card
2.115.355
The ESR1 Card
2.200.846
Version: B 5-17
5.2.11.2 Function
The ESJ1 Card
u Provides 12 FE electrical interfaces.
u Supports VLAN and QinQ tags.
u Port 11 and Port 12 support IEEE 1588.
u Supports traffic management based on the MAC address / VLAN port.
u Supports overvoltage and undervoltage protection and power monitoring.
u Supports active/standby switchover of the clock.
u Supports fault management. Measures and analyzes the alarms generated in

cards and by Ethernet ports, and reports the analysis results.
u Supports reporting the performance statistics of a single card.
The ESJ2 Card
u Provides 12 FE optical interfaces.
u Port 1 to Port 4 support IEEE 1588.
u Supports traffic management based on the MAC address, VLAN, or port.

The ESR1 Card
u Provides 12 FE optical interfaces.
u Supports traffic management based on the MAC address, VLAN, or port.
5-18 Version: B

5.2.12 The E1J2 Card
The following descries the number and functions of the E1J2 card.
u 2.200.037 (75Ω interface);
u 2.200.240 (120Ω interface).
5.2.12.2 Function
u Supports circuit emulation to encapsulate 1 to 32 E1 signals into Ethernet

signals with the GE rate.
u Complies with ITU-T Y.1413, IETF PW3, and MEF 8.
u Transmits data with low delay, meeting the real-time service requirements.
u Supports two emulation modes: structured and non-structured.
u Supports two clock recovery modes: differential and adaptive.
u Supports over-voltage and under-voltage protection and power supply

monitoring.
u Supports online remote upgrade of FPGA and BCT.
u Supports hot-insertion.
Version: B 5-19
5.2.13 The S1J2 / S1J4 Card
The following describes the number and functions of the S1J2 / S1J4 card.
The S1J4 card: 2.200.595.
The S1J2 card: 2.170.586.
5.2.13.2 Function
u Connects and transparently transmits SDH services over packet switched

networks.
u The S1J2 card provides two STM-1 optical interfaces and emulates a maximum
of 126 E1 service circuits.
u The S1J4 card provides eight STM-1 optical interfaces and emulates a
maximum of 504 E1 service circuits.
u Supports loopback testing, including line loopback testing and equipment

loopback testing.
u Supports online remote upgrade of FPGA and BMU.
5.2.14 The AIFJ1 / AIFJ2 Card
The following describes the number and functions of the AIFJ1 / AIFJ2 card.
The AIFJ1 card: 3.699.318.
The AIFJ2 card: 3.699.319.
5.2.14.2 Function
u Inputs the -48V power supply, the current of which is less than 40 A.
5-20 Version: B
u Provides standby 10 A / 5 V power supply.
u Provides the clock interface CKIO, time interface TOD, alarm connector ALM,
and monitoring connector MON, and connects Ethernet signals.
u Provides power and auxiliary card 1 (AIFJ1) and power and auxiliary card 2
(AIFJ2) in the active / standby mode. The two cards are isolated from each
other.
5.3 Software Architecture
The software of the CiTRANS R860 includes communication protocols and interface,
BMU, NMU, and network management software.
5.3.1 Overview
The CiTRANS R860 uses a modularized software architecture. Its software consists
of the BMU, EMU, and OTNM2000, which respectively run on the functional cards,
the RCUO1 card, and network management host. The components work with each
other to perform configuration, management, and monitoring for the . The system
software architecture is shown in Figure 5-8.
Version: B 5-21
Figure 5-8 System Software Architecture
5.3.2 Communication Protocol and Interface
The communication protocols and interfaces of the software modules of the are
described as follows:
u The OTNM2000 provides the Q and CORBA interfaces.
4 The OTNM2000 communicates with the EMU through the Q interface. The
Q interface runs the FiberHome proprietary communication protocol.
4 The OTNM2000 communicates with the upper-level management system

through the CORBA interface.
u NEs (EMUs) communicate with each other over the ESC, which is a physical
channel. The compliant communication protocol is IP.
u The EMU communicates with the BMU over the LAN. The compliant
communication protocol is IP.
5-22 Version: B
5.3.3 BMU
The BMU is embedded into each card to exert direct control on all functional circuits.
The BMU can be used by the RCUO1 card to manage cards. The functions of the
BMU are described as follows:
u Collects and processes alarms, performance data, status information of the

local card in a timely manner.
u Applies to the RCUO1 card for configuration when the card is powered on, and
initializes the card based on the configuration so that the card can work as
expected after power-on.
u Receives control commands issued by the RCUO1 card, performs predefined

operations, and processes queries of the RCUO1 card.
5.3.4 NMU
The NMU runs in an embedded multitask OS. The NMU manages all cards of NEs
through a unified Ethernet bus based on the manager / agent model.
The functions of the modules of the NMU are described as follows:
u Management / agent application functional module
The management / agent application functional module contains the manager (M)
and agent (A). At the NE layer, the management card (RCUO1) of an NE can
be designated as the agent (A) or manager / agent (M/A). The M/A is an agent
with the management function.
4 M/A: serves as an agent of objects of the local NE and manages objects of

managed NEs. The management function involves maintaining remote
objects.
4 A: collects and processes the performance and alarm / fault and status
data of each BMU of the local NE. Also, it receives and responds to
commands and operations related to the local NE sent from the manager.
The EML serves as a higher-level manager for managers at the NEL.
u Communication protocol stack software
Version: B 5-23
The communication protocol stack software is responsible for management

information exchange between the network management system and NEs, and
between NEs.
u Real-time OS
The NMU runs in an embedded real-time OS for resource management. The

OS assists the execution of programs, schedules tasks, performs storage
management, manages peripheral devices, and implements communication
among processes.
5.3.5 Network Management Software
The OTNM2000 is developed based on Windows 2000 Server and consists of the
data collection module, data processing module, graphical user interface (GUI)
module, and database. The software architecture is shown in Figure 5-9.
Figure 5-9 Software Architecture of the OTNM2000
The modules and their functions are described as follows:
5-24 Version: B
u The data collection module collects the alarm and performance data of
managed objects. The data processing module analyzes and processes the
collected data and then stores the data in the database. The OTNM2000
supports SQL Database and Informix Database.
u The data processing module provides fault management, performance

management, configuration management, and security management for the
management module.
u The management module consists of two parts: configuration management and

monitoring management.
4 The configuration management part performs logical configuration,

physical configuration, service configuration, and area configuration.
4 The monitoring management part is the core of the OTNM2000. It provides

switch connection configuration, alarm query, performance query, and fault
management.
Version: B 5-25
6 Service and Network
The following details the service types provided by the CiTRANS R860 and the
network for each type of service. It covers these topics:
Ethernet Service
CES Service
Radio Service
Network Capability
Version: B 6-1
6.1 Ethernet Service
The CiTRANS R860 supports multiple types of Ethernet services and provides a
complete L2VPN solution.
A VPN is a virtual private network that the carrier provides to a customer on its
public network. Telecommunication carriers can provide carrier-class networks with
high performance and low costs for customers by establishing VPNs over its public
network. This is a good solution for carriers to gain profits. However, traditional
VPNs are incompetent in ensuring VPN scalability, security, management,
maintenance, QoS guarantee, and traffic engineering, and therefore cannot fully
meet customer requirements.
The MPLS-based L2VPN solution is launched to address these problems. The

L2VPN solution overcomes the drawbacks of traditional IP networks, FR networks,
and ATM networks. It also provides advantages including secure information
transmission, real-time information transmission, wide frequency band, convenience,
and low costs. Therefore, the L2VPN solution can meet customer requirements for
the VPN service.
Three types of Ethernet service can be provided by the CiTRANS R860.
u E-Line service
u E-LAN service
u E-Tree service
6.1.1 E-Line Service
Introduction
In the E-Line service, the Ethernet is used to replace the original private line service.
The E-Line service is a P2P service. In the E-Line service, packets of certain ports
or certain packets of a port on the user side are forwarded to ports on the network
side, and packets received from the network side are forwarded to ports on the user
side and other ports on the network side.
The E-Line service can be further classified into two types.
6-2 Version: B
u EP-Line service: No service is multiplexed on the port of the network side.
u EVP-Line service: Services are multiplexed on the port of the network side.
Features
The E-Line service has the following features:
u It supports only P2P service applications.
u Different services are isolated, but they can choose to share (EVP-Line) or
monopolize (EP-Line) the bandwidth.
Example
Figure 6-1 shows an example of the E-Line service provided by the CiTRANS R860.
Company X has two branches deployed in cities A and C, company Y has two
branches deployed in cities B and C, and company Z has two branches deployed in
cities A and B. The branches of each of the three companies need to exchange data.
The CiTRANS R860 can provide the E-Line service for the three companies.
Service data of different companies is labeled with different VPWS tags for isolation
purposes.
Figure 6-1 E-Line Service Example
Version: B 6-3
6.1.2 E-LAN Service
Introduction
In scenarios where the E-LAN service is used to replace the original LAN service,
the E-LAN service is most important and is most widely used. The E-LAN service is
a P2MP service. In the E-LAN service, packets of certain ports or certain packets of
a port on the user side are forwarded to multiple ports on the network side, and
packets received from the network side are forwarded to ports on the user side and
other ports on the network side.
The E-LAN service can be further classified into two types.
u EP-LAN service: No service is multiplexed on the port of the network side.
u EVP-LAN service: Service are multiplexed on the port of the network side.
Features
The E-LAN service has the following features:
u It supports multi-service access.
u Different services are isolated, but they can choose to share (EVP-LAN) or
monopolize (EP-LAN) the bandwidth.
Example
Figure 6-2 shows an example of the E-LAN service provided by the CiTRANS R860.
Company K is headquartered in city C. K has branch 1 deployed in cities A and B,

and branch 2 deployed in cities A, B, and C. Branches 1 and 2 has no business
contact and need to be isolated from each other. The headquarters need to
communicate with the branches and visit the Internet.
The CiTRANS R860 is deployed to provide the E-LAN service for K. Service data of
different branches are labeled with different VPLS tags. In this way, data can be
shared within a branch whereas data of different branches are isolated. The network
access data of the headquarters are isolated from the service data through VPLS.
6-4 Version: B
Figure 6-2 E-LAN Service Example
6.1.3 E-Tree Service
Introduction
The E-Tree service is a P2MP service. In the E-Tree service, packets of certain
ports or certain packets of a port on the user side are forwarded to a port on the
network side, or packets received from the network side are forwarded to ports on
the user side or to other ports on the network side.
The E-Tree service can be used for ISP (Internet Service Provider) connection. Also,
it can be used to provide a basic network for multicast services such as IPTV
(Internet Protocol Television). The E-Tree service can be further classified into two
types.
u EP-Tree service: No service is multiplexed on ports of the network side.
u EVP-Tree service: Services are multiplexed on ports of the network side.
Version: B 6-5
Features
The E-Tree service has the following features:
u It supports the communication mode of a single point (root node) to multiple

points (leaf nodes).
u Data on the root node is forwarded to all leaf nodes.
u Services on different leaf nodes are isolated, but they can choose to share
(EVP-Tree) or monopolize (EP-Tree) the bandwidth.
Example
The E-Tree service is a type of P2MP bidirectional convergence service. Figure 6-3
shows an example of the E-Tree service provided by the CiTRANS R860.
In the example, a 3G network is constructed for a carrier and services of group

customers need to be converged and forwarded to the 3G core network. The
CiTRANS R860 networks with the CiTRANS R845 in hybrid mode to provide the E-
Tree service to aggregate services between RNCs and group customers and
between RNCs and BTSs to the 3G core network.
6-6 Version: B
Figure 6-3 E-Tree Service Example
Version: B 6-7
6.2 CES Service
The CES technology is used on the packet transport network to implement

transparent transmission of TDM circuit switched services. The CiTRANS R860
supports transparent transmission of E1 and STM-1 services on emulated circuits.
6.2.1 Service Example
The CiTRANS R860 provides CES services by using the PWE3 (Emulation Edge-
to-Edge) technology.
CES services are mainly applied in radio services and private line service. The
CiTRANS R860 is connected to the 2G / 3G station or enterprise private line
through E1 or channelized STM-1 line. It then slices STM-1 signals and
encapsulates them into data packets. The packets are forwarded to the peer end
over the MAN, which serves as the transport network. See Figure 6-4.
Figure 6-4 CES Example
6-8 Version: B
6.2.2 Emulation Mode
The CiTRANS R860 supports CES in the structured or non-structured emulation

mode.
In the structured emulation mode:
u Can identify and process the frame structure and transmit signaling in CES
frames.
u Can identify frame structure of CES service. It may not transmit idle timeslot
channels, but only extracts useful timeslots of CE equipment sets from the E1
traffic stream and then encapsulates them into PW packets for transmission.
u Can identify and transmit CAS and CCS in E1 traffic streams.
In the unstructured emulation mode:
u Segments all CES services as bit streams and then encapsulates them for
transmission over a PW tunnel.
u Can transparently transmit CES traffic data and synchronous timing information.
SAToP completely disregards any structure, and PEs have no need to interpret
the CES data or to participate in the CES signaling.
u Is a simple way for transparent transmission of PDH bit-streams.
6.2.3 Clock Synchronization Mode
The CiTRANS R860 provides multiple CES clock synchronization solutions to

ensure the transmission of the CES clock. Three clock synchronization solutions
can be used:
u System clock recovery
u Differential clock recovery
u Adaptive clock recovery
The following describes the working principles of these solutions.
Version: B 6-9
System Clock Recovery
In system clock recovery, the sender that generates CES signals and the receiver
that extracts CES signals use the same network reference clock as the
synchronization signal source. Figure 6-5 shows the working principle of system
clock recovery.
Figure 6-5 Implementation Principle of System Clock Recovery
Differential Clock Recovery
In differential clock recovery, the service receiver and sender have the same public
timing reference signal. The sender packages the synchronization signal on the
service side and transmits the signal to the receiver over the packet switched
network. The receiver then recovers the synchronization signal based on the public
timing reference signal available on the receiver. Figure 6-6 shows the working
principle of differential clock recovery.
6-10 Version: B
Figure 6-6 Implementation Principle of Differential Clock Recovery
Adaptive Clock Recovery
In adaptive clock recovery, no identical reference clock is required. The Timing

packet sent by the sender contains the code of the service clock. The code is
represented as sequence number or timestamp. The receiver then recovers the
clock by using the recovery algorithm based on the sequence number or timestamp.
Figure 6-7 shows the working principle of adaptive clock recovery.
Figure 6-7 Implementation Principle of Adaptive Clock Recovery
Version: B 6-11
6.3 Radio Service
The following describes the service bearer solution and clock synchronization
solution provided by the CiTRANS R860 for the radio network.
6.3.1 Service Bearer Solution for the Radio Network
The CiTRANS R860 enables 2G and 3G services to be carried over IP RAN.
For 2G services, the TDM network carries mainly voice services and the traffic is
light. Typically, a BTS connects to the BSC through 1-3 E1 interfaces. Some carriers
do not have fixed-network E1 lines and therefore need to lease E1 lines from other
carriers with high costs. As carriers extend the radio access network worldwide,
problems such as low bandwidth usage, low scalability, and inflexible configuration
occur on the 2G RAN constructed based on the TDM / SDH. The 2G / 3G RAN
carried over IP is the development trend of the radio service bearer network.
The CiTRANS R860 provides the MPLS-based CES service, transparently

transmits E1 and STM-1 signals by using the PW3E technology, and implements
service data transmission between the BTS and the BSC over the cost-effective
metropolitan Ethernet. Figure 6-8 shows the 2G / 3G RAN solution provided by the
CiTRANS R860.
Figure 6-8 2G/3G RAN Bearer for the CiTRANS R860
6-12 Version: B
6.3.2 Clock Synchronization Solution for the Radio Network
On the 3G mobile service bearer network, time is synchronized for the entire
network through an external clock or GPS. The CiTRANS R860 complies with IEEE
1588v2. The 1 PPS&TOD interface or Ethernet interface can be used for time signal
input and output and time synchronization on the entire network as required by 3G
services.
As shown in Figure 6-9, equipment sets on the bearer network synchronize time
over IEEE 1588v2. NodeBs that support IEEE 1588v2 use multicast 1588v2 time
signals for time synchronization. NodeBs that do not support IEEE 1588v2 use the
Ethernet or WAN interface for frequency synchronization.
Figure 6-9 Clock Synchronization through 1588v2
Version: B 6-13
6.4 Network Capability
The CiTRANS R860 is mainly applied at the distribution layer of MANs. It transmits
packet services over networks and aggregates services to the data backbone
network.
The CiTRANS R860 provides powerful service grooming and convergence

capabilities to meet various application requirements. The CiTRANS R860 provides
the following network interfaces:
u 10GE
u GE
u FE
u STM-1
6.4.1 Typical Network for Ethernet Service
The CiTRANS R860 supports three types of Ethernet services.
u E-Line service
u E-LAN service
u E-Tree service
Table 6-1 describes the application scenarios of the Ethernet service provided by
the CiTRANS R860.
Table 6-1 Application Scenarios of Ethernet Services Provided by the CiTRANS R860
Item Description
Access service E-Line service E-LAN service E-Tree service

Network mode Chain, mesh Mesh Tree
Service type FE, GE, 10GE FE, GE, 10GE FE, GE, 10GE
6-14 Version: B
Table 6-1 Application Scenarios of Ethernet Services Provided by the (Continued)
Item Description
Network
GE, 10GE GE, 10GE GE, 10GE
interface
u Services are u Services are
u Services are connected and connected and
connected and transparently transparently
transparently transmitted over GE transmitted over GE
transmitted or FE. Also, QoS is or FE. Also, QoS is
over GE or FE. ensured. ensured.
Also, QoS is u Traffic statistics u Traffic statistics
ensured. collected based on collected based on
Service u Traffic statistics the tunnel or PW are the tunnel or PW are
scenario collected provided. provided.
based on the u BFD, Ethernet OAM, u BFD, Ethernet OAM,
tunnel or PW and MPLS-TP OAM and MPLS-TP OAM
are provided. are supported. are supported.
u BFD, Ethernet u Layer 2 multicast and u Layer 2 multicast
OAM, and Layer 2 broadcast and Layer 2
MPLS-TP OAM suppression are broadcast
are supported. supported. suppression are
u User data is isolated. supported.
Figure 6-10 shows the typical network of the E-Line service provided by the
CiTRANS R860.
Figure 6-10 Typical Networking of the E-Line Service Provided by the CiTRANS R860
Version: B 6-15
Figure 6-11 shows the typical network of the E-LAN service provided by the
CiTRANS R860.
Figure 6-11 Typical Networking in the Ethernet E-LAN Service
Figure 6-12 shows the typical network of the E-Tree service provided by the
CiTRANS R860.
6-16 Version: B
Figure 6-12 Typical Networking of the E-Tree Service Provided by the CiTRANS R860
6.4.2 Typical Network for CES Service
The CiTRANS R860 supports two types of CES services.
u E1 service
u STM-1 service
Table 6-2 describes the application scenarios of the CES services provided by the
CiTRANS R860.
Table 6-2 Application Scenarios of CES Services Provided by the CiTRANS R860
Item Description
Access service E1 service STM-1 service

Application mode Packet switched Packet switched
Version: B 6-17
Table 6-2 Application Scenarios of CES Services Provided by the (Continued)
Item Description
Network mode Ring, tree, mesh Ring, tree, mesh
Service type E1 STM-1

Network interface E1 STM-1
The convergence point accesses the
Service scenario The E1 emulates the CES. STM-1 to forward service data to the
BSC.
Figure 6-13 shows the typical network of the CES services provided by the
CiTRANS R860.
Figure 6-13 Typical Network of the CES Services Provided by the CiTRANS R860
6.4.3 Typical Network for Mobile Service
The CiTRANS R860 runs at the distribution layer of mobile networks to connect the
BTSs to the BSC. The CiTRANS R860 provides various types of interfaces to
aggregate and carry packet services.
Table 6-3 describes the application scenarios of the mobile services provided by
the CiTRANS R860.
6-18 Version: B
Table 6-3 Application Scenarios of Mobile Services Provided by the CiTRANS R860
Item Description
Access service E1 service

Application mode Packet switched
Network mode Ring, tree, mesh
Service type FE, E1, STM-1
Network interface GE, 10GE

Services are aggregated and encapsulated into STM-1 services
Service scenario
and then forwarded to the BSC.
Figure 6-14 shows the typical network of the mobile services provided by the
CiTRANS R860.
Figure 6-14 Typical Networking of the Mobile Services Provided by the CiTRANS R860
6.4.4 Typical Network for L3VPN
L3VPN is a routing-based VPN solution. The L3VPN technology is described in

ITEF RFC 2547.
The CiTRANS R860 supports the following L3VPN network modes:
u P2P L3VPN
Version: B 6-19
u P2MP L3VPN
u L3VPN Hub-Spoke
Table 6-4 describes the application scenarios of the the L3VPN service provided by
the CiTRANS R860.
Table 6-4 Application Scenarios of the L3VPN Service
Item Description
Network mode P2P P2MP Hub-Spoke
Service Type 10GE, GE, FE 10GE, GE, FE 10GE, GE, FE
Network interface 10GE, GE, FE 10GE, GE, FE 10GE, GE, FE
u Users in the same VPN can forward u The hub PE can exchange routing
traffic to each other but cannot information with all spoke PEs.
communicate with users outside this u Spoke PEs need to use the hub PE for
VPN. mutual access.
u Services are connected and u Services are connected and transparently
transparently transmitted over GE or FE. transmitted over GE or FE. Also, QoS is
Also, QoS is ensured. ensured.
Service scenario u Traffic statistics collected based on the u Traffic statistics collected based on the
tunnel or PW are provided. tunnel or PW are provided.
u BFD, Ethernet OAM, and MPLS-TP OAM u BFD, Ethernet OAM, and MPLS-TP OAM
are supported. are supported.
u User data is isolated. u User data is isolated.
u Routing and forwarding are supported. u Routing and forwarding are supported.
u Dual-homing and FRR protection are u Dual-homing and FRR protection are
supported. supported.
P2P L3VPN
Figure 6-15 shows the network diagram for P2P L3VPN. Users in the same VPN
can communicate with each other. Users in different VPNs cannot communicate
with each other.
6-20 Version: B
Figure 6-15 Ethernet L3VPN Point-to-point Network Diagram
P2MP L3VPN
Figure 6-16 shows the network diagram for P2MP L3VPN. This network mode has
the following features:
u Users in the same VPN can communicate with each other. Users in different
VPNs cannot communicate with each other.
u A CE can belong to multiple VPNs. A user network segment belonging to a

VPN can communicate with other users in this VPN.
u A CE can simultaneously connect to multiple PEs.
Version: B 6-21
Figure 6-16 Ethernet L3VPN Point-to-multipoint Network Diagram
L3VPN Hub-Spoke
Figure 6-17 shows the network diagram for PL3VPN Hub-Spoke.
Figure 6-17 Ethernet L3VPN Hub-Spoke Network Diagram
6-22 Version: B
6.4.5 L2 / L3 Hybrid Network
Figure 6-18 L2 / L3 Hybrid Network
AsFigure 6-18 shows, via using the L2 / L3 bridge connection technology, we can
connect the L2VPN services in the access / distribution network with the L3VPN
routing forwarding services in the IP backbone MAN. This is the evolution for the IP-
based network.
The L2 / L3 hybrid network offers a complete array of service guarantees. It

provides PW redundancy and LSP 1:1 protection for the L2VPN services, and VPN
FRR protection for the L3VPN services; in addition, it uses the BFD fault detection
to switch over services rapidly.
Version: B 6-23
6.4.6 MS-PW Network
In recent years, the PWE3 technology gradually matures, the technology related
drafts are also turned into the formal RFC documents, and the PWE3 technology is
constantly used in the operator network. Via the MS-PW network, the problem of the
lack of flexibility in the current PWE3 network mode is solved. The operations are
described as follows: Between two sets of CiTRANS R860, sets up multiple PWs
using the MS-PW technology, so as to cross networks of different types and
implement the correct routing and forwarding between equipment sets in networks
of different types.
As shown in Figure 6-19, the tunnels with different signaling are connected via the
switching PE nodes, and thus an integrated network is formed. The switching PE
node supports multiple types of tunnel connections, including the dynamic RSVP
tunnel and the static MPLS tunnel.
Figure 6-19 MS-PW Network
6-24 Version: B
6.4.7 Hierarchical VPLS Network
The CiTRANS R860 supports the hierarchical VPLS network. As Figure 6-20 shows,
corporations A and B have multiple divisions in various sites, and they need to
construct the corresponding enterprise networks. We use the hierarchical VPLS
network to implement the interconnection between the enterprise networks in
various sites for each corporation. The hierarchical VPLS network saves the
signaling overheads in the network, and improves the scalability of the VPLS
network deployment.
Figure 6-20 Hierarchical VPLS Network
Version: B 6-25
7 Protection Mechanism
As telecommunication services develop and transport networks become

increasingly large in scale, network stability, security, and reliability become the
concern in the construction and operations of transport networks. These elements
also become the hot spots in competition among carriers. The CiTRANS R860
provides a complete set of protection functions to ensure normal service operations.
The following introduces the protection mechanisms of the CiTRANS R860 and
covers these topics:
Equipment-Level Protection
Network-Level Protection
Protection for Network Management Information
Version: B 7-1
7.1 Equipment-Level Protection
The CiTRANS R860 supports 1+1 protection for the SCUR1 card, the RCUO1 card,
and the power card. The following describes the working principle, switchover
triggering conditions, and protection parameters of the equipment-level protection.
7.1.1 1+1 Protection for the SCUR1 Card
The SCUR1 card processes service switching, conducts clock synchronization and
output, and performs protection switchover.
Working Principle
Two SCUR1 cards working in the active / standby mode are installed on the
CiTRANS R860. In normal cases, only the active card runs. When the active card is
faulty, the standby card is notified of this event through the monitoring channel
between them. Then the standby card becomes active to ensure normal operations
of the CiTRANS R860.
After the original active card resumes, it enters the standby state. When the current
active card becomes faulty, the original active card restores to the working state.
Switchover Triggering Conditions
u A hardware or software fault occurs on the active card.
u The switchover command is manually issued.
u The active card is manually removed.
u The active card performs a hard reset.
Protection Parameters
Table 7-1 describes the protection parameters.
Table 7-1 Protection Parameters
Item Specification
Card slot 09 and 10

Revert mode Non-revertive
7-2 Version: B
Note:
Two revert modes can be used.
u Revertive: After the original active card resumes, services are

automatically switched back to this card.
u Non-revertive: After the original active card resumes, services are

not switched back to this card.
7.1.2 1+1 Protection for the RCUO1 Card
The RCUO1 card of the CiTRANS R860 provides multiple types of management
and auxiliary interfaces for routing protocol control and device management.
Working Principle
Two RCUO1 cards working in active / standby mode are installed on the CiTRANS
R860. In normal cases, only the active RCUO1 card runs. When the active RCUO1
card is faulty, the standby RCUO1 card is notified of this event through the
monitoring channel between them. Then the standby RCUO1 card becomes active
to ensure normal operation of the CiTRANS R860.
After the original active RCUO1 card resumes, it enters the standby state, forming 1
+1 protection again.
u A hardware or software fault occurs on the active card.
u The active card is manually unplugged.
u The active card performs a hard reset.
Table 7-2 describes the 1+1 protection parameters of the RCUO1 card.
Version: B 7-3
Table 7-2 1+1 Protection Parameters of the RCUO1 Card
Item Specification
Card slot 00 and 01

Revert mode Non-revertive
7.1.3 1+1 Protection for the Power Card
The AIFJ1 / AIFJ2 card provides the -48 V power for the CiTRANS R860.
Working Principle
Two power and auxiliary terminal boards working in the 1+1 hot standby mode are
installed on the CiTRANS R860 to ensure normal operations of the CiTRANS R860.
Table 7-3 describes the 1+1 protection parameters of the power card.
Table 7-3 1+1 Protection Parameters of the Power Card
Item Specification
Card slot 16 and 17

Protection mode 1+1 hot standby
7.2 Network-Level Protection
The following describes the working principle, switchover triggering conditions, and
protection parameters for the network-level protection of the CiTRANS R860.
7.2.1 1:1 Protection for Tunnel
Working Principle
In 1:1 protection for tunnels, the standby tunnel is used to protect the services
carried over the active tunnel. In normal cases, services are carried over the active
tunnel. When the active tunnel is faulty, services are switched over to the standby
tunnel.
7-4 Version: B
The active / standby status and switchover status are exchanged using the BFD or
MPLS-TP protocol, which is borne over the protection tunnel. Devices at the two
ends of a tunnel performs service switchover based on the protocol status and
switchover status.
Note:
1:1 protection is enabled for the tunnel between node A and node B. 1:1
protection needs to be configured on the two nodes regardless of the
path that services are transmitted.
Figure 7-1 shows the working principle of 1:1 protection for tunnels.
Figure 7-1 1:1 Protection for Tunnels
u The intermediate node is powered off.
u The working LSP path is faulty.
Version: B 7-5
Item Specification
Switchover type 1:1 protection for tunnels
Revert mode Revertive or non-revertive

Switchover protocol BFD or MPLS-TP
Switchover time (ms) ≤ 50
Hold-off time (ms) 0 to 255
7.2.2 PW Redundancy Protection
Introduction
The PW redundancy protection is similar to the tunnel 1:1 protection. Based on the
BFD for PW, it implements the protection at the PW layer. The tunnel 1:1 protection
is to implement the protection at the tunnel layer based on the BFD for tunnel.
Protection Principle
For the PW redundancy protection, the standby PW is used to protect the service
traffic transmitted over the active PW, and the single receiving is used. The process
of the switchover and resuming is described as follows:
1. When the sink NE detects a fault at the working channel, it will execute the
switchover at once and send the switchover request to the source NE.
2. When the source NE receives the switchover request, the service traffic will be
switched to the standby PW, and the source NE will send the acknowledgment
message. Thus the switchover operations are completed.
3. When the sink NE detects that the working channel has resumed, it will send
the switchover request to the source NE and switches the service traffic to the
active channel.
4. When the source NE receives the switchover request, the service traffic will be
switched to the active PW, and the source NE will send the acknowledgment
message. Thus the switchover operations are completed.
7-6 Version: B
u The BFD for PW detects a fault.
The parameters of the PW redundancy protection are described in Table 7-5.
Table 7-5 PW Redundancy Protection Parameters
Item Description
Switchover type PW redundancy protection
Revert mode Revertive or non-revertive mode

Switchover protocol BFD for PW
7.2.3 Virtual Router Redundancy Protection
Introduction
In VRRP (Virtual Router Redundancy Protocol), the master router forwards data and
the backup routers are in the listening state. When the master router is faulty, a new
master router is elected among the backup routers of the virtual router. The new
master router takes over the data forwarding work from the faulty master router.
VRRP is described in RFC 3768. Table 7-6 describes the terms involved in VRRP.
Table 7-6 Term Description for VRRP
Term Description
A virtual router comprises a master router and multiple backup routers.

Virtual router
The virtual router is considered as the default gateway for the host.
It indicates the ID of a virtual router. Routers constituting a virtual router

VRID
have the same VRID.
Master router The master router forwards packets.
When the master router is faulty, a backup router is elected as the new
Backup router
master router to forward packets.
Version: B 7-7
Table 7-6 Term Description for VRRP (Continued)
Term Description
It indicates the IP address of a virtual router. A virtual router may have

Virtual IP address
one or multiple IP addresses.
A router whose interface IP address is the same as the virtual IP

IP address owner
address is called an IP address owner.
A virtual router has a virtual MAC address. The virtual MAC address is
in the format of 00-00-5E-00-01-{VRID}. In normal cases, a virtual
Virtual MAC address router responds to ARP requests using its virtual MAC address. A
virtual router uses its actual MAC address only when special
configuration is completed for the virtual router.
Priority In VRRP, virtual routers have different priorities.
If a backup router works in non-preemption mode, it will not be elected

Non-preemption
as the new master router even if it is assigned a higher priority when
mode
the master router runs properly.
If a backup router works in preemption mode, after it receives a VRRP

packet, it compares its priority with the priority carried in the packet. If
Preemption mode its priority is higher than the priority of the current master router, it will
become the new master router; otherwise, it remains as a backup
router.
Working Modes
Two working modes are used for VRRP: active / standby and load balancing.
u Active / standby mode
In active / standby mode, all services are carried by the master router. When
the master router becomes faulty, a new master router is elected to take over its
services. See Figure 7-2.
7-8 Version: B
Figure 7-2 Master and Backup Redundancy
RTA is the master router and forwards packets. RTB and RTC are backup
routers and are in the listening state. When RTA becomes faulty, a new master
router is elected based on the priorities of RTB and RTC. The new master
router takes over the data forwarding work from RTA.
u Load balancing mode
Multiple virtual routers can be created on an interface of a router. This router

functions as the master router in a virtual router and as a backup router in other
virtual routers. See Figure 7-3.
Version: B 7-9
Figure 7-3 Load Sharing
Virtual router 1: RTA is the master router and RTB is a backup router.
Virtual router 2: RTB is the master router and RTA is a backup router.
To ensure that RTA and RTB process service flows in load balancing mode, the
default gateway address must be set to 10.1.1.254 and 10.1.1.253 for hosts on
the LAN. Ensure that priorities are properly configured for routers in the two
virtual routers so that a router functions as the master router in only one virtual
router.
u Rapid detection: Rapidly detects faults for the BFD bound with the VRRP, so as
to implement rapid switchover of the VRRP.
u The master router is faulty.
u The master router detects a BFD alarm.
7-10 Version: B
7.2.4 Dual-Homing Protection
Dual-homing protection combines MPLS-TP network side protection and

attachment circuit (AC) protection. Network faults trigger switchover only on the
network side and AC faults trigger switchover only on the AC side. When faults
occur on both the network side and AC side, switchover is triggered simultaneously
at both sides to protect services. LSP 1+1 / 1:1 protection is supported on the
network side whereas 1+1 / 1:1 link protection is supported on the AC side. The two
NEs on the AC side are respectively connected to the working and protection lines
of the RNC.
As shown in Figure 7-4, node A is dual-homed to RNC. The working path is

A→B→C→RNC.
u LSP 1+1 / 1:1 protection is enabled for the path A→C. The working path is
A→B→C, and the protection path is A→D→E→C.
u 1+1 / 1:1 link protection is enabled on the AC side. The working path is
C→RNC, and the protection path is C→E→RNC.
Figure 7-4 Working Status During Normal Operation
The dual-homing switchover mechanism is described as follows:
u Faults occur on the MPLS-TP network.
Version: B 7-11
As shown in Figure 7-5, when a fault occurs on the working path, that is,
A→B→C, an LSP 1+1 / 1:1 protection switchover is triggered for the tunnel
between A and C. The path between C and the RNC remains unchanged.
Therefore, the service path changes to A→D→E→C→RNC, protecting
services on the network side.
Figure 7-5 Dual-homing Protection Switching Status – the Network Side is Faulty
u Faults occur on the AC side.
As shown in Figure 7-6, when a fault occurs on the tunnel between C and RNC,
E receives the fault information sent from C and switches over the services to
the path C→E→RNC. The RNC receives services from E. The service path
changes to A→B→C→E→RNC, protecting services on the AC side.
Figure 7-6 Dual-homing Protection Switching Status – the AC Side is Faulty
7-12 Version: B
u Faults occur on both the MPLS-TP network and the AC side.
As shown in Figure 7-7, when faults occur on both the MPLS-TP network and
the AC side, both A and RNC switch over to the protection path. C sends the
fault information to E. E switches over services to the path A→D→E→RNC,
protecting services.
Figure 7-7 Dual-homing Protection Switching Status – the Network Side and AC Side are Faulty
u Faults occur on node C.
As shown in Figure 7-8, when a fault occurs on Node C, A switches over to the
protection path. Other nodes perform the same actions as in Figure 7-7. The
service path changes to A→D→E→RNC, protecting services.
Figure 7-8 Dual-homing Protection Switching Status – Node C is Faulty
Version: B 7-13
u The intermediate node is powered off.
u The working path on the network side is unavailable.
u The working path on the AC side is unavailable.
Table 7-7 describes the dual-homing protection parameters.
Table 7-7 Dual-homing Protection Parameters
Item Description
1+1 / 1:1 unidirectional switching

AC side
Switchover type 1+1 / 1:1 bidirectional switching
Network side 1+1 / 1:1 bidirectional switching
Revert mode Revertive

Switchover protocol BFD or MPLS-TP
Recovery time (minute) 1 to 12 (default value: 5)
7.2.5 MPLS TE FRR Protection
Introduction
MPLS TE (Traffic Engineering) FRR is a technology for implementing partial

network protection. MPLS TE FRR is a link and node protection mechanism in
MPLS TE. When a link or node fails, the LSP that is configured with FRR
automatically switches over data to the protection link.
Quick response and timely switchover are features of MPLS TE FRR. MPLS TE
FRR can ensure smooth migration of service data without service interruption. In
addition, the ingress node of the LSP attempts to find a new path for re-setting-up
an LSP and switches over service data to the new LSP. Before a new LSP is set up,
service data are forwarded along the protection path.
7-14 Version: B
The components of the MPLS TE system are involved in setting up the FRR LSP
and working LSP. MPLS TE FRR is implemented based on RSVP TE and complies
with RFC 3209 and RFC 4090. The following working modes can be used to
implement the MPLS TE FRR.
u Detour mode (one-to-one backup)
In the detour mode, a protection path is set up for each protected LSP. The
protection path is called detour LSP.
u Bypass mode (facility backup)
In the bypass mode, a single protection path is set up for multiple protected
LSPs. The protection path is called bypass LSP.
For the network shown in Figure 7-9, when the link RTB→RTC fails or the node
RTC fails, the service traffic on the active LSP will be switched to the Bypass
LSP. The outgoing header from the RTB uses the label that the RTF allocates
for the RTB. In addition, the egress label of the RTC is also pushed into the
label stack.
On the link RTB→RTF→RTD, the LSP uses the double labels. For the packet
received by the RTD, after the label allocated for the RTF by the RTD is popped
up, the system uses the label allocated for the RTC by the RTD to forward the
packet.
Figure 7-9 FRR in the Bypass Mode
In the detour mode, each LSP is protected independently and therefore the
overhead is high. In practice, the bypass mode is more widely used.
Version: B 7-15
u The intermediate node is faulty.
u The active LSP is faulty.
7.2.6 VPN FRR Protection
Introduction
VPN FRR (Fast Re-route) resolves the problem of a long route convergence time
via presetting the active and standby next hops on the PE. It implements the rapid
convergence of end-to-end services when a PE node has faults on a network where
CEs are dual-homed to PEs.
7-16 Version: B
Figure 7-10 VPN FRR Protection Principle
In Figure 7-10, PE A sets the active next hop PE B and the standby next hop PE C.
Under the normal condition, the access path from CE A to CE B is: CE A→PE
A→PE B→CE B. When faults of PE B or the outer tunnel of the active route cause
that the PE node is not reachable, PE A will perform forwarding using the forward
information on the standby route; under this condition, the access path from CE A to
CE B is: CE A→PE A→PE C→CE B.
u The active PE is faulty.
u The outer tunnel is faulty.
Version: B 7-17
7.2.7 IP FRR Protection
Introduction
When a link is faulty, the time for the route to be convergent again is generally at a
second level. This can cause the interruption of the normal services for a second
level . Via setting the standby link, the IP FRR technology can fill in the time interval
of route convergence so that the protected services can be switched over within 50
ms.
In the IP FRR protection, three link types are involved, respectively being the active
link, the sub-optimum link, and the standby link.
u The active link refers to the link with the optimum route. When the network
status is normal and the route is convergent, the service traffic is forwarded via
the active link.
u The sub-optimum link refers to the link whose routing cost is higher than that of
the active link. When the active link fails, the route will be convergent to the
sub-optimum link.
u The standby link refers to the appointed link of the standby next hop.
Figure 7-11 shows the principle of the IP FRR.
7-18 Version: B
Figure 7-11 IP FRR Protection Principle
Under the normal conditions, the services are forwarded via the active link between
RTA and RTB. When the active link is faulty, the system will perform the protection
operations as follows:
1. As soon as the active link detects a BFD alarm, the starts the calculation for the
route convergence.
2. RTA executes the link switchover, and the packets are redirected to the
standby link between RTA and RTD for forwarding.
3. After the calculation for the route convergence is completed, the packets will be
redirected to the sub-optimum link between RTA and RTC for forwarding,
according to the new routing table.
4. When the BFD protocol detects that the active link has been resumed, the
routing table will be re-calculated for convergence, and the the packets are
switched over to the resumed active link for forwarding.
Version: B 7-19
Note:
If the sub-optimum link is the same as the preset standby link, the
packets will not be redirected in step 3.
When the active link is faulty, the IP FRR protection can switch over services to the
preset standby link rapidly and fill in the time interval of route convergence. Thus the
services will not be interrupted.
u The active PE is faulty.
u The active link detects a BFD alarm.
7.2.8 LDP FRR Protection
Introduction
The LDP FRR protection is described as follows: When the LDP operates in the
downlink label automatic distribution, orderly label control, and free label keeping
mode, the LDP sets up the standby LSP via generating the label forwarding table
entry for the label mapping of the appointed standby interface or the standby next
hop. When the network operates normally, the label is forwarded by the active LSP.
When the active LSP is faulty, the label is forwarded by the standby LSP. When the
active LSP is faulty, the LDP FRR can implement non-interruption of the service
traffic prior to the network convergence.
When the LDP operates in the downlink label automatic distribution, orderly label
control, and free label keeping mode, the label distribution router saves all received
label mapping for a certain forwarding equivalence class, but it only generates the
label forwarding table entry for the label mapping from the next hop of the route
corresponding to this forwarding equivalence class.
7-20 Version: B
Using this feature of the LDP, the LDP FRR also generates the label forwarding
table entry for the label mapping of the appointed standby interface or standby next
hop. Under the condition that the standby label is saved, this means that the
standby LSP is set up. The label forwarding router can response to the route
change rapidly and switch to the standby label, so as to complete the switching
protection against the network faults.
The outgoing interface of the LSP detects a BFD fault.
7.2.9 LAG Protection for the Ethernet
Introduction
Link aggregation group (LAG) involves bundling a group of physical Ethernet ports
with the same rate into a logical port to increase the bandwidth and provide link
protection. When a certain link fails, the services on it will be switched to other links,
and this improves the link reliability.
Multi-chassis link aggregation group (MC-LAG) supports the link aggregation

spanning equipment sets; it can bundle data links on different equipment sets into a
link aggregation group. When a certain link or equipment fails, the services on it will
be switched to other links or equipment sets, and this improves the link reliability.
Working Principle
In LAG protection, load balancing is implemented among the ports and the ports are
in equal positions. The CiTRANS R860 supports inter-equipment LAG protection
and intra-equipment LAG protection.
LAG has the following advantages:
u Improves link availability: In an LAG, member ports work in dynamic mutual

backup mode. When a port is faulty, other ports take over its services quickly.
Only ports in the same LAG as the faulty port will take over services from the
faulty port.
Version: B 7-21
u Increases the link capacity: The introduction of the LAG effectively increases
the transmission rate of links. Users can bundle multiple physical ports to obtain
a data link with higher bandwidth without upgrading the current equipment. The
capacity of the link is the sum of that of bundled ports.
u Improves the link reliability: When a certain link or equipment set is faulty, the
service packets on it will be forwarded to other links or equipment sets for
transmission.This ensures the normal transmission of services.
The CiTRANS R860 supports Ethernet LAG protection, as shown in Figure 7-12. In
this example, we configure the AC (Attachment Circuit) side LAGs at NE1 and NE2,
so as to implement the link backup on the same equipment set; and configure the
MC-LAG between NE1 and NE2, so as to implement the link backup between
equipment sets.
Figure 7-12 LAG Protection
The link or equipment set is faulty.
7-22 Version: B
Item Specification
Protection type LAG, MC-LAG

Aggregation by source MAC address, destination MAC address, or
Aggregation mode
source and destination MAC addresses
7.3 Protection for Network Management

Information
Introduction
On the transport network, network management information is transmitted over the

supervisory channel. Usually the supervisory channel and the main channel are the
same physical channel. When the main channel fails, the supervisory channel also
fails. Therefore, a protection channel must be provided for transmitting network
management information.
On a ring network, when a transmission segment such as the optical fiber fails,
network management information is automatically transmitted over the supervisory
channel in the other direction. This does not affect network management.
Figure 7-13 shows the schematic diagram of the protection channel for network
management information on a ring network.
Version: B 7-23
Figure 7-13 Backup of the Network Management Information Channel on a Ring Network (When
a Transmission Segment Fails)
If both ends of a site on an optical fiber segment fail, or an optical fiber segment in a
P2P network or chain network fails, the supervisory channels for network
management information also fail. The network administrator cannot obtain
information about failed sites or operate these sites. To avoid such problems, a
protection channel must be deployed for network management information.
Implementation
The CiTRANS R860 can provide a protection channel for network management
information through the data communication network. Between two NEs to be
protected, a router is configured and connected to the data communication network
to establish a protection channel. When the network runs properly, network
management information is transmitted over the working channel. See Figure 7-14.
7-24 Version: B
Figure 7-14 Backup of the Network Management Information Channel (During Normal Operation)
When the main channel becomes faulty, the NE automatically switches over the
network management information to the protection channel. This ensures that the
network management system monitors the entire network. The switchover process
is completed automatically without manual intervention. Figure 7-15 shows the
protection channel.
Version: B 7-25
Figure 7-15 Backup of the Network Management Information Channel (When the Main Channel
Fails)
Note:
In network planning, it is recommended that the protection channel and

main channel use different physical channels.
7-26 Version: B
8 Security Management
Security management involves authenticating operators that access the network

management system to prevent unauthorized operators from accessing network
resources and the CiTRANS R860. The following describes the security protection
for the network management system, and covers these topics:
Network Security Protection
Security Protection for the Network Management System
Version: B 8-1
8.1 Network Security Protection
The following describes the network security protocols and functions supported by
the CiTRANS R860.
8.1.1 ACL
An ACL (Access Control List) is a series of permit and reject statements. It applies
to addresses and upper-level protocols. ACLs are used to control traffic passing
networks.
An ACL performs the following tasks:
u Limits traffic on a network to improve the performance of the network.
u Provides traffic control.
u Ensures security for basic network access.
u Determines which types of traffic is to be forwarded and blocked on interfaces.
u Determines the network zones that a client can access.
u Shields hosts to allow or reject access to network services.
The CiTRANS R860 supports ACLs based on quintuples, which refer to the source
and destination IP addresses, source and destination ports, and IP protocol. It also
supports setting ACL policies based on MAC addresses (including the source and
destination address). ACLs can be configured to take effect in the entire CiTRANS
R860 system or just on its ports.
8.1.2 Traffic Policing
The CiTRANS R860 supports hierarchical committed access rate (CAR) functions.
Two coloring modes are used: color-blind and color-aware.
Traffic Bandwidth Control
By default, the discards red packets and allows yellow and green packets to pass.
The traffic control functions of the CiTRANS R860 are described as follows:
8-2 Version: B
u Measures traffic by interface or subinterface.
u Measures packets in user traffic queues, including the number of forwarded

packets, number of forwarded bytes, and number of discarded packets.
Statistics of packets of eight priorities are collected.
u Measures the number of forwarded packets, number of forwarded bytes, and

number of discarded packets by user group.
u Measures the number of forwarded packets, number of forwarded bytes, and

number of discarded packets by queue on ports. Statistics of packets of eight
priorities are collected.
u Measures the inbound and outbound traffic of connected users when

functioning as an edge device on the L2VPN and L3VPN.
u Measures traffic passing tunnels when functioning as an edge device on the

MPLS TE network.
u Measures traffic on tunnels by PW.
Service Priority Mapping
The CiTRANS R860 supports the DiffServ model. It completely implements PHB
(Per-Hop Behavior) so that carriers can ensure differentiated QoS levels for users.
During data forwarding, the CiTRANS R860 maps user priorities and VC priorities
carried in received packets to PHBs, and PHBs in forwarded packets to VC or VP
priorities.
The CiTRANS R860 supports setting PHBs for VPWSs, VPWS flows, VPLS-VSs,
and LAN ports emulated over VPLS. An existing mapping table (mapping between
PHBs and VC priorities) can be used. Also, a PHB service level can be specified.
8.1.3 Attack Defense
The CiTRANS R860 provides powerful attack defense capabilities.
Version: B 8-3
Queue Buffering Management
When network congestion occurs or worsens, the CiTRANS R860 employs certain
queue buffering management policies to preferentially ensure the QoS of services
with high priorities.
The supports two type of queue buffering management policies: tail drop and
WRED.
u Tail drop
When a queue is full, packets that arrive later are discarded.
u WRED
4 When the number of packets stored in a buffer does not exceed the
threshold specified by START, the system does not discard packets.
4 When the number of packets stored in the buffer exceeds the threshold
specified by END, all packets are discarded.
4 When the number of packets stored in the buffer is between the START
and the END, all packets face a probability of being dropped based on an
average-queue-length function.
Queue Scheduling
When congestion occurs, the CiTRANS R860 employs different queue scheduling
policies to guarantee the QoS of services with high priorities.
The supports the following two queue scheduling modes.
u SP (Strict Priority)
Packets are scheduled in strict accordance with the priorities of queues.

Packets in queues with lower priorities are sent only after all packets in queues
with higher priorities are forwarded.
u WFQ (Weighted Fair Queuing)
Packets are scheduled fairly based on the weights of queues. Queues with
higher priorities are assigned higher weights and therefore occupy more
bandwidth. Similarly, queues with lower priorities are assigned lower weights
and therefore occupy less bandwidth.
8-4 Version: B
Port Rate Limiting
Rate limiting can be enabled on the inbound and outbound ports of service cards
and switch cards of the CiTRANS R860. Rate limiting policies can be employed for
flow attacks.
Prevention of Malformed Packets
The maximum transmission unit (MTU) is configured to control the size of inbound
packets.
u Packets containing less than 64 bytes are identified as fragments and therefore
discarded. Local or remote collision fragments and short packets with invalid
FCSs are such a type of packet.
u Packets that contains invalid FCS (Frame Check Sequence) and more bytes
than the value that the MTU defines are identified as Jabber packets and
therefore discarded.
Broadcast, Multicast, and Flooding Packet Suppression
The CiTRANS R860 supports suppression of broadcast, multicast, and flooding

packets. You can choose to enable traffic suppression for the three types of packets.
Also, you can set the amount of each type of traffic that is allowed to pass within a
specified period of time.
The CiTRANS R860 has policies to prevent distributed DoS (Denial of Service)
attacks from overspreading.
Prevention of IP Address Spoofing
The CiTRANS R860 supports the unicast reverse path forwarding (URPF) function.
That is, it checks whether the source IP address of a packet matches the source
interface based on the forwarding information base (FIB). If not, it discards the
packet.
Version: B 8-5
8.2 Security Protection for the Network

Management System
The following describes the security protection functions provided by the CiTRANS
R860 for the network management system.
8.2.1 Access Control
The OTNM2000 provides access control functions to prevent unauthorized access

to network resources including the OTNM2000.
User Login Management
u Function description: Users must enter the correct user name and password to
log in to the OTNM2000. Only authenticated users can log in.
u Purpose: The function verifies whether an operator is a legal and authorized

user, and ensures that only authorized operators can log in to the OTNM2000.
Forcible Logout
u Function description: A higher-level user can force a lower-level user to log out
of the OTNM2000.
u Purpose: The function prevents multiple users from configuring the CiTRANS
R860 simultaneously and prevents other users from logging in to the CiTRANS
R860 without authorization.
Management Zone Division
u Function description: The CiTRANS R860 NEs are logically divided into
multiple zones. Users of different levels are grant management permission for
different zones. A user can perform management only in the granted zone.
u Purpose: The function avoids security risks caused by the sharing of the
network management database, ensuring the uniqueness of configuration data.
8-6 Version: B
Access Period Limiting
u Function description: Users are configured to access the OTNM2000 only

within the predefined period. That is, only authorized users can access the
OTNM2000 at specified time periods.
u Purpose: The function improves network security and prevents users from
performing operations at unauthorized times, such as when replacing a card or
testing an error code.
License Control
u Function description: A user needs a license to log in to the OTNM2000. The

user cannot log in to the OTNM2000 after the license expires.
u Purpose: The function improves network security.
Login Password Control
u Function description: The login page is automatically closed in case of three

consecutive wrong password entries.
u Purpose: The function prevents unauthorized users from logging in to the

OTNM2000.
8.2.2 User Level and Permission Management
To prevent unauthorized operations, the OTNM2000 assigns different operation

permission to users of different levels.
There are four levels of users. Users of different levels have different management
permission. Each user is assigned proper management permission. A user of a
higher level has the permission of a user of a lower level.
The details are described as follows:
The system administrator is a high-level user and has permission to configure and
modify network resources. The system administrator manages the entire
OTNM2000, and can perform security management operations including setting
passwords for users, adding, modifying or deleting users, and conducting log
management.
Version: B 8-7
Advanced Users
u Add, modify (user name and password), and delete lower-level users, and save
project configuration data.
u View and delete logs.
u Delete alarms.
u Grant the management scope of a user.
u Delete historical performance records.
Intermediate Users
System maintenance users are intermediate users. Such users are responsible for
routine maintenance of the system, and can add or delete lower-level users, access
the network, configure service data, and back up configuration data.
u Maintain the OTNM2000, perform switching configuration for the equipment,

and deliver commands from the OTNM2000 to the CiTRANS R860.
u Access and back up data in the database, including alarms, performance data,
log reports, and profiles of lower-level users.
u Set and modify alarm shielding, performance shielding, and performance

threshold.
u Control switching connections.
Operational Users
Operational users can monitor the alarm status of the system, browse performance
monitoring results, and view reports, including viewing card configuration data and
active configuration data.
Limited Users
Limited users can only query limited alarm and performance status, and cannot
perform other operations in the OTNM2000.
8-8 Version: B
8.2.3 Data Security
The OTNM2000 takes measures including data integrity and confidentiality

management, database security management, and SAT to ensure data security.
u Data integrity: Data are transmitted to the destination without corruption or loss.
Related data are stored and can be recovered when necessary.
u Data confidentiality: Data are protected and unauthorized users cannot obtain
the data.
u Database security management: Data or files in the database can be backed

up only to the standby network management system or peripheral storage
devices to ensure security of the OTNM2000.
u SAT: The OTNM2000 controls the access of users to the LCT. That is, only
users that are authenticated by using the correct user name and password can
log in to the LCT. This protects NE information against leakage and tampering.
8.2.4 Log Management
The operations performed by all users on NEs and the operation results are
recorded in logs. Log management involves setting, viewing, and deleting logs
(including command logs, user logs, and EMU logs). Users can learn operations
performed in the OTNM2000 via logs, and analyze network faults based on logs.
Common log management operations are described as follows:
u Filtering command logs.
u Viewing filtering status of command logs.
u Viewing command logs, user logs, and EMU logs.
u Viewing reported events.
u Deleting command logs, user logs, and EMU logs.
Version: B 8-9
9 Technical Specification
The following lists the technical specifications and safety standards compliance of
the CiTRANS R860, and includes these contents.
System Technical Specification
System Performance Specification
Mechanical Dimension and Power Consumption
Performance Specification of Interface
Clock Specification
EMC / EMI Specification
Applicable Safety Standard
Environment Requirement
Version: B 9-1
9.1 System Technical Specification
Table 9-1 lists the technical specifications of the CiTRANS R860.
Table 9-1 System Technical Specifications
Item Specification
Subrack dimensions (H x W x D) (mm) 923 × 448 × 248

Subrack weight (kg) 25.9
Power consumption in full configuration (W) 1040
Power consumption in typical configuration (W) 640
DC voltage (V) -40 and -57
9.2 System Performance Specification
Table 9-2 lists the system performance specifications of the CiTRANS R860.
Table 9-2 The CiTRANS R860 System Performance Specification
Item Specification
Packet loss of Ethernet services in 24 hours No packet loss in 24 hours
Number of supported PWs 16k

Number of supported LSPs 8k unidirectional
Number of supported VLANs in a single PW 4095
Tunnel 1:1 protection < 50 ms
VPN FRR protection < 50 ms
MPLS TE FRR protection < 50 ms
Protection LDP FRR protection < 50 ms
switching time IP FRR protection < 50 ms
PW redundancy protection < 50 ms
VRRP (Virtual Router
< 200 ms
Redundancy Protection)
Switchover performance of cards (SCUR1, Switchover performed normally without

SCUR2, RCUO1) configured with 1+1 protection influencing services
Quantity of supported CES services 8k

Quantity of supported E-Line services 8k
Quantity of supported E-LAN VSIs 1023
9-2 Version: B
Table 9-2 The System Performance Specification (Continued)
Item Specification
Quantity of supported E-Tree services 1023

Maximum number of visual ports supported by
256
each VSI
Quantity of supported MAC addresses 128k
Quantity of VLAN instances supported by a port /
4k / 16k / 32k
a card / the equipment
CAR / Shaping granularity 64 kbit/s (rate granularity)
Quantity of CARs supported by the equipment 2k

A maximum of 8k multicast groups
Quantity of multicast supported by the equipment
A maximum of 512k multicast members
SAToP and CESoP modes are supported.
The two encapsulation modes
CES performance for E1 and STM-1 services
respectively comply with RFC 4553 and
RFC 5086.
A maximum of 10 directions for each slot
MCC access capability A maximum of 120 directions for the
system
Synchronization status message (SSM) SSM byte information of 24 interface

management ability directions
System SCUR1 320 Gbit/s
switching
SCUR2 360 Gbit/s
capability
8 links can be added to an aggregation

Ethernet link aggregation
link
Number of BGP peers Not less than 1k
Number of entries of an IPv4 routing table 260k at maximum
1k VRFs are supported (one VRF
Maximum number of VRF routes
supports 256k route entries)
Each slot can extract any 2 channels of

Clock distribution
clock
VLAN subinterface 32k/system
MPLS-TP OAM: 2046

Number of OAM entries
BFD OAM: 2k
Version: B 9-3
9.3 Mechanical Dimension and Power

Consumption
Dimensions and weight of the cabinet of the CiTRANS R860 are shown in Table 9-3.
Table 9-3 Dimensions and Weight of the CiTRANS R860 Cabinet
Cabinet Type Dimension (H × W × D) (mm) Weight (kg)
2000 × 600 × 300 61

21-inch cabinet 2200 × 600 × 300 71
2600 × 600 × 300 76
Dimensions and weight of the CiTRANS R860 subrack are shown in Table 9-4.
Table 9-4 Dimensions and Weight of the CiTRANS R860 Subrack
Item Specification
Dimension (H × W × D) (mm) 923 × 448 × 248

Weight of an empty subrack (kg) 25.9
Note:
For details about the power consumption of the entire , see System
Technical Specification.
Table 9-5lists the dimensions, weight, and power consumption of the cards and fan
unit of the CiTRANS R860.
Table 9-5 Dimensions, Weight, and Power Consumption of Cards and Fan Unit of the
CiTRANS R860
Card Name Dimension (H × W × D) (mm) Weight (kg) Power Consumption (W)
RCUO1 370 × 210 × 30 0.93 20

SCUR1 370 × 210 × 30 1.17 48
SCUR2 370 × 210 × 30 2 140
AIF1 370 × 150 × 30 0.78 2.7
AIF2 370 × 150 × 30 0.78 2.7
XSR1 370 × 210 × 30 1.05 64
XSR2 370 × 210 × 30 1.575 72
GSR1 370 × 210 × 30 1.08 60
9-4 Version: B
Table 9-5 Dimensions, Weight, and Power Consumption of Cards and Fan Unit of the
(Continued)
Card Name Dimension (H × W × D) (mm) Weight (kg) Power Consumption (W)
XGR1 370 × 210 × 30 1.125 68

ESR1 370 × 210 × 30 1.5 120
ESJ1 370 × 150 × 30 0.6 18
ESJ2 370 × 150 × 30 0.6 18
S1J4 370 × 150 × 30 0.7 35
S1J2 370 × 150 × 30 0.63 40
E1J2 370 × 150 × 30 1.4 13.6
Fan unit – 1 18
9.4 Performance Specification of Interface
The following lists the performance specifications of the CiTRANS R860 interfaces.
9.4.1 Technical Specification of XGE Interface
Table 9-6 lists the technical specifications of XGE interfaces.
Table 9-6 Technical Specifications of XGE Interfaces
Item Specification
Optical interface type 10GBASE (10 km) 10GBASE (40 km) 10GBASE (80 km)
Transmission distance (km) 10 40 80

Transmitted optical power
-6 and -1 -1 and 2 0 and 4
(dBm)
Center wavelength (nm) 1290 and 1330 1530 and 1565 1530 and 1565
Overload optical power
-1 0 -7
(dBm)
Receiving sensitivity (dBm) -14 -17 -24

Extinction ratio (dB) 6 8.2 9
9.4.2 Technical Specification of GE Interface
Table 9-7 lists the technical specifications of the GE interfaces.
Version: B 9-5
Table 9-7 Technical Specifications of GE Interfaces
Item Specification
1000BASE- 1000BASE-
Optical interface type 1000BASE-SX 1000BASE-LX 1000BASE-VX
ZX1 ZX2
Transmission distance
0.55 10 40 80 100
(km)
Source type MLM MLM SLM SLM SLM

Mean launched power
-9.5 to 0 -8 to -3 -2 to 3 -2 to 5 -2 to 5
(dBm)
Center wavelength (nm) 770 and 860 1270 to 1355 1270 to 1350 1500 to 1580 1500 to 1580
0 -3 -3 -3 -9
(dBm)
Receiving sensitivity
-17 -20 -23 -23 -31
(dBm)
Extinction ratio (dB) 9 9 9 9 9
9.4.3 Technical Specification of STM-1 Interface
Table 9-8 lists the technical specifications of STM-1 interfaces.
Table 9-8 Technical Specifications of STM-1 Interfaces
Item Specification
Nominal bit rate (kbit/s) 155 520

Application code S-1.1 L-1.1 L-1.2
Operating wavelength (nm) 1265 to 1360 1265 to 1360 1480 to 1580
Target distance (km) 15 40 80
Maximum RMS width (s:nm) 7.7 3 -
Maximum -20 dB spectrum width (nm) - - 1

Minimum side mode suppression ratio
- - 30
(dB)
Maximum average transmit power (dBm) -8 0 0

Minimum mean launched power (dBm) -14 -4 -4
Minimum extinction ratio (dB) 8.5 10.5 10.5
Minimum sensibility (dBm)
Note 1 -31 -37 -37
Minimum overload point (dBm) -8 -10 -10
9-6 Version: B
Table 9-8 Technical Specifications of STM-1 Interfaces (Continued)
Item Specification
Maximum optical channel cost (dB) 1 1 1

Note 1: Minimum sensibility refers to the sensibility of the receiver when its service life ends.
Therefore, the sensibility of the receiver must be 3 dB higher than the minimum
sensibility.
9.4.4 Technical Specification of E1 Interface
Table 9-9 lists the technical specifications of E1 interfaces.
Table 9-9 Technical Specifications of E1 Interfaces
Item Specification
Nominal bit rate (kbit/s) 2048

Bit rate accuracy (ppm) ±50
Code HDB3
All marks of a valid signal must conform with the
Pulse type (nominal rectangular)
mask in ITU-T Rec. G.703 irrespective of the sign.
Pair in each direction A coaxial pair A symmetric pair
Test load resistance (Ω) 75 120

Nominal peak voltage for marking pulse
2.37 3
(V)
Nominal peak voltage for spacing pulse

0 ± 0.237 0 ± 0.3
(V)
Nominal pulse width (ns) 244

Ratio of the amplitudes of positive and
negative pulses at the center of a pulse 0.95 to 1.05
interval
Ratio of the widths of positive and negative
0.95 to 1.05
pulses at the nominal half amplitude
Jitter at input and output interfaces ITU-T Rec. G.823 compliant
Frequency range:
Return loss at the output port (dB) (51 kHz to 102 kHz) ≥ 6 dB
(102 kHz to 3072 kHz) ≥ 8 dB
Version: B 9-7
Table 9-9 Technical Specifications of E1 Interfaces (Continued)
Item Specification
Frequency range:
(51 kHz to 102 kHz) ≥ 12 dB
Return loss at the input port (dB)
(102 kHz to 2048 kHz) ≥ 18 dB
(2048 kHz to 3072 kHz) ≥ 14 dB
Input attenuation (dB) 0 to 6 (1024 kHz)
9.4.5 Technical Specification of FE Interface
Table 9-10 lists the technical specifications of the FE interfaces.
Table 9-10 Technical Specifications of FE Interfaces
Item Specification
100BASE-FX (2 100BASE-FX (15 100BASE-FX (40

Optical interface type
km) km) km, 70 km)
Source type MLM SLM SLM

Transmitted optical power
-20 and -14 -20 and -14 -4 and 0
(dBm)
Center wavelength (nm) 1270 and 1380 1270 and 1340 1290 and 1330
-14 -14 -15
(dBm)
Receiving sensitivity (dBm) -31 -31 -37

Extinction ratio (dB) 10 10 10
9.5 Clock Specification

Specifications of Clock Interfaces
The CiTRANS R860 provides interfaces for external clock input and output.
Table 9-11 lists the specifications of the clock interfaces.
9-8 Version: B
Table 9-11 Specifications of Clock Interfaces
Clock Type Specification
Two 75Ω 2048 kbit/s or 2048 kHz inputs

External clock synchronization source
Two 120Ω 2048 kbit/s or 2048 kHz inputs
Two 75Ω 2048 kbit/s or 2048 kHz outputs

Synchronous output clock
Two 120Ω 2048 kbit/s or 2048 kHz outputs
Two TOD time inputs

External time synchronization source
Two PPS time inputs
Two TOD time outputs

Synchronous output time
Two PPS time outputs
Timing and Synchronization Specifications
u Frequency accuracy
Under free-running conditions, the output frequency accuracy is greater than

4.6 ppm.
u Pull-in and pull-out ranges
Both the minimum pull-in and pull-out ranges are ±4.6 ppm.
u Wander in the locked mode
Table 9-12 and Table 9-13 list the wander specifications of the clock in the
locked mode.
Table 9-12 Wander Generation (MTIE) with Constant Temperature
MTIE Observation Interval (t:s)
40 ns 0.1 ＜ t ≤1
0.1
40t ns 1 ＜ t ≤ 100
25.25t ns0.2
100 ＜ t ≤ 1000
Table 9-13 Wander Generation (TDEV) with Constant Temperature
TDEV Observation Interval (t:s)
3.2 ns 0.1＜ t ≤ 25
0.5
0.64t ns 25 ＜ t ≤ 100
6.4 ns 100 ＜ t ≤ 1000
Version: B 9-9
9.6 EMC / EMI Specification
The applicable EMC / EMI standards of the CiTRANS R860 are shown in
Table 9-14.
Table 9-14 Applicable EMC / EMI Standards and Protocols of the CiTRANS R860
Standard / Protocol
Title
Number
Electromagnetic compatibility and Radio spectrum Matters (ERM);
ETSI EN 300 386 Telecommunication network equipment; Electromagnetic
Compatibility (EMC) requirements

EN 55022
EN55024
Electromagnetic compatibility (EMC) - Part 4-2: Electrostatic
EN 61000-4-2
discharge immunity test

EN 61000-4-3 measurement techniques-Radiated, radio-frequency, electromagnetic
field immunity test

EN 61000-4-4
measurement techniques-Electrical fast transient/burst immunity test

EN 61000-4-5
measurement techniques-Surge immunity test

EN 61000-4-6 measurement techniques-Immunity to conducted disturbances,
induced by radio-frequency fields

CISPR 22
CISPR 24
Resistibility of telecommunication equipment installed in a
ITU-T K.20
telecommunications centre to overvoltages and overcurrents
Resistibility of Telecommunication Equipment installed in Customer

ITU-T K.21
Premises to Overvoltages and Overcurrents
ITU-T K.43 Immunity requirements for telecommunication equipment
Resistibility of telecommunication equipment to overvoltages and

ITU-T K.44
overcurrents
9-10 Version: B
9.7 Applicable Safety Standard
Table 9-15 lists the applicable safety standards of the CiTRANS R860.
Table 9-15 Safety Standards

Safety of laser products-Part 1: Equipment classification and
EN 60825-1
requirements
EN 60825-2 Safety of laser products-Part 2: Safety of optical fibre communication
Information technology equipment–Safety–Part 1: General

EN 60950-1
Requirements
Safety of laser products–Part1: Equipment classification and

IEC 60825-1
requirements
IEC 60825-2 Safety of laser products–Part 2: Safety of optical fibre communication
Safety of Information technology equipment including Electrical

IEC 60950
Business Equipment
Information Technology Equipment–Safety–Part 1: General

UL 60950-1
Requirements
9.8 Environment Requirement
The following lists the specifications of the storage environment, operating

environment, and transport environment of the CiTRANS R860.
9.8.1 Storage Environment
u Avoid water seeper and leakage in the storage place.
u Keep the package intact.
u Avoid direct sunlight.
u Avoid damage on the equipment from rodents (such as rats).
9.8.2 Operating Environment
u Ground bearing of the equipment room: ＞600 kg/m2.
Version: B 9-11
u No corrosive and solvent gas, and no dust in the atmosphere; no strong

electromagnetic field nearby.
u Power supply: Can provide steady voltage, and an accumulator of certain

capacitance is equipped.
u Grounding resistance: < 5 Ω.
u Temperature and relative humidity requirements:
4 Guaranteed temperature range: 5℃ to 40℃.
4 Operating temperature: 0℃ to 45℃.
4 Guaranteed relative humidity range: 10% to 85% (30℃).
4 Operational relative humidity range: 5% to 90% (30℃).
u Avoid damage on the equipment from rodents (such as rats).
9.8.3 Transport Environment
u The equipment set is covered with a plastic film, and its top, middle and bottom
parts are wrapped with shock proof packing foam. A wooden case is used for
outside package.
u The equipment set can be transported via vehicles like coaches, trains, ships,
and airplanes.
u Temperature range during transportation is: -20℃ to 60℃.
u Avoid severe collision, fall, rain, and direct sunlight.
9-12 Version: B
Appendix A Abbreviations
AC Attachment Circuit
ACL Access Control List
APS Automatic Protection Switching
ARP Address Resolution Protocol

AS Autonomous System
ASON Automatically Switched Optical Network
ATM Asynchronous Transfer Mode
BC Boundary Clock
BDR Backup Designated Router
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
BITS Building Integrated Timing Supply
BMC Best Master Clock

BMU Board Management Unit
BPDU Bridge Protocol Data Unit
BSC Base Station Controller

CAR Committed Access Rate
CBS Committed Burst Size
CE Custom Edge
CES Circuit Emulation Service

CFM Connectivity Fault Management
CIR Committed Information Rate

CLV Code Length Value
CRC Cyclic Redundancy Check
CSNP Complete Serial Number Packet
CSPF Constrained Shortest Path First

CV Connectivity Verification
DCN Data Communication Network

DDF Digital Distribution Frame
DDN Digital Data Network
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Services

DIS Designated Intermediate System
Version: B A-1
DoS Denial of Service

DR Designated Router
DSCP Differentiated Services Code Point

DTE Data Terminating Entity
E2ETC End-to-end Transparent Clock
EBGP External Border Gateway Protocol
ECMP Equal-Cost Multi-Path
EFM Ethernet in the First Mile

EMC Electromagnetic Compatibility
EMI Electromagnetic Interference
EVC Ethernet Virtual Connection

FC Fiber Channel
FE Fast Ethernet
FEC Forwarding Equivalence Class
FIB Forwarding Information Base
FPGA Field Programmable Gate Array
FR Frame Relay
FRR Fast Reroute

GE Gigabit Ethernet
GR Graceful Restart
GRE Generic Routing Encapsulation
GPS Global Positioning System
GUI Graphical User Interface
HoVPN Hierarchy of VPN
IBGP Internal Border Gateway Protocol
IC Integrated Circuit
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IGP Interior Gateway Protocol
IP Internet Protocol
IPSec Internet Protocol Security
IPTV Internet Protocol Television

IPv4 Internet Protocol Version 4
IPv6 Internet Protocol Version 6
IS Intermediate System
IS-IS Intermediate System to Intermediate System
ISP Internet Service Provider
A-2 Version: B
ITU International Telecommunication Union

International Telecommunication Union- Telecommunication
ITU-T
Standardization Sector
IVL Independent VLAN Learning
L2VPN Layer 2 Virtual Private Network
L3VPN Layer 3 Virtual Private Network
LACP Link Aggregation Control Protocol
LAG Link Aggregation Group
LDP Label Distribution Protocol

LSDB Link State Database
LSP Label Switched Path
LSP Link State Packet
LSR Label Switching Router
LTE Long Term Evolution
MA Maintenance Association
MAC Media Access Control
MC-LAG Multi-chassis Link Aggregation Group
MD Maintenance Domain
MDF Main Distribution Frame
MEF Metro Ethernet Forum
MEN Metro Ethernet Network
MEP Maintenance End Point
MIMO Multiple-Input and Multiple-Out-put
MIP Maintenance Intermediate Point

MME Mobility Management Entity
MP-BGP Multiprotocol Extensions for BGP-4
MPLS Multiprotocol Label Switching
MPLS-TP Multiprotocol Label Switching Transport Profile
MPLS TE Multiprotocol Label Switching Traffic Engineering
MS-PW Multi-Segment Pseudo-Wire
MSTP Multi-Service Transport Platform
MTU Maximum Transmission Unit

NPE Network Provider Edge
NSF None Stop Forwarding
NTP Network Time Protocol

OAM Operation, Administration and Maintenance
OC Ordinary Clock
Version: B A-3
ODF Optical Distribution Frame
OFDM Orthogonal Frequency Division Multiplex
OSI Open Systems Interconnection
OSPF Open Shortest Path First
P2PTC Peer-to-peer Transparent Clock
PBS Peak Burst Size

PDP Power Distribution Panel
PE Operator Edge
PHB Per-Hop Behavior
PHP Penultimate Hop Popping
PIR Peak Information Rate

PPPoE Point-to-Point Protocol over Ethernet
PSNP Partial Serial Number Packet
PTN Packet Transport Network
PTP Precision Time Protocol

PW Pseudo Wire
PWE3 Emulation Edge-to-Edge
QinQ 802.1Q In 802.1Q / Double VLAN

QoS Quality of Service
RAN Radio Access Network

RD Route Distinguisher
RIP Routing Information Protocol
RIPng RIP Next Generation

RNC Radio Network Controller
RSVP Resource Reservation Protocol
RTP Real-time Transport Protocol
SDH Synchronous Digital Hierarchy
SFP Small Form-Factor Pluggable
SGW Signaling Gateway
SN Serial Number
SNCP Sub-network Connection Protection
SNP Serial Number Packet
SONET Synchronous Optical Network
SP Strict Priority
SPF Shortest Path First

SR Service Router
SSM Synchronization Status Message
A-4 Version: B
STM Synchronous Transport Module
SVL Shared VLAN Learning
TC Transparent Clock
TDM Time Division Multiplexing
TPID Tag Protocol Identifier
TPS Tributary Protection Switching
UPS Uninterruptible Power Supply
URPF Unicast Reverse Path Forwarding
UPE User-Facing Provider Edge
VC Virtual Channel
VC Virtual Circuit
VLAN Virtual Local Area Network
VPLS Virtual Private LAN Service
VPN Virtual Private Network
VPRN Virtual Private Routing Network
VPWS Virtual Private Wire Service

VRRP Virtual Router Redundancy Protocol
WFQ Weighted Fair Queuing
WRED Weighted Random Early Detection
XFP 10-Gigabit Small Form-factor Pluggable
Version: B A-5
Product Documentation Customer Satisfaction Survery
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
□ Frequently □ Rarely □ Never □ Other (please specify)
2. When do you use the documentation?
□ in starting up a project □ in installing the product □ in daily maintenance □ in trouble
shooting □ Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
□ 100% □ 80% □ 50% □ 0% □ Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
□ Satisfied □ Unsatisfied (your advice)
5. Which documentation form do you prefer?
□ Print edition □ Electronic edition □ Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
□ Very □ Somewhat □ Not at all (your advice)
2. How do you like the language style of the documentation?
□ Good □ Normal □ Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
□ Yes
□ No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
□ Yes
□ No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
□ Yes (Please give an example)
□ No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with?Why?
9. What is your opinion on the Figures in the documentation?
□ Beautiful □ Unbeautiful (your advice)
□ Practical □ Unpractical (your advice)
10. What is your opinion on the layout of the documentation?

□ Beautiful □ Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com.cn

Manual para Referencia R860

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Manual para Referencia R860

Hochgeladen von

Copyright:

Verfügbare Formate

CiTRANS R860

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our goal.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

No part of this document (including the electronic version) may be

CiTRANS R860 Multi-Service Introduces functions and features, protection mechanisms,

CiTRANS R860 Multi-Service Gives a detailed introduction to commissioning

Gives a detailed description of items and procedures of

Gives a detailed introduction to troubleshooting

CiTRANS R860 Multi-Service

This manual is intended for the following readers:

u Operation and maintenance engineers

To utilize this manual, these prerequisite skills are necessary:

u Router related technology

u Data communication technology

FiberHome CiTRANS R860 Multi-Service Convergence

RCUO1 Routing and Control Card

SCUR1 Cross-connect Clock Card

S1J2 STM-1 Optical Interface Card (2 channels)

S1J4 STM-1 Optical Interface Card (8 channels)

E1J2 E1 Interface Card

AIFJ2 Power and Auxiliary Terminal Board 2

Symbol Refer to Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Warning May cause severe bodily injuries.

➔ Jump Jumps to another step.

Related Documentation ...................................................................................I

Intended Readers ..........................................................................................III

1.1 Architecture ...................................................................................1-2

1.1.1 Overview .........................................................................1-2

1.2 Network Application .......................................................................1-5

1.2.1 Product Positioning..........................................................1-5

2.1 Routing and Switching Capability ...................................................2-2

2.2 Service Type and Access Capability...............................................2-2

2.2.1 Service Type....................................................................2-2

2.3 Interface Type................................................................................2-3

2.3.1 Service Interface..............................................................2-3

2.4 Protection Capability ......................................................................2-5

2.4.1 Equipment-Level Protection .............................................2-5

2.5 Carrier-Class Network Management...............................................2-6

2.5.1 Support to Centralized Configuration Management...........2-7

2.6 Monitoring and Maintenance Function ..........................................2-10

2.6.1 Card Self-Booting ..........................................................2-11

3.1.1 Introduction to QoS ..........................................................3-2

3.2.1 Introduction to OAM .........................................................3-5

3.3 Clock Feature ................................................................................3-9

3.3.1 Clock Signal Synchronization...........................................3-9

3.4 VPN Feature................................................................................3-18

3.4.1 Introduction to VPN........................................................3-18

3.5 Applicable EMC / EMI and Safety Standard and Protocol..............3-24

4 Dynamic Routing .........................................................................................4-1

4.1 Overview .......................................................................................4-2

4.3 OSPF Protocol...............................................................................4-3

4.4 IS-IS Protocol ................................................................................4-7

4.6 IPv6 Dynamic Routing Protocol....................................................4-15

4.7 RSVP ..........................................................................................4-17

5 Product Architecture ....................................................................................5-1

5.1 Logical Structure............................................................................5-2

5.2 Hardware Structure........................................................................5-4