ECC Protocol Stack (IP)

2014.11.01
Davood Salehi
Contents

 ECC Basic Principle

 IP Region Partition and Networking
 ECC debugging commands
 Fault Handling Method of ECC
 Networking Structure
 > Internal Only

Definition of ECC Protocol Stack

 ECC is the abbreviation of Embedded Control Cha
nnel.

 In general, ECC is a group of the communication p

rotocol stacks, which are built on the DCC channel
composed of the byte D of SDH.

 ECC is used to implement the communication am

ong NEs.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Function of ECC Protocol Stack

 Connect to all NEs in the SDH
subnet and provide the comm
SMCC
unication protection.
Qx
 The ECC protocol stack is us
NE
ed to implement the communi
ECC ECC
cation among NEs and of the
most complicated and core te NE NE
chnology in the SDH NMS.
ECC ECC

ECC
NE NE

© ZTE Corporation. All rights

reserved.
 > Internal Only

Basic Principle of ECC Protocol

 The technical proposal of the ECC communication for
the ZTE SDH equipment complies with the ITU-T G.77
12 standard and takes the industry leading thinking of
IP over DCC. Hence, each NE shall be configured wit
h one IP address at least. Taking the valuable IP addr
ess space into account, we remove the traditional fixe
d length subnet mask (FLSM) coding mode, and take t
he variable length subnet mask (VLSM) coding mode
and classless inter-domain routing (CIDR) technology.
Hence, there is not any traditional concept of the addr
ess class in our ECC protocol stack, and the address
class may be generated by any combination of the IP
address and the subnet mask.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Classification of ECC Protocol Stack

 Types of ECC:

 OSI: Open System Interconnect, Seven layer hierarchy.

Complicated, low efficiency, high price.
 TCP/IP: Transfer Control Protocol/Internet Protocol, Main
stream technology for the SDH ECC.
 UDP: User Datagram Protocol, Suitable for the simplified
SDH network.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Classification of ECC Protocol Stack

 Advantage of OSI Protocol:
 The ISO/OSI standard model is an international standard,
which plays a role in guiding the global network structure a
nd the open system routing and is supported by several go
vernment and non-governmental organization (NGO). Its eff
ect is self-evident.

 Disadvantage of OSI Protocol:

 The protocol suite is huge and overall, so its efficiency is rat
her low.
 The protocol is too complicated and hard to implement.
 The optional commercial protocol stack is less and high pric
e.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Classification of ECC Protocol Stack

 Advantage of TCP/IP Protocol:
 Provide broad inclusiveness. TCP/IP almost supports all LAN car
ds and various types of networks with different medias, and almos
t covers all types of computers.
 The scope of application and scale for the TCP/IP protocol is wide
r and there are a large number of the standard software, develop
ment tools and simulation environments, as well as abundant liter
atures for the reference.
 Related to the protocol of the OSI system, the TCP/IP protocol is
simple and practical, and the network technology of the TCP/IP pr
otocol affects several standards to be implemented by the TCP/IP
protocol suite.
 Disadvantage of TCP/IP Protocol:
 It doesn’t comply with the international standard and there is som
e potential hazard in terms of the security.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Classification of ECC Protocol Stack

 Introduction to TCP/IP Protocol:
 Implementation Structure:

Layer Service and Protocol

Application Layer Application program (SNMP/CORBA)
Transport Layer TCP or UDP
Network Layer IP + OSPF + Static Route Configuration
ECC
Data Link Layer PPP Protocol
Physical Layer DCC SDH DCC (D1- D3/D1- D12)

© ZTE Corporation. All rights

reserved.
 > Internal Only

Classification of ECC Protocol Stack

 Introduction to TCP/IP Protocol:
 Key Related Technologies:
1. IP Protocol
Forwarding the packet by looking up the route table (impleme
nted by the operating system, BSD4.3) (refer to RFC791).
2. OSPF Protocol
Implement the neighbor detection, route calculation and route
convergence and generate the route table information require
d to forward the IP protocol (refer to RFC2328).
3. PPP Protocol
It is the PPP link layer protocol, which is used to negotiate the
parameters with the neighbor points, obtain the IP address at
the opposite end and control the link quality (refer to RFC154
8).
© ZTE Corporation. All rights
reserved.
 > Internal Only

Classification of ECC Protocol Stack

 Advantage of UDP Protocol:
 It is shorter development cycle, less development cost, si
mple protocol, and applicable for the SDH network with si
mple networking and network node.

 Disadvantage of UDP Protocol:

 The protocol is not perfect, can not interconnect with the
equipments of other manufacturers or meet the protocol
standard of ITU-T, and it is hard to carry out the admissio
n test.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Classification of ECC Protocol Stack

 The ECC protocol stack of the ZTE transmissio
n products includes two main stages as follows
:

 UDP Protocol (original protocol stack)

 TCP/IP Protocol Stack (New protocol stack)

© ZTE Corporation. All rights

reserved.
 > Internal Only

Classification of ECC Protocol Stack

original static configuration

UDP
protocol stack route mode Two protocol stack can
not interconnect with
new protocol dynamic route each other
TCP/IP
stack protocol (OSPF)

© ZTE Corporation. All rights

reserved.
 > Internal Only

Classification of ECC Protocol Stack

 The TCP/IP protocol stack can implement the automatic
detection and protection of the route and adapt to the dyn
amic change of the network topology. It is basically not n
ecessary to be interfered by the network management sy
stem, and can provide abundant debugging and mainten
ance means. Its disadvantage is the uncertainty of the ro
ute, which is closely related to the stability of the network
planning and the lower layer link. Hence, this protocol is
applicable for network size is large, the network topology
changes frequently and the lower layer link is rather stabl
e.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Classification of ECC Protocol Stack

 The advantage of the private ECC protocol stack is its st
