Home > MOM > HP EVA Management Pack

HP EVA Management Pack

If you have EVA in your environment, then maybe you have tried to deploy the HP management pack for EVA.

The few things I noticed was that HP left two servers in the included tab of the HP Enterprise Storage computer group.  You may want to remove these.

The other thing I noticed is that you may get several alerts from all of your agents for failure to contact WMI namespace.  There is a rule in the MP that looks for a SNMP Trap namespace that can be enabled on the EVA systems.  If you are not using SNMP to alert from the switches and other SNMP capable devices, then you might want to disable this rule.

The computer groups basically include ALL your agents and apply rules to all of your servers.  This is not necessary, so you should remove that criteria, and then include just your command view server and the MOM server that WEBES will send XML feeds too for alerting.

You can feed mom via POP3, SNMP, and XML.  The preferred method is XML.  So when you install this MP, you need to do so on one of your management servers.  The reason that this MP is not just a .akm is because HP installs a service called WEBES Listening Service.  This service will sit on the management server that you want to receive XML alerts from EVA on.

During the set up you will be prompted for POP3 server information, you can skip through that if you will not use POP3 as your notification transport.  After the install, you will need to import the management pack.  Once you have done this, the set up is basically done for MOM.

On your command view server (the server that manages the EVA San), you must ensure DESTA is on and that it is talking to the MOM management server.  At a command prompt you just type “DESTA on” then you enter “DESTA mom on”.  When you do this you will get a prompt for the management server name and port.  The port is a default number and should not need to be changed.  Enter your MOM server name and the port and you are done.

HP does have a test alert that can be generated, however you may want to create a real issue on the SAN to see the alerts that are generated in MOM.  One thing you will notice is that the domain for the command view server might be listed incorrectly in MOM.  If you have multiple domains that EVA is deployed to, then anything that WEBES feeds to MOM will have the correct computer name, but the domain will be listed as the domain where your management server exists.

On the MOM management server, you can turn up logging for the WEBES listening service to ensure it is getting alerts.  There is also an XML document that gets generated in the HP directory. 

When we were initially deploying this management pack we ran into some issues because I changed the computer group formulas and was not including the MOM server that WEBES was alerting too.  However, after a little troubleshooting it became clear that we had to include the management server that is receiving the feeds.

The only other outstanding issue has to do with some additional computers MOM finds.  Each of our command view servers has a MOM agent on them, however in the MOM Admin console we still see the two same servers listed, but with no management server assigned to them and no option to install an agent (in the unmanaged computers view).  There is also another server listed called HPWEBES with a domain HPWEBES.  We have not heard back from HP as to why this is.  This minor issue is harmless, but if you like a clean MOM environment, then this might irritate you. 

The mystery for this has been solved.  HP EVA management servers feed the MOM management server alerts via XML and then the alerts are raised on behalf of the agent by the MOM Management server.  Therefore, these names don’t map one to one with the agents, so they are listed as unmanaged with no management server as the owner.  In drop down lists you can identify these servers because they have a square character after their names.

HP is working on a second version of this management pack that makes things a lot better for you in regards to monitoring EVA with MOM.  The major issue I see so far is that you can only have the WEBES send XML to one management server.  This is a single point of failure.  However I am told that HP is changing this in the new management pack and version of WEBES.

Do you have EVA?  Are you using MOM to monitor it?  Let me know.

