Packet Transport Network Equipment Commissioning Guide

ZXCTN 6500
Packet Transport Network Equipment

Commissioning Guide
Version: V1.00.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2015-01-30 First edition.
Serial Number: SJ-20130301144038-013
Publishing Date: 2015-01-30 (R1.0)
SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

About This Manual
Purpose
This manual describes how to debug the ZXCTN6500 equipment after the hardware and
software are installed.
Intended Readers
This manual is intended for:
l Installation engineers
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters and appendix.
Chapter Summary
Chapter 1, Debugging Describes the procedure for debugging the ZXCTN6500 equipment.
Process Diagram
Chapter 2, Debugging Describes how to prepare the tools and data that are required for
Preparation debugging the ZXCTN6500.
Chapter 3, Debugging Describes how to debug access NEs.

Access NEs
Chapter 4, Interconnection Describes how to debug non-access NEs.

Debugging
Chapter 5, Basic Describes the data that must be configured after equipment
Configuration debugging.
Chapter 6, DCN Describes how to optimize the DCN data.

Performance Optimization
Chapter 7, Debugging Describes how to verify the debugging results.

Result Verification
Appendix, Debugging Provides knowledge on debugging the ZXCTN6500 equipment.

Knowledge
Conventions
This manual uses the following conventions.

Typeface Meaning
Danger: indicates an imminently hazardous situation. Failure to comply can result in

death or serious injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result in

serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.
II

Contents
About This Manual ......................................................................................... I
Chapter 1 Debugging Process Diagram................................................... 1-1
Chapter 2 Debugging Preparation ............................................................ 2-1
Chapter 3 Debugging Access NEs............................................................ 3-1
3.1 (Optional) Loading the ZXCTN6500 Software....................................................... 3-1
3.2 Configuring an Access NE Through Command Lines............................................ 3-4
3.3 Configuring Access NEs on the EMS ................................................................... 3-9
3.3.1 Logging In to the EMS Client..................................................................... 3-9
3.3.2 Creating an Access NE........................................................................... 3-10
3.3.3 Uploading the Database ..........................................................................3-11
3.3.4 Configuring Boards................................................................................. 3-12
Chapter 4 Interconnection Debugging ..................................................... 4-1

4.1 DCN+MCC ........................................................................................................ 4-1
4.2 Pure DCN .......................................................................................................... 4-3
Chapter 5 Basic Configuration.................................................................. 5-1

5.1 Configuring a Loopback Interface ........................................................................ 5-1
5.1.1 Configuring a Loopback Interface Through the GUI .................................... 5-1
5.1.2 Configuring a Loopback Interface Through the CLI ..................................... 5-2
5.2 Configuring an L3 Interface ................................................................................. 5-2
5.2.1 Configuring an L3 Interface Through the GUI ............................................. 5-2
5.2.2 Configuring an L3 Interface Through the CLI .............................................. 5-3
5.3 (Optional) Configuring a Subinterface .................................................................. 5-4
5.3.1 Configuring a Subinterface Through the GUI .............................................. 5-4
5.3.2 Configuring a Subinterface Through the CLI............................................... 5-5
5.4 Configuring an ARP Entry ................................................................................... 5-5
5.4.1 Configuring an ARP Entry Through the GUI ............................................... 5-5
5.4.2 Configuring an ARP Entry Through the CLI ................................................ 5-7
Chapter 6 DCN Performance Optimization .............................................. 6-1

Chapter 7 Debugging Result Verification................................................. 7-1
7.1 Checking Interface Status ................................................................................... 7-1
7.2 Checking Optical Power...................................................................................... 7-2
7.3 Checking Network Management Monitoring Channels .......................................... 7-3

Chapter 8 Debugging Knowledge ............................................................. 8-1
8.1 Monitoring Schemes........................................................................................... 8-1
8.2 DCN Port Area Migration Rules........................................................................... 8-2
8.3 File Structure in Debugging OAM Mode ............................................................... 8-2
8.4 Clearing Configuration Data ................................................................................ 8-2
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II

Chapter 1
Debugging Process Diagram
Figure 1-1 shows the process for debugging the ZXCTN6500 equipment.
Figure 1-1 Debugging Process Diagram
1-1

ZXCTN 6500 Commissioning Guide
This page intentionally left blank.
1-2

Chapter 2
Debugging Preparation
You should make the following preparations before debugging the equipment.
Important Safety Precautions

l Wear an electrostatic discharge wrist strap when you maintain devices (store, install,
and unpack the equipment).
l Do not touch the components, wires, or connector pins of the board that you remove
or install.
l Keep components that are not in use in an antistatic bag.
l There must not be food packaging materials, plastic, or polystyrene foam, which are
prone to generate static electricity, near the components and parts.
For a description of the requirements for operation safety, refer to Table 2-1.
Table 2-1 Operation Safety Requirements
Operation Requirements
Removing and installing The power board does not support hot swapping, and it cannot be removed
a power board or plugged when the system is powered on.
Never plug or remove a power board with the power cable attached. You
must insert the power board and then connect the power cable, or unplug
the power cable and then remove the power board.
Equipment grounding l The cabinet and subrack cover are properly grounded.
requirements l The grounding cable of the cabinet is connected to the grounding
copper bar of the equipment room.
l Subracks are secured to the rear columns of the cabinet.
l Boards are connected to the equipment cover through front panels.
There is no electrical connection in the boards.
Other safety l Never block the vents when the system is operating.
requirements l A proper tool must be used to tighten screws when you install a front
panel.
l The operations for debugging a device must not affect other online
devices.
Collecting Equipment Information

Before debugging the equipment, you should collect the equipment information with
reference to Table 2-2.
2-1

Table 2-2 Equipment Information
Item Description
General l Project time requirements

project l User requirements
information l Equipment installation and interconnection
l Equipment software version and EMS version
NE planning Network topology diagram

information
Service requirements
Monitoring The ZXCTN6500 supports monitoring on DCN or Ethernet.

planning l DCN: DCN is applicable to the system that has only the
DCN. The monitoring VLAN does not need to be planned
(default: VLAN　4094), but the DCN management IP address
and route need to be planned. The default management IP
address of version V1.00.10R1 is 2.0.0.0, and that of version
V1.00.10R2 is 0.0.0.0.
l Ethernet: The Ethernet is applicable to the system that has
both the DCN and MCC. The interface VLAN and IP address
need to be planned.
IP address Only the directly-connected IP addresses between ZXCTN

planning equipment need to be planned. For an access NE, the IP address
of Qx interface needs to be planned.
NE interface All the ZXCTN6500 interfaces are layer-3 interfaces. The IP

planning addresses are configured under the interfaces. They are similar
to router interfaces.
Loopback The loopback addresses are the same as the MNG IP addresses.
address
Preparing Debugging Tools

Prepare the following tools and meters, and the meters must be calibrated by the national
metrology department.
l Notebook computer where the data comprehensive test platform is installed.
l Serial port cable for the equipment. If the serial port cable for the notebook computer
is not available, an adapter for converting USB to serial port is required.
l Communication tools: Phillips screwdrivers, straight screwdrivers, diagonal pliers,
sharp-nose pliers, wire stripper, crimping pliers, antistatic wrist straps, and fiber
pigtails.
l Meters: optical power meter, ground resistance tester, multimeter, Spirent-9000A, and
IXIA data tester.
2-2

