We have a new release of the Kemp LoadMaster Management Pack. You can read all the details on Daniele Grandini’s blog.
Tag: SNMP
Kemp LoadMaster Monitoring Management Pack (Community MP)
Recently I was looking how to monitor Kemp LoadMaster devices with SCOM. I was able to discover them trough SCOM as Network Devices but that was the only thing and it was not enough. Fortunately fellow MVP Daniele Grandini decided to help me and develop Kemp LoadMaster Management Pack. He was the main driver for this MP to exists as he was the main developer and I’ve took the task of testing it and fixing some small bugs that we’ve encountered. This is initial version of the MP and contains some know issues some of them are due to kemp loadmaster others are internal for the MP. Consider this version somehow as beta as we have some plans to re-write the MP in the future if we can. You will find the MP here along with some documentation. You can log any feedback you have on the Codeplex page.
Configuring HP Storage Management Pack for SNMP devices in SCOM
In my previous posts I’ve covered Configuring HP ProLiant Server Management Pack and Configuring HP BladeSystem Management Pack and now it is time of another MP by HP. In this post I will cover how to configure HP Storage Management Pack for SNMP Devices. This MP supports two more methods (WEBES and WMI) for monitoring bedsides SNMP and depending on the method various HP Storage systems are monitored. The HP devices supported by SNMP method are:
- P9000
- P2000/MSA
- Tape Storage
- P4000
- B-Series Switches
- HP 3PAR Storage System
- HP D2D Backup System
Note: I will cover configuration that only needs to be done on SCOM side. Configuration on the different storage systems for SNMP is available in the user’s guide of the management pack. Make sure you have the latest firmware versions of these devices
It is common practice management packs such HP Storage to be installed on the RMS server but depending on your environment you can use any other server with SCOM agent on it. Follow these general steps to install and configure HP Storage MP for SNMP devices:
1. Install Windows SNMP Service feature on your RMS server.
2. Download the HP Storage Management Pack from HP site.
3. One zip file is download which when extracted contains the following files:
• HP Storage Management Pack for System Center.zip
• HP Storage WEBESListener for System Center.zip
• HPStorageManagementPackforSystemCenterUserGuide-2.x pdf (User Guide)
4. If you will not use WEBES method you can only unzip HP Storage Management Pack for System Center.zip.
5. Copy the zip files to your RMS server.
6. Unzip the HP Storage Management Pack for System Center.zip file.
7. Navigate to the unzipped folder, and run setup.exe.
8. Click Next to continue.
9. Click Next to confirm the installation.
10. Click Close after installation is finished.
Note: All files including the HPEnterpriseStorageMP.mp are installed in ~:\Program Files\HP\HP Enterprise Storage directory for a 32-bit operating system, and ~:\Program Files(x86)\HP\HP Enterprise Storage directory for a 64-bit operating system.
11. The management pack will be automatically imported in SCOM if not you can locate the mp file and import it manually.
12. After the MP is installed SNMP Service have to be configured.
12. Start Services.msc. Locate SNMP Service and double click on it to open Properties.
13. Click on Security tab.
14. Check Send authentication trap.
15. Add Community name with READ rights on Accepted community names. This is the community name that you will use for Storage devices when configure them.
16. Select Accept SNMP packets from these hosts.
17. Add the IP addresses of every storage device you will monitor trough HP Storage MP.
18. Click OK to save settings.
19. After SNMP Service is configured properly SNMP Trap Catcher Rule in HP Storage MP have to be enabled.
20. Open SCOM console.
21. Click on Authoring pane.
22. Click on Rules.
23. In the Rules window, search for HP Storage Trap Catcher rule using the Look for: search bar.
24. Right-click the HP Storage Trap Catcher rule and select Overrides > Override the Rule. Select For a specific object of the type: HP Storage SNMP Trap Catcher discovery and in the search filed find the FQDN of your RMS server. Select it and click OK.
25. Override Properties window will appear.
26. Check the box under Override column. Change the value under Override Value from False to True. Select the management pack that you save overrides and click OK.
Note: Management Server Action Account has to be a member of the Operations Manager Administrators user role in SCOM. If this not set you may have trouble with some PowerShell scripts not being able to finish successfully.
Another additional configuration that I recommend is that if you do not have P4000/E5000/X5000 systems in your environment is to disable HPEnterpriseStorage.SNMP_CommandExecutor.Rule and HPEnterpriseStorage.WMI_CommandExecutor.Rule. These rules are executed every minute and could cause some performance issues on your RMS server also they are improperly targeted to Group. Follow these steps to disable them:
1. Open SCOM console.
2. Click on Authoring pane.
3. Click on Rules.
4. In the Rules window, search for SNMP_Command using the Look for: search bar.
5. In the listed rules search for the Type : Group.
6. Right Click on the HPEnterpriseStorage.SNMP_CommandExecutor.Rule -> Overrides -> Override the Rule -> For all the Objects of the class :Group.
7. Select the check in front of Enabled. Set Override value from True to False. For Management pack select your MP for overrides and click OK.
8. Repeat steps from 4 till 7 searching by WMI_Command for HPEnterpriseStorage.WMI_CommandExecutor.Rule rule.
After these steps are executed you are left with only configuring the storage devices to send SNMP packets to your RMS server.
Configuring HP ProLiant Server Management Pack for SCOM
In my previous post I’ve covered the configuration of the management pack for HP Enclosures. But this MP only monitors health of the enclosures and not the blade servers inside via SCOM. In order to monitor blade servers or any other standalone HP server you have to install and configure HP ProLiant Server Management Pack. Actually if you want to use HP BaldeSystem Management pack you must import HP ProLiant Server Management Pack also.
HP ProLiant Server Management Pack can monitor HP servers trough two different methods:
- SNMP method – For this method you must install HP Insight Management Agents on every server you will monitor besides the SCOM agent. This method uses SNMP to send trap messages.
- WMI method – For this method you must install HP Insight Management WBEM Providers on every server you will monitor besides the SCOM agent. This method relays on WMI service.
As I am a Windows Engineer I prefer WMI method and on this article I will cover only this way of implementation.
The guide that is provided with this management pack covers both methods and I recommend reading it. This article will walk you trough the basic actions you need to do to install and configure HP ProLiant Management Pack for SCOM:
1. First you need to download the management pack itself from here. The MP is part of HP Insight Control for Microsoft System Center solution.
2. You will download one zip file that contains – 32-bit installation file, 64-bit installation file, License agreement file, Release notes file, User Guide and Troubleshooting Guide.
3. Copy 64-bit installation (if your SCOM server is 32-bit use 32-bit installation) to your RMS server and install it. It is pretty simple installation you can leave the default options. During the installation you will be present to choose if you want to install SNMP based method, WMI based method or both. If you choose only one of the methods the installation will only import the management pack that corresponds to the chosen method. It is best to choose both because you can always switch between methods or for example you can monitor one group of servers with one method and another group with the other one.
Note In the documentation of the MP it is not mentioned that the MP requires to be installed on the RMS server. In fact the MP can be installed on any Management Server or any server that have SCOM agent installed.
4. After the installation is finished the HP ProLiant Management Pack should be imported in SCOM and HP Custom Data Manager application should be installed. This application will allow you to enter additional information (fore example end of hardware support date) for individual servers that will be populated in SCOM Database.
5. After the MPs are imported discovery of HP servers will start. Discoveries are enabled by default so there is no additional configuration there. At this step it is best to check if all your HP monitored servers have HP Insight Management WBEM Providers installed. This can be achieved by opening SCOM console and navigating to Monitoring Pane –> HP Systems –> Windows Server State. Here you can see the discovered HP Servers in your environment. Modify this view to show HP Management Version column. This will show you if SCOM agent found HP Insight Management WBEM Providers.
6. Next and final step is to configure the MP to use WMI based method. By default HP ProLiant Server MP uses SNMP based method and this can be switched to WMI by overriding a rule. To do that you have to navigate to Authoring Pane –> Management Pack Object –> Object Discoveries. There you have to look for HP ProLiant Server Discovery Rule. When you find that rule select it and right click on it. Select Overrides –> Override the Object Discovery ->For all objects of type: Windows Computer. A new dialog will appear. Select all check boxes under Override column, change the value for SNMPWMIPrefernece from SNMP to WMI and save the override to your HP ProLiant Server Management Pack for overrides.
Note If you want to switch to WMI based method only for particular servers create SCOM group and populate the group with the servers you want to monitor via that method. When you make the override in step 6 override for specific group and choose the custom created group.
7. This will switch to WMI based method for all Windows computers in your environment. After you made this setting you can again navigate to Monitoring Pane –> HP Systems –> Windows Server State.Edit the view to show Monitoring Source column. You will see your HP servers slowly switching from HP Insight Management Agents for monitoring source to HP Insight Management WBEM Providers.
After step 7 no further overrides are need in order to make HP ProLiant Server Management pack to work via WMI based method.
Configuring HP BladeSystem Management Pack for SCOM
Most of the large organizations today do not buy individual servers (exceptions are present of course) instead they buy Enclosures. In one such enclosure you can put up to 16 server and/or storage blades. HP as one of the biggest hardware vendors offers two such solutions – HP BladeSystem c3000 and HP BladeSystem c7000. If you bought such solution you receive for free HP BladeSystem Management Pack from HP for SCOM to monitor HP Enclosures. To start monitoring you HP Enclosures of course you have to first install and configure that MP on your SCOM environment. HP is providing installation and configuration guide for the management pack but I will walk you trough the steps you need to perform if you stumble on some difficulties. These steps are applicable for SCOM 2007 and 2012 versions:
1. First you need to download HP BladeSystem MP. You can find it here. The MP is part of Insight Control for Microsoft System Center solution.
2. After the MP is downloaded it is best to install SNMP Services feature on your RMS server (RMS Emulator). As in 2012 you have RMS emulator and you can move that role to other Management Server it is good idea to install SNMP Services on another Management server if you want to failover in case your RMS Emulator server goes down. SNMP Services installation does not require restart.
3. The HP BladeSystem MP when it is downloaded is archived in a zip file in which you can find several files – 64-bit installation file, 32-bit installation file, License agreement file, Release notes file, User guide and Troubleshoot guide. When you unzip it copy the 64-bit installation file (these days there are not many 32-bit SCOM servers 
) to your RMS server.
4. Start the 64-bit installation. Keep in mind that this management pack have certain requirements – HP ProLiant Server Management Pack imported (I will describe installation and configuration of that MP in another article), Windows PowerShell 1.0, .NET 2.0 Framework, SNMP Trap Service (We installed it in step 2) and of course at least SCOM 2007. Finish the installation with the default settings. It is pretty simple installation. If you have SCOM 2012 you perform the installation on the your failover Management Server also.
5. After the installation is finished you will see two new service and one application installed:
6. Next step is to configure SNMP. Open Services console. Find SNMP service and double-click on it. A dialog box will appear on which you have to click on Security tab:
7. You have to check Send authentication trap option. Add community name that you will use for communication between the RMS server and the enclosures. You can use READ ONLY rights.
8. Select Accept SNMP packets from these hosts and add all your IP’s of your Onboard Administrators (Primary and Secondary). Onboard Administrator is the control interface from Enclosures. Click OK when you are done. Now the RMS server is configured to receive SNMP packets from the Enclosures you will monitor. If you are using SCOM 2012 you can make the same settings on your Management Server that you will use for failover of your RMS Emulator role.
9. Next step is to add your HP Enclosures to HP Device Monitor Console. You can find that console in Start Menu -> All Programs -> HP SCOM Management Packs.
10. When you start it you need to make a connection to localhost, FQDN (of your RMS server)or NetBIOS name (of your RMS Server). The console actually connects to that HP Monitor Device Service that is installed on the RMS.
11. After you are connect to that service trough the console on the right of the console you will find Actions menu from where you can select Add Onboard Administrator option.
12. Click on Add Onboard Administrator.
13. A new dialog box will appear where you have to add IP address or FQDN of your Onboard Administrator. You also have to provide your administrator username and password to your Onboard Administrator interface.
14. Add all your Onboard Administrators to the console using steps 12 and 13. Adding OAs in the console will discover all components of your Enclosures and will draw SCOM diagrams for them. If you have SCOM 2012 you can connect the HP Device Monitor Console to your failover Management Server and add the same OAs there.
15. The final configuration step is to configure OAs to send SNMP traps to the RMS server. This can be achieved by opening OA web interface. When you open the interface you have to expand Enclosure Information than expand Enclosure Settings and finally click on SNMP Settings. Check Enable SNMP option, fill the other fields and click Apply. For Read and Write community name use the one entered you’ve used in step 7.
16. Now that SNMP is enabled we have to configure OA to send traps to specific IP address. Right beneath Enable SNMP settings there is SNMP Alert Destination setting. For host you have to enter the IP address for your RMS server and for community name enter the one you’ve used in step 7. Click Add. There is Send Test Alert button which will send trap to your RMS server and will appear as warning alert in SCOM console. This is very handful option to verify that your configuration was successful.
17. Repeat steps 15 and 16 for all your OAs.
When you complete your configuration you can use Send Test Alert option to see if all enclosures are configured correctly and are receiving alerts. You also should be able to use all your enclosures by opening the SCOM console, navigating to Monitoring pane –> HP Systems –> HP BladeSystem Enclosures –> Enclosure State:
Note: HP BladeSystem Management Pack should be imported during the installation. If for some reason this is not done you can import the MPs manually by finding them on the RMS server in the installation folder of the MP. This also refers to HP ProLiant Server Management Pack.
If you have SCOM 2012 and your RMS Emulator server fails you can follow two steps to recover your monitoring for HP BladeSystem Enclosures:
1. Transfer RMS Emulator role to your failover Management Server
2. Change the IP address of your failover Management Server to the IP address of your failed RMS Emulator server because SNMP traps are send to specific IP address. If you do not want to change the IP address on your Management server you have to reconfigure all OAs to sent SNMP traps to your new RMS Emulator.
Note: HP BladeSystem Management Pack does not require to be installed on RMS server (RMS Emulator). It can be installed on any SCOM Management Server or Server that have agent installed but is common practice such monitoring solutions to be installed on RMS. Also the documentation of the management pack doesn’t mention that the MP relays on the RMS (RMS Emulator) server to function properly.
Cloud Administrator in Azure World 