SJ-20140731105308-020-ZXR10 M6000-S (V3.00.10) Carrier-Class Router Routine Maintenance - 608079

ZXR10 M6000-S
Carrier-Class Router
Routine Maintenance
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-020

Publishing Date: 2014-10-20 (R1.0)
SJ-20140731105308-020|2014-10-20 (R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Routine Maintenance Overview............................................... 1-1
1.1 Purposes ........................................................................................................... 1-1
1.2 Principles and Precautions.................................................................................. 1-1
1.3 Introduction to Routine Maintenance Items........................................................... 1-3
Chapter 2 Periodic Inspection of Equipment Hardware and

Software Statuses .................................................................................. 2-1
2.1 Checking Equipment Software Status .................................................................. 2-1
2.1.1 Checking the OSPF Status ....................................................................... 2-1
2.1.2 Checking the IS-IS Status ......................................................................... 2-2
2.1.3 Checking the BGP Status ......................................................................... 2-3
2.1.4 Checking the Equipment Version............................................................... 2-4
2.1.5 Checking Equipment Boot Mode ............................................................... 2-5
2.2 Checking Equipment Hardware Status................................................................. 2-5
2.2.1 Checking the Power Supply Status............................................................ 2-6
2.2.2 Checking the Fan Status........................................................................... 2-6
2.2.3 Checking Temperature.............................................................................. 2-7
2.2.4 Checking CPU and Memory Usages.......................................................... 2-9
2.3 Checking Equipment Alarms ............................................................................. 2-10
Chapter 3 Scheduled Maintenance Items................................................. 3-1

3.1 Daily Maintenance Items..................................................................................... 3-1
3.1.1 Checking the Equipment Room Environment ............................................. 3-1
3.1.2 Checking Power Supplies ......................................................................... 3-2
3.1.3 Checking the Cabinet Environment............................................................ 3-2
3.1.4 Checking Basic Equipment Information...................................................... 3-3
3.1.5 Checking Equipment Operational Status.................................................... 3-4
3.1.6 Checking Service Operational Status......................................................... 3-9
3.2 Monthly Maintenance Items .............................................................................. 3-16
3.2.1 Check Power Supply Redundancy........................................................... 3-16
3.2.2 Checking Basic Equipment Information.................................................... 3-17
3.2.3 Checking System Time ........................................................................... 3-19
3.2.4 Checking User Security Management ...................................................... 3-20
3.2.5 Checking Equipment Interface Configuration............................................ 3-21
I
SJ-20140731105308-020|2014-10-20 (R1.0)
3.2.6 Checking Service Operational Status....................................................... 3-22

3.2.7 Checking Basic Equipment Configuration................................................. 3-22
3.3 Quarterly Maintenance Items ............................................................................ 3-23
3.3.1 Checking Cabinet Environment ............................................................... 3-23
3.3.2 Checking User Security Management ...................................................... 3-24
3.3.3 Checking Equipment Basic Configuration................................................. 3-25
3.4 Yearly Maintenance Items ................................................................................. 3-26
3.4.1 Checking Equipment Room Environment ................................................. 3-26
3.4.2 Checking Cabinet Environment ............................................................... 3-26
Tables .............................................................................................................. I
Glossary ........................................................................................................ III
II
SJ-20140731105308-020|2014-10-20 (R1.0)
About This Manual

Purpose
This manual describes the purposes, principles and specifications of routine maintenance
for the ZXR10 M6000-S series products, and categories of maintenance items, mainly
including items of network data configuration and status inspection, equipment hardware
and software status inspection, and periodic maintenance.
Intended Audience
This manual is intended for:
l
l
l
Network planning engineers

Commissioning engineers
Maintaining engineers
What Is in This Manual

This manual contains the following chapters.
Describes the purposes, principles, and specificaChapter 1, Routine Maintenance Overview
tions of routine maintenance, and categories of maintenance items.
Chapter 2, Periodic Inspection of Equipment
Describes items of periodic inspection of equipment
Hardware and Software Statuses
hardware and software statuses.

Describes items of scheduled maintenance, including items of daily maintenance, monthly mainte-
Chapter 3, Scheduled Maintenance Items
nance, quarterly maintenance, and yearly maintenance.
Conventions
This manual uses the following typographical convention.
Note: provides additional information about a certain topic.
I
SJ-20140731105308-020|2014-10-20 (R1.0)
This page intentionally left blank.
II
SJ-20140731105308-020|2014-10-20 (R1.0)
Chapter 1
Routine Maintenance
Overview
Table of Contents
Purposes....................................................................................................................1-1
Principles and Precautions .........................................................................................1-1
Introduction to Routine Maintenance Items.................................................................1-3
1.1 Purposes
Routine maintenance is a process during which preventive operations are performed
periodically to discover and resolve potential faults of the equipment and the equipment
room and ensure normal operation of the entire system.
The purposes of routine maintenance are as follows:
l
l
l
l
Discover and resolve equipment alarms and problems in time to minimize equipment
faults.
Discover and resolve link or connection faults in time to ensure normal service
operation.
Keep the equipment in good condition and ensure reliable system operation.
Discover and handle such defects as natural aging, functional failure, or performance
deterioration during equipment operation to prevent potential accidents.
1.2 Principles and Precautions

If any fault is found during routine maintenance, start the troubleshooting process and
contact the customer service center or local agency of ZTE for troubleshooting. To
ensure long-term, safe and reliable operation of the equipment, reduce accidents and
emergencies, and lower maintenance cost, the following principles and rules should be
considered and observed during operation and maintenance of the equipment.
Machine Room Management

Observe the following precautions when you manage a equipment room.
l
Make sure that the equipment room meets the related national standards or the basic
industrial standards. Keep the equipment room clean and dry, maintain a suitable
temperature, and prevent insects and mice.
1-1
SJ-20140731105308-020|2014-10-20 (R1.0)
ZXR10 M6000-S Routine Maintenance
Make sure that the system power supply is stable and reliable. Check the system
earthing and lightning protection periodically. Especially before and after the thunder
storm season, check the lightning protection system.
Make sure that the illuminance in the equipment room meet the basic maintenance
requirements. Repair the lights that are not in good condition. Prevent the illuminance
dead angles that affect maintenance.
Establish a complete set of maintenance regulations for the equipment room to
standardize the routine maintenance work of the maintenance personnel. Create
detailed duty logs and make detailed records of the routine operation state of the
system, version, data change, upgrading and troubleshooting. This facilitates fault
analysis and troubleshooting once a fault occurs. Keep a shift record to define the
responsibilities clearly.
General Requirements
l
Make complete equipment room maintenance rules to regulate maintenance

personnel operations. Keep detailed log books for ease of troubleshooting, including
system operation, versions, data changes, update, and troubleshooting. Keep shift
record books and define the responsibilities clearly.
Maintenance personnel must be trained for the position, know about the equipment
and related networks, and master basic equipment operations and emergency
handling skills. Besides, maintenance personnel must comply with maintenance
operations described in this manual, for example, wearing antistatic wrist straps
before contacting equipment hardware to ensure personal safety and equipment
security. With professional attitude and high maintenance level, maintenance
personnel should improve maintenance skills by constant learning.
Record all major operations, such as board switchover, system reset, and software
loading, and confirm operation feasibility before performing operations. Only qualified
operators can perform major operations after backing up data and taking emergency
and security measures.
Back up data before modifying the data. Verify that the equipment operates properly
during a period of time, for example, one week, and then delete the backup data.
l
l
Network management passwords must be set by levels, managed strictly, and

modified periodically. Besides, the passwords must be known only to maintenance
personnel.
Do not play games or surf on terminals. Do not install, run or copy system-irrelated
software on terminals. Do not use terminals for other purposes.
Prepare common tools and instruments, such as screw drivers (straight and
cross), signaling instrument, network cable plier, multimeter, AC power supply for
maintenance purpose, telephone cable, and network cable. Calibrate instruments
periodically to ensure accuracy.
Check spare parts periodically to ensure that they are sufficient and in good condition,
and prevent moisture and mildew. Store spare parts and faulty parts separately after
replacement. Supplement common spare parts when they are exhausted. Repair
faulty boards in time and ensure the availability of sufficient board spare parts.
1-2
SJ-20140731105308-020|2014-10-20 (R1.0)
Chapter 1 Routine Maintenance Overview
l
l
l
l
l
l
Keep necessary software and materials handy.

Maintain normal temperature and humidity in the equipment room. Keep the
equipment room clean and prevent dust, moisture, rats and insects from entering the
equipment room. The equipment room environment must meet the requirements of
the Environment Acceptance Report.
Ensure reliable and stable power supplies. Check statuses of system grounding and
lightning protection ground periodically, especially before thunderstorm seasons and
after storms.
Repair broken lamps in time, and avoid dark areas in the equipment room.
Perform routine tests and inspections every day in accordance with suggestions
described in this manual, and make records.
Troubleshoot faults in time after finding them. If a fault is complicated, record various
original information, and contact ZTE technical support.
Put contact information of ZTE technical support in a conspicuous place for timely
contact. Update the contact details periodically.
1.3 Introduction to Routine Maintenance Items

According to the maintenance period, routine maintenance can be divided into four types.
l
l
l
l
Daily maintenance performed every day

Monthly maintenance performed once a month
Quarterly maintenance performed once a quarter
Yearly maintenance performed once a year
Routine maintenance items provide basic references and suggestions on daily

maintenance, monthly maintenance, quarterly maintenance, and yearly maintenance of
the operating environment, hardware, and software of the ZXR10 M6000-S equipment,
such as the equipment room environment, cabinet environment, board operation status,
port status, and routing protocol.
During equipment operation, maintenance personnel implement equipment maintenance
and management by referring to the operation guide of maintenance items. Meanwhile,
maintenance personnel can also add or delete maintenance items described in this chapter
in accordance with network architecture and equipment room environment requirements.
For all the routine maintenance items, refer to Table 1-1.
Table 1-1 Routine Maintenance List
Maintenance
Maintenance List
Period
Daily
Checking the equipment room environment, including temperature and humidity
maintenance
condition.
Checking power supplies of the equipment room, including AC and DC power
supplies.
1-3
SJ-20140731105308-020|2014-10-20 (R1.0)
Maintenance
Maintenance List
Period
Checking the cabinet environment, including the serial port cables and antistatic
wrist straps installed in the cabinets.
Checking basic equipment information, including software version, board online
status, alarms, operation logs, and abnormal files.
Checking equipment operational status, including equipment temperature, power
and fan module status, board indicator status, CPU usage, memory usage,
interface status, and interface traffic.
Checking service operational status, including protocol (such as OSPF, IS-IS,
BGP, LDP, and VRRP) status.
Monthly
maintenance
Checking power supply redundancy

Checking basic equipment information, including configuration files,
synchronization between the active and standby MPUs, version boot information,
and remaining capacity of hard disks.
Checking the system time.
Checking user security management, including the security of user passwords
and Enable passwords.
Checking the equipment interface information, including interface status, interface
description and interface configuration.
Checking service operational status, including protocol (such as OSPF, IS-IS,
BGP, LDP, and VRRP) status.
Checking basic equipment configuration, including configuration saving and
backup.
Quarterly
Checking cabinet environment, including cabling status, labels, rack appearance,
maintenance
cleanliness of air filters and fan modules, and heat dissipation of the rack.
Checking user security management, including changing user passwords and
enable passwords.
Checking basic equipment configuration, especially redundancy configurations
on the equipment.
Yearly
Checking equipment room environment, including fire protection condition,
maintenance
anti-theft condition, equipment grounding, power supply redundancy, and board

redundancy.
Checking cabinet environment, especially the cleanliness of the equipment.
1-4
SJ-20140731105308-020|2014-10-20 (R1.0)
Chapter 2
Periodic Inspection of
Equipment Hardware and
Software Statuses
Table of Contents
Checking Equipment Software Status.........................................................................2-1
Checking Equipment Hardware Status .......................................................................2-5
Checking Equipment Alarms ....................................................................................2-10
2.1 Checking Equipment Software Status

Check the software module status of the equipment, including protocol (OSPF, IS-IS, and
BGP) status, equipment version and boot mode.
2.1.1 Checking the OSPF Status

Check the neighbor status of the OSPF protocol, database information, and configuration
information such as router-id.
Steps
1. Check the OSPF neighbor status.
The OSPF neighbor status should be FULL. If it is not, check the configurations of
both sides, especially the advertising of the network segments of directly-connected
interfaces.
ZXR10#show ip ospf neighbor
OSPF Router with ID (20.0.0.3) (Process ID 32)
Neighbor ID
Pri State
DeadTime
Address
Interface
20.0.0.7
00:00:30
192.168.1.6
gei-0/0/0/3.32
FULL/DR
Neighbor ID
Pri State
DeadTime
Address
Interface
10.0.0.4
00:00:33
172.0.1.2
gei-0/0/0/2.31
FULL/DR
2-1
SJ-20140731105308-020|2014-10-20 (R1.0)
2. Check the OSPF database information.

Check whether the advertising information of the OSPF link status is correct.
ZXR10#show ip ospf database
Router Link States (Area 0.0.0.1)
Link State ID
ADV Router
Age
Seq#
Checksum
Link count
20.0.0.3
20.0.0.3
707
0x80000122
0x19e6
20.0.0.4
20.0.0.4
287
0x8000011f
0x34b4
20.0.0.7
20.0.0.7
1549
0x80000127
0xba16
20.0.0.8
20.0.0.8
1569
0x80000125
0x9a25
20.0.0.9
20.0.0.9
938
0x80000125
0x5459
3. Check the OSPF configuration information.

Check whether the OSPF configuration, redundancy configuration, route advertising,
route redistribution, and router-id are correct.
ZXR10#show running-config ospfv2
!<ospfv2>
router ospf 31
network 10.0.0.4 0.0.0.0 area 0.0.0.0
network 172.0.1.0 0.0.0.3 area 0.0.0.0
network 172.0.1.16 0.0.0.3 area 0.0.0.1
passive-interface loopback1
router-id 10.0.0.4
$
router ospf 32 vrf VPN123
network 192.168.1.16 0.0.0.3 area 0.0.0.1
passive-interface loopback2
redistribute connected
redistribute bgp-int route-map U31
router-id 20.0.0.4
$
!</ospfv2>
End of Steps
2.1.2 Checking the IS-IS Status

Check the neighbor status of the IS-IS protocol and the configuration information.
Steps
1. Check the IS-IS neighbor status.
2-2
SJ-20140731105308-020|2014-10-20 (R1.0)
Chapter 2 Periodic Inspection of Equipment Hardware and Software Statuses
The IS-IS neighbor status should be UP. If it is not, check the configurations of both
sides and verify that the corresponding interface is configured with IS-IS.
ZXR10#show isis adjacency
Process ID: 0
Interface
System id
State
Lev
Holds
SNPA(802.2)
Pri
gei-0/0/0/1
ER2-M6000-3S
UP
L2
00D0.D012.3456
64
gei-0/0/0/2
B1-M6000-3S
UP
L2
25
0000.3441.EEB1
64
MT
2. Check the IS-IS configuration information.

Check whether the IS-IS configuration is correct and whether there is redundancy
configuration.
ZXR10#show running-config isis
!<isis>
router isis 0
area 86.0025
system-id 1000.0000.0004
is-type level-2-only
metric-style wide
distance 105
fast-flood 6
fast-reroute enable
ignore-lsp-errors
i-spf
lsp-gen-interval 1 50 50
spf-interval 1 50 50
maximum-paths 8
mpls ldp sync
mpls traffic-eng level-2
interface loopback1
ip router isis
circuit-type level-2-only
$
End of Steps
2.1.3 Checking the BGP Status

Check the neighbor status of the BGP protocol and the configuration information.
Steps
1. Check the BGP neighbor status.
The BGP neighbor status should be Established.
configuration.
If it is not, check the BGP
2-3
SJ-20140731105308-020|2014-10-20 (R1.0)

ZXR10#show bgp all summary
Neighbor
Ver
As
MsgRcvd
MsgSend
Up/Down
State
10.0.0.1
100
4890
4866
2d23h
Established
10.0.0.2
100
4857
4861
2d23h
Established
2. Check the MP-BGP neighbor status.

ZXR10#show bgp vpnv4 unicast summary
Neighbor
Ver
As
MsgRcvd
MsgSend
Up/Down
State/PfxRcd
10.0.0.1
100
4889
4865
2d23h
10
10.0.0.2
100
4856
4860
2d23h
3. Check the BGP configuration information, especially the AS configuration information.

ZXR10#show running-config bgp
!<bgp>
router bgp 100
synchronization disable
neighbor 10.0.0.1 remote-as 100
neighbor 10.0.0.1 activate
neighbor 10.0.0.1 update-source loopback1
neighbor 10.0.0.2 remote-as 100
neighbor 10.0.0.2 update-source loopback1
address-family ipv4 vrf VPN123
redistribute ospf-int 32
$
address-family ipv4 vrf IP-RAN
maximum-paths ibgp 8
redistribute subscriber-host
$
address-family vpnv4
$
End of Steps
2.1.4 Checking the Equipment Version

Check the current version of the equipment, including software and hardware versions.
Steps
1. Run the show version command to check whether the equipment operating versions
meet the requirements.
Upgrade them to correct versions if they fail to meet the requirements.
2-4
SJ-20140731105308-020|2014-10-20 (R1.0)

ZXR10#show version
ZXR10 M6000-5S
ZTE ZXR10 Software, Version: M6000 V3.00.10(2.1.1), Release software
Copyright (c) 2014 by ZTE Corporation
Build on 2014/10/15 14:44:35
System image file is <sysdisk0: verset/base.set>, file size is 1,146,652,669 Bytes
System image is loaded from local
System uptime is 6 day(s), 16 hour(s), 1 minute(s)
End of Steps
2.1.5 Checking Equipment Boot Mode

Check whether the boot mode of the equipment is "local".
Steps
1. Run the show nvram command to check whether the boot mode of the equipment is
"local".
ZXR10#show nvram
imgfile-location
: local /*local indicates that the boot mode is set to "local".*/
mng-ip-address
: 192.168.0.1 255.255.255.0
boot-server
: 192.168.0.2
default-gateway
: 192.168.0.2
boot-username
: target
ftp-path
: \
mng-ipv6-address
: 192:168:6:0:0:0:0:3/64
boot-ipv6-server
: 190:0:0:0:0:0:0:1
def-ipv6-gateway
: 192:168:6:0:0:0:0:1
mng-ipv6-enable
: enable
boot-from
: ipv4-server
The boot mode of the equipment is suggested to be "local". If it is not, change it to

"local". Use the following command.
ZXR10(config)#nvram imgfile-location local
End of Steps
2.2 Checking Equipment Hardware Status

Check the hardware status of the equipment, including the power module status, fan
module status, temperature, CPU usage, and memory usage of the equipment.
2-5
SJ-20140731105308-020|2014-10-20 (R1.0)
2.2.1 Checking the Power Supply Status

Check whether the equipment has power supply redundancy, whether the working status
of the power supply is normal, and whether the voltage and current satisfy the operation
requirements of the equipment.
Context
There should be power supply redundancy. If there is not, new power module needs to
be added to ensure normal equipment operation. In normal conditions, Phy status is
online and Power status is normal. If they are not, check whether the power modules
are switched on.
Steps
1. Run the show power command to check the power supply status of the equipment.
ZXR10#show power
[shelf 0 LCC]:
Total power capacity
: 3429.49W
Total used power
Power type
: DC
Power group numbers : 2
Power modules per group: 1

Redundancy type
Division numbers
: 664.00W
: 1
: 1+1
Group A power capacity : 3429.49W

Group B power capacity : 0.00W
Used power
Supply
Phy
Power
Com
Run
Division Module Name
Status
Status
Status
Status
A0
PPC34 D008
online
normal
normal
B0
PPC34 D008
online
abnormal normal
Power
Power
: 664.00W
Power
Power
Output
Output
Power
Power
normal
abnormal
Software
Module Capacity
Voltage
Current Alloted
Available Version
A0
3429.49W
52.12V
12.74A
664.00W
2765.49W
V1.1
B0
65.80W
1.00V
0.00A
0.00W
65.80W
V1.1
End of Steps
2.2.2 Checking the Fan Status

Check whether the fan module of the equipment works normally.
Context
In normal conditions, the fan status is online or work normally. If it is not, check whether
the fan module works properly.
2-6
SJ-20140731105308-020|2014-10-20 (R1.0)
Steps
1. Run the show fan command to check whether the fan works properly.
ZXR10#show fan
[shelf 0 LCC]:
Group 0: online
Fan speed mode: auto
Fan
name: FAN
Index
Status
Speed
work normally
73%
work normally
71%
work normally
73%
work normally
69%
Group 1: online
Fan
name: FAN
Index
Status
work normally
73%
Speed
work normally
69%
work normally
73%
work normally
70%
Group 2: online
Fan
name: FAN
Index
Status
Speed
work normally
74%
work normally
76%
work normally
74%
work normally
75%
End of Steps
2.2.3 Checking Temperature

Check whether the equipment temperature meets the operation requirements.
Context
Minor is the lowest equipment temperature threshold, and Temper is the current
equipment temperature. In normal conditions, the current temperature should be lower
than the lowest equipment temperature threshold. If not, check whether the equipment
fan or air conditioners of the equipment room works normally.
2-7
SJ-20140731105308-020|2014-10-20 (R1.0)
Steps
1. Run the show temperature detail command to check whether the equipment
temperature is normal.
ZXR10#show temperature detail
----------------------------------------------------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 0]
BoardType I2C Addr
Status
Minor Major Fatal Temper
----------------------------------------------------PFU
48
Normal
70
75
80
30
PFU
50
Normal
85
90
95
26
PFU
52
Normal
85
90
95
37
PFU
82
Normal
85
90
95
33
PFU
84
Normal
90
95
100
29
PFU
86
Normal
85
90
95
36
PFU
152
Normal
85
90
95
47
PFU
154
Normal
85
90
95
33
PFU
48
Normal
95
105
110
26
PIU
25
Normal
85
90
95
35
PIU
27
Normal
85
90
95
28
[shelf 0, slot 2]
BoardType I2C Addr
Status
----------------------------------------------------PFU
48
Normal
85
90
95
29
PFU
50
Normal
85
90
95
22
PFU
52
Normal
90
95
100
28
PFU
82
Normal
80
85
90
26
PIU
25
Normal
75
85
95
19
[shelf 0, slot 3]
BoardType I2C Addr
Status
----------------------------------------------------PFU
48
Normal
85
90
95
26
PFU
50
Normal
85
90
95
22
2-8
SJ-20140731105308-020|2014-10-20 (R1.0)

PFU
52
Normal
90
95
100
23
PFU
82
Normal
80
85
90
26
PIU
25
Normal
75
80
90
16
PIU
26
Normal
75
80
90
18
[shelf 0, slot 5]
BoardType I2C Addr
Status
----------------------------------------------------MPU
Normal
85
95
100
40
MPU
Normal
95
105
110
43
MPU
17
Normal
55
58
60
24
MPU
87
Normal
70
75
80
23
MPU
91
Normal
85
95
105
28
MPU
90
Normal
85
90
95
25
End of Steps
2.2.4 Checking CPU and Memory Usages

Check whether the CPU and memory usages of the equipment are too high. If the CPU
or memory usage keeps high for a long period, services are easily interrupted.
Context
In normal situations, the 5-second CPU usage ratio of boards should be lower than 70%
and the memory usage ratio of boards should be lower than 80%. If the CPU or memory
usage keeps high for a long period, find out the cause and resolve the problem immediately.
Steps
1. Run the show processor command and check the CPU and memory usages of
equipment boards.
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
================================================================================
2-9
SJ-20140731105308-020|2014-10-20 (R1.0)

================================================================================
Character CPU(5s) CPU(1m) CPU(5m) Peak PhyMem FreeMem Mem

================================================================================
PFU-0/0/0
N/A
5%
6%
6%
8%
2048
609
70.264%
-------------------------------------------------------------------------------PFU-0/2/0
N/A
8%
7%
6%
8%
4096
2769
32.397%
-------------------------------------------------------------------------------PFU-0/3/0
N/A
7%
9%
9%
12%
4096
2757
32.690%
-------------------------------------------------------------------------------MPU-0/5/0
MSC
13%
13%
13%
15%
4096
2666
34.912%
--------------------------------------------------------------------------------
In the above table, the third columnCPU (5s) is the CPU usage ratio of the board in
five seconds, and the last columnMem is the memory usage ratio.
End of Steps
2.3 Checking Equipment Alarms

