Nortel Meridian 1 PC Console Interface Unit Operating manual

© 1998 Northern Telecom
All rights reserved
Printed in the United States of America
Northern Telecom reserves the right to make changes in equipment, design, or components as progress in
engineering or manufacturing may warrant.
Meridian 1 and SL-1 are trademarks of Northern Telecom. UNIX is a trademark of AT&T. Motorola is a
trademark of the Motorola Corporation. MVME products are trademarked by the Motorola Corporation.
LaserJet is a trademark of Hewlett-Packard. Reflection is a trademark of Walker Richer & Quinn.
Meridian 1
Application Module and
Intelligent Peripheral Equipment Module
Diagnostic and Maintenance Guide
Publication number: 553-3211-510
Product release: Meridian Link Release 5C/CCR Release 3C
Document status: Standard 1.0
Date: October 1998

ii
553-3211-510 Standard 1.0 October 1998

iii
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Publication history
October 1998
Standard 1.0

iv Publication history
553-3211-510 Standard 1.0 October 1998

v
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Contents
About this guide xi
References xi
Chapter 1: Overview 1
Application Module and IPE Module 1
Customer Controlled Routing 2
Meridian Link 2
Meridian 1 utilities 2
Application Module hardware components 4
IPE Module hardware components 11
SMM167 11
IPE Module faceplate 11
Tape drive 13
Disk drive 13
I/O connectors 13
Application Module and IPE Module utilities 14
Logging in 14
The ccrusr function 15
The maint function 15
The mlusr function 15
The trmcnfg function 16
Advanced maintenance 16

vi Contents
553-3211-510 Standard 1.0 October 1998
Chapter 2: Application Module commands 17
adminÑenter a link-related session 20
applconfigÑdisplay/modify application configuration 20
applexitÑexit software applications 21
applstartÑstart software applications 21
backconfigÑschedule unattended backup 22
backdataÑback up data files 27
backfilesÑback up selected data files 31
bootconfigÑdisplay and modify boot configuration 34
ccrexitÑshut down the CCR application 35
ccrmidnightÑrun midnight routines on system 36
ccrstartÑstart up the CCR application 37
ccrtrafficÑmaintain script statistics 37
ccrusrÑenter a CCR user session 43
chgpasswdÑchange user passwords 44
conshareÑMeridian 1 console session 45
diskuseÑdisplay disk usage statistics 47
editvoiceÑcreate/edit voice prompts 47
exitÑlog out 48
filedeleteÑdelete a file 49
fileverifÑverify system files 50
helpÑlist all commands 51
installÑload software tape onto the hard disk 52
lanconfigÑchange the system's ethernet configuration 55
langconfigÑconfigue CCR logon screen languages 58
mlexit 59
mlstart 59
mlusrÑenter a link-related user session 59
portconfigÑconfigure terminals and printers 60
powerdownÑsafely power down or reboot the module 62
printconfigÑconfigure printers 66
quitÑlog out 70
resetmodemÑreset the modem on the Application
Module 70
restartÑstop and start the link processes 71
rootpasswdÑchange the root password 72
rstdataÑrestore data from backup tape 73
rstfilesÑrestore a set of files 76
scriptinfoÑdisplay a summary of script information 77

Contents vii
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
showidÑdisplay Meridian 1 information 78
startNSEÑactivate Ethernet LAN support 79
stopNSEÑde-activate Ethernet LAN support 79
tapeinfoÑdisplay information on a system tape 80
versionÑdisplay Application Module or IPE Module
software version 81
viewÑdisplay SysLog and link-related files 84
viewlogÑdisplay SysLog file 86
Chapter 3: Link maintenance commands 87
Using link maintenance commands 88
Command format 88
Link control commands 93
enable link 93
disable link 93
Link status commands 94
status link 94
get links 94
Link configuration commands 96
display linkctl 96
change linkctl 97
read linkctl 100
save linkctl 101
display link 102
change link 104
save link 114
read link 115
Link statistics command 116
Meridian Link messages 119
Message types 119
Message names 119
Specifying message types in commands 119
Association services commands 120
get associations 120
get directory numbers 121
get resource 122
message statistics 123
filter commands 126
record commands 129