atic route, which is basically not affected by the change o
f the network topology and the stability of the lower layer l
ink, while its fatal disadvantage is that it can not applicabl
e for the change of the network topology, and it is require
d to configure the route table of the whole network again
once the network topology changes. Hence, this protocol
is applicable for the network whose size is small (the NEs
in one subnet don’t exceed 64), the network topology is s
table and the lower layer link is poor.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 In-Band Mode:
 DCC overhead in the SDH optical card

 Out-Band Mode:
 Timeslot in 2M
- Optical interface E1
- Electrical interface E1
 Ethernet

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 In-Band Mode:
 DCC (Data Communication Channel):
For the optical transmission equipment of ZTE company,
one segment from the optical board 186-processor to the
FPGA CMOS chip is defined as the DCC segment.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 In-Band Mode:
 DCC (Data Communication Channel):
Architecture of ECC Communication Module

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 In-Band Mode:
 DCC Overhead Bytes of Optical/Electric Board for SD
H:
One STM-N frame has two DCC channels:

Bytes Locate in Rate Name

D1 to D3 RSOH 192 kbps (3 x 64kbps) DCC(R)
D4 to D12 MSOH 576 kbps (9 x 64kbps) DCC(M)

DCC(R) can access regenerator stations and terminal sta

tions, while DCC(M) is channel for network management
information between terminal stations.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Channel Structure:
A1 A1 A1 A2 A2 A2 J0
RSOH B1 E1 F1
D1 D2 D3
AU - PTR

9 Rows
B2 B2 B2 K1 K2
D4 D5 D6

MSOH D7 D8 D9
D10 D11 D12
S1 M1 E2
9 bytes
© ZTE Corporation. All rights
reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Channel Structure:

 DCC Channel Hardware Structure:

Inside each NE, the ECC function module relates to two
boards, one is the NCP board, another is the optical boa
rd. These two boards are connected with each other via
bus.
In NCP board, the network management information, pr
otocol maintenance information of link layer and OSPF r
oute protocol information will be stored and transmitted t
hrough the 186-processor in the optical board to realize
the “loading” from ECC information to DCC byte. Finally,
FPGA will embed the information in SDH frame.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Channel Structure:

 DCC Channel Software Structure:

At present, ZTE company uses two types of protocols: p
rivate protocol and TCP/IP protocol. The main protocols
include:

1) IP Protocol:
Use IP protocol to realize data packet forwarding by find
ing route list. (Operation system realization, BSD4.3); (P
lease refer to RFC791)

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Channel Structure:

 DCC Channel Software Structure:

2) OSPF Protocol:
Realize neighbor discovery, route calculation and route
aggregation to make the route table information needed
by IP protocol forwarding (Please refer to RFC2328). Su
pport two kinds of network types: Peer to Peer type (opti
cal ECC mode), Broadcast type (network interface ECC
mode);

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Channel Structure:

 DCC Channel Software Structure:

3) PPP Protocol:
Peer to Peer link layer protocol realizes the parameters
realization negotiation with the neighbor point, link qualit
y control function and IP address allocation of the optica
l board.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Channel Structure:

 DCC Channel Software Structure:

Layer Service and Protocol

Application Layer Application program (SNMP/CORBA)
Transport Layer TCP or UDP
Network Layer IP + OSPF + Static Route Configuration
ECC
Data Link Layer PPP Protocol
Physical Layer DCC SDH DCC (D1- D3/D1- D12)

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 DCC Overhead Byte of Optical/Electric Board for
SDH (In-band Mode)

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 2M Time Slot (Out-band Mode):
 The ECC port may be of the PPP or bus mode, and the
ECC module of the 2M board (or the service 2 of the opt
ical/electric board) may be implemented by the software
or FPGA.
 At present, the ZXMP S200 equipment can provide the
2M time slot to transmit the ECC protocol.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Channel of ECC Protocol Stack

 Ethernet (Out-band Mode):

 Connect the NEs by the Ethernet, which uses the Ether

net protocol.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 ECC (Embedded Control Channel):

1) For the optical transmission equipment of ZTE compa

ny, ECC channel extension is defined as one segment fr
om the NCP to the optical board 186-processor.
2) ECC uses DCC as its physics layer to provide the lo
gic channel between SDH NEs.
3) Detect if the ECC channel is clear according to the c
ommand “eping + optical board slot number + optical po
rt number”.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 EMS (NE Management System):
SDH network management in NE layer is in charge of th
e SDH NE.

 SMS (Sub-net Management System):

SDH management sub-net, is composed of a series of u
nattached SDH ECC and relevant data communication li
nks inside the station.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 Q Interface:
Include Q3 interface and Qx interface. It can connect th
e different network management entities.

 Access NE:
Be directly connected with the EMS server. There is one
access NE in a SMS, which is connected with the EMS.
The EMS server needs to bind an IP address in the sam
e network segment with the NE.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 Gateway NE:
Be directly connected with DCN or EMS and realize the
data transmission function between other NEs and the
EMS in communication course.

 Non-Gateway NE:
A non-Gateway NE needs the Gateway NE to realize th
e data transmission function in communication with the
EMS, and is not directly connected with DCN or EMS.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 Backbone Area:
The region id number is 192. Region partition is a syste
matism route selection technique. The link status chang
e inside the area will not influence other areas. This tech
nique is good for reducing the quantity of route computi
ng information, route list and link update load.

 Non-Backbone Area:
The region ID number is non-192, that is, 1~223. The tr
ansmission of the EMS information between Non-backb
one regions must be realized by transmission of backbo
ne region.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 Border NE:
It is the backbone NE, which across connects backbone
region and non-backbone region at the same time.

 NAT (Network Address Transform):

When “inner” network of the private (preserved) address
transmits the data packet via router, the private address
will be transformed into the legal IP address.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 DCN (Data Communication Network):
DCN is the medium connecting Manager and Agent to r
ealize the remote EMS server supervision.

 Manager System:
