1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. MCC1
  6. Maintenance procedures

Avaya MCC1 Maintenance Procedures

Hide thumbs Also See for MCC1:
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
Table of Contents

Advertisement

Quick Links

Maintenance Procedures
555-245-103
Issue 1.1
December 2003

Advertisement

Table of Contents
loading

Related Manuals for Avaya MCC1

Summary of Contents for Avaya MCC1

  • Page 1 Maintenance Procedures 555-245-103 Issue 1.1 December 2003...

  • Page 2: Procedure

    The final responsibility for securing both this system and its networked equipment rests with you - Avaya’s customer system Avaya Inc. provides a limited warranty on this product. Refer to your administrator, your telecommunications peers, and your managers. sales agreement to establish the terms of the limited warranty. In Base the fulfillment of your responsibility on acquired knowledge and addition, Avaya’s standard warranty language as well as information...
  • Page 3 The LASER devices operate within the following parameters: Avaya attests that this registered equipment is capable of providing users access to interstate providers of operator services through the use • Maximum power output: -5 dBm to -8 dBm of access codes. Modification of this equipment by call aggregators to •...

  • Page 4: Reset Level

    FIC Code SOC/REN/ Network (SDoC) Identifier A.S. Code Jacks Avaya Inc. in the United States of America hereby certifies that the Ground Start CO trunk 02GS2 1.0A RJ11C equipment described in this document and bearing a TIA TSB-168 DID trunk 02RV2-T AS.0...

  • Page 5: Table Of Contents

    Contents Contents About this book • Overview • Audience • Downloading this book and updates from the Web Downloading this book • Safety and security-alert labels • Safety precautions Electromagnetic interference • Related resources • Technical assistance Within the United States International •...
  • Page 6 Contents • Power interruptions Nominal power holdover Power interruption effects External alarm leads • Protocols OSI layers Usage Protocol states Connectivity rules • Signaling Disconnect supervision Transmission characteristics • Service codes • Facility Interface Codes • Multimedia Interface (MMI) • S8300 and G700 maintenance strategy Media Module maintenance Access to the G700 Media Gateway and S8300 Media Server...
  • Page 7 Windows 2000 login types for the customer Enabling Windows 2000 customer logins Communication Manager logins for the customer • Avaya Site Administration configuration • Navigating the Command Line Interface • Accessing the S8100 Media Server for maintenance Web browser interface...
  • Page 8 Contents Hardware configurations • Multicarrier cabinets • PNC cabling — fiber-optic hardware EI-to-EI or EI-to-SNI intercabinet fiber-optic cables EI-to-SNI or EI-to-EI intracabinet metallic cabling DS1 CONV cabling • Circuit packs • Duplication for reliability • Basic server and IPSI connections High reliability connectivity Critical reliability connectivity Standard and High Reliability configurations...
  • Page 9 Contents • S8100 Initialization LED boot sequence Communication Manager initialization Shutdown S8100 recovery Communication Manager resets Recovery from fatal errors in the S8100 Resolving alarms • Link Recovery H.248 server-to-gateway Link Recovery H.323 gateway-to-endpoint Link Recovery • System resets Reset Level 1 (Warm Restart) Reset Level 2 (Cold-2 Restart) Reset Level 3 (Communication Manager reboot) Reset Level 4...
  • Page 10 Contents • Troubleshooting ATM Initial LED inspection A500 switch diagnostics ATM administration A500 administration TN230X circuit pack(s) Physical layer SONET layer Q.SAAL (data link) layer Q.93B (network) layer ATM call control CaPro layer Unusual ATM trouble conditions • Troubleshooting Multimedia Call Handling (MMCH) Expansion Services Module •...
  • Page 11 • S8300 and G700 component maintenance Field-replaceable components Processors Avaya Cajun equipment Replacing the G700 Media Gateway Replacing the S8300 Media Server or hard drive Replacing Media Modules Replacing Avaya Expansion Modules Replacing an Avaya Octaplane Stacking Module Maintenance Procedures December 2003...
  • Page 12 Contents • S8500 component maintenance Replacing the S8500 hard drive Replacing the S8500 Media Server Replacing the Remote Supervisor Adapter (RSA) Replacing the S8500 dual network interface • S8700 component maintenance Replacing the S8700 Media Server Replacing the S8700 hard drive •...
  • Page 13 Contents • Analog tie trunk back-to-back testing E&M mode test procedure Simplex mode test procedure • TN760E tie trunk option settings • TN464E/F option settings • Terminating Trunk Transmission testing • Removing and restoring power Removing and restoring power to the Media Gateway Removing and restoring power from the Media Server Removing and restoring power on the S8100 media server Setting neon voltage (ring ping)
  • Page 14 Contents Maintenance Procedures December 2003...

  • Page 15: About This Book

    About this book Overview This document provides procedures to monitor, test, and maintain an Avaya Media Server or Gateway system. It covers many of the faults and troubles that can occur and provides simple procedures to correct them. Simple, traditional troubleshooting methods are sometimes sufficient to locate and clear faults. The traditional methods include substitution, visual inspections, continuity checks, and clarification of operating procedures with end users.

  • Page 16: Downloading This Book And Updates From The Web

    Downloading this book and updates from the Web You can download the latest version of this book from the Avaya Web site. You must have access to the Internet, and a copy of Acrobat Reader must be installed on your personal computer.

  • Page 17: Safety Precautions

    Administration for Network Connectivity for Avaya Communication 555-233-504 Manager, 555-233-504 Avaya P330 Manager User Guide Avaya P333T User’s Guide Getting Started with the Avaya S8700 Media Server with the Avaya G650 555-245-703 Media Gateway, 555-245-703 (1 of 2) Maintenance Procedures...

  • Page 18: Technical Assistance

    Maintenance and repair, call the Avaya National Customer Care Support Line at 1-800-242-2121 • Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353 International For all international resources, contact your local Avaya authorized dealer for additional help. Maintenance Procedures December 2003...

  • Page 19: Trademarks

    About this book Trademarks Trademarks All trademarks identified by the ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. Sending us comments Avaya welcomes your comments about this book. To reach us by: •...

  • Page 20: Conventions Used In This Document

    Table 2: Typography used in this book This typeface and syntax are To represent... shown as... For example... Specific component • Avaya component model S8700: Ensure that the duplication link information number is securely connected. • Indented lines set apart...

  • Page 21: Useful Terms

    About this book Useful terms Table 2: Typography used in this book This typeface and syntax are To represent... shown as... For example... SAT screen input • Bold for input Set the Save Translation field to and output daily. • Constant width for field The message Command...
  • Page 22 About this book Useful terms Table 3: Terminology summary Present Terminology Former Terminology Communication Manager MultiVantage Avaya Call Processing S8300 Media Server ICC, Internal Call Controller S8700 Media Server (or non-co- ECC, External Call Controller resident S8300) MGP, Media Gateway Processor...

  • Page 23: Maintenance Strategy

    Maintenance strategy Maintenance Objects Maintenance strategy The maintenance subsystem is the part of a system’s software that is responsible for initializing and maintaining the system. This subsystem continuously monitors the system’s health and records detected errors. The maintenance subsystem also provides a user interface for on-demand testing. This chapter provides a brief description of the maintenance strategy and presents background information about the system’s overall functions.

  • Page 24: Maintenance Testing

    Maintenance strategy Maintenance testing Most MOs are individual circuit packs such as the: • Direct Inward Dial Trunk circuit pack (DID-BD) • DS1 Tie Trunk circuit pack (TIE-DS1) • Expansion Interface (EI) circuit pack (EXP-INTF) Some MOs represent hardware components that correside on a circuit pack. For example, the following circuit packs have the listed circuits residing on them: •...

  • Page 25: Demand Testing

    Maintenance strategy Co-Resident DEFINITY LAN Gateway maintenance • Fixed-interval tests: — Performed at regular time intervals and cannot be administered — Run concurrently with periodic maintenance — The MOs that run fixed-interval testing are listed below: Maintenance Object Interval (min) TDM-BUS TONE-PT Demand testing...

  • Page 26: Administration And Maintenance

    Maintenance strategy Media processor (DEFINITY ONE) Administration and maintenance Before the LAN interface on the TN2314 processor card can be used, the Processor Ethernet? field must be enabled in the License File for this system. Display the System-Parameters Customer- Options form ( display system-parameters customer-options ), page 4, to check that this field is enabled (set to y).

  • Page 27: Alarm And Error Reporting

    • WARNING alarms identify failures that cause no significant degradation of service or failures of equipment external to the system. These are not reported to the Avaya alarm receiving system or the attendant console. •...

  • Page 28: Alarm Reporting

    Alarm reporting Every major or minor alarm is reported to the Avaya alarm receiver system to generate a trouble report in the Avaya Services Ticketing System. Some warning alarms can be upgraded in conjunction with the Enhanced Remote Support (ERS) offer.

  • Page 29: Power Interruptions

    Maintenance strategy Power interruptions Figure 2: Alarm reporting flowchart Some All minor downgraded major alarms warning alarms alarms Every timer and count is reset Call to alarm receiving system alarm successfully raised? completed? Call to alarm receiving system successful Fifth retry attempt? hour wait test been...

  • Page 30: Nominal Power Holdover

    Maintenance strategy Power interruptions If power is interrupted to a DC- or an AC-powered cabinet without optional backup batteries, the effect depends upon the decay time of the power distribution unit: • If the interruption period is shorter than the decay time, there is no effect on service, though some -48V circuits may experience some impact.

  • Page 31: External Alarm Leads

    EXT-DEV alarms are generated by the equipment connected to these leads and reported to the Avaya alarm receiving system. These might be used to report failures of UPSs or battery reserves powering the switch. They are also commonly used to monitor adjuncts such as AUDIX.

  • Page 32: Osi Layers

    Maintenance strategy Protocols OSI layers The Open System Interconnect (OSI) model for data communications contains seven layers, each with a specific function. Communications to and through the system concern themselves only with Layers 1 and 2 of the model. • Layer 1, or the physical layer, covers the physical interface between devices and the rules by which bits are passed.

  • Page 33: Usage

    Maintenance strategy Protocols Figure 3: Intra-port and Inter-port data transmission states ORIGINATING SYSTEM DESTINATION DATA DATA MODULE MODULE DATA DATA MODULE MODULE RS232C RAW BITS RS232C ASCII ASCII USER DEFINED MODEM MODEM POOLING CABLE MODEM MODEM RS232C ANALOG ANALOG RS232C ASCII VOICE GRADE DATA ASCII...
  • Page 34 Maintenance strategy Protocols Layer-1 protocols Layer-1 protocols are used between the terminal or host DTE and the DCE, used between the DCE equipment and the system port, and used inside the system. The following Layer-1 protocols are used between the DTE equipment and the DCE equipment. DCE equipment can be data modules, modems, or Data Service Units (DSUs).

  • Page 35: Protocol States

    Maintenance strategy Protocols Inside the system, data transmission appears in one of two forms: • Raw digital data, where the physical layer protocols, like DCP, are stripped at the incoming port and reinserted at the outgoing port. • Pulse Code Modulation (PCM)-encoded analog signals (analog transmission by a modem), the signal having been digitized by an analog-to-digital coder/decoder (CODEC) at the incoming port.

  • Page 36: Connectivity Rules

    Maintenance strategy Protocols Both the physical-layer protocol and the Digital Multiplexed Interface (DMI) mode used in the connection are dependent upon the type of 8-bit code used at layer 2 between the DTE and DCE equipment, as listed in Table 7, Physical-layer protocol versus character code, on page 36 and Table 8, Digital Multiplexed Interface (DMI) mode versus character code,...

  • Page 37: Signaling

    Maintenance strategy Signaling origination or destination system. A modem-pool member is always inserted automatically for calls to off-premises sites via analog or voice-grade trunking. For internal calls, however, the systems are capable of automatically inserting a modem-pool member. • Data cannot be carried over analog facilities unless inside the system it is represented as a PCM- encoded analog signal.

  • Page 38: Transmission Characteristics

    Maintenance strategy Signaling Conference, Transfer, and Call-Forwarding Denial If a station or attendant attempts to connect parties without disconnect supervision together, the outcomes listed in Table 9, Attempted connection without disconnect supervision, on page 38 are possible. Table 9: Attempted connection without disconnect supervision Attempted activity Possible outcome Digital station or local...
  • Page 39 Maintenance strategy Signaling Frequency response Table 10, Analog-to-analog frequency response, on page 39 lists the analog-to-analog frequency response for station-to-station or station-to-CO trunk, relative to loss at 1 kHz for the United States. Table 10: Analog-to-analog frequency response Frequency Maximum loss Minimum loss (Hz) (dB)
  • Page 40 Maintenance strategy Signaling Insertion loss Table 12, Insertion loss (United States), on page 40 lists the insertion loss in the system for port-to-port, analog, or digital connections in the United States. Table 12: Insertion loss (United States) Nominal loss Typical connections (dB) at 1 kHz On-premises to on-premises station On-premises to off-premises station...
  • Page 41 Maintenance strategy Signaling Table 15: Quantization distortion loss (analog port-to-analog port) Signal level Distortion loss 0 to -30 dBm0 >33 dB -40 dBm0 >27 dB -45 dBm0 >22 dB Table 16, Quantization distortion loss, on page 41 lists the quantization distortion loss in the system for analog port-to-digital port and digital port-to-analog port.

  • Page 42: Service Codes

    Maintenance strategy Service codes Peak noise level Table 18, Peak noise level, on page 42 shows the peak noise level. Table 18: Peak noise level Type of Peak noise level connection (dBrnC) Analog to analog Analog to digital Digital to analog 1 Decibels above reference noise with C-filter Echo path delay •...

  • Page 43: Facility Interface Codes

    Maintenance strategy Facility Interface Codes Facility Interface Codes A Facility Interface Code (FIC) is a 5-character code (United States only) that provides the technical information needed to order a specific port circuit pack for analog private lines, digital lines, MTS lines, and WATS lines.

  • Page 44: Multimedia Interface (Mmi)

    This leads to a dual strategy in which some of the G700's subsystems are maintained and controlled by a Media Server running Avaya Communication Manager, while others are covered by maintenance software residing on the G700. The latter subsystems are not monitored directly by a Media Server.

  • Page 45: Media Module Maintenance

    290. CAUTION: The Avaya Expansion Modules and Cascade Modules — are NOT hot-swappable. They are service-disrupting and can reset the entire G700 upon insertion or removal. Power down the system, including shutting down the S8300 hard drive, if present, prior to any insertion or removal of Avaya Expansion and Cascade modules.

  • Page 46: Access To The G700 Media Gateway And S8300 Media Server

    Access to the G700 Media Gateway and S8300 Media Server You can access the Avaya Media Servers in several ways: • Web server access to the Avaya Media Server IP address (Accesses Web page with Online Help) • Telnet from customer LAN to the: •...

  • Page 47: Layer 2 Switching Processor Cli

    For more information about the L2 Processor CLI refer to Avaya P330 Manager User Guide. G700 server-controlled maintenance DEFINITY equivalent elements Many of the Avaya Media Modules and G700 subsystems are based on existing DEFINITY circuit packs or systems as listed in Table 23, DEFINITY equivalent elements, on page 47.

  • Page 48: Capacity Constraints And Feature Limitations

    DEFINITY server port boards and the associated ports. Some tests abort with abort code 1412 to indicate that these tests cannot be run on a Media Module Maintenance Object by maintenance software on Avaya Media Servers. NOTE: No alarms are generated for failures detected by tests that are specified to abort for Media Modules.
  • Page 49 Maintenance strategy G700 server-controlled maintenance Table 24: Media module tests Maintenance Executed for Media Module Object Test Media Module Analog Media Board (ANA- NPE Audit Test (#50) Abort Module Ringing Application Test (#51) (DEFINITY server (DEF TR-LN- TN797) Control Channel Looparound Test (#52) SAKI Sanity Test (#53) Analog Line...
  • Page 50 Maintenance strategy G700 server-controlled maintenance Table 24: Media module tests Maintenance Executed for Media Module Object Test Media Module BRI Trunk Media Board (MG-BRI) NPE/NCE Audit Test (#50) Abort Module (MM720) (DEF TBRI-BD) Control Channel Looparound Test (DEF TN2185) (#52) LAN Receive Parity Error Counter Test (#595) SAKI Sanity Test (#53)
  • Page 51 Maintenance strategy G700 server-controlled maintenance Table 24: Media module tests Maintenance Executed for Media Module Object Test Media Module BRI Trunk Media Board (BRI- NPE/NCE Audit Test (#50) Abort Module MM) (DEF Control Channel Looparound Test Abort (DEFINITY TBRI-BD) (#52) TN2185) LAN Receive Parity Error Counter Test (#595)
  • Page 52 Maintenance strategy G700 server-controlled maintenance Table 24: Media module tests Maintenance Executed for Media Module Object Test Media Module DCP Media Board (MG- NPE Audit Test (#50) Abort Module DCP) (DEF Control Channel Loop Test (#52) (DEFINITY server DIG-BD) TN2224) SAKI Sanity Test (#53) Digital Line Digital Line NPE Crosstalk Test (#9) Abort...
  • Page 53 Maintenance strategy G700 server-controlled maintenance Table 24: Media module tests Maintenance Executed for Media Module Object Test Media Module DS1 CO Trunk NPE Crosstalk Test (#6) Abort (CO-DS1) Conference Test (#7) Abort Port Audit and Update Test (#36) DS1 CO Trunk Seizure Test (#314) Abort DS1 DID Trunk NPE Crosstalk Test (#6)

  • Page 54: Testing

    Maintenance strategy G700 server-controlled maintenance Table 24: Media module tests Maintenance Executed for Media Module Object Test Media Module Voice Board (MG- Control Channel Loop Test (#52) Announcements ANN) Invalid LAPD Frame Error Counter (DEFINITY server Test (#597) TN2501AP) PPE/LANBIC Receive Parity error Counter Test (#595) Receive FIFO Overflow Error Counter Test (#596)
  • Page 55 Maintenance strategy G700 server-controlled maintenance Table 25: Tests not executed on the G700 platform Test Notes NPE_AUDIT This test is really an audit that sends network update messages to various ports on a board. Since the Media server does not handle network connections for the MG, this test is not run.
  • Page 56 Maintenance strategy G700 server-controlled maintenance Tone detector tests not executed on the G700 Table 26, Tone detector tests not executed on the G700 platform, on page 56 lists the tone detector tests not executed on the G700. Table 26: Tone detector tests not executed on the G700 platform Test Notes TD_DET_TS...

  • Page 57: Maintenance Features For The G700

    Maintenance features for the G700 Table 29, Maintenance features for Avaya G700 Media Gateway, on page 57 specifies maintenance features as they apply to the Avaya G700 with the S8300 Media Server. Table 29: Maintenance features for Avaya G700 Media Gateway Controller...
  • Page 58 Maintenance strategy G700 server-controlled maintenance Table 29: Maintenance features for Avaya G700 Media Gateway Controller S8700/ S8500 Supported feature S8300 Notes System tone test call Requires changes to the call processing software in for G700 the S8300 and the G700...

  • Page 59: Access And Login Procedures

    G700 Media Gateway. The procedures in this chapter assume that you are connecting to the S8300 and/or the G700 with an Avaya Services laptop. However, the methods apply for any type of PC. This chapter contains information on these topics: •...

  • Page 60: Laptop Settings And Connections

    NOTE: Avaya Service technicians can use the NetSwitcher program to configure alternate network profiles so they can easily connect to a number of different systems. NetSwitcher configures a profile for each type of system for easy future access without requiring you to reset TCP/IP properties or browser settings manually.

  • Page 61: Laptop Settings

    Disable/bypass proxy servers in browser NOTE: The S8300 Media Server uses the same access configuration as an Avaya S8100 Media Server with a CMC1 or G600 Media Gateway. If you already have a NetSwitcher profile for the S8100 Media Server, try using that profile first before configuring a new one.
  • Page 62 Access and login procedures Laptop settings and connections Right-click the correct Local Area Connection from the list in the window. Select Properties to display the Local Area Connection Properties dialog box. Select Internet Protocol (TCP/IP). Click the Properties button. The Internet Protocol (TCP/IP) Properties screen appears. On the General tab, select the radio button Use the following IP address.
  • Page 63 Access and login procedures Laptop settings and connections In the TCP/IP Properties box, click the IP Address tab. Click the radio button to Specify an IP address , and enter the following: • IP address: 192.11.13.5 • Subnet mask: 255.255.255.252 NOTE: Record any IP addresses, DNS settings, or WINS entries that you change.

  • Page 64: Laptop Connections

    Access and login procedures Laptop settings and connections If Use a proxy server for your LAN is not selected, no change is necessary; click Cancel to exit. If Use a proxy server for your LAN is selected, you can: • Deselect it and click OK to exit;...
  • Page 65 Access and login procedures Laptop settings and connections Table 30: Crossover cable pinout chart Pin to S8300 Media Server’s Pin to laptop’s Services Ethernet interface Connects to Ethernet card Connect the other end of the crossover cable to the Services port on the front of the S8300. If your laptop is configured with the correct network settings, you can now open your Internet browser or start a Telnet session and log in.

  • Page 66: Connecting Through An External Modem

    Media Server (Windows 2000 or XP) To use Windows for modem connection NOTE: The remote dial-up PC must be configured for PPP access. Also, Avaya Terminal Emulator does not support Windows XP. Right-click My Network Places and click Properties .
  • Page 67 Access and login procedures Laptop settings and connections Select Dial-up to private network on the Network Connection Type screen. NOTE: If your system has more than one modem, you may be requested to select the device. If so, select the modem you are using to dial out. In the Phone number field, enter the appropriate telephone number inserting special digits such as 9 and 1 or *70, if necessary.
  • Page 68 Use Avaya Terminal Emulator for LAN connection to Communication Manager You can download the Avaya Terminal Emulator from the main menu for the Avaya Integrated Management. Simply click Download next to the Administration menu item and follow the instructions. Once the Terminal Emulator is installed on your PC, use the following steps to establish a LAN connection to your Media Server.
  • Page 69 To establish a modem connection to the Media Server Double-click the Terminal Emulator icon on your desktop. Alternatively, go to the Start menu, select Programs, then select Avaya, and finally select Terminal Emulator. The system displays the Terminal Emulator. From the menu bar across the top of the screen, select Phones, then select Connection List.
  • Page 70 Access and login procedures Laptop settings and connections In the TCP/IP port number field, leave 23 if you want to log in at the Linux command line. Type 5023 if you want to log in directly to the Communication Manager SAT command line. In the Modem field, use the dragdown box to select the type of modem that your PC uses.

  • Page 71: Login Methods

    Access and login procedures Login methods Table 32: w2ktt terminal emulation function keys Function Key Sequence Function Cancel Execute Help Next Page Previous Page Login methods This section describes how to log on to the S8300 Media Server using Telnet or the built-in Web Interface and how to start a SAT session.

  • Page 72: Logging In Using A Telnet Session On Your Laptop

    Access and login procedures Login methods Logging in using a telnet session on your laptop To run telnet Ensure you have an active Ethernet or serial connection from your computer to the server. Access the telnet program; for example: On a Windows system, go to the Start menu and select Run . •...
  • Page 73 Access and login procedures Login methods Figure 5: Welcome screen Click the Continue button. Accept the server security certificate to access the Login screen. The Login screen (Figure 6, Logon screen, on page 74) displays. Maintenance Procedures December 2003...
  • Page 74 Access and login procedures Login methods Figure 6: Logon screen Log in as craft . The main menu (Figure 7, Main menu, on page 75) displays. Maintenance Procedures December 2003...
  • Page 75 Access and login procedures Login methods Figure 7: Main menu Click on the link for Launch Maintenance Web Pages The system displays the S8300 main menu in the left panel and a usage-agreement notice in the right window (Figure 8, Maintenance Web pages, on page 76).

  • Page 76: Logging In To Communication Manager (Sat Screens)

    Figure 8: Maintenance Web pages Check the top of the left panel. • The Avaya Media Server you are logged into is identified by name and server number. • The S8300 Media Server number is always 1. Logging in to Communication Manager (SAT...

  • Page 77: Logging In To The Layer-2 Switching Processor

    Type telnet <xxx.xxx.xxx.xxx> , where <xxx.xxx.xxx.xxx> is the IP address of the Layer 2 stack master processor on the customer’s LAN. Login at the Welcome to Avaya P330 screen. Login: xxx from the planning documentation Password: xxx from the planning documentation You are now logged-in at the Supervisor level.
  • Page 78 For a complete list of command line interface commands, type help or refer to the Avaya P330 Manager User Guide.

  • Page 79: Logins And Passwords On The S8100

    Windows 2000 login. This enhancement allows a customer to use a login, such as NTADMIN, to access Windows 2000 via a “bash shell”. This feature is not intended to be used by Avaya Services personnel who continue to use the Lucent Services logins (lucent1, lucent2, lucent3).

  • Page 80: Windows 2000 Logins For The Customer

    The same logins are used with ports 22, and 24, as well as 23. The difference is that a direct connection is made to the appropriate application without a LAC prompt or having to use an alias login. See “Avaya Site Administration” in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146.

  • Page 81: Windows 2000 Login Types For The Customer

    Access and login procedures Logins and passwords on the S8100 Windows 2000 login types for the customer Administrator login NTadmin • This is a standard Windows 2000 administrator account used to administer network parameters and similar functions. INTUITY AUDIX logins browse •...

  • Page 82: Enabling Windows 2000 Customer Logins

    Activate and set passwords for the browse, vm, and sa accounts. This also can be done via the command line tool net user. See “Lucent access controller bash commands” in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146...

  • Page 83: Communication Manager Logins For The Customer

    Access and login procedures Logins and passwords on the S8100 Create three Windows 2000 accounts in the Officeadmin group for three application administrators. These accounts are used to download ASA software. The account names can be chosen as desired. For this example they are called D1user1, D1user2, and D1user3. Create one Windows 2000 account in the Officeuser group for download of the INTUITY Message Manager Software.The NTadmin account should be used for Windows 2000 administration only.
  • Page 84 Access and login procedures Logins and passwords on the S8100 Forced password aging (Communication Manager-specific) Forced password aging operates as follows: The password for each login can be aged starting with the date the password was created, or changed, and continuing for a specified number of days (1 to 99). 7 days before the password expiration date, the user is notified that the password is about to expire at the login prompt.
  • Page 85 Access and login procedures Logins and passwords on the S8100 Administer login command permissions Users with super-user permissions can set the permissions of logins they create by performing a change permissions <login-name> command. This causes the Login Permissions form to display. The Login Permissions form allows the user to control access to various categories of commands for a given login.

  • Page 86: Avaya Site Administration Configuration

    The system displays the Add Voice System window. Enter a name in the Voice System Name: field. As a technician configuring Avaya site Administration on your laptop, use a generic name, as you will be able to use this connection item for all S8300 Media Servers.

  • Page 87: Navigating The Command Line Interface

    Access and login procedures Navigating the Command Line Interface When prompted, log in. When you are logged in, click Start GEDI . Navigating the Command Line Interface Table 36, Navigational aid for CLI commands, on page 87 describes a few Command Line Interface commands that you will need to navigate between the processors on the G700.

  • Page 88: Accessing The S8100 Media Server For Maintenance

    — INTUITY Message Manager To use the web browser interface, see “Via a Web browser session” in Chapter 2, “Connectivity and Access to S8100” in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146.

  • Page 89: Avaya Site Administration

    Shutdown system • Install License and Authentication files NOTE: Refer to the Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146, Chapter 3, System Initialization, Section, “Obtaining a License.” • Startup/shutdown system IP addresses •...
  • Page 90 Access and login procedures Accessing the S8100 Media Server for maintenance Maintenance Procedures December 2003...

  • Page 91: License And Authentication Files

    The Avaya Authentication file contains the logins and passwords to access the S8300 Media Server. This file is updated regularly by Avaya services personnel, if the customer has a maintenance contract. A valid authentication file must be present on the S8300 Media Server, or all access to Avaya Communication Manager from any login is blocked.

  • Page 92: Installing License And Authentication Files

    The init login can no longer change the customer options, offer option, or special applications forms. Once the Avaya authentication files are installed, Avaya services logins to the S8700 Media Server are protected by a challenge/response system called Access Security Gateway (ASG). The ASG challenge/response protocol confirms the validity of each user, reducing the opportunity for unauthorized access.

  • Page 93: License Files For Different Configurations

    Access Security Gateway (ASG), which means a craft login will be challenged. Click Install Avaya Authentication > Install to install the Authentication File. License Files for different configurations License files are assigned differently, depending on the Media Server and G700 Media Gateway configuration.

  • Page 94: Survivable Configuration

    S8300 functioning in Local Survivable Processor mode. This field is modified only through the License File and is “display only” on the Customer Options form. License File modes License files for the Avaya S8300 Media Server in an Avaya G700 Media Gateway function in the following three modes: License-Normal This is the desired mode of operation for a stable switch.

  • Page 95: No-License

    License and Authentication files License and options forms interactions Access the following sections of the Web Interface: • Security -- View License Status • Server Configurations and Upgrades -- View Serial Number No-License In this mode, call processing continues, but the system operates in No-License Mode. Clear No-License Mode by correcting the error that caused entry into No-License Mode, or by installing a valid license that is consistent with the configuration of the switch.

  • Page 96: Maintenance Procedures

    License and Authentication files License and options forms interactions Table 37: Type I Feature License Behavior License content Consequence Value Lock Feature status Options screen Locked Translation is always ignored. init and dadmin may turn this Feature is enabled any time feature off and then back on, but translations are loaded.

  • Page 97: Hardware Configurations

    • Duplication for reliability • G700 with a Media Server system Multicarrier cabinets For information on the MCC1 (multicarrier) cabinet and the carriers in them, refer to Hardware Guide for Avaya Communication Manager, 555-233-200. PNC cabling fiber-optic hardware — The term “fiber” is used to refer to all the hardware needed for the three basic types of connections used to form multi-PN systems: •...
  • Page 98 Hardware configurations PNC cabling — fiber-optic hardware are available in various lengths up to 150 feet (46 m) for single-mode fiber and up to 200 feet (61 m) for multimode fiber. These fibers are used to connect lightwave transceivers to each other when they are close enough together, or to optical cross-connect facilities for greater distances.

  • Page 99: Ei-To-Sni Or Ei-To-Ei Intracabinet Metallic Cabling

    Hardware configurations PNC cabling — fiber-optic hardware EI-to-SNI or EI-to-EI intracabinet metallic cabling Metallic cable can be substituted for fiber-optic cable for “fiber” connections between EIs or between an EI and an SNI in the same MCC cabinet, using the same I/O plate connectors. DANGER: The metallic cables should not be used for intercabinet connections, since doing so would violate system ground integrity.
  • Page 100 Hardware configurations PNC cabling — fiber-optic hardware The DS1 CONV to EI/SNI cable is a shielded metallic Y-cable held in place at the EI/SNI port connector by a 4B retainer and at the DS1 CONV port connector by a 4C retainer. The cable end with one 25-pair amphenol connector attaches to the I/O Plate connector for the EI or SNI.

  • Page 101: Circuit Packs

    TN1654. Circuit packs Check the Minimum Vintage Table to determine which circuit packs will work with the Avaya S8700 Media Server for Multi-Connect Configuration. This table can be found online at http://support.avaya.com (search for “Minimum Vintage Table”) or in the Software Release Letter that accompanies the software CD.

  • Page 102: Duplication For Reliability

    IPSI per port network. Each media server is connected to the Ethernet switch which is on the LAN for connectivity to the IPSIs. IPSI circuit packs are described in more detail in the Hardware Guide for Avaya Communication Manager, 555-233-200.

  • Page 103: Critical Reliability Connectivity

    Hardware configurations Basic server and IPSI connections A port network can be IPSI-connected or non-IPSI-connected. In the high reliability configuration, all IPSI-connected port networks must have duplicated IPSIs. The non-IPSI-connected port networks will have nonduplicated Tone/Clock boards. Critical reliability connectivity In a critical-reliability configuration there is full duplication of these components: •...
  • Page 104 Hardware configurations Basic server and IPSI connections Figure 13: S8700 IP Connect duplex reliability Ethernet 2 Ethernet 1 Ethernet 1 Ethernet 0 CONSOLE IPSI IPSI IPSI 100bT 100bT 100bT LINK LINK LINK LINK LINK LINK TRMT TRMT TRMT TRMT TRMT TRMT PN 1 PN 2...
  • Page 105 Hardware configurations Basic server and IPSI connections S8700 MC Figure 14: High reliability for Multi-Connect configuration Ethernet 4 Ethernet 4 Ethernet 2 Ethernet 1 Ethernet 1 Ethernet 0 Ethernet 0 Ethernet 3 CONSOLE CONSOLE IPSI IPSI IPSI 100bT 100bT 100bT LINK LINK LINK...
  • Page 106 Hardware configurations Basic server and IPSI connections Figure notes Administration PC — used to access Network control B interface: default Ethernet S8700 Media Server over the corporate 3. The server’s Ethernet connection to a duplicated set of Ethernet switches. This private LAN carries control signals for the PNs when the primary control network is unavailable.

  • Page 107: Critical Reliability Configuration

    Hardware configurations S8100 Media Server components and functionality Figure notes Services interface: default Ethernet 1. The Bearer network server’s dedicated Ethernet connection to a laptop. This link is active only during on- site administration or maintenance. Network control A interface: default Ethernet 0.

  • Page 108: Virtual Boards And Devices

    If Windows 2000 is running on a laptop computer, set the terminal type to W2KTT for telnet sessions. For more information, refer to Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146.

  • Page 109: Gui Operation

    The S8100 uses Avaya Site Administration, which has a graphical user interface (GUI) for all functions. See Chapter 2, “Connectivity and Access to S8100” in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146.
  • Page 110 Hardware configurations S8100 Media Server components and functionality How backup works The S8100 system performs a backup by copying the files to be stored into a destination directory. All files currently in the directory are removed prior to backup. An identification file (ident file) is created for each backup, listing: •...
  • Page 111 Writable CDs Access Security Gateway Access Security Gateway (ASG), formerly SoftLock, is part of Avaya Site Administration. ASG is a centralized access interface that uses a challenge/response protocol to verify the authenticity of a user and to reduce the opportunity for unauthorized access. This is done through a key made of up to 20 octal digits.

  • Page 112: G600 And Cmc1 Media Gateways Design

    The ASG Mobile V1.1 window appears. In the Tech ID field, type your login ID, which is the name of the attached file (without the.asg extension). Your login ID is the same as your Avaya login or an abbreviated part of it. NOTE: Your new password will be sent to you in a separate e-mail.
  • Page 113 Hardware configurations S8100 Media Server components and functionality TN2314 processor circuit pack The TN2314 Processor circuit pack is the hardware component of the S8100 Media Server and is the heart of the G600 and CMC1 Media Gateway systems. It uses Microsoft Windows 2000 server as its operating system, allowing for graphical user interaction, network connections, standard applications, and coresidency and multitasking of applications.

  • Page 114: Cmc1 Media Gateway Cabinets

    Hardware configurations S8100 Media Server components and functionality CMC1 Media Gateway cabinets A CMC1 Media Gateway configuration can contain three 10-slot Compact Modular Cabinets (CMC1) which include: • Slots for circuit packs • Power supply Slots Each CMC1 has: • Two shelves, each containing 5 slots •...
  • Page 115 Hardware configurations S8100 Media Server components and functionality Figure 15: S8100 with the CMC1 slot configuration In Use Maj Alarm Min Alarm Clock Service Access Emergency Transfer Auto Complete Shutdown scdmlft3 KLC 071902 Figure notes Circuit pack slots 1 through 5 Power supply Circuit pack slots 6 through 10 PCMCIA hard disk...

  • Page 116: G600 Media Gateway Cabinet

    Hardware configurations S8100 Media Server components and functionality G600 Media Gateway cabinet A G600 configuration can contain two 10-slot rack- or shelf-mounted systems, which include: • Slots for circuit packs • Power supply Slots Each G600 Media Gateway cabinet has: •...

  • Page 117: Ups

    Hardware configurations S8100 Media Server components and functionality Figure 16: G600 Media Gateway (IP600) slot configuration 100bT In Use LINK LINK Maj Alarm TRMT TRMT Min Alarm Clock Service Access Emergency Transfer Auto Complete Shutdown Power scdpff02 KLC 071902 Figure notes Grounding receptacle TN799DP C-LAN 650A Power Supply...

  • Page 118: Circuit Packs

    IP network. The value of the G700 system is that it provides a standards-based, IP communications infrastructure that enables Avaya to lower customers’ total cost of ownership (i.e. applications to the edge of the network, high reliability for critical applications, and multi-service networking with feature transparency).

  • Page 119: Server Initialization, Recovery, And Resets

    Server initialization, recovery, and resets S8700 Initialization Server initialization, recovery, and resets This chapter describes various maintenance aspects of media servers and their troubleshooting, including: • S8700 on page 119 • Shutdown on page 123 • S8100 recovery on page 124 •...

  • Page 120: Active Server's Initialization

    Standby server’s initialization These steps are executed on the standby server: Avaya™ Communication Manager — On the standby server, many processes are frozen so that the Standby DupMgr can shadow into them without interfering with those writes. However, some shadowed and unshadowed processes need to run on the standby. These processes are known as the “run-on-standby”...

  • Page 121: S8100 Initialization

    Server initialization, recovery, and resets S8100 Initialization • tmr_mgr — unshadowed • pcd — shadowed The active server’s PCD shadows into the standby’s PCD, so the standby’s PCD does not to write to shadowed memory. The standby’s PCD handshakes with every administered PN and counts accessible PNs to include in state-of-health reports to the Arbiter.

  • Page 122: Communication Manager Initialization

    Server initialization, recovery, and resets S8100 Initialization Figure 17: TN2314 processor panel In Use Maj Alarm Min Alarm Clock Service Access Emergency Transfer Auto Complete Shutdown ckdf231x KLC 080102 Other circuit packs You might see some LEDs on power up on the other circuit packs. Under normal operation, you should not see LEDs lit on the circuit packs, with the following exception: A solid green LED on any circuit pack indicates that diagnostic tests are in progress on that circuit pack.

  • Page 123: Shutdown

    Server initialization, recovery, and resets S8100 Initialization change system-parameters offer-options Page 1 of OFFER OPTIONS Offer Category: A Activate Offer? y Field descriptions Only Type A is allowed. Offer category Type y if the entry for Offer category is correct Activate offer? and press Type n if there is an error in the Offer category...

  • Page 124: S8100 Recovery

    Typically used for planned shutdown. See Appendix D for shutdown and restart actions and Appendix G for bash commands in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555- 233-146.
  • Page 125 HiMonitor reboots Linux. CAUTION: Escalate to an Avaya engineer for guidance with this recovery, because it is potentially disruptive. A process can legitimately occupy abnormally high amounts of processor time due to server load, and killing it could make the server totally unavailable.
  • Page 126 Watchdog logs a message to syslog and does not start Communication Manager software. Restarts Restart is a traditional Avaya term for a system restart of less severity than a full recreation. Restarts are accomplished by retaining the memory state of certain processes. Maintenance Procedures...

  • Page 127: Communication Manager Resets

    Server initialization, recovery, and resets S8100 Initialization The WatchDog process is not restartable, nor can it invoke restarts in Communication Manager. No Watchdog-started applications can restart. They are reloaded, as previously described. If the Watchdog itself dies, the parent Watchdog process restarts it. If the Watchdog dies 10 times in 2 minutes, init logs a message to Syslog for the GMM to process.

  • Page 128: Recovery From Fatal Errors In The S8100

    Server initialization, recovery, and resets S8100 Initialization Table 45: Communication Manager resets Component Configuration Link to more information High Reliability • IPSV-CTL (Ipserver Interface Control) Maintenance Alarms Reference (555-245-102) Critical Reliability Port Networks Standard Reliability • reset ipserver-interface in Maintenance Commands Reference (555-245-101) High Reliability •...

  • Page 129: Resolving Alarms

    Server initialization, recovery, and resets S8100 Initialization SPE-down mode In the S8100 system, SPE-Down mode refers to the condition in which: • Windows 2000 failed • System firmware still running The firmware will issue an INADS alarm call at 7 minute intervals. If the problem has not been corrected after the first three messages have been issued, the alarm call interval is increased to 45 minutes.

  • Page 130: Link Recovery

    Maintenance Commands Reference (555-245-101). For more information, refer to the manual Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146. Obtaining information from Communication Manager alarms You can use the following Communication Manager commands to obtain more alarm information.

  • Page 131: H.248 Server-To-Gateway Link Recovery

    Server initialization, recovery, and resets Link Recovery H.248 server-to-gateway Link Recovery The H.248 link between an Avaya server running Avaya Communication Manager Software and the Avaya Media Gateway provides the signaling protocol for: • Call setup • Call control (user actions such as Hold, Conference, or Transfer) while the call is in progress •...
  • Page 132 Server initialization, recovery, and resets Link Recovery H.248 Link Recovery processes This section describes the H.248 Link Recovery scenarios and the concurrent call handling and maintenance activities: • General Link Recovery process on page 132 • Call handling during recovery on page 134 •...
  • Page 133 Server initialization, recovery, and resets Link Recovery Table 47: General Link Recovery process Process sequence Description Link failure detected (see Conditions that trigger Link Recovery on page 131) The Primary and Total Search Timers begin running. The gateway attempts to re- establish the H.248 link with original server, which is the first element in the Media Gateway Controller (MGC) list.
  • Page 134 Link recovery unsuccessful Server alarms Expiration of the Link Loss Delay Timer triggers Communication Manager alarm notification. These events and their associated alarm levels are in Table 48, Avaya Communication Manager alarms, on page 134. Table 48: Avaya Communication Manager alarms...
  • Page 135 NOTE: Avaya Communication Manager does not raise an alarm until the Link Loss Delay timer expires. If the link to the original gateway is restored before this timer expires, then no alarm is raised. If the Link Loss Delay Timer expires but the gateway successfully connects with an LSP, Avaya Communication Manager generates a warning alarm anyway, even though the H.248 link is up.
  • Page 136 Server initialization, recovery, and resets Link Recovery In the H.248 MEDIA GATEWAY section type a number (1-30; default is 5) in the Link Loss Delay Timer (minutes) field. This is the number of minutes that Communication Manager retains the gateway’s call state information. NOTE: The value of this timer should be longer than either of the gateway timers (see Administering the gateway timers and Transition Point...
  • Page 137 Server initialization, recovery, and resets Link Recovery NOTE: The Total Search Timer value should be greater than the Primary Search Timer but shorter than the Link Loss Delay Timer. Establish the Transition Point by typing set mgp reset transition-point <n>, where <n> is the numbered element in the MGC list.
  • Page 138 Server initialization, recovery, and resets Link Recovery Table 50: H.248 Link Recovery feature/adjunct interactions Feature or adjunct Description Feature Access Codes (FAC) Feature Access Codes, whether dialed or administered buttons, do not work. Non-IP trunks/stations, including These resources are unavailable until the H.248 link is re- such circuit-switched TDM resources established.

  • Page 139: H.323 Gateway-To-Endpoint Link Recovery

    The Linux command start -ac issued to each LSP will then restart Communication Manager on each of those platforms. H.323 gateway-to-endpoint Link Recovery The H.323 link between an Avaya Media Gateway and an H.323-compliant IP endpoint provides the signaling protocol for •...
  • Page 140 IP endpoints supported All IP endpoints can, but are not required to, support this feature. This includes softphones, IP telephones, and Avaya MVCS. As an example, a sampling of Avaya endpoints are listed below: • Avaya IP Softphone; R5 for Windows 2000 •...
  • Page 141 • MultiVantage Connection Server (MVCS) Version 2.0 and above • Avaya Softconsole R2: firmware version 2.000 and above NOTE: As of this writing, there are no plans for the R2 version of Softconsole. But by the time it becomes available, the iClarity component that actually provides this feature will be available and that is what Softconsole will use.
  • Page 142 Server initialization, recovery, and resets Link Recovery Table 52, Cross-product interactions due to link failure, on page 142 describes the performance interactions due to link failure-induced time delays. Table 52: Cross-product interactions due to link failure Product or adjunct Description Terminals Time-of-Day, busy lamp states, and call appearance status on some sets might not instantaneously reflect the correct information until...
  • Page 143 Server initialization, recovery, and resets Link Recovery During the recovery process, when the IP endpoint is attempting to re-register, the customer will experience some noticeable anomalies in the handling of some features or capabilities: • An IP endpoints will not have dial-tone for a new call. •...
  • Page 144 Server initialization, recovery, and resets Link Recovery These three (3) administrable parameters are explained in Table 53, Administrable H.323 Link Bounce Recovery parameters, on page 145. The Idle Traffic Interval is the period of time between the IP endpoint’s last broadcast Keep-Alive signal and the Gateway’s last acknowledgement as depicted in Figure 19, Idle Traffic Interval, on page 144.
  • Page 145 Server initialization, recovery, and resets Link Recovery Figure 21: Keep-Alive signals not acknowledged by Gateway Figure notes Gateway Keep-Alive Count = 2 IP endpoint Endpoint attempts to re-register with Gateway No Gateway acknowledgement or H.323 link to IP endpoint Table 53, Administrable H.323 Link Bounce Recovery parameters, on page 145 lists the administrable parameters that interact within the H.323 Link Bounce Recovery feature.
  • Page 146 Server initialization, recovery, and resets Link Recovery Table 53: Administrable H.323 Link Bounce Recovery parameters Parameter (device) Definition Primary Search Time (GST) While on-hook, this is the maximum time period that the IP (Endpoint) endpoint expends attempting to register with its current Communication Manager server (Gateway).
  • Page 147 Server initialization, recovery, and resets Link Recovery Table 54: H.323 Link Recovery sequence Process sequence Description The TCP Keep-Alive timer on the C-LAN circuit pack starts (15 minutes). If the signalling link is still down, the H.323 Link Loss Delay Timer begins (Note 2 in Figure 22, H.323 Link Bounce recovery process, on page 148).
  • Page 148 Server initialization, recovery, and resets Link Recovery Figure 22: H.323 Link Bounce recovery process Figure notes Alternate Gateway List Endpoint attempts re-registration while call is in progress H.323 Link Loss Delay Timer Call ends and endpoint continues re- (gateway) registration attempts Primary Search Time Endpoint attempts re-registration to any (endpoint)
  • Page 149 Server initialization, recovery, and resets Link Recovery The three (3) C-LAN entries imply that the IP endpoint has three (3) different interfaces to the Communication Manager server that is hosting the Gateway function. Thus, for the purposes of registration to the Gateway, the IP endpoint can connect to any one of the three (3) C-LANs since all connect to the same Gateway.
  • Page 150 Server initialization, recovery, and resets Link Recovery IP-Options System Parameters display system-parameters ip-options Page 1 of IP-OPTIONS SYSTEM PARAMETERS IP MEDIA PACKET PERFORMANCE THRESHOLDS Roundtrip Propagation Delay (ms) High: 800 Low: 400 Packet Loss (%) High: 40 Low: 15 Ping Test Interval (sec): 20 Number of Pings Per Measurement Interval: 10 RTCP MONITOR SERVER Default Server IP Address:...
  • Page 151 Server initialization, recovery, and resets Link Recovery Table 55: Administrable parameters on IP-Options System Parameters form Parameter Definition H.323 Link Loss Delay Timer This timer specifies how long the Communication Manager server [Used within Gateway] preserves registration and any stable calls that may exist on the endpoint after it has lost the call signaling channel to the endpoint.

  • Page 152: System Resets

    Server initialization, recovery, and resets System resets Table 56: Administrable parameters on IP Network Regions form Parameter Definition Idle Traffic Interval The maximum traffic idle time after which a TCP Keep-Alive (KA) [Endpoint] signal is sent from the endpoint. Keep Alive Interval The time interval between TCP Keep-Alive re-transmissions.

  • Page 153: Reset Level 1 (Warm Restart)

    Server initialization, recovery, and resets System resets Reset Level 1 (Warm Restart) Duration Up to 10 seconds, typically 4 seconds (S8100: 60 seconds) Causes reset system 1 command from Communication Manager (SAT/ASA) command line Spontaneous server interchange (those caused by hardware faults) Software faults that are not service affecting Abort of planned server interchange Effects...

  • Page 154: Reset Level 2 (Cold-2 Restart)

    Server initialization, recovery, and resets System resets Reset Level 2 (Cold-2 Restart) Duration Up to 3.75 minutes (S8100: In a large system, up to 5 minutes) Causes reset system 2 command from Communication Manager (SAT/ASA) command line Escalation from SAT’s reset level 1 An attempted SAT’s reset level 1 during a PNC interchange Spontaneous interchange into an unrefreshed standby server Effects...

  • Page 155: Reset Level 3 (Communication Manager Reboot)

    Server initialization, recovery, and resets System resets Reset Level 3 (Communication Manager reboot) This is the same as Reset Level 4 (see below). This command is retained for consistency with other MultiVantage Applications products. Reset Level 4 Communication Manager reload CAUTION: Reset system 4 leads to an interchange of the system’s servers.

  • Page 156: Reset Level 5 (Extended Communication Manager Reboot)

    Server initialization, recovery, and resets System resets Reset Level 5 (Extended Communication Manager reboot) This is the same as Reset Level 4. This command is retained for consistency with other MultiVantage Applications products. S8100 system reset You can reset the S8100 system from either the web browser interface or the UNIX bash shell from a Telnet session.

  • Page 157: S8300/G700 System Reset

    Server initialization, recovery, and resets System resets S8300/G700 System reset There is no change in how Communication Manager functions for system resets in the S8300 Media Server in a G700 Media Gateway. Although translations may be present for a G700, Communication Manager waits for a link to be established before attempting to access the G700.
  • Page 158 Server initialization, recovery, and resets System resets Maintenance Procedures December 2003...

  • Page 159: Troubleshooting

    While touching any component inside a cabinet, ground yourself using a wrist strap attached to the cabinet’s frame, and avoid sources of static electricity. • When you log on with Avaya Site Administration (ASA), alarm notification is normally disabled. Log off ASA as you leave the system. •...

  • Page 160: Removing And Restoring Embedded Audix Power

    Troubleshooting Safety precautions • Do not power down either a switch-node or port carrier to replace a board. • Handle fiber-optic cables with care. Bending, piercing, or cutting a cable can sever communications between major subsystems. • To disconnect a fiber-optic cable, grasp both the lightwave transceiver and the cable’s connector. •...

  • Page 161: Electrostatic Discharge

    The smallest amount of ESD we can feel is far above the threshold of damage to a sensitive component or service disruption! Figure 23, Wrist-strap jack for ESD grounding (MCC1), on page 162 shows the location of the grounding jack.

  • Page 162: Suppressing Alarm Origination

    Also, while logged in as “craft,” an idle terminal is automatically logged off after 30 minutes. At that time, any unresolved alarms are reported to Avaya’s alarm receiving system. If you are logged in as “craft” at two terminals, the logoff occurs when the second terminal is unused for 30 minutes.

  • Page 163: Troubleshooting Duplicated Servers

    Troubleshooting Troubleshooting duplicated servers Troubleshooting duplicated servers The sections, Server initialization, recovery, and resets on page 119, IPSV-CTL (Ipserver Interface Control), and IP-SVR (IP Server Interface) contain procedures for troubleshooting specific problems with servers and IPSIs. CAUTION: Follow normal escalation procedures before shutting down either an application or the entire system.

  • Page 164: Determining The Time Of A Spontaneous Interchange

    Troubleshooting Troubleshooting trunks with Automatic Circuit Assurance Determining the time of a spontaneous interchange Use display initcauses to tell at what time a spontaneous interchange has taken place. The display initcauses command displays a record of every system reset. In the following example, a spontaneous interchange into Server B took place at 2:53 p.m.

  • Page 165: Trunk Group Busy/Warning Indicators To Attendant

    Troubleshooting Trunk Group Busy/Warning Indicators to attendant Trunk Group Busy/Warning Indicators to attendant An attendant console is required. Trunk Group Busy/Warning Indicators to Attendant provides the console user with a visual indication of the trunk group status for each trunk group associated with the 12 Trunk Group Select buttons located on the console.
  • Page 166 Troubleshooting LA85 port tester Table 57: Port fault isolation using the LA85 port tester To begin the isolation You might need this procedure preliminary information at the... or equipment... And if... Then... Wall field in Use display errors command Off-board Verify wiring from switch to equipment errors indicated...

  • Page 167: Fiber Link Fault Isolation

    Troubleshooting Fiber link fault isolation • N = Not lighted • N/A = Not applicable Table 58: LED indications for the LA85 port tester Port Bl-W Bl-W W-BL Analog DCP (2-wire) MFET MFAT 1 The red LED lights on a reversal. If the analog set contains a polarity guard, the set is still operable.
  • Page 168 Troubleshooting Fiber link fault isolation Complete the following steps: Enter display alarms with category pnc. Are there any on-board alarms? If so, replace the circuit pack(s). Enter display errors for category pnc. Check for any of the following errors: Error Type FIBER-LK SNI-BD...
  • Page 169 Troubleshooting Fiber link fault isolation Error Type SNI’s Slot 2561 2817 3073 3329 3585 3841 (2 of 2) • After replacing an SNI circuit pack, clear alarms by executing test board UUCSS long clear for every alarmed EXP-INTF circuit pack. Wait 5 minutes for any SNI-BD or SNI- PEER alarms to clear.
  • Page 170 Troubleshooting Fiber link fault isolation NOTE: If a fiber out-of-frame condition exists and lightwave transceivers are used, verify that both lightwave transceivers are the same type, (9823a or 9823b). If not, replace one of the transceivers so that they match. [A 9823A supports distances up to 4900 feet (1493 m), and a 9823B supports distances up to 25,000 feet (7620 m).] •...

  • Page 171: Troubleshooting Sni/Ei Links With Manual Loop-Back

    Troubleshooting Fiber link fault isolation Troubleshooting SNI/EI links with manual loop-back NOTE: Do not use this procedure on a connection with a DS1 CONV as an endpoint. Use this procedure to isolate a fault in the cables or lightwave transceivers of an SNI/EI link. By performing the loopback at both endpoints and, if applicable, at the cross-connect field, the failure point can be identified.
  • Page 172 Troubleshooting Fiber link fault isolation Test #242 can be run as part of the test board UUCSS long command for an EI circuit pack. Besides testing on-board components, this test is helpful for isolating problems between a circuit pack and the lightwave transceiver.

  • Page 173: Troubleshooting Atm

    Troubleshooting Troubleshooting ATM Table 59: DS1 interface cable connectors 50-pin 15-pin connector connector Lead Desig. color Color Plug 04 Facility D Line In W-BL W-BL Facility D Line In LID* BL-W BL-W Facility D Line Out Facility D Line Out LOD* Plug 03 Facility C Line In...

  • Page 174: Initial Led Inspection

    Troubleshooting Troubleshooting ATM Figure 26: ATM troubleshooting schematic AX500 Switch PPN Switch EPN ATM call control Q.93B Q.93B CaPro Switch Q.SAAL Q.SAAL processor Switch fabric SONET SONET Fiber Fiber Physical Physical TN2238 TN2238 Port boards iodftrb LJK 020801 NOTE: The CaPro element (Note 1 in Figure 26, ATM troubleshooting schematic, on page 174) is a software module within the S8700 Multi-Connect server.
  • Page 175 Troubleshooting Troubleshooting ATM Table 61, A500 LED Quick Reference, on page 175 shows the various LEDs on the A500 ATM switch and the meanings of the different states. Table 61: A500 LED Quick Reference Component Label Color State Meaning Switch Green Intermitten Normal state.

  • Page 176: A500 Switch Diagnostics

    Troubleshooting Troubleshooting ATM Table 61: A500 LED Quick Reference Component Label Color State Meaning Port Board Green No ATM cells are being received. This is not Per Port a normal state if the terminating PN is supposed to be up and running. Green Intermitten ATM cells are being received intermittently.
  • Page 177 Can you log into the A500 console using the diagnostic account root from the local console terminal or through Telnet? (See Figure 27, A500 login screen, on page 177.) Figure 27: A500 login screen A500 System Console (c) 1997 Avaya Inc. login: root password: XXXXXX ********** New System Alarms **********...

  • Page 178: Atm Administration

    TFTP server, does the TFTP server field have the customer- provided Internet address, as configured using the tftp setserver command? Does the ATM address field have the customer-provided or Avaya-provided network prefix (the first thirteen bytes, set by using the modify atmprefix command)?
  • Page 179 Troubleshooting Troubleshooting ATM Figure 29: Screen output for list atm pnc command list atm pnc Page SPE A ATM PNC A-PNC B-PNC Connection # 01B02 02A01 You can also use list configuration UUC (non-control cabinets) to confirm the PN’s board locations and correct insertion.
  • Page 180 Troubleshooting Troubleshooting ATM Figure 31: Screen output for display circuit-packs 1 display circuit-packs 1 CIRCUIT PACKS Cabinet: Carrier: Cabinet Layout: five-carrier Carrier Type: processor *** PROCESSOR BOARDS NOT ADMINISTERABLE IN THIS SCREEN *** CIRCUIT PACKS Cabinet: Carrier: Cabinet Layout: five-carrier Carrier Type: port Slot Code...
  • Page 181 Troubleshooting Troubleshooting ATM Administered with hard-coded PNNI routes If the PNs are addressed using hard-coded PNNI routes in the A500, the display looks like Figure 33, Screen output for display atm pnc 1, on page 181 (pnc 1) and Figure 34, Screen output for display atm pnc 2, on page 181 (pnc 2).

  • Page 182: A500 Administration

    Troubleshooting Troubleshooting ATM Figure 35: Screen output for display atm pnc 1 with End System Identifiers display atm pnc 1 ATM PNC Connection Number: A - PNC Location: 01B02 Name: Address Format: E.164 ATM Private AFI: E.164: 0001013035381053 HO-DSP: 00000000 ESI: 000000000011 SEL:...
  • Page 183 Troubleshooting Troubleshooting ATM Figure 37: Screen output for the show signaling summary command A500:show signaling summary Port loc VCI IntType Signaling ILMI SAP State State ------ ------- ------- ----------- ---- ------------ ----- A1.1 Network UNI3.1 A1.2 Network UNI3.1 a If an A500 port with an attached S8700 Multi-Connect PN is not listed in this display, it is likely that the port was administered incorrectly as having no UNI signaling (admin link command).
  • Page 184 Troubleshooting Troubleshooting ATM If the A500 was administered using End System Identifiers, enter show signaling esi on the A500 console. Figure 39, Screen output A500: show signaling esi command, on page 184 shows the command output. Figure 39: Screen output A500: show signaling esi command A500:show signaling esi Addresses registered on A1.1 ----------------------------...
  • Page 185 Troubleshooting Troubleshooting ATM Figure 40: A500 screen output for show sys interfaces command Device Oper Admin State Type Status Status _________________________________________________________________ A1.1 present STS_3c (MultiMode) A1.2 present STS_3c (MultiMode) A1.3 down down present STS_3c (MultiMode) A1.4 down down present STS_3c (MultiMode) A1.5 down down...

  • Page 186: Tn230X Circuit Pack(S)

    Troubleshooting Troubleshooting ATM TN230X circuit pack(s) Did the TN230X come up correctly? Review the LED conditions for the TN230X: • Do the TN230X LEDs (see Table 60 on page 174) indicate a normal operational state (any of the following): — Archangel mode in the PN —...
  • Page 187 Troubleshooting Troubleshooting ATM Figure 42: List configuration carrier 2a screen list configuration carrier 2a SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 02A01 ATM PNC EI TN2305 000001 02A09 DS1 INTERFACE TN767E 000004 02A10 DIGITAL LINE TN754B 000016 02A11...

  • Page 188: Physical Layer

    Troubleshooting Troubleshooting ATM Figure 44: Screen output for the test board 2a01 command test board 2a01 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 02A01 ATM-EI PASS 02A01 ATM-EI PASS 02A01 ATM-EI 1258 PASS 02A01 ATM-EI PASS 02A01 ATM-EI...
  • Page 189 Troubleshooting Troubleshooting ATM Ensure that the fields have the following indicated values. SAP State If it is PHY_DOWN or DOWN, there may be a loss of signal on the port in question. This command detects a continuity problem only with the Receive (right-hand) fiber. It does not detect the state of the Transmit (left-hand) fiber.

  • Page 190: Sonet Layer

    Troubleshooting Troubleshooting ATM Oper Status should be up. If it is down, there is likely a loss of signal on the port in question (State of present), or the A500 does not recognize the port board (State of invalid). This command detects a continuity problem only with the Receive (right-hand) fiber; it does not detect the state of the Transmit (left-hand) fiber.

  • Page 191: Q.saal (Data Link) Layer

    Troubleshooting Troubleshooting ATM Figure 47: A500: show stats sonet a1.2 screen Sonet per-Port Statistics --------------------------------- Receive Cell Count: 80654 Transmit Cell Count: 79555 Section Level Bit Err: Line Bit Err: Line FEB Err: Path Bit Err: Path FEB Err: Correctable HCS Err: Uncorrectable HCS Err: Loss of Frame Err: Loss of Signal Err:...

  • Page 192: Q.93B (Network) Layer

    Troubleshooting Troubleshooting ATM Figure 48: A500: show signaling stats a1.2 qsaal screen A500: show signaling stats a1.2 qsaal ------------------------Q.SAAL Statistics------------------------ Port A1.2: ---------- Type: UNI3.1 VPI: 0x00, VCI: 0x05 -------- -------- BGN PDUs: BGAK PDUs: END PDUs: ENDAK PDUs: RS PDUs: RSAK PDUs: BGREJ PDUs: SD PDUs:...
  • Page 193 Troubleshooting Troubleshooting ATM Figure 49: A500:show signaling stats A1.2 q93b A500:show signaling stats a1.2 q93b -------------------------Q.93B Statistics------------------------ Port A1.2: ---------- -------- -------- Connect Messages: Setup Messages: Release Messages: Rel Cmplt Messages: Add Party Messages: Add Party Acks: Add Party Rejects: Drop Party Messages: Drop Party Acks: Last Cause Code:...
  • Page 194 Troubleshooting Troubleshooting ATM Figure 50: A500:show signaling cause 31 A500:show signaling cause 31 Cause 31: Normal, unspecified At the S8700 Multi-Connect SAT type display errors, and press Enter Set the Error List to errors and Category to PNC on the input screen (Figure 51, S8700 Multi-Connect display errors input screen, on page 194), and press...

  • Page 195: Atm Call Control

    Troubleshooting Troubleshooting ATM Figure 52: Screen output for display errors command display errors Page SPE A HARDWARE ERROR REPORT Port Mtce First Last Err Err Rt/ Al Ac Name Name Type Data Occur Occur Cnt Rt Hr AT01A ATM-NTWK 11/12/16:59 12/09/15:10 14 0 AT01A ATM-NTWK 11/13/18:27 11/20/20:02 5...

  • Page 196: Capro Layer

    Troubleshooting Troubleshooting ATM Figure 53: A500: show switch circuit table screen A500:show switch circuit table _______________________________________________________ Input Output Connection | port vpi vci| port vpi vci| type class parameters |______________|______________|_________________________| A1.1 Self ppd on A1.1 A1.2 VBRnrt pcr=5729 /scr=5729 /mbs=17187 A1.1 A1.2 pcr=173...
  • Page 197 Troubleshooting Troubleshooting ATM Figure 54: List sys-link screen list sys-link SYSTEM LINKS INFORMATION Location Link Type/ State Current Faulted Last Fault Channel Path Path Recorded 02A0101 present present 12/06/1997 16:20 01B0202 PACL present present 12/06/1997 16:17 02A0102 PACL present present 12/06/1997 16:20 Ensure that the fields have the following indicated values.
  • Page 198 Troubleshooting Troubleshooting ATM Are talk paths being established between PNs? Diagnostics • Can you talk both ways on a set on one PN dialed from another PN, and vice versa? Enter show switch circuit on the A500 console. Figure 56, A500:show switch circuit screen, page 198 shows the screen output.

  • Page 199: Unusual Atm Trouble Conditions

    Troubleshooting Troubleshooting ATM Unusual ATM trouble conditions There are a few failure modes in the S8700 Multi-Connect/A500 combination that are particularly difficult to diagnose. One example might be that you can’t make a completely successful call, even though most indications from S8700 Multi-Connect and the A500 look pretty good. This section documents some hints and clues that may help diagnose the following failure modes: •...
  • Page 200 Troubleshooting Troubleshooting ATM Action Correct the ATM addresses (or swap fibers) on the A500 between the incorrectly connected PPN and PN. Swapped Routes, End System Identifiers, or Fiber between two PNs Symptoms • Every TN230X completes board insertion. • The PPN cold starts both incorrectly connected PNs as usual. •...

  • Page 201: Troubleshooting Multimedia Call Handling (Mmch)

    Troubleshooting Troubleshooting Multimedia Call Handling (MMCH) Troubleshooting Multimedia Call Handling (MMCH) Expansion Services Module An Expansion Services Module (ESM) provides T.120 data sharing capability on a MMCH multipoint H.320 video conference. Each conference participant must have endpoints administered and a personal computer with the H.320 video application installed.
  • Page 202 For calls that are routed in the network through an Avaya/LEC interface, the originating equipment may launch a 64-kbps call attempt, and the far end receives either a 56- or 64-kbps indication. If the far end receives a 64-kbps indication, the call may have used 56-kbps facilities.
  • Page 203 Troubleshooting Troubleshooting Multimedia Call Handling (MMCH) Some parties cannot be heard by others (audio subsetting) Description Problems where varying subsets of the conference hear different things may have problems with the various summing resources/groups that are in use. Traditionally, these faults are caused by the server not cleaning up the connections properly.
  • Page 204 Depending on the type of endpoint, this can cause the endpoint to disconnect or just freeze video until the main problem is resolved. Specifically, PictureTel System 4000 endpoints seem to be the most sensitive to instability. The Avaya Vistium disconnects fairly infrequently. The CLI Rembrandt II VP freezes video and waits for framing to be recovered.
  • Page 205 Troubleshooting Troubleshooting Multimedia Call Handling (MMCH) Voice-activated switching problems Voice-activated switching on the S8700 Media Server Multimedia Call Handler (MMCH) does not follow the loudest talker. The MMCH queues every speaking party and selects a new video broadcaster (the second-oldest speaking party) when the oldest speaking party has stopped talking. The new broadcaster will see the last speaker as its video.
  • Page 206 Table 63: Audio echo troubleshooting Situation Problem Action For some Avaya Vistium Endpoint causes audio Isolate the offending endpoint by endpoints, an external speaker may echo throughout the...

  • Page 207: Troubleshooting Isdn-Pri

    Troubleshooting Troubleshooting ISDN-PRI When a downgrade does occur, information on the Status Conference screen indicates the success or failure of the 64-kbps endpoints that are participants to properly rate adapt to 56 kbps. As a general indication that the conference has rate adapted, the Conference Transfer Rate and Effective Transfer Rate fields show initial and current transfer rates, respectively.
  • Page 208 Troubleshooting Troubleshooting ISDN-PRI Figure 58: Troubleshooting ISDN-PRI (Page 1 of 2) START ARE THERE DETERMINE PRESENT STATUS ALARMS OR ERRORS OF DS-1 FACILITYVIA UDS1-BD AGAINST UDS1-BD OR OR DS1-BD MO SECTION. DS1-BD FOLLOW REPAIR PROCEDURES IF MULITPLE ALARMS EXIST, ARE THERE INVESTIGATE IN FOLLOWING ALARMS OR ORDER:...

  • Page 209: Troubleshooting Isdn-Pri Endpoints (Wideband)

    Troubleshooting Troubleshooting ISDN-PRI endpoints (wideband) Figure 59: Troubleshooting ISDN-PRI (Page 2 of 2) COMPARE INDICATED FROM FACILITY TO RECORD PAGE OF PREVIOUS PROBLEMS PERFORM AN IN-DEPTH ANALYSIS OF T1 FACILITY INCLUDING: TRANSMISSION FACILITY, EXTERNAL EQUIPMENT THERE ARE BIT (DACS, CSUs, ETC.) TRANSIENT ERRORS OCCURRING AND ANY OTHER...
  • Page 210 Troubleshooting Troubleshooting ISDN-PRI endpoints (wideband) This troubleshooting procedure is limited to diagnosing faults between the switch and either the ISDN- PRI’s: • Line-side terminal adapter • Endpoint equipment Problems encountered on the network side of a wideband connection or problems with end-to-end equipment compatibility are beyond the scope of this section.
  • Page 211 Troubleshooting Troubleshooting ISDN-PRI endpoints (wideband) Figure 60: Processing of PRI endpoint problems (page 1 of 2) START Are there alarms or FOLLOW REPAIR PROCEDURE errors against IN THE DS1-BD MO SECTION DS1-BD? Are there IF MULTIPLE ALARMS EXIST, alarms or INVESTIGATE IN THE errors against FOLLOWING ORDER: PI-BD,...

  • Page 212: Troubleshooting Isdn-Bri / Asai

    Troubleshooting Troubleshooting ISDN-BRI / ASAI Figure 61: Processing of PRI endpoint problems (page 1 of 2) FROM PAGE 1 Does every TRANSIENT FAILURES ALWAYS FAIL call fail or are the failings transient? CHECK THE HEALTH OF THE Are there APPLICATION EQUIPMENT bit errors (FOR EXAMPLE, VIDEO CODEC) Perform an in-depth...
  • Page 213 Troubleshooting Troubleshooting ISDN-BRI / ASAI Figure 62: ISDN-BRI/packet-bus connectivity Duplicated Duplicated Only Only Testing/ Testing/ Reconfig Reconfig Packet Bus Packet Bus Signaling Signaling Links Links Signaling Links BRI-PT ABRI-PT BRI-PT ABRI-PT ASAI-ADJ ASAI-ADJ The flowchart in Figure 63, Troubleshooting ISDN-BRI problems (Page 1 of 2), on page 214 describes the steps needed to isolate and resolve an ISDN-BRI problem.
  • Page 214 Troubleshooting Troubleshooting ISDN-BRI / ASAI Figure 63: Troubleshooting ISDN-BRI problems (Page 1 of 2) START ARE THERE ALARMS OR ERRORS AGAINST PKT-BUS IS THIS A ARE THERE FOLLOW THE CRITICAL RELIABILITY ALARMS OR REPAIR SYSTEM? ERRORS AGAINST PROCEDURE (DUPLICATED PNC) M/T-PKT FOR M/T-PKT IS THE...

  • Page 215: Troubleshooting Isdn-Pri Test Calls

    Troubleshooting Troubleshooting ISDN-PRI test calls Figure 64: Troubleshooting ISDN-BRI problems (Page 2 of 2) FROM FROM PAGE PAGE IS THE FOLLOW THE PROBLEM AFFECTING REPAIR MOs ON MULTIPLE PROCEDURE BRI-BD CIRCUIT FOR PKT-BUS PACKS * IS THE FOLLOW THE PROBLEM AFFECTING REPAIR MULTIPLE MOs ON PROCEDURE...

  • Page 216: Synchronous Method

    Troubleshooting Troubleshooting ISDN-PRI test calls NOTE: Before attempting to make an ISDN-PRI test call to the public network (the far end), make sure that test call service is provisioned by the network. The user must subscribe to Test Type 108 service and have the correct far-end test call number administered on the Trunk Group screen for the call to be allowed.
  • Page 217 Troubleshooting Troubleshooting ISDN-PRI test calls To initiate an outgoing ISDN-PRI test call with the asynchronous method, issue the start command listed above, which enables you to specify a specific the trunk on which to originate the ISDN-PRI test call. An optional qualifier can be used that specifies in minutes (1 to 120) the duration of the test call.

  • Page 218: Troubleshooting The Outgoing Isdn-Testcall Command

    Troubleshooting Troubleshooting the outgoing ISDN-testcall command Troubleshooting the outgoing ISDN-testcall command If the TestCall BCC field appears on the Trunk Group screen, ensure that the TestCall BCC field indicates the correct BCC for the service provisioned on the ISDN-PRI trunk. The TestCall BCC values are defined as follows: Voice Digital Communications Protocol Mode 1...

  • Page 219: Packet And Serial Bus Maintenance

    Packet and serial bus maintenance Isolating and repairing packet-bus faults Packet and serial bus maintenance The topics covered in this chapter include: • Isolating and repairing packet-bus faults on page 219 • S8100 packet bus fault isolation and repair on page 245 •...

  • Page 220: Remote Versus On-Site Maintenance

    Packet and serial bus maintenance Isolating and repairing packet-bus faults • Packet bus fault isolation flowchart on page 234 is the starting point for the troubleshooting process. It is used to determine whether a failure of service is caused by the packet bus itself or by another MO on the packet bus.

  • Page 221: Packet-Bus Faults

    Packet and serial bus maintenance Isolating and repairing packet-bus faults The packet bus carries various types of information: • Signaling and data traffic destined for other port networks and/or Center Stage Switches (CSSs) through the TN570 Expansion Interface circuit pack access. •...

  • Page 222: Circuit Packs That Use The Packet Bus

    Packet and serial bus maintenance Isolating and repairing packet-bus faults • TN556 ISDN-BRI: — BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) — BRI-PORT (ISDN-BRI Port) ABRI-PORT (ASAI ISDN-BRI Port) — BRI-SET, BRI-DAT, Various Adjuncts • TN464F Universal DS1: — UDS1-BD (UDS1 Interface Circuit Pack) —...

  • Page 223: Effects Of Circuit-Pack Failures On The Packet Bus

    Packet and serial bus maintenance Isolating and repairing packet-bus faults NOTE: Every Maintenance/Test circuit pack must be of vintage TN771D or later. This circuit pack is also used for ISDN-PRI trunk testing (M/T-DIG) and ATMS trunk testing (M/T- ANL). Effects of circuit-pack failures on the packet Certain faults of any of the previous circuit packs can disrupt traffic on the packet bus.

  • Page 224: Packet Bus Maintenance

    Packet and serial bus maintenance Isolating and repairing packet-bus faults TN771D Maintenance/Test — A Maintenance/Test board’s fault may either: — Falsely indicate a packet-bus fault — Cause the inability to detect such a fault If the test board’s fault is on its packet-bus interface, the packet bus may also be alarmed. Failure of any circuit pack’s bus interface may alarm the packet bus due to shorting of packet-bus leads.
  • Page 225 Packet and serial bus maintenance Isolating and repairing packet-bus faults System response varies according by type of bus failure and whether or not the failure occurs in a: • PN controlled by an IPSI-connected PN In such a PN, a catastrophic TDM bus failure (one that affects both TDM buses) disables all traffic in the PN.

  • Page 226: General Fault Correction Procedures

    Packet and serial bus maintenance Isolating and repairing packet-bus faults These interactions allow normal non-packet system traffic to continue unaffected, and they reduce the number of entries into the error/alarm logs. If the packet bus failure is caused by a failed circuit pack, errors against the circuit pack should appear in the error/alarm logs as an aid for fault isolation.
  • Page 227 Packet and serial bus maintenance Isolating and repairing packet-bus faults The analog trunk testing functions are discussed in the following sections in: • TIE-TRK (Analog Tie Trunk) • DID-TRK (Direct Inward Dial Trunk) • AUX-TRK (Auxiliary Trunk) NOTE: Every Maintenance/Test circuit pack must be of TN771D vintage or later. TN771D packet bus testing functions The Maintenance/Test packet-bus port (M/T-PKT) provides the packet-bus testing and reconfiguration capabilities.
  • Page 228 Packet and serial bus maintenance Isolating and repairing packet-bus faults TN771D in stand-alone mode In TN771D stand-alone mode, a terminal is connected to the Maintenance/Test circuit pack with an Amphenol connector behind the cabinet. This setup allows direct inspection of the packet bus and identifies shorted or open leads.
  • Page 229 Packet and serial bus maintenance Isolating and repairing packet-bus faults Entering and exiting stand-alone mode While in stand-alone mode, the TN771D’s red LED is lit. This is normal and serves as a reminder to remove the TN771D from stand-alone mode. CAUTION: A TN771D in stand-alone mode must be the only TN771D in the PN.
  • Page 230 Packet and serial bus maintenance Isolating and repairing packet-bus faults Figure 66: Stand-alone mode confirmed TN771 STAND-ALONE MODE (Type “?” at the prompt for help) Command: NOTE: If the previous display does not appear, check the wiring between the terminal and the TN771D, and the terminal parameters settings.
  • Page 231 Packet and serial bus maintenance Isolating and repairing packet-bus faults Figure 67: Stand-alone mode display L L L L L L L L L L H H H H H H H H H H S S S L P 0 1 2 3 4 5 6 7 8 P 0 1 2 3 4 5 6 7 8 S F B F _______________________________________________ Command: •...
  • Page 232 Packet and serial bus maintenance Isolating and repairing packet-bus faults Figure 68: Packet bus leads on the backplane (front view) Front View Backplane Separation Maintenance Procedures December 2003...
  • Page 233 Packet and serial bus maintenance Isolating and repairing packet-bus faults Figure 69, Packet bus leads on the backplane (rear view), on page 233 shows the location of the packet bus leads for a given slot as seen from the front and back of the carrier. Figure 69: Packet bus leads on the backplane (rear view) Back View Maintenance Procedures...

  • Page 234: Packet Bus Fault Isolation Flowchart

    Packet and serial bus maintenance Isolating and repairing packet-bus faults Special precaution concerning the TN771D A TN771D Maintenance/Test circuit pack must be taken to the customer site if: • The Maintenance/Test packet-bus port indicates that a packet-bus fault is present by logging a major or minor alarm against PKT-BUS.
  • Page 235 Packet and serial bus maintenance Isolating and repairing packet-bus faults the flowchart at the step that follows the reference to repair procedures and continue from there. The following status commands can also help diagnose packet-bus problems, especially when logged in remotely.
  • Page 236 Packet and serial bus maintenance Isolating and repairing packet-bus faults NOTE: Bold-face letters in the flowchart are explained in Flowchart notes on page 236. Figure 71: Troubleshooting packet-bus problems (2 of 2) From page Is a Are there Follow the repair TN771 present alarms or errors procedure for...
  • Page 237 Packet and serial bus maintenance Isolating and repairing packet-bus faults Problems with the system clock (TDM-CLK) can cause service disruptions on the packet bus. Every alarm active against TDM-CLK should be resolved first, even if the explanation refers only to TDM bus. A packet-bus problem cannot cause a TDM-CLK problem, but a TDM-CLK problem can cause a packet-bus problem.
  • Page 238 Packet and serial bus maintenance Isolating and repairing packet-bus faults Investigate errors and alarms in the following order: Circuit-pack level Ports Endpoints Follow the Troubleshooting procedures on page 239. If the packet-bus problem cannot be resolved with these procedures, follow normal escalation procedures. Correcting packet-bus faults Status port-network command Status port-network P displays include the service state, alarm status, and (if the Maintenance/Test...

  • Page 239: Troubleshooting Procedures

    Packet and serial bus maintenance Isolating and repairing packet-bus faults S8700 only Considerations for duplicated systems Some packet bus-related components are duplicated in systems with one of the duplication options: • In standard or high-reliability systems (duplicated server, nonduplicated PNC): —...
  • Page 240 Packet and serial bus maintenance Isolating and repairing packet-bus faults CAUTION: Packet-bus fault isolation procedures involve removing circuit packs and possibly disconnecting entire carriers. These procedures are destructive. Whenever possible, implement these procedures during hours of minimum system use. To replace the following circuit packs, follow instructions in the appropriate sections: •...
  • Page 241 Packet and serial bus maintenance Isolating and repairing packet-bus faults Table 64: Packet circuit packs Circuit Pack Name Code Associated maintenance objects Universal DS1 TN464F UDS1-BD, ISDN-LNK IP Server Interface TN2312A PKT-INT (IPSI) Expansion Interface TN570 EXP-INTF Procedure 2: removing and reinserting port circuit packs Procedure 2 removes and reinserts port circuit packs (purple slots) and the EI circuit pack one or several at a time.
  • Page 242 Packet and serial bus maintenance Isolating and repairing packet-bus faults If the packet-bus fault is still present: a Determine whether the backplane pins in the removed circuit pack’s slot are bent using the output from the Maintenance/Test circuit pack’s stand-alone mode and the backplane illustrations that appear earlier in this discussion.

  • Page 243: Systems With Nonduplicated Spes

    Packet and serial bus maintenance Isolating and repairing packet-bus faults S8700 only Systems with nonduplicated SPEs Power down the control carrier. Remove the suspected circuit pack. Determine whether the backplane pins in the removed circuit pack’s slot are bent. If the backplane pins are bent: a Straighten or replace the pins.
  • Page 244 (see Figure 72, Carrier rewiring example—rear view of MCC1, on page 244). When the length of the packet bus is modified with this procedure, circuit packs that are essential to system operation (and the TN771D Maintenance/Test circuit pack in stand-alone mode) must still be connected to the new ‘shortened’...

  • Page 245: S8100 Packet Bus Fault Isolation And Repair

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair Procedure 4 consists of two parts. Part 1 on page 245 attempts to clear the packet-bus fault by replacing every bus cable and terminator within a PN. Part 2 on page 245 attempts to isolate the fault to a particular carrier by extending the packet bus from the control carrier to additional carriers one at a time.

  • Page 246: Remote Versus On-Site Maintenance

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair This chapter is organized into several sections that provide introductory information, as well as packet bus fault isolation and correction procedures. The sections of the chapter are as follows: •...

  • Page 247: Tools For Packet Bus Maintenance

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair The Maintenance/Test Packet Bus port (described in detail later in this chapter) can give the remote technician information about the state of the packet bus. This information can be obtained with the status system command and via the PKT-BUS test sequence.

  • Page 248: Circuit Packs That Use The Packet Bus

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair • Opens. An open occurs when there is a break on the packet bus such that the electrical path to the termination resistors is broken. Usually, this break is caused by a failed TDM/LAN cable or by a failed TDM/LAN terminator.
  • Page 249 Packet and serial bus maintenance S8100 packet bus fault isolation and repair around a small number of failed leads. The TN771D circuit pack provides a standalone mode (that is, one that does not involve communication with the SPE) for inspecting the packet bus for faults. This is a critical tool for the packet bus fault correction procedures, which are described later.

  • Page 250: Packet Bus Maintenance

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair However, if an ISDN-BRI circuit pack fails such that it transmits bad data, all devices connected to the circuit pack fail to function. This failure may also disrupt the entire Packet Bus whenever the circuit pack tries to transmit data.
  • Page 251 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Packet bus maintenance software Packet Bus maintenance software involves the traditional set of error conditions, tests, and alarms relevant to Packet Bus faults. These are described in PKT-BUS (Packet Bus - S8100) in Maintenance Alarms Reference (555-245-102) and they are similar in design to the maintenance strategy for most maintenance objects.

  • Page 252: Maintenance/Test Circuit Pack (Tn771D)

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair If the Packet Bus problem still exists, port circuit packs (those in the purple slots) are removed to look for circuit pack(s) that have failed and/or have damaged the Packet Bus pins (a diagram of the backplane pins is provided later).
  • Page 253 Packet and serial bus maintenance S8100 packet bus fault isolation and repair In normal switch operation, the Maintenance/Test provides the visual feedback of the Packet Bus state. When standalone mode (described in the next section) is in effect, these visual indications are still provided;...
  • Page 254 Packet and serial bus maintenance S8100 packet bus fault isolation and repair It is preferable that the slot chosen is in the A carrier if a free slot that matches the criteria presented in the first two items of information in this list is available. Entering and exiting standalone mode NOTE: When in standalone mode, the red LED on the TN771 is lit.
  • Page 255 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Figure 73: Normal standalone mode display TN771 STANDALONE MODE (Type "?" at the prompt for help) Command: CAUTION: If the display in Figure 73, Normal standalone mode display, on page 255 does not appear, be sure to check the wiring between the terminal and the TN771, and also the terminal parameters.
  • Page 256 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Figure 74: Example standalone mode display _ ____________________________________________________________________________________________________ Command: The information within a standalone mode display is used in the Packet Bus Fault Correction procedures that follow. The TN771 display indicates the specific leads on the backplane to examine for bent or damaged pins.
  • Page 257 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Figure 75: Packet bus leads on the backplane (front) SLOT XXX ....
  • Page 258 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Figure 76: Packet bus leads on the backplane (back) SLOT XXX ....

  • Page 259: Packet Bus Fault Isolation Flowchart

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair • Maintenance/Test Packet Bus port indicates that a Packet Bus fault is present. NOTE: Such a fault is indicated by a Major or Minor alarm against the Packet Bus. A Major alarm is indicated in the error log by Error Type 513, while a Minor alarm is indicated by Error Type 2049.
  • Page 260 Packet and serial bus maintenance S8100 packet bus fault isolation and repair NOTE: The following status commands can also help diagnose Packet Bus problems: • status system • status packet-control • status bri-port • status station • status data-module For a description of these commands, refer to Maintenance Commands Reference (555-245-101). The commands provide information about the service state of various Packet maintenance objects.
  • Page 261 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Figure 77: Packet bus fault isolation flowchart (1 of 2) Refer to Is packet "maintenance related bus use START system parameters enabled? form" in chapter 5 Are the Follow the repair Are there packet bus...
  • Page 262 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Figure 78: Packet bus fault isolation flowchart (2 of 2 From page Is a Are there Follow the repair TN771 present alarms or errors procedure for in this port against M/T-PKT network?
  • Page 263 Packet and serial bus maintenance S8100 packet bus fault isolation and repair The following paragraphs supplement the corresponding letter in the flowchart. Problems with the system clock (TDM-CLK) can cause service disruptions on the Packet Bus as well as on the TDM Bus. Therefore, if there are alarms active against TDM-CLK, these alarms should be resolved before any other Packet Bus fault isolation is attempted.

  • Page 264: S8100 Packet Bus Fault Correction

    Packet and serial bus maintenance S8100 packet bus fault isolation and repair The answer is ‘‘Yes’’ if the TN771 in standalone mode indicates any faulty leads. The answer is also ‘‘Yes’’ if Test #572 in the PKT-BUS test sequence fails, and/or if the status system display indicates that faulty leads are present and the TN771 in the port network is known to be functioning correctly.
  • Page 265 Packet and serial bus maintenance S8100 packet bus fault isolation and repair indicated in this case because the TN771 is not defective. Refer to CARR-POW (Carrier Power Supply) maintenance in Maintenance Alarms Reference (555-245-102), and ensure that a -5 volt power supply is available.
  • Page 266 Packet and serial bus maintenance S8100 packet bus fault isolation and repair Table 65: Packet bus circuit packs Circuit Pack Circuit Pack Name Code Associated Maintenance Objects ISDN-BRI TN556 BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, ASAI-ADJ Maintenance/Test TN771 M/T-BD, M/T-PKT For each circuit pack type (see Table 65, Packet bus circuit packs, on page 266), perform the following steps:...
  • Page 267 Packet and serial bus maintenance S8100 packet bus fault isolation and repair If the Packet Bus problem is present when the circuit pack is inserted, but is resolved when the circuit pack is removed, either the circuit pack or the backplane pins in that slot caused the problem. If the backplane pins are intact, replace the circuit pack.
  • Page 268 Packet and serial bus maintenance S8100 packet bus fault isolation and repair If the Packet Bus fault is not present, do the following: a Reinsert a circuit pack. If multiple circuit packs have been removed, reinsert the circuit packs one at a time, and repeat the following substeps until all of the circuit packs have been reinserted.
  • Page 269 Packet and serial bus maintenance S8100 packet bus fault isolation and repair If the Packet Bus fault does not recur, the procedure is completed. If Procedure 3 fails to identify the cause of the problem, go to Procedure 4. In a High or Critical Reliability System, do the following: High or Critical Reliability only If the circuit pack to be replaced is in the SPE, perform an SPE interchange by entering the reset system interchange command.
  • Page 270 Packet and serial bus maintenance S8100 packet bus fault isolation and repair WARNING: Power must be removed from the entire port network before any cables or terminators are removed. Failure to do so can cause damage to circuit packs and power supplies and can be hazardous to the technician.

  • Page 271: G650 Serial Bus Fault Detection And Isolation

    Packet and serial bus maintenance G650 Serial Bus fault detection and isolation Determine if the Packet Bus fault is still present. If so, and if there are shorts on the Packet Bus, perform Procedure 2 and/or Procedure 3 for only the circuit packs in those carriers that are connected to the ‘‘shortened’’...
  • Page 272 Packet and serial bus maintenance G650 Serial Bus fault detection and isolation Figure 80: TDM/LAN bus connection to the Serial Bus Serial Bus faults can be caused by • A defective circuit pack connected to the inserted into one of the G650 slots. •...

  • Page 273: Procedure 1

    Packet and serial bus maintenance G650 Serial Bus fault detection and isolation Procedure 1 This procedure removes and reinserts port circuit packs (those in the purple slots) one or more at a time. Use this procedure for each port circuit pack in the port network until the problem is resolved or until all circuit packs in the port network have been tried.
  • Page 274 Packet and serial bus maintenance G650 Serial Bus fault detection and isolation cable assemblies and TDM/LAN bus terminators are replaced. If this action does not resolve the Serial Bus fault, the carriers are reconfigured so that certain carriers are disconnected from the Serial Bus. This is done by moving the TDM/LAN bus terminators (AHF110) on the carrier backplane.

  • Page 275: Component Replacement

    — Replacing Media Modules on page 299 — Replacing Avaya Expansion Modules on page 301 — Replacing an Avaya Octaplane Stacking Module on page 302 • S8500 component maintenance on page 302 — Replacing the S8500 hard drive on page 303 —...

  • Page 276: Replacing Variable-Speed Fans

    Component replacement Variable-speed fans Alarm leads from each fan are tied together into a single lead that registers a minor alarm against CABINET whenever a fan’s speed drops below a preset limit or fails altogether. NOTE: The front fans may run at a different speed than the rear fans since they are controlled by different sensors.

  • Page 277: Replacing The Temperature Sensor

    Component replacement Reseating and replacing circuit packs Disconnect cabinet local cable connector J2F from the P2F connector on top of the power filter. Disconnect cable connector J2 from the P2 connector on the fan assembly. Loosen the power filter mounting screws using a 5/16” nut driver and remove the filter. CAUTION: Failure to connect the J2 connector on the fan assembly can damage the fan alarm circuits.

  • Page 278: Special Procedures

    IP-SVR (IP Server Interface) If the IPSI has a static IP address, refer to the “Reusing a TN2312AP circuit pack” section in Installing the Avaya S8700 Media Server with an Avaya G650 Media Gateway, 555-245-109 for reseating and replacement procedures.
  • Page 279 Component replacement S8100 component maintenance The procedures for unseating, reseating, and replacing control circuit packs vary depending on the system configuration. Therefore, before performing these maintenance activities, refer to the appropriate procedure below. Control circuit packs To unseat a control circuit pack Remove power from the PPN using the procedure provided in Hardware shutdown on page 394.
  • Page 280 Component replacement S8100 component maintenance Save translations Connect the laptop to the S8100. Click Start > Run. Type telnet name in the dialog box, where name is the local name of your TN2314 system processor. In the Enter your login name dialog box, type lucent1, lucent2, or lucent3, and click OK. In the Enter password dialog box, type the appropriate password for the login used, and click A LAC prompt displays (LAC>).

  • Page 281: Replacing Fans And Air Filters (Cmc1)

    Component replacement S8100 component maintenance Check for proper operation • Alarms • Trunk status • INTUITY functionality Replacing fans and air filters (CMC1) Air filters on the CMC1 should be inspected annually. (See Table 67, Inspecting air filters, on page 281.) Table 67: Inspecting air filters Then Filter is dirty or clogged...

  • Page 282: Fan Assembly Removal/Replacement

    Component replacement S8100 component maintenance Figure 81: Fan/filter removal Filter scdmfltr RPY 072297 Fan assembly removal/replacement Pull (unplug) the fan assembly from the chassis. The power for the fan automatically disconnects when the assembly is unplugged. Plug in the new fan assembly. The power for the fan automatically connects when the fan assembly is plugged in.
  • Page 283 For information about how to start a web browser, see the procedure, “Via a Web Browser Session” in Chapter 2, “Connectivity and Access” in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146.
  • Page 284 Component replacement S8100 component maintenance Click OK. Click the Continue button. click on the Backup & Restore link (under System Maintenance). Click on the Immediate Backup link. Select the desired items for immediate backup (i.e., Communication Manager translation files; INTUITY translations, names, and messages). Verify that the backup destination shows pcmcia.

  • Page 285: S8100 Fan/Filter Removal/Replacement

    Verify that the load of software on the hard drive matches that on the customer’s CD. If it does not match, follow the Update Software procedure in Installation and Upgrades for the Avaya S8100 Media Server with the Avaya G600 and CMC1 Media Gateways, 555-233-146.
  • Page 286 Component replacement S8100 component maintenance Figure 82: S8100 fan/filter removal Filter scdmfltr RPY 072297 Removing or replacing the S8100 fan assembly Pull (unplug) the fan assembly from the chassis using the thumb/finger notch provided. The power for the fan automatically disconnects when the assembly is unplugged. Plug in the new fan assembly.

  • Page 287: S8300 And G700 Component Maintenance

    S8300 and G700 component maintenance Maintenance of the G700 Media Gateway components is performed by resident software. Components not maintained by the resident software, such as Media Modules, are maintained by Avaya Communication Manager in a manner similar to their DEFINITY server counterparts.

  • Page 288: Processors

    Component replacement S8300 and G700 component maintenance Table 68: Equipment List: G700 — Continued G700 700169998R LAN Cable 700228273R Ground Cable 700236680R Grounding Kit Table 69: Equipment list: G700 power cords G700 Power Cords Material Code: 170904 Apparatus Code: none Not Optional When you order this material code, a descriptive attribute will be required;...

  • Page 289: Avaya Cajun Equipment

    Use the information in Table 71, Avaya Cajun equipment, on page 289 when ordering Avaya Cajun equipment for use with the Avaya S8300 Media Server with G700 Media Gateway system. Table 71: Avaya Cajun equipment Avaya Cajun Equipment CASCADE/OCTAPLANE MODULE...

  • Page 290: Replacing The G700 Media Gateway

    Depending upon these circumstances, some or all of the components inserted into the G700 (S8300 Media Server, LED Panel, Avaya Expansion Module, Avaya Octaplane Module, or various Media Modules) can be reused in the replacement G700.
  • Page 291 S8300 Services port and using the Maintenance Web interface. NOTE: See Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100 for detailed information about setting up connections to the G700 and S8300 and the associated laptop configurations.
  • Page 292 Component replacement S8300 and G700 component maintenance Table 72: Replacement scenarios Original Software hardware release on hardware is: Scenario Replacement procedure Original - Back up data later than - Replace hardware - Install license and authentication files - Upgrade software on new hardware - Configure network data - Restore all data Original...
  • Page 293 Maintenance Web. The electronic version, used with the Installation Wizard, is recommended because it simplifies the data-entry task and is more accurate. You can obtain the pre-installation worksheet from http://support.avaya.com/avayaiw/. NOTE: You do not need to create a pre-installation worksheet for the other scenarios (1, 2, 3, 5, and 6).
  • Page 294 Component replacement S8300 and G700 component maintenance At the customer site Use the following procedure to replace the S8300 hard drive or the S8300 Media Server circuit pack (including its hard drive). Procedure to replace the S8300 hardware If the S8300 hardware is still functional or can be made functional, connect your laptop to the Services port on the S8300 and access the Maintenance Web Interface.
  • Page 295 Component replacement S8300 and G700 component maintenance h Select the FTP Backup Method and enter the customer-supplied information for: — User Name — Password — Host Name — Directory Click the Start Backup button. If IA770 is installed on the S8300, back up AUDIX announcements: —...
  • Page 296 Component replacement S8300 and G700 component maintenance Unscrew the four screws on the bottom of the S8300 circuit pack that attach to the hard- drive standoffs (Refer to Figure 83, S8300 hard drive replacement, on page 298). Detach the hard-drive ribbon cable from the hard drive (leave cable attached to the S8300 circuit pack).
  • Page 297 — Configure the S8300 as you would a new install using either the Avaya Installation Wizard and the Pre-Installation Worksheet previously created, or using the Maintenance Web Interface.
  • Page 298 Component replacement S8300 and G700 component maintenance Figure 83: S8300 hard drive replacement A LM IC E I C E indchd3 KLC 120402 Figure notes S8300 circuit pack Ribbon-cable connector Hard drive Hard-drive connector pins Hard-Drive standoffs Optional CWY1 board Screws Maintenance Procedures December 2003...

  • Page 299: Replacing Media Modules

    S8300 and G700 component maintenance Replacing Media Modules The information in the Table 73, Equipment list: Media Modules, on page 299 is necessary when ordering or replacing Avaya Media Modules. Table 73: Equipment list: Media Modules Media Modules T1/E1 Media Module Material Code: 170900...
  • Page 300 Upon Media Module replacement, modules are registered with the G700 Media Gateway, where board type, suffix, and vintage are verified. The G700 then sends appropriate H.248 messages to the controller, thus creating Communication Manager objects. For detailed descriptions of the Media Modules see Hardware Guide for Avaya Communication Manager, 555-233-200. WARNING: The G700 must not be operated with any slots open;...

  • Page 301: Replacing Avaya Expansion Modules

    The G700 must not be operated with any slot open; empty slots must be covered with the supplied blank plates. CAUTION: The G700 must be powered off before you insert or remove an Avaya Expansion Module. Replacing an Expansion Module in the G700 Power off the unit if the equipment has been in operation.

  • Page 302: Replacing An Avaya Octaplane Stacking Module

    G700 Media Gateways can be mounted in equipment stacks with routers, switches, or other G700s. The stack is limited to ten elements. To link multiple units, each G700 must be equipped with an Avaya Octaplane Stacking Module, which is mounted through the rear panel of the G700. See Hardware Guide for Avaya Communication Manager, 555-233-200 for a general description of the hardware.

  • Page 303: Replacing The S8500 Hard Drive

    Component replacement S8500 component maintenance Replacing the S8500 hard drive For procedures to replace the S8500 hard drive, see Job Aid: Replacing the S8500 Hard Drive, 555-245- 761. Replacing the S8500 Media Server For procedures to replace the S8500 Media Server, see Job Aid: Replacing the S8500 Media Server, 555- 245-762.

  • Page 304: Replacing The Remote Supervisor Adapter (Rsa)

    Replacing the Remote Supervisor Adapter (RSA) This section contains information and procedures for replacing the Remote Supervisor Adapter (RSA) board in the Avaya S8500 Media Server. Detailed discussions of these topics follow: • Backing up the RSA on page 305 •...
  • Page 305 Backing up the RSA Backup the RSA configuration before shutting down the S8500 Media Server. If it is not possible to backup the RSA at this time, locate the most recent RSA backup file before proceeding. Complete the following steps to backup the RSA configuration: Establish a connection from the services laptop to the RSA: •...
  • Page 306 Figure 87: RSA Welcome window NOTE: If the session times out unexpectedly, click Start New Session and Refresh. Click Continue to start the session. Click Configuration File in the navigation pane. In the Backup ASM Configuration section click, view the current configuration summary. Maintenance Procedures December 2003...
  • Page 307 Figure 88: Backing up the ASM configuration After verifying that the current configuration summary settings are correct, click Close. Now you can see the Backup ASM Configuration window (Figure 88, Backing up the ASM configuration, on page 307). In the Backup ASM Configuration section click Backup. Enter a name for the backup fileset and choose a location to write the backup files.
  • Page 308 Figure 89: Figure 5: Sever Welcome window Accept the Avaya certificate by clicking Yes. Log into the media server using the craft logon and the associated password (Figure 90, Logon window, on page 309). Maintenance Procedures December 2003...
  • Page 309 Figure 90: Logon window Suppress alarm origination by clicking Yes. Click Launch Maintenance Web Interface. Click Backup Now in the navigation pane. Select all data sets under the Data Sets heading. Select one of the following backup methods: • • Email •...
  • Page 310 Unplug the external power supply connection (Note 2 in Figure 85, RSA faceplate and connectors, on page 304) from the RSA. DANGER: Ensure that all power is removed from the media server and the RSA. Disconnect the modem from the RS-232 port on the RSA. Disconnect and label the LAN connection (if used) from the Ethernet port on the RSA.
  • Page 311 Replacing the ribbon cable The 20-pin ribbon cable connects the RSA to the server system board and is required for power and data transfer. The ribbon cable is shipped in the same box as the RSA. Replace the ribbon cable before installing the new RSA card.
  • Page 312 Figure 92: Removing the RSA from the riser connector 0 -1 0 -2 3 ,0 1 ,5 /6 0 /6 0 /6 4 B it z /6 L IN L IN h3msrrsa LAO 071803 Figure notes Connector Adapter support bracket Captive screw Riser card connector Remove the RSA card from PCI-X slot 1 by pulling the card gently out of the riser card connector.
  • Page 313 Replace the adapter support bracket lining up the tabs on each side of the bracket and the screw holes on the riser card connector. Align the riser card with the connector and the tabs on the adapter support bracket with the provided holes and press the riser card firmly into the connector.
  • Page 314 Powering up the Media Server Complete the following steps if you want to start the server at this time: Plug the power cord in the back of the server. Press the Power Button located on the front on the right hand side. Log into the server to ensure that the startup is complete.
  • Page 315 In the Restore ASM Configuration section, click Browse. See Figure 94, Restoring ASM configuration, on page 315 for an example of the restoring ASM configuration window. Figure 94: Restoring ASM configuration Click the saved configuration file that you want to restore and click Open. The file will appear in the box.
  • Page 316 To check what RSA firmware version is compatible with the release of Communication Manager that is running on the server: Open an browser window on your laptop. Enter www.support.avaya.com in the address field. Highlight Support in the top heading. Highlight and click Software and Firmware Downloads.
  • Page 317 314) or manually input the correct information. b Generate an alarm to a test alarm by clicking Generate Test Alert. If the RSA has LAN connectivity, send an SNMP alert. Call the Avaya alarming group and verify the alarm was received.
  • Page 318 Restoring the RSA defaults CAUTION: DO NOT select Restore Defaults. Doing so removes the Avaya defaults that are superimposed over the manufacturers’ resulting in loss of access to the RSA card. “Restore” in this instance means reinstating the manufacturer’s factory default settings and rendering the server incapable of providing IP Telephony.

  • Page 319: Replacing The S8500 Dual Network Interface

    Replacing the S8500 dual network interface This section describes the steps required to replace an existing dual network interface card (NIC) on the S8500 Media Server. The control network traffic from the server out to the dedicated customer LAN travels through the NIC. The components of this procedure include: •...
  • Page 320 Figure 95: Welcome Window Click Continue. Accept the Avaya certificate by clicking Yes. The logon window appears (Figure 96, Logon window, on page 321). Type craft in the Logon ID field and the password (obtained from ART) in the Password field () and click Logon.
  • Page 321 Figure 96: Logon window Suppress alarm origination by clicking Yes. Click Launch Maintenance Web Interface. Click Backup Now in the navigation pane. Select all data sets under the Data Sets heading. Select one of the following backup methods: • • E-mail •...
  • Page 322 Disconnect and label the LAN connection (if used) from the Ethernet port on the RSA. Pull the server forward so that the server rails expand and the retaining clips on the rails click into place. Unplug and label the cable from the Ethernet port labeled LINK A on the dual NIC. Removing the cover of the Media Server CAUTION: Remove all power from the media server before starting this procedure.
  • Page 323 Removing the fan unit Locate the fan slot adjacent to the power plug on the rear of the server. Remove the two screws holding the fan unit. You do not need to unplug the fan unit. Set the adapter-support bracket to the right of the fan. Removing the old NIC Completely unscrew the captive screw on the left hand side of the PCI-2 slot.
  • Page 324 Figure 98: Replacing the faceplate h3msfnic LAO 072103 Figure notes Screws holding faceplate Smaller faceplate Faceplate on NIC shipped from factory Inserting the new NIC Carefully grasp the new NIC by the top edge or upper corners and align it with the PCI-2 expansion slot.
  • Page 325 Figure 99: Repositioning the new NIC , 0 A , 5 A 0 / 6 0 / 6 / 6 4 B it z / 6 h3msrnic LAO 080103 Figure notes Mounting screws Smaller faceplate Fan assembly Network interface card Captive screws Replacing the fan unit Replace the fan unit with the fan blades pointed down toward the NIC., securing the fan unit with...
  • Page 326 Release the retaining tabs on the rails and slide the S8500 Media Server back into place on the data rack. Locate the marked cable that you removed from the old NIC and plug it into the Ethernet 2 port, which is labeled ACT/LINK A on the small faceplate of the new NIC. Powering up the server Complete the following steps if you wish to start the media server at this time: Plug the power cord into the power receptacle on back of the server.
  • Page 327 Configuring the NIC Under Server, click Configure Server Click Continue through the review notices until you get to the xxx page. Select Configure Individual Services and click Continue. Select Set Identities and click Continue. The following Ethernet ports are listed: •...
  • Page 328 Figure 101: Ping screen In the field, type in the host name or IP address of a computer on the Host Name or IP address network. Click Execute Ping. Verify that the ping was successful, indicating that the media server is connected to the customer’s network.

  • Page 329: S8700 Component Maintenance

    342 Replacing the S8700 Media Server You might need to replace an Avaya S8700 Media Server to correct a problem, such as a functional failure of the motherboard, the hard drive, or other components. Depending on which software release that the failed media server is running, you might need to upgrade the software on the replacement media server and, perhaps, the existing media server.
  • Page 330 330, verify that the following tasks have been done: • Ask the customer for the Product ID for the media server being replaced. If the customer does not have it, run the Avaya Registration Tool (ART) to obtain the Product ID number for replacement media server. •...
  • Page 331 S8700 component maintenance Initial on-site tasks NOTE: Except where noted in the following checklist, see “Upgrading the Avaya S8700 Media Server Configurations” section on the Avaya S8300 and Avaya S8700 Media Server Library CD-ROM (555-233-825) for details on tasks. Table 76: Initial tasks for replacing an S8700 Media Server...
  • Page 332 S8700 component maintenance Table 76: Initial tasks for replacing an S8700 Media Server Task Description Resolve Alarms on the Under Alarms and Notification click View Current Alarms. Active Media Server Use a terminal emulator to access the Communication Manager SAT command prompt screen. Use the display alarms command and resolve any alarms.
  • Page 333 S8700 component maintenance Table 77: Tasks for replacing an S8700 Media Server Task Description Remove Media Server from Remove the media server from the rack. Rack Replace the S8700 Media Remove the S8700 Media Server being replaced Server on page 338. Reinstall the Media Server in Reinstall the media server in the rack.
  • Page 334 Click Upload Files to Server (via browser) to copy the Manager Software Patch patch to the /var/home/ftp directory. Use telnet to access the Linux command prompt screen. Refer to Avaya S8300 & S8700 Media Server Patching Procedures available at http://avaya.com/support for the patch installation procedures.
  • Page 335 C-LAN, MedPro, and VAL circuit packs. Refer to VAL Circuit Pack Firmware “Upgrading the S8700 Media Server Configuration” section of the Avaya S8300 and Avaya S8700 Media Server Library CD-ROM (555-233-825). CAUTION: Upgrading the firmware on a circuit pack requires a reset of that circuit pack.
  • Page 336 S8700 component maintenance Table 78: Final Tasks for replacing an S8700 Media Server Task Description Ping the Connections on the Under Diagnostics click Execute Pingall. Ensure that all Replacement Media Server connections, including the active media server, the IPSI circuit packs, and all administered connections respond. Check Alarms on Both Media Under Alarms and Notification click View Current Server...
  • Page 337 Install Software Patch copy the patch to the /var/home/ftp directory. Refer to on Existing Media Server Avaya S8300 & S8700 Media Server Patching Procedures available at http://avaya.com/support. (For R1.0/R1.1 replacement Under Server click Release Server to verify that the only) Release the Existing media server is released from the busy out mode.
  • Page 338 338 before installing the replacement media server in the rack. Refer to Getting Started with the Avaya S8700 Media Server with the Avaya G650 Media Gateway, 555- 245-703 for information on installing the S8700 Media Server in the rack and reconnecting all the cables.
  • Page 339 S8700 component maintenance Slide the media server cover back from the front panel (see Figure 102, Media Server cover removal and replacement, on page 339) until the cover’s tabs are released from the top slot of front panel. Lift the cover straight up and remove it from the media server. Figure 102: Media Server cover removal and replacement bkdsopen LAO051303 Figure notes...
  • Page 340 S8700 component maintenance Unplug the ribbon cable from the back of the hard drive (Figure 103, Hard drive bracket and hard drive, on page 340). Note that the red stripe on the ribbon cable is on the side closest to the power cable.
  • Page 341 S8700 component maintenance Remove the cover of the replacement S8700 Media Server Follow the steps in Remove the cover of the failed S8700 Media Server on page 338. Remove the hard drive Follow the steps in Remove the hard drive on page 339.

  • Page 342: Replacing The S8700 Hard Drive

    Before you go on site, verify that the following tasks have been done. • Ask the customer for the Product ID for the media server being replaced. If the customer does not have it, run the Avaya Registration Tool (ART) to obtain the Product ID number for the replacement media server. •...
  • Page 343 Table 80, Initial tasks for replacing a hard drive on an S8700 Media Server, on page 344, see “Upgrading the Avaya S8700 Media Server Configurations” documentation on the Avaya S8300 and S8700 Media Server Library CD-ROM, 555-233- 825, for detailed task lists. Maintenance Procedures...
  • Page 344 LSP (use stop -acfn command) until the media server has R1.2 been upgraded. For detailed information, see Installation and Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server, 555-234-100. Determine If the On the Web Interface, select View Backup Log to search for Customer Has a Recent backup files.
  • Page 345 S8700 component maintenance Table 80: Initial tasks for replacing a hard drive on an S8700 Media Server Task Description Use telnet to access the Linux command line on the active Suppress Alarm media server . Use the almsuppress -t 120 command to Origination on the Active S8700 Media suppress alarms for the duration of the replacement process.
  • Page 346 Click Upload Files to Server (via browser) to copy the patch Manager Software to the /var/home/ftp directory. Use telnet to access the Linux Patch command prompt screen. Refer to Avaya S8300 & S8700 Media Server Patching Procedures available at http://avaya.com/support for the patch installation procedures.
  • Page 347 R1.2 system. At the same time, upgrade the firmware on the C- only) Upgrade IPSI, C- LAN, MedPro, and VAL circuit packs. Refer to “Upgrading the LAN, MedPro, and S8700 Media Server Configuration” section of the Avaya S8300 VAL Circuit Pack and Avaya S8700 Media Server Library CD-ROM (555-233- Firmware 825).
  • Page 348 S8700 component maintenance Table 82: Final tasks for replacing a hard drive in an S8700 Media Server Task Description Stop Communication At the Linux command line, type stop -acf. Manager and Busy Out On the Maintenance Web Interface, under Server click Busy the Media Server Out Server to busy out the media server.
  • Page 349 Under Miscellaneous click Upload Files to Server (via replacement only) browser) to copy the patch to the /var/home/ftp directory. Refer Install Software Patch to Avaya S8300 & S8700 Media Server Patching Procedures on Existing Media available at http://avaya.com/support. Server (4 of 5)
  • Page 350 Wear an antistatic wrist ground strap whenever handling components such as the hard drive of an Avaya S8700 Media Server. Connect the strap to an approved ground, such as an unpainted metal surface. Also, place the hard drive on an antistatic mat that is similarly grounded.
  • Page 351 S8700 component maintenance Use a #1 cross-point (Phillips) screwdriver to unscrew the two screws at the back of the media server that hold the cover in place (Figure 104, Media Server cover removal and replacement, page 351). Slide the media server cover back from the front panel (Figure 104, Media Server cover removal and replacement, on page 351) until the cover’s tabs are released from the top slot of the front...
  • Page 352 S8700 component maintenance Partially pull out the hard drive bracket (Figure 105, Hard drive bracket and hard drive, on page 352) so that you can disconnect the cables. Note the position of the ribbon cable within the chassis so you can return it to exactly the same position later. Unplug the 4-wire power cable from the back of the hard drive (Figure 105, Hard drive bracket and hard drive,...

  • Page 353: G600 Component Maintenance

    G600 component maintenance Reattach the ribbon cable. Be sure the red stripe on the cable is on the side closest to the power cable. Reattach the power cable (Figure 105, Hard drive bracket and hard drive, on page 352). Lay the ribbon cable into the media server housing as it was before disconnecting it. This prevents bunching of the cable when you slide the hard drive bracket back into the media server.

  • Page 354: Replacing A Biu Or Rectifier

    Replacing a BIU or rectifier Figure 106: Removing the G600 fan assembly fndpremv LJK 102600 Plug in the new fan assembly. The power for the fan automatically connects when the fan assembly is plugged in. Tighten every thumb screw on the fan assembly. Replacing a BIU or rectifier To remove a battery interface unit (BIU) or rectifier, first attach a grounding strap from the cabinet to your bare wrist, and then perform the following steps:...

  • Page 355: Additional Maintenance Procedures

    Setting G700 synchronization on page 408 • IP Telephones on page 412 Upgrading firmware To update firmware on Avaya equipment use the information sources listed in Table 83, Firmware upgrade information sources, on page 355. Table 83: Firmware upgrade information sources...

  • Page 356: Loopback Jack Installation

    Additional maintenance procedures DS1 CPE loopback jack (T1 only) NOTE: The loopback jack operates with any vintage of TN767E (or later) or TN464F (or later) DS1 circuit packs. The loopback jack operates with the 120A2 (or later) ICSU only; not the 31xx series of Channel Service Units (CSUs), other external CSUs, or earlier ICSUs.

  • Page 357: Administration

    Additional maintenance procedures DS1 CPE loopback jack (T1 only) Administration At the management terminal, enter change ds1 location (the DS1 Interface circuit pack for which the loopback jack was installed). Be sure the near-end CSU type is set to integrated. On page 2 of the screen, change the supply CPE loopback jack power field to y.
  • Page 358 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Enter location to clear the ESF error count. clear meas ds1 esf Enter location to display the bit error count. Refer to Table 84, DS1 span list meas ds1 sum troubleshooting, on page 358 for troubleshooting information.

  • Page 359: Loopback Jack Fault Isolation Procedures

    Additional maintenance procedures DS1 CPE loopback jack (T1 only) If the test runs for 1 minute with an error count of 0, confirm that the 3-in-24 pattern error detector is operating properly by entering test ds1-loop location inject-single-bit-error. This causes the 3-in-24 pattern generator on the DS1 circuit pack to inject a single-bit error into the transmit pattern.
  • Page 360 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Table 85: DS1 span section descriptions Section Smart Jack location Section 1: Between the 120A2 (or later) ICSU and the loopback jack Section 2: Between the loopback jack and the smart jack (network interface point) Section 3: From the smart jack to the Central Office (CO).
  • Page 361 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Figure 107: Network Interface at Smart Jack Figure notes Span Section 1 Loopback Jack Span Section 2 Network Interface Smart Jack Span Section 3 Interface Termination or Fiber MUX 120A2 (or later) Integrated Central Office Channel Service Unit (ICSU) RJ-48 to Network Interface...
  • Page 362 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Figure 108: Network Interface at Extended Demarcation Point (Smart Jack inaccessible) Figure notes Span Section 1 Loopback Jack Span Section 2 “Dumb” Block (Extended Demarcation) Span Section 3 Network Interface Smart Jack 120A2 (or later) Integrated Interface Termination or Fiber MUX Channel Service Unit (ICSU)
  • Page 363 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Figure 109: Network Interface at Extended Demarcation Point (Smart Jack accessible) Figure notes Span Section 1 “Dumb” Block (Extended Demarcation) Span Section 2 Loopback Jack Span Section 3 Network Interface Smart Jack 120A2 (or later) Integrated Interface Termination or Fiber MUX Channel Service Unit (ICSU)
  • Page 364 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Figure 110: Network Interface at “Dumb” Block Figure notes Span Section 1 Loopback Jack Span Section 2 “Dumb” Block (Demarcation Point) 120A2 (or later) Integrated Interface Termination or Fiber MUX Channel Service Unit (ICSU) RJ-48 to Network Interface (up Central Office to 1000 Feet) (305 m)
  • Page 365 Additional maintenance procedures DS1 CPE loopback jack (T1 only) Figure 111: Network Interface at “Dumb” Block with repeater line to Fiber MUX Figure notes Span Section 1 Loopback Jack Span Section 2 “Dumb” Block (Demarcation Point) 120A2 (or later) Integrated Channel Service Unit Repeater (ICSU) RJ-48 to Network Interface (up to 1000 Feet) (305...

  • Page 366: Configurations Using Fiber Multiplexers

    Additional maintenance procedures DS1 CPE loopback jack (T1 only) b The local DS1 interface’s payload loopback, activated and tested by the DS1 service provider at the CO end. The far-end ICSU’s line loopback. This test is activated at the management terminal by entering test ds1-loop location far-csu-loopback-test-begin.

  • Page 367: Facility Test Calls

    Additional maintenance procedures Facility test calls Be aware that there are installations that use repeated metallic lines between the MUX and the “dumb” block. These lines require DC power for the repeaters and this DC power is present at the “dumb”...
  • Page 368 • yy = Circuit number Circuit range depends upon the Media Module on which the trunk is set up. For the Avaya Analog Media Module (MM711), the range is 1-8; for the Avaya T1/E1 Media Module (MM710), the range could be 1-23, 1-24, 1-31, or 1-32, depending upon the type of translation and signaling.

  • Page 369: Ds0 Loop-Around Test Call

    The port is a tone receiver. NOTE: For a definition of call progress tones, refer to Overview for Avaya Communication Manager, 555-233-767. Place a call. If the call does not go through (no ringing is heard), check to see if the circuit has been removed or if the trunk is a rotary trunk.

  • Page 370: Dtmr Test Call

    Dial tone The port is a trunk. See the preceding section. NOTE: For a definition of call progress tones, refer to Overview for Avaya Communication Manager, 555-233-767. Dial the sequence 1234567890*# If the sequence is entered and received correctly, dial tone is returned and another test call can be made.
  • Page 371 Table 87, TDM Bus time slot numbers, on page 371. NOTE: For a definition of call progress tones, refer to Overview for Avaya Communication Manager, 555-233-767. TDM bus time slots When you address a tone-carrying time slot on the TDM bus (A or B) that is currently carrying tones, you will be connected to that time slot and will hear the tone as follows: •...

  • Page 372: Out-Of-Service Time Slot Test Call

    Additional maintenance procedures Facility test calls Table 87: TDM Bus time slot numbers TDM Bus A TDM Bus B time slot time slot Tone heard Reorder Touch Tone 1 — 697 Hz Touch Tone 2 — 770 Hz Touch Tone 3 — 852 Hz Touch Tone 4 —...

  • Page 373: System Tone Test Call

    Inter-PN resources are not available. System tone The specified tone will be heard if it is functioning. NOTE: For a definition of call progress tones, refer to Overview for Avaya Communication Manager, 555-233-767. Table 88: System tone identification numbers Number...
  • Page 374 Additional maintenance procedures Facility test calls Table 88: System tone identification numbers Number Description Internal call waiting tone Ringback tone Special ringback tone Dedicated ringback tone Dedicated special ringback tone Touch tone 1 Touch tone 2 Touch tone 3 Touch tone 4 Touch tone 5 Touch tone 6 Touch tone 7...
  • Page 375 Additional maintenance procedures Facility test calls Table 88: System tone identification numbers Number Description Hold recall Hold confirmation Zip tone 2804 Hz 1004 Hz (-16db) 1004 Hz (0 db) 404 Hz Transmission test sequence 105 Redirect tone Voice signaling tone Digital milliwatt 440 Hz + 480 Hz Music...

  • Page 376: Media Gateway Batteries

    Additional maintenance procedures Facility test calls Media Gateway batteries The backup batteries in the power distribution unit in the bottom of the cabinet should be replaced every four years or whenever a POWER alarm that indicates the condition of the batteries is logged. Systems with an uninterruptible power supply (UPS) may not be equipped with backup batteries.

  • Page 377: Call Admission Control-Bandwidth Limitation

    Additional maintenance procedures Call Admission Control-Bandwidth Limitation PREVENTIVE MAINTENANCE LOG Date equipment installed: ________________________ Scheduled Date Completed Scheduled Date Completed Air Filters Date Completed Date Completed Single- carrier cabinet Multicarrier cabinet Battery Scheduled Date Completed Scheduled Date Completed Packs Date Completed Date Completed...

  • Page 378: Cac-Bl Description

    Additional maintenance procedures Call Admission Control-Bandwidth Limitation CAC-BL description In order to ensure Quality of Service for Voice over IP calls, there is a need to limit overall VOIP traffic on WAN links. The Call Admission Control-Bandwidth Limitation feature of Communication Manager allows the customer to specify a VOIP bandwidth limit between any pair of IP network regions, and then to deny calls that need to be carried over the WAN link that exceed that bandwidth limit.

  • Page 379: Supported Network Topologies

    Additional maintenance procedures Call Admission Control-Bandwidth Limitation The feature provides administrators with a static display of bandwidth utilization and an event log of call denials through SAT commands. Supported network topologies Network topologies can be described as fully connected, hub and spoke, or a combination. All network topologies are supported, with the following two limitations: •...
  • Page 380 Additional maintenance procedures Call Admission Control-Bandwidth Limitation Figure 112: status ip-network-region <n> status ip-network-region 2 Inter Network Region Bandwidth Status Src Dst Conn Conn BW-limits BW-Used (Kbits) #-of-Connections Denials Rgn Rgn Type Stat Today direct pass 128 Kbits indirect pass indirect pass indirect pass For more details on the indirect regions, the second form of the command must be used (See...

  • Page 381: System Resets

    Table 89, Call processing features impacted by CAC-BL, on page 382 lists call processing features impacted by CAC-BL. For more information about Call Admission Control, see the Administrator’s Guide for Avaya Communication Manager, 555-233-506. Maintenance Procedures December 2003...

  • Page 382: Analog Tie Trunk Back-To-Back Testing

    Additional maintenance procedures Analog tie trunk back-to-back testing Table 89: Call processing features impacted by CAC-BL Announcements Media processor resources Call queuing Multi-level precedence and preemption (MLPP) Call redirection Multiple terminations Call routing by trunking Music on hold Conference RSVP E911 Shuffling Firmware download to port...
  • Page 383 Additional maintenance procedures Analog tie trunk back-to-back testing Enter n to add a new (test) trunk group. Then enter information for the following add trunk fields: Group Type Use trunk access code obtained from dial plan Trunk Type wink/wink (in/out) Port Assign two of the ports from the tie trunk.
  • Page 384 Additional maintenance procedures Analog tie trunk back-to-back testing Figure 115: Trunk Group form - E & M mode (Page 2 of 2) Page 2 of TRUNK GROUP GROUP MEMBER ASSIGNMENTS Port Name Mode Type Answer Delay 1: B1901 E & M t1 stan 2: B1902 E &...
  • Page 385 Additional maintenance procedures Analog tie trunk back-to-back testing Place a call from one voice terminal to another voice terminal using the tie trunk ports assigned. Dial TAC and extension. For example, if TAC of tie trunk group is 110 and station number is 5012, then dial 110 5012.

  • Page 386: Simplex Mode Test Procedure

    Additional maintenance procedures Analog tie trunk back-to-back testing Table 90: Carrier lead appearances MDF 110 connecting block terminals CO Trunk TN747 Tie Trunk TN760 (2 of 2) Simplex mode test procedure Repeat steps 1 through 7 of the Table , E&M mode test procedure, on page 382.
  • Page 387 Additional maintenance procedures Analog tie trunk back-to-back testing Enter add trunk n to add a new (test) trunk group. Then enter information for the following fields: Group Type Use trunk access code obtained from dial plan. Trunk Type (in/out) wink/wink Port Assign two of the ports from the tie trunk.

  • Page 388: Tn760E Tie Trunk Option Settings

    Additional maintenance procedures TN760E tie trunk option settings Port 1 Port 2 (type 5) (type 5) (simplex) (simplex) connected to connected to connected to connected to Repeat Steps 13 through 16 of the E&M mode test procedure on page 382. TN760E tie trunk option settings S8100 only The TN760E Tie Trunk circuit pack interfaces between 4 tie trunks and the TDM bus.
  • Page 389 E&M/S Admin- MPLX Prot/Unprot istered Installation situation Preferred signaling format switch switch port Circumstance System Far-End Co-Located Avaya PBX E&M Type 1 E&M Type 1 E&M Unprotected Type 1 Compatible Standard Compatible Inter-Building Avaya PBX Protected Protected Type 1 E&M...

  • Page 390: Tn464E/F Option Settings

    Additional maintenance procedures TN464E/F option settings TN464E/F option settings S8100 only The TN464E/F DS1/E1 Interface - T1/E1 circuit pack interfaces between a 24- or 32-channel Central Office/ISDN or tie trunk and the TDM bus. Set the switches on the circuit pack to select bit rate and impedance match. See Table 94, Option switch settings on TN464E/F, on page 390 and...

  • Page 391: Terminating Trunk Transmission Testing

    Additional maintenance procedures Terminating Trunk Transmission testing Terminating Trunk Transmission testing The Terminating Trunk Transmission (TTT) (non-interactive) feature provides for extension number access to three tone sequences that can be used for trunk transmission testing from the far end of the trunks.

  • Page 392: Removing And Restoring Power To The Media Gateway

    Additional maintenance procedures Removing and restoring power Removing and restoring power to the Media Gateway For a multicarrier cabinet, set the emergency transfer switch to ON. This locks the PN in the emergency transfer mode until the trouble is cleared. Depending on which type of cabinet you are powering down, do one of the following: •...

  • Page 393: Removing And Restoring Power On The S8100 Media Server

    Additional maintenance procedures Removing and restoring power To restore power to the media server: Follow these steps to open the bezel door to access the power switch: a Grasp the tab at each end of the hinged bezel door. b Gently pull the tabs out and down to swing open the hinged bezel door. Press the power switch to apply power to the server, then close the bezel door.
  • Page 394 Additional maintenance procedures Removing and restoring power The system is ready for power off when the green “OK Remove” LED light on the TN2314 processor circuit pack appears. (This takes about 3 minutes.) Unplug the power cord, or Disengage the latch on the power supply and pull it from its slot so that the backplane pins are not connected.

  • Page 395: Setting Neon Voltage (Ring Ping)

    Additional maintenance procedures Removing and restoring power Setting neon voltage (ring ping) This procedure must be performed at installation and after replacement of the power supply. NOTE: The frequency (20, 25 or 50 Hz) is set by a switch on the power supply. Check the setting on this switch to ensure it is properly set.

  • Page 396: Removing And Restoring Power On The G700 Media Gateway

    Additional maintenance procedures Removing and restoring power Figure 119: Setting the neon voltage didmt1 KLC 053097 Removing and restoring power on the G700 Media Gateway The G700 Media Gateway contains a detachable power cord. You can add power by plugging the power cord into the G700 receptacle, then plugging the cord into the wall outlet.
  • Page 397 Additional maintenance procedures Removing and restoring power • Immediate – the system does not wait for processes to terminate normally before it shuts the server down Accept the default option. d Leave the checkbox After Shutdown, Restart System unchecked. Click Shutdown. Alternatively, you can manually initiate a shutdown process by first depressing for at least two seconds the button located next to the fourth GREEN “Ok-to-Remove”...

  • Page 398: Automatic Transmission Measurement System

    Additional maintenance procedures Automatic Transmission Measurement System b Complete Shutdown Failure – If an operating system level failure has occurred, it is possible that the processor will never be yielded for the shutdown to begin, even after process priorities are equalized by the recovery function at the 80 second interval. After two minutes, the S8300 will be reset by the hardware watchdog.

  • Page 399: Atms Tests

    Table 95: ATMS administration Form Field Entry/Remarks System-parameters ATMS y If this field is n, contact your Avaya customer-options representative for a change in your license file. Station Extension At least one TN711 analog port must be assigned.
  • Page 400 Additional maintenance procedures Automatic Transmission Measurement System Input parameters Input Description trunk addresses Specify a single trunk or several trunks by using trunk, port, or board addresses. These parameters are described in the introduction to Input parameters on page 400. If you enter a trunk- group number without a member number, every member of the group is tested.
  • Page 401 Additional maintenance procedures Automatic Transmission Measurement System Table 96: Measurement capability by TTL type Terminating Test Line Type 105 Type 105 Type High-Level/ with without Low-Level Return Return Tone Test Loss Loss Source Type Type Loss at 1004 Hz Far End to Near End Loss at 1004 Hz Near End to Far End...
  • Page 402 Additional maintenance procedures Automatic Transmission Measurement System Measurement data gathered by analog testcalls can be retrieved with the list testcalls command as described in ATMS reports on page 403. The measurements that are made and recorded depend on the type of test that is specified and the capabilities of the far-end TTL. Figure 120, Test results for test analog-testcall trunk 60, on page 402 shows a typical result for test...

  • Page 403: Atms Reports

    Additional maintenance procedures Automatic Transmission Measurement System ATMS reports The list testcalls command produces detailed and summary reports of measurements made by the ATMS. Measurement reports contain data on trunk signal loss, noise, singing return loss, and echo return loss, and are used to determine the quality of trunk lines.

  • Page 404: Atms Summary Report

    Additional maintenance procedures Automatic Transmission Measurement System Input Description to-mem When used with grp, display measurements for every trunk-group member from one up to the specified trunk-group member entered. When used with mem, this is the ending trunk-group member in a range.

  • Page 405: Atms Detail Report

    Additional maintenance procedures Automatic Transmission Measurement System Output fields Field Description Results for each trunk group are listed by trunk-group number. Trk Grp Num Only outgoing or 2-way analog trunks are listed. Num Of Trks The number of members in the trunk group. The date of the oldest measurement in the trunk group.
  • Page 406 Additional maintenance procedures Automatic Transmission Measurement System Figure 122: ATMS detail report ATMS TRUNK MEASUREMENTS Group: 78 Type: co Vendor: AT&T TTL Type: 105-w-rl THRESHOLD VALUES Loss dev at 1004Hz-loss 404Hz 2804Hz C-msg C-ntch Noise Noise Marginal Unacceptable Trk Test Test Test -16dBm OdBm Mem Date...
  • Page 407 Additional maintenance procedures Automatic Transmission Measurement System Field Description Tst Rslt The results of the trunk transmission test as follows: • pass: the test call completed successfully and trunk performance was satisfactory. • marg: trunk measurements exceeded the marginal threshold, but not the unacceptable.

  • Page 408: Atms Measurement Analysis

    Setting G700 synchronization If the Avaya G700 Media Gateway contains an MM710 T1/E1 Media Module, it is usually advisable to set the MM710 up as the primary synchronization source for the G700. In so doing, clock sync signals from the Central Office (CO) are used by the MM710 to synchronize all operations of the G700.

  • Page 409: Viewing G700 Synchronization Sources

    Additional maintenance procedures Setting G700 synchronization Control of which reference source is the “Active” source is accomplished by issuing the command set sync interface {primary | secondary}. If “secondary” is chosen, then the secondary source becomes “Active”, and the primary becomes “standby”, and, in addition, fallback to the primary source will not occur if or when it becomes available.
  • Page 410 Additional maintenance procedures Setting G700 synchronization Table 97: mgp-001-1(configure)# show sync timing Source Status Failure Primary Not Configured Secondary Not Configured Local Active None Comment: No failures, SIG GREEN on and ACT on when trunk is seized. Table 98: mgp-001-1(configure)# set sync interface primary v4 mgp-001-1(configure)# show sync timing Source Status...
  • Page 411 Additional maintenance procedures Setting G700 synchronization The results from the above command are shown in Table 100: Table 100: TEST RESULTS Maintenance Test No. Port Name Alt. Name Result Error Code 001V4 MG-DS1 PASS Command successfully completed If a secondary is similarly provisioned: Table 101: mgp-001-1(configure)# set sync interface secondary v3 mgp-001-1(configure)# show sync timing SOURCE...

  • Page 412: Ip Telephones

    4624 IP Telephone User’s Guide, 555-233-776 • 4612 IP Telephone User’s Guide, 555-233-777 The Avaya 4600-Series IP Telephones are relatively trouble-free. Table 106, IP Telephone problems and solutions, on page 413 provides the most common problems an end user might encounter. For other IP Telephone questions or problems, contact your Telephone System Administrator.
  • Page 413 Additional maintenance procedures IP Telephones • Phone does not ring • Speakerphone does not operate • A feature does not work as indicated in the User Guide • All other IP Phone problems Table 106: IP Telephone problems and solutions Problem/Symptom Suggested solution Phone does not activate after...
  • Page 414 If the connection is secure, verify that you are using an properly approved headset, base unit and/or adapter, as described in the list of approved Avaya Communication compatible Headsets. Phone does not ring If you have a 4612 or 4624 IP Telephone, use the Menu to access the RngOf (Ringer Off) feature;...

  • Page 415: Resetting And Power Cycling Ip Telephones

    Additional maintenance procedures IP Telephones Resetting and power cycling IP Telephones Reset your IP Telephone when other troubleshooting suggestions do not correct the problem. Power cycle with the approval of your System Administrator only when a reset does not resolve the problem. Resetting an IP Telephone This basic reset procedure should resolve most problems.
  • Page 416 Additional maintenance procedures IP Telephones Maintenance Procedures December 2003...

  • Page 417: Index

    Accessing S8100 Media Server for maintenance Avaya Octaplane blank admonishments Avaya Octaplane Stacking Module air filters replacement steps air filters, inspecting Avaya S8300 Media Server with G700 Media Gateway alarm logs access alarms maintenance features classifications system interactions external leads...
  • Page 418 Index components field replaceable Conference, Transfer, and Call-Forwarding denial connectivity ISDN-BRI/packet bus cabinets packet bus multicarrier rules cabling connectivity, packet bus DS1 connectors connector pins DS1 CONV control circuit packs fiber-optic replacing metallic reseating capabilities, system unseating captive screws CO-trunk-to-digital interface frequency response Cascade Cables CPU occupancy caution symbol...
  • Page 419 Index DS1 span fiber troubleshooting administration DSO frequency response connections, metallic cabling DSU, see Data Service Unit fault-isolation procedure DTE, see data terminal equipment fiber-optic cables DTMR Test Call hardware duplication FIC, see Facility Interface Code and reliability options field replaceable components of servers filters spontaneous interchanges...
  • Page 420 Index impedance, setting kernel log Linux daemon (klogd) impedances loop in termination initialization active server and recovery LAN Cable arbiter module Layer 2 Switching Processor Communication Manager application hardware-sanity check layers, of OSI model init process and related protocols reboots LED Module server LEDs...
  • Page 421 Multimedia Interface (MMI) arenas background testing packet bus packet bus software preventive maintenance features Neon voltage Avaya S8300 Media Server with G700 Media network assessment Gateway network interface Communication Manager network jacks maintenance objects (MOs) network time protocol daemon (xntpd)
  • Page 422 Index precautions, safety preventive maintenance batteries private-line service codes Open System Interconnect model procedures Layer 1 (physical layer) SNI/EI manual loop back protocols Process Manager (prc_mgr) Layer 2 (data-link layer) processor occupancy protocols protocols OSI model, see Open System Interconnect model 8-bit character code analog CEPT1...
  • Page 423 PCM-encoded analog reset system 5 SIGTERM signal DEFINITY extended reboot single-frequency return loss resets, system smart jack resolving alarms configurations restart as traditional Avaya term manual loop-back procedure single-process software Restoring power upgrades specifications information requirements spontaneous interchanges websites startup Linux scripts...
  • Page 424 Index terminal Transfer on Ringing equipment port wiring transmission terminal emulation characteristics errors w2ktt stream Terminating Trunk Transmission (TTT) test troubleshooting termination impedances ASAI problems test calls duplicated media servers DS0 loop around IP telephones DTMR ISDN- facility BRI problems system tone TDM bus time slot endpoints (wideband)
  • Page 425 Index web interface Windows 2000 logins wiring premises terminal equipment ports xntpd Linux daemon Maintenance Procedures December 2003...
  • Page 426 Index Maintenance Procedures December 2003...

This manual is also suitable for:

Scc1Cmc1G600G650G350G700

Table of Contents