HP LeftHand SAN Solutions

Transcription

1 HP LeftHand SAN Solutions Support Document Service Notes How to Test SNMP with LeftHand SAN

2 Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notices Copyright 2009 Hewlett-Packard Development Company, L.P. 2

3 How To - Test SNMP with LeftHand SAN Summary Simple Network Management Protocol (SNMP) is a protocol that SAN administrators use to monitor the health of their SAN. SAN/iQ supports SNMP monitoring by sending trap information Procedure There are several steps involved in testing SNMP. 1 Download MIBs 2 Download SNMP utilities 3 Setup SNMP access 4 Test query access 5 Test traps reception 6 Troubleshoot Download MIBs If you are using SAN/iQ version 6.3, then the MIBs are placed in the installation folder of the Centralized Management Console by default. You can also download the MIBs from our ftp site at ftp://ftp.lefthandnetworks.com/ <release version>. Download SNMP Utilities The following links will help you to get SNMP utilities for Windows and Unix. ftp://ftp.lefthandnetworks.com/utilities/snmp_windows_client/ net-snmp pre1-1.win32.exe 3

4 search.php?query=net-snmp-utils&submit=search+...&system=&arch = Set Up SNMP Access Refer to the LeftHand SAN User s Manual or the online help in the Console and review Chapter 7. titled Using SNMP, for the guidelines to configure the SNMP General and SNMP Trap settings in the Console. The SNMP General settings allow you to configure the community string and access for an SNMP client to query the NSM. The SNMP Trap settings allow you to list the SNMP clients for which you want to receive trap events for monitoring variables that have been configured to send SNMP traps. Instructions for configuring variables for sending SNMP traps are in the Active Monitoring section of the Reporting chapter of the User's Manual or online help. Note In the 6.3 version of the Console, every time the access control list on the SNMP General tab is modified, the community string must be modified as well before the changed settings can be successfully applied. Once the access control list is modified, the community string can be reconfigured back to the original string. Test Query Access Test the access control configuration and SNMP Query/Response by running the following commands on the host. If the responses to these commands are received as illustrated below, then you have verified that the host has access to exchange SNMP queries/response with the NSM. snmpwalk -v 2c -t 10 M <path to folder containing the MIBs> -m all <ipaddress of nsm>-c <community-string>.iso.org.dod.internet.private.enterprises.lefthandnetworks.lhnproducts.lh nnusdevicesmibs.l hnnuscommonmib.lhnnuscommonobjs.lhnnuscommoninfo.infoserial Number.0 The output of this command should return the MAC address of the NSM. For example, LEFTHAND-NETWORKS-NUS-COMMON-INFO-MIB::infoSerialNumbe r.0 = STRING: 00:30:48:2D:93:0E 4

5 snmpwalk -v 2c -t 10 M <path to folder containing the MIBs> -m all <ip of nsm> -c <community-string>.iso.org.dod.internet.private.enterprises.lefthandnetworks.lhnproducts.lh nnusdevicesmibs.l hnnuscommonmib.lhnnuscommonobjs.lhnnuscommoninfo.infomodel. 0 The output of this command should return the model of the NSM. For example, LEFTHAND-NETWORKS-NUS-COMMON-INFO-MIB::infoModel.0 = STRING: "NSM160" snmpwalk -v 2c -t 10 M <path to folder containing the MIBs> -m all c nsmtraps.iso.org.dod.internet.private.enterprises.lefthandnetworks.lhnproducts.lhn NusDevicesMIBs.l hnnuscommonmib.lhnnuscommonobjs.lhnnuscommoninfo.infosoftwa reversion.0 The output of this command should return the software version NSM. For example, LEFTHAND-NETWORKS-NUS-COMMON-INFO-MIB::infoSoftwareVers ion.0 = STRING: Test Trap Reception The following command will catch any traps that are sent by the NSMs to the host configured as a trap recipient. snmptrapd -f -Le To test SNMP trap reception, do the following. 1 Configure the remote copy monitoring variables (Remote IP Copy Status, Remote IP Copy Complete and Remote IP Copy Failover) to send SNMP traps. 2 Create a test remote copy within the management group and run this command on the host. snmptrapd -f -Le 5

6 If a trap is successfully received, the following output message will be displayed :37:59 NET-SNMP version Started :39: [UDP: [ ]:37283]: SNMPv2-MIB::sysUpTime.0 = Timeticks: (298618) 0:49:46.18 SNMPv2- MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises SNMPv2-SMI::enterprises = STRING: Management Group: IntRipc ; Remote Copy Volume: 'RC_Sch_0_Rmt.484' Complete = true. SNMPv2- SMI::enterprises = Hex-STRING: 07 D5 0B 0B 0D 08 1C 00 2B Change the remote snapshot to primary and notice a new trap message on the host. Right-click on the remote volume and select Edit Volume. Change the Type from Remote to Primary. Check for the new trap message, show below :39: [UDP: [ ]:37283]: SNMPv2-MIB::sysUpTime.0 = Timeticks: (298629) 0:49:46.29 SNMPv2- MIB::snmpTrapOID.0 = OID:SNMPv2-SMI::enterprises SNMPv2- SMI::enterprises = STRING: Management Group: IntRipc; Change to Primary for Remote Copy Snapshot: RC_Sch_0_Rmt.482 = true. SNMPv2-SMI::enterprises = Hex-STRING: 07 D5 0B 0B 0D 08 1C 00 2B Troubleshoot Verify that the server can ping NSMs. Verify that NSMs can ping server. Verify that the community string is the same on the NSM and the SNMP management application. Verify that the correct IP addresses for the hosts are added to the access control lists for SNMP General and SNMP Trap settings. If running snmptrapd returns an error message udp port 161 already in use, then stop any other SNMP client services that are running on that host before running snmptrapd. 6