6 Common Avaya System and Session Manager Troubleshooting Solutions

As many of you work on integrating Avaya Aura System and Session Manager into your networks, the case for troubleshooting will indeed occur.

There are built in tests in the System Manager that allow you to run tests on fourteen different areas, including Session Manager. But what do you do with the results when you get them?

I am going to outline six of the most common problems and solutions when installing and implementing System and Session Manager and what steps you can take to troubleshoot and correct the problem.

1. Symptom: Session or System Manager tests fail hostname resolution.
   Remedy: Putty to Session Manager and log in using craft/craft01
   then, su – sroot/sroot01. Or System Manager, log in using admin/admin
   then su – root/root01 Type in cd /etc, then press enter. Type more hosts and verify the hosts table has an entry for both Session Manager and System Manager. If an entry is missing, from the location you are currently at,type vi hosts. This will bring you into edit mode for the hosts table. Position your cursor at the end of the existing entry, then press I for insert mode. Hit enter to begin a new line in the Hosts file and enter the missing entry. Upon completion of the entry. Press escape and then Type :wq! To write the file and exit the table. Go back to System Manager and run your tests from the Session Manager dashboard to verify tests will now Pass.
2. Symptom: Session Manager Security Module wont come up
   Remedy: Putty to Session Manager and log in using craft/craft01
   Then, su – sroot/sroot01. Type ifconfig >text, then type in more text and verify that ETH2 or ETH3 is set with the SIP Entity address (.xxx). If there is no entry, then type ifconfig eth2/3 xxx.xxx.xxx.xxx(IP Address) netmask xxx.xxx.xxx.xxx up, then enter. Go back to System Manager and verify the security module is up and operating at the  Session Manager Dashboard level.
3. Symptom: Calls will not route through Session Manager
   Remedy: Verify SIP ETH is up and running using the above steps.
4. Symptom: Entity Links show down or none at all
   Remedy: Verify date in Session Manager and System Manager(*).
   Type in Date at the CLI through Putty. Correct date by logging into Session or System Manager and then   typing in date --set=”12 JULY 2011 13:00:00”(Date/Time)
5. Symptom: Entity Links show down or none at all
   Remedy: Putty into Session Manager using craft/craft01, then su – sroot/sroot01. Type in initDRS to allow database replication to occur. Verify Links are up through System Manager Session Manager dashboard.
6. Symptom: Trust Management failed
   Remedy: Log into System Manager, then go to Security,Certificates, Enrollment Password and verify password is still active and valid. Next putty into Session Manager using craft/craft01, then su – sroot/sroot01 type in initTM to establish Trust Management.

Now keep in mind that these are the most commonly occurring faults you will encounter during an Install or Upgrade to your System and Session Manager. Other troubles can occur, but using this information will help you in your implementation of the Avaya System and Session Manager.

Related Courses
View Avaya System Manager Administration courses.
View Avaya Session Manager Administration courses

Sign up for our newsletter