Check the alarms of the equipment itself, including alarms of the ports, protocols, and
services.
Context
Check the alarm information of the equipment. Mainly check whether there are down
alarms of key ports, alarms of frequent port status (up/down) switchovers, down alarms of
routing protocols, and alarms of frequent protected service switchovers.
Steps
1. Run the show logging alarm command to check the alarm information of the equipment.
ZXR10#show logging alarm
An alarm 400136 ID 169 level 5 cleared at 19:08:51 06-08-2014 sent by
M6000-3S PFU-0/0/0
%PORT% Physical interface status
The physical interface gei-0/0/0/8
turned into UP
An alarm 150101 ID 170 level 5 cleared at 19:08:51 06-08-2014 sent by
M6000-3S MPU-0/4/0
%IP% Interface status
The interface(index=23,name='gei-0/0/0/8') turned
into protocol UP
An alarm 150101 ID 170 level 5 occurred at 19:01:47 06-08-2014 sent by
M6000-3S MPU-0/4/0
%IP% Interface status
The interface(index=23,name='gei-0/0/0/8') turned
into protocol DOWN

M6000-3S PFU-0/0/0
2-10
SJ-20140731105308-020|2014-10-20 (R1.0)

%PORT% Physical interface status
The physical interface gei-0/0/0/8 turned
into DOWN
End of Steps
2-11
SJ-20140731105308-020|2014-10-20 (R1.0)
2-12
SJ-20140731105308-020|2014-10-20 (R1.0)
Chapter 3
Scheduled Maintenance
Items
By the cycle of scheduled maintenance, routine maintenance is classified as daily
maintenance, monthly maintenance, quarterly maintenance, and yearly maintenance.
Maintenance of different cycles has different focuses.
Table of Contents
Daily Maintenance Items ............................................................................................3-1
Monthly Maintenance Items......................................................................................3-16
Quarterly Maintenance Items....................................................................................3-23
Yearly Maintenance Items ........................................................................................3-26
3.1 Daily Maintenance Items

