Technical Notes P/N Rev 01

Transcription

1 SNMP Trap Monitoring Solution EMC SourceOne Version 7.0 and later Technical Notes P/N Rev 01 September 27, 2013 These technical notes contain supplemental information about EMC SourceOne, version 7.0 and later. Topics include: SNMP trap monitoring solution for SourceOne overview... 2 Configuration components... 2 Configuration for a small SourceOne deployment... 3 Configuration for a large SourceOne deployment... 8 Customizing SNMP Trap NMS example of an SNMP trap monitoring solution Glossary

2 SNMP trap monitoring solution for SourceOne overview SNMP trap monitoring solution for SourceOne overview SourceOne now supports SNMP trap monitoring to provide notification of event log errors. The SNMP facilitates the reporting of errors to monitoring tools. Configuration components The following components require configuration to generate structured SNMP traps for logged events, and for the SNMP management station to capture and react to these events. SNMP agent All Windows Server versions come with an SNMP agent that generates explicit SNMP trap messages from any of the logged discrete Windows event messages. This SNMP agent is the mechanism SourceOne uses to create notifications. SourceOne creates an event log entry for all errors. Windows contains a SNMP agent, but it is not part of the default installation. After the installation of the SNMP agent, configure the following: The basic SNMP agent settings such as the trap destinations, the community string, and site-specific SNMP details The event agent components by defining event messages to capture and retransmit as SNMP messages SNMP management station A SNMP management station receives and processes alerts. SNMP management console You must extend the SNMP management console to support the Windows event traps. The Windows SNMP event agent does not include a prebuilt MIB. SourceOne, provides a sample MIB file that includes most critical errors, and you have the ability to add more. After you add any errors, import and compile the resulting MIB in the management system. 2 SNMP Trap Monitoring Solution: Technical Notes

3 Configuration for a small SourceOne deployment Microsoft SCCM For a small deployment, EMC configures each SourceOne server. For a large deployment (for example: the SourceOne environment is complicated with many nodes), EMC configures the Microsoft SCCM to make the translation efficient. Configuration for a small SourceOne deployment To configure a small SourceOne deployment, you must first install and enable the SNMP service and then import event configurations. Installing SNMP service To install and enable the SNMP service, you must install the SNMP Service in either Windows 2003 or Windows Depending on whether you are using Windows 2003 or Windows 2008, there are different steps to follow when installing the SNMP service. Windows 2003 Windows 2008 To install the SNMP service in Windows 2003, perform the following steps: 1. Open the Control Panel. 2. Double-click Add/Remove Programs. 3. Click Add/Remove Windows Components. 4. Select Management and Monitoring Tools from the list. 5. Click Details. 6. Ensure a check exists for Simple Network Management Protocol and WMI SNMP Provider. 7. Click OK. 8. Click Next and follow instructions to complete installation. To install the SNMP service in Windows 2008, perform the following steps: SNMP Trap Monitoring Solution: Technical Notes 3

4 Configuration for a small SourceOne deployment 1. Open the Control Panel and view by category. 2. Click Turn Windows features on or off under Programs category. The Server Manager MMC component appears. 3. Click Features node. 4. Click Add features to open Add Features Wizard. 5. In the Features list, ensure a check exists for SNMP services and SNMP WMI Provider. 6. Click Next then click Install and follow instructions to complete. Configuring an agent To configure the SNMP agent, perform the following steps: 1. Open the services MMC app. 2. Right-click on the SNMP service. 3. Select Properties. 4. Select the Agent tab. 4 SNMP Trap Monitoring Solution: Technical Notes

5 Configuration for a small SourceOne deployment 5. Add the name of the person to contact (for example: the network administrator) and the location of the contact. Figure 1 SNMP Service Properties (Local Computer) Agent Note: Microsoft deprecated SNMP in Windows Server This can result in a missing Agent tab after installing the SNMP Service. Consult Microsoft s documentation to add the Agent tab. To configure the trap destination, perform the following steps: 1. Click the Traps tab. 2. Click Add. SNMP Trap Monitoring Solution: Technical Notes 5

6 Configuration for a small SourceOne deployment 3. Type the hostname, IP address, or IPX address of the computers running an SNMP manager program. Figure 2 SNMP Service Properties (Local Computer) Traps Note: Microsoft deprecated SNMP in Windows Server This can result in a missing Traps tab after installing the SNMP Service. Consult Microsoft s documentation to add the Traps tab. Configuring community names The SNMP service must have at least one community name. Public is the installation default community name which you can edit or remove. 6 SNMP Trap Monitoring Solution: Technical Notes

7 Configuration for a small SourceOne deployment You can add and remove community names by using the Security tab and also filter the type of packets that the computer accepts. Figure 3 SNMP Service Properties (Local Computer) Security Note: Microsoft deprecated SNMP in Windows Server This can result in a missing Security tab after installing the SNMP Service. Consult Microsoft s documentation to add the Security tab. Importing event configurations The event configuration file (cnf) contains entries of events. The entry format is as follows: #pragma add EventLogFile EventSource EventID [Count [Period] ] For example: #pragma add "EMC" "EMC SourceOne" SNMP Trap Monitoring Solution: Technical Notes 7