viii Contents
553-3211-510 Standard 1.0 October 1998
monitor commands 133
traffic commands 137
Link tracing commands 141
trace link 141
trace main 141
untrace link 142
untrace main 142
Link testing commands 145
continuity test 145
loopback test 146
File viewing commands 150
view 150
viewlog 151
Miscellaneous commands 152
exit 152
quit 152
help 152
version 155
Chapter 4: Diagnosing faults 157
Quick reference fault isolation 157
Diagnostic procedure 1: Power fault suspected 158
Diagnostic procedure 2: Power fault suspected 164
Diagnostic procedures 3 and 4: Card fault suspected 167
Reseating a card 169
Advanced diagnostic tests 169
Diagnostic procedure 4: Card fault suspected 176
Diagnostic procedure 5: System console fault suspected 178
Diagnostic procedure 6: System start-up problem 184
Diagnostic procedure 7: Dial-up problem 187
Diagnostic procedure 8: Application terminal problem 190
Diagnostic procedure 9: Printer faults 200
Disk/tape drive unit faults 206
Login failure 207
Difficulty logging in as ccrusr 207
Difficulty logging in as maint 208
Difficulty logging in as mlusr 209
Link failure 210
AML (Link 0) will not establish 210

Contents ix
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
X.25 host computer link (Link 1) will not establish 217
TCP/IP host computer link (Link 1) will not establish 225
Meridian Mail Link (Link 2) will not establish 226
Meridian Link application malfunction 227
Application registration fails 227
Meridian Link call processing functions fail 230
Meridian Link-based applications do not receive expected
messages 233
Chapter 5: Application Module and 237
Messages that appear on the system console 238
System and UNIX messages 238
Application messages 239
maint messages 243
Other messages that appear on the system console 260
Messages that appear in the SysLog file 266
System and UNIX messages 266
Application messages 267
maint messages 280
Bad-event messages 286
Other messages reported in the SysLog file 287
Chapter 6: Link error messages 291
Link maintenance commands fail 291
mlusr error messages 293
Diagnostic tools error messages 298
Stale association 300
Removing a stale mlusr association 300
Chapter 7: CCR log file messages 303
Chapter 8: Recovery/replacement procedures 365
Powerdown and restart procedures 366
Procedure 1: Software powerdown 366
Procedure 2: SBC restart 368
Procedure 3: Hardware powerdown 370
Procedure 4: Power up the Application Module or IPE
Module 370

xContents
553-3211-510 Standard 1.0 October 1998
Hardware replacement procedures 371
Procedure 5: Replace the Application Module power
supply 371
Procedure 6: Replace the Application Module disk/tape
unit 371
Procedure 7: Replace the Application Module
MVME147/167 SBC card 372
Procedure 8: Configure the Application Module MVME147
SBC card 373
Procedure 9: Configure the Application Module MVME167
SBC card or the IPE Module 378
Procedure 10: Replace the Application Module 382
Procedure 11: Replace the MVME332XT or
MVME332XTS ACC card 383
Procedure 12: Replace the NT6D51 transition card 384
Procedure 13: Remove the Application Module 385
Procedure 14: Replace the Application Module 386
Procedure 15: Remove the IPE Module 387
Procedure 16: Replace the IPE Module 387
Procedure 17: Replace the Application Module MVME712
transition card 388
Procedure 18: Replace or reconfigure the Application
Module MVME705B transition card 392
Software reinstallationÑinitializing the system from tape 394
Procedure 19: Load the operating system tape on an
Application Module with an MVME147 card 395
Procedure 20: Load the operating system tape on an IPE
Module or an Application Module with an MVME167
card 412
Procedure 21: Reboot and go through setup 431
Procedure 22: Load the application software from tape 441
Procedure 23: Back up configuration files and data files 454
Procedure 24: Restore configuration files and data files
from the backup tape 456
Procedure 25: Enable or disable Ethernet LAN support 460
List of terms 469
Index 475

xi
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
About this guide
This guide is designed to assist in identifying, diagnosing, and resolving
fault conditions in the Application Module and IPE Module. The intended
audience for this guide includes end users, field technicians, and field
support engineers.
This guide provides an overview to the Application Module and IPE
Module, and to Application Module commands, a section on diagnosing
faults, and a list of error and status messages to help diagnose faults.
Procedures for software recovery and hardware replacement follow.
The term ÒMeridian 1Ó is used throughout this document, and refers to
Meridian 1 and ÒMeridian 1-readyÓ systems (such as Meridian SL-1 style
cabinets that have been upgraded).
References
The following Northern Telecom (Nortel) publications (NTPs) may be of
assistance when using this document:
¥Application Equipment Module Installation Guide
(NTP 553-3203-200)
¥Meridian Link/Customer Controlled Routing Installation and Upgrade
Guide (NTP 553-3202-210)
¥Application Module and Intelligent Peripheral Equipment Module
Advanced Maintenance Guide (NTP 553-3211-512)
¥Meridian Link/Customer Controlled Routing Engineering Guide
(NTP 553-3211-520)
¥Customer Controlled Routing User Guide (P0747008)