3.1.1 Checking the Equipment Room Environment
Purpose
This procedure describes how to check the equipment room environment to ensure
suitable temperature and humidity.
Inspection Items
l
l
l
l
Check and record the operational statuses of the air conditioners in the equipment
room. Repair or replace the faulty ones immediately.
Check the reading on the thermometer.
Observe the reading on the hygrometer.
Check the outside and inside of the equipment, floor, and working table.
Reference Standards
l
l
The air conditioners in the equipment room are operating properly.

The temperature and humidity in the equipment room meet the requirements
described in Table 3-1.
3-1
SJ-20140731105308-020|2014-10-20 (R1.0)
Table 3-1 Temperature and Humidity Requirements

Maintenance Items
Reference Standard
Temperature in the
Operating temperature: -5C to 45C
equipment room
Humidity in the
equipment room
Storage temperature: -40C to 70C

Operating humidity: 5% to 90%
Storage humidity: 0% to 95%
If the temperature does not meet the requirements, verify that the air conditioners in
the equipment room are operating properly.
If the humidity is too low, install humidifiers.
dehumidifiers.
If the humidity is too high, install
3.1.2 Checking Power Supplies

Purpose
This procedure describes how to check the power supplies in the equipment room to
ensure normal operational voltage provided by AC and DC power supplies.
Inspection Items
l
l
Check power supplies in the equipment room, and the DC operating voltage, and
make a record.
Check power supplies in the equipment room, and the AC operating voltage, and
make a record.
3.1.3 Checking the Cabinet Environment

Purpose
This procedure describes how to verify that serial port cables and the antistatic wrist straps
are installed in the cabinets.
Inspection Items
l
l
Verify that there are antistatic wrist straps in the cabinets.

Verify that there are serial port cables in the cabinets.
Reference Standards
There should be at least one serial port cable and one antistatic wrist strap in a cabinet.
3-2
SJ-20140731105308-020|2014-10-20 (R1.0)
Chapter 3 Scheduled Maintenance Items
3.1.4 Checking Basic Equipment Information

Purpose
This procedure describes how to check basic equipment information, service traffic, and
operational indicators to find potential faults.
Inspection Items
l
l
l
l
Check
Check
Check
Check
software version and board operational status.

alarm information.
operational logs.
fault record files.
Reference Standards
l
Run the show version command to check the software version and board operational
statuses.
Software version and version operating duration must be the same as those recorded
by users. Installed boards are in Online status.
If the information is not the same or there is a fault, identify the causes immediately.
The following is a result example:
ZXR10#show version
ZXR10 M6000-5S
ZTE ZXR10 Software, Version: M6000 V3.00.10(2.1.1), Release software
Copyright (c) 2014 by ZTE Corporation
Build on 2014/10/15 14:44:35
System image file is <sysdisk0: verset/base.set>, file size is 1,146,652,669 Bytes
System image is loaded from local
System uptime is 6 day(s), 16 hour(s), 1 minute(s)
Run the show logging alarm command to check whether there is any alarm information.
ZXR10#show logging alarm
ZXR10 M6000-S MPU-0/3/0
%L2VPN% PW status
The status of the pw5809(inst_name = e1-2, inst_type = mspw,
pwtype = 21) was down
Run the show logfile command to check the operation logs.

ZXR10#show logfile
StartTime: 08:32:27 06-04-2014
FlowID: 305
VtyNo: vty0
HostName: ZXR10
EndTime: 08:33:26 06-04-2014
UserName: who
Result: cease-data
UserLevel: 15
IP: 168.1.40.254
CMDLevel: 2
3-3
SJ-20140731105308-020|2014-10-20 (R1.0)

CMDLine: show logging alarm
Check the Exc_Omp.txt, Exc_pp.txt files in the /sysdisk0/ directory and the files
in the EXCINFO folder.
There should be no new fault record files.
If there is a new fault record file generated after the last check, analyze the file.
ZXR10#cd /sysdisk0
ZXR10#dir
......
15
----
66643
09-07-2009
10:05
Exc_pp.txt
16
----
16536
09-16-2009
04:20
Exc_Omp.txt
......
ZXR10#cd EXCINFO
ZXR10#dir
Directory of MPU-0/4/0: /sysdisk0/EXCINFO
8254240
KB total (4674988 KB free)
attribute
size
date
time
name
<DIR>
4096
09-02-2009
04:55
<DIR>
4096
09-02-2009
04:55
..
----
271834
09-14-2011
17:26
Exc_0_0_3_0.txt
----
13826
09-02-2009
04:56
Exc_0_0_1_0.txt
----
188966
09-07-2009
11:11
Exc_0_0_4_0.txt
3.1.5 Checking Equipment Operational Status

Purpose
This procedure describes how to check equipment operational status to prevent faults and
ensure reliable system operation.
Inspection Items
l
l
l
l
l
l
l
Check
Check
Check
Check
Check
Check
Check
equipment temperature.
fan status.
power supply status.
board indicators.
CPU usage and memory usage.
interface status.
interface traffic.
Reference Standards
l
Run the show temperature detail command to check current system temperature.
3-4
SJ-20140731105308-020|2014-10-20 (R1.0)
In normal situations, the system temperature should be lower than the lowest alarm
threshold.
As shown below, the Minor column shows the lowest alarm threshold, and the Temper
column shows the current system temperature.
ZXR10#show temperature detail
[shelf 0, slot 0]
PCB
I2C Addr
Status
--------------------------------------------------PFU
48
Normal
85
90
95
42
PFU
50
Normal
85
90
95
40
Run the show fan command to check the fan operational status.
In normal situations, the configured fan modules should be in online and work
normally statuses.
If a fault occurs on a configured fan module, for example, the status is offline, handle
the fault immediately.
ZXR10#show fan
[shelf 0 LCC]:
Group 0: online
Fan
name: FAN
Index
Status
Speed
work normally
73%
work normally
71%
work normally
73%
work normally
69%
Group 1: online
Fan
name: FAN
Index
Status
work normally
73%
Speed
work normally
69%
work normally
73%
work normally
70%
Group 2: online
Fan
name: FAN
Index
Status
Speed
work normally
74%
work normally
75%
3-5
SJ-20140731105308-020|2014-10-20 (R1.0)
work normally
74%
work normally
75%
Run the show power command to check the power supply operational status.
In normal situations, the configured power supply modules should be in the online
and normal statuses.
If a fault occurs on a configured power supply module, for example, the status is
abnormal, handle the fault immediately.
ZXR10#show power
[shelf 0 LCC]:
Total power capacity
: 3429.49W
Total used power
Power type
: DC
Power group numbers : 2
Power modules per group: 1

Redundancy type
Division numbers
: 664.00W
: 1
: 1+1
Group A power capacity : 3429.49W

Group B power capacity : 0.00W
Used power
Supply
Phy
Power
Com
Run
Division Module Name
Status
Status
Status
Status
A0
PPC34 D008
online
normal
normal
B0
PPC34 D008
online
abnormal normal
Power
Power
: 664.00W
Power
Power
Power
Power
normal
abnormal
Output
Output
Module Capacity
Voltage
Current Alloted
Available Version
Software
A0
3429.49W
52.12V
12.74A
664.00W
2765.49W
V1.1
B0
65.80W
1.00V
0.00A
0.00W
65.80W
V1.1
Check whether equipment indicators are normal.

In normal situations, the indicators should be in the following statuses:
Module with Indicators
Active MPU/SRU
Normal Indicator Status

The RUN indicator flashes synchronously, and the ACT indicator
is solid on.
Standby MPU/SRU
The RUN indicator flashes synchronously, and the ACT indicator

is off.
SFU and the PFU
The RUN indicator flashes synchronously.
DC power supply module
The RUN indicator is solid on.
AC power supply module
Fan module
If the indicator status is abnormal, locate and resolve the problem immediately.
3-6
SJ-20140731105308-020|2014-10-20 (R1.0)
Run the show processor command to check CPU usage and memory usage of each
board.
The 5-second CPU usage of a board should be less than 70%, and the memory usage
(the last column) of a board should be less than 80%.
If the CPU usage or the memory usage is too high for a long time, identify the causes
immediately.
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

