Routine Maintenance and

Troubleshooting
of ZXR10 M6000
V1.1
Objectives

 To know the routine maintenance process of

M6000
 To know the troubleshooting process of M6000
Contents

 Routine Maintenance Process of M6000

 Troubleshooting Process
 Routine Maintenance Process of ZXR10

Check the working

status of the device

Check whether
there is any alarm

Maintenance record
management

Software version
management

© ZTE Corporation. All rights reserved

 Check the Working Status of the Device

 Check the working status of the device

 Check whether the router control module indicators are
working normally. In normal cases, the OK or RUN light is ON.
 Check whether the router board indicators are working
normally. In normal cases, the link connection indicator is
always ON, and the data sending/receiving indicator is
blinking. You can refer to the User Manual or the
Maintenance Manual for details of different situations.
 Check whether the Console or management interface can be
used normally.
 Check whether the router power supply and the fan are
working normally, and check whether the router temperature
is normal.

© ZTE Corporation. All rights reserved

 Check the Status of the Ports or Interfaces

 Check the status of the interfaces on the device.

ZXR10# show ip interface

© ZTE Corporation. All rights reserved

 Check the Communication Status between the
Router and the Connected Devices

 Log on the local router via the hyper terminal or TELNET. Use the "ping"
command to test the directly-connected network segments so as to check the
connectivity. In normal cases, you can ping through the host in the directly-
connected network segment, unless the host has some firewall running on it.
 Check whether the items in the routing table are normal. In normal cases, the
routing table should contain all the necessary items.

 You can use the following command to check the routing table on the device:

ZXR10# show ip forwarding route

© ZTE Corporation. All rights reserved

 Check Whether the Related Services are Normal

 The device may be connected with other devices, such

as the ATM devices, the ADSL devices, the video
conference devices, or the SWITCH. So it is necessary
to check whether the related services are normal, such
as the internet surfing service, and the video
conference service.

© ZTE Corporation. All rights reserved

 Set the System Log Function on the Device and
Regularly Check the Log Record
 Cache the system logs on the device.
 Limited by the system memory volume, this method
can record only few logs.

© ZTE Corporation. All rights reserved

 Set and View the System Logs
 Under the Global Configure mode, you can use the following commands to set
the system log function:

zte(config)# logging on
zte(config)# logging level 5
zte(config)# logging buffer 500
 Under the Enable mode, you can use the following command to view the log
record:
zte# show logging alarm

 Save the system logs on the NMS server

This operation is not limited by the router memory volume. You can record all the
logs of the router if there is enough hard disk space.

© ZTE Corporation. All rights reserved

 Set and View the System Logs

 Under the Global Configure mode, you can use the following commands to set
the system log function:
ZXR10(config)#syslog level WARNINGS
ZXR10(config)#syslog-server facility syslog
ZXR10(config)#syslog-server host 1.1.1.1

 The router will send the log information to the server via FTP in real-time manner.

© ZTE Corporation. All rights reserved

Contents

 Routine Maintenance Process of M6000

 Troubleshooting Process
 Troubleshooting Process

Troubleshooting process for the

"all services blocked" failure

Troubleshooting process for

the "some services aborted" failure

© ZTE Corporation. All rights reserved

 Troubleshooting Process for the "All Services
Blocked" Failure
 The "all services blocked" failure may be caused by
that the uplink port is faulty, the uplink interface is
faulty, the physical connection (including the
transmission link) is faulty, or the control module is
suspended.
 In order to analyze the cause of the failure, you must
not restart the router immediately when the failure
occurs.

© ZTE Corporation. All rights reserved

 Troubleshooting Process for the "All Services
Blocked" Failure
 Usually, you can take the following steps to handle this failure:
 Check whether the uplink port indicator and the data sending/receiving
indicator are normal.
 If not, you need to find out whether the device is faulty or the physical
connection is faulty. A frequently used method is to test the self loopback of
the optical interface or connect the PC directly to the electronic interface. If
the test result is normal, it means the physical connection is faulty or the peer
end device is faulty.
 Check whether the data link is normal
 If the uplink port indicator is normal, you need to log on the router via the
hyper terminal or Telnet to do further tests. After logging on the router, you
can ping the nodes from-near-to-far to check whether the local router can
get to the internet smoothly.

© ZTE Corporation. All rights reserved

 Troubleshooting Process for the "All Services
Blocked" Failure
 Check whether the local router has uplink route and whether there is
returning route from the peer end router
 You can check the routing table of the local router to see whether it has any
uplink route. In order to find out whether there is any returning route from
the peer end router, you can take the following method: from the PC
connected with the local router, ping the uplink port of the local router, and
then ping the peer end router interface. If the former "ping" command gets
through and the latter does not, it means the peer end router doesn't has the
returning route to the local router, and you need to conduct troubleshooting
for the peer end router.