Manager system, composed of a father Manager proces
s and several sub Manager processes, is a NE manage
ment system. By communicating and cooperating with e
ach other, it realizes the following functions: transmitting
NE settings commands, accepting NE alarm, collecting
performance, and so on.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Term Explanation
 Agent:

NE NCP Board. The relevant management system trans

mits the commands, the executive result will be returned
to the relevant EMS.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Communication Flow between EMS and NE

 EMS → NE:
For the EMS data, there are three times of unpacking processe
s to finish one-way communication from the EMS to the NE.
(1) EMS Unpacking:
the EMS Server processes TCP unpacking based on the Ether
net bus format, and transmits the data grouping to NCP;

(2) NCP Unpacking:

After processed on NCP by IP/OSPF protocol, firstly, the releva
nt optical board PPP channel is selected, and then the grouping
packets are unpacked for the second time based on the HDLC
bus demands and transmitted to 186-processor of the optical b
oard.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Communication Flow between EMS and NE

 EMS → NE:

(3) Optical Board Unpacking:

The optical board unpacks the packets for the third time based
on storage and forwarding demands and transmits the data gro
uping from 186-processor of the optical board to FPGA.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Communication Flow between EMS and NE

 NE → EMS:
For the EMS data, there are three times of packing processes t
o finish one-way communication from the NE to the EMS:

(1) Optical Board Packing:

The optical board FPGA receives the data grouping and packs t
he data in grouping for the first time based on storage and forw
arding demands, and then transmits data to 186-processor of th
e optical board;

© ZTE Corporation. All rights

reserved.
 > Internal Only

Communication Flow between EMS and NE

 NE → EMS:

(2) NCP Packing:

The data grouping is packed for the second time based on the
HDLC bus demands, and transmitted from the 186-processor to
the NCP board. The NCP board PPP protocol receives the data
and sends them to IP layer. After be processed by IP and route
protocol, the IP grouping continuous transmission or putting in d
ata to EMS TCP layer will be selected according to the situation.

(3) EMS Packing:

The TCP layer data is packed for the third time by the NCP boar
d and transmitted to the EMS.

© ZTE Corporation. All rights

reserved.
Contents

 ECC Basic Principle

 IP Region Partition and Networking
 ECC debugging commands
 Fault Handling Method of ECC
 Networking Structure
 > Internal Only

IP Region Partition and Networking

 Why IP Region Partition is important?
 In one subnet, because of limitation of route table space
and route information processing capability in NCP, it is
required that, in one NE, the summation of the route insi
de region, the route between regions, the external route
and the optical interface route can not exceed 128.
 With expansion of network scale, because of limitation o
f the NCP board memory, the route table and the interfa
ce amount in NE, the NE amount in one subnet must be
controlled, and the IP region partition must be processe
d to make a rational allocation of NE.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC capacity and design

 Area ID design:

 The elements with “192” area ID and also the links betw
een two elements (Area ID=192) are called the backbon
e area.
 The elements with “193~223” area ID and also the links
between two elements (Area ID=193~223) are called th
e none backbone area.
 The inter-section elements between the backbone area
and none backbone area are called “boundary element
s”. The boundary elements are both the backbone area
elements and none backbone area elements.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC capacity and design

 Area ID design:

 The elements in the same area can communicate each

other.
 The elements in the backbone area can communicate wi
th the elements in the connected none backbone area.
 The elements in the different none backbone area cann
ot communicate each other directly, even they are conn
ected, but they can communicate each other via backbo
ne area.
 In the whole network, area ID must be unique and in on
e area every components (elements and links) must be
connected.
© ZTE Corporation. All rights
reserved.
 > Internal Only

ECC capacity and design

 Area ID design:

 For the backbone area elements, the quantities of all the ba

ckbone area elements and all the none-backbone area shou
ld not exceed 128.
 For the boundary elements, the quantities of all the backbon
e area elements, all the none-backbone area and the conne
cted none backbone area elements should not exceed 128.
 For the none backbone area elements, the quantities of all t
he none backbone area elements and all the AREA should n
ot exceed 128.
 All these rules for the Area ID assignment are based on the
OSPF protocol.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC capacity and design

 How to Divide IP Areas:

 All areas must be connected to the backbone area and the connection points a
re called border NEs.
 A border NE should directly connect with as few non-backbone areas as possib
le, and preferably with only one. For a border NE, the total number of non-back
bone areas it connects directly plus all NEs in the backbone area shall not exc
eed 128.
 All NEs in the same area must be interconnected.
 The ECCs of non-backbone areas cannot directly interoperate with one anothe
r, but via the backbone area instead. Hence, we should try to keep the ECC ch
annels, which can be protected originally, when selecting the backbone area a
nd the border NEs. In other words, ECC protection should better be implement
ed inside the area.
 Do not set too many NEs in the backbone area and too many border NEs, bec
ause area division would be meaningless if there are too many NEs in the back
bone area and the relations between areas would be complex if there are too
many border NEs.
© ZTE Corporation. All rights
reserved.
 > Internal Only

ECC capacity and design

 Area ID design:
 Example: 192

200

193 201 199

194 202 198

195 203 197

196
192 Backbone Area: 202 ， 203
193 Area: 192 ， 193 ， 194 ， 198 ， 199 ， 200 ，
201
194 Area: 195 ， 196 ， 197
© ZTE Corporation. All rights
reserved.
Host IP and Route Setting of NMS
 > Internal Only

ECC capacity and design

 EMS computer Setting:

 Route add 0.0.0.0 mask 0.0.0.0 193.1.1.18 -p

 Static route: route add 193.1.0.0 mask 255.255.0.0 193.
1.1.18 -p
 Delete route: route delete 193.1.0.0 mask 255.255.255.
