NEC Univerge SV9100 User manual

System Maintenance Manual
NDA-31584
Issue 1.0
SV9100
®

NEC Corporation of America reserves the right to change the specifications, functions, or features at
any time without notice.
NEC Corporation of America has prepared this document for use by its employees and customers.
The information contained herein is the property of NEC Unified Solutions, Inc. and shall not be
reproduced without prior written approval of NEC Unified Solutions, Inc.
Dterm®is a registered trademark of NEC Corporation. UNIVERGE®is a trademark of NEC
Corporation. Windows®is a registered trademark of Microsoft Corporation. All other brand names and
product names referenced in this document are trademarks or registered trademarks of their
respective companies.
Copyright 2014
NEC Corporation of America
6535 N. State Highway 161
Irving, TX 75039-2402
Communications Technology Group

Preface
Before Reading this Manual
This manual provides detailed information for diagnostic and maintenance information for the SV9100
system.
There are three parts to this manual:
Chapter 1 – Troubleshooting IP on an SV9100 System
This chapter provides some helpful tips for troubleshooting IP on the SV9100 system.
Chapter 2 – System Maintenance
The technician can use this chapter to troubleshoot and diagnose problems during and after SV9100
system installation. The troubleshooting flow charts and general test procedures help the technician
identify possible causes of the problem by defining the problem area.
Chapter 2 – Diagnostics
This chapter provides a description of the SV9100 Diagnostic Interface Module (DIM) built into the
GCD-CP10 blade. The DIM can monitor the activity of the system under the control of commands
entered by the engineer.

THIS PAGE INTENTIONALLY LEFT BLANK

System Maintenance Manual i
___________________________________________________________________________________
___________________________________________________________________________________
TABLE OF CONTENTS
Chapter 1 Troubleshooting IP on an SV9100 System
Section 1 Introduction ................................................................................................. 1-1
Section 2 Ping ............................................................................................................ 1-1
2.1 Pinging from a PC .....................................................................................1-3
2.2 Pinging from an UNIVERGE SV9100 IP Phone .......................................1-3
Section 3 Packet Traces ............................................................................................ 1-5
Chapter 2 System Maintenance
Section 1 Introduction ................................................................................................. 2-1
Section 2 Operational Test Procedures ..................................................................... 2-1
2.1 General Information ..................................................................................2-1
2.2 Before Initializing ......................................................................................2-1
2.2.1 Cable Connections ........................................................................2-1
2.2.2 Initialization Check ........................................................................2-2
2.3 System Initialization ..................................................................................2-2
2.4 After Initialization ......................................................................................2-2
Section 3 Troubleshooting ......................................................................................... 2-3
3.1 Remote Administration and Maintenance .................................................2-3
3.2 Problem Solving ........................................................................................2-3
3.2.1 System Down ................................................................................2-3
3.2.2 Partial Operation ...........................................................................2-3
3.2.3 Reset .............................................................................................2-3
3.3 Flowcharts ................................................................................................2-4
Chapter 3 Diagnostics
Section 1 What is Available? ....................................................................................... 3-1

___________________________________________________________________________________
ii Table of Contents
___________________________________________________________________________________
Issue 1.0 UNIVERGE SV9100
Section 2 Before you Start ........................................................................................ 3-1
Section 3 To Log On to the DIM Locally via the Ethernet Socket of the
GCD-CP10 ................................................................................................ 3-2
Section 4 To Disconnect from the DIM Locally via the Ethernet Socket of the
GCD-CP10 ................................................................................................ 3-4
Section 5 SV9100 DIM Commands .......................................................................... 3-5
Section 6 Common DIM Commands ......................................................................... 3-8
Section 7 SV9100 Net DIM Commands .................................................................. 3-10
Section 8 IP Related Commands ............................................................................ 3-15
Section 9 Reading SV9100 DIM Traces .................................................................. 3-24
Section 10 ISDN Layer 3 Trace (Mail in 0 0 1 2) ....................................................... 3-26
Section 11 ISDN Layer 3 Trace (mail in 0 0 1 2) with SV9100 Main Activity
(Mail in 0 0 0 0) ........................................................................................ 3-28
Section 12 SV9100Net Trace (Nwinfo Debug Light) ................................................. 3-32
Section 13 SV9100Net Trace Using the ISDN Debug Trace (Mail in 0012) ............. 3-35

System Maintenance Manual iii
___________________________________________________________________________________
___________________________________________________________________________________
LIST OF FIGURES
Figure 1-1 Ping Traces ................................................................................................................1-2
Figure 1-2 Ping Usage Example ..................................................................................................1-4
Figure 1-3 Trace File Example .................................................................................................... 1-6
Figure 3-1 SV9100 Ethernet Properties ....................................................................................... 3-2
Figure 3-2 SV9100 System Activity .............................................................................................3-3

___________________________________________________________________________________
iv List of Figures
___________________________________________________________________________________
Issue 1.0 UNIVERGE SV9100
THIS PAGE INTENTIONALLY LEFT BLANK