================================================================================
PFU-0/0/0
N/A
7%
6%
6%
8%
2048
609
70.264%
-------------------------------------------------------------------------------PFU-0/2/0
N/A
6%
7%
7%
8%
4096
2769
32.397%
-------------------------------------------------------------------------------PFU-0/3/0
N/A
8%
9%
9%
13%
4096
2757
32.690%
-------------------------------------------------------------------------------MPU-0/5/0
MSC
13%
13%
13%
14%
4096
2666
34.912%
--------------------------------------------------------------------------------
Run the show ip interface brief command to check the interface statuses.
The management status, physical status and protocol status of an interface in use
should be up.
If a fault occurs, check the configurations and physical connections immediately.
ZXR10#show ip interface
brief
Interface
IP-Address
Mask
Admin Phy
Prot
gei-0/0/0/1
172.0.0.6
255.255.255.252
up
up
up
3-7
SJ-20140731105308-020|2014-10-20 (R1.0)
gei-0/0/0/2
172.0.0.9
255.255.255.252
up
up
up
gei-0/0/0/2.00000031
172.0.1.1
255.255.255.252
up
up
up
gei-0/0/0/2.00000100
172.0.0.29
255.255.255.252
up
up
up
gei-0/0/0/2.00001001
7.100.0.1
255.255.255.252
up
up
up
Run the show interface command to check interface traffic.

Traffic on all interfaces should not exceed 80% of the threshold, and the traffic does
not change too much compared with that in the last check.
If the interface traffic exceeds 80% or changes a lot, identify the causes immediately.
Meanwhile, verify that there is any Cyclic Redundancy Check (CRC) fault on the
interfaces.
For the Ethernet interface, check whether the interface is working in half-working
status.
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*/
Internet address is 20.0.0.55/24
/*IP address of the interface*/
BW 1000000 Kbps
/*Bandwidth of the interface*/
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*/
Holdtime is 120 sec(s)
/*Hold time of the interface*/
The port is optical
/*Optoelectronic attribute of the interface*/
The MDIMode of the port is not supported

Loopback cancel
/*MDI mode of the interface*/
/*Loopback mode of the interface*/
Duplex full
/*Working
Negotiation auto
/*Negotiation mode of the interface*/
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
Last Refresh Time: 2014-05-28 17:13:50
/*The last time when the statistics information of the interface is

cleared and refreshed*/
120s input rate : 194Bps
1Pps
/*Rate of input packets in 120 seconds on the interface*/

120s output rate: 101Bps
0Pps
/*Rate of output packets in 120 seconds on the interface*/