© ZTE Corporation. All rights reserved

 Troubleshooting Process for the "All Services
Blocked" Failure
 Restart the router when the operation system of the router is down.
 If you can not log on the router via the hyper terminal and Telnet, it may be
caused by that the operation system of the router is down. Then you should
restart the router.

© ZTE Corporation. All rights reserved

 Troubleshooting Process for the "Some Services
Aborted" Failure
 When some of the services are aborted, you can take the
following steps to diagnose and shoot the failure:
 Check whether the ports and the physical connection are normal;
 Check whether the data link layer is normal;
 Check whether the local router has the routing information to the network
segment of the user who suffers from "service aborted". Check whether the
default gateway or the routing configurations at the user side are correct.
 If the user can ping through the local router but cannot visit it, you need to
check whether the local router has the returning route from the related
network segment.
 If the other users in the same network segment do not meet with the failure
of "service aborted", you should check whether the PC and other terminals of
the user are working normally.

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

 You can conduct the troubleshooting for the

emergent failure according to the following
instructions.
 During the process, you should make a record for the
operation log so as to help analyzing the failure.

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

1. Check the interface status

 Related commands:

ZXR10#show interface

 Check whether all the related interfaces are in normal physical

status. if the protocol status is "UP", it means the interface is
normal. If the protocol status is "DOWN", you need to check the
related physical connection.

ZXR10#show ip interface brief

 Check whether the related interface IP is correct. The interface IP

may be lost due to improper operations.

© ZTE Corporation. All rights reserved

 View the Port Information
ZXR10#show interface fei-0/2/0/1
fei-0/2/0/1 is up, line protocol is up
Description is none
Hardware is Fast Ethernet, address is 00e0.d021.0203
Internet address is 11.1.1.1/24
IP MTU 1500 bytes
MTU 1600 bytes BW 100000 Kbits
Loopback-Cancel
Duplex full
Negotiation-Auto
ARP type ARP
ARP Timeout 04:00:00
Last Clear Time : 2010-01-09 13:54:39 Last Refresh Time: 2010-01-09 17:58:00
120s input rate : 3092Bps 32Pps
120s output rate: 92Bps 1Pps
Intf utilization: input 0% output 0%
In_DropEvents 0 In_Bytes 44225986
In_Packets 489462 In_Unicast 0
In_Broadcasts 446039 In_Multicasts 38647
In_CRC-ERROR 0 In_Undersize 0
In_Oversize 0 In_Fragments 0
In_Jabbers 0 In_Collisions 0
In_64B 357417 In_65-127B 68249
…….

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

1. Check the interface status

ZXR10#ping <the peer end interface IP>

 You can use the "ping" command to check whether the IP layer
of the interface is normal. If you can ping through the peer end
interface IP and no packet is lost, it means the interface has no
problem.

ZXR10#show arp

 You can use the "show arp" command to check whether

the current interface has resolved the IP address of the
peer end interface. If the peer end device has error
configuration, the device cannot resolve the peer end arp
record even if the physical connection is normal.

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

2. Check the routing status

 Related commands:

ZXR10#show ip forwarding route

ZXR10#show ip ospf neighbor
ZXR10#show ip bgp neighbor
ZXR10#show running-config
 When the configuration and status of the interface are normal, check
the routing table to see whether the routing status is normal. If the
routing is abnormal, you need to check the current routing protocol
to see whether the OSPF neighbor and the BGP neighbor status are
normal.
 If the routing protocol is abnormal, you can compare the
configuration of the routing protocol (including the static routing)
with the backup configuration. The routing protocol configuration
may be lost due to improper operations.

© ZTE Corporation. All rights reserved

 View the Routing Table

R1# show ip forwarding route

IPv4 Routing Table:
Dest Mask Gw Interface Owner pri metric
1.1.1.1 255.255.255.255 11.1.1.1 fei-0/1/0/1 static 1 0
1.1.1.2 255.255.255.255 1.1.1.2 loopback1 address 0 0
1.1.1.3 255.255.255.255 13.1.1.2 fei-0/2/0/1 static 1 0
10.1.1.0 255.255.255.0 11.1.1.1 fei-0/1/0/1 bgp 20 33
11.1.1.0 255.255.255.252 11.1.1.2 fei-0/1/0/1 direct 0 0
11.1.1.2 255.255.255.255 11.1.1.2 fei-0/1/0/1 address 0 0
12.1.1.0 255.255.255.252 13.1.1.2 fei-0/2/0/1 bgp 200 0
13.1.1.0 255.255.255.252 13.1.1.1 fei-0/2/0/1 direct 0 0
13.1.1.1 255.255.255.255 13.1.1.1 fei-0/2/0/1 address 0 0
14.1.1.0 255.255.255.252 13.1.1.2 fei-0/2/0/1 bgp 200 0
20.1.1.0 255.255.255.0 13.1.1.2 fei-0/2/0/1 bgp 200 122
192.168.0.0 255.255.252.0 11.1.1.1 fei-0/1/0/1 bgp 20 33
192.168.0.0 255.255.255.0 11.1.1.1 fei-0/1/0/1 bgp 20 33
192.168.1.0 255.255.255.0 11.1.1.1 fei-0/1/0/1 bgp 20 33
192.168.2.0 255.255.255.0 11.1.1.1 fei-0/1/0/1 bgp 20 33
192.168.3.0 255.255.255.0 11.1.1.1 fei-0/1/0/1 bgp 20 33

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

