Page 1 Critical Release Notice Publication number: 297-8213-550 Publication release: Standard 09.03 The content of this customer NTP supports the SN07 (DMS) and ISN07 (TDM) software releases. Bookmarks used in this NTP highlight the changes between the baseline NTP and the current release.
Page 2 Publication History September 2004 Standard release 09.03 for software release SN07 (DMS) and ISN07 (TDM). Change of syntax entry in Maintenance overview section on page 1-5 according to CR Q00891462. March 2004 Standard release 09.02 for software release SN06 (DMS) and ISN06 (TDM). Change of phone number from 1-800-684-2273 to 1-877-662-5669, Option 4 + 1.
Page 3 297-8231-550 DMS-100 Family Subscriber Carrier Module-100S Maintenance Manual XPM10 and up Standard 09.01 August 1998...
Page 5 DMS-100 Family Subscriber Carrier Module-100S Maintenance Manual Publication number: 297-8231-550 Product release: XPM10 and up Document release: Standard 09.01 Date: August 1998 1994, 1995, 1996, 1997, 1998 Northern Telecom All rights reserved Printed in the United States of America NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom.
Page 8 Revision history This document has been revised for release NA17. Information about troubleshooting an SMS line equipped mismatch has been added in an Appendix. XPMTLC0001SMS XPM_PARTITION MICA...
Page 9: Table Of Contents
Contents About this document How to check the version and issue of this document vii References in this document vii What precautionary messages mean viii How commands, parameters, and responses are represented ix Input prompt (>) ix Commands and fixed parameters ix Variables ix Responses ix Maintenance summary...
Page 10 iv Contents Digital phase lock loop (DPLL) clock failure 1-73 DS-1 link automatic maintenance 1-73 Protection switching 1-73 Subscriber lines automatic maintenance 1-84 Escalation to manual maintenance 1-85 Manual protection switching 1-85 SMS hardware Hardware components 2-1 SMS module 2-3 The RCS module 2-5 The DS-1 links connecting the SMS and the RCS 2-5 Additional components 2-7...
Page 11 Contents v Manually busying SMS C-side links 7-141 Returning a card for repair or replacement 7-149 Removing and replacing a card 7-153 Locating and clearing SMS trouble Trouble isolation and correction Locating and clearing faults 9-1 Problem condition indicators 9-1 Fault isolation tests for the SMS 9-3 Handling a SysB SMS unit 9-3 Handling an ISTb SMS unit 9-6...
Page 12 vi Contents Troubleshooting chart 10-1 Clearing a SMS alarm 10-1 Clearing an RCS alarm 10-5 Advanced troubleshooting procedures 11-1 Advanced trouble locating procedures 11-1 Using the XPM footprint tool 11-1 Accessing the data collected 11-3 Limits 11-9 Powering up the SMS 11-9 Powering down SMS 11-10 SMS routine maintenance procedures 12-1...
Page 13: About This Document
About this document How to check the version and issue of this document The version and issue of the document are indicated by numbers, for example, 01.01. The first two digits indicate the version. The version number increases each time the document is updated to support a new software release. For example, the first release of a document is 01.01.
Page 14: What Precautionary Messages Mean
viii About this document Translations Guide XPM Translations Guide What precautionary messages mean The types of precautionary messages used in NT documents include attention boxes and danger, warning, and caution messages. An attention box identifies information that is necessary for the proper performance of a procedure or task or the correct interpretation of information or data.
Page 15: How Commands, Parameters, And Responses Are Represented
About this document ix CAUTION Possibility of service interruption or degradation CAUTION Possible loss of service Before continuing, confirm that you are removing the card from the inactive unit of the peripheral module. Subscriber service will be lost if you remove a card from the active unit.
Page 16 x About this document The following excerpt from a procedure shows the command syntax used in this document: Manually busy the CTRL on the inactive plane by typing >BSY CTRL ctrl_no and pressing the Enter key. where ctrl_no is the number of the CTRL (0 or 1) Example of a MAP response : FP 3 Busy CTRL 0: Command request has been submitted.
Page 17: Maintenance Summary
Maintenance summary The subscriber carrier system consists of the Subscriber Carrier Module-100S (SMS) and one or more Remote Concentrator SLC-96 (RCS) modules. This document contains descriptions and step-by-step information to maintain the system at an efficient operating level. This information relates to the SMS, RCS, and DS-1 links.
Page 18: Functional Description Of The Sms
1-2 Maintenance overview — routine exercise (REx) tests — automatic subscriber lines tests Escalation to manual maintenance. This section discusses manual protection switching. Manual protection switching occurs when the SMS cannot switch a protection link into service. The SMS cannot switch a protection link into service after the SMS detects a fault on a primary link.
Page 19: The Sms Configuration
Maintenance overview 1-3 take down of connections to and from the RCS-subscriber record of dial pulse digits detection of use of flash feature forward messages RCS to CM and CM to RCS. reception and issue of coin service control messages that include: —...
Page 20 1-4 Maintenance overview The SMS configuration Shelf 0 Shelf 1 A maximum of four ports for each plane A maximum of four ports for each plane DS30 interface DS30 interface Plane 0 Plane 1 128 channels 128 channels 128 internal 128 internal Formatter Formatter...
Page 21 Maintenance overview 1-5 The universal processor (UP) card (NTMX77) replaces separate master and signal processor and memory cards. Electrically erasable programmable read only memory (EEPROM) on the NTMX77 card contains firmware for downloading. Firmware in EEPROM allows you to load firmware on a manually busy (ManB) XPM or unit separate from the RAM load.
Page 22 1-6 Maintenance overview The NT6X42 card performs channel supervision message (CSM) control. The CSM is a 40-bit message that contains 24 synchronization bits, 8 integrity bits, and 8 data bits. The system transfers the complete message over 40 frames. The integrity bit between the peripheral module (PM) that sends the CSM and the PM that receives the CSM must match.
Page 23 Maintenance overview 1-7 Use the following parameters to load the local loadfile: WARNING Possible service interruption The LOCAL LOADFILE option of the LOADPM command has a parameter of [<file> string}]. If you use this file_name parameter, you must use the loadfile named in the parameter.
Page 24 1-8 Maintenance overview When you first install the NT7X05 card, the loadfile is invalid. Load the loadfile with the XPMSTOR parameter. Use the enhanced QUERYPM command with the new FILES option to view the state of files on the NT7X05. An example of the QUERYPM command follows. >QUERYPM FILES Example of a MAP response: Unit 0:...
Page 25: The Sms Internal Messaging
Maintenance overview 1-9 The SMS internal messaging The following diagram shows the message paths in the SMS. Message paths in SMS Host communication DS30 Interface 6X40 DS-30 links from the host XPM Speech Bus Formatter 6X41 Channel Supervision Message 6X42 Peripheral Speech Loader 7X05...
Page 26 1-10 Maintenance overview The UP formulates the SMS messages intended for the CM. The UP directs the messages. The UP sends the messages through the DS30 cards from the message and tone card (NT6X69). The CM messages are placed on channel 0 of DS30 links 0 and 2.
Page 27 Maintenance overview 1-11 Functional block diagram of the SMS with XPM PLUS DS30 Interface 6X40 Msg & Wired links Tone Wired link To other 6X69 unit Speech Formatter 6X41 6X42 Unified Wired link A–bus Processor memory MX77 6X78 Peripheral Loader 7X05 Universal Tone Receiver...
Page 28: Spontaneous Call Waiting With Disposition (Dscwid)
1-12 Maintenance overview Spontaneous Call Waiting with disposition (DSCWID) You must have the NT6X78AB, the NT6X69AD, and the NT6X92BB cards to comply with the ADSI protocol. The ADSI protocol supports CLASS features that provide information that relies on display to subscribers with ADSI-compatible CPE.
Page 29 Maintenance overview 1-13 Example of a DSCWID call on an ADSI set Data ACK (DTMF A) Data Flash Softkey hit DTMF digit DTMF digit Example of a DSCWID call on a SCWID set Data ACK (DTMF D) Data Flash Select option DTMF digit DTMF digit DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 30 1-14 Maintenance overview Example of a DSCWID call on a 2500 set Data Flash to answer Flash Select option DTMF digit DTMF digit When a UTR channel is not available, the system continues to send alerting signals to the CPE. If all UTR channels are not available, the system does not send data to the CPE.
Page 31 Maintenance overview 1-15 Later DSCWID option selections on a SCWID or 2500 set use a new timer (T-flash). The system uses the T-flash time when a subscriber answers the call. The T-flash timer allows time for the customer to select an option after a flash.
Page 32 1-16 Maintenance overview The DSCWID with ADSI set allocations Stable two-party call state New incoming call detected alerting applied Waiting call state BUSY DROP ANSWER HOLD CONF Flash + Flash + Flash + *Flash + Flash + Flash + DEFAULT DTMF 9 DTMF 8 DTMF 7...
Page 33: Thr Xpm Intermodule Communication
Maintenance overview 1-17 Thr XPM intermodule communication The extended multiprocessor system (XMS)-based PM (XPM) uses the IMC links to exchange call processing and diagnostic messages. The IMC links transmit software loads and related data between the active and inactive units. The two IMC links used in the XPM are the following: the message protocol and tone card (NT6X69) the unified processor card (NTMX77) The message protocol card is the primary IMC link in the XPM.
Page 34 1-18 Maintenance overview Data is set in the active unit of an XPM through the node and link return-to-service (RTS). Data is also set through state changes that are triggered externally. Data goes to the inactive XPM unit through the group and separate messages of the current XPM data-synchronization mechanism.
Page 35 Maintenance overview 1-19 a complete description of the datafill for table PMNODES, refer to the XPM Translations Reference Manual. Enhanced XPM node table synchronization Data Active unit Inactive unit Configuration table map Node and Node and information does not port tables port tables transmit to the inactive unit Feature AF5678 adds a new software component, configuration data table...
Page 36 1-20 Maintenance overview The system adds a new XPM, but not during a one night process (ONP) conversion. Nodes added during ONP are not new nodes. These nodes must be in-service. Note: When an office receives an initial software load with the new node table management system, the CM gains control.
Page 37: Information Flows To And From The Sms
Maintenance overview 1-21 To implement the enhanced synchronization capability that feature AF5678 provides, the following functions are created or changed: The XPM does not derive node table data from a part of data sent from the CM. The CM specifies all the data that the node and port tables contain.
Page 38 1-22 Maintenance overview Control messaging between the SMS and the RCS The derived data link (DDL) is the message protocol that transfers messages from the SMS to the RCS. The DDL transfers messages from the RCS to the SMS. The DDL is a 2.2 Kbit/s data path. The system robs frame signaling (Fs) bits to form the DDL.
Page 39 Maintenance overview 1-23 The DDL message bits and field names (continued) DDL bits Field name Bits 15 through 17 Maintenance field (M-field). The M-field on the A-link carries information for all shelves. This M–field controls card and customer loop testing. Bits 18 and 19 Alarm data link field (A-field).
Page 40 1-24 Maintenance overview start or stop ringing start or stop forward disconnect scan for on-hook and off-hook collect ANI/Coin information collect channel maintenance information The UP collects the return signaling information from the RCS. This information includes the following data: call origination call disconnect digit collection...
Page 41: Call Processing
Maintenance overview 1-25 Disconnect—subscriber goes on-hook from off-hook and stays on-hook for a minimum of 1550 ms (flash option allowed). When the flash option is not allowed, disconnect occurs when a subscriber line goes on-hook from off-hook. The subscriber stays on-hook for a minimum of 400 ms.
Page 42 1-26 Maintenance overview send dial tone to an off-hook subscriber that originated a call scan for and collecting digits ring a subscriber line send audible ringback tone to a calling subscriber trip ringing on a called subscriber when that subscriber goes off-hook disconnect the call-holding bridge on telephone keysets.
Page 43 Maintenance overview 1-27 Call processing software modules Central control ANI/Coin Channel and loop testing Forward disconnect Channel assign and UP ringing deassign task looping test request Digit collection DDL facility A/B bit facility routine Digit message scanning A/B DDL ANI/Coin card collecting patterns...
Page 44 1-28 Maintenance overview requests for channel and loop tests requests for the system to generate a forward disconnect pattern on a channel to an RCS. The forward disconnect pattern causes a line card with an associated keyset to force the keyset to drop the call-holding bridge.
Page 45 Maintenance overview 1-29 The DDL facility maintains an inventory of available DS-1 channels. When DDL facility receives TPT messages that request channels assignments and deassignments (Mode II), the DDL facility updates this inventory. Subscriber lines that connect to a Mode I or Mode III RCS have set DS-1 channel assignments.
Page 46 1-30 Maintenance overview The UP receives a start or stop ringing message from the TPT. After the UP receives a message, the UP ringing task sends messages to the A/B-bit facility. The A/B-bit facility sends the required A- and B-bits on the correct P-side channel.
Page 47 Maintenance overview 1-31 The DDL facility sets equipped, active channels to available in the inventory of the DDL facility. A TPT message causes the process to occur. The TPT sends a message to the A/B-bit facility. This message requests the A/B-bit facility to scan equipped, active channels for off-hook. Call processing sequence of events—originating end The following sequence of events occurs during call processing at the originating end of a call:...
Page 48 1-32 Maintenance overview Call processing sequence of events—terminating end The following sequence of events occurs during call processing at the terminating end of a call: 1 The TPT sends a message to the UP ringing task to start ringing the called subscriber loop.
Page 49: Warm Swact
Maintenance overview 1-33 Configuration for digit collection with UTR present receiver Network originating line Warm SWACT A Warm SWACT allows the inactive unit of the SMS to maintain established calls (calls in the talking state). The inactive unit of the SMS can process new calls.
Page 50 1-34 Maintenance overview The following limits apply to the Warm SWACT feature: The Warm SWACT feature maintains calls. If a subscriber line test is active and a Warm SWACT occurs, the test fails. Synchronization of call data between mates occurs when call processing does not occur.
Page 51 Maintenance overview 1-35 Subscriber A calls subscriber B and establishes a speech path. Subscriber A has the call waiting (CWT) line service option. A third party dials subscriber A. Subscriber A receives information about the waiting call. A controlled Warm SWACT occurs on the SMS that connects to subscriber A.
Page 52 1-36 Maintenance overview If the SWACT controller denies a manual request for a SWACT, you receive this information. You receive a reason for the denial. The message informs you that you can enter the SWACT FORCE command to override the SWACT controller.
Page 53 Maintenance overview 1-37 stability from the original active unit over the SWACT back. The system drops new calls made after the SWACT. The system drops new calls made before SWACT back. If a SWACT back is not successful, both units of the XPM become system busy and return to service.
Page 54 1-38 Maintenance overview The SWACT controller polls data in the XPM to determine if the inactive unit can maintain activity. The XPM communicates to the SWACT controller query if the active unit can comply with the request to drop activity. State data determines if the active unit can or cannot drop activity. For more information about XPM state data, refer to the section on Pre-gain audit in this document.
Page 55 Maintenance overview 1-39 The sequence for a controlled and uncontrolled SWACT and the SWACT-back operation of feature AN0538 appears in this figure. The following sections describe this feature. SWACT sequence 1. CC uses manual command 1. SMS starts SWACT or REx schedule to start because of trap or error warm SWACT 2.
Page 56 1-40 Maintenance overview SWACT back example SWACT ISTb controller Unit 0 >SW ACT Data polling InSv Unit 1 Active diagnostic XPM status history Inactive ISTb SWACT refused >SWACT FORCE Unit 0 by SWACT Controller InSv Unit 1 Active Inactive 1. Both units are in service. Unit 0 is active. 2.
Page 57 Maintenance overview 1-41 SWACT-back If an SMS does not receive a gain-acknowledged message from the CC, the original active SMS unit initiates a SWACT-back. During a SWACT-back, the original active SMS unit attempts to regain activity. If successful, the inactive unit is set SysB and returns to service. The active unit remains in service.
Page 58: Routine Exercise Test
1-42 Maintenance overview Routine exercise test A REx test includes a series of tests performed on an XPM unit. The best test schedule is for the system scheduler or operating company personnel to initiate an XPM unit test each day. The REx test combines the diagnostic and operational routines available on XPMs.
Page 59 Maintenance overview 1-43 REx state machine actions Start Test the inactive unit SysB the inactive unit RTS the inactive unit (InSv tests only) (out-of-service tests only) Wait for superframe and data synchronization to occur Initiate a pre-SWACT audit (See note 1) to determine if you must request a SWACT (See note 2)
Page 60 1-44 Maintenance overview If a REx test fails, the system generates a PM600 log. The PM600 log initiates a major alarm for the XPM that failed the REx test. The major alarm appears at the MAP terminal under the PM banner at the top of the display.
Page 61 Maintenance overview 1-45 Diagnostic name and description (continued) Diagnostic name (mnemonic) Description of diagnostic PS SPCH P–side Speech Links SMSAB 6x81 A/B Bits SMS MSG SMS A/B DDL Msg SPCH DG Speech Path SYNC DG Sync Diag TONE DG Tone Diag TS DIAG Time Switch Diag UTRDIAG...
Page 62 1-46 Maintenance overview If a restart occurs during a REx, the system does not generate the PM600 log. The system does not generate the PM600 log because the restart deallocates the temporary data store that creates the PM600 log. A SWACT controller override is not available for a manual REX test. Refer to SWACT controller section in this document.
Page 63 Maintenance overview 1-47 Displays the failure reason for a SWACT denial or failure performed during a manual REx at the MAP terminal as REx failed. Use the command string TST REx QUERY for the posted XPM to obtain the reason for the failure. The system generates a PM600 log report that details the REx failure reason.
Page 64: Ani And Coin Functions
1-48 Maintenance overview You must enter data in table REXSCHED to establish the REx schedule for the SMS. The REx coordinator needs the information in this table to schedule the tests according to operating companies specifications. Enter data in table REXSCHED to disable the test . For more information on table REXSCHED, refer to the data design section of the Translations Guide.
Page 65 Maintenance overview 1-49 negative coin check The RCS transmits the following signals to the SMS in response to SMS signals: on-hook off-hook coin ground unequipped These signaling states are associated with specified A-bit and B-bit patterns. The Bell Communications Research document Digital Interface Between the SLC-96 Digital Loop Carrier System and a Local Digital Switch describes these patterns.
Page 66 1-50 Maintenance overview The subscriber can begin to dial. The subscriber must deposit the correct number of coins for a local call before dialing completes. If the subscriber does not deposit the correct amount a recording activates. The recording instructs the subscriber to start the call again and deposit the correct amount. The cycle of this announcement occurs two times.
Page 67 Maintenance overview 1-51 Local coin overtime At the end of the first time period for a call, an announcement instructs the subscriber deposit additional coins for the call to continue. A quarter is an example of a coin that you can deposit to continue a call. The SMS sends the RCS a positive coin check pattern to check if the quarter is present.
Page 68: P-Side Channel Management
1-52 Maintenance overview ANI and coin function limits The following limits apply to ANI and coin functions: Coin cards can be in the four slots on the right of an RCS shelf only. This coin card position applies if the shelf is part of a shelf group that operates in Mode II.
Page 69 Maintenance overview 1-53 When verification cannot proceed, operating company personnel receive one of the following responses: busy tone (60 ipm) indicates normal access is available. Operating company personnel cannot access the busy tone now for one of the following reasons. The busy tone has an activated custom calling feature or the busy tone connects to another operator.
Page 70 1-54 Maintenance overview Line conditions for operator verification (continued) Line condition Characteristics DMS response Busy line Line is traffic busy, voice Access connection is complete. and voice/data, simple Operating company personnel line can hear conversation, quiet line, reorder, busy tone, announcement, or other indications that the line is traffic busy.
Page 71 Maintenance overview 1-55 Line conditions for operator verification (continued) Line condition Characteristics DMS response Line goes off-hook during Normal access connection verification retained. Customer does not receive dial tone Attempt to activate System ignores transient state custom calling feature while line line verification occurs Line with cutoff on Line has the Operator can obtain a...
Page 72: Functional Description Of The Rcs
1-56 Maintenance overview Functional description of the RCS The remote concentrator SLC-96 (RCS) is a digital loop carrier that serves a maximum of 96 subscribers. The RCS connects to the DMS-100 through the SMS. Three to five DS-1 links connect the RCS to the SMS. Two to four of these links are active DS-1 links and one link is an optional DS-1 protection link.
Page 73: Derived Data Link
Maintenance overview 1-57 In Mode III, the RCS operates with one DS-1 link for each shelf group. The RCs uses a multiplexer to multiplex channels from the two shelves on a shelf group on one DS-1 link. Derived data link Messaging between the RCS and the SMS uses the derived data link (DDL).
Page 74: Functional Description Of The Ds-Link
1-58 Maintenance overview Functional description of the DS-link The DS-1 links connect the SMS to the RCS. The SMS provides a maximum of 20 DS-1 links to the SMS remotes. Each remote terminates from two to four primary DS-1 links from an SMS. The number of links depend on the mode of operation.
Page 75: Parity On The Xpm
Maintenance overview 1-59 The SMS P-side links carry messages that are important to the maintenance of subscriber service. A defective P-side link can damage subscriber service. In a P-side link, a channel must be available for a call attempt to be successful.
Page 76: Parity Faults
1-60 Maintenance overview The individual cards with memory (NT6X46, NT6X47, or NTMX77) have the parity hardware. A priority 6 interrupt to the local CPU reports parity faults. The level 6 interrupt autovector in an XPM is bound to an assembly interrupt handler.
Page 77: Exception Traceback Enhancements (Af5680)
Maintenance overview 1-61 Perform low-level categorization of the fault (hard/soft/intermittent) regardless of the interrupt source. Determine if the fault address is in code space or not in code space. Leave the fault indication in place if the fault is not corrected. Save the fault data according to where the interrupt originated.
Page 78 1-62 Maintenance overview System component interactions The system components interact with the XPM exception processing system to recover from error exceptions. The system components report and display information about error exceptions. The system components are listed below. PMDEBUG XPM maintenance If the system detects a fatal error, the system initiates local maintenance action to drop activity from an active unit only.
Page 79: Data Mismatch
Maintenance overview 1-63 An enhancement to exception recovery deals with the Direct Memory Access Memory Management Unit (MX77 DMA MMU). You must take special action when you attempt to recover from an MX77 DMA MMU error. In the past, when a DMA MMU error occurred, the exception processing system selected the interrupted task.
Page 80 1-64 Maintenance overview Each XPM unit has tables that contain information. The information is about nodes that each XPM unit connects to and terminals that each XPM unit uses. The two systems that determine unit table mismatches are as follows: Mate unit matching compares the inactive unit tables with the active unit.
Page 81 Maintenance overview 1-65 The system generates a minor alarm when at least one datafilled line on the remote terminal becomes unequipped. One of the following methods can clear the minor alarm: insert a line card remove the datafill in the computing module for the line card that is missing If a line card is inserted, the system will RTS the line within 20 seconds.
Page 82 1-66 Maintenance overview Dynamic data update A dynamic data update occurs on an continuous basis. Changed data in the active unit is updated in the inactive unit. Dynamic data updates include the following information: RCS status (in-service or busy) FSR codes subscriber states channel reassignment port statuses...
Page 83: Rcs Fault Conditions
Maintenance overview 1-67 Critical dynamic data allows the inactive unit to take over call processing from its mate. The inactive unit retains a majority of established calls. Enhanced Dynamic Data Sync (EDDS) Dynamic data describes the link and node states in the XPM needed to support call processing.
Page 84: Ds-1 Link Fault Conditions
1-68 Maintenance overview is entered. This text is datafilled in table RCSINV. The alarm text must be consistent with the problem the hard-wired alarm is configured. DS-1 link fault conditions The DS-1 links that connect the SMS-RCS subsystem can have several faults.
Page 85 Maintenance overview 1-69 reads the location again. If the area is defective after the second read, the audit tries to write a test pattern to the defective memory location. The CM acts on the XPM parity audit to correct the memory fault as efficiently as possible.
Page 86 1-70 Maintenance overview The audit discovers a mismatch in node status. A PM181 log with the following reason must occur and OM PM2ERR must increment by one. Node Status Mismatch Call processing connection audit The call processing connection audit maintains an order for the SMS and RCS timeswitch connection records.
Page 87: Pre-Swact And Post-Swact Audits
Maintenance overview 1-71 Pre-SWACT and post-SWACT audits The SWACT audits provide a mechanism in the XPM that increases SWACT reliability. The mechanism prevents a SWACT to a mate unit that cannot maintain activity. If a SWACT occurs and the newly active unit does not establish two-way communication with the CM, a SWACT back to the originally active unit is attempted.
Page 88 1-72 Maintenance overview Pre-gain audit The pre-gain audit monitors the XPM status data in the inactive unit. The pre-gain audit sends the XPM status data to the pre-drop audit in the active unit. The pre-drop audit uses the XPM status data to determine if the active unit must drop activity.
Page 89: Digital Phase Lock Loop (Dpll) Clock Failure
Maintenance overview 1-73 SWACT back is not needed or a SWACT back is complete, the XPM informs the CM. The inactive unit is busied and returned to service. Digital phase lock loop (DPLL) clock failure The enhanced field failure information feature allows the system to identify when a loss of synchronization causes a system busy.
Page 90 1-74 Maintenance overview Protection link configuration Network Protection link Unprotected RCS Protection switches are initiated: automatically by the RCS or SMS manually by operating company personnel who use the CARRIER level PROTSW command during execution of the FELP command The FELP command enables a continuous loopback on all 24 DS-1 channels of a specified link.
Page 91 Maintenance overview 1-75 Causes of automatic protection switching Either an SMS or an RCS can initiate a protection switch after a primary link failure is detected. The module that detects the failure initiates the protection switch. The SMS initiates a switch for the following faults: bipolar violations (BpV) exceeding the threshold datafilled in table CARRMTC loss of signal that lasts for a time greater than the threshold datafilled in...
Page 92 1-76 Maintenance overview that detects the fault does not have another fault on a link. The SMS and RCS are the ends that detect the fault. Three tables must be datafilled to support protection switching: table CARRMTC, table LTCPSINV and table RCSINV. How to datafill tables CARRMTC, LTCPSINV, and RCSINV is described in the Translations Guide.
Page 93 Maintenance overview 1-77 system busied and the protection link remains switched for that shelf. The primary link that serves the shelf that has faults is system busied. Calls cannot be processed for the shelf that has faults. Refer to scenario 10. Note: The switch to the shelf that has faults causes a fault to be detected on the protection link.
Page 94 1-78 Maintenance overview A protection switch does not occur. The C-link is system busied. The RCS detects a fault on the A-link. A protection switch does not occur. The A-link is system busied. Note: If the RCS is in Mode II or III, the RCS is system busied because all DS-1 links are out-of-service.
Page 95 Maintenance overview 1-79 Scenario 7 All DS-1 links, which includes the protection link, are in-service. Faults are not present on any link. The RCS detects a fault on the C-link. At the same time, the SMS detects a fault on the B-link. The B-shelf is protection switched.
Page 96 1-80 Maintenance overview Scenario 10 All DS-1 links, which includes the protection link, are in-service. Faults are not present on any link. The transmit receive unit card of the RCS C-shelf is removed. The SMS detects a fault (frame loss) on the C-link. Removal of the transmit receive unit card causes frame loss on the RCS transmit side of the DS-1 link.
Page 97 Maintenance overview 1-81 The A-link is system busied. The protection link is not switched. The SMS notes the protection link as having faults. The A-shelf transmit receive unit serves the A-link and protection link. The protection link is not switched to the A-shelf. Note: The SMS can switch the protection link to the A-shelf for a short time.
Page 98 1-82 Maintenance overview another fault on an INSV link, a protection switch occurs. Refer to scenarios 4 and 5. If the RCS detects a fault on a ManB link other than the A-link, a protection switch does not occur. The SMS can detect another fault on an INSV link other than the A-link.
Page 99 Maintenance overview 1-83 Scenario 3 The A-link is ManB. The protection link is INSV and available. A fault is not present on the A-link. A fault occurs on the A-link toward the SMS. The protection link is not switched. Note: The SMS does not scan for near-end faults on the A-link because the link is ManB.
Page 100: Subscriber Lines Automatic Maintenance
1-84 Maintenance overview Scenario 7 The C-link is ManB. The RCS detects a fault on the C-link. The A-, B- and D-links are INSV. The protection link is INSV and available. The SMS detects a fault on the B-link. The protection link is switched to the B-shelf. Scenario 8 The C-link is ManB.
Page 101: Escalation To Manual Maintenance
Maintenance overview 1-85 Escalation to manual maintenance The SMS detects a fault on a primary link. The SMS cannot switch a protection link into service. The maintenance personnel can manually protection switch the DS-1 link that has faults from the MAP terminal. Manual protection switching and the scenarios where manual protection switching takes place are discussed in “Manual protection switching”...
Page 102 1-86 Maintenance overview An automatic protection switch is requested for the A-shelf. The SMS is manually switched for another shelf. The protection link is dropped from the B-, C- or D-shelf and switched to the A-shelf. Automatic protection switching for the A-shelf overrides manual protection switching for the B-, C-, or D-shelves.
Page 103 Maintenance overview 1-87 Scenario 4 The C-shelf is manually protection switched. Faults are not present on any primary link. The protection link is INSV. A fault is detected on the B-link. The protection link remains switched to the C-shelf. The B-shelf is system busied.
Page 104 1-88 Maintenance overview Scenarios of manual protection link release Scenario 1 The C-shelf is protection switched because of a defective C-link. The protection link is INSV. You manually release the protection link. The protection link is immediately switched back to the C-shelf. Scenario 2 The C-shelf is manually protection switched.
Page 105 Maintenance overview 1-89 Note: To perform full disable protection switching, both the DMS switch and the RCS ends must be disabled for protection switching. Scenarios of enabling and disabling protection switching Scenario 1 All primary DS-1 links and the protection link are INSV. Faults are not present on any links.
Page 106 1-90 Maintenance overview The A-shelf is automatically or manually protection switched and the A-link is manually busied. When this condition occurs, the protection link remains switched to the A-shelf. Refer to scenario 3. Scenarios of manually busy, switched primary links Scenario 1: The C-shelf is protection switched because of a defective C-link.
Page 107 Maintenance overview 1-91 Call processing cannot proceed over a protection link if the protection link is switched for a manually busy primary link. The SMS detects a fault and a protection switch occurs. The CARRIER level of the MAP display indicates that the primary link is protection switched.
Page 109: Sms Hardware
SMS hardware This chapter describes the subscriber carrier system hardware components which give the subscribers the full resources of a digital switching system for call processing and maintenance. Hardware components The hardware components are discussed in subsequent sections of this chapter as follows: SMS module RCS module...
Page 110 2-2 SMS hardware SMS–RCS configuration Network DS30 links: 3–4 links will handle traffic for all SMS applications Subscriber module SLC-96 Central Digital cross-connect office Office repeater bay Main distribution frame DS-1 links: 2–4 per RCS plus an optional protection line; 2–20 per SMS Remote Remote...
Page 111: Sms Module
SMS hardware 2-3 SMS module The SMS module resides in a subscriber carrier equipment (SCE) frame or a cabinetized version of the frame and is comprised of two units. Unit 0 occupies the lower shelf; unit 1 occupies the upper shelf. The SCE frame and its cabinetized version can house up to two SMS modules each.
Page 112 2-4 SMS hardware SMS SCE frame Unit 1 SMS module 1 Unit 0 Unit 1 SMS module 0 Unit 0 Cooling Unit 297-8231-550 Standard 09.01 August 1998...
Page 113: The Rcs Module
SMS hardware 2-5 The RCS module The remote concentrator SLC-96 (RCS) module comprises up to four line shelves labeled A, B, C, and D. Shelves A and B form the upper shelf group, AB; shelves C and D form the lower shelf group, CD. Each shelf group operates independently in one of three modes.
Page 114 2-6 SMS hardware An RCS in Mode I has up to four primary DS-1 links to the SMS, plus an optional protection link. This configuration allows a maximum of four Mode I remotes, including protection links, to hang off the SMS. Note: If no protection links are configured, up to five RCS modules in Mode I may be configured.
Page 115: Additional Components
SMS hardware 2-7 Protection switches are initiated automatically by the RCS or SMS, manually by operating company personnel using the CARRIER level protection switch (PROTSW) command, or during execution of the far end loop test (FELP) command. The FELP command enables a continuous loop back on all 24 DS-1 channels of a specified link.
Page 117: Sms Signaling
SMS signaling Signaling for SMS This section describes the signaling protocols that the subscriber module SLC-96/remote concentrator SLC-96 (SMS-RCS) subsystem uses. The following sections discuss SMS-RCS signaling format, signaling protocols and the features the format and protocols support. SMS-RCS signaling links The SMS and the RCS exchange information over DS-1 lines that use an extended super frame format.
Page 118 3-2 SMS signaling Format of a DS-1 frame Framing bit Voice channel 1 Voice channel 2 Voice channel 24 S 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 185 186 187 188 189 190 191 192 Channel frame Channel frame Ft frame 1 Fs frame 2 Ft frame 3 Fs frame 4...
Page 119: Signaling Protocols
SMS signaling 3-3 Every fourth bit carries the cyclic redundancy check (CRC), which begins with the second bit. The system performs a block check field six times in an extended super frame. The CRC-6 check detects bits that emulate an FSP bit, and determines when an out-of-frame condition is present.
Page 120 3-4 SMS signaling These 12 bits transfer the signaling pattern from two superframes. The system takes the Fs bits from the next four superframes. This action occurs at the transmit receive unit card in the RCS or at the time switch card in the SMS.
Page 121 SMS signaling 3-5 Message time-out and message checksum or CRC calculation performs message error detection. In the event of protocol, checksum, or CRC failure on an outgoing message, the sending node retries the send sequence. On an incoming message failure, the sending node reroutes the message over an alternate control side (C-side) link.
Page 122: Sms-Rcs Signaling Functions
3-6 SMS signaling The DMS–X message header is the first six bytes as follows: The first byte is the start of message. The second byte is the destination task identification (ID) of the message. An outgoing message uses this ID to identify the process to receive the message.
Page 123 SMS signaling 3-7 The SMS sends the following signaling information to the RCS on a per-channel basis: start or stop ringing start or stop forward disconnect scan for on-hook and off-hook collect ANI/Coin information collect channel maintenance information The SMS collects return signaling information from the RCS that includes the following data: call origination call disconnect...
Page 124 3-8 SMS signaling With a UTR, the CC conveys the need for a receiver to the SMS. The SMS goes through the following steps: 1 Request a UTR channel. 2 Instruct the UTR to start monitoring tones. 3 When monitoring starts, the system informs the SMS of digits and normally performs some translations functions on the digits.
Page 125 SMS signaling 3-9 The following signals are transmitted from the SMS to the RCS: negative loop mode channel test positive loop mode ground start –R ringing positive coin check positive coin control negative coin control negative coin check The following signals are transmitted from the RCS to the SMS in response to SMS signals: on-hook off-hook...
Page 126 3-10 SMS signaling Custom local area signaling services (CLASS) features The following CLASS features are supported: calling number delivery (CND) automatic call back (ACB) automatic recall (AR) customer originated trace (COT) calling number delivery blocking (CNDB) Ringing The following ringing types are supported: bridged ringing —...
Page 127: Universal Tone Receiver (Utr) Features
SMS signaling 3-11 Ω SCD252 for 1500- loops A specified RCS supports one type of ringing. For example, an RCS supports FSR but not coded, or coded but not FSR. A field in table RCSINV indicates the type of ringing an RCS uses. Refer to the data schema section of the Translations Guide for more information on Table RCSINV datafill.
Page 128 3-12 SMS signaling With a UTR, the SMS goes through the following steps: 1 Request a UTR channel. 2 Instruct the UTR to start monitoring tones. 3 When monitoring starts, the system informs the SMS of collected digits. The SMS normally performs some translations functions on the digits. 4 When the receiver is no longer required, the SMS frees the allocated UTR channel.
Page 129 SMS signaling 3-13 Any subsequent DSCWID options on a SCWID or 2500 use a new timer (T-flash). The system uses T-flash after the subscriber answers a call with SCWID and 2500 sets. This action provides the customer with enough time to select an option after a flash.
Page 130 3-14 SMS signaling DDL message bits and field names DDL bits Field name Explanation Bits 1 –11 Concentrator field (C-field) To operate in Mode II, shelf groups AB and CD use the C-field. This field carries information for shelves A, B, C and D. The information includes control of subscriber assignment and deassignment to DS-1 channels, hook transitions and activation of the PCM looping...
Page 131 SMS signaling 3-15 Nailed-up cross-connections Nailed-up connections support the following special services features: maintenance and table control for nailed-up specials on SMS SMS special services digital dataphone service (DDS) hairpin direct inward dial (DID) PBX by hairpin integrated local specials One endpoint of the nailed-up connection must terminate on a switch that supports these special services.
Page 132 RCS and SMS into a channel bank or some other digital facility. In this event, the digital facility is a Nortel (Northern Telecom) channel bank. From the channel bank, data flows to the DMS-100 and switches to the terminating party.
Page 133 SMS signaling 3-17 Direct inward dial (DID) PBX by hairpin This feature uses the following items: special-services channel units in an RCS a hairpin connection a DS-1 link from an SMS to a DTC other piece of telephone equipment The following DID PBX configuration figure illustrates this feature. DID PBX configuration example DMS-100 PX digital trunks...
Page 134 3-18 SMS signaling Integrated local specials The special plain ordinary telephone service (SPOTS) channel unit (S9CD271A) supports POTS and special services like the following: INWATS OUTWATS The SPOTS channel unit is configured in loop or ground start mode. When SPOTS channel units are configured in loop start, the units do not support PBX.
Page 135 SMS signaling 3-19 Note: The S9CD271A SPOTS channel unit, which is not recommended for use in a Mode III RCS, can be used for this purpose. Even-numbered circuits can be assigned in Mode III. The SPOTS channel unit does not provide for tip-ring reversal. Tip-ring reversal is a signal for many switches to indicate a toll call to the originating party.
Page 137: Converting From Mode I To Mode Ii
Converting from Mode I to Mode II Mode I to Mode II conversion Two procedures follow for conversion from Mode I to Mode II operation. This conversion can be required to free up DS-1 links to the remote site for additional SLC-96 systems.
Page 138: Two Available Links
4-2 Converting from Mode I to Mode II Example configuration for procedure Mode I to Mode II conversion (no available links) REM1 00 2 REM1 00 0 SMS 0 Protection link Protection link DS-1 port (link) designations REM1 00 1 REM1 00 3 Protection link Protection link...
Page 139 Converting from Mode I to Mode II 4-3 Mode I to Mode II conversion (two available links) At the maintenance and administration position (MAP) terminal 1 In Mode II operation, you cannot enter special-service or coin cards in the first eight slots of each shelf in the remote. To verify this statement, obtain a hardcopy of table LNINV.
Page 140 4-4 Converting from Mode I to Mode II >POS SMS 0 SMS 0 (0 DS1 DEFAULT N) (1 DS1 DEFAULT N) (2 DS1 DEFAULT N) (3 DS1 DEFAULT N) (4 DS1 DEFAULT N) (5 DS1 DEFAULT N) (6 DS1 DEFAULT N) (7 DS1 DEFAULT N) (8 DS1 DEFAULT N) (9 DS1 DEFAULT N) (10 NILTYPE) (11 NILTYPE) (12 NILTYPE) (13 NILTYPE) (14 NILTYPE) (15 NILTYPE) (16 NILTYPE) (17 NILTYPE) (18 NILTYPE) (19 NILTYPE) $...
Page 141 Converting from Mode I to Mode II 4-5 4 To post and busy the remote from the PM MAP level, type >MAPCI;MTC;PM >POST RCS site rcs_no unit_no >BSY Example: >MAPCI;MTC;PM >POST RSC KRCS 00 0 >BSY “CALLS WILL BE AFFECTED. PLEASE CONFIRM (YES OR NO)”...
Page 142 4-6 Converting from Mode I to Mode II >$ LOOPTEST: >N SHLFGRPMODE: MODE1 >MODE2 PORT: > 12 PORT: >$ LOOPTEST: >N Step through the fields that remain until the tuple to change appears. Press the Enter key to step through the fields that remain. KRCS 00 0 MIS 1 NOLOAD...
Page 143 Converting from Mode I to Mode II 4-7 >CHA MACHINES NOT IN SYNC – DMOS NOT ALLOWED JOURNAL FILE UNAVAILABLE – DMOS NOT ALLOWED ENTER Y TO CONTINUE PROCESSING OR N TO QUIT >Y Step through the fields until the PORT field appears. Press the Enter key to step through the fields.
Page 144 4-8 Converting from Mode I to Mode II >POS SMS 0 >CHA MACHINES NOT IN SYNC – DMOS NOT ALLOWED JOURNAL FILE UNAVAILABLE – DMOS NOT ALLOWED ENTER Y TO CONTINUE PROCESSING OR N TO QUIT >Y Step through the fields until the port to change appears. Press the Enter key to step through the fields.
Page 145 Converting from Mode I to Mode II 4-9 >POST SMS 0 >BSY UNIT 0 >RTS UNIT 0 >SWACT A warm SwAct will be performed This action will take this PM and all of Its Subtending Nodes temporarily out of service and <#>...
Page 146: No Available Links
4-10 Converting from Mode I to Mode II >RTS No available links Use the following procedure if links are not available (that is, NILTYPE ports are not present in table LTCPSINV). The ports the protection links from two other remotes use, are borrowed to make the conversion to Mode II.
Page 147 Converting from Mode I to Mode II 4-11 2 To change the entry in table RCSINV from Mode I to Mode II, you must change the SMS ports. If NILTYPE ports are not available in table LTCPSINV, borrow the ports the protection links from two other remotes use.
Page 148 4-12 Converting from Mode I to Mode II >POS REM1 00 2 REM1 00 2 MIS 1 NOLOAD SMS 0 MODE1 (0) (2)$ MODE1 (4) (6)$ WP1B MISC_ALARM MAJOR 35 DAVIS DRIVE RTP The remote to convert in this example uses SMS port 8 for the protection link of the remote.
Page 149 Converting from Mode I to Mode II 4-13 Repeat this procedure for the other link. 5 To post and offline the remote to change to Mode II, type >MAPCI;MTC;PM >POST RCS rcs no >BSY >OFFL Example: >MAPCI;MTC;PM >POST REM1 00 2 >BSY “CALLS WILL BE AFFECTED.
Page 150 4-14 Converting from Mode I to Mode II Step through the fields that remain until the tuple to change appears. ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT. >Y TUPLE CHANGED JOURNAL FILE INACTIVE Repeat this procedure for REM1 00 3. 7 In table RCSINV, change the remote to convert from Mode I to Mode II.
Page 151 Converting from Mode I to Mode II 4-15 >N REM1 00 2 MIS 0 NOLOAD SMS 0 MODE2 (9)$ N MODE2 (19)$ N WP1B MISC_ALARM MAJOR 35 DAVIS DRIVE RTP ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT. >Y WARNING: Static data not updated for SMS 0...
Page 152 4-16 Converting from Mode I to Mode II ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT. >Y WARNING: Static data not updated for SMS 0 You must BSY and RTS the SMS TUPLE CHANGED JOURNAL FILE INACTIVE 9 Two protection links were deleted when the remote converted to Mode II back to table RCSINV.
Page 153 Converting from Mode I to Mode II 4-17 10 To change the two links freed in step 7 that remain to NILTYPE in table LTCPSINV type, >TABLE LTCPSINV >POS sms no >CHA >QUIT Example: >TABLE LTCPSINV >POS SMS 0 >CHA MACHINES NOT IN SYNC –...
Page 154 4-18 Converting from Mode I to Mode II Example: >MAPCI;MTC;TRKS;CARRIER >POST SMS 0 The maximum size of the posted set is five. You can enter the NEXT command until the protection lines appear in the posted set. CLASS SITE SMS D ALRM SLIP FRME BER ES SES STATE...
Page 155 Converting from Mode I to Mode II 4-19 >SWACT A warm SwAct will be performed This action will take this PM and all of its subtending nodes temporarily out of service and <#> active terminals may be affected. Please confirm (“YES” or “NO”): >Y SMS 0 SwAct Passed 13 To translate the P-side links and return to service any P-side links that...
Page 156 4-20 Converting from Mode I to Mode II Example: >POST RCS REM1 00 2 >BSY >RTS 297-8231-550 Standard 09.01 August 1998...
Page 157: Sms Recovery Procedures
SMS recovery procedures This section contains a recovery procedure that restores a Subscriber Carrier Module-100S (SMS) host computer to service. Maintenance personnel use this procedure in a DMS-100/200 office. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 158 Recovery procedures Recovering an SMS Application Use this procedure to return an SMS to service (RTS). Action This procedure contains a summary flowchart and a list of steps. Use the flowchart that follows provides an overview of the procedure. 297-8231-550 Standard 09.01 August 1998...
Page 159 Recovery procedures 5-3 Recovering an SMS (continued) Summary of Recovering an SMS ManB the SMS This flowchart summarizes the procedure. Use the instructions that follow this flowchart to perform the procedure. Does SMS LOADPM with have NT7X05 LOCAL IMAGE card? LOADPM LOCAL IMAGE pass?
Page 160: Recovering An Sms
5-4 Recovery procedures Recovering an SMS (continued) Recovering an SMS At the MAP terminal Enter this recovery procedure when the MAP display indicates the following: both units of a posted SMS are out-of-service (OOS) a critical alarm occurs To manbusy (ManB) the SMS, type >BSY PM and press the Enter key.
Page 161 Recovery procedures 5-5 Recovering an SMS (continued) The peripheral loader card (NT7X05) allows local loading of the SMS data. Local data loading reduces recovery time. To determine if the NT7X05 card is provisioned, type: >QUERYPM FILES and press the Enter key. Example of a MAP display: Trks APPL...
Page 162 5-6 Recovery procedures Recovering an SMS (continued) CAUTION LOCAL IMAGE cannot load ISDN units Do not LOADPM from the LOCAL IMAGE on units with ISDN capability. The NT7X05 card does not support ISDN. Use LOCAL LOADFILE or load from the central control (CC) on units with ISDN. To load the SMS from the local image, type >LOADPM PM LOCAL IMAGE and press the Enter key.
Page 163 Recovery procedures 5-7 Recovering an SMS (continued) To load the SMS from the CC, type >LOADPM PM and press the Enter key. If the load passes step 7 fails step 12 To return the peripheral module (PM) to service, type >RTS PM and press the Enter key.
Page 164 5-8 Recovery procedures Recovering Recovering an SMS an SMS (continued) (end) unit_no is the number of the SMS unit (0 or 1) to test CAUTION Data match in progress An ISTb alarm appears after an RTS passes on both units. Wait 3-5 min for the system to clear this alarm. This process allows a dynamic data match between active and inactive units.
Page 165: Sms Alarm Clearing Procedures
SMS alarm clearing procedures This section contains card replacement procedures for the Subscriber Carrier Module-100S (SMS) Remote within DMS-100/200 offices. The alarm indicates the procedure that maintenance personnel must use to clear the trouble. Maintenance personnel use the procedures to clear alarms as the alarms appear at the MAP terminal display.
Page 166: Pm Sms Critical
Alarm clearing procedures PM SMS critical Alarm display Trks nSMS Indication An SMS under the PM subsystem header at the MTC level of the MAP display indicates a PM critical alarm. Meaning The indicated number (n) of SMSs are in the critical state. Result Call processing ceases.
Page 167 Alarm clearing procedures 6-3 PM SMS critical (continued) Summary of clearing a PM SMS critical alarm This flowchart summarizes the procedure. Use the instructions that follow this flowchart to perform the procedure. Access SMS at PM level of MAP display Silence Silence the alarm alarm...
Page 168 6-4 Alarm clearing procedures PM SMS PM SMS critical critical (continued) (end) Clearing a PM SMS critical alarm At the MAP terminal To access the MTC level and silence the alarm, type >MAPCI;MTC;SIL and press the Enter key. To access the PM level and identify the SMS module that is in a critical state, type >PM;DISP STATE SYSB SMS and press the Enter key.
Page 169: Pm Sms Major
Alarm clearing procedures PM SMS major Alarm display Trks nSMS Indication The alarm code SMS under the PM subsystem header indicates a PM alarm. The header appears at the MTC level of the MAP display. The letter M under the alarm code indicates the alarm class is major. Meaning The indicated number (n) of SMSs are in an in-service trouble state.
Page 170 6-6 Alarm clearing procedures PM SMS major (continued) Summary of clearing a PM SMS major alarm This flowchart summarizes the procedure. Access MTC MAP level and Use the instructions that follow silence alarm this flowchart to perform the procedure. Post ISTb SMS Query for faults Card list Replace...
Page 171 Alarm clearing procedures 6-7 PM SMS major (continued) Summary of clearing a PM SMS major alarm (continued) Busy, load, and Data out of Passes? return inactive date? unit to service Contact next level of maintenance End of Is active unit procedure InSv? SWACT to...
Page 172 6-8 Alarm clearing procedures PM SMS major (continued) Clearing a PM SMS major alarm At the MAP display When the system detects a fault, the system can trigger an audible alarm. To access the MTC level of the MAP display and silence the alarm, type >MAPCI;MTC;SIL and press the Enter key.
Page 173 Alarm clearing procedures 6-9 PM SMS major (continued) To return the inactive unit to service, type >RTS UNIT unit_no and press the Enter key. where unit_no is the number of the inactive unit If the message passes step 38 fails step 37 CAUTION Service disruption.
Page 174 6-10 Alarm clearing procedures PM SMS major (continued) To switch the activity of the unit, type >YES and press the Enter key. The system runs a pre SWACT audit to determine the ability of the inactive unit to accept activity. Note: A maintenance flag appears when maintenance tasks are in progress.
Page 175 Alarm clearing procedures 6-11 PM SMS major (continued) Example of a MAP response: Node is ISTb One or both units inservice trouble Unit 0 The following inservice troubles exist: Static data mismatch with CC Unit 1 The following inservice troubles exist: Static data mismatch with CC card list appears at the MAP step 28...
Page 176 6-12 Alarm clearing procedures PM SMS major (continued) To return the inactive unit to service, type >RTS UNIT unit_no and press the Enter key. where unit_no is the number of the inactive unit If RTS passes step 38 fails step 37 Perform the procedure “Updating static data.”...
Page 177 Alarm clearing procedures 6-13 PM SMS major (continued) To access table LTCINV, type >TABLE LTCINV and press the Enter key. To position on the tuple for the SMS that has defects, type >POS SMS sms_no and press the Enter key. where sms_no is the number of the SMS that has defects...
Page 178 6-14 Alarm clearing procedures PM SMS major (continued) To eave table LTCINV, type >QUIT and press the Enter key. Perform the procedure Updating static data from Alarm Clearing Procedures . When you complete this procedure, go to step 23. To check for fault indicators, type >QUERYPM FLT and press the Enter key.
Page 179 Alarm clearing procedures 6-15 PM SMS major (continued) unit_no is the number of the inactive unit If test passes step 30 fails, and the system produces a step 28 card list fails, and the system does not step 37 produce a card list Check the card list that appears at the MAP terminal.
Page 180 6-16 Alarm clearing procedures PM SMS major (continued) To display information about the P-side links, type >TRNSL P and press the Enter key. Example of a MAP response: LINK 1 xxx xxx0 01 0 1;CAP S;STATUS: SysB LINK 2 xxx xxx0 01 0 2;CAP S;STATUS: OK LINK 3 xxx xxx0 01 0 3;CAP MS;STATUS: OK MSGCOND: OPN LINK 4 xxx xxx0 01 0 4;CAP MS;STATUS: OK MSGCOND: OPN LINK 5 xxx xxx0 01 0 5;CAP S;STATUS: OK...
Page 181 Alarm clearing procedures 6-17 PM SMS major (continued) Check the card list that appear at the MAP terminal. Example of a MAP display: Site Flr RPos Bay_id Shf Description Slot EqPEC HOST SME 00 SMS : 000 6X85 HOST SME 00 SMS : 000 6X85 If you...
Page 182 6-18 Alarm clearing procedures PM SMS major (continued) CAUTION Service disruption. The PM can drop calls. If the system prompts you to confirm a cold SWACT, perform this activity in a period of low traffic. The PM will end all calls, including data calls. To switch the activity of the units, type >SWACT and press the Enter key.
Page 183 Alarm clearing procedures 6-19 PM SMS PM SMS major major (continued) (end) To switch the activity of the unit, type >YES and press the Enter key. The system runs a pre-SWACT audit to determine the ability of the inactive unit to accept activity.
Page 184: Pm Sms Minor
6-20 6-20 Alarm clearing procedures 6-20 PM SMS minor Alarm display Trks nSMS Indication The software management system (SMS) under the peripheral module (PM) subsystem header at the maintenance (MTC) level of the MAP display indicates a PM minor alarm. Meaning The value n indicates the number of SMS units in the in-service trouble (ISTb) state.
Page 185 Alarm clearing procedures 6-21 PM SMS minor (continued) Summary of clearing a PM SMS minor alarm This flowchart summarizes the From the MAP procedure. display access MTC level and Use the instructions that follow silence alarm this flowchart to perform the procedure.
Page 186 6-22 Alarm clearing procedures PM SMS minor (continued) Summary of clearing a PM SMS minor alarm (continued) This flowchart summarizes the procedure. Use the instructions that follow this flowchart to perform the procedure. End of Busy, load, and Data out of Passes? procedure RTS unit...
Page 187 Alarm clearing procedures 6-23 PM SMS minor (continued) Clearing a PM SMS minor alarm At the MAP terminal When the system detects a fault, the system can trigger an audible alarm. To access the MTC level of the MAP display and silence the alarm, type >MAPCI;MTC;SIL and press the Enter key.
Page 188 6-24 Alarm clearing procedures PM SMS minor (continued) To determine the SMS that is ISTb, type >DISP STATE ISTB SMS and press the Enter key. Example of a MAP response: ISTb SMS: To access the ISTb SMS, type >POST SMS sms_no and press the Enter key.
Page 189 Alarm clearing procedures 6-25 PM SMS minor (continued) unit_no is the number of the inactive unit If RTS passes step 46 fails step 45 CAUTION Service disruption. Calls can drop! If the system prompts you to confirm a cold SWACT, perform this activity only during a period of low traffic.
Page 190 6-26 Alarm clearing procedures PM SMS minor (continued) Note: A maintenance flag (Mtce in the following example) appears when maintenance tasks are in progress. Wait until the flag disappears before you proceed with the next maintenance action. Example of a MAP response: SMS 0 ISTb Links_OOS: CSide 0, PSide 0...
Page 191 Alarm clearing procedures 6-27 PM SMS minor (continued) Example of a MAP response: Node is ISTb One or both units inservice trouble Unit 0 The following inservice troubles exist: Static data mismatch with CC Unit 1 The following inservice troubles exist: Static data mismatch with CC the system displays a card list step 34...
Page 192 6-28 Alarm clearing procedures PM SMS minor (continued) To return the inactive unit to service, type >RTS UNIT unit_no and press the Enter key. where unit_no is the number of the inactive unit If RTS passes step 46 fails step 45 Perform the procedure, “Updating static data”.
Page 193 Alarm clearing procedures 6-29 PM SMS minor (continued) To position on the tuple for the SMS that has faults, type >POS SMS sms_no and press the Enter key. where sms_no is the number of the SMS that has faults To change the load name, type >CHA LOAD and press the Enter key.
Page 194 6-30 Alarm clearing procedures PM SMS minor (continued) To check for fault indicators, type >QUERYPM FLT and press the Enter key. If PM load mismatch with CC continues to appear step 45 does not appear step 46 Determine if the card replaced is the NT6X78. If card replaced is NT6X78 step 29...
Page 195 Alarm clearing procedures 6-31 PM SMS minor (continued) NT2X70 NT7X05 If inactive unit requires reloading step 31 does not require reloading step 32 To reload the inactive unit, type >LOADPM UNIT unit_no CC DATA and press the Enter key. where unit_no is the number of the inactive unit If LOADPM...
Page 196 6-32 Alarm clearing procedures PM SMS minor (continued) To test the CMR card, type >TST UNIT unit_no CMR and press the Enter key. where unit_no is the number of the unit that contains the CMR card that has defects If test passes step 37 fails, and card list appears...
Page 197 Alarm clearing procedures 6-33 PM SMS minor (continued) unit_no is the number of the inactive unit If RTS passes step 46 fails step 45 To return the CMR card to service, type >RTS UNIT unit_no CMR and press the Enter key. where unit_no is the number of the unit containing the CMR card that has defects...
Page 198 6-34 Alarm clearing procedures PM SMS minor (continued) To test the link busy in step 39, type >TST LINK link_no and press the Enter key. where link_no is the number of the link busy in step 39 If test passes step 43 fails, and the system generates a step 41...
Page 199 Alarm clearing procedures 6-35 PM SMS minor (continued) where link_no is the number of the link tested in step 33. If RTS passes step 44 fails step 45 Determine if additional SysB links are present. If additional SysB links are present step 39 are not present step 46...
Page 200 6-36 Alarm clearing procedures PM SMS minor (continued) The system determines the type of SWACT (warm or cold) the system can perform. The system displays a confirmation prompt for the selected SWACT. If SWACT cannot continue at this time step 48 can continue at this time step 49 Do not switch activity of the units.
Page 201 Alarm clearing procedures 6-37 PM SMS PM SMS minor minor (continued) (end) Go to step 13 to clear the alarm condition on the newly inactive unit. The procedure is complete. If other alarms display, refer to the correct how to clear an alarm procedures for the indicated alarms.
Page 202 6-38 6-38 Alarm clearing common procedures 6-38 Updating static data Application Use this procedure to update static data in the XPM. Action This procedure contains a summary flowchart and a list of steps. Use the flowchart to review the procedure. Follow the steps to perform the procedure.
Page 203: Updating Static Data Xpm
Alarm clearing common procedures 6-39 Updating static data (continued) Summary of updating static data in an XPM This flowchart summarizes the procedure. Use the instructions that follow Busy the this flowchart to perform the inactive unit procedure. RTS with NODATASYNC option Switch unit End of...
Page 204 6-40 Alarm clearing common procedures Updating static data (continued) Updating static data in an XPM At the MAP terminal: Proceed only if a step in a maintenance procedure directed you to this procedure. Independent use of this procedure can cause equipment damage or loss of service.
Page 205 Alarm clearing common procedures 6-41 Updating static data Updating static data (continued) (end) To perform a SwAct, type >SWACT UNIT unit_no and press the Enter key. MAP prompt: A Cold SwAct will be performed This action will take this PM and all of Its Subtending Nodes temporarily out of service and <n>...
Page 207: Sms Card Replacement Procedures
SMS card replacement procedures This section contains card replacement procedures for the Subscriber Carrier Module-100S Remote within DMS-100/200 offices. These detailed procedures can be used by maintenance personnel to remove and replace a circuit pack. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 208: Nt2X70 Sms
Card replacement procedures NT2X70 Application Use this procedure to replace an NT2X70 card in an SMS. Suffixes Name NT2X70 Power convertor (5V/12V) Common procedures None Action The following flowchart is only a summary of this procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 209 Card replacement procedures 7-3 NT2X70 (continued) Summary of card replacement procedure for an NT2X70 card in an SMS This flowchart summarizes the procedure. Use the instructions in the Locate procedure that follows this faulty flowchart to perform the card procedure. ManBusy inactive inactive...
Page 210 7-4 Card replacement procedures NT2X70 (continued) Replacing an NT2X70 card in an SMS At the frame Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 211 Card replacement procedures 7-5 NT2X70 (continued) The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time step 23 Switch the activity of the unit by typing >YES and pressing the Enter key.
Page 212 7-6 Card replacement procedures NT2X70 (continued) At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS. This protects the equipment against damage caused by static electricity.
Page 213 Card replacement procedures 7-7 NT2X70 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced. This will move the card 1/2 inch from the shelf backplane. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 214 7-8 Card replacement procedures NT2X70 (continued) Holding the card by the face plate, slide the card along the guides until the card is free from the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 215 Card replacement procedures 7-9 NT2X70 (continued) With the locking levers on the replacement card in the open position, place the back edge of the card into the upper and lower guides of the desired slot position on the shelf. Gently slide the card into the shelf. Seat and lock the card.
Page 216 7-10 Card replacement procedures NT2X70 (continued) Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf. Simultaneously rotate the top latch downward and the bottom latch upward. The card will lock into position when the lock-latches are flush with the faceplate of the card.
Page 217 Card replacement procedures 7-11 NT2X70 (continued) Set the POWER switch to the ON position. If FSP is equipped with fuses step 16 circuit breakers step 17 Press and hold the RESET button for 1 second. Both the converter FAIL LED and FRAME FAIL lamp on the frame supervisory panel (FSP) will be ON.
Page 218 7-12 Card replacement procedures NT2X70 (continued) Test the inactive unit by typing >TST UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit If TST passed step 21 failed step 25 Return the inactive SMS unit to service by typing >RTS UNIT unit_no and pressing the Enter key.
Page 219 Card replacement procedures 7-13 NT2X70 NT2X70 (continued) (end) Obtain further assistance in replacing this card by contacting the personnel responsible for higher level of support. You have successfully completed this procedure. Return to the maintenance procedure that directed you to this card replacement procedure and continue as directed.
Page 220: Nt6X40 In A Sms
7-14 7-14 Card replacement procedures 7-14 NT6X40 in a SMS Application Use this procedure to replace the following cards in a Subcriber Carrier Module (SMS) as identified in the following table. ATTENTION Replacement restrictions apply to certain versions of the NT6X40 card.
Page 221 Card replacement procedures 7-15 NT6X40 in a SMS (continued) Common procedures The following common procedures are referenced: Manually busying SMS C-side links Removing and replacing a card Returning a card for repair or replacement Do not go to a common procedure unless directed to do so in the step-action procedure.
Page 222 7-16 Card replacement procedures NT6X40 in a SMS (continued) Summary of Replacing NT6X40 in a SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this flowchart to perform the procedure. Post SMS and make unit inactive Manually busy network links...
Page 223 Card replacement procedures 7-17 NT6X40 in a SMS (continued) Replacing an NT6X40 in a SMS At your current location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 224 7-18 Card replacement procedures NT6X40 in a SMS (continued) Determine the location of the SMS containing the NT6X40 circuit card you are replacing by typing >QUERYPM and pressing the Enter key. Example of a MAP response: QueryPM PM Type: SMS PM No.: 0 PM Int.
Page 225 Card replacement procedures 7-19 NT6X40 in a SMS (continued) Switch activity by typing >SWACT and pressing the Enter key. Example of a MAP response: SMS 0 A Warm SwAct will be performed after data sync of active terminals. Please confirm (”YES”, ”Y”, ”NO”, or ”N”): you are prompted to confirm a step 8 warm SWACT...
Page 226 7-20 Card replacement procedures NT6X40 in a SMS (continued) Manually busy all C-side links associated with the inactive PM unit you are working on using the procedure Manually busying Series II PM and CPM C-side links in this document. When you have completed the procedure, return to this point.
Page 227 Card replacement procedures 7-21 NT6X40 in a SMS (continued) WARNING Avoid contaminating the fiber tip surface Do not touch the tip of the fiber. Dirt or oil from the skin transferred to the fiber tip surface degrades fiber performance. WARNING Fiber cable may become damaged Take care when handling fiber cables.
Page 228 7-22 Card replacement procedures NT6X40 in a SMS (continued) WARNING Protect back plane pins Do not allow screws to drop onto or touch the back plane pins. When removing and replacing the screws for the card, the back plane pins above and below must be protected to prevent shorting out.
Page 229 Card replacement procedures 7-23 NT6X40 in a SMS (continued) Remove the screw that holds the circuit card to the support assembly. Locate the screw which is positioned half-way down the outer edge of the circuit card. Remove the washer holding the screw in place. Remove the screw and the spacer located between the circuit card and the support assembly.
Page 230 7-24 Card replacement procedures NT6X40 in a SMS (continued) Place the circuit card just removed in an electrostatic discharge protective container. Note: If the circuit card you are replacing has switches, ensure the switches on the replacement circuit card have the same settings. Using the levers located at the top and bottom of the 6X40 circuit card firmly press the connector pin socket on the card onto the connector pins on the backplane.
Page 231 Card replacement procedures 7-25 NT6X40 in a SMS (continued) At the front of the shelf Reseat the NT6X40 card unseated in step 12. Go to step 25. Replace the card using the procedure “ Removng and replacing a card ” in this section.
Page 232 7-26 Card replacement procedures NT6X40 in a SMS (continued) Return the network link to service by typing >RTS plane_no LINK link_no and pressing the Enter key. where plane_no is the number of the plane (0 or 1) for the link link_no is the link number (0 to 3) Example of a MAP response:...
Page 233 Card replacement procedures 7-27 NT6X40 in a SMS (continued) Determine the status of the XPM unit containing the NT6X40 circuit card you replaced by typing >QUERYPM and pressing the Enter key. SysB ManB OffL CBsy ISTb InSv 0 Quit 2 Post_ 3 ListSet 0 InSv Links_OOS: CSide...
Page 234 7-28 Card replacement procedures NT6X40 NT6X40 in a SMS in a SMS (continued) (end) Return to the maintenance procedure that sent you to this procedure and continue as directed. Consult office personnel to determine why the component is offline. Continue as directed by office personnel.
Page 235: Nt6X41 Sms
7-29 Card replacement procedures 7-29 7-29 NT6X41 Application Use this procedure to replace an NT6X41 card in an SMS. Suffixes Name NT6X41 AA, AB Speech bus formatter Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 236 7-30 Card replacement procedures NT6X41 (continued) Summary of card replacement procedure for an NT6X41 card in an SMS This flowchart summarizes the procedure. Use the instructions in the Locate procedure that follows this faulty INACTIVE flowchart to perform the card unit procedure.
Page 237 Card replacement procedures 7-31 NT6X41 (continued) Replacing an NT6X41 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 238 7-32 Card replacement procedures NT6X41 (continued) The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time step 23 Switch the activity of the unit by typing >YES and pressing the Enter key.
Page 239 Card replacement procedures 7-33 NT6X41 (continued) Set the PM to the ROM level by typing >PMRESET UNIT unit_no NORUN and pressing the Enter key. where unit_no is the number of the faulty SMS unit At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS.
Page 240 7-34 Card replacement procedures NT6X41 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 241 Card replacement procedures 7-35 NT6X41 (continued) Open the locking levers on the replacement card. Align the card with the slots in the shelf and gently slide the card into the shelf. Seat and lock the card. Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf.
Page 242 7-36 Card replacement procedures NT6X41 (continued) Use the following information to determine where to go next in this procedure. If you entered this procedure from alarm clearing procedures step 18 other step 16 Test the inactive unit by typing >TST UNIT unit_no and pressing the Enter key.
Page 243 Card replacement procedures 7-37 NT6X41 NT6X41 (continued) (end) At the frame Remove the sign from the active SMS unit. Send any faulty cards for repair using local procedure. Record the following items in office records according to local policy: date the card was replaced serial number of the card symptoms that prompted replacement of the card You have successfully completed this procedure.
Page 244: Nt6X42 Sms
7-38 7-38 Card replacement procedures 7-38 NT6X42 Application Use this procedure to replace an NT6X42 card in an SMS. Suffixes Name NT6X42 Channel supervision message Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 245 Card replacement procedures 7-39 NT6X42 (continued) Summary of card replacement procedure for an NT6X42 card in an SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this Locate flowchart to perform the RTS inactive faulty procedure.
Page 246 7-40 Card replacement procedures NT6X42 (continued) Replacing an NT6X42 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 247 Card replacement procedures 7-41 NT6X42 (continued) Switch the activity of the units by typing >SWACT and pressing the Enter key. The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time...
Page 248 7-42 Card replacement procedures NT6X42 (continued) At the MAP terminal Busy the inactive PM unit by typing >BSY UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS.
Page 249 Card replacement procedures 7-43 NT6X42 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 250 7-44 Card replacement procedures NT6X42 (continued) Align the card with the slots in the shelf and gently slide the card into the shelf. Seat and lock the card. Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf.
Page 251 Card replacement procedures 7-45 NT6X42 (continued) Use the following information to determine what step to go to next in this procedure. If you entered this procedure from alarm clearing procedures step 17 other step 15 Test the inactive unit by typing >TST UNIT unit_no and pressing the Enter key.
Page 252 7-46 Card replacement procedures NT6X42 NT6X42 (continued) (end) Obtain further assistance in replacing this card by contacting the personnel responsible for a higher level of support. At the frame Remove the sign from the active SMS unit. Send any faulty cards for repair according to local procedure. Note in office records according to local policy: date the card was replaced serial number of the card...
Page 253: Nt6X44 Sms
7-47 Card replacement procedures 7-47 7-47 NT6X44 Application Use this procedure to replace an NT6X44 card in an SMS. Suffixes Name NT6X44 AB, CA Time switch Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 254 7-48 Card replacement procedures NT6X44 (continued) Summary of card replacement procedure for an NT6X44 card in an SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this flowchart to perform the Locate procedure. inactive faulty card unit ManBusy End of...
Page 255 Card replacement procedures 7-49 NT6X44 (continued) Replacing an NT6X44 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 256 7-50 Card replacement procedures NT6X44 (continued) The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT cannot continue at this time step 23 can continue at this time step 6 Switch the activity of the unit by typing >YES and pressing the Enter key.
Page 257 Card replacement procedures 7-51 NT6X44 (continued) At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS. This protects the equipment against damage caused by static electricity.
Page 258 7-52 Card replacement procedures NT6X44 (continued) Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 259 Card replacement procedures 7-53 NT6X44 (continued) Close the locking levers. Use the following information to determine where to go next in this procedure. If you entered this procedure from alarm clearing procedures step 20 other step 15 Test the inactive SMS unit by typing >TST UNIT unit_no and pressing the Enter key.
Page 260 7-54 Card replacement procedures NT6X44 NT6X44 (continued) (end) Return the inactive SMS unit to service by typing >RTS UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit If RTS passed step 17 failed step 21 At the frame...
Page 261: Nt6X69 Sms
7-55 Card replacement procedures 7-55 7-55 NT6X69 Application Use this procedure to replace an NT6X69 card in an SMS. Suffixes Name NT6X69 AB, AC, AD, QA CPP message protocol and tone generator Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 262 7-56 Card replacement procedures NT6X69 (continued) Summary of card replacement procedure for an NT6X69 card in an SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this Test Locate faulty flowchart to perform the INACTIVE card procedure.
Page 263 Card replacement procedures 7-57 NT6X69 (continued) Replacing an NT6X69 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 264 7-58 Card replacement procedures NT6X69 (continued) The system determines the type of SWACT it can perform, and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time step 23 Switch the activity of the unit by typing >YES and pressing the Enter key.
Page 265 Card replacement procedures 7-59 NT6X69 (continued) Set the PM to the ROM level by typing >PMRESET UNIT unit_no NORUN and pressing the Enter key. where unit_no is the number of the faulty SMS unit At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS.
Page 266 7-60 Card replacement procedures NT6X69 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 267 Card replacement procedures 7-61 NT6X69 (continued) Open the locking levers on the replacement card. Align the card with the slots in the shelf and gently slide the card into the shelf. CAUTION Loss of subscriber service Subscriber service may be lost in the active unit when reseating the NT6X69 card.
Page 268 7-62 Card replacement procedures NT6X69 (continued) Close the locking levers. Perform a full reset of the inactive unit by typing >PMRESET UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit Use the following information to determine what step to go next in this procedure.
Page 269 Card replacement procedures 7-63 NT6X69 (continued) If TST passed step 18 failed step 22 Return the inactive SMS unit to service by typing >RTS UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit If RTS passed step 19...
Page 270 7-64 Card replacement procedures NT6X69 NT6X69 (continued) (end) For further assistance with switch of activity, contact the personnel responsible for the next level of support. Note: If the system recommends using the SWACT command with the FORCE option, consult office personnel to determine if use of the FORCE option is advisable.
Page 271: Nt6X78 Sms
7-65 Card replacement procedures 7-65 7-65 NT6X78 Application Use this procedure to replace an NT6X78 card in an SMS. Suffixes Name NT6X78 AA, AB CLASS modem resource Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 272 7-66 Card replacement procedures NT6X78 (continued) Summary of Card replacement procedure for an NT6X78 card in an SMS This flowchart summarizes the procedure. Use the instructions in the Locate procedure that follows this faulty flowchart to perform the card procedure. inactive unit Busy CMR...
Page 273 Card replacement procedures 7-67 NT6X78 (continued) Replacing an NT6X78 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 274 7-68 Card replacement procedures NT6X78 (continued) Busy the CMR card by typing >BSY UNIT unit_no CMR and pressing the Enter key. where unit_no is the number of the unit containing the faulty CMR card At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS.
Page 275 Card replacement procedures 7-69 NT6X78 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 276 7-70 Card replacement procedures NT6X78 (continued) Open the locking levers on the replacement card. Align the card with the slots in the shelf and gently slide the card into the shelf. Seat and lock the card. Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf.
Page 277 Card replacement procedures 7-71 NT6X78 (continued) If load passed step 11 failed step 14 Test the CMR card by typing >TST UNIT unit_no CMR and pressing the Enter key. where unit_no is the number of the unit containing the faulty CMR card If TST passed step 12...
Page 278 7-72 Card replacement procedures NT6X78 NT6X78 (continued) (end) At the frame Remove the sign from the active SMS unit. Send any faulty cards for repair according to local procedure. Record the following items in office records according to local policy: date the card was replaced serial number of the card symptoms that prompted replacement of the card...
Page 279: Nt6X80 Sms
7-73 Card replacement procedures 7-73 7-73 NT6X80 Application Use this procedure to replace an NT6X80 card in an SMS. Suffixes Name NT6X80 AA, BB SCM pad/ring Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 280 7-74 Card replacement procedures NT6X80 (continued) Summary of card replacement procedure for an NT6X80 card in an SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this flowchart to perform the Locate procedure. inactive faulty card unit ManBusy End of...
Page 281 Card replacement procedures 7-75 NT6X80 (continued) Replacing an NT6X80 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 282 7-76 Card replacement procedures NT6X80 (continued) The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time step 23 Switch the activity of the unit by typing >YES and pressing the Enter key.
Page 283 Card replacement procedures 7-77 NT6X80 (continued) unit_no is the number of the faulty SMS unit At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS.
Page 284 7-78 Card replacement procedures NT6X80 (continued) Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 285 Card replacement procedures 7-79 NT6X80 (continued) Close the locking levers. Use the following information to determine where to go next in this procedure. If you entered this procedure from alarm clearing procedures step 17 other step 15 Test the inactive unit by typing >TST UNIT unit_no and pressing the Enter key.
Page 286 7-80 Card replacement procedures NT6X80 NT6X80 (continued) (end) unit_no is the number of the faulty SMS unit If RTS passed step 19 failed step 18 Return to the maintenance procedure that directed you to this procedure. At the point where a faulty card list was produced, identify the next faulty card on the list and go to the appropriate card replacement procedure for that card in this manual.
Page 287: Nt6X85 Sms
7-81 Card replacement procedures 7-81 7-81 NT6X85 Application Use this procedure to replace an NT6X85 card in an SMS. Suffixes Name NT6X85 AA, AB, AC DS-1 interface for SLC-96 Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 288 7-82 Card replacement procedures NT6X85 (continued) Summary of card replacement procedure for an NT6X85 card in an SMS This flowchart summarizes the procedure. Use the instructions in the Locate procedure that follows this faulty flowchart to perform the card procedure. Display and busy links to DS–1 card...
Page 289 Card replacement procedures 7-83 NT6X85 (continued) Replacing an NT6X85 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 290 7-84 Card replacement procedures NT6X85 (continued) Display the DS-1 links associated with the faulty DS-1 interface card by typing >TRNSL P and pressing the Enter key. Record all link numbers, information on faulty links, and any protection line information. Each 6X85 card has 2 ports; for instance, ports 0 and 1 are on one 6X85 card.
Page 291 Card replacement procedures 7-85 NT6X85 (continued) Access the carrier level of the MAP display by typing >TRKS;CARRIER;POST SMS mod_no link_no SMS mod_no link_no ... and pressing the Enter key. where mod_no is 0–127 with an NT40 and 0–255 with DMS SuperNode link_no is the number of a protection line connected to the faulty card Note: As many as five SMS mod_no link_no commands can be executed...
Page 292 7-86 Card replacement procedures NT6X85 (continued) Access the PM level of the MAP display by typing >PM;POST SMS sms_no and pressing the Enter key. where sms_no is 0–127 for NT40 and 0–255 for DMS SuperNode Example of a MAP response INSV LINKS_OOS CSIDE 0...
Page 293 Card replacement procedures 7-87 NT6X85 (continued) Remove the NT6X85 card as shown in the following figures. Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf.
Page 294 7-88 Card replacement procedures NT6X85 (continued) Open the locking levers on the replacement card. Align the card with the slots in the shelf and gently slide the card into the shelf. Seat and lock the card. Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf.
Page 295 Card replacement procedures 7-89 NT6X85 (continued) Use the following information to determine what step to go to next in this procedure. one protection line busied in step step 5, then step 16 8 and you are at the PM level two protection lines busied in step step 16 8 and you are at carrier level...
Page 296 7-90 Card replacement procedures NT6X85 NT6X85 (continued) (end) Repeat this command for each busied link. If RTS passed step 18 failed step 21 Send any faulty cards for repair according to local procedure. Note in office records according to local policy: date the card was replaced serial number of the card symptoms that prompted replacement of the card...
Page 297: Nt6X86 Sms
7-91 Card replacement procedures 7-91 7-91 NT6X86 Application Use this procedure to replace an NT6X86 card in an SMS. Suffixes Name NT6X86 A-bit message card Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 298 7-92 Card replacement procedures NT6X86 (continued) Summary of card replacement procedure for an NT6X86 card in an SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this flowchart to perform the Locate procedure. inactive faulty card unit ManBusy End of...
Page 299 Card replacement procedures 7-93 NT6X86 (continued) Replacing an NT6X86 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 300 7-94 Card replacement procedures NT6X86 (continued) By observing the MAP display, be sure the card to be removed is on the inactive unit. If faulty card is on active unit step 5 inactive unit step 8 Switch the activity of the units by typing >SWACT and pressing the Enter key.
Page 301 Card replacement procedures 7-95 NT6X86 (continued) Return to the “SMS alarm clearing procedures” section in this document to clear the alarm condition on the inactive unit. When the alarm is cleared, return to step 6 of this procedure. At the frame Put a sign on the active unit bearing the words: Active unit—Do not touch.
Page 302 7-96 Card replacement procedures NT6X86 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Verify the replacement card has the same PEC, including suffix, as the card you just removed.
Page 303 Card replacement procedures 7-97 NT6X86 (continued) Open the locking levers on the replacement card. Align the card with the slots in the shelf and gently slide the card into the shelf. Seat and lock the card. Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf.
Page 304 7-98 Card replacement procedures NT6X86 (continued) Use the following information to determine what step to go to next in this procedure. If you entered this procedure from alarm clearing procedures step 17 other step 15 Test the inactive unit by typing >TST UNIT unit_no and pressing the Enter key.
Page 305 Card replacement procedures 7-99 NT6X86 NT6X86 (continued) (end) Obtain further assistance in replacing this card by contacting the personnel responsible for higher level of support. At the frame Remove the sign from the active SMS unit. Send any faulty cards for repair according to local procedure. Record the following items in office records according to local policy: date the card was replaced serial number of the card...
Page 306: Nt6X92 Sms
7-100 7-100 Card replacement procedures 7-100 NT6X92 Application Use this procedure to replace an NT6X92 card in an SMS. ATTENTION To ensure peak performance, do not install the UTR and GTR on the same SMS. Presently, there is no way of knowing which receiver is used to interpret tones.
Page 307 Card replacement procedures 7-101 NT6X92 (continued) Summary of card replacement procedure for an NT6X92 card in an SMS This flowchart summarizes the procedure. Use the instructions in the procedure that follows this flowchart to perform the Locate procedure. inactive faulty card unit ManBusy End of...
Page 308 7-102 Card replacement procedures NT6X92 (continued) Replacing an NT6X92 card in an SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 309 Card replacement procedures 7-103 NT6X92 (continued) The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time step 23 Switch the activity of the unit by typing >YES and pressing the Enter key.
Page 310 7-104 Card replacement procedures NT6X92 (continued) At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point at the left side of the frame supervisory panel of the SMS. This protects the equipment against damage caused by static electricity.
Page 311 Card replacement procedures 7-105 NT6X92 (continued) Open the locking levers on the replacement card. Align the card with the slots in the shelf and gently slide the card into the shelf. Seat and lock the card. Using your fingers or thumbs, push on the upper and lower edges of the faceplate to ensure the card is fully seated in the shelf.
Page 312 7-106 Card replacement procedures NT6X92 (continued) Use the following information to determine where to go next in this procedure. If you entered this procedure from alarm clearing procedures step 17 other step 15 Test the inactive unit by typing >TST UNIT unit_no and pressing the Enter key.
Page 313 Card replacement procedures 7-107 NT6X92 NT6X92 (continued) (end) At the frame Remove the sign from the active SMS unit. Send any faulty cards for repair according to local procedure. Record the following items in office records according to local policy: date the card was replaced serial number of the card symptoms that prompted replacement of the card...
Page 314: Nt7X05 Sms
7-108 7-108 Card replacement procedures 7-108 NT7X05 Application Use this procedure to replace the following card in an SMS. Suffixes Name NT7X05 Peripheral loader Common procedures None Action The following flowchart is a summary of the procedure. To replace the card, use the instructions in the procedure that follows the flowchart.
Page 315 Card replacement procedures 7-109 NT7X05 (continued) Summary of card replacement procedure for an NT7X05 card in an RSC SMS This flowchart summarizes the procedure. Locate From Use the instructions in the faulty other procedure that follows this card procedure flowchart to perform the procedure.
Page 316 7-110 Card replacement procedures NT7X05 (continued) Replacing an NT7X05 card in an SMS At your Current Location Proceed only if you were either directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure to verify or accept cards, or were directed to this procedure by your maintenance support group.
Page 317 Card replacement procedures 7-111 NT7X05 (continued) sms_no is the number of the SMS to be busied Example of a MAP display: Trks APPL 1SMS SysB ManB OffL CBsy ISTb InSv 0 Quit 2 Post_ 3 ListSet 0 ISTb Links_OOS: CSide 0, PSide 5 TRNSL_ Unit0:...
Page 318 7-112 Card replacement procedures NT7X05 (continued) Switch the activity of the unit by typing >YES and pressing the Enter key. The system runs a pre-SWACT audit to determine the ability of the inactive unit to accept activity reliably. Note: A maintenance flag appears when maintenance tasks are in progress. Wait until the flag disappears before proceeding with the next maintenance action.
Page 319 Card replacement procedures 7-113 NT7X05 (continued) At the frame WARNING Static electricity damage Before removing any cards, put on a wrist strap and connect it to the wrist strap grounding point on the left side of the frame supervisory panel of the SMS. This protects the equipment against damage caused by static electricity.
Page 320 7-114 Card replacement procedures NT7X05 (continued) Open the locking levers on the card to be replaced and gently pull the card towards you until it clears the shelf. FW-xxxxx Ensure the replacement card has the same PEC, including suffix, as the card you just removed.
Page 321 Card replacement procedures 7-115 NT7X05 (continued) Close the locking levers. At the MAP display Test the inactive SMS unit by typing >TST UNIT sms_unit_no and pressing the Enter key. where sms_unit_no is the number of the inactive SMS unit Example of a MAP response: Test Passed Test Failed If TST...
Page 322 7-116 Card replacement procedures NT7X05 (continued) Return the inactive SMS unit to service by typing >RTS UNIT unit_no and pressing the Enter key. where unit_no is the number of the SMS unit (0 or 1) tested in step 14 If TST passed step 16 failed...
Page 323 Card replacement procedures 7-117 NT7X05 NT7X05 (continued) (end) You have successfully completed this procedure. Return to the maintenance procedure that directed you to this card replacement procedure and continue as directed. For further assistance with switch of activity, contact the personnel responsible for the next level of support.
Page 324: Ntmx71 Sms
7-118 7-118 Card replacement procedures 7-118 NTMX71 Application Use this procedure to replace a NTMX71 card in a SMS. Suffixes Name NTMX71 XPM Plus Terminator Paddleboard Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 325 Card replacement procedures 7-119 NTMX71 (continued) Summary of card replacement procedure for a NTMX71 card in a SMS This flowchart summarizes the procedure. Use the instructions in the Post the PM step-action procedure that follows this flowchart to perform the procedure.
Page 326 7-120 Card replacement procedures NTMX71 (continued) Replacing a NTMX71 card in a SMS At your Current Location Proceed only if you have been directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or have been directed to this procedure by your maintenance support group.
Page 327 Card replacement procedures 7-121 NTMX71 (continued) The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time step 23 Confirm the system prompt by typing >YES and pressing the Enter key.
Page 328 7-122 Card replacement procedures NTMX71 (continued) pre-SWACT query failure unit is jammed inactive unit is in overload pre-SWACT difficulties You must clear all faults on the inactive unit and switch activity to the inactive unit before attempting to change the faulty card on the active unit. A problem has been detected as a result of your attempt to SWACT to the inactive unit.
Page 329 Card replacement procedures 7-123 NTMX71 (continued) Busy the inactive PM unit by typing >BSY UNIT unit_no and pressing the Enter key. where unit_no is the number of the inactive SMS unit (0 or 1) Set the PM to the ROM level by typing >PMRESET UNIT unit_no NORUN and pressing the Enter key.
Page 330 7-124 Card replacement procedures NTMX71 (continued) DANGER Risk of eye or facial injury When removing the NTMX77 card, do not jerk the paddleboard from the backplane pins. Instead, gently rock the paddleboard off the packplane pins. Remove the NTMX71 card. Place the card you have removed in an electrostatic discharge (ESD) protective container.
Page 331 Card replacement procedures 7-125 NTMX71 (continued) If load passed step 28 failed step 33 Test the inactive SMS unit by typing >TST UNIT unit_no and pressing the Enter key. where unit_no is the number of the SMS unit loaded in step 27 If TST passed step 29...
Page 332 7-126 Card replacement procedures NTMX71 NTMX71 (continued) (end) Note the following in the office records: date the card was replaced serial number of the card symptoms that prompted replacement of the card Go to step 34. For further assistance, contact the personnel responsible for the next level of support.
Page 333: Ntmx77 Sms
7-127 Card replacement procedures 7-127 7-127 NTMX77 Application Use this procedure to replace an NTMX77 card in an SMS. Suffixes Name NTMX77 Unified processor (UP) Common procedures None Action The following flowchart is only a summary of the procedure. To replace the card, use the instructions in the step-action procedure that follows the flowchart.
Page 334 7-128 Card replacement procedures NTMX77 (continued) Summary of card replacement procedure for an NTMX77 card in an SMS This flowchart summarizes the Locate faulty procedure. NTMX77 card Use the instructions in the procedure that follows this LOADPM UNIT flowchart to perform the with LOCAL procedure.
Page 335 Card replacement procedures 7-129 NTMX77 (continued) Summary of card replacement procedure for an NTMX77 card in an SMS LOADPM UNIT with CC firmware TST SMS RTS SMS TST pass? End of RTS pass? procedure Contact the next level of support DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 336 7-130 Card replacement procedures NTMX77 (continued) Replacing an NTMX77 card in an SMS At your Current Location Proceed only if you were either directed to this card replacement procedure from a step in a maintenance procedure, are using the procedure for verifying or accepting cards, or were directed to this procedure by your maintenance support group.
Page 337 Card replacement procedures 7-131 NTMX77 (continued) Switch the activity of the units by typing >SWACT and pressing the Enter key. The system determines the type of SWACT it can perform and displays a confirmation prompt for the selected SWACT. If SWACT can continue at this time step 6 cannot continue at this time...
Page 338 7-132 Card replacement procedures NTMX77 (continued) At the MAP terminal Busy the inactive SMS unit by typing >BSY UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit Set the unit to the ROM level by typing >PMRESET UNIT unit_no NORUN and pressing the Enter key.
Page 339 Card replacement procedures 7-133 NTMX77 (continued) Locate the card to be removed on the appropriate shelf. Open the locking levers on the card to be replaced and gently pull the card toward you until it clears the shelf. Ensure the replacement card has the same PEC, including suffix, as the card you just removed.
Page 340 7-134 Card replacement procedures NTMX77 (continued) WARNING Possible loss of P-side nodes Monitor the LEDs on the faceplate of the replacement NTMX77 when installing. 1. The INSV and ESA LEDs may come ON and must go OFF in less than 4 seconds. 2.
Page 341 Card replacement procedures 7-135 NTMX77 (continued) Close the locking levers. Reseat the NT6X41 card. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 342 7-136 Card replacement procedures NTMX77 (continued) At the MAP terminal The peripheral loader card (NT7X05) allows local loading of the NTMX77 data. Local data loading reduces recovery time. Check if the NT7X05 card is provisioned by typing: >QUERYPM FILES and pressing the Enter key. Example of a MAP display: Trks APPL...
Page 343 Card replacement procedures 7-137 NTMX77 (continued) CAUTION ISDN units can not be loaded by LOCAL IMAGE Do not LOADPM from the LOCAL IMAGE on units with ISDN capability. The NT7X05 card does not support ISDN, use LOCAL LOADFILE or load from the CC on units with ISDN.
Page 344 7-138 Card replacement procedures NTMX77 (continued) If load passes step 22 fails step 29 Query the XPM countrs for the firmware load on the NTMX77 by typing: >QUERYPM CNTRS and pressing the Enter key. Example of a MAP display: Unsolicitited MSG limit = 250, Unit 0 = 0, Unit 1 = 0 Unit 0: Ram Load: ESS05AW EPRom Version: AB02...
Page 345 Card replacement procedures 7-139 NTMX77 (continued) Load the firmware in the inactive SMS unit by typing >LOADPM UNIT unit_no CC FIRMWARE and pressing the Enter key. where unit_no is the number of the faulty SMS unit busied in step 9 If load passes step 23...
Page 346 7-140 Card replacement procedures NTMX77 NTMX77 (continued) (end) Return the inactive SMS unit to service by typing >RTS UNIT unit_no and pressing the Enter key. where unit_no is the number of the faulty SMS unit tested in step 23 If RTS passes step 25 fails...
Page 347: Manually Busying Sms C-Side Links
7-141 Card replacement common procedures 7-141 7-141 Manually busying SMS C-side links Application Use this procedure to remove from service C-side links between an XMS–based peripheral module (XPM) and the network. Use this procedure for both junctored networks (JNET) and enhanced networks (ENET). This procedure assumes that the user posted the peripheral module (PM) and the PM is available for query.
Page 348 7-142 Card replacement common procedures Manually busying SMS C-side links (continued) Summary of Manually busying SMS C-side links This flowchart summarizes the Display C-side procedure. links for the Use the instructions that follow this flowchart to perform the procedure. Is this an Access the enhanced LINKS level of...
Page 349 Card replacement common procedures 7-143 Manually busying SMS C-side links (continued) Manually busying SMS C-side links CAUTION Loss of service Proceed only if you have been directed here from a step in a maintenance procedure. This procedure removes from service C-side links between the Series II PM and the network.
Page 350 7-144 Card replacement common procedures Manually busying SMS C-side links (continued) Record the network plane, pair, and link for each C-side link for the XPM shelf associated with the card you replace. Note 1: The NT6X40AA DS-30 C-side interface card supports eight C-side links per card, with two cards provisioned for each PM unit.
Page 351 Card replacement common procedures 7-145 Manually busying SMS C-side links (continued) To busy one of the links you recorded in step 2, type >BSY plane_no link_no and press the Enter key. where plane_no is the number of the plane for the link (0 or 1) link_no is the link number (0 to 63) Example of a MAP response:...
Page 352 7-146 Card replacement common procedures Manually busying SMS C-side links (continued) shelf_no is the number of the shelf (0 to 7) to which the XPM C-side links are connected Example of a MAP display: ENET System Matrix Shelf 0 1 2 3 Plane 0 CSLink F –...
Page 353 Card replacement common procedures 7-147 Manually busying SMS C-side links (continued) the links are DS-30s and you have step 12 not manually busied all links the links are DS-30s and you have step 13 manually busied all links the link is a DS-512 step 13 Repeat step 11 for each DS-30 link recorded in step 7.
Page 354 7-148 Card replacement common procedures Manually busying SMS C-side links Manually busying SMS C-side links (end) (continued) Table 1xxx Port to link correlation for NT6X40AA cards in XPM 6X40 trnsl 6X40 trnsl port slot link plane port slot link plane Note: The trnsl link corresponds to the list obtained through the TRNSL C command.
Page 355: Returning A Card For Repair Or Replacement
7-149 Card replacement procedures 7-149 7-149 Returning a card for repair or replacement Returning a card for repair or replacement Application Use this procedure to return a circuit card for repair or replacement. An example of a circuit card you might return is a power converter. Operating companies return the cards to different addresses that depend on the location of the company (Canada or the United States).
Page 356 7-150 Card replacement procedures Returning a card for repair or replacement (continued) Summary of returning a card for repair or replacement This flowchart summarizes the procedure. Place card in Use the instructions that follow ESD protective this flowchart to perform the procedure.
Page 357 Address the carton to: Nortel Customer Service Center, 4600 Emperor Blvd., Morrisville, North Carolina, 27560 Go to step 11.
Page 358 Address the carton to: Nortel Customer Operations, c/o Wesbell Transport, 1630 Trinity Road, Unit #3 Door #4, Mississauga, Ontario, L5T 1L6 This procedure is complete.
Page 359: Removing And Replacing A Card
7-153 Card replacement procedures 7-153 7-153 Removing and replacing a card Application Use this procedure when you remove a circuit card and insert a replacement circuit card. Action This procedure contains a summary flowchart and a list of steps. Use the flowchart to review the procedure.
Page 360 7-154 Card replacement procedures Removing and replacing a card (continued) Removing and replacing a card in a shelf At the cabinet CAUTION Equipment damage Take the following precautions when you remove or insert a card: 1. Make sure you do not apply direct pressure to the components.
Page 361 Card replacement procedures 7-155 Removing and replacing a card (continued) Open the locking levers on the defective circuit card. The top locking lever opens up and the bottom locking lever opens down. Gently pull the circuit card toward you until the circuit card clears the shelf. Place the circuit card you have removed in an electrostatic discharge (ESD) protective container.
Page 362 7-156 Card replacement procedures Removing and replacing a card Removing and replacing a card (continued) (end) Open the locking levers on the replacement circuit card. Align the circuit card with the slots in the shelf and carefully slide the circuit card into the shelf. Seat and lock the circuit card.
Page 363: Locating And Clearing Sms Trouble
Locating and clearing SMS trouble Maintenance engineering and field maintenance personnel use this section. Maintenance personnel must have knowledge of the following: the Subscriber Carrier Module-100S (SMS) interface to the remote-concentrator SLC-96 (RCS) and the DS-1 links between the SMS and the RCS the subscriber loop.
Page 365: Trouble Isolation And Correction
Trouble isolation and correction Locating and clearing faults Problem condition indicators Problem conditions can include the following: operational measurements (OM) log reports alarms Operational measurements The OMs monitor and count events in the system. The OMs are the best means for detecting both current and potential system troubles. The OM thresholding feature monitors and reports key Subscriber Carrier Module 100–S (SMS) activity.
Page 366 9-2 Trouble isolation and correction The level of the alarm indicates alarm seriousness and corresponding urgency for correction. Alarm levels are minor, major, or critical. The following table describes alarm conditions. Alarm description Alarm MAP display Description Indicates does not affect Minor blank service.
Page 367: Fault Isolation Tests For The Sms
Trouble isolation and correction 9-3 Standard problem solving steps Perform the following standard troubleshooting steps to locate and clear faults: 1 Silence audible alarms that occur when the system detects alarm conditions. 2 Isolate the fault. Read status displays and trace fault codes to the menu level required to clear the fault.
Page 368 9-4 Trouble isolation and correction Accessing SysB alarms for the SMS Message at SMS level Possible conditions The central-side (C-side) peripheral All C-side Links are Down module (PM) cannot communicate with the SMS. The computing module (CM) detects Audit Detected Inconsistent that unit 0 is active, but unit 1 is PM Activity inactive.
Page 369 Trouble isolation and correction 9-5 Accessing SysB alarms for the SMS (continued) Message at SMS level Possible conditions Terminated REX Incomplete The routine exercise (REX) test cannot complete the series of tests because of a condition that is not normal. At least one unit is: InSv trouble (ISTb) Inactive unit is BSY.
Page 370: Handling An Istb Sms Unit
9-6 Trouble isolation and correction Standard troubleshooting methods require a test of an exact unit of a SysB SMS. If the unit passes the tests and can RTS, the system clears the SysB fault. A list of suspected defective SMS cards can accompany test failures. The following is an example of a card list.
Page 371 Trouble isolation and correction 9-7 Assessing ISTb alarms for the SMS (continued) Message at SMS level Alarm Possible conditions Minor The C-side message links fail the CSLinks Out of periodic InSv C-side links test, one Service each minute. Minor A P-side link became SysB. The PSLinks Out of system requires DS-1 link Service...
Page 372: Handling An Imc Link Fault
9-8 Trouble isolation and correction reset the SMS load the SMS again Handling an IMC link fault When the intermodule communication (IMC) link audit detects data loss or damage to the messages over IMC links, the SMS becomes ISTb. The system generates a PM128 log.
Page 373 Trouble isolation and correction 9-9 problem indicators for each type of fault. Actions that the CM and the operating company personnel must take appear under each trouble indicator. The three types of parity faults are as follows: An intermittent fault. This fault occurs when the SMS detects a parity error and does not find an error during the read over of the location.
Page 374 9-10 Trouble isolation and correction PM181 JUL23 23:29:16 5561 INFO SMS 0 UNIT 0 Node: ISTb, Unit 0 Act: InSv, Unit 1, Inact: InSv Parity audit detected hard parity fault Site Flr RPos Bay_id Description Slot EqPEC SMS 00 SME 00 SMR: MX77AA Other problem indicators include the following:...
Page 375 Trouble isolation and correction 9-11 Other problem indicators include the following: PM128—The SMS is set to ISTb, with the active unit as ISTb from InSv. PM128 JUL23 23:29:16 5561 TBL ISTb SMS 0 Node: ISTb, (Inact OOS) From InSv Unit 0 Act: IsTb (Parity errors detected) from InSv Unit 1 Inact: PM 189—The active unit of the SMS has a hard fault.
Page 376 9-12 Trouble isolation and correction PM189—The inactive unit of the SMS has a fault in program store. PM189 JUL23 23:29:17 5561 INFO PM SW INFORMATION REPORT SMS 0 Unit 0: Inact TASKID: 00370037 PARAUDT, TIME: 22:29:16.68 COMID: FF NILCID TEXT: softpgm 00 00 57 F6 00 00 >...
Page 377 Trouble isolation and correction 9-13 –The following ISTb is present: a soft parity fault was >QUERYPM FLT detected in program store of memory. Action by the CM In this example the inactive unit is not InSv. The CM cannot take the defective unit OOS because this action busies the SMS.
Page 378 9-14 Trouble isolation and correction The CM returns the unit to service. The CM can also download new static data and run full diagnostics if necessary. User action The CM brings the unit back to service and interruption is required if the SMS does not RTS.
Page 379 Trouble isolation and correction 9-15 Node: ISTb, Unit 0 Act: InSv, Unit 1, Inact: InSv Parity audit detected intermittent parity fault. Other problem indicators include the following: PM128—The SMS is set ISTb, with the inactive unit as OOS. PM128 JUL23 23:29:16 5561 TBL ISTb SMS 0 Node: ISTb, (Inact OOS) From InSv...
Page 380: Fault Isolation Tests For The Rcs
9-16 Trouble isolation and correction Node: ISTb, (Inact OOS) From InSv Unit 0 Act: ISTb (Parity errors detected) from InSv Unit 1 Inact: SysB PM189—The active unit of the SMS has a parity fault that is not continuous. PM189 JUL23 23:29:17 5561 INFO PM SW INFORMATION REPORT SMS 0 Unit 0: TASKID:...
Page 381 Trouble isolation and correction 9-17 minor power/miscellaneous shelf. These alarms appear as PM128 log reports at the MAP terminal. In addition to the description provided in the following paragraphs, information and instructions for actions are provided in the alarm description table in this document.
Page 382: Rcs Fault Isolation Tests
9-18 Trouble isolation and correction Shelf alarm A shelf alarm indicates a failure on a specified RCS shelf. This failure is major and sets the RCS to ISTb. A LCGA, where the SMS detects a fault on a DS-1 link, is an example of a fault that causes a shelf alarm. The types of shelf alarms include A SHELF, B SHELF, C SHELF, and D SHELF.
Page 383: Fault Isolation Tests For Ds-1 Link Faults
Trouble isolation and correction 9-19 options. When the user issues the FELP TEST, all 24 DS-1 channels on the specified link are looped, and the system sends PCM on DS-1 channel 4. The PCM is looped, and the PCM sent and received are compared. The user can perform the FELP command on InSv, protection, and BSY DS-1 links.
Page 384: Alarms
9-20 Trouble isolation and correction display carriers in an exact state post a carrier or group of carriers protection switch a carrier. The following commands cannot be executed on a remote carrier, but the commands appear on the CARRIER menu display: >TST >BSY >RTS...
Page 385 Trouble isolation and correction 9-21 A carrier is placed temporarily system busy (SysB-T) or permanently system busy (SysB-P). The state depends on the number of times the system returned the carrier to service. The carrier is set SysB-T if the carrier meets the following requirements: A steady state alarm was raised for a carrier, excess bipolar violations occurred, or the carrier exceeded the OL for frame losses or slips.
Page 386 9-22 Trouble isolation and correction Maintenance limit, OOS limit, and audit interval carrier defaults Item Audit interval Frame Loss 10.0 min Slip 10.0 min BpV (BER) 1 in 10 1 in 10 4.8 s 10.0 min The DMS-100 switch counts frame losses, slips, BpV, and RTS for either specified time or audit intervals.
Page 387 Trouble isolation and correction 9-23 DETAIL MAP display that shows carrier information Trks APPL DETAIL CLASS Alarm SysB ManB Uneq Offl CBsy PBsy InSv Quit_ TRUNKS Post_ REMOTE PROTLN Loop_ N CLASS SITE SMS CK D ALRM SLIP FRME BER ES SES STATE PROT Tst_ 0 REMOTE HOST 0 1 –5.2 OS...
Page 388: Fault Isolation For Subscriber Lines
9-24 Trouble isolation and correction Fault isolation for subscriber lines Subscriber lines maintenance Lines maintenance for the RCS consists of the following areas: commands issued from the LTP and automatic line testing (ALT) levels line diagnostic initiated by a system diagnostic scheduler, a DMS-100 software process that occurs when a call fails twice subscriber station tests line tests executed through a mechanized loop tester (MLT) or test desk...
Page 389: Maintenance Scenarios
PM reply that is not planned software error test alarm return code. When a test is aborted because of the conditions mentioned earlier, Nortel recommends the following actions: 1 Check the RCS for PM reply time-out and a PM reply that is not planned.
Page 390 9-26 Trouble isolation and correction 6 Replace the line card for failure messages. Several error messages that apply to diagnostics appear on the following table: Diagnostic error messages and failed tests Failed test Error message Negative tip party ringing Tip ringing, ANI ground Positive tip party ringing Positive tip party Positive ring party ringing...
Page 391 Trouble isolation and correction 9-27 Run lines tests To access subscriber lines from the LTP or the ALT level, a metallic test access (MTA) minibar switch is used with a metallic test pair. Up to 32 RCS modules can share a metallic test pair. A maximum of 2000 subscriber lines are recommended for support off one test pair.
Page 392 9-28 Trouble isolation and correction MTA for the RCS line card RING RCS LINE CARD When a subscriber loop connects to the MTA, it can be tested from the LTP or the ALT levels. The RCS line cards have test access (TA) and cutoff (CO) functions on the same relay.
Page 393 Trouble isolation and correction 9-29 pathways to the loop. The attempt to run the silent switchman test causes a of the reorder tone to return to the RCS line. The same relay cuts the line card off from the subscriber loop. The test pair that comes from the MTA switch accesses the subscriber loop.
Page 394 9-30 Trouble isolation and correction To remove a termination, the SMS sends an on-hook message to the RCS in the M-field of the DDL. The following sequence of events occurs during test setup of an RCS line card: 1 The CM sends a test request to the SMS. 2 To initiate test setup in the RCS, the SMS sends an A- and B-bit pattern to the RCS.
Page 395 Trouble isolation and correction 9-31 9 The channel loss test uses the TTU. 10 The noise test uses the TTU. 11 The SMS sends the RCS a message to terminate the channel test and sends idle A-B bits. 12 The diagnostic is complete. Multi-party test sequence The test sequence for a multi-party card follows: 1 The SMS sends the RCS a channel test setup request.
Page 396 9-32 Trouble isolation and correction 17 The SMS sends the RCS a message to remove termination. 18 The SMS signals the RCS to test +T ringing and scans for off-hook. The RCS connects absorb-PTPG termination, detects termination as off-hook if +T ringing is present, and signals off-hook to the SMS. 19 The echo return loss test uses TTU to determines if absorb termination made.
Page 397 Trouble isolation and correction 9-33 16 The SMS sends a request to the RCS for a reverse battery test and scans for off-hook. If there a positive talk battery is present, the following actions occur. The RCS detects off-hook and sends off-hook A-B bits to the SMS.
Page 398 9-34 Trouble isolation and correction Bridged access that uses a conference card DS30 Test Analog trunks links Test desk trunk Digital Port 1 network Port 2 Port 3 Conference card Line card DS–1 link Line card Operating company personnel can dial the subscriber line directory number (DN) or line equipment number (LEN) to test from the test desk.
Page 399 Trouble isolation and correction 9-35 If the conference call is set up and the test desk disconnects, the two original lines remain connected. The original lines remain connected without the use of a conference card. The following list is a list of events that lead to a conference call that fails to be set up.
Page 400 9-36 Trouble isolation and correction Test desk receives reorder tone 120 ipm — the MTA network is not available — the line is hardware not assigned — the line is ManB — the line is line module BSY — the line is in the PLO state —...
Page 401 Trouble isolation and correction 9-37 Test desk configuration Input/ DS30 link Tip, ring, sleeve, ground output test trunk Horizontal Test access Applique 2 test pair network DS30 link Digital network Vertical test pair DS30 link DS-1 link Station testing Station testing helps to determine if a station functions correctly while the station connects to a loop and a line circuit group.
Page 402: Diagnostic Tests For The Sms
9-38 Trouble isolation and correction The following is a list of information that appears in log reports ALT101 or LINE101 or at the MAP display. The information is for station ringer and dialable short circuit tests that the system aborts: connection failure PM is not ready check the channel test unit, the line card, or both...
Page 403: A- And B-Bit Diagnostic
Trouble isolation and correction 9-39 timers/integrated circuits that you can program. Note: After the system runs the ROM diagnostic, operating company personnel must load the unit again. A- and B-bit diagnostic The A- and B-bit diagnostic tests the A- and B-bit circuits on the NT6X44 time switch card.
Page 404: Formatter Diagnostic
9-40 Trouble isolation and correction correct action between the integrity match-mismatch and CDB update logic correct operation of the CSM loop on the NT6X41 formatter card. This diagnostic involves the following hardware components: the NT6X42 CSM card the NT6X41 formatter card the speech bus Formatter diagnostic The formatter diagnostic tests the NT6X41 formatter card.
Page 405: Tones Diagnostic
Trouble isolation and correction 9-41 the NT6X85 DS-1 interface cards the speech bus Tones diagnostic The tones diagnostic runs PCM checksums on the tones of ports 16 and 17 phantom ports. The tones diagnostic runs the checksum to make sure that these checksums agree with the checksums in the tone ROM.
Page 406: Ring/Pad Card Diagnostic
9-42 Trouble isolation and correction comparators to detect defective comparators that office synchronization uses. This diagnostic involves the following hardware components: the NT6X44 the NT6X69 (NT6X69AD ASIC version if UTR is present) Ring/pad card diagnostic The ring/pad diagnostic tests the hardware and functionality of the NT6X80 ring/pad card.
Page 407: Testing The Ddl Card
Trouble isolation and correction 9-43 The signaling processor (SP) checks the received message against the transmitted message. If the two messages are not identical, the mismatch indicates a fault in the SLC-96 card. The DS-1 board diagnostic is part of the command.
Page 408: P-Side Link Diagnostic
9-44 Trouble isolation and correction The location of the failure in the DMS office appears in the failure message. The message identifies the production engineering code (PEC) of the card suspected of the failure. The parts of the A/B-DDL card tested depend on the SMS mode of operation.
Page 409: Cmr Diagnostic
Trouble isolation and correction 9-45 When a system audit detects a SysB link, the DMS-100 generates the following PM110 log: PM110 MAY16 09:27:33 4899 INFO CARRIER SMS 60 CARRIER–NO: 8, REASON: REMOTE LINK SYSBSY When a link is RTS, the SMS and RCS leave the ISTb state and enter the InSv state.
Page 410: Utr Diagnostic
9-46 Trouble isolation and correction This diagnostic provides the SMS with both InSv and OOS diagnostics. This diagnostic also provides the SMS with a CMR audit. The CMR audit activates the InSv diagnostic on a normal base. The feature provides a diagnostic interface to report CMR failures.
Page 411: Xpm Diagnostic History
Trouble isolation and correction 9-47 the continuity circuit. The diagnostic uses the following components for the SMS hardware: the NT6X92 UTR card the NT6X44 time switch card the NT6X69 message card the NT6X85 DS-1 interface card the speech bus XPM diagnostic history The Extended Peripheral Module diagnostics history, feature number AF5006, provides a resident database to record selected diagnostic results of XPMs.
Page 412 9-48 Trouble isolation and correction Operating company personnel analysis Feature AF5006 provides data on the failure history of diagnostics. This data is in the form of the number of failures that occur and the cards that are at fault. The commands display data for an XPM or for all XPMs that this feature supports.
Page 413 Trouble isolation and correction 9-49 Note: Feature AF5006 records cards an XPM implicates and not cards that the CM generates. Diagnostics can be grouped together and run as a set of diagnostics or run as a single test. The following list is a list of defined sets: the InSv tests the OOS tests facility audit tests...
Page 414 9-50 Trouble isolation and correction (both). The table also identifies diagnostics that the SWACT controller requires. Diagnostics supported Required by SWACT Diagnostic Description Type controller name AB DIAG A/B bits solicited CMRDIAG CMR card both CSMDIAG CSM diag solicited CS SPCH Network links solicited DS1DIAG...
Page 415 Trouble isolation and correction 9-51 The following table lists the cards that this feature supports: Supported cards Card name Description NT6X40 Indicates Net interface link NT6X41 Indicates Speech bus formatter and clock NT6X42 Indicates CSM NT6X44 Indicates Time switch and A/B bit logic NTMX77 Indicates UP processor...
Page 416 9-52 Trouble isolation and correction A single test failure can report one or more diagnostic failures and zero or more cards that are defective. A diagnostic can run in one unit to report cards in that unit and the mate unit. When a diagnostic fails, the separate diagnostic routine sends the failure information to the history database.
Page 417: Diagnostic Tests For Lines
Trouble isolation and correction 9-53 — the time when the last diagnostic failure occurred on unit 1 Short term counters are reset (set to zero) inside on a unit base when a unit correctly gains activity. This gain of activity can happen as a result of an command.
Page 418: Loop Detector
9-54 Trouble isolation and correction Loop detector The loop detector test checks the capability of the line circuit to detect off-hook or on-hook conditions. The loop detector test runs as part of test setup. The SMS sends an A- and B-bit pattern that causes the RCS to apply an absorb termination.
Page 419: Coin Collect And Coin Return
Trouble isolation and correction 9-55 With multi-party ringing, the SMS sends the RCS signals to execute a loss and ANI/coin test after the ringing test. These tests determine if the correct termination connected at the RCS. Coin collect and coin return The coin collect and coin return test checks the ability of RCS coin cards to provide coin collect and coin return functions.
Page 421: Troubleshooting Chart
10-1 Troubleshooting chart Clearing a SMS alarm The following troubleshooting chart provides operating company personnel with troubleshooting procedures for Subscriber Carrier Module-100S (SMS) alarms. More complete troubleshooting methods for the SMS are in the “Clearing an SMS alarm” section in this document. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 422 10-2 Troubleshooting chart Clearing an SMS alarm Alarm condition Possible cause Action Critical Both C-side cards have faults. Proceed as follows: Identify the SMS module in the critical state. Post the SMS module in the critical state. Identify problems with the posted SMS.
Page 423 Troubleshooting chart 10-3 Clearing an SMS alarm (continued) Alarm condition Possible cause Action Major A C-side card has faults. Proceed as follows: Silence the alarm. Identify the SMS unit in the ISTb condition. Post the SMS unit in the ISTb condition. Identify the problems with the posted SMS unit.
Page 424 10-4 Troubleshooting chart Clearing an SMS alarm (continued) Alarm condition Possible cause Action Major (continued) DS30 link has faults. Proceed as follows: Silence the alarm. Identify the SMS unit in the ISTb condition. Post the SMS unit in the ISTb condition. Identify the problems with the posted SMS unit.
Page 425: Clearing An Rcs Alarm
Troubleshooting chart 10-5 Clearing an SMS alarm (continued) Alarm condition Possible cause Action Minor Non-software cards have Proceed as follows: faults. Silence the alarm. Identify the SMS unit in the ISTb condition. Post the SMS unit in the ISTb condition. Identify the problems with the posted SMS unit.
Page 427: Advanced Troubleshooting Procedures
11-1 Advanced troubleshooting procedures Advanced trouble locating procedures Normally you busy and test a defective component. As a result of this test, a list of cards appears in the MAP terminal. The card at the top of the list is the cause of the component problem.
Page 428 11-2 Advanced troubleshooting procedures Note: The system does not lock the buffers for planned SMS outages like manual warm activity switches (SWACT) or routine exercise (REX) tests. The system does not lock the buffers for Busy (BSY) operations. The system does not lock buffers if a holding buffer is locked. The system records critical events in the SMS with the associated data during the normal operation of the SMS.
Page 429: Accessing The Data Collected
Advanced troubleshooting procedures 11-3 the footprint area and the address of the last used buffer. Maintenance personnel can use this data if the SMS cannot return to task level. If the SMS cannot return to service, the read-only memory (ROM) firmware dumps the data.
Page 430 11-4 Advanced troubleshooting procedures Data can appear if the SMS is at the ROM level. To display the data, use the command string DISPLAY MEMORY The commands the system provides as part of the PMDEBUG user interface to the SMS footprint tool appear in the following table. SMS footprint commands Command DISPLAY DATA...
Page 431 Advanced troubleshooting procedures 11-5 is the buffer number is the hex value for the specified class is the event number of the specified class DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 432 11-6 Advanced troubleshooting procedures Maintenance class output Examples of stored maintenance data follow: activity drop <000> CLASS EVENT CC TIME OF EVENT MAINTENANCE (#00) 01:13:19:12.52 Dropped Activity. Parml = SWACT_when_ready. Drop source = cc_manual. <000> CLASS EVENT CC TIME OF EVENT MAINTENANCE (#00) 01:13:19:12.52 Unit Has Received A Jam Inactive Message.
Page 433 Advanced troubleshooting procedures 11-7 operational faults Examples of stored operational fault data follow: <003> CLASS EVENT CC TIME OF EVENT MAINTENANCE (#00) 01:13:19:12.52 Operational Fault Data Continued. Rec_data 0 through 6”: #00 #00 #00 #00 #00 #00 <002> CLASS EVENT CC TIME OF EVENT MAINTENANCE (#00) 01:13:19:12.52...
Page 434 11-8 Advanced troubleshooting procedures Diagnostic class output An example of stored diagnostic data follows: <000> CLASS EVENT CC TIME OF EVENT MAINTENANCE (#02) 00:00:03:20.84 Diag_id = did_tone_diag{#B5} – Tone Diagnostic. Loc_msw = #0011. Loc_lsw = #001F. Expected = #48. Received = #41. Qualifier = #12.
Page 435: Limits
Advanced troubleshooting procedures 11-9 Diagnostics results graph output An example of the diagnostics results graph display output follows: <001> CLASS EVENT CC TIME OF EVENT DIAG GRAPH (#0F) 00:00:06:34:58 Diag_id =did_cmr_diag(#7) – CMR Card Diagnostics. res_num=FF(P=Pass,F=Fail,N=Not Run|Test Undefined,O=Other) Diag Results Graph: P F N N N N N N N N N N N N N N N N N N Limits The system loses the data the SMS footprint facility collects under the following conditions:...
Page 436: Powering Down Sms
11-10 Advanced troubleshooting procedures a. Repeat steps 2 and 3 for the other SMS unit. b. Busy both SMS units. 4 List the PM LOADS at the input-output device. List the specified PM LOADS in use to RTS the units. Normally, you complete this step during the power-up procedure.
Page 437 Advanced troubleshooting procedures 11-11 6 Enter the network level and busy the port assigned to the link or links. Step 4 notes this port. >NET >LINKS pair where pair is the network #) >BSY plane link 7 Reenter the PM level and POST the SMS that step 2 notes. >TRNSL C Note the state of the busy link.
Page 439: Sms Routine Maintenance Procedures
12-1 SMS routine maintenance procedures This section contains routine procedures for the Subscriber Carrier Module-100S (SMS). These procedures cover preventive tasks that maintenance engineering and field maintenance personnel must perform at normal intervals. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 440 12-2 12-2 Routine maintenance procedures 12-2 Inspecting cooling unit filters Inspecting cooling unit filters Application Use this procedure to inspect cooling unit filters in frame cooling units. Interval Perform this procedure in two week intervals. Common procedures There are no common procedures. Action This procedure contains a summary flowchart and a list of steps.
Page 441: Inspecting Cooling Unit Filters Sms
Routine maintenance procedures 12-3 Inspecting cooling unit filters (continued) Summary of Inspecting cooling unit filters This flowchart summarizes the procedure. Set FAN Use the instructions that follow ALARM this flowchart to perform the OVERRIDE on procedure. Remove air intake grill and filter Clean grill Clean or...
Page 442 12-4 Routine maintenance procedures Inspecting cooling unit filters (continued) Inspecting cooling unit filters At your current location DANGER Rotating fan blades Do not reach in more than 6 in. beyond the upper lip of the air-intake grill. If you reach in more than 6 in., your fingers can touch the rotating blades of the cooling unit fans.
Page 443 Routine maintenance procedures 12-5 Inspecting cooling unit filters (continued) Shine a trouble light through the filter. If light is visible through the filter step 7 is not visible through the filter step 9 Install the filter in the grill again. Install the filter again and grill assembly in the frame.
Page 444 12-6 Routine maintenance procedures Inspecting cooling unit filters Inspecting cooling unit filters (continued) (end) Install the filter and grill on the frame. Go to step 19. On the front of the FSP, set the FAN ALARM OVERRIDE switch to OFF. The procedure is complete.
Page 445: Replacing Cooling Unit Filters Sms
12-7 Routine maintenance procedures 12-7 12-7 Replacing cooling unit filters Replacing cooling unit filters Application Use this procedure to replace cooling unit filters in frame cooling units. Interval Perform this procedure at intervals of three months. Common procedures There are no common procedures. Action This procedure contains a summary flowchart and a list of steps.
Page 446 12-8 Routine maintenance procedures Replacing cooling unit filters (continued) Summary of Replacing cooling unit filters This flowchart summarizes the procedure. Use the instructions that follow Set FAN this flowchart to perform the ALARM procedure. OVERRIDE on Remove air intake grill and filter Replace filter Reinstall grill...
Page 447 Routine maintenance procedures 12-9 Replacing cooling unit filters Replacing cooling unit filters (continued) (end) Replacing cooling unit filters At your Current Location DANGER Rotating fan blades Do not reach in more than 6 in. beyond the upper lip of the air-intake grill. If you reach beyond 6 in., your fingers can contact the rotating blades of the cooling unit fans.
Page 448: Testing The Dead System Alarm Sms
12-10 12-10 Routine maintenance procedures 12-10 Testing the dead system alarm Testing the dead system alarm Application Use this procedure to verify that the dead system alarm is operating correctly. Interval Perform this procedure monthly. Common procedures There are no common procedures Action This procedure contains a summary flowchart and a list of steps.
Page 449 Routine maintenance procedures 12-11 Testing the dead system alarm (continued) Summary of Testing the dead system This flowchart summarizes the procedure. Access EXT level of the MAP Use the instructions that follow display this flowchart to perform the procedure. Test MTM dead system alarm List the alarms Observe MAP...
Page 450 12-12 Routine maintenance procedures Testing the dead system alarm (continued) Summary Testing the dead system alarm Type SETSD SDOC3CUTOFF Test OAU dead system alarm List the alarms Observe MAP responses, audible alarms, and ACD lamps Did critical Did critical Did ABOAUFL Did MAP &...
Page 451 Routine maintenance procedures 12-13 Testing the dead system alarm (continued) Testing the dead system alarm At your Current Location In offices equipped with NT0X63 alarm control and display panels (ACD), ensure that the AUDIBLE ALARM DISABLE switch is set downward. To access the EXT level of the MAP screen, type >MAPCI;MTC;EXT and press the Enter key.
Page 452 12-14 Routine maintenance procedures Testing the dead system alarm (continued) To access system table ALMSD, type >TABLE ALMSD and press the Enter key. To position on the field bearing the name of the SD group, type >POS sd_group and press the Enter key. where sd_group is the SD group name identified in step 5 To list the table, type...
Page 453 Routine maintenance procedures 12-15 Testing the dead system alarm (continued) Replace the card. Return to step 1 of this procedure. To respond to the warning, type >SETSD SDOC3CUTOFF OP and press the Enter key. To test the dead system alarm, type >TSTDSALM OAUFAIL 12 and press the Enter key.
Page 454 12-16 Routine maintenance procedures Testing the dead system alarm Testing the dead system alarm (continued) (end) It is possible that you missed an indication. Return to step 1 and repeat this procedure. The dead system alarm is correct. The procedure is complete. 297-8231-550 Standard 09.01 August 1998...
Page 455: Testing Power Converter Voltages Sms
12-17 Routine maintenance procedures 12-17 12-17 Testing power converter voltages Testing power converter voltages Application Use this procedure to test power converter voltages for all power converters in the subscriber carrier equipment (SME) frame. Interval Perform this procedure every six months. Common procedures There are no common procedures Action...
Page 456 12-18 Routine maintenance procedures Testing power converter voltages (continued) Summary of Testing power converter voltages This flowchart summarizes the procedure. Use the instructions that follow this flowchart to perform the Obtain dc procedure. voltmeter Measure voltages at face plate test points Are voltages End of within 2 % of face...
Page 457 Routine maintenance procedures 12-19 Testing power converter voltages Testing power converter voltages (continued) (end) Testing power converter voltages At your Current Location Obtain a dc voltmeter. Measure the voltage at the test points on the faceplates of all NT2X70 power converters in the SME frame.
Page 458: Returning A Card For Repair Or Replacement Sms
Returning a card for repair or replacement Application Use this procedure to return a circuit card, like a power converter, to Nortel for repair or replacement. Your location, Canada or the United States, determines the documents you must complete. Your location determines to which address you must return the card.
Page 459 Routine maintenance procedures 12-21 Returning a card for repair or replacement (continued) Summary of Returning a card for repair or replacement This flowchart summarizes the procedure. Place card in Use the instructions that follow ESD protective this flowchart to perform the procedure.
Page 460 Fill in the return label for each card that you return. For additional help to fill out the label, call 1-800-347-4850. Pack the card or assembly in a Nortel card shipping carton and seal the carton. If a Nortel shipping carton is not available, use another carton. Make sure you...
Page 461 Attach one copy of the card label of to a card latch. Keep the other copies of the label for your records. Pack the card or assembly in a Nortel shipping carton and seal the carton. If a Nortel shipping carton is not available, use another carton. Make sure that...
Page 462: Testing Wrist Strap Grounding Cords Sms
12-24 12-24 Routine maintenance procedures 12-24 Testing wrist strap grounding cords Testing wrist strap grounding cords Application Use this procedure to verify wrist strap grounding cord resistance. The resistance must be low enough to allow static electricity to discharge from the person.
Page 463 Routine maintenance procedures 12-25 Testing wrist strap grounding cords (continued) Summary of Testing wrist strap grounding cords This flowchart summarizes the procedure. Obtain Use the instructions that follow ohmmeter this flowchart to perform the procedure. Detach cord from wrist strap Measure resistance between ends...
Page 464 12-26 Routine maintenance procedures Testing wrist strap grounding cords (continued) Testing wrist strap grounding cords At your current location Obtain an ohmmeter. Detach the grounding cord from the wrist strap. Measure the resistance between opposite ends of the grounding cord with the ohmmeter.
Page 465 Routine maintenance procedures 12-27 Testing wrist strap grounding cords Testing wrist strap grounding cords (continued) (end) The procedure is complete. DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 467 A --3 A - Appendix SMS unequipped lines troubleshooting This section provides the user with the necessary information and tools to verify if the SMS lines in the Line Maintenance Busy (LMB) state are in that state because of a valid unequipped line condition in the Mode 1 SLC-96. Note: In order to use the troubleshooting steps provided in this document, the user must have access to the PMDEBUG utility.
Page 468 A --4 Appendix Each shelf in the RT can have a maximum of 24 lines installed. Since the DS-1 link has 24 DS0 timeslots, there is a one-to-one association between physical line location and a DS0 timeslot. This association between line association and DS0 timeslot is as follows: Table 1 DS0 to SLC Line Circuit Translation SLC-96 Line Circuit to DMS LEN and DS0 Timeslot Translation...
Page 469 Appendix A --5 Troubleshooting Walk-through This section is made up of a walk-through of the process for determining the status of unequipped SMS lines. Post up the line in question. This procedure uses the first two lines off the SLC-96. The following displays shows the data for a line in the IDLE state. >...
Page 470 A --6 Appendix -------------------------------------------------------------- LEN: ERCS 00 0 00 01 TYPE: SINGLE PARTY LINE SNPA: 619 DIRECTORY NUMBER: 5161212 LINE CLASS CODE: OWT ** SIGNALLING TYPE: DIGITONE LINE TREATMENT GROUP: LINE ATTRIBUTE INDEX: CARDCODE: SCD203 GND: N PADGRP: STDLN BNV: NL MNO: N PM NODE NUMBER PM TERMINAL NUMBER : OPTIONS:...
Page 471 Appendix A --7 We now go through the CHNLS, PROT, and NODE levels and dump out the node table information in the SMS. This is required in order to get the internal RT number that the SMS associates with the particular SLC-96 with which we are working.
Page 472 A --8 Appendix line indicated that our line was on node number 235. If we find the entry for Node 235, we see that it is Internal code number 2 in the table, external code number 235, and its RCT number is 0. In order to get the RT index number for this SMS, we must add 1 to the RCT number.
Page 473 Appendix A --9 0. We also know from our line to DS0 associated that line 0 signaling information should be in timeslot (chnl) 0 and that line 1 signaling information should be in chnl 2 location. Reference Table 1). Both lines are reporting onhook, which is expected for an IDLE equipped line.
Page 474 A --10 Appendix mode: scan off-hook flash option: false timer blk not attached Chnl blk, Image, port Map, Bits, sAn, Digit, Outg, Uneq scan, * UP:SMSS> * A/bdata, Ddldata, Tsw, Psport, Rtstat, psW, Cmb, Mtc, aLms, * UP:SMSS> * LTCUP> quit NOTE: PMDEBUG will terminate when last request is complete PMDEBUG TERMINATES We have now removed the first line card in the A shelf of the SLC-96.
Page 475 Appendix A --11 WARNING: You now have access to the PM monitor...proceed with caution LTCUP> TIme,TAsk,Load,Xprompt,CHEaptmr,DAtadump,Uspace,Debug,BPMonito r,Swerr,C++monitor,Ipc,Verreg,Patches,Flq,Msg6x69,UArtimc,Newm sging,NWmsgtrc,MSGTr,Chnls,CDm,DYnamic,MTc,Rcvrmon,SChnls,CSm, DS1,CMr,UTr,OMUnsol,DIagnose,IMage,Audit,MAtediag,CAudit,PRfm, PErcall,Bigfoot,PARaudt,CP,CNd,Trmtrc,SMsm,SMSS,LTst. From the SMsm level, we now dump the line config status. We now see that the first two lines of the A shelf are set to a value of 0. This indicates that the lines are not equipped in the SLC-96.
Page 476 A --12 Appendix A/bdata, Ddldata, Tsw, Psport, Rtstat, psW, Cmb, Mtc, aLms, * UP:SMSS> a Chnl blk, Image, port Map, Bits, sAn, Digit, Outg, Uneq scan, * UP:SMSS> b 0 Chnl 00 unequiped Chnl 0C on hook Chnl 01 on hook Chnl 0D unequipped Chnl 02...
Page 477 Appendix A --13 number). The SMS does not tie up resources scanning lines that cannot make telephone calls. UP:SMSS> c 0 d mode: no scan flash option: false timer blk not attached LTCUP> quit NOTE: PMDEBUG will terminate when last request is complete PMDEBUG TERMINATES We now insert the first line card into the A-shelf of the SLC-96.
Page 478 A --14 Appendix CKT TYPE STATE FAIL EqPEC ============================================================== ERCS 00 0 00 00 619 351 1234 IDL SCD203 Number of entities in the posted set: 1 > post l ercs 0 0 0 1 print CKT TYPE STATE FAIL EqPEC ============================================================== ERCS 00 0 00 01...
Page 479 Appendix A --15 SHELF SLOTS: 1| 2| 3| 4| 5| 6| 7| 8| 9| A| B| C| 10|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| Value of 0 = unequipped line, Value of 1 = equipped line Rt config, All chnl bsy, pWrk trc, aBbt, Set ln config Disp ln config status, disp ln config Image cHnl aud, send Cfield msg, Line, sMsr, * UP:SMsm>...
Page 480 A --16 Appendix Dumping the scan information for both lines now indicates that we are scanning for the offhook condition.l If the line were actually unequipped, then we would be scanning for the “onhook from unequip” condition. This condition would definitely indicate that the SMS is not reporting a valid unequipped line.
Page 481 Appendix A --17 SHELF SLOTS: 1| 2| 3| 4| 5| 6| 7| 8| 9| A| B| C| 10|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| Value of 0 = unequipped line, Value of 1 = equipped line Rt config, All chnl bsy, pWrk trc, aBbt, Set ln config Disp ln config status, disp ln config Image cHnl aud, send Cfield msg, Line, sMsr, * Since we know that the SMS is not receiving the unequipped AB-bit...
Page 482 A --18 Appendix SHELF SLOTS: 1| 2| 3| 4| 5| 6| 7| 8| 9| A| B| C| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| Value of 0 = unequipped line, Value of 1 = equipped line Rt config, All chnl bsy, pWrk trc, aBbt, Set ln config Disp ln config status, disp ln config Image cHnl aud, send Cfield msg, Line, sMsr, * We can verify if the audit has detected the change and sent the information to...
Page 483 Appendix A --19 SHELF SLOTS: 1| 2| 3| 4| 5| 6| 7| 8| 9| A| B| C| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| 11|11|11|11|11|11|11|11|11|11|11|11| Value of 0 = unequipped line, Value of 1 = equipped line Rt config, All chnl bsy, pWrk trc, aBbt, Set ln config Disp ln config status, disp ln config Image cHnl aud, send Cfield msg, Line, sMsr, * UP:SMsm>...
Page 484 A --20 Appendix We can get a history of what the unequipped line detection feature has reported by dumping the AUDT202 logs out of the DMS. This shows us when the line state changed from IDL to LMB and from LMB back to IDL. >...
Page 485: Index
13-1 Index sequence of events originating end 1-31 Alarm clearing terminating end 1-32 critical 6-2 setup 1-30 procedure 6-4 software modules 1-26 minor 6-20 A/B–bit facility 1-29 procedure 6-23 DDL 1-28 audits SMS maintenance task 1-30 call processing connection 1-70 TPT 1-27 CMR card 1-70 UP ringing task 1-29...
Page 486 13-2 Index A– and B– bit 9-39 static data 11-8 CMR 9-45 resets and timestamps 9-52 CSM 9-39 ROM diagnostics 9-49 DS–1 card 9-42 SWACT controller 9-47 DS–1 DDL 9-42 formatter 9-40 message 9-40 faults P–side link 9-44 clearing ring / pad card 9-42 IMC link 9-8 ROM 9-38 parity 9-8...
Page 487 Index 13-3 single–party sequence 9-30 protection link release 1-87 station 9-37 protection switching 1-85 test desk tests 9-36 protection switching enabling / disabling lines, maintenance scenarios 9-25 1-88 lines diagnostics scenarios of protection switching 1-86 automatic number identification (ANI) 9-54 functional description 1-2 channel loss 9-53 cards 1-5...
Page 488 13-4 Index warm SWACT 1-35 quick recovery 5-5 SWACT back illustration 1-40 Remote concentrator SLC–96 (RCS), alarm clearing maintenance overview, escalation to manual mainte- 10-5 nance, manually busy switched links 1-89 remote concentrator SLC–96 (RCS), module 2-5 manual maintenance 1-85 mode I 2-5 manually busy switched links 1-89 mode II 2-5...
Page 489 Index 13-5 troubleshooting 9-3 warm 1-33 advanced 11-1 SWACT (switch of activity), illustration 1-39 troubleshooting chart 10-1 system REX (SREX) scheduler 1-47 SWACT audits 1-71 SWACT back 1-35 Universal tone receiver (UTR) 3-11 DMS-100 Family SMS Maintenance Manual XPM10 and up...
Page 492 DMS-100 Family Subscriber Carrier Module-100S Maintenance Manual Product Documentation—Dept 3423 Northern Telecom P.O. Box 13010 RTP, NC 27709–3010 1-877-662-5669, Option 4 + 1 1994, 1995, 1996, 1997, 1998 Northern Telecom All rights reserved NORTHERN TELECOM CONFIDENTIAL: information contained in this document is the property of Northern Telecom.

Nortel DMS-100 Series Maintenance Manual

Quick Links

Troubleshooting

Related Manuals for Nortel DMS-100 Series

Summary of Contents for Nortel DMS-100 Series

Table of Contents