System Maintenance Manual 1 - 1
Chapter
1
Troubleshooting IP on an SV9100 System
SECTION 1 INTRODUCTION
This book provides some helpful tips for troubleshooting IP on the
UNIVERGE® SV9100 system.
SECTION 2 PING
This is one of the most useful tools available to troubleshoot IP
connectivity. PING is a standard component of Microsoft Windows® and
is also implemented on the UNIVERGE SV9100 IP Phones. Ping sends a
small IP packet to a specified destination and waits for a response back.
It should be possible to ping IP Phones, the GCD-CP10 (CPU), GPZ-IPLE
and any other devices on the network. Send a ping and wait for a reply. If
a reply is not received, the ping response “times out”. This indicates a
connection problem.
Refer to Figure 1-1 Ping Traces on page 1-2 for examples of these two
conditions.

Issue 1.0 UNIVERGE SV9100
1 - 2
Figure 1-1 Ping Traces
Unsuccessful Ping Trace
Successful Ping Trace

UNIVERGE SV9100 Issue 1.0
System Maintenance Manual 1 - 3
If unable to ping a device, it may mean that either the source or destination device:
is not configured correctly
is not connected to the LAN (e.g., cable disconnected)
has a developed a fault
or any device in between the source or destination may be faulty (e.g., routers)
2.1 Pinging from a PC
The command syntax for ping is:
ping [-t] [-n count] [-l size] target
-t (optional) continually sends PING requests until Ctrl-C is
pressed to cancel -n (optional) sends a specified number of PING
requests -l (optional) sends packets of a specified size (bytes)
target the destination IP address or host name
Note that there are other options available with the Microsoft Windows®
implementation of ping. The most commonly used options are listed above.
Examples:
ping 192.168.2.100 -t Continually pings 192.168.2.100 until Ctrl-C
pressed
192.168.2.100 -n 10 -l 40 Sends ten 40-byte packets to 192.168.2.100
ping 192.168.2.100 Sends four 32-byte packets (default) to
192.168.2.100
2.2 Pinging from an UNIVERGE SV9100 IP Phone
The System IP Phone has a version of ping within the Maintenance Menu.
Hold down help button for 3 sec
Press 3 (Ping)
Enter address
Press OK
The following options are available:
1. Echo request start: Starts the ping process using the settings in options
2 and 3 below.
2. Destination address: The target destination IP Address
3. A successful ping results in: 1.OK 2.OK 3.OK 4.OK Complete
A unsuccessful ping results in: 1.NG 2.NG 3.NG 4.NG Complete

Issue 1.0 UNIVERGE SV9100
1 - 4
An example of ping usage:
A UNIVERGE SV9100 IP Phone unsuccessfully attempts to connect to the
UNIVERGE SV9100 system as shown in Figure 1-2 Ping Usage Example.
As seen in Figure 1-2 Ping Usage Example, there are several devices that
could cause a connection problem:
UNIVERGE SV9100 IP Phone [phone])
Local Hub
Local Router (192.168.1.1)
Leased Line
Remote Router (192.168.2.1)
Manageable Data Switch
UNIVERGE SV9100
You will see that by pinging from the System IP Phone and PCs, we can work
out where the problem lies by process of elimination. We start by pinging the
nearest device and working outward toward the intended destination.
Figure 1-2 Ping Usage Example
Hub Router Router
Default Gateway
192.168.2.1
Default Gateway
192.168.1.1
PC
192.168.1.101
IP Phone
192.168.1.100
Leased
Line
UNIVERGE SV9100
192.168.2.100
PC
192.168.2.101
Manageable Data
Switch

UNIVERGE SV9100 Issue 1.0
System Maintenance Manual 1 - 5
Examples:
The UNIVERGE SV9100 IP Phone can successfully ping all devices up to
and including the local router. Anything beyond that point fails. This would
suggest that the Leased Line or remote router has a problem.
The local PC (192.l68.1.101) can ping all devices except the UNIVERGE
SV9100 IP Phone. The UNIVERGE SV9100 IP Phone can not ping
anywhere. This would suggest that there is a problem with the UNIVERGE
SV9100 IP Phone or its connection to the switch/hub.
SECTION 3 PACKET TRACES
It is possible to use a packet trace utility (also known as “Sniffers”) to determine what
data is being transmitted and received on an ethernet network. These can be
particularly useful to determine the cause of connection issues or voice quality issues.
The packet trace utility has to run on a PC that is connected to a managed switch port
that is capable of port mirroring. The technician will need to enable port mirroring on
the Switch port the IPLE is connected to, and mirror to the port the PC that is running
wireshark is connected to. A HUB may not be used in front of the SV9100, however a
HUB may be used for wireshark captures in front of IP Telephones. The reason for
this is the IPLE Network connection does NOT support half-duplex devices.
There are many utilities available that will allow packet trace to be run on a network.
One such utility is Ethereal. This is a software application distributed under a GNU
general public license (www.wireshark.org). This allows the files to be captured and
saved in a standard format for analysis later.
A sample trace file is shown in Figure 1-3 Trace File Example on page 1-6.