Peak rate:
input
219Bps
peak time
2014-05-28 14:20:40
output
115Bps
peak time
2014-05-28 14:05:30
Intf utilization: input 0%
output 0%
3-8
SJ-20140731105308-020|2014-10-20 (R1.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
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
3.1.6 Checking Service Operational Status

Purpose
This procedure describes how to check the service operational status to ensure reliable
service operation.
Inspection Items
l
l
l
l
l
l
Check
Check
Check
Check
Check
Check
OSPF neighbor status.

IS-IS neighbor status.
BGP neighbor status.
routing information.
the MPLS IP status.
the L3VPN status.
3-9
SJ-20140731105308-020|2014-10-20 (R1.0)
l
l
l
Check the L2VPN status.

Check the MPLS-TE status.
Check the BFD status.
Reference Standards
l
Check the OSPF neighbor status.

In normal situations, all OSPF neighbors should be in FULL status, or the DRother
is in 2-way status. If they are not, find out the cause.
ZXR10#show ip ospf neighbor
Neighbor ID
Pri State
DeadTime
Address
Interface
10.0.0.3
FULL/DR
00:00:35
172.0.1.1
gei-0/0/0/2.31
10.0.0.9
FULL/DR
00:00:39
172.0.1.17
gei-0/0/0/3.31
Check the IS-IS neighbor status.

In normal situations, all IS-IS neighbors should be in UP status. If they are not, find
out the cause.
ZXR10#show isis adjacency
Process ID: 0
Interface
System id
State
Lev
Holds
SNPA(802.2)
Pri
gei-0/0/0/1
ER1-M6000-8S
UP
L2
0022.935D.D9C0
64
gei-0/0/0/2.100
B2-M6000-3S
UP
L2
002D.DEFE.4F03
64
MT
Check the BGP neighbor status.

In normal situations, all BGP neighbors should be in Establish status. If they are not,
find out the cause.
ZXR10#show bgp all summary
Neighbor
Ver
As
MsgRcvd
MsgSend
Up/Down
State
10.0.0.1
100
1715
1696
1d0h
Established
10.0.0.2
100
1637
1623
23:38:04
Established
8.0.0.2
300
00:00:00
Connect
Check the route information.

In normal situations, compare the inspection result of this time with that of last time.
The number of route entries should not change greatly. If it is not, find out the reason
of the change.
ZXR10#show ip forwarding route
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,
3-10
SJ-20140731105308-020|2014-10-20 (R1.0)

GW-UE: PS-USER, P-VRF: Per-VRF-label, TE: RSVP-TE;
Status codes: *valid, >best;

Gw
Interface
Owner
Pri Metric
*> 0.0.0.0/0
Dest
172.0.0.30
gei-0/0/0/2.100
ISIS-L2
105 1520
*> 7.7.0.1/32
172.0.0.5
gei-0/0/0/1
BGP
200 0
*> 7.7.0.3/32
7.7.0.3
loopback100
Address
*> 10.0.0.1/32
172.0.0.5
gei-0/0/0/1
ISIS-L2
105 1510
ZXR10#show ip forwarding route summary

The total routes of global and all VPNs:
Route Source
Count
static:
direct:
29
martian:
address:
35
ospf:
13
bgp:
35
rip:
isis-level1:
isis-level2:
18
icmp:
snmp:
nat:
pat:
vrrp:
ppp:
asbrvpn:
rsvpte:
user-ipaddr:
user-network:
static-vrf:
ipsec:
perVrf-label:
ps-busi:
ps-user:
ldp-area:
user-special:
dhcp-dft:
dhcp-static:
nat64-sl:
ves:
Total:
131
Check the MPLS IP status.

3-11
SJ-20140731105308-020|2014-10-20 (R1.0)
In normal situations, all LDP neighbors should be in oper status. If they are not, find
out the cause. The label should be either numbers or pop. If it is untag, the LSP
is abnormal. Check the status of the LDP neighbors connected on both sides of the
equipment in the network.
/*Check the LDP neighbor status. */
ZXR10#show mpls ldp neighbor instance 1
Peer LDP Ident: 10.0.0.1:0; Local LDP Ident: 10.0.0.3:0
TCP connection: 10.0.0.1.646 - 10.0.0.3.26526
State: Oper; Msgs sent/rcvd: 1511/1507; Downstream
Up Time: 1d0h
LDP discovery sources:
gei-0/0/0/1; Src IP addr: 172.0.0.5
Targeted Hello (10.0.0.1); Src IP addr: 10.0.0.1
Addresses bound to peer LDP Ident:
7.7.0.1
10.0.0.1
172.0.0.1
172.0.0.5
172.0.0.242
/*Check the LDP label. */

ZXR10#show mpls forwarding-table
Local
Outgoing
Prefix or
Outgoing
label
label
Lspname
interface
Next Hop
M/S
16384
Poptag
10.0.0.1/32
gei-0/0/0/1
172.0.0.5
16385
16390
10.0.0.2/32
gei-0/0/0/2.100
172.0.0.30
16385
16385
10.0.0.2/32
gei-0/0/0/1
172.0.0.5
16386
Poptag
10.0.0.103/32
gei-0/0/0/8.2000
172.0.0.218
16387
Poptag
10.0.0.7/32
gei-0/0/0/3.31
172.0.1.6
16388
279
10.0.0.8/32
gei-0/0/0/3.31
172.0.1.6
Check the VRF configuration.

ZXR10#show running-config vrf
!<vrf>
ip vrf IP-RAN
rd 4134:3050
/*Check the RD, import and export configurations. */
mpls label mode per-vrf

address-family ipv4
route-target import 4134:305000
route-target export 4134:305000
$
$
ip vrf VPN123
description For mng
rd 4134:1619
mpls label mode per-vrf
3-12
SJ-20140731105308-020|2014-10-20 (R1.0)

address-family ipv4
route-target import 4134:161900
route-target export 4134:161900
$
$
!</vrf>
Check the L3VPN route.

ZXR10#show ip forwarding route vrf IP-RAN
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
Gw
Interface
Owner
Pri
Metric
*> 2.2.2.2/32
10.0.0.1
gei-0/0/0/1
BGP
200
*> 2.2.2.2/32
10.0.0.2
gei-0/0/0/2.100
BGP
200
*> 7.0.0.0/26
7.0.0.1
supervlan1
Direct
*> 7.0.0.1/32
7.0.0.1
supervlan1
Address
*> 7.0.0.7/32
7.0.0.7
supervlan1
USER-I
*> 10.0.1.1/32
10.0.0.1
gei-0/0/0/1
BGP
200
Check the labels of the private network.

ZXR10#show ip protocol routing vrf IP-RAN
Codes: OSPF-3D=ospf-type3-discard, OSPF-5D=ospf-type5-discard, TE=rsvpte,
OSPF-7D=ospf-type7-discard, USER-I=user-ipaddr, RIP-D=rip-discard,
OSPF-E=ospf-ext, ASBR-V=asbr-vpn, GW-FWD=ps-busi, GW-UE=ps-user,
BGP-AD=bgp-aggr-discard, BGP-CE=bgp-confed-ext, NAT64=sl-nat64-v4,
USER-N=user-network, USER-S=user-special, DHCP-S=dhcp-static,
DHCP-D=dhcp-dft, VES=video-enhanced-service
Marks: *valid, >best, s-stale
Dest
NextHop
Intag
Outtag
RtPrf
Protocol
*>
2.2.2.2/32
10.0.0.1
212993
212993
200
BGP-INT
*>
2.2.2.2/32
10.0.0.1
212993
212993
200
BGP-INT
*>
2.2.2.2/32
10.0.0.2
212993
212993
200
BGP-INT
*>
2.2.2.2/32
10.0.0.2
212993
212993
200
BGP-INT
*>
7.0.0.0/26
7.0.0.1
212993
notag
Direct
7.0.0.0/26
10.0.0.4
212993
212993
200
BGP-INT
7.0.0.0/26
10.0.0.4
212993
212993
200
BGP-INT
Check the labels of the public network.

ZXR10#show mpls forwarding-table
Local
Outgoing
Prefix or
Outgoing
Next Hop
M/S
3-13
SJ-20140731105308-020|2014-10-20 (R1.0)

label
label
Lspname
interface
16384
Poptag
10.0.0.4/32
gei-0/0/0/2.100
172.0.0.30
16385
16385
10.0.0.2/32
gei-0/0/0/2.100
172.0.0.30
16385
16386
10.0.0.2/32
gei-0/0/0/1
172.0.0.5
16386
16386
100.1.1.1/32
gei-0/0/0/2.100
172.0.0.30
16386
16387
100.1.1.1/32
gei-0/0/0/1
172.0.0.5
16387
16387
100.1.1.2/32
gei-0/0/0/2.100
172.0.0.30
16387
16388
100.1.1.2/32
gei-0/0/0/1
172.0.0.5
16388
16388
100.1.1.3/32
gei-0/0/0/2.100
172.0.0.30
/*In normal situations, "outgoing label" should be either numbers or "Poptag".

If it is "Untag", the LSP is abnormal.
Check the LDP configurations on both sides. */
Check the MPBGP neighbor status.

ZXR10#show bgp vpnv4 unicast summary
Neighbor
Ver As
MsgRcvd
MsgSend
Up/Down
State/PfxRcd
10.0.0.1
100
296
286
04:11:43
26
10.0.0.2
100
294
287
04:11:50
26
/*"26" refers to the 26 VPN routes learned from the MPBGP neighbor. */
Check the learning situation of the MPBGP routes.

/*Check the routes learned from the MPBGP neighbor. */
ZXR10#show ip bgp neighbor vpnv4-in 10.0.0.1
Routes Learned From This Neighbor:
Status codes: * valid, > best, i - internal, s - stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Dest
Next Hop
Metric
LocPrf
InTag
Path
Route Distinguisher: 4000:1

*>i
172.2.1.0/30
10.0.0.1
100
212994 ?
*>i
172.2.1.4/30
10.0.0.2
100
212995 ?
*>i
172.4.1.0/30
10.0.0.1
100
212994 ?
Route Distinguisher: 4134:1619 (default for vrf VPN123)

*>i
10.1.1.0/24
10.0.0.1
100
212992 ?
*>i
10.1.1.35/32
10.0.0.1
100
212992 ?
*>i
20.0.0.1/32
10.0.0.1
100
212992 ?
*>i
20.0.0.2/32
10.0.0.2
100
212992 ?
/*Check the routes sent to the MPBGP neighbor. */

ZXR10#show ip bgp neighbor vpnv4-out 10.0.0.1
Routes Sent To This Neighbor:
Origin codes: i - IGP, e - EGP, ? - incomplete
Dest
Next Hop
Metric
LocPrf
Tag
Path
Route Distinguisher: 4134:1619 (default for vrf VPN123)

20.0.0.3/32
10.0.0.3
100
212994
3-14
SJ-20140731105308-020|2014-10-20 (R1.0)

20.0.0.7/32
10.0.0.3
100
212994
20.0.0.8/32
10.0.0.3
103
100
212994
129.0.0.1/32
10.0.0.3
100
212994
192.168.1.8/30
10.0.0.3
100
212994
192.168.1.16/30
10.0.0.3
100
212994
102
Route Distinguisher: 4134:3050 (default for vrf IP-RAN)
7.0.0.0/26
10.0.0.3
100
212993
7.0.0.7/32
10.0.0.3
100
212993

ZXR10#show l2vpn forwardinfo
Headers: PWType - Pseudo Wire type and Pseudo Wire connection mode
Llabel - Local label, Rlabel - Remote label
VPNowner - Owner type and instance name
Codes
: H - HUB mode, S - SPOKE mode, L - VPLS, W - VPWS, M - MSPW,

MO - MONITOR, $pw - auto_pw
PWName
PeerIP
FEC
PWType
State Llabel
Rlabel
VPNowner
pw201
10.0.0.9
128
Ethernet
UP
81920
2110
W:201
pw202
10.0.0.9
128
Ethernet
UP
81921
3105
W:202
pw203
10.0.0.9
128
Ethernet
UP
81922
96
W:203
pw204
10.0.0.9
128
Ethernet
UP
81923
32
W:204
pw205
10.0.0.9
128
Ethernet
UP
81924
3169
W:205
pw206
10.0.0.9
128
Ethernet
UP
81925
2062
W:206
pw207
10.0.0.9
128
Ethernet
UP
81926
1103
W:207
/*In normal situations, all PWs are in "UP" status. If they are not,
check the configuration of PWs on both sides of the equipment
in the network, especially some parameters that need negotiation. */
Check the MPLS-TE status.

ZXR10#show mpls traffic-eng tunnels brief
Signalling Summary:
LSP Tunnels Process:
running
RSVP Process:
running
Forwarding:
enabled
TUNNEL NAME
DESTINATION
UP IF
DOWN IF
STATE/PROT
tunnel_1
10.0.0.2
up/down
Check the BFD status.

/*Check all PW BFD statuses. */
ZXR10#show bfd neighbors pw brief
Pwname
LD
RD
Hold
State
pw220
2072
150
UP
pw219
2071
150
UP
pw218
2070
150
UP
pw217
2069
150
UP
pw216
2068
150
UP
3-15
SJ-20140731105308-020|2014-10-20 (R1.0)

pw215
2067
11
150
UP
pw214
2066
13
150
UP
/*Check pw details of the BFD. */

ZXR10#show bfd neighbors pw detail
---------------------------------------------------------------------------Pw Name: pw5809
Pw TTL:1
LocalAddr:--PeerAddr :--Local Discr:2083
Remote Discr:5
State:UP
Holddown(ms):300
BFD Type:PwType
Instance Name:bfd-pw5809
---------------------------------------------------------------------------Version:1
Dest UDP Port:3784
Final Bit:1
Local Diag:0
Demand Mode:0
Poll Bit: 0
MinTxInt:100
MinRxInt:100
Multiplier:3
Received MinTxInt:100
Received MinRxInt:100
Received Multiplier:3
Length:24
Min Echo Interval:0
Rx Count:51
Rx Interval (ms) min/max/avg:90
/90
/90
Tx Count:62
Tx Interval (ms) min/max/avg:75
/75
/75
Registered Protocols:INSTANCE
Uptime:0 day(s),0 hour(s),0 minute(s)
Control Plane Rcv Phy Interface Name:gei-0/0/0/3
---------------------------------------------------------------------------/*In normal situations, all BFD neighbors should be in "UP" status.
If they are not, check the configuration of BFD on both sides of
the equipment in the network. Check other BFD neighbor status
in the same way as described for the pw BFD.*/
3.2 Monthly Maintenance Items

3.2.1 Check Power Supply Redundancy
Purpose
This procedure describes how to check the power supply module redundancy to ensure
reliable device operation.
Inspection Items
Open the cabinet and verify that there is power supply module redundancy.
3-16
SJ-20140731105308-020|2014-10-20 (R1.0)
Reference Standard
Redundant equipment power supplies should be available.
3.2.2 Checking Basic Equipment Information

Purpose
This procedure describes how to check basic equipment information to ensure reliable
equipment operation.
Inspection Items
l
l
l
l
Check configuration files.

Check synchronization between the active MPU and the standby MPU.
Check version boot information.
Check remaining capacity of hard disks.
Reference Standards
l
Run the show running-config command to check the configuration file.

ZXR10#show running-config
!<mim>
!configuration saved at 13:10:46 Wed Jun 4 2014 by write txt
!configuration saved at 13:10:46 Wed Jun 4 2014 by write zdb
!last configuration change at 14:02:14 Wed Jun 4 2014 by who
!</mim>
!<port-request-info>
request interface ulei-0/0/0/2
!</port-request-info>
!<system-config>
hostname ZXR10
Current configurations must meet the configuration requirements.

Run the write command to save a new configuration
l
Run the show synchronization command to check synchronization between the active
MPU and the standby MPU.
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

==================================================================
==================================================================
3-17
SJ-20140731105308-020|2014-10-20 (R1.0)
LE
Location
Status
Sync-state
==================================================================
T_SC
MPU-0/10/0
Slave
Synchronized
-----------------------------------------------------------------T_SC
MPU-0/11/0
Master
Synchronized
------------------------------------------------------------------
Check the version boot information.
Run the show nvram command to check the version file location where the
equipment boots next time.
ZXR10#show nvram
imgfile-location
: local
mng-ip-address
: 192.168.0.1 255.255.255.0
boot-server
: 192.168.0.2
default-gateway
: 192.168.0.2
boot-username
: target
ftp-path
: \
mng-ipv6-address
: 192:168:6:0:0:0:0:3/64
boot-ipv6-server
: 190:0:0:0:0:0:0:1
def-ipv6-gateway
: 192:168:6:0:0:0:0:1
mng-ipv6-enable
: enable
boot-from
: ipv4-server
/*If the version file location is not "local", change it to "local". */

ZXR10#(config)#nvram imgfile-location local
In normal situations, the boot mode should be local. If it is not, run the nvram
imgfile-location local command in configuration mode and change it to "local".
Check whether the load mode of configuration is txt.

ZXR10#show load-mode
txt
/*If it is not, change the load mode to "txt". */

ZXR10(config)#load-mode txt
Due to changes in table structures among versions, if the load mode is zdb,
the configuration may be incompatible and cannot be loaded normally. The load
mode needs to be changed to txt.
l
Run the dir command to check the remaining capacity of hard disks.
ZXR10#dir
Directory of MPU-0/5/0: /datadisk0
6686008
KB total (5432736 KB free)
/*Delete old version files. Activated version files cannot be deleted. */

ZXR10(config)#product manage
3-18
SJ-20140731105308-020|2014-10-20 (R1.0)

ZXR10(config-pm)#install delete Base-1.21.0-10600
The remaining capacity should be more than 3 G. If it is less than 3 G, delete some
useless version files and fault record files.
3.2.3 Checking System Time

Purpose
This procedure describes how to check the system time to ensure that system time is the
same with the standard time.
Inspection Items
Check the system time.
Reference Standard
In normal situations, the system time should be consistent with the local standard time
(with the deviation of less than five minutes). If they are inconsistent, run the clock set
command to modify the time. If the system acquires the time from the NTP server, check
related configuration and status of the NTP.
ZXR10#show clock
05:39:12 UTC Wed Jun 4 2014
/*Modify the time if they are inconsistent. */

ZXR10#clock set 11:08:00 06-04-2014
/*Check the NTP configuration. */

ZXR10#show running-config ntp
!<ntp>
ntp enable
ntp master 4
ntp server 10.0.0.1 priority 1
ntp server 10.0.0.2 priority 2
ntp source ipv4 10.0.0.4
!</ntp>
/*Check the NTP status. The status should be synchronized. */

ZXR10#show ntp status
Clock is synchronized, stratum 4, reference is LOCAL
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
2**6 reference time is d74247e1.9be76c8b (03:13:37
Wed
Jun 11
2014 UTC)
clock offset is 0.00 msec, root delay is 0.00 msec

root dispersion is 0.01 msec, peer dispersion is 0.00 msec
3-19
SJ-20140731105308-020|2014-10-20 (R1.0)
3.2.4 Checking User Security Management

Purpose
This procedure describes how to check user security management configurations to
confirm system administrator identity.
Inspection Items
Check usernames and passwords.
Reference Standards
Run the show running-config adm-mgr command to check usernames and passwords.
It is suggested to set usernames and passwords as below:
l
l
Do not use simple words such as zte, zxr10 and who as usernames.
Set a user password. The length is no less than 6 bits. The password should contain at
least two of the following types: number, lowercase, uppercase and special character.
If the user passwords are not displayed with encryption, encrypt them.

ZXR10#show running-config adm-mgr
!<adm-mgr>
enable secret level 15 5 RcMLuUKvnFZX9kNAV6A/UA==
system-user
account-switch on accounting-template 2001
authorization-template 1
bind aaa-authorization-template 2001
local-privilege-level 15
$
authentication-template 1
bind aaa-authentication-template 2001
$
user-name who
bind authentication-template 1
bind authorization-template 1
password encrypted
e09a66ada5ddf9e2c17976f988fa508b43c2b6636096567d62fac3390409d8b2
$
$
!</adm-mgr>
3-20
SJ-20140731105308-020|2014-10-20 (R1.0)
3.2.5 Checking Equipment Interface Configuration

Purpose
This procedure describes how to check equipment interface configurations to ensure that
the interfaces are operating properly.
Inspection Items
l
l
Check the status information of all interfaces.

Check the interface configuration.
Reference Standards
l
Check the status information of all interfaces.

ZXR10#show ip interface brief
Interface
IP-Address
Mask
Admin Phy
Prot
gei-0/0/0/1
172.0.0.6
255.255.255.252 up
up
up
gei-0/0/0/2
172.0.0.9
255.255.255.252 up
up
up
gei-0/0/0/2.00000031
172.0.1.1
255.255.255.252 up
up
up
gei-0/0/0/2.00000100
172.0.0.29
255.255.255.252 up
up
up
gei-0/0/0/2.00001001
7.100.0.1
255.255.255.252 up
up
up
gei-0/0/0/3
unassigned
unassigned
up
up
up
gei-0/0/0/3.00000031
172.0.1.5
255.255.255.252 up
up
up
gei-0/0/0/3.00000032
192.168.1.5
255.255.255.252 up
up
up
gei-0/0/0/3.00004094
unassigned
unassigned
up
up
up
gei-0/0/0/4
unassigned
unassigned
up
down down
gei-0/0/0/5
unassigned
unassigned
down
down down
Check the interface configuration.

In normal situations, it is suggested to configure interface description for all in-service
interfaces by referring to related specifications. If an in-service interface is not
configured with interface description, configure the interface as soon as possible.
ZXR10#show running-config-interface gei-0/0/0/1
!<if-intf>
interface gei-0/0/0/1
description ZTE1 gei-0/0/0/1
mtu 9000
ip address 172.0.0.6 255.255.255.252
mpls mtu 9000
ipv6 enable
ipv6 address 240e:26:8800:1::6/127
no shutdown
$
!</if-intf>
!<ldp>
mpls ldp instance 1
3-21
SJ-20140731105308-020|2014-10-20 (R1.0)

interface gei-0/0/0/1
$
$
!</ldp>
3.2.6 Checking Service Operational Status

Purpose
Check the service operational status of the equipment to ensure normal service operation.
Service operational status is an important inspection item that is implemented in not only
daily maintenance but also monthly maintenance.
Inspection Items
l
l
l
l
l
l
l
l
l
Check
Check
Check
Check
Check
Check
Check
Check
Check
the
the
the
the
the
the
the
the
the
OSPF neighbor status.

IS-IS neighbor status.
BGP neighbor status.
route information.
MPLS IP status.
L3VPN status.
L2VPN status.
MPLS-TE status.
BFD status.
Reference Standards
For details, refer to 3.1.6 Checking Service Operational Status.
3.2.7 Checking Basic Equipment Configuration

Purpose
This procedure describes how to check the basic equipment configurations to ensure
reliable equipment operation.
Inspection Items
l
l
Save the configuration files.

Back up the configuration files.
Reference Standard
l
Save the current configuration files.

ZXR10#write
Write DB OK!
Building configuration...
3-22
SJ-20140731105308-020|2014-10-20 (R1.0)

..[OK].
Copy the current configuration files to the background FTP server by using the
management interface.
ZXR10#copy ftp vrf mng root: /sysdisk0/DATA0/startrun.dat
//169.1.113.7/startrun.dat@target:target
Start copying file
Copy file ok!!sended 448160 BYTEs!!
3.3 Quarterly Maintenance Items

3.3.1 Checking Cabinet Environment
Purpose
This procedure describes how to check cabinet environment to ensure that the cabinet
environment is in good condition.
Inspection Items
l
l
l
l
l
Check cabling status.

Check labels.
Check rack appearance.
Clean air filters and fan modules.
Check heat dissipation.
Reference Standards
l
l
Power cables and signal cables should be kept separately tidily in order.
It is recommended to use knife-shaped labels (easy to view information and can be
maintained for a long time). Verify that the labels are pasted firmly and the descriptions
on the labels are correct.
If a label does not meet the requirements, change the label.
For details of the requirements for pasting a label, refer to ZXR10 M6000-S hardware
installation guide.
l
l
Rack appearance should be in good condition. Blank filler panels should be installed
on empty slots.
Air filters and fans should be clean so that aeration and heat dissipation of the cabinet
door and the fan frame will not be affected.
3-23
SJ-20140731105308-020|2014-10-20 (R1.0)
3.3.2 Checking User Security Management

Purpose
This procedure describes how to check user security management to ensure secure
equipment operation environment.
Inspection Items
l
l
Change user passwords.

Change enable passwords.
Reference Standards
l
Change the user passwords.

It is recommended to change the user passwords every 3-6 months.
Set a password. The length is no shorter than 6 bits. The password should contain at
least two of the following types: number, lowercase, uppercase and special character.
/*Change the password of the zte user to NJZTE. */
ZXR10(config)#aaa-authentication-template 2001
ZXR10(config-aaa-authen-template)#aaa-authentication-type local
ZXR10(config-aaa-authen-template)#exit
ZXR10(config)#aaa-authorization-template 2001
ZXR10(config-aaa-author-template)#aaa-authorization-type local
ZXR10(config-aaa-author-template)#exit
ZXR10(config)#system-user
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)#user-name zte
ZXR10(config-system-user-username)#bind authentication-template 1
ZXR10(config-system-user-username)#bind authorization-templat 1
ZXR10(config-system-user-username)#password NJZTE
ZXR10(config-system-user-username)#exit
ZXR10(config-system-user)#exit
Change the system passwords of all secret levels.