0 193.1.1.18
 View route: route print

© ZTE Corporation. All rights

reserved.
 > Internal Only

IP Region Partition and Networking

 IP Region Partition Principle:
 According to the characteristic of the OSPF protocol, wh
en the NE amount in the subnet is more than 64, it is su
ggested to divide these NEs into the different regions to
obtain the steady and better performance. If the NE am
ount in the subnet is more than 128, the region partition
must be executed.
 The ECCs in non-backbone region can not communicat
e with each other. The interworking non-backbone regio
ns must be connected with their own backbone regions.
In backbone region, the NE directly connecting with no
n-backbone region is known as the border NE.

© ZTE Corporation. All rights

reserved.
 > Internal Only

IP Region Partition and Networking

 IP Region Partition Principle:
 The amount of the NEs in backbone region and the bord
er NEs is suggested no more than 64. Each border NE t
ries to make the few direct connections with non-backbo
ne region. All the NE amount in the connected non-back
bone region plus the NE amount in backbone region ca
n not exceed 128.
 Each NE in the same region must be connected with ea
ch other (no cross connection), and can not be separate
d into the several independent parts, otherwise, the NE
will break away from the EMS. So the ECC protection ro
ute must be considered during settings of the backbone
regions and the non-backbone regions.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Definition of Network Address for NEs

 IP Address Calculation:
 The 4-Byte IP address includes the area ID, NE ID and
single board ID in the following format:
IP: (Byte1) . (Byte2) . (Byte3) . (Byte4)
MASK: 255 . (Byte2) . (Byte3) . 0
Example: 192.1.1.18 Mask: 255.255.0.0

 The (Byte1) is composed of the area ID, the (Byte 2) an

d part of the (Byte 3) form the NE ID, and the remaining
address bit and the (Byte 4) forms the single board ID.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Definition of Network Address for NEs

 IP Address Calculation:
 Corresponding to IP address: The area ID plus the NE I
D is equal to the network ID, and the single board ID is t
he host ID. (When mask bit is 1, the corresponding IP b
yte is the network number; when mask bit is 0, the corre
sponding IP byte is the host number).

 Area ID value is 1 ~ 223, and the area of corresponding

OSPF is 1 ~ 223. It is suggested that the NEs of the sa
me area ID don’t exceed 64, and it shall not exceed 128
at most. 192 is the backbone area, and others are the n
on-backbone area. In general, it is suggested to use 19
3 ~ 201 for the non-backbone area.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Definition of Network Address for NEs

 IP Address Calculation:
 Corresponding to IP address: The area ID plus the NE I
D is equal to the network ID, and the single board ID is t
he host ID. (When mask bit is 1, the corresponding IP b
yte is the network number; when mask bit is 0, the corre
sponding IP byte is the host number).

© ZTE Corporation. All rights

reserved.
 > Internal Only

Definition of Network Address for NEs

 Definition of Area ID:
 The byte 1 of the network address indicates the NE affili
ated area, whose value is 1 ~ 223, and the area of corre
sponding OSPF is 1 ~ 223. It is suggested that the NES
of the same area ID don’t exceed 64, and it shall not ex
ceed 128 at most. 192 is the backbone area, and others
are the non-backbone area. In general, it is suggested t
o use 193 ~ 201 for the non-backbone area.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Definition of Network Address for NEs

 Definition of NE ID:
 The byte 2 and byte 3 of the NE address form the NE ID
after the AND operation with corresponding bytes of the
address mask. Each NE shall correspond to an unique
NE in the same area.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Definition of Network Address for NEs

 Definition of Single Board ID:
 The byte 2, 3 and 4 of the NE address form the single b
oard ID after the AND operation with the base-minus-on
e's complement of corresponding bytes for the address
mask. The single board ID is assigned to various single
boards in NE. The NCP board shall be defined explicitly,
and other single boards may be allocated automatically
according to the single board ID of NCP. The single boar
d ID in different NEs may be repeated.
 At present, the single board ID is only valid for the singl
e board related to the ECC channel, such as the NCP b
oard and the optical board.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Definition of Network Address for NEs

 Definition of Single Board ID:
 The single board ID and its related byte 4 of the network
address are specified as follows:
1) The NCP board ID shall be greater than 9 and less th
an 100. It is suggested to take 18 uniformly.
2) The host ID of NMS is 1 – 9, and it is suggested to st
art with 1 uniformly.
Doing so is to prevent the repetition of the address betw
een some single board and the network management h
ost in the same NE.
 Note that the address of the single board shall not be re
peated with that of the network management host.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Definition of Network Address for NEs

 Definition of Single Board ID:

 In an area, every NE must have a unique NE ID.

 Each board in an NE is allocated with a board ID. The b

oard ID of the NCP board should be defined and that of
other boards are automatically allocated according to th
e NCP board ID.
NCP board number same with Host Number and its def
ault value is 18.
NCP can assign the corresponding IP to every optical in
terface based NCP IP address.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Definition of Network Address for NEs

 Definition of Single Board ID:

 Description of the board ID:

The board ID of a board is roughly defined as follows:
[(Byte4) + (Board address -1)x4+(Optical port No.)]
Example:
First Port of OL64 board located in slot 6:
(NCP IP is 193.1.3.18)
18 + (6-1) x4 +1 =39  IP: 193.1.3.39
At present, the board ID is effective only for the NCP bo
ard, the optical boards and the other boards related to t
he ECC channel.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Physical Link Supported by ECC Protocol

At present, the physical layer of the ECC protocol supports t
wo modes.
1) Optical fiber connection (DCC channel)
2) Network cable connection (Ethernet)

