zxdsl 9806h - donbassmedia.net.ua

Transcription

ZXDSL 9806H
ZTE Broadband Universal Access System
Troubleshooting Manual
Version 2.1
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION
Copyright © 2010 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
1.0
30/09/2009
First version
1.1
15/05/2010
Update boards information
Serial Number: sjzl20095518
Contents
Preface.............................................................. I
Troubleshooting Overview ................................1
Safety Instruction........................................................... 1
Symbol Instructions ........................................................ 1
Troubleshooting Scope .................................................... 2
Requirements for Maintenance Engineers ........................... 3
Tools and Meters ............................................................ 3
Get In Touch .................................................................. 4
Troubleshooting Flow and Methods ...................5
Troubleshooting Flow ...................................................... 5
Common Troubleshooting Methods .................................... 6
Fault Classification .......................................................... 7
ADSL/ADSL2+ Service Faults ............................9
ADSL/ADSL2+ Basic Information ...................................... 9
Introduction............................................................... 9
Technology Implementation ......................................... 9
Information Collection ................................................10
Potential Result .............................................................10
Fault Location ...............................................................10
Fault Troubleshooting Flow ..............................................11
User Modem Check ....................................................12
User-side Software and Hardware Configuration
Check ..............................................................13
External Line Check ...................................................13
Port Status Check ......................................................15
Data Configuration Check ...........................................16
Upper-layer Equipment Data Configuration Check ..........17
Fault Handling...............................................................17
Unable to Make a Call Or Access Internet ......................17
Able to Make a Call, But Unable To Access Internet .........18
Internet Access at Low Speed .....................................19
Confidential and Proprietary Information of ZTE CORPORATION
I
ZXDSL 9806H Troubleshooting Manual
Unstable Internet Access with Frequent Disconnections ................................................................20
Troubleshooting Cases....................................................20
Frequent Drops .........................................................20
Modem is Disabled While Calling ..................................20
Low Access Rate Because of Subscriber Line
Problem ...........................................................21
Electrical Wire Interference Causes Modem
Disconnection ...................................................21
Normal Dialup, But Wrong User Name and Password
Prompt.............................................................21
Website Unaccessible After Successful Dialup ................22
Modem Link Established at Low Rate ............................22
Unsuccessful PPPoE Authentication...............................22
PPPoE Authentication Successful, But Website
Unaccessible .....................................................23
Low Speed Internet Access with Frequent
Disconnections ..................................................23
Packet Loss...............................................................23
VDSL2 Service Faults....................................... 25
VDSL2 Basic Information ................................................25
Introduction..............................................................25
Technology Implementation ........................................25
Fault Location ...............................................................27
User Modem Check ....................................................28
User-side Software and Hardware Configuration
Check ..............................................................29
External Line Check ...................................................29
Port Status Check ......................................................31
Data Configuration Check ...........................................32
VoIP Service Faults ......................................... 35
VoIP Basic Information ...................................................35
Introduction..............................................................35
II
Fault Location ...............................................................36
User Phone Check......................................................38
Lines Check ..............................................................39
User Port Running Status Check ..................................40
Equipment Running Status Check ................................41
RTP Resource Data Configuration Check........................42
User Service Data Configuration Check .........................42
H.248 Link Status Check ............................................43
SS Data Configuration Check.......................................43
Fault Handling...............................................................44
No Dialing Tone After Hook-Off ....................................44
Busy Tone When Hook-Off ..........................................44
Busy Tone When Dialing ............................................44
Unreliable Calling Connection ......................................45
Call Drop ..................................................................45
Noise in Call..............................................................45
Unable to Hear Calling Party........................................46
Abnormal H.248 Link .................................................46
No Number Display Because of Splitter .........................47
Unsuccessful Fax Service ............................................47
Hearing SIT Tone After Dialup .....................................47
Multicast Service Faults................................... 49
Multicast Basic Information .............................................49
Introduction..............................................................49
Fault Location ...............................................................51
STB Check ................................................................52
User Port Service Data Configuration Check ..................52
Multicast Data Configurations Check.............................52
Multicast Programme Configuration Check.....................53
User Cannot Watch Video ...........................................53
Static User and DHCP User Cannot Receive IPTV
Service ............................................................53
III
System Faults.................................................. 55
Information Collection ....................................................55
Equipment Working Environment Check........................57
Hardware Running Status Check ..................................57
Fault Handling...............................................................59
Fails to View Message Through HyperTerminal ...............59
Startup Failure after Version Update.............................59
ISP Chip Works Abnormally.........................................59
Narrowband Card Offline ............................................60
Broadband Card Offline ..............................................60
NM Faults ........................................................ 61
NM Basic Information .....................................................61
NM Installation and Configuration Requirements ............61
Operating System and Database..................................62
NM Server and Client Configuration in case of Multiple
IPs ..................................................................62
NMS and SQL Server 2005 Installation in Window
2003................................................................63
Mysql Installation ......................................................64
SUN + ORACLE Environment .......................................65
Basic NMS Installation and Configuration..............65
NMS Start-up in UNIX........................................66
Problems Related to Oracle Installation ................66
SID Configured in Oracle Inconsistent with
NMS .....................................................67
Solaris Commands ............................................68
Fault Location ...............................................................70
NMS Fault Troubleshooting Flow.......................................71
NM Environment Check ..............................................71
NM Server Operating System Configuration Check..........73
Database System Running Check .................................74
Logic Connection between NM and Database .................74
NM Basic Information Configuration Check ....................74
NM System Right Configuration Check ..........................75
NE SNMP Configuration Check .....................................75
NM Fault Handling .........................................................75
IV
Unable to Ping In-band NM .........................................75
Data and Version Upload/Download Unsuccessful ...........76
NMS Fails to Receive NE Alarm Messages ......................76
Unable To Start Client ................................................77
NM Server Startup Failure...........................................77
Figures ............................................................ 79
Tables ............................................................. 81
Index .............................................................. 83
Glossary .......................................................... 85
V
This page is intentionally blank.
VI
Preface
Purpose
This manual provides the methods for troubleshooting on the
ZXDSL 9806H (V2.1) ZTE Broadband Universal Access System.
Intended
Audience
This manual is intended for engineers and technicians who perform
operation and maintenance activities on the ZXDSL 9806H (V2.1)
ZTE Broadband Universal Access System.
Prerequisite Skill
and Knowledge
To use this document effectively, users should have a basic concept
of xDSL technologies, telecommunications technology, and Access
Network.
What Is in This
Manual
Related
Documentation
This manual contains the following chapters:
Chapter
Summary
Chapter 1,
Troubleshooting
Overview
Introduces troubleshooting scope, safety
instruction and symbols.
Chapter 2,
Troubleshooting
Flow and Methods
Describes troubleshooting flow and methods.
Chapter 3,
ADSL/ADSL2+
Service Faults
Describes ADSL/ADSL2+ service faults
troubleshooting and common faults handling.
Chapter 4, VDSL2
Service Faults
Describes VDSL2 service faults troubleshooting
and common faults handling.
Chapter 5, VoIP
Service Faults
Describes VoIP service faults troubleshooting
and common faults handling.
Chapter 6, Multicast
Service Faults
Describes multicast service faults
troubleshooting and common faults handling.
Chapter 7, System
Faults
Describes system faults troubleshooting and
common faults handling.
Chapter 8, NM
Faults
Describes NM faults troubleshooting and
common faults handling.
The following documentation is related to this manual:
�
ZXDSL 9806H (V2.1) ZTE Broadband Universal Access System
Documentation Guide
�
ZXDSL 9806H (V2.1) ZTE Broadband Universal Access Product
Information
�
Feature Description
�
Hardware Description
�
Troubleshooting Manual
I
How to Get in
Touch
�
Routine Maintenance
�
Version Update
�
Network Management User Manual
�
Configuration Manual (CLI)
�
Configuration Manual (NetNumen)
�
Command Manual (Volume I)
�
Command Manual (Volume II)
�
Command Manual (Volume III)
The following sections provide information on how to obtain support for the documentation and the software.
If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at [email protected]. You can also call our customer support center
at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality and
usefulness of this document. For further questions, comments, or
suggestions on the documentation, you can contact us by e-mail
at [email protected]; or you can fax your comments and suggestions to (86) 755 26772236. You can also browse our website
at http://support.zte.com.cn, which contains various interesting
subjects like documentation, knowledge base, forum and service
request.
Declaration of
RoHS Compliance
To minimize the environmental impact and take more responsibility to the earth we live, this document shall serve as formal
declaration that manufactured by ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European Parliament
- RoHS (Restriction of Hazardous Substances) with respect to the
following substances:
�
Lead (Pb)
�
Mercury (Hg)
�
Cadmium (Cd)
�
Hexavalent Chromium (Cr (VI))
�
PolyBrominated Biphenyls (PBB’s)
�
PolyBrominated Diphenyl Ethers (PBDE’s)
This declaration is issued based on our current level of knowledge.
Since conditions of use are outside our control, ZTE CORPORATION
makes no warranties, express or implied, and assumes no liability in
connection with the use of this information.
II
Chapter
1
Troubleshooting
Overview
Table of Contents
Safety Instruction...............................................................
Symbol Instructions ............................................................
Troubleshooting Scope ........................................................
Requirements for Maintenance Engineers ...............................
Tools and Meters ................................................................
Get In Touch ......................................................................
1
1
2
3
3
4
Safety Instruction
When the system is operational, observe the following safety instructions to avoid serious damages:
�
Only professional personnel who have taken proper trainings
can install, operate, and maintain the equipment.
�
Follow local safety precautions and relevant procedures during
equipment installation, operation, and maintenance to avoid
personal injury or equipment damage.
ZTE does not bear any liabilities incurred by violation of the universal safety operation requirements, or violation of the safety
standards for installation and configuration of the system.
Note:
Safety precautions introduced in this manual are only supplementary to local safety specifications.
Symbol Instructions
Table 1 lists the safety symbols in this manual. These symbols are
used to provide safety tips during equipment installation, operation and maintenance.
1
TABLE 1 SAFETY SYMBOLS
Safety Symbol
Meaning
Caution!
Antistatic sign
Danger! Electric shock!
Caution, scald
Caution, laser
Caution, microwave
There are four levels of safety symbols: Danger, Warning, Caution,
and Note.
Table 2 describes the safety symbol levels.
TABLE 2 SAFETY SYMBOL LEVELS
Level
Description
Danger
Failure to observe the safety
instructions will result in death or
equipment damage.
Warning
instructions may result in serious
personal injury or equipment
damage.
Caution
instructions may result in minor
or moderate personal injury or
equipment damage.
Provides description and tips to
help operation and maintenance.
Note
Troubleshooting Scope
This manual covers the troubleshooting of the following faults:
�
2
ADSL/ADSL2+ service faults
Chapter 1 Troubleshooting Overview
�
VDSL2 service faults
�
VoIP service faults
�
Multicast service faults
�
System faults
�
Network management faults
Requirements for
Maintenance Engineers
Table 3 lists the requirements for maintenance engineers.
TABLE 3 REQUIREMENTS FOR MAINTENANCE ENGINEERS
Type
Requirement
Technology knowledge
Knowledge about Ethernet
protocols
Knowledge about TCP/IP protocols
Knowledge about xDSL technology
Knowledge about multicast
protocols
Knowledge about H.248 protocol
Equipment knowledge
Knowledge about ZXDSL 9806H
hardware configuration
card functions and interfaces
networking
System operation and
maintenance techniques
Knowledge about maintenance on
ZXDSL 9806H
Knowledge about operation on
ZXDSL 9806H series products
Tools and meters
Knowledge about the usage of
tools and meters
Tools and Meters
Table 4 describes the tools and meters used for maintenance.
3
TABLE 4 TOOLS AND METERS
Name
Description
Snipe-nose pliers
It is used to grip objects in
confined spaces.
Wire-stripping pliers
It is used to cut and remove
insulation on electrical wire while
leaving the wire intact.
Diagonal pliers
It is used to cut wires.
Antistatic wrist strap
It is used to prevent electrostatic
discharge.
Ethernet cable tester
It is used to test cable connection.
Optical power meter
It is used to test optical power.
Multimeter
It is used to measure voltage,
current and resistance.
Ground resistance tester
It is used to measure ground
resistance.
Tape measure
It is used to measure length.
Get In Touch
The maintenance engineer can use the following information to
obtain support for troubleshooting:
4
�
Website: [email protected]
�
Hotlines:
�
800-830-1118
�
400–830–1118
�
Fax: 0755–26770801
�
E-mail: [email protected]
Chapter
2
Troubleshooting Flow
and Methods
Table of Contents
Troubleshooting Flow .......................................................... 5
Common Troubleshooting Methods........................................ 6
Fault Classification .............................................................. 7
Troubleshooting Flow
Figure 1 shows troubleshooting flow.
5
FIGURE 1 TROUBLESHOOTING FLOW
Common Troubleshooting
Methods
The following are common troubleshooting methods :
�
Observation
When a fault occurs, maintenance engineers need to observe
it at first.
�
�
�
�
Observe indicators on the card, such as the RUN and ALM
indicators.
Observe the alarm box indicator.
Observe the alarm information on the NMS (maintenance
console).
Plugging/unplugging
When a card does not work normally, unplug and then plug the
card. Sometimes, a card works unusually due to poor contact.
6
Chapter 2 Troubleshooting Flow and Methods
Caution:
While plugging/unplugging a card, make sure that the card is
hot-swappable. The maintenance engineer must put on the
antistatic wrist strap.
�
Card replacement
Replace the card with a new one if the fault still exists after
plugging/unplugging the card.
�
Alarm log analysis
Alarm logs are information displayed on the NMS terminal.
Alarm logs help maintenance engineers to check the system's
running status and locate the fault.
�
Component replacement
Replace the faulty component with a spare component if it is
difficult to locate a fault.
�
PING command
For network faults, execute the ping command to locate the
fault.
�
Isolation
When one part of the system is faulty, isolate the system from
the equipment which is relevant to the faulty part. The faulty
equipment may have an influence on the running of the relevant part of the system.
�
Self-test
When the system or cards are powered ON, they have a selftest. The indicators on a card tell whether the card works normally or not.
�
Press
Pressing a chip or cable connector can remove the fault due to
poor contact.
Fault Classification
Faults can be classified into the following categories:
�
ADSL/ADSL2 service faults
�
VDSL2 service faults
�
VoIP service faults
�
Multicast service faults
�
System faults
�
NM faults
7
8
Chapter
3
ADSL/ADSL2+ Service
Faults
Table of Contents
ADSL/ADSL2+ Basic Information .......................................... 9
Potential Result .................................................................10
Fault Location ...................................................................10
Fault Troubleshooting Flow..................................................11
Fault Handling...................................................................17
Troubleshooting Cases........................................................20
ADSL/ADSL2+ Basic
Information
This topic introduces ADSL/ADSL2+ technology and its implementation in ZXDSL 9806H.
Introduction
ADSL uses the FDM technology. ADSL allows more downstream
bandwidth from central office to customer site than upstream. The
upstream uses the frequency band from 30 KHz to 138 KHz. The
downstream uses the frequency band from 138 KHz to 1.104 MHz.
The upstream rate can reach up to 1 Mbps and downstream rate
can reach up to 8 Mbps.
ADSL2+ is a new generation of ADSL broadband service access
technology. Compared with ADSL, ADSL2+ supports higher rate,
wider frequency and more sub-bands (512 sub-bands). The upstream rate can reach up to 1 Mbps and downstream rate can reach
up to 24 Mbps. The longest transmission distance is 6.5 Km.
Technology Implementation
ZXDSL 9806H provides ASTDE and ASTEB cards to support
ADSL/ADSL2+ service access.
9
�
ASTDE card provides 16-route ADSL/ADSL2+ subscriber interfaces and POTS interfaces.
�
ASTEB card provides 24-route ADSL/ADSL2+ subscriber interfaces and POTS interfaces.
Information Collection
Item
Related Command
Description
Show card interface
status.
show interface
slot/port-list
When a card works
normally, the
LinkStatus is Up.
Show card interface
VLAN.
show interface
slot/port-list
vlan-config
Check the interface
VLAN configuration.
Show ADSL line
profile.
show adsl profile
filename
Check ADSL line
parameters.
Show ADSL interface
status.
show interface
slot/port-list
port-status
Check ADSL interface status and upstream/downstream
rate.
Show port PVC
configuration.
show atm vc
slot/port
Make sure VPI/VCI
setting on Modem is
consistent with that
on DSLAM.
Potential Result
During the process of removing a fault, the following operations
affect the user service:
�
Card reset
�
Plugging or unplugging of the card.
Fault Location
Table 5 describes ADSL/ADSL2+ service faults and causes. The
maintenance engineer can locate the fault according to descriptions in this table.
10
Chapter 3 ADSL/ADSL2+ Service Faults
TABLE 5 ADSL/ADSL2+ SERVICE FAULT LOCATION
Fault Description
Fault Cause
Some user cannot access the
Internet.
�
�
�
�
�
All users of one card cannot
access the Internet.
�
�
�
All users of a whole shelf cannot
�
�
�
�
The user Modem does not
work normally.
There is software or hardware
problem at the user side.
The external line is faulty.
ZXDSL 9806H user port is
faulty.
ZXDSL 9806H data is not
configured properly.
The card connected to these
users is faulty.
ZXDSL 9806H backplane is
faulty.
ZXDSL 9806H main control
card is faulty.
ZXDSL 9806H uplink port is
faulty.
ZXDSL 9806H system is
faulty.
The upper-layer network is
faulty.
Fault Troubleshooting Flow
Figure 2 shows ADSL/ADSL2+ service fault troubleshooting flow.
11
FIGURE 2 ADSL/ADSL2+ SERVICE FAULT TROUBLESHOOTING FLOW
User Modem Check
Check the user modem. Indicators show modem's working status.
Table 6 describes indicators' status. This topic takes ZXDSL 831A
as an example.
TABLE 6 MODEM FAULT LOCATION
Indicator
Status
Description
PWR
OFF
Modem is not powered
ON or modem is
faulty.
ON
If PWR is ON and
other indicators are
all OFF, modem is
faulty.
ON
Modem is activated.
OFF
Modem is failed
to detect signals.
DSL
12
Indicator
LAN
USB
DIAG
Status
Description
Or, modem is not
activated.
Flashing
Modem is failed
to detect signals.
Or, modem is not
activated.
ON
Ethernet is connected.
OFF
Modem is not
connected to the
network card. Or, the
network card is faulty.
ON
Modem is connected
to the computer.
OFF
Modem is not
connected to the
computer. Or, the
computer's USB
interface is faulty.
ON
There is modem
version problem.
User-side Software and Hardware
Configuration Check
If the user's modem works normally, check the software and hardware configuration, including:
�
Cable connection
�
Network card
�
Dial-up software
�
Virus scan
�
Firewall
External Line Check
Check the external lines at user side and office side.
�
�
External line check at user side
�
Voltage between Line A and Line B
�
Resistance between Line A and Line B
�
Capacitance between Line A and Line B
�
Line length
External line check at office side
13
�
TDR test
�
PSD test
�
SNR test
�
Pulse noise test
ADSL subscriber line must meet the requirements described in
Table 7.
TABLE 7 ADSL SUBSCRIBER LINE REQUIREMENTS
14
Requirement
Remark
There is no extra inductor on
subscriber lines.
If a telephone is connected with
the modem, locate the splitter
before the phone and modem.
A subscriber line must be a twisted
pair copper wire.
If the service wire is a four-core
wire, it is recommended to use
a four-core twisted pair cable
instead of a four-core parallel
wire. For four-core parallel wire,
use one pair and leave the other
idle. The length must not exceed
20 meters.
There is no shielding requirement
for subscriber lines.
-
Use subscriber lines without
bridge taps.
-
The insulation resistance of
two subscriber lines to the
ground must be greater than 5
megaohms.
-
The direct loop resistance of
subscriber line must be not larger
than 1.1 kiloohms.
-
The capacitance between
subscriber lines must be less than
200 nF . The capacitance between
subscriber lines and the ground
must be less than 5%.
If the capacitance is smaller than
150 nF, the Internet access speed
can be more stable and higher.
The near end crosstalk ratio must
be greater than 50 dB and the far
end crosstalk ratio is the total of
the near end crosstalk ratio and
the line attenuation.
–
The idle channel noise must be
smaller than or equal to -55
dBm. The average noise power
spectrum density is smaller than
or equal to -115 dBm/Hz.
–
The nominal characteristic
impedance of the line is 100 ohm,
with a maximum of 10% error
allowed.
–
Requirement
Remark
Within the frequency range of 26
kHz – 1104 kHz, the longitudinal
conversion loss must be greater
than or equal to 50 dB. In special
conditions, it can be greater than
40 dB.
–
Table 8 lists attenuations of ADSL subscriber lines with different
line diameters. The unit for attenuation value is dB.
TABLE 8 CABLE PAIRS ATTENUATIONS PER KILOMETER
f
(kHz)
40
60
80
120
150
300
1024
0.32
mm
11.4
13.01
14.38
15.12
16.8
18.13
33.5
0.4
mm
8.29
9.34
10.05
10.87
12.1
14.78
27.3
0.5
mm
5.99
6.85
7.06
7.77
9
12.18
22.5
Table 9 lists maximum frequency attenuations.
TABLE 9 MAXIMUM FREQUENCY ATTENUATIONS
Frequency f(Hz)
Maximum Attenuation
60
37
150
69
300
52
400
60
500
67
600
72
If the attenuation is greater than the maximum value, the ADSL
service is not available. Even if the service is launched, the performance and stability are not guaranteed. When the line attenuation
of relevant sub-band’s carrier frequency is greater than 70 dB, the
line cannot carry any information.
Port Status Check
Card Indicators
Table 10 describes LED indicators on SCCB card.
15
TABLE 10 LED INDICATORS ON SCCB
Indicator
Color
Status
Description
RUN
Green
Flashing
Card is working
normally.
PWR
Green
ON
Power is
working
normally.
OFF
Power is
not working
normally.
ON
Link is
connected.
OFF
Link is not
connected.
ON
Link is
connected.
OFF
Link is not
connected.
Flashing
The interface is
receiving/transmitting data.
OFF
The interface
is not receiving/transmitting data.
L1, L2 (Optical
interface link
indicators)
Electrical
interface/link
indicator
Green
Green
Yellow
Port Status
Execute the show interface slot/portlist command to check port
status. In normal status, the LinkStatus is Up.
Execute the show interface slot/portlist port-status command
to check port status and rate.
Data Configuration Check
Check the following data configurations:
�
VLAN configuration
Execute the show interface slot/portlist vlan-config command to check the port's VLAN configuration.
�
PVC configuration
Execute the show atm vc slot/portlist command to check the
port's VPI/VCI configuration.
�
ADSL line profile configuration
Execute the show adsl profile profilename command to check
ADSL line profile configuration, focusing on the following parameters:
16
�
AtucConfTargetSnrMgn
�
ConfProfileLineType
�
AtucChanConfFastMaxTxRate
�
AtucChanConfFastMinTxRate
�
AtucChanConfInterleaveMaxTxRate
�
AtucChanConfInterleaveMinTxRate
�
AtucChanConfMaxInterleaveDelay
�
AturConfTargetSnrMgn
�
AturChanConfFastMaxTxRate
�
AturChanConfFastMinTxRate
�
AturChanConfInterleaveMaxTxRate
�
AturChanConfInterleaveMinTxRate
�
AturChanConfMaxInterleaveDelay
Upper-layer Equipment Data
Configuration Check
If there is no problem with the equipment hardware and data
configuration, check data configurations of the upper-layer equipment, including:
�
Corresponding interface status
�
Interface rate mode
�
Interface security
�
Interface access control
�
Traffic limit
Fault Handling
This section introduces ADSL/ADSL2+ service fault handling.
Unable to Make a Call Or Access
Internet
Symptom
Troubleshooting
The user cannot make a call or access the Internet.
1. Check user-side line.
2. Check office-side line.
3. If there is no problem with lines, check the splitter.
17
Able to Make a Call, But Unable To
Access Internet
Symptom
Troubleshooting
Users are able to make calls, but unable to access the Internet.
This fault involves all parts of the system networking. Check the
modem indicators, user’s computer setting and equipment at the
local office.
1. Check modem indicators.
This topic takes ZXDSL 831A as an example. Table 11 describes
indicators' status.
Indicator
Status
Description
PWR
OFF
Modem is not
powered ON or
modem is faulty.
ON
If PWR is ON and
all OFF, Modem is
faulty.
ON
Modem is activated.
OFF
Modem is failed
to detect signals.
Or, modem is not
activated.
Flashing
Modem is failed
to detect signals.
Or, modem is not
activated.
ON
Ethernet is
connected.
OFF
Modem is not
connected to the
network card. Or,
the network card is
faulty.
ON
Modem is connected
to the computer.
OFF
Modem is not
connected to the
computer. Or, the
computer's USB
interface is faulty.
ON
There is modem
version problem.
DSL
LAN
USB
DIAG
2. Check the dial-up software if the modem is working normally.
18
�
�
If the user fails to dial up, reinstall the dial-up software.
Set the computer's TCP/IP properties correctly. For dial-up
users, the IP addresses are obtained automatically.
�
Set the format of dial-up account correctly.
�
Set the password of dial-up account correctly.
3. Check the following if PPPoE dial-up is successful, while authentication is failed.
�
�
If the system uses Ethernet interface for uplink and the
user uses PPPoE software, check whether upper-layer service exists at user side. If upper-layer service exists, it is
upper-layer server configuration problem. If upper-layer
service does not exist, it may be system data configuration
problem.
If the user uses the dial-up software of the system or other
dial-up software, check authentication process. If authentication is successful, while Internet access fails, it is upper-layer server configuration problem. If authentication
fails, it may be system data configuration problem.
4. Both PPPoE dial-up and authentication are successful. It still
fails to access the Internet. Try different websites. If it fails to
open other websites also, it is access server problem.
5. Configurations at both the user side and office side are correct.
If it still fails to access the Internet, check the lines.
Internet Access at Low Speed
Symptom
Troubleshooting
Users can access the Internet, but the access speed is very low.
1. If all users access the Internet at low speed, check traffic control, QoS and rate configurations at both ZXDSL 9806H and
upper-layer access server.
2. If only some users access the Internet at low speed, check the
following:
�
�
3.
Open the relevant line profile. Check the maximum upstream/downstream rate settings.
Check the bit error ratio of the line. If the bit error ratio is
too large, decrease bandwidth or increase noise tolerance.
If the fault exists, use a line tester to locate the fault.
If only interleaved-channel users access the Internet at low
speed, check the following:
�
�
Modify the line profile of interleaved-channel users to be the
line profile of users who can access the Internet normally.
Check the relevant line profile, especially maximum upstream/downstream rate and interleaving depth.
19
Unstable Internet Access with
Frequent Disconnections
Symptom
Internet access is not stable and disconnection occurs frequently.
Troubleshooting
1. Check the length of ADSL/ADSL2+ subscriber line. ADSL subscriber line cannot exceed 3 km. ADSL2+ subscriber line cannot exceed 5 km.
2. Check whether there is an electrical interference near modem.
3. Check the location of splitter.
4. Check subscriber line contact.
5. Check line quality.
Troubleshooting Cases
This section introduces ADSL/ADSL2+ service troubleshooting
cases.
Frequent Drops
Symptom
Troubleshooting
Drops occur frequently in a cyber café.
1. Test background noise.
The incoming subscriber line is parallel line. It is about 40
meters. Besides, the cyber café is near the road. The background noise is too high. Many frequency points are around
-100 dBm/Hz. Some frequency points are around -80 dBm/Hz.
It is far beyond the requirement, which is -110 dBm/Hz.
2. Use twisted pairs cable.
Modem is Disabled While Calling
Symptom
Troubleshooting
When the user makes a call, the modem is disabled.
1. Check the modem.
2. Check the user card.
3. Disconnect user-side line. Test the user line near the distribution frame in the equipment room. The fault does not occur.
4. Test the user line near the distribution frame in district where
the user lives. The fault does not occur.
20
5. Check the user's junction box. A pair of phone line is connected improperly. Connect the phone line again. The fault is
removed.
Low Access Rate Because of
Subscriber Line Problem
Symptom
ADSL service is configured. The Internet access rate is very slow.
Sometimes the user fails to open a website.
Troubleshooting
1. CheckZXDSL 9806H data configuration, including upstream/downstream rate, noise margin and channel mode.
2. Check the incoming subscriber line. The subscriber line is parallel line. Use twisted pairs cable. The access rate is enhanced.
Electrical Wire Interference Causes
Modem Disconnection
Symptom
Troubleshooting
ADSL service is not stable. Modem is disconnected frequently.
1. Check the voltage. The voltage is normal.
2. Replace the relevant port, modem and external line trunk. The
fault exists.
3. Connect a modem at the junction box. Modem works normally.
Connect a modem at the subscriber line. Modem does not
work. There is interference from the junction box to subscriber
line.
4. Check the junction box to subscriber line. One part is 30 centimeters away from an electrical wire. Move the electrical wire
100 centimeters away from the subscriber line. The fault is
removed.
Normal Dialup, But Wrong User
Name and Password Prompt
Symptom
The dial-up process is normal. The wrong user name and password
prompt appears after entering user name and password.
Troubleshooting
1. Check the user name and password. Make sure both password
and user name are right.
2. Check BAS configuration.
3. Check switch or route configuration.
4. Check authentication server configuration.
21
Website Unaccessible After
Successful Dialup
Symptom
ADSL service is provisioned. PPPoE dial-up is successful. However,
the user fails to access the Internet or ping any website.
Troubleshooting
1. After successful dial-up, check IP assignment and DNS information. If both IP address assignment and DNS is shown normally, it is not BAS problem.
2. Execute the winipcfg command to check the computer IP.
3. If the computer IP is '0.0.0.0', it is the computer problem. Replace the computer.
Modem Link Established at Low Rate
Symptom
Troubleshooting
Modem link is established successfully. But the rate is too slow.
1. Check subscriber line, including line attenuation and line noise.
2. Check modem. If the modem cannot work normally, replace it.
3. Check ADSL subscriber card.
4. Check ZXDSL 9806H user port rate configurations. If the link
establishment rate is the same as the configured rate, it is not
a fault.
Unsuccessful PPPoE Authentication
Symptom
Troubleshooting
ADSL link is established but PPPoE authentication fails.
1. Check PPPoE user name and password.
2. Check network card.
3. Check PPPoE dial-up software.
4. Check broadband card status.
5. Check ZXDSL 9806H data configuration. Make sure user port
VLAN configuration is consistent with uplink port VLAN configuration.
6. Check broadband uplink port status.
7. Check connection between ZXDSL 9806H and BAS.
8. Check BAS data configuration and running status.
22
PPPoE Authentication Successful,
But Website Unaccessible
Symptom
Troubleshooting
PPPoE authentication is successful but the user fails to access website.
1. Check TCP/IP settings, especially DNS.
2. Check IE settings. Do not select 'Automatically detect setti
ngs'.
3. For Windows users, if TCP/IP and IE settings are correct, install
ADSL dial-up software again.
4. If the user uses LAN. Check LAN networking.
5. Check BAS data configuration and BAS running status.
Low Speed Internet Access with
Frequent Disconnections
Symptom
Troubleshooting
Users access the Internet at low speed and disconnection occurs
frequently.
1. If the modem is not compatible, use other modem type.
2. Check the networking at the user side.
3. Check modem settings. Generally, if the built-in dial-up function is already enabled, do not enable bridging function.
4. Check duplex rate mode.
5. Check card parameters and line specifications. Modify parameters such as noise margin and delay.
6. Check upper-layer network and BAS configurations.
Packet Loss
Symptom
Troubleshooting
The Internet access rate is too slow and there is packet loss.
1. Check ZXDSL 9806H optical power. Both the receiving and
transmitting optical power should be normal.
2. Check the optical power of uplink equipment. There is received
optical power loss. Clean the fiber pigtail. The fault still exits.
3. Check ODF in the equipment room. If there is some problem
with the flange, replace the flange. Clean fiber pigtail. Test the
optical power again. It is normal. The Internet access rate is
enhanced but there is packet delay.
4. Check the line profile. The line mode is interleaved. Change
the interleaved mode to be fast channel mode. The fault is
removed.
23
24
Chapter
4
VDSL2 Service Faults
Table of Contents
VDSL2 Basic Information ....................................................25
Fault Location ...................................................................27
VDSL2 Basic Information
This topic introduces VDSL2 technology and its implementation in
ZXDSL 9806H.
Introduction
VDSL2, the second generation of VDSL, provides high-bandwidth
access, with symmetric and asymmetric transmission rates.
VDSL2 uses DMT technology.
VDSL2 features are as follows:
�
Compatible with ADSL/ADSL2/ADSL2+
�
ITU-T VDSL2 standard (G.993.2) compliant
�
Supports symmetric rate up to 100 Mbps
�
Supports Triple-play services, including data service, VoIP,
IPTV andHDTV
�
Multiple band-plan definitions
ZXDSL 9806H provides VSTDC card to support VDSL2 service access.
VSTDC provides 16-route VDSL2 subscriber interfaces and POTS
interfaces.
25
Its maximum transmission distance is 2.5 Km. Its downstream
transmission rate reaches up to 85 Mbps and upstream transmission rate reaches up to 50 Mbps.
Item
Related Command
Description
Show card interface
status.
show interface
slot/port-list
When a card works
normally, the
LinkStatus is Up.
Show card interface
VLAN.
show interface
slot/port-list
vlan-config
Check the interface
VLAN configuration.
Show VDSL2 line
profile.
show vdsl2
base-profile
filename
Check VDSL2 line
parameters.
show vdsl2
dpbo-profile
filename
show vdsl2
upbo-profile
filename
show vdsl2
service-profile
filename
Show VDSL2 interface
status.
show interface
slot/port-list
port-status
Check VDSL2 interface status and upstream/downstream
rate.
Show port PVC
configuration.
show atm vc
slot/port
Make sure VPI/VCI
setting on Modem is
consistent with that
on DSLAM.
Potential Result
26
�
Card reset
�
Chapter 4 VDSL2 Service Faults
Fault Location
Table 12 describes VDSL2 service faults and causes. The maintenance engineer can locate the fault according to descriptions in
this table.
TABLE 12 VDSL2 SERVICE FAULT LOCATION
Fault Description
Fault Cause
Some user cannot access the
Internet.
�
�
�
�
�
All users of one card cannot
�
�
�
�
�
�
�
The user Modem does not
work normally.
There is software or hardware
problem at the user side.
faulty.
users is faulty.
ZXDSL 9806H backplane is
faulty.
ZXDSL 9806H main control
card is faulty.
ZXDSL 9806H uplink port is
faulty.
ZXDSL 9806H system is
faulty.
The upper-layer network is
faulty.
Figure 3 shows VDSL2 service fault troubleshooting flow.
27
FIGURE 3 VDSL2 SERVICE FAULT TROUBLESHOOTING FLOW
User Modem Check
Check the user modem. Indicators show modem's working status.
Table 13 describes indicators' status.
Indicator
Status
Description
PWR
OFF
Modem is not powered
ON or modem is
faulty.
ON
If PWR is ON and
all OFF, modem is
faulty.
ON
Modem is working
normally.
OFF
Modem does not
work. Connect the
phone line properly.
VDSL Link
28
Status
Description
Flashing
VDSL line is not
stable.
LAN Activity
Flashing
The interface is
receiving/transmitting
data.
LAN Link
ON (Green)
Ethernet rate is 10
Mbps.
ON (Orange)
Ethernet rate is 100
Mbps.
OFF
Modem is not
connected to the
network card. Or, the
network card is faulty.
Indicator
User-side Software and Hardware
Configuration Check
If the user's modem works normally, software and hardware configuration check includes:
�
Cable connection
�
Network card
�
Dial-up software
�
Virus scan
�
Firewall
External Line Check
Check the external lines at user side and office side.
�
�
External line check at user side
�
Voltage between Line A and Line B
�
Resistance between Line A and Line B
�
Capacitance between Line A and Line B
�
Line length
External line check at office side
�
TDR test
�
PSD test
�
SNR test
�
Pulse noise test
29
VDSL subscriber line must meet the requirements described in
Table 14.
TABLE 14 VDSL SUBSCRIBER LINE REQUIREMENTS
30
Requirement
Remark
There is no extra inductor on
subscriber lines.
If a telephone is connected with
the modem, locate the splitter
before the phone and modem.
A subscriber line must be a twisted
pair copper wire.
If the service wire is a four-core
wire, it is recommended to use
a four-core twisted pair cable
instead of a four-core parallel
wire. For four-core parallel wire,
use one pair and leave the other
idle. The length must not exceed
20 meters.
There is no shielding requirement
for subscriber lines.
-
VDSL subscriber line is less than
1 Km.
The appropriate length for VDSL
subscriber line is not longer than
1 Km.
Use subscriber lines without
bridge taps.
-
The insulation resistance of
two subscriber lines to the
ground must be greater than 5
megaohms.
-
The direct loop resistance of
subscriber line must be not larger
than 220 ohms.
-
The capacitance between
subscriber lines must be less than
40 nF . The capacitance between
subscriber lines and the ground
must be less than 5%.
-
The near end crosstalk ratio must
be greater than 50 dB and the far
end crosstalk ratio is the total of
the near end crosstalk ratio and
the line attenuation.
–
The idle channel noise must be
smaller than or equal to -55
dBm. The average noise power
spectrum density is smaller than
or equal to -115 dBm/Hz.
–
Requirement
Remark
The nominal characteristic
impedance of the line is 100 ohm,
with a maximum of 10% error
allowed.
–
Within the frequency range of 900
kHz – 7.9 MHz, the longitudinal
conversion loss must be greater
than or equal to 50 dB. In special
conditions, it can be greater than
40 dB.
–
Table 15 lists attenuations of VDSL subscriber lines with different
line diameters. The unit for attenuation value is dB.
TABLE 15 CABLE PAIRS ATTENUATIONS PER KILOMETER
f
(kHz)
40
60
80
120
150
300
1024
0.32
mm
11.4
13.01
14.38
15.12
16.8
18.13
33.5
0.4
mm
8.29
9.34
10.05
10.87
12.1
14.78
27.3
0.5
mm
5.99
6.85
7.06
7.77
9
12.18
22.5
Table 16 lists maximum frequency attenuations.
TABLE 16 MAXIMUM FREQUENCY ATTENUATIONS
Frequency f(Hz)
Maximum Attenuation
60
7.47
150
9.6
300
11.8
1000
22
Port Status Check
Card Indicators
31
Indicator
Color
Status
Description
RUN
Green
Flashing
Card is working
normally.
PWR
Green
ON
Power is
working
normally.
OFF
Power is
not working
normally.
ON
Link is
connected.
OFF
Link is not
connected.
ON
Link is
connected.
OFF
Link is not
connected.
Flashing
The interface is
OFF
The interface
L1, L2 (Optical
interface link
indicators)
Electrical
interface/link
indicator
Green
Green
Yellow
Port Status
Execute the show interface slot/portlist command to check port
status. In normal status, the LinkStatus is Up.
Execute the show interface slot/portlist port-status command
to check port status and rate.
Data Configuration Check
Check the following data configurations:
�
VLAN configuration
Execute the show interface slot/portlist vlan-config command to check the port's VLAN configuration.
�
VDSL2 line profile configuration
Execute the show vdsl2 service-profile profilename command to check VDSL2 line profile configuration, focusing on
the following parameters:
32
�
AtucConfTargetSnrMgn
�
Ch1ProfMaxDataRateDs/Ch1ProfMaxDataRateUs
�
Ch1ProfMaxDelayDs/Ch1ProfMaxDelayUs
�
Ch1ProfMinProtectionDs/Ch1ProfMinProtectionUs
Configuration Check
If there is no problem with the equipment hardware and data configuration, check the data configurations of the upper-layer equipment, including:
�
�
Interface rate mode
�
Interface security
�
�
Traffic limit
33
34
Chapter
5
VoIP Service Faults
Table of Contents
VoIP Basic Information .......................................................35
Fault Location ...................................................................36
Fault Handling...................................................................44
VoIP Basic Information
This topic introduces VoIP technology and its implementation in
ZXDSL 9806H.
Introduction
VoIP is a general term for a family of transmission technologies
for delivery of voice communications over the IP network. VoIP
systems usually interface with the traditional PSTN to allow for
transparent phone communications.
VoIP architecture contains the following parts:
�
Media gateway
�
Media gateway controller
�
Voice server
�
Signalling gateway
ZXDSL 9806H supports H.248 protocol. It provides VoIP service.
The VoIP sub-card, which is built in the control and switch card,
implements the VoIP service. A single ZXDSL 9806H system supports 128–route VoIP subscribers.
35
Item
Related Command
Description
View narrowband
attributes
configuration.
get- mgbaseattr
Check the protocol
type and port number.
View narrowband
capacity
configuration.
get-mgcapabili
-
View MGC
configuration.
get- mgc
Check MGC type, IP
address, port which
communicates with
MG.
View VoIP
configuration.
get-voip-config
Check MG
signaling and
media information
configuration.
View narrowband user
line attributes.
get-slcattrib
Check user line
status and attributes
configuration.
View user line
Termination ID.
get-ipstermid
Check user line
Termination ID.
Potential Result
�
Card reset
�
Fault Location
Table 18 describes VoIP service faults and causes. The maintenance engineer can locate the fault according to descriptions in
this table.
36
Chapter 5 VoIP Service Faults
TABLE 18 VOIP SERVICE FAULT LOCATION
Fault Description
Fault Cause
Some user cannot make a call.
�
�
�
�
�
All users of one card cannot make
calls.
�
�
�
�
make calls.
�
�
�
�
faulty.
Port TID is not added at
ZXDSL 9806H side or the port
TID is not consistent with that
on SS.
Port TID is not added at MGC
side.
The user's right is restricted
at SS.
The user card cable is
connected improperly.
users is faulty.
Port TID is not added at
ZXDSL 9806H side or the port
TID is not consistent with that
on SS.
The users of the card are not
added at MGC side.
ZXDSL 9806H cannot
communicate with MGC.
VoIP sub-card is faulty.
User TID and RTP TID at
ZXDSL 9806H side are
configured improperly.
User TID and RTP TID at
MGC side are configured
improperly.
Figure 4 shows VoIP service fault troubleshooting flow.
37
FIGURE 4 VOIP SERVICE FAULT TROUBLESHOOTING FLOW
User Phone Check
Check the user phone, including:
38
�
Junction box of the user phone
�
Phone wire
�
Battery
�
Phone key
�
Pulse/audio frequency dialing mode
Lines Check
Check the internal lines and external lines.
�
�
Internal lines
�
Feeding voltage
�
Ringing voltage
�
Circuit current
External lines
�
DC voltage
�
AC voltage
�
Insulation resistance
�
Capacitance
Table 19 lists the line test specifications.
TABLE 19 LINE TEST SPECIFICATIONS
Item
Result
Specification
Feeding voltage
Normal
34 V ≤ Measured
value ≤ 90 V
Abnormal
Measured value < 34
V
Measured value > 90
V
Circuit current
Normal
18 mA ≤ Measured
value ≤ 35 mA
Abnormal
Measured value < 18
mA
Measured value > 35
mA
External lines
Abnormal AC voltage
VACag ≥ 8 V
VACbg ≥ 8 V
VACab ≥ 8 V
Swinging cross with
other lines
VDCag ≤ –30 V
Abnormal DC voltage
VDCag ≥ 8 V
VDCbg ≤ –30 V
VDCbg ≥ 8 V
VDCab ≥ 8 V
39
Item
Result
Specification
Abnormal insulation
resistance
100 Kohm < Rag ≤
500 Kohm
100 Kohm < Rbg ≤
100 Kohm
Abnormal capacitance
0.3 uF ≤ Cag < 0.7 uF
0.3 uF ≤ Cbg < 0.7 uF
Cab ≥ 3.0 uF
Poor insulation
10 Kohm < Rab ≤ 60
Kohm
10 Kohm < Rag ≤ 100
Kohm
10 Kohm < Rbg ≤ 100
Kohm
Line disconnected
Cab < 0.2 uF
Swinging cross
(self-cross)
Rab ≤ 10 K
Lines grounded
Rag ≤ 10 Kohm
Rbg ≤ 10 Kohm
Leakage current
VACag > 100 V
VACbg > 100 V
Circuit current
resistance
Abnormal circuit
current
Measured value < 22
mA
Measured value > 60
mA
Abnormal circuit
resistance
Measured value >
1000 ohm
Measured value < 0
ohm
–
–
–
–
–
–
–
–
–
–
–
–
VACag: AC Voltage between Line A and ground
VACbg: AC Voltage between Line B and ground
VACab: AC Voltage between Line A and Line B
VDCag: DC Voltage between Line A and ground
VDCbg: DC Voltage between Line B and ground
VDCab: DC Voltage between Line A and Line B
Rag: Insulation resistance between Line A and ground
Rbg: Insulation resistance between Line B and ground
Rab: Insulation resistance between Line A and Line B
Cag: Capacitance between Line A and ground
Cbg: Capacitance between Line B and ground
Cab: Capacitance between Line A and Line B
User Port Running Status Check
Check the user port running status using the following commands:
�
40
Execute the get-slcphonenum slot slotnumber command to
check the phone number corresponding to the user port.
�
Execute the get-slcstatus command to check user circuit status.
�
Execute the get-ipsstatus command to check ISP circuit status.
�
Execute the get-slcstatistic command to check subscriber
line status such as idle, occupied and blocked.
Equipment Running Status Check
Card Indicators
Indicator
Color
Status
Description
RUN
Green
Flashing
Card is working
normally.
PWR
Green
ON
Power is
working
normally.
OFF
Power is
not working
normally.
ON
Link is
connected.
OFF
Link is not
connected.
ON
Link is
connected.
OFF
Link is not
connected.
Flashing
The interface is
OFF
The interface
L1, L2 (Optical
interface link
indicators)
Electrical
interface/link
indicator
Green
Green
Yellow
Table 21 describes LED indicators on ATLA/ATLC card.
41
TABLE 21 LED INDICATORS ON ATLA/ATLC
Man-machine
Commands
Indicator
Color
Status
Description
RUN
Green
ON
Card is working
normally.
ALM
Red
ON
Card is faulty
or software is
faulty.
HOOK
-
ON
When a user
hooks off, the
HOOK indicator
is ON.
Execute the show card command to show card status.
Execute the show temperature-check command to check temperature and fan running status.
Execute the show interface slot/port command to check port status. In normal status, the LinkStatus is Up.
Execute the get-bdstat-s command to check the card status in
detail.
RTP Resource Data Configuration
Check
Check the RTP resource data configuration using the following
commands:
�
Execute the get-ipstermid command to view TID format and
series number, which must be consistent with those on SS side.
�
Execute the get-ipsstatistic command to view user circuits
number and circuit status such as idle, occupied and blocked.
�
Execute the get-ipsstatus command to view user circuit status such as idle, occupied and blocked.
User Service Data Configuration
Check
Check the user service data configuration using the following commands:
42
�
Execute the get-mgc mgcid mgcid command to view SS parameters.
�
Execute the get-mgbaseattr, get-mgcapabili and get-voip
-config commands to view AG parameters.
�
Execute the show ip subnet command to view VoIP VLAN
information.
�
Execute the get-slctermid slot slotnumber command to view
TID format and serial number, which must be consistent with
those at SS side.
�
Execute the get-slcstatus command to view user status.
�
Execute the get-slcstatistic command to check subscriber
line status such as idle, occupied and blocked.
�
Execute the get-slcattrib slot slotnumber command to view
circuit fax mode, which must be consistent with those at SS
side.
H.248 Link Status Check
If the link between ZXDSL 9806H and SS is connected, execute
the h248state command to check the H.248 link status.
In normal status, H.248 link is
H248-SS link status(H248Trkplink) :
OK MGCid is x
Configuration Check
If there is no problem with the equipment hardware and data configuration, check the data configurations of the upper-layer equipment, including:
�
�
Interface rate mode
�
Interface security
�
�
Traffic limit
SS Data Configuration Check
SS is the calling and control core of NGN. Check the data configuration at SS side, including:
�
Phone number configuration
�
H.248/MGCP configuration
�
TID configuration
�
Digitmap configuration
43
Fault Handling
This section introduces VoIP service fault handling.
No Dialing Tone After Hook-Off
Symptom
Troubleshooting
When a user hooks off, there is no dial tone.
1. Make sure it is a problem of a single user or all users.
2. Check whether hook-off status is normal.
�
�
Check the HOOK indicator after picking up the phone. In
normal status, the HOOK indicator is ON.
Execute the get-slcstatus command to view subscriber
line status. Check whether the user line is occupied.
3. If only a single user has the problem, check whether its corresponding card is configured and whether the card is online.
4. If all users have the problem, check the backplane. If it is
necessary, replace the backplane.
Busy Tone When Hook-Off
Symptom
Troubleshooting
The user hooks off and only hears busy tone.
1. Check H.248 link.
�
�
�
Execute the get-mgc command to check MGC configuration. If MGC is not configured, use the add-mgc command
to create it. If MGC is not configured properly, use the
mod-mgc command to modify it.
Check whether ZXDSL 9806H data is configured at SS side,
including IP address, protocol port and gateway.
Execute the show ip subnet command to check VoIP VLAN
configuration. If VoIP VLAN is not configured, use the ip
subnet command to configure it.
2. Execute the get-slctermid command to check the user's TID.
3. Check SS data configurations, especially on packet type configuration, number assignment and protocol type.
Busy Tone When Dialing
44
Symptom
The user hooks off and hears the busy tone when dialling a number.
Troubleshooting
1. On SS, check the user's calling right. If the user has not a
calling right, add it on SS.
2. Check the number table configured on SS. If the number table
does not contain the number set with the number initial, add
the number set.
Unreliable Calling Connection
Symptom
Troubleshooting
Sometimes users can make a call. Sometimes, users cannot make
a call. The connection is unreliable.
1. Check IPS module.
i. Execute the get-ipsstatu command to view IPS circuit status. In normal status, IPS circuit is IDLE.
ii. Execute the get-ipstermid command to view configurations of the terminal corresponding to the IPS circuit.
iii. Execute the get-allnat command to view NAT configurations of the IPS circuit.
2. Check IPS status at SS side and at ZXDSL 9806H side. IPS
status at both sides needs to be consistent with each other.
Call Drop
Symptom
Troubleshooting
Call drop occurs when a user is making a call.
1. If call drop occurs after long conversation, check whether Long
Conversation Restriction is set on SS. If Long Conversation Restriction is set, it is normal.
2. If call drop occurs frequently, check whether there are frequent
hook-on messages or hook-switch messages on ZXDSL 9806H.
3. Check user port signals at ZXDSL 9806H. Check whether the
user has severe interference from outside.
Noise in Call
Symptom
Troubleshooting
When a user is calling, there is noise during the call.
1. Check the phone, line, signal of the opposite side.
2. Check the phone of the local side.
3. Check the phone line of the local side.
4. If a splitter is used, check the splitter and the DSL line card at
the opposite side.
5. If it is a toll call, check the network status.
6. Check the media gain of ZXDSL 9806H. If it is too large, reduce
it.
45
7. Check the working ground and protection ground. The voltage
difference between the working ground and protection ground
should be less than 0.1 V.
Unable to Hear Calling Party
Symptom
The user makes a call. The called party cannot hear the calling
party.
Troubleshooting
1. Catch packets at the uplink interface of ZXDSL 9806H after
making a call. Check whether there are bidirectional media
packets.
2. Check route configuration on ZXDSL 9806H. Execute the getvoip-ipaddr command and show ip route command to check
whether the next-hop IP address is configured.
This section introduces VoIP service troubleshooting cases.
Abnormal H.248 Link
Symptom
Troubleshooting
H.248 link between ZXDSL 9806H and SS is disconnected.
1. Ping the uplink interface of ZXDSL 9806H from a computer,
which is in the same network segment with ZXDSL 9806H. If
it fails, check the system data configuration, SCCB card status
and uplink subcard.
2. Execute the get-voip-ipaddr command or show ip route
command to check whether ZXDSL 9806H is configured with
the next-hop route. If the next-hop route is not configured,
create one. If the next-hop route is not configured properly,
modify it.
3. Execute the get-mgc command to check MGC configuration. If
MGC is not configured, use the add-mgc command to create it.
If MGC is not configured properly, use the mod-mgc command
to modify it.
4. Check whether ZXDSL 9806H data is configured at SS side,
including IP address, protocol port and gateway.
5. Execute the show ip subnet command to check VoIP VLAN
configuration. If VoIP VLAN is not configured, use the ip
subnet command to configure it.
46
No Number Display Because of
Splitter
Symptom
Troubleshooting
ADSL service and VoIP service are configured. Both of them are
normal. The incoming call number display function is enabled. But
no number is displayed when a call comes in.
1. Check the user phone.
2. Check line connection.
3. Check whether a voice splitter is connected.
4. Test the distribution frame. Number is not displayed if a splitter
is connected. If there is no splitter, the number is displayed.
5. Replace the splitter. The fault is removed.
Unsuccessful Fax Service
Symptom
Calling between fax machines is successful but fax service is not
successful.
Troubleshooting
1. Check the fax machine. Make sure fax machine works properly.
2. Execute the get-rtppar command to check fax mode of user
ports which are used for fax service. Fax mode of both user
ports needs to be the same.
3. If the fax service is implemented between ZXDSL 9806H systems, check the fax mode of both ZXDSL 9806H systems. Fax
modes of both ZXDSL 9806H systems need to be the same.
4. If the fax service is implemented between ZXDSL 9806H and
PSTN via TG, check the fax mode of TG. Fax modes of TG and
ZXDSL 9806H need to be the same.
5. If T.38 mode is used, check whether SDP field is set in SS.
6. Check line quality. PSTN line quality and bearer network quality.
7. Check uplink port mode. It is recommended to use 100 Mbps
full duplex mode.
Hearing SIT Tone After Dialup
Symptom
Troubleshooting
The user hears SIT after dialing.
1. Check number table and number analysis configuration of SS.
If the number table contains the number cluster and the relevant number analysis is not configured, SIT is generated.
2. Check whether the user number in SS is consistent with the
number cluster in ZXDSL 9806H
47
48
Chapter
6
Multicast Service Faults
Table of Contents
Multicast Basic Information .................................................49
Fault Location ...................................................................51
Multicast Basic Information
This topic introduces multicast technology and its implementation
in ZXDSL 9806H.
Introduction
Multicast is a network addressing method for the delivery of information to a group of destinations simultaneously using the most
efficient strategy. In this method messages are delivered over
each link of the network only once, creating copies only when the
links to the multiple destinations split (typically network switches
and routers). Multicast is often used for streaming media and Internet television applications.
Multicast has the following advantages:
�
Save network bandwidth
�
Less load on network devices
�
Server does not need to process quests for each user.
The core of multicast technology is to copy the packet at the place
near to the receiver as close as possible.
The source host just sends data packet to a specific multicast
group. All receivers in the multicast group can receive the same
data copy. Other hosts in the network cannot receive the data except the host (destination host) in the multicast group. Hosts in a
multicast group can be in the same physical network or in different
physical networks.
The multicast group is identified with Type D IP address (224.0.0.0
~ 239.255.255.255).
49
ZXDSL 9806H supports IGMP Snooping, IGMP Proxy and IGMP
Router
�
In IGMP Snooping mode, the system does not manage status
of multicast members. It just listens to IGMP traffic and forwards IGMP packets passively. It has a little influence on the
system load. However, it greatly increases the load of processing protocols.
�
In IGMP Proxy mode, the system manages status of multicast
members actively, efficiently reducing the load of processing
protocols.
�
IGMP Router mode is a simplified proxy mode. In case that
multicast service is sent to the uplink port, the system does
not require uplink port for multicast service dynamically.
Item
Related Command
Description
View IGMP
information.
show igmp
Check IGMP mode
and IGMP status.
View CAC information.
show igmp cac
Check CAC status
and CAC multicast
address.
View channel package
information.
show igmp
channel-package
Check multicast
channel package
list.
View MVLAN
information.
show igmp mvlan
Check source port,
destination port and
multicast groups in
MVLAN.
View interface IGMP
information.
show igmp
interface
Check multicast
group member
configuration.
Potential Result
50
�
Card reset
�
Chapter 6 Multicast Service Faults
Fault Location
Table 22 describes multicast service faults and causes. The maintenance engineer can locate the fault according to descriptions in
this table.
TABLE 22 MULTICAST SERVICE FAULT LOCATION
Fault Description
Fault Cause
Multicast service for some user is
disconnected.
�
�
�
Multicast service for all users of a
whole shelf is disconnected.
�
�
�
The STB is faulty.
The user port service data is
not configured properly.
Multicast program is not
The user port service data is
Multicast program is not
The multicast data of
upper-layer equipment is
Figure 5 shows multicast service fault troubleshooting flow.
FIGURE 5 MULTICAST SERVICE FAULT TROUBLESHOOTING FLOW
51
STB Check
Check the STB, including:
�
TV and STB power indicators
�
CATV cable
�
Connection between CATV and STB
�
Video channel
�
Intelligent card
�
Remote controller
User Port Service Data Configuration
Check
Check the user port service data configuration using the following
commands:
�
Execute the show igmp interface slot/port command to view
IGMP enabled/disabled status, fast-leave status and bandwidth
limit.
�
Execute the show igmp interface slot/port group command
to view multicast group registered on the port.
�
Execute the show igmp mvlan mvlanid command to check
the receive port and multicast group.
Multicast Data Configurations Check
Check the multicast data configurations, including:
�
ICMP mode
Execute the show igmp command to view IGMP mode, CAC
and CDR status.
�
Multicast programme configuration
Execute the show igmp mvlan mvlanid command to view
MVLAN configuration, source port and destination port.
�
Programme preview configuration
Execute the show igmp view-profile profilename command
to view preview configurations such as preview count and preview interval.
�
Multicast bandwidth configuration
Execute the show igmp mvlan mvlanid group groupaddress
command to view the bandwidth of a multicast group.
�
52
CAC configuration
Chapter 6 Multicast Service Faults
Execute the show igmp cac command to view CAC configuration.
Multicast Programme Configuration
Check
Execute the show igmp mvlan mvlanid command to view the
programmes in multicast VLAN.
This section introduces multicast service troubleshooting cases.
User Cannot Watch Video
Symptom
The user is successful to establish multicast forwarding table on
BRAS and ZXDSL 9806H and is able to view data traffic, but fails
to view video at the client side.
Troubleshooting
1. Ping the multicast server from the client. It is successful. There
is no problem with unicast.
2. Multicast table can be established. There is no problem with
route.
3. Use the multicast software Wlisten and Wsend to have a test.
The client can receive multicast data. There is no problem with
multicast configuration and multicast forwarding.
4. Play the VLC media player. The client can watch video. Catch
packets at the client. The received multicast packets are not
assembled successfully.
5. Catch packets at the multicast server. If the packets are the
same as those caught at the client, the packets sent from multicast server are faulty. Replace a computer. The fault is removed.
Static User and DHCP User Cannot
Receive IPTV Service
Symptom
Troubleshooting
Static users and DHCP users cannot use IPTV service.
1. If the client wants to receive multicast data from the server,
unicast route must be properly established. Ping the server
from the client. It is successful. There is no problem with
unicast route.
53
2. Check RP registration. If the server is registered on RP, there
is no problem with the multicast server.
3. Connect the computer to the switch. Configure relevant data.
If IPTV service is normal, there may be problem with ZXDSL
9806H.
4. ZXDSL 9806H is only for data transparent transmission. Check
VLAN configurations on ZXDSL 9806H. VLAN is configured
properly.
5. Catch packets at the switch to view data sent from ZXDSL
9806H. Catch packets at the computer to view IGMP packet
version. The version of IGMP packet from the multicast client
is correct. The packet caught on the switch does not contain
IGMP packet. It means ZXDSL 9806H has discarded IGMP
packet. The multicast forwarding table cannot be created at
the switch and BRAS. IPTV cannot be received.
6. Configure IGMP Snooping on ZXDSL 9806H. Configure transparent transmission on the switch. IPTV service is normal.
54
Chapter
7
System Faults
Table of Contents
Information Collection ........................................................55
Fault Handling...................................................................59
Card Indicators
Indicator
Color
Status
Description
RUN
Green
Flashing
Card is working
normally.
PWR
Green
ON
Power is
working
normally.
OFF
Power is
not working
normally.
ON
Link is
connected.
OFF
Link is not
connected.
ON
Link is
connected.
OFF
Link is not
connected.
Flashing
The interface is
OFF
The interface
L1, L2 (Optical
interface link
indicators)
Electrical
interface/link
indicator
Green
Green
Yellow
55
Man-machine
Commands
Indicator
Color
Status
Description
RUN
Green
ON
Card is working
normally.
ALM
Red
ON
Card is faulty
or software is
faulty.
HOOK
-
ON
When a user
hooks off, the
HOOK indicator
is ON.
Execute the show card command to show card status.
Potential Result
�
Card reset
�
�
System reboot
Figure 6 shows system fault troubleshooting flow.
56
Chapter 7 System Faults
FIGURE 6 SYSTEM FAULT TROUBLESHOOTING FLOW
Equipment Working Environment
Check
Check the equipment working environment, including the following
items:
�
Power voltage
�
DC voltage range: -56 V ~ -40 V
�
AC voltage range: 85 V ~ 264 V
�
Working temperature: -30 ℃ ~ 55 ℃
�
Working humidity: 5% ~ 95%
�
Cleanness: Dust concentration with a diameter greater than
5µm is equal to or less than 3 × 104 grains/m3, and the dust
is not be electrically conductive, magnetically conductive and
erosive.
�
Grounding resistance: < 1 ohm
�
Air pollution: Do not expose the equipment to corrosive gases
(e.g., SO2, oxides of SO2 and ammonia), smog or oil solvents.
No smoking in the equipment room.
Hardware Running Status Check
Card Indicators
57
Indicator
Color
Status
Description
RUN
Green
Flashing
Card is working
normally.
PWR
Green
ON
Power is
working
normally.
OFF
Power is
not working
normally.
ON
Link is
connected.
OFF
Link is not
connected.
ON
Link is
connected.
OFF
Link is not
connected.
Flashing
The interface is
OFF
The interface
L1, L2 (Optical
interface link
indicators)
Electrical
interface/link
indicator
Green
Green
Yellow
Man-machine
Commands
Indicator
Color
Status
Description
RUN
Green
ON
Card is working
normally.
ALM
Red
ON
Card is faulty
or software is
faulty.
HOOK
-
ON
When a user
hooks off, the
HOOK indicator
is ON.
Execute the show card command to check card status.
58
Chapter 7 System Faults
Fault Handling
This section introduces system fault handling.
Fails to View Message Through
HyperTerminal
Symptom
Troubleshooting
During the process of starting the main control card, the user fails
to view any message through HyperTerminal interface.
1. Check the serial port cable connection.
2. Check baud rate setting on HyperTerminal. It must be '9600 –
n – 8 – 1'. Serial port connection is broken if baud rate is not
correctly configured.
Startup Failure after Version Update
Symptom
Troubleshooting
Main control card fails to start after the version update.
1. Check the version. Make sure the version is correct or version
file is not damaged.
2. If the BOOT version does not match with update version, burn
BOOT version again.
This section introduces system troubleshooting cases.
ISP Chip Works Abnormally
Symptom
The user hooks off and hears busy tone. The NMS displays ISP
relevant unit running alarm.
Troubleshooting
1. Execute the get-ipsstatus command to view ISP circuit status. In normal status, it is IDLE. If it is FAULT, check the main
control card or restart the main control card.
2. Execute the get-ipstermid command to view the relevant terminal configuration. Check whether ISP subcard is inserted.
3. Execute the get-allnat command to view NAT configuration.
59
Narrowband Card Offline
Symptom
The ALM indicator on the narrowband user card is always ON. Or,
the HOOK indicator is always ON. The user hooks off and hears
nothing. The NMS displays that the user is offline.
Troubleshooting
1. Execute the show card slot command to check whether the
offline slot is configured with a narrowband card. The configured card type needs to be consistent with the real card type.
2. Perform signaling trace. Check whether ZXDSL 9806H reports
the off-hook message after the user hooks off. If there is no
report message, the main control card does not work normally.
3. Replace the narrowband user card with a new one.
whether the fault is removed.
Check
Broadband Card Offline
Symptom
Link between ZXDSL 9806H and modem is not established. The
NMS shows that the user is offline.
Troubleshooting
1. Execute the show card slot command to check the card configuration. The card configured on the NMS must be consistent
with the card inserted on the slot.
2. Replace the card's boot chip.
3. Download the card version.
4. Check the main control card.
5. Replace the user card.
60
Chapter
8
NM Faults
Table of Contents
NM Basic Information .........................................................61
Fault Location ...................................................................70
NMS Fault Troubleshooting Flow...........................................71
NM Fault Handling .............................................................75
NM Basic Information
This topic introduces the installation and configuration of network
management software.
NM Installation and Configuration
Requirements
Requirements for NM installation and configuration are as follows:
�
Do not save the installation source file and destination directory
on Windows desktop.
�
Installation directory name cannot be too long. The directory
such as 'D:\9806H\netnumen' is recommended.
�
For NetNumen (Version 2), it is required to create a webnmsdb database (Do not modify the name) in SQL Server enterprise manger. Initialize the database.
�
NetNumen (Version 4) has a built-in FTP server. Do not enable
the built-in FTP server. Select Use Outside FTP Server.
�
After installing NetNumen, configure parameters such as database, NE configuration, FTP parameters, database backup and
log management.
�
If the system gives a prompt
NetNumen (Version 4) startup error
, capture the error message.
61
Operating System and Database
Requirements for the operating system and database are as follows:
�
Use only one network card and one IP address at the server.
If multiple IP addresses are required, make sure that NMS can
start when one IP is used. Then, set multiple IP addresses.
�
In Windows XP/2003 operating system, open Control Panel
> System Options. Close DEP. Right-click the installation file
and select Compatible with win2000
�
Windows operating system must be Windows 2000
Server/Windows XP Professional/Windows 2003 Server.
Install SQL Server 2000 database (Standard, Enterprise or
Development). For Windows XP/2003 operating system, only
SQL Server 2000 Enterprise/Development is installed. SQL
Server 2000 SP3 patch must be installed.
�
Select local system account instead of domain account while
installing SQL server 2000. Select SQL Server and Windows
for identification authentication.
�
For Solaris operating system, use Solaris9. Install Oracle 9
database. Install patch 9.2.0.7 or 9.2.0.8. Database SID is
uep.
�
Copy the installation program to the FTP directory.
NM Server and Client Configuration
in case of Multiple IPs
By default, both NetNumen server and client use only one IP address. When the computer configured with NetNumen have multiple IP addresses, it is necessary to configure NetNumen.
�
NetNumen (Version 2)
�
Set RMI server IP.
Edit the 'WebNMS\setRmiServer.bat' file. Modify the following line:
set RMI_IP=localhost
Change 'localhost' to be the communication IP for NetNumen server/client. If the NetNumen client/server has multiple IP addresses, make sure which IP is for communication.
�
Set the IP of FTP server.
Edit the 'WebNMS\ipms\conf\IPMS_param.conf' file. Modify the following line:
FTP_PARAMETERS
FTPIPAddress="localhost" /
Change 'localhost' to be the IP address of FTP server.
62
Chapter 8 NM Faults
�
NetNumen (Version 4)
Set the IP of FTP server.
Open the FTP configurations in NetNumen Config Center.
Change 'localhost' to be the IP address of FTP server.
Edit the 'ums-svr\zxnm01\dsl\dsl-base.par\con\IPMS_
param.xml' file. Modify the following line:
FTP_PARAMETERS
FTPIPAddress="localhost"
System should be able to ping the FTP server..
Note:
Restart the NetNumen server to save changes.
NMS and SQL Server 2005
Installation in Window 2003
NetNumen N31 supports SQL Server 2005. This topic describes
SQL Server 2005 and NetNumen N31 installation in Windows 2003.
1. Install Windows installer 3.1 before installing SQL Server 2005.
2. Perform the following steps to install SQL Server 2005. Use
default values for the unmentioned options.
i. Run the installation program. Input the license key. The
SQL server Database Services option is mandatory. The
others are optional.
ii. Select installation directory. It is not recommended to save
the data files on the default disk (Disk C). Select other disks
with large space.
iii. Select installation instance.
value.
Generally, use the default
iv. Select account. For a single system, select Use Built-in
System Account.
v. Select ID mode. Generally, select hybrid mode. Input the
password of the 'sa' user. The password netnumen is recommended.
vi. Set the order rule. Generally, the default value is used.
3. Set communication protocol.
i. Run Programs > Microsoft SQL Server > SQL server
Configuration Manager. Select SQL Network Configuration > MSSQLSERVER Protocol. Enable Named
Pipes and TCP/IP.
ii. Double-click TCP/IP. Select the IP address corresponding
to the network card. Select Yes for the Enabled option.
Make sure the port number is 1433.
63
4. Re-start SQL Server 2005 database.
5. Configure NetNumen N31 configuration center.
i. Run Start > Programs > NetNumen N31 > Tools >
NetNumen N31 Config Center.
ii. Select Common Configuration > Database Configuration. Select MS SQL2005 in the Database Tpye dropdown menu. Modify database parameters such as password and port number.
iii. Click Save.
Mysql Installation
It is recommended to install Oracle database in Unix system. In
special cases, Mysql database can be used. Perform the following
steps to install Mysql:
1. Install different MySQL5.0 installation kit for different Solaris
versions.
�
�
Solaris 8: Use 'mysql-standard-5.0.9-beta-solaris8-sparc64bit.tar.gz'.
Solaris 9: Use 'mysql-standard-5.0.9-beta-solaris9-sparc64bit.tar.gz'.
2. Execute the following commands to add MySQL user and
group:
shell> groupadd mysql
shell> useradd -g mysql mysql
3. Copy
the
'mysql-standard-5.0.9-beta-solaris*-sparc64bit.tar.gz'
in
the
'/export/home/ myspace/ mysql'
directory. Decompress the installation file.
Execute the following commands to decompress the file:
shell>cd /usr/local
shell>rm mysql
shell>cd /export/home/myspace/mysql
shell>gunzip mysql-standard-5.0.9-beta-solaris*-sparc-64bit.tar.gz
shell>tar xvf mysql-standard-5.0.9-beta-solaris*-sparc-64bit.tar
shell>cd /usr/local
shell>ln -s /export/home/myspace/mysql/mysql-standard5.0.9-beta-solaris*- sparc-64bit mysql
4. Modify file or directory right.
Execute the following commands to modify file or directory
right:
shell>cd /usr/local/mysql
shell>scripts/mysql_install_db --user=mysql
shell>chown -R root .
shell>chown -R mysql data
shell>chgrp -R mysql .
5. Modify root user password.
Execute the following commands to modify root user password:
shell>cd /usr/local/mysql/bin
64
Chapter 8 NM Faults
shell>./mysqld_safe --default-character-set=gb2312 --user=mysql &
shell>./mysql -uroot
mysql>use mysql;
mysql>update user set password=password(’public’) where
user=’root’;
// mysql>select user, host from user;
mysql> update user set user=’%’ where host=’localhost’
and user=’’;
mysql>update user set host=’%’ where host=’localhost’
and user=’root’;
mysql>update user set user=’%’ where host=’nm9000’ and
user=’’;
//mysql>update user set host=’%’ where host=’nm9000’
and user=’root’;
mysql>flush privileges;
mysql>exit;
shell>./mysqladmin -uroot -ppublic shutdown
6. Start MySql database.
Execute the following commands to start MySql server:
shell>cd /usr/local/mysql/bin
shell>./mysqld_safe --default-character-set=gb2312
--lower_case_table_ names=1 –user=mysql &
�
Start NM server.
Run the 'zxnm01v4\tools\configcenter\bin\run.bat' file.
Set database IP address, user name and password. Click OK.
SUN + ORACLE Environment
This section introduces NM operation and configuration in SUN +
Oracle environment.
Basic NMS Installation and Configuration
It is required to use the 'oracle' user to install the NMS in Oracle
environment. Execute the env command to check the parameters.
1. NMS installation
Open the directory where the NMS installation file resides. Input ./install.sh or, right-click the file and change the property to be 'executable. Double-click Run.
Check the parameters in NetNumen N31 Config Center. The
database IP address must be the real IP address of the network
card. Do not use 127.0.0.1.
If FTP function is used in UNIX, the root path for the 'zte' and
'webnms' users must be the same. Create these two users in
UNIX manually.
2. Database initialization
Login to the database as the 'root' user. Enter the Solaris window.
#cd /export/home/netnumen
#pwd
/export/home/netnumen
65
#chmod -R 777 .
#su – oracle
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
$cd /export/home/netnumen/ums-svr/docs/dbscript/install-db
$./install-db.sh
Observe the initialization. The following prompts are normal.
Record other prompts.
chmod: WARNING: can’t change convert.bat
chmod: WARNING: can’t change db-installer-jdbc.sh
Or,
[exec] SP2-0332: Cannot create spool file.
[exec] SP2-0332: Cannot create spool file.
NMS Start-up in UNIX
�
Run
'/netnumen/bin/startNmsServer.sh'
or
'/netnumen/ums-svr/bin/console.sh' to start up the NMS on Unix
server locally.
�
For dual systems, use 'console.sh' to be start-up script.
Modify the '/netnumen/umssvr/ platform/psl/ext-service/console/conf/maincontroller.xml' file. Select '0' for
client-type. In this way, when the NetNumen is started, the
console interface is not displayed.
�
Run '/netnumen/bin/remoteStartServer.sh' to start up the
NMS if logon to the Unix server is through Telnet or X-manager
remotely.
Problems Related to Oracle Installation
During the Oracle database installation process, following problems may occur:
�
The login user is not Oracle user.
The './install.sh: sqlplus:
the 'install.sh' file is run.
not found'
message appears when
Perform the following steps:
i.
Run sqlplus. If the '# sqlplus sqlplus: not found' message
appears, the login user is wrong. If it is successful to run
sqlplus, the user name prompt appears, it means the user
is right.
ii. Exit sqlplus.
iii. Run the 'install.sh' file again.
�
NMS server cannot connect to the database.
When NMS client is started, many 'SQLException' messages appear. It fails to start NMS client.
Perform the following steps:
i.
Ping the database server. If it fails, modify network settings.
ii. Check IP and database name parameters.
66
Chapter 8 NM Faults
iii. Check Oracle database running status.
a) Log on to the database as 'oracle' user.
b) Start SQL*PLUS: $sqlplus /nolog.
c) Log on to the database as 'sysdba' user: SQL>connect
system/manager as sysdba.
d) Start the database: SQL>startup.
If the database is already running, the 'ORA-01081:
cannot start alreadyrunning ORACLE - shut it down first'
message appears. If not, continue the start process.
e) Exit SQL*PLUS: SQL>exit.
iv. Check whether database monitor is started.
a) Log on to the database as 'oracle' user.
b) Run the monitoring program: $ lsnrctl.
c) Start the monitor: LSNRCTL> start.
If the monitor is already started, the 'TNS-01106:
Listener using listener name LISTENER has already been
started' message appears. If not, continue the start
process.
d) Exit the monitoring program: LSNRCTL> exit.
SID Configured in Oracle Inconsistent with NMS
Generally, it is recommended to configure SID in Oracle database
to be 'uep'. If it is not, it is necessary to modify relevant NMS
configuration files.
Perform the following steps to modify SID on NMS configuration
files.
1. Modify NMS server start-up file: ums-svr/deploy/deploy-default.properties.
Set all 'databasename' in this file to be the SID of Oracle database. In this instance, it is 'ipms'. The descriptions are as
follows:
default.uep.ds.databasename=ipms
uep-mif-mifcore.MIBDS.ds.databasename=ipms
uep-pal-fm.fm.ds.databasename=ipms
uep-pal-pm.ueppmds.ds.databasename=ipms
jms.jms.ds.databasename=ipms
2. Modify NMS database initialization script configuration
file:
ums-svr/docs/dbscript/install-db/uep/conf/install-uep-conf.properties.
Set DBSID to be the SID of Oracle database. In this instance,
it is 'ipms'.
Perform the modification before creating NMS database. Then,
initialize database.
67
Solaris Commands
Table 27 lists Solaris commands.
TABLE 27 SOLARIS COMMANDS
Command
Meaning
Example
Cd
Change directory.
-
Ls
Display the
directory/file
information. It equals
to the dir command.
The ls-l command
displays the detailed
information.
Rmdir
Delete an empty
directory.
-
mkdir
Create a directory.
-
pwd
Display the current
directory.
-
rm
Delete a file.
Use the rm –R *
command to delete all
files in the directory.
Carefully use it.
cp
Copy a file.
Copy a file: cp
NM01.zip /netnumen
Copy a directory: cp
-r /netnumen/umssvr/tools
/export/home
Copy a directory/file
on the remote
server: rcp –p/-rp
netnu men1:/export/home/oracle.tar
/export/home
mv
Change a file name.
Move a file or
directory.
-
chmode
Change file right.
chmod 755 file
chmod u+w file
chmod g+w file
chmod o+w
The -R parameter
recursion
68
Chapter 8 NM Faults
Command
Meaning
Example
find
Find the designated
file.
Find the file in the
root directory and
display the result on
the terminal: find /
-name filename -print
df
Display disk usage.
df –kh
uname
Display system
information.
uname -a
netstat
Display network
status.
netstat –r: Check
the route status.
ifconfig
Configure or view
network interface
parameters.
View network status:
ifconfig -a
Configure interface
address (for
mm7000): ifconfig
eri0 136.1.56.170
ifconfig eri0
up(down)
ifconfig eri0 add
Add a logic address:
if ipaddress
admintool
Create a
user/directory.
-
date
View or set system
time.
-
env
View system
environment
parameters.
-
route add
Add a route.
Add the default
gateway: route add
default 136.1.0.1 1
If the '/etc/defaultrouter' file exists, the
system will set the IP
address in this file to
be its gateway when
the system starts up.
tar
Encapsulate/Deencapsulate.
De-encapsulate: tar
-xvf oracle.tar
Encapsulate: tar -cf
a.tar a
Zip
Compress files.
-
Unzip
Uncompress files.
unzip a.zip
69
Command
Meaning
Example
ps
View the process.
View all java process:
ps -ef | grep java
kill
Kill a process.
kill -9 120
Kill a process, then,
restart the process:
kill -HUP 120
Pkill
Kill a process
according to the
process name.
pkill httpd
Potential Result
During the process of removing a fault, restarting the NM server
or database terminates the network management at the client.
Fault Location
Table 28 describes NM faults and causes. The maintenance engineer can locate the fault according to descriptions in this table.
TABLE 28 NM FAULT LOCATION
Fault Description
Fault Cause
The server cannot be started.
�
�
�
�
The client cannot be started.
�
�
�
�
Other faults
70
The database does not work
normally.
The NMS installation directory
name is too long.
The port is occupied by other
programmes.
The operating system is not
compatible with the NMS.
The firewall is installed.
The bandwidth is not enough.
The port is occupied by other
programmes.
The NMS version at the client
is not consistent with that at
the server.
Refer to NM Faults Handling.
Chapter 8 NM Faults
NMS Fault Troubleshooting
Flow
Figure 7 shows NMS fault troubleshooting flow.
FIGURE 7 NMS FAULT TROUBLESHOOTING FLOW
NM Environment Check
Software
Requirements
�
Windows operating system
�
�
�
Windows XP, Windows 2000, Windows 2003 with the latest
patches
SQL Server 2000/SQL Server 2005
Sun Solaris operating system
�
Sun Solaris (above 6.5)
�
Oracle 9i database
71
Hardware
Requirements
�
Hardware requirements for Windows platform
Table 29 lists hardware requirements for Windows server.
TABLE 29 HARDWARE REQUIREMENTS FOR WINDOWS SERVER
NetNumen N31 Type
Hardware Platform
NETNumen N31-EXX-S-1.0
Intel XEON or Pentium IV 2.0
GHz, 1 GB RAM, Two 36 GB
HDDs, DVD drive, 10/100 Mbps
Ethernet Network Adapter
NETNumen N31-EXX-M-1.0
GHz (Two on-board Processors),
2 GB RAM, Two 36 GB HDDs,
DVD drive, 10/100 Mbps
NETNumen N31-EXX-L-1.0
GHz (Two on-board Processors),
DVD drive, 10/100 Mbps
NETNumen N31-EXX-U-1.0
GHz (Four on-board Processors),
DVD Combo drive, 10/100 Mbps
Table 30 lists hardware requirements for Windows client.
TABLE 30 HARDWARE REQUIREMENTS FOR WINDOWS CLIENT
�
NetNumen N31 Type
Hardware Platform
Pentium IV 2.0 GHz, 512 MB
RAM ,20 GB HDD, CDROM,
Sound Card, 10/100 Mbps
RAM, 20 GB HDD, CDROM,
Hardware requirements for Solaris platform
Table 31 lists hardware requirements for Solaris server.
72
Chapter 8 NM Faults
TABLE 31 HARDWARE REQUIREMENTS FOR SOLARIS SERVER
NetNumen N31 Type
Hardware Platform
SUN Blade 2000 UltraSPARC III
Cu 1.2 GHz, 1 GB RAM, 73 GB
HDD, DVD drive, 10/100 Mbps
SUN Blade 2000 UltraSPARC
III Cu 1.2 G (two on-board
processors), 2 GB RAM, 73 GB
HDD, DVD drive, 10/100 Mbps
V880 UltraSPARC III Cu 1.2 GHz
(Four on-board processors), 4
GB RAM, Two Optical Interface
36 GB HDD, DVD drive, 10/100
Mbps Ethernet Network Adapter
V880 UltraSPARC III Cu 1.2 GHz
(Eight on-board processors),
4 GB RAM, Two 36 GB Optical
Interface HDD, DVD Drive,
10/100 Mbps Ethernet Network
Adapter
Table 32 lists hardware requirements for Solaris client.
TABLE 32 HARDWARE REQUIREMENTS FOR SOLARIS CLIENT
NetNumen N31 Type
Hardware Platform
Intel Pentium IV 2.0 GHz G, 1
GB RAM ,20 GB HDD, CDROM
drive, Sound Card, 10/100 Mbps
NM Server Operating System
Configuration Check
Check the operating system which is running NM server, including:
73
�
Software and hardware configurations
�
Firewall
�
Disabled ports such as Port 1433, FTP port
�
Computer name: The renamed computer may cause abnormal
running.
Database System Running Check
Select Programs > Microsoft SQL Server > Enterprise Manager. Check the following items:
�
In the Database folder, there must be UEP, UEP_CAF_FM
and UEP_FM.
�
Click Security > Login. Check the password of sa user. It
must be consistent with the password set in NetNumen system
(Default: netnumen).
Logic Connection between NM and
Database
Check the logic connection between NM and database.
1. Run the database.
2. Run NetNumen N31 config center.
Select Start > Programs > NetNumen N31 > Tools > NetNumen N31 Config Center.
3. Test connection.
Select Common Configuration > Database Configuration.
Check SQL server configurations. Click Test Connection to
check the connection.
4. If the connection is failed, select Start > Programs > NetNumen N31 > Tools > NetNumen N31 Init Database. Initialize the database.
NM Basic Information Configuration
Check
Make sure that the following operations are performed in the NetNumen N31 config center before starting NetNumen N31.
1. Config center selection
Select Start > Programs > NetNumen N31 > Tools > NetNumen N31 Config Center.
2. NE selection
74
Chapter 8 NM Faults
Select DSL Product > Access Layer > DSL Product.
3. Database configuration
Select Common Configuration > Database Configuration.
Check SQL server configurations.
4. FTP server configuration
Select Common Configuration > FTP Service. Check FTP
server configurations. If the outside FTP server is used, select
Use Outside FTP Server.
NM System Right Configuration
Check
Login to NetNumen N31 Client. Select View > Security Management. On the Security Management interface, select Security
Management Tree > User Management. Check the user information.
NE SNMP Configuration Check
Execute the show snmp command to check SNMP server configuration.
Execute the snmp-server community communityname ro | rw
command to configure the attribute 'community'.
Execute the snmp-server host ipaddress command to configure
SNMP server IP address.
NM Fault Handling
This section introduces NM fault handling.
Unable to Ping In-band NM
Symptom
Troubleshooting
NMS fails to get information after ZXDSL 9806H is started.
1. Check whether NetNumen N31 Server/Client is able to ping the
uplink port of ZXDSL 9806H.
i. Check the cable connection among the computer, switch
and uplink port ofZXDSL 9806H.
ii. Check indicators. In normal status, L1/L2 optical interface
or Ethernet electrical interface indicator is green. Network
interface indicator on the computer is flashing.
75
iii. Execute the show ip subnet command to view VoIP VLAN.
Voice and management uplink ports need to be added to
this VLAN.
iv. If the computer and the uplink port of ZXDSL 9806H are not
in the same network segment, check the gateway settings
of ZXDSL 9806H and the computer.
2. Execute the get-ctrlport command to view the relevant control port. The control port needs to contain the equipment port
number, which is 161. The transmission-layer protocol is UDP.
Data and Version Upload/Download
Unsuccessful
Symptom
Downloading/uploading fails even after the directory and file name
is configured in NetNumen N31 client.
Troubleshooting
1. Check parameters on the Version Upload/Download interface, including the file directory and file name.
2. Make sure that it is successful to ping ZXDSL 9806H from FTP
server.
3. Make sure that FTP server is started. FTP server uses Port 21.
The version file directory is specified on FTP server.
4. To upload version, make sure that the FLASH of ZXDSL 9806H
has the version to be uploaded. To download version, make
sure that the directory on FTP server has the version to be
downloaded.
NMS Fails to Receive NE Alarm
Messages
Symptom
ZXDSL 9806H has alarm message. Open the Realtime Current
Alarms window in NetNumen N31 client. There is no alarm about
NE.
Troubleshooting
1. Execute the get-ctrlport command to view whether ZXDSL
9806H is configured with control port 162 (UDP type).
2. In NetNumen N31 client, check whether ZXDSL 9806H is configured with Trap Server. Make sure the IP address of Trap
Server is correct.
3. In NetNumen N31, check whether alarm filtering is configured.
4. Use the serial port query software to view whether control port
163 is used by other software. If it is used, uninstall the software.
76
Chapter 8 NM Faults
Unable To Start Client
Symptom
Troubleshooting
The Netnumen N31 Client cannot be started after the NMS is installed.
1. Make sure the server IP address is correct.
2. Make sure the database and server run normally.
3. Check firewall settings.
4. Check the use of system ports.
5. Check the bandwidth use.
NM Server Startup Failure
Symptom
Troubleshooting
NM server fails to start.
1. Check whether SQL server works normally.
2. Make sure SQL server is installed with service pack SP3 or
above.
3. Select Start > Programs > NetNumen N31 > Tools > NetNumen N31 Config Center. Select Common Configuration
> Database Configuration. Make sure all parameters are
4. Check NMS installation directory.
77
78
Figures
Figure 1 Troubleshooting Flow .............................................. 6
Figure 2 ADSL/ADSL2+ Service Fault Troubleshooting Flow .....12
Figure 3 VDSL2 Service Fault Troubleshooting Flow ................28
Figure 4 VoIP Service Fault Troubleshooting Flow ...................38
Figure 5 Multicast Service Fault Troubleshooting Flow .............51
Figure 6 System Fault Troubleshooting Flow ..........................57
Figure 7 NMS Fault Troubleshooting Flow ..............................71
79
80
Tables
Table 1 Safety Symbols ....................................................... 2
Table 2 Safety Symbol Levels ............................................... 2
Table 3 Requirements for Maintenance Engineers .................... 3
Table 4 Tools and Meters ..................................................... 4
Table 5 ADSL/ADSL2+ Service Fault Location ........................11
Table 6 Modem Fault Location..............................................12
Table 7 ADSL Subscriber Line Requirements ..........................14
Table 8 Cable Pairs Attenuations Per Kilometer ......................15
Table 9 Maximum Frequency Attenuations.............................15
Table 10 LED Indicators on SCCB .........................................16
Table 11 Modem Fault Location ............................................18
Table 12 VDSL2 Service Fault Location..................................27
Table 13 Modem Fault Location ............................................28
Table 14 VDSL Subscriber Line Requirements ........................30
Table 15 Cable Pairs Attenuations Per Kilometer.....................31
Table 16 Maximum Frequency Attenuations ...........................31
Table 18 VoIP Service Fault Location ....................................37
Table 19 Line Test Specifications ..........................................39
Table 21 LED Indicators on ATLA/ATLC..................................42
Table 22 Multicast Service Fault Location ..............................51
Table 27 Solaris Commands ................................................68
Table 28 NM Fault Location .................................................70
Table 29 Hardware Requirements for Windows Server.............72
Table 30 Hardware Requirements for Windows Client ..............72
Table 31 Hardware Requirements for Solaris Server................73
Table 32 Hardware Requirements for Solaris Client.................73
81
82
Index
A
ADSL/ADSL2 Service
Information Collection ...... 10
ADSL/ADSL2 Technology
Introduction ......................9
ADSL/ADSL2+ Service
Fault Handling ................. 17
ADSL/ADSL2+ Service
Fault Location .................. 10
ADSL/ADSL2+ Service
Troubleshooting Cases ...... 20
VoIP Service Information
Collection........................ 36
VoIP Service Troubleshooting Cases ............ 46
VoIP Technology
Introduction .................... 35
M
Multicast Service Fault
Location.......................... 51
Multicast Service
Multicast Service
Troubleshooting Cases ...... 53
Multicast Technology
Introduction .................... 49
N
NM Fault Handling ............. 75
NM Fault Location .............. 70
S
System Fault Handling ....... 59
System Fault Information
Collection........................ 55
System Troubleshooting
Cases ............................. 59
T
troubleshooting methods ......6
V
VDSL2 Service Fault
Location.......................... 27
VDSL2 Service
VDSL2 Technology
Introduction .................... 25
VoIP Service Fault
Location.......................... 36
VoIP Service Faults
Handling ......................... 44
83
84
Glossary
AC
- Alternating Current
ADSL
- Asymmetric Digital Subscriber Loop
AG
- Access Gateway
BAS
- Broadband Access Server
BRAS
- Broadband Remote Access Server
CAC
- Channel Access Control
CATV
- CAble TeleVision
CDR
- Call Detail Record
DC
- Direct Current
DHCP
- Dynamic Host Configuration Protocol
DMT
- Discrete Multi-Tone
DNS
- Domain Name Server
DSL
- Digital Subscriber Line
DSLAM
- Digital Subscriber Line Access Multiplexer
FDM
- Frequency Division Multiplexing
FTP
- File Transfer Protocol
HDTV
- High Definition Television
ICMP
- Internet Control Message Protocol
IGMP
- Internet Group Management Protocol
IP
- Internet Protocol
IPS
- Intelligent Protection Switching
85
IPTV
- Internet Protocol Television
ISP
- Internet Service Provider
ITU-T
- International Telecommunication Union-Telecommunication Standardization Sector
LAN
- Local Area Network
MG
- Media Gateway
MGC
- Media Gateway Controller
MGCP
- Media Gateway Control Protocol
MVLAN
- Multicast Virtual Local Area Network
NAT
- Network Address Translation
NE
- Network Element
NGN
- Next Generation Network
NMS
- Network Management System
ODF
- Optical Distribution Frame
POTS
- Plain Old Telephone Service
PPPoE
- Point to Point Protocol over Ethernet
PSD
- Power Spectrum Density
PSTN
- Public Switched Telephone Network
PVC
- Permanent Virtual Channel
QoS
- Quality of Service
RP
- Rendezvous Point
RTP
- Real-time Transport Protocol
SDP
- Session Description Protocol
SIT
- Special Information Tone
86
Glossary
SNMP
- Simple Network Management Protocol
SNR
- Signal to Noise Ratio
SS
- Soft Switch
STB
- Set Top Box
TCP/IP
- Transfer Control Protocol/Internet Protocol
TDR
- Time Domain Reflectometry
TG
- Trunk Gateway
TID
- Terminal Identification
UDP
- User Datagram Protocol
VCI
- Virtual Channel Identifier
VDSL
- Very High Speed Digital Subscriber Line
VDSL2
- Very High Bit Rate Digital Subscriber Line 2
VLAN
- Virtual Local Area Network
VPI
- Virtual Path Identifier
VoIP
- Voice over Internet Protocol
87

zxdsl 9806h - donbassmedia.net.ua

Transcription

Similar documents

GOLDEN MILE PROPERTY

Convergence Challenges for the SME

Manufacturing Energy Management Solution (MEMS)

Cybex Trazer

Making a Positive Connection

ZTE Enterprise Products

Marie-Helene Cormier1, Ruth Elaine Blake2, Dwight F. Coleman1

2 aeronautical industries to materials a4m 8 2 13 salvato