I have a cluster of Mitel 3300 ICP PABX’s across several offices internationally and have been looking for a monitoring solution that can send alerts whenever an alarm is triggered on any one of the PABX controllers. Mitel already have a monitoring solution called Enterprise Manager, but this didn’t do what I wanted it to do. Enterprise Manager will send out emails based on certain policies and allow for issue escalation but its features are a little limited. I already have an extensive Nagios setup that will SMS and email for alerts, so I looked at integrating with this system.
I had a failure in one of my Exchange Storage Groups last night and the Storage Group had dismounted itself. However the Information Store service was still running and so were the other three Storage Groups on the server. So that got me to thinking, how do I monitor the individual Storage Groups for failures with Nagios?
Linode provides a convenient XML data feed that provides information about your CPU usage and Network Usage. The graph for the CPU Usage seems a little useless, but I have included it here as the XML feed provides the data.
You will need your linode account number to use the graphs, you can find this number by looking at the graphs provided to you in your Linode account management interface. The title of the graph will be “http://www.linode.com/ – yourhostname (linode12345) – CPU – …….”. You will need the text from inside the ( ) for your username ie linode12345.
I recently wrote a three part article on using Autoyast to automate the installation of OpenSUSE machines. I this article I will show you how to setup a local software update repository as well.
OpenSUSE and SLES (SuSE Linux Enterprise Server) both come with AutoYaST which is a very powerful tool that allows administrators to quickly and easily deploy servers that have an identical configuration for rapid server deployment.
In this three part series we will explore creating a repository for use with multiple systems, creating and customizing the AutoInstall file, and finally running through an install procedure.
Part 3 – Putting it all together and installing a server
In this part we will look at running through a machine install making use of our newly created repository and AutoInstall file.