8 Configuration for a large SourceOne deployment You can edit the cnf file by using a text editor. The evntcmd.exe program is an event to trap translator configuration tool that you can type at a command line. You can use this program to import a cnf file. For example: evntcmd <cnf_file_path> Figure 4 evntcmd.exe command The SourceOne installation CD includes a sample cnf file. The file: path is Setup\Monitoring\SNMP name is sourceone_snmp.cnf Consult Microsoft s documentation for more information regarding syntax. Completing the configuration To complete the configuration, go to Customizing SNMP Trap on page 11. Configuration for a large SourceOne deployment For a large SourceOne deployment (for example: the SourceOne environment is complicated with many nodes), EMC configures the Microsoft SCCM to make the translation efficient by using SCCM to add or enable the SNMP service component, adding a program in SCCM, and advertising the program. 8 SNMP Trap Monitoring Solution: Technical Notes

9 Configuration for a large SourceOne deployment Using SCCM to add or enable the SNMP service component To use SCCM to add or enable the SNMP service component, perform the following steps: 1. Install or configure SCCM. 2. Add or enable the SNMP service component. Consult Microsoft s documentation for more information about these steps. Adding a program in SCCM and advertising the program To add a program in SCCM and advertise the program, perform the following steps: 1. Create a package. 2. Create a program for the package. Figure 5 New Program Wizard SNMP Trap Monitoring Solution: Technical Notes 9

10 Configuration for a large SourceOne deployment Importing event configurations The event configuration file (cnf) contains entries of events. The entry format is as follows: #pragma add EventLogFile EventSource EventID [Count [Period] ] For example: #pragma add "EMC" "EMC SourceOne" You can edit the cnf file by using a text editor. The evntcmd.exe program is an event to trap translator configuration tool that you can type at a command line. You can use this program to import a cnf file. For example: evntcmd <cnf_file_path> Figure 6 evntcmd.exe command The SourceOne installation CD includes a sample cnf file. The file: path is Setup\Monitoring\SNMP name is sourceone_snmp.cnf Consult Microsoft s documentation for more information regarding syntax. Distributing After you create the program, you can distribute the package and advertise the program to a SCCM client. 10 SNMP Trap Monitoring Solution: Technical Notes

11 Customizing SNMP Trap Completing the configuration To complete the configuration go to Customizing SNMP Trap on page 11. Customizing SNMP Trap You can use an event to trap translator to configure events. The event to trap translator manages the event to trap mappings. To customize SNMP trap settings, first view a graphical list of all registered events and then configure available events and their corresponding SNMP traps. Viewing a graphical list of all registered events To view a graphical list of all registered events, at a Run menu or a command line prompt, type the following: evntwin.exe Figure 7 Example of an import of a sample cnf file from the SourceOne installation CD in view mode SNMP Trap Monitoring Solution: Technical Notes 11

12 Customizing SNMP Trap Configuring available events and their corresponding SNMP traps You can select the events that you want to map to SNMP traps by using the event to trap translator. To configure available events and their corresponding SNMP traps, perform the following steps: 1. View a graphical list of all registered events. 2. Click the Edit button to manage the available events and their corresponding SNMP traps. You can also add events, remove events, and export them to a cnf file. Figure 8 Example of an import of a sample cnf file from the SourceOne installation CD in edit mode 12 SNMP Trap Monitoring Solution: Technical Notes

13 NMS example of an SNMP trap monitoring solution 3. Double-click an event to monitor it. Figure 9 Properties 4. Change if applicable the event count or period (interval). 5. Restart the SNMP service in order for the changes to take effect. NMS example of an SNMP trap monitoring solution The following is a NMS example of an SNMP trap monitoring solution. The example uses HP BTO Software (HP OpenView). EMC does not provide support for using an NMS product, including HP BTO Software. Contact HP if you have any questions. Perform the following steps to view any SourceOne errors that exist: 1. Import a mib file by typing the following at a command line prompt to generate policy files from the mib file: SNMP Trap Monitoring Solution: Technical Notes 13

14 NMS example of an SNMP trap monitoring solution mib2policy -p PolicyName MIBFilePath Figure 10 Administrator: Command Prompt mib2policy command The SourceOne installation CD includes a sample mib file. The file: path is Setup\Monitoring\SNMP name is SourceOneEvents.mib 2. At the command line prompt, type the following to upload the policy: ovpmutil cfg pol upl PolicyName_header.xml /asterisk Figure 11 Administrator: Command Prompt ovpmutil command 14 SNMP Trap Monitoring Solution: Technical Notes

15 Glossary 3. Navigate to HP Operations Manager and view any SourceOne errors. Figure 12 HP Operations Manager Glossary The following glossary describes terms within this document: Table 1 Glossary (page 1 of 2) Term Agent Community String NMS Managed Device Description An agent is a network-management software module that resides on a managed device. An agent has local knowledge of management information and translates that information to or from an SNMP specific form. A method to authenticate clients. Network Management System. Executes applications that monitor and control managed devices. A NMS provides most of the processing and memory resources required for network management. More than one NMS may exist on any managed network. A managed device is a network node that implements an SNMP interface that allows unidirectional (read-only) or bi-directional access to node-specific information. Managed devices exchange node-specific information with the NMS. SNMP Trap Monitoring Solution: Technical Notes 15

16 Glossary Table 1 Glossary (page 2 of 2) Term Microsoft SCCM MIBs OIDs SNMP Traps Description Microsoft System Center Configuration Manager. SCCM is a systems management software product that manages large groups of computers running various operating systems. Management Information Bases. MIBs describe the structure of the management data of a device subsystem. Object Identifiers. OIDs uniquely identify managed objects in a MIB hierarchy. Simple Network Management Protocol. A SNMP manages devices on IP networks. Some examples of devices that typically support SNMP include routers, switches, servers, workstations, and printers. Traps are asynchronous notifications from agent to manager. Copyright EMC Corporation. All rights reserved. Published in the USA. Published September 2013 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC 2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support ( 16 SNMP Trap Monitoring Solution: Technical Notes