How to access a G430?

[bartfliet]

Hello everybody,

I'm trying to restart a G430 in one of our of-site offices. When I enter the IP in my browser, it's giving me the next message

-----------------------------------------------------------------------------
This application requires the Sun Microsystems Java Plug-In, minimum version 1.4.2 to be installed in your browser.

You can:

•Retrieve the same from here.
After download is complete, run the executable you have downloaded to complete the plug-in installation.


•Install it from the Documentation CD provided with the G430 Device.


Refer to the User's Guide for details on how to install the plug-in.

•Retrieve the G430 Manager documentation from here.
.


Refer to the User's Guide for details on how to install the plug-in.


---------------------------------------------------------------------------------

So I installed the Java SE thing, though when I try to go to the device, I'm still getting the same message. I tried clicking the "g430 manager documentation from here" button, though that just takes me to the general Avaya site, when I look for an install guide for the "g430 manager" I only get manuals saying how to install the hardware, though not the manager software...
Anybody have any helpfull tips?

 

[kyle555]

Ssh

 

[bartfliet]

Or is there a way to restart a media gateway through the aura site administration?

 

[bartfliet]

I just did a "list media-gateway" command, and noticed that with every site it said "y" under "reg?" and with the one where it isn't working it says "p". What does this "reg?" stand for, and could this be the issue?

I just noticed I haven't explained the issue. The problem is that users at this site can't receive calls from outside lines. Inside lines, and placing calls to outside/inside lines isn't an issue.

 

[kyle555]

Ha. OK. So, P is pending registration. That means it failed over, can now speak to the core CM again, and is waiting for the configured failback parameter to kick in to go back to normal operation. Hint: you probably don't have one defined and that's why you're in that boat.

If that were gateway 6, "display media-gateway 6" and look at it's recovery rule. Bet ya it's blank. If it were, say, recovery rule 1, "disp sys mg 1" and you'll see the parameters for failback - could be immediate, or "after 5 pm" or "when there's no calls up" or anything. So long as it's not blank, then it'll never failback.

So, coles notes here: in the gateway "set mgc list 1.1.1.1,2.2.2.2,3.3.3.3." primary search 1, total search 10, transition point 1.
That means the gateway will try to hit CM on 1.1.1.1 for 1 minute (primary search), then passes the transition point of 1 (to say, it's trying the 2nd and 3rd entries) each for 1 minute, cycles thru 2.2.2.2 for a minute and then 3.3.3.3 for a minute, and then 1.1.1.1 for a minute, 2.2.2.2, etc until 10 mins and then reboots itself.

The gateway alarm light will be on because it's registered to a entry past the transition point. That's how the gateway knows it's in failover and will respect whatever failback rule there is (which you're missing and why it's never going back)

So, "list survivable" and you'll see a CM that's "regsitered Y" and "active Y". The active one is the one that's still serving your G430.
You can reset a gateway from CM, can't remember if the core CM that has the registration pending can do it though. So, go into the live LSP/survivable CM and "reset media-gateway 6 level 2". Level 1/2/3 are "platform/link/modules" and just bouncing the link would be enough to unregister it from the failover CM and make it come home happy.

 

[montyzummer]

There is a reset media gateway x command in ASA, you could also try a "enable mg-return" command that will stay active for 1 hr and try and bring the gateway back to core.

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.