SJ-20140731105308-006-ZXR10 M6000-S (V3.00.10) Carrier-Class Router Initial Configuration Guide - 608093

ZXR10 M6000-S
Carrier-Class Router
Initial Configuration Guide

Version: 3.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
2014-10-20
First edition.
Serial Number: SJ-20140731105308-006

Publishing Date: 2014-10-20 (R1.0)
SJ-20140731105308-006|2014-10-20 (R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Initial Configuration Flow......................................................... 1-1
Chapter 2 Initial Configuration Preparations ........................................... 2-1
Chapter 3 Initial Configuration .................................................................. 3-1
3.1 Accessing the Equipment Through the Console Port ............................................ 3-1
3.2 Starting the Equipment ....................................................................................... 3-3
3.3 Common Check Items ........................................................................................ 3-6
3.3.1 Checking the Software Version.................................................................. 3-6
3.3.2 Checking the Base MAC Address............................................................ 3-10
3.3.3 Checking the Status of Synchronization Between the Active and Standby
Main Control Boards ............................................................................. 3-12
3.3.4 Checking the Board Status ..................................................................... 3-13
3.3.5 Checking the Interface Status ................................................................. 3-14
3.3.6 Checking the Fan Status......................................................................... 3-17
3.3.7 Checking the Power Status ..................................................................... 3-18
3.3.8 Checking the Temperature of the Equipment ............................................ 3-18
3.3.9 Checking the Alarm Information .............................................................. 3-19
3.4 Common Configuration Items............................................................................ 3-22
3.4.1 Configuring the Equipment Name ............................................................ 3-22
3.4.2 Configuring the System Time .................................................................. 3-22
3.4.3 Configuring the Syslog Function .............................................................. 3-24
3.4.4 Configuring the Location and Contact Information .................................... 3-26
3.4.5 Configuring Information Saved in the NVRAM .......................................... 3-27
3.4.6 Configuring the Enable Password............................................................ 3-28
3.4.7 Configuring Telnet .................................................................................. 3-29
3.4.8 (Optional) Configuring ACL-Based Filtering of Telnet Users....................... 3-31
3.4.9 Configuring SSH .................................................................................... 3-31
3.4.10 Configuring FTP ................................................................................... 3-37
3.5 Link Layer Initial Configuration .......................................................................... 3-39
3.5.1 Configuring an Ethernet Interface ............................................................ 3-39
3.5.2 Configuring a POS Interface ................................................................... 3-41
3.6 Network Layer Initial Configuration .................................................................... 3-42
3.6.1 Configuring Interface IP Addresses ......................................................... 3-43
I
SJ-20140731105308-006|2014-10-20 (R1.0)
3.6.2 Configuring Static Routes ....................................................................... 3-44

3.6.3 Configuring OSPF Dynamic Routes......................................................... 3-45
3.6.4 Configuring IS-IS Dynamic Routes .......................................................... 3-47
3.6.5 Configuring BGP Dynamic Routes........................................................... 3-49
3.7 Configuring the Interconnection Between the Equipment and the Network
Management System ...................................................................................... 3-51
3.8 Saving the Configuration................................................................................... 3-52
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
SJ-20140731105308-006|2014-10-20 (R1.0)
About This Manual

Purpose
This manual provides information about the initial configuration (debug) flow of the ZXR10
M6000-S Carrier-Class Router (hereinafter referred to as the ZXR10 M6000-S) and
detailed configuration steps and commands.
Intended Audience
This manual is intended for debug engineers.
What Is in This Manual

This manual contains the following chapters:
Chapter
Summary
1, Initial Configuration Flow
Describes the initial configuration flow and steps of the ZXR10

M6000-S.
2, Initial Configuration
Preparations
Describes the hardware, software, tool, documentation, and data

preparations that must be made before the initial configuration of
the ZXR10 M6000-S.
3, Initial Configuration
Describes the initial configuration items, steps, and commands.
Conventions
This manual uses the following typographical conventions:
Typeface
Meaning
Italics
Variables in commands. It may also refer to other related manuals and documents.
Bold
Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
Constant
Text that you type, program codes, filenames, directory names, and function names.
width
[]
Optional parameters.
{}
Mandatory parameters.
Separates individual parameters in a series of parameters.

Warning: indicates a potentially hazardous situation. Failure to comply can result in
serious injury, equipment damage, or interruption of major services.
Note: provides additional information about a certain topic.
I
SJ-20140731105308-006|2014-10-20 (R1.0)
This page intentionally left blank.
II
SJ-20140731105308-006|2014-10-20 (R1.0)
Chapter 1
Initial Configuration Flow

Initial Configuration Flow Overview
This manual describes the initial configuration flow of the ZXR10 M6000-S Carrier-Class
Router (hereinafter referred to as the ZXR10 M6000-S), including preparations (or
debugging operations) before the initial configuration and detailed initial configurations.
Figure 1-1 shows the entire initial configuration flow.
Figure 1-1 Initial Configuration Flow
1-1
SJ-20140731105308-006|2014-10-20 (R1.0)
ZXR10 M6000-S Initial Configuration Guide
Initial Configuration Flow Description

Table 1-1 provides a description of the initial configuration flow of the ZXR10 M6000-S.
Table 1-1 Intial Configuration Flow Description
Initial Configuration Flow
Description
Initial configuration
Before the configuration, hardware, software, tools, documentation,
preparations
and data must be prepared so that the initial configurations can be

performed smoothly.
Initial configuration
After hardware installation, the ZXR10 M6000-S must be checked and

basically configured to ensure that it operates properly and can be
remotely accessed and managed through basic network connections.
The initial configurations include:
l
Accessing the Equipment Through the Console Port: describes

how to access the ZXR10 M6000-S through a PC.
Starting the Equipment: describes how to start the equipment

after it is installed.
Common Check Items: describes common check items of the

equipment, including software version, interface status, and so on.
Common Configuration Items: describes common configuration

items of the equipment, including equipment name, system time,
and so on.
Link Layer Initial Configuration: describes basic link layer

configuration of the equipment.
Network Layer Initial Configuration: describes basic network

layer configuration of the equipment.
Configuring the Interconnection Between the Equipment and

the Network Management System: describes how to configure
the interconnection between the equipment and the network
management system.
Saving the Configuration: describes how to save the

configuration.
1-2
SJ-20140731105308-006|2014-10-20 (R1.0)
Chapter 2
Initial Configuration
Preparations
Hardware Preparations
Before the initial configuration, you must check hardware facilities such as the power and
grounding, cables and connectors, boards, fans, and downstream devices and ensure that
these facilities meet the debugging conditions of the initial configuration.
Table 2-1 lists the hardware items that need to be checked before the initial configuration.
Table 2-1 List of Hardware Items to be Checked
Item to be Checked
Description
Power and grounding
Ensure that the power cable and grounding cable are correctly
connected and are in good contact.
Ensure that labels of the power cable, grounding cable, and power
distribution switch are correct, clear, and tidy.
Ensure that all the protective grounding cables on the cabinet and
equipment are in good contact.
Ensure that the power supply for the equipment is installed as requested
in the hardware installation guide and can operate normally.
Cables and connectors
Check the serial cables, network cables, optical cables, and subscriber
lines and ensure that these items meet the following requirements:
Boards
The connectors of these cables are not loose or lost.
The sheaths of these cables are not damaged.
Ensure that the number and type of the boards comply with the
configuration requirements.
Ensure that all the boards are properly installed as requested in the
hardware installation guide.
Fans
Ensure that the fan type complies with the configuration requirements.
Ensure that all the fans are properly installed as requested in the
hardware installation guide.
Downstream devices
Ensure that the physical location of the interface to which the equipment
is to be connected is known.
Ensure that the interconnected device operates normally and can be
used for debugging.
2-1
SJ-20140731105308-006|2014-10-20 (R1.0)
Note:
The hardware installation personnel has already checked the "power and grounding" and
"cables and connectors" items during the installation check. To ensure the reliability of
hardware connections during the debugging, the configuration personnel can recheck the
above items.
Software Preparations
Before the initial configuration, you must prepare all the required software for subsequent
configurations.
Table 2-2 lists the software items that need to be checked before the initial configuration.
Table 2-2 List of Software Items to be Checked
Item to be Checked
Description
System software package
Required software should be included in the system software package.
Software tools
Verify that the software tools to be used in the initial configuration are
ready and complete. In general, the software to be used includes:
l
HyperTerminal: This software tool is provided by the Windows

operating system and will be used when you try to log in to the
equipment through the serial port.
FTP server software: This software tool will be used

when the equipment tries to load software. Filezilla
Server is recommended and can be downloaded from
http://filezilla-project.org/.
Tool Preparations
Before the initial configuration, you must prepare and check all the required tools for
subsequent configurations.
Table 2-3 lists the tools that need to be checked before the initial configuration.
Table 2-3 List of Tools to be Checked
Item to be Checked
Description
Cables and interfaces
Verify that the devices are correctly connected based on the network
deployment and that the types of interfaces on the devices are the
same as those of the prepared cables. The following are the tools that
must be prepared before the initial configuration:
l
1 standard RS-232 serial cable, used for accessing the equipment

through the Console port.
1 network cable, used for configuring the management network

port or other services.
2-2
SJ-20140731105308-006|2014-10-20 (R1.0)
Chapter 2 Initial Configuration Preparations
Item to be Checked
Description
l
Multiple optical fiber cables, used for connecting to the

interconnected device.
Maintenance terminal
Prepare 1 maintenance terminal, which is in general a PC (installed with

HyperTerminal) and used to access the equipment and perform initial
configurations on the equipment.
Auxiliary instruments and
Optical power meter: This meter is used for testing the actual optical
meters
power received at an optical interface, the receiving sensitivity of an

optical interface, and the overload optical power of an optical interface.
Multimeter: This meter is used for testing the voltage, resistance, and
strength of current during the debugging of the power supply.
Documentation Preparations
Before the initial configuration, you must collect the required technical documentation,
which includes, but is not limited to the documents listed in Table 2-4.
Table 2-4 Technical Documentation Required During the Initial Configuration
Document
Description
ZXR10 M6000-S (V3.00.10) Carrier-Class Router
Describes the composition, hardware structure,
Hardware Description
boards, power supplies and fans of the ZXR10

M6000-S.

Hardware Installation Guide
Describes the engineering preparations, active

device installation, power cable installation, cable
installation, and hardware installation check of
the ZXR10 M6000-S.
Describes the principle, configuration commands
Configuration Guide
and configuration instance of every functional

module of the ZXR10 M6000-S.
Describes preparations and configurations
Initial Configuration Guide
included in the initial configuration flow of the

ZXR10 M6000-S.
Data Preparations
Before the initial configuration, you must collect information about the hardware
configuration, network architecture, and data planning of the equipment for subsequent
data configurations.
Table 2-5 lists data that need to be collected before the initial configuration.
2-3
SJ-20140731105308-006|2014-10-20 (R1.0)
Table 2-5 List of Data Items to be Collected

Data to be Collected
Description
Hardware configuration
This data item includes all the required boards and the slot where every
board is located.
Network architecture and
This data item includes but is not limited to: network architecture mode,
data plan
assignment of IP addresses, allocation of VLANs, service type, and

data planning.
2-4
SJ-20140731105308-006|2014-10-20 (R1.0)
Chapter 3
Initial Configuration
Table of Contents
Accessing the Equipment Through the Console Port ..................................................3-1
Starting the Equipment ...............................................................................................3-3
Common Check Items ................................................................................................3-6
Common Configuration Items ...................................................................................3-22
Link Layer Initial Configuration .................................................................................3-39
Network Layer Initial Configuration ...........................................................................3-42
Configuring the Interconnection Between the Equipment and the Network
Management System ...............................................................................................3-51
Saving the Configuration ..........................................................................................3-52
3.1 Accessing the Equipment Through the Console

Port
This procedure describes how to establish a local configuration environment through the
console port, so that users can use the HyperTerminal provided by the Windows operating
system (Windows XP, for example) to establish a connection to the ZXR10 M6000-S.
Prerequisite
Before accessing the equipment through the console port, ensure that the equipment is
powered on and can operate normally.
Context
Figure 3-1 shows a local configuration environment, in which the COM port (serial
communication port, also called the RS-232 port) of a PC is connected to the console port
on the MPU board of the ZXR10 M6000-S.
Figure 3-1 Example of Connecting a PC to the Console Port of the ZXR10 M6000-S
Steps
1. Connect the COM port of a PC to the console port of the ZXR10 M6000-S by using a
serial cable.
3-1
SJ-20140731105308-006|2014-10-20 (R1.0)
For the properties of the console port, refer to the ZXR10 M6000-S (V3.00.10)
Carrier-Class Router Hardware Description.
2. Select Start > Programs > Accessories > Communications > HyperTerminal. The
Connection Description dialog box is displayed, see Figure 3-2.
Figure 3-2 Connection Description Dialog Box
3. Enter the name of the connection to be created in the Name text box, select an icon
for the connection, and click OK. The Connect To dialog box is displayed, see Figure
3-3.
Figure 3-3 Connect To Dialog Box
3-2
SJ-20140731105308-006|2014-10-20 (R1.0)
Chapter 3 Initial Configuration
4. Select COM1 from the Connect using list and click OK. The COM1 Properties dialog
box is displayed, see Figure 3-4.
Figure 3-4 COM1 Properties Dialog Box
5. Click the Restore Defaults button to restore the default property settings of the COM
port and click OK.
End of Steps
Result
After the above configuration:
l
l
If the equipment is not started, start the equipment and then perform the subsequent
check and initial configuration.
If the equipment is already started and is operating normally, press the Enter key. If
the ZXR10 prompt is displayed, it indicates that you successfully access the ZXR10
M6000-S and can configure and manage it as required.
3.2 Starting the Equipment

This procedure describes how to start the equipment locally or from the network when it is
powered on for the first time after installation.
3-3
SJ-20140731105308-006|2014-10-20 (R1.0)
Prerequisite
To start the equipment from the network, ensure that:
l
l
l
The equipment is not installed with a version file or the version file on the equipment
needs to be replaced.
The address of the management port on the equipment is already planned.
The FTP server and the version file for starting the equipment are already prepared.
To start the equipment locally, ensure that the equipment is already installed with a version
file and the version file does not need to be replaced.
Steps
l
Start the equipment from the network.

1. Set the boot menu.
When the equipment is started from the network, the boot menu should be
configured as follows:
Welcome to ZBOOT-3.0 System!
Copyright 1984-2014
ZTE .
Board Name
: USRUD
PCB / BOM/ EPLD
: 1 / 9 / 1
Bootrom Version
: 2.13
Boot Build
: 626667
Board Addr
: Rack 0,Shelf 0,Slot 11,Cpu 0,BkBrd 9
Current Boot Mode: Local(0)

Creation Date
: Sep 26 2014
Systerm Control
: 1
15:36:31
(SLAVE)
Reset Num/Reason : 3 / 0x942

Press any key to stop autoboot:
/*Press any key to enter the boot configuration mode*/

Do you want to manual config ? (Yy/Nn)
/*Select whether to configure the boot parameters manually*/
BootMenu Selection as follow:

0
- Auto boot
- Manual BOOT Config
- Show BOOT Config
- Print this help list
[Boot]:1
/*Select the Manual BOOT Config option*/
Config As SC? (Yy/Nn)
: y
/*Set the system controller*/
Boot Mode(0:Local 1:Net ):1

/*1 refers to that the current boot mode is to start the equipment
from the network*/
3-4
SJ-20140731105308-006|2014-10-20 (R1.0)

Base MAC Addr
: 34:34:77:ee:ff:50
/*Set the base MAC address of the equipment, which must be the
same as the base MAC address labeled outside the equipment*/
Mac Total
: 62
/*Set the maximum MAC offset, range: 1-63*/

Local IP
: 169.1.18.3
/*Set the IP address of the network management port*/

Net Mask
: 255.255.0.0
/*Set the subnet mask of the network management port*/

Config IPv6 Net?(Yy/Nn)
Gateway IP
: n
: 169.1.110.210
/*Set the IP address of the FTP gateway*/

Server IP
: 169.1.110.210
/*Set the IP address of the FTP server*/

File Name
: M6000-SV3.00.10_2.1.1.64.2.dbg.set
/*Set the name of the version file to be started*/

FTP Path
/*Set the path from which the equipment downloads the version
file.This parameter may not need configuration. Default: blank.*/
FTP Username
: M6000
/*Set the username for logging in to the FTP server.This parameter

may not need configuration. Default: Board name_CPU name*/
FTP Password
: *****
/*Set the password for logging in to the FTP server. This parameter
may not need configuration. The default password is the same as the
user name.*/
Serial Authenticate (Yy/Nn) : n
/*Set whether to enable the serial port authentication*/
Enable Password
: ******
/*Set the enable password. This parameter may not need

configuration. Default: "zxr10", which can be used as
the enable password of the 18th-level permission.*/
Format Storage Disk(Yy/Nn)
:n
Manual boot now? (Yy/Nn) y

/*Enter y at the prompt and press the Enter key to start
the equipment*/
2. Wait a few minutes until the following information is displayed, which indicates that
the equipment is started successfully.
********************************************************************
Welcome to ZXR10 Carrier-Class High-end Router of ZTE Corporation
********************************************************************
ZXR10>
3-5
SJ-20140731105308-006|2014-10-20 (R1.0)
Start the equipment locally.

1. Set the boot menu.
When the equipment is started locally, the boot menu should be configured as
follows:
Welcome to ZBOOT-3.0 System!

Copyright 1984-2014
ZTE .
Board Name
: USRUD
PCB / BOM/ EPLD
: 1 / 9 / 1
Bootrom Version
: 2.13
Boot Build
: 626667
Board Addr
: Rack 0,Shelf 0,Slot 10,Cpu 0,BkBrd 9
Current Boot Mode: Local(0)

Creation Date
: Sep 26 2014
Systerm Control
: 1
15:36:31
(SLAVE)
Reset Num/Reason : 10 / 0x42224332

Press any key to stop autoboot:
boot from local, is running <1>!
2. Wait a few minutes until the following information is displayed, which indicates that
the equipment is started successfully.
********************************************************************
********************************************************************
ZXR10>
End of Steps
3.3 Common Check Items

After the startup of the equipment and before the initial configuration, you must check the
following items of the equipment:
l
l
l
l
Software version
Base MAC address
Status of synchronization between the active and standby main control boards
Status of every hardware module
3.3.1 Checking the Software Version

This procedure describes how to query the current software version of the equipment and
to verify that it complies with the requirement.
3-6
SJ-20140731105308-006|2014-10-20 (R1.0)
Steps
1. Run the show version command to query the version information.
The following example shows how to query the version information:
ZXR10#show version
ZXR10 M6000-8S
ZTE ZXR10 Software, Version: M6000 V3.00.10(2.1.1), Release software
Copyright (c) 2014 by ZTE Corporation
Build on 2014/10/09 08:56:30
System image file is <sysdisk0: verset/M6000-SV3.00.10_2.1.1.64.2.dbg.set>, file
size is 2,011,224,702 Bytes
System image is loaded from local
System uptime is 0 day(s), 0 hour(s), 8 minute(s)
[MPU, shelf 0, slot 10]:

System BaudRate :
9,600 bps
MPU-0/10/0, SSC:
Board Name
SRU-1H
Bootrom Version :
V2.13
Creation Date
2014/09/26 15:51:25
System Nvram
8,192 bytes
System Memory
4,096 Mbytes
Uptime is 0 day(s), 0 hour(s), 8 minute(s)
[MPU, shelf 0, slot 11]:

System BaudRate :
9,600 bps
MPU-0/11/0, MSC:
Board Name
SRU-1A
Bootrom Version :
V2.13
Creation Date
2014/09/26 15:51:25
System Nvram
8,192 bytes
System Memory
4,096 Mbytes
[PFU, shelf 0, slot 0]:

PFU-0/0/0:
Board Name
PFU-40-A2
Bootrom Version :
V1.03
Creation Date
2012/11/20 18:09:19
System Nvram
8,192 bytes
System Memory
4,096 Mbytes
System Flash
256 Mbytes

Interface Card 0: 08P48-SFP
Interface Card 0 Uptime is 0 day(s), 0 hour(s), 1 minute(s)
3-7
SJ-20140731105308-006|2014-10-20 (R1.0)

Interface Card 1: 08P48-SFP

PFU-0/2/0:
Board Name
PFU-40-A2
Bootrom Version :
V1.03
Creation Date
2012/11/20 18:09:19
System Nvram
8,192 bytes
System Memory
4,096 Mbytes
System Flash
256 Mbytes

Interface Card 0: 02XGE-SFP+-S

PFU-0/3/0:
Board Name
PFU-20-H2
Bootrom Version :
V2.06
Creation Date
2013/09/07 14:18:21
System Nvram
8,192 bytes
System Memory
4,096 Mbytes
System Flash
128 Mbytes

PFU-0/5/0:
Board Name
PFU-100-H2
Bootrom Version :
V2.02
Creation Date
2013/11/05 15:51:18
System Nvram
8,192 bytes
System Memory
4,096 Mbytes
System Flash
128 Mbytes

Interface Card 0: 01XLGE-CFP-S
Interface Card 1: 01XLGE-CFP
[SMU, shelf 0, slot 6]:

SMU-0/6/0:
Board Name
GSU-A2
Bootrom Version :
V2.08
Creation Date
2013/11/05 15:55:42
System Nvram
8,192 bytes
3-8
SJ-20140731105308-006|2014-10-20 (R1.0)

System Memory
2,048 Mbytes
System Flash
128 Mbytes
SPU-0/6/1:
Board Name
GIU-A-I
Bootrom Version :
V2.06
Creation Date
2012/12/03 12:46:45
System Nvram
8,192 bytes
System Memory
8,192 Mbytes
System Flash
128 Mbytes
SPU-0/6/2:
Board Name
GIU-A-I
Bootrom Version :
V2.06
Creation Date
2012/12/03 12:46:45
System Nvram
8,192 bytes
System Memory
8,192 Mbytes
System Flash
128 Mbytes
SPU-0/6/3:
Board Name
GIU-A-I
Bootrom Version :
V2.06
Creation Date
2012/12/03 12:46:45
System Nvram
8,192 bytes
System Memory
8,192 Mbytes
System Flash
128 Mbytes
SPU-0/6/4:
Board Name
GIU-A-I
Bootrom Version :
V2.06
Creation Date
2012/12/03 12:46:45
System Nvram
8,192 bytes
System Memory
8,192 Mbytes
System Flash
128 Mbytes

PFU-0/7/0:
Board Name
PFU-20-H2
Bootrom Version :
V2.06
Creation Date
2013/09/07 14:18:21
3-9
SJ-20140731105308-006|2014-10-20 (R1.0)

System Nvram
8,192 bytes
System Memory
2,048 Mbytes
System Flash
128 Mbytes
[SFU, shelf 0, slot 8]:

SFU-0/8/0:
Board Name
SFU-8-H
Bootrom Version :
V2.01
Creation Date
2014/04/01 16:55:09
System Nvram
8,192 bytes
System Memory
1,024 Mbytes
System Flash
256 Mbytes
[SFU, shelf 0, slot 9]:

SFU-0/9/0:
Board Name
SFU-8-H
Bootrom Version :
V2.01
Creation Date
2014/04/01 16:55:09
System Nvram
8,192 bytes
System Memory
1,024 Mbytes
System Flash
256 Mbytes
End of Steps
Result
In the above example, the current version of the ZXR10 M6000-S is Version: M6000
V3.00.10(2.1.1). Perform the following based on whether it is the same as that required in
the service planning:
l If the current version number of the ZXR10 M6000-S is the same as that in the service
planning, perform the subsequent configurations as required.
l If the current version number of the ZXR10 M6000-S is different from that in the service
panning, upgrade the software version.
3.3.2 Checking the Base MAC Address

This procedure describes how to query the base MAC address of the equipment and to
verify that it is the same as the MAC address labelled on the shelf.
Steps
1. Run the show nvram command to query the mng-ip-address of the equipment.
The following is an example:
3-10
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10#show nvram
imgfile-location
: local
mng-ip-address
: 169.1.10.187 255.255.0.0
boot-server
: 169.1.85.66
default-gateway
: 169.1.85.66
boot-username
: m6000
ftp-path
: /
mng-ipv6-address
: 169:1:10:0:0:0:0:187/64
boot-ipv6-server
: 169:1:10:0:0:0:0:200
def-ipv6-gateway
: 169:1:10:0:0:0:0:200
mng-ipv6-enable
: disable
boot-from
: ipv4-server
2. Query the base MAC address of the equipment through the mng port and compare it
with the MAC address labelled on the shelf.
ZXR10#show interface mgmt_eth
mgmt_eth is up, line protocol is up, IPv4 protocol is up, IPv6 protocol is down
Hardware is Management Ethernet, address is 4c09.b4f2.07c0
Internet address is 169.7.2.33/16
BW 100000 Kbps
IP MTU 1500 bytes
MTU 1514 bytes
Current mgmt port position:shelf 0, slot 3
Holdtime is 0 sec(s)
The port is electric
The MDIMode of the port is reserved
Loopback cancel
Duplex full
Negotiation auto
ARP type ARP
ARP Timeout 04:00:00
Last Clear Time : 2014-05-26 16:15:22
Last Refresh Time: 2014-05-28 16:39:00
120s input rate : 947Bps
7Pps
120s output rate: 458Bps
3Pps
Peak rate:
input
3265Bps
peak time
2014-05-26 16:17:50
output
5488Bps
peak time
2014-05-26 16:18:00
Intf utilization: input 0%
output 0%
HardWareCounters:
In_Bytes
153562460
In_Packets
1646340
In_CRC_ERROR
In_Unicasts
381263
In_Broadcasts
1265049
In_Multicasts
28
In_Undersize
In_Oversize
In_64B
N/A
In_65_127B
N/A
3-11
SJ-20140731105308-006|2014-10-20 (R1.0)

In_128_255B
N/A
In_256_511B
N/A
In_512_1023B
N/A
In_1024_1518B
N/A
In_1519_MaxB
N/A
E_Bytes
65911561
E_Packets
341778
E_CRC_ERROR
E_Unicasts
332817
E_Broadcasts
8961
E_Multicasts
E_Undersize
E_Oversize
E_64B
N/A
E_65_127B
N/A
E_128_255B
N/A
E_256_511B
N/A
E_512_1023B
N/A
E_1024_1518B
N/A
E_1519_MaxB
N/A
E_SingCollision
N/A
E_MultCollision
N/A
E_LateCollision
N/A
E_ExceCollision
N/A
End of Steps
Result
If the base MAC address is different from the MAC address labelled on the shelf, restart
the equipment and then configure its base MAC address to the MAC address on the label.
For the procedure of starting the equipment, refer to 3.2 Starting the Equipment.
3.3.3 Checking the Status of Synchronization Between the Active

and Standby Main Control Boards
This procedure describes how to query the status of synchronization between the active
and standby main control boards.
Steps
1. Run the show synchronization command to query the status of the active/standby
synchronization.
ZXR10#show synchronization
======================================================================
======================================================================
LE
: the name of logic entity
Location
: the location of logic entity in the system
Status
: the status of logic entity(master or slave)
Sync-state : the state of synchronization

======================================================================
======================================================================
LE
Location
Status
Sync-state
======================================================================
T_SC
MPU-0/10/0
Slave
Synchronized
3-12
SJ-20140731105308-006|2014-10-20 (R1.0)

---------------------------------------------------------------------T_SC
MPU-0/11/0
Master
Synchronized
----------------------------------------------------------------------
End of Steps
Result
If Sync-state is Synchronized, it indicates that the active/standby synchronization is
completed.
3.3.4 Checking the Board Status

This procedure describes how to query the status, CPU usage, and memory usage of a
board of the equipment.
Steps
1. Run the show processor [<shelf>[slot]] command to query the status information of
boards of the ZXR10 M6000-S.
In the above command, [<shelf>[slot]] indicates the location of the board to be queried.
<shelf> is the number of the shelf where the equipment is located. By default, the
shelf number of the ZXR10 M6000-S is 0. <slot> is the slot number of the board to be
queried. You should verify that the displayed slot number on the PC is the same as
the actual slot number.
ZXR10#show processor
================================================================================
================================================================================
Character: CPU current character in system
MSC
: Master-SC in Cluster System
SSC
: Slave-SC in Cluster System
N/A
: None-SC in Cluster System
CPU(5s)
: CPU usage ratio measured in 5 seconds
CPU(1m)
: CPU usage ratio measured in 1 minute
CPU(5m)
: CPU usage ratio measured in 5 minutes
Peak
: CPU peak usage ratio measured in 1 minute
PhyMem
: Physical memory (megabyte)
FreeMem
: Free memory (megabyte)
Mem
: Memory usage ratio
================================================================================
================================================================================
Character CPU(5s) CPU(1m) CPU(5m) Peak PhyMem FreeMem Mem

================================================================================
3-13
SJ-20140731105308-006|2014-10-20 (R1.0)

PFU-0/0/0
N/A
36%
30%
30%
36%
4096
2077
49.292%
-------------------------------------------------------------------------------PFU-0/2/0
N/A
12%
13%
13%
19%
4096
2080
49.219%
-------------------------------------------------------------------------------PFU-0/3/0
N/A
5%
8%
8%
11%
4096
2485
39.331%
-------------------------------------------------------------------------------PFU-0/5/0
N/A
10%
13%
14%
19%
4096
2013
50.854%
-------------------------------------------------------------------------------SMU-0/6/0
N/A
2%
2%
2%
3%
2048
1234
39.746%
-------------------------------------------------------------------------------SPU-0/6/1
N/A
1%
1%
1%
1%
8192
7452
9.033%
-------------------------------------------------------------------------------SPU-0/6/2
N/A
1%
1%
1%
1%
8192
7451
9.045%
-------------------------------------------------------------------------------SPU-0/6/3
N/A
1%
1%
1%
1%
8192
7451
9.045%
-------------------------------------------------------------------------------SPU-0/6/4
N/A
1%
1%
1%
1%
8192
7450
9.058%
-------------------------------------------------------------------------------PFU-0/7/0
N/A
10%
8%
8%
12%
2048
453
57.881%
-------------------------------------------------------------------------------SFU-0/8/0
N/A
4%
4%
3%
4%
1024
798
22.070%
-------------------------------------------------------------------------------SFU-0/9/0
N/A
4%
4%
4%
4%
1024
798
22.070%
-------------------------------------------------------------------------------MPU-0/10/0
SSC
3%
3%
3%
3%
4096
2174
46.924%
-------------------------------------------------------------------------------MPU-0/11/0
MSC
2%
2%
2%
3%
4096
1697
58.569%
--------------------------------------------------------------------------------
End of Steps
Result
Normally, the CPU usage of a board should not exceed 70%, the memory usage should
not exceed 80%, and the displayed slot number is correct.
Before large-scale service deployment, if the CPU or memory usage is very high for a long
time, contact ZTE technical support.
3.3.5 Checking the Interface Status

This procedure describes how to query the status of interfaces on the equipment. Before
the intial configuration, you must verify that the corresponding interfaces operate properly.
Steps
1. Run the show ip interface brief command to query the status information of all the
interfaces.
3-14
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10#show ip interface brief
Interface
IP-Address
Mask
Admin Phy
Prot
gei-0/1/0/1
unassigned
unassigned
up
down down
gei-0/1/0/1.00000001
unassigned
unassigned
down
down down
gei-0/1/0/1.00000002
unassigned
unassigned
up
down down
gei-0/1/0/2
20.0.0.55
255.255.255.0
up
up
up
gei-0/1/0/2.00000002
unassigned
unassigned
up
up
down
gei-0/1/0/3
unassigned
unassigned
down
down down
gei-0/1/0/4
unassigned
unassigned
down
down down
gei-0/1/0/5
unassigned
unassigned
up
down down
gei-0/1/0/6
unassigned
unassigned
down
down down
gei-0/1/0/7
unassigned
unassigned
down
down down
gei-0/1/0/8
unassigned
unassigned
down
down down
gei-0/1/0/9
unassigned
unassigned
down
down down
gei-0/1/0/10
unassigned
unassigned
down
down down
gei-0/1/0/11
unassigned
unassigned
down
down down
gei-0/1/0/12
unassigned
unassigned
down
down down
gei-0/1/0/13
unassigned
unassigned
down
down down
gei-0/1/0/14
unassigned
unassigned
down
down down
gei-0/1/0/15
unassigned
unassigned
down
down down
gei-0/1/0/16
unassigned
unassigned
down
down down
gei-0/1/0/17
unassigned
unassigned
down
down down
gei-0/1/0/18
unassigned
unassigned
up
down down
gei-0/1/0/19
unassigned
unassigned
up
down down
gei-0/1/0/20
unassigned
unassigned
down
down down
ulei-0/1/0/1
unassigned
unassigned
down
up
down
ulei-0/1/0/1.1
unassigned
unassigned
down
up
down
ulei-0/1/0/2
unassigned
unassigned
down
up
down
ulei-0/1/0/6
unassigned
unassigned
down
up
down
Normally, the IP address, mask, administrative status, physical status, and protocol
status of every interface will be displayed.
2. Run the show interface <interface-name> command to query details of a particular
interface.
ZXR10#show interface gei-0/1/0/2
gei-0/1/0/2 is up, line protocol is up, IPv4 protocol is up, IPv6 protocol is down
/*Whether the protocol on the interface is up*/
Hardware is Gigabit Ethernet, address is 4c09.b4f2.07c0
/*Hardware type and physical address of the interface*/
BW 1000000 Kbps
/*IP address of the interface*/

/*Bandwidth of the interface*/
3-15
SJ-20140731105308-006|2014-10-20 (R1.0)

IP MTU 1500 bytes
/*Layer-3 MTU value of the interface*/
MTU 1600 bytes
/*Layer-2 MTU value of the interface*/
MPLS MTU 1500 bytes
/*MPLS MTU value of the interface*/
/*Hold time of the interface*/
The port is optical

/*Optoelectronic attribute of the interface*/
The MDIMode of the port is not supported
/*MDI mode of the interface*/
Loopback cancel
/*Loopback mode of the interface*/
Duplex full
/*Working mode of the interface*/
Negotiation auto
/*Negotiation mode of the interface*/
SD-FER disable
ARP type
ARP
/*ARP information of the interface*/
ARP Timeout 04:00:00

Last Clear Time : 2014-05-26 16:19:04
/*The last time when the statistics information

of the interface is cleared and refreshed*/
1Pps
/*Rate of input packets in 120 seconds on the interface*/

0Pps
/*Rate of output packets in 120 seconds on the interface*/

Peak rate:
input
219Bps
output
115Bps
peak time
2014-05-28 14:20:40
peak time
2014-05-28 14:05:30
output 0%
/*Usage of the input or output bandwidth*/

HardWareCounters:
In_Bytes
29012917
In_Packets
299213
In_CRC_ERROR
In_Unicasts
11457
In_Broadcasts
34668
In_Multicasts
253088
In_Undersize
In_Oversize
In_64B
40392
In_65_127B
250075
In_128_255B
8741
In_256_511B
In_512_1023B
In_1024_1518B
In_1519_MaxB
E_Bytes
14596883
E_Packets
171591
E_CRC_ERROR
N/A
E_Unicasts
11441
E_Broadcasts
17333
E_Multicasts
142817
E_Undersize
E_Oversize
N/A
E_64B
23038
E_65_127B
139921
E_128_255B
8627
E_256_511B
E_512_1023B
E_1024_1518B
E_1519_MaxB
E_SingCollision
N/A
E_MultCollision
N/A
E_LateCollision
N/A
E_ExceCollision
N/A
StreamCounters
3-16
SJ-20140731105308-006|2014-10-20 (R1.0)

In_Bytes
27817551
In_Packets
299228
In_Discards
173297
In_V4Bytes
5670083
In_V4Pkts
65661
In_V6Bytes
In_V6Pkts
In_UpsendCar_Drop
E_Bytes
13564819
E_Packets
171598
E_Discards
E_V4Bytes
E_V4Pkts
E_V6Bytes
E_V6Pkts
End of Steps
3.3.6 Checking the Fan Status

This procedure describes how to query the statuses of fans of the equipment. Fan modules
dissipate heat generated by the equipment. Therefore, you should ensure that all the fan
modules operate properly before the initial configuration.
Steps
1. Run the show fan command to query the statuses of fans.
ZXR10#show fan
[shelf 0 LCC]:
Group 0: online
Fan speed mode: auto
Fan
name: FAN TRAY
Index
Status
Speed
work normally
59%
work normally
59%
work normally
59%
work normally
59%
Group 1: online
Fan speed mode: auto
Fan
name: FAN TRAY
Index
Status
Speed
work normally
79%
work normally
81%
work normally
79%
work normally
81%
End of Steps
Result
The displayed status of fans must be the same with their actual status. If work normally
is displayed, the corresponding fan is operating normally.
3-17
SJ-20140731105308-006|2014-10-20 (R1.0)
Fans of the ZXR10 M6000-S series equipment vary. Therefore, the displayed information
may vary with the actual equipment.
3.3.7 Checking the Power Status

This procedure describes how to query the statuses of power supplies of the equipment.
Before the initial configuration, you must ensure that the power supplies of the equipment
operate properly.
Steps
1. Run the show power command to query the power status.
ZXR10#show power
[shelf 0 LCC]:
Total power capacity
: 2678.00W
Power type
: AC
Total used power
Power group numbers : 2
Power modules per group: 1

Redundancy Type
: 601.47W
Division numbers
: 1
: 1+1
Group A power capacity : 0.00W

Group B power capacity : 2678.00W
Used power
Supply
Phy
Power
Com
Run
Division Module name
Status
status
Status
Status
A0
UNKNOWN
offline
N/A
N/A
N/A
B0
PPC34 A008
online
normal
normal
normal
Power
Power
: 601.47W
Power
Module Capacity
Power
Output
Output
Power
Voltage
Current Alloted
Power
Software
Available Version
A0
N/A
N/A
N/A
N/A
N/A
N/A
B0
2678.00W
53.56V
11.23A
601.47W
2076.53W
V4.9
End of Steps
Result
The displayed power status must be the same as the actual power status. If normal is
displayed, the power supply is operating normally.
Power supplies of the ZXR10 M6000-S series equipment vary. Therefore, the displayed
information varies with the actual equipment.
3.3.8 Checking the Temperature of the Equipment

This procedure describes how to query the temperature of the equipment.
3-18
SJ-20140731105308-006|2014-10-20 (R1.0)
Steps
1. Run the show temperature command to query the temperature of the equipment.
ZXR10#show temperature detail 0 3
/*Query the temperature of the board in slot 3*/
----------------------------------------------------BoardType : Type of board
I2C
: Inter integrated circuit
Addr
: Address of check point
Status
: Status of check point
Minor
: Slight alarm value (celsius)
Major
: Serious alarm value (celsius)
Fatal
: Fatal alarm value (celsius)
Temper
: Current temperature (celsius)
-----------------------------------------------------
[shelf 0, slot 3]
BoardType I2C Addr
Status
Minor Major Fatal Temper
----------------------------------------------------PFU
48
Normal
85
90
95
38
PFU
50
Normal
85
90
95
35
PFU
52
Normal
90
95
100
37
PFU
82
Normal
80
85
90
39
End of Steps
Result
If the temperature of the board is lower than the value of Minor and the Status is
Normal, the board operates normally. If the temperature of the board is higher than the
value of Minor and the Status is Abnormal, the board operates abnormally.
3.3.9 Checking the Alarm Information

This procedure describes how to enable the alarm function and terminal monitoring switch
of the equipment and to query the alarm information.
Steps
1. Enter the global configuration mode and run the following commands to enable
the alarm function of the equipment and to set alarm levels and the interval for
automatically saving alarms.
ZXR10#configure terminal
ZXR10(config)#logging on
3-19
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10(config)#logging console warnings
ZXR10(config)#logging trap-enable warnings
2. Enter the privileged mode and run the terminal monitor command to enable the
terminal monitoring switch, so that you can view alarms in real time on the current
terminal.
ZXR10#terminal monitor
3. Run the show logging alarm command to query alarms. You can use different
parameters in this command to query alarms in a particular time period, alarms of a
particular type, or alarms of a particular level.
ZXR10#show logging alarm
End of Steps
Example
The following example shows how to query the alarm information after enabling the alarm
function and terminal monitoring switch:
1. When there are alarms generated or cleared, the terminal will print the alarm
information in real time.
For example, if you disable virtual interface Loopback 7, two alarms indicating that the
status of interface Loopback 7 is down will be generated.
ZXR10(config)#interface loopback7
ZXR10(config-if-loopback7)#shutdown
An alarm 150111 ID 39 level 5 occurred at 01:53:55 05-29-2014 sent by
ZXR10 MPU-0/3/0
%IP% Interface layer2 status The interface(index=262167,name='loopback7')
layer2 status turned into protocol DOWN
ZXR10 MPU-0/3/0
%IP% Interface status The interface(index=262167,name='loopback7')
turned into protocol DOWN
If you re-enable interface Loopback 7, the system prompts that alarms are already
cleared.
ZXR10(config)#interface loopback7
ZXR10(config-if-loopback7)#no shutdown
An alarm 150111 ID 39 level 5 cleared at 01:56:29 05-29-2014 sent by
ZXR10 MPU-0/3/0
%IP% Interface layer2 status The interface(index=262167,name='loopback7')
layer2 status turned into protocol UP
3-20
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10 MPU-0/3/0
%IP% Interface status The interface(index=262167,name='loopback7')
turned into protocol UP
2. Run the show logging alarm command to query all the occurred alarms.
ZXR10#show logging alarm
A notification 360106 ID 42 level 7 occurred at 02:14:48 05-29-2014 sent by
ZXR10 MPU-0/3/0
%ADM-MGR% User login!
User-account who login, access type cli,vty no 1,
ip address 169.7.2.55.
A notification 360107 ID 41 level 7 occurred at 02:14:25 05-29-2014 sent by

ZXR10 MPU-0/3/0
%ADM-MGR% User logout!
User-account who logout, access type cli,vty no 1,
ip address 169.7.2.55.

ZXR10 MPU-0/3/0
%IP% Interface status
The interface(index=262167,name='loopback7')
turned into protocol UP

ZXR10 MPU-0/3/0
%IP% Interface layer2 status

ZXR10 MPU-0/3/0
turned into protocol DOWN

ZXR10 MPU-0/3/0
layer2 status turned into protocol DOWN

ZXR10 MPU-0/3/0
turned intoprotocol UP

ZXR10 MPU-0/3/0
3-21
SJ-20140731105308-006|2014-10-20 (R1.0)
3.4 Common Configuration Items

After the startup of the equipment and before the service configuration, you must configure
the following:
l
l
l
l
l
Configuring the equipment name

Configuring the system time
Configuring the syslog function
Configuring the enable password
Configuring whether users can remotely access the equipment
3.4.1 Configuring the Equipment Name

The default name of the ZXR10 M6000-S is ZXR10. This procedure describes how to
configure the equipment name based on the network planning for the convenience of
equipment identification and maintenance.
Steps
1. Enter the privileged mode and run the configure terminal command.
/*Enter the configuration mode*/
Enter configuration commands, one per line. End with CTRL/Z.

ZXR10(config)#
2. Run the hostname <host-name> command to modify the name of the equipment.
<host-name> is the new name of the equipment, a string of 132 characters.
To restore the default equipment name, use the no form of this command.
The following example shows how to configure the equipment name to M6000:
ZXR10(config)#hostname M6000
M6000(config)#
End of Steps
Result
After the configuration, the following information is displayed and indicates that the
equipment name is modified to M6000:
M6000(config)#exit
M6000#
3.4.2 Configuring the System Time

This procedure describes how to configure the system time for the following purposes:
l
l
The ZXR10 M6000-S can work well with other devices.

The time of alarms and logs is accurate.
3-22
SJ-20140731105308-006|2014-10-20 (R1.0)
Context
The following procedure uses data plans in Table 3-1 as an example to describe how to
configure the system time.
Table 3-1 Data Plans for System Time Configuration
Item
Data Plan
Description
UTC time
Zero o'clock on January 1,
The equipment calculates the current time
2013
based on the UTC time and the time zone.
UTC + 08:00 (Beijing)
You can run the clock timezone <timezone><ho
Time zone
urs-offset><minutes-offset> command to set the

time zone.
The equipment calculates the current system
time by adding or subtracting the hours or
minutes specified in the above command.
NTP
IP address of the NTP server:
The time of the equipment should be the same
1.1.1.1
as that of the NTP server.
Steps
1. Set the UTC time to zero o'clock on January 1, 2013.
Run the clock set <current-time><current-date> command to configure the UTC time as
follows:
ZXR10#clock set 00:00:00 01-01-2013
<current-time>: the current time, format: hh:mm:ss, for example, 00:00:00.

<current-date>: the current date, format: MM-DD-YY, range: 1-1-2001 to 12-31-2037,
for example, 01-01-2013.
2. Set the time zone (the offset from the UTC time) of the equipment to the Beijing time
zone, which equals an offset of +8 hours from the UTC time.
Run the clock timezone <timezone-name><hours-offset>[<minutes-offset>] command to
configure the time zone as follows:
ZXR10(config)#clock timezone Beijing 8 0
<timezone-name>: name of the time zone, length: 132 characters, for example,
Beijing.
<hours-offset>: hourly offset of the time zone, range: -1212, for example, 8.
[<minutes-offset>]: minute offset of the time zone, range: 059, for example, 0.
3-23
SJ-20140731105308-006|2014-10-20 (R1.0)
Note:
The ZXR10 M6000-S obtains the current system time by adding or subtracting the
corresponding offset on the basis of the UTC time. Based on the above configuration,
the system time can be obtained by adding 8 hours and 0 minutes on the basis of the
UTC time, which means that the system time is 08:00:00 Tues Jan 1 2013.
3. (Optional) Configure the NTP function.

NTP is a time synchronization protocol for members distributed across a network, and
NTP packets are transmitted through UDP. NTP devices automatically adjust their
system clocks to the same time through the exchange of NTP packets.
Run the ntp server {[vrf <vrf-name>]<ipv4-address>|<ipv6-address>} priority [[version
<1-4>],[key <1-255>],[lock | unlock]] command to configure the NTP function as follows:
ZXR10(config)#ntp enable
ZXR10(config)#ntp server 1.1.1.1 priority 1
End of Steps
Result
The following example shows how to run the show clock command to query the current
system time.
ZXR10#show clock
08:00:00
Beijing
Tues Jan 1 2013
In the above example, the current system time is 8 o'clock on January 1, 2013 and the
time zone is the Beijing time zone, which are the same as the data plan.
3.4.3 Configuring the Syslog Function

This procedure describes how to enable the syslog function of the ZXR10 M6000-S, so that
it can communicate with the preset syslog server through the syslog protocol and upload
its log information to the syslog server for future use.
Prerequisite
The addresses of the FTP server and the syslog server are already planned.
configure the syslog function:
Table 3-2 Data Plans for the FTP and Syslog Servers
Server
IP Address
FTP Server
168.1.70.100
3-24
SJ-20140731105308-006|2014-10-20 (R1.0)
Server
IP Address
Syslog Server
192.168.0.100
Context
The syslog function allows users to set and query log information, which provides
convenience for daily router maintenance. Through log information, maintenance
personnel can acquire the alarms generated by the router and the interface status
changes in real time.
The log information can be displayed on the configuration terminal in real time or saved to
the router or back-end log server in the file format.
Steps
1. Enable the log function.
2. Configure the level of alarms to be reported to the syslog server.

The following example shows how to set the alarm level to ERRORS:
ZXR10(config)#syslog level errors
3. Configure a syslog category.

The following example shows how to set the category whose name is syslog:
ZXR10(config)#syslog-server facility syslog
4. Configure the source address of the syslog server.

The following example shows how to set the source address of the syslog server to
169.1.5.5:
ZXR10(config)#syslog-server source ipv4 169.1.5.5
5. Configure the IP address of the syslog server.

ZXR10(config)#syslog-server host 192.168.0.100
6. Configure to upload the log information to the FTP server in the format of a log file.
The following example shows how to configure to upload the log information to the
FTP server as the zxralarm.log file:
ZXR10(config)#logging ftp notifications vrf mng 168.1.70.100 target target
zxralarm.log
End of Steps
Result
The following example shows how to run the show logging configuration command to verify
that the configuration is successful:
ZXR10#show logging configuration
logging on
3-25
SJ-20140731105308-006|2014-10-20 (R1.0)

syslog level errors
syslog-server host 192.168.0.100 fport 514 lport 514 alarmlog cmdlog
debugmsg servicelog braslog natlog
syslog-server facility syslog
logging ftp notifications vrf mng 168.1.70.100 target target zxralarm.log
syslog-server source ipv4 169.1.5.5
Verify that the information about the log server is normal and the log information file is
saved to the specified FTP server.
3.4.4 Configuring the Location and Contact Information

This procedure describes how to configure the location and contact information of the
equipment based on the network plan for the convenience of maintenance.
Steps
1. Enter the privileged mode and run the configure terminal command.
The following is a configuration example:
ZXR10(config)#
2. Run the location <position> command to set the location information of the equipment.
<position> indicates the location information which should be 1 to 200 characters in
length and supports spaces.
ZXR10(config)#location NO. 55, Hi-tech Road South, ShenZhen, P.R.China
3. Run the contact <address> command to set the contact information of the equipment.
<address> indicates the address of the equipment which should be 1 to 200 characters
in length and supports spaces.
ZXR10(config)#contact NO. 55, Hi-tech Road South, ShenZhen, P.R.China
End of Steps
Result
After the configuration, run the show location and show contact commands to query the
location and contact information of the equipment.
ZXR10#show location
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
ZXR10#show contact
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
3-26
SJ-20140731105308-006|2014-10-20 (R1.0)
3.4.5 Configuring Information Saved in the NVRAM

This procedure describes how to configure the information saved in the NVRAM, including:
l
l
l
l
IP address of the FTP server and user name and password for logging in to the server
IP address of the default gateway
FTP path
Startup mode of the equipment and name of the version file to be started
Context
NVRAM is a component of the MPU board used for saving the user name, password for
accessing the FTP server, and other information.
Steps
1. Run the nvram boot-server <ip-address> command to set the IP address of the FTP
server.
2. Run the nvram boot-username <boot-username> command to set the user name of the
FTP server.
<boot-username> indicates the user name of the FTP server and its length is from 1 to
19 characters.
3. Run the nvram boot-password <password> command to set the password of the FTP
server.
<password> indicates the password of the FTP server and its length is from 1 to 19
characters.
4. Run the nvram default-gateway <ip-address> command to set the IP address of the
default gateway.
5. Run the nvram ftp-path [<path>] command to set the FTP path.
<path> indicates the FTP path and its maximum length is 79 characters.
6. Run the nvram imgfile-location {local | network <file-name>} command to set the
startup mode of the equipment and the name of the version file to be started.
local indicates starting the equipment locally and network indicates starting the
equipment from the network.
<file-name> indicates the path of the version file to be started and its length is from 1
to 79 characters.
End of Steps
Example
The following example shows how to set the information saved in the NVRAM:
ZXR10(config)#nvram boot-server 192.168.10.10
ZXR10(config)#nvram boot-username m6000
ZXR10(config)#nvram boot-password m6000
3-27
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10(config)#nvram default-gateway 192.168.10.10
ZXR10(config)#nvram ftp-path /
ZXR10(config)#nvram imgfile-location network M6000V3.00.10_1.1.0.42.2.set
3.4.6 Configuring the Enable Password

An administrator can configure the enable password of the system, which provides security
authentication of login users.
Steps
1. In the global configuration mode, run the enable secret level <1-18><password>
command to configure the passwords for privilege levels 1 to 18.
ZXR10(config)#enable secret level 2 222
ZXR10(config)#enable secret level 3 333
ZXR10(config)#enable secret level 15 ZXR10
ZXR10(config)#enable secret level 18 ZXR10123
2. In the global configuration mode, run the nvram enable-password <old password><new
password ><new password > command to modify the enable password of the system
preset during the startup.
The following example shows how to modify the enable password ZXR10 to abc:
ZXR10(config)#nvram enable-password ZXR10 abc abc
End of Steps
Result
To verify that the enable password is configured correctly, perform the following operations
(For example, enable 2 and enable 18):
ZXR10#disable
/*Enter disable at the prompt to enter the user mode*/
ZXR10>show privilege
/*Query the current privilege level*/
Current privilege level is 1
ZXR10>enable 2
/*The current privilege level is 1*/
/*Enter enable 2 at the prompt to enter privilege level 2*/
Password:
/*Enter 222 as the password for privilege level 2,
which is displayed in encrypted format*/
ZXR10#show privilege
ZXR10>enable 18
/*The current privilege level is 2.*/
/*Enter enable 18 at the prompt to enter privilege level 18*/
Password:
/*Enter ZXR10123 as the password for privilege level 18,
which is displayed in encrypted format*/
3-28
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10#show privilege
/*The current privilege level is 18*/
3.4.7 Configuring Telnet

This procedure describes how to configure telnet on the ZXR10 M6000-S, so that users
can remotely access the equipment through telnet.
Context
The following procedure uses data plans in Table 3-3 as an example to describes how to
configure telnet.
Table 3-3 Data Plans for Telnet Configuration
Item
Data Plan
Description
Username
who
Password
who
Maximum number of users that
10
Default: 15
User privilege level
15
Default: 0
Idle timeout
30 minutes
Maximum length of time for which the
can log in to the equipment at

one time
telnet connection can be idle, default: 120

minutes. If the preset maximum length of
time is reached, the idle connection will
be disconnected.
Absolute timeout
120 minutes
Maximum length of time for which the

telnet user is allowed to be online, default:
1440 minutes. If the preset maximum
length of time is reached, the user will be
kicked offline.
Authentication mode
Local authentication
AAA authentication template bound to

the telnet user.
Authorization mode
Local authorization
AAA authorization template bound to the

telnet user.
Steps
1. Enter the system-user mode, create a user and bind it to a particular authentication
template and authorization template.
ZXR10(config)#system-user
ZXR10(config-system-user)#user-name who
ZXR10(config-system-user-username)#bind authentication-template 1
ZXR10(config-system-user-username)#bind authorization-template 1
3-29
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10(config-system-user-username)#password who
ZXR10(config-system-user-username)#exit
ZXR10(config-system-user)#authentication-template 1
ZXR10(config-system-user-authen-temp)#bind aaa-authentication-template 2001
ZXR10(config-system-user-authen-temp)#exit
ZXR10(config-system-user)#authorization-template 1
ZXR10(config-system-user-author-temp)#bind aaa-authorization-template 2001
ZXR10(config-system-user-author-temp)#local-privilege-level 15
ZXR10(config-system-user-author-temp)#exit
ZXR10(config-system-user)#exit
2. Configure the authentication template.

ZXR10(config)#aaa-authentication-template 2001
ZXR10(config-aaa-authen-template)#aaa-authentication-type local
ZXR10(config-aaa-authen-template)#exit
3. Configure the authorization template.

ZXR10(config)#aaa-authorization-template 2001
ZXR10(config-aaa-author-template)#aaa-authorization-type local
ZXR10(config-aaa-author-template)#exit
4. Enter the global configuration mode and configure the maximum number of online
users.
ZXR10(config)#line telnet max-link 10
5. Enter the global configuration mode and configure the idle timeout and absolute
timeout (unit: minutes).
ZXR10(config)#line telnet idle-timeout 30
ZXR10(config)#line telnet absolute-timeout 120
End of Steps
Result
After the configuration, you can access the ZXR10 M6000-S as the configured telnet user
to verify that the configuration is successful.
Example
The following example shows how to access the network management port whose address
is 10.10.1.100 as the configured telnet user:
telnet 10.10.1.100
*********************************************************************
*********************************************************************
Login at: 15:47:42 01-06-2014
Username:who
3-30
SJ-20140731105308-006|2014-10-20 (R1.0)

Password:
ZXR10>
3.4.8 (Optional) Configuring ACL-Based Filtering of Telnet Users

This procedure describes how to configure an ACL to restrict the IP address segments
that can access the equipment through telnet and to filter user packets to the equipment.
Context
configure ACL-based filtering of telnet users:
Table 3-4 Data Plans for Configuring ACL-Based Filtering of Telnet Users
Item
Data Plan
Description
ACL name
tlist
IP addresses that are allowed to
10.10.1.1
Source IP addresses of the
access the equipment
10.10.1.2
network management device,

log host, and administrator's
host.
Steps
1. Create an ACL.
ZXR10(config)#ipv4-access-list tlist
ZXR10(config-ipv4-acl)#rule permit 10.10.1.1
ZXR10(config-ipv4-acl)#rule deny any
ZXR10(config-ipv4-acl)#exit
This ACL only permits packets from addresses 10.10.1.1 and 10.10.1.2 and denies all
the packets from other addresses.
2. Apply the ACL to filter out telnet users that do not comply with the ACL rules.
ZXR10(config)#line telnet access-class ipv4 tlist
End of Steps
3.4.9 Configuring SSH

This procedure describes how to configure SSH on the ZXR10 M6000-S, so that users
can access the equipment through SSH ensuring a secure data transmission.
Context
SSH is a protocol that provides a secure channel for remote accesses and other services
over an insecure network. It is developed based on the traditional telnet protocol. During
the data sending and receiving, the SSH protocol automatically encrypts and decrypts
the data. Compared with telnet, SSH is secure enough in both authentication and data
3-31
SJ-20140731105308-006|2014-10-20 (R1.0)
transmission so as to prevent man-in-the-middle attacks, DNS spoofing attacks, and IP

spoofing attacks.
There are three authentication modes for SSH users: local authentication, RADIUS
authentication, and TACACS+ authentication. The following procedure uses data plans
in Table 3-5 as an example to describe how to configure SSH.
Table 3-5 Data Plans for SSH Configuration
Item
Data Plan
Description
Username
zte
Password
ztezte
The password for local authentication is zte.

The address of the RADIUS server is 192.168.11.1 and the
password is ztezte.
The address of the TACACS+ server is 192.168.11.160 and
the password is ztezte.
Privilege level
15
Default: 0. In the user management template, set the

privilege level of local users to 15.
Steps
l
Configure an SSH user whose authentication mode is local authentication.

1. In the global configuration mode, enable SSH.
ZXR10(config)#ssh server enable
2. Configure the AAA authentication and authorization templates and set the
authentication mode to local authentication.
ZXR10(config-aaa-authen-template)#aaa-authentication-type local
ZXR10(config-aaa-author-template)#aaa-authorization-type radius
3. Configure a user management template and bind the AAA templates to the user
management template.
4. Create a user, configure the username and password, and bind the user to the
corresponding templates.
3-32
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10(config-system-user)#default-privilege-level 0
ZXR10(config-system-user)#user-name zte
ZXR10(config-system-user-username)#password ztezte
Configure an SSH user whose authentication mode is RADIUS authentication.

2. Configure the RADIUS server.

ZXR10(config)#radius authentication-group 1
ZXR10(config-authgrp-1)#server 1 192.168.11.1 key zte123
ZXR10(config-authgrp-1)#exit
authentication mode to RADIUS authentication.
ZXR10(config-aaa-authen-template)#aaa-authentication-type radius
ZXR10(config-aaa-authen-template)#authentication-radius-group 1
ZXR10(config-aaa-author-template)#aaa-authorization-type radius
5. Create a user, configure its username and password, and bind it to the
ZXR10(config-system-user-username)#password zte
Configure an SSH user whose authentication mode is TACACS+ authentication.

3-33
SJ-20140731105308-006|2014-10-20 (R1.0)

2. In the global configuration mode, enable the TACACS+ function and configure the
TACACS+ server.
ZXR10(config)#tacacs enable
ZXR10(config)#tacacs-server host 192.168.11.160 key zte
ZXR10(config)#tacplus group-server zte-group
ZXR10(config-sg)#server 192.168.11.160
ZXR10(config-sg)#exit
authentication mode to TACACS+ authentication.
ZXR10(config-aaa-authen-template)#aaa-authentication-type tacacs
ZXR10(config-aaa-authen-template)#authentication-tacacs-group zte-group
ZXR10(config-aaa-author-template)#aaa-authorization-type tacacs
ZXR10(config-aaa-author-template)#authorization-tacacs-group zte-group
5. Create a user, configure its username and password, and bind it to the
ZXR10(config-system-user-username)#password zte
End of Steps
Result
After the configuration, users can access the ZXR10 M6000-S through SSH.
3-34
SJ-20140731105308-006|2014-10-20 (R1.0)
Example
The following procedure uses two client programs, SecureCRT and Putty, as an example
to describe how to configure SSH:
l
Access the equipment by using SecureCRT.

1. Start SecureCRT and select File > Quick Connect. The Quick Connect dialog
box is displayed, see Figure 3-5.
Figure 3-5 Quick Connect Dialog Box
2. Select SSH2 from the Protocol list, enter the address of the remote router in the
Hostname text box, and click the Connect button. A dialog box is displayed.
3. Enter the SSH username and then click Yes. A dialog box is displayed.
4. Enter the SSH password and then click Yes. The information indicating that you
have successfully accessed the equipment is displayed.
Access the equipment by using Putty.
1. Start Putty. The PuTTY Configuration dialog box is displayed, see Figure 3-6.
3-35
SJ-20140731105308-006|2014-10-20 (R1.0)
Figure 3-6 PuTTY Configuration Dialog Box
2. In the Host Name text box, enter the host name or IP address (for example,
192.168.2.1) of the remote router.
3. Click SSH in the navigation tree in the left pane and set Preferred SSH protocol
version to 2. The parameter setting result is displayed, see Figure 3-7.
3-36
SJ-20140731105308-006|2014-10-20 (R1.0)
Figure 3-7 PuTTY Configuration Dialog BoxSetting the Version of the SSH
Protocol
4. Click Open to log in to the equipment.

5. Enter the correct username and password. The information indicating that you
have successfully accessed the equipment is displayed.
3.4.10 Configuring FTP

This procedure describes how to configure FTP , so that users can access the equipment
by FTP through the IP address of the network management port.
Context
configure FTP.
Table 3-6 Data Plans for FTP Configuration
Item
Data Plan
Description
Username
zte
Default: who. Only one FTP user can be

configured.
Password
ZXR10
Default: who
3-37
SJ-20140731105308-006|2014-10-20 (R1.0)
Item
Data Plan
Description
FTP server root directory
/datadisk0/
Default: /datadisk0/
Steps
1. Configure the FTP username and password. For details, refer to 3.4.7 Configuring
Telnet.
2. In the global configuration mode, configure the FTP server root directory.
ZXR10(config)#ftp-server top-directory /datadisk0/
3. In the global configuration mode, enable the FTP server.

ZXR10(config)#ftp-server enable
End of Steps
Result
After the configuration, you can access the ZXR10 M6000-S through FTP.
Example
The following example describes how to access the equipment through FTP. In this
example, the IP address of the network management port of the equipment is 10.10.1.100
and a PC (whose operating system is Windows XP) is connected to the equipment.
1. Open the command prompt window on the PC, enter the following command to access
the equipment through FTP:
C:\Documents and Settings\Administrator>ftp 10.10.1.100
Connected to 10.10.1.100.
220 VxWorks (Linux OSS FTP SERVER) FTP server ready
User (10.10.1.100:(none)): zte
331 Password required
Password:
230 Login successful
2. Query file directories on the equipment.

ftp> dir
200 PORT command successful.
150 Opening data connection.
drw-rw-rw- 1 noone nogroup
Jul 04 17:58 LOG
May 30 19:15 performance
Jul 03 03:17 techspt
226 Transfer complete.

ftp: 183 bytes received in 0.27Seconds 0.69Kbytes/sec.
3. Upload files.
ftp> put e:/ftp/1.txt 2.txt
3-38
SJ-20140731105308-006|2014-10-20 (R1.0)

ftp: 402 bytes sent in 0.00Seconds 402000.00Kbytes/sec.
ftp> dir
Jul 04 17:58 LOG
May 30 19:15 performance
-rwxr--r-- 1 noone nogroup
402
Jul 03 03:17 techspt

Jul 09 2012 2.txt

ftp: 241 bytes received in 0.22Seconds 1.11Kbytes/sec
3.5 Link Layer Initial Configuration

Link layer initial configuration (debugging) refers to some basic interface debugging
operations performed before service configuration to ensure that the corresponding
interface can operate normally in the subsequent service configuration.
Before the service configuration, you must perform the following:
l
l
l
Configuring Ethernet interfaces

Configuring POS interfaces
Debugging the optical power of interfaces
3.5.1 Configuring an Ethernet Interface

This procedure describes how to configure the MTU, operating mode and speed of an
Ethernet interface.
Context
MTU indicates the size (in bytes) of the largest data packet that can pass on a layer of a
particular communication protocol.
Steps
1. Configure the MTU of the Ethernet interface.
ZXR10(config)#interface gei-0/1/0/1
ZXR10(config-if-gei-0/1/0/1)#mtu 1800
2. Configure the operating mode and negotiation mode of the Ethernet interface.
ZXR10(config-if-gei-0/1/0/1)#duplex duplex-full
ZXR10(config-if-gei-0/1/0/1)#negotiation negotiation-force
3. Configure the speed of the Ethernet interface.

ZXR10(config-if-gei-0/1/0/1)#speed speed-1G
4. Add the description of the Ethernet interface for future maintenance.

3-39
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10(config-if-gei-0/1/0/1)#description connect-to-ZTE
End of Steps
Result
After the configuration, run the show interface <interface-name> command to query the MTU,
IP address and mask, operating speed, operating mode, and description of an Ethernet
interface.
The following example shows how to query the above parameters of interface gei-0/1/0/1:
ZXR10(config)#show interface gei-0/1/0/1
gei-0/1/0/1 is up, line protocol is up, IPv4 protocol is up, IPv6 protocol is down
Description is connect-to-ZTE
/*Description of the interface*/
Hardware is Gigabit Ethernet, address is 4c09.b4f2.07c0

BW 1000000 Kbps
/*Bandwidth of the interface*/
IP MTU 1500 bytes

MTU 1800 bytes
/*MTU of the interface*/
MPLS MTU 1500 bytes

The port is optical
The MDIMode of the port is not supported
Loopback cancel
Duplex full
/*Operating mode of the interface*/
Negotiation force
/*Negotiation mode of the interface*/
SD-FER enable
FER occur threshold is 9*10e-3
FER clear threshold is 6*10e-4
FER current is 0.0*10e-7
ARP type
ARP
ARP Timeout
04:00:00
Last Clear Time : 2014-05-26 16:19:04
0Pps
0Pps
Peak rate:
input
0Bps
peak time
N/A
output
0Bps
peak time
N/A
output 0%
HardWareCounters:
In_Bytes
In_Packets
In_CRC_ERROR
In_Unicasts
In_Broadcasts
In_Multicasts
In_Undersize
In_Oversize
In_64B
In_65_127B
3-40
SJ-20140731105308-006|2014-10-20 (R1.0)

In_128_255B
In_256_511B
In_512_1023B
In_1024_1518B
In_1519_MaxB
E_Bytes
E_Packets
E_CRC_ERROR
N/A
E_Unicasts
E_Broadcasts
E_Multicasts
E_Undersize
E_Oversize
N/A
E_64B
E_65_127B
E_128_255B
E_256_511B
E_512_1023B
E_1024_1518B
E_1519_MaxB
E_SingCollision
N/A
E_MultCollision
N/A
E_LateCollision
N/A
E_ExceCollision
N/A
StreamCounters
In_Bytes
In_Packets
In_Discards
In_V4Bytes
In_V4Pkts
In_V6Bytes
In_V6Pkts
In_UpsendCar_Drop
E_Bytes
E_Packets
E_Discards
E_V4Bytes
E_V4Pkts
E_V6Bytes
E_V6Pkts
3.5.2 Configuring a POS Interface

POS is a technology that provides a high-speed channel for transmitting IP packets over
SONET/SDH. As an advanced technology for connecting Wide Area Networks (WANs),
POS supports optical fiber media and IP packet data.
Before the service configuration, you must configure the following parameters of the related
POS interface:
l
l
l
l
Overhead bytes
Link-layer protocol
CRC value
Clock mode
Steps
1. Configure the overhead bytes of the POS interface.
ZXR10(config)#interface pos192-0/3/0/1
ZXR10(config-if-pos192-0/3/0/1)#flag c2 027
ZXR10(config-if-pos192-0/3/0/1)#flag j0 16-trace-byte ZTE ZTE ZTE ZTE
ZXR10(config-if-pos192-0/3/0/1)#flag j1 16-trace-byte Z
2. Configure the link-layer protocol of the POS interface.

ZXR10(config-if-pos192-0/3/0/1)#encapsulation ppp
3-41
SJ-20140731105308-006|2014-10-20 (R1.0)
3. Configure the Cyclic Redundancy Check (CRC) value of the POS interface.
ZXR10(config-if-pos192-0/3/0/1)#crc crc32
4. Configure the clock mode of the POS interface.

ZXR10(config-if-pos192-0/3/0/1)#clock mode send internal
5. Configure the description of the POS interface for future maintenance.

ZXR10(config-if-pos192-0/3/0/1)#description Testing for the version of 3.0
End of Steps
3.6 Network Layer Initial Configuration

Network layer initial configuration refers to operations performed so that the equipment
can interwork with other devices in the network and can be connected to the network
management server.
Before the service configuration, you must perform the following:
l
l
l
Configuring interface IP addresses

Configuring static routes
Configuring dynamic routes (OSPF, IS-IS, and BGP)
You can access the network management server through in-band management or
out-of-band management based on the actual network planning.
l
In-band management: Management control packets and service data are transmitted
through the same physical channel (for example, an Ethernet interface of the
equipment).
The largest defect of in-band management is that when the network is interrupted due
to a fault, both data transmission and management cannot be performed normally.
Out-of-band management: The ZXR10 M6000-S is connected to the network through

an out-of-band management interface.
The out-of-band management supports the transmission of management control
packets and service data through different physical channels, so that these two
types of transmission are independent and cannot affect each other. Therefore,
the out-of-band management can help you cut operational expenditure, increase
operation efficiency, shorten downtime, and improve quality of service.
If the IP address of the in-band or out-of-band network management port is not in the
same network segment as that of the network management server, you can configure static
routes or dynamic routes to achieve the accessibility between the above two.
3-42
SJ-20140731105308-006|2014-10-20 (R1.0)
3.6.1 Configuring Interface IP Addresses

This procedure describes how to configure IP addresses of interfaces on the equipment
so that it can interwork with layer 3 networks of other devices.
Steps
1. Configure a layer 3 interface so that it can interwork with other devices.
The following example shows how to configure the IP address of interface gei-0/1/0/1:
ZXR10(config-if-gei-0/1/0/1)#no shutdown
ZXR10(config-if-gei-0/1/0/1)#ip address 10.1.1.1 255.255.255.0
2. Configure a layer 2 sub-interface so that it can interwork with other devices.

The following example shows how to configure the IP address of sub-interface
gei-0/4/0/1.1:
ZXR10(config)#interface gei-0/4/0/1.1
ZXR10(config-if-gei-0/4/0/1.1)#exit
ZXR10(config)#vlan-configuration
ZXR10(config-vlan)#interface gei-0/4/0/1.1
ZXR10(config-vlan-if-gei-0/4/0/1.1)#encapsulation-dot1q 1
ZXR10(config-vlan-if-gei-0/4/0/1.1)#exit
ZXR10(config-vlan)#exit
ZXR10(config)#interface gei-0/4/0/1.1
ZXR10(config-if-gei-0/4/0/1.1)#ip address 10.4.1.35 255.255.255.0
ZXR10(config-if-gei-0/4/0/1.1)#end
End of Steps
Result
Run the show running-config-interface command to query the interface configuration.
ZXR10(config)#show running-config-interface gei-0/1/0/1
!<if-intf>
interface gei-0/1/0/1
no shutdown
ip address 10.1.1.1 255.255.255.0
!</if-intf>
Run the ping command to test the network connectivity.

ZXR10#ping 10.4.1.34
sending 5,100-byte ICMP echo(es) to 10.4.1.34,timeout is 2 second(s).
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max=1/1/1 ms.
3-43
SJ-20140731105308-006|2014-10-20 (R1.0)
3.6.2 Configuring Static Routes

If the management network port is connected to the network management server and the
IP address of the management network port is not in the same network segment as that
of the network management server, you can configure static routes, so that the equipment
can normally communicate with the network management server.
Context
Figure 3-8 shows an example of configuring static routes.
Figure 3-8 Example of Configuring Static Routes
Steps
1. Configure the IP addresses of the routers and the management port of the network
management system in Figure 3-8 (The configuration commands are omitted).
2. In global configuration mode, configure static routes on the R1.
R1(config)#ip route 10.10.1.5 255.255.255.0 192.168.20.1
3. In global configuration mode, configure a static route on R2.

R2(config)#ip route 10.10.1.5 255.255.255.0 172.16.10.2
4. In global configuration mode, configure a static route on R3.

R3(config)#ip route 192.168.20.0 255.255.255.0 172.16.10.1
End of Steps
Result
Run the show ip forwarding route command to query the route forwarding table on the
ZXR10 M6000-S, and verify that the configured static routes are operating normally.
R1#show ip forwarding route
3-44
SJ-20140731105308-006|2014-10-20 (R1.0)

IPv4 Routing Table:
Headers: Dest: Destination,
Codes
Gw: Gateway,
Pri: Priority;
: BROADC: Broadcast, USER-I: User-ipaddr, USER-S: User-special,

MULTIC: Multicast, USER-N: User-network, DHCP-D: DHCP-DFT,
ASBR-V: ASBR-VPN, STAT-V: Static-VRF, DHCP-S: DHCP-static,
GW-FWD: PS-BUSI, NAT64: Stateless-NAT64, LDP-A: LDP-area,
GW-UE: PS-USER, P-VRF: Per-VRF-label, TE: RSVP-TE;
Status codes: *valid, >best;

Dest
*> 10.10.1.5/24
Gw
Interface
Owner
Pri Metric
192.168.20.1
gei-0/3/0/1
Static
Run the ping command to test the connectivity between the ZXR10 M6000-S and the
network management system.
R1#ping 10.10.1.5
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 1/1/1 ms.
3.6.3 Configuring OSPF Dynamic Routes

For the network that uses the in-band management method, you can configure OSPF
dynamic routes as layer 3 routing channels, so that the layer 3 communication between
the equipment and the network management server can operate normally.
Context
Figure 3-9 shows an example of configuring OSPF dynamic routes.
Figure 3-9 Example of Configuring OSPF Dynamic Routes
3-45
SJ-20140731105308-006|2014-10-20 (R1.0)
Steps
2. Configure OSPF routes on the R1.
R1(config)#router ospf 1
R1(config-ospf-1)#network 192.168.20.0 0.0.0.255 area 0
R1(config-ospf-1)#end
3. Configure OSPF routes on R2.

4. Configure OSPF routes on R3.

End of Steps
Result
Run the show ip forwarding route to query the route forwarding table on the ZXR10
M6000-S and verify that the configured OSPF routes are operating normally.
R1(config)#show ip forwarding route
IPv4 Routing Table:
Codes
Gw: Gateway,
Pri: Priority;


Dest
Gw
Interface
Owner
Pri Metric
*> 172.16.10.0/24
192.168.20.1
gei-0/3/0/1
OSPF
110 2
*> 10.10.1.0/24
192.168.20.1
gei-0/3/0/1
OSPF
110 2
R1#ping 10.10.1.5
!!!!!
3-46
SJ-20140731105308-006|2014-10-20 (R1.0)
3.6.4 Configuring IS-IS Dynamic Routes

For the network that uses the in-band management method, you can configure IS-IS
dynamic routes as layer 3 routing channel, so that the layer 3 communication between
the equipment and the network management server can operate normally.
Context
Figure 3-10 shows an example of configuring IS-IS dynamic routes.
Figure 3-10 Example of Configuring IS-IS Dynamic Routes
Table 3-7 shows the data plans related to IS-IS configuration in the above network.
Table 3-7 IS-IS Network Layer Data Plans
Item
Data Plan
Description
Network entity name of the
10.0000.0000.0001
Format: XX.X X X X. X X X X. X X X X.00:
R1
.00
20.0000.0000.0002
R2
.00
The former "XX" indicates the area

address and is used to separate areas.
The 12 "X" in the middle indicates the

system ID and is used to identify the host.
20.0000.0000.0003
R3
.00
Level of the R1
Level-2
Modify the default level to Level-2
Level of the R2
Level-1-2
Use the default value Level-1-2
Level of the R3
Level-1-2
Use the default value Level-1-2
The last "00" indicates NASP selector and

is 00 in the IP protocol.
Steps
3-47
SJ-20140731105308-006|2014-10-20 (R1.0)
2. Configure IS-IS routes on the R1.

R1(config)#router isis
R1(config-isis-0)#area 10
R1(config-isis-0)#system-id 0000.0000.0001
R1(config-isis-0)#redistribute connected
R1(config-isis-0)#interface gei-0/3/0/1
R1(config-isis-0-if-gei-0/3/0/1)#circuit-type level-2-only
R1(config-isis-0-if-gei-0/3/0/1)#ip router isis
R1(config-isis-0-if-gei-0/3/0/1)#end
3. Configure IS-IS routes on R2.

R2(config-isis-0-if-gei-0/1/0/1)#exit
R2(config-isis-0-if-gei-0/1/0/2)#end
4. Configure IS-IS routes on R3.

R3(config-isis-0-if-gei-0/3/0/1)#exit
End of Steps
Result
ZXR10 M6000-S and verify that the configured IS-IS routes are operating normally.
IPv4 Routing Table:
Codes
Gw: Gateway,
Pri: Priority;


Dest
Gw
Interface
Owner
Pri Metric
3-48
SJ-20140731105308-006|2014-10-20 (R1.0)

*> 172.16.10.0/24
192.168.20.1
gei-0/3/0/1
ISIS-L2
115 10
*> 10.10.1.0/24
192.168.20.1
gei-0/3/0/1
ISIS-L2
115 10
R1#ping 10.10.1.5
!!!!!
3.6.5 Configuring BGP Dynamic Routes

For the network that uses the in-band management method, you can configure BGP
dynamic routes as the layer 3 routing channels, so that the layer 3 communication
between the equipment and the network management server can operate normally.
Context
Figure 3-11 shows an example of configuring BGP dynamic routes.
Figure 3-11 Example of Configuring BGP Dynamic Routes
Steps
2. Configure BGP routes on the R1.
R1(config)#router bgp 65002
R1(config-bgp)#redistribute connected
R1(config-bgp)#neighbor 192.168.20.1 remote-as 65001
3-49
SJ-20140731105308-006|2014-10-20 (R1.0)

R1(config-bgp)#end
3. Configure BGP routes on R2.

R2(config-bgp)#neighhor 192.168.20.2 remote-as 65002
R2(config-bgp)#end
4. Configure BGP routes on R3.

R3(config-bgp)#end
End of Steps
Result
ZXR10 M6000-S and verify that the configured BGP routes are operating normally.
IPv4 Routing Table:
Codes
Gw: Gateway,
Pri: Priority;


Dest
Gw
Interface
Owner
Pri Metric
*> 192.168.20.0/24
192.168.20.2
gei-0/3/0/1
BGP
200 0
*> 172.16.10.0/24
192.168.20.1
gei-0/1/0/1
BGP
200 0
*> 10.10.1.0/24
192.168.20.1
gei-0/1/0/1
BGP
200 0
R1#ping 10.10.1.5
!!!!!
3-50
SJ-20140731105308-006|2014-10-20 (R1.0)
3.7 Configuring the Interconnection Between the

Equipment and the Network Management System
This procedure describes how to configure the SNMPv1, SNMPv2c, or SNMPv3
interconnection between the ZXR10 M6000-S and the network management system, so
that the network management system can manage the equipment.
Context
configure the interconnection between the ZXR10 M6000-S and the network management
system:
Table 3-8 Data Plans for Configuring the Interconnection Between the Equipment
and the Network Management System
Item
Data Plan
IP address of the management port of the
10.10.1.5
network management system

SNMP read and write community names in
Name of the read community: public
SNMPv1
Name of the write community: private
SNMP read and write community names in
Name of the read community: public
SNMPv2
Name of the write community: private
User group name and username in SNMPv3
User group name: ztegrp

Username: zte
Steps
l
Configure an SNMPv1 interconnection to the network management system.

1. Configure the community names and privileges.
ZXR10(config)#snmp-server community public ro
ZXR10(config)#snmp-server community private rw
2. Configure the SNMPv1 access control list.

ZXR10(config)#ipv4-access-list zte
ZXR10(config)#snmp-server access-list ipv4 zte
3. Configure the trap function.

ZXR10(config)#snmp-server enable trap
ZXR10(config)#snmp-server host vrf mng 10.10.1.5 trap version 1 public

3-51
SJ-20140731105308-006|2014-10-20 (R1.0)

ZXR10(config)#snmp-server community public ro
ZXR10(config)#snmp-server community private rw


ZXR10(config)#snmp-server host vrf mng 10.10.1.5 trap version 2c public

ZXR10(config)#snmp-server group ztegrp v3 auth
ZXR10(config)#snmp-server user zte ztegrp v3 auth md5 zte


ZXR10(config)#snmp-server host vrf mng 10.10.1.5 trap version 3 auth zte
End of Steps
Result
After completing above configuration on the ZXR10 M6000-S and that of network
management stations, you can access the equipment through the network management
server.
3.8 Saving the Configuration

This procedure describes how to save the configuration of the ZXR10 M6000-S to the
database.
3-52
SJ-20140731105308-006|2014-10-20 (R1.0)
Steps
1. In privileged mode, run the write command to save the configuration.
ZXR10#write
Write DB OK!
Building configuration...
..[OK]
2. In global configuration mode, run the load-mode command to load configuration

information from the saved txt file.
ZXR10(config)#load-mode txt
End of Steps
Result
You can query whether the txt file is saved correctly. By default, the txt file is saved under
the /sysdisk0/DATA0 directory.
After the equipment is restarted, a successful load of configuration information indicates
that the configuration was saved correctly.
3-53
SJ-20140731105308-006|2014-10-20 (R1.0)
3-54
SJ-20140731105308-006|2014-10-20 (R1.0)
Figures
Figure 1-1 Initial Configuration Flow.......................................................................... 1-1
Figure 3-1 Example of Connecting a PC to the Console Port of the ZXR10
M6000-S................................................................................................. 3-1
Figure 3-2 Connection Description Dialog Box .......................................................... 3-2
Figure 3-3 Connect To Dialog Box ............................................................................ 3-2
Figure 3-4 COM1 Properties Dialog Box ................................................................... 3-3
Figure 3-5 Quick Connect Dialog Box ..................................................................... 3-35
Figure 3-6 PuTTY Configuration Dialog Box ........................................................... 3-36
Figure 3-7 PuTTY Configuration Dialog BoxSetting the Version of the SSH
Protocol ................................................................................................ 3-37
Figure 3-8 Example of Configuring Static Routes .................................................... 3-44
Figure 3-9 Example of Configuring OSPF Dynamic Routes..................................... 3-45
Figure 3-10 Example of Configuring IS-IS Dynamic Routes .................................... 3-47
Figure 3-11 Example of Configuring BGP Dynamic Routes ..................................... 3-49
I
SJ-20140731105308-006|2014-10-20 (R1.0)
Figures
II
SJ-20140731105308-006|2014-10-20 (R1.0)
Tables
Table 1-1 Intial Configuration Flow Description.......................................................... 1-2
Table 2-1 List of Hardware Items to be Checked ....................................................... 2-1
Table 2-2 List of Software Items to be Checked ........................................................ 2-2
Table 2-3 List of Tools to be Checked........................................................................ 2-2
Table 2-4 Technical Documentation Required During the Initial Configuration ........... 2-3
Table 2-5 List of Data Items to be Collected .............................................................. 2-4
Table 3-1 Data Plans for System Time Configuration .............................................. 3-23
Table 3-2 Data Plans for the FTP and Syslog Servers............................................. 3-24
Table 3-3 Data Plans for Telnet Configuration ......................................................... 3-29
Table 3-4 Data Plans for Configuring ACL-Based Filtering of Telnet Users .............. 3-31
Table 3-5 Data Plans for SSH Configuration ........................................................... 3-32
Table 3-6 Data Plans for FTP Configuration ............................................................ 3-37
Table 3-7 IS-IS Network Layer Data Plans .............................................................. 3-47
Table 3-8 Data Plans for Configuring the Interconnection Between the Equipment
and the Network Management System................................................... 3-51
III
SJ-20140731105308-006|2014-10-20 (R1.0)
Tables
IV
SJ-20140731105308-006|2014-10-20 (R1.0)
Glossary
ACL
- Access Control List
BGP
- Border Gateway Protocol
CPU
- Central Processing Unit
CRC
- Cyclic Redundancy Check
DNS
- Domain Name Server
IP
- Internet Protocol
IS-IS
- Intermediate System-to-Intermediate System
MPU
- Management Process Unit
MTU
- Maximum Transmission Unit
NTP
- Network Time Protocol
NVRAM
- Non-Volatile Random Access Memory
OSPF
- Open Shortest Path First
POS
- Packet Over SONET/SDH
SDH
- Synchronous Digital Hierarchy
SNMP
- Simple Network Management Protocol
SONET
- Synchronous Optical Network
SSH
- Secure Shell
V
SJ-20140731105308-006|2014-10-20 (R1.0)
UDP
- User Datagram Protocol
UTC
- Universal Time Coordinated
VLAN
- Virtual Local Area Network
WAN
- Wide Area Network
VI
SJ-20140731105308-006|2014-10-20 (R1.0)

SJ-20140731105308-006-ZXR10 M6000-S (V3.00.10) Carrier-Class Router Initial Configuration Guide - 608093

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SJ-20140731105308-006-ZXR10 M6000-S (V3.00.10) Carrier-Class Router Initial Configuration Guide - 608093

Caricato da

Copyright:

Formati disponibili

ZXR10 M6000-S

Initial Configuration Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20140731105308-006

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

3.6.2 Configuring Static Routes ....................................................................... 3-44

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

1, Initial Configuration Flow

Describes the initial configuration flow and steps of the ZXR10

Describes the hardware, software, tool, documentation, and data

Describes the initial configuration items, steps, and commands.

Separates individual parameters in a series of parameters.

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

Initial Configuration Flow

ZTE Proprietary and Confidential

ZXR10 M6000-S Initial Configuration Guide

Initial Configuration Flow Description

Before the configuration, hardware, software, tools, documentation,

and data must be prepared so that the initial configurations can be

After hardware installation, the ZXR10 M6000-S must be checked and

Accessing the Equipment Through the Console Port: describes

Starting the Equipment: describes how to start the equipment

Common Check Items: describes common check items of the

Common Configuration Items: describes common configuration

Link Layer Initial Configuration: describes basic link layer

Network Layer Initial Configuration: describes basic network

Configuring the Interconnection Between the Equipment and

Saving the Configuration: describes how to save the

ZTE Proprietary and Confidential

Power and grounding

Cables and connectors

The connectors of these cables are not loose or lost.

The sheaths of these cables are not damaged.

ZTE Proprietary and Confidential

ZXR10 M6000-S Initial Configuration Guide

System software package

Required software should be included in the system software package.

HyperTerminal: This software tool is provided by the Windows

FTP server software: This software tool will be used

Cables and interfaces

1 standard RS-232 serial cable, used for accessing the equipment

1 network cable, used for configuring the management network

ZTE Proprietary and Confidential

Chapter 2 Initial Configuration Preparations

Multiple optical fiber cables, used for connecting to the

Prepare 1 maintenance terminal, which is in general a PC (installed with

Auxiliary instruments and

power received at an optical interface, the receiving sensitivity of an

ZXR10 M6000-S (V3.00.10) Carrier-Class Router

Describes the composition, hardware structure,

boards, power supplies and fans of the ZXR10

ZXR10 M6000-S (V3.00.10) Carrier-Class Router

Describes the engineering preparations, active

ZXR10 M6000-S (V3.00.10) Carrier-Class Router

Describes the principle, configuration commands

and configuration instance of every functional

ZXR10 M6000-S (V3.00.10) Carrier-Class Router

/Press any key to enter the boot configuration mode/

/Select whether to configure the boot parameters manually/

/Select the Manual BOOT Config option/

/Set the system controller/

/Set the maximum MAC offset, range: 1-63/

/Set the IP address of the network management port/

/Set the subnet mask of the network management port/

/Set the IP address of the FTP gateway/

/Set the IP address of the FTP server/

/Set the name of the version file to be started/