Chapter 3
Debugging Access NEs
Table of Contents
(Optional) Loading the ZXCTN6500 Software.............................................................3-1
Configuring an Access NE Through Command Lines .................................................3-4
Configuring Access NEs on the EMS..........................................................................3-9
3.1 (Optional) Loading the ZXCTN6500 Software

If the ZXCTN6500 program files do not exist when the equipment is started for the first
time, the program files need to be loaded when the equipment is booted. If the program
files exist, you can skip this step.
Step 1 Configure the FTP server on the PC.
Step 2 Connect the PC to the ZXCTN6500 equipment.
Step 3 Start the ZXCTN6500 equipment and set the boot parameters.
1. Configure the FTP server on the PC.

Configure the FTP Server on the PC. The Xlight FTP Server is recommended. The
Xlight FTP Server can operate on multiple operating systems, such as Windows XP,
server 2000, server 2003, and Windows 7. 3CDaemon can be used on Windows 7.
Caution!
Do not use WFTPD for uploading the program files. It may fail to be started.
a. Start Xlight FTP Server. Click . The user list window is displayed.
b. In the window displaying the user list, click from the right menu. The user
information dialog box is displayed.
c. Enter the user name (upp), password (upp), and the main directory in the dialog
box, and click OK.
2. Connect the PC and the ZXCTN6500 equipment.
Connect the PC and the ZXCTN6500 equipment, see Figure 3-1.
3-1

Figure 3-1 PC and ZXCTN6500 Equipment Connection Diagram
l The Console port is located on the main control board. For the 6500-8, the main
control board is the NCPSA board on slot 13 or slot 14. For the 6500-16L, the
main control board is the NCPA board on slot 39 or 40. For the 6500-32, the main
control board is the NCPB board on slot 13 or 14.
l The default address of the LCT port is 1.1.1.18/24. The LCT port of the PC and the
ZXCTN6500 belong to the same network segment. For example, the IP address
of the PC is set to 1.1.1.1/24.
3. Start the ZXCTN6500 equipment and set the boot parameters.
a. Power on the ZXCTN6500 equipment.
When the equipment is started, the equipment writes the program files into the
verset directory of the main control board. The names of the program files are
the same as the names saved in the FTP Server. The ZXCTN6500 automatically
completes synchronization between the active main control board and the standby
main control board. The ZXCTN6500 sets the startup mode to local startup, and
the file names are the same as the file names that are saved in the FTP server.
b. When the following information is displayed, press any key to enter the boot setting
window.
Press any key to stop autoboot:3
c. When the following information is displayed, enter y to modify the startup

configuration parameters.
Do you want to manual config? (Yy/Nn)y
d. After the boot menu is displayed, enter 1 and press the Enter key.
BootMenu Selection as follow:
0 - Auto boot
1 - Manual BOOT Config
2 - Show BOOT Config
? - Print this help list
[ZBoot]: 1
e. Set the boot parameters.

Config As SC? (Yy/Nn) : n y
Boot Mode(1: Local Flash; 2: Net): 2 //To set local boot, select 1.
Base MAC Addr : 0:d0:d0:77:8:0 //It does not need to be modified.
Press the Enter key.
Mac Total : 16 //It does not need to be modified.
Press the Enter key.
Local IP : 192.168.1.150 1.1.1.18 //Set the LCT IP address,
3-2

Chapter 3 Debugging Access NEs
default: 1.1.1.18/24. It does not need to be modified.

Net Mask : 255.255.255.0 //Press the Enter key.
Gateway IP : 192.168.1.223 1.1.1.1 //Set the gateway IP address to the
IP address of the FTP Server.
Server IP : 10.8.8.125 1.1.1.1 //IP address of the FTP Server
File Name : base.set //The main program of the ZXCTN 6500
product is *.set. The file name can be set as required, but it must be the same
with the file name in the FTP Server
FPGA File Name : fpga.bin //For versions later than B12,
enter fpga.bin. The fpga.bin file does not need to be stored in the FTP Server.
For earlier versions, a null fpga.bin file needs to be configured.
A null file in the FTP Server should be named as fpga.bin.
FTP Path : //If the file is stored in the FTP root
directory, press the Enter key.
FTP Fpga Path : //If the file is stored in the FTP root
directory, press the Enter key.
FTP Username : upp //Configure the user name of the FTP Server.
The settings are same to step 1.c.
FTP Password : *** //Configure the password of the FTP Server.
The settings are same to step 1.c.
FTP Password Confirm : *** //Confirm the password of the FTP Server.
The settings are same to step.
Serial Authenticate (Yy/Nn) : n //Do not enable serial authentication.
Enable Password : ****** //Configure the password for enable. T
he default password is zxr10, and it does
not need to be modified.
f. When the following information is displayed, enter y to set the equipment to

network startup.
Manual boot now? (Yy/Nn) y
Note:
After the equipment loads program files through the network and restarts
successfully, it writes the program files into the memory and sets the restart mode
to FLASH. The directory for loading the program files is sysdisk0: verset/base.set.
Troubleshooting
If the program files cannot be loaded properly, solve the problem as follows:
1. Verify that the program files are complete.
2. Verify that the FTP software operates properly.
3-3

3. Verify that the network cables between the PC and the LCT port of the main control
board of the equipment are connected properly.
4. Verify that the IP addresses of the PC and the LCT port of the equipment belong to
the same network segment.
3.2 Configuring an Access NE Through Command

Lines
For a description of the required data, refer to Table 3-1.
Table 3-1 Data Required for Configuring Access NEs
NE IP Address
U31 EMS 198.8.8.5/24
Access NE l MNP IP: 198.2.1.151

l Qx:198.8.8.18/24
1. Connect to the access NE.
a. Use a serial cable to connect the serial port of the PC and the Console port of the
ZXCTN6500 main control board.
b. Start the Hyper terminal on the PC (Windows XP is used as an example). Click
Start > All Programs > Accessories > Communications > Hyper Terminal.
The Connection Description dialog box is displayed.
c. Enter a name for the new connection. For example, ZXCTN. Click and OK.
The Connect To dialog box is displayed.
3-4

d. From the Connect using list, select the serial port that the serial cable is
connected to, for example COM1. Click OK.
e. In the COM1 Properties dialog box, set the port. Set Bits per second to 115200.
Use the default settings for other parameters.
f. Click OK. The Hyper Terminal dialog box is displayed.
3-5

2. Configure the access NE on the hyper terminal.

a. Enter global configuration mode.
ZXR10>en // Enter "enable", and press the Enter key to enter the privilege
mode with the prompt #.
Password:
ZXR10#
ZXR10#conf t // Enter "configure terminal" to enter the global configuration mode
with the prompt (config)#.
Enter configuration commands, one per line. End with CTRL/Z.
ZXR10(config)#
b. Set the equipment name to 6500–1.

ZXR10#(config)#hostname 6500-1
6500-1(config)#
c. Configure the MNG IP.
Note:
The default OSPF areas are different for versions ZXCTN6500 V1.00.10R1 and
ZXCTN6500 V1.00.10R2. The default OSPF area for ZXCTN6500 V1.00.10R1
is 2.0.0.0. The default OSPF area for ZXCTN6500 V1.00.10R2 is 0.0.0.0. The
configuration commands are described as follows based on the versions.
l 65R1
3-6

