How to Setup Ironport Monitoring with the IronportMonitor ZenPack.

From SysAdminWiki

Contents 1 Overview 2 Procedure 3 Building the Performance Graphs Manually 4 Screenshots 5 Notes 6 Contact

Overview

Ironport is an intelligent email gateway / web security appliance. There are many different models, but monitoring them is all done the same way, mainly by SNMP. This tutorial shows you how to setup Zenoss to monitor how these devices are performing. This has been tested on multiple C150's but should work for any model.

Things to Note:

• Your email relay's are setup as listeners. You will not want to monitor smtp on your main ironport IP. Add the ListenerIP to Zenoss as its own device and have it just monitor the smtp service. That being said Zenoss will pick up the fact that your listener IP is virtual interface and display it on your OS page allowing you to see the through put on the Data 1 interface statistics.

• You have to load the following mibs: ASYNCOS-MAIL-MIB.txt & IRONPORT-SMI.txt. Which you can get from Ironport's support page.

• This Zenpack is geared towards the C model Ironports but should work for the others as well.

Procedure

• 1. First thing that needs to be done is to get the SNMP setup on the Ironport itself and to make sure you can do an snmpwalk from the zenoss server to the Ironport itself. This is done using the snmpconfig utility on from the Ironport CLI. From your zenoss server do the following:

snmpwalk -v2c -c<ironport_community> <ironport_IP>

• 2. Next load the Ironport MIBs into Zenoss, including the AsyncOS ones. They are available on Ironport's website. If you do not intend on sending traps from the Ironport to Zenoss then you do not need to do this for the zenpack to work.

• 3. Next install the [ZenPacks.Ironport.PerformanceGraphs-1.0-py2.4.egg] using zenpack -install. More detailed instructions on installing zenpacks is available [here.]

• 4. If that works then have Zenoss discover the device using the proper community string. Set the Device Class Path to /Devices/Ironport. The Zenpack should have created that for you. Allow it to collect data for a few minutes.

• 5. Navigate to your device from the Device List section and click the drop down menu, click More -> Templates. Click the next drop down -> click Add Template. Type Ironport into the ID feild.

• 6. Wait about 10 minutes and check the Perf tab of your Ironport Device and your should see some graphs.

• 7. Next you will want to configure the Thresholds to something more custom to your environment. Do so by going to /Devices/Ironport and clicking on the Template tab. There are some default thresholds already configured, have a look at their properties and make sure they suit your needs.

Building the Performance Graphs Manually

This can be handy when you want to add more OIDs to monitor, Ironport releases some new mibs, you want to extend the ZenPack, learning purposes, or the ZenPack won't install for you.

• 1. Load your Ironport into Zenoss and make sure SNMP is working correctly. I put mine into /Devices/Ironport.

snmpwalk -v2c -c<ironport_community> <ironport_IP>

• 2. Next add a new Device Organizer for Ironport.

Click Devices -> On the Sub-Devices Box click the drop down arrow and choose Add New Organizer. Type Ironport in the ID Box.

• 3. Browse into /Devices/Ironport and click the Templates Tab.

• 4. Click the Drop down menu and choose Add New Template. Enter Ironport into the ID feild.

• 5. Click the Ironport Template link and you will be in the performance template page. Here is where we set our data sources, build the graphs, and set the thresholds.

• 6. Enter the following in the Description:

"Performance Template for Ironport Mail Relay Devices, based on the AnsycOS and Ironport MIBs."

• 7. So now we build data sources. This is the most important part. CASE IS IMPORTANT. I ALSO RECOMMEND NOT USING WHITE SPACE IN NAMES.

Make sure to not miss any of these steps:

• • 7a. Click the dropdown menu and select Add New Datasource.
  • 7b. In the ID feild call it fanRPMs and Type is SNMP.
  • 7c. After hitting OK you land on the Data Source properties page.
  • 7d. Set Enabled to True.
  • 7e. Enter the following for OID:

1.3.6.1.4.1.15497.1.1.1.10.1.2.1

• • 7f. Next Click the drop down on Data Points and select Add Datapoint. Call it fanRPMs as the ID.
  • 7g. On the data point properties page Type should be Guage.
  • 7h. Enter 1000 as RDD Min and 6000 as RDD Max.
  • 7i. Leave the Create CMD blank.

OK, so that is the first data point. Now we repeat this about 7 times, except using differnt names and replacing the OID with the correct one. Also note you do not need to set the RDD MIN OR MAX range for the rest of these

• Here is a list of name and OID to change so you can copy/paste them:

fanRPMsFan2			1.3.6.1.4.1.15497.1.1.1.10.1.2.2
mailTransferThreads 		1.3.6.1.4.1.15497.1.1.1.20.0 	
memoryAvailabilityStatus 	1.3.6.1.4.1.15497.1.1.1.7.0
openFilesOrSockets 		1.3.6.1.4.1.15497.1.1.1.19.0 
perCentCPUUtilization 		1.3.6.1.4.1.15497.1.1.1.2.0
perCentDiskIOUtilization 	1.3.6.1.4.1.15497.1.1.1.3.0 
perCentMemoryUtilization 	1.3.6.1.4.1.15497.1.1.1.1.0 
perCentQueueUtilization 	1.3.6.1.4.1.15497.1.1.1.4.0 
temperatureEntry 		1.3.6.1.4.1.15497.1.1.1.9.1.2.1

It should look like this:

SO once you have those sources , create the performance graphs:

• 8a. On graph definitions click the drop down and select Add Graph.
• 8b. In the ID feild type: Open Files Or Sockets
• 8c. On the graph properties page, click the drop down beside Graph Points, and select Add Datapoint.
• 8d. Now you have a list of all the available graph points. Notice they are the ones we just created in the previous steps. So we pick the one for openFilesOrSockts_openFilesOrSockets. Then click ok.
• 8e. Thats it for the graph point. We will customize the look of these later. For now lets get the rest of the Graph Points built. Do the rest the same way as above except the fanRPMs one. You will add 2 data points to the same graph, both fanRPMs and fanRPMsFan2 data points should be listed on this one.

Here is how it should look:

• 9. ADD THRESHOLDS. (to come.)

Screenshots

Notes

Version 1.0 - Includes changes from 0.9. 0.9 never was released for download.

• Added new perf graph which includes cpu,mem,disk usage coralated onto one graph.
• Improved cosmetics of perf graphs.
• Improved thresholds.
• Removed MemoryAvailabiltyStatus perf graph.
• Removed RDDmin/max for fanRPMs.

(will be released Jan. 09)

Version 0.9 - Added /Manufactuers/Ironport with a list of models and AsyncOS versions from 3 to 6.3.

Version 0.8 - Graphs and Alerting for Open Files or Sockets, Mail Transfer Threads, Percent CPU Utilization, Percent Disk IO Utilization, Percent Memory Utilization, Percent Queue Utilization, Memory Availability Status, Fan RPMs, Device Temperature. All thresholds set to warning except fan RPMs which is set a high threshold and will show as critical. One user has reported to me that their fan2 was exceeding 7000RPMs (was indeed a problem), so I do plan to lower it in 0.9 where none of our Ironport's are not exceeding 3600RPM's.

Contact

Any questions about this ZenPack can be directed to nmkj05 at gmail dot com.