Server Management - Systems Insight Manager
1826523 Members
4076 Online
109695 Solutions
New Discussion

monitoring Eva 5000 with SIM4.1

 
Ben Butler
Advisor

monitoring Eva 5000 with SIM4.1

I can see the SMA and am getting traps etc from it, I have the MIB compiled and registered for the EVA. I cannot work out how i am able to get events directly from the EVA ans not via the SMA? does any one have any ideas????
11 REPLIES 11
Rob Buxton
Honored Contributor

Re: monitoring Eva 5000 with SIM4.1

Well you've got further than we have.
Our SMA sends out the SNMP Traps to our SIM Server, but HPSIM doesn't recognise them.
I know they're arriving at the HPSIM Server from a small utility we got.

Why are you trying to get the EVA to deliver SNMP Traps directly rather than the SMA?
Ben Butler
Advisor

Re: monitoring Eva 5000 with SIM4.1

I suppose its out of curiosity, as there is a CPQHSV110v3.MIB i just wondered if using this instead of the cpqsanevent.mib would give me any different information about the EVA. I have just discoverec though, that alerts from the SMA also use the CPQHSV110v3.MIB. so i suppose that answers my question.

Do you have the latest insight agents etc, installed on your SMA?
Joe Hegyi
Advisor

Re: monitoring Eva 5000 with SIM4.1

I haven't been able to get this to work either. Sometimes I really miss the old Win32 Insight Manager. CIM is the biggest pain the in backside to work with.
Joe Hegyi
Advisor

Re: monitoring Eva 5000 with SIM4.1

Oops, i meant SIM :)
Rob Buxton
Honored Contributor

Re: monitoring Eva 5000 with SIM4.1

Ben,
No, we don't have the latest Agents on the SMA, I thought you needed to be fairly careful about what's installed on the SMA. They're still at 6.30, we tend to leave that to the HP guys to update.
We do have the latest Agents installed everywhere else though.
I'll check to see if we can update the Agents and to what version.
Ben Butler
Advisor

Re: monitoring Eva 5000 with SIM4.1

We are running 6.30 agents on our SMA, so you should be ok there. are you using any discovery filters? it may be worth specifying the IP range of your SMA and removing discovery filters then re running the discovery process. Also check the automatically discover a system when an event is recieved. you then might be able to get it recognised by setting up and sending a test SNMP trap from the SMA. It might also be worth adding the SNMP forwarding details on to your EVA's through command view.
Rob Buxton
Honored Contributor

Re: monitoring Eva 5000 with SIM4.1

Ben,
Thanks, but that's how we run anyway, without Discovery Filters.
New systems are discovered fine.

If we generate an SNMP Trap using the HP Management Agents GUI from the SMA Server HPSIM sees the trap fine, if we use the SMA software to generate the trap, it doesn't make it to HPSIM, only as far as the HPSIM Server.

We have some HP guys here looking at it so hopefully we'll be underway soon.
Kevin Everts_1
Regular Advisor

Re: monitoring Eva 5000 with SIM4.1

Does anyone know if you can install the latest agents on the management appliance? We just got an EVA and I would like to update the agents from 6.40.

On a side note, are you supposed to run Windows update on that server?
Rob Buxton
Honored Contributor

Re: monitoring Eva 5000 with SIM4.1

Kevin,
Genearlly the SMA is either updated by HP or by using specific SMA packages.
They also seem to have a list of hotfixes that don't break it.

Ben,
I found that SNMP was working all along, the traps were just turning up as Informational. The SNMP Traps when sent from the HP Management Agent GUI turn up with a Severity of Major. I'd assumed they'd be the same!
Michael Browne_1
New Member

Re: monitoring Eva 5000 with SIM4.1

I'm having similar problems in that SIM can receive normal insight traps, as tested through the mangement agents test trap, but the EVA traps arent being picked up at all although I can see them being sent to the SIM box through a sniffer, for some reason SIM isnt processing the traps.

I did notice in the packet that the traps sent from the appliance default to 'public' authentication community string instead of using our standard community string, unlike the test trap form the agents which uses the correct string. Is there a way to change the community string that is included in the trap from Command View EVA?
Ben Butler
Advisor

Re: monitoring Eva 5000 with SIM4.1

solution to problem was not resolved as such, but the answer to the question regarding SNMP alerts from an EVA was answered