S8700/G700 Gateway install in progress, need assistance 2

[heathersue]

Hi Everyone,

We are working with a vendor in Mexico on a new install of Gateway and Sedia Server, standalone w/ Intuity Audix VM.

We are having a bit of trouble, we assigned IP addresses within the Voice VLAN (60) to the Processor, stack processor, MGP, DSP, and Voicemail. We can ping everthing but the Processor and MGP. We tried installing a new
S8300 card into the gateway, but the same result. Anyone know any tricks or info on how to get past this point and get the processor to 'talk' to the gateway? Thanks!

Heather

 

[pabxdude]

when trying to ping, what sort of message do you get back?

did an install of S8300/G700 last week, all addresses like yours in same subnet. Getting error 'destination unreaschable' when trying to ping S8300.

to fix, simply reloaded CM onto S8300, and reconfigured the interfaces etc, and all started working.

 

[heathersue]

Hi

We were getting the failure message, timed out...

we managed to get past that by redoing everything through the wizard, and we thought we were done and our last step was to reboot. After we rebooted, everthing came back except for the link between the 8300 and the gateway. So we configured again with the wizard, and rebooted, and same result - it loses the link from the gateway again. I have a red alarm light on both gateway chassis' now. Any ideas? Please help. Thanks!!!!!

Heather

 

[mark5830]

Can you specify what you are using in your ip settings and also the ip routes you are setting.

 

[sjforcum]

Run configure server on the S8300. There is a known issue with S8300 / G350 or 700 using the installation wizard.

It appears to run fine, but when you power cycle, you can no longer communicate to the devices. There is some sort of routing table in Linux that gets corrupted by the power down. When you run "configure server" from the web interface, it sort of hard writes the table and you never have the issue again.

SJF

 

[heathersue]

Hi,

Thank you both for your posts!!!!

sjforcum, that is the exact thing we are running into, I want to give that a try... when I run configure server from the web interface, it it similar steps to the wizard, just in a different format?

mark5830
Here are the IP addresses we are using:

S8300 Avaya Gateway Processor/Cust Access 10.136.4.253
Stack Avaya Gateway Stack Processor 10.136.4.252
MGP Avaya Gateway Media Gateway Processor 10.136.4.251
VOIP Avaya Gateway DSP Resources 10.136.4.250
IA770 Avaya Gateway Voice Mail 10.136.4.249

Thanks!!!!!!

 

[heathersue]

Hi All,

I think I have something...anyone know where I can get patch 12866? Thanks!!!

 

[manfmmd]

Here is the PCN:

http://support.avaya.com/elmodocs2/qppcn/Cust_3_1_2_1586P_SP_PCN.pdf

You have to go to the SSO Download Center and search for the patch.

 

[sjforcum]

Configure server actually HAS all of the information in it...all you have to do is configure all services and then just keep hitting next until you get to the end. Then it writes everything....although the latest CM pack may finally fix this (lord only knows what took so long...we first found this in CM3.1)

 

[heathersue]

Thanks!!

 

[manfmmd]

heathersue

I'm waiting on permission to post a link where you can download it from.. Please bear with me.. If I'm not allowed to post the link, you'll have to go through the SSO download process or through your BP.

 

[manfmmd]

You can download the 12866 patch here:

http://tinyurl.com/y4er8z

Copy and paste into IE if you are running FF. Please let me know when you have it downloaded so that I can kill the download.

If you want to confirm the MD5 checksum with the Avaya website, here is a free checker:

http://www.fastsum.com/download/FastsumSetup-1.5.exe

Here is the page that shows you the MD5:

http://support.avaya.com/japple/css...eID=282185&temp.bucketID=108025&PAGE=Document

 

[pbx1960]

Man oh Man, can I relate to these issues. I am in Kabul, Afghanistan. I got here about six months ago, and the big boys wanted me to get something so they could make conference calls, I suggested an IP Office since that was all they wanted, they liked the idea, but when I flew to Dubai to work with a vendor, they told me the IP Office had issues with E1 interfaces, and told me they would sell me an 8300 with g700 for less. That seemed like a good idea, but, with support here in Afghanistan being so difficult, I think I should have went with the IP Office, because it wouldn't require so much network interfacing, I also question the validity of E1s having problems in IP Office, I have installed a lot of them in America with T1s, and they run flawlessly.
Anyway, I went bac to Dubai, and got trained, we worked in the lab, loading Linux and CM, then configured all the goodies, a three digit dial plan, and added two stations in the 100 range. I emailed back to my boss that I needed five IP adrresses from the Kabul network, so we could configure the machine and the Media Gateway, as they usually do here, they sat on their hands, and I came back, waited nearly three months for the box to arrive. It got here, and I ran my cabling, and racked the Server, I then went into AIW, and started the programming, all seemed well, I entered IPs I had begged for from IP, and asked them what the IP route was, they swore it was 0.0.0.0 and then the default gateway, so I had to take their word on it. Everytime I got to the part where the controller list tells you to ping the server, it would fail, I kept telling IP I thought there was a problem getting through the routing, but they wouldn't listen. Worse than all of this, when I went into emulation mode, the Media Gateway was installed as Gateway 2, even though we only have one box, and my dial plan would not allow me to add extensions in the 100 range. I couldn't find the extensions we had built in Dubai, slowly things became clear, I did not have the same box in my hands, that I had worked on in Dubai, as it was all preconfigured, obviously as an expansion Cabinet. Tech support is very hard to reach from here, but when I did reach them they just kept giving me generic troubleshooting tips which I had performed a dozen times before calling them. I asked for the license key and proceeded to reinstall CM, it went OK until I tried to log back in, it won't accept my login credentials, I suspect it was reset and must be done by an Avaya Associate, so I am dead in the water. Such a shame. I really like Avaya, but, their assumption that any install will have easy access to their craft techs through remote, is not good. Here in Kabul, we cannot really call out of country, when we do get a connection, it is so bad it is essentially useless, oddly enough, we have decent Internet Service, so, I usually use Skype when I need to make a call, although it doesn't work when I call Dubai or Iran, I can hear them, but on their phones, mobile, office, etc, they can't hear me. i don't know how I am going to get this password problem straightened out since we don't have dial in modem capability. These guys wanted this done in a hurry, but sat ontheir hands and got it to me with a week to go before my Christmas vacation, I leave tomorrow for the States, and this thing is dead, dead, dead, and they think it is my fault, life can really suck!