Categories: MOM
  1. Manjun
    August 17, 2006 at 9:23 am

    I got the following message in the WEBESListenerLog.log file after run WSEA test on the CommandView server, does it means the MOM management server can get alert from EVA? Thank you.
    POST /ms/eventWebesXML HTTP/1.1User-Agent: HttpConnection/1.0Host: umdmom02:8945Accept: image/gif, image/jpeg, */*Accept-Encoding: gzipContent-Type: text/xmlContent-Length: 2479
    <?xml version="1.0" encoding="UTF-8"?><ProblemReport>  <Severity>MAJOR</Severity>  <ReferenceCode>SEATEST event callout</ReferenceCode>  <BriefDescription>SEATEST event callout</BriefDescription>  <evidence>Analysis Revision: SEATEST Rules V1.2Event Time:        Thu 17 Aug 2006 11:11:54 GMT-04:00</evidence>  <DateOccured>java.util.GregorianCalendar[time=1155827514000,areFieldsSet=true,areAllFieldsSet=true,lenient=false,zone=java.util.SimpleTimeZone[id=Custom,offset=-14400000,dstSavings=3600000,useDaylight=false,startYear=0,startMode=0,startMonth=0,startDay=0,startDayOfWeek=0,startTime=0,startTimeMode=0,endMode=0,endMonth=0,endDay=0,endDayOfWeek=0,endTime=0,endTimeMode=0],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2006,MONTH=7,WEEK_OF_YEAR=33,WEEK_OF_MONTH=3,DAY_OF_MONTH=17,DAY_OF_YEAR=229,DAY_OF_WEEK=5,DAY_OF_WEEK_IN_MONTH=3,AM_PM=0,HOUR=11,HOUR_OF_DAY=11,MINUTE=11,SECOND=54,MILLISECOND=0,ZONE_OFFSET=-14400000,DST_OFFSET=0]</DateOccured>  <NotificationDestinations>    <OS>true</OS>    <Customer>true</Customer>    <Provider>true</Provider>    <Script>true</Script>    <UserInterface>true</UserInterface>  </NotificationDestinations>  <WCCVersion>Web-Based Enterprise Services Common Components for Windows V4.4.3 (Build 50), member of Web-Based Enterprise Services Suite for Windows V4.4.3 (Build 50)</WCCVersion>  <Obligation>    <State>Valid</State>    <ObligationNumber>USE05338L3</ObligationNumber>    <SerialNumber>USE05338L3</SerialNumber>    <ServiceProvider>Hewlett-Packard Company</ServiceProvider>  </Obligation>  <RouteCode>SICL</RouteCode>  <NodeName>NWSANMGT01</NodeName>  <Profile>    <profileLine>No Profile Set</profileLine>  </Profile>  <CAProblemReport>    <ManagedEntity>SEATEST event callout</ManagedEntity>    <ReportingNode>NWSANMGT01</ReportingNode>    <ReportingOS>Windows</ReportingOS>    <CalloutID>SEATEST event callout</CalloutID>    <FullDescription>This report was generated as a result of analyzing a SEATESTevent.  Please refer to the SEA User Guide for analysis details and command verb syntax.</FullDescription>    <FRUList>No service action is required.</FRUList>    <EventTime>Thu 17 Aug 2006 11:11:54 GMT-04:00</EventTime>    <CreationTime>Thu 17 Aug 2006 11:12:08 GMT-04:00</CreationTime>    <ExpirationTime>Thu 17 Aug 2006 11:11:54 GMT-04:00</ExpirationTime>    <CAVersion>System Event Analyzer for Windows V4.4.3 (Build 50)</CAVersion>  </CAProblemReport></ProblemReport>
    Handshaking messageBytes value: HTTP/1.1 200 Document FollowsDate: 8/17/2006 11:12:16 AMServer: JavaHttpServer/0.1Last-Modified: 8/17/2006 11:12:16 AMContent-type: text/htmlContent-length: 8Content-Language: en-us
    Got it!
    Waiting for a connection…

  2. Blake
    September 2, 2006 at 11:32 am

    Not sure, just looks to me like a handshaking test.  If you import the management pack, be sure to associate your MOM management server that will recieve XML feeds from WEBES with the HP computer group.  I changed the computer groups in the HP management pack to not include all computers, then I added the command view server, the clusters, and my MOM management server that will get the XML feeds.  Once we turned on WEBES (desta mom on – I think this is the command) we were able to look at the XML log files on the MOM management server in the Program Files\\HP directory.  We also generated some alerts and saw that they were picked up in MOM.  HP has a test alert that they include, but I do not think it works.  You are going to have to pull a few drives and or a fiber cable so that the Management pack will generate an alert.

  3. Dan
    September 24, 2006 at 2:26 am

    Hi Blake, I am in the process of deploying the MP and I too have made the mistake of not including the MOM server in the computer group. Will do this tomorrow and report on my progress.
    WRT the servers \’stuck\’ in unmanaged mode in the MOM console; have you tried deleting them from MOM? If the MOM agent is installed and can successfully contact the MOM server then it should reappear as a manually installed agent pending approval, although you\’ll need to disable the \’Reject New Manual Agent Installations\’ option and restart the MOM service first.
    Thanks for the blog, the information could turn out to be invaluable 😉

  4. Blake
    September 25, 2006 at 2:43 pm

    In regards to the "orphaned" servers in your MOM admin console I finally figured it out.  You should see HPWebes and any of your EVA management servers.  You will notice that they are not managed by any MOM server.  Why is this?  Because these are the instances of those computers that are being used to RAISE alerts by your MOM management server (the one you configured DESTA to send alerts to).  In otherwords (similar to SNMP traps to MOM), when the MOM management server raises an alert on behalf of an agent, then those computer names will appear in unmanaged computers with no management server associated with them.  You can delete them, but they will come back.  Also, when creating computer groups you will notice these servers because they have the servername plus a BLOCK character after them.  It\’s annoying, but you can work with it.  Until you include the MOM server in the computer group (HP Enterprise Storage) you will not get any HP EVA alerts (from the HP management pack).  This would happen in MOM 2000 when you would use a tool to create an event log entry on a server.  The resource kit tool (from windows – forget the name) would generate an event on a server, but your workstation would be the computer name.  Then if you looked in all computers in the mom console, you would see your workstation.  That took me some time to figure out as well.  I am assuming this is the same behavior in MOM 2005.

  5. Dan
    September 26, 2006 at 2:40 am

    Hi again Blake,
    I have looked again at the configuration in MOM. I have added the MOM server in to the HP Enterprise Storage MOM group. I have noticed that the rule (HP Enterprise Storage Event Collector) is disabled. As I understand it this rule executes the script that gathers all the storage related information (HP Enterprise Storage Event Provider) every 10 minutes; without this script running none of the rules would ever fire. I am in the process of digging through the script content (no comments, thanks HP), one of the first things I notice is that it reads a config file ("C:\\Program Files\\HP\\HP Enterprise Storage\\DataFile") that is hard coded in the script – however on my MOM server this file does not exist. Have I downloaded a very poor beta vesion here!?!?!

  6. Dan
    September 26, 2006 at 9:09 am

    Back again, with a better understanding this time (I hope!). Now I have fully digested the "HP Enterprise Storage Event Provider" script I realise that it is purely focused on POP3 collection of WEBES notifications sent as SMTP, they could have given it a getter name! At last I have managed to get WEBES forwarding reports as XML; I have installed WEBES version 4.5 and apart from enabling MOM notifications using the command "DESTA MOM ON" I didn\’t have to do anything else.
    I know realise that the "WEBESEventListener" service that receives the XML file from WEBES, is responsible for raising the events in MOM. Hurray, at last I am receiving events in to MOM from WEBES. I found it a little annoying that the event generated with the "WSEA TEST" command is not forwarded to MOM as an event, it appears to be dropped at the event listener service.
    Hope this blog helps someone else out too.

  7. Blake
    September 26, 2006 at 11:42 am

    Congrats Dan.  Now do yourself a favor and create a rule that monitors the HP EVA error log so you can keep an eye on when there are problems with phone home or other issues with the EVA Management server.

  8. Unknown
    November 28, 2006 at 5:40 am

    Thanks for the helpful remarks. We also ran into the same configuration issues with HP StorageWorks MP version 1.5.1, trying to forward HP EVA errors and warnings to MOM. Today I found that there is a new Management Pack version 2.0 available at HP website
    I will update our version from 1.5.1 to 2.0 and give you an update tomorrow

  9. Unknown
    December 1, 2006 at 2:52 am

    I installed the new version 2.0 of HP StorageWorks MP, which has a new Rule Group structure below
    HP Enterprise Storage
    – HP Enterprise Storage SNMP Provider
    – HP Enterprise Storage WEBES Provider
    and so on…

  10. Unknown
    December 1, 2006 at 3:02 am

    Also, Computer Group assignments have changed in version 2.0. Now MOM Management Servers are added by default, and no longer all Computers are added (by Search) to "HP Enterprise Storage", which was wrong. Unfortunately, the old Rule Group structure (version 1.5.1) was not deleded and kept during update. Thus we ended up with two separate Rule Groups "HP Enterprise Storage" in MOM Administrator Console, which is not very nice. Nevertheless, a first error alert was forwarded from our HP EVA to MOM by the HP StorageWorks MP (version 2.0) rule HP Enterprise Storage\\HP Enterprise Storage WEBES Provider\\HP Enterprise Storage EVA\\HP Enterprise Storage Enterprise Virtual Array Errors correctly today. 
    Regards Volker

  11. Blake
    December 4, 2006 at 11:08 pm

    I installed the new version in one of our labs.  HP told us it would create a new group, and not import over the old one.  So you found that out the hard way I guess (so did I).  I am not sure it\’s "that" much better then the old one yet.  Seems pretty much the same.  There might be some new features that I have not found yet.

  12. Unknown
    October 16, 2007 at 11:52 am

    I have just installed the HP Storagrworks pack and can monitor my EVA from it fine using XML and WEBES. however i keep getting this error since installing the pack on all my HP servers in the OPS MGR log, any ideas??
    Event Type: ErrorEvent Source: Health Service ModulesEvent Category: NoneEvent ID: 9100Date:  10/16/2007Time:  2:46:22 PMUser:  N/AComputer: PRDMGTPH01Description:An error occurred on line 576 while executing script \’HP Enterprise Storage SNMP Trap Event Provider\’Source: Microsoft VBScript runtime errorDescription: Path not found
    One or more workflows were affected by this. 
    Workflow name: HPEnterpriseStorage.Trap.Catcher.Rule Instance name: HP Enterprise Storage SNMP Trap Catcher Discovery Instance ID: {ABD77DEF-34E9-B6DD-9ACA-A6CF31BDE6E7} Management group: ESG_SCOM
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  13. Blake
    October 18, 2007 at 2:44 pm

    Is that from MOM 2005 or 2007?  The SNMP error is common if that rule is enabled and the WMI namespace does not exist.  Look in the HP EVA MP for a rule that uses SNMP.  Disable this.  You only need this rule if you are sending SNMP from EVA to MOM.

  14. Patrick
    December 1, 2008 at 3:59 am

    I have the HPEnterpriseStorage.Trap.Catcher.Rule disabled but further receiving the SNMP error. Any idea?!

  15. Blake
    December 11, 2008 at 7:32 pm

    There are a few other snmp rules that you will need to find.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: