G700. MGP problem

[tohm]

Hi.
I have G700 mediagateway. After upgrade firmware I can't start MGP session:

P330-1(super)# ses mgp
Connection to the module is not available !
Available modules are:
----------------------
G700 (*) In Slot 1

I tried reset G700 to factory settings (nvram init), but it has not changed anything

P330-1(configure)# dir
M# file ver num file type file location file description
-- ---- -------- ---------- ------------- ----------------
1 module-config N/A Running Conf Ram Module Configuration
1 stack-config N/A Running Conf Ram Stack Configuration
1 EW_Archive 6.0.1 SW Web Image Nv-Ram WEB Download
1 Booter_Image 3.2.5 SW BootImage Nv-Ram Booter Image

P330-1(configure)# sh image v
Mod Module-Type Bank Version
------ ----------- ---- -------
1 Avaya G700 Media Gateway A 0.0.0
1 Avaya G700 Media Gateway B 4.1.12

P330-1(configure)# sh module
Mod Type C/S S/N Statuses
--- ----------------- ---- -------- ----------------------------
1 G700 3.3 70493xx PS:OK Fans:Not Prsnt Mode:Layer2
No Expansion Not Present
NoCascade Conn-Up:None Conn-Down:None

Currently, I can log only to P330 via console port, telnet IP or web panel and program everything about the commands available from the stack session. I can easily change the firmware viisa / p330Tweb

Is there any help for this gateway? Is there any way I can get to the configuration MGP/VoIP?
Help me, please!

 

[smokinjoe2938]

you have a static address of 192.11.13.5 255.255.255.252 and gateway set to 192.11.13.6 correct? also can you ping the G700?

 

[tohm]

After NVRAM init G700 have default IP 149.49.32.134, not 192.11.13.6. I configure my laptop IP e.g. 149.49.32.150 and have communication to G700. I can use console port too. Earlier information I copied from this G700, stack processor is available, MGP isn't available only. I can't configure it with the CLI, because P330 don't create a session to MGP. When I use software Avaya GIW I can give the IP address for P330 stack and default gateway, but the configuration of the MGP also not available. Other card in slot doesn't recognize too.

 

[kyle555]

I'm no doctor, but I think he's dead. Unless you're stuck with licensing tied to its serial #, I'd check out ebay

 

[WellingtonPaez]

Are you trying to connect from the main MG? remember to be in configure mode in order to access the MGP

 

[WellingtonPaez]

you might need to unplug the stacking cable and configure them two separate

 

[tohm]

I think the same, but I'm looking to do some "hardware" way, eg. memory pin-out shorting on board, uploading MGP firmware via TFTP, maybe JTAG/ISP, some backdoor e.t.c.
I have a feeling, that the G700 is not "dead" completely, because before uploaded the latest firmware P330, after 15-20 minutes or "NVRAM init", was possible sometimes madecommand "session MGP". Unfortunelly P330 firmware downgrade didn't help - "sesion MGP" command isn't possible now - MGP isn't recognized.

 

[tohm]

WellingtonPaez,
this is G700 as one mediagateway (one board with stack, MGP, VoIP proc). I remember to use "session mgp" in cofigure mode.

 

[montyzummer]

does the show faults/voltages command show anything useful , or logging file content , can you ping the ip addresses.can you set up a modem session and try and access via that method instaed. Also look below and see the ip reason you should be able to sort that out.

1. Using the serial interface, make sure the internal P330 Processor configuration (IP address, subnet
mask) is correct. From the internal P330 Processor CLI, issue the command
show interface
.
2. Verify that the interface "inband" has a valid IP address in the customer LAN.
3. If it is not a valid customer LAN IP address, if it is 0.0.0.0, or if it is the factory default "149.49.35.214",
then the IP address for the internal P330 Processor has not been set.
4. Use the procedures described in the Installation and Upgrades documentation to set the internal P330
Processor interface.
Note
: If you don't have a serial interface cable, then telnet into the Media Gateway Processor (MGP).
From the MGP, type the command
session stack
to get into the internal P330 Processor. Then use the
procedures described in the Installation and Upgrades documentation to set the internal P330 Processor
interface

see below notes as these steps may help you , the first

