Download Print this page
Avaya G700 Troubleshooting Manual
Avaya G700 Troubleshooting Manual

Avaya G700 Troubleshooting Manual

Hide thumbs Also See for G700:

Advertisement

guide provides resolutions for several categories of problems that could occur during installation, configuration, or maintenance of an Avaya
This
Media
Gateway.
Additional assistance
If you cannot find the resolution to a problem using this Guide, you need to escalate the problem:
Before escalating an issue, please be sure you have tried all of the relevant suggestions in this guide to isolate the problem.
You should know whom to contact when you cannot resolve the issue. If you don't know, please call 1-800-242-2121 in North America, or call your
Avaya regional representative from other locations.
Requirements
As a user of this guide, you should have the following qualifications and access:
Qualifications: Avaya certified technician to perform G700 installation and maintenance.
Access: Know login, password, and access procedures with appropriate permissions.
How to use this Troubleshooting Guide -- General Troubleshooting Strategy
To use this Guide, please follow these procedures:
1.
Get the basic information about the system: load, version, vintage, etc.
a.
Upgrade G700 to latest Generally Available (GA) software & firmware.
b.
Make sure that systems interconnected with the G700 have the correct installed minimum configurations.
(please see ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/media/minhardwarevintages.pdf)
2.
Isolate the possible "root cause" based on the symptoms observed. First find the symptom listed (in left-most column) in the guide, then:
i. For each symptom, there is a possible cause listed in the next column
ii. Try each possible resolution (column to the right) for that cause
iii. If the resolution does not clear the trouble or eliminate the symptom, then go to the next possible cause associated with that symptom
(usually the next row)
iv. Several different root causes may be associate with the same symptom
3.
Be systematic, make only one change at a time and observe the results.
a.
Does the symptom persist? If so, proceed to the next possible cause.
b.
If the symptom disappears, check for cause and effect (reintroduce the change to see of symptoms re-appear).
4.
Eliminate obvious and easy to verify causes first, like physical connections, (layer 1 and 2) before proceeding to more complex causes (layers 3 and higher).
5.
Document all of the different troubleshooting steps taken.
a.
Precise and detailed information will help you when you escalate the problem.
b.
For example, you may want to print out this sheet and check-off each procedure that has been used.
6.
Finally, you can compare "normal" settings of the equipment with the current parameter settings of the problematic equipment. If you find a difference
between the "normal" settings and the problematic equipment, try changing the settings of the problematic equipment to match the settings of the "normal"
equipment.
G700 Troubleshooting Guide
TM
G700

Advertisement

loading

