Nortel Spectrum Peripheral Module Quick Reference Guide |
Spectrum Peripheral Module Overview
The DMS-Spectrum Peripheral Module (SPM) is functionally equivalent to a Digital Trunk Controller (DTC) for interswitch trunks. It provides Common Channel Signaling #7 (CCS7) and Per-Trunk Signaling (PTS) speech and data trunks on TR-782 compliant OC-3 carriers. Internally, all trunks are treated as DS-0s or as sets of DS-0s.
The SPM is a set of information-processing modules that provide telecommunications switches with direct access to Optical Carrier (OC) networks. The basic mechanical element of the SPM consists of a dual-shelf assembly that is mounted to a common backplane. A shelf assembly contains two identical shelves. Each shelf can contain up to 15 information-processing modules that plug into the backplane. The backplane provides the electrical interconnection between the modules. The modules contain circuit packs that perform a variety of functions from supplying electrical power to providing optical connections to a high-speed transport network. SPM modules also provide some call-processing and high-speed carrier capabilities. In addition to the SPM used for call processing on the DMS switch, which is the focus of this Quick Reference Guide, there are two additional types of SPMs classes.
Spectrum Peripheral Module Architecture
The DMS Call Processing Class SPM and the DTC within the DMS Switching Architecture

Spectrum Peripheral Module to Enhanced Network Connectivity
Note: Each SPM Common Equipment Module (CEM) card has four DS-512 ports which are cabled via fiber straight from the front of the CEM cards to ENET planes using NT9X40DA Paddleboards. Then from the ENET via existing DS-512 fibers to the Message Switch (MS).
Connectivity Notes for Enhanced Network and Message Switch
----------------------------------------------------------------------- MS 0 slot 6 ENET PL 0 Sh 0 | MS 1 slot 6 ENET PL 0 Sh 0 MS 0 slot 7 ENET PL 0 Sh 1 | MS 1 slot 7 ENET PL 0 Sh 1 MS 0 slot 8 ENET PL 1 Sh 0 | MS 1 slot 8 ENET PL 1 Sh 0 MS 0 slot 9 ENET PL 1 Sh 1 | MS 1 slot 9 ENET PL 1 Sh 1 -----------------------------------------------------------------------
Various Links of a DMS Call Processing Spectrum Peripheral Module

Various Links of an Interworking Spectrum Peripheral Module

SPM Hardware
NTLX91BA Frame Layout for a 4-Slot High-Speed Backplane
Note: The NTLX91BA frame allows for ATM when it is available.

Note: For a description of the alarm indicators for the frame and Resource Modules (RM), see the "LED Alarm Indicators" section, or see NTP 297-1771-550, SPM Hardware Maintenance Reference Manual.
Spectrum Peripheral Module Frame Components
----------------------------------------------------------------------------------------- SPM Frame Components Frame Hardware Item Product Engineering Code ----------------------------------------------------------------------------------------- SPM Shelf Assembly NTLX51XX 2 per SPM frame AA = 2 high-speed slots BA = 4 high-speed slots ----------------------------------------------------------------------------------------- SPM Backplane Assembly NTLX52XX XX = 01 for 2 high-speed slots XX = 11 for 4 high-speed slots ----------------------------------------------------------------------------------------- SPM Mechanical Assembly NTLX5101 1 per shelf ----------------------------------------------------------------------------------------- Cooling Unit Assembly NTLX55XX 2 per frame ----------------------------------------------------------------------------------------- Fan Assembly Unit NTLX56XX 4 per cooling unit ----------------------------------------------------------------------------------------- Air Filter Assembly NTLX5015 2 per frame ----------------------------------------------------------------------------------------- Air Filter Tray Assembly NTLX5016 1 per shelf ----------------------------------------------------------------------------------------- Power Cabling Interface Unit NTLX57XX 1 PCIU per SPM frame Contains the following: Alarm Card Assembly NTLX58XX 1 per PCIU Fan Management Unit Assembly NTLX59XX 2 per PCIU ----------------------------------------------------------------------------------------- Upper Grill Assembly NTLX5010 1 per frame ----------------------------------------------------------------------------------------- Lower Grill Assembly NTLX5011 1 per frame ----------------------------------------------------------------------------------------- -End-
Spectrum Peripheral Module Diagram
Note: Configuration shown is for a NTLX51BA four high-speed slot SPM.

