Avaya SAL GW Server

[avAyATEKky]

I have came across a situation with SAL GW Server (not System Platform SAL) not sending alarms. I can log into the SAL and do a test alarm and receive Avaya test email, but when I actually have an alarm nothing. Now I thought SNMP on all my devices thats registered (product ID/SEID) should point to the SAL then forward to Avaya. But there is no SNMP setup on any of the devices.

Bottom line does any one knows how the SAL actually communicates with the devices sending traps.

Today Makes Tomorrow

 

[kyle555]

I'm pretty sure everything is supposed to send SNMP to the SAL gateway. I remember adding some elements like AAEP and stuff and when you configure an SNMP destination your choices are "NMS" or "SAL" and it presumably send SAL SNMP in a mildly different way.

Even without SNMP, Avaya should be able to access those machines via SEID through SAL, so your setup wasn't totally useless.

 

[dialtonebone]

Yes, the process is pretty simple for alarming: product sends an SNMP trap to SALGW, SALGW then processes and sends it to the configured SAL server at Avaya or your BP.

Have you checked that products (CM/AAM/whatever you have) are sending SNMP traps to SALGW? If you have CM or AAM, ssh to the server and type "almsnmpconf". This will tell you what's up.

 

[avAyATEKky]

Thanks, that what I thought due to how I have use in before on the System platform SAL. But when I set up a CM, or etc to snmp to the SAL GW it test good in CM but I do not get the Avaya test email. They put this in last month and stated its working but I think its just working from the SAL to them, not the managed devices to SAL to them.

Today Makes Tomorrow

 

[avAyATEKky]

Also the Services VM template on the system platform does that need to be running for the other platforms to send snmp to a sal gateway read that in an article.

Today Makes Tomorrow