Summary of Contents for Avaya G700

  • Page 1 G700 Troubleshooting Guide guide provides resolutions for several categories of problems that could occur during installation, configuration, or maintenance of an Avaya G700 This Media Gateway. Additional assistance If you cannot find the resolution to a problem using this Guide, you need to escalate the problem: •...
  • Page 2 Access to the G700 and S8300 The following diagram shows an Avaya™ G700 Media Gateway with an Avaya™ S8300 Media Server and the access methods for various configuration and maintenance tasks.
  • Page 3 This is a living document. All information is subject to change at any time. © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions.
  • Page 4 3. Low voltage may be responsible for slower fans. Issue MGP CLI command show voltages to determine been operating at voltages for the Media Modules and other components of the G700. Voltage may be reduced by a short in one of less than 90% of the media modules or a bad power supply.
  • Page 5 Alarm is present. Processor (MGP) or 2. If there is a temperature fault, turn off the G700 and let it cool; then, check to see if the fans are working and/or Media Modules. if there is sufficient space around the G700 for air circulation.
  • Page 6 3. If fans are faulty then replace the entire G700. Fans are not field replaceable. fault in the Root source serving the 4. If the alarm clears in 10-20 seconds, it was a probable voltage spike. Do not replace the G700. Cause column is MG Processor is 5.
  • Page 7 3. If fans are faulty then replace the entire G700. Fans are not field replaceable. source serving the fault in the Root 4. If the alarm clears in 10-20 seconds, it was a probable voltage spike. Do not replace the G700. media modules is Cause column is 5.
  • Page 8 3. If fans are faulty then replace the entire G700. Fans are not field replaceable. indicates that the source serving the 4. If the alarm clears in 10-20 seconds, it was a probable voltage spike. Do not replace the G700. fault in the Root DSP units is out of 5.
  • Page 9 Procedure for setting synchronization timing sources on E1/T1 MM or MM710: The command Media Modules. 2. Be sure that the E1/T1 MM has been added properly on the Avaya™ S8300 Media Server or Avaya™ S8700 Synchronization show faults Media Server, otherwise go to System Access Terminal (SAT) and issue a ADD DS1 command before going to signal lost.
  • Page 10 Red LED on LED LED board is not 1. Verify there are faults in the system. Use the Avaya™ G700 Media Gateway Processor (MGP) Command Line board is on but no making good Interface (CLI) command show faults to display any faults on the G700.
  • Page 11 © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other registered trademarks or trademarks are property of their respective owners.
  • Page 12 Resolution a) IP Phone does No VoIP 1. Check if there is an Avaya™ G700 Media Gateway or a prowler resource available with the right codec for the IP Phone, not get Dial-tone resource using the SAT commands described in the Avaya Multivantage Administrators guide.
  • Page 13 Voice Quality G700 Troubleshooting Page 2 Symptom Root Cause Resolution Echoes during an Levels issues 1. Check levels and adjust loss plan in SAT. IP call - - impedance 2. Check to see if problem is from T1. If so, upgrading T1 board to TN464G series with hard echo canceller may fix particularly mismatch.
  • Page 14 Example: change trunk-group 18 5. On page 2 set Ds1 Echo Cancellation? to ’y’. 6. If Echo Cancellation is not displayed, escalate the problem and contact Avaya or your Authorized Avaya Business Partner to turn ON Echo Cancellation (must purchase).
  • Page 15 3. If the problem persists, escalate. © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other registered trademarks or trademarks are property of their respective owners.
  • Page 16 Endpoints Page 1 G700 Troubleshooting Symptom Root Cause Resolution IP phone is in May have wrong 1. Check the server IP address by pressing "MUTE or HOLD" button + ADDR + # and use # to navigate, ’discovery’ state and controller IP address, until you see the "CallSv"...
  • Page 17 6. Otherwise, cancel out of the form and issue a list media command on the SAT. This returns a list of G700s with associated network region. 8. Issue a display media x command, where x is the G700 number, for each of the G700s to display its network region number.
  • Page 18 © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 19 1. An Ethernet cross-over cable is required, if connecting the G700 ports to a switch or router. communication cable, or a bad 2. Check the EXT1 or EXT2 LEDs on the G700 LED board to make sure they are 'on'. with the Avaya™ configuration on 3.
  • Page 20 © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 21 Access-Networking Page 1 G700 Troubleshooting Symptom Root Cause Resolution Cannot Communicate Incorrect 1. Connect to the internal P330 Processor, and from the internal P330 Processor CLI issue the with the Media configuration of IP command session mgp. Gateway Processor address, subnet 2.
  • Page 22 1. Using the services port, verify the Avaya™ S8300 Media Server configuration with the Configure with the Avaya™ configuration of Server Web page wizard (Assuming that you are onsite and standing in front of the Avaya™ G700 Media S8300 Media Server External (customer's) Gateway and S8300).
  • Page 23 2. Verify the VLAN settings on the MGP with the command show interface. The default value is [1]. internal P330 3. The VLAN ID is set on the MGP, and applies to the VoIP engines as well as the Avaya™ S8300 Processor and/or Media Server in the same Avaya™...
  • Page 24 Access-Networking Page 4 G700 Troubleshooting Symptom Root Cause Resolution Cannot communicate Incorrect 1. Using the serial interface, make sure the internal P330 Processor configuration (IP address, subnet (ping or telnet) with the configuration of mask) is correct. From the internal P330 Processor CLI, issue the commands: internal P330 network gateway.
  • Page 25 2. From the internal P330 Processor CLI, issue the command show rmon stat <port>. the internal P330 3. In a multi-Avaya™ G700 Media Gateway stack, verify the stack connections by checking the LED on Processor. the Octaplane Module or with the command show module.
  • Page 26 Processor or MGP was 1. Power down and power up the Avaya™ G700 Media Gateway, using proper procedures (see lost. Maintenance documentation). 2. From a PC, use the ping command to ping the IP address of the internal P330 Processor.
  • Page 27 P330 resets. © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 28 Upgrading Page 1 G700 Troubleshooting Symptom Root Cause Resolution Copy TFTP returns failure. Image file to download does not Make sure the file to be downloaded exists and is spelled correctly in the exist or filename is not spelled command.
  • Page 29 1. Typo in the download path. the download path. 2. DNS name is used in the download path and the Avaya™ S8300 Media Server status indicates ’idle state’ doesn’t have DNS set up (so try using the IP address).
  • Page 30 Unable to login to the No lacfile on the new partition. This 1. Reboot the Avaya™ S8300 Media Server by pressing the reset button, or by Avaya™ S8300 Media could occur while performing an power cycling. Since the upgrade is not permanent yet, it will reboot to the old Server after upgrade.
  • Page 31 © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 32 Resolution Avaya™ S8300 Media Server The primary call controller 1. Login as craft or cust to the SAT/Avaya Site Administration screen of the configured as a Local Survivable is not yet aware that the primary controller (i.e. either the Avaya™ S8700 Media Server or Avaya™ S8300...
  • Page 33 Resolution Avaya™ S8300 Media Server There is a network issue 1. If the primary call controller is an Avaya™ S8700 Media Server, check to see if configured as a Local Survivable between the primary call the CLAN is in service.
  • Page 34 © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 35 Authentication File, and translations from the old one. Avaya™ S8300 Media Module. 3. If this is unsuccessful, then replace the Avaya™ G700 Media Gateway, and insert the new Expansion Server. Module and the new S8300. 4. If the problem persists, contact Avaya or your Authorized Avaya Business Partner.
  • Page 36 2. Check to see if you have the correct cable and cable adapter. 3. If everything is set right with the correct cable and the problem persists, try using a LAN connection via EXT1 or EXT2, if the Avaya™ G700 Media Gateway is already configured with IP addresses (as a work- around) 4.
  • Page 37 Processor interface. © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 38 © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.
  • Page 39 MGC. Note: This editable field is labeled "identifier". 4. If the Serial Numbers do not match, then change the Serial Number of the incriminated G700 in the MGC by typing the following command on the SAT : change media-gateway <G700_NUMBER>.
  • Page 40 S8300/S8700. Gateway Controller 3. If the ping is not successful, and the controller is in the same Avaya™ G700 Media Gateway (Avaya™ (MGC). S8300 Media Server), verify the physical layer with the command session icc 4. If the controller is external and the ping fails, you need to verify VLANs, gateway addresses (use show ip route to see if the problem is with the S8300 or the MGP, as in the networking symptom AN-7 "cannot...
  • Page 41 Here is an example of valid values : “Primary Search = 1”, “Total Search = 30”, “Transition register with the Media Point = 1”. The Primary Search is the time in minutes during which the G700 is going to try to connect to Gateway Controller the S8300/S8700.
  • Page 42 Resolution © 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc.