Nortel Meridian Meridian 1 Maintenance Manual

Application module and intelligent peripheral equipment module meridian link release 5c/ccr release 3c diagnostic and maintenance guide
Hide thumbs Also See for Meridian Meridian 1:
Table of Contents

Advertisement

Meridian 1
Application Module and
Intelligent Peripheral Equipment Module
Diagnostic and Maintenance Guide
Publication number:
Product release:
Document status:
Date:
© 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.
553-3211-510
Meridian Link Release 5C/CCR Release 3C
Standard 1.0
October 1998

Advertisement

Table of Contents
loading

Summary of Contents for Nortel Meridian Meridian 1

  • Page 1 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 © 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.
  • Page 2 553-3211-510 Standard 1.0 October 1998...
  • Page 3 Publication history October 1998 Standard 1.0 Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide...
  • Page 4 Publication history 553-3211-510 Standard 1.0 October 1998...
  • Page 5: Table Of Contents

    Contents About this guide References Chapter 1: Overview Application Module and IPE Module Customer Controlled Routing Meridian Link Meridian 1 utilities Application Module hardware components IPE Module hardware components SMM167 IPE Module faceplate Tape drive Disk drive I/O connectors Application Module and IPE Module utilities Logging in The ccrusr function The maint function...
  • Page 6 Contents Chapter 2: Application Module commands adminÑenter a link-related session applconfigÑdisplay/modify application configuration applexitÑexit software applications applstartÑstart software applications backconfigÑschedule unattended backup backdataÑback up data files backfilesÑback up selected data files bootconfigÑdisplay and modify boot configuration ccrexitÑshut down the CCR application ccrmidnightÑrun midnight routines on system ccrstartÑstart up the CCR application ccrtrafficÑmaintain script statistics...
  • Page 7 showidÑdisplay Meridian 1 information startNSEÑactivate Ethernet LAN support stopNSEÑde-activate Ethernet LAN support tapeinfoÑdisplay information on a system tape versionÑdisplay Application Module or IPE Module software version viewÑdisplay SysLog and link-related files viewlogÑdisplay SysLog file Chapter 3: Link maintenance commands Using link maintenance commands Command format Link control commands enable link...
  • Page 8 viii Contents monitor commands traffic commands Link tracing commands trace link trace main untrace link untrace main Link testing commands continuity test loopback test File viewing commands view viewlog Miscellaneous commands exit quit help version Chapter 4: Diagnosing faults Quick reference fault isolation Diagnostic procedure 1: Power fault suspected Diagnostic procedure 2: Power fault suspected Diagnostic procedures 3 and 4: Card fault suspected...
  • Page 9 X.25 host computer link (Link 1) will not establish TCP/IP host computer link (Link 1) will not establish Meridian Mail Link (Link 2) will not establish Meridian Link application malfunction Application registration fails Meridian Link call processing functions fail Meridian Link-based applications do not receive expected messages Chapter 5: Application Module and Messages that appear on the system console...
  • Page 10 Contents Hardware replacement procedures Procedure 5: Replace the Application Module power supply Procedure 6: Replace the Application Module disk/tape unit Procedure 7: Replace the Application Module MVME147/167 SBC card Procedure 8: Configure the Application Module MVME147 SBC card Procedure 9: Configure the Application Module MVME167 SBC card or the IPE Module Procedure 10: Replace the Application Module Procedure 11: Replace the MVME332XT or...
  • Page 11: About This Guide

    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) ¥...
  • Page 12 About this guide 553-3211-510 Standard 1.0 October 1998...
  • Page 13: Chapter 1: Overview

    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.
  • Page 14: Customer Controlled Routing

    2 Chapter 1: Overview 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.
  • Page 15 ¥ 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 ¥...
  • Page 16: Application Module Hardware Components

    4 Chapter 1: Overview 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.
  • Page 17 ¥ 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.
  • Page 18 6 Chapter 1: Overview ¥ 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 Ñ...
  • Page 19 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. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 1: Overview 7...
  • Page 20 8 Chapter 1: Overview Figure 1 Application Module in the AEMÑfront view CCR Module (left side) Power supply 553-3211-510 Standard 1.0 October 1998 Meridian Link Module (right side) Disk/tape unit: topÑtape drive bottomÑhard disk drive...
  • Page 21 Figure 2 Application Module in the AEMÑrear view Meridian Link Module Transition cards Part of chassis (cannot be ordered) Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Power sense card CAUTION Risk of system damage If you want to remove a card, you must perform the required software and hardware power-down processes.
  • Page 22 10 Chapter 1: Overview The module power distribution unit (MPDU) in each AEM provides a circuit breaker for each Application Module in the AEM so you can power down components in one module without affecting the other (see Figure 3). Figure 3 MPDU circuit breaker associations 553-3211-510 Standard 1.0 October 1998...
  • Page 23: Ipe Module Hardware Components

    IPE Module hardware components The IPE Module contains an SMM167 single board computer (SBC) card, a 240-Mbyte disk drive, a 600-Mbyte tape drive, and an IPE adapter card. Only the IPE Module is field-replaceable. SMM167 This card, one of the Motorola MVME167 family, consists of the following: ¥...
  • Page 24 12 Chapter 1: Overview ¥ SCSI indicator: This yellow LED is lit almost continuously when in use. The intensity varies according to the amount of data movement. ¥ Fail indicator: This red LED is lit when a hardware or software failure occurs on the SBC card.
  • Page 25: Tape Drive

    Tape drive The tape drive is a 600-Mbyte cassette tape drive. The tape drive cannot be replaced in the field. The following tapes are supplied with the IPE Module: ¥ a 155-Mbyte tape that provides the operating system for the IPE Module ¥...
  • Page 26: Application Module And Ipe Module Utilities

    14 Chapter 1: Overview Application Module and IPE Module utilities You access applications software by logging in as one of the following: ccrusr Use this login to perform CCR functions, such as profile and script management. maint Use this login to perform generic functions (such as start/stop applications, tape backup/restore, password administration), and to prepare the system for a power down or reset.
  • Page 27: The Ccrusr Function

    The ccrusr function You can reach the ccrusr function from within maint using the ccrusr command, or by logging in as ccrusr at the ÒConsole login:Ó prompt. The function allows you to do the following (depending on your access privilege): ¥...
  • Page 28: The Trmcnfg Function

    16 Chapter 1: Overview Table 1 AML administration commands Commands display linkctl read link save link display link change link enable link disable link status link statistics link The mlusr function offers help facilities to assist you. To use the help facility, type help (or help+command when you need help on a particular command) and press [Return].
  • Page 29: Chapter 2: Application Module Commands

    Chapter 2: Application Module commands To use the Application Module commands in this chapter, you must be logged in as a maintenance user (maint). The commands may be entered at the Application Module or IPE Module console or at a terminal attached through a modem port or a teletype (TTY) port (if available).
  • Page 30 18 Chapter 2: Application Module commands Table 2 Application Module commands Command admin applconfig applexit applstart backconfig backdata backfiles bootconfig ccrexit ccrmidnight ccrstart ccrtraffic ccrusr chgpasswd conshare diskuse editvoice exit filedelete fileverif help 553-3211-510 Standard 1.0 October 1998 Description enters link-related user session displays and modifies application configuration (customer number) (CCR only) exits the CCR application...
  • Page 31 Table 2 Application Module commands (continued) Command Description install loads the software tape onto the hard disk lanconfig allows for changing the system's ethernet configuration langconfig configures language options for CCR (CCR only) mlexit performs no useful function (Meridian Link only) mlstart performs no useful function (Meridian Link only) mlusr...
  • Page 32: Adminñenter A Link-Related Session

    20 Chapter 2: Application Module commands adminÑenter a link-related session This command allows you to enter a link maintenance session, in which you may use the commands described in Chapter 3, ÒLink maintenance commands.Ó You can also use the mlusr command to enter a link maintenance session.
  • Page 33: Applexitñexit Software Applications

    applexitÑexit software applications This command applies to CCR only. This command stops all software applications. Th operating system up and running. The applications should be shut down properly to preserve file integrity and save configurations. Example maint> applexit 05/14/92 20:34:26 Notifying CCR Application of Shutdown 05/14/92 20:34:32 Stopping CCR application Releasing Communication Resources...
  • Page 34: Backconfigñschedule Unattended Backup

    22 Chapter 2: Application Module commands backconfigÑschedule unattended backup You can schedule a backup for any future time. This is useful for performing routine backups during off-hours. You can also indicate that you wish the backup to reoccur (backup will be repeated every night or once a week, as you specify).
  • Page 35 Figure 4 Cassette tape with write protection disabled Top view of tape This side in Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 2: Application Module commands 23 Write-enabled tab position Front view of tape (the front is the side with the Meridian 1 software label)
  • Page 36 24 Chapter 2: Application Module commands Figure 5 Inserting tape into tape drive Arrow points in Blank tape Notch points down Note: Ensure you use the correct backup tape. An IPE Module uses a 600-Mbyte tape. An Application Module uses a 155-Mbyte tape. 553-3211-510 Standard 1.0 October 1998 IPE Module drive side...
  • Page 37 Note: In the following examples, <cr> indicates where you press [Return]. Also, use uppercase characters when typing the day (SUN, MON, and so on). Example 1: Scheduling a new backup maint> backconfig A backup has not been scheduled. Do you want to schedule a backup [y,n]: y Enter time in 24-hour form: 00:00Ñ23:59 Enter return for no change Change scheduling time from Ô02:00Õ...
  • Page 38 26 Chapter 2: Application Module commands Example 2: Modifying an existing backup schedule maint> backconfig Backup is scheduled for 02:05 on ALL Backup will reoccur at same time and date Do you want to modify backup schedule? [y,n] y Do you want to unschedule backup? [y,n] n Enter time in 24-hour form: 00:00-23:59 Enter a return for no change Change scheduling time from '02:05' to: 04:00...
  • Page 39: Backdatañback Up Data Files

    backdataÑback up data files You can back up configuration files and data files to cassette tapes. All data files can be loaded onto one data cassette tape. When inserting the tape into the tape drive, check to make sure that the arrow printed on the face of the cartridge is positioned toward the right side of the drive (as shown in Figure 6) and the notch points down (as shown in Figure 7).
  • Page 40 28 Chapter 2: Application Module commands Figure 7 Inserting tape into tape drive Arrow points in Blank tape Notch points down Note: Ensure you use the correct backup tape. An IPE Module uses a 600-Mbyte tape. An Application Module uses a 155-Mbyte tape. 553-3211-510 Standard 1.0 October 1998 IPE Module drive side...
  • Page 41 Chapter 2: Application Module commands 29 Example: maint> backdata Files will be backed-up from: /usr/maint/files/AMprofile /usr/maint/files/AutoStart /usr/maint/files/IncrDY /usr/maint/files/IncrTM /usr/maint/files/Port /usr/maint/files/Prefs /usr/maint/files/Speed /usr/mlusr/conf/hdlchlnk.dataf /usr/mlusr/conf/hdlcmlnk.dataf /usr/mlusr/conf/lh.config /usr/mlusr/conf/loop13DCE.d /usr/mlusr/conf/loop13DTE.d /usr/mlusr/conf/loop31DCE.d /usr/mlusr/conf/loop31DTE.d /usr/mlusr/conf/tscfg.datafile /usr/mlusr/conf/vlink.datafile /usr/mlusr/conf/x25bcf333.2 /usr/mlusr/conf/x25hlink.datafi (actual list of directories may differ depending on the application) Make sure tape is in drive When ready, enter ÔYÕ...
  • Page 42 30 Chapter 2: Application Module commands Example (continued): Starting backup Backup successful maint> 553-3211-510 Standard 1.0 October 1998 4k of usr/maint/files/AMprofile 4k of /usr/maint/files/AutoStart 4k of /usr/maint/files/IncrDY 4k of /usr/maint/files/IncrTM 4k of /usr/maint/files/Port 4k of /usr/maint/files/Prefs 4k of /usr/maint/files/Speed 4k of /usr/mlusr/conf/hdlchlnk.dataf 4k of /usr/mlusr/conf/hdlcmlnk.dataf...
  • Page 43: Backfilesñback Up Selected Data Files

    backfilesÑback up selected data files You can back up selected configuration and data files to cassette tapes. The selected files can be loaded onto one data cassette tape. When inserting the tape into the tape drive, check to make sure that the arrow printed on the face of the cartridge is positioned toward the right side of the drive (as shown in Figure 8) and the notch points down (as shown in Figure 9).
  • Page 44 32 Chapter 2: Application Module commands Figure 9 Inserting tape into tape drive Arrow points in Blank tape Notch points down Note: Ensure you use the correct backup tape. An IPE Module uses a 600-Mbyte tape. An Application Module uses a 155-Mbyte tape. 553-3211-510 Standard 1.0 October 1998 IPE Module drive side...
  • Page 45 Example: maint> backfiles (The screen clears and a list of files appears.) 1. /usr/maint/files/AMprofile 2. /usr/maint/files/AutoStart 3. /usr/maint/files/IncrDY 4. /usr/maint/files/IncrTM 5. /usr/maint/files/Port 6. /usr/maint/files/Prefs 7. /usr/maint/files/Speed 8. /usr/maint/logs/SysLog 9. /usr/maint/logs/SysLog.old 10. /usr/mlusr/conf/hdlchlnk.dataf 11. /usr/mlusr/conf/hdlcmlnk.dataf 12. /usr/mlusr/conf/lh.config 13. /usr/mlusr/conf/loop13DCE.d 14. /usr/mlusr/conf/loop13DTE.d 15.
  • Page 46: Bootconfigñdisplay And Modify Boot Configuration

    34 Chapter 2: Application Module commands bootconfigÑdisplay and modify boot configuration This command applies to CCR only. You can configure the application for automatic reboot when the system boots. By default, the software application starts automatically whenever the Application Module or IPE Module restarts. Example: enabling auto-start maint>...
  • Page 47: Ccrexitñshut Down The Ccr Application

    ccrexitÑshut down the CCR application This command applies to CCR only. This command allows you to shut down the CCR application while leaving other Application Module or IPE Module processes running. Example: maint> ccrexit 05/14/92 20:34:26 Notifying CCR Application of Shutdown 05/14/92 20:34:32 Stopping CCR application Releasing Communication Resources...
  • Page 48: Ccrmidnightñrun Midnight Routines On System

    36 Chapter 2: Application Module commands ccrmidnightÑrun midnight routines on system This command applies to CCR only. The ccrmidnight routines run every night to check that the system memory matches the disk and to put any errors or related information in the CCR log files.
  • Page 49: Ccrstartñstart Up The Ccr Application

    ccrstartÑstart up the CCR application This command applies to CCR only. This command allows you to start up the CCR application. It is not usually necessary to use a ccrstart command explicitly, because an applstart command will start all applications on an Application Module. Example: maint>...
  • Page 50 38 Chapter 2: Application Module commands Configuring a traffic report Configure a traffic report by selecting option 1 from the CCR Traffic and Statistics Reporting Utility menu to display a list of traffic report configuration options. Example: Configure Traffic Report Options Include/Exclude Script Statistics Change Interval Between Reports Change Period of Record Keeping...
  • Page 51 Enabling/disabling traffic Turn traffic reports on and off through maintenance by selecting option 2 (enable) or option 3 (disable) from the CCR Traffic and Statistics Reporting Utility menu. Enabling the reports starts the traffic recorders. Disabling the reports halts all traffic reporting activity. View traffic history Traffic reports are saved in CCR log files.
  • Page 52 40 Chapter 2: Application Module commands Example (continued): Enter the number of the function you want to perform. (Hit the <RETURN> key to EXIT) 2 7. Feb_03_94.0007 1. Feb_02_94.0001 2. Feb_02_94.0002 02/02/94 16:04:23 Feb_02_94.0002 created. 02/02/94 16:00:35 Traffic Logger shut down per OA&M request 02/02/94 15:57:18 Feb_02_94.0001 created.
  • Page 53 Example: View Traffic Report Configuration Script Statistics Reporting Interval Reporting Period Reporting State (Hit the <RETURN> key to EXIT) The Current values are those that are currently being used by the reporting facility. The New values are those that a maintenance user has edited but not yet enabled.
  • Page 54 42 Chapter 2: Application Module commands ¥ BUSYÑnumber of times a FORCE BUSY command was executed ¥ DISCONNECTÑnumber of times a FORCE DISCONNECT statement was executed ¥ QUITÑnumber of times that the script execution was completed ¥ ANSWEREDÑnumber of calls answered for the script ¥...
  • Page 55: Ccrusrñenter A Ccr User Session

    ccrusrÑenter a CCR user session This command applies to CCR only. This command enables you to enter into a CCR user session in order to manage your scripts, variables, associations, and profiles of CCR users. CCR user sessions are described in more detail in the CCR User Guide (P0747008).
  • Page 56: Chgpasswdñchange User Passwords

    44 Chapter 2: Application Module commands chgpasswdÑchange user passwords You can change the factory configured passwords for maint and application users (such as mlusr and ccrusr), and for security reasons it is recommended that you do so. Only the first eight characters of a password are checked.
  • Page 57: Conshareñmeridian 1 Console Session

    conshareÑMeridian 1 console session Use the conshare command to pass through to the Meridian 1 interface and conduct a maintenance session from your maint login session. The Application Module or IPE Module is optionally cabled to a Meridian 1 SDI port. Initially, you will be prompted to confirm whether the SDI port is correctly configured.
  • Page 58 46 Chapter 2: Application Module commands Example: maint> conshare Is the SDI port configured correctly? Use help for more information. When ready, enter 'y' to continue, or 'n' to quit: [y,n] y Enter port in the form /dev/tty0n: where n=1, 2, or 3 Enter a return for no change Change maintenance port from '/dev/tty02' to: <cr>...
  • Page 59: Diskuseñdisplay Disk Usage Statistics

    diskuseÑdisplay disk usage statistics The hard disk is formatted into system volumes, each with its special purpose. The diskuse command displays the amount of space used in each volume and is useful for diagnosing certain problems. Example: maint> diskuse FILE SYSTEM USAGE AS OF 05/24/92 20:43:16 File System /usr...
  • Page 60: Exitñlog Out

    48 Chapter 2: Application Module commands File "VPE.PRO" created. Enter the telephone number associated with the vpe session: xxxx (see Note 1) If VPE will always be used to access the same account, enter Account #: xx (see Note 2) If your UNIX account is secure, enter the Password (for automatic logon): xxxxxxxx (see Note 3) ****************************************...
  • Page 61: Filedeleteñdelete A File

    filedeleteÑdelete a file This command allows you to select files and then delete them. Example: maint>filedelete (The screen clears and a list of files appears.) 1. /usr/lib/api_headers/ambase_api.h 2. /usr/lib/api_headers/api_nwk_if.h 3. /usr/lib/hp/ambase_api.a 4. /usr/lib/hp/rose_ts.a 5. /usr/lib/hp/rtp.a 6. /usr/lib/hp/system.0 7. /usr/lib/hp/upper.a 8. /usr/lib/mot/ambase_api.a 9.
  • Page 62: Fileverifñverify System Files

    50 Chapter 2: Application Module commands fileverifÑverify system files Use this command to verify that the correct application files ¥ are present ¥ are the proper size ¥ have proper ownership and permissions ¥ are structurally correct (for dynamic data files) If the fileverif command indicates that files are missing or are present but not the correct size, there may be problems on your system.
  • Page 63: Helpñlist All Commands

    helpÑlist all commands If you type help or ? at the Òmaint>Ó prompt and press [Return], the system displays a list of the command names and a short description of each. Example: maint> help Application Module Commands admin link/association administration (same as mlusr) applconfig display and modify CCR customer configuration applexit...
  • Page 64: Installñload Software Tape Onto The Hard Disk

    52 Chapter 2: Application Module commands installÑload software tape onto the hard disk In an initial installation, this command loads the software tape onto the hard disk. This command instructs the program as to which applications are to be started, and what options are to be activated in each application. The inactive application remains on the hard disk for later activation, if the customer buys further options and obtains a new keycode.
  • Page 65 Chapter 2: Application Module commands 53 Example (continued): Note: The configuration specified is displayed, as shown in the following example. The following applications are configured: Meridian Link Large CCR The following packages are configured: Ethernet NSE software is enabled. Is this correct (y/n/q)?: y Note: Enter y to enable the NSE software, n to return to the keycode entry prompt, or q to exit without enabling.
  • Page 66 54 Chapter 2: Application Module commands Example (continued): If you made any mistakes in entering the module name and IP address, you can correct them. Would you like to re-enter the module name or IP address? [y,n]: n Entry for <module name> with address <address> added to tcpip transport provider database.
  • Page 67: Lanconfigñchange The System's Ethernet Configuration

    lanconfigÑchange the system's ethernet configuration This command allows the user to change the following information in the system's ethernet configuration: ¥ default gateway address ¥ subnet mask address ¥ host name ¥ IP address Note: It is recommended that the CCR/Meridian Link module be connected to the Ethernet LAN before you run lanconfig.
  • Page 68 56 Chapter 2: Application Module commands Example 1: System has default gateway and subnet mask pre- configured, and has NSE running maint> lanconfig Default gateway is currently configured as: 1.2.3.4 If you would like a default gateway IP address configured or changed, please enter the IP address in Internet dot notation (e.g.
  • Page 69 Chapter 2: Application Module commands 57 Example 2: System has no default gateway and no subnet mask pre- configured, and has NSE running maint> lanconfig Default gateway is not currently configured! If you would like a default gateway IP address configured or changed, please enter the IP address in Internet dot notation (e.g.
  • Page 70: Langconfigñconfigue Ccr Logon Screen Languages

    58 Chapter 2: Application Module commands langconfigÑconfigue CCR logon screen languages This command applies to CCR only. The CCR application supports one or two languages at a time on the CCR logon screen. The langconfig command lets you define one language as the default and another (which is optional) as a second language.
  • Page 71: Mlexit

    mlexit This command applies to Meridian Link only. This command performs no usable functions. mlstart This command applies to Meridian Link only. This command performs no usable functions. mlusrÑenter a link-related user session This command allows you to enter a link maintenance session, in which you may use the commands described in Chapter 3, ÒLink maintenance commands.Ó...
  • Page 72: Portconfigñconfigure Terminals And Printers

    60 Chapter 2: Application Module commands portconfigÑconfigure terminals and printers This command applies to CCR only. The CCR application provides eight ports for printers and terminals. However, IPE Modules can only use ports 7 and 8 for terminals and printers. When the system is shipped, all ports are configured for printers (off).
  • Page 73 Changing port characteristics Select option 2 from the CCR Port Configuration Utility menu to change port characteristics. Note: In the example below, <cr> indicates where you press [Return]. Example: Change Port Characteristics Enter PORT number (1 - 8): 8 Available states: off (printer) Select a state (default: ÒoffÓ): on Available BAUD Rates:...
  • Page 74: Powerdownñsafely Power Down Or Reboot The Module

    62 Chapter 2: Application Module commands powerdownÑsafely power down or reboot the module The Application Module and IPE Module are shut down first by exiting from the application, then by entering the powerdown command. You may choose either to start an express powerdown (which occurs immediately) or to set a time delay so that other users have a chance to read the warning messages and log off.
  • Page 75 The following messages appear on the screen. Do nothing while this is running. Once this message is complete, you may power down. Example: Shutdown messages Shutdown started. Mon Sep 20 12:17:20 PDT 1993 Broadcast Message from root (console) on sysV68 Mon Sep 20 12:17:21 THE SYSTEM IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged.
  • Page 76 64 Chapter 2: Application Module commands The following messages appear on the screen. Do nothing while this is running. Once this message is complete, you may power down. Example: Shutdown messages Shutdown started. Broadcast Message from root (console) on sysV68 Mon Sep 20 12:17:21 THE SYSTEM IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged.
  • Page 77 If, instead of performing an express reboot, you want to alert all users currently logged into the system of the reboot, type n and press [Return]. You are prompted to enter the number of seconds the system should wait after the warning message. Type the number of seconds that will allow the users to save their work and log off.
  • Page 78: Printconfigñconfigure Printers

    66 Chapter 2: Application Module commands printconfigÑconfigure printers This command applies to CCR only. The CCR application provides eight ports for printers and terminals. However, IPE Modules can only use ports 7 and 8 for printers and terminals. The ÒEnter PORT numberÓ prompt shows the port numbers of available ports.
  • Page 79 Adding a printer You may configure a port to run a printer by turning the state to off with the portconfig command. You may configure the printer for the application by selecting option 1 from the printconfig menu. Ensure that the baud rate set by the portconfig command is set to 9600 for Hewlett Packard (HP) printers.
  • Page 80 68 Chapter 2: Application Module commands Listing configured printers List all configured printers by selecting option 3 from the printconfig menu. Example: List of CCR Printers Printer Name ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ Printer1 (Hit the <RETURN> key when finished) Status of configured printers Display the status of all configured printers by selecting option 4 from the printconfig menu.
  • Page 81 Disabling printers Disable a printer to take it off-line temporarily without deleting printer configuration. To disable a printer, select option 6 from the printconfig menu. Example: CCR Disable Printer Operation Enter printer name: Printer1 Disabling Printer ÒPrinter1Ó... printer ÒPrinter1Ó now disabled (Hit the <RETURN>...
  • Page 82: Quitñlog Out

    70 Chapter 2: Application Module commands quitÑlog out This command allows you to log out of maint or whatever account you are using. If you logged in from the ÒConsole Login:Ó prompt, it will reappear when you log out. You can also use the exit command to log out. Example: maint>...
  • Page 83: Restartñstop And Start The Link Processes

    restartÑstop and start the link processes This command stops all link processes and all applications running within the application, then restarts the processes and applications, if desired. This command, in particular, stops and restarts the link to the Meridian 1. This command will not automatically restart applications that are external to the Application Module or IPE Module.
  • Page 84: Rootpasswdñchange The Root Password

    This command changes the root password and immediately locks everyone out of the root level. The new password is randomly generated. To find out what the new password is, contact Nortel support personnel. Example: maint> rootpasswd (Pause) maint>...
  • Page 85: Rstdatañrestore Data From Backup Tape

    rstdata—restore data from backup tape If restoring configuration files and data files becomes necessary due to catastrophic conditions such as a hard disk failure, use this command to recover the data and return to an operational state. Complete information on backup and restore procedures for a hard disk failure are provided in Chapter 8, “Recovery/replacement procedures”.
  • Page 86 74 Chapter 2: Application Module commands Example (continued): Files will be restored to: /usr/maint/files/AMprofile /usr/maint/files/AutoStart /usr/maint/files/IncrDY /usr/maint/files/IncrTM /usr/maint/files/Port /usr/maint/files/Prefs /usr/maint/files/Speed /usr/mlusr/conf/hdlchlnk.dataf /usr/mlusr/conf/hdlcmlnk.dataf /usr/mlusr/conf/lh.config /usr/mlusr/conf/loop13DCE.d /usr/mlusr/conf/loop13DTE.d /usr/mlusr/conf/loop31DCE.d /usr/mlusr/conf/loop31DTE.d /usr/mlusr/conf/tscfg.datafile /usr/mlusr/conf/vlink.datafile (actual list of directories may differ depending on the release) Note: If you are restoring from a backup tape created using the backfiles command, you will only restore the files selected during the backfiles command Please enter 'y' to do restore, or 'n' to quit: [y,n] y...
  • Page 87 Example (continued): 4k of 4k of 4k of 4k of 4k of Restore successful Configuration changed, restarting link processes. Configure Link 0 : successful Enable Link 0 : successful Application release successful Do you want to restart the application(s)? Enter ÔyÕ to restart the application(s), or ÔnÕ not to restart: [y,n] y Starting the application(s) 02/04/94 11:05:41 Starting CCR Application...
  • Page 88: Rstfilesñrestore A Set Of Files

    76 Chapter 2: Application Module commands rstfilesÑrestore a set of files This command allows you to select and restore a set of files. Note: The following example shows the command being executed on an Application Module or IPE Module with only the CCR application. For modules that have only the Meridian Link application, replace references to CCR and Customer Controlled Routing with Meridian Link.
  • Page 89: Scriptinfoñdisplay A Summary Of Script Information

    scriptinfoÑdisplay a summary of script information This command applies to CCR only. The scriptinfo command displays a complete list of scripts in the system, as well as all status information concerning those scripts. The list provides the following information: ¥ script nameÑname assigned to the script ¥...
  • Page 90: Standard 1.0 October

    78 Chapter 2: Application Module commands showidÑdisplay Meridian 1 information The showid command indicates the ID and the package authorizations for the Meridian 1 connected to the Application Module or IPE Module. The following services may appear in the list: Operations, Administration, and Maintenance software required for any Application Module or IPE Module application This service appears automatically if both Service 97 and Service 98...
  • Page 91: Startnseñactivate Ethernet Lan Support

    startNSEÑactivate Ethernet LAN support This command allows you to invoke the networking feature based on the Network Service Extension (NSE) software package. It provides remote access to the Application Module or IPE Module from a PC using the telnet utility, and transfers files from a PC to the Application Module or IPE Module using the ftp utility.
  • Page 92: Tapeinfoñdisplay Information On A System Tape

    80 Chapter 2: Application Module commands tapeinfoÑdisplay information on a system tape This command applies to CCR only. Once you insert the CCR application tape into the tape drive you can use the tapeinfo command to display information about the software before installing it on your system.
  • Page 93: Versionñdisplay Application Module Or Ipe Module Software Version

    versionÑdisplay Application Module or IPE Module software version This command indicates the current software release of each software package installed on the Application Module or IPE Module. Example: (CCR installed) maint> version The following packages are installed on this Application Module: Product: SYSTEM V/68 Base Operating System R3V7 Version:...
  • Page 94 82 Chapter 2: Application Module commands Example: (CCR and Meridian Link installed) maint> version The following packages are installed on this Application Module: Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: Type return to continue, q to quit: <cr> 553-3211-510 Standard 1.0 October 1998 SYSTEM V/68 Base Operating System R3V7 FE03.71 RM03...
  • Page 95 Example: (CCR and Meridian Link installed) (continued) Product: Host Based X.25 for NTI Version: ECK01.0 IR03 Installed: May 1 12:25 Product: X25NET333 DNLD, DRIVER/API,NETMAN Version: Release 4.1 Installed: May 1 12:21 Product: LP Support System Version: LQ02.03 Installed: May 1 10:52 Product: SYS V/68 Network Services Extension R3V7.1 Version:...
  • Page 96: Viewñdisplay Syslog And Link-Related Files

    84 Chapter 2: Application Module commands viewÑdisplay SysLog and link-related files This command enables you to choose a set of log, trace, or record files and display the set. Trace and record files are described in Chapter 3, ÒLink maintenance commands.Ó Contents of the SysLog file are described in Chapter 5, ÒApplication Module and IPE Module error messages.Ó...
  • Page 97 When you have selected all the files you wish to display at one time, press [Return] again. The contents of the files you selected appear as a continuous file. When you have finished viewing the selected files, type x and press [Return].
  • Page 98: Viewlogñdisplay Syslog File

    86 Chapter 2: Application Module commands viewlogÑdisplay SysLog file This command displays the contents of the SysLog file on the console. Contents of the SysLog file are described in Chapter 5, ÒApplication Module and IPE Module error messages.Ó Use the page up and down keys or the arrow keys to scroll through the log/trace/record file.
  • Page 99: Chapter 3: Link Maintenance Commands

    Chapter 3: Link maintenance commands Use the commands in this chapter to manage the links between the Application Module or IPE Module, Meridian 1, host computer, and Meridian Mail. The commands provide the following: ¥ Link controlÑenables and disables the link ¥...
  • Page 100: Using Link Maintenance Commands

    88 Chapter 3: Link maintenance commands Using link maintenance commands Link maintenance commands are available when you are logged in as mlusr and the CCR or Meridian Link application is running. To access the commands, do one of the following: ¥...
  • Page 101 Table 3 Link maintenance commands Command enable link link# disable link link# status link link# get links display linkctl change linkctl read linkctl filename save linkctl filename display link link# change link link# save link link# [filename] read link link# [filename] statistics link link# get associations get dn association_id...
  • Page 102 90 Chapter 3: Link maintenance commands Table 3 Link maintenance commands (continued) Command enable msgstat association_id disable msgstat association_id clear msgstat association_id [message] [message...] get msgstat association_id [message] [message...] set filter association_id message [message...] clear filter association_id message [message...] enable filter association_id disable filter association_id get filter association_id set record association_id...
  • Page 103 Table 3 Link maintenance commands (continued) Command enable record association_id disable record association_id get record association_id set monitor association_id message [message...] clear monitor association_id message [message...] enable monitor association_id disable monitor association_id get monitor association_id enable traffic association_id [period] [file_name] [lpr] [terminal] disable traffic association_id get traffic association_id...
  • Page 104 92 Chapter 3: Link maintenance commands Table 3 Link maintenance commands (continued) Command loopback test continuity test trace link link# [trace_level] [filename] trace main [trace_level] [filename] untrace link link# untrace main view viewlog help help keyword version exit quit 553-3211-510 Standard 1.0 October 1998 Description allows you to connect a cable between two ports and perform a loop test...
  • Page 105: Link Control Commands

    Link control commands There are two link control commands: enable and disable link. In this section, bolded text indicates text you input. enable link The enable link command puts the specified link in the enabled state. If the remote end is down, the link remains enabled but down. The normal response to enable is ÒEnable link link_number: successful.Ó...
  • Page 106: Link Status Commands

    94 Chapter 3: Link maintenance commands Link status commands There are two link status commands: status link and get links. status link The status link command shows whether the link is up or down, enabled or disabled. If a link status changes involuntarily, a Link Up/Down message is displayed on the system console (if mlusr is logged in) and written to the SysLog file.
  • Page 107 Examples (Meridian Link): mlusr> get links Number of Links: 3 Link ID: Link Type: MSL-1 link Machine ID: hdlcdest Link ID: Link Type: Host link Machine ID: x25dest Link ID: Link Type: MMail link Machine ID: MeridianMail mlusr> mlusr> get links Number of Links: 3 Link ID: Link Type:...
  • Page 108: Link Configuration Commands

    96 Chapter 3: Link maintenance commands Link configuration commands The link control file (linkctl) contains information on all links to the Application Module or IPE Module, specifically the link number, link type (protocol used), and the file name where the link configuration parameters are stored.
  • Page 109: Change Linkctl

    change linkctl This command allows you to maintain entries within the link control file by specifying a link to display information and then opting to delete the link, leave it unchanged, or specify changes to it. The file name includes the complete directory path to a link configuration file (which contains parameter settings for the link).
  • Page 110 98 Chapter 3: Link maintenance commands Example (continued): New Entry Type : Entry > <cr> New Control File Image: Confirm? (yes or no): y In the following example, only the host link (link 1) information is changed to indicate that it uses TCP/IP rather than X.25 protocol. Note: To change link 1 to use the TCP/IP protocol, type LAN in the link type field, and type lanhlnk in the file name field.
  • Page 111 Example (continued): Current Entry > 1 Type : "delete" to remove "<ret>" to keep as is, "<link number> <link type> <file name>" to change Entry > 1 Current Entry > 2 ASYNC Type : "delete" to remove "<ret>" to keep as is, "<link number>...
  • Page 112: Read Linkctl

    100 Chapter 3: Link maintenance commands read linkctl To use this command, you must specify the name of the link control file (from the /usr/mlusr/conf directory). You are prompted to accept or reject the new configuration. Command format: mlusr> read linkctl filename Note: The file name should follow a slash character;...
  • Page 113: Save Linkctl

    save linkctl If you change the link control information, you can use the save linkctl command to save the new information in a new file to preserve the original information in the default link control file for possible later use. The save linkctl command saves the current link control information to the file specified.
  • Page 114: Display Link

    102 Chapter 3: Link maintenance commands display link This command displays the contents (parameter settings) of a link configuration file. Table 4 (following the description of the change link command) describes the parameters in more detail. Command format: mlusr> display link link_number Example: Link 0 (LAPB) configuration mlusr>...
  • Page 115 Example: Link 1 (X.25) configuration (Meridian Link) mlusr> display link 1 Protocol: X25 Machine ID: x25dest Delay: 0 Port type: X PDN type: 44 Baud rate: 19200 RFS timer: 150 Remote address: 3 Maximum out frames (K): 7 Local DTE address: 000000990100 Flow control negotiation: 0 Outgoing packet size: 128 Outgoing window size: 2...
  • Page 116: Change Link

    See the save link command for information on saving your changes permanently. 553-3211-510 Standard 1.0 October 1998 CAUTION Risk of data loss Do not use the change link command without the direction of Nortel support personnel or Host Computer support.
  • Page 117 In the following example, the change link command is used to review all parameters associated with link 0. Only the Machine ID (from hdlcdest to SL18) and MVME705B port configuration (from DTE to DCE) are changed. Example: mlusr> change link 0 Machine ID Current hdlcdest...
  • Page 118 106 Chapter 3: Link maintenance commands Example (continued):: Remote address Options [1 3] Current 3 > <cr> Range [0 9999] Current > <cr> Maximum out frames (K) Range [1 7] Current 7 > <cr> Maximum trans attempts (N2) Range [1 9999] Current >...
  • Page 119 Table 4 Link parameters Link parameter X.25, TCP/IP, LAPB, and ASYNC parameters: Protocol* Link type* Machine ID Delay ASYNC only : Port number TCP/IP only Port X.25 and LAPB parameters: Port type* Physical DTE/DCE * Parameters marked with an asterisk (*) cannot be changed. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 3: Link maintenance commands 107 Allowed values...
  • Page 120 108 Chapter 3: Link maintenance commands Table 4 Link parameters (continued) Link parameter PDN type Maximum Frame length* Baud rate Fail timer RFS timer * Parameters marked with an asterisk (*) cannot be changed. 553-3211-510 Standard 1.0 October 1998 Allowed values (defaults in parentheses) 0, 40Ð48 300, 600, 1200, 2400,...
  • Page 121 Table 4 Link parameters (continued) Link parameter Internal address Remote address Maximum out frames Maximum trans attempts (N2) Local DTE address Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 3: Link maintenance commands 109 Allowed values (defaults in parentheses) (1), 3 1, (3) 0Ð(30)Ð9999...
  • Page 122 110 Chapter 3: Link maintenance commands Table 4 Link parameters (continued) Link parameter X.25-only parameters: Flow control negotiation Incoming packet size Outgoing packet size Incoming window size Outgoing window size Throughput negotiation used 553-3211-510 Standard 1.0 October 1998 Allowed values (defaults in parentheses) (0)Ð1 16, 32, 64, (128), 256,...
  • Page 123 Table 4 Link parameters (continued) Link parameter Incoming throughput class Outgoing throughput class Lowest LCN for DTE/DCE* Highest LCN for DTE/DCE* * Parameters marked with an asterisk (*) cannot be changed. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 3: Link maintenance commands 111 Allowed values (defaults in parentheses)
  • Page 124 112 Chapter 3: Link maintenance commands Table 4 Link parameters (continued) Link parameter Lowest LCN* Highest LCN* LOC LIC* HOC HIC* * Parameters marked with an asterisk (*) cannot be changed. 553-3211-510 Standard 1.0 October 1998 Allowed values (defaults in parentheses) 4095 0Ð(1800)Ð9999 0Ð(2000)Ð9999...
  • Page 125 Table 4 Link parameters (continued) Link parameter Allowed values (defaults in parentheses) 0Ð(1800)Ð9999 0Ð(1800)Ð9999 0Ð(600)Ð9999 0Ð(1500)Ð9999 0Ð(1300)Ð9999 Maximum T12 0Ð(3)Ð9999 retries Maximum T13 0Ð(3)Ð9999 retries Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 3: Link maintenance commands 113 Description Amount of time (in 1/10 second increments) the AM or IPE Module will...
  • Page 126: Save Link

    114 Chapter 3: Link maintenance commands save link This command saves the link parameters to the file specified. If no file name is provided, the file name specified in the link control file is used and you are asked to confirm that the default file should be overwritten (replaced).
  • Page 127: Read Link

    read link Use this command to reconfigure a link from the parameters saved in a file. If you do not provide a file name, the file name specified in the link control file is used. Configuration files can be read from any specified directory. You are asked to confirm the parameters.
  • Page 128: Link Statistics Command

    116 Chapter 3: Link maintenance commands Link statistics command The link statistics command generates a protocol-specific list of statistics for the link number you specify. Peg counts for the various frame/packet types sent or received are displayed, along with other information such as timeouts, number of active virtual circuits, and number of signal losses.
  • Page 129 Example: Link 1 (TCP/IP) statistics (Meridian Link) mlusr> statistics link 1 Host Connection Count 1 Connection Abort: Retransmission error 0 Connection Abort: User timeout 0 Connection Abort: Keep alive timeout 0 Retransmit Count 12 Packets Resized Smaller 0 Number ACKs Generated 4688 Packets Dropped: Not in window 0 Packets Dropped: Bad checksum 0 Duplicate Packets Received 1...
  • Page 130 118 Chapter 3: Link maintenance commands Example: Link 2 statistics (Meridian Link) mlusr> statistics link 2 Report Period 9887 seconds Received Packets Count: Sent Packets Count: Received Error Packets Counts: Peak Registrations 6357 Cur Processes Registered 0 Cur Total Processes Registered 0 Last Reset 0 Last Synchronization 553-3211-510 Standard 1.0 October 1998...
  • Page 131: Meridian Link Messages

    Meridian Link messages The association services commands (described in following pages of this chapter) provide a detailed view of the messages that pass across link 1. Some of these commands enable you to obtain information on particular messages, while ignoring other messages. Message types allow you to refer to specific messages when you use Meridian Link commands.
  • Page 132: Association Services Commands

    120 Chapter 3: Link maintenance commands Association services commands These commands provide information covering application associations currently established on the Application Module or IPE Module. get associations This command displays information on current active associations. The mlusr association is always shown with an application ID of ADMIN.nnnn, where nnnn is a number.
  • Page 133: Get Directory Numbers

    get directory numbers Registering DNs with the Meridian 1, using the DN Registration message, allows an application to specify DNs for which it would like to receive events. The get dn command displays one of the following: ¥ ALLÑmeaning that the application has registered all DNs within the selected customer number on Meridian 1 for the specified association ¥...
  • Page 134: Get Resource

    122 Chapter 3: Link maintenance commands get resource For some Meridian Link features, the application must acquire a resource from Meridian 1 in order to perform a certain function. For example, an application must acquire a Control DN (CDN) before it can route the call on behalf of that CDN.
  • Page 135: Message Statistics

    message statistics The statistics commands collect and display message statistics (number of each type of message flowing over the link). There are four statistics commands. These include ¥ enable message statistics collection ¥ disable message statistics collection ¥ clear messages for statistics ¥...
  • Page 136 124 Chapter 3: Link maintenance commands Disable message statistics collection This command stops the accumulation of statistics for an associationÑ assuming that the specified statistics collection had been enabled. Statistics collection can be disabled for all or selected messages. Command format: mlusr>...
  • Page 137 Get message statistics This command displays peg counts (the current statistics collected since the last get command) for specified messages on the specified association. Command format: mlusr> get msgstat association_id message [message ...] Example: To obtain the statistics collected for message mlmakecall for association ID 1: mlusr>...
  • Page 138: Filter Commands

    126 Chapter 3: Link maintenance commands filter commands Five filter commands enable you to control which Meridian Link messages pass across the link. These are ¥ set filter ¥ enable filter ¥ disable filter ¥ clear filter ¥ get filter status Type help msgtypes and press [Return] to see a list of all message types that can be selected in the messages parameter.
  • Page 139 Enable filter This command turns on filtering of messages. Before entering this command, use the set filter command to specify which message types should be filtered out. Command format: mlusr> enable filter association_id Example: To enable filtering for association_id 1: mlusr>...
  • Page 140 128 Chapter 3: Link maintenance commands Clear filter This command removes one or more message types from the list of messages to be filtered out. Command format: mlusr> clear filter association_id message [message ...] Example: To stop filtering out two messages (make call and initiate transfer), for association ID 1: mlusr>...
  • Page 141: Record Commands

    record commands Five record commands enable you to control recording of specified messages flowing across the link for an association. The messages are recorded in hexadecimal format to files on the Application Module or IPE Module hard disk (see Figure 10). The commands are as follows: ¥...
  • Page 142: Set Record

    130 Chapter 3: Link maintenance commands Figure 10 Example of a recording file : hlink (assoc id=2) Message: FF 0A 00 25 02 80 01 08 08 5E 30 08 00 08 35 30 30 36 31 08 00 08 35 30 31 31 03 70 2E 04 01 02 3F 04 01 08 : hlink (assoc id=2) Message:...
  • Page 143 Enable record This command turns on message recording. Before issuing this command, use get record to confirm the list of messages to be recorded. If necessary, use set record or clear record to modify the list. Recording stays active until you disable it or exit mlusr.
  • Page 144 132 Chapter 3: Link maintenance commands Clear record This command clears the specified message types from the list of messages to be recorded. Command format: mlusr> clear record association_id message [message ...] Example: To clear recording for two messages, makecall and calloffer, for association ID 2: mlusr>...
  • Page 145: Monitor Commands

    monitor commands The monitor commands display messages flowing on the identified association_id on the system console. The messages appear in hexadecimal format. There are five monitoring commands: ¥ set monitor ¥ enable monitor ¥ disable monitor ¥ clear monitor ¥ get monitor The format of the monitor file displayed on the console is the same as for the recording file.
  • Page 146 134 Chapter 3: Link maintenance commands Enable monitor This command turns on the message monitoring. Before using the enable monitor command, use the get monitor command to confirm the list of messages to be monitored. If necessary, use set monitor or clear monitor to modify the list.
  • Page 147 Disable monitor This command turns off message monitoring. It does not alter the list of messages that were set for monitoring. Command format: mlusr> disable monitor association_id Example: To disable monitoring for messages set for association_id 1: mlusr> disable monitor 1 Disable monitor successful mlusr>...
  • Page 148 136 Chapter 3: Link maintenance commands Get monitor status This command displays the current monitor status and a list of the messages to be monitored. Command format: mlusr> get monitor association_id Example: To get the status for association_id 1: mlusr> get monitor 1 Messages Monitored : Make call Answer...
  • Page 149: Traffic Commands

    traffic commands The traffic commands count messages flowing to and from an application over a period of time. There are three traffic commands, as follows: ¥ enable traffic ¥ disable traffic ¥ get traffic Enable traffic This command turns on traffic reporting for the specified association. Command format: mlusr>...
  • Page 150 138 Chapter 3: Link maintenance commands Disable traffic This command turns off the traffic reporting for the specified association. Command format: mlusr> disable traffic association_id Example: To disable traffic reporting for association_id 1: mlusr> disable traffic 1 Get traffic This command displays the traffic information (period, filename, printer and terminal) for the specified association, which has traffic turned on.
  • Page 151 Example: Traffic report Application Message Traffic Report Application = ADMIN.4017; Association = 1; Service(s) = 1 MSL-1 Link = None; Host Link = None; Meridian Mail Link = None Filename = traffic.1; Time period = 5 minutes Meridian Link Messages ====================== <0100>...
  • Page 152 140 Chapter 3: Link maintenance commands Example: Traffic report (continued) <0600> messages: EnlFil EnlFilRp DisFil 00000001 00000001 00000001 00000001 00000000 00000000 00000000 00000000 GetFil GetFilRp 00000001 00000001 <1300> messages: Polling ContTest ContRp 00000000 00000001 00000001 00000000 <1600> messages: EnlTraf EnlTraRp DisTraf DisTraRp GetTraf GetTraRp 00000000 00000001 00000000 00000000 00000000 00000000 Summary: Total Meridian Link messages sent by application: 16...
  • Page 153: Link Tracing Commands

    Link tracing commands Unlike message recording or monitoring, which record or display messages flowing on a specified stream (association ID), message tracing records all messages flowing on a link or through the system. A link trace writes application layer messages flowing over the link to a file with a hexadecimal format.
  • Page 154: Untrace Link

    142 Chapter 3: Link maintenance commands untrace link Use untrace link to turn off a trace that was initiated by the trace link command. Command format: mlusr> untrace link link_number untrace main The untrace main to turn off a trace that was initiated by the trace main command.
  • Page 155 Example: trace link 0 05/20/92 20:41:33 to PBX CALLDIS link 0 03 15 00 00 00 02 16 2E 00 01 00 01 00 00 00 00 00 00 02 00 AA 15 05/20/92 20:41:34 from PBX USM link 0...
  • Page 156 144 Chapter 3: Link maintenance commands Example: trace link 2 05/27/93 12:43:37 from mmlh 2 Trace Link Response 2C 05 19 E9 00 00 00 00 00 00 00 00 00 00 00 00 FF 0A 00 10 01 80 05 02 10 00 1A 03 02 71 03 00 05/27/93 12:44:53 to mmlh link 2 (assoc id=69) Meridian Mail Msg: LH:AM Register...
  • Page 157: Link Testing Commands

    Link testing commands Two commands test the physical continuity of links: continuity test and loopback test. continuity test This command allows you to test end to endÑfrom the Application Module or IPE Module software to the Meridian 1, including all applications in the module and host computer.
  • Page 158: Loopback Test

    146 Chapter 3: Link maintenance commands loopback test This test verifies the condition of synchronous links, typically link 0 (AML) and link 1 (host link) on the Application Module or IPE Module. If the Meridian Link system is running with a host link over Ethernet TCP/IP, the user has the option to run a loopback ping test which invokes the UNIX ping command to verify that the host is operational.
  • Page 159 Command format: mlusr> loopback test Example: This command tests links 0 and 1. mlusr> loopback test Enter first Port/Link number (e.g. 0, 1, or ÔqÕ): 0 Enter second Port/Link number (e.g. 0, 1, or ÔqÕ): 1 Please plug in a straight cable between the ports Ready (yes or no): y Performing Loopback Test: Link 0 (DTE) and Link 1 (DCE) Note: 0 and 1 are the port numbers that the user enters.
  • Page 160 148 Chapter 3: Link maintenance commands If TCP/IP is running, the loopback test invokes the UNIX ping command from the mlusr session. You are then prompted to enter the IP address or the host machine name. Note: You can use the terminalÕs interrupt character to escape out of ping.
  • Page 161 Example of an unsuccessful ping operation: This command tests links 0 and 1. mlusr> loopback test Would you like to ping the host machine or perform the loopback test between ports 0 and 1 on the AM? Enter p to ping, <cr> to perform loopback (default): p Note: If a failure occurs in checking for TCP/IP, or if the user chooses <cr>...
  • Page 162: File Viewing Commands

    150 Chapter 3: Link maintenance commands File viewing commands Two commands are provided for viewing files: view and viewlog. view This command enables you to choose a set of log, trace, or record files and to display the set. Trace and record files are described earlier in this chapter, and the SysLog file is described in Chapter 5, ÒApplication Module and IPE Module error messages.Ó...
  • Page 163: Viewlog

    Viewing a file The following commands are available to you while you are viewing a file: or u or d Prev or U Next or D viewlog This command displays the contents of the current SysLog file. This command is identical to the viewlog command in maint. Command format: mlusr>...
  • Page 164: Miscellaneous Commands

    152 Chapter 3: Link maintenance commands Miscellaneous commands The miscellaneous commands are exit, quit, help, and version. The exit and quit commands are interchangeable. exit This command ends the current mlusr session. quit This command ends the current mlusr session. help Provides a summary of all available commands, organized by topic.
  • Page 165 Figure 11 Link maintenance help command Meridian Link Administration Command Summary note: | denotes or, [...] denotes optional, {...} denotes choice Link configuration and control commands: get links #shows configured links display|change linkctl #manage link control file read|save linkctl [file_name] #read/save from/to a different file display|change link link_number #show/change link parameters enable|disable|status|statistics link link_number #link operations read|save link link_number [file_name] #read/save link parameters...
  • Page 166 154 Chapter 3: Link maintenance commands Figure 11 Link maintenance help command (continued) Examples: mlusr> status link 1 mlusr> set monitor 2 all mlusr> enable monitor 2 mlusr> display link 1 mlusr> trace link 1 mlusr> get traffic 1 mlusr> disable traffic 1 mlusr>...
  • Page 167: Version

    version This command indicates the current software release of any applications running on the Application Module or IPE Module. Example: (CCR and Meridian Link installed) mlusr> version The following packages are installed on this Application Module: Product: SYSTEM V/68 Base Operating System R3V7 Version: FE03.71 RM03 Installed:...
  • Page 168 156 Chapter 3: Link maintenance commands Example: (CCR and Meridian Link installed) (continued) Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: Product: Version: Installed: mlusr> 553-3211-510 Standard 1.0 October 1998 Host Based X.25 for NTI ECK01.0 IR03 May 1 12:25 X25NET333 DNLD, DRIVER/API,NETMAN...
  • Page 169: Chapter 4: Diagnosing Faults

    In some cases, you are referred to specific recovery or replacement procedures, which are described in Chapter 8, ÒRecovery/replacement procedures.Ó If a problem persists, contact your Nortel support personnel. Quick reference fault isolation Verify this: Is the module powered up?
  • Page 170: Diagnostic Procedure 1: Power Fault Suspected

    Chapter 4: Diagnosing faults Diagnostic procedure 1: Power fault suspected (Application Module) Is the Meridian 1 column powered up? You hear the blower units at the base of the column. Go to DANGER Danger of Electric Shock All power cabling changes and checks should be made with the column and/or module power turned off.
  • Page 171 Diagnostic procedure 1 Power fault suspected (Application Module) (continued) Does the pedestal breaker remain on? Is correct power supply breaker for AM on? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Pedestal breaker trips repeatedly. Refer to Application Equipment Module Installation Guide (553-3201-200).
  • Page 172 Chapter 4: Diagnosing faults Diagnostic procedure 1 Power fault suspected (Application Module) (continued) AM power supply breaker stays on? Do LEDs on AM cards and/or disk/tape unit light? Go to 553-3211-510 Standard 1.0 October 1998 Breaker trips repeatedly. Replace power supply. See Procedure 5: Replace the Application Module power supply.
  • Page 173 Diagnostic procedure 1 Power fault suspected (Application Module) (continued) Cables to AM power supply properly connected? AM and column power supply properly connected? AM power supply and disk/tape unit properly connected? Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 161 Connect cables securely.
  • Page 174 Chapter 4: Diagnosing faults Diagnostic procedure 1 Power fault suspected (Application Module) (continued) LEDs on disk/tape unit light or flash briefly? Go to 553-3211-510 Standard 1.0 October 1998 Connections secure between AM power supply & disk/tape unit? Replace Application Module. See Procedure 14: Replace the Application Module.
  • Page 175 Diagnostic procedure 1 Power fault suspected (Application Module) (continued) Do LEDs on any AM cards light or flash briefly? Stop Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Connections secure between AM power supply and AM? Replace Application Module.
  • Page 176: Diagnostic Procedure 2: Power Fault Suspected

    Chapter 4: Diagnosing faults Diagnostic procedure 2: Power fault suspected (IPE Module) Option 11 Meridian 1? Meridian 1 cabinet powered Go to 553-3211-510 Standard 1.0 October 1998 Meridian 1 column powered Check Meridian 1 Option 11 cabinet power. Refer to Application Equipment Module Installation Guide (553-3201-200).
  • Page 177 Diagnostic procedure 2 Power fault suspected (IPE Module) (continued) IPE Module powered up? Check for PWR xxx messages at the Meridian 1 system console. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Press the power push button on the IPE Module face plate.
  • Page 178 Chapter 4: Diagnosing faults Diagnostic procedure 2 Power fault suspected (IPE Module) (continued) Does the pedestal breaker remain on? Go to 553-3211-510 Standard 1.0 October 1998 Pedestal breaker trips repeatedly. Refer to Application Equipment Module Installation Guide (553-3201-200). Review environmental conditions to ensure they are within specification and blowers function...
  • Page 179: Diagnostic Procedures 3 And 4: Card Fault Suspected

    Diagnostic procedures 3 and 4: Card fault suspected Refer to the following figures for status information on LED indicators at the front of the Application Module and IPE Module. Figure 12 Application Module LED status indicators under normal operation MVME 147SA-1 FAIL STATUS...
  • Page 180 Chapter 4: Diagnosing faults Figure 13 IPE Module status indicators under normal operation 553-3211-510 Standard 1.0 October 1998 SCSI ABORT SCSI RESET FAIL Legend: Flashing *when used...
  • Page 181: Reseating A Card

    Reseating a card To reseat a card, remove the card using the extractors at top and bottom. Pull out several inches. Using both hands, push in firmly, applying pressure to the center of the card where the screw is located, until faceplate is flush with adjacent cards and extractors have returned to level position.
  • Page 182 Chapter 4: Diagnosing faults Diagnostic procedure 3 Card fault suspected (Application Module) Do any LEDs light on the MVME147/167 SBC card? Go to 553-3211-510 Standard 1.0 October 1998 Seat the cards firmly in the module. Ensure that the power cable for the column is connected to the power source.
  • Page 183 Diagnostic procedure 3 Card fault suspected (Application Module) (continued) Red LED lit on the MVME147/167 SBC card? If possible, perform a software powerdown. See Procedure 1: Software powerdown. Press the red reset button on the SBC card and wait for the system to boot.
  • Page 184 Chapter 4: Diagnosing faults Diagnostic procedure 3 Card fault suspected (Application Module) (continued) Boot process gets past ÒTesting CompleteÓ? Does ÒConsole Login:Ó prompt appear? Is red LED lit on the MVME147/167 SBC card? 553-3211-510 Standard 1.0 October 1998 Replace the MVME147/167 SBC card.
  • Page 185 Diagnostic procedure 3 Card fault suspected (Application Module) (continued) Green LED lit on the MVME147/167 SBC card? Yellow LED flashing on the MVME147/167 SBC card? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 173 Restart the AM.
  • Page 186 Chapter 4: Diagnosing faults Diagnostic procedure 3 Card fault suspected (Application Module) (continued) Yellow LED on MVME147/167 SBC card lit steadily? Applications appear to be running properly? No immediate action is necessary. Monitor the applications. 553-3211-510 Standard 1.0 October 1998 Note: A steadily lit yellow LED on the MVME147/167...
  • Page 187 Diagnostic procedure 3 Card fault suspected (Application Module) (continued) Red LED lit on MVME333-2 XCC card? Can AM establish a LAPB or X.25 connection? Replace the card. See Procedure 10: Replace the MVME333-2 XCC card. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Note: A lit red LED on the MVME333-2 XCC card indicates that the card is defective or the...
  • Page 188: Diagnostic Procedure 4: Card Fault Suspected

    Chapter 4: Diagnosing faults Diagnostic procedure 4: Card fault suspected (IPE Module) Do any LEDs light on IPE Module? Is the FAIL indicator Replace the IPE Module. See Procedure 16: Replace the IPE Module. 553-3211-510 Standard 1.0 October 1998 IPE Module powered down? Power down the IPE...
  • Page 189 Diagnostic procedure 4 Card fault suspected (IPE Module) (continued) Boot process gets past ÒTesting completeÓ? Does ÒConsole login:Ó prompt appear? Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Replace the IPE Module. See Procedure 16: Replace the IPE Module.
  • Page 190: Diagnostic Procedure 5: System Console Fault Suspected

    Chapter 4: Diagnosing faults Diagnostic procedure 5: System console fault suspected This procedure applies to the system console only. Is the console supported by AM or IPE Module applications? Is the console powered on? Console completes its start-up self test? Go to 553-3211-510 Standard 1.0 October 1998 Replace the console...
  • Page 191 Diagnostic procedure 5 System console fault suspected (continued) Is CAPS LOCK off? Are the terminal settings correct? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 179 Turn CAPS LOCK off; press the Control and ÒdÓ...
  • Page 192 Chapter 4: Diagnosing faults Diagnostic procedure 5 System console fault suspected (continued) Does the terminal pass the test? See Terminal test box. Is the console cable correctly connected? Go to 553-3211-510 Standard 1.0 October 1998 Replace the terminal. Connect properly. See ÒMeridian Link/CCR interface cablingÓ...
  • Page 193 Diagnostic procedure 5 System console fault suspected (continued) Are internal cables connected properly? Was system running when console fault appeared? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 181 Connect MVME712 card properly. See ÒMeridian Link/CCR interface cablingÓ...
  • Page 194 Chapter 4: Diagnosing faults Diagnostic procedure 5 System console fault suspected (continued) ÒConsole LoginÓ appears if you press Return a few times? Stop 553-3211-510 Standard 1.0 October 1998 Press the Setup key and select ÒClear CommÓ. Go to...
  • Page 195 Diagnostic procedure 5 System console fault suspected (continued) ÒConsole LoginÓ appears when you press Break? See Note. Stop One or more of these are defective. Replace each item in turn until output appears at the system console: ¥ cable from Application Module or IPE Module to system console ¥...
  • Page 196: Diagnostic Procedure 6: System Start-Up Problem

    Chapter 4: Diagnosing faults Diagnostic procedure 6: System start-up problem Typical start-up messages are listed here, along with points at which a problem could occur. To see the start-up messages, restart the Application Module or IPE Module using Procedure 2: SBC restart. Note: The illustrations in this section are for the Application Module MVME167 card or IPE Module.
  • Page 197 If ÒLoading: Operating SystemÓ is not displayed, UNIX was probably not installed correctly. If it is determined that UNIX was not installed correctly, go to ÒSoftware reinstallationÓ for installation instructions. Loading: Operating System If ÒLoading: Operating SystemÓ is the last message displayed and the system seems to be frozen, the SCSI bus may need to be reset.
  • Page 198 Chapter 4: Diagnosing faults Check for the following problem indicators during system start-up: ¥ Fail (red) LED on the Application Module MVME147/167 card remains lit after system start-up is completedÑreplace the MVME147/167 card and reboot ¥ Fail (red) LED on the IPE Module remains lit after system start-up is completedÑreplace the IPE Module, reload the software and reboot ¥...
  • Page 199: Diagnostic Procedure 7: Dial-Up Problem

    Diagnostic procedure 7: Dial-up problem Do you have an IPE Module or an MVME712M or A card, with an external modem? (IPE Module, MVME712M, or MVMV712A with external modem) Is the modem connected to a telephone line? Did the calling party dial the correct number? Go to...
  • Page 200 Chapter 4: Diagnosing faults Diagnostic procedure 7 Dial-up problem (continued) Is the modem operational? See ÒTesting the modemÓ box. Go to Testing the modem Make a telephone call to the modem. You should hear a high-pitched tone when the modem answers. 553-3211-510 Standard 1.0 October 1998 Do you hear continuous ringback...
  • Page 201 Diagnostic procedure 7 Dial-up problem (continued) Is there a Òlogin:Ó prompt? Stop Testing for applications 1. Log in as maint. 2. Type version and press Return. 3. Verify that there is an entry in the list for your application. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Is your console set up correctly? applications running...
  • Page 202: Diagnostic Procedure 8: Application Terminal Problem

    Chapter 4: Diagnosing faults Diagnostic procedure 8: Application terminal problem This procedure applies to CCR only. Does any terminal function correctly Go through the following procedures for each faulty terminal. Replace a working terminal with this one. Does it function? (Terminal or modem problem.)
  • Page 203 Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Is the system using an IPE Module? Replace the IPE Module. See Procedure 16: Replace the IPE Module. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 191 Reseat the affected MVME332XT(s)
  • Page 204 Chapter 4: Diagnosing faults Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Is the terminal connected through a modem? Is the modem powered on? Go to 553-3211-510 Standard 1.0 October 1998 Is the terminal a VT220-compatible ASCII terminal? Go to...
  • Page 205 Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Are all modem cable connections secure? Is there a dial tone on each modem line? Modem on Application Module or IPE Module set to auto-answer mode? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 193 Connect all modem...
  • Page 206 Chapter 4: Diagnosing faults Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Attach the failing terminal directly to an AM or IPE Module port. Does it function? Note: An IPE Module port is on an NT1R03 octopus (Terminal cable.
  • Page 207 Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Is the terminal supported by CCR? Is the terminal powered on? Terminal completes its start-up self test? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 195 Replace the terminal with an appropriate...
  • Page 208 Chapter 4: Diagnosing faults Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Are the terminalÕs settings correct? Does the terminal test pass? See the ÒTerminal testÓ box. Go to 553-3211-510 Standard 1.0 October 1998 Verify and correct the settings.
  • Page 209 Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Are all cable connections secure? Is the terminal functioning? Stop Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 197 Connect properly. See ÒMeridian Link/CCR interface cablingÓ...
  • Page 210 Chapter 4: Diagnosing faults Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Is the PC powered on? Does the PC boot successfully? Does Reflection 4+ run correctly? 553-3211-510 Standard 1.0 October 1998 Connect the PC to a power source and turn it on.
  • Page 211 Diagnostic procedure 8 Application terminal problem (continued) This procedure applies to CCR only. Attach failing terminal directly to an AM or IPE Module port. Does it work? (Port problem) Is the system using an (IPE Module) Check the connections of the affected NT1R03 octopus cable.
  • Page 212: Diagnostic Procedure 9: Printer Faults

    Chapter 4: Diagnosing faults Diagnostic procedure 9: Printer faults This procedure applies to CCR only. Does any printer function correctly? Go through the following procedures for each faulty printer. Connect printer in place of a working one. Does it function? (Printer problem) Go to...
  • Page 213 Diagnostic procedure 9 Printer faults (continued) This procedure applies to CCR only. Is the system using an IPE Module? Replace the IPE Module. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 201 Reseat the affected MVME332XT(S) cards.
  • Page 214 Chapter 4: Diagnosing faults Diagnostic procedure 9 Printer faults (continued) This procedure applies to CCR only. Is the printer supported by CCR? Is the printer powered on? Does the printer complete its start-up self test? Go to 553-3211-510 Standard 1.0 October 1998 Replace the printer with an appropriate printer type.
  • Page 215 Diagnostic procedure 9 Printer faults (continued) This procedure applies to CCR only. Is the printer ONLINE? Paper in the tray and paper jam light off? Are all cable connections secure? Go to Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 4: Diagnosing faults 203 Press the ONLINE button.
  • Page 216 Chapter 4: Diagnosing faults Diagnostic procedure 9 Printer faults (continued) This procedure applies to CCR only. Is the printer configured correctly on the module? Does the printout look appropriate? Stop 553-3211-510 Standard 1.0 October 1998 Use the printconfig command to configure the printer.
  • Page 217 Diagnostic procedure 9 Printer faults (continued) This procedure applies to CCR only. Attach the failing terminal directly to a module port. Does it work? (Port problem) Is the system using an AM? (IPE Module) Check the connections of the affected NT1R03 octopus cable.
  • Page 218: Disk/Tape Drive Unit Faults

    Chapter 4: Diagnosing faults Disk/tape drive unit faults Hard disk drive read/write fault If the following error message appears repeatedly on the system console, the hard disk drive is defective and needs to be replaced: page read error on integral hard disk #, partition # To replace the IPE Module hard disk, you must replace the IPE Module.
  • Page 219: Login Failure

    Login failure Once UNIX has booted, you can log in with one of the login IDs described in Chapter 1, ÒOverview.Ó The following example shows how to log in by entering the desired login ID at the UNIX login prompt. The default password for each login ID is the same as the login ID.
  • Page 220: Difficulty Logging In As Maint

    Application Module has restarted. Log in as maint and enter the following command to determine if CCR is configured to automatically start: ¥ If you still cannot log in as ccrusr, contact your Nortel support personnel. Difficulty logging in as maint If the login is successful, the Òmaint>Ó prompt appears.
  • Page 221: Difficulty Logging In As Mlusr

    Difficulty logging in as mlusr You can login to mlusr at the ÒConsole login:Ó prompt or by using the mlusr command from maint. If the login is successful and the Òmlusr>Ó prompt appears, the system is ready to accept additional commands. ¥...
  • Page 222: Link Failure

    Chapter 4: Diagnosing faults Link failure The Application Module or IPE Module supports three links: ¥ Link 0, an LAPB link to the Meridian 1 (AML) ¥ Link 1, an X.25 or a TCP/IP link to a host computer (Meridian Link only) ¥...
  • Page 223 For X11 Release 17 /X11 International Phase 7 or earlier software onlyÑcheck link status from the Meridian 1. Refer to X11 Input/Output Guide (NTP 553-3001-400) for more information, if necessary. Example: Link is attached to ESDI port 8 Substitute the port number in your configuration for the digit 8 in this example.
  • Page 224 Chapter 4: Diagnosing faults For X11 Release 18 or later software onlyÑcheck link status from the Meridian 1. Refer to X11 Input/Output Guide (NTP 553-3001-400) for more information, if necessary. Example: Link is attached to ESDI or MSDL port 8 Substitute the port number in your configuration for the digit 8 in this example.
  • Page 225 Meridian 1 will be displayed. ¥ Ensure that the list includes entries for the software packages. If the required packages are not listed, contact your Nortel support personnel. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide...
  • Page 226 If the Meridian 1 machine (system ID) does not match the machine ID given in response to the showid command, the AML cannot function. Contact your Nortel support personnel for the correct Application Module software. Check ESDI or MSDL port configuration on the Meridian 1.
  • Page 227 ¥ The CMS number is an ESDI or MSDL port number between 0 and 15. ¥ Set LD17 prompts as described in the Meridian Link/Customer Controlled Routing Installation and Upgrade Guide (NTP 553-3202-210). Check the ESDI or MSDL card option settings. ¥...
  • Page 228 Chapter 4: Diagnosing faults 12 For an Application Module, replace the MVME705B transition card, using the following procedures: ¥ ¥ 13 Start up the application by logging in as maint, typing pressing [Return]. Redundant Meridian Link only 14 Manually switch the active link over to the standby link in LD 48. See Chapter 12, ÒMeridian 1 configuration for Meridian Link/CCRÓ...
  • Page 229: X.25 Host Computer Link (Link 1) Will Not Establish

    X.25 host computer link (Link 1) will not establish This section applies to Meridian Link only. The following section describes the steps to take if the X.25 Host Link between the host computer and the Application Module or IPE Module does not establish.
  • Page 230 Nortel neither supplies nor recommends a particular make or model for this purpose. If problems exist with the external modems, Nortel recommends that the customer call service representatives for the modem equipment. (A common symptom for an excessive cable length is that the link will establish for only a short period of time.) See the Meridian Link/Customer...
  • Page 231 Check the Host Link configuration parameters. ¥ Log in as mlusr and use the display link 1 command to display the current configuration. mlusr> display link 1 The following display appears (default values are shown): Protocol: Machine ID: x25dest Delay: Port type: PDN type: Baud rate:...
  • Page 232 Chapter 4: Diagnosing faults 553-3211-510 Standard 1.0 October 1998 This parameter depends on the type of X.25 network PDN type used by the host computer. The possible values are as follows: 0 Ñ LAPB 40 Ñ DATEX-P (Germany) 41 Ñ TRANSPAC (France) 42 Ñ...
  • Page 233 Remote address This should be identical to the host computer configuration. It specifies the frame recovery time (in 1/10 second increments). Maximum out frames (K) computer configuration. It specifies the LAPB window size. Maximum trans attempts (N2) the host computer configuration. It specifies the maximum number of retries to complete a transmission.
  • Page 234 Chapter 4: Diagnosing faults 553-3211-510 Standard 1.0 October 1998 Lowest LCN for DTE/DCE circuit number that will be assigned for an incoming (if DTE) or outgoing (if DCE) X.25 call request. It is not used by the Application Module. The default value is -1. Highest LCN for DTE/DCE virtual circuit number that will be assigned for an incoming (if DTE) or outgoing (if DCE) X.25 call request.
  • Page 235 This specifies (in 1/10 second increments) the amount of time the application will wait for an X.25 Clear Confirmation packet after sending an X.25 Clear Request packet to the host (T23 for DTE). This specifies (in 1/10 second increments) the amount of time the application will wait for a packet with any P(R) value after sending an X.25 Data packet to the host (T24 for DTE).
  • Page 236 Chapter 4: Diagnosing faults If modems are used, both the Application Module and the host computer connections should be configured as DTE. Perform the following steps to configure the Host Link (link 1) on the Application Module as DCE or DTE. ¥...
  • Page 237: Tcp/Ip Host Computer Link (Link 1) Will Not Establish

    Ñ Restart the application. If neither of the above steps gives you the message ÒLink 1: UpÓ, contact your Nortel support personnel. If the response is ÒLink 1 : DisabledÓ, enable the link by typing enable link1 in the mlusr prompt.
  • Page 238: Meridian Mail Link (Link 2) Will Not Establish

    Chapter 4: Diagnosing faults Meridian Mail Link (Link 2) will not establish The following section describes the steps to take if the link between Meridian Mail and the Application Module does not establish. Check link status from the Meridian Link. ¥...
  • Page 239: Meridian Link Application Malfunction

    Meridian Link application malfunction An application malfunction denotes the failure of the host-based application. Given that the base Application Module or IPE Module is operational (UNIX is loaded, application software is running, and both link 0 and link 1 are up), if the host application does not perform as desired, the failure is classified as an application failure.
  • Page 240 Chapter 4: Diagnosing faults Normally there will be at least two messages displayed: an Application Registration message and an Application Registration Response message. If there is no response, verify that the association ID located in byte five of the Application Registration message is set to Also verify that the following bytes appear somewhere in the Application Registration message: 05 09 78 32 35 64 65 73 74.
  • Page 241 ¥ 0006 indicates information is missing from the Application Registration message. Verify that the message contains at least the following information Header Application protocol Application ID Service ID ¥ 0008 indicates the message length contained in bytes three and four of the Application Registration message is not correct. The message length is the size in bytes of the entire message.
  • Page 242: Meridian Link Call Processing Functions Fail

    Chapter 4: Diagnosing faults ¥ ¥ Meridian Link call processing functions fail If an applicationÕs attempts to control calls (for example, Make Call, Release, Answer) at a DN fail, it is possible that the Meridian 1 database or the application software is not configured correctly, or that the application software is not equipped with the required packages.
  • Page 243 Check Meridian Link Module software option services The application software tape lists the options or services purchased. ¥ Inbound and outbound call management (package 96) This package cannot be ordered but will be supplied if packages 97 and 98 are both ordered (for compatibility with older host applications).
  • Page 244 Chapter 4: Diagnosing faults ¥ Make sure the application is registered with the appropriate service: Ñ 95 = Pass-through OR Ñ 96 = inbound and outbound OR Ñ 97 = inbound call management Ñ 98 = outbound call management Ñ 100 = host enhanced routing Ñ...
  • Page 245: Meridian Link-Based Applications Do Not Receive Expected Messages

    Meridian Link-based applications do not receive expected messages Some of the messages received by a Meridian Link-based application from the Meridian 1 are unsolicited due to events that occur on devices (ringing, answering, and so on). Some messages are responses from the application software after the application has requested a service.
  • Page 246 Chapter 4: Diagnosing faults Check application and DN registration The application must register with the application software to gain access to the application services. ¥ Log in as mlusr. ¥ Use the get associations command to display all the applications and their association IDs.
  • Page 247 Check Meridian 1 configuration If the telephone configuration on the Meridian 1 is not correct, the Meridian 1 will not send any messages to the Application Module or IPE Module. For the application to receive a particular type of message, the feature must be turned on.
  • Page 248 Chapter 4: Diagnosing faults 553-3211-510 Standard 1.0 October 1998...
  • Page 249: Chapter 5: Application Module And

    SysLog file will be displayed on the system console. If you observe a message that is not described in this guide, contact your Nortel support personnel for assistance.
  • Page 250: Messages That Appear On The System Console

    238 Chapter 5: Application Module and IPE Module error messages Note: The use of single quotation marks in a message (included in one of the tables in this chapter) indicates that either a command or parameter specified by you or the system is being referenced in the message.
  • Page 251: Application Messages

    Indicates an internal application problem. Use Procedure 2: SBC restart. Indicates an internal application problem. Tell your Nortel support personnel there is no service in TSprofile and request new application software. There is a problem writing to an application trace file.
  • Page 252 95 percent. Indicates an internal application problem. Tell your Nortel support personnel there is no service in TSprofile and request new application software. There is a problem writing to the SysLog file. The file system may be full.
  • Page 253 Chapter 5: Application Module and IPE Module error messages 241 Table 6 Application messages that appear on the console (continued) Message msgsnd ÔUNIX error msgÕ tsasctbl: init_assoc_tbl: shmget( ) ÔUNIX error msgÕ tsdntbl: init_dn_rout_tbl: shmget(Ê) ÔUNIX error msgÕ tslnktbl: init_link_tbl: shmget( ) ÔUNIX error msgÕ...
  • Page 254 242 Chapter 5: Application Module and IPE Module error messages Table 6 Application messages that appear on the console (continued) Message tsmsgio: set_up_ipc: msgget(Q_APPL_KEY, 0666|IPC_CREAT) ÔUNIX error msgÕ tsmsgio: send_out_msg: msgsnd( ) ÔUNIX error msgÕ tsmsgio: check_q: msgctl( ) ÔUNIX error msgÕ tssrvtbl: init_serv_tbl( ): shmget ÔUNIX error msgÕ...
  • Page 255: Maint Messages

    Chapter 5: Application Module and IPE Module error messages 243 maint messages The following is a summary of the messages (errors and warnings) displayed on the console while you are using maint commands. In any case where it is likely that the application software has not been installed successfully, reinstall the application software using the reinstallation procedure.
  • Page 256 Reinstall the CCR software. The data in the AMprofile has been corrupted. Reinstall the CCR software or consult your Nortel support personnel. The add process was not found. It is likely that the application software has not been installed successfully.
  • Page 257 Chapter 5: Application Module and IPE Module error messages 245 Table 7 maint messages that appear on the console (continued) Command Message applstart Customer Controlled Routing was (continued) not started successfully switch link process missing: tsroot Application(s) were not started successfully.
  • Page 258 No file was selected. No files are available for backup. The command which invoked the selector is programmed incorrectly. Report the failure to your Nortel support personnel. The selector cannot obtain enough memory to function. Report the failure to your Nortel support personnel.
  • Page 259 Chapter 5: Application Module and IPE Module error messages 247 Table 7 maint messages that appear on the console (continued) Command Message ccrstart ERROR: CCR terminated due to memory allocation failure ERROR: CCR terminated due to a problem reading the AMprofile. ERROR: CCR terminated due to invalid CCR packaging.
  • Page 260 248 Chapter 5: Application Module and IPE Module error messages Table 7 maint messages that appear on the console (continued) Command Message ccrstart CCR ccrlog process is already (continued) running. CCR mmgr process is already running. CCR cpexec process is already running.
  • Page 261 Chapter 5: Application Module and IPE Module error messages 249 Table 7 maint messages that appear on the console (continued) Command Message ccrusr ERROR: Insufficient memory for profile data. Exiting user session. ERROR: AMprofile cannot be read properly. Exiting user session. ERROR: A CCR application has not been installed properly.
  • Page 262 No files are available to be deleted. The command which invoked the selector is programmed incorrectly. Report the failure to your Nortel support personnel. The selector cannot obtain enough memory to function. Report the failure to your Nortel support personnel.
  • Page 263 Either the specified file has become corrupted or an update file was deliberately placed in the system to correct a problem. Consult your Nortel support personnel for assistance with this condition. This message appears even if no errors are found. If at least one error is listed, the static file tests found at least one file that failed.
  • Page 264 252 Chapter 5: Application Module and IPE Module error messages Table 7 maint messages that appear on the console (continued) Command Message fileverif Permissions and ownership tests (continued) found failures listed above. /usr/maint/file/AutoStart file has incorrect value 'value' /usr/maint/files/IncrDY file has incorrect value 'value' /usr/maint/files/Port file has incorrect value 'value'...
  • Page 265 Chapter 5: Application Module and IPE Module error messages 253 Table 7 maint messages that appear on the console (continued) Command Message langconfig Error: secondary language cannot (continued) be the same as the default language. Select again. Incorrect input -- select again. Error: need to define environment variable: CCRUSR_HOME_PATH Error: need to define environment...
  • Page 266 254 Chapter 5: Application Module and IPE Module error messages Table 7 maint messages that appear on the console (continued) Command Message printconfig Printer name already exists Must give a non-null string for the name Port already in use. Request denied.
  • Page 267 No files are available to be restored. The command which invoked the selector is programmed incorrectly. Report the failure to your Nortel support personnel. The selector cannot obtain enough memory to function. Report the failure to your Nortel support personnel.
  • Page 268 256 Chapter 5: Application Module and IPE Module error messages Table 7 maint messages that appear on the console (continued) Command Message scriptinfo No ccr_scriptinfo file available scriptinfo failed: MULTILANGUAGE_ERR scriptinfo failed: MEMORY_ERR scriptinfo failed: ASSOCTABLE_ERR scriptinfo failed: FILEOPEN_ERR showid Error accessing encrypted ID and package data tapeinfo...
  • Page 269 No files are available to be viewed. The command which invoked the selector is programmed incorrectly. Report the failure to your Nortel support personnel. The selector cannot obtain enough memory to function. Report the failure to your Nortel support personnel.
  • Page 270 258 Chapter 5: Application Module and IPE Module error messages Table 8 mlusr messages that appear on the console and SysLog files Message Exiting mlusr: Function SysLog file ts_block call to fcntl() failed Exiting mlusr: Function SysLog file ts_unblock call to fcntl() failed mlusr: SysLog file...
  • Page 271 Chapter 5: Application Module and IPE Module error messages 259 Table 8 mlusr messages that appear on the console and SysLog files (continued) Message SysLog file Exiting mlusr: Application registration failed SysLog file mlusr: out of memory for DN list Console mlusr: out of memory for DN list...
  • Page 272: Other Messages That Appear On The System Console

    260 Chapter 5: Application Module and IPE Module error messages Other messages that appear on the system console The messages in this section may appear on your system console at any time. These error, warning, or status messages, appear as a result of lower- level software processes.
  • Page 273 Chapter 5: Application Module and IPE Module error messages 261 Table 10 SysLog messages that appear on the console (continued) Message syslog: openpipe: could not make named pipe syslog: openpipe: could not open named pipe syslog: openpipe: could not clear NO_DELAY syslog: midnight: cannot remove SysLog.old...
  • Page 274 262 Chapter 5: Application Module and IPE Module error messages Table 10 SysLog messages that appear on the console (continued) Message syslog: append_syslog: open of System Log failed syslog: write_syslog: write to System Log failed syslog: efopen: stat failed syslog: efopen: ustat failed syslog: efopen: not enough free disk space to create file syslog: efopen: could not open...
  • Page 275 Chapter 5: Application Module and IPE Module error messages 263 Table 10 SysLog messages that appear on the console (continued) Message syslog: nextfile: cannot echo message to SysLog.tmp syslog: nextfile: cannot tail SysLog.old syslog: nextfile: cannot move SysLog.tmp syslog: nextfile: failed to get file info syslog: nextfile: can not append to System Log...
  • Page 276 264 Chapter 5: Application Module and IPE Module error messages system watchdog The following messages appear as a result of the system watchdog, which acts as a process manager for application software. All messages start with the date and time. Table 11 sys_wdog messages that appear on the console Message...
  • Page 277 Chapter 5: Application Module and IPE Module error messages 265 Table 11 sys_wdog messages that appear on the console (continued) Message 'message text' sys_wdog: invoking process 'process name' sys_wdog: process 'process name' is deleted from watch-list watch_list is empty Watch_list: add: msgget failed add: msgsnd failed del: msgget failed...
  • Page 278: Messages That Appear In The Syslog File

    266 Chapter 5: Application Module and IPE Module error messages Messages that appear in the SysLog file The SysLog file collects messages from the various application processes. The following is a sample SysLog file displayed by means of the viewlog command (which is described in Chapter 2, ÒApplication Module commandsÓ).
  • Page 279: Application Messages

    Chapter 5: Application Module and IPE Module error messages 267 Application messages The following list is a summary of the application error messages that might be collected in the SysLog file. All messages start with the date and time. Table 12 Application messages that appear in the SysLog file Message hlnkHDLC: init_comm_sw:...
  • Page 280 268 Chapter 5: Application Module and IPE Module error messages Table 12 Application messages that appear in the SysLog file (continued) Message hlinkHDLC: read (conf) - errno ='UNIX error number' hlinkHDLC: ldatq( ) - errno ='UNIX error number' hlnkHDLC: msgget( ) - errno ='UNIX error number' hlnkHDLC error in wait_msg_q( ) - errno ='UNIX error number'...
  • Page 281 Chapter 5: Application Module and IPE Module error messages 269 Table 12 Application messages that appear in the SysLog file (continued) Message hlinkX25: disp_msg( ) lseek failed hlinkX25: Invalid State: 'state number' hlinkX25: bad event:'event number' - state:'state number' hlinkX25: above event not processed hlinkX25: X.25 Link Reset - Cause:'cause number'...
  • Page 282 270 Chapter 5: Application Module and IPE Module error messages Table 12 Application messages that appear in the SysLog file (continued) Message hlinkX25: ioctl( ) - errno ='UNIX error number' hlinkX25: proceventq( ) - errno ='UNIX error number' hlinkX25: pend( ) - errno ='UNIX error number' hlinkX25: nconi( ) - errno ='UNIX error number'...
  • Page 283 Chapter 5: Application Module and IPE Module error messages 271 Table 12 Application messages that appear in the SysLog file (continued) Message hlinkX25: nstatq( ) - errno ='UNIX error number' hlinkX25 error in wait_msg_q( ) - errno ='UNIX error number' hlnkX25: msgget( ) - errno ='UNIX error number' hlnkX25: write to trace file failed...
  • Page 284 272 Chapter 5: Application Module and IPE Module error messages Table 12 Application messages that appear in the SysLog file (continued) Message hlinklan: listen socket is not valid Ð errno = ÔUNIX error numberÕ hlinklan: listen socket type is invalid Ð errno = ÔUNIX error numberÕ...
  • Page 285 Chapter 5: Application Module and IPE Module error messages 273 Table 12 Application messages that appear in the SysLog file (continued) Message hlinklan: bind( ) Ð errno = ÔUNIX error numberÕ hlinklan: fcntl( ) Ð errno = ÔUNIX error numberÕ hlinklan: socket read error Ð...
  • Page 286 274 Chapter 5: Application Module and IPE Module error messages Table 12 Application messages that appear in the SysLog file (continued) Message hlinklan: Bad MLink msg encountered hlinklan: msgget( ) Ð errno = ÔUNIX error numberÕ hlinklan: shmget( ) Ð errno = ÔUNIX error numberÕ...
  • Page 287 Chapter 5: Application Module and IPE Module error messages 275 Table 12 Application messages that appear in the SysLog file (continued) Message Invalid State: 'state number' Link 0 Disabled Link 0 Enabled but down Link 0 Up Link 1 Disabled Link 1 Enabled but down Link 1 Up Link 2 Disabled...
  • Page 288 Meridian 1 ID reported by showid and the one printed on the application software label. Contact your Nortel support personnel if there is a discrepancy. Option 209 is not configured on the X11 software of the connected Meridian 1.
  • Page 289 Chapter 5: Application Module and IPE Module error messages 277 Table 12 Application messages that appear in the SysLog file (continued) Message mlnkHDLC: init_stat_count: lsetstat( ) - errno ='UNIX error number' mlnkHDLC: pend( ) - errno ='UNIX error number' mlnkHDLC: lconq - errno ='UNIX error number' mlnkHDLC: lstatq - errno ='UNIX error number'...
  • Page 290 278 Chapter 5: Application Module and IPE Module error messages Table 12 Application messages that appear in the SysLog file (continued) Message mlnkHDLC: write to trace file failed mlnkHDLC: above event not processed mlnkHDLC: msgget( ) - errno ='UNIX error number' mlnkHDLC error in wait_msg_q( ) - errno ='UNIX error number' mlnkHDLC: unsupported sub...
  • Page 291 Chapter 5: Application Module and IPE Module error messages 279 Table 12 Application messages that appear in the SysLog file (continued) Message x25dmin: xopen( ) - errno ='UNIX error number' x25dmin: ioctl( ) - errno ='UNIX error number' x25dmin: shmget( ) - errno ='UNIX error number' x25dmin: x25stat_data( ) - errno ='UNIX error number'...
  • Page 292: Maint Messages

    280 Chapter 5: Application Module and IPE Module error messages maint messages The following is a summary of the various messages reported during the use of maint commands. All messages start with the date and time. Table 13 maint messages that appear in the SysLog file Command Message login: maint...
  • Page 293 Chapter 5: Application Module and IPE Module error messages 281 Table 13 maint messages that appear in the SysLog file (continued) Command Message applexit mlnkHDLC is not running (continued) backconfig Backup scheduled every 'day' at 'time' Backup scheduled once for 'day' at 'time' backdata Backup unsuccessful...
  • Page 294 282 Chapter 5: Application Module and IPE Module error messages Table 13 maint messages that appear in the SysLog file (continued) Command Message ccrusr (no messages) chgpasswd (no messages) conshare conshare session unsuccessful diskspace (no messages) diskuse Disk usage greater than 95% filedelete Nothing selected: no action taken No files to delete: no action taken...
  • Page 295 Either the specified file has become corrupted or an updated file was deliberately placed in the system to correct a problem. Consult your Nortel support personnel for assistance with this condition. This message appears even if no errors are found. If at least one error is listed, the static file tests found at least one file that failed.
  • Page 296 284 Chapter 5: Application Module and IPE Module error messages Table 13 maint messages that appear in the SysLog file (continued) Command Message fileverif (continued) /usr/maint/file/AutoStart file has incorrect value 'value' /usr/maint/files/IncrDY file has incorrect value 'value' /usr/maint/files/Port file has incorrect value 'value' /usr/maint/files/Speed has incorrect value 'value'...
  • Page 297 Chapter 5: Application Module and IPE Module error messages 285 Table 13 maint messages that appear in the SysLog file (continued) Command Message restart (no messages) rstdata Restore unsuccessful scriptinfo No ccr_scriptinfo file available scriptinfo failed: MULTILANGUAGE_ERR scriptinfo failed: MEMORY_ERR scriptinfo failed: ASSOCTABLE_ERR scriptinfo failed: FILEOPEN_ERR...
  • Page 298: Bad-Event Messages

    286 Chapter 5: Application Module and IPE Module error messages Bad-event messages The following is an explanation for the Òbad eventÓ messages that you may see in the Application Module or IPE Module system log file ÒSyslogÓ. Basically there are three parts to the messages: <link process name>...
  • Page 299: Other Messages Reported In The Syslog File

    Chapter 5: Application Module and IPE Module error messages 287 <state> 0Ñinitial state of the link when applstart is invoked 1Ñlink is initializing 2Ñlink has initialized and is waiting for configuration instructions 3Ñlink is configured but disabled 4Ñlink is temporarily down due to configuration of other link 5Ñlink is enabled but is not established 6Ñlink is established Other messages reported in the SysLog file...
  • Page 300 288 Chapter 5: Application Module and IPE Module error messages system watchdog The following messages appear as a result of system watchdog processes. All messages start with the date and time. Table 15 sys_wdog messages that appear in the SysLog file Message sys_wdog: process 'process ID' died...
  • Page 301 Chapter 5: Application Module and IPE Module error messages 289 Table 15 sys_wdog messages that appear in the SysLog file (continued) Message 'message text' sys_wdog: invoking process 'process name' sys_wdog: process 'process name' is deleted from watch-list watch_list is empty Watch_list: Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Description...
  • Page 302 290 Chapter 5: Application Module and IPE Module error messages 553-3211-510 Standard 1.0 October 1998...
  • Page 303: Chapter 6: Link Error Messages

    This chapter describes error messages that you might see when using link maintenance commands or when using diagnostic tools such as the continuity test and loopback test. If you see an error message that is not described in this guide, contact your Nortel support personnel for assistance. Link maintenance commands fail Link maintenance commands can fail for either syntax or functional reasons.
  • Page 304 292 Chapter 6: Link error messages These errors are corrected by full specification of the command option. Refer to Chapter 3, ÒLink maintenance commandsÓ or use the online help facility (for example, help trace) for more information on each command. A second class of errors occurs due to error conditions existing within the Meridian Link software.
  • Page 305: Mlusr Error Messages

    This might happen when the Application Module or IPE Module is experiencing heavy message traffic while other activities (trace running, monitoring, and so on) are running. Avoid unnecessary activity on the Application Module or IPE Module during high message traffic periods. mlusr error messages The following summary of the error messages reported by application software to the system console covers the error messages in Application...
  • Page 306 294 Chapter 6: Link error messages 0903 - Link ID Already Exists To rectify this problem, reboot the module. 0904 - Meridian 1 or host machine name already exists mlusr attempted to configure a link with an existing name. Use a different name.
  • Page 307 090A - Enable link command failed Application Module cannot enable link 0 (AML) or link 1 (host link). There are a number of possible reasons for this error. First, the X.25 software may not be installed on the Meridian Link Module or the X.25 software may not be installed correctly.
  • Page 308 296 Chapter 6: Link error messages 090F - Link command failed due to reconfiguration of associated link Link 0 (AML) and link 1 (host link) use the two ports on the same MVME705B transition card and MVME333-2 XCC card. If link 0 is being configured, any mlusr command for link 1 will be rejected.
  • Page 309 0B02 - Facility already enabled Facility is already enabled and an attempt is made to turn on the same message facility. No action is necessary. 0B03 - Facility already disabled Facility is already disabled, and an attempt is made to turn off the same message facility.
  • Page 310: Diagnostic Tools Error Messages

    298 Chapter 6: Link error messages Diagnostic tools error messages This is a summary of error messages reported when using the following diagnostic tools: continuity test, traffic reports, and loopback test. No more input is allowed Certain diagnostic tests are in progress. No other input is allowed until the tests are completed.
  • Page 311 Check the MVME705 and MVME333 cards. ¥ Run SSID on the MVME333 card. ¥ Check jumper settings on both cards. Try swapping cards. Loopback Test Failed: No response message from mlink or hlink The links are up, but the Meridian Link Module does not get a loopback test response message back from the links.
  • Page 312: Stale Association

    300 Chapter 6: Link error messages Stale association Associations that terminate before releasing their registered association are considered stale. Because the Meridian Link Module allows a maximum of sixteen registered associations, stale associations should be removed. Stale associations can be removed if the failed application recovers to the point of being able to release itself, or if the module is rebooted.
  • Page 313 The current mlusr association is #2, API_TOOL. Assuming no other user is logged in as mlusr, association #1, ADMIN.1334, is stale. To remove it 1. Quit the current session and enter mlusr> quit Application release successful BYE-BYE 2. Log in as disttech. From the Òdisttech>Ó prompt execute the following command: /usr/mlusr/bin/rm_assoc -a Ôassociation_IDÕ...
  • Page 314 302 Chapter 6: Link error messages 553-3211-510 Standard 1.0 October 1998...
  • Page 315: Chapter 7: Ccr Log File Messages

    Chapter 7: CCR log file messages If you have a problem with CCR, be sure to check your error logs for information regarding the problem. To access your CCR error logs, use the following procedure: Log in as maint. Type view and press [Return]. Screen information such as the following appears: maint>...
  • Page 316 304 Chapter 7: CCR log file messages Note: The messages contained within the SysLog file are discussed in Chapter 5, ÒApplication Module and IPE Module error messages.Ó Type the appropriate number for the file you wish to view and press [Return].
  • Page 317 Log files contain a list of messages that describe events and problems in the system. Some messages are one-line descriptions of events (preceded by date and time) and other messages include more information, in the following format: m/d/y h:m:s class mmmm sev where: m/d/y = date event took place...
  • Page 318 (listed in message number order), the impact of the event or error, and where possible, a strategy for recovery. If a problem persists, contact your Nortel support personnel. Some messages are accompanied by parameters that help pinpoint the location and possible cause for the event.
  • Page 319 1002 Call processing out of memory Log message Cause 1, 2, 3, or 4 [Script Name], which have the Parameters following meanings 1: Could not allocate memory for tracking outstanding commands to the Meridian 1. 2: Could not allocate memory to activate a new Variable Table. 3: Could not allocate memory to activate a new Association Table.
  • Page 320 308 Chapter 7: CCR log file messages 1003 Log message Parameters User ID, [User Name], and Procedure where the error occurred File Name, [Original Directory], and Procedure where the error occurred [Script Name], [Script State], and Procedure where the error occurred. Description enough memory to continue its operation unimpaired.
  • Page 321 Invoke the diskuse command. If the disk usage is not over Recovery 95%, contact your Nortel support personnel. If the disk usage is 95% or more, use the filedelete command to delete low priority files. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide...
  • Page 322 For example, if the Event Log cannot create its output files, the no log files are generated. Recovery 95%, contact your Nortel support personnel. If the disk usage is 95% or more, use the filedelete command to delete low priority files. 1008...
  • Page 323 1009 The process died due to an unrecoverable error. Log message Cause 1, 2, or 3, which have the following meanings Parameters 1: Call processing software restarted 2: Event Log software restarted 3: CCR system manager software restarted The software encountered an unrecoverable internal Description condition and was restarted by the system watchdog utility.
  • Page 324 312 Chapter 7: CCR log file messages 1010 Log message overflowing. Parameters Description structures. Impact follows: Recovery follows: 553-3211-510 Standard 1.0 October 1998 Internal data structures in call processing are Cause 1, 2, or 3, which have the following meanings 1: Too many outstanding commands to Meridian 1 2: Too many installed scripts 3: Too many variable tables...
  • Page 325 1011 The system profile file contains invalid data. Log message None Parameters Data required from the system profile file was not found Description during start-up of the call processing software. The application does not start up. Impact Use the version command to verify which CCR is installed. Recovery Verify that the information reported is correct.
  • Page 326 314 Chapter 7: CCR log file messages Description path with the Meridian 1. Causes 1, 2, 3 and 4 have to do with application registration. If the application fails to start up after three tries due to communication failure, the application will report this error and shut down automatically.
  • Page 327 1013 The process restarted unexpectedly due to error. Log message Component, Object, and Function Parameters The reporter process restarted because of an error. Description Some traffic messages may be lost. Impact The system recovers automatically. Recovery 1014 Unable to establish inter-process communication path. Log message Component, Object, and Function Parameters...
  • Page 328 316 Chapter 7: CCR log file messages 1016 Log message Parameters Description some problem with the association id. Impact is a very serious problem when this error shows. It implies the subsequent CDN acquires may meet the same problem. Recovery 1017 Log message Parameters...
  • Page 329 1018 Application deregistration failed Log message Component, Object, Function, Cause 1, 2, 5 Parameters 1. Bad Association ID/ CCR System Initialization 2. CCR Request Timed Out 5. Invalid Password The CCR application was not able to be deregistered Description smoothly due to some unknown synchronization problems. MSL-1 will still think CCR is alive until it times out.
  • Page 330 318 Chapter 7: CCR log file messages 1020 Log message Parameters Description been corrupted and/or the installation was not performed properly. Recovery installed. Reinstall the CCR package. 1021 Log message Parameters Description expression portion of the script. Impact problem. Recovery in the math expression.
  • Page 331 2002 Link congestion is reported by Meridian 1. Log message None Parameters When Meridian 1 detects 10 consecutive time-outs (of Description four seconds each) for a CCR software reply to an incoming call event, Meridian 1 assumes the link is congested. When Meridian 1 detects link congestion, it issues a message Impact to the CCR software to clear out the backlog of messages.
  • Page 332 320 Chapter 7: CCR log file messages 2004 Log message Parameters Description to Meridian 1 has failed. Impact to Meridian 1 default treatment for both existing calls and new calls. The call processing software will lose all knowledge of any active calls.
  • Page 333 2006 Script exception occurred during call processing Log message Cause 1, 2, 3, 4, or 5; [Script Name, Script Offset] Parameters 1: Invalid opcode encountered 2: Invalid parameter in opcode encountered 3: Invalid statistics access encountered 4: Stack overflow encountered 5: Stack empty condition encountered An invalid operation was encountered during script Description...
  • Page 334 322 Chapter 7: CCR log file messages Description failed to complete. The script is not installed. Impact problem has been corrected. Recovery 553-3211-510 Standard 1.0 October 1998 A script installation into the call processing software The script cannot be used in active call processing until the Recovery differs according to the cause, as follows: 1: Software errorÑlog out and log back into the system, then retry the installation.
  • Page 335 2008 Script removal failed Log message Cause 1, 2, 3, or 4 and Script Name Parameters 1: Bad message: missing or wrong information in the request message 2: Meridian 1 link down: statistics changes required to complete the removal cannot be requested 3: Time-out on requested statistics changes from Meridian 1 4: Unknown script: script is not installed A script removal from the call processing software failed...
  • Page 336 324 Chapter 7: CCR log file messages 2009 Log message Parameters Description previous version of the Variable Table remains active. Impact until the problem has been corrected. Recovery 553-3211-510 Standard 1.0 October 1998 Variable Table activation failed Cause 1, 2, 3, 4, or 5 1: Bad message: missing or wrong information in the request message 2: Meridian 1 link down: statistics changes required to complete...
  • Page 337 2010 Association Table activation failed Log message Cause 1, 2, 3, and 4 which have the following meanings Parameters 1: Bad message: missing or wrong information in the request message 2: Request clash: another Association Table activation was already underway 3: Load failure: the call processing software could not successfully load the Association Table into memory 4: Activation failure: the maximum allowable number of active...
  • Page 338 326 Chapter 7: CCR log file messages 2011 Log message Parameters Miscellaneous information Description handed back to Meridian 1 default operation. Impact Recovery 553-3211-510 Standard 1.0 October 1998 Call rejected by call processing software Cause 1, 2, 3, 4, or 5; [CDN], [Script name], and 1: Unable to allocate memory for a new call 2: No association for the CDN 3: No script found for the call...
  • Page 339 For duplicate call IDs, a call arrived with the same identification number as an existing call. This situation is likely to point to a software error, (old calls in the system are not being cleaned up). Restart the application. 5: For the specific conditional branches that executed for this call, the first statement encountered by call processing was a QUIT or WAIT statement.
  • Page 340 328 Chapter 7: CCR log file messages Notes on flow control Errors related to flow control have the following severity levels: ¥ Level 0 indicates no flow control (the flow control condition has cleared). Continue or resume normal call processing operation. See CCR message 6018.
  • Page 341 2013 Flow control level 3 indication received from the Log message Meridian 1. Refer to ÒNotes on flow control,Ó CCR message 2012. None Parameters A flow control level 3 indication (see ÒNotes on flow Description controlÓ following message 2012) was issued by the Meridian 1 indicating that the Meridian 1 inbound traffic flow consistently exceeded configured limits.
  • Page 342 Recovery your Nortel support personnel. 553-3211-510 Standard 1.0 October 1998 Fail to delete session entry from user session list: User ID, Process ID, Lock Type, Error Status, and...
  • Page 343 2017 Fail to write to the Variable Table file: references not Log message reset Error status and procedure where the error occurred Parameters This happens during shutdown or restart of the call Description processing software. The software failed to update the file copy of the Variable Table after resetting the variable references.
  • Page 344 332 Chapter 7: CCR log file messages 2019 Log message Parameters Description processing software. The software failed to read in the Variable Table; thus, it failed to reset the variable references upon shutdown or call processing software restart. Impact the installation because the Variable Table is not active in the call processing software.
  • Page 345 2021 Fail to open a user profile for read: validation of the Log message profile aborted User ID, Directory, and Procedure where the error Parameters occurred Failure to open a user's profile file for read access. Most Description likely the profile has been deleted without updating the profile list or the file has the wrong permissions.
  • Page 346 334 Chapter 7: CCR log file messages 2023 Log message aborted Parameters Error Status, and Procedure where the error occurred Description user profile manipulation. The software failed to delete the profile entry from the profile list. Deletion is aborted. Impact unless coupled with a memory shortage or file read/write error.
  • Page 347 2025 Fail to delete the file from the directory: operation Log message aborted File Name and Procedure where the error occurred Parameters Failure to delete the file from its directory when trying to Description move the file to the Trash Directory. The file deletion attempt is aborted.
  • Page 348 336 Chapter 7: CCR log file messages 2027 Log message aborted Parameters Status, and Procedure where the error occurred Description script manipulation. The software failed to delete the script entry from the script list. The entry deletion is aborted. Impact There will be an inconsistency in the specified script.
  • Page 349 2029 Cannot create an existing resource: operation aborted Log message User ID, User Name, Process ID, Action Type, Cause, Parameters and Procedure where the error occurred; or Script Name, Process ID, Action Type, Cause, and Procedure where the error occurred This happens during user profile or call script creation.
  • Page 350 Invalid action type in message: message ignored or User ID/Script Name, Process ID, Action Type, Cause, This happens during user profile and call script The indicated action (Action Type) to the indicated system Report the problem to your Nortel support personnel.
  • Page 351 2033 Invalid cause value encountered in message: message Log message ignored User ID/Script Name, Process ID, Action Type, Cause, Parameters and Procedure where the error occurred This happens during user profile, call script, and Description Association Table manipulation. An invalid cause is encountered in the message from the user session.
  • Page 352 340 Chapter 7: CCR log file messages 2036 Log message communication. Parameters Description Module is unknown and the program is unable to communicate link status between processes. Impact system is unaware of the fact (default link state is up). Recovery related errors.
  • Page 353 The user should reenter the script editor or revalidate the Recovery script and continue. Report the occurrence to your Nortel support personnel. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 7: CCR log file messages 341...
  • Page 354 342 Chapter 7: CCR log file messages 2041 Log message Parameters 9, 10, and 11 Description Impact could result in a script or variable table installation failing. Recovery problem. 2042 Log message Parameters Description Impact Recovery 553-3211-510 Standard 1.0 October 1998 ACD statistics start request failed Component, Object, Function, Cause 1, 2, 3, 4, 5, 6, 7, 8, 1.
  • Page 355 2043 CDN is de-acquired by tsmain Log message Component, Object, Function, Cause 3 Parameters 3: A system error occurred. The CDN has been released forcefully by the system due Description to a system problem. The CDN is released from the MSL-1 point of view. All calls Impact to this CDN will be defaulted.
  • Page 356 344 Chapter 7: CCR log file messages 2045 Log message Parameters Description Impact Recovery 2046 Log message Parameters Description was not successful either because there is a synchronization problem, or the CDN device state cannot be changed. Impact Recovery 553-3211-510 Standard 1.0 October 1998 CDN acquire release error occurred None The CDN acquire release request for a CDN failed.
  • Page 357 2047 Application registration error occurred Log message Component, Object, Function, Cause 1, 2, 3, 4 Parameters 1. Bad Application ID 2. Bad Service Number 3. Bad Machine Name 4. Bad Customer Number The CCR application registration response message Description shows that the registration request was not successful. The CCR system will restart.
  • Page 358 346 Chapter 7: CCR log file messages 2050 Log message Parameters Description unrecognizable. Impact cannot be made against this CDN. Recovery 2051 Log message Parameters Description valid state. Impact Recovery everything should return to normal. 553-3211-510 Standard 1.0 October 1998 CDN is in a wrong state Component, Object, Function During a CDN acquire or release, the CDN state was...
  • Page 359 2052 Call treatment was not executed successfully Log message Script Name, Script Command, Parameter, Component, Parameters Object, Function, Cause 6: Invalid Device ID was given 7: Invalid DN was given 8: Bad queuing priority was specified 9: Request failed on the MLS-1 for an unspecified reason 10: ACD queue is in Night Service.
  • Page 360 348 Chapter 7: CCR log file messages 5001 Log message Meridian 1. Refer to ÒNotes on flow controlÓ, CCR message 2012. Parameters Description controlÓ, following message 2012) was issued by Meridian 1, indicating that the Meridian 1 inbound traffic flow occasionally exceeds configured limits on Meridian 1.
  • Page 361 5003 Unrecognized file found: file is moved to the trash Log message directory File Name and Procedure Parameters The software found an unrecognized file in the specified Description directory. The file is moved to the Trash Directory. This happens during midnight routines, start-up, or shutdown. There is no system impact.
  • Page 362 350 Chapter 7: CCR log file messages 5006 Log message Parameters occurred Description profile actually exists, but is not in the profile list. The profile entry is inserted into the profile list. Impact Recovery 5007 Log message Parameters occurred Description script list.
  • Page 363 5008 Script source file doesn't exist: delete entry from script Log message list Script Name and Procedure where the error occurred Parameters This happens during midnight or shutdown. The software Description could not find a script source file. The script entry is deleted from the script list.
  • Page 364 352 Chapter 7: CCR log file messages 5011 Log message Parameters Description but there is no script entry in the script list. All associated files are moved to the Trash Directory. This happens during midnight routines or shutdown. Impact Recovery 5012 Log message Parameters...
  • Page 365 5014 Script link file should not exist: file removed. Log message Script Name and Procedure where the error occurred. Parameters This happens during midnight routines or shutdown. The Description software found a script link file in the file system, but there is no script entry in the script list.
  • Page 366 354 Chapter 7: CCR log file messages 5016 Log message Parameters Script Name, Process ID, Action type, Cause, and Procedure User ID, Process ID, and Procedure User ID, Process ID, Lock Type, and Procedure Process ID, Action Type, Cause, and Procedure Description manager and is, therefore, an invalid user session.
  • Page 367 5019 Statistics timed out on Meridian 1 Log message Component, Object, Function, and ACD DN Parameters The statistics request for the ACD DN has timed out. Description Any script using an intrinsic with this ACD DN will not Impact evaluate correctly. Ensure that the ACD DN is configured on Meridian 1.
  • Page 368 356 Chapter 7: CCR log file messages 5022 Log message Parameters Description active associations than is allowed for the installed CCR package. All associations have been changed to the ÒOFFÓ state. The active association limit is displayed in the data section of this log event. Recovery activate the associations up to the active association limit for the installed CCR.
  • Page 369 6002 Meridian 1 link up Log message None Parameters The communications software has been able to Description re-establish the path with Meridian 1 after a previous failure. The application is now fully operational again. There is no system impact. Impact None Recovery 6003...
  • Page 370 358 Chapter 7: CCR log file messages 6006 Log message Parameters Description been successfully completed. Impact Recovery 6007 Log message Parameters Description The message is followed by a successful completion or by a failure message. Impact Recovery 6008 Log message Parameters Description been successfully completed.
  • Page 371 6010 Script installation completed Log message User ID and Script Name Parameters A previously requested script installation has been Description successfully completed. The new script is now ready for use in active call processing. Impact None Recovery 6011 Script removal initiated Log message User ID and Script Name Parameters...
  • Page 372 360 Chapter 7: CCR log file messages 6014 Log message Parameters Description Impact Recovery 6015 Log message Parameters Description Impact Recovery 6016 Log message Parameters Description software and a graceful shutdown was done by the software. Impact before it will function again. Recovery 6017 Log message...
  • Page 373 6018 Flow control level 0 indication received from Log message MeridianÊ1. Refer to ÒNotes on flow controlÓ, CCR message 2012. None Parameters A flow control level 0 indication (see ÒNotes on flow Description controlÓ following message 2012) was received from MeridianÊ1. This notification indicates that previous flow control or overload conditions that have been encountered are now cleared.
  • Page 374 362 Chapter 7: CCR log file messages 6021 Log message request. Parameters Description receiving the shutdown request from the CCR Module software. Impact Recovery 6022 Log message Parameters Description only occur with the Give Interruptible IVR treatment. Impact Recovery 6023 Log message Parameters Description...
  • Page 375 Chapter 7: CCR log file messages 363 6024 Error Filtering summary report Log message Component, Object, Function, Data Parameters The Error Filtering feature gives a summary report of all Description the filtering errors that occurred in the system since the last report. No impact to the system.
  • Page 376 364 Chapter 7: CCR log file messages 553-3211-510 Standard 1.0 October 1998...
  • Page 377: Chapter 8: Recovery/Replacement Procedures

    Chapter 8: Recovery/replacement procedures This chapter contains all software and hardware recovery procedures that can be performed in the field. These procedures include the following: ¥ software powerdown and restart ¥ hardware powerdown and restart ¥ various hardware replacement procedures ¥...
  • Page 378: Powerdown And Restart Procedures

    366 Chapter 8: Recovery/replacement procedures Powerdown and restart procedures Procedure 1: Software powerdown Log in as maint. The default password is maint. At the Òmaint>Ó prompt, type powerdown and press [Return]. The following messages appear: Figure 14 Powerdown notification message screen 1 Would you like to power down or reboot? Powering down allows you to turn the system off.
  • Page 379 Procedure 1: Software powerdown (continued) The information shown in Figure 16 appears on the screen. Figure 16 Shutdown message screen Shutdown started. Mon Sep 20 12:17:20 PDT 1993 Broadcast Message from root (console) on sysV68 Mon Sep 20 12:17:21... THE SYSTEM IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged.
  • Page 380: Procedure 2: Sbc Restart

    368 Chapter 8: Recovery/replacement procedures Procedure 2: SBC restart Log in as maint. The default password is maint. At the Òmaint>Ó prompt, type powerdown and press [Return]. The following messages appear: Figure 17 Powerdown notification message screen 1 Would you like to power down or reboot? Powering down allows you to turn the system off.
  • Page 381 Procedure 2: SBC restart (continued) Figure 19 Shutdown messages Shutdown started. Mon Sep 20 12:17:20 PDT 1993 Broadcast Message from root (console) on sysV68 Mon Sep 20 12:17:21... THE SYSTEM IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged. INIT: New run level: 6 The system is coming down.
  • Page 382: Procedure 3: Hardware Powerdown

    370 Chapter 8: Recovery/replacement procedures Procedure 3: Hardware powerdown Complete Procedure 1: Software powerdown. When the system confirms that it is secured for powering down, set the MPDU circuit breaker for the Application Module to OFF (down) or press the black power pushbutton on the IPE Module. The top breaker powers the Application Module next to the MPDU (on the left-hand side facing the AEM).
  • Page 383: Hardware Replacement Procedures

    Hardware replacement procedures Procedure 5: Replace the Application Module power supply Complete Procedure 3: Hardware powerdown. Loosen the screws at the top and bottom of the power supply. Pull the power supply out of the Application Module. Slide the replacement power supply into the Application Module. Tighten the screws on the front of the power supply.
  • Page 384: Procedure 7: Replace The Application Module Mvme147/167 Sbc Card

    372 Chapter 8: Recovery/replacement procedures Procedure 7: Replace the Application Module MVME147/167 SBC card Complete Procedure 3: Hardware powerdown. Loosen the screws at the top and bottom of the card. Use the ejectors to unlock the card. Pull the card out of the Application Module. Slide the replacement card into the Application Module.
  • Page 385: Procedure 8: Configure The Application Module Mvme147 Sbc Card

    Procedure 8: Configure the Application Module MVME147 SBC card MVME147 SBC cards may be shipped with the battery backed-up RAM (BBRAM) values set to their original factory defaults. To set the BBRAM information for use with the Application Module, follow the procedure described below.
  • Page 386 374 Chapter 8: Recovery/replacement procedures Procedure 8: Configure the Application Module MVME147 SBC card (continued) Write down the release level of the monitor/debugger (known as firmware level). In Figure 20, this is shown as 2.42. This number will be used later in this procedure. Figure 21 Start-up interrupt menu 1) Continue System Start-up...
  • Page 387 Procedure 8: Configure the Application Module MVME147 SBC card (continued) Figure 23 Disk/tape controller list after aligning LUNs Disk Controllers Available Type Address # dev VME147 $FFFE4000 VME147 $FFFE4000 VME147 $FFFE4000 VME147 $FFFE4000 VME147 $FFFE4000 VME147 $FFFE4000 VME147 $FFFE4000 VME147 $FFFE4000 Save map in NVRAM [Y,N] N? The LUN results appear.
  • Page 388 376 Chapter 8: Recovery/replacement procedures Procedure 8: Configure the Application Module MVME147 SBC card (continued) At the Ò147-Diag>Ó prompt, type env and press [Return]. The environment prompts appear. Answer the prompts as indicated in Figures 26, 27, or 28, depending on the firmware installed in your system. The firmware release appeared in the start-up messages shown in step 3.
  • Page 389 Procedure 8: Configure the Application Module MVME147 SBC card (continued) Figure 28 Environment prompts for firmware revision 2.42 Bug or System environment [B,S] = S? Execute/Bypass System Memory Sizing [E,B] = B? Execute/Bypass SST Memory test [E,B] = B? Set VME Chip: Board ID(def is 0) [0-FF] = $00? GCSR base address offset(def is 0F) [0-0F] = $0F? Utility Interrupt Mask(def is 0) [0-FE] = $00?
  • Page 390: Procedure 9: Configure The Application Module Mvme167 Sbc Card Or The Ipe Module

    378 Chapter 8: Recovery/replacement procedures Procedure 9: Configure the Application Module MVME167 SBC card or the IPE Module MVME167 cards and IPE Modules are shipped with auto-boot no-pause disabled, which means that at boot time, it will pause at the Ò167-Diag>Ó or Ò4120-Diag>Ó...
  • Page 391 Procedure 9: Configure the Application Module MVME167 SBC card or the IPE Module (continued) Figure 31 Start-up interrupt menu 1) Continue System Start-up 2) Select Alternate Boot Device 3) Go To System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape Enter Menu #: The start-up interrupt menu appears.
  • Page 392 380 Chapter 8: Recovery/replacement procedures Procedure 9: Configure the Application Module MVME167 SBC card or the IPE Module (continued) Figure 32 Environment prompts (MVME167 card) Bug or System environment [B/S] = S? Field Service Menu Enable [Y/N] = Y? Remote Start Method Switch [G/M/B/N] = B? Probe System for Supported I/O Controllers [Y/N] = Y? Negate VMEbus SYSFAIL* Always [Y/N] = N? Local SCSI Bus Reset on Debugger Start-up [Y/N] = Y?
  • Page 393 Procedure 9: Configure the Application Module MVME167 SBC card or the IPE Module (continued) Figure 34 Environment prompts (IPE Module) Bug or System environment [B/S] = B? Field Service Menu Enable [Y/N] = N? Probe System for Supported I/O Controllers [Y/N] = Y? Local SCSI Bus Reset on Debugger Start-up [Y/N] = Y? Ignore CFGA Block on a Hard Disk Boot [Y/N] = Y? Auto Boot Enable [Y/N]...
  • Page 394: Procedure 10: Replace The Application Module

    382 Chapter 8: Recovery/replacement procedures Procedure 10: Replace the Application Module MVME333-2 XCC card Complete Procedure 3: Hardware powerdown. Loosen the screws at the top and bottom of the card. Use the ejectors to unlock the card. Pull the card out of the Application Module. Check the jumpers on the replacement card (see Table 16).
  • Page 395: Procedure 11: Replace The Mvme332Xt Or Mvme332Xts Acc Card

    Procedure 11: Replace the MVME332XT or MVME332XTS ACC card Complete Procedure 3: Hardware powerdown. Loosen the screws at the top and bottom of the card. Use the ejectors to unlock the card. Pull the card out of the Application Module. Check the switches and jumpers on the replacement card (see Tables 17 and 18).
  • Page 396: Procedure 12: Replace The Nt6D51 Transition Card

    384 Chapter 8: Recovery/replacement procedures Procedure 12: Replace the NT6D51 transition card You must remove the Application Module from the AEM to access the transition cards. Complete Procedure 13: Remove the Application Module. Loosen the screws at the top and bottom of the card faceplate (at the rear of the Application Module).
  • Page 397: Procedure 13: Remove The Application Module

    Procedure 13: Remove the Application Module You do not need to remove cards, the power supply, or the disk/tape unit from the Application Module before removing the module from the AEM. Complete Procedure 3: Hardware powerdown. Perform the following steps at the rear of the Application Module: ¥...
  • Page 398: Procedure 14: Replace The Application Module

    386 Chapter 8: Recovery/replacement procedures Procedure 14: Replace the Application Module If you are replacing the Application Module with a new one, retain the cards, power supply, and disk/tape unit from the original Application Module for use as spare components. This procedure assumes that you have removed the Application Module using Procedure 13.
  • Page 399: Procedure 15: Remove The Ipe Module

    Procedure 15: Remove the IPE Module You do not need to turn off the power on the IPE shelf or Option 11 cabinet before removing the IPE Module. Complete Procedure 3: Hardware powerdown. Press the black power pushbutton on the IPE Module to turn the power off.
  • Page 400: Procedure 17: Replace The Application Module Mvme712 Transition Card

    388 Chapter 8: Recovery/replacement procedures Procedure 17: Replace the Application Module MVME712 transition card You must remove the Application Module from the AEM to access the transition cards. Complete Procedure 13: Remove the Application Module. Loosen the screws at the top and bottom of the card faceplate (at the rear of the Application Module).
  • Page 401 Procedure 17: Replace the Application Module MVME712 transition card (continued) Figure 36 MVME712A transition card configuration Console Modem power (for external modem) MVME732 Modem Board (non-component side) (to SDI, for conshare) (to Meridian Mail, for Host Enhanced Voice Processing) Printer (unused) To P2 adapter board Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide...
  • Page 402 390 Chapter 8: Recovery/replacement procedures Procedure 17: Replace the Application Module MVME712 transition card (continued) Figure 37 MVME712AM transition card configuration Console Modem power (unused) MVME732 modem board (non-component side) (to SDI, for conshare) (to Meridian Mail, for Host Enhanced Voice Processing) Phone hookup (for modem, to MDF or RJ11) Printer...
  • Page 403 Procedure 17: Replace the Application Module MVME712 transition card (continued) Figure 38 MVME712M transition card configuration SP1, 3 SP2, 4 Ethernet port (LAN-based PC or host computer) Printer port (not used) Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 8: Recovery/replacement procedures 391 R1 R2 13 14...
  • Page 404: Procedure 18: Replace Or Reconfigure The Application Module Mvme705B Transition Card

    392 Chapter 8: Recovery/replacement procedures Procedure 18: Replace or reconfigure the Application Module MVME705B transition card You must remove the Application Module from the AEM to access the transition cards. Complete Procedure 13: Remove the Application Module. Loosen the screws at the top and bottom of the card faceplate (at the rear of the Application Module).
  • Page 405 Procedure 18: Replace or reconfigure the Application Module MVME705B transition card (continued) Figure 39 MVME705B serial port configuration Connect for DTE Jumpers for DTE Connect for DCE Jumpers for DCE Connect for DTE Jumpers for DTE Connect for DCE Jumpers for DCE Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 8: Recovery/replacement procedures 393 ¥¥...
  • Page 406: Software Reinstallationñinitializing The System From Tape

    394 Chapter 8: Recovery/replacement procedures Software reinstallationÑinitializing the system from tape Some events may require you to load the operating system and application software from tape. If the disk drive fails or your system experiences a software problem, reload the software using the tapes delivered with the system.
  • Page 407: Procedure 19: Load The Operating System Tape On An Application Module With An Mvme147 Card

    Procedure 19: Load the operating system tape on an Application Module with an MVME147 card This procedure assumes that you have backed up all files and have powered down the Application Module. Do not press the [Backspace] or [Delete] key when the operating system is not installed, or you may drop out of the procedure into a previous menu or out of the installation procedure altogether.
  • Page 408 396 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 41 Start-up interrupt menu 1) Continue System Start-up 2) Select Alternate Boot Device 3) Go To System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape...
  • Page 409 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) The LUN results appear (Figure 43). Type y and press [Return] to save the map in non-volatile memory. The Ò147-Diag>Ó prompt reappears. Type ab and press [Return] to set autoboot enable.
  • Page 410 398 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 46 Environment prompts for firmware revision 2.2 Bug or System environment [B,S] = S? SYSTEM V/68 or VERSAdos operating system [S,V] = S? Execute/Bypass SST Memory test [E,B] = E? Set VME Chip: Board ID [0-FF] = $00?
  • Page 411 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 48 Environment prompts for firmware revision 2.42 Bug or System environment [B,S] = S? Execute/Bypass System Memory Sizing [E,B] = B? Execute/Bypass SST Memory test [E,B] = B? Set VME Chip: Board ID(def is 0) [0-FF] = $00? GCSR base address offset(def is 0F) [0-0F] = $0F?
  • Page 412 400 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 49 Insert tape into the tape drive Arrow points in BOS installation tape Tape Notch points down 553-3211-510 Standard 1.0 October 1998 side This Tape drive latch...
  • Page 413 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 50 Start-up interrupt menu 1) Continue System Start-up 2) Select Alternate Boot Device 3) Go To System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape Enter Menu #: When the tape indicator goes off, type 2 and press [Return].
  • Page 414 402 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 51 System start-up messages Testing Complete Autoboot in progress ... To abort hit <BREAK> RAM address from VMEbus = $00000000 Booting from: Loading: Volume:...
  • Page 415 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) During the installation or start-up of BOS, different characters than usual represent the character delete, line delete, and interrupt functions. During these operations, ¥ character delete (backspace), usually [Control-h], is [#] ¥...
  • Page 416 404 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Type 1 and press [Return] to install the software. The BOS installation procedure begins. Figure 53 BOS installation, phase 1 BOS INSTALLATION PROCEDURE Phase 1.
  • Page 417 You noted the disk type for your system in step 6. (See Figure 42 for an example.) Most of the disk drives shown in the above figure are not used by Nortel. Some common disk types used by Nortel and their corresponding selection numbers are listed in the table below.
  • Page 418 406 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Type the number corresponding to your disk drive, and press [Return]. The system response is: ÒSelected the XXXX disk typeÓ, where XXXX represents the disk type selected.
  • Page 419 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) You are prompted to enter the user file system slice number. Press [Return] to use the default slice number (2). Phase 2 of the BOS installation begins, and the slice table appears. Figures 59, 60, 61, and 62 show disk slicing tables for four different drive types.
  • Page 420 408 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 61 Disk slicing table for 180-Mbyte disk drive slice ---> Modify any of these parameters? (y, n, ?, q): Figure 62 Disk slicing table for 240-Mbyte disk drive slice...
  • Page 421 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) You are prompted to indicate whether you wish to install online problem descriptions. Nortel does not use these descriptions. Type n and press [Return] to indicate no. Figure 65 Verify installation prompt --->...
  • Page 422 410 Chapter 8: Recovery/replacement procedures Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Note: Phases 3 and 4 may take from 30 to 90 minutes to complete. Figure 67 BOS installation, phases 3 and 4 ***>...
  • Page 423 Procedure 19: Load the operating system tape on an Application Module with an MVME147 card (continued) Figure 68 BOS installation, completion Re-enter new password: ***> Unmounting all mounted file systems ***> Synchronizing the installation disk BOS product installation is completed. You must RESET the system and allow it to autoboot from the hard disk ************************** **** RESET THE SYSTEM ****...
  • Page 424: Module Or An Application Module With An Mvme167 Card

    412 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card If you have just installed a new MVME167 card in an Application Module and you are installing the software for the first time, you need to do steps 2Ð6.
  • Page 425 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) At the Ò4120-Diag>Ó or Ò4120-Bug>Ó prompt, type env and press [Return]. The environment prompts appear. Answer them as indicated in the figure below.
  • Page 426 414 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 71 Additional prompts (IPE Module) Update Non-Volatile RAM (Y/N)? Reset Local System (CPU) (Y/N)? At the Ò167-Diag>Ó...
  • Page 427 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 72 Environment prompts (MVME167 card) Bug or System environment [B/S] = S? Field Service Menu Enable [Y/N] = Y? Remote Start Method Switch [G/M/B/N] = B? Probe System for Supported I/O Controllers [Y/N] = Y? Negate VMEbus SYSFAIL* Always [Y/N] = N?
  • Page 428 416 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Note: If the Ò167-Diag>Ó or Ò4120-Diag>Ó prompt appears, type menu and press [Return]. Figure 74 Start-up interrupt menu 1) Continue System Start-up 2) Select Alternate Boot Device...
  • Page 429 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 75 Insert tape into the tape drive Arrow points in BOS installation tape Tape Notch points down Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 8: Recovery/replacement procedures 417 IPE Module drive side...
  • Page 430 418 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Type 2 and press [Return]. Figure 76 Alternate boot device prompt Alternate Boot Device (Controller,Drive,File): Change it (Y/N)? You are prompted to change the alternate boot device.
  • Page 431 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) You are prompted to enter the file name. Press [Return]. Figure 80 Continue start-up prompt Continue System Start Up (Y/N)? You are prompted to continue start-up.
  • Page 432 420 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Write down the vendor and description of the disk drive installed in SCSI address 00. This information is required later in the procedure.
  • Page 433 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 82 BOS software management menu The BOS (FE03.71) Software Management Menu 1 install Install FE03.71 BOS Software 2 upgrade Upgrade To FE03.71 BOS Software --->...
  • Page 434 You noted the disk type for your system in step 14. (See Figure 81 for an example.) Most of the disk drives in the above figure are not used by Nortel. Some common disk types used by Nortel and their corresponding selection numbers are listed in the table below.
  • Page 435 Although options 8, 9, 16, and 17 start with the prefix Òm147,Ó these options are also applicable to IPE Modules and Application Modules with MVME167 cards. If you experience difficulties, contact your local Nortel support personnel. Disk types used...
  • Page 436 424 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 87 Same disk drive prompt The usr file system is often on the same disk drive as the root file system, but not always.
  • Page 437 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 89 Disk slicing table for 104-Mbyte disk drive Phase 2. Configure Root And Usr File-Systems And Swap Area Check the following slicing information for the root file systemÕs disk drive;...
  • Page 438 426 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 91 Disk slicing table for 180-Mbyte disk drive Phase 2. Configure Root And Usr File-Systems And Swap Area Check the following slicing information for the root file systemÕs disk drive;...
  • Page 439 ---> Install On-line Problem Descriptions (Tars on Tape)? (y, n, ?, q) [n]: You are prompted to indicate whether you wish to install online problem descriptions. Nortel does not use these descriptions. Type n and press [Return] to indicate no.
  • Page 440 428 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 96 Software installation summary Selected to run mkcomply to verify correct installation. Check the information below. the previous questions will have to be answered again.
  • Page 441 Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 97 BOS installation, phases 3 and 4 ***> Checking tape in drive Phase 3. Prepare Installation Disk Drive(s) ***> Retensioning tape (in background) ***>...
  • Page 442 430 Chapter 8: Recovery/replacement procedures Procedure 20: Load the operating system tape on an IPE Module or an Application Module with an MVME167 card (continued) Figure 98 BOS installation, completion ***> Unmounting all mounted file systems ***> Synchronizing the installation disk You must RESET the system and allow it to autoboot from the hard disk Remove the operating system tape from the drive.
  • Page 443: Procedure 21: Reboot And Go Through Setup

    Procedure 21: Reboot and go through setup If you have just installed the operating system tape, ensure that you perform the following procedure before you load the application tape. Note: If your configuration requires an MVME332 card, ensure that it is installed prior to starting this procedure.
  • Page 444 432 Chapter 8: Recovery/replacement procedures Procedure 21: Reboot and go through setup (continued) The autoboot process then starts. Autoboot messages for the IPE Module or MVME167 card are shown in Figures 101 and 102. Messages for the MVME147 card are similar. A series of test messages will appear on one line across the screen for approximately 10 minutes.
  • Page 445 Procedure 21: Reboot and go through setup (continued) Figure 102 System autoboot messages 2 This machine has not been used as a customer machine yet. follow are from checking the built-in file systems for damage that might have occurred during shipment. all is well.
  • Page 446 434 Chapter 8: Recovery/replacement procedures Procedure 21: Reboot and go through setup (continued) At the Ò#Ó prompt, type portconfig -m and press [Return]. The following messages appear on your screen. Figure 103 Portconfig warning THIS WILL REMOVE EXISTING tty NODES IN CREATE NEW ONES BASED ON THE DRIVERS CONFIGURED INTO THE MOST RECENTLY BUILT KERNEL IN HARDWARE CONFIGURATION.
  • Page 447 Procedure 21: Reboot and go through setup (continued) Figure 104 Portconfig messages ----------------------------------------------- Found a vme332xt driver entry in /usr/src/uts/m68k/cf/master (major # 34) Found a configured board (board 0) Removing existing /dev/tty entries for module 1 rm -f /dev/tty1[0123456789] Making tty entries for board 0 Ports appear on backpanel module 1/dev: tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 Adding m332xt Controller board 1 associated entries to /etc/inittab.
  • Page 448 436 Chapter 8: Recovery/replacement procedures Procedure 21: Reboot and go through setup (continued) At the Ò#Ó prompt, type setup and press [Return]. The setup procedure begins. Figure 105 Time zone prompt The first step is to set the timezone, date, and time of the system clock. Current time and time zone is: Change the time zone? [y, n, ?, q] You are prompted to change the time zone.
  • Page 449 Procedure 21: Reboot and go through setup (continued) At the ÒEnter zone number:Ó prompt, type the number corresponding to your time zone and press [Return]. If your time zone is not listed in time zones 1Ð12, type 13 and press [Return].
  • Page 450 438 Chapter 8: Recovery/replacement procedures Procedure 21: Reboot and go through setup (continued) You are prompted to change the date and time. If you do not wish to change the date and time, type n, press [Return], and proceed to step 17.
  • Page 451 Procedure 21: Reboot and go through setup (continued) When prompted, type the minutes and press [Return]. Figure 115 Date and time set prompt Date and time will be set to: You are prompted to confirm the date and time. Type y and press [Return].
  • Page 452 440 Chapter 8: Recovery/replacement procedures Procedure 21: Reboot and go through setup (continued) Figure 118 Administrative passwords prompt Do you want to give passwords to administrative logins? [y, n, ?, q] You are prompted to give passwords to administrative logins. Type q and press [Return].
  • Page 453: Procedure 22: Load The Application Software From Tape

    Procedure 22: Load the application software from tape Before loading the application tape (labeled Tape 2 of 2), ensure that you reboot and go through setup as described in Procedure 21. This procedure assumes you are at the ÒConsole Login:Ó prompt. If you have just performed Procedure 21, you may see the Ò#Ó...
  • Page 454 442 Chapter 8: Recovery/replacement procedures Procedure 22: Load the application software from tape (continued) Figure 123 Software management menu 1 installpkg 2 listpkg 3 removepkg Enter a number, a name, the initial part of a name, or ? or <number>? for HELP, At the software management menu, type 1 and press [Return] to select the install option.
  • Page 455 Procedure 22: Load the application software from tape (continued) Figure 126 Insert tape into the tape drive Arrow points in Application tape Tape Notch points down Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide Chapter 8: Recovery/replacement procedures 443 IPE Module drive side This...
  • Page 456 The system response is ÒInstalling Meridian ApplicationsÓ. You are prompted to press [Return] to continue. Press [Return]. A series of software install messages appears for approximately 10 minutes (Figure 127). If an error occurs, contact your Nortel support personnel. Figure 127...
  • Page 457 Procedure 22: Load the application software from tape (continued) Figure 128 Meridian ID prompt Please enter the Meridian 1 ID of this site: (or Q or q to quit) The system prompts you for the Meridian 1 ID. Type your ID and press [Return].
  • Page 458 446 Chapter 8: Recovery/replacement procedures Procedure 22: Load the application software from tape (continued) Figure 131 Keycode prompt 3 Keycode group 3 (or Q or q to quit): You are prompted for the third group of keycode characters. Type the third group and press [Return]. Figure 132 Keycode prompt 4 Keycode group 4 (or Q or q to quit):...
  • Page 459 Procedure 22: Load the application software from tape (continued) If you are activating the Meridian Link application, you are prompted to enter the Meridian Link protocol. If you are using the X.25 protocol, type x, press [Return], then go to step 19.
  • Page 460 448 Chapter 8: Recovery/replacement procedures Procedure 22: Load the application software from tape (continued) Figure 137 Verification prompt Saving default subnet mask: The following will be installed: Meridian Link Large CCR The following packages are configured: Ethernet NSE software is enabled. Is this correct (y/n/q)? The system lists the application or applications installed.
  • Page 461 Procedure 22: Load the application software from tape (continued) Figure 138 CCR customer number prompt Please enter the CCR customer number (0-99): You are prompted to enter your CCR customer number (Figure 138). Type the number and press [Return]. Note: A two-minute pause occurs at this point before the following messages appear.
  • Page 462 450 Chapter 8: Recovery/replacement procedures Procedure 22: Load the application software from tape (continued) If you disable Ethernet support, you must perform a complete reinstallation of the base operating system and application(s) before you can reenable Ethernet support. Figure 140 Software install messages 2 Configuring your system for NSE.
  • Page 463 Procedure 22: Load the application software from tape (continued) You are prompted for the name of the Application Module or IPE Module. (The term Òmodule nameÓ refers to an Ethernet host computer, which in this case is the Application Module or IPE Module.) Type the module name and press [Return].
  • Page 464 452 Chapter 8: Recovery/replacement procedures Procedure 22: Load the application software from tape (continued) Figure 144 Reboot prompt Entry for <module name> with address <address> added to tcpip transport provider database. Now your system has been modified. You must reboot the system to have the new kernel take effect.
  • Page 465 Procedure 22: Load the application software from tape (continued) Figure 146 Reboot messages 2 Copyright Motorola Inc. 1988 - 1992, All Rights Reserved M4120 Debugger/Diagnostics Release Version 1.1 - 09/30/92 (IR01) COLD Start Local Memory Found =01000000 (&16777216) MPU Clock Speed =25Mhz Autoboot in progress...
  • Page 466: Procedure 23: Back Up Configuration Files And Data Files

    454 Chapter 8: Recovery/replacement procedures Procedure 23: Back up configuration files and data files At the Console Login: prompt, type maint (if you are not already logged in) and press [Return]. The default password is maint. Insert the backup tape into the drive. Ensure that the tape is a backup tape and not a system tape, because any information on the tape will be overwritten by the backup.
  • Page 467 Procedure 23: Back up configuration files and data files (continued) Figure 148 Backdata messages 2 Starting backup usr/maint/files/AMprofile /usr/maint/files/AutoStart /usr/maint/files/IncrDY /usr/maint/files/IncrTM /usr/maint/files/Port /usr/maint/files/Prefs /usr/maint/files/Speed Backup successful maint> At the Òmaint>Ó prompt, type exit and press [Return] to log out of maint.
  • Page 468: Procedure 24: Restore Configuration Files And Data Files From The Backup Tape

    456 Chapter 8: Recovery/replacement procedures Procedure 24: Restore configuration files and data files from the backup tape At the ÒConsole Login:Ó prompt, type maint and press [Return]. You are prompted for a password. Type the password and press [Return]. The default password is maint. At the Òmaint>Ó...
  • Page 469 Procedure 24: Restore configuration files and data files from the backup tape (continued) Figure 151 Rstdata messages screen 1 Stopping application(s) 02/02/94 16:00:27 Notifying CCR of Shutdown... 02/02/94 16:00:37 Stopping CCR application Release Communication Resources... Please wait while tape file list is extracted. You may be prompted about restoring link control files (Figure 152).
  • Page 470 458 Chapter 8: Recovery/replacement procedures Procedure 24: Restore configuration files and data files from the backup tape (continued) Figure 153 Rstdata messages screen 2 Files will be restored to: /usr/maint/files/AMprofile /usr/maint/files/AutoStart /usr/maint/files/IncrDY /usr/maint/files/IncrTM /usr/maint/files/Port /usr/maint/files/Prefs /usr/maint/files/Speed /usr/maint/conf/hdlchlnk.dataf /usr/maint/conf/hdlcmlnk.dataf /usr/maint/conf/lh.config /usr/mlusr/conf/loop13DCE.d /usr/mlusr/conf/loop13DTE.d /usr/mlusr/conf/loop31DCE.d /usr/mlusr/conf/loop31DTE.d...
  • Page 471 Procedure 24: Restore configuration files and data files from the backup tape (continued) Figure 154 Rstdata messages screen 3 Starting restore Restore successful Configuration changed, restarting link processes. Configure Link 0 : Configure Link 1 : Configure Link 2 : Enable Link 0 : successful Enable Link 1 :...
  • Page 472: Procedure 25: Enable Or Disable Ethernet Lan Support

    460 Chapter 8: Recovery/replacement procedures Procedure 25: Enable or disable Ethernet LAN support Before you enable or disable Ethernet LAN support, ensure that all applications have been stopped. This procedure can be used to enable or disable Ethernet LAN support. The example shown in the following procedure is for enabling the support.
  • Page 473 Procedure 25: Enable or disable Ethernet LAN support (continued) Note: If you make a mistake while typing your Meridian ID or keycode, do not try to backspace and correct the error. Instead, continue until step 12, where you will be able to type n, press [Return] and return to step 6.
  • Page 474 462 Chapter 8: Recovery/replacement procedures Procedure 25: Enable or disable Ethernet LAN support (continued) Figure 160 Keycode prompt 4 Keycode group 4 (or Q or q to quit): You are prompted to enter the fourth group of keycode characters. Type the fourth group and press [Return]. Figure 161 Keycode prompt 5 Keycode group 5 (or Q or q to quit):...
  • Page 475 Procedure 25: Enable or disable Ethernet LAN support (continued) Figure 163 IP address prompt Meridian Link using TCP/IP connection. If you would like a default gateway IP address configured or changed, please enter the IP address in internet dot notation (e.g. 47.82.45.10), for no change enter <cr>: To configure or change a default gateway IP address, type the IP address in the proper format and press [Return].
  • Page 476 6. Re-key your Meridian ID and keycode. If the list of applications is still incorrect, type q and press [Return]. The message ÒSoftware not configuredÓ appears. Call your Nortel support personnel for a new keycode. If the list is correct, type y and press [Return].
  • Page 477 Procedure 25: Enable or disable Ethernet LAN support (continued) Figure 167 Ethernet connection prompt Installing NSE R3V7.1. Please wait. Is your module connected to the Ethernet (y/n) ? You are asked whether your Application Module or IPE Module is connected to Ethernet (Figure 167). For more information about Ethernet connections, refer to ÒMeridian Link/CCR interface cablingÓ...
  • Page 478 466 Chapter 8: Recovery/replacement procedures Procedure 25: Enable or disable Ethernet LAN support (continued) Figure 168 Software install messages 2 Configuring your system for NSE. Please wait. /usr/src/uts/m68k/sysgen/sysgen -l /usr/src/uts/m68k/sysgen LIBDIR=../cf SYS= CFLAGS= -O L -DSTREAMS -DBRIDGE CPU=m68k CC=/bin/pcc/cc "INCRT=/usr/include" "DASHO=-O"...
  • Page 479 Procedure 25: Enable or disable Ethernet LAN support (continued) Figure 170 Module address prompt Enter the MODULE ADDRESS to be added to the tcpip transport provider database (?, or module address): You are prompted for the address of the Application Module or IPE Module (Figure 170).
  • Page 480 468 Chapter 8: Recovery/replacement procedures Procedure 25: Enable or disable Ethernet LAN support (continued) You are prompted to reboot the system (Figure 172). Type y and press [Return]. Application shutdown and start-up messages appear. Eventually the ÒConfiguration successfulÓ message appears (Figure 173). Figure 173 Installation confirmation Configuration successful...
  • Page 481: List Of Terms

    AEM in a Meridian 1. Application Module Link (AML) A Nortel internal and proprietary link that connects the Meridian 1 (via ESDI or MSDL) to the Application Module or IPE Module. Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide...
  • Page 482 See control directory number. central office (CO) A public network telephone exchange. Local subscribers are connected to the CO via local loops; PBXs are connected to the CO via trunks. NortelÕs DMS-100 is an example of a CO. Command and Status Link (CSL) A Nortel internal and proprietary link, also known as AML.
  • Page 483 An attribute of a trunk. The CO passes the extension number of the called party over a DID trunk to the PBX when offering a call to the PBX. The PBX is then able to automatically route the call to the extension without requiring operator/attendant assistance.
  • Page 484 Meridian 1 CPU and other components within the Meridian 1 system. Intelligent Peripheral Equipment (IPE) Module NortelÕs smaller application processor that can be packaged in a Meridian 1 Option 11 cabinet or in an IPE shelf. Interactive Voice Response (IVR) A system/facility that plays voice menus to callers, and acts upon user input (typically DTMF digits from a touch-tone phone).
  • Page 485 Overlays are exited by typing ****. QPC513 A Nortel Meridian 1 circuit pack, also known as ESDI (Enhanced Serial Data Interface). This card supports internal communications between the Meridian 1 CPU and other components within the Meridian 1 system.
  • Page 486 Application Module or IPE Module hardware components. terminal number (TN) The physical address of a device (for example, telephone set, a trunk, and attendant) on the Meridian 1 PBX. The TN is composed of the loop, shelf, card and unit IDs. See terminal number.
  • Page 487: Index

    Index ACC card LEDs 6 location in Application Module 8 accessing CCR log file 303 ACD see Automatic Call Distribution (ACD) ACD DN see Automatic Call Distribution Directory Number (ACD DN) adding a printer 67 admin command 20 advanced diagnostic tests 169 advanced maintenance 16 AEM 469 AM see Application Module (AM)
  • Page 488: Standard 1.0 October

    476 Chapter 10: Index lanconfig 53 langconfig 55, 58 midnight 36 mlexit 59 mlstart 59 mlusr 59 portconfig 60 powerdown 62 printconfig 66 quit 70 resetmodem 70 restart 71 rootpasswd 72 rstdata 73 rstfiles 76 scriptinfo 77 showid 78 startNSE 79 stopNSE 79 summary 18 tapeinfo 80...
  • Page 489 cable connection MVME705B card 392 call processing functions fail diagnosing faults 230 card diagnosing fault 167 reseating 169 card fault suspected (Application Module) diagnostic procedure 167 diagnostic procedure flowchart 170 card fault suspected (IPE Module) diagnostic procedure 167 diagnostic procedure flowchart 176 cassette tape inserting 24, 28, 32 write-protection disabled 23, 27, 31...
  • Page 490 478 Chapter 10: Index clear message for monitoring 135 clear messages for statistics 124 clear record 132 conshare 45 continuity test 145 disable filter 127 disable link 93 disable message statistics collection 124 disable monitor 135 disable recording 131 disable traffic 138 diskuse 47 display link 102 display linkctl 96...
  • Page 491 Command and Status Link (CSL) 470 components hardware (Application Module) 4 hardware (IPE Module) 11 configuration link 0 (LAPB) 102 link 1 (X.25) 102, 103 link 2 (ASYNC) 103 MVME705B card serial port 393 MVME712A card 389 MVME712AM card 390 MVME712M card 391 configuration file restoring from backup 456...
  • Page 492 480 Chapter 10: Index system console fault suspected flowchart system start-up problem 184 diagnostic tools error message 298 dial-up problem diagnostic procedure flowchart 187 DID see Direct Inward Dialing (DID) difficulty logging in ccrusr 207 maint 208 mlusr 209 Direct Inward Dialing (DID) 471 directory number (DN) 471 Directory Number Identification Service (DNIS) 471...
  • Page 493 exit command 48, 152 express powerdown 62 failure Meridian Link application registration 227 Meridian Link call processing 230 Meridian Link messages 233 mlusr command 291 fault card 167 diagnosing 157 disk/tape unit 206 power (Application Module) 158 power (IPE Module) 164 printer 200 system console 178 file...
  • Page 494 482 Chapter 10: Index installing BOS (IPE Module) 412 BOS (MVME147 card) 395 BOS (MVME167 card) 412 BOS tape in tape drive 400 Intelligent Peripheral Equipment (IPE) Module see IPE Module Interactive Voice Response (IVR) 231, 472 internal error message 266 IPE Module 472 components 11 definition 472...
  • Page 495 link maintenance command 87 association services commands 120 change link 104 change linkctl 97 clear filter messages 128 clear message for monitoring 135 clear messages for statistics 124 clear record 132 continuity test 145 disable filter 127 disable link 93 disable message statistics collection 124 disable monitor 135 disable recording 131...
  • Page 496 484 Chapter 10: Index loading application tape onto hard disk 441 BOS (IPE Module) 412 BOS (MVME147 card) 395 BOS (MVME167 card) 412 location Application Module components 8 MVME705B transition card jumpers 393 MVME712A card 389 MVME712AM card 390 MVME712M card 391 logging in 14 logging out 14 login...
  • Page 497 specifying type 119 statistics 123 SysLog 260 SysLog file 266, 287 system and UNIX 238 system console 238 system restart 373, 395 system watchdog 264 type 119 viewing CCR log file 303 message statistics commands 123 midnight command 36 miscellaneous commands 152 mlexit command 59 mlstart command 59 mlusr...
  • Page 498 486 Chapter 10: Index overlay 473 parameter changing 104 configuration 219 link 107 reconfiguring 115 saving 114 PBX 470, 471 port characteristics changing 61 displaying 60 portconfig Application Module command 60 changing port characteristics 61 displaying port characteristics 60 position ID 343...
  • Page 499 powerdown 370 powerdown and restart 366 rebooting and setup 431 recovery/replacement 365 removing the Application Module 385 removing the IPE Module 387 replacing Application Module disk/tape unit 371 replacing Application Module MVME147/67 SBC card 372 replacing Application Module power supply 371 replacing MVME333-2 XCC card 382 replacing the Application Module 386 replacing the IPE Module 387...
  • Page 500 488 Chapter 10: Index Application Module 4 configuring MVME147 373 configuring MVME167 378 indicators (LEDs) 11 SBC card 4 IPE Module 11 location in Application Module 8 restart procedure 368 switches (IPE Module) 12 script 14, 77, 471 definition 473 state 77 statistics 37, 38, 41 statistics output 41...
  • Page 501 system console diagnosing fault 178 messages 238 system console fault suspected diagnostic procedure flowchart 178 system restart messages 373, 395 system setup 431 system start-up problem diagnostic procedure 184 system watchdog message summary 264 messages 264 SysLog file 288 tape initializing the system 394 inserting 24, 28, 32 installing BOS tape in tape drive 400...
  • Page 502 490 Chapter 10: Index X.25 Communication Controller (XCC) card LED 5 XCC card jumper settings 382 LED 5 location in Application Module 8 replacing 382 553-3211-510 Standard 1.0 October 1998...
  • Page 503 Tell us about yourself: Name: _____________________________________________________________________ Company: ___________________________________________________________________ Address: ____________________________________________________________________ Occupation:______________________________________ Phone: _____________________ What is your level of experience with this product? New User How do you use this book? Learning Did this book meet your needs? If you answered No to this question, please answer the following questions. What chapters, sections, or procedures did you find hard to understand? _____________________________________________________________________________ _____________________________________________________________________________...
  • Page 504 Copyright © 1998 Northern Telecom All rights reserved Information subject to change without notice. Meridian 1, SL-1, and Nortel 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.

This manual is also suitable for:

Meridian 1

Table of Contents