6500-1(config)#dcn //Enter the dcn command to enter the DCN

configuration mode.
6500-1(config-dcn)#mngip 198.2.1.151 255.255.255.255 2.0.0.0
//Configure the MNG IP.
6500-1#sho dcnbase //Query the DCN configuration parameters.
global: 1
qxip qxipmask qxmac qxospfenable qxflood qxospfarea
0.0.0.0 0.0.0.0 0203.0405.a1a1 0 0 0.0.0.0
mngip mngipsubfix ospfarea
198.2.1.151 255.255.255.255 2.0.0.0
6500-1#
l 65R2
6500-1(config)#dcn //Enter the dcn command to enter the DCN configuration mode.
6500-1(config-dcn)#mngip 198.2.1.151 255.255.255.255 0.0.0.0
//Configure the MNG IP.
6500-1#show dcnbaseinfo
D - default. C - custom. A - Auto Calc.
dcn status: enable
DevSeriNo(hex):3EC5E
NEID(hex): 40.0B.EC.5E[A]
DeviceType:UPP3081-32(342)
baseMac(hex): 34e0.cffe.c5e0
qxip qxipmask qxmac qxospfenable qxflood qxospfarea
-- -- 34e0.cffe.c5e0 [D] -- -- --
mngip mngipsubfix ospfarea
198.2.1.151 255.255.255.255 0.0.0.0[D]
6500-1#
d. Configure the Qx IP.

l 65R1
6500-1(config-dcn)#qx 198.8.8.18 255.255.255.0 0203.0405.a1a1 1 0 2.0.0.0
//Configure the MNG IP
6500-1#sho dcnbase //Query the DCN configuration parameters.
l 65R2
6500-1(config-dcn)#qx 198.8.8.18 255.255.255.0 0203.0405.a1a1 1 0 0.0.0.0
//Configure the MNG IP
6500-1#show dcnbaseinfo
//Query the DCN configuration parameters.
3. (Optional) Configure routes.

If the U31 server is configured with the client, you should configure routes between
the U31 server and the U31 client, see Figure 3-2. If the U31 client is not configured,
you do not need to configure routes.
3-7

Figure 3-2 Routes between the U31 Server and the U31 Client
a. Configure the static route on each ZXCTN equipment in the network.

6500-1(config-dcn)#statrout 10.8.8.0 255.255.255.0 198.8.8.18
b. On the U31 client, run the following command to add the static route of the
management IP address through which the client is connected to the access NE.
route add 198.2.1.0 mask 255.255.255.0 10.8.8.1 -p
4. Configure AAA authentication.

6500-1#conf t
6500-1(config)#multi-user configure //Enable multi-user configuration.
6500-1(config)#commit
Note:
The following script is applicable to version R1B14, but not to R1P01/P02/P03.
6500-1(config)#aaa-authentication-template 2001
//AAA authentication instance 2001
6500-1(config-aaa-authen-template)#aaa-authentication-type local
//*The AAA authentication type is local.*//
6500-1(config-aaa-authen-template)#exit
6500-1(config)#aaa-authorization-template 2001
//AAA authorization instance 2001
6500-1(config-aaa-author-template)#aaa-authorization-type mix-radius
//*The AAA authorization type is mix-radius.*//
6500-1(config-aaa-author-template)#exit
6500-1(config)#commit
//Commit the settings.
6500-1(config)#system-user
//Enter the system user configuration mode.
6500-1(config-system-user)#username who password who authentication-template
1 authorization-template 1
//*User with user name and password who uses authentication instance 1
and authorization instance 1.*//
6500-1(config-system-user)#authentication-template 1
//*User authentication instance 1 is bound to AAA authentication instance 2001.*
3-8

//6500-1(config-system-user-authen-temp)#bind-authentication-template 2001
6500-1(config-system-user-authen-temp)#exit
6500-1(config-system-user)#authorization-template 1
//*User authorization instance 1 is bound to AAA authorization instance 2001.*//
6500-1(config-system-user-author-temp)#bind-authorization-template 2001
6500-1(config-system-user-author-temp)#local-privilege-level 15
//The privilege level is 15.
6500-1(config-system-user-author-temp)#end
6500-1#
6500-1#write
Note:
If you cannot log in to the equipment due to user name or password error during
upgrade, you should set noload after connecting to the equipment.
3.3 Configuring Access NEs on the EMS

3.3.1 Logging In to the EMS Client
This procedure describes how to start the NetNumen U31 server and client, and how to
log in to the client.
Prerequisite
l You have obtained the License file in accordance with the ZTE process. If you do not
have the License, call 800-810-3118.
l The NetNumen U31 server and client have been installed.
Steps
1. Start the NetNumen U31 server.
In the PC where the Ne!qazxsw2tNumen U31 server is installed, click Start >
All Programs > NetNumen (TM) U31 Unified Network Management System >
U31 console The Console dialog box is displayed, and all Console processes are
automatically started.
3-9

2. Log in to the NetNumen U31 client.

a. In the PC where the NetNumen U31 client is installed, click Start > All Programs
> NetNumen (TM) U31 Unified Network Management System > U31 client.
The dialog box is displayed.
b. Enter the user name, password, and server address. Click OK to log in to the
EMS system. The default user name is admin, and the password is null.
– End of Steps –
3.3.2 Creating an Access NE

This procedure describes how to create an access NE on the U31 system.
Prerequisite
l You have logged in to the NetNumen U31 client.
l You have the user permissions of "Operator Role" or above.
Steps
1. Right-click the Topology Management window, and select Create Object > Add
BN-xTN NE. The Add BN-xTN NE dialog box is displayed.
2. From the left object tree, select CTN Device > ZXCTN 6500-16L.
3. Enter the NE name, IP address, subnet mask, gateway NE and click Apply.
3-10

Note:
The ZXCTN 6500 V1.00.10R1 does not support GNEs. The ZXCTN 6500 V1.00.10R2
supports GNEs.
4. Right-click 6500-1, and select NE Property. Configure Service Route ID. It can be
set to the router-id or the MNG IP. Click Apply.
3.3.3 Uploading the Database

This procedure describes how to upload configuration data of the initialized equipment to
the EMS database to ensure that the configuration data of the board is the same as that
in the EMS database.
Prerequisite
l The NE has been created on the EMS, and the NE is online.
3-11

Steps
1. In the topology window, right-click the NE that you want to synchronize data. From the
shortcut menu, select Data Synchronization.
2. From the Upload tab, select the NE that you want to upload data. For example,
6500–1. Click Upload.
Related Task
After the database is uploaded successfully, compare the data. The data of the equipment
should be the same as the data saved in the EMS database.
To compare the data, perform the following operations:
1. In the topology window, right-click the NE whose data you have uploaded to the
database. For example, 6500–1.
2. Click NE Management > Data Synchronization. The Data Synchronization dialog
box is displayed.
3. Click Compare. Select the NE and click Compare.
3.3.4 Configuring Boards

You can configure boards by using one of the following methods.
3-12

3.3.4.1 Manually Adding a Board

