Page 1 Maintenance of the Avaya G350 Media Gateway 555-245-105 Issue 3 June 2004...
Page 2 • Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Be aware that there may be a risk of unauthorized intrusions associated Avaya’s standard warranty language as well as information regarding...
Page 3 • A reorder tone is received. • 21 CFR 1040.10 and CFR 1040.11. Avaya attests that this registered equipment is capable of providing users The LASER devices used in Avaya equipment typically operate within the access to interstate providers of operator services through the use of access following parameters: codes.
Page 4 68, but many have been registered with the FCC before the SDoC process If this happens, the telephone company will provide advance notice in was available. A list of all Avaya registered products may be found at: order for you to make necessary modifications to maintain uninterrupted http://www.part68.org...
Page 5: Table Of Contents
• Maintenance strategy • Media Module maintenance Hot swap • LEDs • Maintenance access to the Avaya G350 Media Gateway and Media Servers Web interface Avaya G350 Media Gateway CLI • Upgrading software • Plugging in and unplugging the Media Gateway •...
Page 6 • G350 subsystems maintained by Communication Manager • Maintenance commands Categories of maintenance commands SAT commands specific to the Avaya G350 and G700 Media Gateways Hidden Communication Manager SAT commands • Dynamic Call Admission Control Enabling Dynamic CAC on the G350 Using Dynamic CAC on the Media Gateway Controller •...
Page 7 Error Log Entries and Test to Clear Values System Technician-Demanded Tests: Descriptions and Error Codes Digital Line Electronic Power Feed Test(#11) DIG-LINE Station Lamp Updates Test (#16) Digital Station Audits Test (#17) Maintenance of the Avaya G350 Media Gateway June 2004...
Page 8 • MG-BRI (BRI Trunk Media Module MM720 and MM722) LEDs ISDN Interface Reference Points Error Log Entries and Test to Clear Values System Technician-Demanded Tests: Descriptions and Error Codes • MG-DCP (Digital Line Media Module) Maintenance of the Avaya G350 Media Gateway June 2004...
Page 9 • XXX-BD (Common Port Media Module) XXX-BD Common Media Modules Error Log Entries and Test to Clear Values Technician-Demand Tests: Descriptions and Error Codes Control Channel Looparound Test (#52) SAKI Sanity Test (#53) Maintenance of the Avaya G350 Media Gateway June 2004...
Page 10 Log in to the Media Server from your laptop using Telnet Log in to the S8300 Web Interface from your laptop Open the Communication Manager SAT screens Log in to the G350 Media Gateway interface with a direct connection to the Services port Log in to the G350 interface with...
Page 11 Contents • Avaya Site Administration Configure Avaya Site Administration Logging in to the S8300 with Avaya Site Administration • Navigational aid for CLI commands • Terminal emulation function keys for Communication Manager G350 and Media Module LEDs • G350 front panel LEDs...
Page 12 Communication Manager hardware traps Backup and restore traps • S8300 alarms – _WD • S8300 alarms – ENV • S8300 alarms – login • S8300 alarms – _TM • S8300 alarms – UPS Index Maintenance of the Avaya G350 Media Gateway June 2004...
Page 13: About This Book
You can download the latest version of the Maintenance of the Avaya G350 Media Gateway 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 14: Related Resources
About this book Related resources Related resources For more information on the Avaya G350 Media Gateway and related features, see the following books: Title Number Overview of the Avaya G350 Media Gateway 555-245-201 Installation of the Avaya G350 Media Gateway...
Page 15: Sending Us Comments
E-mail, send your comments to: document@avaya.com • Fax, send your comments to: 1-303-538-1741 Ensure that you mention the name and number of this book, Maintenance of the Avaya G350 Media Gateway, 555-245-105. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 16 About this book Sending us comments Maintenance of the Avaya G350 Media Gateway June 2004...
Page 17: Maintenance Overview
The G350 with a Media Server infrastructure is comprised of three modular elements: Media Gateways, Media Servers, and Software. Integration with your network system The G350 with a Media Server incorporates the following features that help it fit easily into your system: • It is built around open IP standards (H.248 and H.323).
Page 18: Maintenance Strategy
G350. The latter subsystems are not monitored directly by a Media Server. It is anticipated that future development will enhance the capability of the G350’s maintenance software to maintain all subsystems, which will lessen the G350’s dependence on a Media Server.
Page 19: Media Module Maintenance
Modules are administered from the server, using Communication Manager. Maintenance for each Media Module is very similar to that for its respective DEFINITY server circuit pack counterpart. Field replacement of Media Modules can be performed in many cases without removing power to the G350 (hot swapping).
Page 20: Maintenance Access To The Avaya G350 Media Gateway And Media Servers
Avaya Integrated Management • Avaya QoS Manager You can access the Avaya G350 Media Gateway and the Avaya S8300 Media Server in several ways: • Web server access to the Media Gateway or Media Server IP address (accesses Web page with Online Help) •...
Page 21: Web Interface
The Avaya G350 Media Gateway Command Line Interface (CLI) provides access to configurable and read-only data of all G350 subsystems as well as running tests and displaying results. As a minimum, the CLI supports all functionality the Device Manager provides. It provides access to the status, parameters, and test of Media Modules, IP Entity Configuration, TFTP/FTP Servers, and DSP/VoIP resources.
Page 22: Useful Terms
ICC, Internal Call Controller S8700 Media Server (Could also be a ECC, External Call Controller non-co-resident S8300 or S8500) MGP, Media Gateway Processor 860T Processor Layer 2 Switching Processor P330 Stack Processor, i960 Processor Maintenance of the Avaya G350 Media Gateway June 2004...
Page 23: G350 Component Maintenance
® Power cords Each G350 Media Gateway ships with one power cord, suitable for the local region. If the power cord provided with the equipment does not have the correct plug configuration needed in a particular country, please refer to the cordset specifications below:...
Page 24: Replacing The Avaya G350 Media Gateway
G350. To replace the G350: If the original G350 is still in operation, power down the system. This should be done at a time when there will be the minimum interruption in service. Perform a shutdown of the S8300 Media Server, if present, using either the Web interface or manually, using the shutdown button on the S8300 faceplate.
Page 25 Manager Version Files Files Server Screens 2.0 or Later Translations (not for an Translations (not for an Click Continue, LSP) LSP) each screen System & Server System & Server Security Security Maintenance of the Avaya G350 Media Gateway June 2004...
Page 26 After 80 seconds, the YELLOW ACT LED is illuminated, indicating that process priorities have been equalized, and that diagnostic information has been saved for later analysis. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 27 Local Survivable Processor (LSP). Although the S8300 can fit into any of the slots on the G350, it only functions when inserted in Slot V1 on the left side of the G350. The plate above the slot must be removed to provide clearance for the S8300.
Page 28 Loosen the two captive screws on the S8300. Remove the plate between slots V1 and V2, labelled “Remove before removing or inserting S8300 module”. Disengage and remove the S8300 from the G350. Replacing the S8300 Hard Drive If you are replacing the entire S8300 board, proceed to Reinserting the S8300 Media Server.
Page 29 IC E I C E 1. S8300 Circuit Board 2. Hard Drive 3. Hard-Drive Standoffs 4. Screws 5. Ribbon Cable Connector 6. Hard-Drive Connector Pins 7. Optional CWY1 Board indchd3 KLC 120402 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 30 G350 component maintenance Reinserting the S8300 Media Server To reinsert the S8300 Media Server into the G350: Insert the S8300 into slot v1 of the G350 (refer to Figure 2, Align the S8300 Media Server/LSP, on page 30). With the optional CWY1 and hard drive attached to the S8300 board, insert the S8300 board about 1/3 of the way into the guides (the guides are in slot v1 for the S8300).
Page 31 Figure 3, S8300 Media Server Replacement Flowchart, on page 33 shows several tasks for the G350/S8300 system solution, depending on operational and configuration factors. The letters in the following list correspond to the letters in Figure 3, S8300 Media Server Replacement...
Page 32 Table 4, Backup and Restore Requirements, on page 25). Installation procedures for a new G350/S8300 are described in detail in Installation of the Avaya G350 Media Gateway Controlled by an Avaya S8300, S8500, or S8700 Media Server, 555-245- 104. If an upgrade is necessary, these procedures are described in detail in Upgrade and Service Guide for the Avaya G350 Media Gateway, 555-245-106.
Page 33 Perform Upgrade Installation Backups? Files Procedures Install Patch If Necessary Configure Server Messaging? Backup System Restore Backup Files Install Intuity Embedded? AUDIX? IA770 AUDIX Done Install Intuity Install Other AUDIX LX Messaging Maintenance of the Avaya G350 Media Gateway June 2004...
Page 34: Media Modules
CAUTION: The MM312, MM314, MM340, MM342, MM714 and MM722 are not supported by the Avaya G700 Media Gateway. Do not insert an MM312, MM314, MM340, MM342, MM714 or MM722 media module into an Avaya G700 Media Gateway. The information in...
Page 35 • Changing the Media Module type Since Voice Media Modules on the G350 are administered by Communication Manager, the modules are not inserted until the G350 registers with the Communication Manager. Likewise, all Voice Media Modules and associated Maintenance Objects are removed if the G350 link goes down. Data Media Modules are operational regardless of the G350 registration status.
Page 36 The G350 then sends appropriate H.248 messages to the controller, creating Communication Manager objects. You can hot-swap voice modules. This means you can add a voice module to the Avaya G350 Media Gateway while the system is running, without any disruption to your network. Configuration of the G350 is not necessary when you add a voice module.
Page 37 G350 component maintenance Permitted Slots The G350 chassis has six media module slots, marked V1, V2, V3, V4, V5, V6. Each media module is restricted to certain slots. Before inserting Media Modules, consult the following table to find out which Media Modules can be...
Page 38: Facility Test Call
DID trunks cannot be accessed. NOTE: Do not use this trunk test call procedure to test ISDN-PRI or ATM-CES trunks. For more information about testing ISDN-PRI or ATM-CES trunks, see ATM-BCH, Test #258. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 39 — X = Slot number (1 - 5, if no S8300/LSP in Slot 1) — 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 40: Setting G350 Synchronization
MM710 up as the primary synchronization source for the G350. In so doing, clock sync signals from the Central Office (CO) are used by the MM710 to synchronize all operations of the G350. If no MM710 is present, it is not necessary to set synchronization.
Page 41: Viewing G350 Sync Sources
YELLOW ACT LED to be on. • When the MM710 is driving a clock sync source line to the G350 main clock, the YELLOW ACT LED does not indicate port activity, but instead indicates that the MM710 is the sync source by flashing with a regular 3-second period: —...
Page 42 Comment: The ACT LED does not change its behavior. NOTE: The following command is sent from the SAT CLI, and not from the G350 CLI. To test for slippage, from the SAT, use the command: test mo logical 4255 physical 1v4 test 144...
Page 43 G350 component maintenance Setting G350 synchronization To activate the secondary sync source: Table 13: G350-001# set sync source secondary G350-001# show sync timing SOURCE STATUS FAILURE Primary Locked Out None Secondary Active None Local Standby None Note: The system uses one clock at a time only: therefore only the secondary is active and the primary is locked out.
Page 44: Ip Telephones
NOTE: Refer to 4600 Series IP Telephone LAN Administration, 555-233-507 for troubleshooting details and error codes, as well as the phone administration information. The Avaya 4600-Series IP Telephones are relatively trouble-free. Table 17, IP Phone Problems and Solutions, on page 44 provides the most common problems an end user might encounter. For other IP Telephone questions or problems, contact your Telephone System Administrator.
Page 45 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. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 46: Reset And Power Cycle
This basic reset procedure should resolve most problems. To reset your phone: Press Hold. Using the dial pad, press the following keys in sequence: 73738# The display shows the message “Reset values? * = no # = yes.” Maintenance of the Avaya G350 Media Gateway June 2004...
Page 47 If power-cycling does not correct the problem, a more severe power cycle routine can be performed by unplugging both the phone and the Ethernet cables. However, because this type of power cycle involves reprogramming certain values, it should only be performed by your Telephone System Administrator. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 48 G350 component maintenance IP telephones Maintenance of the Avaya G350 Media Gateway June 2004...
Page 49: Avaya Communication Manager Controlled Maintenance
Avaya Communication Manager controlled maintenance G350 subsystems maintained by Communication Manager Avaya Communication Manager controlled maintenance This chapter addresses Avaya G350 Media Gateway subsystems and components that are controlled by Avaya Communication Manager SAT commands. G350 subsystems maintained by Communication Manager...
Page 50: Sat Commands Specific To The Avaya G350 And G700 Media Gateways
This is a destructive command so the Media Module must be busied out before a demand reset can be done. • If an invalid G350 number is entered with the test command for a Media Module board or port, the following message is displayed: “xxxx” port/board is not valid •...
Page 51 Maintenance commands add/change/display/status media gateway [x, next] Figure 5: Media-Gateway Administration Screen The Avaya G350 and G700 Media Gateways Primary Server administers the Avaya G350 and G700 Media Gateways by the command add media-gateway x add media-gateway next , where x is valid between the range of 1 to the capacity for a given primary server, and next is the next available number to be administered.
Page 52 The Avaya G350 Media Gateway Media Modules are listed by Slot V1-V6, followed by the input field for ‘Module Type’. The Avaya Media Modules can be one of six types: analog, BRI, DCP, ETH 24P, ICC, or DS1 (also referred to as T1/E1). The default for the Module Type field is a blank field.
Page 53 Avaya Communication Manager controlled maintenance Maintenance commands list media-gateway From the primary server, the command shows all Avaya G350 and G700 Media list media-gateway Gateways currently administered. NOTE: The "print" modifier is supported on Linux and Windows platforms only if the terminal type for the command is 4410.
Page 54 The populated IP address is persistent over reboots. list configuration media-gateway The command list configuration media-gateway x lists all the assigned ports on the Media Modules for the specified Media Gateway. Figure 7: List Configuration Media-Gateway Screen Maintenance of the Avaya G350 Media Gateway June 2004...
Page 55 The alarms displayed here are only associated with board type alarms on the Media Modules. Status for VoIP and Media Gateway alarms are provided via the Media Gateway Processor CLI. Figure 8: Status Media-Gateways Screen Maintenance of the Avaya G350 Media Gateway June 2004...
Page 56: Hidden Communication Manager Sat Commands
Hidden Communication Manager SAT commands Certain Communication Manager SAT commands have no practical use or are not supported on an Avaya G350 Media Gateway. These commands are removed from the S8300 Media Server/LSP software to prevent any misunderstanding or confusion as to what functions are supported. The S8300 Media Server/LSP runs a subset of Communication Manager code.
Page 57 (cabinet) isdnpri-testcall modem-pool hardware-group (carrier) packet-interface port_network pnc-standby hardware-group (pnc) pgate-port tone-clock host-adapter tone-clock interface port-network isdnpri-testcall switch-node led (switch-node) synchronization maintenance system mass-storage modem-pool network-control packet-interface 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 58: Dynamic Call Admission Control
Dynamic Call Admission Control In order to manage the flow of calls and voice data on the G350 most efficiently, the Media Gateway Controller must have real-time information about the network topology and currently available bandwidth.
Page 59: Using Dynamic Cac On The Media Gateway Controller
System resets There is no change in how Communication Manager functions for system resets in Avaya S8300 Media Server with a media gateway. Although translations may be present for a media gateway, Communication Manager waits for a link to be established before attempting to access the media gateway. Upon notification that registration has occurred, maintenance waits for the Media Module Manager to indicate that a Media Module is present before attempting to determine which Media Modules are present.
Page 60: H.248 Server-To-Gateway Link Recovery
In this case, the log entries may still be useful in tracking down a potential source of trouble. 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: •...
Page 61 The length of time that the gateway 1-60 spends trying to connect to all alternate resources. The sequence of events during Link Recovery is described in Table 24, General Link Recovery process, on page 62. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 62 Note: If the Link Loss Delay Timer expires but the gateway successfully connects with an alternate resource, the system generates a warning alarm anyway, even though the H.248 link is up. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 63 Communication Manager. • The maintenance subsystem begins a context audit after Link Recovery. Link recovery unsuccessful If link recovery was unsuccessful, both Communication Manager and the media gateway generate events and alarms. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 64 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 65 Avaya Communication Manager controlled maintenance System resets Link recovery administration Link Recovery requires both Avaya Communication Manager and Media Gateway administration. Link Recovery administration involves: • Administering the server timer • Administering the Media Gateway — Administering the gateway timers and Transition Point —...
Page 66 C-LAN circuit pack and then tries one other alternate resource during the Primary Search Timer period. See Table 23, Link Recovery Timers, on page 61 for more information about the Link Recovery timers. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 67 ASAI-based applications that utilize timing loops, time- (ASAI) related methods, or events might not perform as intended. In addition, applications that do not accommodate time- outs or missing state transition(s) might behave unpredictably. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 68 You can use the S8300 Web Interface to shutdown and reboot each LSP registered with the server. This is the recommended way for customers to reestablish the LSP’s connection to the primary server. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 69: Maintenance Objects
Alarm and Error logs and as output of various commands such as (see port test board Figure 10, Display of test board command, on page 70). Maintenance of the Avaya G350 Media Gateway June 2004...
Page 70: Avaya G350 Media Gateway Mos
Avaya Communication Manager controlled maintenance Maintenance Objects Figure 10: Display of test board command Avaya G350 Media Gateway MOs The following list shows new, G350 specific maintenance objects. Other maintenance objects have been modified slightly for the G350. • MED-GTWY (MEDIA GATEWAY) •...
Page 71: Mo Groupings By Mm Type
Avaya Communication Manager controlled maintenance MO groupings by MM type MO groupings by MM type Table 28, Media Module Tests, on page 71 shows MO groupings by Avaya Media Module type. Table 28: Media Module Tests Media Module Maintenance Object...
Page 72: Mo Test Commands
2 = the number of times the test should be repeated. Abort Code 1412 Tests that do not run on the G350 will abort with Abort Code 1412. Tests that abort are listed under each MO, but are not described.
Page 73: Alarm-Pt (Alarm Port)
SeSquence and investigate errors. (b) Indicates that the Media Module has been removed or has been insane for more than 11 minutes. To clear the error, reseat or replace the Media Module. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 74: System Technician-Demanded Tests: Descriptions And Error Codes
Enter test external-device-alarm port GGGVSpp to determine if the port is reporting an EXT-DEV failure before retesting. If the port has no EXT-DEV failure, retry the command at 1-minute intervals for a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 75 Retry the command at 1-minute intervals for a maximum of 5 times. PASS The port’s battery feed chip is able to provide power to the external device alarm to detect contact closure. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 76: Station Status And Translation Audits And Updates Test (#36)
5 times. FAIL The translation update failed. This does not indicate a hardware problem but may be an internal software error. PASS The software and the port processor have the same status. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 77: An-Ln-Pt (Analog Line Port)
Analog Line Port Note: You must consult local records for the location and designation of the equipment rack where the G350 is mounted. The MM711 Analog Trunk and Line Media Module provides 8 ports, each of which may be administered in any of several ways, as described in maintenance object MG-ANA.
Page 78 — If this disturbs the customer or the terminal equipment, disable it by setting the Tests field on the change station extension form to n. This may also disable Test #35. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 79: System Technician-Demanded Tests: Descriptions And Error Codes
: This test will abort with Error Code 1412. NPE Crosstalk Test (#6) Note : This test will abort with Error Code 1412. Station Status and Translation Audits and Updates Test (#36) *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 80: Battery Feed Test (Also Called Port Diagnostic Test) (#35)
To enable the test for a particular station being tested, enter change station extension . Change the Test? field on the station form to y. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 81 System resources required to run this test are not available. Retry the command at 1-minute intervals no more than 5 times. If the test continues to abort, escalate the problem. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 82 Use the test board GGGVS long command. This re-establishes the link between the internal ID and the port. If this is not the case, check to make sure that a valid board is inserted. 3 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 83: Station Status And Translation Audits And Updates Test (#36)
Use the status station extension command to determine when the port is available. Retry the command at 1-minute intervals no more than 5 times. If the test continues to fail, escalate the problem. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 84: Station Present Test (Also Called Ringing Application Test) (#48)
If this ringing disturbs the customer or the terminal equipment, you can disable it via the Tests field on the change station extension form. However, on some software releases, Tests #6, 7, and 35 also are disabled. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 85: Maintenance Of The Avaya G350 Media Gateway June
System resources required to run this test are not available. Retry the command at 1-minute intervals no more than 5 times. If the test continues to abort, escalate the problem. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 86 Use the test board GGGVS long command. This re-establishes the link between the internal ID and the port. If this is not the case, check to make sure that a valid board is inserted. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 87: Co-Ds1 (Ds1 Co Trunk)
DS1 CO Trunk Note: For Avaya G350 systems you must consult local records for the location and designation of the equipment rack where the G350 is mounted. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options command and that at least 75 percent of the trunks in this trunk group are alarmed.
Page 88: Error Log Entries And Test To Clear Values
(h) Error Type 1793—DS1 Interface Media Module is out-of-service. Look for MG-DS1 errors in the Hardware Error Log. Refer to the DS1 Trunk Media Module or MG-DS1 Media Module Maintenance documentation for details. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 89: System Technician-Demanded Tests: Descriptions And Error Codes
Note: This Test ABORTS Conference Circuit Test (#7) Note: This Test ABORTS DS1 CO Trunk Seizure Test (#314) Note: This Test ABORTS Port Audit and Update Test (#36) *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 90: Port Audit And Update Test (#36)
If it is OK to put the trunk back in service, use the release trunk command to put the trunk back in service, and then retry the test. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 91 (even though the reset board command does work). The software puts the hyperactive board back in service after the hyperactivity clears. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 92: Co-Trk (Analog Co Trunk)
GGGVSpp l Analog CO Trunk Note: For Avaya G350 systems you must consult local records for the location and designation of the equipment rack where the G350 is mounted. **A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options command and that at least 75% of the trunks in this trunk group are alarmed.
Page 93 CO Response: Trip ringing, provide loop current. PBX On-Hook first (Drop Message): Open the Tip-Ring Loop, no loop current. CO Response: Open circuit on Tip. CO On-Hook first (Disconnect): Open circuit on Tip, no loop current. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 94: Error Log Entries And Test To Clear Values
*Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures. **Major alarms may be downgraded to Warning alarms based on the value used in the set options command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 95 Call Seizure Tests have passed. Problems at the CO may cause this condition rather than problems with the PBX. • If test fails after two repetitions, replace Media Module. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 96 Tip and Ring observations. If the line is determined to be noisy, refer the problem to the CO. If the reverse current detector is defective, ignore this error. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 97 Busyout the affected port, and run a long test. If CO Demand Diagnostic Test #3 passes and this error keeps occurring, refer problems to CO. Release the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 98: System Technician-Demanded Tests: Descriptions And Error Codes
MFT/Range Extenders are being used. If extenders are present, then there is a good chance that there is excessive loop current, which will cause Test #3 to log errors. However, all else being normal, these errors should not affect the customer. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 99: Dial Tone Test (#0)
5 times. 1005 ABORT Trunk has been administered as incoming-only; dial tone can only be obtained on outgoing trunks. This is a normal condition. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 100 Repeat test on both trunks and determine if problem follows trunk or remains at original port. If problem follows trunk, refer problem to CO. If problem remains at port, replace circuit pack and repeat test. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 101: Co Demand Diagnostic Test (#3)
Tip lead. This test also verifies that there is no external ground on the Ring lead. In the absence of other failures, the Media Module should be replaced only if this test fails with the CO line disconnected. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 102 2000 ABORT Response to the test was not received within the allowable time period. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 103 Use the reset board command. Use the release busy board command. Use the test board command. This should re-establish the linkage between the internal ID and the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 104: Port Audit Update Test (#36)
If the trunk is out-of-service, continue to Step 2. Enter release trunk command to put trunk back into in-service. Retry the test command. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 105: Did-Ds1 (Direct Inward Dial Trunk)
– The trunk is in an activated state and can be used for incoming calls. If the DS1 Media Module is out-of-service, then all trunks on the DS1 Interface Media Module are put into the out-of-service state and a Warning alarm is raised. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 106: Error Log Entries And Test To Clear Values
Error Type 1—DS1 Interface Media Module detects a hardware error on the DS1 DID trunk. The Aux Data field indicates the following: 57476 On-hook before wink 57477 On-hook before ready to receive digits 57485 Wink too short for valid signal Maintenance of the Avaya G350 Media Gateway June 2004...
Page 107: System Technician-Demanded Tests: Descriptions And Error Codes
: This test will abort with Error Code 1412 Conference Circuit Test (#7) Note : This test will abort with Error Code 1412 Port Audit and Update Test (#36) *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 108: Port Audit And Update Test (#36)
Response to the test was not received in the allowable time period. 2100 ABORT Could not allocate resources to run this test. Retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 109 Use the test board long command. This should re-establish the linkage between the internal ID and the port. If this is not the case, check to see that there is a valid board inserted. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 110: Did-Trk (Direct Inward Dial Trunk)
Settings must be compatible with the local environment and with parameter settings on the far-end. Refer to Administrator’s Guide for Avaya Communication Manager, 555-233-506, for information on how to administer trunks. The Application Notes section of that book shows the correct settings for administrable timers and other parameters on a country-by-country basis.
Page 111: Ports Out-Of-Service Without Errors Or Alarms
*Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures. **Major alarms may be downgraded to Warning alarms based on the value used in the set options command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 112 Refer problem to CO. • — Digit detection CO is starting new rotary dial digit within 150 msec of previous digit. Verify trunk administered interdigit timing parameters. Refer problem to CO. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 113: System Technician-Demanded Tests: Descriptions And Error Codes
Note: This test will abort with Error Code 1412 Port Diagnostic Test (#35) Looparound and Conference Circuit Test (#33) Note: This test will abort with Error Code 1412 Port Audit Update Test (#36) *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 114: Port Diagnostic Test (#35)
Response to the test was not received within the allowable time period. 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 115 Use the release busy board command. Use the test board command. This should re-establish the linkage between the internal ID and the port. If the problem persists, replace the circuit pack. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 116: Port Audit Update Test (#36)
1-minute intervals a maximum of 5 times. 2100 ABORT Could not allocate the necessary system resources to run the test. Retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 117: Dig-Line (Digital Line)
DIG-LINE testing can be affected by the health of the digital line Media Module. Keep this in mind when investigating digital line problems. There are instances where the service state of a station is mentioned. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 118: Programmable Terminals
(Transmission & Sidetone) 302B1 Adjunct Levels System level 84xx (Transmission & Sidetone) Handset Expander Option System level 84xx Administrable Options (Speakerphone & Mute Button) Per-terminal 84xx Administrable Softkeys Per-terminal, 8410D, 8434D System level Maintenance of the Avaya G350 Media Gateway June 2004...
Page 119: Nonvolatile Memory
118, these changes can be for a specified terminal or may be system-wide. If the change is for system-level parameter, a background global update request is made to download all programmable terminals. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 120: Demand Download Actions
Demand Download Actions Busyout/Release Command A maintenance demand busyout/release request for a station will cause the terminal to be downloaded regardless of its previous download status. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 121: Status Of Parameter Downloads
Terminal is busy programming data from a previous PROGRAM message. • Terminal is in the Programming Disabled state. • Terminal is in the Local Program Options Mode. • Terminal is disconnected or out of service (use status station command). Maintenance of the Avaya G350 Media Gateway June 2004...
Page 122: Error Log Entries And Test To Clear Values
*Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures. **Major alarms may be downgraded to Warning alarms based on the value used in the set options command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 123 No action is necessary. • The Media Module’s message buffer is full. This may be caused by having many display phones with heavy traffic connected to the Media Module. No action is necessary. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 124: System Technician-Demanded Tests: Descriptions And Error Codes
Digital Line NPE Crosstalk Test (#9) Note: This Test ABORTS Digital Line Electronic Power Feed Test (#11) DIG-LINE Station Lamp Updates Test (#16) Station (Digital) Audits Test (#17) *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 125: Digital Line Electronic Power Feed Test(#11)
If the port status is idle, then retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 126 Use the release busy board command. Use the test board command. This should re-establish the linkage between the internal ID and the port. If the problem persists, replace the circuit pack. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 127: Dig-Line Station Lamp Updates Test (#16)
If either list config or display port indicates that the port is not a TTI port, escalate the problem. If both commands indicate that the port is a TTI port, the abort is correct, and no action is necessary. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 128: Digital Station Audits Test (#17)
This information is checked and a pass/fail result is provided. • — Ringer Update Test This updates the digital telephone ringer state according to the processor records. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 129 If both commands indicate that the port is a TTI port, the abort is correct, and no action is necessary. 2000 ABORT Response to the test was not received in the allowable time period. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 130: Diod-Trk (Diod Trunk)
Refer to the Administration Manual for information on how to administer trunks. The Application Notes section of that book shows the correct settings for administrable timers and other parameters on a country-by-country basis. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 131: Services Supported By Diod Trunks
PBX Off-Hook (Answer Message): Close loop CO Response: Trip ringing, provide loop current. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop current CO Response: CO goes to idle state (see Note). NOTE: CO does not normally provide an On-Hook (Disconnect) signal. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 132: Error Log Entries And Test To Clear Values
This indicates that the CO releases the trunk at least four minutes after the PBX dropped the call. This error code is only logged as an informational event and causes no other testing to occur. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 133 Busyout the affected port, and run a Long test. If Dial Tone Test #0 passes, ignore this error. Release the port. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 134: System Technician-Demanded Tests: Descriptions And Error Codes
Note: This Test will abort with Error Code 1412 Looparound and Conference Test (#33) Note: This Test will abort with Error Code 1412 Audit Update Test (#36) *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 135: Port Audit Update Test (#36)
Enter status-command to verify that the trunk is in-service. If the trunk is in-service, no further action is necessary. If the trunk is out-of-service, continue to Step 2. Enter release-trunk command to put trunk back into in-service. Retry the test command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 136: Isdn-Lnk (Isdn-Pri Signaling Link Port)
The ISDN-LNK in turn depends on the MM710 it resides on which provides the link to the processor. If there are problems with the ISDN-LNK, also investigate the MM710 Interface Media Module (MG-DS1). Maintenance of the Avaya G350 Media Gateway June 2004...
Page 137: Hardware Error Log Entries And Test To Clear Values
Maintenance will not start any testing or generate any alarms in response to this error. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 138: System Technician-Demanded Tests: Descriptions And Error Codes
This test will ABORT with error code 1412, Signaling Link Board Check (#643) Signalling Port LAN Loopback Test (#939) This test will ABORT with error code 1412. *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 139: Signaling Link Board Check (#643)
Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 140: Isdn-Sgr (Isdn-Pri Signaling Group)
D-channel goes down. If the active D-Channel does go down, the backup D-Channel takes over and provides signaling for all the B-channels in the signaling group. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 141: Error Log Entries And Test To Clear Values
Check out other errors against ISDN-SGR, ISDN-TRK, and other hardware components on the link. There is no test to clear these errors. The error counter is decremented by 1 every 15 minutes. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 142 They provide added data that may prove useful when tracking down obscure networking and routing problems. The following table provides more information: Maintenance of the Avaya G350 Media Gateway June 2004...
Page 143 Consider modifying all routing patterns containing this the call may not be trunk group, to route calls around the network which is successful). out of service. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 144 This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 145 (for example, some ISDN switches may not allow a voice station to call a data extension). 3942 Timer expiry: T310 time- out, no answer to CALL PROCEEDING. 3 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 146: System Technician-Demanded Tests: Descriptions And Error Codes
Re-attach the disconnected PRI terminal adapter, or Disable the rollabout video feature on this board by entering change ds1 GGGVSpp and set field “Alarm when PRI Endpoint Detached?” to “y.” 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 147: Remote Layer 3 Query (#637)
The ISDN PRI Specification allows up to 2 minutes for a response. Check the Error Log for ISDN-SGR (ISDN-PRI Signaling Group) errors of type 2305 for evidence of a Remote Layer 3 Query failure. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 148 ABORT, since this test cannot run unless at least one B-channel is administered. If at least one B-channels is administered, there is an internal system error. Retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 149 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 150: Secondary Signaling Link Hardware Check (#639)
Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 151: Layer 2 Status Test (#647)
Channel (D-channel) at the far end has been administered correctly. Verify that the DS1 port used for the Primary D-channel has not been busied out at the far end. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 152 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 153: Isdn-Trk (Ds1 Isdn Trunk)
GGGVSpp l DS1 ISDN Trunk Note: For Avaya G350 Media Gateway systems you must consult local records for the location and designation of the equipment rack where the G350 is mounted. For additional repair information, see also DS1-BD for TN767 ports and MM710.
Page 154: Alarming Based On Service States
As a port on a DS1 Media Module (MG-DS1), and as part of a signaling group dependent on a D-channel (ISDN-LNK) for signaling, operation of the ISDN-TRK is dependent on the health of these other maintenance objects. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 155: Ds1 Isdn Trunk Service States
This state is supported only by systems using country protocol 1 (including US). The near- end is waiting for a response from the far-end to a maintenance message requesting that the B-channel be transitioned to the maintenance service state. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 156 Repeated failure of far end Maintenance software will to respond to messages. periodically try to resend messages. You can speed the process with test trunk grp#/mbr# and/or test signaling-gr #. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 157: Error Log Entries And Test To Clear Values
*Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures. **Major or minor alarms may be downgraded to Warning alarms based on the value used in the set options command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 158 Service State Audit attempt failed (see Test #256). The trunks will not be usable for any outgoing calls (although incoming calls will be accepted) until the test passes and the trunk state is changed to in-service (use status trunk group#/member# to investigate trunk status). Maintenance of the Avaya G350 Media Gateway June 2004...
Page 159 The Warning alarm will be retired automatically whenever an outgoing or incoming call that uses this trunk is answered by the called endpoint. If problems persist, then busy-out the ISDN trunk to take it out of the hunt group. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 160: System Technician-Demanded Tests: Descriptions And Error Codes
Service State Audit Test (#256) Call State Audit Test (#257) ISDN Test Call Test (#258) Note: This Test ABORTS when run on a Avaya G350 Media Gateway system. D = Destructive, ND = Non-destructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 161: Audit And Update Test (#36)
Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 162: Signaling Link State Check Test (#255)
Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 163: Service State Audit (#256)
The trunk is not in the out-of-service/far-end state, which is required to run this test on systems using a country protocol other than 1. 1117 ABORT A service state audit message is outstanding. Wait 2 minutes and then try again. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 164 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 165: Call State Audit Test (#257)
ISDN state of the trunk). 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 166: Med-Gtwy (Media Gateway)
Alive messages that are exchanged between the server and media gateway fail. These messages indicate the status of the H.248 link between the two. If the keep alive messages are active all is well, if not an error is logged. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 167: Error Log Entries And Test To Clear Values
Error Type 257: If the server is an LSP, this error type indicates that at least one Media Gateway is registered with the LSP. • Error Type 513: this error type indicates that there is a problem on the G350. Log on to the G350 and check the error log for problems using the G350 CLI. •...
Page 168 MWI The Avaya MM714 Media Module has 8 ports. Ports 1-4 can only be configured as lines, and ports 4-8 can only be configured as trunks. The MM 711 Analog Media Module supports eight analog interfaces allowing the connectivity of Loop Start, Ground Start, Analog DID trunks, and 2-wire analog Outgoing CAMA E911 trunks.
Page 169: System Technician-Demanded Tests: Descriptions And Error Codes
The MM720 and MM722 BRI Media Modules contain eight, 4-wire ports that interface to the network at the ISDN S/T reference point over two 64 Kb/s channels (B1 and B2) and over a 16Kb/s signaling (D) channel. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 170: Leds
171 gives definitions for the generic ISDN Interface Reference Points. Figure 11: Integrated Trunk-Side BRI, ISDN Interface Reference Points 4-Wire 4-Wire Terminal Adapter 2-Wire 4-Wire 2-Wire 4-Wire 2-Wire 2-Wire ISDN Interface Reference Points cydfisdn RPY 072397 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 171: Error Log Entries And Test To Clear Values
None MINOR • 257 (b 65535 Control Channel Loop Test MINOR test board GGGVM r 20 (#52) • 513 (c 4352 to None 4357 • 769 (d 4358 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 172 See the repair procedure in Note ( • Error Type 769 – The circuit pack detects a program logic error. While no action is required, this error can lead to other errors against this circuit pack. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 173: System Technician-Demanded Tests: Descriptions And Error Codes
Control Channel Loop-Around Test (#52) NPE/NCE Audit Test (#50) Aborts with Error Code 1412 LAN Receive Parity Error Counter Test (#595) SAKI Sanity Test (#53) * D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 174: Mg-Dcp (Digital Line Media Module)
Note: You must consult local records for the location and designation of the equipment rack where the G350 is mounted. NOTE: Refer to XXX-BD (Common Port Media Module) for Media Module level errors. See also “DIG-LINE” for related line information. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 175: Mg-Ds1 (Ds1 Interface Media Module)
EC Direction determines the direction from which echo will be eliminated, ether inward or outward. • EC Configuration is the set of parameters that will be used when cancelling echo. This information is stored in firmware on the MG-DS1 Media Module. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 176: Mm710 Ds1 Media Module
Each trunk, line, or endpoint has its own maintenance strategy, but all depend on the health of the MG- DS1 Interface Media Module. Refer to the following MOs for details: TIE-DS1, CO-DS1, DID-DS1, OPS-LINE, ISDN-TRK, ISDN-LNK, ISDN-SGR, WAE-PT and PE-BCHL. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 177: Media Module Administration And Options
None MIN/WRN** 65535 Control Channel MINOR test board GGGVS l r 20 Loop Test (#52) 257(e) None 513(f) MIN/WRN** 514(g) 46086 MIN/WRN** 769(h) 46085 MIN/WRN** 770(i) 46096 MIN/WRN** 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 178 Slip Alarm Inquiry MIN/WRN** test board GGGVS r 6 3160 (m) Test (#144) 3585 to Misframe Alarm MIN/WRN** test board GGGVS r 6 3601 (o) Inquiry Test (#145) 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 179 Slip Alarm Inquiry MIN/WRN** test board GGGVS r 6 3160 (m) Test (#144) 3585 to Misframe Alarm MIN/WRN** test board GGGVS r 6 3601 (o) Inquiry Test (#145) 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 180 Execute the remove ds1 GGGVS and change media module GGGVS commands. • Error Type 18 — The MG-DS1 Interface Media Module has been busied out by a busyout board GGGVS command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 181 Clear the alarm using the following commands: busyout board GGGVS, reset board GGGVS, test board GGGVS long, release board GGGVS. If the error recurs within 10 minutes, replace the Media Module. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 182 AUX Data "minus 3072" shows the last slip count reported. • Error Types 3585 to 3601 — Error Type 3585 shows that this board is receiving misframes, and the AUX Data "minus 3584" shows the last misframe count reported. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 183 However, if this error type is logged when the Media Module is being lightly used, it may indicate a problem with the Media Module or the equipment attached to it. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 184: System Technician-Demanded Tests: Descriptions And Error Codes
Misframe Alarm Inquiry Test (#145) Translation Update Test (#146) SAKI Sanity Test (#53) Internal Looparound Test (#135) Note: This test will ABORT with Error Code 1412 *D = Destructive; ND = Nondestructive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 185: Control Channel Looparound Test (#52)
Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 186: Saki Sanity Test (#53)
FAIL The Media Module failed to reset. FAIL The Media Module failed to restart. Execute the reset board command again. If the problem persists, replace the Media Module. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 187: Loss Of Signal Alarm Inquiry Test (#138)
The MM710 Interface Media Module raises a Loss of Signal alarm after the signal has been lost for about 1 second. It will not retire the alarm until the signal has returned for about 10 seconds. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 188 In addition, many hardware errors would be logged against the associated trunk circuits. If the facility is OK and the error occurs again after 15 minutes, replace the Media Module. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 189 Use the test board long command. Use the release busy board command. If the test still fails replace the board. PASS DS1 signal is present and the physical link is healthy. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 190: Blue Alarm Inquiry Test (#139)
5 seconds on the DS1 line. Since LLB is a maintenance condition rendering all DS0 channels unavailable for signaling or bearer traffic, maintenance software treats this the same as a Blue Alarm. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 191 15 minutes, replace the Media Module. 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 192 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 193: Red Alarm Inquiry Test (#140)
Interface Media Module detects an LMA, the Media Module transmits a Remote Multiframe Alarm (RMA) to the remote DS1 endpoint. Maintenance software handles both Red alarm and LMA alarm(s) using the same mechanism. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 194 In addition, many hardware errors would be logged against the associated trunk circuits. If the facility is OK and the error occurs again after 15 minutes, replace the Media Module. 1 of 4 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 195 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 2 of 4 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 196 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 3 of 4 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 197: Yellow Alarm Inquiry Test (#141)
Remote Multiframe Alarm (RMA) indicates that the remote DS1 endpoint is in a Loss of Multiframe Alarm condition while the MG-DS1 Interface Media Module is administered using the DMI-BOS common channel signaling. The RMA is handled as a Yellow alarm. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 198 In addition, many hardware errors would be logged against the associated trunk circuits. If the facility is OK and the error occurs again after 15 minutes, replace the Media Module. 1 of 5 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 199 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 2 of 5 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 200 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 3 of 5 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 201 Media Module to the terminating device. Check premise distribution system (or intra-premise wiring) for physical connection failures. Replace the local MG-DS1 Interface Media Module and repeat the test. 4 of 5 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 202: Major Alarm Inquiry Test (#142)
Major alarm is cleared. The maintenance software places all trunks or ports on the Media Module in the out-of-service state if the Major alarm persists for more than 20 minutes. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 203 15 minutes, replace the Media Module. 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 204 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 205: Minor Alarm Inquiry Test (#143)
Media Module are kept in the in-service state after the Minor alarm is confirmed. The Minor Alarm Inquiry Test runs every 10 minutes until the Minor alarm is cleared. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 206 15 minutes, replace the Media Module. 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 207 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 208: Slip Alarm Inquiry Test (#144)
If the count of slips is over the threshold, a Minor alarm is raised against the MG-DS1 Interface Media Module. All trunks or ports of the MG-DS1 Interface Media Module remain in the in-service state. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 209 Media Module. 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 210 Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 211: Misframe Alarm Inquiry Test (#145)
MG-DS1 Interface Media Module. A Minor alarm against the MG-DS1 Interface Media Module is raised, but all trunks or ports of the MG- DS1 Interface Media Module remain in the in-service state. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 212 15 minutes, replace the Media Module. 2100 ABORT Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 213 DS1 endpoint. Check the physical connectivity of the MG-DS1 interface Media Modules and the cable. Replace the local MG-DS1 interface Media Module, and repeat the test. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 214 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 3 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 215: Translation Update Test (#146)
This test is executed only for MM710 Media Modules that have been administered on the DS1 Media Module form to provide echo cancellation. The MM710 must be busied out before this demand test is run. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 216 Retry the command at 1-minute intervals for a maximum of 5 times. 2500 ABORT Internal system error. Retry the command at 1-minute intervals for a maximum of 5 times. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 217 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 218: Mg-Icc (Internal Call Controller)
LSP and primary call controller. This is an indication that the LAN or the primary call controller is down. System Technician-Demanded Tests: Descriptions and Error Codes There are no System Technician-Demanded Tests associated with this MO. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 219: Plat-Alm (Platform Alarms)
Settings must be compatible with the local environment and with parameter settings on the far-end. Refer to “Administrator’s Guide for Avaya Communication Manager, 555-233-506” for information on how to administer trunks. The Application Notes section of that book shows the correct settings for administrable timers and other parameters on a country-by-country basis.
Page 220: Hardware Error Log Entries And Test To Clear Values
Type Data Board test trunk grp/mbr 1(a) 57476 57477 57485 57487 15(b) Port Audit and Update Test (#36) 18(c) busyout trunk WARNING release trunk grp/mbr grp/mbr* 19(d) None 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 221 This error can be caused by incompatible translations. Make sure the parameters administered on the DS1 Media Module form match those administered on the far-end switch. See Administrator’s Guide for Avaya Communication Manager, 555-233-506, for details. The Aux Data field indicates the following hardware error types:...
Page 222 Error Type 18—The DS1 tie trunk has been busied out by a busyout trunk grp/mbr command. No calls can be made on this trunk except for the Facility Access Test Call. Facility Access Test Calls are described in Chapter 6 and in Administrator’s Guide for Avaya Communication Manager, 555-233-506.
Page 223: System Technician-Demanded Tests: Descriptions And Error Codes
Table 124: TEST #36 Audit and Update Test 1 of 3 Error Test Code Result Description/ Recommendation ABORT Internal system error Retry the command at 1-minute intervals a maximum of 5 times. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 224 If the trunk is out-of- service, continue to step 2. Enter the release trunk command to put the trunk back into in-service. Retry the test command. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 225: Ds1 Tie Trunk Seizure Test (#136)
The trunk is administered with maintenance test disabled. • The outgoing signal type of the trunk is either automatic or immediate-start. • This test always passes if the associated board is the TN802 IP trunk Media Module. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 226 Verify that the ’Maintenance Test’ field on the ’Trunk Administration’ screen is set to ’n.’ To enable the test, change the trunk administration and enter ’y’ into the ’Maintenance Test’ field. Repeat the test. 1 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 227 DS1-BD (DS1 trunk Media Module) Maintenance documentation or to the MM-DS1 (MM-DS1 trunk Media Module) Maintenance documentation. Retry the test at 1-minute intervals for a maximum of 5 times. 2 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 228 ID and the port. If this is not the case, check to see that there is a valid board inserted. *Earlier G1 Software Versions reported Error Code 2053 as a FAIL. 3 of 3 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 229: Wae-Port (Wideband Access Endpoint Port)
DS1 facilities to connect Communication Manager to non-switched network services, such as the Avaya fractional T-1 service. An example of this is the Avaya Static Integrated Network Access, where a trunk group to AT&T 4ESS Switched Services shares an access T-1 facility with a Wideband Access Endpoint.
Page 230: Error Log Entries And Test To Clear Values
If the wideband access endpoint port is out of service, enter release access-endpoint extension to put it back into service. Retry the test command. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 231: Technician-Demand Tests: Descriptions And Error Codes
Sequence D/ND* NPE Crosstalk Test (#6) Note: This Test ABORTS with code 1412 when run on a Avaya G350 Media Gateway system. Conference Circuit Test (#7) Note: This Test ABORTS with code 1412 when run on a Avaya G350 Media Gateway system.
Page 232: Xxx-Bd (Common Port Media Module)
Note: You must consult local records for the location and designation of the equipment rack where the G350 is mounted. Refer to the appropriate Media Module documentation for the correct MO name displayed in this field. It usually ends with BD. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 233: Xxx-Bd Common Media Modules
Level Board Test to Clear Value test board GGGVS sh 1(a) Media Gateway MINOR removed or SAKI Sanity Test (#53) 18(b) busy-out board WARNING release board GGGVS GGGVS 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 234 If the test does not clear error 23, then execute reset board GGGVS and run the long test again. If the reset/test does not clear error 23, replace the Media Module. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 235 However, if this error type is logged when the Media Module is being lightly used, it may indicate a problem with the Media Module or the equipment attached to it. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 236: Technician-Demand Tests: Descriptions And Error Codes
The SAKI Sanity Test is run on other Media Modules only when they are reset via the reset board command. • This is only applicable to MM711 Analog Line Media Modules. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 237: Control Channel Looparound Test (#52)
Verify that the board is physically in the system. Verify that the system is not in a stage of booting up. Retry the command at 1-minute intervals for a maximum of 5 times. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 238: Saki Sanity Test (#53)
Media Module under test is providing timing for the platform, it cannot be reset without major platform disruptions (Note: For this type of system the sync timing source is local to the G350). Set the synchronization timing source to another DS1 interface Media Module located in the same G350 and retest.
Page 239: License And Authentication Files
S8300 Media Server, or all access to Avaya Communication Manager from any login is blocked. A new license file and the Avaya authentication file may be installed independently of each other or any other server upgrades.
Page 240 License and authentication files License and authentication file installation 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 241: Installing License And Authentication Files
Access the Maintenance web pages part of Avaya Integrated Management (AIM) from your laptop, using IP address 192.11.13.5. Logon at the Avaya Integrated Management Logon screen. The main menu for Avaya Integrated Management appears. Figure 12: Integrated Management Main Menu From the Integrated Management main menu, select Launch Maintenance Web Interface.
Page 242 Click Submit. A message appears telling you your installation was successful. From the navigation menu, select Security > Authentication File. The Authentication File web page appears. Figure 14: Authentication File Web Page Maintenance of the Avaya G350 Media Gateway June 2004...
Page 243: License Files For Different Configurations
G350 cannot be served by its primary Media Server. Each S8300 configured as an LSP has its own license file that contains the serial number of the G350 into which the LSP is physically inserted. As soon as the LSP becomes active and begins providing service as the Media Server, it invokes License-Error mode.
Page 244: License File Modes
A survivable processor begins to provide service, which causes a major alarm • The serial number in the license file does not match the serial number of the G350 into which the S8300 is physically inserted To resolve this problem: •...
Page 245: License And Options Forms Interactions
1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 246: Type Ii Entries
(V1), and an upper limit value (V2). V1 is never greater than V2. See Table 137, Type II and Type III Feature License Behavior, on page 246. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 247: Access And Login Procedures
This chapter describes the various ways of connecting to, and logging into, the S8300 Media Server and the Avaya G350 Media Gateway. Use this chapter as a reference for the other chapters in this book. The procedures in this chapter assume that you are connecting to the S8300 and/or the G350 with an Avaya Services laptop.
Page 248 Diagnosis of Media Server Alarm notification Remote access to the G350 Media Gateway Connect to the G350 remotely using a USB modem plugged in to the USB port of the G350. Tasks Diagnosis of media gateway Remote administration of media gateway...
Page 249: Connecting A Laptop To The S8300 Services Port
G350 to the customer’s LAN. There are various ways that the G350 is connected to the customer’s LAN, depending the G350’s configuration. • If you have a G350 by itself, or a G350 with a router, the G350 connects to the LAN via the ETH LAN port. •...
Page 250: Configuring The Laptop Network Settings
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 (formerly called DEFINITY One), try using that profile first before configuring a new one.
Page 251 Ethernet card. — Windows NT: On the Protocols tab, select in the installed network components list. TCP/IP Select the Properties button. In the TCP/IP Properties box, click the tab. IP Address Maintenance of the Avaya G350 Media Gateway June 2004...
Page 252 Tools > Internet Options Click the tab. Connections Click the button. LAN Settings Use a proxy server for your LAN is not selected, no change is necessary; click Cancel to exit. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 253: Connection Methods
— Crossover cables of various lengths are commercially available. — See Table 138, Crossover cable pinout chart, on page 254 for pinout connections if needed. Crossover of the transmit and receive pairs (as shown) is required. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 254: Connect Laptop To The G350 Serial Port
192.11.13.6 . Connect laptop to the G350 Serial port To configure a G350 that does not have an S8300, you may need to set up a direct connection from your laptop’s serial port to the G350 Console (serial) port. To connect a laptop directly to the serial port on the Avaya G350 Media Gateway:...
Page 255: Connect Laptop To Customer Lan
— Enable modem for unlimited incoming calls — use this option if you want to provide regular dial-up access to the Media Server for Services personnel or some other reason. The modem is now ready to receive calls. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 256 Use Windows for modem connection to the Media Server (Windows 2000 or XP) To use Windows for a 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...
Page 257 Communication Manager You can download the Avaya Terminal Emulator from the main menu for the VisAbility™ Management Suite. 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 258 To establish a LAN 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 259: Log In Methods
261. Log in methods This section describes how to log on to the Avaya G350 Media Gateway or the S8300 Media Server using Telnet or the built-in Web Interface and how to start a SAT session. These procedures assume: •...
Page 260: Log In To The Media Server From Your Laptop Using Telnet
Check the top of the right panel. — The Avaya Media Server you are logged into is identified by name and server number. — The S8300 Media Server number is always 1. Maintenance of the Avaya G350 Media Gateway...
Page 261: Open The Communication Manager Sat Screens
Log in to the G350 Media Gateway interface with a direct connection to the Services port Use this procedure to log in to the G350 Media Gateway interface when you have a direct connection with your laptop to the S8300 Services port.
Page 262: Log In To The G350 Interface With A Lan Connection
Log in to the G350 interface with a LAN connection Use this procedure to log in to the G350 interface when you have a connection to the customer’s LAN. To log in to the G350 interface with a LAN connection: With a connection to the customer’s LAN (either remotely or on site), telnet to the G350 interface...
Page 263: Log In To The G350 Interface With Device Manager
Avaya Site Administration is part of the Avaya VisAbility Suite. Normally, the customer can simply select Download next to the Administration item on the Media Server Home Page to download Avaya Site Administration. The customer then follows the directions presented by the download/installation wizard.
Page 264: Logging In To The S8300 With Avaya Site Administration
Import. For more information, refer to Online Help, Guided Tour, and Show Me, accessed from the Avaya Site Administration Help menu. To use Avaya Site Administration, open the application and select the switch (media server) you want to access. When prompted, log in.
Page 265: Navigational Aid For Cli Commands
<command> help displays help for <command> The command-line prompts in a G350 CLI session use the media gateway’s name that is assigned when it is configured. You can Telnet to another interface from a current Telnet session. Maintenance of the Avaya G350 Media Gateway...
Page 266: Terminal Emulation Function Keys For Communication Manager
Table 141, w2ktt terminal emulation function keys, on page 266 lists key presses for terminal w2ktt emulation. Table 141: w2ktt terminal emulation function keys Function Key Sequence Function Cancel Execute Help Next Page Previous Page Maintenance of the Avaya G350 Media Gateway June 2004...
Page 267: G350 And Media Module Leds
267 indicates the meanings associated with standard DEFINITY server LEDs. Although in some cases these LEDs have been augmented or modified for the S8300 Media Server and Avaya G350 Media Gateway, it is important to be aware of their standard meanings when viewing the system.
Page 268: System Leds
G350 and Media Module LEDs G350 front panel LEDs System LEDs The system LEDs show the status of the Avaya G350 Media Gateway. The following table shows the meaning of the system LEDs when they are lit: Table 143: System LEDs...
Page 269: Media Module Leds
269). On the Avaya BRI (MM720, MM722), Avaya DCP (MM312, MM712, MM717), Avaya WAN (MM340, MM342), and Avaya Analog (MM711, MM714) Media Modules, these are the only LEDs present. The Avaya T1/E1 Media Module (MM710) has an additional LED, as shown in Figure 18, T1/E1 Media Module with Fourth LED, on page 269.
Page 270 RED LED turns off. NOTE: For an S8300 configured as an LSP, the converse is true. If an Avaya G350 Media Gateway registers with an LSP, a major alarm is generated, and the RED LED turns on.
Page 271 During normal call processing operation, the YELLOW LED turns on whenever an Avaya G350 Media Gateway, an IP station, or an IP console is registered with the S8300. Likewise, it turns off when none of the IP endpoints are registered.
Page 272 OK To REMOVE - GREEN – lights up fourth then turns off ACT - YELLOW and OK To REMOVE - GREEN – light up a second time and then turn off Maintenance of the Avaya G350 Media Gateway June 2004...
Page 273: Mm710 T1/E1 Media Module Leds
— During board reset initialization testing (GREEN TST LED remains on until initialization testing is complete) NOTE: For ISDN operation, the Yellow LED will be turned on if ANY port has an active TDM connection (including the D-channel). Maintenance of the Avaya G350 Media Gateway June 2004...
Page 274 YELLOW ACT LED to be on. • When the MM710 is driving a clock sync source line to the G350 main clock, the YELLOW ACT LED does not indicate port activity, but instead indicates that the MM710 is the sync source by flashing with a regular 3-second period: —...
Page 275: Avaya Mm314 Media Module Leds
If the port LED is lit, the line is operating in Full Duplex mode. If the port LED is off, the line is operating in Half Duplex mode. 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 276 Link Aggregation Trunking If the LED is lit, the port belongs to a LAG. Power over Ethernet If the LED is lit, the port is operating in PoE mode. 2 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 277: Monitoring
In addition, the G350’s packet sniffing service is capable of capturing non-Ethernet packets, such as frame-relay and PPP. Non-Ethernet packets are wrapped in a dummy Ethernet header to allow them to be viewed in a libpcap format. Thus, the G350 allows you to analyze packets on all the interfaces of the device.
Page 278 A capture list contains rules and actions. A rule specifies criteria against which packets are tested. The action tells the G350 what to do for packets matching the rule criteria. Only packets that match the specified criteria and have an action of capture are captured to the capture file.
Page 279 For example, to capture filter-group set the G350 to use capture-list 501 on its interfaces, specify the following command: G350-001# capture filter-group 501 If no capture-list is applied, the packet sniffing service captures all packets.
Page 280: Analyzing Captured Packets
This feature is critical for mechanisms such as policy-based routing that must guarantee service on a particular path. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 281: Configuring Extended Keepalive
Small Branch For example, your branch office may have a G350 that connects to the Headquarters over a T1 line and via an xDSL connection to the Internet. The T1 line is used for voice traffic, while data packets are sent over the xDSL line.
Page 282: Reporting On Interface Status
FastEthernet 10/2 is Keepalive up, line protocol is Keepalive FastEthernet 10/2 is up, line protocol is Keepalive FastEthernet 10/2 is KeepAlive- down up, line protocol is Down down (no KeepAlive) 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 283 Shutdown FastEthernet 10/2 is Down Down AdminDown administratively down, line protocol is down 2 of 2 For detailed specifications of CLI commands, refer to Avaya G350 Media Gateway CLI Reference, 555-245-202. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 284 Monitoring Extended keepalive Maintenance of the Avaya G350 Media Gateway June 2004...
Page 285: Alarming
Media Modules, Media Servers, and the Media Gateway are all capable of detecting internal failures and generating traps and alarms. • The G350 detects faults and alerts the Media Server; the Media Server then raises an alarm, and sends the alarm to an appropriate alarm management site. •...
Page 286: Alarm Classifications
TRAP A trap is an event notification that is sent to the SNMP trap manager and received from the Media Gateway, or RTCP Monitor (Avaya VisAbility). ALARM Some traps are determined to be an alarm. If determined to be an alarm they are sent to an appropriate alarm management site, such as INADS.
Page 287: Alarm-Related Leds
Alarming Alarm-related LEDs Alarm-related LEDs The following alarm-related LEDs appear on the faceplate of the G350 or attendant console, and show how certain LEDs reflect specific alarm situations. Table 155: Alarm-Related LEDs Location Alarm-Related Cause ALARM LED Attendant Console The system alarm causes the attendant console ALARM LED to light.
Page 288: Qos Alarms
Avaya P333T User’s Guide. The Dynamic Trap Manager feature of the G350 insures that SNMP traps and alarms are always sent to the currently active Media Gateway Controller. By default, the Dynamic Trap Manager sends all SNMP messages to the currently active MGC.
Page 289: Snmp Alarming On The G350
OSS Method – The server’s software applications and hardware devices under its control can generate Operations Support System (OSS) alarms. These alarms are recorded in the server logs, and may be reported to Avaya’s Initialization and Administration System (INADS) or another services support agency over the server’s modem interface.
Page 290 Configuring the G350 to send SNMPv3 alarms The Avaya G350 Media Gateway uses SNMPv3 for traps and alarms. In order to configure the Avaya G350 Media Gateway to send SNMP traps to the primary server you must enable the SNMP agent, specify the SNMP host, and setup SNMP authentication.
Page 291 Cascade connection fault notifications Configure SNMPv3 authentication In order to use SNMPv3 authentication, you must create users, groups, and views for the G350. The G350 provides several pre-configured views and groups for setting up SNMP authentication. Refer Table 157, G350 Pre-configured Views,...
Page 292 (USM) 3 (AuthPriv) For a complete discussion of SNMP administration, refer to Administration of the Avaya G350 Media Gateway, 555-245-501. For the full syntax of SNMP-related commands and an explanation of their parameters, refer to Avaya G350 Media Gateway CLI Reference, 555-245-202.
Page 293: G350 Traps
Alarm format G350 traps A trap is a special condition that exists or an event that occurs within the Avaya G350 Media Gateway system. Some traps indicate configuration changes or component modifications and are merely informative. Other traps indicate warning or error conditions that may compromise the performance of the media gateway.
Page 294: G350 Traps And Resolutions
G350 traps G350 traps and resolutions “121.1.1.2” is the IP address for Telnet access to the alarmed Avaya G350 Media Gateway • Processor (MGP). “cmgMultipleFanFault” is the trap name (3rd column of Table 159, G350 Traps and Resolutions, • on page 294).
Page 295 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 2 of 12 Trap Enterprise Name Facility Severity Description / Resolution avayaG350 lntPolicyAccessControlViolationFit Policy Warning A packet has violated a policy rule on the specified interface. The trap includes information about the slot where the event occurred.
Page 296 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 3 of 12 Trap Enterprise Name Facility Severity Description / Resolution avEntTraps avEnt48vPwrFlt Supply There is a problem with the 48V power supply. Check voltages. Use the CLI command...
Page 297 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 4 of 12 Trap Enterprise Name Facility Severity Description / Resolution avEntTraps avEntAmbientHiThresholdTempFlt Temp The ambient temperature in the device is above the acceptable temperature range. Verify there are faults in the system. Use...
Page 298 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 5 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 30 cmgSyncSignalFault Major The synchronization signal has been lost. Check that the provisioned clock-sync source has a good signal using the Media Gateway CLI command show sync timing.
Page 299 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 6 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 50 cmgModuleRemove A Media Module has been removed. cmgTrapTypes 52 cmgModuleInsertFault The insertion sequence for a Media Module has failed.
Page 300 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 7 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 94 cmgFirmwareDownloadFault Major An attempt to download a software module has failed. Check the event log to find the specific error.
Page 301 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 8 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 106 cmgRegistrationFault Major The Media Gateway cannot register with any controllers in its controller list. Verify that the controller list is correct.
Page 302 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 9 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 114 cmgMgAutoReset Warning The Media Gateway automatically reset. This may be due to a critical error from which the Media Gateway could not recover.
Page 303 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 10 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 116 cmgModuleAutoReste Warning cmgModuleAutoReset — A Media Module in the Media Gateway automatically reset (rebooted). To...
Page 304 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 11 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 122 cmgConfigUpoadFault Major An attempt to upload a configuration file failed. Check the event log for an error message during the backup/restore process.
Page 305 G350 traps G350 traps and resolutions Table 159: G350 Traps and Resolutions 12 of 12 Trap Enterprise Name Facility Severity Description / Resolution cmgTrapTypes 128 cmgVoipAutoReset Warning The VoIP module in the Media Gateway automatically reset.To resolve the problem, take...
Page 306 G350 traps G350 traps and resolutions Maintenance of the Avaya G350 Media Gateway June 2004...
Page 307: Media Server Alarms
Media Server alarms Media Server alarms In the Avaya S8300 Media Server with an Avaya G350 Media Gateway system, some maintenance processes take place on the G350 while others are controlled by Avaya Communication Manager and pertain to the S8300.
Page 308: Viewing The Alarm
Alarming on an external Media Server Alarms for external media servers follows that described for the S8700 or DEFINITY servers. See Maintenance for the Avaya S8700 Media Server with the SCC1 or MCC1 Media Gateway, 555-233-143 ® or Maintenance for Avaya DEFINITY Server R, 555-233-117.
Page 309: Alarming On The S8300 Functioning As A Local Survivable Processor
The S8300 functioning as a Local Survivable Processor (LSP) logs an alarm when it becomes active. It also logs an alarm for every G350 Media Gateway that registers with it. It does NOT log alarms when IP phones register with it; rather, it logs a warning.
Page 310: Backup And Restore Traps
A trap of major severity is sent as soon as a REPLY_ERROR message is returned. The trap states “Translation Data backup not available,” and names the backup location stored in the string “BACKUP_LOCATION.” Maintenance of the Avaya G350 Media Gateway June 2004...
Page 311: S8300 Alarms - _Wd
1. Get a fresh copy of watchd.conf (from the CD for field, and from remote server or /root2 for the labs). 2. From the Web Interface, choose Alarms and Notification; select the appropriate alarm; choose Clear Maintenance of the Avaya G350 Media Gateway June 2004...
Page 312 It has been found that the most common cause for rolling reboot is that files are not where they are expected 2. If everything looks OK with step 1, further investigation of trace log is necessary. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 313 1. Verify that the file named in the log exists and is executable. 2. Verify that the string in watchd.conf is correct. 3. From the Web Interface, choose Alarms and Notification; select the appropriate alarm; choose Clear Maintenance of the Avaya G350 Media Gateway June 2004...
Page 314 Clear Table 171: Alarm #16 1 of 2 Number Source Event ID Alarm Level Major Alarm Text Description Watchd high monitor thread is rebooting the system 1 of 2 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 315 Notification; select the appropriate alarm; choose Clear. Watch to see if alarm returns. The server should have rebooted by the time a support person can analyze the system. A reboot normally fixes problems with unresponsive software. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 316: S8300 Alarms - Env
Possible Causes Motherboard's Temperature reached Critical High Determining Cause Alarm condition present indicates the problem occurred. Resolution 1) look for any obstructions blocking the G350 fans 2) check for G350 fan alarms 3) clear alarms 4) shutdown 5) restart 6) If the alarm condition is not present, use “almclear -n #id” to manually clear the alarm.
Page 317: S8300 Alarms - Login
Resolution Notify Customer Table 176: Alarm #46 Number Source login Event ID Alarm Level Minor Alarm Text Description Possible Causes Security violation Determining Cause Choose View Current Alarms Resolution Notify customer Maintenance of the Avaya G350 Media Gateway June 2004...
Page 318 Resolution Notify customer Table 178: Alarm #48 Number Source login Event ID Alarm Level Major Alarm Text Description Possible Causes Security violation Determining Cause Choose View Current Alarms Resolution Notify customer Maintenance of the Avaya G350 Media Gateway June 2004...
Page 319: S8300 Alarms - _Tm
Choose View Current Alarms Resolution 1. Backup translations to a unique location (for possible later diagnostic use) 2. Restore most recent previous translations. 3. Restart Communication Manager (reset system 4). 4. Notify Tier 3. Maintenance of the Avaya G350 Media Gateway June 2004...
Page 320: S8300 Alarms - Ups
Possible Causes UPS will turn off power to the load in less than 5 seconds Determining Cause Alarm condition present indicates the problem occurred. Resolution Return AC power to UPS Maintenance of the Avaya G350 Media Gateway June 2004...
Page 321 Minor Alarm Text Description upsAlarmInputBad Possible Causes An input condition is out of tolerance Determining Cause Alarm condition present indicates the problem occurred. Resolution provide appropriate AC power to the UPS Maintenance of the Avaya G350 Media Gateway June 2004...
Page 322 Event ID Alarm Level Warning Alarm Text Description upsAlarmBypassBad Possible Causes bypass is out of tolerance Determining Cause Alarm condition present indicates the problem occurred. Resolution return AC input power to UPS Maintenance of the Avaya G350 Media Gateway June 2004...
Page 323 Output on one of the receptacles is out of tolerance Determining Cause Alarm condition present indicates the problem occurred. Resolution Requires diagnosing the UPS – may be simpler to just replace it and diagnose it later Maintenance of the Avaya G350 Media Gateway June 2004...
Page 324 Source Event ID Alarm Level Warning Alarm Text Description upsAlarmFanFailure Possible Causes One or more UPS fans have failed Determining Cause Alarm condition present indicates the problem occurred. Resolution Fix fan Maintenance of the Avaya G350 Media Gateway June 2004...
Page 325 General fault in the UPS has occurred Determining Cause Alarm condition present indicates the problem occurred. Resolution Requires diagnosing the UPS – may be simpler to just replace it and diagnose it later Maintenance of the Avaya G350 Media Gateway June 2004...
Page 326 Media Server alarms S8300 alarms – UPS Maintenance of the Avaya G350 Media Gateway June 2004...
Page 327: Index
Automatic launch of traceroute S8300 IP address Avaya Communication Manager Web Interface, viewing telnet alarms via Avaya Site Administration Avaya S8300 Media Server with G350 Media Gateway ACK LED access Administration system interactions circuit packs Avaya Site Administration trunks...
Page 328 H.248 link recovery Hard drive replacing S8300 Media Server Hot-inserting, voice modules E1/T1 Media Module Hot-swapping hot swapping S8300 caution LEDs voice modules Echo canceller hardware error MM710 Media Module Test Maintenance of the Avaya G350 Media Gateway June 2004...
Page 329: Maintenance Of The Avaya G350 Media Gateway June
Ok-to-remove wideband access endpoint port red ALM Maintenance commands S8300 Media Server G350 Media Gateway S8300 states S8300 shutdown sequence standard DEFINITY server LEDs sync source troubleshooting and diagnostics usage Maintenance of the Avaya G350 Media Gateway June 2004...
Page 330 MG-DS1 alarming MG-ICC Analog Media Module maintenance objects analog station/trunk MG-VOIP analog trunk/telephone port board Minor alarms audits MM710 clock sync source BRI Trunk LEDs busyout port location captive screws MM711 Maintenance of the Avaya G350 Media Gateway June 2004...
Page 331 Media Server hard drive captive screws Resetting hard drive shutdown IP telephones hot swapping caution system LED differences LED states information requirements LEDs websites LEDs lighting sequence LEDs, additional location replacement shutdown Maintenance of the Avaya G350 Media Gateway June 2004...
Page 332 T1/E1 Media Module viewing alarms Terminal emulation Wideband access Wideband access endpoints w2ktt Wideband switching Terminals, downloads Testing abort code common port circuit pack maintenance echo canceller ringing caused by XXX-BD trunks Maintenance of the Avaya G350 Media Gateway June 2004...

Avaya G350 Maintenance Manual

About this Book

1 Maintenance Overview

2 G350 Component Maintenance

3 Avaya Communication Manager Controlled Maintenance

4 License and Authentication Files

5 Access and Login Procedures

6 G350 and Media Module Leds

7 Monitoring

8 Alarming

9 G350 Traps

10 Media Server Alarms

Index

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Avaya G350

Summary of Contents for Avaya G350