Server Troubleshooting Techniques
3 procedures to a ensure a successful Avaya Aura deployment.
By the end of this post, ‘Server Troubleshooting Techniques,’ you will learn the three procedures that I use to install the new Avaya Aura servers. Following these principal rules of checking the server hardware, software, and ensuring software stability, will help you install any type of VoIP solution including ECG, and SME, also called SMB.
As system technicians/engineers, we get to help our clients by installing the solution proposed by the AE; which, unfortunately, it is not always the real offer the customer got presented with. It is up to us to make it possible for the customer to get a working solution that benefits their needs and do what they had in mind.
It is important to point out that although these systems are already pre-configured with CMs translations and system configuration pre-built, you still need to check that these procedures mentioned below are taken.
These are the three techniques=
- 1.- Hardware check
- 2.- Software Validation
- 3.- Software Stability
1.- Hardware check
Once you have successfully installed the servers following the ‘Environmental Avaya Guidelines,’ you must verify that all of the installed components are working. You can do this by running health commands and navigating the server maintenance SMI.
Communications Manager Health Commands
status health – this command shows the system performance by displaying events and categorizing them in alarm interval from minor to majors, listing port networks and other variants.
Display Alarms – This command will capture both CM and most of the server alarms into a single output. For example, the AC-Power alarm is generated when there is a problem with electric power. For a list of alarms see the references.
Server Alarms – These can be found in the Server SMI Console under Maintenance/Alarms. For example, the Linux servers run the Arbiter process on duplicated servers, and Arbiter alarms are generated as ARB Event-IDs 3, 7,8, etc. For a full list of server alarms refer to the references
Server Shell Maintenance Commands
To get to Communications Manager Shell Level Access, type ‘go shell’ from CM’s CLI or Command Line. Once in the shell, you can run these commands=
vm_status – This commands is a shell command that generates information about the status of Communication Manager.
statuslicense -v = This command looks at the license status preloaded in the system.
raid_status -p -v = As a shell command it displays HDD status
For more shell commands go my previous post ‘Avaya Shell’
2.- Software Validation
After finishing a new server installation, it is always a good practice to have the necessary files to activate your software. These two main files are the License File and Authentication or Password file.
WebLM – This component provides license management to any Avaya Aura server and its components. The WebLM can be deployed as embedded or in its own server.
The License file gets installed in the WebLM server; then CM communicates with he WebLM, and activates the RTUs purchased by the customer.
The password or Authentication file gets installed under SP Web Console. For pre 6.0 servers, both files get installed using the SMI Maintenance console, and navigating to License File and Authentication File menu options.
One more thing here, for newer severs, you must provide the MAC Address of the Cluster or Primary Server in order to generate the license file.
There is one command that I recommend that you run from CM’s Shell=
productid – display the system configured product ID. Keep in mind that this number must match the licensed generated for this system.
Finally, check that the license is active and valid without mismatches. It is important to mention that each license is generated based on software releases.
3.- Software Stability
As installers, we all know how often Avaya releases patches and service packs. Do your homework before going out to the customer site and download the most stable patches, service packs, and apply them to the new server(s).
Please note: I reserve the right to delete comments that are offensive or off-topic.