Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2
January 1998
Maintenance Architecture
Page 1-5 What’s new for R6.2r
1
Figure 1-2. Change system-parameters customer-options form
!WARNING:
Do not change the Softlock? field to y, as it locks all administered
passwords in the system.
Similarly, Figure 1-3 shows page 2 of the Change System-parameters Security
form containing the following SoftLock fields that
should not be changed:
nSYSAM-LCL?
nSYSAM-RMT?
nMAINT?
nSYS-PORT?
These fields are shown in bold for reference only.
change system-parameters customer-options Page 2 of 4
OPTIONAL FEATURES
OPERATIONS SUPPORT PARAMETERS
ISDN-BRI trunks? n Restrict Call Forward Off Net? y
ISDN-PRI? y Secondary Data Module? y
ISDN-PRI over PACCON? y Softlock? n
Malicious Call Trace? n Station and Trunk MSP? n
Mode Code Interface? n Tenant Partitioning? n
Multifrequency Signaling? y Terminal Trans. Init. (TTI)? y
Multimedia Appl. Server Interface (MASI)? n Time of Day Routing? n
Multimedia Call Handling (Basic)? n Uniform Dialing Plan? n
Usage Allocation Enhancements? n
Personal Station Access (PSA)? y
Wideband Switching? n
Wireless? n
Processor and System MSP? n
Private Networking? n
(NOTE: You must logoff and login to effect the permission changes.)
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2
January 1998
Maintenance Architecture
Page 1-6 What’s new for R6.2r
1
Figure 1-3. Change system-parameters security form
!WARNING:
Do not change any of these fields to y.
Init logins
There are no changes to these logins for R6.2.
INADS and craft logins
There are no changes to these logins for R6.2.
Multimedia Call Handling (MMCH)
Enhancements
A new TN2207 PRI circuit pack allows connection to the Expansion Services
Module (ESM).
nProvides T.120 data-sharing capability on a MMCH multipoint H.320 video
conference
nEach conference participant must have endpoints administered and a
personal computer with the H.320 video application installed.
nThe DEFINITY ECS must have the expansion service module installed.
See ‘‘
Expansion Services Module’’ in Chapter 5, ‘‘Responding to Alarms and
Errors’’ for connectivity information.
change system-parameters security Page 2 of 2
SECURITY-RELATED SYSTEM-PARAMETERS
SECURITY VIOLATION NOTIFICATION PARAMETERS
SVN Station Security Code Violation Notification Enabled? n
STATION SECURITY CODE VERIFICATION PARAMETERS
Minimum Station Security Code Length: 4
Security Code for Terminal Self-Administration Required? y
SOFTLOCK PARAMETERS
SYSAM-LCL? n SYSAM-RMT? n
MAINT? n SYS-PORT? n
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-7 Maintenance Objects 1 Maintenance Objects The system is partitioned into separate entities called maintenance objects (MOs). Each MO is monitored by the system and has its own maintenance strategy. Most MOs are individual circuit packs such as the processor circuit pack (PROC) and expansion interface circuit pack (EXP-INTF). Some are hardware components that reside on part of a circuit pack. For example, the TDM bus clock (TDM-CLK) and tone generator (TONE-PT) circuits reside on the tone/clock circuit pack (TONE-BD). Others represent larger subsystems or sets of monitors, such as expansion port network (EXP-PN) and cabinet environmental sensors (CABINET). Finally, some MOs represent processes or combinations of processes and hardware, such as synchronization (SYNC) and duplicated port network connectivity (PNC-DUP). The above abbreviations are maintenance names as recorded in the error and alarm logs. Individual copies of a given MO are further distinguished with an address that defines its physical location in the system. These addresses are described in Chapter 8, ‘‘ Maintenance Commands’’. Repair instructions and a description of each MO appear alphabetically in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. Alarm and Error Reporting During normal operations, software, hardware, or firmware may detect error conditions related to specific MOs. The system attempts to fix or circumvent these problems automatically, but if a hardware component incurs too many errors, an alarm is raised. Alarm and Error Logs The system keeps a record of every alarm detected in the system. This record, the alarm log, and the error log can be displayed locally on the management terminal or remotely by Initialization and Administration System (INADS) personnel. An alarm is classified as MAJOR, MINOR, or WARNING, depending on its effect on system operation. Alarms are also classified as ON-BOARD or OFF-BOARD. nMAJOR alarms identify failures that cause critical degradation of service and require immediate attention. On high and critical reliability systems, MAJOR alarms can occur on standby components without affecting service since their active counterparts continue to function. nMINOR alarms identify failures that cause some service degradation but do not render a crucial portion of the system inoperable. The condition requires attention, but typically a a MINOR alarm affects only a few trunks or stations or a single feature.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-8 Alarm and Error Reporting 1 nWARNING alarms identify failures that cause no significant degradation of service or failures of equipment external to the system. These are not reported to INADS or the attendant console. nON-BOARD problems originate in circuitry on the alarmed circuit pack. nOFF-BOARD problems originate in a process or component external to the circuit pack. Multiple alarms against a given MO can change the level of a given alarm as it appears in the alarm log. If there is an active error against an MO that causes a MINOR alarm and an active error that causes a MAJOR alarm, then the alarm log would show two MAJOR alarms. If the MINOR alarm problem is resolved first, the error is still marked as alarmed until the MAJOR alarm problem is resolved, and the alarm log would still show two MAJOR alarms. If the MAJOR alarm problem is resolved first, the error is still marked as alarmed until the MINOR alarm problem is resolved, and the alarm log would now show two MINOR alarms. Similarly, the presence of an ON-BOARD alarm will cause all alarms against that MO to report as ON-BOARD. NOTE: To determine the actual level and origin of each alarm when there are more than one against the same MO, you must consult the Hardware Error Log Entries table for that MO. The alarm log is restricted in size. If the log is full, a new entry overwrites the oldest resolved alarm. If there are no resolved alarms, the oldest error (which is not alarmed) is overwritten. If the log consists of only active alarms, the new alarm is dropped. INADS Alarm Reporting All Major and Minor alarms and some downgraded Warning alarms are reported to INADS. (Some classes of alarms can be downgraded to lower levels by INADS at the customer’s request). When the system raises one of these alarms, an attempt is made to call INADS. If the call to INADS fails, the call is retried in 7 minutes. This is repeated until four attempts have been made in a period of approximately 21 to 30 minutes. If all 4 attempts fail, the system waits 1 hour. Then it starts over again with 4 call attempts spaced 7 minutes apart. This cycle repeats until either the call to INADS successfully completes, or until the whole cycle is repeated 6 times. If, at any time during, a new alarm is raised by the system that should be reported to INADS, all timers and counts are reset and the strategy is repeated from the beginning. During the 4 call attempts, the ACK lamp on the attendant console is turned off. Approximately 15 minutes into the hour interval between call attempts, the ACK lamp flashes, indicating the system is having trouble reporting alarms to INADS. At the end of the entire scenario described above, if the system could not report the alarm to INADS, the ACK lamp continues to flash.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-9 Port Network Connectivity (PNC) 1 Port Network Connectivity (PNC) Port network connectivity is the equipment and controlling software that allows building large systems comprised of multiple Port Networks (PNs). Each PN is composed of Time Division Multiplexing (TDM) and packet (PKT) busses, and the port circuit packs connecting to them. A multi-carrier cabinet can contain more than one PN. NOTE: The terms LAN bus and PKT bus are interchangeable on the Release 5r. This document uses the term PKT bus, but “LAN” appears marked on some hardware components. This section describes the hardware, software and firmware components that support the PNC. Knowledge of the service and maintenance functions of these components will aid in diagnosing and resolving troubles. Troubleshooting techniques for general PNC components such as busses appear in Chapter 6, ‘‘Additional Maintenance Procedures’’. PNC Configurations The PNC is provided in one of two different configurations: Direct Connect and Center Stage Switch (CSS). In either configuration the TN570 Expansion Interface (EI) board provides the interface to the data on the TDM/PKT busses. In the direct connect configuration up to three PNs connect by hardware between each pair of PN EIs. See Figure 1-4 .
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-10 Port Network Connectivity (PNC) 1 Figure 1-4. Direct Connect PNC In the CSS configuration, up to 16 PNs (including the PPN) can connect to one switch node (SN). With two SNs, up to 22 PNs can be connected. Each SN consists of a carrier containing the following components (in critical reliability systems, each SN is duplicated on a second, identically configured carrier): n1 to 16 switch node interface (SNI) circuit packs (TN573) Each SNI serves as the interface for TDM/PKT data to and from its associated PN EI or to and from an SNI in the other switch node. n1 or 2 switch node clock (SNC) circuit packs (TN572) The SNCs provide timing for bit synchronized switching among the SNIs. nTwo power units Each power unit provides +5V to the circuit packs in its half of the SN and to both SNCs. nOptionally in the PPN only, one Expansion Interface nOptionally, 1 or 2 DS1 converter (DS1C) circuit packs The DS1 CONV circuit packs allow PNs to be located remotely up to 100 miles (161 km) between the two most distant PNs. The DS1 CONVs provide DS1 facility transport for a subset of the fiber timeslots between EIs in a direct connect system or between EIs and SNIs in CSS configurations. They can also be located on port carriers. Slot # Slot # Slot # Slot #2 2 2 1 2 1 Cabinet 2 Cabinet 3 Carrier A Carrier A Cabinet 1 Cabinet 1 EPN EPNE E E E E EI Fiber LinksI I I I IPORT Carrier PORT CarrierPPN PPN
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-11 Port Network Connectivity (PNC) 1 nTDM and PKT busses, and bus terminations There are 16 data busses in the SN. Each SNI has a slot dependent data bus on which it transmits data and has 16 inputs, one for each SN SNI slot, including its own. The data busses are terminated by 4 AHF105 paddle boards that mount on the backside of the backplane slots 2 and 20. nPower distribution and control leads Figure 1-5 shows two examples of CSS configurations. Illustrations of the switch node carrier hardware appear in Chapter 2. Figure 1-5. Center Stage Switch Configurations (Simplex Examples) EI EPN EI EIEPN EPNEI EI EI EIEI EI EI EIEPN EPN EPN EPNEPN EPN EPN EPN Inter-switch node ®bers1carriernode Switch * * * 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 21 Slot number 19 S N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N I S N CS N C S N CS N C E E 2 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 21 carriernode Switch Slot number 19* * S N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N IS N I CSS with two switch nodes EI EPN EI EIEPN EPN PPN EI EI EPNEI EIEPN EPNEPN EIEI EI EI EPNEPN EPN * * * C NS C NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS I NS 19 Slot numberFiber links not usedSwitch node carrier 21 EI EPN EI EPN EI EPNEI EI EI EIEPN EPNEPN EPN EPN EIEI EIEPN EPNEPNEI 5 4 3 20 18 17 16 15 14 13 12 11 10 9 8 7 6 2 1 CSS with one switch node EI EPN EI EIEPN EPN PPN EI EI EPN * The PPN EI or a DS1C circuit pack may reside in this slot ** A DS1C circuit pack may reside in this slot
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-12 SPE Duplication 1 SPE Duplication The Switch Processing Element (SPE) consists of the following circuit packs. These circuit packs reside on the A carrier (control carrier) of the PPN in all systems, except for the UN330B which is found only in high and critical reliability systems. In high and critical reliability systems, the PPN B carrier duplicates exactly the configuration of the A carrier, making two identical SPE complexes. This duplication allows the system to recover from many faults, and enables troubleshooting and repairing of SPE components without interrupting service. The Tone-Clock circuit pack also resides on the control carrier, and is also duplicated. However, it is not considered a part of the SPE. Although the SPE-Select switches control Tone-Clock selection, its duplication strategy differs from that of the SPE. See the ‘‘ TDM-CLK (TDM Bus Clock)’’ and ‘‘TONE-BD (Tone-Clock Circuit Pack)’’ sections in Chapter 9, ‘‘Maintenance Object Repair Procedures’’ for details. Duplicated SPEs employ an active/standby strategy. At any one time, one SPE, A or B, is designated active and controls the switch services network. The other SPE, designated standby, is not required for switch service but remains ready to become active and resume control of service should a service-affecting failure occur in the active SPE. This action is termed an SPE interchange. It is important that the standby SPE be kept as available as possible to allow for a rapid interchange. Table 1-1. SPE Circuit Packs and Maintenance Objects Apparatus Code Circuit Pack NameAssociated Maintenance Objects TN1648 System Access and MaintenanceSYSAM UN330B Duplication Interface DUPINT, DUP-CHL UN331B Processor PROCR TN1650B Memory MEM-BD TN1655 Packet PKT-INT UN332 Mass Storage System/ Network Control (MSSNET)H-ADAPTR, SW-CTL TN1657 Disk Drive DISK TN1656 Tape Drive TAPE STBY-SPE STO-DATA
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-13 SPE Duplication 1 Standby SPE Availability The STBY-SPE maintenance object is responsible for testing of the standby SPE so that any faults that would prevent it from being available for service can be isolated and repaired. Various factors affect the availability of the standby SPE: nThe condition of the individual hardware components of the standby SPE, including circuit packs, power supplies, cables and other supporting components. Loss of power in an SPE due to power supply or power delivery components is discussed under the condition SPE-Down. If a circuit pack in the standby SPE that is critical to call service has failed, the standby will not be able to become active. Maintenance testing of the standby SPE allows isolation and repair of component problems so that the standby can be made available again. nStandby memory content Each write operation in active memory is shadowed to the corresponding location in the standby SPE’s memory. The standby memory should be in agreement with the active in order to support an interchange that will preserve call, feature and translation information. Maintenance software tracking the STBY-SPE MO aims to keep the two memories in agreement. nStandby State-of-Health (SOH) The Duplication Interface circuit packs maintain a state-of-health value which reflects the availability of the standby SPE. If the Standby SPE’s state-of-health level is too poor, it cannot automatically be interchanged into (made active). nStandby SPE-Down If the standby SPE is completely dead and held reset by its SYSAM (in SPE-Down), or the standby SPE has no power, it is unavailable for service. nSystem Time-of-Day If the Time-of-Day clock of the standby SPE is substantially out of synch with the active, interchanges could be more disruptive to service than desirable. System software running on both active and standby SPEs attempts to ensure that the standby SPE is kept fully available in terms of the above factors. The health of both the active and standby is tracked as a State-of-Health (SOH) value.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Maintenance Architecture Page 1-14 SPE Duplication 1 Figure 1-6. Duplicated SPEs — Hardware Configuration Standby SPE State of Health The Duplication Interface circuit packs on each of the two SPEs keep track of the State of Health (SOH) of each of the two SPEs. This circuitry ensures that, at any time, unless the SPE-select switches are locked: nIf the two SPEs have the same SOH, the current active SPE remains active. Active Maintenance Interface SPE-Down InterfaceS Y S A M S Y S A MP R O C R P R O C RM E M O R YM E M O R YM E M O R YM E M O R YP K T I N TT N C L K T N C L K P K T I N T M S S N E T M S S N E T D I S KD I S K T A P E T A P E TDM BusTDM Bus LAN Bus LAN Bus G3-MT G3-MTB Processor Carrier A Processor Carrier Processor Multiplexed Bus Processor Multiplexed BusSCSI Bus SCSI Bus Duplication Cable TN1656 TN1648 UN332 TN1655 TN1650B TN1650BTN1650B TN1650B UN331B UN331B UN330B UN330B TN1657 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .S P E B S P E A TN1648 UN332TN1655TN1657 TN1656 D U P I N T D U P I N T