Cannot communicate
with the motherboard
VoIP engine. (Cannot
ping or telnet to the
MGP).
Incorrect
configuration of VoIP
IP address.
1. Verify the VoIP IP address with the Media Gateway Processor (MGP) CLI command '
show voip vn’
(n=0, if motherboard VoIP).
2. If the VoIP IP address is incorrect, issue a
set interface voip
command with the correct IP address.
3. If the IP address is correct, then try the command
reset voip vn

Cannot communicate
with the Media
Gateway Processor
(MGP) in a stack
configuration. (Cannot
ping or telnet to the
MGP).
Physical layer
problem - bad cable
or Octaplane Module.
1. In a stack configuration, verify that the Octaplane Module is working by checking the green LED on
the back of the G700, or with the internal P330 Processor command
show module
.
2. If the green LED is not on, check the cable connections, and check that the cascade module is seated
properly.
3. Consider a possible bad cable (swap out cable).
4. If not successful, try swapping out the Octaplane Module.
5. As a last step, try issuing an internal P330 Processor command
session <stack number>
to see if
there is connectivity between P330 modules in the stack.
6. If there is connectivity, try a reset of the entire stack.
7. If the problem persists, replace the Avaya
™
G700 Media Gateway. The MGP is not field replaceable

This will let you view logs that may be pertinent to your issue

Level 2:
Technical Services Organization should perform the following when receiving a call from field or
customer regarding this problem:
1. Telnet to the internal P330 Processor. (If you cannot telnet to the internal P330 Processor, ask a tech
to do the remaining steps through the serial port).
2. Go to the 'tech' mode.
3. Go to the 'dev' mode.
4. Look at the internal P330 Processor reset log by using the command
system show reset-log
. Also
look at the internal P330 Processor log using
show logs
.
5. Collect both logs and escalate the problem

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[tohm]

Montyzummer
I made your tutorial:

P330-1# sh interface
Interface Name VLAN IP address Netmask
-------------------- ---- --------------- ---------------
inband 1 192.168.10.66 255.255.255.0
ppp disabled 1 0.0.0.0 0.0.0.0

P330-1# sh ip route
Destination Gateway
------------- -------------
0.0.0.0 192.168.10.1
0.0.0.0 0.0.0.0
0.0.0.0 0.0.0.0
0.0.0.0 0.0.0.0
....

192.168.10.0/24 is my LAN network. I can login to P330 in G700 via serial port (console port), via telnet (192.168.10.66) and web (java applet). I can't login to MGP in G700.
After command session mgp I have:

P330-1(configure)# ses mgp
Connection to the module is not available !
Available modules are:
----------------------
G700 (*) In Slot 1

Cable is OK, but I can connect to P330-1 !
When I connect to p330 in G700 via IP address (telnet) and I trying connect to MGP i have identical response:

Connection to the module is not available !
Available modules are:
----------------------
G700 (*) In Slot 1

I don't have octaplane module in my G700.

After sh module / sh sys command i have:

P330-1(configure)# show module
Mod Type C/S S/N Statuses
--- ----------------- ---- -------- ----------------------------
1 G700 3.3 7049388 PS:OK Fans:Not Prsnt Mode:Layer2
No Expansion Not Present
NoCascade Conn-Up:None Conn-Down:None


P330-1(configure)# sh sys
Uptime d,h:m:s
------------------------
0,0:27:28

System Name System Location System Contact
------------------------- ------------------------- -------------------------
-- empty -- -- empty -- -- empty --

Switch MAC address
------------------
00 04 0d 71 07 5c

I can't switch to tech mode because I don't know tech mode password. You can give me this password ?

Today, something interesting happened. After about an hour of work, G700 made suddenly, spontaneously reset. Then I could log in to the MGP (MGP session)!!! I uploaded the latest firmware for MGP (MGP_30_27_1.bin) and I made the upgrade of all media modules (VoIP module v0 too) and I saw that mediagateway working properly. I was very glad and I thought that was the end of my problems. I made nvram init mgp and P330 nvram init in G700 mediagateway because I wanted to program G700 again, on the target IP addresses from network my customer. Unfortunately, after this operation, my G700 does not see MGP again and I'm at the starting point again. Restoration configuration IP address of my network did not change anything.