Note: SPM module with two shelves can provide up to 26 Resource Modules (RM) in addition to the required Common Equipment Module (CEM) and Shelf Interface Module (SIM) circuit packs.
Note: Each Serial Link (SL) has 256 timeslots. Where three SLs are assigned, there are 768 timeslots that can service the bandwidth equivalent to one STS-1 or DS-3 Resource Module. Note: Serial links in diagram above are shown as 1-S, 3-S, and 9-S.
Note: Slots 1 & 2 and 9 & 10 of shelf 0 have nine S-links or 2,304 timeslots that supports OC-3 or ATM RMs to provide 2,016 circuits.
Note: Prior to SP14, if you plan on implementing ISDN User Part (ISUP) trunking, you must have Link Interface Units SS7 (LIU7) datafilled and configured for external routing. See NTP 297-8991-030, LIU7 External Routing Activation User Guide.
-----------------------------------------------------------------------------------------
SPM Module Diagram Description
Card Description
-----------------------------------------------------------------------------------------
LX57 PCIU Card
-----------------------------------------------------------------------------------------
LX58 Alarm Card
-----------------------------------------------------------------------------------------
LX59 Fan Card
-----------------------------------------------------------------------------------------
LX60 Filler Pack
-----------------------------------------------------------------------------------------
LX5015 Air Filter
-----------------------------------------------------------------------------------------
LX61 SIM (Power Distribution & Alarms) is located in slot 15 of each shelf.
-----------------------------------------------------------------------------------------
LX63 CEM is located in slots 7 & 8 of bottom shelf.
Note: The LX63 CEM is discontinued but is still supported. The LX82 CEMs are
required for Crossover Messaging functionality and Succession Evolution of SPMs.
-----------------------------------------------------------------------------------------
LX82 Enhanced CEM with Ethernet is located in slots 7 & 8 of the bottom shelf.
-----------------------------------------------------------------------------------------
9X40DA ENET Paddle Board connected to front of CEMs.
-----------------------------------------------------------------------------------------
Resource Module & Provisioning Information
-----------------------------------------------------------------------------------------
LX65 Digital Signal Processor (DSP)
Resources: MF, COT, ABBIT, TONESYN. A DSP has 9 islands.
-----------------------------------------------------------------------------------------
LX66 Voice Signal Processor (VSP)
Echo Cancelling (ECAN)
A VSP has 10 islands and up to 26 ECANs per island.
Note: LX65 DSP and LX66 VSP packs go in slots 3 thru 6 and 11 thru 14 of the
bottom shelf and/or slots 3 thru 6 and 9 thru 14 of the top shelf.
(Need three S-links per shelf).
Note: You can mix DSPs, DLCs, and VSPs within the same SPM; however,
make sure the datafill is correct in table MNCKTPAK.
-----------------------------------------------------------------------------------------
LX71 OC-3 Interface Module (OC-3 Transmit & Receive) for TDM (traditional
trunking) packs go in slots 9 & 10 of bottom shelf.
-----------------------------------------------------------------------------------------
LX72 DLC packs for supporting ISDN PRI D-Channel should go in slots 1, 2, 7, & 8
of the top shelf since they only need one S-link per slot.
Note: DLCs can go in other than slots with one S-link, but that would be
wasting S-links.
-----------------------------------------------------------------------------------------
LX73 ATM Interface Module packs go in bottom shelf slots 1 & 2 for the MG4K
(MG4000) SPM configuration, and 9 & 10 of the bottom shelf for the IW SPM.
The ATM pack needs nine S-links per slot.
-----------------------------------------------------------------------------------------
LX74 Synchronous Transport Signal-1 (STS-1) Interface Module
-----------------------------------------------------------------------------------------
LX84AA PCM-30 Low-Speed Access (LSA)
-----------------------------------------------------------------------------------------
LX84DA DS-1 LSA
-----------------------------------------------------------------------------------------
LX85/86 Voice Signal Processor (VSP) (i.e. echo cancellation)
-----------------------------------------------------------------------------------------
LX99 Synchronous Transport Mode-1 (STM-1) Interface Module
-----------------------------------------------------------------------------------------
-End-
Spectrum Peripheral Module Tables
Several new tables have been added for configuring SPMs. Except for the need to datafill table TRKMEM (Trunk Member) after SPM table MNHSCARR, and table TRKSGRP (Trunk Sub-Group) after SPM table MNRIIID for Primary Rate Interface (PRI), datafill the existing tables CLLI (Common Language Location Indentifier), PECINV (PEC Inventory), CLLIMTCE (CLLI Maintenance), and TRKGRP (Trunk Group) for trunking, and table ENCDINV (Enhanced Network Card Inventory) for hooking it up to the ENET, the following new SPM tables must be datafilled in the following order:

