HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

how to monitor Redundancy power supply(ProLiant ML350 G4p ) in SIM

 
javaaobo
Occasional Contributor

how to monitor Redundancy power supply(ProLiant ML350 G4p ) in SIM

how can I monitor Redundancy power supply in SIM
when Redundancy power supply fail,I want get email
------------------
now i just know can set monitor funtion at
SIM->Options->Events->Automatic Event Handling->New Task->new a task->Create an automatic event handling task->with event and system attributes that I will specify
---------------------
Then I want choice which one,can monitor Redundancy power supply

Thanks
3 REPLIES
Rancher
Honored Contributor

Re: how to monitor Redundancy power supply(ProLiant ML350 G4p ) in SIM

Thry setting it up like this. In New Task, after you name the task, in Select Events, select "use event attributes that I will specify." THen in Select Events, choose "where event type is." A box will come up with the available events, and you can select "system and environmental events." There is a "power supply failed" option there that you can select.
javaaobo
Occasional Contributor

Re: how to monitor Redundancy power supply(ProLiant ML350 G4p ) in SIM

setup done,
I have other question
1.why my ML350 G4p's power supply was fail,but I still have not get mail for this event,my mail alarm setting is no problem,I always can get mail for server "System is unreachable: SIM Event"
2.Or the power supply was fail long time,then this event is new task,so can not monitor,is right?
Rancher
Honored Contributor

Re: how to monitor Redundancy power supply(ProLiant ML350 G4p ) in SIM

If this has already failed, you won't get an alert unless you reboot the server, restart the agents, or run hardware polling.