It is recommended to use enable passwords that are different from the user
passwords.
3-24
SJ-20140731105308-020|2014-10-20 (R1.0)
Set an enable password. The length is no less than 6 bits. The passwords should
contain at least two of the following types: number, lowercase, uppercase and special
character.
ZXR10(config)#enable secret level 2 222
ZXR10(config)#enable secret level 3 333
ZXR10(config)#enable secret level 15 zxr10
3.3.3 Checking Equipment Basic Configuration

Purpose
This procedure describes how to check equipment basic configurations to ensure reliable
Inspection Items
Check redundancy configurations on the equipment.
Reference Standard
In normal situations, the system configuration should meet user requirements. Delete
useless configurations.
ZXR10#show running-config
!<mim>
!configuration saved at 13:10:46 Wed Jun 4 2014 by write txt
!configuration saved at 13:10:46 Wed Jun 4 2014 by write zdb
!last configuration change at 14:02:14 Wed Jun 4 2014 by who
!</mim>
!<port-request-info>
!</port-request-info>
!<system-config>
hostname ZXR10
3-25
SJ-20140731105308-020|2014-10-20 (R1.0)
3.4 Yearly Maintenance Items

3.4.1 Checking Equipment Room Environment
Purpose
This procedure describes how to check the equipment room environment to ensure reliable
Inspection Items
l
l
l
l
l
Check
Check
Check
Check
Check
fire protection.
measures against theft.
equipment grounding.
power supply redundancy.
board redundancy.
Reference Standards
l
Check the cabinet, rack and cable tray.