You can manually add a logical board for a logical NE. The logical board must be the same
as the physical board installed on the physical NE.
Prerequisite
You have the user permissions of "Operator Role" or above.
Context
A logical board refers to the board that is created on the EMS. If the logical board is created
but the physical board is not installed on the equipment, the main control board reports the
"board removal" alarm.
Steps
1. In the Topology Management window, right-click the NE to which you want to add a
board, and select Open Rack Chart from the shortcut menu. The Rack Chart dialog
box is displayed.
2. From the tool bar, click .

3. On the Board Selection tab, select the board. The corresponding slots on the subrack
are highlighted in yellow. The board can be inserted into only the highlighted slots.
4. Click any yellow slot to install the board.
l You can also add a board as follows:
Right-click an idle slot on the subrack, and select Install Board from the shortcut
menu, and select the board that you want to add.
l To set the board properties when you add a board, select the Pre-setting check
box in the lower-left corner. The Board Property dialog box is displayed. Set the
board properties. If you do not set the board properties, the default properties are
added.
5. (Optional) Remove a board that is installed incorrectly as follows:
a. Right-click the board in the slot, and select Remove Board from the shortcut
menu. The Confirm dialog box is displayed.
b. Click Yes.
3.3.4.2 Enabling the EMS to Automatically Discover a Board

After an NE is created, you can enable the EMS to automatically discover boards. The
EMS automatically can search for physically installed boards on the NE and create boards
on the EMS.
3-13

Prerequisite
l The NE is in online status.
Steps
1. In the Topology Management window, double-click the NE. The Rack Chart dialog
box is displayed.
2. Perform the following operations as required.
To… Do…
Discover the board in a Right-click the slot where you want to add a board, and select Board
slot Auto Discover from the shortcut menu. The Board Auto Discover
dialog box is displayed.
Discover the boards in all

In the Rack Chart tool bar, select . The Board Auto Discover
slots
dialog box is displayed.
3. Click Correct. A dialog box is displayed. Enter the verification code and click OK. The
EMS verifies the automatically discovered board.
After the board verification is completed, the EMS displays the Rack/Subrack/Slot
No, EMS Board Type, Needed Board Type, and Installed Board Type. EMS Board
Type, Needed Board Type, and Installed Board Type should be the same. The EMS
displays a message box, indicating that the operation is successful.
4. Click OK. The message dialog box is closed.
5. (Optional) To synchronize the board data, click Data Synchronization.
6. Click Close to return to the Rack Chart dialog box.
Result
The automatically discovered boards are displayed in the corresponding slots of the Rack
Chart.
3-14

Chapter 4
Interconnection Debugging
Interconnection debugging means direct debugging on access NEs and non-access NEs,
that is, configuration of monitoring management.
Two monitoring management modes can be used:
l DCN+MCC: uses Ethernet encapsulation. The CLI-based configuration procedure
will be described later.
l Pure DCN mode: uses PPPoE encapsulation. The GUI-based configuration
procedure will be described later.
Figure 4-1 shows the differences between the two monitoring modes.
Figure 4-1 Differences Between Two Monitoring Modes
Table of Contents
DCN+MCC .................................................................................................................4-1
Pure DCN...................................................................................................................4-3
4.1 DCN+MCC
This procedure describes how to configure a monitoring channel between 6500–1 and
6500–3 through the CLI.
1. Configure the L2 Ethernet attribute of a DCN interface for Xge_1/3/0/1 on 6500-1.
6500-1(config-dcn)#l2 xgei-1/3/0/1 1 0011.2222.3333 4094 10
//The parameters respectively are the interface L2 attribute,
physical interface, DCN flag (1: enable, 0: disable), DCN MAC address,
VLAN ID, and bandwidth (unused, default: 10 Mbps).
4-1

2. Configure the L3 Ethernet attribute of a DCN interface for Xge_1/3/0/1 on 6500-1.

6500-1(config-dcn)#l3 xgei-1/3/0/1 2 1 195.1.1.1 255.255.
255.0 2.0.0.0
physical interface, L3 encapsulation type (1: PPP, 2: Eth),
unnumber attribute (1: not borrowed, 2: borrowed address),
IP address, subnet mask, and OSPF area code (configured
based on network planning).
3. On 6500-1, remotely configure the L2 Ethernet attribute of a DCN interface for

Xge_1/3/0/1 on 6500-3.
6500-1(config-dcn)#neiborl2 xgei-1/3/0/1 3 1 1 0011.2222.
4444 4094 10
local physical interface, slot number and interface number of the
neighbor, DCN flag (1: enable, 0: disable), the DCN MAC address
allocated to the neighbor, VLAN ID, and bandwidth (unused,
default: 10 Mbps).
4. On 6500-1, remotely configure the L3 Ethernet attribute of a DCN interface for

Xge_1/3/0/1 on 6500-3.
6500-1(config-dcn)#neiborl3 xgei-1/3/0/1 3 1 2 1 195.1.1.3
255.255.255.0 2.0.0.0
local physical interface, slot number and interface number of
the neighbor, L3 encapsulation type (1: PPP, 2: Eth), unnumber
attribute (1: not borrowed, 2: borrowed address), IP address,
subnet mask, and OSPF area code (configured
based on network planning).
5. On 6500-1, remotely configure the IP address of the management interface of 6500-3.

6500-1(config-dcn)#neibormngif xgei-1/3/0/1 198.2.1.153 255.
255.255.255 2.0.0.0
//The parameters respectively are the management interface of the
neighbor, local physical interface, IP address allocated to the
neighbor, subnet mask, and OSPF area code (configured based on
network planning).
6500-1#show dcnfib
desip desipmask nexthopip mac slot port
198.2.1.153 255.255.255.255 198.2.1.153 00d8.8041.0003 3 1
198.2.1.156 255.255.255.255 198.2.1.156 00d8.8040.8009 0 0
195.1.1.0 255.255.255.0 198.2.1.156 00d8.8040.8009 3 1
198.8.8.0 255.255.255.0 198.8.8.16 00d8.8040.8009 0 0
4-2

Chapter 4 Interconnection Debugging
6. (Optional) Configure the route from a non-access NE to the U31 client. If the U31
server and client are not on the same PC, perform this step. Otherwise, skip this step.
6500-1(config-dcn)#neiborstatrout xgei-1/3/0/1 10.8.8.0 255.
255.255.0 198.8.8.18
//The parameters respectively are the static route of the neighbor,
local physical interface, route prefix, mask, and next hop.
7. On 6500–1, ping the address of 6500–3. If 6500–3 is configured improperly, it cannot

be reached.
6500-1#ping dcn 198.2.1.153
sending 5,100-byte ICMP echo(es) to 198.2.1.155,timeout is 2 second(s).
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 2/2/2 ms.
8. Telnet to 6500–3 from 6500–1.

6500-1#telnet 198.2.1.153 dcn
Open
Attention: Telnet Escape character is ctrl+']'
**************************************************************
Welcome to ZXR10 ZXCTN 6500 Carrier-Class Router of ZTE Corporation
**************************************************************
Username:who
Password:
ZXR10#
ZXR10#show dcnstaticroute
destip ipprefix nextip
10.8.8.0 255.255.255.0 198.8.8.5
4.2 Pure DCN

This procedure describes how to configure automatic discovery of a DCN through the Link
Layer Discovery Protocol (LLDP). The LLDP allows devices in a network to quickly discover
each other and save detailed information about neighbor devices. Based on automatic
discovery of neighbor devices through the LLDP, the DCN can configure the discovered
devices.
Key configuration steps include:
1. Enabling the LLDP on all NEs.
2. Enabling the DCN on all NEs.
Prerequisite
l Connection of fibers and cables of NE1 through NE4 is completed on the EMS.
l OSPF instances are configured for NE1 through NE4, and the instances are within
the same domain.
4-3

