SAL Gateway upgrade questions 1

[bfordz]

We're running Avaya Aura CM 5.2 with a SALG of 1.x

So, we need to upgrade to stay compliant and "in touch" with Avaya maintenance / support.

To install an external server / SAL Gateway setup:
What type of server / equipment is required?
What OS is required to run the SAL Gateway?
What are the steps / procedures required to setup, install and get a SAL Gateway up and running?

Our vendor wants what seems to be an astronomical $$ amount to do this for us.
My boss doesn't want to pay the extra money because we own outdated / older equipment (we released maintenance in 2/16)
We need the SAL but I'm not sure it's something I can do myself.

Any input / suggestions would be appreciated.

 

[kyle555]

Well, you need the software. You can install it on your own red hat OS that you configure with the right packages. Or, Avaya also has a VMWare based virtual machine that you can just spin up in your infrastructure. If it's just 1 CM, that would probably be the easiest solution.

 

[wpetilli]

I'm using this link and so far it's going great... well written doc. A bunch of stuff still to do, but for the most part it's been spot on.

https://downloads.avaya.com/css/P8/documents/101024119

 

[bfordz]

kyle555,
thanks for the reply and suggestion; I"m not Linux proficient, so installing on our server with Red Hat is probably not the option for us. I do have a Virtual machine running but I'm not terribly proficient in that either but it's worth looking into.
yes, we only have 1 CM so I will look into the VM idea a bit more.

wpetilli,
thanks for your reply and the link. I had a link describing the upgrade but it was pretty vague as far as the steps needed to make the upgrade.
I've downloaded the document and I'm looking it over, it is definitely much more detailed than the previous document I have.
I like the idea of the YouTube videos for the walk thru instructions.

Thank you to both of you.

 

[wpetilli]

Oh well.. I take back what I said. got the base install done w/no problem. Now trying to run the upgrade 2.5 and get to the accepting of the licensing agreement and once I choose to upgrade SAL it's been running for an hour and the status bar keeps going a 1/4 of the way across and then comes back and then starts again.... over and over. The only thing I did was skip the upgrade of Java to 1.7 because after installing the base .ova the version was already 1.7.

 

[wpetilli]

If anyone has hit this same point, I'd appreciate how you got around it. I opened an Avaya support ticket and they won't help until I have the new SAL registered and online, which was on my agenda. Just wanted to do it after all the s/w was completed.

 

[wpetilli]

or if anyone is running ADS2.5 on vmware can you share what your bashrc file looks like? The doc for the whole Java thing is vaguer than vague.

 

[scotthdiv]

I skipped the Java upgrade when I installed ADS 2.0 and was able to upgrade to 2.5 SP3 without it as well.

Are you using the most recent 2.5 SP3 file? There was an issue with the previous one related to the install/upgrade. The one I used was ADS-ServicePack-2.5.3.0-254.tar.gz.

Also - I modified the ADS_Response.properties file to accept the license and ran the installer in unattended mode. Prior to that, I had tried to run it as attended and had the issue you described above.

 

[wpetilli]

the doc said to install the ads2.0 .ova base, then upgrade to 2.5 and then the sp3 file

 

[scotthdiv]

Your right - my apologies. You do have to install 2.5.0.0.177 first. I believe I followed the same steps though - changed the ADS_Response.properties file to accept license and then ran it in unattended mode.

 

[wpetilli]

WORKED!! Thanks so much, I've been going bonkers with this for 3 days. However, I now can't get to the web interface of the SAL after the upgrade and a reboot.

 

[scotthdiv]

Try this command: service gatewayUI start

Also, be sure you are accessing it like this:

https://<ipaddress>:7443

 

[wpetilli]

Thanks - I restored back to the base install, didn't bother installing a new JAVA and did the unattended as you stated and it went perfect. Just waiting for FW rules and smtp relay and can move the managed elements over. Do I need to make any changes in any of my CM/SP/GW's for this new SAL? Been poking around and am not seeing anything on that.

 

[scotthdiv]

No changes should be necessary for CM, etc.

 

[bfordz]

I'm back; I installed the OVA file onto our VMware VM.
I now have a few questions;

What do I use for the WebLM server?
I put an IP in the field just to continue, not sure if it was a correct one.

Also, Now that I've finished the install I can't get to either web interface;
SLA Monitor or SAL Gateway.

I'm getting an SSL error message:
An error occurred during a connection to 192.224.244.48:4511. SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message. Error code: SSL_ERROR_WEAK_SERVER_EPHEMERAL_DH_KEY

I'm not sure where I made my mistake.

If I have to make changes and can't get into the web interface, will I have to run the install file again?

Any help would be appreciated.

 

[kyle555]

I'm not sure why SAL would need WebLM, maybe SLAmon is a licensed feature, but you don't need any licensing to use SAL to pitch alarms from your CM to Avaya nor to let them get in.

Google the diffie hellman thing. Something about weak ciphers used by older Avaya things are turned off by default in newer browsers. You can turn it on in firefox.

 

[bfordz]

kyle555,
Thank you for that response. The WebLM was one of the fields that was required during setup.

I was able to get the SAL Gateway page to come up but the SLA Monitor just gives me a blank page.

Where do I get the login credentials for the SAL Gateway?
Also, how do I get the root password for the CentOS?

Thank you again,

 

[kyle555]

no root, and you probably setup some admin account at deployment that you can do everything you need from...for the most part...

 

[bfordz]

kyle555,
Thanks again for the reply.
I contacted Avaya and they gave me my root password and login for my new SALGW.

I'm now waiting on Avaya GRT for my SEID and Alarm ID#'s.

Thanks again; I'm sure I'll have more questions.

 

[wpetilli]

I'm getting down to the last few elements for avaya to finish the alarming re-tests etc... For a test I did shutdown the original SAL GW and then took a remote branch gw offline to see if I receive the email alert and I did not. If I generate a test alarm from the SAL GW itself I get an email about that, but I'm not getting emails about the remote branch being offline. Do I need to disable or delete the original SAL GW record in GRT?