3. Check the configuration file

 Related commands:

ZXR10#show running-config
– You can compare the current configuration file with the normal backup
configuration file to see whether it has any change The configuration may be
lost due to improper operations. The current service may be affected due to
improper configurations. You must be sure the current configurations are
correct before you start to seek other causes.

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

4. Check the current CPU utilization

 Related commands:

ZXR10# show processor

Check the utilization ratio of each CPU in the current system.

If the CPU utilization is very high within 5 seconds, it means the system is
abnormal. It is notable that the abnormal utilization of the router CPU is
probably caused by abnormal user data traffic, such as the virus. You need to
check whether the anti-virus ACL configuration of the device is correct.

© ZTE Corporation. All rights reserved

 View the Maintenance Commands

 System Info - CPU Utilization

ZXR10#show processor
Character CPU(5s) CPU(1m) CPU(5m) Peak PhyMem FreeMem Mem
===============================================================
===========
PFU-0/0/0 N/A 16% 16% 18% 22% 2048 503 75.439%
--------------------------------------------------------------------------
PFU-0/3/0 N/A 13% 13% 16% 16% 2048 507 75.244%
--------------------------------------------------------------------------
PFU-0/5/0 N/A 13% 13% 15% 16% 2048 512 75.000%
--------------------------------------------------------------------------
PFU-0/7/0 N/A 9% 19% 19% 99% 2048 1321 35.498%
--------------------------------------------------------------------------
SFU-0/9/0 N/A 20% 20% 20% 28% 256 74 71.094%
--------------------------------------------------------------------------
MPU-0/11/0(M) N/A 23% 24% 27% 30% 4096 1660 59.473%
--------------------------------------------------------------------------
ESU-0/11/0 N/A 32% 32% 33% 38% 256 65 74.609%
--------------------------------------------------------------------------
ADU-0/13/0 N/A 11% 11% 11% 25% 256 114 55.469%

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

 5. Check the system version information

 Related commands:

ZXR10#show version

 1) Check the current version information. You may need to provide the version of
the current system.
 2) Check the runtime of the current system. The runtime of the system may be
useful for analyzing the system failure.

© ZTE Corporation. All rights reserved

 System Info - Query the Version

ZXR10#show version
ZXR10 M6000-16
ZTE ZXR10 Software, Version: M6000 1.1.0，Release software
Copyright (c) 2009 by ZTE Corporation.
Build on 2009/08/03 16:18:00
System image file is < sysdisk0: verset/ M6k_10_1.1.0.set > ,
file size is 314,572,800 Bytes
System image is loaded from net
System uptime is 10 days, 10 hours, 23 minutes

© ZTE Corporation. All rights reserved

 Emergency Troubleshooting Procedure

6. Check other information

 Related commands:

ZXR10#show logging alarm

– Check the alarms of the system. The system alarm log may contain
information about the failure, which is useful for analyzing the cause
of the failure.

ZXR10#show logfile

– You can use the "show logfile" command to view the recorded
operation information and check whether there is any improper
operation.
ZXR10#show interface
– The "Show interface" command can be used to check the current
interface status, as well as the related statistics of the interface. The
related statistics can be used to analyze the current network traffic.

© ZTE Corporation. All rights reserved

 View the Port Information
ZXR10#show interface fei-0/2/0/1
fei-0/2/0/1 is up, line protocol is up
Description is none
Hardware is Fast Ethernet, address is 00e0.d021.0203
Internet address is 11.1.1.1/24
IP MTU 1500 bytes
MTU 1600 bytes BW 100000 Kbits
Loopback-Cancel
Duplex full
Negotiation-Auto
ARP type ARP
ARP Timeout 04:00:00
Last Clear Time : 2010-01-09 13:54:39 Last Refresh Time: 2010-01-09 17:58:00
120s input rate : 3092Bps 32Pps
120s output rate: 92Bps 1Pps
Intf utilization: input 0% output 0%
In_DropEvents 0 In_Bytes 44225986
In_Packets 489462 In_Unicast 0
In_Broadcasts 446039 In_Multicasts 38647
In_CRC-ERROR 0 In_Undersize 0
In_Oversize 0 In_Fragments 0
In_Jabbers 0 In_Collisions 0
In_64B 357417 In_65-127B 68249
…….

© ZTE Corporation. All rights reserved