Cleaning after someone else

Cisco2960X48PoE_IPServTechnologies

Cisco2960-X 48_PoE_IPServTechnologies (c)

Cleaning after someone else

This week I got sent out to clean up someone else’s mess.

How many times have you been through something similar?

Write your comments, in the comment section below

 

Avaya Port-Network

G650s_Back_IPServTechnologies

G650s_Back_IPServTechnologies (c)

With all the hype of Cloud computing and VoIP, old good TDM still rules. For 15 years now I’ve been integrating IP with Legacy solutions. Why?…I guess because it just works. Don’t get me wrong, we’ve come a long way since the beginning of Convergence. But it feels that we still have a long road ahead of us, to see the day when SIP takes over, and we say good-bye to Circuit-Switching.

 

SAL SNMP Sub-agent

Today I was out troubleshooting an Avaya Aura Secure Access Link (SAL) Server Gateway. This particular one is running on a stand alone Dell PowerEdge R210 rack-mount server.

SAL Gateway Services Window

SAL Gateway Services Window

As displayed in the photo here. I couldn’t seem to be able to start the SAL SNMP Sub-agent service.

After some digging I was able to fix this issue by restarting the following services=

  • gatewayUI
  • spiritAgent
  • axedaAgent

Once restarted; everything started working normal again!.

These are the commands to restart these services=

  • 1.- Execute the following command to restart the Gateway UI service:  /sbin/service gatewayUI restart 
  • 2.- Execute the following command to restart the spiritAgent service = alarming agent:
    /sbin/service spiritAgent restart 
  • 3.- Execute the following command to restart the axedaAgent service = remote access agent:
    /sbin/service axedaAgent restart