For the optical fiber connection is of the serial port mode (W

AN), the IP address of two NEs connected shall not be of th
e same subnet (it shall not be the same after the IP address
is AND with the IP subnet mask). For the network cable con
nection is of the Ethernet mode (LAN), the IP address of tw
o NEs connected shall be of the same subnet (it shall be th
e same after the IP address is AND with the IP subnet mas
k).
© ZTE Corporation. All rights
reserved.
 > Internal Only

Physical Link Supported by ECC Protocol

For this connection mode, two

connection For this connection mode, only one connection
modes may take effect. mode may take effect.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Link Supported by ECC Protocol

 The following considerations shall be noted when you u
se the network cable to connect with two NEs by the hu
b:
 1. The IP address of two NEs connected shall be of the
same subnet. If there are two NEs, it is suggested to set
the last bit of the IP address as 18 and 133 respectively.
 2. When there are several NEs connected by the netwo
rk cable, for example, you hope to interconnect ten NEs
from 192.1.1.18 to 192.1.10.18 by the network cable, it
may be changed as follows: change the address code fr
om 192.1.1.18 to 192.1.10.18 and the subnet mask as 2
55.255.0.0.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Physical Link Supported by ECC Protocol

 3) Two NEs with different subnet masks can not intercon
nect with each other.

 3)SSS It is not related to the MAC address when they ar

e connected by the optical fiber for the protocol is of the
routing mode, and the MAC address shall not be repeat
ed when they are connected by the network cable for th
e protocol is of the broadcasting mode.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:

 Optical ECC mode:

DCC overhead in the SDH optical card (in-band)

 Timeslot in 2M (in-band)
 Optical interface E1
 Electrical interface E1

 Network interface ECC mode: Ethernet (out band)

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:
 ECC out-band method:
The Qx interfaces of two NEs directly are connected wit
h each other.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:

 ECC in-band physical channel realization method1:

Through the optical interface connection, the DCC physi
cal transportation channel is constructed. The addressin
g method which uses OSPF protocol is in-band mode.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:
 ECC in-band physical channel realization method1:

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:

 ECC in-band physical channel realization method2:

S200 provides two communication modes: E1-optical int
erface ECC, E1-electrical interface ECC, using four 2M
(the No.5-No.8 way of main board 2M interface) to trans
mit the ECC information separately in four directions.
By FPGA process, E1 signal is disassembled into 64Kbi
t/s, and three 64kbps time slots of the equipment tributa
ry board 2Mbps signal are used to transmit DCCr inform
ation.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:

 ECC in-band physical channel realization method2:

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC protocol Basis Principle

 ECC Realization Mode:

 ECC in-band physical channel realization method2:

© ZTE Corporation. All rights

reserved.
 > Internal Only

Networking Structure
 Nowadays, there are two networking structure
s applied widely in real project:

 one networking uses the access NE

 another networking uses the gateway NE.

© ZTE Corporation. All rights

reserved.
Contents

 ECC Basic Principle

 IP Region Partition and Networking
 ECC debugging commands
 Fault Handling Method of ECC
 Networking Structure
 > Internal Only

ECC debugging commands

 When the ECC is not connected, you can locate t
he fault or help to analyze the fault finely by a seri
es of the ECC debug commands.

 Types of commands:
 Common view commands
 Common testing commands
 Common setting commands
 Common Commands on Network Management Comput
er

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 The common view commands include help, ifconf
ig, ppptable, sccinfo, route, arp, netstat, show fec
, ds, sid, a-getreset, ecfg, memstat, show mem, s
how al, qxinfo and date:
 ZTE provide “telnet” session to log in remote elements.
 User name: zte
 Password: ecc

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 help:

 Function: View all the possible commands that can be u

sed in the telnet session.
 Command: help<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 date:

 Function: View NCP Time

 Command: date

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 ifconfig

 Function: View which ports establish the connection.

 Command: ifconfig –a or if –a<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 ifconfig:

 OSPF Protocol support two kinds of network types:

