It is easy to forget one or two details so this is a brief collection of commands and thoughts on Avaya media-gateways.
Serial and Console connection
On the G430 you can connect via the Serial Port, you will either need a crossover cable or a switch and two Ethernet cables.
Connect the laptop to the switch and the switch to the G430 or the laptop directly to the appliance with the crossover cable. Set the IP of the laptop to 126.96.36.199, subnet to 255.255.255.252 and default gateway to 188.8.131.52. Open an SSH session to 184.108.40.206 and login with the credentials provided or if this is a new/factory reset device User:root Password:root.
If this is a working installation you should now be able to reach CM, BSM… from your laptop.
For the G450 you can connect via Serial the same way as above but if this is a new or factory reset appliance you have to use the console port. If using the console port you will need the Avaya provided RS-232 cable also known as a rollover cable and most probably a USB to serial adapter.
Connect the RJ-45 end of the rollover cable to the GW port marked as Console, the big end of it to the usb adapter and the usb to the laptop. Open device manager (windows), go to Ports and check what COM port the Generic USB Adapter got (COMX) now open putty, select serial connection, serial line: COMX, Speed (Baud Rate) 9600 on the left you can open serial settings and check the following data, Data bits:8, Parity: None, Stop bits:1, Flow Control:None. Click open, enter credentials or User:root Pass:root
There are two ways to reset these gateways, one is a software reset and the other a hardware reset, both have the same results but you might have to chose one over the other because of reasons given below. Note that if you reset these devices you will have to physically connect to them to adjust the configuration as DHCP is not enabled by default and you will lose connectivity.
Connect to the GW via SSH, enter username and password and issue the command
nvram init to wipe the config.
If you do not know the credentials but are not on on release 36.5.0 or later you have the possibility to login via Console or Serial and use the default username: root and password: ggdaseuaimhrke once logged in,
nvram init to wipe the config.
If you are on 36.5.0 or later and can not login via SSH you have no choice but to do a hardware reset to have access to the GW again. In this case it is best to have a female to female jumper ready if needed. Power down the device and disconnect it from power. In case of the G430 you have to take off the top of the enclosure and for the G450 you have to pull out the main board from the front (in both cases you have to have a screwdriver). Look for a set of three pins, one is labeled NVRAM, one INIT and one is usually CHECK. Connect NVRAM and INIT with the provided jumper or your female to female jumper wire, power on the Gateway and if you are connected via Serial or Console you should see the appliance resetting, it will tell you when to remove the jumper and reboot the device, if you are not connected just wait 5 minutes, power down the Gateway, remove the jumper and boot it up.
Once reset you can login via Console / Serial with username: root and password: root
Checking the GW firmware
By default software bank B is is being used on a new Gateway, you can check this by running
show image version in the cli, you should get something like this:
TESTGW101-???(super)# show image version
B (current) 37.41.0
Where “current” marks the software bank in use.
Upgrading GW via USB
Download the .bin upgrade file from support.avaya.com and put it on a FAT32 formatted USB stick, plug it in to the first USB slot on the GW (not in the S8300!) on the GW issue the command
dir usbdevice0 you should see the name of the .bin file.
copy usb SW_imageB usbdevice0 g450_sw_37_41_0.bin
you can change imageB to imageA and of course use your software version, mine is just an example. Uploading the file will take a while but you can check the status with
show download software status 10 as soon as it shows “running state: Idle” the download of the file is done. Finish with the steps below.
Upgrading GW via TFPT
Download the .bin upgrade file from support.avaya.com and put it on your TFTP server. On the gateway issue the command
copy tftp SW_imageA g450_sw_37_41_0.bin 192.168.1.1
again, change imageB to imageA, software version and IP if needed. Finish with the steps below.
Finishing the upgrade
If you downloaded the new firmware to the other boot bank you can now change to it by issuing
set boot bank bank-a or
set boot bank bank-b do a
copy run start and a
reset chassis to reboot the GW and load the new firmware.
When sliding in the media modules note that the S8300 can only be put in V1 and other media modules could have a slot and vintage , (sw release or driver) requirement, it is best to consult the documentation for the gateways (ressources on bottom).
Configuring these gateways can be done really fast if you have the required information and know what you are doing.
If this is a new Gateway, the config script should start automatically once you connect , if you manage to hit a wrong button you can start it again with
script-config here you have to enter IP Addressing data.
I will go through the usual extra config of one of these boxes.
Enable port redundancy and disable spanning tree.
show port redundancyFor G430
set port redundancy 10/3 10/4 on
set port redundancy 10/5 10/6 on
set port redundancy enable
set spantree disable
Set reset times
set reset-times transition-point 1
set reset-times primary-search 5
set reset-times total-search 25
Set sync (in case of BRI/PRI connection)
set sync interface primary vX
set sync primary
(in this case X is a slot where you want to sync from)
In case you have a HA-SBC setup and the SBC internal trunk interface (A1) is in the same subnet as the media-gateway, when the SBC switches between primary and standy or you change one of the IP/MAC address combinations that connect to the GW (e.g. deploy a new SBC) you could have one-way audio issues or no audio. To counter this you have to disable arp inspection on the MG.
no ip arp inspection
The documentation states that this setting requires a reset of the GW but it might work without it.
Always do a
copy run start otherwise the GW will lose the configuration on the next restart.
Basic Troubleshooting commands
show platform main
show logging file cont
Best place to start when troubleshooting a GW is
show faults the GW is usually very good at communicating its issue.
- Avaya G430 Branch Gateway Overview and Specification
- Avaya G450 Branch Gateway Overview and Specification
- GW ARP Inspection