Maintenance and Services

I just upgraded our VSALGW running on our Aura System Platform s8800 / CM 5.2.1.

Old VSALGW ver. 1.5.3 to New VMware SALGW OVA ver 2.5.3.0.7

My question(s) and concerns are; what do I have to setup / change in my System Platform / CM so that my Avaya system sees and communicates with my New SALGW?

How does my System Platform / CM know that my New SALGW is a stand alone machine?

Is there a "test" I can make from my System Platform / CM to make sure any Alarms are getting to my SALGW?

The Secure Access Link (SAL) Gateway for SHA-2 compliance 'playbook' doesn't explain anything more once you get the external VMware SALGW up and running. I would rather not wait until something fails to find out no "Alarms" were sent to Avaya.

Brad -

I don't think your System Platform needs to know about your SAL GW. Your SAL GW will communicate with Avaya. After completing the new build, you can test if your are now SHA-2 ready by going here: https://acsbi.avaya.com.

After that is complete, you can check the connectivity/alarming by doing a Health Check. Here are the steps for that:

1. https://secureservices.avaya.com/osm-phs/views/home.xhtml
2. Create Test
3. Enter your location ID
4. Choose the products you want to test connectivity and alarming for
5. The results will be emailed to you

If for some reason a device fails, you are supposed to submit an SR to get Avaya to look at it.

I had to do this recently. I went from one VM to another as the upgrade didn't work. Had to build a new one.

Hope this helps,

Daniel

Daniel,

Thank you very much for that very detailed reply.

I have followed those steps you listed and am now waiting for their response and results.

Brad