Point to Point (Optical ECC mode)
Broadcast type (Network interface ECC mode

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 Ifconfig:
For examlpe:
 1, 2, 3, 4 and 37 indicate the sequence number of all po

rts for this NE.

 The port 1 indicates Ethernet.

 The port 2, 3 and 4 indicate the serial port (the optical p

ort or electric port, correspond to the channel PPP0, PP

P1 and PPP2).
 The port 37 indicates the local loopback address.

 Whether POINTTOPOINT and UP indicate the PPP prot

ocol has been run, and the port has been enabled (nam
ely, the PPP connection is established with the opposite
end).
© ZTE Corporation. All rights
reserved.
 > Internal Only

Common view commands

 Ifconfig:
For examlpe:
 If the port address at current terminal is the same as tha

t at the opposite terminal, it indicates the receiving termi

nal of this port is connected with the transmitting termin
al (namely, the port is looped back). You can usually det
ect the port by the loopback of the port. If there is not a
ny UP, it indicates the PPP port is not enabled, and the
connection of the PPP channel is not established.

 For the new version of ECC, this command can also be

used to query the MAC address of the NCP board (in th
e red box).
© ZTE Corporation. All rights
reserved.
 > Internal Only

Common view commands

 ppptable:

 Function: view the configuration table of the port

 Command: ppptable<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 ppptable:
For example:
 PPP0, PPP1 and PPP2 indicate the created PPP channel

(corresponding sequence number of ports are 2, 3 and 4 re

spectively), the receiving and transmitting address of HDL
C indicates the slot ID of the optical board or other corresp
onding processing boards, and the receiving and transmitti
ng address of HDLC indicates corresponding port ID of the
optical board or other processing boards.
 In general, the receiving address of HDLC is the same as t

hat of the transmitting address. However, it is different for t

he trunk. The status indicates whether this channel is disab
led (0 indicates enabled and 1 indicates disabled).

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 ppptable:
For example:
 In general, the ifconfig and ppptable command are com

bined with each other for the use.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 sccinfo:

 Function: View NCP ECC channel sending and receivin

g packets.
 Command: sccinfo <Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 sccinfo:
For example:
 Channel: The logical channel ID, whose corresponding r

elationship with the single board may be viewed by the p

pptable command.
 tx_packets: The counting of packets transmitted correctl

y.
 tx_dropped: The counting of packets discarded actively

after the waiting for sending is timeout.

 tx_errors: The counting of packets transmitted incorrectl

y.
 rx_packets: The counting of packets received correctly.

 rx_errors: The counting of packets received incorrectly.

© ZTE Corporation. All rights
reserved.
 > Internal Only

Common view commands

 sccinfo:
For example:
 Note: If some channel fails to receive and transmit the d

ata, there may be some fault for corresponding ECC pro

cessing single board of this channel. You can view the c
orresponding relationship between the PPP channel and
the single board by the ppptable command.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 route:

 Function: view route table of the NCP board

 Command: route or route –a<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 route:

 127.0.0.1 indicates the route of the local loopback.

 192.0.0.0 and 195.0.0.0 indicate the convergence route
of the region 192 and 195.
 193.193.0.0, 193.193.198.0 and 193.193.199.0 indicate
the network route of the internal region 193.
 193.193.199.43 and 193.193.201.44 indicate the route o
f the port. In general, there shall be the route to this net
work if there is the route to the port.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 arp:

 Function: Used to view the MAC address of the network

management computer connected with the Qx port by th
is NCP board
 Command: route or arp –a<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 arp:

As shown in the figure:

 It indicates four network management computers are co

nnected with the Qx port by this NCP board, whose MA

C addresses are shown in the figure above respectively
(in the red box).

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common view commands

 show fec:

 Function: The IP address and MAC address of this NCP.

 Command: show fec<Enter>

© ZTE Corporation. All rights

reserved.
 Internal use only ▲

Qxinfo Command

Purpose of command: View the IP address of the network ma

nagement system connected with the NE, the connection stat
e and the cause for the latest disconnection.
Format of command: qxinfo n (n=0,1……15)
 Internal use only ▲

A-getreset Command (S385)

Purpose of command: View the software reset or hardware reset of the NCP board and other single board.
Format of command: a-getreset subrack ID, slot ID, CPU ID or a-get-reset all
ResetType:
There are three reset types, 1 is the hardware reset, 2 is the software reset and 3 is other reset.
Time: The time for the reset.
S320 command to query the reset information: GetReset slot ID
 Internal use only ▲

Ecfg Command

Purpose of command: View the regional configuration.

The network port part is the configuration of the network port, which is the IP
address of the network interface, subnet mask and the network interface regi
on ID in turn.
The optical port part is the configuration of various optical ports, the BoardAd
dr is the slot ID of the optical board, Port is the optical port ID, the IP Address
is the IP address of the configured optical port, and AreaID is the regional ID
of the optical interface. It will be displayed in turn if there are several configur
ed records.
Format of command: ecfg -a
 > Internal Only

Common testing commands

 The common test command includes ping, eping
and sping:

 ZTE provide “telnet” session to log in remote elements.

 User name: zte
 Password: ecc

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 ping:

 Function: test PPP channel stability (test ECC stability)

 Command: ping or ping –s host [count/timeout]<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 eping:

 Function:
Realize the “ping” command in the ECC interface to test
the fiber loopback, the outer loopback at 186-side, the 8
60 self-loop stability and on-off status. (Test ECC stabilit
y)

 Command Format:
eping (Slot Number) (Interface Number) [Data Length
Number of Times Overtime]; <Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 eping:

 Example:

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 eping:

 Example:
In some case, we want to check the ECC part of optical
board, so we can loopback the optical port by fiber, use
the command eping to check it.
telnet IP address of NE, input eping command, the epin
g command format is: eping McuAddr Port Length Time
s Timeout.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 eping:

 Example:

As shown in the above, the result is 'Request timed out',

So there is some problem in optical board or loopback fi
ber.
© ZTE Corporation. All rights
reserved.
 > Internal Only

Common testing commands

 eping:

 Example:

As shown in the above, the result is OK, So the optical b

oard is Ok.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 eping:

 Example:

In order to test the No.1 port of the optical board in No.2

slot, we can extend the eping time.
For example: eping 2 1 100 100 500.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 sping:

 Function: test s interface stability

 Command: sping host [shelf No.] [slot No.] [cpu No.]<E
nter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing commands

 tracert:

 Function: Trace the current route to the destination

 Command: tracert host<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 The common setting commands include enablep
pp, disableppp, sccreset, sccclose, commreset a
nd ecfg:

 ZTE provide “telnet” session to log in remote elements.

 User name: zte
 Password: ecc

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 enableppp:

 Function: Used to enable some PPP port

 Command: enableppp [slot No.] [Port No.]<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 disableppp:

 Function: Used to disable some PPP port

 Command: disableppp [slot No.] [Port No.]<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 disableppp:

 Disable the PPP port of this slot ID and the port ID firstly
, and then set the enable status of the PPP port as 1. Yo
u can not enable this PPP port automatically or manuall
y unless you enable this port by enableppp.
 This function is mainly used when it is connected with th
e equipments of other companies, for the communicatio
n protocol among NEs for various companies may not b
e different. To prevent the ECC information of other equi
pments from having unnecessary effect on our system, i
t is necessary to disable this port.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 sccclose:

 Function: close all the PPP channel

 Command: sccclose<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 sccreset:

 Function: reset all the PPP channels

 Command: sccreset<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting commands

 commreset:

 Function: Reset the MCU communication module

 Command: commreset [shelf No.] [slot No.] [CPU No.]
[Communication Flag]<Enter>
Remark: Communication Flag “1” is the “s” interface; “2”
is the “ECC”

© ZTE Corporation. All rights

reserved.
 Internal use only ▲

Ecfg Command

Purpose of command: Configure the region ID of NE.

Format of command: ecfg -ne
Input NE Area ID[0.0.0.0] : input the information of the area ID. Input Start
Optical Port IP address[0.0.0.0] : Configure the start IP address of the opti
cal interface.
On completion of the configuration, save the configuration and reset the N
CP board to enable the configuration to take effect.
 > Internal Only

Common View Commands on NM Computer

 The common view commands on Network Manag
ement Computer include the route print and the a
rp -a:

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common View Commands on NM Computer

 route print:

 Function: Query the route table on the computer (includi

ng the permanent route).
 Command: route print <Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common viewing Commands on NM Compute

r
 route print:

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common viewing Commands on NM Compute

r
 Arp -a:

 Function: Query the MAC address of all devices which a

re of the same network segment as this computer (inclu
ding the computer and the transmission equipment).
 Command: arp -a<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common viewing Commands on NM Compute

r
 Arp -a:

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common testing Commands on NM Computer

 ping:

 Function: test connection stability

 Command: ping host [count/timeout]<Enter>

 Tracert:

 Function: used to trace the route

 Command: tracert –d<Enter>

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common setting Commands on NM Computer

 route add:

 Function: add the route

 Command: route add “destination” mask “subnetmask”

“gateway ip” <Enter>

Example: route add 10.10.10.0 mask 255.255.255.0 192.1
68.1.12 -p

 route delete:

 Function: delete the route

 Command: route delete “destination” <Enter>
© ZTE Corporation. All rights
reserved.
Contents

 ECC Basic Principle

 IP Region Partition and Networking
 ECC debugging commands
 Fault Handling Method of ECC
 Networking Structure
 > Internal Only

Common View Commands on NM Compute

r
 ECC Trouble Shooting Method

 The appearance of ECC trouble is that the NE cannot b

e managed. The fault caused by ECC mainly indicates t
he NE can not be monitored.
 Firstly, we can use “ping” and “tracert” to find out where
is the problem.
 Then, we can use “telnet” to log in to the NE, and take r
elated command for the query, so as to determine the c
ause for fault and perform related operation.

© ZTE Corporation. All rights

reserved.
 > Internal Only

Common View Commands on NM Compute

r
 ECC Trouble Shooting Method
 Ping the packet and observe the status of ECC.
 Use the ping and tracert command to judge which two N
Es that the ECC fault takes place roughly.
 Telnet element and use “route –a”, “if –a”, “ppptable” or t
he other command to view the route. Finally find out the
faulty card.
 Use “sccinfo” command to view the communication bet
ween NCP and optical line card.
 Reset NCP, or use “commreset” to reset ECC module. T
ry to recover the trouble.
 If necessary, we should also reset the optical line card.
(This operation will possibly affect the traffics.)
© ZTE Corporation. All rights
reserved.
 > Internal Only

Common View Commands on NM Compute

r
 Common ECC Fault

 The NE is out of control, but can ping normally.

 The NE is out of control, and can not ping normally.
 The NE is out of control to a large extent.

© ZTE Corporation. All rights

reserved.
Contents

 ECC Basic Principle

 IP Region Partition and Networking
 ECC debugging commands
 Fault Handling Method of ECC
 Networking Structure
 > Internal Only

Networking Structure
 EMS Access Mode:

 EMS Direct Connection Mode

 DCN remote access mode
 dedicated line access mode

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise1:
 Problem:
Improper Partition of IP Domain Causes NE Out of Cont
rol. Only one of the “193” Area can be managed.

EMS

A B
192

C D

193 193

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise1:
 Issue Description:
The area A and B are of the backbone domain 192, and
the area C and D are of the network segment 193. The
network segment 193 is of the backbone domain 192 re
spectively. During the monitoring of the network manage
ment, two network segments 193 in the area C and D c
an not be monitored at the same time.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise1:
 Fault Analysis:
The OSPF protocol requires various NEs of the same ar
ea be connected with each other, but not connected cro
ss the area. Under this situation, the network managem
ent system can only find one of the routes to two areas
193 for the calculation of the route. Furthermore, there i
s some uncertainty of the route according to the status o
f current network, which is indicated that the network se
gment of the area C and D can not be monitored at the
same time.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise1:
 Solution 1: Connect with two domains 193.

EMS

A B
192

C D

193 193

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise1:
 Solution 2: Change one domain into the network segme
nt 194.

EMS

A B
192

C D

193 194

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise2:
 Problem:
Management of Multi-Address Domain Network. EMS c
an manage only 193 Area elements but cannot manage
194 Area elements.

EMS C

A
7 8 9 1 01 11 2

1 2 3 4 5 6
7x

1x
8x

2x
9x

3x
A
10 x

4x
11 x

5x
1 2x

6x
7x

1x
8x

2x
9x

3x
B
10 x

4x
11 x

5x
1 2x

6x
E t h er n e t

A
D E
B
193 194

C F © ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise2:
 Issue Description:
The network management system (NMS) manages the do
main 193 and 194 at the same time, and the start address
of various NEs are 193.1 and 194.1 respectively, the acce
ss NE are A and D respectively, and corresponding IP are
193.1.1.18 and 194.1.1.18. Add two IP address 193.1.1.1
and 194.1.1.1 on the computer, and set the default gatew
ay as 193.1.1.18, and then make use of the route add 194
.1.0.0 mask 255.255.0.0 194.1.1.18 command to add the
static route. After the equipment room is moved, it is dete
cted that NMS can only monitor the network segment 193
and the NE D. However, the service of the network segme
nt 194 is not affected.
© ZTE Corporation. All rights
reserved.
 > Internal Only

ECC Exercise
 Exercise2:
 Fault Analysis:
The service of the network segment 194 is not affected.
Hence, it is doubled that there is some problem for ECC
.
Use the route print command to query current route tabl
e on NMS, and it detects that the route to the network s
egment is lost for the route add 194.1.0.0 mask 255.255
.0.0 194.1.1.18 is the temporary command, and the add
ed route will lose during the restart of the computer.

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise2:
 Solution:
Take the permanent route add command, to reserve the
memory with the parameter–p.
route add 194.1.0.0 mask 255.255.0.0 194.1.1.18 –p

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise3:
 Problem:
Management Problem Caused by Multi-network Merge.
Before connect these two networks together, there is no
management problem. But after connection, some of th
e elements can not be managed.
B E

A 193 193 D
C F

EMS1 EMS2

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise3:
 Issue Description:
For the requirement of service, we merge two networks
before and after the expansion. We detect there is the
monitoring problem for the network after the merging, a
nd part of NEs can not be monitored.

© ZTE Corporation. All rights

reserved.
 Internal use only ▲

Fault Analysis:
View related configuration, and we detect the IP address of
partial NEs in two domains 193 are the same, which affects
the monitoring of NMS.

Solution:
We take the DCC shield command or disable the ECC port
of the optical board in NMS for the interface NE C and F of
two networks, to meet the requirement to isolate ECC
information of two networks.
 Internal use only ▲

NE Out-of-control Caused by Repetiti

on of MAC Address

　 Issue Description:
When you take Hub, NMS can only control one of the NE A, B, C
and D. When you take the direct connection of the cross network
cable, there is not any problem for the monitoring of various NEs
.
 > Internal Only

ECC Exercise
 Exercise4:
 Problem:
When you take Hub, NMS can only control one of the N
E A, B, C and D. When you take the direct connection of
the cross network cable, there is not any problem for the
monitoring of various NEs.

© ZTE Corporation. All rights

reserved.
 Internal use only ▲

Fault Analysis:
Above information indicates there is mutual affected factor fo
r equipments to affect the monitoring, so it is necessary to ex
amine the MAC address directly. Make use of the ECC com
mand arp to detect the repetition.

Solution:
Change the MAC address of various NEs into different
addresses, to solve this problem.
 Internal use only ▲

Management of NE for Complicated Networking

　 Network Description: The network is composed of five areas, such

as 192, 193, 194, 195 and 196, and the network management computer
is connected with the backbone area 192. The IP of the access NE is 19
2.1.1.18.
 Internal use only ▲

(1) Out-of-control of All NEs in Area 193

 Internal use only ▲

Fault Analysis:
(1) Telnet 192.1.3.18 to log in to the backbone domain NE connected with
193 according to the configuration information of current network, and t
hen use if –a and sccinfo to view the lower layer link. The result is norm
al.
(2) Use route –a to view whether there is the route of NE in the area 193 fo
r the route table.
(3) Select some NE in the area 193, and the ping command will be timeout
.
(4) For tracert –d 193.1.9.18, it will be timeout when it reaches the NE 192.
1.4.18.
(5) When you use telnet 192.1.4.18 to log in to this NE, use the if –a comm
and to detect one address whose IP is 193.1.11.19 connected with it, a
nd then use the route –a command to detect the route that reaches 193
.1.11.0.
Solution:
The query result is that the same non-backbone area is connected by the
backbone area. Change one of the IP as the network segment 192, to solve
the problem.
 Internal use only ▲

(2) Part of NEs are out of control in the area 193, and the out-of-contr
ol NEs 193.1.3.18, 193.1.4.18, 193.1.5.18, 193.1.6.18, 193.1.7.18, 19
3.1.8.18 and 193.1.10.18.
 Internal use only ▲

Fault Analysis:
(1) Use the telnet 193.1.2.18 command to log in to the neighbor NE, and us
e the if –a, sccinfo and ping –s command to detect the information of the
neighbor NE is normal, as well as use the route –a command to demons
trate there is the route to 193.1.3.0.
(2) Use the ping 193.1.3.18 command to detect the timeout, but not unreac
hable. It describes the ping packet to reach the NE 193.1.3.18, but no p
acket is returned.
(3) Use the tracert -d 193.1.3.18 command to detect it will be timeout when i
t tracerts the 193.1.2.18.
(4) Combined with the symmetry of the position characteristics for the out-o
f-control NE, you can confirm that the NE 193.1.4.18 is hung with one N
E in the area 192. 　

Solution:
The IP of NE is not set properly, which causes the problem in the partition of
the area. Change the IP of the NE in the figure into the area 193, to solve the
problem.
 Internal use only ▲

(3) Out-of-control for Part of NEs in Area 194

 Internal use only ▲

Fault Analysis:
The OSPF protocol requires various NEs in the same area shall
be connected, but not be connected cross areas. The optical fib
er broken causes above problem.

Solution:
If the IP area is not partitioned properly, it may cause the same
non-backbone area is connected by the backbone area when
the optical fiber is broken. You can add the static route for the
monitoring when the broken optical fiber is restored.
 > Internal Only

ECC Exercise
 Exercise4:
 Problem:
A is access element, EMS can manage all the other ele
ments except B.

EMS A B D

© ZTE Corporation. All rights

reserved.
 > Internal Only

ECC Exercise
 Exercise4:
 Problem:
EMS can only manage one of the A,B,C and D when we
connect EMS to the element one by one. All the element
can be managed respectively.
net1
A

B net2
EMS
7x 8 x 9 x 1 0x x
1 2 x
1 7x 8x 9x 0 x 1 1x 1 2
1 x
C
7 8
9 1
0 1 2

A 1 2
3 4 5 6
1x 2 x 3 x A4 x x
5 6x 1x 2x 3x B 4 x 5 x x
6

C net3
E th ern et

D
net4

© ZTE Corporation. All rights

reserved.
 Thanks!

© ZTE Corporation. All rights reserved.