Context
Figure 4-2 Two-fiber Ring Network
Table 4-1 NE Attribute Description
Attribute Access NE Non-access NE
NE1 NE2 NE3 NE4
Device type 6500-32 6500-16L 6500-16L 6500-8
Hardware version V1.00.10R2
Software version V1.00
Management DCN
mode
4-4

Table 4-2 IP Address Planning of NEs
Device IP OSPF Area Code
NE1 Qx: 195.1.1.18/24 0.0.0.0
192.1.1.1/32
NE2 192.1.1.2/32 0.0.0.0
NE3 192.1.1.3/32 0.0.0.0
NE4 192.1.1.4/32 0.0.0.0
EMS server 195.1.1.15/24 0.0.0.0
Table 4-3 Planning of Physical Interface Connections
NE Model Manage- Local Interface Manage- Remote Interface

ment Sta- ment Sta-
tus of the tus of the
LLDP De- LLDP In-
vice terface
NE1 ZXCTN Transmit- NE1-PGEA[0-1-42]-ETH:1 Transmit- NE2-PGEA[0-1-4]-

6500-32 ting and ting only ETH:2
receiving
NE1-PGEA[0-1-43]-ETH:1 Receiving NE2-PGEA[0-1-3]-
only ETH:3
NE1-PGEA[0-1-44]-ETH:1 Transmit- NE4-PGEA[0-1-11]-

ting only ETH:3

only ETH:2
NE2 ZXCTN Transmit- NE2-PGEA[0-1-4]-ETH:2 Receiving NE1-PGEA[0-1-42]-

6500-16L ting and only ETH:1
receiving
ting only ETH:1

ting only ETH:1

only ETH:1
4-5

NE Model Manage- Local Interface Manage- Remote Interface

ment Sta- ment Sta-
tus of the tus of the
LLDP De- LLDP In-
vice terface
NE3 ZXCTN Transmit- NE3-PGEA[0-1-6]-ETH:1 Receiving NE2-PGEA[0-1-4]-

6500-16L ting and only ETH:1
receiving
ting only ETH:1

only ETH:1

ting only ETH:15
NE4 ZXCTN Transmit- NE4-PGEA[0-1-9]-ETH:1 Transmit- NE3-PGEA[0-1-5]-

6500-8 ting and ting only ETH:1
receiving
only ETH:16

only ETH:1

ting only ETH:2
Steps
1. Log in to the EMS server through a client, and open the Topology Management view.
2. In the Topology Management view of the EMS, right-click NE1 and select NE
Management from the shortcut menu. The NE Management window is displayed.
3. From the Customized Resource navigation tree, select NE1. From the NE Operation
navigation tree, select Protocol Configuration > Level 2 Protocol Management >
LLDP Configuration. The LLDP Configuration dialog box is displayed.
4. On the LLDP Equipment Information tab, configure the management status of the
LLDP device. For details, refer to Table 4-3.
4-6

5. On the LLDP Port Information tab, configure the management status of each LLDP
interface. For details, refer to Table 4-3.
6. Repeat Steps 3 through 5 to enable the LLDP for NE2, NE3, and NE4.
7. From the Customized Resource navigation tree, select NE1. From the NE
Operation navigation tree, select System Configuration > DCN Management >
DCN Local Global Configuration. The DCN Local Global Configuration dialog
box is displayed.
8. On the DCN Local Global Configuration tab, select Enable from the DCN Global
Enable drop-down list.
9. Click to validate the configuration.

10. Repeat Steps 7 through 9 to enable global DCN for NE2, NE3, and NE4.
4-7

4-8

Chapter 5
Basic Configuration
Table of Contents
Configuring a Loopback Interface ...............................................................................5-1
Configuring an L3 Interface ........................................................................................5-2
(Optional) Configuring a Subinterface.........................................................................5-4
Configuring an ARP Entry ..........................................................................................5-5
5.1 Configuring a Loopback Interface

5.1.1 Configuring a Loopback Interface Through the GUI
This procedure describes how to add, modify, delete, and query loopback interfaces. A
loopback interface is used in the following scenarios:
l It provides a source or destination IP address for service creation.
l It provides a known and stable ID for OSPF routing.
l It acts as an intermediate output interface of data.
Prerequisite
You must have the authority of a system operator or higher.
Steps
1. In the Topology Management view, right-click an NE, and select NE Management
from the shortcut menu. The NE Management window is displayed.
2. From the NE Operation navigation tree, select Interface Configuration > Loopback
Port Configuration. The Loopback Port Configuration dialog box is displayed.
3. Click Add. The Create dialog box is displayed.
4. In the Attributes area, set the basic parameters of the interface. For details, refer to .
5. (Optional) Set an assistant IP address.

a. Click Add, and add an entry in the Assistant IP/Assistant Mask list.
b. Modify the assistant IP address and mask in the list.

6. Click Confirm to return to the Loopback Port Configuration window.
7. (Optional) Perform the following operations as required.
5-1

To... Do...
Modify an interface. i. Select the target interface in the list.
ii. Click Modify. The Modify dialog box is displayed.
iii. Modify the parameter values as required, and click Confirm.
Delete an interface. i. Select the target interface in the list.
ii. Click Delete. In the pop-up dialog box, click Yes.
Query interface Click Refresh. The latest interface information is displayed in the list.
information.
Print interface i. Click Print. In the pop-up dialog box, set printing parameters.
information.
ii. Click Print.
8. Click Apply. In the pop-up dialog box, click OK.

5.1.2 Configuring a Loopback Interface Through the CLI

1. Enter global configuration mode.
6500-1>en //Type "enable", and press Enter to enter privileged
mode with the # prompt.
Password:
6500-1#
6500-1#conf t //In privileged mode, type "configure terminal"
to enter global
configuration mode with the (config)# prompt.
6500-1(config)#
2. Configure a loopback interface.

6500-1(config)#interface loopback1
6500-1(config-if-loopback1)#ip add 10.1.1.1 255.255.255.255
5.2 Configuring an L3 Interface

5.2.1 Configuring an L3 Interface Through the GUI
This procedure describes how to configure an L3 interface. An L3 interface can send and
receive data packets of L2 and L3 services.
5-2

Chapter 5 Basic Configuration
Prerequisite
The corresponding L2 logical interface or L3 physical port is already configured.
Steps
2. In the left navigation tree, select NE Operation > Interface Configuration > L3
Port/Subinterface Configuration. The L3 Port/Subinterface Configuration dialog
box is displayed.
3. Configure the parameters of the L3 interface.
a. Click the IP Port tab.

b. Click Add. The Add dialog box is displayed.
c. Set the properties of the L3 interface. For details, refer to .
Note:
The parameter types and ranges vary with devices. All available parameters for
the current NE are displayed on the GUI of the ZXCTN6500 EMS.
d. Click OK.
5.2.2 Configuring an L3 Interface Through the CLI

6500-1>en //Type "enable", and press Enter to enter
privileged mode with the # prompt.
Password:
6500-1#
6500-1#conf t //In privileged mode, type "configure terminal"
to enter global configuration
mode with the (config)# prompt.
6500-1(config)#
2. Enter interface mode.

