Page 1 297-7001-503 DMS-100 Family DMS VoiceMail Trouble-locating and alarm-clearing procedures SPM 02 Standard 02.02 March 1994...
Page 3 All rights reserved Printed in the United States of America Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. DMS , DMS SuperNode , MAP, Meridian, Meridian Mail, and NT are trademarks of Northern Telecom.
Page 4 Publication history March 1994 Standard 02.02 is the first standard release of the SPM 02 version of this document. SPM 02 is the second software release for DMS VoiceMail. February 1994 Standard 01.03 is the first standard release of the SPM 01 version of this document.
Page 5: Table Of Contents
Contents About this document When to use this document x How DMS VoiceMail documentation is organized x References in this document x What precautionary messages mean xi Regulatory notices xii United States installations xii Canadian installations xiii System redundancy Power Multiserver processor node Signal processing node Telephony interface node...
Page 6 iv Contents Alarms 2-37 Out-of-Service diagnostics 2-39 68K diagnostics 2-39 T1 diagnostics 2-39 VP12 diagnostics 2-40 Bus controller diagnostics 2-40 On-line diagnostics 2-41 Booting the system Booting up procedures 68K node loading Booting problems Multiserver processor node 68K card Bus controller card 68K transition module Bus controller transition module MSP configurations...
Page 7 Contents Accidental removal of the 68K transition module Node stuck in loading state DSP port stuck in pending state DSP stuck in loading state DSP port stuck in out-of-service state DSP port stuck in faulty state DSP port unconfigured DSP port stuck in NoResources state Node rebooting Noisy recorded message or noisy session Disk failure...
Page 8 vi Contents Class 6604 Class 6605 Class 6606 Replacing and resynchronizing disks Tape drive errors Peripherals and links Local terminals Multiple administration terminals Remote terminals Local printers No printer output Printer alarms Backup printers No printer output Printer alarms SMDI links Link bounces up and down constantly Link cannot be brought up If the system shows an alarm...
Page 9 Contents Other bus terminator symptoms 9-19 No SEERs 9-19 Local terminal lockup 9-19 Critical alarm 9-19 Bus extender transition module symptoms 9-20 Nodes unload on secondary shelf 9-20 Loss of voice 9-20 Remote view bootup diagnostics 10-1 Setting up the modem 10-1 Dialing into the SPM 10-1 Modem BIX tip and ring pairs for MSPs and SPNs 10-2 Online recovery...
Page 10 viii Contents Figure 6-1 TIFN cable sets 6-20 Figure 7-1 Node numbers and corresponding disk and pack numbers Figure 9-1 Input/output panel locations - rear SPM view Figure 9-2 Input/output connectors Figure 9-3 Input/output cable identification Figure9-4 Internal backplane cable connections for shelf 26 Figure 9-5 Internal backplane cable connections for shelf 39 Figure 9-6...
Page 11: About This Document
ProcNum1 TabNum1 FigNum1 About this document This document provides information about the DMS VoiceMail system, its subsystems, and procedures for locating troubles and clearing alarms. The procedures are designed for first-line and secondary support maintenance personnel in an operating company. The document is structured in the following chapters: System redundancy discusses the principal subsystems, peripherals, and links that comprise the DMS VoiceMail system and how redundancy has...
Page 12: When To Use This Document
More than one version of this document may exist. To determine whether you have the latest version of this document, check the release information in DMS-100 Family Guide to Northern Telecom Publications, NTP 297-1001-001. How DMS VoiceMail documentation is organized This document is part of DMS VoiceMail documentation that supports the Northern Telecom line of DMS VoiceMail products.
Page 13: What Precautionary Messages Mean
About this document xi What precautionary messages mean Danger, warning, and caution messages in this document indicate potential risks. These messages and their meanings are listed in the following chart. Message Significance DANGER Possibility of personal injury WARNING Possibility of equipment damage CAUTION Possibility of service interruption or degradation Examples of the precautionary messages follow.
Page 14: Regulatory Notices
Normally, an SPM modem port should not share the line with any other device. If your Northern Telecom SPM causes harm to the telephone network, the telephone company may disconnect your service temporarily. The...
Page 15: Canadian Installations
LNs of all the devices does not exceed 100. If you experience trouble with your Northern Telecom SPM equipment, contact your authorized distributor or service center in Canada for repair or warranty information. If you do not know how to contact your distributor, call 1-800-NORTHERN.
Page 16 xiv About this document 297-7001-503 Standard 02.02 March 1994...
Page 17: System Redundancy
System redundancy Power For power distribution purposes, each shelf of the service peripheral module (SPM) is divided into two halves between card slots 19 and 20. Each half-shelf is powered by two power converters that are supplied by the A and B central office power feeds.
Page 18: Multiserver Processor Node
1-2 System redundancy Multiserver processor node DMS VoiceMail uses a pair of multiserver processors (MSPs) to provide system redundancy. The primary MSP has the active bus controller. Multiserver programs are distributed to both MSPs. When the active MSP fails, bus control passes to the second MSP and the appropriate multiserver programs are restarted.
Page 19: Signal Processing Node
System redundancy Signal processing node A DMS VoiceMail subscriber is normally associated with one signal processing node (SPN). SPNs are configured in pairs. If one SPN fails, the overall system capacity is diminished. However, since SPNs are paired (that is SPNs 1-2, 3-4, 5-6, etc.), all subscribers on a failed SPN can still gain access to their mailboxes through the other SPN.
Page 20: Telephony Interface Node
1-4 System redundancy Telephony interface node The telephony interface node (TIFN) consists of a 68K card and a T1 card. TIFNs are configured in redundant pairs. If the primary TIFN fails, the T1 spans and SMDI links that terminate on the primary TIFN are automatically shifted to the secondary TIFN.
Page 21: Disk Drives
System redundancy Disk drives Each MSP and SPN node has two SCSI paths to two disk drives. Node A writes to Disk 1 and shadows Disk 2. Node B writes to Disk 2 and shadows Disk 1. If a disk drive fails, both nodes have a surviving disk. If a node fails, access to that node’s stored data can be routed through the other node in the pair.
Page 22: T1 Spans
1-6 System redundancy T1 spans Each pair of telephony interface nodes (TIFNs) can terminate up to four T1 spans. Four T1 spans terminate on the primary TIFN. When an error is detected at the primary TIFN, one or more of the T1 spans are automatically switched to the redundant TIFN.
Page 23: Simplified Message Desk Interface Links
System redundancy Simplified message desk interface links Each telephony interface node (TIFN) can terminate up to four simplified message desk interface (SMDI) connections. Up to four SMDI links can terminate on a TIFN. When an error is detected at the primary TIFN, one or more of the SMDI links are automatically switched to the redundant TIFN.
Page 24: Local Maintenance Console
1-8 System redundancy Local maintenance console Port one on each of the two MSPs is dedicated to local maintenance and administration support. A relay mounted on the input/output daughter board selects which MSP is connected to the maintenance terminal. This selection is based on an MSP active signal from MSP 1 that controls which MSP is connected to the terminal.
Page 25: Remote Access
System redundancy Remote access Remote access to the SPM can be achieved by dialing a directory number that is assigned to the remote access port on the multiserver processor (MSP). Each MSP has a 2400-baud modem dedicated to its second port for this purpose.
Page 26 1-10 System redundancy 297-7001-503 Standard 02.02 March 1994...
Page 27: Maintenance Principles
Maintenance principles Maintenance model Figure 2-1 illustrates the basic maintenance model that DMS VoiceMail uses. The most common maintenance states are shown (that is, inservice, out-of-service, and faulty) while transient states (such as, pending, loading, etc.) are not shown. Figure 2-1 DMS VoiceMail maintenance model InService Component...
Page 28: Maintenance Actions And System Events
2-2 Maintenance principles An out-of-service component is brought back to the inservice state by manually using the enable command. Out-of-service diagnostics can be run against an out-of-service component. If the diagnostics pass, the component remains out-of-service. However, if the diagnostics fail, the component is put in the faulty state by the system.
Page 29: Figure 2-2 Boot Sequence
Maintenance principles Nominal boot sequence Figure 2-2 illustrates the boot sequence for both the primary and secondary MSPs. Figure 2-2 Boot sequence Primary Secondary Power Power BootROM Initialization BootROM Start Clocks Initialization Wait 10 sec. Check For Clocks No Clock Clock Active MSP Boot Via...
Page 30 2-4 Maintenance principles Primary MSP boot sequence When a primary MSP is booted, the following sequence of events occurs: the 68K card of the MSP powers up and starts the BootROM sequence • the 68K card reads its physical slot location to determine whether it has the primary MSP role •...
Page 31 Maintenance principles series of transitions from the inservice standby state to the out-of-service state. Disabling the primary MSP When the primary MSP is disabled, the secondary MSP takes over from the primary MSP through an MSP switchover. This puts the secondary MSP in the inservice state and the primary MSP in the out-of-service state.
Page 32: Figure 2-4 Enabling Msps
2-6 Maintenance principles Enabling MSPs Figure 2-4 illustrates the sequence of events when the primary and secondary MSPs are enabled. Enabling the primary MSPs When the primary MSP is enabled, it takes system control from the secondary MSP through an MSP switchover. This put the primary MSP in the inservice state and the secondary MSP in the inservice standby state.
Page 33: Tifn Maintenance Actions
Maintenance principles TIFN maintenance actions Maintenance operations can be performed on the Telephony Interface Node (TIFN), the 68K card, the T1 card, T1 spans, T1 channels, and SMDI links. Normally, a maintenance action performed to a higher entity causes a ripple effect for lower entities.
Page 34 2-8 Maintenance principles Enabling T1 spans Figure 2-5 illustrates the sequence of events when T1 spans are enabled from the out-of-service and inservice standby states. When an out-of-service T1 span is enabled, it goes through a transitional pending/loading state before going to either the inservice or inservice standby state.
Page 35 Maintenance principles Switchover occurs when individual T1 spans are switched to the redundant TIFN. The primary T1 span goes to the out-of-service state and the secondary T1 span goes to the inservice state. Disabling a T1 span in the inservice standby state causes the T1 span to go to the out-of-service state.
Page 36 2-10 Maintenance principles T1 channels Figure 2-7 illustrates the sequence of events when T1 channels are enabled and disabled. Enabling T1 channels When an out-of-service T1 channel is enabled, it goes through a transitional loading state that takes about one minute before going to the idle state.
Page 37: Spn Maintenance Actions
Maintenance principles 2-11 SPN maintenance actions Maintenance operations can be performed on the Signal Processing Node (SPN) at the node, card and DSP port levels. For example, disabling a VP12 card marks its 12 channels as OutOfService. However, disabling an SPN does not put its cards out-of-service.
Page 38 2-12 Maintenance principles Figure 2-8xxx Enabling and disabling a VP12 card Enable VP12 Card Disable VP12 Card InService OutOfService Courtesy Disable Pending InService Disable OutOfService DSP ports Figure 2-9 illustrates the sequence of events when DSP ports are enabled and disabled. Enabling DSP ports When an out-of-service DSP port is enabled, it goes through a transitional loading state that takes about one minute before going to the idle state.
Page 39 Maintenance principles 2-13 Figure 2-9xxx Enabling and disabling a DSP port Enable DSP Port Disable DSP Port OutOfService Idle Active Courtesy Disable Disable Loading Pending No Resource OutOfService Idle Active DMS VoiceMail Trouble-locating and alarm-clearing procedures SPM 02...
Page 40: System Status And Maintenance Menu
2-14 Maintenance principles System status and maintenance menu The System Status and Maintenance menu is used to access screens that display the status of various types of components. It is from this menu that alarms can be silenced using the Silence Alarm softkey. When the Silence Alarm softkey is selected, the administrator is given the option of silencing the critical, major, or minor alarms.
Page 41: Node Status Screen
Maintenance principles 2-15 Node status screen The Node Status screen displays the operational status of nodes in the system. This screen is used to identify nodes that are faulty or suspected of not operating correctly. A normally operating node is either in the inservice (InService) or inservice standby (InSvStandby) state.
Page 42: Out-Of-Service Diagnostics
2-16 Maintenance principles Card status screen The Card Status screen displays the operational status of the cards on a particular node in the system. Before entering the screen, the administrator is prompted for the number of the node for which the card status should be displayed.
Page 43 Maintenance principles 2-17 T1 link status screen The T1 Link Status screen displays the operational status of primary and redundant T1 spans in the system. A normally running T1 span is either in the InService or InSvStandby state. This screen is used to identify T1 spans that are not operating correctly.
Page 44 2-18 Maintenance principles Figure 2-13xxx T1 Link Status screen System Status and Maintenance T1 Link Status System Status: InService Alarm Status:Critical=Off Major=On Minor=Off Clocking Primary Connection Redundant Connection Link Cand Mode Number Location Status Number Location Status 11-1-1 InService 12-1-1 InSvStandby 11-1-2 InService...
Page 45 Maintenance principles 2-19 SMDI link status screen The SMDI Link Status screen displays the operational status of the primary and secondary SMDI connections in the system. A normally running SMDI link is either in the InService or InSvStandby state. This screen is used to identify SMDI links that are not operating correctly.
Page 46 2-20 Maintenance principles Figure 2-14xxx SMDI Link Status screen System Status and Maintenance SMDI Link Status System Status: InService Alarm Status:Critical=Off Major=Off Minor=Off Primary Connection Redundant Connection Link SMDI SMDI SMDI SMDI Number Location Status Number Location Status 15-1-1 InService 16-1-1 InSvStandby 15-1-2...
Page 47 The SPM Cross Reference Table screen translates a logical location of a card (that is, node-card) to a physical location (that is, shelf-slot) on the SPM frame. It also indicates the Northern Telecom product equipment code, shown as CardNumber. This screen is used if it is necessary to identify where on the physical SPM frame a faulty card is located.
Page 48 2-22 Maintenance principles Disk maintenance screen Disks are added to DMS VoiceMail in pairs. When new data is written to disk, both drives in a pair are updated at the same time with the same information. If one of the drives in a pair fails, it can be removed from service and replaced without loss of data or interruption of service.
Page 49 Maintenance principles 2-23 Figure 2-17 illustrates the Disk Pair Status screen. Figure 2-17xxx Disk Pair Status screen ABC Company System Status and Maintenance Disk Pair Status for Pair X System Status: InService Alarm Status: Critical=Off Major=On Minor=Off Node Primary Shadow ReadWrite ReadWrite ReadWrite...
Page 50 2-24 Maintenance principles SEER operations System Event and Error Reports (SEERs) collect information on every system event and error reported by the system software components. Severity level SEERs are classified into four severity classifications: critical, major, minor, and info. Type SEERs are also classified into four types: Error, Admin, System, and All.
Page 51 Maintenance principles 2-25 Figure 2-19 illustrates how a sample Report screen appears. Figure 2-19xxx Report screen ABC Company Limited System Status and Maintenance SEER Period from 5/17/91 04:00 to End of SEER data. Error Date Time Type/Severity, Description 35-0 5/17 04:30SysInf SEER registered and active 26-0 5/17 04:32SysInf...
Page 52 2-26 Maintenance principles Troubleshooting using SEERs To troubleshoot DMS VoiceMail problems through SEERs, use the following guidelines: • Group SEERs by hardware location (HWLOC). • Using the timestamp, trace the grouped SEERs back to a single root event that initiated the generation of multiple SEERs. •...
Page 53 Maintenance principles 2-27 However, the Voice Channel Maintenance (VCM - Class 41) is notified of the VSS program termination and its cause by the Program Resource Manager. The VCM recovers by restarting the VSS program. During the loading sequence the channel status is set to “L”. Example 2 Starting state Figure 2-21 illustrates the T1 Link Status screen with all primary T1 links in...
Page 54 2-28 Maintenance principles SEER>09/26/92 13:08:20 268305 S:SysInf LOCN:13/ 2/12000000066D1807 4708 [0:31] T1 Trunk OpStatus chg from 1 to0 (HWStatus:0) 0 HWLOC:1-13-1-1 SEER>09/26/92 13:08:23 268729 S:SysInf LOCN:14/ 2/0D000000066EC1807 4700 [0:31] T1 Link Status - InService (0) (1) 0 HWLOC:1-14-3-1 Explanation: The first four SEERs indicate that a T1 alarm has been triggered by the primary T1 connection on link A (HWLOC: 1-13-1-1).
Page 55 Maintenance principles 2-29 SEER>09/26/92 13:08:39 270431 S:SysInf LOCN: 14/ 2/0D00000006EC1807 4700 [0:31] T1 Link Status - Alarm Active (3) (5) 0 HWLOC:1-14-3-1 SEER>09/26/92 13:08:41 276916 S:ErrMaj LOCN: 1 / 4/0100000012823A13 4163 VCM:fDoOneSpan: too many switches (Alarm), probable far end problem, cmd=BSwitch devStatus=isOnLine PartnerStatus=isStdBy HWLOC:1-13-1-1 SEER>09/26/92 13:08:44 277299 S:SysInf LOCN: 1/ 0/0100000003821504...
Page 56 2-30 Maintenance principles T1 red alarm Figure 2-23 indicates an InSvRedAlarm on Link A. Figure 2-23xxx T1 Link Status screen System Status and Maintenance T1 Link Status System Status: InService Alarm Status:Critical=Off Major=Off Minor=On Clocking Primary Connection Redundant Connection Link Cand Mode Number Location Status...
Page 57 Maintenance principles 2-31 Channels in pending state Figure 2-24 illustrates the T1 Channel Status screen with all channels on link A in the pending (P) state. Figure 2-24xxx T1 Channel Status screen System Status and Maintenance T1 Channel Status System Status: InService Alarm Status: Critical=Off Major=Off Minor=On...
Page 58 2-32 Maintenance principles Recovery Figure 2-25 illustrates the T1 Link Status screen after recovery with the redundant link in the InService state. In this state, the system can continue to function with full redundancy. It is an acceptable practice to use the Switch Link softkey to put the primary link back to the InService state.
Page 59 Maintenance principles 2-33 Hardware database The hardware database provides an indication of component status in the SPM and contains about 500 hardware database locations (HWLOC) entries. Each HWLOC refers to a particular hardware entity, such as a voice processor card or a an external T1 span. Hardware database locations The HWLOC is a five-digit code that represents the following information: Example...
Page 60 2-34 Maintenance principles Nodes DMS VoiceMail supports up to 16 nodes that are numbered 1 to 16. In the hardware database, the HWLOC for node one is n-1 and for node two is n-2, where “n” is the frame number of the SPM. A node refers to one processor card and its transition module and any associated peripheral cards and their transition modules.
Page 61 Maintenance principles 2-35 Telephony channels A T1 channel can be identified in four ways. The following is an example of the four ways to identify the 22nd channel of the first T1 span: • In the MMI, the T1 channel is identified as Link A Channel 22. The software that corresponds to the channel is a VSS that runs on node three (SPN1).
Page 62 2-36 Maintenance principles DSP ports There are two ways to identify a DSP port. The MMI numbers the DSPs from 1 to 24. On each node there are two VP12 cards, each of which have 12 DSP ports. On nodes three and seven, the VP12 cards are in positions two and three.
Page 63 Maintenance principles 2-37 Table 2-3xxx HWLOC DSP port information (continued) MMI Port Number Node 3 HWLOC Node 4 HWLOC 1-3-3-3-2 1-4-2-3-2 1-3-3-3-3 1-4-2-3-3 1-3-3-4-1 1-4-2-4-1 1-3-3-4-2 1-4-2-4-2 1-3-3-4-3 1-4-2-4-3 Alarms Three categories of external alarms exist: • critical • major •...
Page 64: Figure 2-26 Basic Alarm Components
2-38 Maintenance principles Figure 2-26 Basic alarm components MSP1 Bus I/O Panel Controller 3 Alarm Circuits MSP2 Bus Controller The SEER server is the basic mechanism for setting alarms. SEERs can generate four types of reports: • critical • major •...
Page 65: 68K Diagnostics
Maintenance principles 2-39 Out-of-Service diagnostics Out-of-service diagnostics run on a node testing a specific card and its associated transition module, if any. 68K diagnostics The 68K diagnostics have two components - firmware and software. The firmware associated diagnostics run each time a card or node is booted. The diagnostics check the 68K card to ensure that it is operational before attempting to load software.
Page 66: Vp12 Diagnostics
2-40 Maintenance principles The 68K card downloads firmware to each 68302 microprocessor and cooperates with the 68302 firmware to check the following for each T1 span: • 68302 self-test • 68K/68302 communications • T1 line circuit • T1 framer • T1 data path •...
Page 67: On-Line Diagnostics
Maintenance principles 2-41 Startup and offline diagnostics differ slightly for the bus controller. Offline diagnostics on an out-of-service bus controller occur while the system is operating so that interaction between the out-of-service bus controller and the system bus must be limited. Startup diagnostics on a bus controller assumes no active service, so that impact to the system bus can occur.
Page 68 2-42 Maintenance principles 297-7001-503 Standard 02.02 March 1994...
Page 69: Booting The System
Booting the system WARNING Do not change system hardware during booting up As the system boots, do not change system hardware. Cards must not be installed or removed during booting up. Changing the system hardware during booting up can cause the system to enter an undefined state. Booting up procedures The SPM is intended to be operated and maintained without rebooting.
Page 70: 68K Node Loading
3-2 Booting the system 68K node loading As power is applied to each node, each 68K card goes through an initialization process. Included as part of the process is a check of the physical slot address to determine whether the 68K card is the primary or secondary MSP.
Page 71: Booting Problems
Booting the system Booting problems Problems can be experienced during bootup that can cause the boot procedure to fail and leave the system in a non-operational state. Table 3-1 lists booting problems that can be experienced and refers to the applicable trouble clearing procedures in other chapters of this document.
Page 72 3-4 Booting the system 297-7001-503 Standard 02.02 March 1994...
Page 73: Multiserver Processor Node
Multiserver processor node The Multiserver Processor (MSP) node is the controlling node of the Service Peripheral Module (SPM). Multiserver programs run on the MSP and are responsible for booting other nodes, program management, and voice channel allocation. The MSP consists of four cards: •...
Page 74 4-2 Multiserver processor node When a problem occurs, the MSP is not immediately marked faulty. The system attempts to reboot the MSP up to three times. For each attempt, the system waits approximately three minutes before attempting to reboot the MSP again.
Page 75: Maintenance Exceptions
Multiserver processor node • InSvStandby means that the MSP is the redundant node, and is available to take over as the primary MSP. • Disabling MSP1 causes a switchover to MSP2 as the primary one. • Enabling MSP1 when MSP1 is in the faulty state causes MSP1 to go to the InSvStandby state.
Page 76: Cannot Enable Node
4-4 Multiserver processor node If the Window Manager appears on the screen, then the system is partially alive. In either case, attempt to dial-in to the system to determine whether it is alive. If you can dial-in to the system remotely, then, •...
Page 77: Out-Of-Service Diagnostics Fail On 68K Card
Multiserver processor node If MSP1 is in the InService state and you are attempting to disable MSP2, but the disable does not start, then there is a software problem. Call your NT support personnel. If MSP2 starts to disable but does not reboot to the OutOfService state, then there may be hardware problems.
Page 78: System Response
4-6 Multiserver processor node System response The following sections discuss problems that can occur with an MSP and the associated actions that should be taken to solve problems. Lost communication through the terminal If there is no response from the terminal, or there is no indication, determine whether the terminal is working properly.
Page 79: Node Oscillating Between Inservice/Insvstandby And Outofservice
Multiserver processor node Node oscillating between InService/InSvStandby and OutOfService If an MSP is oscillating between the InService/InSvStandby and OutOfService states, a software program is continually crashing and recovering. SEERs should be generated that indicate which program is at fault. From the Node Status screen, attempt to disable and then enable the MSP. If this does not work, call your NT support personnel.
Page 80 4-8 Multiserver processor node Disable the backup MSP through the terminal. This forces the program resource manager to reboot the MSP. It can take up to eight minutes to complete the boot. If the reboot is not successful, then check the following items to ensure that they are provisioned properly in the cabinet: •...
Page 81: Signal Processing Node
Signal processing node The Signal Processing Node (SPN) provides the voice processing for the DMS VoiceMail system. Each SPN has a maximum capacity of 24 channels. SPNs are configured in pairs. If one SPN fails, the overall system capacity is diminished. However, since SPNs are paired (that is SPNs 1-2, 3-4, 5-6, etc.), all users of a failed SPN can still gain access to their mailboxes through the other SPN.
Page 82: Maintenance Exceptions
5-2 Signal processing node Maintenance exceptions Any time a reference is made to replacing or resetting hardware (that is, cards, terminals, etc.) any referenced maintenance procedures should be followed. Follow the appropriate card replacement procedures contained in DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502). Cannot enable node Verify that power is being applied to the node Check that the power converters for the SPN are on.
Page 83: Cannot Enable Card
Signal processing node Check that the cards for the node are seated properly. If not, carefully reseat the card. Check the 68K card status If a node fails to enable, go to the Node Status screen for that node. From this screen, check the status of all the cards in that node.
Page 84: Cannot Enable Dsp Channel
5-4 Signal processing node If the card fails to disable, check for SEERs and refer to the section called Cannot disable card that appears later in this chapter. If the card goes out-of-service, attempt to run the out-of-service diagnostics on the card. Refer to the section in Chapter 2 of this document that pertains to out-of-service diagnostics.
Page 85: Cannot Disable Channel
Signal processing node Replace the card and attempt to disable it. For further information about card replacement, refer to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502). If the card fails to disable, replace the transition module and re-attempt to disable the card. Card fails to disable from the InService state Courtesy disable the SPN and then reseat all of the cards on the node.
Page 86: System Response
5-6 Signal processing node System response The following sections discuss problems that can occur with an SPN and the associated actions that should be taken to solve problems. Voice card/DSP port problems If the voice card and or the DSP port status are faulty or out-of-service, do the following: •...
Page 87: Dsp Stuck In Loading State
Signal processing node DSP stuck in loading state From the DSP Port Status screen, disable the DSP port. If the DSP port does not disable, refer to Cannot disable channel in this chapter. If successful, enable the DSP port. If the DSP port does not enable, refer to Cannot enable channel in this chapter.
Page 88: Noisy Recorded Message Or Noisy Session
5-8 Signal processing node Noisy recorded message or noisy session Determine the DSP ports that are causing the problem and disable them. Call your NT support personnel for assistance. Disk failure Replace the faulty disk pack. Refer to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502).
Page 89: Node Recovery
Signal processing node Node recovery When an SPN shows a faulty status, or the node does not enable, the most expedient method of resolving the problem is to completely replace the defective SPN. This is done by replacing all of the cards, front and back, associated with the node.
Page 90 5-10 Signal processing node 297-7001-503 Standard 02.02 March 1994...
Page 91: Telephony Interface Node
Telephony interface node The Telephony Interface Node (TIFN) provides the interface between T1 spans and Simplified Message Desk Interface (SMDI) links to the DMS VoiceMail system. The TIFN consists of four cards: • 68K card • T1 card • modem transition module •...
Page 92: Maintenance Exceptions
6-2 Telephony interface node Maintenance exceptions Any time a reference is made to replacing or resetting hardware (that is, cards, terminals, etc.) any referenced maintenance procedures should be followed. Follow the appropriate card replacement procedures contained in DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502). Cannot enable node If you cannot enable a node, use procedure 6-1.
Page 93: Cannot Enable Card
Telephony interface node Cannot enable card If you cannot enable a card, use procedure 6-2. Procedure 6-2xxx Cannot enable card Step Action and response Verify that the card is faulty From the Card Status screen, check the status of the card. If the card is in the faulty state, go to the next step and run the out-of-service diagnostics.
Page 94 6-4 Telephony interface node Procedure 6-2xxx Cannot enable card (continued) Step Action and response Disable the node From the Node Status screen, disable the TIFN. If the TIFN is successfully disabled, go to the next step. If you cannot disable the TIFN, then go to the procedure called Cannot disable node in this chapter.
Page 95: Cannot Enable T1 Link
Telephony interface node Cannot enable T1 link If you cannot enable a T1 link, use procedure 6-3. Procedure 6-3xxx Cannot enable T1 link Step Action and response Verify that the T1 link is faulty From the T1 Link Status screen, check the status of the link. If the T1 link is in the faulty state, skip the next two steps and go to the step called Disable the T1 card .
Page 96 6-6 Telephony interface node Procedure 6-3xxx Cannot enable T1 link (continued) Step Action and response Run the out-of-service diagnostics From the Card Status screen, run the out-of-service diagnostics for the T1 card. If the out-of-service diagnostics pass, go to the next step. If the out-of-service diagnostics fail, go to the procedure called Out-of-service diagnostics on T1 card fail in this chapter and then return to this procedure and go to the next step.
Page 97: Cannot Enable T1 Channel
Telephony interface node Cannot enable T1 channel If you cannot enable a T1 channel, use procedure 6-4. Procedure 6-4xxx Cannot enable T1 channel Step Action and response Disable the T1 channel From the T1 Channel Status screen, disable the T1 channel. If the T1 channel is successfully disabled, go to the next step.
Page 98: Cannot Enable Smdi Link
6-8 Telephony interface node Cannot enable SMDI link If you cannot enable an SMDI link, use procedure 6-5. Procedure 6-5xxx Cannot enable SMDI link Step Action and response Disable the SMDI link From the SMDI Link Status screen, disable the SMDI link. If the SMDI link is successfully disabled, go to the next step.
Page 99: Out-Of-Service Diagnostics On 68K Card Fail
Telephony interface node Out-of-service diagnostics on 68K card fail If the out-of-service diagnostics on the 68K card fail, use procedure 6-6. Procedure 6-6xxx Out-of-service diagnostics on 68K card fail Step Action and response Replace the 68K card Go to the procedure for replacing the NTGX05AA 68K card in the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502) .
Page 100: Cannot Disable Node
6-10 Telephony interface node Cannot disable node If you cannot disable the TIFN, use procedure 6-8. Procedure 6-8xxx Cannot disable node Step Action and response Reseat the 68K card Transfer any active traffic from the TIFN that cannot be disabled. Unseat the 68K card momentarily and then reseat the 68K card.
Page 101: Cannot Disable Card
Telephony interface node 6-11 Cannot disable card If you cannot disable the 68K card, use procedure 6-9. Procedure 6-9xxx Cannot disable card Step Action and response Disable the node From the Node Status screen, disable the TIFN that is associated with the card that cannot be disabled.
Page 102: Cannot Disable T1 Channel
6-12 Telephony interface node Cannot disable T1 channel If you cannot disable a T1 channel, use procedure 6-11. Procedure 6-11xxx Cannot disable T1 channel Step Action and response Disable the T1 span From the T1 Link Status screen, disable the T1 span that is associated with the T1 channel that cannot be disabled.
Page 103: Symptom Response
Telephony interface node 6-13 Symptom response The following sections discuss problems that can occur with a TIFN and the associated actions that should be taken to solve problems. Node stuck in loading state If a TIFN is stuck in the loading state, use procedure 6-13. Procedure 6-13xxx Node stuck in loading state Step...
Page 104: Channel Stuck In Pending State
6-14 Telephony interface node Channel stuck in pending state If a T1 channel is stuck in the pending state, use procedure 6-14. Procedure 6-14xxx Channel stuck in pending state Step Action and response Disable the T1 channel From the T1 Channel Status screen, disable the T1 channel. If the T1 channel is successfully disabled, go to the next step.
Page 105: Channel Stuck In Loading State
Telephony interface node 6-15 Channel stuck in loading state If a T1 channel is stuck in the loading state, use procedure 6-15. Procedure 6-15xxx Channel stuck in loading state Step Action and response Check for SEERs Check for a SEER with the following error string: Could not login to agent SLID : xxx 8001 If such an error string is present, go to the next step.
Page 106: Channel Stuck In Out-Of-Service State
6-16 Telephony interface node Channel stuck in out-of-service state If a T1 channel is stuck in the out-of-service state, use procedure 6-16. Procedure 6-16xxx Channel stuck in out-of-service state Step Action and response Enable the T1 channel From the T1 Channel Status screen, enable the T1 channel. If the T1 channel is successfully enabled, you have completed this procedure.
Page 107: Channel Stuck In Faulty State
Telephony interface node 6-17 Channel stuck in faulty state If a T1 channel is stuck in the faulty state, use procedure 6-17. Procedure 6-17xxx Channel stuck in faulty state Step Action and response Disable the T1 channel From the T1 Channel Status screen, disable the T1 channel. If the T1 channel is successfully disabled, go to the next step.
Page 108: Channel Stuck In No-Resource State
6-18 Telephony interface node Channel stuck in no-resource state If a T1 channel is stuck in the no-resource state, use procedure 6-18. Procedure 6-18xxx Channel stuck in no-resource state Step Action and response Check the status of partner SPN From the System Status screen, check the SPN channels that are associated with the TIFN that has a channel stuck in no-resource.
Page 109: Node Rebooting
Telephony interface node 6-19 Node rebooting If a TIFN continuously attempts to reboot, use procedure 6-19. Procedure 6-19xxx Node rebooting Step Action and response Node reboots continuously If a TIFN is continuously attempting to reboot (that is, constantly changing from the faulty state to the rebooting state and back again), then go to the next step.
Page 110: T1 Link Alarms
6-20 Telephony interface node T1 link alarms If T1 link alarms are encountered, use procedure 6-20 to resolve the alarm(s). Figure 6-1 illustrates the location of the three TIFN cable sets that are referred to in the following procedure. Figure 6-1xxx TIFN cable sets DMS VoiceMail Link 1...
Page 111 Telephony interface node 6-21 Procedure 6-20xxx T1 link alarms (continued) Step Action and response Enable the T1 link From the T1 Link Status screen, enable both the primary and secondary T1 links. If the T1 links are successfully enabled, go to the next step. If the T1 links do not enable, go to the procedure called Cannot enable T1 link in this chapter.
Page 112 6-22 Telephony interface node Procedure 6-20xxx T1 link alarms (continued) Step Action and response Enable the node From the Node Status screen, enable the TIFN. If the TIFN is successfully enabled, you have completed this procedure. If the TIFN does not enable, go to the procedure called Cannot enable node in this chapter.
Page 113 Telephony interface node 6-23 Procedure 6-20xxx T1 link alarms (continued) Step Action and response Check channel bank Diagnose the channel bank that connects to cable set 1. Refer to the documentation supplied by the channel bank manufacturer. If after checking the channel bank and making any required adjustments no alarm exists, you have completed this procedure.
Page 114: Smdi Link Alarms
6-24 Telephony interface node SMDI link alarms Refer to the section entitled SMDI links in Chapter 8 for information on how to clear SMDI alarms. Node recovery When a TIFN appears to be faulty or the node does not enable, the most expedient method of resolving the problem is to completely replace the defective TIFN.
Page 115: Disks And Tape Drives
Disks and tape drives Interpreting Class 66 disk managing SEERs The disk manager is the operating system component that maintains disk configuration. It generates SEERs to report errors encountered during file system disk accesses and to log disk mirroring maintenance operations. Disk manager SEERs identify disks by node number and SCSI ID.
Page 116 7-2 Disks and tape drives Figure 7-1xxx Node numbers and corresponding disk and pack numbers Node # Disk # Pack* Node # Disk # Pack* * A pack can include one disk drive, two disk drives, or a disk drive and a tape unit.
Page 117: Class 6602
Disks and tape drives Class 6602 Error string format 6602 node n>disk a down; disk b remains Cause One of the disks in a mirrored disk pair has gone down. Action If this SEER appears during normal operation, replace the failed disk indicated by the SEER using the Disk Maintenance and Disk Pair Status screens on the terminal.
Page 118: Class 6603
7-4 Disks and tape drives Class 6603 Error string format 6603 node n disk d>sense key: s error code: e [block: b] Cause The disk drive has reported an exception. The sense key number indicates the exception type as given below. The error code included is vendor unique, and a block number may also be shown.
Page 119: Class 6604
Disks and tape drives Class 6604 Error string format 6604 node n disk d > drive error: e Cause The SCSI device reported an exception. The drive error number indicated the exception type as listed below: Driver Error Meaning Selection Timeout Unexpected Timeout Bus Reset Input Parity Error...
Page 120: Class 6605
7-6 Disks and tape drives Check that the associated SCSI cables are firmly connected. Reseat the disk pack indicated by the SEER. Reseat the 68K card associated with the failed disk pack. Replace the 68K card associated with the failed disk pack. Replace the disk pack indicated by the SEER.
Page 121: Tape Drive Errors
Disks and tape drives Tape drive errors The tape drive should be replaced when you receive repeated errors when attempting to write to tape. You should also consider replacing the tape drive if the light on the front of the tape drive is out or if you cannot hear the tape spinning.
Page 122 7-8 Disks and tape drives 297-7001-503 Standard 02.02 March 1994...
Page 123: Peripherals And Links
Peripherals and links Local terminals If the local terminals are having problems, do the following in sequence: Check the following port setting information: baud rate, XON/XOFF, character length, and start bit. Refer to the DMS V oiceMail System Installation and Modification Guide (NTP 297-7001-504) for correct port setting information.
Page 124: Multiple Administration Terminals
8-2 Peripherals and links Multiple administration terminals If multiple administration terminals that are connected to a telephony interface node (TIFN) experience problems, do the following: • Verify that the TIFN is operating properly. If necessary, use the procedures in Chapter 6, Telephony Interface Node, to recover the TIFN. •...
Page 125: Remote Terminals
Peripherals and links Remote terminals If remote terminals are having problems, do the following: Verify the dial-in DN. Hold down the BREAK key. Type <CNTL> R. Type <CNTL> Q. Type <CNTL> W. Check the DMS VoiceMail System Installation and Modification Guide, NTP 297-7001-504 , for the following port setting information: baud rate, XON/XOFF, character length, and start bit.
Page 126: Local Printers
8-4 Peripherals and links Local printers No printer output Node printer port setup is incorrect Check that the node printer port is set up as explained in the DMS VoiceMail System Installation and Modification Guide (NTP 297-7001-504). Printer setup is incorrect Verify that the printer setup matches the node printer port setting.
Page 127: Backup Printers
Peripherals and links Backup printers No printer output Terminal printer port setup is incorrect Check that the terminal printer port is setup as explained in the terminal’s installation manual. Printer setup is incorrect Verify that the printer setup matches the terminal printer port setting. Cable connections to the printer are incorrect Verify that the printer cable used is the correct type for the printer port of the terminal.
Page 128: Smdi Links
8-6 Peripherals and links SMDI links Link bounces up and down constantly Check the connectivity of the related SMDI cables, and verify that the external modem settings are correct. For further information on modem settings, refer to the DMS VoiceMail Planning and Engineering Guide, 297-7001-100.
Page 129: If The System Shows An Alarm
Peripherals and links connected, then an InsrvRedAlarm is displayed. These alarm conditions are not the same as T1 alarms. After waiting about five minutes, once all of the T1 channels and the system appears to be ready but the external modem is not yet connected, check the modem connections and the wiring on the DMS VoiceMail modem transition module.
Page 130 8-8 Peripherals and links message should appear on the LCD for a UDS modem. If not, disable and then enable the link. Return to service (RTS) the link and then RTS the card. Attempt to make a call if there is no link up message, then check the DMS side to determine if the MPC card is enabled.
Page 131: Link Up For A Short Time And Then Down
Peripherals and links Link up for a short time and then down Verify that the cables are of the type recommended for SMDI links. Check the connectivity of the related SMDI cable. Verify that the SMDI links are datafilled correctly. Refer to the DMS VoiceMail Translation Procedures, 297-7001-310.
Page 132: T1 Links
8-10 Peripherals and links T1 links All channels are not working Channel status remains NoResource Check if the corresponding nodes are inservice. If not, enable the nodes. Check if the corresponding T1 links are inservice. If not, enable the T1 links.
Page 133: Some Channels Are Not Working
Peripherals and links 8-11 If SEERs indicate failed on ‘Voice Answer,’ check that the agent login/logout codes datafilled in the hardware database match the ones configured on the DMS switch-side. Some channels are not working Disable and enable the channel to see if there is any sign of failing during the Agent login/logout operations.
Page 134 8-12 Peripherals and links 297-7001-503 Standard 02.02 March 1994...
Page 135: Cabinet And I/O Connections
Cabinet and I/O connections Frame supervisory panel For information on how to clear alarms related to the frame supervisory panel of the Service Peripheral Module (SPM), refer to the BCS34, or later, issue of the DMS-100 Lines, Trunks, and Peripherals - External Subsystems Alarm and Performance Monitoring Procedures (NTP 297-1001-583).
Page 136 9-2 Cabinet and I/O connections Figure 9-1 Input/output panel locations - rear SPM view Shelf 39 I/O Panels I/O Panels Mount Inside Mount Inside Shelf 26 I/O connectors inside of the cabinet Connectors on the inside of the cabinet bulkhead are designated J1 through J9 as well as JX and JY on the daughterboard.
Page 137: Input/Output Panel Replacement
Cabinet and I/O connections I/O connectors outside the cabinet Connectors on the outside of the cabinet bulkhead are designated P1A through P1C and P10 and P11. Connectors P1A to P1C provide cable connections for the active current loop and modem pairs to the main distribution frame. Connectors P10 provides alarm relay connections to the main distribution frame.
Page 138 9-4 Cabinet and I/O connections Input/output panel daughter board replacement Removing the input/output panel daughterboard assembly disconnects modem links from the TIFNs and current loops from MSPs and SPNs. If these links are inservice (SMDI connections, remote terminal connections, or local terminal current loop connections), they should be taken out-of-service before the daughterboard is removed.
Page 139: Input/Output Cabling
Cabinet and I/O connections The input/output panel is then removed and replaced in the reverse order of the above steps. Input/output cabling Input/output cable identification Figure 9-3 identifies all of the cables that are connected between the four input/output panels and the two electronics shelves of the SPM. Internal T1 cables are also shown although these are not connected to the input/output panels.
Page 140 9-6 Cabinet and I/O connections Figure 9-3xxx Input/output cable identification Inside Outside Outside Inside Loop Back TIFN TIFN Node Node Node Node Node Node Secondary Electronics Shelf Outside Inside Inside Outside Loop Back TIFN TIFN Node Node Node Node Node Node Node Node...
Page 141 Cabinet and I/O connections Figure9-4xxx Internal backplane cable connections for shelf 26 GX0147 = Left Hand BulkHead GX0148 = Right Hand BulkHead NT GX04BA Shelf 39 Slot 07 NT GX04BA GX0147 GX0148 P3 P2 P1 P1 P2 P3 P4 GX0147 P3 P2 P1 Cable Codes...
Page 142 9-8 Cabinet and I/O connections Figure 9-5xxx Internal backplane cable connections for shelf 39 GX0147 = Left Hand BulkHead GX0148 = Right Hand BulkHead NT GX04BA Shelf 26 Slot 07 NT GX04BA GX0147 P1 P2 P3 P4 Cable Codes P2 P2 J2 J3 J1 J2 J3 J4 9 10 11 12 13 14 15 16 17 18 19...
Page 143 Cabinet and I/O connections Figure 9-6xxx Internal backplane cable connections for shelf 00 Module 1 Module 2 Module 3 Module 4 Shelf 26 26/30R 26/29R 26/19R 26/16R Slot 30 NTGX06AA NTGX06AA NTGX06AA NTGX06AA R = Rear GX0114 GX0103 GX0103 GX0103 GX0114 GX0102 GX0103...
Page 144 9-10 Cabinet and I/O connections Figure 9-7xxx Internal back plane cable connections for shelf 13 Module 3 Module 4 Module 5 Module 6 Shelf 39 39/30R 39/29R 39/19R 39/15R Slot 30 NTGX06AA NTGX06AA NTGX06AA NTGX06AA R = Rear GX0103 GX0103 GX0103 GX0103 GX0114...
Page 145: Input/Output Cable Replacement
Cabinet and I/O connections 9-11 Input/output cable replacement If the replacement of cards and transition modules fail to clear a fault condition, the cabling from the transition module of the identified node can be replaced. If the node is fully out-of-service, the cable can be replaced without any further preparations.
Page 146 9-12 Cabinet and I/O connections Table 9-2xxx Input/output cable identification (continued) Node Node Port Shelf Connector type number number Function 26 Left SPN2 Node 4 Port 2 Modem Port (Cont’d) SPN2 Node 4 Port 3 SPN2 Node 4 Port 4 SPN3 Node 5 Port 1...
Page 147 Cabinet and I/O connections 9-13 Table 9-2xxx Input/output cable identification (continued) Node Node Port Shelf Connector type number number Function 39 Left SPN5 Node 7 Port 1 SPN5 Node 7 Port 2 Modem Port SPN5 Node 7 Port 3 SPN5 Node 7 Port 4 SPN6...
Page 148: Input/Output Cable Replacement
9-14 Cabinet and I/O connections Input/output cable replacement For the specific cable to be replaced, identify the signals on the cable from the previous section and then follow the recommended procedure that is listed in Table 8-3. The actual procedures are discussed after Table 9-3. Table 9-3xxx Recommended I/O cable replacement procedures Shelf...
Page 149 Cabinet and I/O connections 9-15 Table 9-3xxx Recommended I/O cable replacement procedures (continued) Shelf I/O connector Recommended procedure 39 Left T1-2 Procedure C (cont’d) T1-3 Procedure C T1-4 Procedure C Procedure A Take the associated nodes out-of-service by following the appropriate procedures contained in the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502).
Page 150: How The Meridian Mail Bus Is Configured
9-16 Cabinet and I/O connections How the Meridian Mail bus is configured Figure 9-8 illustrates how the Meridian Mail bus (MMBus) is physically configured. Figure 9-8xxx MMBus physical configuration Secondary Electronic Shelf Extender Cables Primary Electronic Shelf Rear View Bus extender cable replacement To replace an extender cable between NTGX04BA bus extender transition modules, refer to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502) for instructions on how to disable the affected transition...
Page 151: Bus Extender Transition Module Replacement
Cabinet and I/O connections 9-17 Bus extender transition module replacement To replace an NTGX04BA bus extender transition module, refer to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502). After replacing an extender cable or bus extender transition module, monitor the reloading of all the affected nodes. Typically, the nodes on the secondary electronics shelf are affected.
Page 152: Secondary Shelf Bus Terminator Symptoms
9-18 Cabinet and I/O connections Remove and inspect the NTGX04AA bus terminator transition module from the primary electronics shelf. Check the switch settings and fuses. For detailed information on card removal, refer to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502). Secondary shelf bus terminator symptoms Nodes time-out booting If the nodes on the secondary shelf time-out on a diagnostics request from a...
Page 153: Other Bus Terminator Symptoms
Cabinet and I/O connections 9-19 Remove and inspect the NTGX04AA bus terminator transition module from the secondary electronics shelf. Check the switch settings and fuses. For detailed information on card removal, refer to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502). Other bus terminator symptoms No SEERs Local terminal lockup...
Page 154: Bus Extender Transition Module Symptoms
9-20 Cabinet and I/O connections Bus extender transition module symptoms Nodes unload on secondary shelf If the nodes on the secondary electronics shelf unload while in service, there may be a problem with the NTGX04BA bus extender transition module on the primary electronics shelf.
Page 155 Cabinet and I/O connections 9-21 Referring to the DMS VoiceMail Card Replacement Procedures (NTP 297-7001-502), reseat and replace the MMBus extender components in the following order and check for clearing of the problem after each step: extender cables connected to the NTGX04BA extender on both shelves. extender cable NTGX04BA on the right-side primary shelf as per Figure 9-8.
Page 156 9-22 Cabinet and I/O connections 297-7001-503 Standard 02.02 March 1994...
Page 157: Remote View Bootup Diagnostics
10-1 Remote view bootup diagnostics The following procedure is used by maintenance personnel for logging in to the service peripheral module (SPM) remotely and viewing the bootup diagnostics for both the signal processing node (SPN) and the multiserver processor (MSP) node. The procedures outlined in this section describe how to reconfigure the modem from a leased-line mode to a mode that will accept auto-answer and other parameters necessary for remote access to the SPN.
Page 158: Modem Bix Tip And Ring Pairs For Msps And Spns
10-2 Remote view bootup diagnostics Reboot the node again by disabling the SPN through the the MMI. If the MMI is unavailable, or you are unable to reboot the node. Unseat the 68K card to force a reboot. At this point, the user should be able to view the bootup sequence remotely. Note: In place of steps 1 and 2, you can change the hardware database port name of the second port to UATxxxx and make it a terminal type with a window size 80x24.
Page 159 Remote view bootup diagnostics 10-3 Table 10-3xxx Modem tip and ring pairs (shelf 39 left) I/O Panel connector Pin number Signal Binder / Color MR52 Blue / G2W (SPN5) MT52 Blue / G1W MR12 Blue / BL2BK (SPN6) MT12 Blue / BL1BK Table 10-4xxx Modem tip and ring pairs (shelf 39 right) I/O Panel connector...
Page 160 10-4 Remote view bootup diagnostics 297-7001-503 Standard 02.02 March 1994...
Page 161: Online Recovery
11-1 Online recovery Problems encountered during online maintenance can cause the system to abort a maintenance procedure and leave the system in an incomplete state. When problems of this type are encountered during an initial system installation or during software modifications to the system, use the following procedure to recover the system.
Page 162 11-2 Online recovery Summary of Online recovery Find the online procedure that is causing the problem. Unseat MSP1 Was it a Were you in You have software disk, boot from the Prepare completed this MSP2, resynch upgrade? Stage? procedure. disks. Unseat MSP1 Was it a Were you in...
Page 163 Online recovery 11-3 Online recovery Step Action Determine the online system maintenance procedure that you were using when the problem was encountered. If you were doing Software Upgrade Go to step 2. Language Expansion Go to step 5. Hardware Modification Go to step 8.
Page 164 11-4 Online recovery Online recovery (continued) Step Action Recovering an online language expansion Determine which stage of the online language expansion procedure the problem was encountered. If you were in the Prepare stage From the OnLine Maintenance Menu, select the Reset On-line Maintenance Status menu item.
Page 165 Online recovery 11-5 Online recovery (continued) Step Action Copy the backup StartList:RW1:PD:Startlist.back to :RW1:PD:Startlist. Copy the backup OFS/1/ofs/vm.back to /1/ofs/vm. Copy the backup Hardware Database /1/hwd.back to /1/hwd. Copy the backup System Record /1/isr1sysrec.back to /1/isr1sysrec. From the OnLine Maintenance Menu, select the Reset On-line Maintenance Status menu item.
Page 166 11-6 Online recovery 297-7001-503 Standard 02.02 March 1994...
Page 168 DMS-100 Family DMS VoiceMail Trouble-locating and alarm-clearing procedures © 1993, 1994 Northern Telecom All rights reserved. Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.

Northern Telecom DMS-100 Series Manual

Quick Links

Need help?

Questions and answers

Related Manuals for Northern Telecom DMS-100 Series

Summary of Contents for Northern Telecom DMS-100 Series

Table of Contents