xii About this guide
553-3211-510 Standard 1.0 October 1998

1
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Chapter 1: Overview
Application Module and IPE Module
The Application Module (AM) is a subunit that fits into an Application
Equipment Module (AEM). It is an auxiliary application processor that
provides an interface between the AEM and the MeridianÊ1, and possibly
also a host computer, depending on the particular application running. The
interface between the Application Module and the Meridian 1 is the
Application Module Link (AML). The AML may also be referred to as a
Command and Status Link (CSL) in the Meridian 1.
The Intelligent Peripheral Equipment (IPE) Module is a subunit that fits
into an IPE shelf or Option 11 cabinet. The IPE Module also uses the AML
as the interface to the Meridian 1 system.
Diagnostic tools are provided on both the Meridian 1 and the Application
Module or IPE Module sides of the link. Tools on the Meridian 1 are
typically the X11 input/output programs (Loads or LDs). Tools on the
Application Module or IPE Module include commands and utilities
accessed through the system console, or a terminal attached through a
modem port or a TTY port (if available).
Note: If you configure the optional conshare capability available to
the Application Module and IPE Module, you can also access the
Meridian 1 from the Application Module or IPE Module system
console.

2Chapter 1: Overview
553-3211-510 Standard 1.0 October 1998
Customer Controlled Routing
The Customer Controlled Routing (CCR) application provides a scripting
interface, through which you can control the handling and treatment for
calls that come through the Meridian 1 system.
You can install either the large version of CCR or the small version but not
both versions. Small CCR supports twenty active script associations at
most; Large CCR supports as many as 240 active associations.
Meridian Link
The Meridian Link application is a communications facility between a host
computer and a Meridian 1 system. Optionally, the Meridian Link
application also provides an interface between the Meridian 1 system and
Meridian Mail for voice processing.
Meridian 1 utilities
You can use the X11 input/output programs listed below for configuring
and maintaining the Application Module Link (AML). You can also use the
programs for configuring telephones, Automatic Call Distribution (ACD),
routes, and trunks.
Note: For basic application configuration, see the Meridian
Link/Customer Controlled Routing Installation and Upgrade Guide
(NTP 553-3202-210). Further information can be found in the
X11 Input/Output Guide (NTP 553-3001-400).
¥ LD2: Traffic report control program
¥ LD10: Single-line telephone administration; it configures
500/2500-type telephones
¥ LD11: Multiline telephone administration; it configures multiline and
digital telephones
¥ LD14: Trunk administration; it configures trunks
¥ LD15: Customer data block; it configures customer-wide options
¥ LD16: Trunk routes; it configures routes

Chapter 1: Overview 3
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
¥ LD17: Configuration record; it configures the ESDI or MSDL port
between the Application Module or IPE Module and the MeridianÊ1
¥ LD20: Print program; it displays telephone configurations
¥ LD21: Print program; it displays the Customer Data Block
configuration
¥ LD22: Print program; it displays the ESDI or MSDL port
configuration and the Meridian 1 software packages equipped on the
system
¥ LD23: Automatic Call Distribution (ACD); it configures ACD groups
¥ LD48: Link Diagnostic; it controls the status of the Application
Module Link (AML) from the Meridian 1 and monitors AML
messages flowing in and out of the Meridian 1

4Chapter 1: Overview
553-3211-510 Standard 1.0 October 1998
Application Module hardware components
The Single Board Computer (SBC) card can be either an
MVME147SA-1 or an MVME167-03. For easier reading, this card will be
referred to as the MVME147/167 card.
The hardware components listed below (see Figures 1 and 2) are field-
replaceable units.
¥ MVME147SA-1 SBC card
This is the main CPU card of the Application Module. There are four
LEDs and two switches on the faceplate of the SBC card:
Ñ The red LED (Fail indicator) is lit when the BRDFAIL bit is set or
when a watchdog time-out occurs. It is normal for this indicator to
flicker while diagnostics are running; when a failure occurs, this
indicator is steadily lit.
Ñ The yellow LED (Status indicator) is lit when the MC68030
STATUS pin is low (when steadily lit, it indicates that the processor
has stopped).
Ñ The green LED (Run indicator) is lit when the microprocessor
executes a bus cycle.
Ñ The green LED (SCON indicator) is lit to indicate that the SBC
card is the VME bus system controller.
Ñ The ABORT switch stops program execution and returns control to
the debugger.
Ñ The RESET switch, when enabled, generates a local reset. If the
SBC card is the system controller, this switch also generates a
VME bus system reset.
!
CAUTION
Risk of data loss
Do not press both the ABORT and RESET buttons at
the same timeÑyou risk losing device configuration
information.