6500-1(config)#interface xgei-1/3/0/1
6500-1(config-if-xgei-1/3/0/1)#
3. Configure the IP address of an L3 interface.
5-3

6500-1(config-if-xgei-1/3/0/1)#ip address 100.1.1.1 255.255.255.252
5.3 (Optional) Configuring a Subinterface

5.3.1 Configuring a Subinterface Through the GUI
A subinterface can only send and receive data packets of L3 services. This procedure
describes how to configure the startup state, port type, VLAN, and other related
parameters.
Prerequisite
You must have the authority of a system operator or higher.
Steps
2. In the left navigation tree, select NE Operation > Basic Configuration > Basic Data
Configuration. The Basic Data Configuration dialog box is displayed.
3. Click the L3 Port/Subinterface Configuration tab, and then click the Sub Port tab.
Note:
You can also open the Sub Port tab page as follows: From the navigation tree, select
NE Operation > Interface Configuration > L3 Port/Subinterface Configuration. In
the right dialog box, click the Sub Port tab.
4. Click Add. The Add dialog box is displayed.

5. Set the parameters of the subinterface. For details, refer to .
Note:
The parameter types and ranges vary with devices. All available parameters for the
current NE are displayed on the GUI of the ZXCTN6500 EMS.
6. Click OK.
5-4

5.3.2 Configuring a Subinterface Through the CLI

Password:
6500-1#
6500-1#conf t //In privileged mode, type "configure terminal" to
enter global configuration mode
with the (config)# prompt.
6500-1(config)#
2. Enter VLAN configuration mode.

6500-1(config)#vlan-configuration
6500-1(config-vlan)#
3. Configure VLAN encapsulation for a subinterface.

6500-1(config-vlan)#interface xgei-1/3/0/1.2
6500-1(config-vlan-if-xgei-1/3/0/1.2)#encapsulation-dot1q 100
//The ID of the encapsulated
VLAN of the subinterface is 100.
6500-1(config-vlan-if-xgei-1/3/0/1.2)#exit
6500-1(config-vlan)#exit
6500-1(config)#
4. Enter subinterface configuration mode to configure the IP address of the subinterface.

6500-1(config)#interface xgei-1/3/0/1.2
6500-1(config-if-xgei-1/3/0/1.2)#ip address 100.1.1.1 255.255.
255.252
6500-1(config-if-xgei-1/3/0/1.2)#end
6500-1#
5.4 Configuring an ARP Entry

5.4.1 Configuring an ARP Entry Through the GUI
This procedure describes how to add an ARP entry for a qualified port, and configure the
parameters of the ARP entry.
Prerequisite
l The corresponding IP interface is already configured.
l You must have the authority of a system operator or higher.
5-5

Context
This procedure describes how to manually configure an ARP entry. An ARP entry can also
be configured automatically after you do the following: On the ARP Table Configuration
tab, click Auto. The system then automatically calculates ARP data based on the topology,
interface configuration, and the MAC address of the rack where the NE is located.
Steps
2. From the left navigation tree, select NE Operation > Basic Configuration > Basic
Data Configuration. The Basic Data Configuration dialog box is displayed.
3. Click the ARP Configuration tab.
Note:
You can also open the ARP Configuration tab page as follows: From the navigation
tree, select NE Operation > Protocol Configuration > ARP Configuration.
4. Click the ARP Table Configuration tab. From the list, select the port for which an
ARP entry is to be configured.
5. Click Add. The Add dialog box is displayed, see Figure 5-1.
5-6

Figure 5-1 Add Dialog Box
6. Set the parameters in the dialog box. For details, refer to .
Note:
The value of IP Address of Peer must be the same as the MAC address of the peer
NE.
7. Click OK to return to the ARP Table Configuration tab.

8. Click Apply. The Message dialog box is displayed. Click OK.
5.4.2 Configuring an ARP Entry Through the CLI

Password:
6500-1#
6500-1#conf t //In privileged mode, type "configure terminal" to
enter global configuration
mode with the (config)# prompt.
5-7


6500-1(config)#
2. Enter ARP configuration mode.

6500-1(config)#arp
6500-1(config-arp)#
3. Configure an interface or subinterface ARP entry.

l If an L3 interface is used for the interconnection between two devices, configure
an ARP entry under the L3 interface.
6500-1(config-arp)#
6500-1(config-arp)#interface xgei-1/3/0/1
6500-1(config-arp-if-xgei-1/3/0/1)#arp permanent 100.1.1.2
0000.1111.2222
//The parameters include the remote IP address and remote MAC address.
l If a VLAN is used for the interconnection between two devices, configure an ARP
entry under the subinterface and bind it to the VLAN.
6500-1(config-arp)#
6500-1(config-arp)#interface xgei-1/3/0/1.2
6500-1(config-arp-if-xgei-1/3/0/1)#arp permanent 100.1.1.2 0000.
1111.2222 100
//The parameters include the remote IP address, remote MAC address, and bound VLAN.
5-8

Chapter 6
DCN Performance
Optimization
After completing the DCN configuration, you can optimize DCN performance from the
following aspects.
Disabling Redundant DCN Ports

The DCN function only requires that two optical interfaces in different slots be enabled.
You can disable redundant DCN ports to reduce CPU usage of the DCN function.
Note:
To disable the DCN function in versions earlier than 6500 V1.00.10R1B14, you should
disable the DCN function on ports through the CLI or disable the ports for which the DCN
function is disabled through the GUI, and then run the cli show command to check whether
the DCN function is still enabled for some ports. If yes, manually disable the DCN function
for the ports.
l CLI mode
6500(config-dcn)#l2 gei-1/17/0/15 0 0011.2222.3333 4094 2
//0 indicates that the DCN function is disabled for the port.
l GUI mode
1. In the Topology Management view, right-click an NE, and select NE
Management from the shortcut menu. The NE Management window is
displayed.
2. From the navigation tree, select [NE Operation > System Configuration > DCN
Management > DCN Local Global Configuration].
3. On the Port DCN Enable tab, select the port for which the DCN function is to be
disabled, and click .
6-1

Using Ethernet Encapsulation for Interworking

If the number of DCN optical directions is too large, for example, in a star topology, it is
recommended to use Ethernet encapsulation.
In Ethernet encapsulation, the link layer only needs to use the ARP to learn MAC
addresses. In addition, it runs on an interface board, and thus it can greatly reduce the
load of the CPU on the main control board and improve communication capabilities in
optical directions.
6-2

Chapter 7
Debugging Result
Verification
After completing debugging, you should verify the following physical performance
indicators:
Table of Contents
Checking Interface Status ..........................................................................................7-1
Checking Optical Power .............................................................................................7-2
Checking Network Management Monitoring Channels................................................7-3
7.1 Checking Interface Status

This procedure describes how to check the status of E1 and Ethernet interfaces.
Check Method
l For E1 interfaces:
Perform self-loop on each E1 interface and check alarms. Or use a diode to check
the interface.
l For Ethernet interfaces:
Perform loopback on a network interface by using a loopback network connector.
In addition, you can run the show ip interface brief command to check the status of
each interface. For the meanings of the query results, refer to Table 7-1.
Caution!
The show ip interface brief command is not applicable to E1 interfaces. When this
command is used to query the status of E1 interfaces, the displayed status is always
up.
ZXR10#show ip int b
Interface IP-Address Mask Admin Phy Protocal
xgei-1/3/0/1 unassigned unassigned up up up
xgei-1/3/0/2 200.30.2.3 255.255.255.0 up up up
7-1