There should not be any hidden fire alarm at any place in the equipment room. The
fire protection facilities in the equipment room should be in good condition and can be
used.
Check the doors, windows and security nets of the equipment room.
In normal situations, all the doors, windows and security nets of the equipment room
should be in good condition.
Use a multimeter to measure the grounding resistance.

In normal situation, the grounding resistance should be less than 1 .
Check the power supply system redundancy in the equipment room.

There should be UPS in the equipment room. In the core equipment room, there
should be storage batteries.
Check the storeroom.

For the important components on the equipments, such as MPU/SRU, SFU, PFU and
PIU, there should be spare ones.
If spare components are insufficient, contact ZTE technical support.
3.4.2 Checking Cabinet Environment

Purpose
This procedure describes how to check cabinet environment and ensure that the cabinet
environment is normal.
3-26
SJ-20140731105308-020|2014-10-20 (R1.0)
Inspection Items
Verify that the equipment is clean.
Reference Standard
Verify that air filters, fans, boards, optical interfaces, and tail fiber connectors are clean.
Air filters, fans, boards, optical interfaces, and tail fiber connectors should be cleaned
periodically.
If there is too much dust, choose an appropriate time to do cleaning by using special tools.
3-27
SJ-20140731105308-020|2014-10-20 (R1.0)
3-28
SJ-20140731105308-020|2014-10-20 (R1.0)
Tables
Table 1-1 Routine Maintenance List .......................................................................... 1-3
Table 3-1 Temperature and Humidity Requirements.................................................. 3-2
I
SJ-20140731105308-020|2014-10-20 (R1.0)
Tables
II
SJ-20140731105308-020|2014-10-20 (R1.0)
Glossary
AS
- Autonomous System
BFD
- Bidirectional Forwarding Detection
BGP
- Border Gateway Protocol
CPU
- Central Processing Unit
CRC
- Cyclic Redundancy Check
FTP
- File Transfer Protocol
IP
- Internet Protocol
IS-IS
- Intermediate System-to-Intermediate System
L2VPN
- Layer 2 Virtual Private Network
L3VPN
- Layer 3 Virtual Private Network
LDP
- Label Distribution Protocol
LSP
- Label Switched Path
MP-BGP
- Multiprotocol BGP
MPBGP
- Multi-Protocol Border Gateway Protocol
MPLS
- Multiprotocol Label Switching
MPLS-TE
- Multi-Protocol Label Switching-TE
MPU
- Management Process Unit
III
SJ-20140731105308-020|2014-10-20 (R1.0)
NTP
- Network Time Protocol
OSPF
- Open Shortest Path First
PFU
- Packet Forwarding Unit
PIU
- Physical line Interface Unit
SFU
- Switch Fabric Unit
SRU
- Switching and Routing Unit
UPS
- Uninterruptible Power Supply
VRF
- Virtual Route Forwarding
VRRP
- Virtual Router Redundancy Protocol
IV
SJ-20140731105308-020|2014-10-20 (R1.0)

SJ-20140731105308-020-ZXR10 M6000-S (V3.00.10) Carrier-Class Router Routine Maintenance - 608079

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SJ-20140731105308-020-ZXR10 M6000-S (V3.00.10) Carrier-Class Router Routine Maintenance - 608079

Enviado por

Direitos autorais:

Formatos disponíveis

ZXR10 M6000-S

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20140731105308-020

ZTE Proprietary and Confidential

Chapter 2 Periodic Inspection of Equipment Hardware and

Chapter 3 Scheduled Maintenance Items................................................. 3-1

ZTE Proprietary and Confidential

3.2.6 Checking Service Operational Status....................................................... 3-22

ZTE Proprietary and Confidential

About This Manual

Network planning engineers

What Is in This Manual

tions of routine maintenance, and categories of maintenance items.

Chapter 2, Periodic Inspection of Equipment

Describes items of periodic inspection of equipment

Hardware and Software Statuses

hardware and software statuses.

Chapter 3, Scheduled Maintenance Items

nance, quarterly maintenance, and yearly maintenance.

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

1.2 Principles and Precautions

Machine Room Management

ZTE Proprietary and Confidential

ZXR10 M6000-S Routine Maintenance

Make complete equipment room maintenance rules to regulate maintenance

Network management passwords must be set by levels, managed strictly, and

ZTE Proprietary and Confidential

Chapter 1 Routine Maintenance Overview

Keep necessary software and materials handy.

1.3 Introduction to Routine Maintenance Items

Daily maintenance performed every day

Routine maintenance items provide basic references and suggestions on daily

Checking the equipment room environment, including temperature and humidity

ZTE Proprietary and Confidential

ZXR10 M6000-S Routine Maintenance

Checking power supply redundancy

Checking cabinet environment, including cabling status, labels, rack appearance,

Checking equipment room environment, including fire protection condition,

anti-theft condition, equipment grounding, power supply redundancy, and board

ZTE Proprietary and Confidential

2.1 Checking Equipment Software Status

2.1.1 Checking the OSPF Status

OSPF Router with ID (20.0.0.3) (Process ID 32)

OSPF Router with ID (10.0.0.3) (Process ID 31)

ZTE Proprietary and Confidential

ZXR10 M6000-S Routine Maintenance

2. Check the OSPF database information.

OSPF Router with ID (20.0.0.3) (Process ID 32)

Router Link States (Area 0.0.0.1)

3. Check the OSPF configuration information.

2.1.2 Checking the IS-IS Status

ZTE Proprietary and Confidential

Chapter 2 Periodic Inspection of Equipment Hardware and Software Statuses

2. Check the IS-IS configuration information.

2.1.3 Checking the BGP Status

If it is not, check the BGP

ZTE Proprietary and Confidential

ZXR10 M6000-S Routine Maintenance

2. Check the MP-BGP neighbor status.

3. Check the BGP configuration information, especially the AS configuration information.

: local /local indicates that the boot mode is set to "local"./