Chapter 1: Overview 5
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
¥ MVME167-03 SBC card
The main CPU card of the Application Module. There are eight LEDs
and two switches on the faceplate of the SBC card:
Ñ The red LED (Fail indicator) is lit when the BRDFAIL bit is set or
when a watchdog time-out occurs. It is normal for this indicator to
flicker while diagnostics are running; when a failure occurs, this
indicator is steadily lit.
Ñ The yellow LED (Status indicator) is lit when the MC68040
STATUS pin is low (when steadily lit, it indicates that the processor
has stopped).
Ñ The green LED (Run indicator) is lit when the microprocessor
executes a bus cycle.
Ñ The green LED (SCON indicator) is lit to indicate that the SBC
card is the VME bus system controller.
Ñ The green LED (LAN indicator) is lit when the LAN chip is the
local bus master.
Ñ The green LED (+12V indicator) is lit when power is available to
the transceiver interface.
Ñ The green LED (SCSI indicator) is lit when the SCSI chip is the
local bus master.
Ñ The green LED (VME indicator) is lit when the board is using the
VME bus, or when the board is accessed by the VME bus.
Ñ The ABORT switch stops program execution and returns control to
the debugger.
Ñ The RESET switch, when enabled, generates a local reset. This
switch also generates a VME bus system reset.
¥ MVME333-2 X.25 Communication Controller (XCC) card
This card supports synchronous communications links to a host
computer and the Meridian 1. On the faceplate, there is a single red
LED (Fail indicator), which lights when a hardware or LAPB/X.25
communication software error occurs.

6Chapter 1: Overview
553-3211-510 Standard 1.0 October 1998
¥ MVME332XTS Asynchronous Communication Controller (ACC) card
This card provides eight RS-232 interface ports for connection of
terminals and printers. There are three LEDs on the faceplate of the
ACC card:
Ñ The red LED (Fail indicator) lights when a hardware failure
occurs on the ACC card.
Ñ The red LED (Halt indicator) lights steadily when the on-board
processor halts, indicating an ACC card malfunction.
Ñ The green LED (Run) indicates the activity level of the ACC card
by lighting dimly, brightly, or in pulsing mode. A dimly lit LED
indicates that the system is idle, meaning that no terminal
activities are occurring. A brightly lit or pulsing LED indicates
data transfer activities are taking place.
¥ MVME712A and MVME712AM transition cards
The MVME712A and MVME712AM cards provide four 9-pin
connectors (asynchronous serial ports 1Ð4) and a printer-port
connector. Additionally, the MVME712AM card provides an RJ11
port.
The MVME712AM card has a built-in modem and is used in countries
in which the modem is type-approved. The MVME712A transition
card, which does not provide a built-in modem, uses a locally-
approved external modem for remote maintenance.
The built-in modem in the MVME712AM card provides full duplex
operation over two-wire Public Switch Telephone Networks (PSTNs).
It operates in asynchronous mode at data rates of 300, 600, 1200, or
2400 bps.
This transition card also provides an Ethernet connection.
¥ MVME712M transition card
This card supports RS-232 ports and Ethernet and SCSI interfaces for
the SBC card.

Chapter 1: Overview 7
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
¥ MVME705B transition card
This card supports two synchronous I/O ports for the MVME333-2
XCC card. SP1 connects the Application Module Link (AML) to the
Meridian 1.
¥ NT6D51AA transition card
This card supports eight serial I/O ports for the MVME332XTS ACC
card. SP1 connects to ports 1, 2, and 3; SP2 connects to ports 4, 5, and
6; and SP3 connects to ports 7 and 8.
¥ Power supply
This is located at the front left-side of the Application Module.
¥ Disk/tape unit
This is located at the front right-side of the Application Module. This
unit contains a hard disk drive and a cassette tape drive.
The entire Application Module is also field-replaceable. If, in diagnosing
the problem, replacing the above components does not help, contact your
Nortel support personnel.

8Chapter 1: Overview
553-3211-510 Standard 1.0 October 1998
Figure 1
Application Module in the AEMÑfront view
CCR Module (left side)
Power
supply
Meridian Link Module (right side)
Disk/tape unit: topÑtape drive
bottomÑhard disk drive
M
V
M
E
1
4
7
or
1
6
7
M
V
M
E
3
3
3
-
2
M
V
M
E
3
3
2
X
T
S
M
V
M
E
1
4
7
or
1
6
7
M
V
M
E
3
3
3
-
2