Table 7-1 Query Result Description
Field Description
Admin Indicates the management status of an interface. The value up indicates that the
interface is available. The value down indicates that the interface is unavailable.
In interface mode, you can run the no shutdown command to set an interface
to be available, and run the shutdown to set an interface to be unavailable. By
default, an interface is available.
Phy Indicates the physical status of an interface. The value up indicates that the
interface is active. The value down indicates that the interface is abnormal or
not connected. If the value is down, check the corresponding network cables
or fibers.
Protocol Indicates the status of the link layer protocol. The value up indicates that the
protocol is available. The value down indicates that the protocol is unavailable.
If the value is down, check the corresponding configuration.
7.2 Checking Optical Power

Optical power includes the average optical transmit power and the average optical receive
power. The check methods are respectively described as follows.
Testing the Average Optical Transmit Power

For the network connection used in the test, see Figure 7-1. Set the optical receive
wavelength of the optical power meter to the same as the optical transmit wavelength
of the target optical interface board. Connect one end of a tail optical fiber to the target
optical transmit interface, and the other end to the test input interface of the optical power
meter. When the optical power becomes stable, read the value of the optical power, that
is, the optical transmit power of the optical interface.
Figure 7-1 Testing the Average Optical Transmit Power
The type of the tail optical fiber used in the test varies with the mode (single mode or
multiple mode) of the optical interface on the optical interface board.
7-2

Chapter 7 Debugging Result Verification
For the requirements of the average optical transmit power of each type of optical power,
refer to the Technical Specifications in "Product Description".
If the test result does not comply with the specifications, verify that the tail optical fiber
connection is good and the fiber connectors are clean. Dip a piece of dust-free paper into
anhydrous alcohol, and then use it wipe the fiber connectors. You can also replace the tail
optical fiber and test again. If the result is still not good, replace the optical interface board
and test again.
Testing the Average Optical Receive Power

For the network connection used in the test, see Figure 7-2. Set the optical receive
wavelength of the optical power meter to the same as the optical transmit wavelength of
the target optical interface board. Connect the line optical signals to the optical power
meter. When the optical power becomes stable, read the value of the optical power
(removing the attenuation of the tail optical fiber), that is, the optical receive power of the
optical interface. The type of the tail optical fiber used in the test varies with the mode
(single mode or multiple mode) of the optical interface on the optical interface board.
Figure 7-2 Testing the Average Optical Receive Power
The average optical receive power should be greater than the optical receive sensitivity
of the corresponding type of optical interface board, but smaller than the overload optical
power of the board. For the requirements of the average optical receive power of each
type of optical power, refer to the Technical Specifications in "Product Description".
7.3 Checking Network Management Monitoring

Channels
1. Run the ping command to check interconnection information. The expected result is
as follows:
ZXR10#ping dcn 198.2.1.153
sending 5,100-byte ICMP echo(es) to 198.2.1.155,timeout is 2
second(s).
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 2/2/2 ms.
7-3

If packet loss occurs, check the link information, for example, self-negotiation, optical
transmit/receive power, and network cable order.
2. Run the show ip interface brief command to verify that the mapping between VLAN
subinterfaces and IP addresses is consistent with the planning table.
ZXR10#show ip interface b
Interface IP-Address Mask Admin Phy Prot
xgei-1/3/0/2 200.30.2.3 255.255.255.0 up up up
3. Run the show interfac command to check the status of physical NNI ports and verify
that there are transmitted or received packets and CRC.
ZXR10#show interface xgei-1/9/0/1
xgei-1/9/0/1 is up, line protocol is up
Description is none
Hardware is XGigabit Ethernet, address is 0001.02ff.ff01
Internet address is unassigned
IP MTU 1500 bytes
MTU 1600 bytes
BW 10000000 Kbits
Holdtime is 120 sec
The port is optical
The MDIMode of the port is not supported
Loopback cancel
Duplex full
Negotiation force
ARP type ARP
ARP Timeout 04:00:00
There is no statistic about this interface!
At present, 6500 V1.00.10R1B14 does not provide any command for querying traffic
statistics and optical power of an interface. These functions are supported in 6500
V1.00.10R2. You can run the clear statistics interface xgei-1/3/0/1 command to clear
the statistical data, and re-calculate the number of packets transmitted or received by
an interface.
4. Run the show arp command to verify that the ARP table of the Ethernet is normal.
ZXR10#show arp
Arp protect whole is disabled
The count is 9
IP Hardware Exter Inter Sub
Address Age Address Interface VlanID VlanID Interface
--------------------------------------------------------------------------------
14.0.0.2 01:20:03 0010.9400.0005 xgei-1/10/0/ N/A N/A xgei-1/10/0/4
7-4

Chapter 7 Debugging Result Verification
4
10.0.0.4 P 0001.0200.0e01 gei-1/11/0/1 N/A N/A N/A
10.10.1.2 01:41:42 0010.9400.0002 gei-1/11/0/2 1101 N/A gei-1/11/0/2.
.1001 1001
10.10.2.2 01:41:42 0010.9400.0002 gei-1/11/0/2 1102 N/A gei-1/11/0/2.
.1002 1002
12.12.0.2 P 0001.0200.0c01 gei-1/11/0/6 N/A N/A N/A
10.0.1.3 P 0001.0200.0d01 gei-1/11/0/1 N/A N/A N/A
1
14.14.0.2 P 0001.0200.0e01 gei-1/11/0/1 N/A N/A N/A
3
123.123.200.200 P 0001.0200.0e01 gei-1/11/0/1 1 N/A N/A
4.1
123.123.150.100 P 0001.0200.0d01 gei-1/11/0/1 1 N/A N/A
5.1
192.168.11.223 01:28:24 3440.b5a2.9e90 mgmt_eth-1/1 N/A N/A mgmt_eth-1/13
3/255/1 /255/1
22.0.0.1 01:05:27 0065.0008.0003 xgei-1/16/0/ N/A N/A xgei-1/16/0/2
2
If Age is H, the IP address is used by an interface on the router. If Age is P, the ARP
is manually configured as static. Check whether ARP table entries of the peer end are
available. If not, verify that the address of the peer end is configured correctly.
7-5

7-6

Chapter 8
Debugging Knowledge
Table of Contents
Monitoring Schemes...................................................................................................8-1
DCN Port Area Migration Rules ..................................................................................8-2
File Structure in Debugging OAM Mode .....................................................................8-2
Clearing Configuration Data .......................................................................................8-2
8.1 Monitoring Schemes

A monitoring scheme is configured to allow the EMS host to manage and configure NEs. At
present, the ZXCTN6500 provides two monitoring schemes. For the comparison between
the two schemes, refer to Table 8-1.
Table 8-1 Monitoring Schemes
Item DCN Scheme DCN VLAN Scheme
Applicable environment Pure DCN DCN+MCC
Routing protocol OSPF OSPF
OSPF area scheme l For R1, the default OSPF area l For R1, the default OSPF area
is 2.0.0.0. is 2.0.0.0.
l For R2, the default OSPF area l For R2, the default OSPF area
is 0.0.0.0. is 0.0.0.0.
The OSPF area can be modified The OSPF area can be modified
as required. OSPF areas can be as required. OSPF areas can be
divided by physical interface. divided by physical interface.
Link layer protocol PPPOE Ethernet