Note: Use >MAPCI;MTC;PM;POST SPM (spm #);TRNSL (trn #) to get the same information.
-------------------------------------------------------------------------- DS-1P Line Encoding Parameters in Table MNHSCARR FRAMEFMT DS1ZCS Equivalent To -------------------------------------------------------------------------- ESF OFF B8ZS / 64 kbs ESF ON Does Not Exist SF OFF B8ZS / 56 kbs SF ON AMI / 56 kbs --------------------------------------------------------------------------
Spectrum Peripheral Module MAP Level Commands
The CARRIER level has been modified to permit posting of new class carriers which include OC-3S and STS-3L physical carriers and the STS-1P, DS-3P, VT-15P, and DS-1P logical carriers.
See the SPMTKCNV level off the TTP level for the commands relating to moving existing trunks from DTCs to SPMs. Reference NTP 297-1771-819, SPM Commands Reference Manual for command details.
Spectrum Peripheral Module "PM" MAP Level

Spectrum Peripheral Module "SELECT" MAP Level

Spectrum Peripheral Module Tools & Command Interpreter Level Commands
Note: See SPM Tools Reference Manual, NTP 297-1771-120 and SPM Commands Reference Manual, NTP 297-1771-819 for more details on commands and tools.
REMLOGIN to the Spectrum Peripheral Module
The SPM can be accessed through Remote Login (REMLOGIN). Most REMLOGIN commands and some directories are currently password protected. The Debug Shell (dSH) provides access to the commands and directories on the SPM. The following example is for a remote login into SPM module 0, shelf 0 debug shell, and then within the debug shell, into the OC-3 in logical slot 9:
At the Command Interpreter (CI) level enter:
>REMLOGIN SPM 0 0 # Logs into SPM debug shell (/DSHELL directory) and the
SPM CEM in slot 7 (dSH:7).
dSH:7>REMLOGIN -S 9 # Accesses the OC-3 in logical slot 9 (-S 9) from the
SPM CEM in slot 7 (dSH:7).
Other helpful commands after remotely logging into an SPM:
>SWNODE or dSH:7>SWNODE # Use this command to switch between CI and REMLOGIN session.
dSH:7>CD /<dir> # Use CD command to change directories.
dSH:7>LS # Use LS command to get a list of directory commands.
dSH:7>CD /CARM
dSH:7>CALS # Use the CALS command (SP15) in the CARM directory to list the
status of all carriers.
# Note: Password protection is removed after SP15 for access
to the CALS command.
The following are some examples of directory levels that can be accessed by using the CD /<dir> command. Once in the directory level, use the LS command to see directory level commands. Use HELP <command> and HELP <dir> for descriptions.
PERFMON (Performance Monitoring) Level
The Performance Monitoring (PERFMON) level of the MAP terminal provides access to Synchronous Optical Network (SONET) GR-253 compliant performance monitoring. To access the PERFMON level, use one of the following commands:
>MAPCI;MTC;TRKS;CARRIER;POST SPM (spm #);PERFMON (carrier #) >MAPCI;MTC;TRKS;CARRIER;POST SPM (spm #) (circuit #);PERFMON 0
The METERPP command off the PERFMON level is used to set the benchmark reading for Optical Power Receiver (OPR) and stores it in memory. This benchmark reading is then used by the SPM to calculate the optical receive levels. The METERPP does not do any signal attenuation measurements. If the OC-3S facilities are not setup during installation, the operating company may have to perform this.
The PPQUERY command off the PERFMON level displays the current 24-hour performance parameter counts, the 15-minute performance parameter, and the 24-hour performance parameter thresholds.
SPM Software Verification Notes
Note 1. For offices with NA010, the only way to find out what load is in a specific SPM resource module is to REMLOGIN to it and use the Query Load (QLOAD) command.
Note 2. For NA011 and above, the QUERYPM FILES command is available and will provide SPM resource module load information (i.e. >MAPCI NODISP;MTC;PM;POST SPM (spm #);QUERYPM FILES).
Note 3. Table PMLOADS will provide the software name (ACTFILE) and volume name (ACTVOL). Table MNCKTPAK provides the software load version for each resource module in a SPM (i.e. DSP0014 is software load version SP14).
Note 4. SPM loadname convention can have up to three values. Example: SP14.1.2 is software version SP14, maintenance release version 1, and emergency release version 2. The latest SPM loads on disk can be queried to get release and version information. This can be obtained by entering DISKUT, listing the SPM loads to get them in the user directory (i.e. >LF S00DIMAGE), and then use command >SPMLFINFO (loadname) (i.e. >SPMLFINFO DSP0013_010056).
SPM and Related Log Messages
Local SPM logs can be obtained by remote logging into the CEM and then by dumping error buffers using the /AER directory. Resource module log buffers can be dumped by remotely logging into them.
-----------------------------------------------------------------------------------------
SPM Log Messages
Log Description
-----------------------------------------------------------------------------------------
SPM300 Generated when a device fault occurs.
Note: Provides an ordered card list.
-----------------------------------------------------------------------------------------
SPM301 Generated when the clock oscillator tuning range reaches 70% and again when it
reaches 90%.
-----------------------------------------------------------------------------------------
SPM310 This log is generated by SPMECMON in automatic performance monitoring mode and
if SOS message reporting is enabled when an echo cancellation performance issue
is suspected.
Note: Data contained in this log can be compiled to detect potential echo
cancellation or network problems.
-----------------------------------------------------------------------------------------
SPM311 Software Exception Report (SWER) occurs on a SPM.
-----------------------------------------------------------------------------------------
SPM312 Generated when a trap occurs on a SPM.
-----------------------------------------------------------------------------------------
SPM313 A fault is recorded in the Module Information Memory (MIM) on a SPM.
-----------------------------------------------------------------------------------------
SPM330 Generated when the two CEMs of a SPM come in to datasync or go out of datasync.
-----------------------------------------------------------------------------------------
SPM331 Generated when a device has a protection switch failure.
-----------------------------------------------------------------------------------------
SPM332 Generated when the sync reference source is switched by system or manual action,
or if the last sync reference source in an OC-3 protection group is lost.
-----------------------------------------------------------------------------------------
SPM334 An alternate sync reference source is not available & timing source no longer
meets SONET spec.
-----------------------------------------------------------------------------------------
SPM335 Generated when a device has a protection switch failure.
-----------------------------------------------------------------------------------------
SPM340 Generated when the CM SWACTs and the CEM EXEC updates fail.
-----------------------------------------------------------------------------------------
SPM350 Generated as a warning that specific SPM node resources are near exhaust.
-----------------------------------------------------------------------------------------
SPM500 Generated when a device changes state.
-----------------------------------------------------------------------------------------
SPM501 Generated when the clock mode changes from sync, freerun, holdover, or acquire to
sync, freerun, holdover, or acquire. Alarm severity is provisioned.
Note: This log is not generated when the clock mode changes from synchronization
to holdover. See log SPM332 for more information.
-----------------------------------------------------------------------------------------
SPM502 ATM Connection State Change Log
-----------------------------------------------------------------------------------------
SPM503 ATM Connections OOS State Change Log
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
SPM504 ATM Connections RM Device OOS State Change Log
-----------------------------------------------------------------------------------------
SPM600 Generated when the MS changes modes and is not able to notify the in-service SPM
of the mode change.
-----------------------------------------------------------------------------------------
SPM630 Generated when a successful sparing event occurs.
-----------------------------------------------------------------------------------------
SPM650 Successful loading operation.
-----------------------------------------------------------------------------------------
SPM651 Generated when an in-service CEM loading or RM loading operation fails on a
circuit pack.
-----------------------------------------------------------------------------------------
SPM650 Generated when in-service CEM loading or RM loading operation passes on a
circuit pack.
-----------------------------------------------------------------------------------------
SPM660 Generated each time a SPMECMON continuous monitored trunk is involved in an
echo canceller enabled answered call. Echo cancellation performance information
such as ERL, ERLE, etc. is provided.
-----------------------------------------------------------------------------------------
SPM661 Indicates successful completion of a SPMECMON ON or OFF command.
-----------------------------------------------------------------------------------------
SPM700 Generated when a Distributed Data Manager (DDM) audit failure occurs on a SPM
subgroup.
-----------------------------------------------------------------------------------------
SPM701 Generated when a DDM audit succeeds a SPM subgroup.
-----------------------------------------------------------------------------------------
SPM702 Generated when a DDM dynamic update fails on a SPM subgroup.
-----------------------------------------------------------------------------------------
SPM703 DDM audit successfully updates a SPM subgroup following a DDM dynamic update
failure.
-----------------------------------------------------------------------------------------
SPM704 Generated when a DDM dynamic update fails for a SPM trunk member.
-----------------------------------------------------------------------------------------
SPM705 Generated when a SPM trunk is set to LO or SYSB.
-----------------------------------------------------------------------------------------
SPM706 Generated when a trunk is automatically returned to service after being in LO.
-----------------------------------------------------------------------------------------
SPM707 Generated when the dynamic update fails for the ISDNPARM table.
-----------------------------------------------------------------------------------------
SPM708 Generated when the DDM audit updates the ISDNPARM table.
-----------------------------------------------------------------------------------------
SPM709 Generated when the dynamic update fails for the ISDNPROT table.
-----------------------------------------------------------------------------------------
SPM710 Generated when the audit updates the ISDNPROT table.
-----------------------------------------------------------------------------------------
SPRF670 Provides data from the past 15 samples of the SPM Activity (SPMACT) subtool of
SPERFORM.
-----------------------------------------------------------------------------------------
SPRF671 Provides data from the past 15 samples of the SPM Usage (SPUSAGE) subtool of
SPERFORM.
-----------------------------------------------------------------------------------------
CARR300 Generated when an OC-3 carrier failure event is cleared.
-----------------------------------------------------------------------------------------
CARR310 Generated when an OC-3 carrier failure event occurs.
-----------------------------------------------------------------------------------------
CARR500 Generated when an OC-3 carrier changes to an in-service date from MANB or SYSB.
-----------------------------------------------------------------------------------------
CARR501 Generated when an OC-3 carrier changes from SYSB or MANB to CBSY.
-----------------------------------------------------------------------------------------
CARR510 Generated when an OC-3 carrier changes from CBSY, MANB or SYSB to in-service.
-----------------------------------------------------------------------------------------
CARR511 Generated when an OC-3 carrier changes from in-service or CBSY to SYSB.
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
CARR512 Generated when an OC-3 carrier changes to CBSY from SYSB, in-service or MANB.
-----------------------------------------------------------------------------------------
CARR800 Generated when Threshold Crossing Alert (TCA) for a metered performance
parameter is cleared. Metered performance parameters include Laser Bias Count
(LBC), Optical Power Transmitted (OPT), and Optical Power Received (OPR).
-----------------------------------------------------------------------------------------
CARR810 Generated when a TCA occurs, i.e. when the metered performance parameter exceeds
its provisioned level of severity.
-----------------------------------------------------------------------------------------
CARR811 Generated when a TCA occurs for a non-metered parameter, e.g. Coding Violations
(CV), Errored Seconds (ES), and Unavailable Seconds (UAS).
-----------------------------------------------------------------------------------------
ENET211 This log is enhanced to provide DMS-SPM information.
-----------------------------------------------------------------------------------------
ENET311 Generated when a critical fault is detected on the P-side link.
-----------------------------------------------------------------------------------------
ENET308 Modified to include In-Service Trouble (ISTB) reasons for Integrated Link
Maintenance (ILM).
-----------------------------------------------------------------------------------------
PRSM400 Generated when a SPM load file (containing SPM PRSU fixes) is datafilled in
table PMLOADS.
-----------------------------------------------------------------------------------------
-End-
SPM OM Groups and Registers
In addition to the OM groups and registers provided in the table below that are directly related to the SPM, it is recommended that the following OM groups and their registers be used for performance monitoring:
To view the real-time data for the active registers directly on the SPM, use the CI level REMLOGIN command to remotely login to the SPM. Then, at the SPM, change to the directory RESMAN (>CD /RESMAN) and use the PRINTOMS command to see the active data.
-----------------------------------------------------------------------------------------
SPM OM Groups and Registers Table
OM Registers OM Groups Description
-----------------------------------------------------------------------------------------
COTLOW DSPRMAN Continuity Tone Transceiver (COT) Low-Water Threshold
Violations on SPM node from COT resource pool.
-----------------------------------------------------------------------------------------
COTLOST DSPRMAN Count of COT resources lost or taken away from resource
management users such as CallP.
-----------------------------------------------------------------------------------------
COTDENY DSPRMAN Number of COT requests denied.
-----------------------------------------------------------------------------------------
COTUTIL DSPRMAN Average percent usage of COT resources.
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
COTHI DSPRMAN High-water mark for COT resources from COT resource pool.
-----------------------------------------------------------------------------------------
COTFAIL DSPRMAN Number of COT failures for SPM based SS7 trunks.
-----------------------------------------------------------------------------------------
DTMFLOW DSPRMAN DTMF Low-Water Threshold Violations on SPM node from DTMF
resource pool.
-----------------------------------------------------------------------------------------
DTMFLOST DSPRMAN Count of DTMF resources lost or taken away from resource
management users such as CallP.
-----------------------------------------------------------------------------------------
DTMFDENY DSPRMAN Number of DTMF requests denied.
-----------------------------------------------------------------------------------------
DTMFUTIL DSPRMAN Average percent utilization of DTMF resources.
-----------------------------------------------------------------------------------------
DTMFHI DSPRMAN High-water mark for DTMF allocations from DTMF resource pool.
-----------------------------------------------------------------------------------------
TONELOW DSPRMAN TONESYN Low-Water Threshold Violations on SPM node from
TONESYN resource pool.
-----------------------------------------------------------------------------------------
TONELOST DSPRMAN Count of TONESYN resources lost or taken away from resource
management users such as CallP.
-----------------------------------------------------------------------------------------
TONEDENY DSPRMAN Number of TONESYN resource requests denied.
-----------------------------------------------------------------------------------------
TONEUTIL DSPRMAN Average percent utilization of TONESYN resources.
-----------------------------------------------------------------------------------------
TONEHI DSPRMAN High-water mark for TONESYN allocations from TONESYN resource
pool.
-----------------------------------------------------------------------------------------
MFLOW DSPRMAN MF Low-Water Threshold Violations on SPM node from MF
resource pool.
-----------------------------------------------------------------------------------------
MFLOST DSPRMAN Count of MF resources lost or taken away from resource
management users such as CallP.
-----------------------------------------------------------------------------------------
MFDENY DSPRMAN Number of MF requests denied.
-----------------------------------------------------------------------------------------
MFUTIL DSPRMAN Average percent utilization of MF resources.
-----------------------------------------------------------------------------------------
MFHI DSPRMAN High-water mark for MF allocations from MF resource pool.
-----------------------------------------------------------------------------------------
ECANLOW ECANRMAN ECAN Low-Water Threshold Violations on SPM node from ECAN
resource pool.
-----------------------------------------------------------------------------------------
ECANLOST ECANRMAN Count of ECAN resources lost or taken away from resource
management users such as CallP.
-----------------------------------------------------------------------------------------
ECANDENY ECANRMAN Number of ECAN requests denied.
-----------------------------------------------------------------------------------------
ECANFAIL ECANRMAN Number of ECAN fail to converge reported via SOS message
events.
-----------------------------------------------------------------------------------------
ECANUTIL ECANRMAN Average percent utilization of ECAN resources.
-----------------------------------------------------------------------------------------
ECANHI ECANRMAN High-water mark for ECAN allocations from ECAN resource pool.
-----------------------------------------------------------------------------------------
-End-
SPM Alarms
If your office is pre-NA011 and you have a non-node visible alarm, (such as a PROTFAIL), you must use LOGUTIL and/or DLOG/SCANLOG to locate a SPM331 log indicating the source of the alarm.
In NA011 and above offices, with core GA patch BUZ59 applied, you can list all SPMs with alarms, including the ones caused by protection switching alarms by entering:
>MAPCI NODISP;MTC;MTC;POST SPM ALL
and then entering:
>QUERYPM FLT ALL
Tables MNPRTGRP, MNCKTPAK, MNNODE, and MNHSCARR all contain alarm datafill.
SPM Alarm Quick Reference Table
The following table provides a quick reference for alarms and their associated logs and tables.
-----------------------------------------------------------------------------------------
SPM Alarm Quick Reference Table
Alarm Name Type Alarm Description and Associated Logs & Tables
-----------------------------------------------------------------------------------------
SPM Alarms Under the PM Banner (1SPM)
-----------------------------------------------------------------------------------------
CLKOOS Major Clock out-of-synchronization. See Log SPM334 and table MNCKTPAK.
-----------------------------------------------------------------------------------------
COTLOW Minor The demand for CCS7 COT resources exceeded the low-water mark
threshold setting. See log SPM350 and table MNNODE.
-----------------------------------------------------------------------------------------
DTMFLOW Minor The demand for DTMF resources exceeded the low-water mark
threshold setting. See log SPM350 and table MNNODE.
-----------------------------------------------------------------------------------------
ECANLOW Minor The demand for Echo Canceller (ECAN) resources exceeded the
low-water mark threshold setting. See log SPM350 and table MNNODE.
-----------------------------------------------------------------------------------------
HLDOVR Major The CEM clocks have lost network synchronization and are running
in Holdover (HLDOVR) mode. See log SPM501 and table MNCKTPAK.
-----------------------------------------------------------------------------------------
HLDOVR24 Major The CEM clocks are running in the holdover mode and have not been
synchronized with the network for 24-hours or more. See log
SPM501 and table MNCKTPAK.
-----------------------------------------------------------------------------------------
ISTB Minor SPM node or one or more of its devices are in an In-Service Trouble
(ISTB) state. See logs SPM300, 331, 500, 630, and ENET308.
For datafill, see tables MNCKTPAK and MNNODE.
-----------------------------------------------------------------------------------------
MANB Major The SPM node or one or more of its devices is in a Manual Busy
(MANB) state that could be affecting service. See logs SPM300,
SPM331, SPM500, SPM650, and CARR500, CARR501, CARR510, and CARR512.
For datafill related to the MANB alarm, see tables NMCKTPAK and
MNNODE.
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
MANBNA Major The SPM is in MANB state and is Not Accessible (NA), and a network
error caused it to be isolated from the ENET links or the MS ports.
A serious disruption of service exists. See log SPM600 and tables
MNCKTPAK and MNNODE.
-----------------------------------------------------------------------------------------
MFLOW Minor The demand for Multifrequency (MF) resources exceeded the low-water
mark threshold setting. See log SPM350 and tables MNCKTPAK and
MNNODE.
-----------------------------------------------------------------------------------------
NOSPARE Major The last spare module providing redundancy for an OC-3, DSP, VSP,
DLC, or ATM is not available. See logs SPM330 or SPM331 and table
MNPRTGRP.
-----------------------------------------------------------------------------------------
PROTFAIL Critical Protection (PROT) switching failed to occur on protected modules
OC-3, DSP, VSP, DLC, or ATM. See SPM300, SPM331, SPM500, or
SPM630 and table MNCKTPAK.
-----------------------------------------------------------------------------------------
SYSB Critical The SPM node or one or more of its devices is in a SYSB state that
could be affecting service. See logs NODE500, SPM300, SPM331,
SPM500, SPM650, and CARR500, CARR501, CARR510, and CARR512.
For datafill related to the SYSB alarm, see tables NMCKTPAK and
MNNODE.
-----------------------------------------------------------------------------------------
SYSBNA Critical The SPM is in SYSB state and is Not Accessible (NA), and a network
error caused it to be isolated from the ENET links or the MS ports.
A serious disruption of service exists. See log ENET311 and tables
MNCKTPAK and MNNODE.
-----------------------------------------------------------------------------------------
TONESLOW Minor The demand for Tone Synthesizer (TONESYN) resources exceeded the
low-water mark threshold setting. See log SPM350 and tables
MNCKTPAK and MNNODE.
-----------------------------------------------------------------------------------------
VCXO70 Minor The Voltage Controlled Crystal Oscillator (VCXO) has exceeded the
70% threshold of its dynamically adjustable range in order to keep
the CEM synchronized to a timing reference. See log SPM301 and
table MNCKTPAK.
-----------------------------------------------------------------------------------------
VCXO90 Minor VCXO has exceeded the 90% threshold of its dynamically adjustable
range in order to keep the CEM synchronized to a timing reference.
Synchronization failure can occur. See log SPM301 and table
MNCKTPAK.
-----------------------------------------------------------------------------------------
SPM Alarms Under the IOD Banner (2MPCOS)
-----------------------------------------------------------------------------------------
CSS-N Minor A Threshold Crossing Alert (TCA) is generated because the
Controlled Slip Seconds Near-End (CCS-N) performance parameter
has exceeded a count greater than 4. The alarm clears when the
count returns to less than 1. See log CARR811 and table MNHSCARR.
-----------------------------------------------------------------------------------------
CV-F Minor A TCA is generated because the Coding Violation Near-End (CV-N)
and Coding Violation Far-End (CV-F) has exceeded a count greater
than 4,430. The alarm clears when the count returns to 1,732 or
less. See log CARR811 and table MNHSCARR.
-----------------------------------------------------------------------------------------
ES-N ES-F Minor A TCA is generated because the Errored Seconds Near-End (ESN) and
Errored Seconds Far-End (ES-F) has exceeded daily limit of 864.
The alarm clears when the count returns to 346 or less. See log
CARR811 and table MNHSCARR.
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
SEFS-N Minor A TCA is generated because the Severely Errored Framing Seconds
Near-End (SEFS-N) has exceeded daily limit of 17. The alarm clears
when the count returns to 7 or less. See log CARR811 and table
MNHSCARR.
-----------------------------------------------------------------------------------------
SES-N SES-F Minor A TCA is generated because the Severely Errored Seconds Near-End
(SES-N) and Severely Errored Seconds Far-End (SES-F) has exceeded
daily limit datafilled in table MNHSCARR. The alarm clears when
the count returns to the low-level limit as datafilled in MNHSCARR.
See log CARR811 and table MNHSCARR.
-----------------------------------------------------------------------------------------
UAS-N UAS-F Minor A TCA is generated because the Unavailable Seconds Near-End
(UAS-N) and Unavailable Seconds Far-End (UAS-F) has exceeded daily
limit datafilled in table MNHSCARR. The alarm clears when the count
returns to the low-level limit as datafilled in MNHSCARR. See log
CARR811 and table MNHSCARR.
-----------------------------------------------------------------------------------------
SPM Alarms Under the TRKS Banner (62CG, 62GC, 62G, or 62TG)
-----------------------------------------------------------------------------------------
AIS Minor AIS alarm generated when an unbroken sequence of Alarm Indication
Signal (AIS) frames is detected for a duration of 2.5-seconds.
Alarm clears when an AIS is not detected for 10-seconds. See
logs CARR300, CARR310, and table MNHSCARR.
-----------------------------------------------------------------------------------------
BERSF Minor Bit Error Rate Signal Failure (BERSF) generated when BER exceeds
datafilled value for a duration of 2.5-seconds. Alarm clears when
BERSF value is not detected for 10-seconds. See logs CARR300,
CARR310 and the SFBERLIM field in table MNHSCARR.
-----------------------------------------------------------------------------------------
LOS Critical Loss-of-Signal (LOS) alarm is generated when pulses are not detected
for a duration of 2.5-seconds. Clears when pulses are detected for
10-seconds. See logs CARR300, CARR310 table MNHSCARR.
-----------------------------------------------------------------------------------------
BERSD Minor Bit Error Rate Signal Degradation (BERSD) generated when BER exceeds
datafilled value for a duration of 2.5-seconds. Alarm clears when
BERSF value is not detected for 10-seconds. See logs CARR300,
CARR310 and the SDBERLIM field in table MNHSCARR.
-----------------------------------------------------------------------------------------
LOP Minor Loss-of-Pointer (LOP) alarm is generated when an unbroken sequence
of frames and invalid pointers is detected for a duration of
2.5-seconds. Alarm clears when valid pointers are detected for
10-seconds. See logs CARR300, CARR310, and table MNHSCARR.
-----------------------------------------------------------------------------------------
RA1 Minor Remote Alarm Indication (RAI) alarm generated when an unbroken
sequence of frames with RAI signals is detected for a duration
of 2.5-seconds. Alarm clears when a RAI is not detected for
10-seconds. See logs CARR300, CARR310, and table MNHSCARR.
-----------------------------------------------------------------------------------------
RFI Minor Remote Failure Indication (RFI) alarm generated when an unbroken
sequence of frames with RAI signals is detected for a duration of
2.5-seconds. Alarm clears when a RFI is not detected for
10-seconds. See logs CARR300, CARR310, and table MNHSCARR.
-----------------------------------------------------------------------------------------
SIMPLEX Critical SIMPLEX alarm is generated when protection switching is unavailable.
Alarm clears when the spare RM returns to service. See logs CARR300
and CARR310 and table MNPRTGRP.
----------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------
SPM Alarms Under the CCS Banner (2RS)
-----------------------------------------------------------------------------------------
LBC-N Critical A TCA is generated because the Laser Bias Current Near-End (LBC-N)
performance parameter in the OC-3 has exceeded 150. Alarm clears
when count is less than 125. See logs CARR800, CARR810, and table
MNHSCARR.
-----------------------------------------------------------------------------------------
OPR-N Critical A TCA is generated because the Optical Power Received Near-End
(OPR-N) performance parameter in the OC-3 has dropped below 85.
Alarm clears when the parameter rises above 95. See logs
CARR800, CARR810, and table MNHSCARR.
-----------------------------------------------------------------------------------------
OPT-N Critical A TCA is generated because the Optical Power Transmitted Near-End
(OPT-N) performance parameter in the OC-3 has dropped below 85.
Alarm clears when the parameter rises above 95. See logs CARR800,
CARR810, and table MNHSCARR.
-----------------------------------------------------------------------------------------
-End-
Carrier Performance Parameters Cross Reference Table
-------------------------------------------------------------------------------------------- Carrier Performance Parameters Cross Reference Table Table MNHSCARR Performance Parameters OC-3S STS-3L STS-1P DS-3P VT-15P DS-1 -------------------------------------------------------------------------------------------- CV-N Coding Violations Near-End X X X X X X CV-F Coding Violations Far-End X ES-N Errored Seconds Near-End X X X X X X ES-F Errored Seconds Far-End X SES-N Severely Errored Seconds Near-End X X X X X X SES-F Severely Errored Seconds Far-End X UAS-N Unavailable Seconds Near-End X X X X X UAS-F Unavailable Seconds Far-End X CCS-N Controlled Slip Seconds Near-End X SEFS-N Severely Errored Frame Seconds Near-End X AISS-N Alarm Indication Signal Seconds Near-End X PSC-N Protection Switch Count Near-End X LBC-N Laser Bias Current Near-End X OPR-N Optical Power Received Near-End X OPT-N Optical Power Transmitted Near-End X -------------------------------------------------------------------------------------------- -End-
SPM Other Miscellaneous
SPM DS-512 Message Channel Reconfiguration Commands
To upgrade an existing SPM to have messaging channel crossover connections for each CEM connected either to a single-shelf ENET assembly or a dual-shelf ENET assembly, the following non-menu commands are available. The commands are listed in the order in which a user will execute them.
Table MNHSCARR Diagram
Use the below diagram to get a picture of how this table is used to identify the carriers or subcarriers terminating on the SPM. Information provided in the MNHSCARR table includes:
The P-side of the OC-3 circuit pack carries a high-speed optical carrier. With the first SPM application being OC-3, the different termination points of the SONET carrier (OC-3 section, STS-3 line, STSL path, DS-3 path, VT-15 path) and the low-speed sub-carrier (DS-1 path) will be supported.

Determining Spectrum Peripheral Module Trunk Terminal & Node Numbers
Unless you know the SPM and the and circuit numbers, locate it in table TRKMEM. Example of TRKMEM:
SRMPODNWDS0 255 0 SPM 1 98 5
In this example for trunk 255 in the SRMPODNWDS0 trunk group, 98 is the circuit number (span number) and 5 is the circuit channel number in SPM 1.
Terminal Number (TN) = (SPAN * 24) + CHANNEL (Where CHANNEL is 1 to 24)
SPM circuit numbers start at 95 which is span 0; therefore, circuit 98 in this example would be span 3. Since we now know the span is 3 and the channel is 5, we can figure the terminal number. Terminal Number is: (3 * 24 + 5) = 77
To get Node Number (NODENO), you can use the XPMIST command. Example:
>XPMIST;NODENO SPM 1
Another way to get a SPM trunk TN and NODENO is to go into TOOLSUP and turn PMIST on. Once in PMIST, use the command >CONVERT TRK SRMPODNWS0 255. The output will be in hexadecimal, so convert to decimal if needed.
DSP Island Resource Provisioning
Each DSP resource module provides a total of 9 DSP Islands (DSPIs). The resources should be allocated across the resource modules so that the DSP messaging load is evenly distributed. Only one type of resource can be provisioned per DSPI. The following table defines the capacity number for each resource:
-----------------------------------------------------------------------------------------
DSP Island Resource Provisioning
Resource Capacity* Notes and Descriptions
-----------------------------------------------------------------------------------------
COT 80 Continuity Tone Transceiver (COT)
-----------------------------------------------------------------------------------------
ToneSyn 255 It is not recommended to have more than 14 AB Bit (ABBIT)
resources (one ABBIT DSPI) on a RM that also has 255 ToneSyn
(Tone Synthesizers) resources allocated on it, since both
of these resources are messaging intensive.
-----------------------------------------------------------------------------------------
DTMF 64 DTMF receiver with dial tone generation.
-----------------------------------------------------------------------------------------
ABBIT 14 It is not recommended to have more than 28 ABBIT resources
(two ABBIT DSPIs) on the same RM.
-----------------------------------------------------------------------------------------
MF 40 Multifrequency (MF) Receiver
-----------------------------------------------------------------------------------------
STA 0 No Service Test Application (STA) resources should be
datafilled. If STA resources are currently datafilled,
they should be deleted from table MNCKTPAK based upon what
the NTP states for DSP resource allocation.
-----------------------------------------------------------------------------------------
* Note: Each of the values in this column is equal to one DSPI.
-----------------------------------------------------------------------------------------
LED Alarm Indicators
For a detailed description of the alarm LED indicators for the frame and resource modules, see NTP 297-1771-550, SPM Hardware Maintenance Reference Manual.
The following table provides a quick reference for resource module LED status and what their indication means:
-----------------------------------------------------------------------------------------
LED Alarm Indicators
LED Status Indication and Action
-----------------------------------------------------------------------------------------
GREEN OFF Green LEDs are in sleep-mode (module can also be not powered or not
RED OFF seated). When all LEDs are off, there are no critical faults and an
indicator test is not underway. Use an indicator test to check LED
function. Also, see note below on prolonging LED life.
-----------------------------------------------------------------------------------------
GREEN ON A Power On Self Test (POST) or an LED indicator test is underway.
RED ON During a POST, the LEDs are controlled by the Initial Boot Loader
(IBL) software. If both LEDs remain on for an extended period after
a POST, the module is defective. For detailed instructions for
replacement, see the appropriate NTP for card replacement procedures.
Also, see note below on prolonging LED life.
-----------------------------------------------------------------------------------------
GREEN ON Normal operation there are no critical faults and no action is required.
RED OFF Do not remove a module displaying this alarm indication or combination.
-----------------------------------------------------------------------------------------
GREEN OFF Critical fault - replace the module. For detailed instructions for
RED ON replacement, see the appropriate NTP for card replacement procedures.
----------------------------------------------------------------------------------------
AMBER OFF Normal operation all external signal inputs to the module faceplate are valid.
-----------------------------------------------------------------------------------------
AMBER ON At least one external signal source entering the module faceplate is not
carrying a valid signal.
-----------------------------------------------------------------------------------------
-End-
Note: To prolong LED life, program the green LEDs so it can enter the sleep-mode. LED sleep-mode timing is controlled by the entry in field LEDTIMER in data schema table MNNODE. Sleep-mode does not apply to red LEDs.