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.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2014-10-20
First edition.
SJ-20140731105308-020|2014-10-20 (R1.0)
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
I
SJ-20140731105308-020|2014-10-20 (R1.0)
Tables .............................................................................................................. I
Glossary ........................................................................................................ III
II
SJ-20140731105308-020|2014-10-20 (R1.0)
Intended Audience
This manual is intended for:
l
l
l
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)
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.
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)
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
l
l
SJ-20140731105308-020|2014-10-20 (R1.0)
l
l
l
l
l
l
Maintenance List
Period
Daily
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
Quarterly
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
maintenance
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
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
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)
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
End of Steps
Steps
1. Check the IS-IS neighbor status.
2-2
SJ-20140731105308-020|2014-10-20 (R1.0)
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
End of Steps
Steps
1. Check the BGP neighbor status.
The BGP neighbor status should be Established.
configuration.
2-3
SJ-20140731105308-020|2014-10-20 (R1.0)
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
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
End of Steps
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)
End of Steps
Steps
1. Run the show nvram command to check whether the boot mode of the equipment is
"local".
ZXR10#show nvram
imgfile-location
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
End of Steps
2-5
SJ-20140731105308-020|2014-10-20 (R1.0)
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
Power type
: DC
Division numbers
: 664.00W
: 1
: 1+1
Supply
Phy
Power
Com
Run
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
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 speed mode: auto
Fan
name: FAN
Index
Status
work normally
73%
Speed
work normally
69%
work normally
73%
work normally
70%
Group 2: online
Fan speed mode: auto
Fan
name: FAN
Index
Status
Speed
work normally
74%
work normally
76%
work normally
74%
work normally
75%
End of Steps
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
Addr
Status
Minor
Major
Fatal
Temper
-----------------------------------------------------
[shelf 0, slot 0]
BoardType I2C Addr
Status
----------------------------------------------------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)
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
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
SSC
N/A
CPU(5s)
CPU(1m)
CPU(5m)
Peak
PhyMem
FreeMem
Mem
================================================================================
2-9
SJ-20140731105308-020|2014-10-20 (R1.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
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
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
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
2-10
SJ-20140731105308-020|2014-10-20 (R1.0)
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
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
3-1
SJ-20140731105308-020|2014-10-20 (R1.0)
Reference Standard
Temperature in the
equipment room
Humidity in the
equipment room
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.
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.
Inspection Items
l
l
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)
Inspection Items
l
l
l
l
Check
Check
Check
Check
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.
The following is a result example:
ZXR10#show logging alarm
An alarm 240202 ID 103 level 5 occurred at 18:46:27 06-03-2014 sent by
ZXR10 M6000-S MPU-0/3/0
%L2VPN% PW status
VtyNo: vty0
HostName: ZXR10
UserName: who
Result: cease-data
UserLevel: 15
IP: 168.1.40.254
CMDLevel: 2
3-3
SJ-20140731105308-020|2014-10-20 (R1.0)
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.
The following is a result example:
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
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
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 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 speed mode: auto
Fan
name: FAN
Index
Status
work normally
73%
Speed
work normally
69%
work normally
73%
work normally
70%
Group 2: online
Fan speed mode: auto
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
Power type
: DC
Division numbers
: 664.00W
: 1
: 1+1
Supply
Phy
Power
Com
Run
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
Standby MPU/SRU
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.
The following is a result example:
ZXR10#show processor
================================================================================
================================================================================
Character: CPU current character in system
MSC
SSC
N/A
CPU(5s)
CPU(1m)
CPU(5m)
Peak
PhyMem
FreeMem
Mem
================================================================================
================================================================================
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.
The following is a result example:
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
BW 1000000 Kbps
Duplex full
/*Working
Negotiation auto
SD-FER disable
ARP type ARP
1Pps
0Pps
219Bps
peak time
2014-05-28 14:20:40
output
115Bps
peak time
2014-05-28 14:05:30
output 0%
3-8
SJ-20140731105308-020|2014-10-20 (R1.0)
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
Inspection Items
l
l
l
l
l
l
Check
Check
Check
Check
Check
Check
SJ-20140731105308-020|2014-10-20 (R1.0)
l
l
l
Reference Standards
l
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
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
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
Gw: Gateway,
Pri: Priority;
3-10
SJ-20140731105308-020|2014-10-20 (R1.0)
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
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
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
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
3-12
SJ-20140731105308-020|2014-10-20 (R1.0)
Gw: Gateway,
Pri: Priority;
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
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
Outgoing
Prefix or
Outgoing
Next Hop
M/S
3-13
SJ-20140731105308-020|2014-10-20 (R1.0)
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
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. */
Next Hop
Metric
LocPrf
InTag
Path
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 ?
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 ?
Next Hop
Metric
LocPrf
Tag
Path
10.0.0.3
100
212994
3-14
SJ-20140731105308-020|2014-10-20 (R1.0)
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
7.0.0.0/26
10.0.0.3
100
212993
7.0.0.7/32
10.0.0.3
100
212993
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. */
running
RSVP Process:
running
Forwarding:
enabled
TUNNEL NAME
DESTINATION
UP IF
DOWN IF
STATE/PROT
tunnel_1
10.0.0.2
up/down
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)
2067
11
150
UP
pw214
2066
13
150
UP
Remote Discr:5
State:UP
Holddown(ms):300
BFD Type:PwType
Instance Name:bfd-pw5809
---------------------------------------------------------------------------Version:1
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
Rx Count:51
/90
/90
Tx Count:62
/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.*/
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.
Inspection Items
l
l
l
l
Reference Standards
l
Run the show synchronization command to check synchronization between the active
MPU and the standby MPU.
ZXR10#show synchronization
==================================================================
==================================================================
LE
Location
Status
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
------------------------------------------------------------------
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
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".
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
3-18
SJ-20140731105308-020|2014-10-20 (R1.0)
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.
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
Wed
Jun 11
2014 UTC)
3-19
SJ-20140731105308-020|2014-10-20 (R1.0)
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.
3-20
SJ-20140731105308-020|2014-10-20 (R1.0)
Inspection Items
l
l
Reference Standards
l
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
3-21
SJ-20140731105308-020|2014-10-20 (R1.0)
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
Reference Standards
For details, refer to 3.1.6 Checking Service Operational Status.
Inspection Items
l
l
Reference Standard
l
3-22
SJ-20140731105308-020|2014-10-20 (R1.0)
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!!
Inspection Items
l
l
l
l
l
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)
Inspection Items
l
l
Reference Standards
l
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.
The following is a result example:
ZXR10(config)#enable secret level 2 222
ZXR10(config)#enable secret level 3 333
ZXR10(config)#enable secret level 15 zxr10
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>
request interface ulei-0/0/0/2
request interface ulei-0/0/0/3
!</port-request-info>
!<system-config>
hostname ZXR10
3-25
SJ-20140731105308-020|2014-10-20 (R1.0)
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 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.
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)