No need to configure interface IP VLANs are DCN VLANs, which
addresses. are bound to L3 interfaces under
Interfaces communicate by using a VRF DCN.
unnumbered loopback addresses.
VLAN configuration Explicit configuration is not needed. VLAN planning is needed, which is
By default, VLAN 4094 is used. the same as the MCC scheme.
IP address planning Loopback management IP IP addresses should be divided by

addresses should be planned, and area.
IP addresses should be divided by
area.
8-1

Item DCN Scheme DCN VLAN Scheme
Commissioning mode The configuration of NE B to be The configuration of NE B to be

commissioned is distributed by its commissioned is distributed by its
neighbor NE A. neighbor NE A.
Scenario Used by China Telecom in the Used by China Mobile

future. China Telecom at present.
8.2 DCN Port Area Migration Rules

The ZXCTN6500 joins an OSPF domain by interface. When new access NEs are added or
the existing network is expanded, MNG IP addresses of the DCN are migrated according
to the following rules:
l 65R1
The default area is 2.0.0.0. The DCN management interface automatically joins the
area 0.0.0.0 only if the user modifies an L3 interface (MCC,VLAN, or Qx interface)
within the DCN VRF to the OSPF area 0.0.0.0.
l 65R2
The default area is 0.0.0.0. By default, all the L3 interfaces (including MCC,VLAN,
and Qx interfaces) within the DCN VRF are in the OSPF area 0.0.0.0.
l If all the DCN L3 interfaces (including PPPoE MCC, Qx, and VLAN interfaces in
UP state) are in another OSPF area (for example, 3.0.0.0), the DCN management
interface is migrated to the area 3.0.0.0.
l If other DCN L3 interfaces are in different non-backbone domains, it is considered as
abnormal DCN configuration. In that case, the management interface should still stay
in the current area (not necessarily the default area).
8.3 File Structure in Debugging OAM Mode

8.4 Clearing Configuration Data
After a device is powered on, you can run the show running-config command to check
whether the system has existing configuration data. If yes, you should clear the
configuration data, and configure the system again as required.
To clear configuration data, choose either of the following methods:
Method 1 (recommended): Reset the device, and restart it in no load mode.
Set the startup mode.
ZXR10(config)#load-mode ?
noload Start up with no configuration
txt Load configuration from command-line txt file
8-2

Chapter 8 Debugging Knowledge
zdb Load configuration from binary database file

ZXR10(config)#load-mode noload
There are three startup modes:

l noload: no load mode. If this mode is set, the system will not read the configuration
data in the CF/SD card upon the next startup. That is equivalent to clearing all the
configuration data. DCN related information, however, will still be loaded. Thus, NEs
monitored in DCN mode can still be managed after being restarted.
l txt: restart mode. It is the same as the startrun load mode, and is often used for
loading configuration during upgrade.
l zdb: The system reads and loads the ZDB database. After the system is restarted,
all the configuration is saved.
8-3

8-4

Figures
Figure 1-1 Debugging Process Diagram ................................................................... 1-1
Figure 3-1 PC and ZXCTN6500 Equipment Connection Diagram ............................. 3-2
Figure 3-2 Routes between the U31 Server and the U31 Client ................................ 3-8
Figure 4-1 Differences Between Two Monitoring Modes............................................ 4-1
Figure 4-2 Two-fiber Ring Network............................................................................ 4-4
Figure 5-1 Add Dialog Box ........................................................................................ 5-7
Figure 7-1 Testing the Average Optical Transmit Power ............................................ 7-2
Figure 7-2 Testing the Average Optical Receive Power............................................. 7-3

Figures
II

Tables
Table 2-1 Operation Safety Requirements................................................................. 2-1
Table 2-2 Equipment Information .............................................................................. 2-2
Table 3-1 Data Required for Configuring Access NEs ............................................... 3-4
Table 4-1 NE Attribute Description ............................................................................ 4-4
Table 4-2 IP Address Planning of NEs ...................................................................... 4-5
Table 4-3 Planning of Physical Interface Connections ............................................... 4-5
Table 7-1 Query Result Description........................................................................... 7-2
Table 8-1 Monitoring Schemes.................................................................................. 8-1
III

Tables
IV

Glossary
DCN
- Data Communications Network
MCC
- Management Communication Channel

Packet Transport Network Equipment Commissioning Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Packet Transport Network Equipment Commissioning Guide

Uploaded by

Copyright:

Available Formats

ZXCTN 6500

Packet Transport Network Equipment

Revision No. Revision Date Revision Reason

R1.0 2015-01-30 First edition.

Serial Number: SJ-20130301144038-013

Publishing Date: 2015-01-30 (R1.0)

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 3, Debugging Describes how to debug access NEs.

Chapter 4, Interconnection Describes how to debug non-access NEs.

Chapter 6, DCN Describes how to optimize the DCN data.

Chapter 7, Debugging Describes how to verify the debugging results.

Appendix, Debugging Provides knowledge on debugging the ZXCTN6500 equipment.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

Danger: indicates an imminently hazardous situation. Failure to comply can result in

Warning: indicates a potentially hazardous situation. Failure to comply can result in

Caution: indicates a potentially hazardous situation. Failure to comply can result in

Note: provides additional information about a topic.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

Chapter 4 Interconnection Debugging ..................................................... 4-1

Chapter 5 Basic Configuration.................................................................. 5-1

Chapter 6 DCN Performance Optimization .............................................. 6-1

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

Figure 1-1 Debugging Process Diagram

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

Important Safety Precautions

Table 2-1 Operation Safety Requirements

Collecting Equipment Information

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

Table 2-2 Equipment Information

General l Project time requirements

NE planning Network topology diagram

Monitoring The ZXCTN6500 supports monitoring on DCN or Ethernet.

IP address Only the directly-connected IP addresses between ZXCTN

NE interface All the ZXCTN6500 interfaces are layer-3 interfaces. The IP

Preparing Debugging Tools

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

3.1 (Optional) Loading the ZXCTN6500 Software

Step 1 Configure the FTP server on the PC.

Step 2 Connect the PC to the ZXCTN6500 equipment.

1. Configure the FTP server on the PC.

2. Connect the PC and the ZXCTN6500 equipment.

Connect the PC and the ZXCTN6500 equipment, see Figure 3-1.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

Figure 3-1 PC and ZXCTN6500 Equipment Connection Diagram

c. When the following information is displayed, enter y to modify the startup

e. Set the boot parameters.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

default: 1.1.1.18/24. It does not need to be modified.

f. When the following information is displayed, enter y to set the equipment to

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

3.2 Configuring an Access NE Through Command

Table 3-1 Data Required for Configuring Access NEs

U31 EMS 198.8.8.5/24

Access NE l MNP IP: 198.2.1.151

1. Connect to the access NE.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

f. Click OK. The Hyper Terminal dialog box is displayed.

SJ-20130301144038-013|2015-01-30 (R1.0) ZTE Proprietary and Confidential

2. Configure the access NE on the hyper terminal.

b. Set the equipment name to 6500–1.