Issue 1.0 UNIVERGE SV9100
1 - 6
Figure 1-3 Trace File Example

System Maintenance Manual 2 - 1
Chapter
2
System Maintenance
SECTION 1 INTRODUCTION
The technician can use this book to troubleshoot and diagnose problems
during and after system installation. The troubleshooting flow charts and
general test procedures help the technician identify possible causes of the
problem by defining the problem area.
Using the System Data Upload/Download feature, all System
Programming and Speed Dial data can be stored on disk for safe keeping.
After all System Programming is completed, it should be downloaded to a
disk for backup. When system memory fails, this data on the disk can be
uploaded and the memory restored.
SECTION 2 OPERATIONAL TEST PROCEDURES
2.1 General Information
When an UNIVERGE SV9100 system is first powered up, an
initialization is performed. During this process the GCD-CP10
(CPU), located in the first chassis, scans each interface slot to
determine the hardware configuration used. This information is
stored in the resident system program memory with the system
default values. This section provides test procedures that are used
before, during, and after the initialization process.
2.2 Before Initializing
The technician must follow these steps before initializing the
system.
2.2.1 Cable Connections
All wiring for power supplies or flat cable connectors
should be checked for solid connections.

Issue 1.0 UNIVERGE SV9100
2 - 2
2.2.2 Initialization Check
To determine if the system is initializing correctly, only the first
chassis, GCD-CP10, one GCD-8DLCA, and terminals should be
installed on the system. After initialization, all the terminals assigned
to the GCD-8DLCA can be used for internal calls to one another. (By
default, these stations are assigned station numbers 101~108).
2.3 System Initialization
Before initialization is performed and verified, the entire system should be
initialized.
With power OFF, all interface and option cards can be installed in the
controlling chassis. The technician can then power up the system to perform
a First Initialization. After the initialization, each station display shows default
time and date indications.
For example: 12-2 Fri 10:47 AM
2.4 After Initialization
Check all blade slots in software to ensure the initialization process scanned
the installed hardware correctly.
A general system operation check should be performed using default values
prior to system programming.
After all previous steps are performed and any problems corrected, system
programming is complete.
After System Programming is finished, the technician should perform a
Second Initialization. Performing the First Initialization a second time causes
all programming memory to be lost. Second Initialization refreshes the system
RAM without losing any memory.
This completes the installation procedure for the UNIVERGE SV9100 system.
The technician should check the operation of each Multiline Terminal to
ensure the system is working properly.
Ensure that the battery is installed in CN15 on the
GCD-CP10.

UNIVERGE SV9100 Issue 1.0
System Maintenance Manual 2 - 3
SECTION 3 TROUBLESHOOTING
3.1 Remote Administration and Maintenance
PCPro can remotely access the UNIVERGE SV9100 system for maintenance
and diagnostics. The remote PC and the system are connected using a
modem on the GCD-CP10 or using IP.
3.2 Problem Solving
To find the cause, consider all problem symptoms carefully. As each aspect of
the problem is considered, the technician is guided to a probable solution.
The problem must be defined as accurately as possible, so that the most
efficient steps to the solution can be taken. Flowcharts in the next section
help define the problem.
3.2.1 System Down
This term describes one of the following situations:
No access to internal dial tone on any installed Multiline Terminal or
Single Line Telephone.
No LED or display indication on any installed Multiline Terminal.
No system tones are generated.
3.2.2 Partial Operation
This term refers to any situation that cannot be completely described
under the System Down conditions.
3.2.3 Reset
At times, the station and/or the blade must be reset. The following
resets are used in the system:
Terminal Reset – Unplug the station line cord from the station and then
plug it back into the station.
Blade Reset - Unseat the blade and reseat.

Issue 1.0 UNIVERGE SV9100
2 - 4
3.3 Flowcharts
Condition Flowchart Page
A. System Down
1. No Internal Dial Tone to any
Multiline Terminal or SLT A1 2-5
2. No LED or Display
Indications on any Multiline
Terminal
A2 2-6
B. Partial Operations
1. Frequency Interference B1 2-7
2. No or Intermittent CO/PBX
Ring C1 2-8
3. Call Dropping C2 2-9
4. No Outside Dial Tone Access C3 2-10
5. CO/PBX Dialing Problem:
Cannot Dial Out on CO C4 2-11
C. Multiline Terminal Problems
1. Multiline Terminal Function D1 2-12
2. Multiline Terminal Ringing D2 2-13
3. Multiline Terminal Dial Tone
Access D3 2-14
D. Single Line Telephone Problems
1. No Dial Tone Access on SLT E1 2-15
2. Ringing Problem on SLT E2 2-16
3. No Dial Access to SLT
Features E3 2-17
E. Low Volume Problems F1 2-18
F. External Paging Problems G1 2-19
G. SMDR Output Problems
No Call Accounting System H1 2-20