ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

ilo4 RIBCL scripting question, please? How can I test the ILO AlertMail feature from a script?

ukdc
Advisor

ilo4 RIBCL scripting question, please? How can I test the ILO AlertMail feature from a script?

Hi

Our ILOs are set up to send alerts via email in the usual way and testing the feature from the ILO web GUI works as expected. What I would like to do is be able to test the feature from a script (eg to have a periodic check that can be run across the entire estate to verify that the alerting mechanism is in good shape).

Although HP's perl scripting toolkit shows examples of configuring these settings via script, I cannot find any way of initiating a test of AlertMail.

Any ideas, please?

 

 

3 REPLIES
ukdc
Advisor

Re: ilo4 RIBCL scripting question, please? How can I test the ILO AlertMail feature from a script?

FYI the newer "hprest" tool makes it easy to trigger a test of the AlertMail feature (so this will be the method in the future; for now it would be nice to use the existing scripting framework). You just POST the following chunk of JSON to the ILO:

{
    "path": "/redfish/v1/Managers/1/NetworkService/Actions/Oem/Hp/HpiLOManagerNetworkService.SendTestAlertMail",
    "body": {
        "Action": "SendTestAlertMail"
    }
}

 

Jimmy Vance
HPE Pro

Re: ilo4 RIBCL scripting question, please? How can I test the ILO AlertMail feature from a script?

Nice find. I did some checking and the only thing I could  come up with is the SMASH CLP command oemhpe_send_TestAlertmail  to send the an AlertMail test from the iLO command line

 




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
ukdc
Advisor

Re: ilo4 RIBCL scripting question, please? How can I test the ILO AlertMail feature from a script?

Jimmy,

 

Thanks for the suggestion. It looks like the "command" I'm looking for was overlooked in the design (or it would surely appear in some documentation, example scripts or someone's blog!). HP's answer would probably be "switch to the 'hprest' method as that is the future" which is hard to argue with (it's not reasonable to expect them to spend any development $$ adding this feature into the "old" scripting interface).

 

Regards,

Richard.